GB/T 36451-2018Information technology -- Telecommunications and information exchange between systems -- Community energy-saving control network protocol (English PDF)

1.1 Scope

This standard defines communication between components (gateways, storage, application units) and data exchange in an IPv4/IPv6 network environment.

The protocol enables the compatibility of multi-vendor devices with an open application interface on a common digital infrastructure. This standard defines the construction

Important system components of the digital community, including gateways for fieldbus networks, storage for data sharing platforms, and application notes

Yuan can be used to build ubiquitous facility network infrastructure between buildings and within the city. This standard allows multiple service providers and integrators

Distributed operations of the infrastructure define component management protocols that support distributed infrastructure interoperability. This standard also considers the phase

The security requirements should be in order to ensure the security and integrity of the data.

1.2 Purpose

This standard applies to the construction of green communities that are well managed and energy efficient, and are allowed to be included.

Interconnection of multiple building facilities, including small-scale different field networks, data sharing platforms and application units. Products based on this standard can

Achieve ubiquitous information perception, storage and display, for example, capacity and energy use, environmental status and information, human activities, HVAC

State, lighting system, weather, alarm, data analysis, data prediction, etc. This standard provides for interoperability between system components.

And share the data platform, including the realization of synergy with the control system.

3.1 Terms and definitions

The following terms and definitions apply to this document. Terms not defined in this clause should be consulted in the IEEE Online Standards Dictionary. 5)

3.1.1

Access control accesscontrol

Allow authorized access and methods of using resources.

3.1.2

Actuator actuator

A device that receives a data signal and converts it into a physical action.

3.1.3

Extensible markup language namespace eXtensibleMarkupLanguage(XML)namespace

A method of distinguishing XML elements and attributes that have the same name but different meanings. The URL is prefixed with a "local name".

Ensure the uniqueness of the element or attribute name. URL is only used as a way to create a unique prefix, not necessarily pointing to something on the Internet.

Actual page.

3.1.4

Sensor sensor

A converter that converts physical, biological, or chemical parameters into digital signals.

3.1.5

Globally unique identifier universalyuniqueidentifier

UUID

An identifier that guarantees uniqueness within certain defined spaces.

Note. In this standard, the query expressions and lookup expressions in the transport data structure are identified by the UUID unless otherwise stated. 6)

Html.

6) The notes in the standard text, tables and graphics are for reference only and do not contain the necessary requirements for the implementation of this standard.

3.2 Abbreviations

The following abbreviations apply to this document.

AAA. Authentication, Authorization, and Accounting (Authentication, Authorization, and Accounting)

API. Application Programming Interface (ApplicationProgrammingInterface)

EPR. End-Point Reference (End-PointReference)

FTP. File Transfer Protocol (FileTransferProtocol)

HTTP. Hypertext Transfer Protocol (HypertextTransferProtocol)

HTTPS. Hypertext Transfer Protocol Secure Protocol (HypertextTransferProtocolSecure)

IP. Internet Protocol (InternetProtocol)

IPv6. Internet Protocol Version 6 (InternetProtocolVersion6)

NAT. Network Address Translation (NetworkAddressTranslation)

RPC. Remote Procedure Call (RemoteProcedureCal)

SIP. Session Initiation Protocol (SessionInitiationProtocol)

SMTP. Simple Mail Transfer Protocol (SimpleMailTransferProtocol)

SOAP. Simple Object Access Protocol (SimpleObjectAccessProtocol)

SSH. Secure Shell Protocol (SecureShel)

SSL. Secure Sockets Layer (SecureSocketsLayer)

TCP. Transmission Control Protocol (TransmissionControlProtocol)

TTL. time to live (TimeToLive)

UGCCNet. UbiquitousGreenCommunityControlNetwork

URI. Uniform Resource Identifier

UUID. Globally Unique Identifier (UniversalyUniqueIdentifier)

VPN. Virtual Private Network (VirtualPrivateNetwork)

