SYNCHRONOUS_REQUEST_RESPONSE

All the reverse entity references for this entity

This Service Interface exposes the technical operation that allows the consumer to get the status of each individual service and the global CCS Service on request. It is typically used when starting the Service, for initialisation

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 set of operations related to SSR Code Management that are not necessarily required to achieve a usual/basic interoperability level.

Operations

The operation allows to reset the isEligibleForModeSCode indicator (i.e. change it from TRUE to FALSE) or, if manually reset, to enable again its automatic reassessment (i.e. enable its automatic change from FALSE to TRUE, if previously manually changed from TRUE to FALSE).
The setModeSEligible attribute is ignored by CCS.

When the system will have to automatically assign a SSR code to the flight, the system will take this status (indicator set or not) into account to determine the proper code to use (discrete or conspicuity).
By default, automatic reassessment is allowed.
On reset of the "Eligible for Mode S Code" indicator in the SFPL, the system shall:
- trigger a new discrete SSR code automatic assignment to the controlled SFPL internal segments that had the conspicuity code automatically assigned and are not in left status, if any, and
- store the conspicuity code in the PSSR of these internal segments, if any, and
- remove the Mode S address stored in the SFPL, if the SFPL was correlated on the conspicuity code.
- disable the automatic reassessment of the indicator.
If automatic reassessment is allowed, the indicator is TRUE if :
- the flight is Mode S equipped
- the entire remaining route is included in a Mode S declared Airspace
- the flight belongs to a Mode S flagged directional flow.
For an inbound flight, if the SSR code received from the upstream segment is the Mode S conspicuity code, the system forces the Mode S capability of the flight and considers it as a Mode S flight..

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 the set of basic operations needed for SSR Code Management.

Operations

The operation allows to release an assigned SSR code if it is not used for correlation purpose.
Due to the limited number of Mode 3/A SSR codes it is necessary to release assigned codes back into the pool of available codes when possible. Normally this would be handled automatically with the Flight Data Manager or other service monitoring the status of a flight and requesting the release of a code when a flight lands, leaves the Area of Responsibility of an ATSU or is cancelled..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Processing Consideration

The operation allows to manually assign a code given in the input, or to request an automatic code assignment.
The manual assignment is allowed if there is no code assigned, as well as if there is one already assigned to the flight, in order to modify it.
If ssrCode is provided in the input (i.e. manual assignment), the operation allows changing either the code assigned to the segment given in the input, the code assigned to the previous segment, or the one assigned to the next.
- for the assignment of the code to the given segment: If the controlled SFPL internal segment is correlated on the current assigned SSR code, or if the flight is not yet correlated and previousSSRCode is empty, the system shall push the currently assigned SSR code in the previousSSRCode and the new assigned one in the assignedSSRCode. Otherwise the system shall overwrite the currently assigned SSR code by the new one.
- for the assignment of the code to the previous or next segment: the input is accepted if the code to modify is not currently used for correlation purpose.

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Processing Consideration
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 operations that allow the consumer to manage a simulation session (start, stop, set simulation time speed)

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

This Service Interface exposes the operation used by a Technical user to start/restart the CCS Platform (or part of it).

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 data related to the current test/training session, if any.

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 operations used by the Operational Supervisor to modify the Sector Configuration Data.

Operations

Enables to activate a sector mapping: the supervisor selects a mapping (next or pre-defined mapping) that will replace the current mapping of the concerned ASTUSectorConfiguration.
The supervisor may also choose to revert back to the pre-defined default sector mapping. If not, the input parameters shall be the identifier and the state (next or pre-defined) of the origin sector mapping.
As a consequence, the parameter sectorMappingId is MANDATORY when the parameter revertToDefaultMapping is not filled or set to FALSE (but if revertToDefaultMapping is set to YES, sectorMappingId is not needed)..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

Enables to delete a given sector mapping. Only the next sector mapping can be deleted.
The input parameter is the identifier of the concerned ATSUSectorConfiguration (sufficient to delete a next mapping knowing that only one next sector mapping per ATSUSectorConfiguration).
.

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