HJ 727-2014Technical specification for data exchange of environmenal information (English PDF)

Foreword

To implement the "People's Republic of China Environmental Protection Law" to strengthen environmental information management, standardize the process of environmental information exchange, Promote environmental data sharing and application, the development of this standard.

This standard specifies the XML description of environmental information, exchange format, describes the environment between the heterogeneous system letter Exchange model, transmission mode, exchange process.

Appendix A and B of this standard are normative and Appendix C is an informative appendix.

This standard is released for the first time.

This standard is organized by the Ministry of Environmental Protection Science and Technology Standards Division.

The main drafting of this standard. the Ministry of Environmental Protection Information Center, Jiangsu Province Environmental Information Center.

The Environmental Protection Department of this standard approved on December 25, 2014.

This standard is implemented on March 1, 2015.

This standard is explained by the Ministry of Environmental Protection.

Environmental Information Exchange Technical Specification

1 Scope of application

This standard specifies the XML description of the environmental information, the exchange format, the exchange model, the transmission mode, the exchange process Etc., applicable to national, provincial and municipal environmental protection departments between the environmental information exchange activities.

The exchange of various types of environmental information can be based on the basis of this standard, according to the exchange of information items, to develop detailed data Exchange message format. Such as environmental pollution sources automatic monitoring of information transmission, exchange for HJ/T 352-2007.

2 Normative reference documents

The contents of this standard refer to the following documents or their terms. Those who do not specify the date of the reference file, the effective version of the appropriate for this standard.

Basic set of character set for Chinese characters in information exchange GB 2312-1980 GB 13000.1-1993 Information technology - Generic multi-octet character set (UCS) Part 1. Architecture and basic Text plane HJ/T 352-2007 Environmental pollution source automatic monitoring information transmission, exchange technical specifications (Trial) Classification and code of environmental information HJ/T 417-2007

3 Terms and definitions

The following terms and definitions apply to this standard.

Environmental information Environmental management, environmental science, environmental technology, environmental protection industry and other environmental protection-related data, instructions and signals Etc., as well as related dynamic change information, including text, numbers, symbols, graphics, images, and sound and other shapes formula.

4 Acronym

The following abbreviations apply to this standard.

FTP File Transfer Protocol (File Transfer Protocol) HTTP HyperText Transfer Protocol (HyperText Transfer Protocol) SOAP Simple Object Access Protocol (Simple Object Access Protocol) XML Extensible Markup Language (Extensible Markup Language) EiXML environment information can be extended markup language (environmenal information Extensible Markup Language)

5 Environmental Information Classification

The classification of environmental information shall be in accordance with the requirements of HJ/T 417-2007.

6 Exchange information XML description

7 Environmental Information Exchange Network Foundation

The environmental information exchange between the nodes adopts the national environmental protection business network.

Environmental Information Exchange the environment information exchange method is divided into data transmission and data call in two ways.

12 Environmental information exchange process

020 Data does not exist Operation data does not exist

030 Data already exists Operational data already exists

031 Data is ambiguous operation of the data ambiguity

032 Data format Incorrect data format does not match target type

033 data capacity is too large capacity of the data is too large, does not meet the transmission requirements

040 Permission Overrun exceeds the assigned permission range

050 Database error database system error

060 can not establish a network connection network can not connect to the end node 061 network connection interrupted the network suddenly interrupted, the exchange process is not complete

12.3.3 Data error

Data content related to the error message. If the receiver receives an incorrectly formatted packet, it needs to be sent back to the sender Return data error message. Data error information structure see Table 8, "data error code" coding rules in Table 9.

Table 8 Data Error Message Structure

Data error code data error description See Appendix A Information Interchange .xsd

Table 9 "Data Error Encoding" rules

Coding description

001 data is malformed

002 The package version is incorrect

003 Unsupported exchange type 004 exchange format error 005 packets can not be verified by Schema 006 packet signature verification is incorrect 007 is not connected to the specified recipient 008 address does not match, that is, the receiver of the packet is not the same as the "receiver" of the packet Note. The default service priority of the data is 4, and the default service priority is 3.

13 Environmental Information Exchange Message Specification

13.1 Environment information exchange message structure the eixml message is the basic exchange unit in the environment information exchange, including the message header and the message body. Message structure See Table 10.

