CAANEWG05NE25

8/13/2019 CAANEWG05NE25

1/58

CA/ANE/WG/5 - NE/25Organizacin de Aviacin Civil Internacional 16/12/09OFICINA REGIONAL PARANORTEAMRICA,CENTROAMRICA Y CARIBEQuinta Reunin del Grupo de Trabajo de Expertos Centroamericanos enNavegacin Area (CA/ANE/WG/5)Tegucigalpa, Honduras, 26 al 29 de enero de 2010

Cuestin 2 delOrden del Da Revisin de los asuntos sobre Navegacin Area

2.2 Actividades especficas de navegacin area2.2.2 Comunicaciones, Navegacin y Vigilancia (CNS)

SERVICIOS DEL DIRECTORIO AMC

(Presentada por la Secretara)

RESUMENEsta nota de estudio presenta el acuerdo a corto y mediano plazo entreEUROCONTROL y la OACI para la coordinacin de la atribucin ygestin de las direcciones AMHS, los Servicios de Directorio y lacapacitacin ofrecida a los usuarios para las operaciones AMC.

Referencias: Comunicaciones a los Estados: SP 54/1-03/39 y AN 7/49.1-09/34 EMX0479, del 13 de mayo de 2009 - Registro e instruccin para

la gestin y actualizacin de la informacin sobre direcciones del

sistema de tratamiento de mensajes de los servicios de trnsito

areo (ATS) (AMHS). EMX0717, del 28 de julio 2009 - Seminario de la OACI sobre

implementacin de Aplicaciones Tierra/Tierra y Aire/Tierra del

ATN y Curso de instruccin sobre el Centro de Gestin de

Mensajes ATS (AMC) para las Regiones NAM/CAR/SAM.Objetivos

EstratgicosEsta nota de estudio se relaciona con el Objetivo

estratgico D.

1. Introduccin

1.1 En cumplimiento a la Recomendacin 5/3 del Grupo de Expertos de TelecomunicacionesAeronuticas (ATNP) para la creacin de un Registro Central para la gestin del sistema de tratamientode mensajes de los servicios de trnsito areo (ATS) (AMHS), la OACI emiti la comunicacin a losEstados SP 54/1-03/39, de fecha 30 de mayo de 2003, solicitando informacin de parte de los Estados yde las organizaciones internacionales interesadas, para permitir a la OACI establecer los dominios para lagestin del AMHS y el registro de informacin para el direccionamiento.

1.2 Basndose en las respuestas recibidas por parte de los Estados, se estableci un registroque se public en la ICAO-Net en la siguiente direccin:www.icaonet.int/anb/panels/acp/amhs/amhs.cfm.

8/13/2019 CAANEWG05NE25

2/58

8/13/2019 CAANEWG05NE25

3/58

S09-1031

Tel.: +1 514-954-8219 ext. 6712

Ref.: AN 7/49.1-09/34 14 de abril de 2009

Asunto: Gestin y actualizacin de la informacinsobre direcciones del sistema de tratamiento de mensajes

de los servicios de trnsito areo (ATS) (AMHS)

Tramitacin: Inscribir a un representante del Centro COMpara que sea un usuario del Centro de gestin

de la transmisin de mensajes ATS (AMC),

mediante el procedimiento descrito en el Adjunto B

Seor/Seora:

1. Tengo el honor de sealar a su atencin una novedad reciente relativa a la gestin mundial del

sistema de tratamiento de mensajes de los servicios de trnsito areo (ATS) (AMHS) emergente. Los mtodosy procedimientos descritos en la presente sern importantes para las personas que participan en la

planificacin y explotacin de sus sistemas de conmutacin de mensajes.

2. La transicin a partir de la red de telecomunicaciones fijas aeronuticas (AFTN), que

envejece, al AMHS est en curso y contina a buen paso. Para que el AMHS funcione de manera ordenada a

escala mundial, es necesario coordinar y sincronizar la atribucin de direcciones AMHS. Atendiendo a esa

necesidad y en cooperacin con la Organizacin Europea para la Seguridad de la Navegacin Area

(EUROCONTROL), la OACI ha establecido procedimientos para la coordinacin y sincronizacin de las

direcciones AMHS a corto y medio plazo.

3. Antes de introducir los procedimientos, quisiera presentarle los antecedentes de esta novedad.

Mediante la comunicacin SP 54/1-03/39, de fecha 30 de mayo de 2003, se pidieron las observaciones deEstados y organizaciones internacionales interesadas para permitir a la OACI establecer el Registro de

dominios de gestin e informacin de direccionamiento AMHS. Dicho registro ya se ha establecido y puede

consultarse en ICAO-Net, URL: www.icaonet.int/anb/panels/acp/amhs/amhs.cfm.

4. Una vez establecido el registro, se necesitaba un medio de coordinacin de direcciones.

En la 49 reunin del Grupo Europeo de Planificacin de la Navegacin Area (GEPNA) se adoptaron dos

conclusiones relativas a lo siguiente:

APNDICE ACA/ANE/WG

NE

8/13/2019 CAANEWG05NE25

4/58

CA/ANE/WG/05-NE/25 - A2 -

Conclusin 49/23 Coordinacin de direcciones AMHS

Que se invite a la OACI a utilizar lo antes posible la instalacin del Centro europeo de

gestin

de la transmisin de mensajes ATS para apoyar la implantacin inicial del AMHS, con baseen el proyecto propuesto de procedimientos de coordinacin de direcciones AMHS entre el

Registro OACI de MD AMHS y el Centro de gestin de la transmisin de mensajes ATS.

Conclusin 49/24 Usuarios del Centro de gestin de la transmisin de mensajesAMHS

Que se invite a la OACI a pedir a los Estados situados fuera de la Regin EUR de la OACI

que se inscriban, lo antes posible, en el Centro de gestin de la transmisin de mensajes

ATS como explotadores externos de centros COM.

5. La presente comunicacin constituye una respuesta a las citadas conclusiones del GEPNA.

La OACI utilizar, a corto y medio plazo, el Centro europeo de gestin de la transmisin de mensajes ATS(AMC), proporcionado por EUROCONTROL, para coordinar la atribucin y gestin de direcciones AMHS.

Por consiguiente, se invita a todos los Estados a designar a representantes que se inscriban como usuarios del

AMC mediante el procedimiento descrito en el Adjunto B.

6. En el Adjunto A figuran los procedimientos para la coordinacin de direcciones AMHS por

intermedio del AMC. Los usuarios deben recibir capacitacin antes de que se les permita de hecho entrar

datos en el AMC (http://www.eurocontrol.int/amc).Se proporcionar (gratuitamente) a todos los usuarios

inscritos una sesin de capacitacin los das 3 y 4 de junio de 2009. La sesin de capacitacin tendr lugar en

el Instituto de servicios de navegacin area (IANS) de EUROCONTROL, situado en Luxemburgo.

7. Todos los Estados y ANSP que explotan centros COM internacionales y tengan la intencin

de implantar el AMHS en un futuro cercano deberan participar, sin demora, en el procedimiento decoordinacin de direcciones AMHS.

8. A largo plazo, se necesitar un mtodo de gestin de direcciones AMHS verdaderamente

mundial. El personal de la Seccin CNS/AIRS de la Direccin de navegacin area tomar las medidas

necesarias para elaborar recomendaciones apropiadas para el establecimiento de centros de gestin en las

Regiones de la OACI y tambin para la cooperacin entre dichos centros.

Le ruego acepte el testimonio de mi mayor consideracin y aprecio.

Taeb Chrif

Secretario General

Adjuntos:A Procedimientos a corto plazo propuestos

para la coordinacin mundial de direcciones AMHS

B Procedimiento de inscripcin

ca/CC

8/13/2019 CAANEWG05NE25

5/58

ADJUNTO Aa la comunicacin AN 7/49.1-09/34

PROCEDIMIENTOS A CORTO PLAZO PROPUESTOSPARA LA COORDINACIN MUNDIAL DE DIRECCIONES AMHS

(Basados en el Apndice O del Informe GEPNA/49)

1. INTRODUCCIN

1.1 La presente nota fue preparada por el Equipo de coordinacin interregional del sistema de

tratamiento de mensajes de los servicios de trnsito areo (ATS) (AMHS) (en breve, el Equipo IRC), creado

para tratar cuestiones interregionales relacionadas con el sistema de tratamiento de mensajes de los servicios

de trnsito areo (ATS) (AMHS) bajo la coordinacin de la Oficina Europa y Atlntico septentrional

(EUR/NAT) de la OACI (Pars), con el apoyo del Grupo Europeo de Planificacin de la Navegacin Area

(GEPNA).

1.2 Como parte de la definicin de la organizacin del trabajo a corto plazo respecto a la

utilizacin mundial del Centro de gestin de la transmisin de mensajes ATS (AMC) para el Registro de

dominios de gestin (MD) AMHS, el plan de accin del Equipo IRC abarcaba un proyecto de procedimientos

que han de elaborarse para la gestin mundial de direcciones AMHS a corto plazo utilizando el AMC1.

1.3 El AMC es un concepto definido en elManual de gestin de la transmisin de mensajes ATS

(Doc 021 EUR de la OACI) para la gestin fuera de lnea del entorno integrado y heterogneo de transmisin

de mensajes, constituido por la red de telecomunicaciones fijas aeronuticas (AFTN), la red OACI comn de

intercambio de datos (CIDIN) y el AMHS. En dicho concepto se describe la organizacin de la gestin y se

incluye un conjunto de funciones y procedimientos que se implantan en los sistemas AMC para proporcionar

servicios a los usuarios AMC de los ANSP, particularmente en sus centros de comunicaciones (COM)

internacionales.

1.4 Figuran en la presente los procedimientos propuestos, cuyo objetivo global consiste en

asegurar a corto plazo que la gestin mundial de direcciones AMHS se lleve a cabo de manera uniforme,

desde el punto de vista tanto operacional como oficial (institucional).

1.5 A medio y largo plazo, la Direccin de navegacin area crear un equipo especial para que

elabore recomendaciones apropiadas relativas a la evolucin futura de la gestin de direcciones AMHS,

incluido el posible establecimiento de centros de gestin en las Regiones de la OACI, de ser necesario. Dicho

equipo debera estar integrado por representantes de los Estados contratantes de la OACI en diversas regiones.

2. ANTECEDENTES DE LA GESTIN MUNDIAL DE DIRECCIONES AMHSA CORTO PLAZO UTILIZANDO EL AMC

2.1 El mtodo de gestin mundial de direcciones AMHS a corto plazo es el siguiente:

a) para fines operacionales, existe un acuerdo relativo al uso del AMC a corto plazo por

