LHG:ONERES Interface: Difference between revisions
Jump to navigation
Jump to search
Stefanseiler (talk | contribs) |
Stefanseiler (talk | contribs) |
||
| Line 35: | Line 35: | ||
* <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 | * <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 | ** once an hour polling the database | ||
** receiving SOS/DSC messages from SARA if new relevant bookings to track appear or are no longer required. | ** 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 | * <u>Future booking data cache</u> - uses the interface to one time pre-fetch the booking information and store it here | ||
** receive a SOS/DSC 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>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</code> | ** 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 | *** 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 | *** with a <code>forceupdate</code> parameter, which queries the oneres-api and return the real-time answer | ||
Revision as of 09:54, 20 November 2025
ONERES is a Lufthansa Tool to access bookings and general flight availability information
Contained data
Flight Plan
This holds the regularly planned flights:
- FLIGHT NUMBER
- FROM
- TO
- LOCAL DEPARTURE TIME
- LOCAL ARRIVAL TIME
- Planned flight duration
- Planned craft type
- Repetition pattern (weekdays, monthly, exact dates)
General Availability (GAV)
This holds for each flight identified by:
- departure date and flight number or
- departure date and departure time and departure port and destination port
Nnumber of bookable seats per transportation class ( Y = economy / C = business / F = first )
Booking information
This holds information for each PAX booking, where we can retrieve for each SAR the full booking information with all elements (itinerary, cost, ... ) especially the ones relevant to special assistance requests.
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