ACP WGN04 WP 32 Rev 1
09 November 2004
AERONAUTICAL COMMUNICATIONS PANEL(ACP)
WORKING GROUP N (NETWORKING) – 4TH MEETING
New Orleans, 9th November – 19th November 2004
Decomposition of the Functionality of the Global Minimum AMHS Profile
Presented by EUROCONTROL
Summary
This paper provides a detailed decomposition of the functionality of the AMHS Global Minimum
Profile to distinguish its mandatory functions from the options made available by the Extended
Service specified in Doc. 9705. To do this, a set of definitions for AMHS-specific ‘Elements of
Service’ and Functional Groups are defined. These aid the specification and discussion of AMHS
Profiles, lend clarity to the overall functionality of different AMHS profiles and allow comparison with
X.400/MHS systems.
Decomposition of the Functionality of the Global Minimum AMHS Profile
Ref : DAS/CSM/ARCH/AMHS Eos
TABLE OF CONTENTS
1.
2.
3.
Introduction .....................................................................................................................................1
1.1
References ................................................................................................................................1
1.2
Abbreviations ............................................................................................................................1
MHS Standard Functional Groups .................................................................................................2
2.1
Standard Functional Groups .....................................................................................................2
2.2
Role of Standard Functional Groups in AMHS .........................................................................2
AMHS Elements of Service ............................................................................................................3
3.1
AMHS IPM Heading Extension EoS .........................................................................................3
3.2
AMHS Binary Body Part EoS ....................................................................................................3
3.3
AMHS ATS Message Legal Recording EoS .............................................................................3
3.4
AMHS Message Server Access EoS ........................................................................................3
3.5
AMHS use of ATN Directory (ATN-DIR) EoS ...........................................................................3
3.6
AMHS Secure User EoS ...........................................................................................................3
3.7
AMHS Address Conversion EoS ..............................................................................................4
3.8
AMHS Systems Management EoS ...........................................................................................4
3.9
AMHS AFTN Access Unit EoS .................................................................................................4
3.10 AMHS CIDIN Access Unit EoS (This is possibly redundant) ....................................................4
AMHS Cryptographic Capability EoS ..................................................................................................4
3.12 AMHS Determination of AMHS User’s Capabilities EoS ..........................................................4
4.
AMHS Functions ...........................................................................................................................4
4.1
AMHS Basic ATS (AMHS Basic) .............................................................................................5
4.2
AMHS IPM Heading Extensions (IHE) FG ................................................................................5
4.3
AMHS Binary Body Part (BBP) FG ...........................................................................................5
4.4
AMHS Security (AMHS-SEC) FG .............................................................................................5
4.5
AMHS AFTN Access Unit (AFTN-AU) FG ................................................................................5
4.6
AMHS CIDIN Access Unit (CIDIN-AU) FG (This is possibly redundant) ..................................5
4.7
AMHS Directory (AMHS-DIR) FG .............................................................................................6
4.7.1 Import of ISO/IEC ISP 10611-6 DIR Functional Group components ...................................6
4.7.2 ATN Directory Support .........................................................................................................6
4.8
AMHS Management (MAN) FG ................................................................................................6
4.9
AMHS MAP (MAP) FG ..............................................................................................................6
5.
Applicability of AMHS FGs to AMHS Systems ...............................................................................7
6.
AMHS Directory Functions ............................................................................................................7
6.1
AMHS DIR Basic User .............................................................................................................7
Version: 0.5
Date: 10/11/2004
Page: ii
Decomposition of the Functionality of the Global Minimum AMHS Profile
Ref : DAS/CSM/ARCH/AMHS Eos
6.2
AMHS DIR IHE Support FG ......................................................................................................8
6.2.1 Object Classes for IHE Support ...........................................................................................8
6.2.2 Attribute Types for IHE Support ...........................................................................................8
6.3
AMHS DIR Address Publication Support ..................................................................................8
6.3.1 Object Classes for Address Publication Support .................................................................8
6.3.2 Attribute Types for Address Publication Support .................................................................8
6.4
AMHS DIR AFTN<>AMHS Conversion Support ......................................................................8
6.4.1 Object Classes for AFTN<>AMHS Address Conversion Support ......................................8
6.4.2 Attribute Types for AFTN<>AMHS Address Conversion Support .......................................8
6.5
AMHS DIR CIDIN<>AMHS Conversion Support ......................................................................8
6.5.1 Object Classes for CIDIN<>AMHS Address Conversion Support .......................................9
6.5.2 Attribute Types for CIDIN<>AMHS Address Conversion Support .......................................9
6.6
AMHS DIR Secure User Support FG ........................................................................................9
6.6.1 Object Classes for Secure AMHS User Support .................................................................9
6.6.2 Attribute Types for Secure AMHS User Support .................................................................9
6.7
AMHS DIR Systems Administrator DIR FG ..............................................................................9
6.7.1 Object Classes for AMHS Administrator Support ................................................................9
6.7.2 Attribute Types for AMHS Administrator Support ................................................................9
6.8
AMHS DIR Directory User DIR FG ...........................................................................................9
6.8.1 Object Classes for AMHS User Support ..............................................................................9
6.8.2 Attribute Types for AMHS User Support ..............................................................................9
6.9
AMHS DIR use of ATN Directory (ATN-DIR) FG ......................................................................9
6.10 Further ATN-DIR Functional Groups ......................................................................................10
7.
Functional Groups of the AMHS Global Minimum Profile ............................................................11
8.
Recommendations .......................................................................................................................12
Version: 0.5
Date: 10/11/2004
Page: iii
Decomposition of the Functionality of the Global Minimum AMHS Profile
Ref : DAS/CSM/ARCH/AMHS Eos
1.
INTRODUCTION
This paper should be considered to be an input to the discussions on AMHS
Implementation Profiles [2] and the Global Minimum AMHS Profile. It proposes a set of
definitions of AMHS-Elements of Service and Functional Groups to do this, and suggests
that they should be retained at an appropriate place so that they can be referenced by
regional profiles (thus providing a common understanding of their definitions), and also
give more transparency to actual functionality of the AMHS as compared to MHS.
The functionality of the base standards is specified as a set of more than 100 elements of
service. Each of these identifies a discrete bit of functionality of MHS. To reduce the
number of options that systems engineers need to consider during procurement, the
profiling of the original MHS (X.400) standards in the ISPs is based on the specification of
a set of useful ‘Functional Groups’ which have the following properties:

Each specifies a set of one or more MHS Elements of Service which work together to
provide a particular functionality of MHS (thus reducing the number of options);

Each implies the capability of an MHS system to receive and create the protocol
elements associated with the Element of Service;

Each implies that the MHS system component being specified can perform the
processing associated with the Element of Service.
The base standards specify MHS functionality as ‘Elements of Service’ and the ISPs
specify a set of Standard Functional Groups. Some of these Functional Groups form the
basis for specifying the procurement of AMHS functionality.
However, AMHS has more functionality than MHS, so it seems appropriate to extend the
concepts of Elements of Service and Functional Groups to include these extensions and
to be able to reference the functions that they define accurately. Also, there are a number
of quite distinct AMHS uses of the Directory which need to be defined with some
precision. So, a number of AMHS-Directory Functional Groups are also defined in this
document.
This paper therefore extends the Elements of Service and Functional Group concepts of
the ISPs into the domain of AMHS to simplify its profiling, to give names to the different
functions, and to document the new AMHS and AMHS-Directory functions with more
precision.
1.1
1.2
References
[1]
ISO/IEC ISP 10611-1 AMH1n Message Handling Systems – Common Messaging
[2]
ACP WGN02-WP14 – ‘AMHS Implementation Profiles’
[3]
ICAO Doc. 9704 SVIII and SV VI
[4]
AMHS and ATN Directory Functional Groups - An Information Paper
[5]
ICAO Doc. 9793 ‘CAMAL’
Abbreviations
EoS
FG
Version: 0.5
Element of Service
Functional Group
Date: 10/11/2004
Page: 1
Decomposition of the Functionality of the Global Minimum AMHS Profile
Ref : DAS/CSM/ARCH/AMHS Eos
2.
MHS STANDARD FUNCTIONAL GROUPS
2.1
Standard Functional Groups
The following lists the Standard MHS Functional Groups Specified in ISO/IEC 10611-1
Common Messaging for Message Transfer System functionality and ISO/IEC 12062-1
IPM Functionality:
Functional Group
MTS Relevance
IPM Relevance
ISO/IEC ISP 10611-1
ISO/IEC ISP 12062-1
X
X
Distribution Lists (DL)
XX
XX
Physical Delivery (PD)
X
X
Redirection (RED)
X
X
Latest Delivery (LD)
X
X
Return of Contents (RoC)
X
X
Security (SEC)
XX
XX
Use of Directory (DIR)
XX
XX
84 Interworking (84IW)
X
-
Simple Protected Password
(SPP)
X
X
Redirection Instructions
(RED2)
X
X
Delivery Constraints (DC)
X
X
Restricted Delivery (RD)
X
X
IPM Manual Forwarding
(FWD) new
-
X
IPM Business Class (BC)
-
XX
Conversion (CV)
Those Functional Groups marked X indicate whether they are relevant in the IPM or MTS
services. Those marked XX Bold are of particular relevance to AMHS. The remaining
Functional Groups may be of local significance within an ATSP or Region.
2.2 Role of Standard Functional Groups in AMHS
The following indicates the relevance of the Standard Functional Groups in AMHS:
Functional Group
AMHS use
Distribution Lists (DL)
To provide an equivalent functionality to the AFTN PDAI.
Mandatory for all AMHS Systems
Security (SEC) (SEC 0)
To support the optional AMHS Integrity and authentication
requirements.
Use of Directory (DIR)
To support the optional Directory name Resolution (to ORAddresses and to OSI Addresses), and to store Distribution List
definitions.
Version: 0.5
Date: 10/11/2004
Page: 2
Decomposition of the Functionality of the Global Minimum AMHS Profile
Ref : DAS/CSM/ARCH/AMHS Eos
IPM Business Class (BC)
To support IPM Heading Extensions
3. AMHS ELEMENTS OF SERVICE
Elements of service in the base standards represent the ‘atomic’ level of MHS
functionality, and are the basis for the technical specification of MHS systems. The base
standards contain in excess of 100 Elements of Service.
The following additional AMHS Elements of Service are defined for AMHS by the
specifications of the Basic and Extended AMHS services in ICAO Doc. 9705.
3.1 AMHS IPM Heading Extension EoS
This mandates:

the use of the IPM Business Class Messaging Functional Group;

for ATS Message User Agents, the logic to convey the authorization time, originatorreference, precedence-policy-identifier and precedence fields of the IPM heading and
body information to carry parts of the ATS Message Text as specified in 3.1.2.2.3.3.1
of Doc. 9705;

for MTCUs acting as AFTN Gateways, the logic to convey the authorization time,
originator-reference, precedence-policy-identifier and precedence fields of the IPM
heading to carry parts of the ATS Message Text as specified in section 3.1.2.3.4.2 of
Doc. 9705;
Note: that the CIDIN use of IHE has been regarded as redundant.
3.2 AMHS Binary Body Part EoS
This AMHS Element of Service specifies the use of the File Transfer Body Part to convey
binary data through the AMHS. The use of the File Transfer Body Part in AMHS is
specified in section 3.1.2.2.3.4 of Doc. 9705.
3.3 AMHS ATS Message Legal Recording EoS
This AMHS Element of Service provides for Legal Recording of ATS Messages passed
through AMHS as specified in sections 3.1.2.1.7, 3.1.2.2.1.2, 3.1.2.2.2.2, 3.1.2.3.3.1,
3.1.2.4.3.1 of Doc. 9705.
3.4 AMHS Message Server Access EoS
This AMHS Element of Service specifies the access mechanisms to be used between an
ATS Message UA and the Message Server. It is defined in sections ????? of Doc. 9705.
Note – the precise definitions of this are not obvious to the author at the time of drafting.
3.5 AMHS use of ATN Directory (ATN-DIR) EoS
This Element of Service mandates the AMHS processes required to use the ATN-specific
Directory Information Base defined in Doc. 9705 SV VII.
3.6 AMHS Secure User EoS
This mandates the ability of a UA to provide authentication of an originated message and
to verify such authentication.
NOTE: this Element of Service subsumes the CAMAL (Doc. 9793) defined use of the
directory ‘retrieval of certificates’, but additionally mandates access to other security
related information such as cryptographic profile parameters.
Version: 0.5
Date: 10/11/2004
Page: 3
Decomposition of the Functionality of the Global Minimum AMHS Profile
Ref : DAS/CSM/ARCH/AMHS Eos
3.7 AMHS Address Conversion EoS
Note: that this Element of Service fulfils the CAMAL (Doc.9793) Address Conversion
function.
This AMHS Element of Service mandates that an AMHS MTCU shall have the capability
of converting between AFTN and AMHS Addresses, and between CIDIN and AMHS
Addresses.
Doc. 9705 defines functions for converting between AFTN and AMHS addresses together
with a directory content schema to support it. There are three AMHS OR-Address
schemes that may need to be mapped – CAAS (the preferred scheme), XF, and MF
(which is deprecated – or – discouraged).
CAAS and XF require directory information to relate an ICAO States Name (e.g. ‘GB’ for
the UK) to the name of the corresponding ATSP’s Private Management Domain Name
(PRMD Name). This information must be accessible by all AFTN/AMHS gateways. The
directory is one way to distribute the information. ICAO have, in principle, agreed to
collect and disseminate this information (perhaps in the near future through the directory).
3.8 AMHS Systems Management EoS
This Element of Service specifies management techniques used for managing AMHS. It
is specified in Doc 9705 sections 3.1.2.1.2.4 (this will need some refinement).
3.9 AMHS AFTN Access Unit EoS
This Element of Service performs the functions of importing/exporting messages between
AMHS and the AFTN as specified in Doc. 9705 sections 3.1.2.3.4 and 3.1.2.3.5.
3.10 AMHS CIDIN Access Unit EoS (This is possibly redundant)
This Element of Service performs the functions of importing/exporting messages between
AMHS and CIDIN as specified in Doc. 9705 section 3.1.2.4.4.
3.11 AMHS Cryptographic Capability EoS
This AMHS Element of Service mandates the use of the cryptographic techniques
defined in Doc. 9705 SV VIII to support authentication of messages and to verify that
authentication.
3.12 AMHS Determination of AMHS User’s Capabilities EoS
This function (listed in CAMAL Doc. 9793) makes use of directory information to
determine the AMHS-specific capabilities of an AMHS user. One of its uses is to support
the IHE Functional Group.
4.
AMHS FUNCTIONS
This section defines one mandatory AMHS Basic function (which corresponds to the
definition of the AMHS Basic Service defined in the SARPs), and nine AMHS optional
Functional Groups as a useful collections of Standard MHS, AMHS and Directory
Functional Groups (defined in section 6) for use in AMHS procurement. Together with the
mandated Basic AMHS, they cover the entire functionality of the Basic and Extended
AMHS Service as defined in the Doc. 9705. Examination will reveal that they are sensible
and are the minimal ‘lumps’ of procurement that an AMHS system may be required to
support. Section 2.1 lists other MHS Functional Groups defined in the ISO/IEC ISPs that
may also be procured on a local basis.
Version: 0.5
Date: 10/11/2004
Page: 4
Decomposition of the Functionality of the Global Minimum AMHS Profile
Ref : DAS/CSM/ARCH/AMHS Eos
4.1 AMHS Basic ATS (AMHS Basic)
NOTE: This formalises the corresponding definition of the BASIC AMHS service defined
in Doc. 9705 in terms of AMHS profiles.
This provides the basic minimum AMHS System specified by the SARPs. It mandates:

the basic minimum MHS functionality (as expressed by the ISPs with no optional
Functional Groups selected);

the Distribution List FG;

AMHS ATS Legal Recording AMHS EoS.
It’s intent is to specify the minimum functions for conveying ATS (AFTN) Messages
through AMHS. Its implementation is mandated for all AMHS systems.
4.2 AMHS IPM Heading Extensions (IHE) FG
This is used to procure an MTCU or UA capability of generating, receiving and translating
the Business Class fields associated with the IPM Heading Extensions functions defined
in Doc 9705. It is selected to mandate:

the IPM Heading Extension EoS

AMHS Determination of AMHS User’s Capabilities EoS

the use of the AMHS DIR ATN IHE Support FG.
4.3 AMHS Binary Body Part (BBP) FG
This is used to procure the capability of a UA to generate and receive a Binary Body Part.
This is selected to mandate the use of the AMHS Binary Body Part EoS.
4.4 AMHS Security (AMHS-SEC) FG
This is used to procure a UA that is capable of authenticating the origin of a message,
and of verifying the authentication of messages received. This is selected to mandate:

the AMHS Secure User EoS;

AMHS Cryptographic capability EoS;

AMHS DIR Secure User Support FG.
4.5 AMHS AFTN Access Unit (AFTN-AU) FG
This is used to procure an AFTN<>AMHS message mapping capability for an MTCU.
This mandates:

the AMHS AFTN Access Unit EoS;

the AMHS Address Conversion EoS;

AMHS DIR AFTN<>AMHS Address conversion support.
4.6 AMHS CIDIN Access Unit (CIDIN-AU) FG (This is possibly redundant)
This is used to procure a CIDIN<>AMHS message mapping capability for an MTCU. This
is selected to mandate
Version: 0.5

the AMHS CIDIN Access Unit EoS;

the AMHS Address Conversion EoS;
Date: 10/11/2004
Page: 5
Decomposition of the Functionality of the Global Minimum AMHS Profile
Ref : DAS/CSM/ARCH/AMHS Eos

AMHS DIR CIDIN<>AMHS Address Conversion Support.
4.7 AMHS Directory (AMHS-DIR) FG
This is used to import of all of the functions defined for the ‘Use of Directory’ Functional
Group defined in ISO/ISP 10611-1, and to add AMHS specific requirements to those
functions.
4.7.1 Import of ISO/IEC ISP 10611-6 DIR Functional Group components
NOTE: that the Element of Service in the ISO/ICE ISP DIR Functional Group are
imported and mandated to ensure that AMHS-DIR supports several Directory related
functions defined in CAMAL (ICAO Doc. 9793), namely:

Name Resolution;

DL Expansion;

Determination of MHS User capabilities.
AMHS-DIR mandates the AMHS logic to access to all of the basic X.500 directory
schema elements necessary to support AMHS’s use of the Directory. In order to fulfil
some AMHS functions, some AMHS User Agents and MTAs will need to be supplied with
specific messaging related capabilities which require the following directory information,
including:

OR-Addresses;

Distribution List Information;

MHS user’s capabilities;

OSI Addresses (PSAP, SSAP, TSAP) of Message Stores and MTAs.
This data supports the user in creating and addressing messages before submission to
the MTS, supports the UA/MTA in submitting, transferring and delivering messages using
OSI data communications.
4.7.2 ATN Directory Support
In order to be able to access the ATN Directory and to support AMHS specific directory
related functions, the AMHS-DIR Functional Group also mandates:

AMHS Determination of AMHS User’s Capabilities EoS;

AMHS DIR use of ATN Directory (ATN-DIR) FG.
4.8 AMHS Management (MAN) FG
This is used to procure an XMIB capability for the subject AMHS component system. This
is selected to mandate the AMHS Systems Management EoS.
4.9 AMHS MAP (MAP) FG
This is selected to mandate the AMHS Message Server Access EoS.
Version: 0.5
Date: 10/11/2004
Page: 6
Decomposition of the Functionality of the Global Minimum AMHS Profile
Ref : DAS/CSM/ARCH/AMHS Eos
5.
APPLICABILITY OF AMHS FGS TO AMHS SYSTEMS
The following table specifies which FGs apply to the various AMHS system components.
AMHS MTA
AMHS MTCU
AMHS Message
Store
AMHS ATS
Message
Terminal
X
X
X
X
X
X
X
AMHS BBP
X
X
AMHS-SEC
X
X
Basic (BAS)
AMHS IHE
AMHS<>AFTN
AU (AFTN-AU)
X
AMHS<>CIDIN
AU (CIDIN-AU)
X
AMHS Directory
(DIR)
X
X
AMHS
Management
(MAN)
X
X
AMHS MAP
(MAP)
X
6.
X
X
X
X
X
AMHS DIRECTORY FUNCTIONS
This section defines a Basic Directory capability together with a number of optional
AMHS-Directory Functional Groups for use in procuring Directory DSA and DUA
components to support AMHS Functional Groups. Each consists of a set of Directory
Schema Elements1 that both DSAs shall store, and DUAs shall be able to access. Their
purpose is solely to support the AMHS Functional Groups specified in section 4.
Directory profiles have not traditionally been defined in terms of Functional Groups.
However, for procurement reasons it is useful to associate distinct sets of Directory
Schema with the appropriate AMHS functions that use DUAs to access information held
in DSAs. This will at least aid the discussion of Directory Profiling by attaching ‘names’ to
bits of Directory functionality. Therefore, this paper suggests that ATN Directory
Functional Groups be defined to support the AMHS - Directory procurement task.
Note: these definitions have no effect on the technology nor the ‘bits’ on the wire nor
systems interoperability2. They are merely concepts allowing the easy identification of
‘lumps’ of Directory Schema for reference purposes in procurement.
An AMHS-Directory Functional Group therefore specifies a Directory Schema that
supports an AMHS function. The following Directory Functional Groups are proposed for
the support of AMHS. A directory Functional Group will apply to both the UA and the
DSA. The list is not intended to be exhaustive.
6.1 AMHS DIR Basic User
To mandate storage of all of the basic schema elements and basic operations necessary
to support an ATN Directory and AMHS. In order to fulfil AMHS functions, some AMHS
1
E.g. Object Classes, Attribute Types and Attribute Syntaxes.
2
E.g. These Functional Groups only address Schema Elements, and not protocol aspects.
Version: 0.5
Date: 10/11/2004
Page: 7
Decomposition of the Functionality of the Global Minimum AMHS Profile
Ref : DAS/CSM/ARCH/AMHS Eos
User Agents will be supplied with specific messaging related capabilities which require
the following Directory Information, including:

OR-Addresses;

Distribution List Information;

MHS user’s capabilities;