parte de las Regiones Europa (EUR) y Asia/Pacfico (ASIA/PAC), as como la

Administracin Federal de Aviacin (FAA) de los Estados Unidos. Debera alentarse a

otras regiones que an no hayan analizado la gestin AMHS a utilizar el AMC en cuanto

inicien el estudio de la implantacin del AMHS.

b) por lo que respecta a los aspectos institucionales, la OACI tiene la intencin de publicar

una versin oficial del registro en su sitio web.

1 Puede obtenerse informacin ms amplia en http://www.eurocontrol.int/amc/

- A3 - CA/ANE/WG/05- NE/25

8/13/2019 CAANEWG05NE25

6/58

2.2 Adems, el Registro oficial de la OACI y el AMC operacional contienen los mismos datos y

deberan armonizarse peridicamente.

2.3 La organizacin del trabajo propuesta en la presente se ha seleccionado para una gestin

mundial de las direcciones AMHS utilizando el AMC. Esto implica que debera recomendarseenrgicamente el uso del AMC a todo Estado contratante de la OACI en el mundo entero, en cuantoemprenda un proyecto o una implantacin AMHS. Los procedimientos dependern del hecho de que todoslos Estados participen en el AMHS, o sea, todos los Estados que declaren cambios en el direccionamiento

AMHS son usuarios AMC.

2.4 Estos procedimientos debern basarse en la utilizacin operacional del AMC y en la

publicacin oficial del Registro de MD AMHS por la Sede de la OACI en su sitio web utilizando datos AMC.

3. ALCANCE DE LOS CAMBIOS PREVISTOS DE DIRECCIONES AMHS

3.1 Los posibles cambios que han de tratarse como parte de la gestin de direcciones AMHS se

clasifican en dos categoras y abarcan las modificaciones siguientes:

a) Cambios importantes (no deben ser frecuentes):

1) Modificacin2del nombre PRMD,

2) Cambio de plan de direccionamiento, entre los que se definen en los Doc 9705 y

9880 de la OACI, de XF a CAAS o viceversa (poco probable);

b) Cambios pequeos (normalmente ms frecuentes):

1) Modificaciones en la tabla CAAS (asociaciones entre indicadores de lugar valor

del atributo de direccinOU y valor del atributo de direccin O).

3.2 Los cambios importantes tienen o bien repercusiones institucionales o repercusiones

operacionales considerables.

3.3 Los cambios pequeos slo tienen repercusiones operacionales, que pueden ser mucho ms

limitadas, segn el alcance de los cambios, que pueden evaluarse de manera aproximada basndose en:

a) el nmero de indicadores de lugar afectados por el cambio; y/o

b) la frecuencia de los mensajes entre los usuarios en los lugares cuyos indicadores queden

afectados.

3.4 Excepcionalmente, un cambio pequeo podra tener repercusiones institucionales. Sin

embargo, esto debera ser muy raro. Dado que no se define ningn procedimiento concreto para ello, tales

situaciones se tratarn caso por caso y de manera individual.

El trmino modificacin debera entenderse aqu de manera general, en el sentido de adicin, modificacin o supresin.

CA/ANE/WG/05- NE/25 - A4 -

8/13/2019 CAANEWG05NE25

7/58

4. SITUACIONES RELACIONADAS CON LOS PROCEDIMIENTOS

4.1 Interacciones oficiales

4.1.1 Debido a sus repercusiones institucionales o sus repercusiones operacionales considerables,

los cambios importantes deberan ser objeto de interacciones oficiales entre los Estados y la OACI. Se supone

que stas se basen en el intercambio de documentos escritos por fax o cartas. En el Adjunto A a la presente

comunicacin se proporcionan formularios para tales documentos.

4.2 Sistemas

4.2.1 A corto plazo, slo existen dos sistemas para contribuir a la gestin de direcciones AMHS,

como se mencion ms arriba:

a) el AMC implantado por EUROCONTROL bajo la gida de la Oficina EUR (Pars) dela OACI, para todos los fines operacionales, siguiendo una conclusin de GEPNA/45; y

b) el Registro OACI de MD AMHS, para fines oficiales. Este sistema est cargado condatos AMC para asegurar uniformidad con el estado operacional de la red AMHS.

4.3 Participantes

4.3.1 Los procedimientos dependen de la participacin en la actividad AMC de todos los Estados

y ANSP asociados al AMHS. Se supone que los participantes en los procedimientos sean:

a) Estados, como iniciadores de cambios en el direccionamiento AMHS y como autores de

la implantacin de sistemas AMHS. Por consiguiente, la nocin de Estado abarca:

1) las personas encargadas de las declaraciones oficiales, para cambios importantes;

2) los operadores de los Centros COM que cooperan (CCC)3encargados de la gestin

operacional del AMHS. Utilizan datos AMC para configurar sus conmutadores de

mensajes y cabeceras AFTN/AMHS.

3) otros usuarios AMC, tales como directores de proyectos AMHS, ingenieros que

participan en proyectos AMHS, personal de centros COM, etc. (Se definen para

ellos varias categoras de usuarios AMC, incluidos Usuario AMF-I4 y Usuario de

lectura nicamente);

b) Oficinas regionales de la OACI como posible interfaz para los Estados en cada Regin

de la OACI. La Oficina regional est representada por el especialista CNS;

c) La Sede de la OACI, representada por la Direccin de navegacin area y, ms

concretamente (de ser necesario), por su Seccin de comunicaciones, navegacin y

vigilancia/Servicios de recursos de informacin aeronutica (Seccin CNS/AIRS);

3 En la terminologa AMC actual, el trmino CCC se limita a Europa y se utiliza centro COM externo para Estados fuera de Europa.

Esta distincin debera desaparecer, y deberan actualizarse la terminologa y la documentacin cuando se inicie el uso mundial del

AMC basado en estos procedimientos.4 Usuario AMF-I significa un usuario AMC que participa concretamente en la gestin de AMHS fuera de lnea Funciones de

apoyo a la implantacin, en nombre de su Estado o ANSP, p. ej., el jefe del proyecto de implantacin del AMHS.

- A5 - CA/ANE/WG/05 - NE/25

8/13/2019 CAANEWG05NE25

8/58

d) Operadores AMC responsables del funcionamiento global del AMC y de los

procedimientos conexos.

5. PROCEDIMIENTO PARA CAMBIOS IMPORTANTES

5.1 En la Figura 1 se proporciona un diagrama simplificado del procedimiento propuesto para

cambios importantes. Las etapas principales son las siguientes:

1. una persona autorizada en el Estado en cuestin declara el cambio a la OACI utilizando

un formulario impreso normalizado OACI en este caso significa la Oficina regional

correspondiente a la Regin de la OACI donde est situado el Estado. El formulario

comprende la fecha de aplicacin del cambio (una fecha AIRAC);

2. el especialista CNS de la Oficina regional, en coordinacin con la Sede de la OACI,

segn corresponda5, valida el carcter aceptable del cambio declarado desde el punto de

vista oficial e institucional;

3. a raz de la validacin, el especialista CNS enva la declaracin de cambio al operador

AMC utilizando medios apropiados tales como fax, correo-e, etc. (lo que difiere de la

entrada de los datos en el AMC);

4. el operador AMC entra los datos en el AMC basndose en la respuesta recibida de la

Oficina regional en el momento apropiado, teniendo en cuenta la fecha de aplicacin del

cambio y utilizando los procedimientos operacionales del AMC;

5. en la fecha de aplicacin, o sea, en cada fecha del ciclo AIRAC, la Seccin CNS/AIRS

de la Sede de la OACI recibe del AMC un fichero de exportacin de gestin de

direcciones AMHS y lo carga en el Registro oficial OACI de MD AMHS.

5.2 Las etapas 3 a 5 se llevan a cabo como parte del funcionamiento normal del AMC. Esto

significa que, paralelamente a esta operacin, el operador AMC y los directores de AMHS en otros Estados

siguen los procedimientos AMC normales. Los operadores CCC explotan los datos AMC que reflejan el

cambio, junto con otros datos de gestin AMHS, para actualizar sus sistemas.

5.3 En cada etapa puede tener lugar coordinacin, de ser necesario, entre las distintas partes

interesadas para asegurar que el cambio propuesto sea correcto.

5 p. ej., para asegurar el carcter unvoco mundial de un nombre PRMD solicitado respecto a otras solicitudes bajo consideracin en

otras regiones.

CA/ANE/WG/05- NE/25 - A6 -

8/13/2019 CAANEWG05NE25

9/58

Figura 1: Procedimiento para tratar cambios importantes de direcciones AMHS

Procedimiento para cambios importantesSede OACIRegistro oficialde MD AMHS

Sede OACISeccin CNS

AMC

Operador CCCen el Estadoque iniciaun cambio

Entrada de datosIntercambio de documentos escritosLectura y bsqueda de datos

Directores AMHSen otros Estados:- Operadores CCC- Otros usuarios AMC

Oficinaregionalde la OACI

Operador AMC

6. PROCEDIMIENTO PARA CAMBIOS PEQUEOS

6.1 En la Figura 2 se proporciona un diagrama simplificado del procedimiento propuesto para cambios

pequeos. Las etapas principales son las siguientes:

1. el operador CCC en el Estado en cuestin entra en el AMC los datos correspondientes al

cambio previsto utilizando procedimientos operacionales AMC normales, teniendo en

cuenta la fecha de aplicacin del cambio (una fecha AIRAC);

2. el operador AMC aplica los procedimientos operacionales AMC normales, de modo que

la situacin de los datos cambiados pase a ser operacional en la fecha de aplicacin;

3. en la fecha de aplicacin, o sea, en cada fecha del ciclo AIRAC, la Seccin CNS/AIRSde la Sede de la OACI recibe del AMC un fichero de exportacin de gestin de

direcciones AMHS y lo carga en el Registro oficial OACI de MD AMHS (esta operacin

es idntica a la etapa 5 del procedimiento para cambios importantes).

6.2 Estas operaciones se llevan a cabo como parte del funcionamiento normal del AMC. Esto

significa que, paralelamente a estas operaciones, los operadores CCC y otros usuarios AMC en otros Estados