Table 10 eixml message structure

The head of the Source See Appendix B eiXML.xsd

13.2 Message header

The purpose of the message header is to transfer the packet correctly to the destination address when the information between the two nodes is exchanged.

The header structure is shown in Table 11.

Table 11 Message header structure

Sender Receiver Message No. Service Time Service Time Service Type Service Priority Receipt Source See Appendix B eiXML.xsd 13.2.1 sender the node that sent the packet.

13.2.2 Receiver

The node that receives the packet.

13.2.3 Message serial number the environment information data matches the sequence number of the packet when the information is exchanged between the sender and the receiver.

The message sequence number is generated by the data sender, and the receiver increments the message sequence number by a length of 24 bytes Visible string, the composition of the way.

Year Month Day Hour Minute Seconds Random Number Accumulation YYYYMMDDHHMMSSSSSRRRRnnn where the random number is a decimal representation of less than 9999 randomly generated numbers, the cumulative number of the beginning of 001.

If a node of the data transmission time for December 10, 2009 15.25.24 seconds 023 milliseconds, with Machine number is 1208, the cumulative number is 001, then the data transmission message serial number is..200912101525241208001; then the message of the recipient is.200912101525240231208002.

13.2.4 Service hours the service time shall be in accordance with the requirements of 10.2.4 of HJ/T 352-2007.

13.2.5 Service time limit the service time limit shall comply with the requirements of 10.2.1 of HJ/T 352-2007.

13.2.6 Service Type

Indicates the type of packet carrying information, which is data request and data transmission.

The service type can be expanded as needed.

13.2.7 Service priority Indicates the priority of the packet at the time of network transport switching and system processing. Generally divided into 5, the higher the series, priority the higher the level. If the request packet specifies that the service priority is level 5, the service priority of the corresponding packet is 5 levels.

13.2.8 Receipt requirements Define whether the receiver is required to give a receipt that the other party has received the packet. 0 indicates that no receipt is required, 1 indicates that it is required to return, the default is 0.

13.3 Message body

13.3.1 Structure of the message body the environmental information sender needs the data content of the receiving party, including the data information or the error information generated by the system. can to expand as needed. The structure of the report is shown in Table 12.

Table 12 Structure of the message body

Environmental information classification code information type signature information system receipt

13.3.2 Environmental Information Classification Code the environmental information classification code shall comply with the requirements of HJ/T 417-2007.

13.3.3 Information Type the information type code is shown in Table 13.

Table 13 Information Type Code

Encoding information type

13.3.4 Signature information the signature information consists of five elements. a summary algorithm, a signature algorithm information, a signature value, a signature time, and a signature note.

The algorithm is as follows. 0,1,2.0 denotes SHA-1 algorithm, 1 denotes MD5 algorithm, 2 denotes SHA-1 and MD5, can be expanded according to actual needs.

The signature algorithm information is. signature algorithm name and public key certificate. The signature algorithm name is. 0,1,2.0 that RSA Algorithm, 1 for DSS algorithm, 2 for ECC algorithm (according to actual needs). The public key certificate is held by the signer Public key certificate.

The signature information structure is shown in Table 14. The information structure of the signature algorithm is shown in Table 15.

Table 14 Signature information structure

Algorithm signature algorithm signature

Table 15 Signature algorithm information structure

Public signature certificate Used by eiXML Source See Appendix B eiXML.xsd

13.3.5 System receipt when the receiver correctly receives the packet, it returns the acknowledgment packet correctly received by the sender.

13.3.6 Data items

Transfer data according to message type.

Environmental Information Exchange Security Mechanism

14.1 Authentication

When the child node communicates with the parent node, it is authenticated to ensure the security of the node. When the parent node communicates with the child node, Secure the node with heartbeat information.

14.2 Encrypted transmission each node uses SSL configuration, requires the sender node to use HTTPS to log in, through authentication After the data is encrypted and transmitted. Can be encrypted according to other circumstances using other means of transmission.

14.3 Signature

In the data transmission process, require the transmission node to join the data signature information. The signature information element is within the data element the summary of the signature is signed.

14.4 Data consistency Data transmission process, the need to ensure data consistency. When the same data is repeated, the last one is used the data shall prevail and the transmission time shall be based on the recipient node time.

Appendix A

(Normative appendix) Environmental information exchange