Patent Description:
The present disclosure relates to systems for transferring information between a vehicle based user device and a server to validate a user's identity before granting internet access to the user device.

In-flight entertainment and connectivity (IFE or entertainment) systems have been deployed onboard aircraft to provide entertainment, such as internet access, movies, television, audio entertainment programming, electronic games, and other electronic content to passengers. IFE systems are increasingly using wireless devices that can be operated by passengers to display content from the internet. Such user devices can include passenger electronic devices (PEDs) that are transported onto the aircraft by the passengers and seat video display units (SVDUs) that may be in communication with passenger control units (PCUs) supplied as aircraft equipment. Such PEDs can include cellular phones, tablet computers, laptop computers, wireless headphones, etc. Passengers can operate the user devices to connect to the internet and select internet content for playback or display through the user devices.

Some government regulations require verification of the identity of a person prior to granting internet access to that person. For example, Chinese regulations require that Internet Service Providers (ISPs) collect government issued identification information of an individual (e.g., passport number, full name, address, date of birth, etc.) before internet service can be provided to the individual. In China, for example, an ISP manually collects the individual's government issued identification information, validates the information (e.g., by manually inspecting the government identification document), and manually inputs validation of the individual's government identification into the ISP's system. This process, however, is not feasible inside an aircraft or other vehicle.

The scope of the invention is defined by independent claims related to an entertainment system according to claim <NUM> and a corresponding method according to claim <NUM>.

The present disclosure also describes a ground based server that can retrieve user identity or internet subscription plan information for user devices that were connected to the internet while located in a vehicle. The ground based server includes a repository that stores internet session information for user devices having onboard internet protocol addresses mapped to an internet protocol address for a vehicle based server. The ground based server includes a processor that receives requests from a second server for the identity of users of the user devices having the onboard internet protocol addresses mapped to an internet protocol address for the vehicle based server. From the information in the request, the ground based server retrieves the user identities or the users' internet subscription plan information for the identified user devices. The ground based server communicates the user identities or the users' internet subscription plan information to the second server.

Other systems, servers, processors and/or corresponding methods according to embodiments of the inventive subject matter will be or become apparent to one with skill in the art upon review of the following drawings and detailed description. It is intended that all such additional systems, servers, processors and/or corresponding methods be included within this description, and be protected by the accompanying claims provided they fall within their scope. Moreover, it is intended that all embodiments disclosed herein can be implemented separately or combined in any way and/or combination.

Other features of embodiments will be more readily understood from the following detailed description of specific embodiments thereof when read in conjunction with the accompanying drawings, in which:.

In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. In other instances, well-known methods, procedures, components and circuits have not been described in detail so as not to obscure the present invention. It is intended that all embodiments disclosed herein can be implemented separately or combined in any way and/or combination.

Various embodiments of the present disclosure are directed to innovative ways for transferring information between a user device, a ground based computer server and/or an aircraft based or other vehicle based computer server to validate a user's identity or internet subscription plan before granting internet access to a user's user device. Although embodiments herein are primarily described in the context of transferring data to and/or from an aircraft based server that is part of an IFE system deployed onboard an aircraft, the invention is not limited thereto. Instead, these and other related embodiments may be used to transfer data to and/or from servers located in other types of vehicles, including without limitation, trains, automobiles, cruise ships, and buses.

Various embodiments are explained below in the non-limiting context of validating a user's identity using travel information of the user. Although embodiments herein are primarily described in the context of travel information for airline flights, the travel information is not limited thereto. Instead, these and other related embodiments may be used for travel information associated with other types of vehicles, including without limitation, trains, automobiles, cruise ships, and buses.

Various embodiments of the present disclosure are explained below in the non-limiting context of validating the identity of passengers using user devices before granting the user devices access to the internet. Although embodiments herein are primarily described in the context of passengers of a vehicle, the invention is not so limited. The passengers include crew members and other representatives of the vehicle operators, including without limitation, employees and representatives of airline, train, automobile, cruise ship, and bus operators.

Various embodiments are explained below in the non-limiting context of an IFE system that includes user devices. The user devices include passenger electronic devices (PEDs) and seat video display units (SVDUs) that may be mounted to structures within the aircraft, including to seatbacks, seat armrests/frames, bulkheads, overhead structures etc. and communicate through Bluetooth connections with user terminals, which are also referred to as passenger control units (PCUs) and passenger electronic devices (PEDs). The PEDs can be transported onto the aircraft by the passengers and include mobile phones, tablet computers, laptop computers, wireless Bluetooth headphones, etc. The PCUs can be supplied as aircraft or vehicle equipment. The user terminals and SVDUs each include Bluetooth transceivers that are configured to transmit and receive radio frequency (RF) signals, such as in the ISM band.

<FIG> illustrates an aircraft fuselage <NUM> containing an IFE system that provides entertainment services and connections to passengers. The IFE system can include a server <NUM> that can stream and/or download electronic content from the internet through wired networks (e.g., Ethernet) and/or through wireless access points (WAPs) <NUM> to user devices <NUM>, including PEDs that are transported by passengers and/or crew members onboard and off the aircraft <NUM>. The server <NUM> may additionally stream and/or download electronic content from the internet through WAPs <NUM> to seat video display units (SVDUs) 110c. Server <NUM> has a unique internet protocol (IP) address assigned to it by an internet service provider (ISP) for internet services provided onboard the aircraft. The IP address for server <NUM> is stored in the ISP's ground system, including an association between the IP address for server <NUM>, the tail number of the aircraft <NUM> and the identity of the airline operating the aircraft <NUM> on which server <NUM> is installed. A network translation router (NAT) <NUM> is configured to route communication packets between a user device <NUM>, server <NUM> and/or a ground based server <NUM>. The network translation router <NUM> assigns a unique onboard IP address to each user device <NUM> onboard the aircraft <NUM>, and maps each IP address to the IP address for the aircraft <NUM>, as further disclosed in more detail below.

