|
US$789.00 ยท In stock
Delivery: <= 5 days. True-PDF full-copy in English will be manually translated and delivered via email.
HJ 727-2014: Technical specification for data exchange of environmenal information
Status: Valid
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| HJ 727-2014 | English | 789 |
Add to Cart
|
5 days [Need to translate]
|
Technical specification for data exchange of environmenal information
| Valid |
HJ 727-2014
|
Standard similar to HJ 727-2014 HJ 511 HJ 945.3 HJ 943 Basic data | Standard ID | HJ 727-2014 (HJ727-2014) | | Description (Translated English) | Technical specification for data exchange of environmenal information | | Sector / Industry | Environmental Protection Industry Standard | | Word Count Estimation | 30,340 | | Date of Issue | 12/25/2014 | | Date of Implementation | 3/1/2015 | | Regulation (derived from) | Ministry of Environmental Protection notice 2014 No. 87 | | Issuing agency(ies) | Ministry of Ecology and Environment | HJ 727-2014: Technical specification for data exchange of environmenal information---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.
Technical specification for data exchange of environmenal information
National Environmental Protection Standard of the People 's Republic of China
Environmental Information Exchange Technical Specification
2014-12-25 release
2015-03-01 Implementation
Ministry of Environmental Protection released
1 Scope of application
2 normative reference documents
3 terms and definitions
4 Abbreviations .2
5 Environmental Information Classification
6 Exchange Information XML Description
7 Environmental Information Exchange Network Foundation
8 Environmental Information Exchange
9 The overall framework for environmental information exchange
10 Environmental Information Exchange Model
11 environmental information transmission .3
12 environmental information exchange process .4
13 Environmental Information Exchange Message Specification 15
Appendix A (normative) Environmental Information Exchange Schema.16
Appendix B (Normative Appendix) Environment Information Interchange Message Format Schema.22
Appendix C (informative) Information exchange xml file object item Example 27
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, 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, images and sound and other shapes
formula.
3.2 Information type information type
The types of data to be exchanged mainly include data sets, files, documents, reports, service information, etc.
So that the database, pictures, documents, audio, video, service information.
3.3 Information exchange
Will be distributed in different regions, different departments, different systems of the same application or different applications in the same kind of information
Format, time requirements to the exchange center (also can be another system).
3.4 exchange node exchanging node
A switching node is an environmental department that participates in the exchange of environmental information. The relationship between the switching nodes is defined according to the structure of the tree
The upper-level switching node is the parent node of the next-level switching node, and the next-level switching node is the sub-section of the upper-level switching node
Point; in accordance with the direction of transmission, all data are sent by the sender to the transmission side.
3.5 national node national node
Department of Environmental Protection. A national node is the parent of each provincial node.
3.6 provincial node
Provincial Environmental Protection Department (bureau) node. Each provincial node is a child node of a national node, and it is a node of the municipal level
Parent node.
3.7 municipal node city node
Municipal Environmental Protection Agency node. Each city node is a child node of its provincial node.
3.8 Information exchange format
A pre-defined and structured, functionally aggregated aggregate data element or set of data elements that cover the
Sharing of information on certain types of exchange information sharing requirements, aimed at bilateral or multilateral information exchange to ensure that the parties to the exchange
Information unambiguous understanding and automatic processing.
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
6.1 character set
The character set used shall comply with the requirements of GB 13000.1-1993 or GB 2312-1980.
6.2 namespace
The environment information exchange method XML description uses the namespace
Environment Information Exchange Message Format XML Description The namespace used is.
6.3 Schema description
The exchange of information Schema description shall comply with the requirements of Appendix A and Appendix B.
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.
8.1 Data transmission
A switching node actively transfers data to another switching node. For example, provincial nodes pass directly to national nodes
Lose all the data of a day water quality automatic station.
8.2 Data Calls
Data call refers to a switch node to another exchange node to send data requests, and by the node to send its number
according to. For example, a national node sends a data request to a provincial node that requires data from a source of pollution for one day.
Once the node has collected the data, the node transmits the data to the national node; or a provincial node queries the national node for another
A state of some of the data, the national node in the collection of data, the data transmitted to the provincial node to send the request.
Overall Framework for Environmental Information Exchange
The overall framework of environmental information exchange, between the provincial node and the national level node, between the municipal node and the provincial node
The data is sent with the data call. The overall framework for environmental information exchange is shown in Figure 1.
Figure 1 Overall framework for environmental information exchange
Environmental Information Exchange Model
The environment information exchange model is based on generalized XML technology for data standardization integration, realizing heterogeneous systems, heterogeneous numbers
The information exchange between the libraries. The exchange model is shown in Figure 2.
When complex cross-node environment information exchange is performed, multiple switching models can be used to complete step-by-step exchange.
Figure 2 Environmental information exchange model
11 environmental information transmission
11.1 Message Queue Transmission
The data transmission between the switching nodes uses the message queue way, through the message queue middleware to complete the child node and the parent section
Point between the data transmission.
The switch node sends a message to the message queue middleware, the format of the message can be in XML format, or only a variety of
Data, and commands, and after receiving the message, the messages are grouped and added to each message queue for execution.
11.2 FTP transmission mode
For all kinds of multimedia and text files, use FTP to transfer between switching nodes.
11.3 Web Services transmission mode
Use Web Services to transfer XML-formatted environment information.
11.4 HTTP transmission mode
Use HTTP to transfer files in the network.
11.5 SOAP transmission mode
Use SOAP to transfer XML-formatted environment information.
12 environmental information exchange process
12.1 exchange operation
12.1.1 Data request
A data request operation refers to sending a request from one node to another, requesting the party to send a set of environmental messages
The data request data structure is shown in Table 1.
Table 1 Data Request Data Structure
Children data messages
Source See Appendix A Environmental Information Exchange Method .xsd
12.1.2 Data transmission
Data transfer operation refers to a node will be a group of environmental information to another node, the data transmission data structure see table
Table 2 Data transmission data structure
Children data messages
Source See Appendix A Environmental Information Exchange Method .xsd
12.2 exchange process
12.2.1 Data upload
The main link of data upload is the data transmission operation of the child node to the parent node, the environment letter between the child node and the parent node
The exchange of certificates is carried out using the digital certificate of the certificate. The process is shown in Figure 3.
Figure 3 data upload
12.2.2 Data is issued
The main link of the data is the data transmission operation of the parent node to the child node, and the data is not sent to the parent node.
Identity for authentication. The process is shown in Figure 4.
Figure 4 data issued
12.2.3 Data Query and Response
The main link between the data query and the response is the data request of the parent node to the child node, the data of the child node to the parent node
Transmission operation, the process shown in Figure 5.
Query failed
Parent node child node
Query request
Processing success, transmission of data
Request processing
Processing error, return error message
Query failed
Request response
Processing returns the result
success
Figure 5 Data query and response
12.2.4 Cross-Node Data Query and Response
The main link between the query and response of the inter-node data is the data transmission request for the parent node A to the parent node, and the parent node
The node B data call, the data transmission of the child node B to the parent node, the data transmission of the parent node to the child node A, the child node
A and sub-node B belong to a parent node, the process shown in Figure 6.
Figure 6 Cross-node data query and response
12.3 error message
12.3.1 Error Message Structure
The error message types include operation errors, data errors, etc. The error message structure is shown in Table 3.
Table 3 Error Message Structure
Wrong operation error
See Appendix A Information Interchange .xsd
12.3.2 Operation error
A) Operational error structure
The structure of the operation in the exchange process is shown in Table 4.
Table 4 Operation error structure
Character operation error code operation error name operation error description
See Appendix A Information Interchange .xsd
B) Encoding rules
Operation category code (2-bit encoding) Transmission mode code (2-bit code) Error cause code (3-bit code).
Operation category coding, transmission mode coding, error cause code are shown in Table 5, Table 6, Table 7.
Table 5 Operation category coding
Code Name Description
01 Data transmission operation Operation related to data request
02 Data Call Operation Operation related to data transfer
Table 6 transmission mode coding
Code Name Description
01 Message Queue Transfer uses Message Queuing to transfer the way
02 FTP transfer using FTP transfer mode
03 Web Services transfers the way you use Web Services to transfer
04 HTTP transmission using HTTP transmission
05 SOAP transfer using SOAP transfer
Table 7 Error Cause Code
Code Name Description
001 digital certificate Illegal node authentication is invalid and digital certificate is invalid
002 Digital certificate has expired node authentication is invalid and digital certificate has expired
003 digital certificate has been abolished node authentication is invalid, digital certificate has been abolished
004 other certificate error node authentication is invalid, other certificate error
010 node does not exist Node information is not registered
011 node dropped node is registered but not online
012 node information expired node information is not re-registered after replacement
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" 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 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 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 signature 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
Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of HJ 727-2014_English be delivered?Answer: Upon your order, we will start to translate HJ 727-2014_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 HJ 727-2014_English with my colleagues?Answer: Yes. The purchased PDF of HJ 727-2014_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 [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.
|