GB/T 38624.1-2020Internet of things—Gateway—Part 1: Gateway technology requirements for access of sensing device (English PDF)

3.1 IoT gateway

With data storage capabilities, computing capabilities, and protocol conversion capabilities, it can establish communication connections and pass through the northbound interface with the application platform

An entity that communicates with the perception control device on the southbound interface.

Note. The entity can be an independent device or software.

3.2 Northbound interface

The interface between the IoT gateway and the public telecommunication network.

Note. Rewrite GB/T 30269.901-2016, definition 3.2.

3.3 Southbound interface

The interface between the IoT gateway and the perception control device.

Note. Rewrite GB/T 30269.901-2016, definition 3.3.

3.4 Edge processing

Perform local operations such as control, early warning or alarm based on local strategies and data processing results.

5.1 Overview

The IoT gateway is an entity that supports the interconnection of the perception control system with other systems and realizes the local management of the perception control domain.

Management, protocol conversion, data processing, gateway equipment management, identification management, security management and other functions.

5.2 Access Management

The access management requirements are as follows.

a) The southbound interface for sensory control equipment should be provided, including (but not limited to) GB/T 6107-2000, TIA/EIA485-A

Wired interfaces or wireless interfaces such as low-power wide area network, Zigbee, and cellular communication;

b) It should support the management of connected perception control devices, including the query of device software and firmware version, and the query of device operating status.

Inquiries, etc., and supports remote upgrades of equipment software and firmware;

c) It should support the network management of the connected sensing and control equipment, especially the automatic recognition of the dynamic changes of the equipment network topology.

5.3 Protocol conversion

The protocol conversion requirements are as follows.

a) It should have the function of converting different access protocols from different sensing and control devices to the same agreed protocol,

Complete the data report;

b) It should have the function of converting the protocol from the northbound interface into different types of protocols, and connect to the corresponding sensor through the southbound interface.

The control device completes the control of the device.

5.4 Data processing

The IoT gateway should provide preprocessing, edge processing and storage of the data accessed by the sensing and control device.

5.5 Gateway Device Management

5.5.1 Local Management

The local management requirements of the IoT gateway are as follows.

a) Should support its own local management functions, including but not limited to maintaining the gateway device's own login records, operation records, and external

Attack records, power management and software upgrades, etc.;

b) It should have a positioning function, such as Beidou or GPS to complete positioning, and provide location information sharing function.

5.5.2 Remote management

The remote management requirements of the IoT gateway are as follows.

a) The IoT gateway should support remote management to realize the registration and access management functions of the gateway.

1) The registration information should be permanently stored, and the registration information stored locally in the gateway can be managed and maintained;

2) It should support the reading, modification and deletion of gateway access configuration through remote management. When a configuration error occurs, you should

Automatically restore the last successfully connected configuration.

b) The IoT gateway should support remote firmware upgrades, remote power management strategy configuration and management.

5.6 Logo management

The identification management requirements of the IoT gateway are as follows.

a) It should be able to identify the physical identification, network address identification and application attribute identification from the northbound interface, and the identification coding rules should comply with

GB/T 37032-2018 relevant regulations;

b) It shall have the function of identification mapping and conversion, which can realize the mutual mapping and conversion of various types of identifications passed by the southbound interface and the northbound interface.

5.7 Security Management

The IoT gateway should implement basic security management functions, including user authentication, encrypted transmission mechanism, attack protection, etc..

a) User authentication should support at least a simple password authentication mechanism, and other authentication mechanisms, such as digital certificates, smart cards or

Identify through the biological characteristics of the human body, etc.;

b) The IoT gateway should support encryption of the data it transmits to ensure data security;

c) When the IoT gateway is attacked (at least it supports vulnerability scanning or denial of service attacks), it should be able to automatically record the origin of the attack

Key information such as address, attack time and attack type, generates real-time alarm information, and has certain blocking capabilities.

6.1 Overview

The general configuration data of the IoT gateway includes basic gateway information, physical port parameters, data analysis protocol parameters, protocol parser parameters,

Equipment parameters, etc. Configuration can be achieved through local or remote gateway configuration tools. IoT gateway configuration, observation from different perspectives, may produce

For different configurations, this chapter only gives general requirements on data configuration from the aspect of data composition.

6.2 General data configuration

General data configuration requirements for IoT gateways are shown in Table 1.

Table 1 General data configuration requirements for IoT gateways

Refer to Appendix A for the general data configuration example of IoT gateway described in JSON.

Appendix A (Informative appendix)

General data configuration example of IoT gateway

A.1 Overview

This appendix uses JSON to give examples of the five configuration data described in 6.2, and gives an IoT gateway communication in a hypothetical scenario.

Describe examples with data configuration.

The meaning of each field in the example is given in the list behind each example; the Chinese field name is given in the "Description" column.

A.2 Basic information of the gateway

The basic information of the gateway is shown in the serial number 1 in Table 1.The JSON format is as follows, and the field description is shown in Table A.1.

"modelVersion"."1.0.0",//The version number of the configuration data, this version is fixed as "1.0.0"

"changeSerial".1,//The maintenance serial number of the gateway configuration change, when the gateway configuration changes the sequence number is increased by 1

"changeTime"."2017-04-10t12.24.04.220z",//The time of the last configuration update, gateway maintenance

"gatewayid"."",//Gateway ID "description"."",//Gateway description

"vendor"."",//Gateway manufacturer

"model"."",//Gateway model

"hardwareVersion"."",//hardware version number

"softwareVersion"."",//software version number

"physicalPortList".[],//The physical port list of the gateway

"driverList".[],//Device driver list

"protocolList".[],//Data analysis protocol list

"driverInstanceList".[],//Protocol parser list

"deviceList".[]//Device list

Table A.1 Description of the fields in the gateway basic information example […]