Passengers may be provided internet services to the user devices <NUM> through aircraft based server <NUM>. The server <NUM> may be communicatively connected to the user devices <NUM> through a wired data network (e.g., Ethernet cabling and electronic network interfaces) and/or a wireless data network. An example wireless data network is described in <FIG> that includes a plurality of WAPs <NUM> that are installed (mounted) at spaced apart locations within the aircraft <NUM> fuselage to provide corresponding wireless communication cells. The WAPs <NUM> communicate through a wireless air interface that can be based on one or more communication protocols including, without limitation, any one or more of IEEE <NUM>, WIMAX, 3GPP Long Term Evolution (LTE), etc..

The user devices <NUM> can include, without limitation, tablet computers, laptop computers, palmtop computers, cellular smart phones, media players, SVDUs, etc. When owned by a passenger, a user device <NUM> can also be referred to as a passenger electronic device (PED). Each of the user devices <NUM> is assigned a unique onboard IP address by NAT <NUM> that is used for routing communications through the IFE system and to ground based servers.

Some or all of the seats of the aircraft <NUM> may be associated with a docking station may have a wired interface. An SVDU 110c facing the seat includes a processor that is connected to communicate through a Bluetooth transceiver and through the wired interface of the docking station. A PCU can include a processor connected to communicate through a wired interface and to communicate through a Bluetooth transceiver. The PCU may be configured to be releasably docked in the docking station to communicatively connect the wired interfaces of the PCU and the docking station. While docked in the docking station the processor of the PCU and the processor of the SVDU are configured to communicate through the wired interfaces of the PCU and the docking station to establish a Bluetooth connection between the Bluetooth transceivers of the PCU and the SVDU. The processor of the PCU may be configured to not operate to establish the Bluetooth connection using communications through the Bluetooth transceiver of the PCU while docked in the docking station. Accordingly, a Bluetooth connection between a pair of Bluetooth transceivers in a PCU and a SVDU 110c can be establish through wired communications via the docking station, and subsequent communications while the Bluetooth connection is maintained (e.g., unrelated to establishing the Bluetooth connection) are then performed through the Bluetooth transceivers.

Referring to <FIG> and <FIG>, in accordance with various present embodiments, the system includes a central Bluetooth connection controller <NUM> that is communicatively connected to the SVDUs 110c through a wired network, such as Ethernet, and/or through the WAPs <NUM> via a wireless network such as WiFi <NUM>. The central Bluetooth connection controller <NUM> is configured to control setup, maintenance, and/or termination of Bluetooth connections between the SVDUs 110c and the PCUs.

The aircraft <NUM> may also include a satellite link interface <NUM> that is configured to provide wireless data communications through a satellite communication system and/or through direct aircraft-to-ground communication links. The satellite data link interface <NUM> may be any satellite connectivity system that provides data communications capabilities for aircraft within range of satellite based communications network equipment, using radio transceiver circuits located onboard the aircraft. The wireless communications may be performed using IEEE <NUM>, WIMAX, and/or 3GPP LTE technologies, etc. A communication link can be established, for example, between the aircraft based server <NUM> and a ground based server <NUM> via the satellite network.

The aircraft <NUM> may also include a ground data link interface <NUM> that is configured to provide wireless data communications through a satellite communication system and/or through direct aircraft-to-ground communication links. The ground data link interface <NUM> may be any ground connectivity system that provides data communications capabilities for aircraft within range of ground based communications network equipment located at airports, using radio transceiver circuits located onboard the aircraft and at airports (e.g., at gate locations). The wireless communications may be performed using IEEE <NUM>, WIMAX, and/or 3GPP LTE technologies, etc. The aircraft can be recognized by the ground network when it arrives at an airport or gate, and a communication link can be established between the aircraft based server <NUM> and a ground based server <NUM> via the ground network.

<FIG> is a block diagram of the IFE system of <FIG> having elements that are configured to operate in accordance with some embodiments of the present disclosure. Referring to <FIG>, the IFE system includes system devices that can be located at each passenger seat location, and which is configured to communicate with various types of user devices that can be provided by the airline and/or carried on-board by passengers. The seat-located system devices can communicate using RF resources within the ISM band with the PCUs using a Bluetooth (BT) scatternet wireless network <NUM> and may use an IEEE <NUM>. 11ac wireless network <NUM>. The example user devices include PEDs 110a having both a Bluetooth transceiver and a IEEE <NUM> (WiFi) transceiver and other user devices 110b having a Bluetooth transceiver.

The system devices can include a SVDU 110c, a dockable wireless controller 200c, and a dockable PCU 200d. The system may include only one or both of the dockable wireless controller 200c and the dockable passenger control unit 200d, which may be the same or similar type of device or may be different types of devices, and which can be collectively referred to as wireless controllers. The dockable wireless controller 200c and the dockable PCU 200d can be operated by a passenger to wirelessly control the SVDU 110c, such as to select internet content that is consumed (e.g., played through a display device), select among menu items, and control other operations of the SVDU 110c. Audio content may be streamed through the Bluetooth connection from the SVDU 110c to a user device, e.g., Bluetooth headphones. Pictures, video, textual information, and/or commands may be communicated from the SVDU 110c to a user device through the Bluetooth connection.

