Skip to content

Seat Property Transfer Overview#

The Seat Property Transfer feature allows a PED (Personal Electronic Device) application to send user profile and preference information to the aircraft’s seatback system. This integration enables a more personalised in-flight entertainment experience—passengers can configure their settings on the PED, which then syncs with the seat back monitor to reflect their preferences, such as language, content types, or display message.

Below is an overview of the key steps involved in implementing seat property transfer, aligned with the detailed flow in the iOS and Android developer documentation.

Step 1: Initializing the Seat Property Transfer Service#

Before sending any data to the seatback system, the PED app must initialize the Seat Property Transfer service. This is done after the Seat Pairing process is complete. Initialization ensures that the SDK is ready to manage and send user-related data to the seatback monitor.

Although seat pairing is required to transfer data to the seatback system, passengers can configure their user profile and preferences in the companion app even before boarding the aircraft. This means travelers can input details such as name, preferred language, parental control settings, or media preferences while still on the ground without requiring a seat connection.

Once the passenger is onboard and pairs their device with the seat, the previously configured data can be seamlessly transferred and applied to the seatback system. This approach not only improves user convenience but also helps reduce interaction time during flight.

Note: For platform-specific implementation details on how to set up and store user profile and preferences pre-flight, refer to the respective Android and iOS developer guides.

Step 2: Sending Data to the Seatback#

After the transfer service is initialized, developers can begin pushing actual content—user profile and preferences—to the seatback. The SDK provides APIs to send these as a key-value object.

Two major types of data can be sent:

Transferring User Profile Data

User profile data includes basic passenger information such as: First name, Last name, Gender, etc.

Developers need to initialize the profile service, configure the necessary profile properties, and—if the Sync Engine is available—optionally perform synchronization with the seatback system. After setting the profile, the data is prepared for transfer—on iOS, it is serialized into a dictionary, while on Android, it is converted into a JSON object—before being sent to the seat.

Transferring User Preferences

Preferences reflect how the user wants to interact with the system—for example, content filters, accessibility features, or preferred genres.

After initialization of user preference service , the developer can set values such as:

  • Preferred content types (e.g., "media.video.movie")

  • Preferred genres

  • Preferred Language

As with the profile service, this data can either be synchronized using the Sync Engine or directly serialized and transferred to the seat.

Optional Synchronization (Sync Engine)#

Both the User Profile and Preferences services support optional synchronization with the seat. This is only available if the aircraft’s IFE system includes the Sync Engine component.

When synchronization is used:

  • Conflicts between PED and seat data (e.g., changed names or settings) can be resolved using conflict resolution APIs.

  • After resolving any conflicts, the data is written back and becomes active on both ends.

If Sync Engine is unavailable, developers must skip the sync call and simply serialize the data and send it directly to the seat.

Note: Syncing is not mandatory for data transfer. The documentation provides guidance on when to skip it.

Step 3: Transmitting Serialized Data to the Seat#

Once the profile or preference data has been configured and optionally synced, the final step is to serialize the data and send it to the seat using the Seat Property Transfer API.

Step 4: Receiving Properties on the Seat#

Once pairing between the PED and seatback system is established, the seatback application is capable of receiving data transmitted from the PED. This data typically includes user profile details, personal preferences (such as language or parental rating), and optional display messages.

The seatback system listens for incoming data sent from the PED, and when received, processes the information structured in a predefined format. The received content is categorized into three groups—user profile, user preferences, and display messages—each containing relevant properties set by the PED app.

This personalized data can then be used by the seatback application to tailor the in-flight experience. For instance, it can apply the user's preferred language automatically, configure parental control settings, and display a welcome message using the passenger’s name. This enhances continuity and personalization across devices, ensuring the user’s preferences follow them from their phone to the seatback screen.

Version 1.0