W3C. World Wide Web Consortium (WorldWideWebConsortium)

WSDL. WebServices Description Language (WebServicesDescriptionLanguage)

XML. Extensible Markup Language (eXtensibleMarkupLanguage)

4.1 UGCCNet Architecture

This standard applies to the facility network architecture based on TCP/IP protocol, as shown in Figure 1. One of the main objectives of this standard is to implement the facility network.

Interoperability between network components. Therefore, the gateway, memory and application unit, ie the "components" defined in this standard, have the same communication connection.

mouth. The registrar has different communication interfaces with these components, which are indicated by dashed boxes in Figure 1. The component belongs to the data plane, and the registrar belongs to the control

Plane. AAA is also highlighted in Figure 1, providing operational management support. This standard does not define AAA, but related work

It may be launched in the future if necessary.

Figure 1 ubiquitous green community control network networking architecture

In a ubiquitous green community control network environment, a registrar is a proxy for components that manage meta-information, for example, the roles and roles that components play.

The semantics of the identity, etc., to achieve autonomous binding and management between components. This standard describes in detail the group of ubiquitous green community control networks.

The process of collaborating between pieces.

4.1.1 Gateway

The gateway component connects the sensors and actuators to unify the data model and access methods of these devices and to the physical layer (currently

The data model and access method of the field bus are encapsulated. The gateway operates the actuator according to the values written by other components and goes to it

His components (memory and application unit) provide the values read by the sensor.

4.1.2 Memory

The memory component stores historical data, and the values written by other components are permanently saved on the backend disk, when other components request to obtain data.

The memory is also responsible for providing the corresponding values.

4.1.3 Application unit

The application unit component provides related applications for the data read by the sensor and the instructions of the actuator. Application unit can provide user access

The port displays the current environmental conditions, supports the user to input the setting strategy for the actuator, and can also analyze the sensor as a virtual device in real time.

Get the data and provide the results of the analysis.

4.1.4 Registrar

The registrar acts as a proxy for gateways, memory, and application units, and is primarily responsible for implementing proactive and appropriate bindings between components. Registrar is not

In the data plane, there is no direct manipulation of sensors and actuators. This standard allows the system to operate without a registrar.

4.2 Typical communication process

The typical communication protocol process between components and registrars is shown in Figure 2, solid lines indicate communication between components, and dashed lines indicate components and registrars.

Communication between.

Figure 2 Typical ubiquitous green community control network communication process

The role of the Registrar Management component and the corresponding point ID. When the component needs to access the data or interface corresponding to a point identifier, the first

First query the registrar. The registrar will carry the access URI of the component that manages the data or interface corresponding to the point identifier in the returned response.

The interaction between the component and the registrar is optional. If the requesting component knows the URI of the access object through configuration, it is not necessary to check with the registrar.

Inquiry. The communication description from Process A to Process I is given below.

Note. See Appendix A for a detailed description of each communication process.

a) Registration of components. The registration information includes (1) point information managed by the gateway, and (2) data corresponding to the point identifier stored by the memory,

(3) Point data read or provided by the application unit. See 5.3.2 for details.

b) Search for the corresponding point through a semantic query. See 5.3.3 for details.

c) Search for the memory corresponding to a specified point and return the access URI of the parsed component (see IETRFFC3986) 7). specific

See 5.3.3 for content.

d) Transmission of data. The gateway sends the data acquired by the sensor to the memory. See 5.2.3 for details.

e) Acquisition of data. The application unit retrieves data from memory. If the returned data is large, the supported data is segmented sequentially, segment by segment.

transmission. See 5.2.2 for details.

f) Search for the gateway component that manages a specified point. Returns the URI of the parsed component. See 5.3.3 for details.

g) Data acquisition, the application unit obtains data from the gateway. If you don't need segmented hyperdata, you can go over a remote

The reading is completed in the procedure call. See 5.2.2 for details.