The example SVDU 110c includes a display device, video display circuitry, a general-purpose processor, a Bluetooth transceiver, and an Ethernet interface or other wired network interface. The dockable wireless controller 200c includes a general-purpose processor, a Bluetooth transceiver, and a dock wired interface, and may include display circuitry connected to a display device, and audio decoding circuitry connected to a wired headphone jack and/or the Bluetooth transceiver for wireless communication with a passenger's wireless headset. The dockable PCU 200d can similarly include a general-purpose processor, a Bluetooth transceiver, and a dock wired interface, and may include display circuitry connected to a display device, and audio decoding circuitry connected to a wired headphone jack and/or the Bluetooth transceiver for wireless communication with a passenger's wireless headset. The wireless controller 200c, the passenger control unit 200d and dockable passenger control unit 200d, collectively referred to as wireless controller <NUM>, may be configured as handheld devices for operation by passengers and can be stored in docking stations, which may be configured to recharge batteries within the handheld devices. A wireless controller <NUM> may be a handheld device that is owned by the aircraft operator and provided for temporary use by a passenger during a flight, or may be a PED carried on-board by passengers, such as mobile phones, tablet computers, laptop computers, wireless headphones, etc..

The seat-located system devices are connected to host infrastructure that can include the cabin WAPs <NUM> spaced apart within the aircraft cabin and mounted to cabin ceiling structures, storage bin structures, bulkheads, etc. An Ethernet backbone network <NUM>, e.g., <NUM> Base-T Ethernet, extends throughout the aircraft cabin to communicatively interconnect the seat-located system devices to the server <NUM> and the WAPs <NUM>. The WAPs <NUM> can each include an <NUM>. 11ac or other WiFi transceiver and an Ethernet interface that connects to the Ethernet backbone network <NUM>.

The host infrastructure can include a PCU docking station <NUM>, a wireless controller charging station <NUM> (although its functionality may be incorporated into the docking station <NUM>), and a remote audio unit <NUM>. The wireless controller charging station <NUM> may be located at each seat and have a dock interface that releasably stores the dockable wireless controller 200c and charges a battery therein, and has an Ethernet interface that connects to the Ethernet backbone network <NUM>. The PCU docking station <NUM> may also be located at each seat and have a dock interface that releasably stores the dockable PCU 200d and charges a battery therein, and has an Ethernet interface that connects to the Ethernet backbone network <NUM>.

The SVDU 110c facing a seat includes a processor that is connected to communicate through a Bluetooth transceiver and through the wired interface of the docking station <NUM>. A wireless controller (PCU) <NUM> includes a processor connected to communicate through a wired interface and a Bluetooth transceiver. The wireless controller <NUM> is configured to be releasably docked in the docking station <NUM> to communicatively connect the wired interfaces of the wireless controller <NUM> and the docking station <NUM>. While docked in the docking station <NUM> the processor of the wireless controller <NUM> and the processor of the display unit 110c may be configured to communicate through the wired interfaces of the wireless controller <NUM> and the docking station <NUM>, via a dock-station physical interconnects (e.g., wired connections) <NUM>, to establish a Bluetooth connection between the Bluetooth transceivers of the wireless controller <NUM> and the display unit 110c. The processor of the wireless controller <NUM> may be configured to not operate to establish the Bluetooth connection using communications through the Bluetooth transceiver of the wireless controller <NUM>. Accordingly, a Bluetooth connection between a pair of Bluetooth transceivers in a wireless controller <NUM> and a SVDU 110c is establish through wired communications and subsequent communications while the Bluetooth connection is maintained are then performed through the Bluetooth transceivers.

The system further includes the central Bluetooth controller <NUM> that is communicatively connected to the SVDUs 110c through the Ethernet backbone network <NUM> and/or through the WiFi <NUM> network <NUM>.

The remote audio unit <NUM> may be located at each seat or adjacent to a group of seats, and can contain a wired headphone jack, a Bluetooth transceiver, and an Ethernet interface that connects to the Ethernet backbone network <NUM>, to receive and play audio through a loudspeaker and/or through the Bluetooth transceiver and/or the wired headphone jack to a headset worn by one or more passengers.

Some government regulations require verification of the identity of an individual prior to granting internet access to that individual. For example, Chinese regulations require that Internet Service Providers (ISPs) collect government issued identification information of an individual (e.g., passport number, full name, address, date of birth, etc.) before internet service can be provided to the individual. In China, for example, an ISP manually collects an individual's government issued identification information, validates the information (e.g., by manually inspecting the government identification document), and manually inputs verification of the individual's government identification into the ISP's system. This process is not feasible onboard an aircraft.

When a passenger makes a purchase or request to access internet service while onboard an aircraft, a representative of the ISP for the aircraft's internet service is not onboard the aircraft to validate the passenger's identity. Additionally, when a passenger makes a request to access the internet, the relationship between the passenger's identity and identifying information of the passenger's user device (e.g., IP address) is not known to the ISP for the aircraft. In the absence of validation of that relationship, internet access cannot be granted. For example, a passenger may use a PED carried onboard the aircraft to access the internet over the aircraft's Wi-Fi network or Ethernet. The association between a passenger's identity and the identity of the PED (e.g., mobile phone number, media access control (MAC), Internet Protocol (IP) address for the PED, etc.), however, is not known to the ISP for the aircraft. A passenger may also use an SVDU and PCU onboard the aircraft to access the internet over the aircraft's Wi-Fi network or IFE system. However, the association between the passenger's identity and the identity of the aircraft's PCU (e.g., MAC or IP address, etc.) is not known to the ISP providing internet services inside the aircraft. Alternatively, a passenger may have an established internet subscription plan prior to boarding an aircraft. In this circumstance, the association between the passenger identity and the internet subscription is known to the ISP of the subscription plan, but the association is not known to the ISP for the aircraft. For this and other reasons, various embodiments disclosed herein are directed to transferring information among a user device <NUM>, a ground based computer server <NUM>, and/or an aircraft based or other vehicle based computer server <NUM> to validate a user's identity or internet subscription plan before granting a user device <NUM> of the user access to the internet.