OSI Addresses (PSAP, SSAP, TSAP) of Message Stores and MTAs.
This data is used to support the user to create and address messages before submission
to the MTS and to support the UA in submitting and taking delivery of messages using
OSI data communications.
The primary task is to support translation of user’s Directory names into OR-Addresses, a
function known as Directory Name Resolution. These schema elements are specified in
X.402 and the ISO/IEC ISP referred to as FDI2 – ISO/IEC ISP 11189.
6.2 AMHS DIR IHE Support FG
This mandates the availability of Directory Information supporting the AMHS IHE EoS.
6.2.1 Object Classes for IHE Support
TBD
6.2.2 Attribute Types for IHE Support
TBD
6.3 AMHS DIR Address Publication Support
This mandates the availability of schema elements to support AMHS Address Publication.
6.3.1 Object Classes for Address Publication Support
TBD
6.3.2 Attribute Types for Address Publication Support
TBD
6.4 AMHS DIR AFTN<>AMHS Conversion Support
This mandates the availability of schema elements to support AFTN<>AMHS Address
conversion.
6.4.1 Object Classes for AFTN<>AMHS Address Conversion Support
TBD
6.4.2 Attribute Types for AFTN<>AMHS Address Conversion Support
TBD
6.5 AMHS DIR CIDIN<>AMHS Conversion Support
This mandates the availability of schema elements to support CIDIN<>AMHS Address
conversion.
Version: 0.5
Date: 10/11/2004
Page: 8
Decomposition of the Functionality of the Global Minimum AMHS Profile
Ref : DAS/CSM/ARCH/AMHS Eos
6.5.1 Object Classes for CIDIN<>AMHS Address Conversion Support
TBD
6.5.2 Attribute Types for CIDIN<>AMHS Address Conversion Support
TBD
6.6 AMHS DIR Secure User Support FG
This specifies the additional Directory schema elements (e.g. X.509 Certificates) needed
to support secure AMHS users.
6.6.1 Object Classes for Secure AMHS User Support
TBD
6.6.2 Attribute Types for Secure AMHS User Support
TBD
6.7 AMHS DIR Systems Administrator DIR FG
Directory support for users who may need to update, modify and read any directory
information. These users will also typically be able to control the schema by defining
further schema elements (Object Classes, Attribute Types etc. ...), administer user
access rights and run directory maintenance procedures. These privileged users need
access to whole sections of the Directory Information Tree content that they control, and
use a complete schema for the Directory System Agents they control.
6.7.1 Object Classes for AMHS Administrator Support
TBD
6.7.2 Attribute Types for AMHS Administrator Support
TBD
6.8 AMHS DIR Directory User DIR FG
Users who may need to update, modify and read directory information. Certain parts of
the Directory Information Tree and schema (notably access controls, directory operational
information etc.) are not made available to these user types.
6.8.1 Object Classes for AMHS User Support
TBD
6.8.2 Attribute Types for AMHS User Support
TBD
6.9 AMHS DIR use of ATN Directory (ATN-DIR) FG
This Functional Group mandates the capability of accessing the ATN-Directory DIB as
specified in Doc.9705 SV VII.
Version: 0.5
Date: 10/11/2004
Page: 9
Decomposition of the Functionality of the Global Minimum AMHS Profile
Ref : DAS/CSM/ARCH/AMHS Eos
6.10 Further ATN-DIR Functional Groups
The preceding FG Definitions are not exhaustive. Other ATN Applications may well define
further instances.
Version: 0.5
Date: 10/11/2004
Page: 10
Decomposition of the Functionality of the Global Minimum AMHS Profile
Ref : DAS/CSM/ARCH/AMHS Eos
7. FUNCTIONAL GROUPS OF THE AMHS GLOBAL MINIMUM
PROFILE
The following table sets out the functional groups defined in this document that comprise
the Global Minimum Profile (which coincides with the SPACE profile). It also indicates the
scope of the EUR_AMHS Profile V 2.0.
EUR_AMHS
Profile
SPACE Report Page 60
Definitions
AMHS FGs (for
AMHS
Procurement)
AMHS DIR
FGs (for DIR
Procurement)
Global
Minimum
Profile
Yes
Use of Bilaterally Defined
Body Parts
BBP (4.3) – but
FTBP is used
None
Yes
Yes
Basic ISPs
AMHS-BAS
(4.1)
None
Yes
Yes
FG IPM Distribution Lists
Yes
Traffic Logging
Yes
ATS-Message-Heading
Out of scope
AFTN/AMHS Gateway
AFTN-AU (4.5)
AMHS DIR
Basic User
(6.1)
Yes
AMHS Directory
(DIR) (4.7)
AMHS DIR
AFTN<>AMHS
Conversion
Support (6.4)
Out of scope
Distributed Address
Publishing Service (note
that this seems to be a
purely directory
application, not
necessarily involving a
messaging system, but
illustrated by assuming an
AMHS personal user)
AMHS-DIR
(4.7)??
Use of IPM Heading
Extensions
AMHS-DIR (4.7)
AMHS DIR
Basic User
(6.1)
Yes
AMHS DIR
Address
Publication
Support (6.3)
The options follow
No
AMHS IHE (4.2)
AMHS DIR
Basic User
(6.1)
No
AMHS DIR
IHE Support
(6.2)
No
Security
AMHS-SEC
(4.4)
AMHS DIR
Secure User
(6.6)
No
No
CIDIN Access
CIDIN-AU (4.6)
AMHS DIR
CIDIN<>AMHS
Conversion
Support (6.5)
No
No
AMHS-DIR (4.6)
AMHS DIR
Directory User
(6.9)
MAN (4.8)
??
No
AMHS-DIR (4.7)
No
No
Version: 0.5
Use of Directory
Management
DIR (4.7)
Date: 10/11/2004
Page: 11
Decomposition of the Functionality of the Global Minimum AMHS Profile
Ref : DAS/CSM/ARCH/AMHS Eos
No
Message System Access
MAP (4.9)
??
No
8. RECOMMENDATIONS
1) ICAO ACP WGN should confirm that the interpretation of the functionality of the Global
Minimum AMHS Profile identified in the table of section 7 above is correct.
2) ICAO ACP WGN should review and consider the definitions of Functional Groups as a
contribution to clarify the terminology of AMHS profiling. This will:

provide an immediate introduction (in summary) to the functionality that AMHS adds
to the basic MHS systems specified in ISO/IEC 10021;

serve to unify procurement across different regions and ATSPs;

make specification and comparison of the Global Minimum (and other) profiles easier
and more precise.
-----------------------------------------------
Version: 0.5
Date: 10/11/2004
Page: 12