Login Overview#
The seat pairing login service allows users to log in using their credentials from a personal electronic device (PED) or a Seatback Monitor to access personalized content and services on the Inflight Passenger System (IPS). This feature provides access to personalized content and services based on user-specific authentication fields.
Users can access personalized services such as favorites and bookmarks for movies and TV shows based on their logged-in account. These preferences are synchronized across different seats and PED devices, ensuring the continuity of their media experience. This functionality also applies during connecting flights, allowing users to resume their content and preferences seamlessly.
Prerequisite:
-
Pairing the passenger's personal electronic device (PED) with the seatback monitor is required to use the login from the PED on the seatback monitor.
-
Pairing is not required to log in directly to the seatback monitor.
-
To log in successfully to the IPS, PMD data must be available in the IFE system.
PMD:
Passenger manifest data (PMD) is profile information specific to each flight that is transmitted to the aircraft. For cell modem transmission, it is typically sent shortly (e.g., 20-40 minutes) before departure or during the flight.
Key Actors
-
User (Passenger): The individual attempting to log in to the IPS using their PED.
-
PED (Personal Electronic Device): The user's device that communicates with the IPS.
-
Seatback System: The interface on the back of the seat, communicates with both the PED and IPS.
1. Request Authentication Fields#
-
Trigger: The user opens the PED app or the seatback monitor.
-
Action:
- PED: Requests required authentication fields from the IFE system.
- Seatback Monitor: Requests authentication fields directly from the IFE without pairing.
-
System Interaction:
- The IPS, which is part of the IFE system, queries the Authentication Service to retrieve the current authentication requirements based on the seat class and service configuration.
- Authentication Service sends the required authentication fields to the IPS.
- IPS provides the authentication fields (e.g., frequent flyer number, ticket number) to the PED and seatback monitor.
2. Enter Credentials#
-
Trigger: The user receives authentication fields.
-
Action:
- PED: The user inputs credentials (e.g., frequent flyer number, ticket number) on the PED app.
- Seatback Monitor: The user inputs credentials on the seatback monitor interface.
3. Submit Login Request#
-
Trigger: The user submits their credentials.
-
Action:
- PED: Calls
login(loginFields, onSeatLoginListener)API, passing user credentials to the IFE. - Seatback Monitor: Calls
login(Map<String,String> loginFields, boolean logoutPreviousSeat)API, passing user credentials to the IFE.
- PED: Calls
-
System Interaction:
- IPS forwards login credentials to the Authentication Service for verification.
- Authentication Service validates the credentials.
- Authentication Service sends the login success or failure response to the IPS.
- IPS updates the login state and sends the response back to the initiating device.
4. Notify State Changes#
-
Trigger: Login state changes.
-
Action:
- If the login is initiated from the PED, the login state is transferred to the seatback monitor.
- If the seatback monitor is paired with the PED, any login state changes are notified to the PED.
-
System Interaction:
- The seatback monitor sends login state change notifications to the PED.
5. Access IPS Content#
- Trigger: Successful login.
- Action: The user can now access IPS content on either the PED or seatback monitor.
Version 1.0