h) Notification of data. The application unit periodically sets an event query condition to the gateway, and the gateway goes to the application list when the trigger condition is met.

Yuan actively submits updated data. See 5.2.4 for details.

i) Write data. The application unit sends an instruction to the executor to the gateway. See 5.2.3 for details.

4.3 Network Design

All components can act as a TCP (see IETTFFC793) connection initiator and receiver, and the components are peer-to-peer

System, can form a flat network, so in order to not affect the direct two-way communication, you should avoid introducing a NAT router or defense

Intermediate equipment such as fire walls.

In order to solve this problem, this standard strongly recommends the use of IPv6 networks (see IETFRFC2460), in addition to

HTTP proxy or NAT traversal solutions, however, these solutions typically rely on network configuration requirements. This standard does not exclude this

Class solutions, but require them to interoperate with other systems built on a ubiquitous green community control network, specifically in addition to IPv6

External solutions are outside the scope of this standard.

4.4 System Model and Deployment

The system model of the ubiquitous green community control network is shown in Figure 3.

Figure 3 system model

As the basic unit of the ubiquitous green community control network, the component is a unified abstraction of the gateway, memory, and application unit.

For two methods. data8) and query9). Since gateways, storage, and application units are all inherited classes of components, they have the same

Interfaces (data and query) and communicate using the same protocol.

7) The notes in the standard text, tables and graphics are for reference only and do not contain the necessary requirements for the implementation of this standard.

8) In this standard, "data" is used to indicate the interface method for writing data to the component.

9) "query" in this standard refers to the method of obtaining data from components (including event-based data transmission).

Query is a method of getting data from a component (including event-based data transfer);

Data is a way to write data to a component.

The registrar acts as a proxy for the component, with different interfaces, providing registration10) and lookup11) methods.

Registration is a method of recording component roles and point semantics;

Lookup is a way to search for a specific component or point.

In the actual implementation of gateways, memory, application units, and registrars.

The gateway implements encapsulation of the field bus through the query and data methods, and provides input/output access to the physical device;

The memory saves the data obtained by the data method, and implements the query of the historical data through the query method;

The application unit implements other functions. For example, providing a user portal, implementing data processing, etc.;

The registrar manages and maintains the relationship between the component and the associated point identifier, and provides the component role and point identifier through the registration method.

Binding between semantics, providing queries for component and point identification through the lookup method.

Note. This standard also allows the calling APP system to access other components without the quary and data methods.

10) In this standard, "registration" is used to indicate the interface method for component or point registration.

11) In this standard, "lookup" is used to indicate the interface method of querying components or points.

The above unified abstraction guarantees the network components of independent R&D facilities that can be opened by any manufacturer (ie gateway, memory and application list).

yuan). At the same time, there is no need to make additional changes to the user when deploying the facility network system in the customer's building, as shown in Figure 4.

Figure 4 Implementation of the facility network system

The role of the registrar is to increase the degree of autonomy of collaboration between components. Within the operational scope, the registrar allows components to share roles

Information collaborates (in fact, not only for the operational range, but also for non-operational domains), see Figure 5.

Figure 5 Collaboration between components

4.5 points

4.5.1 Overview

This clause defines the concept of "points", a point identified by a URI-based globally unique identifier that determines the number of exchanges between components

Data flow (such as sensor readings, actuator commands, and control signals, etc.).

4.5.2 Definition

Point describes the message channel used to transfer a particular data sequence between components, a series of sensor readings, actuator commands, etc.

(such as virtual sensor readings, meta control signals) should be bound to the point. Pass at a point (from the sensor or into the actuator)

The data value represents the information, and the data value in the point can be any object type.

Data values for points can be passed between components by calling interface methods of other components. The methods provided are.

Query. Reads an object from a specified point;

Data. Writes an object to a specified point.

By using these methods, one component can get the data value of a specified point from another component, and can also associate a certain number of points.

The value is transferred to another co...