CN111866165B - A communication system for cross-platform IoT embedded devices - Google Patents

Abstract

The invention discloses a communication method of a cross-platform Internet of things embedded system, which designs a communication method and a communication system framework capable of meeting compatibility, improving reusability and ensuring safety and reliability aiming at communication between complex cross-platform Internet of things embedded systems, wherein the method comprises the following steps: configuring a communication protocol, formulating an automatic hierarchical encryption strategy, formulating a hierarchical networking strategy in the system, and designing a communication line of the cross-platform Internet of things embedded system. The invention has the advantages that: the problem that the communication modes of the internet of things embedded system of the multiprocessor are incompatible is solved by formulating the networking strategy of the hierarchy in the system and different communication lines, and the reliability and the safety of the cross-platform internet of things embedded system are improved by formulating the encryption strategy of the hierarchy.

Description

A communication system for cross-platform IoT embedded devices

technical field

The invention relates to the technical field of Internet of Things communication, in particular to a communication method and a communication system of a cross-platform Internet of Things embedded device.

Background technique

The Internet of Things is in the infancy of the industry, and the application fields are diversified and scattered, which makes it difficult for the industry to reach a consensus on relevant communication standards and protocols. For example, the current semiconductor IC intellectual property licensing companies, IC design companies, terminal equipment brand companies, and operating system and network service companies, etc., are trying to use vertical integration strategies, coupled with active research and development and mergers and acquisitions. Based on the advantages of scale, seize the business opportunities of the Internet of Things services that are starting. Some industry players have further launched IoT operating systems that can integrate or widely support communication standards and protocols, thereby creating a complete application service ecosystem. From this point of view, with the maturity of technology, the functional differences provided by various brands in terminals or sensing devices will be narrowed in the future, and the mutual substitutability will be greatly improved. One of the core of competition.

In the Internet of Things, especially in the perception layer, due to the existence of different sensor devices, the Internet of Things is cross-domain and cross-platform, and the operating environment used will also vary according to different industries or fields. Therefore, cross-platform IoT communication usually suffers from the following problems:

Reusability: With the increasing complexity of cross-platform systems, IoT embedded systems with multiple processors abound. There are various communication methods between processors. At present, most system designs are implemented separately for their respective applications and hardware configurations. communication, resulting in incompatible communication methods and poor reusability.

Reliability: The communication between components, processors, and devices requires high communication reliability. However, within the same Device, the communication between components between different processors is not reliable, and is vulnerable to harsh environments such as electromagnetic interference, radiation, Influence of high and low temperature, etc. In addition, the communication between different devices will also have communication errors.

Security: Communication between Component under the same Processor generally can be without security measures. However, if this Processor is connected to the Internet of Things, even the internal communication has security implications. In addition, there are also communication security issues between different devices.

SUMMARY OF THE INVENTION

The purpose of the present invention is to aim at the deficiencies in the prior art, to provide a cross-platform IoT embedded system that can not only satisfy the reusability of complex cross-platform IoT systems, but also ensure the reliability of system communication and improve communication security. System communication method and communication system.

In order to achieve the above purpose, the technical solution adopted by the present invention is: a communication method for a cross-platform IoT embedded system, comprising the following steps:

S01. Configure the MCI communication protocol for data transmission between components in the cross-platform embedded system;

S02. Formulate an automatic hierarchical encryption strategy for data transmission between components in a cross-platform embedded system;

S03. Develop hierarchical networking strategies within the system;

S04. Design communication lines for cross-platform IoT embedded systems.

Further, the components described in step S01 include software programs and hardware devices for Internet of Things control, perception, detection, power supply, transmission, storage, power supply, security, and the like.

Further, the data transmission method described in step S01 includes wired data transmission and/or wireless data transmission.

Further, the automatic hierarchical encryption strategy described in step S02 includes: the communication between the components in the same processor adopts an unencrypted or weakly encrypted data transmission mode; in the same system, each component in different processors The communication between components adopts the data transmission mode of no encryption/weak encryption or weak encryption/strong encryption; the communication between the components in different systems can be the data transmission mode of weak encryption or strong encryption.

Further, the hierarchical networking strategy described in step S03 includes: networking between components in the same processor, networking and ad hoc networking between different processors in the same system, and networking between different systems. network and ad hoc networks.

Further, the design of the communication line described in S04 includes: the MCI communication protocol between the components within the same processor realizes communication through IPC, and the MCI communication protocol between the components of different systems and different processors is implemented through cross-platform. The transmission channel enables communication.

