Voice data single-line communication method and device

Abstract

The invention provides a voice data single-line communication method and device, and the method comprises the following steps: S1, a client transmits equipment information to a main control end, and the main control end receives and verifies the equipment information, thereby achieving the communication authentication of two parties; s2, in a silent state, the client sends an encrypted first-time communication verification message to the master control end, and the master control end receives and verifies the first-time communication verification message and reversely sends an encrypted second-time communication verification message to the client based on the first-time communication verification message; s3, the client receives and verifies the second communication verification message, and sends an encrypted third communication verification message to the master control end based on the second communication verification message; and S4, repeating the steps S2-S3, in a communication state, sending the encrypted voice data to the client by the master control end, receiving and verifying the voice data by the client, and executing a corresponding instruction action. According to the invention, the client and the master control end can realize a safe and efficient communication function through the single-line channel in an offline state.

Description

Technical Field

[0001] The present invention belongs to the technical field of data communication, and in particular relates to a single-line voice data communication method and device. Background Art

[0002] In the field of modern data communication, I2C (Inter-Integrated Circuit) and UART (Universal Asynchronous Receiver-Transmitter) are the two most common serial communication methods, which are widely used in various embedded systems, sensor networks and inter-device communications. Among them, I2C uses a two-wire system, and the SCL and SDA communication lines need to be used respectively to realize the data communication function between different devices, while UART is also a two-wire system, and the TX (transmission) and RX (reception) communication lines need to be used respectively to realize the data communication function between different devices. The hardware connection requirements based on the two-wire communication will occupy more pins of the main control chip, and the circuit wiring will be more complicated, resulting in a significant increase in the cost of hardware use. At the same time, under the existing technology, in the process of data communication, usually only physical security measures (such as anti-tampering hardware) and network security protocols are used to solve the problem of data transmission security. However, in the scenario of offline communication, due to the limitations of hardware and protocols, it is not easy to build a data security transmission mechanism, which makes it difficult to ensure the security and integrity of data transmission. Summary of the invention

[0003] The present invention provides a single-line voice data communication method and device to solve the technical problem that conventional data communication methods and devices in the prior art cannot efficiently and safely realize the single-line data communication function in an offline state.

[0004] To solve the above problems, the technical solution of the present invention is: a single-line voice data communication method, comprising the following steps: S1: The client sends device information to the master control end, and the master control end receives and verifies the device information. If the verification is successful, the communication authentication between the client and the master control end is realized; S2: In a silent state, the client sends an encrypted first communication verification message to the master control end, the master control end receives and verifies the first communication verification message, and sends an encrypted second communication verification message back to the client based on the first communication verification message; S3: the client receives and verifies the second communication verification message, and sends an encrypted third communication verification message to the main control end based on the second communication verification message; S4: Repeat steps S2-S3 until the master control end enters a communication state. In the communication state, the master control end sends encrypted voice data to the client, and the client receives and verifies the voice data and executes corresponding instruction actions.

[0005] Preferably, in S1, the client sends device information to the master control end, further comprising the following steps: S11: The client obtains its own MAC address, uses the AES symmetric encryption algorithm and adopts its CBC working mode to encrypt the MAC address of the client, and sends the encrypted device information to the main control end through a single-line channel.

[0006] Preferably, in S1, the master control end receives and verifies the device information, further comprising the following steps: S12: A mac address whitelist is preset in the main control end. The main control end receives the encrypted device information, uses the AES symmetric encryption algorithm to perform reverse decryption processing, extracts the mac address of the current client, and verifies whether the mac address of the current client is in the mac address whitelist. If so, the communication authentication between the client and the main control end is successful, and the main control end sends an authentication success result to the client. If not, the communication authentication between the client and the main control end fails, and the main control end sends an authentication failure result to the client.

[0007] Preferably, the master control end and the client locally have a heartbeat count Beat_cnt(1) preset respectively. 2 When the master and the client receive a communication verification message, the locally preset heartbeat count Beat_cnt(1) is enabled. 2 +n and update and save, where n represents the total number of unidirectional communication verification messages sent between the client and the master.

[0008] Preferably, in S2, the client sends the encrypted first communication verification message to the master control end, further comprising the following steps: S21: After the communication authentication between the client and the master is successful, the client sends a first communication verification message to the master. The first communication verification message includes a synchronization signal flag Sync and a heartbeat count Beat_cnt (2) encrypted using the AES symmetric encryption algorithm. 1 , where the heartbeat count in the first communication check message is Beat_cnt(2) 1 The parameter value is the locally preset heartbeat count Beat_cnt(1) 2 +1 for the parameter value.

