FF-ICE in the NM B2B
- LEPORI Hubert
- WILSON Scott
This section explains which FF-ICE Services have been deployed by NM and explains how the NM B2B services practically enable the related exchanges of information.
Status
Understanding the distinction "FF-ICE Services" vs "information services"
The FF-ICE/R1 Implementation Guidance Manual, which addresses the first implementation release of FF-ICE, describes the main procedures and processes in terms of six FF-ICE services.
As explained in the FF-ICE/R1 Implementation Guidance Manual, chapter 2.4, FF-ICE Services are defined as a function from a business perspective in a consistent manner with the definition of other services in Annex 3 (MET service), 11 (Air traffic services) and 15 (Aeronautical information services). In order to fulfil the part of the function related to the exchange of information, FF-ICE Services make use of one or more of information services, defined as “A type of service in a service-oriented architecture that provides an ATM information sharing capability.”, in accordance with the PANS-IM requirements. This important clarification can be summarised by the following picture.
FF-ICE Services and related NM B2B R27 (information) services
Family 5.6.1 – Flight Information Exchange covers five of the six FF-ICE Services specified by ICAO ATMRPP for Release 1, namely the Filing Service, the Trial Service, the Flight Data Request Service, the Data Publication Service and the Notification Service. These five services, which are provided by EUROCONTROL NM, makes use of the NM B2B services to fulfil the part of the function related to the exchange of information. The picture below identifies the NM B2B services used in this context, with detailed explanations captured in the subsequent table.
| FF-ICE Service provided by EUROCONTROL NM | Information service(s) | Notes / Explanations |
|---|---|---|
| Filing Service | NM B2B Filing Service
| The NM B2B Filing Service has an interface based on the synchronous Request/Reply MEP that supports the filing of a new eFPL, the update to an existing eFPL and the cancellation of an eFPL. The synchronous reply to the filing of, or update to, an eFPL provides immediate feedback to the operator regarding whether the eFPL was successfully processed, and whether it is acceptable. Changes in eFPL acceptance occurring any time after the filing can be obtained either via the interface of the NM B2B Filing Service based on the Publish/Subscribe MEP, or in request/reply mode via the NM B2B Flight Data Request Service. In the former case, the interface of the NM B2B Filing Service based on the synchronous Request/Reply MEP is used to create and manage the appropriate subscriptions to the changes in eFPL acceptance. |
| Trial Service | NM B2B Trial Service | The NM B2B Trial Service has one single interface based on the synchronous Request/Reply MEP that supports the submission of a what-if type of request to EUROCONTROL NM to ascertain the acceptability/validity and possible ATM impact of a potential eFPL or the effects of a change being considered, without either creating a flight plan or changing the intended filed flight plan. |
| Flight Data Request Service | NM B2B Flight Data Request Service | The NM B2B Flight Data Request Service has one single interface based on the synchronous Request/Reply MEP allowing to immediately retrieve eFPL information, including the eFPL data and the Filing Status of a previously filed eFPL (or the submission status in case of manual intervention). |
| Data Publication Service | NM B2B Publication Service | The NM B2B Publication Service has an interface based on the Publish/Subscribe MEP that will push the eFPLs to the client applications having subscribed to the eFPL topic. The management of these subscriptions is done via the other interface of the NM B2B Publication Service based on the synchronous Request/Reply MEP. |
| Notification Service | NM B2B Notification Service | The NM B2B Notification Service has one interface based on the synchronous Request/Reply MEP that supports the submission of notifications of departure and arrival events. |
Summary - which NM B2B R27 services to consume?
- - - - - - - - - - - - > | Information services | |||||
NM B2B | NM B2B Flight Data Request Service | NM B2B Trial Service | NM B2B | NM B2B Notification Service | ||
|---|---|---|---|---|---|---|
FF-ICE | FF-ICE Filing Service | ü | (ü)(*) | |||
| FF-ICE Flight Data Request Service | ü | |||||
| FF-ICE Trial Service | ü | |||||
| FF-ICE Data Publication Service | ü | |||||
| FF-ICE Notification Service | ü | |||||
(*) if the interface of the NM B2B Filing Service based on the Publish/Subscribe MEP is NOT used
Working Draft