Messaging is an information transfer with a specific person or persons.
A text message provides transport for messaging.
The addressing and routing used in messaging provides for authentication of the sender and recipient.
WAI provides the directory-lookup, authentication of participants, authorizes and routes messages
using a WAIFIND server instance.
Text Message
A text message provides a universal exchange of a chosen language (e.g. English.) Graphical messages are not provided except as a file transfer - a optional feature. A WAI user device will attach an audio file for speech-to-text processing as a basic attribute of a text message input (or what is sent by a WAI user.) A WAI user device may attach an audio file, either from text-to-speech processing or as it was received, as a basic attribute of a text message output (or what is received by a WAI user.) There is no limit to the length of the text message.
Font attributes: Bold, underline, and italic
Message attributes: Subject, Heading, Message text, Time tags, Sender, Recipient(s), Audio file
Directory Lookup
The applicable WAIFIND server instance provides each WAI user a directory of available recipients for the proximate facility. The listing is based on the WAI user role. A WAI user carries categorical classifications based on their profile. The WAI user profile is only securely established by the WAIFIND server. The central WAIFIND server manages a certificate based distribution of user profiles that depends on a connected infrastructure. Only on-line WAIFIND server instances serving a facility can securely reveal a participating WAI user's attributes.
Off-line WAIFIND server instances necessarily are compromised with the concern of rogue, masquerading WAIFIND server instances. Each off-line WAIFIND server must be registered with the central WAIFIND server. A series of certificates is distributed to each WAI user device as a part of their continual provisioning while they are on-line, which is optimized for the regions the user device is located. Only recognized off-line servers that pass WAIFIND off-line authentication are able to communicate with WAI user devices. WAI user devices automatically register the detection of any rogue WAIFIND server, as well the local off-line WAIFIND server. The WAI user devices and the local WAIFIND server upload security logs whenever they are on-line. Every WAIFIND server must login to the central WAIFIND server regularly to remain authorized and relevant.
Authentication and Routing
Each WAI user connects to a WAIFIND server that is managing the facility they are within. The WAIFIND server authenticates each WAI user and reveals their profile and authorized services.
The WAI user device may access the directory to lookup facility support addresses. For example, the user device may list facility customer support, local gate agents, medical assistance, law enforcement.
A WAI user device authorized for facility support can receive messages from WAI users and respond to them, or direct messages to specific user or users. For example, a gate agent may direct messages to a group of passengers advising them to board the airplane.