[0009] Preferably, in S2, the master control end receives and verifies the first communication verification message, and sends an encrypted second communication verification message to the client in reverse based on the first communication verification message, further comprising the following steps: S22: The master control terminal receives the first communication verification message, and first enables the heartbeat count preset locally by the master control terminal to be updated to Beat_cnt(2) 2 ; S23: The master control end uses the AES symmetric encryption algorithm to reversely decrypt and obtain the heartbeat count Beat_cnt (2) 1 , if the received heartbeat count is Beat_cnt(2) 1 The parameter value is the same as the heartbeat count Beat_cnt(2) currently stored locally on the master. 2 If the parameter values ​​of are consistent, the verification is successful, and the master control end sends a second communication verification message to the client. The second communication verification message includes a synchronization signal flag Sync and a heartbeat count Beat_cnt encrypted using the AES symmetric encryption algorithm (3) 1 , where the heartbeat count is Beat_cnt(3) 1 and heartbeat count Beat_cnt(2) 2 +1 has the same parameter value.

[0010] Preferably, in S3, the client receives and verifies the second communication verification message, and sends an encrypted third communication verification message to the main control end based on the second communication verification message, further comprising the following steps: S31: The client receives the second communication verification message and first enables the heartbeat count preset locally on the client to be updated to Beat_cnt (3) 2 ; S32: The client uses the AES symmetric encryption algorithm to reversely decrypt and obtain the heartbeat count Beat_cnt (3) 1 , if the received heartbeat count is Beat_cnt(3) 1 The parameter value is the same as the heartbeat count Beat_cnt(3) currently stored locally on the client. 2 If the parameter values ​​of are consistent, the verification is successful, and the client sends a third communication verification message to the master control end, the third communication verification message includes a synchronization signal flag Sync and a heartbeat count Beat_cnt encrypted using the AES symmetric encryption algorithm (4) 1 , where the heartbeat count is Beat_cnt(4) 1 and heartbeat count Beat_cnt(3) 2 +1 has the same parameter value.

[0011] Preferably, in S4, the main control end sends the encrypted voice data to the client, further comprising the following steps: S41: The main control end calculates and generates a first cyclic redundancy check code CRC according to the data body data, the main control end packages the data body data and the first cyclic redundancy check code CRC, and uses the AES symmetric encryption algorithm to encrypt the voice data, and finally sends it to the client through a single-line channel.

[0012] Preferably, in S4, the client receives and verifies the voice data and executes the corresponding instruction action, further comprising the following steps: S42: The client receives the voice data, uses the AES symmetric encryption algorithm to reversely decrypt to obtain the data body data and the first cyclic redundancy check code CRC, and recalculates and generates a second cyclic redundancy check code CRC based on the received data body data. If the second cyclic redundancy check code CRC is the same as the first cyclic redundancy check code CRC, the client executes the corresponding instruction action recorded in the data body data.

[0013] Based on the same concept, the present invention also provides a single-line voice data communication device for executing a single-line voice data communication method as described in any one of the above, including: a main control device and an execution device, the single-line voice data communication device is configured such that the main control device and the execution device realize the voice data communication function through a single-line channel in an offline state, the main control device is used to output voice data, and the execution device is used to execute corresponding instruction actions according to the voice data.

[0014] Due to the adoption of the above technical solution, the present invention has the following advantages and positive effects compared with the prior art: The present invention provides a single-line communication method and device for voice data. A client and a main control end are provided at the application layer. During the communication process, the main control end first verifies the MAC address of the client through an encryption and decryption algorithm to achieve two-way communication authentication, ensure the legitimacy of the access client, and improve the security of the communication connection. Subsequently, based on the heartbeat mechanism, the client and the main control end successively send and receive verification information of the encrypted heartbeat count Beat_cnt, so as to achieve a safe and effective connection between the client and the main control end in a silent state. Finally, when entering the communication state, the main control end sends the encrypted voice data to the client, and based on the encryption and decryption processing and the cyclic redundancy check code CRC secondary verification, the transmission security and data integrity of the data body are guaranteed.

