SYNCHRONOUS_REQUEST_RESPONSE

All the reverse entity references for this entity

This Service Interface exposes the set of basic operations needed for manual correlation.

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 correlation status of all flights 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 technical operation that allows the consumer (operational supervisor, technical supervisor...) to get the current state of Airspace planning data on request. It is typically used when starting the Service, for initialisation.

Operations

If airspaceStatusRequested is filled, this operation allows a consumer to get the applicable airspace planning data related to all the relevant airspaces (ARES and/or CDR according to its request).
Only the ARES and CDR having at least 1 timesheet are received as a response to this request.

If airspaceName is filled, this operation allows a consumer to get the applicable airspace planning data related to the designated airspace (ARES or CDR).
If the designated airspace doesn’t have any timesheet, no airspace planning data is received..

Synchronous
SYNCHRONOUS
Precondition
Either airspaceStatusRequested or airspaceName should be filled.
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 technical operation that allows the consumer (operational supervisor, technical supervisor...) to get the current state of Airspace status data on request. It is typically used when starting the Service, for initialisation.

Operations

If airspaceStatusRequested is filled, this operation allows a consumer to get the applicable airspace status data related to all the relevant airspaces (ARES and/or CDR according to its request).

If airspaceName is filled, this operation allows a consumer to get the applicable airspace status data related to the designated airspace (ARES or CDR)..

Synchronous
SYNCHRONOUS
Precondition
Either airspaceStatusRequested or airspaceName should be filled.
TI Protocol Methods
transfer
Operation Message
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 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 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 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