<FIG> is a block diagram illustrating operational components of an aircraft based IFE system, satellite communication links, air-to-ground communication links, and ground based servers in accordance with some embodiments of the present disclosure. Referring to <FIG>, when a passenger buys a flight ticket, the passenger is required to provide government identification information. The government identification ("government identity") information may identify any one or more of: passport number, name, home mailing address, birth date, telephone number, government issued identifier for the person, etc. Passenger travel information for the purchased flight and the government identification information is stored with a logical association to each other in a data structure of a database, such as an airline ground based server <NUM>. The passenger travel information ("travel information") may identify any one or more of: passenger name, flight number, passenger ticket number, airline frequent flyer membership information, etc..

Referring to <FIG> and <FIG>, in one embodiment, after the passenger boards the aircraft, the passenger operates a user device <NUM> to connect to the onboard IFE system through WAP <NUM> or the Ethernet. A network address translation router <NUM> assigns a unique onboard IP address to the user device <NUM> for the duration of the flight. The network address translation router <NUM> is configured to map the assigned onboard IP address of the user device <NUM> to the ground IP address assigned to server <NUM>. The network address translation router <NUM> may maintain a mapping table that programmatically associates the onboard IP addresses for each user device <NUM> with the ground IP address assigned to server <NUM>. As a result, each user device <NUM> is uniquely identified by the aircraft ISP's ground network IP address during the time period that each user device <NUM> accesses the internet during the flight.

A passenger operates a user device <NUM> having an assigned onboard IP address to request access to the internet. The request includes passenger travel information for the purchased flight and a request to access the internet. The travel information and the request for internet service may be communicated to server <NUM> in one or separate messages and is collectively referred to herein as a request. Server <NUM> communicates the request to the ground based server <NUM> via satellite communications network interface <NUM> and satellite communications links <NUM> and <NUM> or via ground network interface <NUM> and air-to-ground communication links <NUM> and <NUM>.

Responsive to the request, ground based server <NUM> generates a connection authorization decision. More particularly, ground based server <NUM> receives the request and uses the passenger's travel information to validate the passenger's identity stored in server <NUM>. The ground based server <NUM> is configured to correlate the passenger's travel information to the passenger's government identity information. The server <NUM> may maintain a mapping table that programmatically associates the passenger's travel information to the passenger's government identity information. In some embodiments, to protect the security of the passenger's government identity information, ground server <NUM> does not communicate the passenger's identity to the aircraft <NUM>. Responsive to the request, if a passenger's government identity information is missing or otherwise not validated by server <NUM>, ground based server <NUM> generates a connection authorization decision to deny the passenger's user device <NUM> access to the internet. Responsive to the request, if the passenger's government identity information is validated by ground server <NUM>, ground based server <NUM> generates a connection authorization decision to grant the passenger's user device <NUM> access to the internet and generates a unique internet session token. Ground based server <NUM> communicates the connection authorization decision and token to server <NUM> via satellite communications links <NUM> and <NUM> and satellite interface <NUM>. Alternatively, ground based server <NUM> communicates the connection authorization decision and token to server <NUM> via ground communication links <NUM> and <NUM> and air-to-ground interface <NUM>. The connection authorization decision includes the assigned onboard IP address for the user device <NUM>. The network address translation router <NUM> routes the connection authorization decision through server <NUM> to the user device <NUM>. When the connection authorization decision authorizes a connection to the internet for the user device <NUM>, server <NUM> is configured to connect user device <NUM> to the internet through the onboard Ethernet or through WAP <NUM>. Server <NUM> is configured to monitor and collect internet session information of the user device <NUM>, including but not limited to the unique session token associated with the assigned onboard IP address of the user device <NUM>, as further explained below.

In other embodiments, when a passenger operates a user device <NUM> to request access to the internet, a vehicle based server performs the validation and generates a connection authorization decision, as explained in further detail below with reference to <FIG>.

<FIG> is a block diagram of operational components of the aircraft based server <NUM> of <FIG> and <FIG> that processes and transfers data between a user device <NUM>, a ground based server <NUM>, and/or an aircraft based server <NUM> in accordance with some embodiments of the present disclosure.

Referring to <FIG>, after a passenger boards aircraft <NUM>, the passenger operates a user device <NUM> having a unique onboard IP address assigned by network address translator <NUM> to make a request for internet access. The aircraft based server <NUM> receives the request (block <NUM>) from the user device <NUM>, which includes the onboard IP address assigned to user device <NUM>. The server <NUM> may communicate via network interface <NUM> and wired connections to some onboard user devices <NUM> and/or wireless connections to other onboard user devices <NUM>. Wired communication links may be established using network interfaces (e.g., USB ports) located at passenger seats, which may be connected to seat video display units 110c at each seat location. Wireless communication links may be established through WAPs <NUM>. Some user devices may wirelessly communicate directly with the WAPs <NUM>. Some other user devices <NUM> may wirelessly communicate indirectly with the WAPs <NUM> via seat video display units 110c which relay communications directly between those user devices <NUM> and the WAPs <NUM>. Still some other user devices may communicate through wired connections to the seat video display units 110c (e.g., via USB ports) which relay data through wireless links with the WAPs <NUM>.