siguen los procedimientos AMC normales para explotar los datos AMC que reflejan el cambio, junto con

otros datos de gestin AMHS, para actualizar sus sistemas.

- A7 - CA/ANE/WG/05 - NE/25

8/13/2019 CAANEWG05NE25

10/58

6.3 En cada etapa puede tener lugar coordinacin, de ser necesario, entre las distintas partes

interesadas, y con el especialista CNS de la Oficina regional, de ser necesario6, para asegurar que el cambio

propuesto sea correcto.

Figura 2: Procedimiento para tratar cambios pequeos de direcciones AMHS

Sede OACIRegistro oficialde MD AMHS

Procedimiento para cambios pequeos

Sede OACISeccin CNS

Operador CCC

en el Estado queinicia un cambio

Oficinaregionalde la OACI

AMC

Directores AMHSen otros Estados:- Operadores CCC- Otros usuarios AMC

Operador AMCIntercambio de documentos escritos

Entrada de datos

Lectura y bsqueda de datos

6 La Oficina regional tendr que intervenir nicamente en casos excepcionales, tales como repercusiones institucionales de uncambio pequeo.

CA/ANE/WG/05- NE/25 - A8 -

8/13/2019 CAANEWG05NE25

11/58

Parte 1: Modificacin de la inscripcin del nombre PRMD

Estado:

Letras de nacionalidad: .

Nombre PRMD inscrito antes de la modificacin: ............................................

Se ruega considerar las opciones siguientes en caso de modificacin:

Opcin A: el nombre PRMD, que ser el identificador reservado siguiente.

Opcin B: el nombre PRMD ha de modificarse como se propone ms abajo,

despus de la validacin por la Secretara.

Opcin C: el nombre PRMD se mantendr sin cambios (slo se modifica el plan dedireccionamiento, vase la Parte 2).

Se ruega especificar su seleccin (A, B o C):

Si se seleccion B, especificar el identificador del nombre PRMD propuesto:

Fecha de aplicacin propuesta para la modificacin (una fecha AIRAC):

Nombre de la organizacin encargada de la gestin del MD AMHS (si se aplica): .

Punto de contacto: ..

Direccin de correos o electrnica y nmero de telfono/fax: ..

Comentarios adicionales:

P =

- A9 - CA/ANE/WG/05 - NE/25

8/13/2019 CAANEWG05NE25

12/58

Parte 2: Modificacin de la declaracin del plan de direccionamiento

Estado:

Letras de nacionalidad: .

Nombre PRMD inscrito antes de la modificacin: ............................................

Plan de direccionamiento declarado antes de la modificacin: ....................................

Se ruega seleccionar una de las opciones siguientes en caso de modificacin:

Seleccin A: las direcciones de usuarios AMHS deben atribuirse aplicando el plan de direccionamiento

CAAS (recomendado) en el MD AMHS explotado en el mencionado Estado.

Seleccin B: las direcciones de usuarios AMHS deben atribuirse aplicando el plan de direccionamiento

XF (preestablecido) en el MD AMHS explotado en el mencionado Estado.

Seleccin C: el plan de direccionamiento se mantendr sin cambios (slo se modifica el nombre

PRMD, vase la Parte 1).

Se ruega especificar su seleccin (A, B o C):

Si se seleccion A (CAAS), se ruega llenar la tabla siguiente respecto a todos los indicadores de lugar que

figuran en el Doc 7910 bajo las mencionadas letras de nacionalidad.

Nombre de la organizacinpara el grupo de lugares

Indicadores de lugar

(Ampliar la tabla segn corresponda)

CA/ANE/WG/05- NE/25 - A10 -

8/13/2019 CAANEWG05NE25

13/58

Fecha de aplicacin propuesta para la modificacin (una fecha AIRAC):

Nombre de la organizacin encargada de la gestin del MD AMHS (si se aplica): .

Punto de contacto: ..

Direccin de correos o electrnica y nmero de telfono/fax: ..

- A11 - CA/ANE/WG/05 - NE/25

8/13/2019 CAANEWG05NE25

14/58

ADJUNTO Ba la comunicacin AN 7/49.1-09/34

PROCEDIMIENTO DE INSCRIPCIN(basado en elManual de gestin de la transmisin de mensajes ATS,

seccin 2.5.2.4)

1. A fin de aplicar los procedimientos descritos en el Adjunto A, cada Estado y ANSP debera designar

a un usuario AMC asociado con su centro COM. Puede tambin designarse a una segunda persona

como suplente.

2. El usuario AMC debe inscribirse utilizando el enlace siguiente:

https://extranet.eurocontrol.int/http:/chow.mis.eurocontrol.be:8095/elsh_live/elsh/registerNewUserForAp

plication.do?eurocontrolresourceid=amc_users

3. Una vez terminada esta etapa, se iniciar el procedimiento de acreditacin del usuario definido en la

seccin 2.5.2. delManual de gestin de la transmisin de mensajes ATS.

4. Despus de la acreditacin del usuario, el Equipo de apoyo AMC de EUROCONTROL crear una

cuenta AMC cuyos detalles se enviarn a los usuarios. La capacitacin del usuario se planificar

tambin en esta etapa.

5. Despus de su capacitacin, el usuario podr comenzar a tener acceso al AMC utilizando

http://www.eurocontrol.int/amc/.

FIN

CA/ANE/WG/05- NE/25 - A12 -

8/13/2019 CAANEWG05NE25

15/58

S09-1467

Tel.: +1 514-954-8219 ext. 6712

Ref.: AN 7/49.1-09/34 14 de abril de 2009

Asunto: Gestin y actualizacin de la informacin

sobre direcciones del sistema de tratamiento de mensajes

de los servicios de trnsito areo (ATS) (AMHS)

Tramitacin: Inscribir a un representante del Centro COM

para que sea un usuario del Centro de gestin

de la transmisin de mensajes ATS (AMC),

mediante el procedimiento descrito en el Adjunto B

CORRIGENDO 17 DE ABRIL DE 2009

Enmindesela ltima oracin del prrafo 3 para que diga:

Dicho registro ya se ha establecido y puede consultarse en el sitio web de la OACI, en el URL:

http://www.icao.int/anb/panels/acp/amhs/amhs.cfm

FIN

- A13 -

8/13/2019 CAANEWG05NE25

16/58

1

ATS Messaging ManagementATS Messaging Management

ATS Messa in Mana ement Centre AMC

European Organisation for the Safety of Air Navigation

AMC Users Training

ICAO NAM-CAR-SAM Regions

Santo Domingo, 26th - 27th November 2009

Jean-Marc Vacher, EUROCONTROL

[email protected]

1. Introduction

Chapter 1

Introduction

2

1.1 Course Objective

1. Explain how the AMHS address management procedures

promulgated by ICAO State Letter 09-34 can be performed

using AMC

2. Provide a general view of the AMC application to enable

participants to become efficient AMC users and take benefit of

AMC functions

3. Pre-requisite: provide background AMHS information for

proper understanding of AMC functions

3

1.2 Contents

1. Introduction

2. Background AMHS information3. Overall framework for ATS Messaging Management

4. Technical and practical overview

4

5. Data organization and user interface

6. Overview of operational functions and procedures (AMF-O)

7. Network inventory

8. Addr ess man agement (incl udin g rel ation to ICAO HQ)

9. Routing management

10. Miscellaneous functions

11. Overview of implementation support functions (AMF-I)

12. Questions and answers

APNDICE B CA/ANE/WG/05 NE/25

8/13/2019 CAANEWG05NE25

17/58

2

1.4AMC concept - History

Dec 2001: Start of CIDIN Management Centre (CMC) operation

Dec 2003: ICAO EANPG Conclusion 45/10:

th at Eurocontrol be invited to consider extending the CIDIN Management

Service to provide ATSMHS off-line network management

Sept 2004-May 2005: Study o f AMHS Off-line Management

5

ATS Messag ing Managem ent Man ual (ap pro ved b y AFSG/8 ICAO Paris )

Sept 2005: Eurocontrol DG decision to implement ATS Messaging Management

Centre (AMC)

Oct 2005-Nov 2006: Implementation of the AMC

19th Jan 2007: Start of AMC operational service

Apr il 2007: Ado pti on o f ATS Mess agin g Manag ement Manual Versi on 3.0

as EUR ICAO DOC 021

1.5AMC concept ICAO State Letter

EANPG Conclusions:

Conclusion 49/23 AMHS Address Coordination

That ICAO be invited to utilize the European AMC facility at the earliest opportunity []

Conclusion 49/24 AMHS Messaging Management Centre Users

That ICAO be invited to address States outside the ICAO EUR Region to register with the

AMC] as external COM centre operators, as soon as possible.

6

ICAO State Letter 09-34 (dated 14th April 2009, a response to the EANPG conclusions above):

In the short- to medium-term, ICAO will utilize the European ATS Messaging Management

Centre (AMC), provided by EUROCONTROL, to coordinate the allocation and management

of AMHS addresses.

All States are therefore invited to designate representatives to register as AMC users [].

All States and/or ANSPs, operating international COM Centres, with the intention of

implementing AMHS in the foreseeable future, should engage themselves into the AMHS

address coordination process without delay.

1.6AMC concept - Scope and Objectives

Deliver Off-Line Network Management Services in support of

the ATS Messaging part of the AFS:

the int egrated AFTN / CIDIN / AMHS network

Support to States with AMHS in operation

AMHS Managem ent Fu nct ion s Operat ion al Sup por t (AMF-O)

7

Support to States on their way to implement AMHS

AMHS Managem ent Fu nct ion s Impl ement atio n Sup por t (AMF-I)

Provide the service in a single focal point for AFTN, CIDIN, AMHS

For EUR/NAT Regions

Als o pr ovi de ser vic e to o ther Regio ns, w ith a pri ori ty o n add ress

management

Service provided on a co-operative basis (not chargeable)

2. Background AMHS Information

Chapter 2

Back round AMHS Information

8

CA/ANE/WG/05 - NE/25

8/13/2019 CAANEWG05NE25

18/58

8/13/2019 CAANEWG05NE25

19/58

4

2.1.4 The messages transferred by AMHS

Those specified in Annex 10 and ICAO Document 4444

(contd):

Aeronautical information service (AIS) messages, e.g. NOTAMs

and SNOWTAMs;

13

Service messages.

The most frequent categories:

Flight plans

