/
[AIXM-520] Add data link standard to TrafficSeparationService

[AIXM-520] Add data link standard to TrafficSeparationService

Owned by georgiana.andrei04
Last updated: 2024 Aug 14 by ADAM STYLES

ID:

AIXM-520

target version:

AIXM 5.2

version:

1.0

last updated:

08 AUG 2022

status:

APPROVED


Description

Additional attribute is added to TrafficSeparationService to indicate CPDLC standard.

Rationale for change

See https://aixmccb.atlassian.net/browse/AIXM-418

It was identified that information on CPDLC standard, along with the indication of availability (dataLinkEnabled) and logon information (dataLinkChannel) is necessary for the completeness. A separate attribute dataLinkStandard is created for that purpose.

Impact assessment

[FWD_1:1] No data mapping is necessary and no data loss occurs when data is exchanged from a system (A) that uses AIXM 5.1.1 for output towards a system (B) that uses AIXM 5.2 for input.

[BWD_MAP_LOSS] Data mapping is possible, but some data would be lost (or converted into Notes) when data is exchanged from a system (B) that uses AIXM 5.2 for output towards a system (A) that uses AIXM 5.1.1 for input.

Change Proposal details

In the UML model, in the TrafficSeparationService feature:

  • Add a new dataLinkStandard attribute, defined as “An indication of Controller-Pilot Data-Link Communication (CPDLC) standard used in support of the service.”, data type CodeDataLinkStandardType.

In the UML model, add the following data types:

  • CodeDataLinkStandardBaseType (stereotype <<codelist>>, definition: “A coded value representing the standard used for Controller-Pilot Data-Link Communication (CPDLC).”), with the following list of values:
    • ATN_B1, type = string, definition = “Aeronautical Telecommunications Network (ATN) Baseline 1 ”
    • ATN_B2, type = string, definition = “Aeronautical Telecommunications Network (ATN) Baseline 2”
    • FANS1_A, type = string, definition = “ Future Air Navigation System 1/A”
    • FANS1_A_PLUS, type = string, definition = “ Future Air Navigation System 1/A+ (an updated standard)”
    • ACARS_ATS, type = string, definition = “Aircraft Communications Addressing and Reporting System (ACARS) Air Traffic Services (ATS)”
    • OTHER, type = string, definition = ”Other”
  • CodeDataLinkStandardType (specialisation of CodeDataLinkStandardBaseType, stereotype <<datatype>>, definition: “ A complex data type that enables the provision of a NIL reason for any attribute using this type.”), attribute:
    • nilReason (type: NilReasonEnumeration)

The following UML class diagram shows the new attribute and its list of values:


Mapping AIXM 5.1.1 to AIXM 5.2 (forward)

Not applicable

Mapping AIXM 5.2 to AIXM 5.1.1 (backward)

[MAPC-02] For each AirTrafficControlService or each GroundTrafficControlService that have a child dataLinkStandard element, from the three backward mapping options applicable in this case, the first two (discard the value or use an extension) are straightforward and do not need any further details. The 3rd option (backward mapping into a Note) is detailed in order to provide a complete description of this case and its conversion option. The following mapping into Note algorithm is proposed:

  1. Remove the element dataLinkStandard.
  2. Add an annotation.Note associated with the owner class having
  • purpose=“OTHER:BACKWARD_MAPPING”;
  • LinguisticNote.note=”dataLinkStandard:<value of dataLinkStandard>

Mapping example

(Note: for mapping test data see: https://github.com/aixm/mapping_52_511/tree/master/AIXM-xxx) 

AIXM InputAIXM Output