File Transfer Body Part – Document Type Registrations



ACP Montreal 2004 Support binary messages in AMHS Danny Van Roosbroek1.011 May 2004ACP/Montreal 2004/Support binary messages in AMHS/"ACP/Montreal 2004/Support binary messages in AMHS/This paper recommends the support for binary messages in the context of AMHS, to be included in the minimum global profile.

ACP WGN04 WP 31

03 November 2004

AERONAUTICAL COMMUNICATIONS PANEL (ACP)

WorkinG group N (NETWORKING) – 4th meeting

New Orleans (USA), 8th Nov – 19th Nov 2004

Support for binary messages in AMHS

File Transfer Body Part – Document Type Registrations

Presented by EUROCONTROL

Summary

This paper outlines the need to register distinct Document Types for different Aeronautical and Meteorological Applications of File Transfer Body Parts.

Introduction – The problem

The ACP WGN has recently refined the AMHS SARPs to use the File Transfer Body Part for the transfer of Binary Data through AMHS. The distinction between different contents of the File Transfer data is indicated by the Document Type. The Document Type requires that that each distinct content (e.g. BUFR, ADEX-P) must be allocated an Object Identifier.

In the current FTBP definition (See Doc 9705 – 3.1.2.4.5.1.2.3.12), the default value is set at OID = {iso(1) standard(0) 8571(8571) document type (5) unstructured-binary(3)} – which is correct.

However in use, each different FTBP Data type is expected to implant it’s own OID value. Currently there are no plans to create such a register. Therefore, we need to register a separate OID for each application’s Document Type somewhere (e.g. one for BUFR, one for ADEX-p etc.).

A resolution

The resolution is to define a register of Document Types and to register each distinct FTBP content type as they arise. There are several things to consider in doing this:

• The register will grow as further applications are defined;

• Some Document types may have been pre-registered – e.g. the BUFR content may have been registered by its controlling authority – WMO and we may need to use their registered value;

• Other Document Types may need to be imported from other organisations;

• ACP needs to determine a suitable place in the OID tree to establish the Document Type Register and define a mechanism for maintaining it. A suitable candidate is Doc. 9705 Annex 19 for the purely aeronautical applications.

Recommendation

ACP WGN should:

• create a suitable register of aeronautical FTBP Document Types (e.g. in SV IX of Doc. 9705;

• investigate the registration status of the BUFR application, and possibly agree with WMO a suitable registration.

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download