In one embodiment, the aircraft based server <NUM> transfers the request (block <NUM>) through the aircraft satellite data interface <NUM> to ground based server <NUM> via satellite communications links <NUM> and <NUM>. Alternatively, the aircraft based server <NUM> communicates (block <NUM>) the request through an aircraft air-to-ground data interface <NUM> to ground based server <NUM> via air-to-ground communications links <NUM> and <NUM>.

Continuing with <FIG>, in further operations, the aircraft based server <NUM> receives a connection authorization decision (block <NUM>) from ground based server <NUM> denying or authorizing internet access to user device <NUM> and provides an applicable token based on server <NUM>'s validation of the user's government identity. When the server <NUM> is unable to validate the user's government identity, the connection authorization decision denies internet access to user device <NUM>. Server <NUM> is configured to deny a connection between the user device <NUM> and the internet. When server <NUM> is able to validate the user's government identity, the connection authorization decision authorizes internet access to the user device <NUM>. Server <NUM> is configured to connect (block <NUM>) the user device <NUM> to the internet through a WAP(s) <NUM> or through a wired connection. When the internet connection is authorized, ground based server <NUM> communicates (block <NUM>) to server <NUM> a unique internet session token for the user device <NUM> for associating internet session information of the user device <NUM> with the assigned onboard IP address for the user device <NUM>. While the user device <NUM> is connected to the internet, server <NUM> communicates (block <NUM>) an internet session message for the user device <NUM> to ground based server <NUM>. The internet session message may include, but is not limited to, one or more of a media access control address (MAC) address for the user device <NUM>, the assigned onboard IP address for the user device <NUM> mapped to the ground IP address of the vehicle based server, internet session start and termination time in Coordinated Universal Time (UTC) for the user device <NUM>, and/or the unique session token shared between server <NUM> and ground based server <NUM> for user device <NUM>.

<FIG> is a block diagram of operational components of the ground based server <NUM> of <FIG> that generates connection authorization decisions, generates the session information token used to uniquely identify session information for a user device <NUM> when connected to the internet, stores and provides a passenger's government identity and travel information, and stores and provides internet session information for user devices <NUM> connected to the internet during a flight, in accordance with some embodiments of the present disclosure. Server <NUM> includes a validation and compliance processor <NUM>, a network interface <NUM>, a session log repository <NUM>, and may include a passenger aircraft reservation repository <NUM> that will be explained in further detail below.

Referring to <FIG> and <FIG>, server <NUM> receives a request (block <NUM>) for internet access from a user device <NUM> having a unique onboard IP address assigned by NAT <NUM>. Responsive to the request, server <NUM> generates (block <NUM>) a connection authorization decision and a unique session token when the connection is authorized. Ground based server <NUM> uses passenger travel information from the request to retrieve the passenger's government identity from a passenger aircraft reservation repository <NUM>. Ground based server <NUM> is configured to validate the passenger's government identity from the correlation between the passenger's travel information and the passenger's government identity information stored in repository <NUM>. The aircraft reservation repository <NUM> may be included in server <NUM> or may be a separate repository in communication with server <NUM>. When the passenger's government identity information is successfully retrieved from the passenger aircraft reservation repository <NUM>, ground server <NUM> generates (block <NUM>) an internet connection authorization decision for the user device <NUM> that originated the request. When the passenger's government identity is not validated, ground server <NUM> generates a message denying the request for internet service to the originating user device <NUM>. The connection authorization decision is communicated to server <NUM> via satellite communications links <NUM> and <NUM> and satellite communication interface <NUM>, and from server <NUM> to user device <NUM> via the aircraft's Wi-Fi or Ethernet network. If the passenger's government identity is validated, ground based server <NUM> also generates a unique internet session token (block <NUM>) for user device <NUM>. Ground based server <NUM> communicates (block <NUM>) the connection authorization decision and applicable token to server <NUM> via satellite communications links <NUM> and <NUM> and satellite communications interface <NUM>. Server <NUM> is configured to connect the user device <NUM> to the internet through the aircraft's Wi-Fi network or Ethernet. Server <NUM> uses the internet session token to associate internet session information with the onboard IP address assigned to user device <NUM>. Alternatively, as shown in <FIG>, air-to-ground and Wi-Fi communication links <NUM> and <NUM> may be used in place of satellite communication link <NUM> and <NUM>. Server <NUM> monitors the internet session of user device <NUM> and generates an internet session message for user device <NUM> to ground based server <NUM>. Ground based server <NUM> receives (block <NUM>) the internet session message for user device <NUM> and stores the message in a session log repository (block <NUM>).

In a further embodiment, as described in more detail below, ground based server <NUM> receives a request (block <NUM>) to provide the government identity of a user of a user device <NUM> that was connected to the internet during a flight. Responsive to the request, ground server <NUM> accesses the session logs repository <NUM> and retrieves (block <NUM>) the session information for the identified user device <NUM>. Ground based server <NUM> is configured to retrieve the government identity of the user of the user device <NUM>. The server <NUM> may maintain a mapping table that programmatically associates the passenger's validated government identity information to the unique session token for the user device <NUM>.

Various further operational embodiments are now described in the context of <FIG> which is a combined flowchart and data flow diagram that illustrates operations and data transfers between a user device <NUM>, the aircraft based server <NUM>, and the ground based server <NUM>. In the example embodiment, a passenger purchases a flight using their government issued identity (block <NUM>). During the flight reservation process or separate therefrom (e.g., during a flight check-in process), the reservation system cooperatively identifies the passenger government identity and travel information to ground based server <NUM>, which stores (block <NUM>) the information.