AIS

MET

2.1.5AMHS connectivity requirements

Evolution from AFTN/CIDIN:

AFTN user

AMHS user

AFTN user

14

AFTN/CIDINInfrastructure

AFTN/CIDIN

AMHS user

ATN / AMHS

2.1.6 The functionalities offered by AMHS

Offer a service functionally close to that of AFTN:The Basic ATS Message Handling Service (Basic Service)

This additionally includes:No limit on the number of message destinations

Capability to transfer messages larger than AFTN (no theoretical size limit)

15

ore ex ty on a ress ng

Offer an enhanced service with additional functionalities:The Extended ATS Message Handling Service (Extended Service)

This may include:

Capability to transfer messages containing binary dataSecurity by means of digital signatures

2.2AMHS Technical Overview

Section 2.2:

AMHS components

AMHS protocols

16

messages


8/13/2019 CAANEWG05NE25

20/58

5

2.2.1AMHS components

MTAMTA = MMessage TTransfer AAgent

Message switch

UAUA = UUser AAgent

User access to the MTA

Only protocols are standardized, not the HMI

MSMS = MMessage SStore

Intermediate storage between MTA and UA upon reception

(message database)

Generally co-located with MTA

AUAU = AAccess UUnit

Conversion towards other messaging systems17

2.2.2AMHS component mapping

AFTN MHS/X.400 AMHS

AFTN Centre MTA ATS Message

Server

AFTN Station UA ATS Message User

Agent

AU (+ MTA) AFTN/AMHS

Gateway

18

2.2.3 MHS systems and components

Other

UAP3

PMTAP2

P2

messagingsystem

(e.g. AFTN)

MHS

MTS

P1 1P

1MTA

MTAUA

MSP7

UA

MTA

MS

AUAU

MTS = Message Transfer System

MHS = Message Handling System19

2.2.4AMHS systems and components

Other

UA

MTA

ATS Message

Server

ATS Message

User Agent

AFTN/AMHS

Gateway

messagingsystem

(e.g. AFTN)

MHS

MTA

MTAUA

MS

UA

MTA

MS

AU

AMHS = ATS Message Hand lin g Syst em

ATS Message

Server

AU

20


8/13/2019 CAANEWG05NE25

21/58

6

2.2.5AMHS protocols (1)

format

P2 (Inter-Personal Message or IPM)

Operation with out MS (Message Store)

rotocols

Submission Transfer Delivery

UA UA

P1P3 P3MTA MTA

operations

21

2.2.6AMHS protocols (2)

Operation wit h MS (Message Store)

format

P2 (Inter-Personal Message or IPM)

rotocols

Submission Transfer Delivery

UA UA

P1P3 P7

operations

MTA MTA MS

Retrieval

22

2.2.7AMHS messages

CONTENT (P2)

MESSAGE

HeaderFrom :

To :

Subject :

BodyThis is the text

which I want tosend you etc.

23

2.2.8AMHS messages, probes and reports

P1 Information Objects :

Message = Message with envelope and contents

Contents = P2 Information Object :

IPM = Inter-Personal Message (a true message)

IPN = Inter-Personal Notification - To inform the message originator

Probe = Message without contents (envelope only)

Report = To inform the message originator about the outcome of the communication :

Delivery Report

Non-Delivery Report

about the message reception (reading) :

Receipt Notification (RN in case of reading)

Non-Receipt Notification (NRN in case of message not read)

24


8/13/2019 CAANEWG05NE25

22/58

7

2.3AMHS Organisation and addressing

Section 2.3:

AMHS organisation

AMHS addressing

25

rou ng

2.3.1 X.400 Management Domains

Management Domain:An organisational entity which manages at least one MTA (or several), and

which is responsible for the users connected to its MTA(s)

Notions defined in the base standards:

A Management Domain can be : an ADMD (Administrative Management Domain), usually managed by

a public telecom operator or an international organisation.

a PRMD (Private Management Domain), usually managed by a

company or governmental body. PRMDs are operated under or

within an ADMD

26

2.3.2AMHS Management Domains

ICAO is considered as an Administrative ManagementDomain (ADMD)However this ADMD is virtual and does not manage any MTA, it is definedfor organisational reasons only.

em er a es an recogn se rgan sa onsoperate as PRMDs under the ICAO ADMD There is usually one AMHS MD per State/ANSP.

For organisational and technical reasons, PRMDs are defined for allICAO Member States worldwide. However a State PRMD becomesreal when AMHS is implemented in that State.

State PRMDs are directly interconnected between themselves

27

2.3.3AMHS network organisation

PRMD1

UA

MTA

MS

PRMD2

UA

PRMD3

MTA MTA

PRMD4

State AState A

State BState B

UAUA

State CState C28


8/13/2019 CAANEWG05NE25

23/58

8

2.3.4AMHS addressing for MDs

X.400 and AMHS addressing is hierarchical. An address is an orderedcombination of attributes which all have a specified syntax

An address is usually represented (but not encoded) by a sequencesuch as:attribute1 initials = value1, attribute2 initials = value2, etc.

Each Management Domain is uniquely identified at a global level by3 standard attributes (together known also as GDI):

Country-name (C) for AMHS: C=XX ( International Organisation)

ADMD-name (A) for AMHS: A=ICAO

PRMD-name (P)

Example for AMHS: C=XX, A=ICAO, P=SAUDI ARABIA29

2.3.5AMHS addressing for users

Each user (UA) is identified within the MD by a full O/R Address including additional

attributes among the following:

organisation-name (O)

organisational-units-name (4 values) (OU1 to OU4)

personal-name (surname, given-name, initial) (S, G, I)

common-name (CN)

domain-defined attributes (4 values) (DDA1 to DDA4)

This gives a lot of flexibility and possibilities

Such flexibility needs to be controlled (select/specify the used attributes)

AMHS Addressing Schemes are defined for this purpose:

CAAS (Common AMHS Addressing Scheme)

XF (Translated form)

30

2.3.6AMHS Addressing Schemes

XF Addressing Scheme

Attrib ute Name of attri buteAssign ed

by

Registered

byValue Comment Value

C Country-name ITU-T ITU-T 'XX'According to ITU-T

Recommendation X.666'XX'

A ADMD-name ICAO ITU-T 'ICAO'As agreed b y ICAO and

ITU-T'ICAO'

ITo be defined by each To be defined by each

High level address attributes:

CAAS Addressing Scheme

31

- IANSP ANSP

O O rg anis atio n name ANSP ICAO

e.g. a "region" within a

country, to be defined

by each ANSP

Representing local/

national geographical

information

'AFTN'

OU1Organisational unit

name 1ANSP ICAO

4-character ICAO

location indicator

As spec ified in ICAO

Doc 7910

8-character AFTN address

CN Common name ANSP8-character AFTN

addressnot used

Low level address attributes

Other addressing schemes are possible (but discouraged),

using additional attributes: OUn, S, G, DDAn etc.

If implemented they need to be known and registered.

2.3.7AMHS Addressing Attributes

Name Graphics

Capital letters A, B, ... Z

Small letters a, b, ... z

Digits 0, 1, ... 9

PRMD-name (16 characters max.) and Organisation-name (64 characters max.) must use

the following character set and should be as short as possible.

Name Graphics

Capital letters A, B, ... Z

Digits (if needed) 0, 1, ... 9

Hyphen -

Technica ll y authorised character se t Suggested prefer red character se t

32

Space (space)

Apostrophe '

Left Parenthesis (

Right Parenthesis )

Plus sign +

Comma ,

Hyphen -

Full stop .

Solidus /

Colon :

Equal sign =

Question mark ?


8/13/2019 CAANEWG05NE25

24/58

9

2.3.8AMHS Addressing Examples

Example of CAAS Addresses: Spain, multiple MTAs, multiple O values

C=XX / A=ICAO / P=AENA / O=LECB / OU1 = LEVC / CN = LEVCZPZX(Aeronautical Reporting Office in Valencia Airport)

C=XX / A=ICAO / P=AENA / O=GCCC / OU1 = GCRR / CN=GCRRZTZX(Tower in Lanzarote Island Airport)

Example of CAAS Address: Switzerland, one MTA, single O value

C=XX / A=ICAO / P=SUISSE / O=LS / OU1 = LSAG / CN = LSAGZTZX(Tower in Geneva Airport)

Example of XF Address: United Kingdom

C=XX / A=ICAO / P=EG / O=AFTN / OU1 = EGGGYFYX(U.K. COM Centre)

33

2.3.9AMHS Routing

AMHS (or X.400) routing is performed in MTAs

It is based on address attributes:

For a given combination of attribute values, a route to a next hop MTA is

.

accordingly.

The following address attributes are used:

C, A, P and sometimes O for routing to another domain (inter-domain routing)

Other address attributes within the domain (intra-domain routing)

Routing uses best match algorithms according to the number of matching

attributes

Routing does not use match based on partial character combinations

(only whole attribute values, unlike AFTN)

34

2.3.10 Example of AMHS Routing Table

N Country ADMD PRMD O MTA

1 XX ICAO CFMU CFMUH CFMU-HAREN

2 XX ICAO CFMU CFMUB CFMU-BRETIGNY

3 XX ICAO France LFFF MTA-Athis

4 XX ICAO France LFEE MTA-Reims

5 XX ICAO France LFBB MTA-Bordeaux(national)

intra-

6 XX ICAO France LFMM MTA-Marseille

7 XX ICAO France LFRR MTA-Brest

8 XX ICAO Germany MTA-DFS

9 XX ICAO LI MTA-ENAV

10 XX ICAO DT MTA-ENAV

11 XX ICAO LA MTA-ENAV

12 XX ICAO LM MTA-ENAV

13 XX ICAO LT MTA-ENAV

14 XX ICAO *(1) Gateway(2)

domain

routing

(interna-

tional)

inter-

domainrouting

35

2.4AMHS Systems and Network

Section 2.4:

ATS Message Server

ATS Message User Agent

36

a eway

AMHS and lower layer networks


8/13/2019 CAANEWG05NE25

25/58

10

2.4.1ATS Message Server

The main functions of an ATS Message Server (MTA) are:

Message routing

Intermediate storage before message forwarding

Reliable transfer towards other ATS Message Servers

Management of local users connections, submissions and deliveries

Report generation (DR and NDR)

Management of local distribution lists

Traffic logging

This is done by:

Encoding and decoding envelopes to determine actions to be performed

