Home   Cart   Quotation   Policy   About-Us
www.ChineseStandard.net
SEARCH

MHT4035-2012 English PDF

US$479.00 · In stock
Delivery: <= 4 days. True-PDF full-copy in English will be manually translated and delivered via email.
MHT4035-2012: Data link departure clearance service
Status: Valid
Standard IDUSDBUY PDFLead-DaysStandard Title (Description)Status
MH/T 4035-2012479 Add to Cart 4 days Data link departure clearance service Valid

Similar standards

MH/T 4041   MH/T 4039   MH/T 4038   

Basic data

Standard ID: MH/T 4035-2012 (MH/T4035-2012)
Description (Translated English): Data link departure clearance service
Sector / Industry: Civil Aviation Industry Standard (Recommended)
Word Count Estimation: 19,182
Date of Issue: 19/1/2012
Date of Implementation: 1/5/2012
Issuing agency(ies): Civil Aviation Administration of China

MHT4035-2012: Data link departure clearance service

---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.
Data link departure clearance service ICS 03.220.50 V 54 MH Civil Aviation Industry Standard of the People's Republic of China Aircraft release service before takeoff based on ground-air data link Released on.2012-01-19 2012-05-01 implementation Issued by Civil Aviation Administration of China

Table of contents

Foreword...II 1 Scope...1 2 Normative references...1 3 Terms and definitions...1 4 Abbreviations...3 5 System Function...4 6 Operation and safety requirements...8 7 Data Type and Data Format...9 8 System network layout...15

Foreword

This standard was drafted in accordance with the rules given in GB/T 1.1-2009. This standard was proposed and interpreted by the Air Traffic Management Bureau of the Civil Aviation Administration of China. This standard was approved by the Aircraft Airworthiness Certification Department of the Civil Aviation Administration of China. This standard is under the jurisdiction of the China Academy of Civil Aviation Science and Technology. Drafting organizations of this standard. Air Traffic Management Bureau of Civil Aviation Administration of China, Civil Aviation Data Communication Co., Ltd., Beijing University of Aeronautics and Astronautics. The main drafters of this standard. Miao Xuan, Kang Nan, Tang Yeyang, Xu Youchen, Yan Ran, Yuan Yong, Zhang Bin, Tan Xijing, Zhu Yanbo, Zhang Jun. Aircraft release service before takeoff based on ground-air data link

1 Scope

This standard specifies the operating procedures for the implementation of aircraft release services based on ground-to-air data links (hereinafter referred to as DCL). The core business process, operation and safety requirements of the aircraft release service ground system (hereinafter referred to as the DCL system) based on the ground-air data link General technical requirements for data types, data formats, interface protocol documents, system network layouts, etc. related to core business processes are required. This standard is applicable to the design, update and inspection of various DCL systems.

2 Normative references

The following documents are indispensable for the application of this document. For dated reference documents, only the dated version applies to this article Pieces. For undated references, the latest version (including all amendments) applies to this document. GB/T 2887 General Specification for Computer Sites GB/T 9361 Computer site safety requirements GB 50173 Code for Design of Computer Room MH/T 4007 Civil Aviation Flight Dynamic Fixed Telegram Format AEEC 620 data link ground system standard interface description AEEC 622 Air Traffic Service Data Link Application Standard Based on ACARS Ground-to-Air Network AEEC 623 Character-Oriented Air Traffic Services EUROCAE ED-85A Data Link Application System File-DCL Data Link Service ICAO "Convention on International Civil Aviation" Annex 10 "Aeronautical Communications" ICAO Doc 4444-ATM/501 "Flight and Air Traffic Services Regulations" ICAO Doc 8400 "ICAO Abbreviations and Codes"

3 Terms and definitions

The following terms and definitions apply to this document. 3.1 Aeronautical fixed telecommunication network A worldwide aviation industry for the exchange of telegrams and/or digital data between aviation fixed stations with the same or compatible communication characteristics Fixed circuit system. 3.2 Air/ground data link communication network A system composed of a series of equipment that can be used to realize two-way data communication between aircraft onboard equipment and ground systems. Note. The available ground-to-air data communication network media include. very high frequency (VHF), satellite communication, high frequency (HF) communication and mode S data link, etc. 3.3 Air/ground data communication data format The coding format used for data communication between aircraft and ground application systems. 3.4 DCL service procedure The DCL system implements the business logic of data link services for aircraft release before takeoff. 3.5 Initial altitude The altitude assigned by the controller for the first time after the aircraft takes off. 3.6 Cruising level The altitude where the aircraft is located most of the time during the flight. 3.7 Secondary surveillance radar responder code The number assigned to the multiple impulse response signals issued by the mode A or C transponder. 3.8 Estimated time of departure The planned departure time of the aircraft. 3.9 Flight plan Specific information related to a scheduled flight or part of an aircraft flight provided to an air traffic service unit. 3.10 Waypoint It is used to define a specific geographic location of an area navigation route or the flight path of an aircraft performing area navigation. 3.11 Filed flight plan message According to the flight plan data submitted by the aircraft operator or his agent, the air traffic service unit will send it to all relevant air routes along the route. Telegram from the transportation service unit in China. 3.12 Revise pilot plan report modification message The telegram used to revise the relevant content in the pilot plan report. 3.13 Flight plan cancelation message Used to cancel the telegram that has been sent to the aircraft pilot plan. 3.14 Departure message A telegram used to announce the time of departure of an aircraft. 3.15 Delay message A telegram used to notify information about aircraft delays. 3.16 Standard instrument departure An aerodrome or an instrument flight rule for assignments that connect a specific runway at an airport to a listed important point usually on a designated ATS route (IFR) Departure route, the flight route phase starts from the back point. 3.17 DCL downlink request report request for departure clearance downlink message Data link downlink message containing DCL application information synthesized by airborne equipment. 3.18 DCL uplink report department clearance uplink message The DCL system synthesizes data link uplink messages containing DCL information. 3.19 DCL downlink repeat report department clearance read back downlink message Data link downlink message containing DCL retelling information synthesized by airborne equipment. 3.20 Flight system message uplink message The data link uplink message that contains logical reply information synthesized by the DCL system. 3.21 Flight data processing system A processing system or subsystem capable of providing complete flight plan data and related information.

4 Abbreviations

The following abbreviations apply to this document. ACARS aviation communication addressing and reporting system (aircraft communication addressing and reporting system) AEEC (airline electronic engineering committee) AFTN (aeronautical fixed telecommunication network) AIC aeronautical information circular (aeronautical information circular) AIP aeronautical information publication (aeronautical information publication) ATIS terminal automatic information service (automatic terminal information system) ATS air traffic service (air traffic service) CDA DCL downlink repeat report (departure clearance read back downlink) CHG Revised Pilot Plan (modification message) CLD DCL uplink (departure clearance uplink) CNL flight plan cancellation message D-ATIS data link automatic terminal information system (data link automatic terminal information system) DCL Departure Clearance DEP departure message DLA delay message ETD estimated time of departure EUROCAE European organization for civil aviation electronics (European organization for civil aviation electronics) FDPS flight plan data processing system (flight plan data processing system) FPL pilot plan report (filed flight plan message) FSM flight system message uplink (flight system message uplink) ICAO International Civil Aviation Organization (international civil aviation organization) MTBF mean time between failures (mean time between failures) RCD DCL Downlink request report (request for departure clearance) SID Standard Instrument Departure SSR secondary surveillance radar responder UTC (coordinated universal time)

5 System function

