IPV4_SECURE_UNICAST

Allows a consumer to get the applicable data related to sectorMappings.
This operation returns the SectorMappings: the current SectorMapping and the next SectorMapping (if available) of the requested ATSUSectorConfiguration..

This operation publishes the current radio frequencies allocation plan to the subscribed service consumers at each on-line update.
It provides the list of Responsibilities of the atsuSectorConfiguration and the radio frequency allocated to each one of them, as well as the list of frequencies not allocated to any Responsibility.
.

Allows a consumer to get the current data related to a given radio frequencies allocation plan or the free frequencies related to a given sector configuration.

radioFrequencyAllocationName could be filled to get data for a specific radioFrequencyAllocation (otherwise, the request is global), and sectorConfigurationName could be filled as well, while subscribedRadioFrequencyAllocation is ignored by CCS..

This operation publishes online updates to the configuration of an aerodrome or aerodrome group to subscribed users.
The configuration data that can be changed on-line are:
- current and next aerodrome group configuration
- data related to each aerodrome in the group: aerodrome transition level, runway(s) availability and rates...

Note: an aerodrome group is a set of one or more aerodromes that have inter-dependent runways, e.g. if a runway is in use for departures then another runway cannot be used for arrivals due to conflicting traffic patterns.
.

Allows a consumer to get the applicable data related to a given AerodromeGroupConfiguration.

Allows a consumer to get all the deviations related to all the flights known by the System.
All the request parameters are ignored by CCS.

All the flights, except the ones that have never been correlated, are received as a response to this request (even the flights without any deviation on-going)..

This operation sends the monitoring aids information of a flight when it is updated. As long as there is no update, the monitoring aids information of the last received message remains applicable.
A first notification is sent when the flight correlate for the 1st time (1st progression report), and then a notification is sent each time a deviation is created, removed or modified (ex: when the deviation amplitude is changed).
The evaluation of each deviation being made by the system in a cyclic pattern, its update (creation, removal, modification) can be delayed by a few seconds regarding the event itself. The maximum delay is determined by the cycle value defined in the dataset..

Allows a consumer to get the summary of erroneous AFTN messages referred to FDO for manual correction.

Refer to publishErroneousAFTNMessageData description for more details about the list of errors that can be encountered
.

Allows a consumer to get the applicable flight plan data related to all relevant flights concerning this consumer.
In the request, the parameter oe allows to filter the flights to be received in return (the criteria is fulfilled if oe is part of the list of servedController.controller.identifier for the flight). If no oe is filled, no fliter is applied to the response (all flights known by the system are expected). The parameter wpId is ignored by CCS..

This operation sends the erroneous AFTN messages information for FDO correction.

Upon reception of an AFTN erroneous message associated to a given SFPL, this message is referred to FDO.

Only the following AFTN messages are referred to FDO by CCS (the other are not yet within the scope of PJ16): ACH, APL, ARR, CHG, CNL, DEP, DLA, FPL, IACH, IAPL, IARR, ICHG, ICNL, IDEP, IDLA, IFPL.
The consumer can receive two other kinds of referred message: blocked and not checked.
The information referralType is used to differentiate an erroneous message referred for correction from a message "blocked" by FDM since an erroneous message for the same SFPL was already referred to FDO.