| 
           
             
       
   
   US$699.00 · In stock Delivery: <= 5 days. True-PDF full-copy in English will be manually translated and delivered via email. MHT4041-2014: The technical specification of civil aviation AFTN/SITA communication system Status: Valid    
      
    
  
	
		
			| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF | 
		 
			| MH/T 4041-2014 | English | 699 | 
   Add to Cart
   | 
                    5 days [Need to translate]
                 | 
                    The technical specification of civil aviation AFTN/SITA communication system
                 | Valid | 
                    MH/T 4041-2014
                 | 
		 
	 
     
     
    
    
     
          
  
  Standard similar to MHT4041-2014 MH/T 4039   MH/T 4040   MH/T 4038    
    
  Basic data             |  Standard ID  |          MH/T 4041-2014 (MH/T4041-2014) |               |  Description (Translated English)  |          The technical specification of civil aviation AFTN/SITA communication system |               |  Sector / Industry  |          Civil Aviation Industry Standard (Recommended) |               |  Word Count Estimation  |          28,282 |               |  Date of Issue  |          28/2/2014 |               |  Date of Implementation  |          1/5/2014 |               |  Issuing agency(ies)  |          Civil Aviation Administration of China |         
  MHT4041-2014: The technical specification of civil aviation AFTN/SITA communication system---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.  
