SYNCHRONOUS_REQUEST_RESPONSE

All the reverse entity references for this entity

This Service Interface exposes operations used by the Operational Supervisor to modify the Radio Frequency Allocation.

Operations

Allows a consumer to modify the radio frequency assigned to control responsibility(ies):
- either by selecting a new radio frequency,
- or by reverting back to the predefined value (off-line defined) of the radio frequency assigned to the given control responsibility (if it has been on-line updated before).

The input parameters shall be:
- the value of the new radio frequency and the controlResponsibility(ies) where the indicated frequency shall be assigned,
- or the controlResponsibility(ies) where the default frequency shall be assigned.

When the aim of this operation is to :
- apply a new frequency to one or several Responsibilities, frequency should be filled
- revert to default frequency for one or several Responsibilities, revertToDefaultFreq should be set to TRUE and frequency shouldn't be filled
.

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Processing Consideration

Allows a consumer to change the current radio frequency allocation:
- either by selecting a new radio frequency allocation plan among the predefined radio frequency configurations,
- or by reverting back to the predefined default radio frequency configuration (offline defined).

The input parameters shall be:
- the name of the requested ATSUSectorConfiguration,
- and the name of the radio frequency configuration to load in place of the current one (except on the operation of reverting back to the default one: in this case this is the default radio frequency configuration which will be loaded).

When the aim of this operation is to :
- apply a new plan to an ASTUSectorConfiguration, radioFrequencyAllocationName should be filled
- revert to default frequency plan an ASTUSectorConfiguration, revertToDefaultPlan should be set to TRUE and radioFrequencyAllocationName shouldn't be filled
.

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Processing Consideration
Interface Binding Description

Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler.

Interface Provision Side
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding

This Service Interface exposes operations used by the Operational Supervisor to modify on-line Airspace (ARES or CDR) Status data.

Operations

Enables to unlock a previous manual CDR status.
The input parameters shall be the originator and the CDR identifier (airway name and names of the start and last points of the CDR)..

Synchronous
SYNCHRONOUS
Precondition
The consumer has pre-defined (off-line) all his CDRs as portion of airways.
TI Protocol Methods
transfer
Processing Consideration

Enables to lock the CDR status to open or closed.
The input parameters shall be the originator, the CDR identifier (airway name and names of the start and last points of the CDR) and the CDR status..

Synchronous
SYNCHRONOUS
Precondition
The consumer has pre-defined (off-line) all his CDRs as portion of airways.
TI Protocol Methods
transfer
Processing Consideration
Interface Binding Description

Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler.

Interface Provision Side
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding

This Service Interface exposes operations used by the Operational Supervisor to modify on-line Airspace (ARES or CDR) Planning data.

Operations

Allows to add a timesheet into an ARES timetable to define new activation periods.
The input parameters shall be the originator, the ARES name and the timesheet data containing the activation levels, an activation time period, and optionally a periodicity..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

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

Synchronous
SYNCHRONOUS
Precondition
The consumer has pre-defined (off-line) all his CDRs as portion of airways.
TI Protocol Methods
transfer

Allows to remove an existing activation periods timesheet from a CDR timetable.
The input parameters shall be the originator, the CDR identifier (airway name and names of the start and last points of the CDR) and the identifier of the timesheet to remove..

Synchronous
SYNCHRONOUS
Precondition
The consumer has pre-defined (off-line) all his CDRs as portion of airways.
TI Protocol Methods
transfer

Allows to update an existing activation periods timesheet for an ARES.
The input parameters shall be the originator, the ARES name, the identifier of the timesheet to update and the timesheet data containing the activation levels, an activation time period, and optionally a periodicity..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

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

Synchronous
SYNCHRONOUS
Precondition
The consumer has pre-defined (off-line) all his CDRs as portion of airways.
TI Protocol Methods
transfer
Interface Binding Description

Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler.

Interface Provision Side
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding

This Service Interface exposes operations used by the Operational Supervisor to modify the Aerodrome Configuration Data.

Operations

Allows to modify the current configuration of the runways for an aerodrome of a given Aerodrome Group.
This operation enables an eligible user (normally a supervisor) to modify the following data of a given runway or of the runway(s) of an aerodrome: landing and/or take-off rates, IAP in operation and operating mode (open or closed).
It is also possible to revert to default rate values of runway(s) if no rate value is provided in the operation..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

Allows replacing the current Aerodrome Group Configuration with another given aerodrome group configuration.
The user may activate an offline predefined aerodrome group configuration, activate the one previously defined as the Next one or revert back to the default one.

When the aim of this operation is to :
- activate an offline predefined aerodrome group configuration, aerodromeGroupConfigName should be filled with the name of the configuration,
- activate the next aerodrome group configuration, aerodromeGroupConfigName should not be filled,
- revert back to the default aerodrome group configuration, aerodromeGroupConfigName should not be filled and aerodromeConfigurationOrigin should be DEFAULT.
.

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Processing Consideration

Allows modifying the configuration parameters of an aerodrome.

The 3 possibilities given by this operation are :
- revert to default the aerodrome Altitude Correction
- revert to default the aerodrome Transition Level. In this case, defaultAltitudeCorrection should be set to FALSE
- modify one or several of the following parameters : transitionLevel, altitudeCorrection, modeSCapabilityState. In this case, revertToDefault should not be filled

aerodromeGroup is ignored by CCS..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Processing Consideration

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

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Behaviour
Interface Binding Description

Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler.

Interface Provision Side
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding

This Service Interface exposes the operations that allow the consumer (operational supervisor, technical supervisor...) to get the current state of Sector Configuration data on request.

Operations
Interface Binding Description

Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler.

Interface Provision Side
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding

The RadioFrequencyAllocationProvider service interface definition exposes the operations that allow the consumer (operational supervisor, technical supervisor...) to get the current state of Radio Frequency Allocation data on request.

Operations

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

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Interface Binding Description

Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler.

Interface Provision Side
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding

The AerodromeConfigurationProvider service interface definition exposes the operation that allows the consumer (operational supervisor...) to get the current state of a given Aerodrome Group Configuration on request.

Operations
Behaviour
Interface Binding Description

Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler.

Interface Provision Side
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding

This Service Interface exposes the technical operation that allows the consumer to get the current monitoring aids information of all flights on request. It is typically used when starting the Service, for initialisation.

Operations

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

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Interface Binding Description

Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler.

Interface Provision Side
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding

This Service Interface exposes two technical operations that allows the consumer to get the erroneous AFTN message information for FDO correction, on request. It is typically used when starting the Service, for initialisation.

Operations

Allows a consumer to get the erroneous AFTN messages referred to FDO for manual correction, either for a specific erroneous message by filling the messageId, or all the erroneous messages if the messageId attribute is empty.

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

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Interface Binding Description

Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler.

Interface Provision Side
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding

This Service Interface exposes the technical operation that allows the consumer to get the current flight plan data of all flights on request. It is typically used when starting the Service, for initialisation.

Operations

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

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Processing Consideration
Interface Binding Description

Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler.

Interface Provision Side
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding