Wi-Fi

The simplest WAI installation uses a local WAIFIND server and a COTS Wi-Fi access points.  Without continuous access to the Central WAIFIND server, the local WAIFIND server must manage registration of user devices autonomously. Without BLE, positioning is not feasibly, other than rudimentary proximity to Wi-Fi access points.   

An example of the Wi-Fi only configuration is on an airplane, where registration accepts any user device on the premise that they are all passenger devices.  The Wi-Fi infrastructure is provided as a part of In-flight Entertainment (IFE).

Bluetooth

Bluetooth Low Energy (BLE) beacons provide a unique Identity that applications apply a receive signal strength measurement that is indicative of the distance from the beacon. With this information, an estimated local wireless position can be determined using trilateration.  A database can relate the wireless position into a physical location.  Thus BLE adds wayfinding features, as well as support for position-triggered routing and alerts.  Some IFE supports bluetooth in the seat, primarily for passenger headphones, that will introduce many bluetooth access points that can at least be used as beacons.

Inflight WAI Architecture (2).png

Bluetooth access points offer another interactive connection to user devices. The user device may prefer Wi-Fi networks that do not provide a connection to the local WAI server nor the central WAI server without buying an Internet Access Session.  In these cases, and otherwise, a network of Bluetooth access points may provide a low cost solution without depending on Wi-Fi at all.

Internet

Having access to the Internet offers a extensible solution that has no local WAI infrastructure.  The User Device WAI application communicates with the WAIFIND central server.  In this case, the Facility WAIFIND server is hosted in the WAIFIND central server as a remote/virtual feature.  WAIFIND and the user community complete the database for wayfinding.