[0015] In addition, the present invention provides a single-line voice data communication method and device, which enables the main control device and the execution device to achieve two-way data communication function through a single-line channel in an offline state, and cooperates with a number of verification mechanisms to fully ensure the security, reliability and integrity of the data transmission process. At the same time, the single-line communication greatly reduces the requirements for the number of main control chip pins of the main control device and the execution device during hardware layout, making the circuit wiring more streamlined and the hardware usage cost significantly reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 A timing diagram of a voice data single-line communication method provided by the present invention; Figure 2 A schematic flow chart of a voice data single-line communication method provided by the present invention. DETAILED DESCRIPTION

[0017] The following is a further detailed description of a voice data single-line communication method and device proposed by the present invention in conjunction with the accompanying drawings and specific embodiments. The advantages and features of the present invention will become more apparent from the following description and claims.

[0018] First embodiment See also Figure 1-Figure 2 This embodiment provides a single-line voice data communication method, which enables the main control end and the client to realize the voice data communication function in an offline state through a single-line channel, and specifically includes the following steps: S1: The client sends encrypted device information to the master control end, which receives and verifies whether the device information is legal. If the verification is successful, the communication authentication between the client and the master control end is completed, and the data communication connection is realized; if the verification fails, the client needs to resend the device information until the verification is successful. At this time, the master control end and the client cannot realize the data communication connection, preventing illegal clients from accessing the master control end.

[0019] S2: Set the client and the main control end to be in a silent state when the communication authentication has been completed and there is no voice data transmission demand between the two parties. In the silent state, the client sends the encrypted first communication verification message to the main control end, and the main control end receives and verifies the first communication verification message. If the verification is successful, the main control end sends the encrypted second communication verification message to the client based on the first communication verification message.

[0020] S3: The client receives and verifies the second communication verification message. If the verification is successful, the client sends an encrypted third communication verification message to the main control end based on the second communication verification message.

[0021] S4: Repeat steps S2-S3, that is, the client and the main control end continue to send and receive communication verification messages with different contents in sequence until the nth communication verification message, and then verify whether the client and the main control end are always in a normal and secure connection state to prevent the connection between the client and the main control end from being interrupted or the connection object from being tampered with.

[0022] When there is a need for voice data transmission between the client and the main control end, it is in the communication state. In the communication state, the main control end sends encrypted voice data to the client, the client receives and verifies the voice data, and executes corresponding command actions to realize the voice control function of the client based on the main control end.

[0023] The following is a detailed description of the specific implementation steps of a single-line voice data communication method provided by this embodiment: Preferably, in this embodiment, the client sends device information to the master in S1, further comprising the following steps: S11: The client obtains its own MAC address, which is a unique identification number assigned to the client when it is produced. The client then uses the AES symmetric encryption algorithm and its CBC working mode to encrypt the client's MAC address to form encrypted device information. The client then sends the encrypted device information to the main control end through a single-line channel.

[0024] Among them, the AES symmetric encryption algorithm is a group encryption method, which can divide the client's mac address data into data blocks of fixed size and encrypt each data block separately. The CBC working mode is one of the working modes of the AES symmetric encryption algorithm. The security of encryption can be increased by performing an XOR operation on each plaintext data block and the previous ciphertext data block. In this embodiment, the key required for encryption and decryption of the AES symmetric encryption algorithm is preset in the local files of the legitimate client and the main control end. The encryption function of data communication between the client and the main control end is realized through the AES symmetric encryption algorithm.

[0025] Furthermore, in this embodiment, the master terminal receives and verifies the device information in S1, further comprising the following steps: S12: A mac address whitelist is preset in the local file of the master control end, recording the mac address data of all clients that can be legally connected. The master control end receives the encrypted device information, uses the AES symmetric encryption algorithm for reverse decryption processing, extracts the mac address of the client currently expecting a single-line connection, and verifies whether the mac address of the current client is in the mac address whitelist of the master control end. If it exists, the communication authentication between the client and the master control end is successful, and the two are legally connected, and the master control end sends the authentication success result to the client; if it does not exist, the communication authentication between the client and the master control end fails, indicating that the client currently expecting a single-line connection is not a legal client, and the master control end sends the authentication failure result to the client, and then the client needs to resend the device information to the master control end. In one embodiment, the number of times the client sends device information to the master control end can be limited to a maximum of 3 times. If it exceeds three times, the mac address of the client will be locked and an alarm message will be uploaded.

[0026] Preferably, in this embodiment, a heartbeat count Beat_cnt(1) is preset in the local files of the client and the host. 2 The heartbeat count Beat_cnt can be understood as a counter. When the master and the client receive a communication verification message, they enable the locally preset heartbeat count Beat_cnt (1) 2 +n and update and save, where n represents the total number of one-way communication verification messages sent between the client and the host. For example, when the client sends the first communication verification message, the heartbeat count in the client's local file is Beat_cnt(1) 2 When the master receives the first communication verification message, the heartbeat count in the master's local file is updated to Beat_cnt(2) 2 When the client receives the second communication verification message sent by the master, the heartbeat count in the client's local file is updated to Beat_cnt(3) 2 When the master receives the third communication verification message sent by the client, the heartbeat count in the master's local file is updated to Beat_cnt(4) 2 , and so on.

[0027] Furthermore, in S2, the client sends an encrypted first communication verification message to the master, further comprising the following steps: S21: After the client successfully authenticates the master, the client sends the first communication verification message to the master. The first communication verification message includes a synchronization signal flag Sync and a heartbeat count Beat_cnt (2) encrypted using the AES symmetric encryption algorithm. 1 , where the heartbeat count in the first communication check message is Beat_cnt(2)1 The parameter value is equal to the client's local preset heartbeat count Beat_cnt(1) 2 +1 for the parameter value.

[0028] In this embodiment, the synchronization signal flag Sync is used to ensure the synchronization of data transmission between the client and the master. Heartbeat count Beat_cnt(n) 1 Used to verify the security of the connection between the client and the host. For specific verification methods, see the following text.

[0029] It is worth noting that, in this embodiment, for the convenience of distinction, Beat_cnt(n) 1 Used to refer to the heartbeat count in the communication verification message, Beat_cnt(n) 2 Used to refer to the heartbeat count stored in a local file.

[0030] Furthermore, in S2, the master terminal receives and verifies the first communication verification message, and sends an encrypted second communication verification message to the client in reverse based on the first communication verification message, further comprising the following steps: S22: The master receives the first communication verification message and first enables the master's local preset heartbeat count to be updated to Beat_cnt(2) 2 ; S23: The master end uses the AES symmetric encryption algorithm to reversely decrypt and obtain the heartbeat count Beat_cnt(2) recorded in the first communication verification message. 1 , if the received heartbeat count is Beat_cnt(2) 1 The parameter value and the heartbeat count Beat_cnt(2) currently stored locally on the master 2 If the parameter values ​​are consistent, the verification is successful, indicating that the connection between the client and the master is now secure. The master then sends a second communication verification message to the client. The second communication verification message includes a synchronization signal flag Sync and a heartbeat count Beat_cnt (3) encrypted using the AES symmetric encryption algorithm. 1 , where the heartbeat count is Beat_cnt(3) 1 and heartbeat count Beat_cnt(2) 2 +1 has the same parameter value.

[0031] Preferably, in this embodiment, in S3, the client receives and verifies the second communication verification message, and sends an encrypted third communication verification message to the master based on the second communication verification message, further comprising the following steps: S31: The client receives the second communication verification message and first enables the client's local preset heartbeat count to be updated to Beat_cnt(3) 2; S32: The client uses the AES symmetric encryption algorithm to reversely decrypt and obtain the heartbeat count Beat_cnt (3) recorded in the second communication verification message. 1 , if the received heartbeat count is Beat_cnt(3) 1 The parameter value and the heartbeat count Beat_cnt(3) currently stored locally on the client 2 If the parameter values ​​are consistent, the verification is successful, indicating that the client and the host are still securely connected. The client then sends the third communication verification message to the host. The third communication verification message includes the synchronization signal flag Sync and the heartbeat count Beat_cnt (4) encrypted using the AES symmetric encryption algorithm. 1 , where the heartbeat count is Beat_cnt(4) 1 and heartbeat count Beat_cnt(3) 2 +1 has the same parameter value.

[0032] It is worth noting that, in this embodiment, steps S2-S3 will be repeatedly executed, that is, the client and the main control end continue to send and receive communication verification messages in sequence until the nth communication verification message. Each time the client or the main control end receives the communication verification message, the heartbeat count Beat_cnt(n) recorded in the current communication verification message needs to be recorded. 1 The real-time accumulated heartbeat count Beat_cnt(n) stored locally 2 Compare them. If the two are consistent, it proves that the nth communication verification message is valid, that is, the current client and the main control end still maintain a safe and legal connection at this time.

[0033] Preferably, in this embodiment, the master control end sends the encrypted voice data to the client in S4, further comprising the following steps: S41: In the communication state, the main control end first obtains the data body data of the voice data to be transmitted, and calculates and generates the corresponding first cyclic redundancy check code CRC based on the data body data, then packages the data body data and the first cyclic redundancy check code CRC, and uses the AES symmetric encryption algorithm to encrypt the voice data. Finally, the main control end sends the encrypted voice data to the client through a single-line channel.