Based on the above method, the technical solution adopted by the present invention corresponding to designing an operating system is: a communication system of a cross-platform IoT embedded system, comprising at least one processor, a component management module, a communication protocol management module, and a system security management module , communication networking module, cross-platform transmission channel,

The component management module is used to monitor and manage each component in the system and the data transmission between the components,

The communication protocol management module is used to realize communication transmission, distribution and routing between embedded systems, between processors and between components,

The system security management module is used to realize the communication security between embedded systems, between processors and between components,

The described communication networking module is used to formulate hierarchical networking strategies in the system,

The cross-platform transmission channel is a transmission abstraction layer of the MCI communication protocol, which is used to realize the effective transmission of MCI packets through wired and/or wireless transmission channels.

Further, the cross-platform transmission channel is established on a standard communication protocol or a non-standard communication protocol.

The advantages of the present invention are:

1. The present invention solves the problem of incompatibility of communication modes of multi-processor IoT embedded systems by formulating hierarchical networking strategies in the system and different communication lines.

2. The present invention improves the reliability and security of the cross-platform IoT embedded system by formulating a hierarchical encryption strategy.

Description of drawings

In order to more clearly understand the objects, features and advantages of the present invention, the preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings, wherein:

Fig. 1 is the flow chart of the method of the present invention;

FIG. 2 is a communication frame diagram of the present invention applied to a cross-platform IoT embedded system.

Detailed ways

Referring to FIG. 1 and FIG. 2 , the communication system of the cross-platform IoT embedded device of the present invention is composed of a cross-platform part, a non-cross-platform part and an application program management part.

The application program management part includes access to third-party application systems in the system, such as user applications and third-party application software.

The non-cross-platform part consists of abstraction layers, including:

A cross-platform operating system abstraction layer independent of the actual operating system, used to provide simple functions such as Task, Message Queue, Semaphore, etc. required by embedded systems, and can be used in all embedded real-time operating systems (RTOS), Linux , WinCE, etc.;

A cross-platform hardware abstraction layer independent of actual hardware (Hardware), used to provide operations on actual hardware interfaces, such as UART, I2C, SPI, I/O, PWM, Hardware Timer, etc.

The cross-platform part includes:

The component management module is used to monitor and manage the components in the system and the data transmission between the components. The components include the software and hardware of the Internet of Things control, perception, detection, power supply, transmission, storage, power supply, security and other component units. . This module is the basic application module in this system. Through the cross-platform communication environment, this module can monitor and manage the software or hardware of each component in the system, as well as manage the communication with other components. For example, through the communication protocol channel configured by the system (including IPC and cross-platform transmission channel, etc.), the communication of the components between different processors in the system and the communication between the components in the same processor are realized.

The communication protocol management module is used to realize the communication transmission, distribution and routing between embedded systems, processors and components. This module designs MCI communication protocol for wired data transmission (such as UART, SPI, Ethernet, etc.) and wireless data transmission (such as WiFi, Bluetooth, 2G/3G/4G, etc.) between embedded systems and processors, and its communication channel. The cross-platform transport channel is a transport abstraction layer of the MCI communication protocol for efficient transport of MCI packets through wired and/or wireless transport channels. The basic definition of the cross-platform transmission channel is included in the basic definition of the MCI protocol, as follows:

Transport Header:

Identifier: MCI packet flag, determined according to different transmission forms.

Length: MCI packet length.

Sequence: MCI packet sequence number.

Control: MCI packet ACK/NACK mark, retransmission mechanism, etc.

Error Code: Transport returns a packet error code.

Transport Tail:

CRC: (set check code)

Protocol Header:

Encryption Type: Encryption method.

Error Code: Protocol returns the package error code.

Component IDs:

Component ID definition:

DID – Device ID,

PID – Processor ID,

CID – Component ID,

TID: Target ID – contains the full DID/PID/CID.

SID: Source ID – contains the complete DID/PID/CID.

Command:

Command With Ack: Improves reliability of transmitted commands.

Command Without Ack:

Data: Actual data.

The communication encryption module defines a custom encryption method according to the Component ID, generates transmission security instructions, and realizes the communication security between embedded systems, between processors, and between components. The communication between the components in the same processor is relatively reliable, and there is no external interference. Therefore, an unencrypted data transmission method is usually used, and a weakly encrypted data transmission method is used for high security requirements. In the same system containing multiple processors, the reliability of communication between components in different processors is weak. In harsh environments, such as electromagnetic interference, radiation, high and low temperature, etc., communication between processors in the system may be affected. make an impact. While most problems can be solved using hardware design, physical form (such as a shield), etc., there is still a chance of communication errors. Therefore, an unencrypted/weakly encrypted data transmission method is adopted for the communication between the components between the processors not connected to the external network, and for the communication between the components between the processors connected to the external network, in order to reduce the External interference adopts weak encryption/strong encryption data transmission method. For communication between components between different systems, weakly encrypted data transmission can be used for wired data transmission (strongly encrypted data transmission can also be used when information security requirements are very high). For wireless data transmission In the case of data transmission, strong encryption is used.