The technical specification of civil aviation AFTN/SITA communication system
ICS 03.220.50
V 54
MH
Civil Aviation Industry Standard of the People's Republic of China
Technical specifications for civil aviation automatic reporting system
2014-02-08 released
2014-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 Codes and abbreviations...2
5 Communication protocol and interface...2
6 Telegram format...4
7 Relay system...22
8 Telegraph Terminal...24
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 organization of this standard. Air Traffic Management Bureau of Civil Aviation Administration of China.
The main drafters of this standard. Li Xin, Liu Shujun, Wang Weiqing, Wang Tianyu, Zhang Chunkui, Li Lincan, Du Ming, Zhang Shiping, Tang Yanfeng. MH
Technical specifications for civil aviation automatic reporting system
1 Scope
This standard specifies the communication protocol and interface, telegram format, transmission system and telegraph terminal technical requirements of civil aviation automatic transmission system.
begging.
This standard applies to the design, construction and operation of the automatic reporting system for civil aviation air traffic management.
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.
3 Terms and definitions
The following terms and definitions apply to this document.
3.1
Channel
The virtual channel for interconnection between the relay system and the user terminal or the relay system.
3.2
Routing address
The receiving address in the telegram.
3.3
Management console
Configure the relevant parameters of the reporting system, and at the same time can monitor the operating status of the entire reporting system, record system logs and alarm information
terminal.
4 Codes and abbreviations
4.1 Code
The following codes apply to this document.
4.2 Abbreviations
The following abbreviations apply to this document.
DCE data circuit-terminating equipment
DTE data terminal equipment (data terminal equipment)
FR frame relay
ITU International Telecommunications Union (International Telecommunications Union)
LAPB link access procedure balanced
PVC permanent virtual circuit (permanent virtual circuit)
SVC switched virtual circuit (switched virtual circuit)
5 Communication protocol and interface
5.1 Interface type
The transmission equipment interface of the automatic reporting system is divided into three types. synchronous interface, asynchronous interface and Ethernet interface. Access to the automatic reporting system
User equipment should adopt the interface type and corresponding communication protocol specified in this standard.
5.2 Interface technical requirements
5.3 Synchronization interface
5.4 Asynchronous interface
5.4.1 RS232 interface
5.4.2 Current loop access
The requirements for current (specifically double current) loop access are as follows.
--Physical interface. The interface connection adopts three wires (transmitting wire, receiving wire, signal ground wire) mode;
--Current loop working requirements. voltage is DC ± 24 V, current is DC 4 mA ± 2 mA;
--Communication protocol. asynchronous communication protocol;
--Interface rate. 50 bit/s, 100 bit/s, 300 bit/s, 600 bit/s, 1.200 bit/s;
--Transmission code. When IA-5 is encoded, it contains 7 or 8 data bits, 1 or 2 stop bits, and no parity bit; the transmission code is ITA-2
When encoding, it contains 5 data bits, 1.5 stop bits and no parity bit;
--Hardware interface. Three wires (transmitting wire, receiving wire, signal ground wire) are directly interconnected.
5.5 Ethernet interface
The requirements for Ethernet access are as follows.
--Physical interface. Comply with TIA/EIA-568-A-5 and TIA/EIA-568-B.2 related to EIA-568A interface and EIA-568B interface
Regulations
--Communication protocol. comply with IEEE 802.3 regulations;
--Network protocol. IPX/SPX, TCP/IP, UDP/IP;
--Interface rate. 10 Mbit/s, 100 Mbit/s, 1 000 Mbit/s;
--Interface hardware. The interface is RJ-45 crystal head, and the interface line is shielded or unshielded twisted pair.
6 Telegram format
6.1 Name, logo and description of telegram types
6.1.1.2.1 The message header shall contain the start tag of the telegram, circuit identification, message sequence number, supplementary information and spaces.
6.1.1.2.2 When using ITA-2, the following information should be arranged in order.
――The telegram start mark ZCZC;
――A space;
――The sending terminal identification in the circuit identification is represented by one character;
――The receiving terminal identification in the circuit identification is represented by one character;
――The circuit identification number is represented by one character. If it is a number, you need to add a number key before the number;
――A space;
--number key;
——The message serial number is represented by a 3-digit, 4-digit or 5-digit number;
――A space;
――The supplementary service indication is a 2-digit date and a 4-digit UTC time.
6.1.1.2.3 When using IA-5, the following information should be arranged in order.
a) The start of the telegram is marked SOH;
b) a space;
c) The sending terminal identification in the circuit identification is represented by one character;
d) The receiving terminal identification is represented by one character;
e) The circuit identification number is represented by a character or number;
f) a space;
g) The message sequence number is represented by a 3-digit, 4-digit or 5-digit number;
h) a space;
i) The supplementary service indication is a 2-digit date and a 4-digit UTC time.
6.1.1.3 Receiving address line
6.1.1.3.1 General requirements
The address line specifies the destination address of the message. The composition of the address is composed in the following order.
a) Reroute (optional);
b) Short address line (ie supplementary address line (optional));
c) Normal address line.
Most SITA telegrams only contain normal address lines. If the address part contains multiple elements, each element should have an address before it
Start character.
6.1.1.3.2 Reroute (optional)
Only when the main route is abnormal, the diversion line will be used in the message. The diversion line should follow the header (in the short address line and the normal address
Before the line), it should contain the following parts.
a) Address start tag.
――Different according to different encoding methods;
――When using ITA-2 code, it should include a carriage return, a line feed and a letter key;
――When using Padded Baudot encoding, it should include a carriage return and a line feed;
――When using IA-5 encoding, it should contain a carriage return and a line feed;
――SITA messages only allow the combination of carriage return and line feed, and both sender and receiver should keep the same configuration;
b) Diversion mark. consists of the letters QSP and a space;
c) Route selection mark.
――It has the following two functions.
――Notify the SITA center that needs to implement the rerouting, the telegram is carried on the alternate route and has not been erroneously transferred;
――Notify the destination of the rerouting, the telegram was transferred via the alternate route;
――The format varies according to the application method. When rerouting between local users in the SITA Center, the routing standard used
The record consists of 8 characters.
――The first 4 Arabic numerals indicate the destination of the request for rerouting;
――A letter X in the middle;
――The last 3 characters represent the local SITA center code (city or airport code), which is responsible for rerouting;
――When rerouting between SITA centers, it consists of 7 characters.
――The first 3 characters are the sign of the destination address (city or airport code);
――A letter X in the middle;
――The last 3 characters represent the local SITA center code (city or airport code), which is responsible for rerouting;
――Only when an agreement relationship has been established with the redirected destination can the message redirection operation be performed;
7 Relay system
7.1 Composition
7.1.1 The automatic reporting system consists of a business processing subsystem, a communication subsystem and a monitoring subsystem.
7.1.2 The business processing subsystem mainly deals with the code conversion of input telegrams, the identification of telegram format, the decomposition of telegram content, and the processing of official telegrams.
Management, responsible routing inspection, generation of official telegrams, routing of telegrams, queue management of telegrams to be sent, composition and output of outgoing telegrams
Telegram format encapsulation and code system changes are processed by core telegram processes, and it is responsible for telegram storage and forwarding and historical records of telegram processes.
The core server of the business processing subsystem shall have a redundant configuration. The built-in large-capacity storage system of the server should meet the requirements of hard disk, fan, memory,
Hot-swappable requirements for power supplies and other components.
7.1.3 The communication subsystem is mainly responsible for the communication interface between the forwarding system and the external data network, mainly including synchronous X.25 and frame interruption,
Asynchronous RS-232-C and dual-stream interface and Ethernet interface. The hardware equipment of the communication subsystem should have redundant configuration, and by adding relevant
The hardware interface expands the access capability of the system and increases the number of users accessing the network and the type of protocol.
7.1.4 The monitoring subsystem is mainly responsible for the parameter configuration of the transmission system, the manual processing of business telegrams, the query of historical telegrams and the telegram process
The tracking and other functions should have the ability to monitor the overall reporting system, have statistics, record system traffic and user management functions.
7.2 Function
7.2.1 Communication types
7.2.1.1 Asynchronous mode
Should support Modem and non-Modem two communication methods, non-Modem methods include asynchronous X.28 and asynchronous dual-stream two; support full duplex
Management mode; supports transmission rate setting.
7.2.1.2 TCP/IP mode
Should support full-duplex processing mode; support Ethernet transmission.
7.2.1.3 Synchronization method
Should support X.25 and frame relay two communication methods, X.25 methods include PVC and SVC; support full duplex processing mode; support transmission
Rate setting.
7.2.2 Management operations
It should be able to adapt to the requirements of the forwarding business, add, modify, delete, and query communication channels at any time, and ensure the relative independence of operational influences.
The adjustment of the channel configuration should take effect immediately. When modifying or deleting the channel, make sure that the channel is being output or will be output
The security of the telegram. It should be able to independently control the input and output directions of the channel. It should be able to automatically maintain the order of receiving and sending telegrams on each channel
Serial number. For the main equipment used in system communication, corresponding communication parameter adjustment, setting, and management functions should be provided.
7.2.3 Telegram management
The telegram routing management function should be provided to facilitate the control of telegram forwarding. Route retrieval should be able to support two matching methods. full address and fuzzy address
formula. The routing function should realize the temporary rerouting of telegrams, the filtering processing based on the telegram receiving and generating addresses, the group sending processing of telegrams, and
Should provide.
――Manual processing function for error messages;
-Means to solve the backlog of messages or message loops caused by communication failures;
――Search and output functions of historical telegrams;
――Automatic and manual retransmission mechanism of telegram;
――Four-code translation function for received and sent telegrams;
――AFTN/SITA message conversion function;
――Setting functions of telegram forbidden words, double signature, telegram grade, and command telegram;
――The function of automatically generating official telegrams and responding to official telegrams.
7.2.4 Human Machine Interface
A good Chinese operation interface should be provided, and a convenient and quick menu selection function should be provided.
The user interface can accept input operations from a keyboard or a designated input device.
For the function setting screen, corresponding online help should be provided. The help information includes the purpose of function setting and the meaning of related fields, control
For the required operations in the user interface, the screen should have corresponding operation prompts.
The function parameter settings in the system should be configured in the user interface.
7.2.5 User Management
The functions of user authority division and password setting shall be provided, and the classified management of users shall be implemented to facilitate the division of responsibilities of different personnel. Should provide
Audit processing, when users are doing login, logout, configuration, and maintenance operations, an audit log can be generated to record users, operations, and operations
Time information provides a basis for judging fault responsibility in the future.
The same user should only log in on one management terminal at the same time.
7.2.6 Data Statistics
It should be able to follow the channel, telegram serial number, telegram prefix, telegram type, telegram receiving address, telegram generating address, telegram’s
The keyword and time period classification of the message make statistics on the telegram and store the statistical results.
7.2.7 Monitoring processing
7.2.7.1 System monitoring shall meet the following requirements.
——Intuitively express the monitored object;
——It can reflect the changes in the monitoring elements of the monitoring object in real time;
——The changes in the monitoring elements of the monitoring objects can be expressed in a simple and easy-to-understand form.
7.2.7.2 The system should be able to monitor the following objects and elements.
――The connection and working status of each channel;
――Communication port status of the equipment used;
-Channel input and output telegram;
――The working status of the main and standby machines (if there are main and standby system configurations).
7.2.8 Alarm handling
7.2.8.1 The system alarm shall meet the following requirements.
――The alarm information can be displayed in the form of sound and image in time, which is easy to attract the attention of operators;
――Alarm information is divided by type and displayed in the same alarm screen for easy viewing by operators;
――Only the current alarm information is displayed on the screen, and the query processing screen is provided for the past alarm information;
――Provide alarm information settings, and users can select alarm methods and types of alarm information.
7.2.8.2 The system alarm information is divided into.
――Wrong report alarm. alarm information generated due to message format or processing;
――Channel alarm. alarm information generated due to channel connection error;
――Equipment alarm. alarm information (storage) caused by equipment communication port failure;
――Log alarm. alarm information generated due to too long or too large number of log files.
7.2.9 Fault tolerance processing
7.2.9.1 Data storage
A certain redundancy algorithm should be adopted to ensure the safety of data storage, and each system should not affect the system due to the failure of the storage device in the system
Run.
7.2.9.2 Local communication network
There should be no single point of failure in the communication between the internal devices of the system.
7.2.9.3 Communication link selection
It should be able to meet the principle of failure replacement of non-critical modules through automatic and manual methods.
7.2.9.4 Communication interface
The external communication interface of the redundant system shall satisfy the principle of complete takeover of a single system.
7.2.9.5 Degraded fault tolerance
The capability of "failure weakening" should be provided. The normal transfer of telegrams should be realized in the degraded mode.
7.2.10 Printout
7.2.10.1 The printout content should include.
――Configuration information of channels, routes, and users in the system;
――Log in the system;
――Statistics of various reports generated in billing;
――The telegram that can be queried and browsed in the system.
7.2.10.2 It shall support the output of needle line printers, ink-jet printers and laser printers.
7.3 Operating environment
7.3.1 The system should be able to operate normally in the following environment.
――Working temperature. 0 ℃~40 ℃;
――Relative humidity. 20%~80%.
7.3.2 Equipment power supply requirements. voltage 220 V±20 V, frequency 50 Hz;
7.3.3 If the working environment requires, the equipment should be able to work normally in plateau areas, and the extreme altitude should not exceed 5 000 m.
8 Telegraph terminal
8.1 Functional requirements
8.1.1 It shall have the functions of processing various civil aviation messages, and processing official telegrams and reminders sent by the forwarding center.
8.1.2 It should be able to correctly parse various civil aviation messages, and correctly extract each element in the message, including. prefix, serial number, rank,
One or more information items such as receiving address, withdrawal address, generating address, date and time group, double signature, remarks, and text. For failed parsing
The telegram should be able to specify the cause of the error.
8.1.3 It shall have a message editing function that supports free editing format and template format.
8.1.4 It shall have functions such as address storage, address extraction, telegram storage and extraction, and the establishment and extraction of telegram templates.
8.1.5 It shall have the function of converting between international code and four-character code. It can check whether the message is correct or not between sending messages.
It should be able to prompt and point out the reason for the message error.
8.1.6 The received message should be able to prompt and actively display, and have the conversion display function of international code and four-character code.
8.1.7 The sent and received messages should be automatically saved, and the telegram information for at least 3 months should be saved, with corresponding query and retrieval
Features.
8.1.8 It shall be possible to modify and resend the failed message.
8.1.9 It should be able to query and delete local sending and receiving messages.
8.1.10 There should be a check on the date of sending and receiving, message type, prefix, serial number, grade, receiving address, date and time group, power generation address, double sign
The query function of any combination of words, message keywords and other information.
8.1.11 It should be able to carry out statistics on sent and received messages by date and time, and the statistical results should include the number of messages and the total number of characters in the messages.
8.1.12 It shall have the functions of communication disconnection alarm, software operation failure alarm, error message and distress report alarm, and set different alarms
Different sound prompts; alarm information should be automatically saved and searched and retrieved.
8.1.13 It should support automatic printing of receiving and sending reports, and whether or not to automatically print can be configured by the user. Should be able to print out the message query results and message statistics
Calculate the result. Should support dot matrix printer type.
8.1.14 It should be able to provide detailed online help information.
8.2 Performance requirements
8.2.1 In the query function of the telegraph terminal, the query speed of all single conditions should not exceed 2 s, and the query speed of all complex combined conditions should
No more than 5 s, and all statistical speeds should not exceed 30 s.
8.2.2 The telegraph terminal using RS-232-C interface is calculated based on an average of.200 bytes per report, and the processing volume per hour should not be less than
2 000 copies.
8.2.3 The telegraph terminal using the Ethernet port should process at least 5,000 reports per hour, with an average of.200 bytes per report.
8.2.4 The real-time alarm delay should not exceed 2 s.
8.3 Interface technical requirements
8.3.1 The terminal interface shall support standard RS232 interface, dual-flow loop interface or Ethernet interface.
8.3.2 The RS232 interface shall meet the following requirements.
――Physical interface. RS232, standard connection without Modem (7-wire system);
―Communication protocol. asynchronous communication protocol, see ITU-T X.24;
――Interface rate. 50 bit/s, 100 bit/s, 300 bit/s, 600 bit/s, 1.200 bit/s, 2 400 bit/s,
4 800 bit/s, 9 600 bit/s;
――Transmission code.
――In IA-5 code system, 7 or 8 data bits, 1 or 2 stop bits, and no parity bit;
――In the ITA-2 code system, 5 data bits, 1.5 stop bits, and no parity bit;
――Interface hardware. Interface connection adopts D-type 9-pin or D-type 25-pin plug.
8.3.3 Current (specifically double current) loop access shall meet the following requirements.
――Physical interface. The interface connection adopts three wires (transmitting wire, receiving wire, signal ground wire) mode;
――Current loop working requirements. voltage is DC ±24 V, current is DC 4 mA ± 2 mA;
——Communication protocol. asynchronous communication protocol;
――Interface rate. 50 bit/s, 100 bit/s, 300 bit/s, 600 bit/s, 1.200 bit/s;
――Transmission code.
――In the IA-5 code system, 7 or 8 data bits, 1 or 2 stop bits, no parity bit;
――In the ITA-2 code system, 5 data bits, 1.5 stop bits, no parity bit;
――Load requirements.
――Resistance between signal lines. Open circuit is ∞, closed circuit is less than or equal to 400 Ω;
――The resistance between the signal line and the public circuit is ∞;
――The resistance of the signal ground wire is less than or equal to 4 Ω;
――Hardware interface. Three wires (transmitting wire, receiving wire, signal ground wire) are directly interconnected (the ground wire is local).
8.3.4 The Ethernet interface shall meet the following requirements.
――Physical interface. Comply with TIA/EIA-568-A-5, TIA/EIA-568-B.2;
――Communication protocol. comply with IEEE 802.3;
――Network protocol. IPX/SPX, TCP/IP;
――Interface rate. 10 Mbit/s, 100 Mbit/s, 1 000 Mbit/s;
――Interface hardware. The interface is connected to RJ-45 crystal head or interface cable shielded, unshielded twisted pair (category 5).
8.4 Terminal operating environment
The terminal should be able to operate under the following environmental conditions.
――Working temperature. 0 ℃~40 ℃;
――Relative humidity. 20%~80%.
   
   
  
  
    
  Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of MHT4041-2014_English be delivered?Answer: Upon your order, we will start to translate MHT4041-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 MHT4041-2014_English with my colleagues?Answer: Yes. The purchased PDF of MHT4041-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.  
        
   
        
       
          
               
 
          |