Managing upper layer protocols (and primarily P1, P3 for local users)

37

2.4.2ATS Message User Agent

The main functions of an ATS Message User Agent ( UA) are:

Analyse contents and envelopes of received messages to give them to theuser HMI

Submit messages entered by the user through the HMI

Manage the connection to the MTA

In P7 mode, create and send queries enabling to use the MS services

enerate an sen w en necessary

This is done by:

Managing P3 and P7 protocols in order to : Submit, receive and retrieve messages

Query and manage the MS

Encoding and decoding of P3 and P7 operations and message envelopes

Encoding and decoding of P2 contents

38

2.4.3AFTN/AMHS Gateway Overview

AFTN procedureMTA

" "

P1 protocol stack

to oth er ATS Message Servers

or AFTN/AMHS Gateways

normal flowof messages

message transfer and control unit (AU)

component")

handler ("AFTN

access to

AFTN

ATN transport serviceOr TP0 emulationusing RFC1006 over TCP

access to

ATN/IPS or OSI subnetwork

39

2.4.4AFTN/AMHS Gateway Functions

management of AFTN procedure

AFTN ITA-2 to/from IA-5 conversion

if needed traffic logging

conversion of AFTN messages (and of certain servicemessages) to/from AMHS messages and reports

rejection of AMHS messages which cannot be conveyed overthe AFTN

address mapping : conversion of AFTN addresseeindicators t o/from AMHS O/R addresses

full MHS/X.400 support by ATN Component

The Gateway combines UA and MTA functionalities

40


8/13/2019 CAANEWG05NE25

26/58

11

2.4.5AFTN/AMHS Gateway Message Conversion

MESSAGE COMING

FROM AFTN -O/R Addresses (orig.+dest.)- transmission priority P1

MESSAGE CONVERTED

IN THE AMHS

ZCZC BAC002 Other P1 envelope elementsare generated by the MTCU

PRI : FF

FT: 011030

THIS IS THE MESSAGE

TEXT

-O/R Address- Receipt Notification

request if SSP2

LFPOYIYA

011030

THIS IS THE MESSAGE

LFPSYHYX

NNNN

TEXT

FF

41

2.4.6AMHS and Underlying Network Options

Two options : ATN/IPS (TCP/IP) and ATN/OSI

The choice is related to layers 3 and 4 only

Both options may co-exist globally while preserving end-to-end

AMHS interworking

snge c oce or eac egon s ou e pre erre

At present, all Regions, except Asia/Pacific, are targeting an

ATN/IPS lower layer network infrastructure

42

2.4.7AMHS and Lower Layers

7 Application

MTA

AMHS System = End syst em (host)

7 Application

MTA

AMHS System = End syst em (host)

AMHS exchang es at app licati on l ayer (P1)

Upper

layers

6 Presentation

5 Session

4 Transport

3 Network

2 Data link

1 Physical

Router (IP or OSI/CLNP) =

Intermediate System

3 Network

2 Data link

1 Physical

Router

3 Network

2 Data link

1 Physical

6 Present.

5 Session

4 Transport

3 Network

2 Data link

1 Physical

Exchanges at

network layer

Lower

layers

43

2.4.8AMHS and Lower LayersStore-and-forward AMHS operation

AMHS Exchang esat application layer (P1)

7 A

MTA

AMHS Syst em = End syst em (hos t)

UL

7 A

MTA

AMHS Syst em = End syst em (hos t)

7 A

MTA

6 P

5 S

4 T

3 N

2 DL

1 Ph

LLRouters

3 N

2 DL

1 Ph

3 N

2 DL

1 Ph

6 P

5 S

4 T

3 N

2 DL

1 Ph

6 P

5 S

4 T

3 N

2 DL

1 Ph

Router

3 N

2 DL

1 Ph

44


8/13/2019 CAANEWG05NE25

27/58

8/13/2019 CAANEWG05NE25

28/58

13

3.1.1 Nature of Network Management

Technical scope:

In our context ATS Messaging Management covers:

AFTN, CIDIN, AMHS

Functional scope:

FCAPS model:

49

fault, configuration, accounting, performance, security

Other models:

inventory, change control, help desk, etc.

Real-time / Short-term / Long-term

Centralised / Local:

In our context each COM Centre is managed nationally, i.e.

locally

3.1.2 Need for coordination

Local management does not mean independent one from

each other. Coordination is required, e.g. for:

50

Sharing of common network-related data

Synchronisation of changes in the network

3.1.3 Off-line Network Management

51

3.2.1AMC Participants

AMC Operator

CCC (Co-operating COM Centre) Operators

External COM Centre Operators

AMF-I Users AMC Users

52

Read-Only Users

Operators without formal responsibility

People overseeing activity

Participating COM Centres

How to be in one of these categories ?

Use accreditation procedures in the Manual


8/13/2019 CAANEWG05NE25

29/58

14

3.2.2 Main focus for AMC Participantsin an AMHS Project

AMF-I User

53

CCC Operator

Ext COM Operator

Read-only users

AMF-I Users, CCC Operators and Ext. COM Operators are officially representing their COM Centre and/or ANSP Read-only users have no formal responsibility and may be not directly involved in an AMHS project

3.2.3ATS Messaging Management Area

EUR/NAT Regions

Co-ordinatingCOM Centres

(CCC)

External

COM Centres

AMHS MD1

Other Regions

(e.g. ASIA/PAC)

54

Participating

COM Centres

AMHS MD2AMHS MDs

3.2.4 Organisation

ICAO State

EANPG / AFSG

If in EUR / NAT,

is represented in

Reports to Mandates

55

Other AMC usersCCC Operators

Ext. COM Operators

ATS Messaging Management Centre

Operations Group

Reports to Monitors

and guides

Perform operational

procedures

Interact

informally

to to

3.2.5 Organisation:

AMC Participants and access to functions

AMC

functionsParticipantcategories

AMF-I func tion sAMF-O

functions

AMC

Operatorfunctions

AMF-I users yes some

CCCoperators yes yes

56

External COMoperators

yes All but routingand statistics

Read/only users some some

AMC Operator s yes yes yes

+ AMC Support Group: AMC Project Leader(Eu roco nt rol ) syst em i nf rast ru ct ur e op er at or s

AMCusers

A task p erfor med by a grou p of ANSP/COM Cent re repr esentati vesunder contract by Eurocontrol


8/13/2019 CAANEWG05NE25

30/58

15

4.ATS Messaging Management

Chapter 4

Technical and Practical Overview

57

4.1.1A Database Application

AMC User s

58

AMC Syst ems

Database objects

User interfacesData processing

AMC SystemsAMC Systems

AMC Support Gr oupAMC Support Gr oup

EUROCONTROLEUROCONTROL

AMC OperatorsAMC Operators

4.1.2AMC Participants and systems

59

CCC OperatorsCCC Operators

Internet

External COMExternal COM

OperatorsOperatorsAMFAMF--I UsersI Users Read/Only UsersRead/Only Users

4.2.1 How to become an AMC User ?

Use procedure described inATTACHMENT B to ICAO State

letter AN 7/49.1-09/34 :

Fill in the electronic form provided at:

https://extranet.eurocontrol.int/http:/chow.mis.eurocontrol.be:8095/elsh

live/elsh/re isterNewUserForA lication.do?eurocontrolresourceid=a

60

_ .

mc_users

The accreditation procedure is then started

(see ATS Messaging Management Manual section 2.5.2)

Follow AMC training


8/13/2019 CAANEWG05NE25

31/58

16

4.2.2 How to enter the AMC application ?

Various entry points:

www.eurocontrol.int/amc/

www.paris.icao.int

61

4.2.3 How to enter the AMC application ?(directly to Eurocontrol)

62

Select Enter AMC

4.2.4 How to enter the AMC application ?

63

Enter login

and password

4.2.5 How to enter the AMC application ?(via ICAO)

2. Select Continue to AMC

64

1. Select AMC


8/13/2019 CAANEWG05NE25

32/58

17

5.ATS Messaging Management

Chapter 5

Data Or anization and User Interface

65

5.1.1AMHS Management Domainsand COM Centres in AMC

AMHS MD formally identified by: country-name, ADMD-name,

PRMD-name

identified in short by: MD common name

(generally = PRMD-name) the notion is LOCAL to AMC

contains AMHS MD-related data

is associated to

is associated to

one or several

66

(e.g. addressing scheme)

COM Centre

COM Centre

formally identified by its Location Indicator

contains COM Centre-related data

(e.g. routing tables)(one or several)

Region

Region

is located in one

5.1.2 Relation to ICAO Regions

A common data structure for the description of:

All AMHS MDs world wide

All COM Centres world wide

67

External COM Centres (and other COM Centres outside

EUR/NAT) include no data for these Centres

Regions are taken into account in two different ways:

Using the single COM Centre / Region association in the Search criteria To graphically represent the geographical network organisation, using

Regional COM Charts

5.2.1 Menu and Window Structure

Menu(functions)

Main

window

68

Sub-functions(tabs)


8/13/2019 CAANEWG05NE25

33/58

18

5.2.2 Interface Conventions

Common lay-out

Help

Input fields

Disabled buttons

69

Scroll bars

Waiting after an operation

Maintaining context

Association mechanism

Sorting of columns in RESULTS tables

Record history information

5.2.3 Main Window and Pop-up Structure

70

detailed information

about

selected record

5.2.4 Screen areas of main window

SEARCH area

RESULTS area

71

DETAILS area

ACTIONS

area

5.2.5 Management of Access Rights

at menu level:

not the same groups of functions are visible for each category

72

at window level:

sub-functions can be hidden depending on user category

buttons are enabled / disabled

data are enabled / disabled


8/13/2019 CAANEWG05NE25

34/58

19

5.3.1 Example: Regions function

A function for the description of ICAO Regions and Regional Offices:

Details: Regional Office

Results:

Regional Persons and Contacts

73

Data modification by AMC Operator only

Other users have read access

All users have:

a standard REPORT button

A specific VIEW COM CHART button

5.3.2 Example: Regions function

74

Demonstration

6. Overview of AMF-O Functions and

Procedures

Chapter 6

75

Overview of Operational Functions (AMF-O) and Procedures

6.1.1 List of AMF-O Functions

Network Inventory

Routing Directory

Address Management

76

Statistics

Static Report

COM Charts


8/13/2019 CAANEWG05NE25

35/58

20

6.2.1 Common Aspects of AMF-O Functions

Information is structured in three data areas:

the Operational Data Area

the Pre-Operational Data Area

77

the Background Data Area

Specific functions (different menu items) enable to accesseach area with a given purpose

6.2.2 Background Data Area

purpose working area (CCC, External COM

Centre and AMC Operators)

access restricted to own COM Centre (except

for AMC Operator)

78

AMC Operator actions validating Inventory, work on RoutingTables

functions data entry and validation

6.2.3 Pre-operational Data Area

purpose represent planned operational state

access read (all), routing acknowledgement

restricted

79

AMC Operator actions transfers COM centre information,

propose Routing Tables

functions retrieval, all functions,

routing acknowledgement

6.2.4 Operational Data Area

purpose represent operational state

access read (all)

80

AMC Operator actions copied as whole from Pre-operational

functions retrieval, all functions


8/13/2019 CAANEWG05NE25

36/58

21

6.2.5 Relation between Areas

readall

readall

acknowledge

readown

writeown

CCC

Operator

81

OperationalArea

Pre-operational

Area

readall

readall

writestatus

BackgroundArea

readall

writeall

transfercomplete

area

transfercomplete

area

AMCOperator

6.3.1 General View of Procedures

AMF-O functions are governed by procedures

Although formulated a bit differently,

they are aligned on formerly existing CIDIN Management

82

that area

6.3.2 The AIRAC Cycle

1 2 13 15 16 227 2728

AIRAC Date

28

AIRAC Date

83

cycle n-1 cycle n+1cycle n

6.3.3 The Procedure Cycle

D at a En tr y D at a V a li da ti on a ndProcessing

ACK Phase ACK Processing DataRetrievalandImplementation

(byCCC)

by CCC /

Ext COM / AMC by AMC by CCC by AMCDataPublication

(byAMC)

12

3

45

6

78

9

1

Day inCycle

General View

84

1011

12

1314

15

1617

18

19

2021

22

2324

25

26

2728

LEGEND AMC Operator locks AMC Operator releases therouting matrix

COMCentres

AMC Operator transfers AMC Operator moves datato

t o pr e- op er at io na l ar ea o pe ra ti on al ar ea , u nl oc ks CO M Ce nt re s

and makes officialpublications;

Weekends CCC Operators use new data

for operationalservice


8/13/2019 CAANEWG05NE25

37/58

22

6.3.4 Relation between Data Areas and Procedures

Use of BackgroundData Area

Use of Pre-operationalData Area

Use of OperationalData Area

initial data entryphase data entry investigate validated data

access currentoperational data

creation of newRoutingMatrix

investigate andacknowledgeRouting

access currentoperationaldata

85

phase Matrices

implementation ofnew Routing Matrix

phase

access currentoperational data

6.3.5 View AIRAC Cycles in AMC

A miscellaneous function:

View AIRAC Cycle

View AIRAC Dates

86

Demonstration

7. Network Inventory

Chapter 7

87

Network Inventory

7.1.1 Network InventoryPurpose

support of Routing

88

Persons and Contacts

COM Centre Info and Capabilities

(CIDIN VCGs)

Connections

Update


8/13/2019 CAANEWG05NE25

38/58

23

7.1.2 Inventory Update Interactions

CCC Operator /

Ext COM Operator

enters data

System informs

AMC Operator

CCC / Ext COM

and AMC Operator

coordination

89

CCC Operator /

Ext COM Operator

inspects data

AMC Operator

locks data

i i

AMC Operator

validates data

7.1.3 The Sub-functions of Network Inventory

Persons and Contacts

COM Centres

AFTN/CIDIN Capabilities

AMHS Capabilities

90

VCGs

Connections

7.1.4 Network Inventory: objectives

Persons and Contacts:operational contact points in COM Centres

COM Centres:general information (address)applications (AFTN, CIDIN, AMHS, others)

AFTN/CIDIN Capabilities:

91

details of AFTN and CIDIN configuration and capabilities

AMHS Capabilities:details of AMHS configuration and capabilities

VCGs:list of CIDIN VCGs with adjacent COM Centres

Connections:

list of all connections of all types with other COM Centres(network topology)

7.2.1AMHS Capabilities Data Fields

Field Comments Values

ATS Message S erver Derived from "applications" s elected in the COM Centres

function (not modifiable)

If unticked the whole frame is disabled.

a checkbox:

ticked = present and active

unticked = not present or not active

MTA-name The X.400 MTA-name used to declare an associat ion, to use

in trace-information, etc.

recommendation in EUR AMHS Manual :

'MTA-" followed with LI (4 letters) followed by "-

" and a sequence number

Maximum Content

Length

Maximum length (in bytes) of messages that the MTA is

capable to accept, transfer and deliver


should be at least 2 Mbytes

Message Lifetime Duration during which the MTA will try to transfer before to be coordinated regionally. Under discussion

ATS Message Server frame

92

Extended Encoded

Information Types

(EITs) in support of

Message Encodings that the MTA is capable to transfer to

accept, transfer and deliver

one checkbox (ticked = yes, unticked = no)

for each body part / encoding combination

specified in Doc 9705

AFTN/AMHS

Gateway

Derived from "applications" selected in the COM Centres


If unticked the whole frame is disabled.

a checkbox:

ticked = present and active

unticked = not present or not active

Currently Authorized

Content Length

Maximum length (in bytes) of messages that the gateway will

accept to convert to AFTN


should be at least 2 Mbytes

Maximum Number of

Recipients

The maximum number of recipients O/R addresses allowed in

a message converted by the gateway. Messages with more

recipients are rejected.

Doc 9705 requirement is 512 recipients

Converted General-

Text Body Parts

General-text body parts that the gateway is capable to convert

to AFTN

one checkbox (ticked = yes, unticked = no)

for each body part character set specified in

Doc 9705 (ISO 646 or ISO 8859-1)

Operational Status Coming from the AMHS MD Register function (not modifiable) 'op', 'non-op', 'unknown'

AFTN/AMHS Gateway frame


8/13/2019 CAANEWG05NE25

39/58

24

7.2.2 Protocol Capabilities

The table shows the protocol stacks available for international

AMHS connectivity

Each stack includes application layer (P1 between MTAs),

presentation, session and lower layers

Several instances of the same stack can be present

93

The table is managed as one parameter of the Com Centre:

enabled for modification or creation only when MODIFY is clicked

after entering data, UPDATE in pop-up and SUBMIT in main window

7.2.3 Protocol Capabilities Data Fields


Protoc ol Support ed AMHS protoc ol s for COM

Centre to COM Centre communication.

There can be various protocol stacks

'AMHS/TCP-IP'

'AMHS/ATN-TP4'

'AMHS/TP0-X.25'

P -SEL Pres entat ion s elec tor f or O SIUpper L ay er as signed b y C OM C ent re

Data fields = the parameters which a r emote MTA needs to correctly configure an association:

94

I

stack. A characteristic of the MTA-to-MTA 4 characters maximum

S-SEL Session se lector fo r OSI Upper Layer stack ass igned by COM Centre

16 characters maximum

T-S EL Transport select or for OS I Upper Lay er

stack

assigned by COM Centre

32 characters maximum

Network Address

(NSAP or IP)

The IP address or ATN NSAP allocated to

the considered protocol stack in the MTA.

assigned by COM Centre

Active indicates the current operational status of

the protocol stack

a checkbox:

ticked = active

unticked = present but not

yet active

7.2.4 Connections

need to represent the network topology at messaging level

in summary three main connection categories:

AFTN circuits (conventional or X.25)

CIDIN (PVC or SVC)

AMHS connections

=

95

.

over a lower layer network infrastructure

two tables:

Existing connections

Planned Connections includes Events (creation, modification, etc.)

existing connections form the basis for:

routing tables COM Charts

ANP FASID Report produced by EANPG/AFSG for ICAO

7.2.5 Connections Data Fields


R em ot e C OM Th e " ot he r e nd " o f t he co nn ec tio n a CO M Ce nt re lo ca ti on ind ic at or

described in the AMC (4 letters)

P rot oc ol prot oc ol us ed over t he c onnec tion c an be an AMHS prot ocol s tac k,

'CIDIN PVC' or 'CIDIN SVC',

'Conv. AF TN' or 'AFTN/X.25', etc .

Network Address The network address of the REMOTECom

Centre used for the connection

entered using the remote Centre's

inventory information

Link Type an indication of the physical connectivity used free text, can be the name of the

96

or t e connect on operat ona ower ayers networ

(e.g. REDAN+RAPNET, CFMU,

etc.)

Capac it y the c apac it y of the l ink or c irc ui t (i f f ix ed end- to -

end) or of the network access

value in kbits/s

Circuit type (in pop-

up window only)

the type of circuit supporting the connection,

based on a standard ICAO classification

'L' (Landline), 'M' (Multiplexer), 'N'

(Network), 'R' (Radio), 'S' (Satellite)

S uppl ie r an i nd ic at ion o f t he supp li er o f phy si ca l

connectivity used for the connection

free text, can be a generic name

such as 'telco', or specific 'SITA',

'PENS', etc.

Active indicates the current operational status of theconnection a checkbox:ticked = active

unticked = present but not yet active

(should not happen in "existing

connections")


8/13/2019 CAANEWG05NE25

40/58

25

7.2.6 Network Inventory

97

Demonstration

8.Address Management

Chapter 8

98

Address Management

8.1.1 The Need for Address Management (1)Recipient-Name:C=XX/A=ICAO/P=FA/

O=AFTN/OU1=FAJSYMYX

Originator-Name:

C=XX/A=ICAO/P=SA/

O=SAEZ/OU1=SAEZ/ CN=SAEZYMYX

[]

TAF

99

GG FAJSYMYX

180516 SAEZYMYX

[]

TAF

8.1.2 The Need for Address Management (2)

Recipient-Name:

C=XX/A=ICAO/P=FA/

O=AFTN/OU1=FAJSYMYX

Originator-Name:

100

GG FAJSYMYX

180516 SAEZYMYX

[]

TAF

C=XX/A=ICAO/P=SA/


[]

TAF


8/13/2019 CAANEWG05NE25

41/58

26


in any network, the knowledge of originator and recipient addresses ismandatory to enable the exchange of information

at present there is not yet an official source for AMHS addressing

AMHS Address Management is required because:

101

information: the global ICAO Register of AMHS MDs and addressing information is being i mplemented

by ICAO Headquarters

it is not the role of ICAO HQ to maintain an operational Register subject to the (potentially)frequent changes of a dynamic network under deployment

The ICAO Register is intended to be used for institutional purposes, not for operationalpurposes

There is a need for an operational source of information regarding AMHSaddressing


All addresses are converted at the boundary between CIDIN/AFTN and AMHS.

This means thatANYAFTN address in an AFTN message reaching an

AFTN/AMHS gateway is converted to an AMHS address:

even if the address is in another Region

Address management handles information for AMHS world wide

even if the considered State has not migrated to AMHS

102

Address management is not affected by new implementations (in principle)

The use of wrong AMHS addresses may cause mis-routings and non-deliveries.

Lack of synchronisation in changes introduces wrong addresses.

AFTN and CIDIN addresses are well-known and rather static. At least during the

deployment phase, AMHS addresses are expected to be modified more

dynamically.

8.2.1 Two Aspects in Address Management

CAAS XF

Attrib ute Name of attribute Value Value

C Country-name

A ADMD-name

High level address attributes:

'XX'

'ICAO'AMHS MD Register

103

P PRMD-name

CAAS XF

O Org anis atio n name

e.g. a "region" within a

country, to be de fined by

each ANSP

'AFTN'

OU1

Organisational unit

name 1

4-character ICAO location

indicator

8-character AFTN address

CN Common name8-character AFTN

addressnot used

Low level address attributes

To be defined by each ANSP

Addressing scheme:

Intra-MD

Addressing

Other addressing schemes or addresses using additional attributes

8.2.2 Use of AMHS address information

Routing

In every AMHS MTA

Between AMHS Management Domains (MDs):

Using high-level attributes (C, A, P)

AMHS address information is used for two different aspects:

104

-

Internally to the destination AMHS MD:

Using low-level attributes (O, OU1, CN)

Addressing conversion In AFTN/AMHS Gateways

Upon entry and exit of AMHS:

Using the full address (all attributes of a CAAS or XF address)

Using Nationality Letters (or Designator) associated with the AMHS MD


8/13/2019 CAANEWG05NE25

42/58

27

8.2.3 Use of AMHS address informationexample 1: address conversion in AFTN/AMHS gateway

State AMHS Address Specification

Name

Nationality

Let ters or

Designator

Country-

name

attribute

ADMD-

name

attribute

PRMD-name

attribute

Addr ess ing

scheme

ATN

Directory

naming-

context Com m ents

Solomon Islands AG XX ICAO AG XF

Cte d'Ivoire DI XX ICAO DI XF

Nigeria DN XX ICAO DN XF

Niger DR XX ICAO DR XF

Tunisia DT XX ICAO DT XF

Togo DX XX ICAO DX XF

105

Belgium EB X ICAO BELGIUM CAAS see Table Belgium

Eurocontrol EBBD XX ICAO CFMU CAAS see Table Eurocontrol-CFMU

Germany ED XX ICAO GERMANY CAAS see Table Germany

Estonia EE XX ICAO EE XF

Finland EF XX ICAO EF XF

United Kingdom EG XX ICAO EG XF

Netherlands EH XX ICAO EH CAAS see Table EH

Convert EFHKZTZX :

1) Extract EF, EFHK, EFZTZ, EFHKZTZ

2) Look for best match in Nationality Letters col umn: EF

