Transition to the Internet of things · basic Chapter 11 – essential differences and key overview of the Internet of things architecture, Internet and general hardware projects

Time:2020-1-6

Essential differences and key points of Internet of things architecture, Internet and general hardware projects

In terms of the overall architecture of the Internet of things, it includes two parts: the Internet and the hardware. The hardware is divided into two parts: single machine direct access to the cloud and hardware networking first and then access to the cloud. In practical application, most of the hardware is the structure of networking first and then accessing the cloud. The common understanding of the Internet of things can be regarded as the connection of related hardware devices and Internet applications, forming a new application project. Take a look at the following diagram:
Transition to the Internet of things · basic Chapter 11 - essential differences and key overview of the Internet of things architecture, Internet and general hardware projects

From the above figure, we can see that the cloud part has added the “cloud access” part to the original Internet application, which is dedicated to processing the hardware device access to the cloud server. After the device has established a normal connection with the cloud service, it needs to identify various protocols and data processing and saving, which are completed by the cloud access. But after processing and saving, the rest of the data provides API and statistical analysis, business logic, mobile interaction and so on, which are basically the same as the Internet, except for some differences in the data content. It can give full play to the ability of cloud computing and improve the later function discovery.

On the hardware side, most of the time, you need to add a device (for those directly entering the cloud, you need to add a networking module to the original device), that is, the gateway controller.

First of all, the gateway should connect all terminal devices to form a local interactive network of hardware devices. Therefore, one of the main function blocks of the gateway controller is “physical connection”. It interacts with the terminal equipment (i.e. its own sub equipment) for data instruction (signaling), processes and distributes the signaling from the “access cloud” function block, collects and processes the signaling from the sub equipment and sends it to the “access cloud” function block.

Secondly, all terminal devices that need to participate in networking need to be embedded with a functional block “physical connection” to be responsible for signaling interaction with the gateway compared with ordinary hardware devices. There are two ways of communication: wireless and wired. The protocols used are also different. We should carefully analyze and select them according to our own applicable scenarios.

Then, all the data of the sub devices are gathered in the gateway controller. The gateway controller should selectively report to the cloud according to the needs of the project and the definition of configuration data. Then the gateway controller should have a “access to the cloud” function plate, which is responsible for reporting data to the cloud. And is responsible for receiving the signaling from the cloud. “Access cloud” is a functional module to establish network connection with “cloud access” in the cloud for remote communication, and it is a key access for signaling interaction between hardware equipment and the cloud.

The intermediate transmission is the infrastructure of telecom operators, which we usually can’t get involved in. Later, we will focus on analyte connection, cloud access and cloud access.

At the end of this section, to be continued