SWIM_TI_YP_1_0_AMQP_MESSAGING

All the reverse entity references for this entity

The AFTNCorrectionManagementProvider Service Interface manages the operations performed by the FDO to correct erroneous AFTN messages concerning in-coming flight plan that cannot be processed automatically by the system.
It covers the following cases:
- AFTN Modification messages: CHG, CNL, DLA, ARR, DEP (ICAO format), ICHG, ICNL, IDLA, IARR, IDEP, IACH (ADEXP format). In this case, it may be necessary to associate a FP to these messages to be able to correct them successfully.
- AFTN Creation messages: FPL (ICAO format), IFPL, IAPL (ADEXP format).

Operations

This operation allows the operator to correct the erroneous fields upon the reception of a CHG or ICHG message.
Whenever a change is made to the data contained in a Flight Plan message already sent to the ATSUs concerned with the flight, they must all be notified. It is particularly important to notify changes of Flight Level or Flight Rules, whether the change is made before departure or en-route. Such notification may be done by phone or ATS/DS when possible; otherwise it must be done by means of a modification message sent to AFTN.

The following CHG fields can be corrected through this operation:
CHG content: callsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), destinationAerodromeDesignator (F16a), totalEstimatedElapsedTime (F16b), otherInformation (F18), amendments of other ICAO fields (F22), alternativeDestinationAerodromeDesignator (F16c).
In CHG, F22 should only amend F7b/c, F8, F9, F10, F13b, F14, F15, F16, F18, F19.

The following ICHG fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD),
estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

This operation allows the operator to correct the erroneous fields upon the reception of an FPL or IFPL message.
The FPL message is the flight plan as filed with an ATS unit by the pilot or a designated representative, without any subsequent changes.
The following FPL fields can be corrected through this operation:
callsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), flightRules (F8a), flightType (F8b), numberOfAircraft (F9a), aircraftTypeICAOIdentifier (F9b), wakeTurbulenceCategory (F9c), NCAEquipment (F10a), surveillance equipment (F10b), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), enRouteCruiseSpeed (TAS or Mach) (F15a), requestedFlightLevel (F15b), icaoRoute (F15c), destinationAerodromeDesignator (F16a), totalEstimatedElapsedTime (F16b), alternativeDestinationAerodromeDesignator (F16c), otherInformation (F18), supplementaryInformation (F19).

The following IFPL fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP),
NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

This operation allows the operator to correct the erroneous fields upon the reception of an IAPL message (ICAO format message APL is not applicable CCS).

The following IAPL fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

This operation allows the operator to correct the erroneous fields in the SFPL upon the reception of an IACH message (ICAO format message ACH is not applicable CCS). It is the modification message type distributed by the IFPS upon receipt and successful processing of an FNM, MFS, and AFP for which a valid associated flight plan exists in the IFPS.

The following IACH fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

This operation allows the operator to correct the erroneous fields upon the reception of an ARR or IARR message. Where an Arrival message is required for an IFR/GAT flight or part thereof operating within the IFPZ, the appropriate air traffic services unit shall submit such to the IFPS for processing

The following ARR fields can be corrected through this operation:
callsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), destinationAerodromeDesignator (F16a), destinationAerodromeDesignator and actualLandingTime (F17), date of flight in otherInformation (F18).

The following IARR fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), actualLandingTime (ATA), destinationAerodromeDesignator (ADARR)

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

This operation allows the operator to correct the erroneous fields upon the reception of an CNL or ICNL message. When a schedule flight or a flight for which a Flight Plan Message has been sent, is subsequently cancelled, the ATSU at the point where the flight is cancelled shall send a Cancellation Message.

The following CNL fields can be corrected through this operation:
callsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), destinationAerodromeDesignator (F16a), otherInformation (F18).

The following ICNL fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE)

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

This operation allows the operator to correct the erroneous fields upon the reception of an DLA or IDLA message. When a scheduled flight, or a flight for which a FPL was despatched, has not left the loading apron within 30 minutes after the scheduled or estimated time of departure; or where there is reason to believe that such a flight will not be in a position to leave within the 30 minutes due to the late arrival of the aircraft on the previous sector or for any other reason.

The following DLA fields can be corrected through this operation:
callsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), destinationAerodromeDesignator (F16a), otherInformation (F18).

The following IDLA fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

This operation allows the operator to correct the erroneous fields upon the reception of a DEP or IDEP message. Departure message shall be sent immediately after take-off in respect of all flights for which a Flight Plan Message has been sent.

The following DEP fields can be corrected through this operation:
callsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), destinationAerodromeDesignator (F16a), otherInformation (F18).

The following IDEP fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR), actualTakeOffTime (ATD)

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

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 encompasses the different operations performed by the ATCO and modifying the Flight Plan Data: tactical instructions and system inputs performed to modify the planed route.

Operations

Operation to process the modification of one or several SFPL fields.
The input shall contain the flight identifier, the originator and at least a field to modify.
The fields that can be modified through this operation are related to static SFPL information (information of the SFPL independent of the modifications triggered by tactical instructions) such as: callsign aircraftIdentification (F7a), departureAerodromeDesignator (F13a), destinationAerodromeDesignator (F16a), flightType (F8b), flightRules (F8a), numberOfAircraft (F9a), aircraftTypeICAOIdentifier (F9b), wakeTurbulenceCategory (F9c), NCAEquipment (F10a), surveillance equipment (F10b), equipment status (F81), estimatedOffBlockTime (F13b), requestedFlightLevel (F15b), icaoRoute, enRouteCruiseSpeed (TAS or Mach) (F15a), totalEstimatedElapsedTime (F16b), alternativeDestinationAerodromeDesignator (F16c), ssrCodeData, otherInformation (F18), supplementaryInformation (F19), sidDesignator, starDesignator..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

