...
| Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks | ||||
|---|---|---|---|---|---|---|---|---|
| RTE-401 | All RouteSegments of a Route may have a related a Service provided by a Unit with the name attribute encoded. | PANS-AIM ENR 3 | TBD | RoutePortions have to be defined that cover all RouteSegments of a Route | ||||
| RTE-402 | All RouteSegments of a Route should have a related Service that uses a If a Service is related to a RouteSegments it shall have a RadioCommunicationChannel with the frequencyTransmission and frequencyRecption attribute encoded. | PANS-AIM ENR 3 | TBD | RTE-403 | All RouteSegments of a Route should have a related Service that uses a RadioCommunicationChannel with the frequencyRecption attribute encoded, in case of a bidirectional communication. | Data consistency | TBD | |
| RTE-404 | Data link logon address should be encoded if available. | PANS-AIM ENR 3 | TBD | |||||
| RTE-405 | If any, SATVOICE number, and any navigation, RCP and RSP specification(s) limitations should be encoded using Note. | PANS-AIM ENR 3 | TBD |
...