US20160157296A1

US20160157296A1 - Mesh network based automated upload of content to aircraft

Info

Publication number: US20160157296A1
Application number: US15/014,333
Authority: US
Inventors: Bryan Adrian Lauer
Original assignee: Gogo LLC
Current assignee: Gogo LLC
Priority date: 2012-07-09
Filing date: 2016-02-03
Publication date: 2016-06-02
Also published as: US20140011441A1; CN104641656B; CA2881518A1; US9287999B2; EP2870764A4; US11044785B2; EP2870764A1; US20210315055A1; US10512118B2; WO2014011310A1; CN107846479A; CN104641656A; US20180146505A1; US8934893B2; US20150079897A1; CA2881518C; AU2013289121A1; AU2013289121B2; US11765788B2; US20200068654A1

Abstract

The Automated Content Upload System networks a plurality of vehicles together when they are parked at a particular location. Communications among the vehicles is guided by a content manager, resident at or near a particular location (e.g., an airport), which maintains data representative of vehicle content data presently stored on each vehicle and the list of scheduled vehicle content data available on each vehicle. The content manager guides the exchange of vehicle content data among the vehicles, as well as from the content manager to the vehicle, to automatically distribute vehicle content data to the vehicle efficiently and timely. This process includes the ability to multicast data from the content manager to multiple vehicles in a single transmission, obtaining content delivery efficiency, populating multiple vehicles via a single transmission from the content manager. Furthermore, the content manager can supplement this process via transmissions to the vehicle over an air-to-ground link.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a continuation application that claims priority to and the benefit of the filing date of U.S. application Ser. No. 14/553,641, filed Nov. 25, 2014 and entitled “MESH NETWORK BASED AUTOMATED UPLOAD OF CONTENT TO AIRCRAFT,” which is a continuation application that claims priority to and the benefit of the filing date U.S. application Ser. No. 13/544,742, filed Jul. 9, 2012, which issued as U.S. Pat. No. 8,934,893 on Jan. 13, 2015, and is entitled “MESH NETWORK BASED AUTOMATED UPLOAD OF CONTENT TO AIRCRAFT,” the entire disclosure of each of which is incorporated herein by reference.

FIELD OF THE INVENTION

This invention relates to InFlight Entertainment Content which is delivered to passengers on a vehicle (e.g., an aircraft) and, in particular, to a communication system that provides vehicles or other aircraft with high speed delivery of new InFlight Entertainment Content via a mesh network to enable InFlight Entertainment Content to be populated on the Content Manager which is located on the aircraft by wirelessly transferring InFlight Entertainment Content files from other aircraft or from a central Content Manager.

BACKGROUND OF THE INVENTION

It is a problem in the field of providing in-vehicle entertainment to provide passengers on with the most current content for delivery either to the passenger's wireless personal communication devices or vehicle-based displays. Supplemental communications typically fail to provide sufficient bandwidth to transmit all content from terrestrial sites to vehicles while traveling. As a result, content may typically be manually loaded onto a content server via portable media (USB sticks). Thus, every content update requires a visit to a vehicle by maintenance personnel.
Another method of loading content on traveling vehicles is via wireless download (3G Cellular/4G Cellular/WiFi connectivity). However, the issues with wireless connectivity are the data file size of multimedia or entertainment content (1 GB/movie), the extent of wireless coverage, and the cost of wireless service; it can be very costly to go down this path vs. manually swapping out USB sticks.
Therefore, there presently is no reliable, effective, cost-efficient way of delivering content to traveling vehicles.

BRIEF SUMMARY OF THE INVENTION