5.1 General 5.1.1 The contents of the permit issued by the DCL system to the departing aircraft shall comply with the relevant regulations of China's civil aviation air traffic management. 5.1.2 The DCL service process shall comply with the relevant regulations of EUROCAE ED-85A and related AIP/AIC. 5.1.3 The ground-to-air data communication format related to DCL service information that the DCL system interacts with the ground-to-air data link communication network shall comply with AEEC 620, Requirements of AEEC 622 and AEEC 623. 5.1.4 The DCL system shall meet the requirements of Annex 10 of ICAO Convention on International Civil Aviation, and shall be able to connect to the AFTN network and receive information Function. 5.1.5 The DCL system shall meet the requirements of ICAO Doc 4444 and ICAO Doc 8400. 5.1.6 The DCL system should be equipped with automatic processing of FPL, CHG, CNL, DLA, DEP from the AFTN network in compliance with MH/T 4007 The function of the newspaper. 5.1.7 The format of the CLD message issued by the DCL system should be in compliance with EUROCAE ED-85A, AEEC 620, AEEC 622, AEEC 623. On the basis of this, increase the release of starting altitude and cruise altitude information. 5.1.8 The CLD message issued by the DCL system should use the estimated take-off time information as the take-off time information item, and follow the hhmm (hour and minute) Formatting. 5.1.9 The DCL system should have automatic processing from FDPS or other air traffic control automation systems, and comply with the interface protocol issued by the DCL system provider. The relevant flight plan information in the proposed document to replace the relevant information from AFTN. 5.1.10 The DCL system should be established with the ground-air data link communication network, AFTN, FDPS (if any) or other air traffic control automation systems (if any) Stable, reliable, and monitorable connection. 5.1.11 The DCL system should keep UTC time accurate and have an automatic time calibration function. 5.1.12 The application software of the DCL system should be relatively independent of the hardware equipment. 5.1.13 The DCL system shall comply with the relevant confidentiality requirements of the country and the civil aviation industry, using network systems, database systems and application systems The security mechanism is set to deny illegal users from entering the system and unauthorized operations by legal users to avoid damage to the system and prevent data (including System data and business data) are stolen, deleted, or tampered with. 5.1.14 The DCL system should have a check and prompt function for the information entered by the controller. 5.1.15 The DCL system should have the ability to automatically select departure methods (including standard and non-standard departure methods) based on waypoints and relevant control rules. ability. 5.1.16 The DCL system should have the ability to obtain the external D-ATIS system or ATIS system version information, departure runway number information, and real-time display. 5.1.17 The DCL system should have a complete information query function, covering all kinds of information generated in the service process. 5.1.18 The DCL system should have the ability to save regular historical business data through system configuration parameters. 5.1.19 The DCL system should have configuration capabilities for the index parameters specified in the relevant standards to meet the needs of changes in index parameters. 5.1.20 The DCL system shall have a complete log record function. 5.1.21 The interface language used by the controller in the DCL system should be simplified Chinese. 5.1.22 The DCL system shall have a fault self-detection function. 5.1.23 The DCL system shall have the function of automatic data backup. 5.2 Service process and related requirements 5.2.1 Basic requirements 5.2.1.1 The DCL system should have the ability to automatically reject two or more DCL downlink requests issued by the flight crew. MH 5.2.1.2 The DCL system has interfaces to receive and process flight plan data from the AFTN network, FDPS or other air traffic control automation systems, Should have the ability to automatically receive and process the secondary transponder code. 5.2.2 Service Scope The service coverage is the airport activity area. 5.2.3 Service Process 5.2.3.1 DCL system service type 5.2.3.1.1 Classification The service types of the DCL system are divided into two types. regular services and additional services, and the DCL system should support both types of services. 5.2.3.1.2 DCL system general service On the basis of compliance with the relevant regulations of EUROCAE ED-85A and related AIP/AIC, supplement the logical confirmation report corresponding to the CLD message The judgment process of the document is to shorten the judgment time of CLD packet transmission failure due to the failure of ground-air data link communication. In this service mode, The length of the non-standard SID information and free text information in the DCL uplink report to be sent by the controller should not exceed 39 characters. 5.2.3.1.3 DCL system additional services On the basis of compliance with the regular services of the DCL system, if the controller is to send non-standard SID information and free text information in the DCL uplink report If the length exceeds 39 characters, the DCL system should automatically synthesize the DCL additional uplink report, that is, the CLD message, and separate the non-standard SID information Announce with free text information. 5.2.3.2 DCL system service process 5.2.3.2.1 DCL system conventional service process (see Figure 1) 5.2.3.2.1.1 The DCL service uses the flight crew to actively send an RCD request report to the DCL system within the specified time (in the time period of Ti and Tt). The way of writing begins. 5.2.3.2.1.2 When the flight crew receives the FSM reply message corresponding to the CDA message before Tt, it indicates that the DCL service has been successfully terminated. bundle. 5.2.3.2.2 DCL system additional service process (see Figure 2) 5.2.3.2.2.1 The DCL service uses the flight crew to actively send an RCD request report to the DCL system within the specified time (in the time period of Ti and Tt). The way of writing begins. 5.2.3.2.2.2 When the flight crew receives the FSM reply message corresponding to the CDA message before Tt, it indicates that the DCL service has been successfully terminated. bundle. 5.2.3.2.2.3 When there are additional CLD messages in the process, non-standard SID and free text information are not included in the CLD messages. The text part should use the 39 characters in Table 1 for prompting. RCD message-the DCL downlink request message sent by the flight crew through the onboard equipment; CLD message-the DCL uplink message containing pre-takeoff clearance information sent by the controller through the DCL system; Logical confirmation message-a downlink message that is automatically sent by the airborne device to confirm the reception of the CLD message; CDA message-the DCL downlink retelling report sent by the flight crew through the onboard equipment; FSM message-the system feedback uplink message that is automatically sent by the DCL system in response to the flight crew's downlink message according to the service process; T0--The longest time interval from the sending of the RCD message from the airborne device to the receipt of the FSM reply from the DCL system to the RCD message, published in AIP or AIC; T1--The longest time interval between sending a CLD message from the DCL system to receiving the corresponding logical confirmation message, published in AIP or AIC; T2--The longest time interval between sending a CLD message from the DCL system to receiving the corresponding CDA message, published in AIP or AIC; T3--The longest time interval from the sending of a CDA message from the airborne device to the receipt of the corresponding FSM message, published in AIP or AIC; Ti--The earliest time that the DCL service can start, its determination is closely related to the flight plan data, and it is published in AIP or AIC; Tt--The latest time that the DCL service is completed. If the DCL service is still not completed at this time, it will be regarded as a service failure, and it can still be completed after this time Enough to successfully complete the pre-takeoff release service through voice, and publish it in AIP or AIC.