Allows the operator to make a segment regression.
It turns a controlled segment from live or pending status into monitored status
The system keeps the segment in monitored state until a notification or activation message is received.

The input shall contain the flight identifier, the segment identifier and optionally the segment entry time (estimated time over the segment entry point).
When filled, the segment entry time adjusts the time estimates over the trajectory points.

Caveat: The operation name (coming from SESAR) is misleading in CCS context..

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 encompasses the different operations performed by the ATCO and modifying the Flight Plan Data. These operations can be divided in two sets of operations: the tactical instructions and the system inputs performed to modify the planed route:
- ATC tactical Instructions: Holding, Heading, Speed, Cleared Flight Level (CFL),Rate Of climb/Descend (ROCD), Direct To and Cleared To,
- System inputs: entry FL (EFL), exit FL (XFL), enCruiseFL (ECL) and requested Flight Level (RFL).

Operations

Operation to process the input of a Cleared Flight Level given the flight identifier and the value of the level to be applied.
The input may contain applicationStart data that can be a route point, distance before/after a route point or after current position..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

Operation to process the input of a direct instruction given the flight identifier and the target point of the direct (not overflown point already belonging to the route).
The input may contain application data that can be a route point, distance before/after a route point or after current position..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

Operation to process the input of a heading clearance.
It allows to assign either:
- an absolute heading. To do this:
- routePointId should not be filled
- continueHeading should be either not filled or set to FALSE
- either assignedHeading or application end point shoud be filled. If filled, the application end point should be expressed in the geographical point type
- a relative heading. To do this:
- routePointId should not be filled
- continueHeading should be either not filled or set to FALSE
- directionOfTurn and assignedHeading shoud be filled
- a maintain order. To do this:
- routePointId should not be filled
- continueHeading should be set to TRUE
- a resume own navigation order. To do this, routePointId should be filled..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

Operation to process the modification of a route portion for a specified flight.
The input shall contain:
- the flight identifier,
- the new portion of route.
The input may contain either an application end point (routePoint not overflown used to rejoin the old route) or a new destination aerodrome.
The input may also contain application start data that can be a route point, distance after/before a route point, distance after current position.
.

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 for publishing:
- on-line updates of the status of CCS;
- updates of service appliance status;
- updates of service resource utilisation.

Operations

This operation sends to the subscribed consumers both the specific CCS services statuses and the CCS global one. For each CCS individual service, the possible statuses are:
- INITIATING: CCS individual service is starting up and is not ready to provide its functionalities;
- AVAILABLE_RUNNING: CCS individual service is running in nominal mode and is able to provide its functionalities;
- REDUCED_RESILIENCE: redundance loss;
- SERVICE_NOT_AVAILABLE: CCS individual service is not available;

The CCS global status is the result of the combination of the statuses of the CCS gateway, its AMQP broker and the individual CCS services. Its possible values are:
- INITIATING: the CCS Gateway is starting up regardless the status of the CCS individual services. CCS is not ready to provide its services;
- AVAILABLE_RUNNING: CCS service is running in nominal mode and is able to provide a service;
- REDUCED_RESILIENCE: redundance loss (at least one CCS individual service is REDUCED_RESILIENCE and the other ones are AVAILABLE_RUNNING);
- SERVICE_PARTIAL_FAILURE: at least one CCS individual service is SERVICE_NOT_AVAILABLE;
- SERVICE_NOT_AVAILABLE: either CCS Gateway or its AMQP broker is not available, regardless the status of the CCS individual services;
- SHUTTING_DOWN: CCS Gateway is shutting down following an issued command or unplanned failure.

The subscribed consumers are informed of any change regarding the status of CCS (seen as a global Service) and the status of a CCS individual service. When the CCS global status is published, the reason attribute is used to list all the individual service statuses separated by ";".
Each time the status of an individual service is updated, it would trigger the publication of the global CCS status (even if unchanged), with an updated reason.

Note: the status of SIMULM and SIMULD services is not provided if the platform state is OPERATIONAL.
.

Synchronous
ASYNCHRONOUS
TI Protocol Methods
transfer
Operation Message

This operation sends to the subscribed consumers the various status relative to CCS external interfaces (OLDI, AFTN, METEO, RADAR).

The subscribed consumers are informed of any change regarding the status of CCS external interfaces. The status of each external interface is notified separately; the externalInterfaceName field is used to distinguish what interface the status is related to. .

Synchronous
ASYNCHRONOUS
TI Protocol Methods
transfer
Operation Message

This operation sends to the subscribed consumers clients the various resource utilisation (Disk, CPU, Network) related to service appliances of CCS as a global Service.

The publication is triggered by the following events:
- cpuUtilisation exceeds 95% (alarm start)
- cpuUtilisation decreases under 80% (alarm end)
- storageCapacityUtilisation changes its status (from OK to NOK or vice-versa)

Note: if no cpu start of alarm is notified, no publication is made when the cpu decreases under the 80% threshold..

Synchronous
ASYNCHRONOUS
TI Protocol Methods
transfer
Operation Message
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 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 operation for publishing updates of test/simulation sessions managed by means of the CCS Simulation Management Service.

Operations

This operation sends to the subscribed consumers the current test/simulation session data, if the Platform state is different from OPERATIONAL..

Synchronous
ASYNCHRONOUS
TI Protocol Methods
transfer
Operation Message
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