3) Retrieve MD-name: C=XX, A=ICAO, P=EF

4) Retrieve addressing scheme: XF5) Construct XF-address: C=XX, A=ICAO, P=EF, O=AFTN, OU=EFHKZTZX

8.2.4 Use of AMHS address informationexample 2: address conversion (CAAS)

State AMHS Address Specification

Name

Nationality

Let ters or

Designator

Country-

name

attribute

ADMD-

name

attribute

PRMD-name

attribute

Addr ess ing

scheme

ATN

Directory

naming-

context Com m ents

United Kingdom EG XX ICAO EG XF

Netherlands EH XX ICAO EH CAAS see Table EH

Dem. Republic of the Congo FZ XX ICAO FZ XF

Mali GA XX ICAO GA XF

Gambia GB XX ICAO GB XF

Canary Islands (Spain) GC XX ICAO AENA CAAS see Table Aena

Spain GE XX ICAO AENA CAAS see Table Aena

Location

Indicator/

Organisation

Unit

Region/

Organisation

OU1 O

106

Convert GCRRZPZX (Lanzarote) :

1) Extract GC, GCRR, GCZPZ, GCRRZPZ

2) Look for best match in Nationality Letters column: GC

3) Retrieve MD-name: C=XX, A=ICAO, P=AENA

