MH/T 3031-2023 in English
VALIDTechnical requirement of civil aviation government data sharing and interchanging
- Issued on:2023-07-21
- Implemented on:2023-08-01
- File Format:PDF
- Delivery:Via email within 1~3 business days
$204.00
| Standard No: | MH/T 3031-2023 |
| Document status: | VALID |
| Title in English: | Technical requirement of civil aviation government data sharing and interchanging |
| Title in Chinese: | 民航政务数据共享与交换技术要求 |
| Language: | English |
| File Format: | Electronic (PDF) |
| Delivery: | Via email within 1~3 business days |
| Issued on: | 2023-07-21 |
| Implemented on: | 2023-08-01 |
| ICS Classification: | 35.240.60-IT applications in transport and trade |
| Chinese Classification: | L76-Text preparation and communication |
| Professional Classification: | MH-Civil Aviation |
| Related Keywords: | civil aviation government data sharing
civil aviation government data data exchange system meteorological data data delay |
| Related Topics: | mh/t
civilian robot Unmanned driving laboratory Aviation Data Interface character data Unmanned driving laboratory General purpose for military unmanned aerial vehicles |
本文件规定了民航数据共享交换平台的总体框架、总体要求、交换方式、交换流程和安全要求。
本文件适用于规范中国民用航空局各司局政务信息系统之间，以及民航局各司政务信息系统与国家政务服务平台之间的政务数据共享与交换。
Introduction
Analysis of the core framework of the standard
This standard constructs a civil aviation government data sharing and exchange platform consisting of a directory center, a resource center, and a data exchange system. Its technical architecture is shown in the figure below:
Comparison of data exchange methods
| Exchange type | Applicable scenarios | Key technical parameters | Efficiency indicators |
|---|---|---|---|
| File exchange | Unstructured/low-frequency updated data | Support XLS/XML/CSV formats, no limit on file size | Update cycle ≥ 1 day |
| Database-table exchange | Massive historical/incremental data | Support timestamp/mark bit monitoring, indexing required | Real-time synchronization capability |
| Service interface | High-frequency real-time interaction | REST/WebService protocol, configurable timeout | Millisecond-level response |
Key technical points
1. Database-table exchange monitoring mechanism
The standard clearly requires the use of two data increment identification methods: timestamp (hpt_update_time) or mark bit (hpt_status). Note the following when implementing:
- The timestamp method requires system clock synchronization, with an error of ≤1 second
- The tag bit must include three states: '0-not exchanged/1-exchanged/2-deleted'
2. Service interface specification
The interface naming follows the rule of department abbreviation+information resource name+operation, for example:
Flight Standards Department_Pilot Qualification Data_Query
Implementation Suggestions
Civil Aviation Meteorological Data Sharing Case
A regional administration adopts library table exchange to achieve real-time synchronization of meteorological data:
- Establish a meteorological theme database table, including the hpt_update_time field
- Set a 15-minute incremental synchronization period
- Push data to 12 subordinate units through the exchange platform
After implementation, data delay was reduced from 2 hours to 3 minutes
Safety and compliance requirements
Chapter 7 of the standard clearly stipulates:
- All users must log in through the Civil Aviation Administration unified authentication platform
- Data usage must follow the "least authorization principle"
- Front-end node data cleanup must be performed every month
Loading PDF document...
Error loading PDF. Please make sure the file is valid and try again.