6 Operational and safety requirements

6.1 Basic requirements 6.1.1 Performance requirements 6.1.1.1 The performance requirements of the DCL system shall meet the requirements of EUROCAE ED-85A. 6.1.1.2 The receiving time of a single flight plan data message of the DCL system should be less than 1 s. 6.1.1.3 The processing time of a single flight plan data message in the DCL system should be less than 1 s. 6.1.1.4 The DCL system should work normally under the following conditions. --Ambient temperature. -10 ℃～40 ℃; --Relative humidity. 10%～70%; --Power supply. AC 220 V, 50 Hz. 6.1.2 Safety requirements 6.1.2.1 The safety requirements of the DCL system shall meet the requirements of EUROCAE ED-85A. 6.1.2.2 The DCL system shall ensure the following physical safety. --Environmental safety. Comply with GB 50173, GB/T 2887 and GB/T 9361 regulations; --Equipment security. mainly includes the equipment's anti-theft, anti-destroy, anti-electromagnetic information radiation leakage, prevention of line interception, anti-electromagnetic interference and Power protection, etc. 6.1.2.3 A combination of physical isolation and the installation of firewalls between internal and external networks shall be adopted to ensure network security. Should ensure that the system intranet The WAN is physically isolated from the WAN, and only physically connected to the data source network. At the same time, in order to prevent attacks from the data source business network, the system A firewall should be installed in the part connected to the external business network to further enhance network security. 6.2 Maintainability 6.2.1 Automatic backup The core business historical data should be automatically backed up and deleted according to the configuration parameters. 6.2.2 Redundant backup It shall have the capability of regular backup of the redundant database to ensure rapid repair in the event of failure. 6.2.3 Monitoring and Alarm 6.2.3.1 Real-time monitoring The DCL system should have the function of all-weather monitoring of the core business of the system. 6.2.3.2 Automatic alarm The DCL system shall have the function of prompting maintenance personnel and controllers with sound and light alarms immediately after fault detection. 6.2.3.3 Failure point prompt After the DCL system fails, it should automatically prompt the point of failure so that the maintainer can quickly locate the cause of the failure and troubleshoot. 6.3 Other requirements 6.3.1 Server 6.3.1.1 The key server should be a server with an MTBF greater than 100 000 h. 6.3.1.2 The server shall support mainstream relational databases. 6.3.2 Network switching system 6.3.2.1 The core switch shall be an enterprise-level Gigabit switch with an MTBF greater than 100 000 h. 6.3.2.2 The ......
Image     

Tips & Frequently Asked Questions:

Question 1: How long will the true-PDF of MHT4035-2012_English be delivered?

Answer: Upon your order, we will start to translate MHT4035-2012_English as soon as possible, and keep you informed of the progress. The lead time is typically 2 ~ 4 working days. The lengthier the document the longer the lead time.

Question 2: Can I share the purchased PDF of MHT4035-2012_English with my colleagues?

Answer: Yes. The purchased PDF of MHT4035-2012_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 Sales@ChineseStandard.net. 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.