LHG:ONERES Interface: Difference between revisions
Jump to navigation
Jump to search
Stefanseiler (talk | contribs) |
Stefanseiler (talk | contribs) |
||
| (10 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
== Contained data == | == Contained data == | ||
'''AMADEUS Inventory call''' | |||
This returns General Availability (GAV) and more information on a specific flight at a specific date. | |||
{| class="wikitable" | |||
!Invocation-data | |||
|Flight number, Date | |||
|- | |||
!Result-data | |||
|all data on this flight (GAV, .... ) | |||
|} | |||
This returns for each flight identified by: | |||
This | |||
* '''departure date''' and '''flight number''' or | * '''departure date''' and '''flight number''' or | ||
* '''departure date''' and '''departure time''' and '''departure port''' and '''destination port''' | * '''departure date''' and '''departure time''' and '''departure port''' and '''destination port''' | ||
the amount of bookable seats per transportation class ( Y = economy / C = business / F = first ) | |||
====== Booking information ====== | |||
This interface is a real-time api interface to fetch all booking information relevant to [[special assistance requests.]] | |||
{| class="wikitable" | |||
!Invocation-data | |||
|PNR / Booking-Code | |||
|- | |||
!Result-data | |||
|Booking-Data (Header-Info, Array of elements and element data) | |||
|} | |||
== Planned interface approach == | |||
A '''Flight data SLH Controller''' runs in the '''LH MOC''' digital and delivers these services: | |||
* <u>Flightplan cache</u> - which builds a local business cache from | |||
** the data manually entered in the flightplan | |||
** retrieved from the '''Flight Plan''' interface {{Yellow-Tag|YellowText=Phase 2}} | |||
* <u>Future bookings cache</u> - which holds a list of all bookings relevant to SARA, which are not older than 3 months and the future. This list is updated by | |||
** once an hour polling the database | |||
** receiving <code>SOS/DSC</code> messages from SARA if new relevant bookings to track appear or are no longer required. | |||
* <u>Future booking data cache</u> - uses the interface to one time pre-fetch the booking information and store it here | |||
** receive a <code>SOS/DSC</code> message on propable booking request (a couple of seconds before the user enters the information) - and then the data is prefetched over the ONERES api | |||
** receive a <code>sync SOS/DSC</code> message on booking request query, which | |||
*** checks if the cache was updated in the last hour and then just returns the cache | |||
*** with a <code>forceupdate</code> parameter, which queries the oneres-api and return the real-time answer | |||
== See also == | == See also == | ||
Latest revision as of 12:25, 27 November 2025
ONERES is a Lufthansa Tool to access bookings and general flight availability information
Contained data
AMADEUS Inventory call
This returns General Availability (GAV) and more information on a specific flight at a specific date.
| Invocation-data | Flight number, Date |
|---|---|
| Result-data | all data on this flight (GAV, .... ) |
This returns for each flight identified by:
- departure date and flight number or
- departure date and departure time and departure port and destination port
the amount of bookable seats per transportation class ( Y = economy / C = business / F = first )
Booking information
This interface is a real-time api interface to fetch all booking information relevant to special assistance requests.
| Invocation-data | PNR / Booking-Code |
|---|---|
| Result-data | Booking-Data (Header-Info, Array of elements and element data) |
Planned interface approach
A Flight data SLH Controller runs in the LH MOC digital and delivers these services:
- Flightplan cache - which builds a local business cache from
- the data manually entered in the flightplan
- retrieved from the Flight Plan interface Phase 2
- Future bookings cache - which holds a list of all bookings relevant to SARA, which are not older than 3 months and the future. This list is updated by
- once an hour polling the database
- receiving
SOS/DSCmessages from SARA if new relevant bookings to track appear or are no longer required.
- Future booking data cache - uses the interface to one time pre-fetch the booking information and store it here
- receive a
SOS/DSCmessage on propable booking request (a couple of seconds before the user enters the information) - and then the data is prefetched over the ONERES api - receive a
sync SOS/DSCmessage on booking request query, which- checks if the cache was updated in the last hour and then just returns the cache
- with a
forceupdateparameter, which queries the oneres-api and return the real-time answer
- receive a