HOME   Cart(1)   Quotation   About-Us Policy PDFs Standard-List
www.ChineseStandard.net Database: 189760 (25 Oct 2025)

GB/T 36451-2018 English PDF

US$1104.00 · In stock
Delivery: <= 5 days. True-PDF full-copy in English will be manually translated and delivered via email.
GB/T 36451-2018: Information technology -- Telecommunications and information exchange between systems -- Community energy-saving control network protocol
Status: Valid
Standard IDContents [version]USDSTEP2[PDF] delivered inStandard Title (Description)StatusPDF
GB/T 36451-2018English1104 Add to Cart 5 days [Need to translate] Information technology -- Telecommunications and information exchange between systems -- Community energy-saving control network protocol Valid GB/T 36451-2018

PDF similar to GB/T 36451-2018


Standard similar to GB/T 36451-2018

GB/T 37684   GB/T 37685   GB/T 36327   GB/T 36458   GB/T 36444   

Basic data

Standard ID GB/T 36451-2018 (GB/T36451-2018)
Description (Translated English) Information technology -- Telecommunications and information exchange between systems -- Community energy-saving control network protocol
Sector / Industry National Standard (Recommended)
Classification of Chinese Standard L79
Classification of International Standard 35.110
Word Count Estimation 58,596
Date of Issue 2018-06-07
Date of Implementation 2019-01-01
Issuing agency(ies) State Administration for Market Regulation, China National Standardization Administration

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


---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.
Information technology--Telecommunications and information exchangebetween systems--Community energy-saving control network protocol ICS 35.110 L79 National Standards of People's Republic of China Remote communication and information exchange between information technology systems Community Energy Conservation Control Network Protocol (ISO /IEC /IEEE18880.2015, Informationtechnology-Ubiquitous Greencommunitycontrolnetworkprotocol, IDT) Published on.2018-06-07 2019-01-01 implementation State market supervision and administration China National Standardization Administration issued

Content

Foreword III Introduction IV 1 Overview 1 1.1 Scope 1 1.2 Purpose 1 2 Normative references 1 3 Terms and definitions, abbreviations 2 3.1 Terms and Definitions 2 3.2 Abbreviations 2 4 Architecture 3 4.1 UGCCNet Architecture 3 4.2 Typical Communication Process 4 4.3 Network Design 5 4.4 System Model and Deployment 5 4.5 point 7 5 Communication Protocol 8 5.1 Overview 8 5.2 Communication protocol between components and components 8 5.3 Communication protocol between component and registrar 10 6 Application Programming Interface 11 6.1 Overview 11 6.2 Data Structure of Transmission 11 6.3 Component Access Interface 12 6.4 Registrar Access Interface 14 7 data and query model 17 7.1 General 17 7.2 Point Management of Point Set Tree Structure 17 7.3 Point Collection Tree Structure Query Mode 17 8 data structure 19 8.1 General 19 8.2 Naming rules for object classes and XML elements 19 8.3 Data structure of the communication protocol between components 19 8.4 Data structure of the communication protocol between the component and the registrar 25 9 Protocol Binding 31 10 Security Considerations 31 Appendix A (informative) Typical sequence of UGCCNet communication 32 Appendix B (informative) Typical facility network system deployment 34 Appendix C (informative) query method and data method application guide 35 Appendix D (informative) Web Services Description Language for Component Access Interface 39 Appendix E (informative) Web Services Description Language for Registrar Access Interfaces 45 Appendix F (Informative) Error Types for Component and Component Communication 51 Appendix G (informative) Error type of communication between component and registrar 52

Foreword

This standard was drafted in accordance with the rules given in GB/T 1.1-2009. This standard uses the translation method equivalent to ISO /IEC /IEEE18880.2015 "Information Technology Ubiquitous Green Community Control Network Protocol." The documents of our country that have a consistent correspondence with the international documents referenced in this standard are as follows. ---GB/T 7408-2005 Data element and exchange format information exchange date and time representation (ISO 8601.2000, IDT) This standard also made the following editorial changes. --- In order to harmonize with the national standard system, the standard name was changed to "inter-communication and information between information technology systems" Interest Exchange Community Energy Conservation Control Network Agreement. Please note that some of the contents of this document may involve patents. The issuing organization of this document is not responsible for identifying these patents. This standard is proposed and managed by the National Information Technology Standardization Technical Committee (SAC/TC28). This standard was drafted. China Electronics Technology Standardization Institute, Beijing Tiandi Interconnect Information Technology Co., Ltd., Shenzhen Saixi Information Technology Technology Co., Ltd., China Telecom Co., Ltd. Beijing Research Institute, Next Generation Internet Key Technologies and Evaluation Beijing Engineering Research Center Limited company, Beijing Jiaotong University. The main drafters of this standard. Yan Hong, Song Yang, Liu Dong, Zhuo Lan, Li Wenjie, Zhang Hongke, Shu Shuai, Yu Hui.