The above-described problems are solved and a technical advance achieved in the field by the present Mesh Network Based Automated Upload of Content To Aircraft (termed “Automated Content Upload System” herein) which functions to network a plurality of aircraft, and optionally user wireless personal communication devices, together when they are on the ground at an airport, typically when parked at the gates of an airport. The communications among the aircraft are guided by a Content Manager, typically resident at or near the airport, which maintains data representative of the InFlight Entertainment Content presently stored on each aircraft, as well as the list of scheduled InFlight Entertainment Content that is to be available on each aircraft. The Content Manager guides the exchange of InFlight Entertainment Content data among the aircraft as well as from the Content Manager to the aircraft to automatically distribute InFlight Entertainment Content to the aircraft in an efficient and timely manner. Included in this process is the ability to multicast data from the Content Manager to multiple aircraft in a single transmission, thereby obtaining InFlight Entertainment Content delivery efficiency by populating multiple aircraft via a single transmission from the Content Manager. Furthermore, the Content Manager can supplement this process via transmissions to the aircraft, when in flight, over the existing Air To Ground link. Finally, the users' portable wireless personal communication devices, such as those belonging to aircraft crew, passengers, and the like (collectively termed “users” herein), can be made a temporary node in the mesh network and used to transport content onboard the aircraft or function as a relay point between a source and the next device in the network, as is described below.
In addition, the term “InFlight Entertainment Content” includes movies, music, WEB pages, catalogs, magazines, and any other data that the aircraft passengers may wish to view on their wireless personal communication devices while in flight on the aircraft.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates the Automated Content Upload System in block diagram form;

FIG. 2 illustrates a typical airport configuration with multiple aircraft parked at gates;

FIG. 3 illustrates a map of aircraft interconnections in the network;

FIG. 4 illustrates in flow diagram form the operation of the Automated Content Upload System in defining wireless interconnections among multiple aircraft located at an airport; and

FIG. 5 illustrates, in flow diagram form, the operation of the Automated Content Upload System in loading InFlight Entertainment Content to multiple aircraft located at an airport.

DETAILED DESCRIPTION OF THE INVENTION