The passenger boards the reserved flight and operates a user device <NUM> to connect (block <NUM>) to server <NUM> through the onboard IFE system. Server <NUM> connects to the user device <NUM> and receives (block <NUM>) a unique onboard IP address assigned to the user device <NUM> by the network address translation router <NUM> for the duration of the flight.

The passenger operates (block <NUM>) the user device <NUM> to request access to the internet. Server <NUM> receives (block <NUM>) the request for internet access. Responsive to the request, server <NUM> transfers (block <NUM>) the request to server <NUM> to validate the government identity of the passenger. The request is transferred to server <NUM> through a network connection and/or an off-board communication link that is determined to be available through satellite datalink interface <NUM> or ground datalink interface <NUM>. The request includes travel information and the assigned onboard IP address for the user device <NUM> mapped to the IP address for server <NUM>. Server <NUM> receives (block <NUM>) the request. Responsive to the request, server <NUM> responds to the request and generates (block <NUM>) a connection authorization decision that includes the assigned onboard IP address for the user device <NUM> mapped to the IP address for server <NUM>. If the passenger government identity is validated, server <NUM> provides (block <NUM>) a unique session information token that includes the assigned onboard IP address for the user device <NUM> mapped to the IP address for server <NUM>. Server <NUM> communicates (block <NUM>) the connection authorization decision and any provided session information token to server <NUM>. The aircraft based server <NUM> receives (block <NUM>) the connection authorization decision and any session information token from server <NUM>. Responsive to the connection authorization decision, if the passenger government identification was validated, server <NUM> is configured to connect (block <NUM>) the user device <NUM> to the internet via wireless access point <NUM> or the Ethernet. Responsive to the connection authorization decision, if the passenger's government identity was not, server <NUM> is configured to deny (block <NUM>) the user device <NUM> access to the internet.

Continuing reference to <FIG>, when the user device <NUM> is connected to the internet, server <NUM> monitors (block <NUM>) the internet session and generates (block <NUM>) an internet session message for the user device <NUM> that includes the assigned onboard IP address for the user device <NUM> mapped to the IP address for server <NUM>. Server <NUM> communicates (block <NUM>) the internet session message for the user device <NUM> to ground based server <NUM>, and server <NUM> receives and stores (block <NUM>) the internet session message for user device <NUM>. At or near the end of the flight, the user device <NUM> disconnects (block <NUM>) from the aircraft's wireless access point <NUM> or Ethernet.

In some embodiments, prior to boarding the aircraft <NUM>, a passenger has an established internet subscription plan. In this circumstance, the passenger's government identity was previously validated by the issuer of the internet subscription plan. The association between the government identity of the passenger and the subscription plan, however, is not known to the ISP for the aircraft. Because the passenger's government identity was previously validated by the issuer of the subscription plan, the airline or other vehicle operator need only validate the subscription. With reference to <FIG>, <FIG> and <FIG>, to validate a subscription plan, when a user device <NUM> requests access to the internet, the request includes internet subscription plan information. The internet subscription plan information may identify any one or more of: internet subscription plan identity, mobile telephone number, login credentials, etc.). The request for access to the internet and the internet subscription plan information can be included in one message or in separate messages and are collectively referred to herein as a request.

Continuing with reference to <FIG> and <FIG>, the passenger boards the reserved flight and operates a user device <NUM> to connect (block <NUM>) to server <NUM> through the onboard IFE system. Server <NUM> connects to the user device <NUM> and receives (block <NUM>) a unique onboard IP address assigned to the user device <NUM> by the network address translation router <NUM> and mapped to the IP address for server <NUM> for the duration of the flight.

The passenger operates (block <NUM>) the user device <NUM> to request access to the internet. Server <NUM> receives (block <NUM>) the request for internet access. Responsive to the request, server <NUM> transfers (block <NUM>) the request to the ground based server <NUM> for the ISP of the internet subscription plan to validate the plan. The request is transferred to ground based server <NUM> through a network connection and/or an off-board communication link that is determined to be available through satellite datalink interface <NUM> or ground datalink interface <NUM>. The request contains internet subscription plan information and the assigned onboard IP address for the user device <NUM> mapped to the IP address for server <NUM>. Ground based server <NUM> receives (block <NUM>) the request. Ground based server <NUM> generates (block <NUM>) a connection authorization decision for the user device <NUM> having the unique assigned onboard IP address mapped to the IP address for server <NUM>. Ground based server <NUM> communicates (block <NUM>) the decision for the identified user device <NUM> to aircraft based server <NUM>. The aircraft based server <NUM> receives (block <NUM>) the connection authorization decision including the assigned onboard IP address for the user device <NUM> mapped to the IP address for server <NUM>. Responsive to the connection authorization decision, if the internet subscription plan was validated, server <NUM> is configured to connect (block <NUM>) the user device <NUM> to the internet via wireless access point <NUM> or the Ethernet. Responsive to the connection authorization decision, if the internet subscription plan was not validated server <NUM> is configured to deny (block <NUM>) the user device <NUM> access to the internet. Continuing reference to <FIG>, when the user device <NUM> is connected to the internet, server <NUM> monitors (block <NUM>) the internet session and generates (block <NUM>) an internet session message for the user device <NUM> including the assigned onboard IP address for the user device <NUM> mapped to the IP address of server <NUM>. Server <NUM> communicates (block <NUM>) the internet session message for the user device <NUM> to ground based server <NUM>. Server <NUM> receives and stores (block <NUM>) the internet session message for the user device <NUM> including the assigned onboard IP address for the user device <NUM> mapped to the IP address for server <NUM>. At or near the end of the flight, the user device <NUM> disconnects (block <NUM>) from the aircraft's wireless access point <NUM> or Ethernet.

Referring to <FIG>, in a further embodiment, ground based server <NUM> receives a request (block <NUM>) to provide the government identity of a user of a user device <NUM> that was connected to the internet during a flight. Responsive to the request, ground server <NUM> accesses the session logs repository <NUM> and retrieves (block <NUM>) the session information for the identified user device <NUM>. Ground based server <NUM> is configured to retrieve the internet subscription plan information for the user of the user device <NUM>. The server <NUM> may maintain a mapping table that programmatically associates the passenger's validated internet subscription plan information to the unique session token for the user device <NUM>.

Continuing with reference to <FIG>, based on the unique IP address that was assigned to a user device <NUM> and mapped to the IP address for aircraft server <NUM>, a government or other entity may make a request to the airline and/or the ISP for internet service onboard the aircraft to provide the government identity of a passenger who accessed the internet during a flight. Based on the assigned IP address of the user device <NUM> mapped to the IP address for the aircraft server <NUM>, the ISP can identify the aircraft tail number (also known as ICAO Registration number) and the airline that owns the tail number. The ISP can provide the airline with the assigned IP address for the user device <NUM> mapped to the IP address for server <NUM>, the time period in question, the aircraft tail number and/or the flight number. A request (block <NUM>) containing the assigned IP address for the user device <NUM> mapped to the IP address for server <NUM>, the aircraft tail number and/or the flight number for the time period in question is communicated to ground based server <NUM>. Responsive to the request, server <NUM> retrieves and provides (block <NUM>) the government identity of the user of the identified user device <NUM> or the internet subscription plan information for a user of the identified user device <NUM> from the session log repository <NUM> for the flight in question.

In some embodiments, the aircraft or other vehicle based server generates the connection authorization decision. <FIG> which is a combined flowchart and data flow diagram that illustrates operations and data transfers between a user device <NUM> and an exemplary aircraft based server <NUM>. In the example embodiment, a passenger purchases a flight using their government issued identity (block <NUM>). During the flight reservation process or separate therefrom (e.g., during a flight check-in process), the reservation system cooperatively identifies the passenger government identity and travel information to aircraft based server <NUM>, which encrypts and stores (block <NUM>) the information to protect security of the passenger government identity information.

Referring to <FIG>, the passenger boards the reserved flight and operates a user device <NUM> to connect (block <NUM>) to server <NUM> through the onboard IFE system. Server <NUM> connects to the user device <NUM> and receives (block <NUM>) a unique onboard IP address assigned to the user device <NUM> for the duration of the flight by the network address translation router <NUM> and mapped to the IP address of server <NUM>.

The passenger operates (block <NUM>) the user device <NUM> to request access to the internet. Server <NUM> receives (block <NUM>) the request. The request includes travel information and the assigned onboard IP address for the user device <NUM> mapped to the IP address of server <NUM>. Alternatively, in some embodiments, the request includes internet subscription plan information and the assigned onboard IP address for the user device <NUM> mapped to the IP address of server <NUM>. The request for access to the internet and travel information or internet subscription plan information can be included in one message or in separate messages and are collectively referred to herein as a request. Responsive to the request, server <NUM> generates (block <NUM>) a connection authorization decision. More particularly, aircraft based server <NUM> receives the request and uses the passenger's travel information of internet subscription plan information to validate the passenger's government identity. When the request includes a passenger's travel information, the aircraft based server <NUM> is configured to correlate the travel information to the passenger's government identity information. The server <NUM> may maintain a mapping table that programmatically associates the passenger's travel information to the passenger's government identity information.

Continuing with reference to <FIG> and <FIG>, in other embodiments, when the request includes a passenger's internet subscription plan information, the aircraft based server <NUM> is configured to transfer (block <NUM>) the request to ground based server <NUM> for the ISP of the internet subscription plan to validate the plan. The request is transferred to ground based server <NUM> through a network connection and/or an off-board communication link that is determined to be available through satellite communication interface <NUM> or ground communication interface <NUM>. Ground based server <NUM> receives (block <NUM>) the request and generates (block <NUM>) a connection authorization decision for the identified user device <NUM> having the unique onboard IP address mapped to the IP address of server <NUM>. Ground based server <NUM> communicates (block <NUM>) the decision for the identified user device <NUM> to the aircraft based server <NUM>. The aircraft based server <NUM> receives (block <NUM>) the connection authorization decision including the assigned IP address for user device <NUM> mapped to the IP address of server <NUM>.

Continuing with reference to <FIG>, responsive to the connection authorization decision, if the passenger government identity or internet subscription plan information is validated, a unique session information token associated with the assigned onboard IP address for the user device <NUM> mapped to the IP address of server <NUM>. If the passenger government identification or internet subscription plan was validated, server <NUM> is configured to connect (block <NUM>) the user device <NUM> to the internet via wireless access point <NUM> or the Ethernet. Responsive to the connection authorization decision, if the passenger's identity was not validated, server <NUM> is configured to deny (block <NUM>) the user device <NUM> access to the internet.

Continuing reference to <FIG>, when the user device <NUM> is connected to the internet, server <NUM> monitors (block <NUM>) the internet session and generates (block <NUM>) an internet session message containing internet session information for user device <NUM> having an assigned onboard IP address mapped to the IP address of server <NUM>. Server <NUM> communicates (block <NUM>) the internet session message for the user device <NUM> to ground based server <NUM>, and server <NUM> receives and stores (block <NUM>) the internet session message for user device <NUM> including the assigned onboard IP address mapped to the IP address of server <NUM>. At or near the end of the flight, the user device <NUM> disconnects (block <NUM>) from the aircraft's wireless access point <NUM> or Ethernet.

