曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
investigating why the fleet is only achieving around 90% of messages
delivered by 180 seconds.
2.8 These accumulated analysis graphs provide a clear visual indication of the relative
performance of the different airlines aircraft types. They provide a very visible
representation of where improvement is needed.
Figure 2: Accumulated ADS by airline and aircraft type for 2008
2.9 We have found that some data filtering is required to obtain an accurate
representation of actual performance. Filtering is done in a number of cases as
follows:
a. Duplicated ADS reports are relatively common from all aircraft types.
These are the same reports sent two or three times from the aircraft and if
left in will skew the ADS latency data. These duplicated reports are
ISPACG/23
FIT16 WP-04
Page 5 of 10
removed from the monthly performance data but would be sent as a
separate file to the CRA.
b. We check the extracted data over known periods of system outages that
have been notified by the CSP or where our ground system has been down.
Any delayed reports during these periods are filtered from the data and
again these would be sent in a separate file to the CRA detailing the
notified outage and the delayed reports that have been filtered.
c. If a known problem exists with an aircraft type, or a particular tail in a
fleet, that is causing degraded performance data e.g. VHF transition on the
B777, we will often filter these delayed reports to verify that there is
nothing else impacting performance. This filtering would not be done on
the monthly reporting data sent to the CRA.
2.10 As a region we have now accumulated a significant amount of data and experience in
monitoring FANS1/A CPDLC communication performance and ADS latency and we
propose that the methods outlined in this WP be captured in the draft GOLD
document.
3. ACTION BY THE MEETING
3.1 The meeting is invited to:
a) Note the post implementation monitoring described in this working paper and
agrees that it fulfils the regional requirements for post implementation
monitoring.
b) Recommend that ISPACG support the inclusion of these monitoring
requirements in the draft GOLD document.
Appendix A: Monthly reporting format for CPDLC and ADS.
Appendix B: Regional monitoring statistics.
ISPACG/23
FIT16 WP-04
Page 6 of 10
Appendix A: MONTHLY REPORTING FORMAT FOR CPDLC and ADS
Recording the data points for each CPDLC transaction.
The following data points are recommended as the minimum set that should be extracted
from ANSP datalink system recordings to enable RCP analysis and provide sufficient
information for problem analysis. This does not preclude individual ANSP from extracting
additional data points for their own analysis. To obtain these data points ANSP should note
that they will require additional database information to enable the Aircraft Type and Airline
to be obtained by correlation to the Tail Number extracted from the datalink recordings. All
of the other data points are extracted from either the ACARS header or the CPDLC
application message.
1. ANSP - the four letter ICAO designator of the FIR e.g. NZZO.
2. Tail Number – the aircraft tail number in ICAO Doc 4444 Format (no hyphens,
packing dots etc) e.g N104UA (Note: Extracted from ACARS header)
3. Aircraft Type Designator – the ICAO type designator e.g B744 (Note: extracted from
ANSP database using Tail Number as key)
4. Airline Designator – the IATA designator for the airline. e.g UAL (Note: extracted
from ANSP database using Tail Number as key)
5. Date – in YYYYMMDD format. e.g 20081114 (Note: Extracted from ANSP system
data recording time stamp)
6. MAS RGS - Designator of the RGS that MAS downlink was received from e.g. POR1
(Note: This is a 3 or 4 letter designator extracted from the ACARS header DT line)
7. OPS RGS - Designator of the RGS that the operational response was received from
e.g. AKL1 (Note: This is a 3 or 4 letter designator extracted from the ACARS header
DT line)
8. Uplink Time - The timestamp on the uplink CPDLC message sent by the ANSP in
HH:MM:SS format e.g. 03:43:25 (Note: Extracted from ANSP system data recording
time stamp)
9. MAS Receipt Time - The ANSP timestamp on receipt of the MAS in HH:MM:SS
format e.g. 03:43:55 (Note: Extracted from ANSP system data recording time stamp)
10. MAS round trip time in seconds (#9-#8) e.g. 10
11. The Aircraft FMS time stamp in the operational response messages in HH:MM:SS e.g
03:44:15 (Note: Extracted from the ATCmessageHeader timestamp in the decoded
operational response message. (See RTCA DO-258A section 4.6.3.3))
12. The ANSP timestamp on the receipt of the operational response in HH:MM:SS e.g.
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
航空资料31(49)
