IPV4_SECURE_UNICAST

Allows to update an existing CDR timesheet.
The input parameters shall be the originator, the CDR identifier (airway name and names of the start and last points of the CDR), the identifier of the timesheet to update and the timesheet data containing an activation time period, and optionally the activation levels and/or periodicity..

Allows changing the next configuration to be applied for an aerodrome group by selecting another aerodrome configuration from a predefined configuration list, and/or to change the date and time that the configuration is planned to be activated.
.

In case of operational configuration change, this operation performs the publication of the new status and data related to the updated ATSUSectorConfiguration to the subscribed service consumers..

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..