4) Retrieve addressing scheme: CAAS

7) Construct CAAS address:C=XX, A=ICAO, P=AENA, O=GCCC, OU=GCRR, CN=GCRRZPZX

Sierra Leone GF XX ICAO GF XF

Guinee-Bissau GG XX ICAO GG XF

GCLB GCCC

GCLP GCCC

GCMP GCCC

GCRR GCCC

GCTS GCCC

GCXO GCCC

LEAB LECB

LEAL LECB

LEAP LECB

LEAT LECB

LEBL LECB

LEBN LECB

5) Extract location indicator (GCRR) and look for a match in detailed table Aena

6) Retrieve Organisation-name from column Organisation: GCCC

8.3.1 Two categories of address changes

Major changes: They include:

Addition or deletion of PRMDs

Modification of PRMD-name

Chan e of addressin scheme from XF to CAAS or vice-versa

Two categories of address changes are identified:

107

They have an institutional impact or a major operational impact

They are expected to be infrequent

Minor changes: They consist in modifications in a CAAS table

They have an operational impact which can be more limited They can be more frequent

8.4.1 Example of major address change

PRMD-name = FA becomes PRMD-name = SOUTH-AFRICA

Recipient-Name:

C=XX/A=ICAO/P=FA/

O=AFTN/OU1=FAJSYMYX

Originator-Name:

Routing table:

C=XX/A=ICAO/P=FA => next hop = FAJS

108

GG FAJSYMYX

180516 SAEZYMYX

[]

TAF

C=XX/A=ICAO/P=SA/


[]

TAF

Address conversion:

NLD=FA => C=XX/A=ICAO/P=FA, addr sch=XFRouting table:C=XX/A=ICAO/P=FA => next hop = LEEE

change


8/13/2019 CAANEWG05NE25

43/58

28

8.4.2 Example of major address changePRMD-name = FA becomes PRMD-name = SOUTH-AFRICA

Recipient-Name:

C=XX/A=ICAO/P=SOUTH-AFRICA/

O=AFTN/OU1=FAJSYMYX

Originator-Name:

Routing table:C=XX/A=ICAO/P=SOUTH-AFRICA => next hop = FAJS

109

GG FAJSYMYX

180516 SAEZYMYX

[]TAF

C=XX/A=ICAO/P=SA/


[]

TAF

Address conversion:

NLD=FA => C=XX/A=ICAO/P=SOUTH-AFRICA, addr sch=XFRouting table:

C=XX/A=ICAO/P= SOUTH-AFRICA => next hop = LEEE

change

8.4.3 Example of major address changePRMD-name = FA becomes PRMD-name = SOUTH-AFRICA

Recipient-Name:

C=XX/A=ICAO/P=SOUTH-AFRICA/

O=AFTN/OU1=FAJSYMYX

Originator-Name:

Routing table:C=XX/A=ICAO/P= FA => next hop = FAJS

Non-delivery

Unable-to-transfer

Unrecognised-OR-name

110

GG FAJSYMYX

180516 SAEZYMYX

[]TAF

C=XX/A=ICAO/P=SA/


[]

TAF

Address conversion:

NLD=FA => C=XX/A=ICAO/P=SOUTH-AFRICA, addr sch=XFRouting table:

C=XX/A=ICAO/P=SOUTH-AFRICA => next hop = LEEE

of error

8.4.4 Procedure for major changes

State

ICAO

Headquarters

Official AMHS

MD Register

5

ICAO HQ

CNS Section

111

AMHS Manager s

in other States:

CCC Operators

other AMC users

n a ng

a change

ICAO

Regional

OfficeAMC

AMC Operat or

1

2 4

Exchange of written documents

Data entry

Data reading or retrieval

3

8.4.5 Procedure for major changesas proposed by EANPG/49 and endorsed by ICAO HQ

1. An accredited person in the considered State declares the change to ICAO, using astandard written pro forma ICAO means here the Regional Office for the ICAORegion where the State is located. The pro forma includes the applicability date ofthe change (an AIRAC date);

2. the CNS Officer in the Regional Office, in coordination with ICAO Headquarters asappropriate, validates the acceptability of the declared change from an official andinstitutional view oint

112

3. after validation, the CNS Officer forwards the declaration of change to the AMCOperator, using appropriate means such as fax, e-mail, etc. (different from data entryin AMC); [at the latest 21 days before the applicability date]

4. the AMC Operator enters data in the AMC based on the input received from theRegional Office, at the appropriate time considering the applicability date of thechange and using the AMC operational procedures;

5. at the date of applicability, i.e. at each AIRAC cycle date, the ICAO HQ CNS Sectionretrieves an AMHS address management export file from the AMC and uploads it inthe ICAO Official AMHS MD Register.


8/13/2019 CAANEWG05NE25

44/58

29

8.4.6 Procedure for major changesRole of ICAO Regional Office and Headquarters

1. RO: Receive and process the declaration;

2. Validate the acceptability of the declared change from an official and institutionalviewpoint:

RO: Verify that the PRMD-name has a valid syntax (see 8.1.2) and correctly identifies thedeclaring State or Organisation, e.g. not CAA);

RO + HQ: Verify that the PRMD-name is unique world wide (including declarations beingprocessed);

113

RO: Coordinate with declaring State or Organisation if the two criteria above are not met;

RO: If new or modified, verify that the Nationality Letters or Designator are not ambiguous;

RO: If ambiguous, coordinate with AMC Operator and with declaring State or Organisationto select appropriate Nationality Letters or Designator

3. RO: after validation, forward the declaration of change to the AMC Operator;[at the latest 21 days before the applicability date]

4. No ICAO action;

5. HQ: At each AIRAC cycle date, update Official Register with AMC data.

8.5.1 Example of minor address changeFor OU1 = LFFF, O = LFFF becomes O = LFBB

Recipient-Name:

C=XX/A=ICAO/P=FRANCE/