[0034] Furthermore, in S4, the client receives and verifies the voice data and executes the corresponding command action, further comprising the following steps: S42: The client receives the voice data, first uses the AES symmetric encryption algorithm to reversely decrypt to obtain the data body data and the first cyclic redundancy check code CRC recorded in the voice data, then recalculates and generates the second cyclic redundancy check code CRC based on the received data body data, compares the first cyclic redundancy check code CRC with the second cyclic redundancy check code CRC, if the second cyclic redundancy check code CRC is the same as the first cyclic redundancy check code CRC, it proves that the data body data has been transmitted completely and has not been tampered with, the client sends a verification success result to the main control end, and finally the client executes the corresponding instruction action recorded in the data body data; if the second cyclic redundancy check code CRC is inconsistent with the first cyclic redundancy check code CRC, it is possible that the data body data may have been tampered with, resulting in incomplete data transmission, the client sends a verification failure result to the main control end, and the main control end needs to resend the voice data to the client.

[0035] In summary, this embodiment provides a single-line voice data communication method. First, the client and the main control end verify the MAC address to achieve communication authentication between the client and the main control end. Then, in a silent state, the client and the main control end continue to send communication verification messages in sequence. After receiving the communication verification message, the client and the main control end obtain the heartbeat count Beat_cnt(n) recorded in the communication verification message. 1 And the heartbeat count Beat_cnt(n) 1 The heartbeat count Beat_cnt(n) stored locally and accumulated in real time 2 Comparison is carried out to determine the connection security between the client and the main control end in real time. Finally, in the communication state, the main control end sends encrypted voice data to the client. After receiving the voice data, the client decrypts the voice data and verifies the integrity of the data body, fully realizing the function of efficient and secure transmission of voice data between the client and the main control end through a single-line channel in an offline state.

[0036] Second embodiment Based on the same concept, the present invention further provides a single-line communication device for voice and data, which is used to execute the single-line communication method for voice and data as described in the first embodiment. The single-line communication device for voice and data includes a main control device and an execution device.

[0037] A main control chip is provided in the main control device. In this embodiment, the main control device and the execution device realize data connection interaction through a single-line channel, which effectively reduces the hardware usage cost and is suitable for offline state. It does not rely on network security protocols, and can realize efficient and secure transmission of voice data between the main control device and the execution device. By outputting voice data based on the main control device, the execution device receives and executes corresponding command actions based on the voice data, thereby finally realizing the voice control function of the execution device.

[0038] The embodiments of the present invention are described in detail above in conjunction with the accompanying drawings, but the present invention is not limited to the above embodiments. Even if various changes are made to the present invention, if these changes fall within the scope of the claims of the present invention and their equivalents, they still fall within the protection scope of the present invention.

Claims

1. A single-line voice data communication method, characterized in that: The steps include: S1: The client sends device information to the master control end, and the master control end receives and verifies the device information. If the verification is successful, the communication authentication between the client and the master control end is realized; S2: In a silent state, the client sends an encrypted first communication verification message to the master control end, the master control end receives and verifies the first communication verification message, and sends an encrypted second communication verification message back to the client based on the first communication verification message; S3: the client receives and verifies the second communication verification message, and sends an encrypted third communication verification message to the main control end based on the second communication verification message; S4: Repeat steps S2-S3 until the master control end enters a communication state. In the communication state, the master control end sends encrypted voice data to the client, and the client receives and verifies the voice data and executes corresponding instruction actions.

2. The voice data single-line communication method according to claim 1, characterized in that: In S1, the client sends device information to the master, further comprising the following steps: S11: The client obtains its own MAC address, uses the AES symmetric encryption algorithm and adopts its CBC working mode to encrypt the MAC address of the client, and sends the encrypted device information to the main control end through a single-line channel.

3. The voice data single-line communication method according to claim 2, characterized in that: In S1, the master control end receives and verifies the device information, further comprising the following steps: S12: A mac address whitelist is preset in the main control end. The main control end receives the encrypted device information, uses the AES symmetric encryption algorithm to perform reverse decryption processing, extracts the mac address of the current client, and verifies whether the mac address of the current client is in the mac address whitelist. If so, the communication authentication between the client and the main control end is successful, and the main control end sends an authentication success result to the client. If not, the communication authentication between the client and the main control end fails, and the main control end sends an authentication failure result to the client.

4. The voice data single-line communication method according to claim 1, characterized in that: The heartbeat count Beat_cnt(1) is preset locally on the master terminal and the client terminal respectively. 2 When the master and the client receive a communication verification message, the locally preset heartbeat count Beat_cnt(1) is enabled. 2 +n and update and save, where n represents the total number of unidirectional communication verification messages sent between the client and the master.

5. The voice data single-line communication method according to claim 4, characterized in that: In S2, the client sends an encrypted first communication verification message to the master control end, further comprising the following steps: S21: After the communication authentication between the client and the master is successful, the client sends a first communication verification message to the master. The first communication verification message includes a synchronization signal flag Sync and a heartbeat count Beat_cnt (2) encrypted using the AES symmetric encryption algorithm. 1 , where the heartbeat count in the first communication check message is Beat_cnt(2) 1 The parameter value is the locally preset heartbeat count Beat_cnt(1) 2 +1 for the parameter value.

6. The voice data single-line communication method according to claim 5, characterized in that: In S2, the master control end receives and verifies the first communication verification message, and sends an encrypted second communication verification message to the client in reverse based on the first communication verification message, further comprising the following steps: S22: The master control terminal receives the first communication verification message, and first enables the heartbeat count preset locally by the master control terminal to be updated to Beat_cnt(2) 2 ; S23: The master control end uses the AES symmetric encryption algorithm to reversely decrypt and obtain the heartbeat count Beat_cnt (2) 1 , if the received heartbeat count is Beat_cnt(2) 1 The parameter value is the same as the heartbeat count Beat_cnt(2) currently stored locally on the master. 2 If the parameter values ​​of are consistent, the verification is successful, and the master control end sends a second communication verification message to the client. The second communication verification message includes a synchronization signal flag Sync and a heartbeat count Beat_cnt encrypted using the AES symmetric encryption algorithm (3) 1 , where the heartbeat count is Beat_cnt(3) 1 and heartbeat count Beat_cnt(2) 2 +1 has the same parameter value.

7. The single-line voice data communication method according to claim 6, characterized in that: In S3, the client receives and verifies the second communication verification message, and sends an encrypted third communication verification message to the main control end based on the second communication verification message, further comprising the following steps: S31: The client receives the second communication verification message and first enables the heartbeat count preset locally on the client to be updated to Beat_cnt (3) 2 ; S32: The client uses the AES symmetric encryption algorithm to reversely decrypt and obtain the heartbeat count Beat_cnt (3) 1 , if the received heartbeat count is Beat_cnt(3) 1 The parameter value is the same as the heartbeat count Beat_cnt(3) currently stored locally on the client. 2 If the parameter values ​​of are consistent, the verification is successful, and the client sends a third communication verification message to the master control end, the third communication verification message includes a synchronization signal flag Sync and a heartbeat count Beat_cnt encrypted using the AES symmetric encryption algorithm (4) 1 , where the heartbeat count is Beat_cnt(4) 1 and heartbeat count Beat_cnt(3) 2 +1 has the same parameter value.

8. The voice data single-line communication method according to claim 1, characterized in that: In S4, the main control end sends the encrypted voice data to the client, further comprising the following steps: S41: The main control end calculates and generates a first cyclic redundancy check code CRC according to the data body data, the main control end packages the data body data and the first cyclic redundancy check code CRC, and uses the AES symmetric encryption algorithm to encrypt the voice data, and finally sends it to the client through a single-line channel.

9. The voice data single-line communication method according to claim 8, characterized in that: In S4, the client receives and verifies the voice data and executes the corresponding instruction action, which further includes the following steps: S42: The client receives the voice data, uses the AES symmetric encryption algorithm to reversely decrypt to obtain the data body data and the first cyclic redundancy check code CRC, and recalculates and generates a second cyclic redundancy check code CRC based on the received data body data. If the second cyclic redundancy check code CRC is the same as the first cyclic redundancy check code CRC, the client executes the corresponding instruction action recorded in the data body data.

10. A single-line voice and data communication device, characterized in that: The method for executing a single-line voice data communication method as described in any one of claims 1 to 9 above comprises: a main control device and an execution device, wherein the single-line voice data communication device is configured such that the main control device and the execution device realize a voice data communication function through a single-line channel in an offline state, the main control device is used to output voice data, and the execution device is used to execute corresponding instruction actions according to the voice data.

Images