The Automated Content Upload System 100 functions to network a plurality of Aircraft 221-228 together when they are located at an airport and/or parked at the Gates 211G, 212G of an airport. FIG. 1 illustrates the Automated Content Upload System 100 in block diagram form. The Automated Content Upload System 100 includes a Content Manager 101, which is the repository of InFlight Entertainment Content, as well as the source of control of the mesh network that is established among the aircraft parked at the airport. The Automated Content Upload System 100 also includes one or more Terrestrial Wireless Portals 102, 103 which provide the radio frequency links between the Content Manager 101 and the Aircraft 221-228 (as well as users' Wireless Personal Communication Devices 104, 105).
The Content Manager 101 guides the exchange of InFlight Entertainment Content data among the Aircraft 221-228 as well as from the Content Manager 101 to the Aircraft 221-228 to automatically distribute InFlight Entertainment Content to the Aircraft 221-228 in an efficient and timely manner. The Automated Content Upload System 100 has a plurality of the following attributes:

1. Locate, identify and communicate with all aircraft (network nodes) via Terrestrial Wireless Portals;
2. Perform network registration of each aircraft in an autonomous, automatic manner;
3. Authenticate aircraft (network nodes) on the network to ensure they are legitimate network nodes;
4. Establish regular “all is well” internal communications to verify network health;
5. Establish self-test algorithms in order to verify network functionality;
6. Able to relay data from aircraft to the next; and
7. Able to download content data to multiple aircraft even though data entry into the network is at a single point.
8. Locate, identify, and authenticate users for qualification as temporary mobile nodes in the network.

Network Topology

A mesh network is a local area network (LAN) that employs one of two connection arrangements: full mesh topology or partial mesh topology. In the full mesh topology, each node is connected directly to each of the others. In the partial mesh topology, some nodes may be connected to all the others, but some of the nodes are connected only to those other nodes with which they exchange the most data. The mesh network topology is a peer-to-peer system where a node can send and receive messages, but each node also functions as a router and can relay messages for its neighbors. Through this relaying process, a packet of data finds its way to its ultimate destination, passing through intermediate nodes with reliable communication links. If node fails in this network, the messages are automatically routed through alternative paths.

Physical Orientation of the Network

As shown in FIG. 1, the Automated Content Upload System 100 includes not only a processor, termed Content Manager 101, but also one or more Terrestrial Wireless Portals 102, 103 which function to wirelessly communicate with the Aircraft 221-228. The Content Manager 101 includes an associated Content Memory 111 which functions to store InFlight Entertainment Content for distribution to Aircraft 221-228 as well as a Network Map 112 which identifies the communication connections among the Aircraft 221-228 and, optionally, users' Wireless Personal Communication Devices 104, 105. The Content Manager 101 also includes an Aircraft Content Schedule Table 113 which lists data that identifies the individual aircraft and the content that is presently scheduled to be resident in this aircraft's Aircraft Content Memory 234. Thus, Content Manager 101 can determine what content needs to be loaded on a particular Aircraft 221 by comparing a list of content presently stored in this aircraft's Aircraft Content Memory 234 and content presently scheduled to be resident in this aircraft's Aircraft Content Memory 234 as noted in Aircraft Content Schedule Table 113.
Each Aircraft 221-228 includes an Aircraft Content Network Manager 221A that consists of a server which implements the aircraft-centric portion of the Automated Content Upload System 100. The Aircraft Content Network Manager 221A includes an Aircraft Content Memory 234 that stores the content for distribution to the passengers onboard this aircraft. The Aircraft Content Network Manager 221A also includes an Aircraft Query Generator 231 for wirelessly polling nearby aircraft to establish and update the mesh network that is used to exchange content among the Aircraft 221-228 and from Content Manager 101 to identified Aircraft 221-228. Aircraft Network Memory 232 maintains a record of the nearby aircraft in wireless communication range of the Aircraft 221, and Aircraft Node Registration 233 is a process that shares the collected Aircraft Network Memory content and a list of content stored in the Aircraft Content Memory 234 with the Content Manager 101, as described below.
FIG. 2 illustrates a typical airport configuration with multiple Aircraft 221-228 parked at Gates 211G, 212G. Typically, but not necessarily, a Terrestrial Wireless Portal 102 may be physically installed at a location of an airport terminal building serving a plurality of gates, such as location 211 in the familiar ‘multi-horseshoe’ topography, diagrammatically illustrated in FIG. 1. Where an airport contains multiple terminals or has a large number of gates distributed over a substantial airport area, the airport may be equipped with one or more additional Terrestrial Wireless Portal 103 locations, shown at 212 in FIG. 1, in order to ensure complete gate coverage.
The locations of Terrestrial Wireless Portals 102, 103 are such that, regardless of its location, each of Aircraft 221-228 is assured of having a wireless terrestrial data link with a Terrestrial Wireless Portal 102, 103 of the Automated Content Upload System 100. The spacing between Terrestrial Wireless Portals 102, 103 is such as to provide overlapping terrestrial link communication coverage, as indicated by overlapping circles 214 and 215, whose respective radii encompass the entirety of their associated multi-gate areas 216 and 217.

Mesh Network Creation

In order to support communication among the Aircraft 221-228 and with the Content Manager 101, the mesh network must be established and periodically updated as aircraft arrive and depart from their respective gates and users flow through the terminals and aircraft. As an example, assume that a mesh network among Aircraft 221-226 and Content Manager 101 is established and presently active. The process of creation of a network can be understood by describing the process of adding a new node to an existing network and then extrapolating this process to the case where no network is initially active.
FIG. 4 illustrates in flow diagram form the operation of the Automated Content Upload System 100 in defining wireless interconnections among multiple Aircraft 221-228 located at an airport, as shown diagrammatically in FIG. 3. This process of adding a node to the network entails the newly arrived Aircraft 221 at step 401 activating Aircraft Query Generator 231 to transmit one or more messages over a selected frequency band to establish communications with one or more of the Aircraft 222 located at the airport. If, at step 402, the newly arrived Aircraft 221 fails to locate any other aircraft, then this is an error condition, since the network must contain two or more nodes. Therefore, processing advances to step 403 where an error indication is generated to indicate that the network configuration has failed.
Otherwise, at step 404, the newly arrived Aircraft 221 receives one or more responses to its transmitted query and stores the identity of the responding Aircraft 222, 223 in its Aircraft Network Memory 232 at step 405. If this responding Aircraft (222, for example) has not previously been detected by the newly arrived Aircraft 221, then the number of primary proximate nodes has changed and processing returns to step 404 where the next responsive response (from Aircraft 223, for example) is received and analyzed as noted above. The steps 404-406 are repeated until all of the responses received by newly arrived Aircraft 221 have been processed. At this juncture, all of the Aircraft 222, 223 that are proximate to the newly arrived Aircraft 221 are identified and their identities stored in the Aircraft Network Memory 232 of newly arrived Aircraft 221. The identified nodes that are proximate to and communicable with newly arrived Aircraft 221 form the sub-network for the newly arrived Aircraft 221 within the composite mesh network. In a like manner, all individual Aircraft 222 to 223 have their own sub-networks of nodes which are respectively communicable to themselves, respectively.
The newly arrived Aircraft 221 then activates Aircraft Node Registration 233 to establish a communication link at step 407 with the Content Manager 101 via the Terrestrial Wireless Portal 102. The newly arrived Aircraft 221 downloads the data gathered from the above-noted sub-network determination process and stored in Aircraft Network Memory 232 to the Content Manager 101, which stores mapping data in Network Map 112 from each aircraft indicative of the other airport resident aircraft with which each aircraft can communicate. The Content Manager 101 maintains a multi-dimensional map which charts the interconnections among the aircraft that support the exchange of data. FIG. 3 illustrates a map of aircraft interconnections in the network as stored in Network Map 112.
For the sake of simplicity, the incorporation of users' wireless personal communication devices 104, 105 into the mesh network is not described, although the process is substantially the same as that articulated for aircraft. Since crew members can be identified and their respective flight assignments predetermined, it is advantageous to load content onto their wireless personal communication devices and have these devices propagate content as the crew members move among their respective aircraft assignments. Thus, the propagation of content is significantly enhanced by the addition of a multitude of crew members to the content propagation process. In addition, the crew members' wireless personal communication devices can upload content to the aircraft while the crew member is onboard and the aircraft is in flight. Thus, the temporal and spatial extent of the content loading process is expanded, even though the aircraft has left the terminal, since the content load process continues.
The following description is aircraft-centric for simplicity of description, but the use of the term “aircraft” can include users' wireless personal communication devices as one embodiment of a content delivery node. This node is mobile and is not constrained to be located at a particular gate in the terminal; in fact, it is expected to roam throughout the airport and be resident in various aircraft and at various gates during their tenure at this airport. Thus, the users' wireless personal communication devices are part of the network in the form of mobile repositories of content, with their physical movement from one aircraft to another or from the airport terminal to an aircraft results in the content being available to load into the content memory of the aircraft on which the user is located. Thus, the users' wireless personal communication devices typically do not “store and forward” content via wireless links as the aircraft do; they do store content and manually position themselves inside an aircraft to download the content to the aircraft content memory.

Content Data Distribution

FIG. 5 illustrates in flow diagram form the operation of the Automated Content Upload System 100 in loading InFlight Entertainment Content to multiple aircraft located at an airport. In the Automated Content Upload System 100, as described above, aircraft associate with other aircraft at the gates via aircraft-to-aircraft wireless links. Thus, each aircraft has a “thin link” to the Content Manager 101 via the Terrestrial Wireless Portal 102, 103 and a fat WiFi pipe to the aircraft it is meshed with. At this point, the Content Manager 101 pushes data to specific aircraft via the Terrestrial Wireless Portal 102, 103; and these aircraft push the received content (or content already stored on the aircraft) to other aircraft, as identified to the aircraft, via the WiFi mesh.
The Content Manager 101 stores each aircraft's location, mesh connectivity, mesh link performance, Terrestrial Wireless Portal link performance, as well as a list of content that is stored on the aircraft and a list of content that presently should be stored on the aircraft. The Content Manager 101 also knows the Terrestrial Wireless Portal 102, 103 data budget remaining for the month.
Thus, at step 501, Content Processor 106 of the Content Manager 101 identifies an Aircraft 221 which requires delivery of a selected InFlight Entertainment Content file which is stored in Content Manager Memory 111. Content Processor 106 makes this determination by comparing a list of content presently stored in this aircraft's Aircraft Content Memory 234 and content presently scheduled to be resident in this aircraft's Aircraft Content Memory 234 as noted in Aircraft Content Schedule Table 113. Content Manager 101, at step 502, activates a wireless connection to Aircraft 221 via Terrestrial Wireless Portal 103. Content Manager 101 then, at step 503, transfers the selected InFlight Entertainment Content file to Aircraft 221 via Terrestrial Wireless Portal 103. Another file transfer mode is executed airplane-to-airplane when Content Manager 101 at step 511 identifies a first Aircraft 228 which has stored in its content memory a selected InFlight Entertainment Content file. At step 512, the Content Manager 101 identifies a second Aircraft 221 which does not have the selected InFlight Entertainment Content file stored in its content memory. At step 513, Content Manager 101 reviews the mesh network aircraft interconnection maps, as described above and, at step 514, maps a wireless path through the mesh network from the first Aircraft 228 to the second Aircraft 221, which includes a link through a bridge node (Aircraft 222) to enable the data transfer to take place. Content Manager 101, at step 515, transmits control data to Aircraft 221, 222, and 228 to initiate the transfer of the selected InFlight Entertainment Content file from the content memory of the first Aircraft 228 to the bridge node Aircraft 222 at step 516, which forwards the selected InFlight Entertainment Content file to the second Aircraft 221 at step 517, which stores the selected InFlight Entertainment Content file in its Aircraft Content Memory 334 at step 518.
Since the bandwidth of the aircraft-to-aircraft WiFi link is greater than the bandwidth of the Terrestrial Wireless Portals 102, 103, the transfer of the selected InFlight Entertainment Content file as described above is effected more quickly. In addition, the use of the aircraft as data transfer elements reduces the processing load on the Content Manager 101. Furthermore, Content Manager 101 can use data multicasting to transfer the selected InFlight Entertainment Content file to multiple target aircraft in a single file transfer operation. Thus, Content Manager 101 in the transmission of control data to Aircraft 221, 222, and 228 at step 515 defines a data multicast mode, rather than a point-to-point transmission as described above. This control data causes the first Aircraft 228 to initiate the transfer of the selected InFlight Entertainment Content file from the content memory of the first Aircraft 228 to the bridge node Aircraft 222 at step 516, which stores the selected InFlight Entertainment Content file in its content memory at step 519 and forwards the selected InFlight Entertainment Content file to the second Aircraft 221 at step 517, which stores the selected InFlight Entertainment Content file in its Aircraft Content Memory 334 at step 518.
The Content Manager 101 typically has a plurality of design goals:

1. Minimize the amount of content downloaded over the Terrestrial Wireless Portal;
2. Minimize time to get content on aircraft;
3. Ability to prioritize content distribution (what is high priority, what is low);
4. Each aircraft checks neighboring aircraft inventory and synchronizes/updates content without the need for Content Manager interaction; and
5. File Transfer methods must support frequent breaks in connectivity and file transfer resumption from different sources (servers).

Summary

The Automated Content Upload System networks a plurality of vehicles together when they are parked at a particular location. Communications among the vehicles is guided by a content manager, resident at or near a particular location (e.g., an airport), which maintains data representative of vehicle content data presently stored on each vehicle and the list of scheduled vehicle content data available on each vehicle. The content manager guides the exchange of vehicle content data among the vehicles, as well as from the content manager to the vehicle, to automatically distribute vehicle content data in an efficient and timely manner.

Claims

What is claimed:

1. A content network manager resident on a first vehicle from among a plurality of vehicles, the content network manager being from among a set of content network managers, each content network manager from among the set of content network managers being resident on a respective vehicle from among the plurality of vehicles, the content network manager comprising:

a vehicle content memory configured to store vehicle content data for distribution to passengers onboard the first vehicle;

a network memory, configured to store respective identities of vehicles that respond to a wireless query transmitted by the content network manager, to define a vehicle sub-network including (i) the first vehicle, and (ii) vehicles from among the plurality of vehicles that respond to the wireless query transmitted by the content network manager; and

a vehicle node generator configured to transmit the vehicle data to a content manager via a terrestrial wireless portal, the vehicle data being indicative of (i) vehicle content data stored in the vehicle content memory, (ii) vehicle content data stored in one or more wireless communication devices, the one or more wireless communication devices being detected by the each content network manager using a wireless communication query, and (iii) data indicative of vehicles included in the vehicle sub-network,

wherein the content manager is configured to store the vehicle content data for the plurality of vehicles and includes a content processor configured to transmit, in response to receiving the vehicle data from the vehicle node generator, control signals to the first vehicle to cause the first vehicle to wirelessly distribute, to a second vehicle from among the plurality of vehicles, identified vehicle content data of at least one of (i) the vehicle content memory of the first vehicle, or (ii) the one or more wireless communication devices detected by the content network manager of the first vehicle.

2. The content network manager of claim 1, wherein the content manager further includes a vehicle content schedule table configured to store data indicative of vehicle content presently scheduled to be resident in the vehicle content memory of the content network manager.

3. The content network manager of claim 2, wherein the vehicle content presently scheduled to be resident in the vehicle content memory of the each content network manager as indicated by the vehicle content schedule table is compared, by the content processor, to a list of vehicle content that is presently stored in the vehicle content memory of each content network manager that is associated with each respective vehicle from among the plurality of vehicles.

4. The content network manager of claim 1, wherein the content manager is further configured to map a wireless path from the first vehicle to the second vehicle to wirelessly distribute the identified vehicle content data, and

wherein the wireless path includes at least one additional vehicle which functions as a bridge between the first vehicle and the second vehicle.

5. The content network manager of claim 4, wherein the wireless path includes a series of vehicles, each of which (i) stores and forwards the identified vehicle content data, or (ii) functions as a respective bridge to pass the identified vehicle content data along the wireless path.

6. The content network manager of claim 1, wherein each content network manager further includes a vehicle query generator that is configured to detect a presence of other vehicles within wireless communications range of each respective vehicle content network manager.

7. The content network manager of claim 1, wherein at least a portion of the vehicle content data for distribution to the passengers onboard the first vehicle is received from the content manager via a wireless air-to-ground link.

8. The content network manager of claim 1, wherein at least a portion of the vehicle content data stored at the one or more wireless communication devices is transmitted to the one or more wireless communication devices from the content manager via the terrestrial wireless portal.

9. An automated content upload method, comprising:

operating, by one or more processors, a respective vehicle content network manager resident in each of a plurality of vehicles, the respective vehicle content network manager storing respective vehicle content data for distribution to passengers on each of the plurality of vehicles;

transmitting, by one or more processors, a wireless query on a predetermined frequency band;

storing, by one or more processors, identities of vehicles that respond to the transmitted wireless query to define a vehicle sub-network including (i) vehicles transmitting the wireless query, and (ii) vehicles that respond to the transmitted wireless query;

detecting, by one or more processors, a presence of one or more wireless communication devices having respective vehicle content data stored thereon;

storing, in a vehicle content memory, the respective vehicle content data of the detected one or more wireless communication devices; and

transmitting, to a content manager via a terrestrial wireless portal, vehicle data indicative of (i) the respective vehicle content data stored in the vehicle content memory, (ii) the respective vehicle content data of the detected one or more wireless communication devices, and (iii) data indicative of vehicles in the vehicle sub-network,

wherein the act of transmitting causes the content manager to transmit one or more control signals in response to receiving the vehicle data from the respective vehicle content network manager, to a first vehicle to cause the first vehicle to wirelessly distribute, to a second vehicle, identified vehicle content data that is stored in the vehicle content memory of the first vehicle.

10. The automated content upload method of claim 9, wherein operating the respective vehicle content network manager further comprises:

activating a vehicle query generator to detect a presence of other vehicles located within wireless communications range of the respective vehicle content network manager.

11. The automated content upload method of claim 9, wherein operating the respective vehicle content network manager further comprises:

receiving, from the content manager via a wireless air-to-ground link, at least a portion of the respective vehicle content data for distribution to the passengers on each of the plurality of vehicles.

12. The automated content upload method of claim 11, wherein receiving the at least the portion of the respective vehicle content data from the content manager comprises:

receiving vehicle content data that has been multicast, by the content manager, to multiple vehicles included in the plurality of vehicles.

13. A vehicle content network manager, resident in a first vehicle from among a plurality of vehicles, the vehicle content network manager comprising:

a vehicle query generator configured to detect a presence of other vehicles within wireless communications range of the first vehicle by transmitting a wireless query on a predetermined frequency band;

a vehicle network memory configured to store a respective identity of each other vehicle that responds to the transmitted wireless query to define a vehicle sub-network that includes (i) the first vehicle, and (ii) vehicles that respond to the transmitted wireless query; and

a vehicle node generator configured to transmit, to a content manager via a terrestrial wireless portal, vehicle data including (i) data indicative of vehicle content data stored in the vehicle content memory, (ii) vehicle content data obtained from one or more wireless communication devices, the wireless communication devices being configured to store vehicle content data thereon, and (iii) data indicative of wireless connectivity, via the vehicle sub-network, between the first vehicle and a second vehicle.

14. The vehicle content network manager of claim 13, wherein:

the terrestrial wireless portal is configured to establish bidirectional data communications between the content manager and each of the plurality of vehicles; and

the content manager is configured to respond to the vehicle data transmitted by the vehicle node generator by transmitting control signals to the first vehicle to cause the first vehicle to wirelessly distribute identified vehicle content data stored in the vehicle content memory of the first vehicle to the second vehicle via a vehicle-to-vehicle wireless link.

15. The vehicle content network manager of claim 13, wherein the content manager further includes a vehicle content schedule table configured to store data indicative of vehicle content data presently scheduled to be resident in the vehicle content memory of the first vehicle.

16. The vehicle content network manager of claim 13, wherein the content manager is further configured to map a wireless path from the first vehicle to the second vehicle to wirelessly distribute the identified vehicle content data, and

wherein the wireless path includes at least one additional vehicle that functions as a bridge between the first vehicle and the second vehicle.

17. The vehicle content network manager of claim 13, wherein the wireless path includes a series of vehicles, each of which is (i) configured to store and forward identified vehicle content data, or (ii) function as a bridge to pass the identified vehicle content data along the wireless path via respective vehicle-to-vehicle wireless links.

18. The vehicle content network manager of claim 13, wherein at least a portion of the vehicle content data for distribution to the passengers onboard the first vehicle is received from the content manager via a wireless air-to-ground link.

19. The vehicle content network manager of claim 18, wherein the at least the portion of the vehicle content data is multicast by the content manager to more than one vehicle from among the plurality of vehicles.

20. The vehicle content network manager of claim 13, wherein the vehicle content data stored at the one or more wireless communication devices is received at the one or more wireless communication devices from the content manager via the terrestrial wireless portal.