The communication networking module is used to formulate hierarchical networking strategies between systems, processors, and components, and realize between systems, processors, and components according to the definition of Component ID in the MCI protocol. Between the networking and the self-organizing network framework, the definition of Component ID: DID-Device ID, PID-Processor ID, CID-Component ID, TID: Target ID-includes complete DID/PID/CID, SID: Source ID- Contains the complete DID/PID/CID.

The above are only the preferred embodiments of the present invention. It should be pointed out that for those skilled in the art, without departing from the method of the present invention, several improvements and supplements can be made, and these improvements and supplements should also be regarded as It is the protection scope of the present invention.

Claims (8)

1. a communication system of a cross-platform Internet of Things embedded device, is characterized in that, comprises the following modules: The component management module is used to monitor and manage the components in the cross-platform IoT embedded system and the data transmission between the components. The components include IoT control, perception, detection, power supply, transmission, storage, power supply , the software and hardware of the security component unit; The communication protocol management module is used to realize the communication transmission, distribution and routing between IoT embedded systems, between processors and between components; The cross-platform transmission channel is the transmission abstraction layer of the MCI communication protocol, which is used to realize the effective transmission of MCI packets through wired or wireless transmission channels; The communication encryption module defines a custom encryption method according to the Component ID, generates transmission security instructions, and realizes the communication security between embedded systems, processors and components; The communication networking module is used to formulate hierarchical networking strategies between systems, processors, and components, and realize between systems, processors, and components according to the definition of Component ID in the MCI protocol. The framework between networking and ad hoc networking. 2. The communication system of a cross-platform Internet of Things embedded device according to claim 1, wherein the component management module is a basic application module in the cross-platform Internet of Things embedded system, and through the cross-platform communication environment, The component management module realizes monitoring and management of the software or hardware of each component in the cross-platform IoT embedded system. 3. The communication system for cross-platform Internet of Things embedded devices according to claim 1, wherein the communication protocol management module is directed to wired data transmission and communication between the cross-platform Internet of Things embedded systems and between processors. For wireless data transmission, the MCI communication protocol and its communication transmission channel are designed. 4 . The communication system for cross-platform IoT embedded devices according to claim 3 , wherein the wired data transmission comprises UART, SPI, and Ethernet. 5 . 5 . The communication system for cross-platform IoT embedded devices according to claim 3 , wherein the wireless data transmission includes WiFi, Bluetooth, and 2G/3G/4G. 6 . 6. The communication system for cross-platform IoT embedded devices according to claim 1, wherein the cross-platform transmission channel is an effective transmission channel for realizing MCI packets through a wired transmission channel or a wireless transmission channel. Platform transmission channels include the following: Transport Header; Identifier: MCI packet flag; Length: MCI packet length; Sequence: MCI packet sequence number; Control: MCI packet ACK/NACK flag; Error Code: Transport returns a packet error code; Transport Tail: CRC: set check code; Protocol Header; Encryption Type: encryption method; Error Code: Protocol returns the package error code; Component IDs; Component ID definition; DID-Device ID; PID – Processor ID; CID – Component ID; TID: Target ID – contains the complete DID/PID/CID; SID: Source ID – contains the complete DID/PID/CID; Command; Command With Ack: Improve the reliability of transmission commands; Command Without Ack; Data: Actual data. 7. The communication system of a cross-platform Internet of Things embedded device according to claim 1, wherein the communication encryption module formulates an automatic hierarchical encryption strategy; the automatic hierarchical encryption strategy comprises, the same processor The communication between the components in the system adopts the data transmission method of unencrypted or weak encryption; the communication between the components in different processors in the same system adopts the data transmission method of unencrypted/weak encryption; Communication between components is a data transmission method with weak encryption or strong encryption. 8. The communication system for cross-platform IoT embedded devices according to claim 1, wherein the Component ID comprises DID-Device ID, PID-Processor ID, and CID-Component ID; TID: Target ID contains the complete DID/PID/CID; SID: The Source ID contains the complete DID/PID/CID.

Images