Skip to content

Pairing Overview#

The Seat Pairing Framework, provided by the Companion App SDK, enables passengers to pair their PED (Personal Electronic Device) with the Seatback Monitor in the InFlight Entertainment (IFE) system. When paired, passengers can control media playback, manage seat preferences and view or share content between the PED and the seatback monitor.

Seat Pairing Overview

Process Overview#

Initialize the Pairing Service#

Before pairing can occur, the pairing service must be initialized on the passenger's PED. This is done using the method seatpairing init service. After this service is successfully initialized, it sets a callback mechanism to handle pairing events, such as success and failure. The seatpairing object provides the Companion App access to all methods for pairing.

Pairing Options#

The Seat Pairing Framework provides three pairing modes:

  • Passcode Mode - allows for manual entry of a passcode.

  • QR Code Mode - allows passenger to scan a QR code.

Developers need to integrate these modes based on the passenger's preference and the capabilities of the seatback monitor.

Passcode Mode#

In Passcode Mode, passengers can start pairing from either the PED or the seatback monitor.

  • **Initiated from the PED

    • The passenger selects their seat number, and the app calls initiate pairing with seat number.

      • This triggers the seatback monitor to display a passcode.
    • The passenger then enters this passcode in the PED using the pair with passcode method.

      • This completes the pairing process.
  • Initiated from the Seatback Monitor:

    • The passenger selects the pairing option seatback.

      • The seatback monitor displays a passcode
    • The passenger enters the passcode on the PED.

      • The app calls pair with passcode.

      • This completes the pairing process.

QR Code Mode#

QR code is displayed on the seatback monitor. The passenger scans the QR code with their PED, which automatically triggers a deep link in the Companion App. From there, the app calls pairing method and pass the passcode retrieved through deeplinking. Verify the Companion App manifest file (Android) is set up to handle deep linking. This allows scanning the QR code to smoothly transition the passenger to the pairing interface.

NOTE: Scanning the QR code redirects the PED to the portal. Therefore, to support QR code-based seat pairing, the portal content must be loaded on the rack. Kindly reach out to PAC focal for further assistance.#

Unpairing from the Pairing Service#

Unpairing can be initiated from either the PED or seatback monitor. This provides flexibility for passengers to end their session when they like. Developers can unpair from either the PED or Seatback Monitor.

  • From the PED, the app can include an option to disconnect, calling the appropriate API to stop communication between the two devices.

  • Alternatively, the seatback monitor can provide a similar option, giving passengers control from either interface.

Listener Notification#

Event dispatched when a device pair status has changed#

  • **Parameters

    • iOS - PACSeatPairingPairStatusDidChangeNotification

    • Android - SeatPairingStatusChangedListener

  • **Description

This event triggers whenever a change occurs in the pairing status between the PED and seatback monitor. This change could be a successful pairing, disconnection or any update in the device's state.

Event dispatched when a user rejects a pair request on a seatback monitor#

  • **Parameters

    • iOS :- PACSeatPairingDidRejectInitiatePairNotification

    • Android:- SeatPairingInitiatePairRejectedListener

  • **Description

This event is triggered when a user manually rejects a pairing request that was initiated on the seatback monitor. It could be a security measure or simply a user decision to prevent pairing.

Event dispatched when a user changes pairing mode to pair to a seatback monitor#

  • **Parameters

    • iOS :- PACSeatPairingDidPairModeChangeNotification

    • Android:- SeatPairingStatusChangedListener

  • **Description

This event is triggered when a user manually switches the seatback monitor to pairing mode is triggered. For example, a user pairs a device and initiates the pairing mode from the seatback monitor.

Handling Temporary Device Blocking Errors#

During the seat pairing process, if a device exceeds the allowed number of consecutive pairing failures within a specific time period, it will be temporarily blocked to prevent repeated invalid attempts. It depends on the number of attempts defined in db. When this happens, you will encounter the following errors:

  • iOS: PACSeatPairingPairErrorTemporarilyBlocked

  • Android: SEAT_PAIRING_ERROR_TEMPORARILY_BLOCKED

Reference: Please refer PACSeatPairingPairErrorCode in Apple's documentation and SeatPairingV1.Error in Java documentation to understand how this error integrates with seat pairing APIs.#

This indicates that the PED (Passenger Electronic Device) is temporarily blocked from initiating further seat pairing requests. By default, the block duration is 3600 seconds (1 hour), after which the device will automatically be unblocked and allowed to attempt pairing again.

Note: In case you want to change this value, Kindly contact your Panasonic focal for assistance.#

Version 1.2