GB/T 38637.1-2020 English PDFUS$339.00 · In stock
Delivery: <= 4 days. True-PDF full-copy in English will be manually translated and delivered via email. GB/T 38637.1-2020: Internet of things - Access of sensing and controlling device - Part 1: General requirements Status: Valid
Basic dataStandard ID: GB/T 38637.1-2020 (GB/T38637.1-2020)Description (Translated English): Internet of things - Access of sensing and controlling device - Part 1: General requirements Sector / Industry: National Standard (Recommended) Classification of Chinese Standard: L79 Classification of International Standard: 35.110 Word Count Estimation: 18,173 Date of Issue: 2020-04-28 Date of Implementation: 2020-11-01 Quoted Standard: GB/T 33474-2016 Issuing agency(ies): State Administration for Market Regulation, China National Standardization Administration Summary: This standard specifies the access requirements, application layer access protocol and protocol adaptation for the access of sensing and control devices in the IoT system. This standard applies to the planning and research and development of IoT sensing and control equipment. GB/T 38637.1-2020: Internet of things - Access of sensing and controlling device - Part 1: General requirements---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order. Internet of things - Access of sensing and controlling device - Part 1.General requirements ICS 35.110 L79 National Standards of People's Republic of China IoT perception control device access Part 1.General requirements 2020-04-28 released 2020-11-01 implementation State Administration for Market Regulation Issued by the National Standardization Management Committee Table of contentsPreface Ⅲ 1 Scope 1 2 Normative references 1 3 Terms and definitions 1 4 Abbreviations 1 5 General requirements 2 6 General requirements for indirect access 3 6.1 Access equipment 3 6.2 IoT Gateway 3 6.3 Access and communication mode of perception control equipment and IoT gateway 3 6.4 Access communication method between IoT gateway and application platform 3 7 General requirements for direct access 4 7.1 Access equipment 4 7.2 Access communication method between perception control equipment and application platform 4 8 Application Layer Access Protocol (AAP) 4 8.1 Overview 4 8.2 Message format and message type 4 8.3 Message Interaction Model 5 8.4 Agreement process 7 8.5 Negotiation requirements for protocol functions 7 8.6 Safety requirements 7 9 Protocol adaptation 7 9.1 Message subject 7 9.2 Low-level protocol service interface 7 9.3 Low-level protocol adaptation 8 Appendix A (informative appendix) AAP message example 9 IoT perception control device access Part 1.General requirements1 ScopeThis part of GB/T 38637 specifies the access requirements, application layer access protocols and protocol adaptations for the access of perception control devices in the Internet of Things system. This part is applicable to the planning and research and development of IoT perception control equipment.2 Normative referencesThe following documents are indispensable for the application of this document. For dated reference documents, only the dated version applies to this document. For undated references, the latest version (including all amendments) applies to this document. GB/T 33474-2016 Internet of Things Reference Architecture3 Terms and definitionsThe following terms and definitions apply to this document. 3.1 Perception control equipment In the perception and control domain of the Internet of Things, it has the ability to communicate with external systems, used to collect information in the physical world and can send or receive A device that receives and processes external commands. 3.2 Intelligent perception control equipment Perceptual control equipment (3.1) with information processing components. 3.3 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 The entity that the southbound interface communicates with the perception control device can be an independent device or software.4 AbbreviationsThe following abbreviations apply to this document.5 General requirementsAccording to the reference architecture of the Internet of Things given in GB/T 33474-2016, the perception control device is connected to the resource exchange domain and service provision The domain and operation management domain mainly achieve the following three purposes. a) Access to the software and hardware systems of the resource exchange domain to realize information interaction and sharing; b) Access the basic service system of the service provider domain to realize the interaction of perception and control information; c) Access to the software and hardware systems of the operation and maintenance control domain to realize information exchange and sharing. The association relationship involved in the access of the perception control device is shown in FIG. 1 as an association relationship 7, an association relationship 8, and an association relationship 9. In the actual Internet of Things system, the software and hardware devices of the resource exchange domain, service provision domain, and operation and maintenance control domain are usually deployed in the cloud or central service. The server constitutes an application platform. The ways of sensing control equipment to access the application platform can be divided into indirect access via IoT gateway and non-IoT The direct access of the network gateway is shown in Figure 2, where the sensing control device or the IoT gateway can use the application layer access protocol to access the application platform. The access method is as follows. a) Indirect access. When the communication capability or data processing capability of the sensory control device is limited, multiple sensory The gateway converges and transfers and connects to the application platform. The perception control device is connected to the IoT gateway through the local local area network. The network gateway is connected to the application platform through the wide area network. The IoT gateway provides functions such as protocol conversion, address mapping, and data processing. b) Direct access. Perceptual control equipment can directly interconnect with equipment or systems in other domains.6 General requirements for indirect access6.1 Access equipment Should support the access of two types of non-intelligent sensing control equipment and intelligent sensing control equipment. 6.2 IoT Gateway The IoT gateway should meet the following requirements in the indirect access method. a) Non-intelligent sensing control equipment should use analog signals to connect to the IoT gateway; b) Intelligent sensing control equipment should use digital signals to connect to the IoT gateway; c) The IoT gateway should use digital signals to access the application platform. 6.3 The access communication method between the perception control device and the IoT gateway The communication method requirements for the perception control device to access the IoT gateway are as follows. a) Wired or short-distance wireless transmission network should be adopted; b) It should support the corresponding wired or wireless transmission protocol. 6.4 Access and communication method between IoT gateway and application platform The communication requirements for the IoT gateway to access the application platform are as follows. a) Private or public data communication networks should be used, such as dedicated optical fiber transmission or mobile communication networks provided by operators; b) It should support the coexistence of main and standby communication modes and automatic switching of main and standby communication modes; c) Effective network communication safety protection measures should be taken to ensure communication safety.7 General requirements for direct access7.1 Access equipment Should support intelligent perception control equipment access. 7.2 Access and communication mode of perception control equipment and application platform The communication method requirements for the perception control device to access the application platform are as follows. a) It is generally appropriate to use wide-area wireless communication methods, such as cellular networks, non-cellular networks, etc.; b) When there are special needs, wired communication can be used; c) Effective network communication safety protection measures should be taken to ensure communication safety. 8 Application Layer Access Protocol (AAP) 8.1 Overview AAP is an application layer message protocol, and its operating carriers are intelligent sensing control equipment, IoT gateway (when indirectly connected) and application platform. AAP adapts to the following three types of underlying protocols. a) Message protocols for publishing and subscribing based on message brokers, such as MQTT, etc.; b) Point-to-point application layer protocol based on request/response, such as HTTP; c) Point-to-point message packet transfer protocol, such as Websocket, etc. 8.2 Message format and message type The AAP message consists of three parts. protocol line, message header and message body. a) The agreement line should at least include the format mark and agreement version number. The first byte of the protocol line is the message format flag, indicating the message The encoding format of the header and message body. For example, the beginning of "J" represents the JSON format, and the beginning of "B" represents the binary format. b) The message header should include at least the message type, and can also include timestamps, coding instructions for the message body, compression related information, authentication and encryption information, etc. c) The message receiving end should identify, decode, authenticate and decrypt the message body according to the message header. The messages and message types of AAP are shown in Table 1.Except for the logout message, each message includes two types. request message and response message. (The name is given in primitives), the message description is the description of this kind of message. Table 1 AAP messages and message types 8.4 Agreement process The agreement process is divided into the following four stages. a) Connection establishment stage. the IoT gateway or intelligent sensing control device establishes a connection with the application platform; b) Device registration stage. The IoT gateway or intelligent sensing control device initiates a registration request to the application platform and gets a reply. The platform shows that the IoT gateway or intelligent sensing control device is online; c) Message interaction stage. Information interaction between IoT gateway or intelligent perception control device and application platform, such as application platform Issue commands, IoT gateways or intelligent sensing control devices report data, and send connection keeping messages between the two; d) Connection disconnection stage. The IoT gateway or intelligent sensing control device sends a logout request to the application platform, and the application platform no longer maintains the status of the related equipment. 8.5 Negotiation requirements for protocol functions Both parties to the agreement can negotiate specific agreements to achieve functions, mainly including the following three negotiation modes. a) Actively verify the functions of both parties. After the IoT gateway or intelligent sensing control device establishes a connection with the application platform, actively query the functions supported by the other party; b) Active report support function. After the IoT gateway or intelligent sensing control device establishes a connection with the application platform, it actively reports the functions supported by the other party; c) Actively report support function when receiving unknown request message. When receiving unknown request message, actively report the request message supported by the other party. 8.6 Safety requirements AAP uses at least the following security mechanisms. a) The account and password should be used for authentication between the application platform and the IoT gateway or intelligent sensing control device; b) The TLS/SSL protocol should be used to encrypt and sign the transmitted data to ensure the privacy and integrity of the data; c) For sensitive data or control operations, higher-strength encryption and authentication strategies can be used.9 Protocol adaptation9.1 Message subject The message subject should include the message subject identification, access account number, and message sending or receiving device identification. Different underlying protocol transmission mode pairs The message subject adopts different processing methods, as follows. a) The underlying protocol should adopt the transmission mode of the message agent, and send and subscribe through the message topic; b) The bottom layer protocol should adopt a point-to-point transmission mode, and the message subject is encapsulated into the message packet of the bottom layer protocol. 9.2 Low-level protocol service interface The underlying protocol should meet the following requirements when providing services. a) The underlying protocol provides a service interface to AAP. b) AAP transfers the message connection identifier when calling the service interface of the underlying protocol. Message connection identification in IoT gateway or IntelliSense The control device is generated when the application platform is registered, and is used to uniquely identify the message connection between the IoT gateway or the intelligent perception control device and the application platform. c) The underlying protocol provides service interfaces to AAP, including (but not limited to). 1) Access address binding interface. AAP provides access addresses and related access parameters to the underlying protocol through this interface. 2) Device registration interface. The underlying protocol verifies whether the AAP message is legal through this interface. 3) Connection establishment interface. For the underlying protocol that adopts the message proxy mode, when AAP calls this interface, the IoT gateway or smart Able to perceive the control device and the application platform are connected to the message broker, and subscribe to related message topics; IoT gateway or After the intelligent perception control device is successfully registered on the application platform, the AAP connection is established and the underlying protocol is marked as connection established Stand. When the registration fails, after AAP sends a registration failure message to the protocol peer, it calls the connection closing interface of the underlying protocol to close the connection. For the underlying protocol of the point-to-point transmission mode, AAP calls this interface to implement the IoT gateway or The intelligent perception controls the direct connection between the device and the application platform, and the rest of the process is the same as the message agent mode. 4) Message sending interface. AAP calls this interface to send protocol messages. 5) Message report interface. After the underlying protocol receives the AAP message, call this interface to report the received message to AAP. 6) Connection status query interface. AAP can query the connection status by calling this interface. 7) Connection close interface. If the IoT gateway or intelligent perception control device sends a logout request to the application platform, or a message The agent reports that the IoT gateway or intelligent sensing control device has been disconnected, and AAP calls this interface to close the connection. 9.3 Low-level protocol adaptation 9.3.1 MQTT protocol When adapting to MQTT (Telemetry Transport Protocol). a) The message subject of AAP should be directly mapped to the subject of MQTT; b) The message in AAP should be directly encapsulated into the MQTT message body; c) The access account and password of AAP should correspond to the client account and password of the message broker in MQTT. 9.3.2 HTTP protocol When adapting to HTTP. a) The HTTP header should add corresponding header fields; b) Multiple interaction modes between the application platform and the IoT gateway or intelligent perception control equipment should be implemented. 9.3.3 Websocket protocol When adapting to Websocket, the message subject and body of the AAP should be directly encapsulated into the Websocket message. ......Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 38637.1-2020_English be delivered?Answer: Upon your order, we will start to translate GB/T 38637.1-2020_English as soon as possible, and keep you informed of the progress. The lead time is typically 2 ~ 4 working days. The lengthier the document the longer the lead time.Question 2: Can I share the purchased PDF of GB/T 38637.1-2020_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 38637.1-2020_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet.Question 3: Does the price include tax/VAT?Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countriesQuestion 4: Do you accept my currency other than USD?Answer: Yes. If you need your currency to be printed on the invoice, please write an email to Sales@ChineseStandard.net. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay. |