O=LFFF/OU1=LFFF/CN=LFFFZQZX

Originator-Name:

Routing table:

C=XX/A=ICAO/P=FRANCE => next hop = LFLF

Routing table: includesC=XX/A=ICAO/P=FRANCE/


=> next hop = message delivered (direct user)

114

FF LFFFZQZX

181512 SAEZZPZX

[](FPL-

C=XX/A=ICAO/P=SA/

O=SAEZ/OU1=SAEZ/ CN=SAEZZPZX

[]

(FPL-

Address conversion:NLD=LF => C=XX/A=ICAO/P=FRANCE, addr sch=CAAS,OU1=LFFF => O=LFFF

Routing table:C=XX/A=ICAO/P=FRANCE => next hop = LEEE

Before the

change

8.5.2 Example of minor address change

For OU1 = LFFF, O = LFFF becomes O = LFBB

Recipient-Name:


O=LFBB/OU1=LFFF/CN=LFFFZQZX

Originator-Name:

Routing table:




=> next hop = m essage delivered (direct user)

115

FF LFFFZQZX

181512 SAEZZPZX

[]

(FPL-

C=XX/A=ICAO/P=SA/


[]

(FPL-

Address conversion:NLD=LF => C=XX/A=ICAO/P=FRANCE, addr sch=CAAS,

OU1=LFFF => O=LFBBRouting table:C=XX/A=ICAO/P=FRANCE => next hop = LEEE

Aft er th e

change

8.5.3 Example of minor address change

For OU1 = LFFF, O = LFFF becomes O = LFBB

Recipient-Name:



Originator-Name:



=> next hop = message rejected (direct user)

Routing table:


Non-delivery

Unable-to-transfer

Unrecognised-OR-name

116

FF LFFFZQZX

181512 SAEZZPZX

[]

(FPL-

C=XX/A=ICAO/P=SA/


[]

(FPL-

Address conversion:NLD=LF => C=XX/A=ICAO/P=FRANCE, addr sch=CAAS,

OU1=LFFF => O=LFFFRouting table:C=XX/A=ICAO/P=FRANCE => next hop = LEEE

In case

of error

(case 1)


8/13/2019 CAANEWG05NE25

45/58

30

8.5.4 Example of minor address changeFor OU1 = LFFF, O = LFFF becomes O = LFBB

Recipient-Name:



Originator-Name:

Routing table: includes default route to gatewayC=XX/A=ICAO/P=France => next hop = MTCU

=> message converted (considered as indirect user)

but with failure of reverse conversion

Routing table:


Warning

toGateway

operator

117

FF LFFFZQZX

181512 SAEZZPZX

[](FPL-

C=XX/A=ICAO/P=SA/


[]

(FPL-

Address conversion:NLD=LF => C=XX/A=ICAO/P=FRANCE, addr sch=CAAS,OU1=LFFF => O=LFFF

Routing table:C=XX/A=ICAO/P=FRANCE => next hop = LEEE

In case

of error

(case 2)

8.5.5 Procedure for minor changes

118

8.5.6 Procedure for minor changesas proposed by EANPG/49 and endorsed by ICAO HQ

1. The CCC Operator [or External COM Operator] in the considered State enters datacorresponding to the intended change in the AMC, using the standard AMCoperational procedures, taking into account the applicability date of the change (an

AIRAC date);

2. the AMC Operator performs the standard AMC operational procedures, such that thestatus of changed data is passed to operational at the applicability date;

119

. , . . ,retrieves an AMHS address management export file from the AMC and uploads it inthe ICAO Official AMHS MD Register (this is identical to stage 5 in the proceduresfor major changes).

8.6.1Address Management AMC implementationstructured by different information flows

AMHS MD Register information:

from State/ANSP to ICAO Regional (and HQ) - for validation

from ICAO (Regional and HQ) to AMC for data entry and operational publication

from AMC to ICAO HQ for official Registration and Publication

Potential Institutional

Implications ?Yes

120

Intra-MD Addressing information:

from State/ANSP to AMC for operational publication (direct data entry)

from AMC to ICAO HQ for official Registration and Publication

No

These flows are integrated in AMC functions and procedures


8/13/2019 CAANEWG05NE25

46/58

31

8.6.2AMHS MD State/Org Relationship

managed in AMHS MD Register

already registered for each State world wide (declared or default)

each State/Organisation is associated to one or many Nationality Letters/ Designator(NLD)

each NLD is unique

generally a one-to-one MD-to- State/Organisation relationship

121

occasionally a one-to-many MD-to- State/Organisation relationship

potentially a many-to-one is possible (does not exist at present as such) :

multiple AMHS MDs in one State

Nationality Letters / Designator (NLD) must be different

the references are:

ICAO Doc 7910 Eurocontrol database of ANP locations (consistency issue)

unofficialANP locations and territories, created by AMC Operator when needed

impacts:

address conversion (high level attributes) routing

8.6.3AMHS MD COM Centre Relationship

managed in AMHS MD Register Function

not formally registered / published(apart from Doc 7910)well-known at AFSG/regional group level

each COM Centre is associatedo a uni ue location indicator

AMHS MDidentified by: country-name, ADMD-name, PRMD-name

and MD commonname

contains

122

generally a one-to-oneMD-to-COM Centre relationship

occasionally a one-to-many relationship

the references are:

ICAO Doc 7910 Eurocontrol database

of ANP locations (+ unofficial if needed)

impacts routing

AMHS MD-related data

COM Centre

COM Centre

identifiedby LI

containsCOM Centre-related data

(one or several)

is associated to

8.6.4 overall AMHS MD Register Update

Procedure

States inform ICAO Regional Offices about their intended changes and apply for theirregistration (as part of the procedure for major changes)

ICAO Regional Offices and HQ validate the request, and coordinate with AMC about theneed for an update to the Register (as part of the procedure for major changes)

The AMC Operator takes into account the ICAO validate changes and enters them in theAMC (as part of the procedure for major changes)

-

123

CCC and Ext COM Operators monitor changes and p repare implementation:

processing individually each modification, or

using the EXPORT action to retrieve the whole Register from AMC

On the AIRAC date, the AMC Operator transfers to Operational area

On AIRAC date at 11:00UTC, CCC and Ext COM Operators set the new data to become live

In parallel (at the AIRAC date), with no impact on AMHS network operation, ICAO HQupdates the official Register for institutional purposes, using AMC data

8.6.5AMHS MD Register Data Fields


MD Common Name unique ID local to AMC usually PRMD-name

Global Domain

Identifier (C, A, P)

o ff ic ia l id en ti fi ca ti on of AM HS MD a s de cl ar ed by A NS P an d l is te d in IC AO HQ

Register

Addressing Scheme 'XF', 'CAAS', 'other', as declared in Register

ATN Directory

naming-context

provision for future implementation of Directory

Administrative

Status

relation to AMC 'internal', 'external', 'participating', 'non-

participating'

Operational Status 'op', 'non-op', 'unknown'

S ta te /O r a n iz at io n fr om D o c 7 91 0 = A N P l oc at io ns ( + un of fi ci al s tr ic tl e qu al t o D oc 7 9 10 ( t i n i nc lu de d o r

124

unofficial territory

Nationality Letters /

Designator (NLD)

from Doc 7910 and list of unofficial ICAO locations 2, 4, 5 or 7 letters:

'A*', 'AB', 'ABC*', 'ABCD',

'AB***XYZ', 'ABCDXYZ'

Doc 7910 status indicates if complies with Doc 7910 (as reflected in

ANP locations), or not (not yet)

'official', 'unofficial'

Offic. Register

status

indicates if complies with ICAO HQ Register,

or not (not yet)

'registered'

'not-registered'

COM Centre internat ionally "visible" COM Centre(s) Locat ion Indicator

Location f rom Doc 7910 = ANP locations (+unoff ic ial ) impor ted f rom l ist o f ANP locat ions (+ unoff ic ial )

Relat ion t o Doc 7910 AMHS MD summary of " Doc 7910 s tatus" ' cons ist ent'

'inconsistent'

Relation to Official

Register

AMHS MD summary of "Offic. Register status" 'registered'

'not-registered'


8/13/2019 CAANEWG05NE25

47/58

32

8.6.6AMHS MD Register

125

Demonstration

8.7.1 Intra-MD Addressing: two Parts

CAAS Table:

contains O-OU1 relationship

enabled depending on addressing scheme selection

126

contains full user O/R address

always enabled, not often used during transition from CIDIN/AFTN

AMHS MDs having selected XF do not need to enter data

8.7.2 Intra-MD Addressing Update Procedure

the CCC or Ext COM Operator updates data (data entry phase) in the AMC:

entering individually each modification, or

using an IMPORT action to upload his CAAS Table or User Address Table into AMC

the AMC Operator enters data from ICAO HQ and/or from Regional Offices (if received)

the AMC Operator checks and validates updated data,

127

e co-or nates w t perators an xterna perators, nee e

the AMC Operator transfers to Pre-Operational area

CCC and Ext COM Operators monitor changes and prepare implementation:

processing individually each modification, or

using the EXPORT action to retrieve the whole CAAS Tables from AMC

the AMC Operator transfers to Operational area CCC and Ext COM Operators set the new data to become live

8.7.3 Intra-MD Addressing Data Fields


Organization identifies a geographical unit (e.g. a region within a

State) in conformance with CAAS addressing scheme

assigned by ANSP

Organizational Unit ALL Doc 7910 location indicators

for the considered AMHS MD

Doc 7910 status indicates if complies with Doc 7910 (as reflected in

ANP locati ons), or not (not yet )

'official', 'unofficial'

Offic. Register

status

indicates if complies with ICAO HQ Register,

or not (not yet)

'registered'

'not-registered'

CAAS Table (enabled only if the CAAS Addressing Scheme is selected)

128

AFTN Addr Indicator individual AFTN addressee indicator t o be mapped

individually to an AMHS O/R address

8-letter indicator

O/R Address the corresponding O/R address in conventional format,

built using the O/R address attribute values

derived from fields in pop-up window

User Short Name (in

pop-up window)

a unique identifier of the user to whom the O/R

address is allocated. Can be used to correlate with

data in User Capabilities

assigned by ANSP

"High-level" address

attributes (in pop-up

window)

country -name, ADMD-name, PRMD-name coming from the AMHS MD register


"Low-level" address

attributes (in

Documents

CAANEWG05NE25