Introduction

This standard defines important system components for building a digital community, including gateways for fieldbus networks, for building data sharing The data storage and application units of the station can be used to build ubiquitous facility network infrastructure at the building and city level. This standard In the IPv4/IPv6 network environment, the communication protocol for interconnection and data exchange between components (gateways, storage, application units) can be more Sample devices, memory, and application services including centralized management, energy saving, environmental monitoring, alarm systems, etc. are integrated. It is now widely accepted that deploying facility networks within buildings, houses, and factories is an effective tool for achieving energy management and energy efficiency goals. Networking of facilities based on the TCP/IP protocol enables energy management within buildings and even within the city. However, Most of the former systems were independently developed and operated independently, which made installation and operation costs quite high. In general, in order to better connect sensors and actuators via the Internet in the fieldbus, we have introduced gateways. meter. However, currently we require facility network applications of this size not simply to connect devices, these emerging applications are in the real world. In the implementation of the Department, it is usually necessary to have (1) large-capacity memory for storing historical data of sensor readings, and (2) users supporting interactive operations. Interface, (3) reporting system, and (4) data analyzer. These system components can work together, especially in a network of facilities with energy-aware capabilities. However due to these systems Components are developed independently and independently, so if there is no specific analysis, integration, and manipulation between the systems, It is difficult to achieve collaboration or interoperability directly. If you define a common communication protocol, you can achieve interoperability between these system components and improve the efficiency of the deployment of the facility network. At the same time, it can reduce the cost of system integration and interoperability management, enabling the facility network to be applied to small and medium-sized buildings, even in Inside the house. For product suppliers, the components produced do not need to be customized, and can still be sold all over the world, sometimes with reasonable This can achieve large-scale production. In order to achieve energy management within the entire building and even in the city, the IEEEP18880 working group launched the ubiquitous green society. The District Network Control Protocol Project (UGCCNet), which regulates the remote control architecture of the facility network. The scope and purpose of the project is to pass regulations Communication protocol between network components (ie device access gateway, data storage and application unit) to achieve interoperability between components, Thereby building a facility network infrastructure based on the Internet model. This standard was developed to support interoperability between facility network components. And the openness of component development. First, abstract the generic facility network components through a simple component model. Then, this standard defines the group Communication protocol between pieces. To support autonomous collaboration between components, this standard also introduces a registration mechanism. This standard defines the basic framework for communication and aims to build a new network for facility updates, next-generation facility management and small and medium-sized facilities. Energy saving of a scale-scale facility network. This standard extends the past facility management to transport for the purpose of achieving energy efficiency and integration of management platforms. Battalion management. In addition, the basic framework defined in this standard can also be used for system level collaboration. Remote communication and information exchange between information technology systems Community Energy Conservation Control Network Protocol

1 Overview

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.

2 Normative references

The following documents are indispensable for the application of this document. For dated references, only dated versions apply to this article. Pieces. For undated references, the latest edition (including all amendments) applies to this document. ISO 8601 data element exchange format information exchange date and time representation (Dataelementsandinterchangefor- mats-Informationinterchange-Representationofdatesandtimes)1) IETFRFC793 Transmission Control Protocol [TransmissionControlProtocol(TCP)]2) IETFRFC2460 Internet Protocol Version 6 [InternetProtocol, Version6 (IPv6) Specification] IETFRFC3986 Uniform Resource Identifier. Generic Syntax [UniformResourceIdentifiers(URI). GenericSyntax] W3C􀆿 Extensible Markup Language [ExtensibleMarkupLanguage(XML)1.0]3), 4) W3C XML namespace version 1.1 (NamespacesinXML1.1) W3C SOAP Protocol version 1.2 Part 1. Messaging framework (SOAPVersion1.2-Part 1. Messaging Framework) 4) W3C􀆿 is a trademark of the World Wide Web Consortium (registered in multiple countries); W3C is trademarked by its headquarters organization, Massachusetts Institute of Technology (MIT), Europe Registered and held by the Association for Learning and Informatics (ERCIM), Keio University of Japan and Beijing University of Aeronautics and Astronautics. W3C XML Summary Part 1. Structure (XMLSchema-Part 1. Structures) W3C XML Summary Part 2. Data Types (XMLSchema-Part 2. Datatypes) 3 terms and definitions, abbreviations 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 architecture

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...

Tips & Frequently Asked Questions:

Question 1: How long will the true-PDF of GB/T 36451-2018_English be delivered?

Answer: Upon your order, we will start to translate GB/T 36451-2018_English as soon as possible, and keep you informed of the progress. The lead time is typically 3 ~ 5 working days. The lengthier the document the longer the lead time.

Question 2: Can I share the purchased PDF of GB/T 36451-2018_English with my colleagues?

Answer: Yes. The purchased PDF of GB/T 36451-2018_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+ countries

Question 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 [email protected]. 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.