<FIG> is a block diagram of a server configured to operate according to some embodiments of the present disclosure. The server may be configured to operate as the ground based server <NUM>, the aircraft based server <NUM>, and/or the vehicle based server disclosed herein. Referring to <FIG>, the server <NUM> includes a processor <NUM>, a memory <NUM>, and a network interface <NUM> which may include a radio access network transceiver and/or a wired network interface (e.g., Ethernet interface). The network interface <NUM> is configured to communicate with user devices <NUM> and or other servers, including ground based server <NUM> or aircraft based server <NUM>.

The processor <NUM> may include one or more data processing circuits, such as a general purpose and/or special purpose processor (e.g., microprocessor and/or digital signal processor) that may be collocated or distributed across one or more networks. The processor <NUM> is configured to execute computer program code in the memory <NUM>, described below as a non-transitory computer readable medium, to perform at least some of the operations described herein as being performed by an access control computer. The computer program code when executed by the processor <NUM> causes the processor <NUM> to perform operations in accordance with one or more embodiments disclosed herein for the ground based server <NUM> and/or the aircraft based content server <NUM>. The server may further include a mass storage device interface <NUM> (e.g., connector), user input interface <NUM> (e.g., touch screen, keyboard, keypad, etc.), and a display device <NUM>.

<FIG> is a block diagram of a user device <NUM> configured to operate according to some embodiments of the present disclosure. Referring to <FIG>, the user device <NUM> includes a processor <NUM>, a memory <NUM>, and a radio network transceiver <NUM> which can include, but is not limited to, a LTE or other cellular transceiver, WLAN transceiver (IEEE <NUM>), WiMax transceiver, or other radio communication transceiver or wired network interface (e.g., Ethernet and/or USB) configured to communicate with the ground based server <NUM> and/or the aircraft based server <NUM>.

The processor <NUM> may include one or more data processing circuits, such as a general purpose and/or special purpose processor (e.g., microprocessor and/or digital signal processor) that may be collocated or distributed across one or more networks. The processor <NUM> is configured to execute computer program code in the memory <NUM>, described below as a non-transitory computer readable medium, to perform at least some of the operations described herein as being performed by an access control computer. The computer program code when executed by the processor <NUM> causes the processor <NUM> to perform operations in accordance with one or more embodiments disclosed herein for the user device <NUM>. The user device <NUM> may further include a user input interface <NUM> (e.g., touch screen, keyboard, keypad, etc.) and a display device <NUM>.

In the above-description of various embodiments of the present disclosure, aspects of the present disclosure may be illustrated and described herein in any of a number of patentable classes or contexts including any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof. Accordingly, aspects of the present disclosure may be implemented in entirely hardware, entirely software (including firmware, resident software, micro-code, etc.) or combining software and hardware implementation that may all generally be referred to herein as a "circuit," "module," "component," or "system. " Furthermore, aspects of the present disclosure may take the form of a computer program product comprising one or more computer readable media having computer readable program code embodied thereon.

Any combination of one or more computer readable media may be used. The computer readable media may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an appropriate optical fiber with a repeater, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Program code embodied on a computer readable signal medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the internet using an ISP) or in a cloud computing environment or offered as a service such as a Software as a Service (SaaS).

These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable instruction execution apparatus, create a mechanism for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable medium that when executed can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions when stored in the computer readable medium produce an article of manufacture including instructions which when executed, cause a computer to implement the function/act specified in the flowchart and/or block diagram block or blocks. The computer program instructions may also be loaded onto a computer, other programmable instruction execution apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatuses or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

It is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various aspects of the present disclosure.

Like reference numbers signify like elements throughout the description of the figures.

Claim 1:
An entertainment system (<NUM>) for an aircraft or a vehicle comprising:
a server (<NUM>) based on the aircraft or the vehicle, wherein the server has an internet protocol address;
a communication network (<NUM>, <NUM>) that communicatively interconnects the aircraft or the vehicle based server (<NUM>) with at least one user device (<NUM>) having an onboard internet protocol address mapped to the internet protocol address of the aircraft or the vehicle based server;
at least one processor (<NUM>) associated with the aircraft or the vehicle based server that is configured to:
communicate or receive (<NUM>, <NUM>, <NUM>) a request for internet service originating from at least one user device through the communication network, wherein the request includes travel information for a user of the at least one user device or internet subscription plan information for a user of the least one user device and the onboard internet protocol address of the at least one user device mapped to the internet protocol address of the aircraft or the vehicle based server;
(i) communicate (<NUM>, <NUM>) the request received from the at least one user device to a ground based server so that the ground based server generates an internet connection authorization decision based on validation of an identity of the user from the travel information or the internet subscription plan information, and receive (<NUM>, <NUM>) the internet connection authorization decision from the ground based server or (ii) generate (<NUM>) an internet connection authorization decision, wherein the internet connection authorization decision is based on validation of an identity of the user from the travel information or the internet subscription plan information and includes the onboard internet protocol address of the at least one user device mapped to the internet protocol address of the aircraft or the vehicle based server;
connect (<NUM>, <NUM>, <NUM>) the at least one user device via the onboard internet protocol address mapped to the internet protocol address of the aircraft or the vehicle based server to the internet when the internet authorization decision authorizes the connection; and
communicate (<NUM>, <NUM>, <NUM>) an internet session message for the at least one user device having the onboard internet protocol address mapped to the internet protocol address of the aircraft or the vehicle based server to the ground based server from the aircraft or the vehicle based server.