Facilitating communications between on-board electronic devices and terrestrial devices

Techniques for facilitating data communications among electronic devices via various communication networks are provided. A first electronic device may be connected to a terrestrial network and a second electronic device may be connected to an on-board communications network of a vehicle. A first voice- or message-based content may be received from the first electronic device, for delivery to the second electronic device. A data center may transmit a corresponding forward communication to the second electronic device via a satellite communication link. The data center may also receive a return communication from the second electronic device via either the satellite communication link or a terrestrial communication link, and transmit corresponding content to the first electronic device.

FIELD AND BACKGROUND OF THE DISCLOSURE

Technical Field

The instant disclosure generally relates to delivering communications to and from devices that are on-board vehicles, and, in particular, to systems and methods for facilitating communications between electronic devices via various communication networks.

Background

Currently, existing airlines and other transportation companies provide various services to mobile or wireless devices (e.g., cellular phones, smart devices, laptops, tablet computers, etc.) when such devices are on-board a vehicle while the vehicle is en route to a destination. However, the delivery of terrestrial or native features (e.g., roaming, texting, simultaneous calls, etc.) to mobile or wireless devices while a vehicle is in transit presents difficulties. Typically, to support native, terrestrial features of a mobile or wireless device in a non-terrestrial environment, cellular base stations such as “picocells” are installed on-board the vehicle, and the mobile device connects, via the cellular radio of the mobile device and the on-board cellular base stations, to an on-board network. In some cases, hardware in addition to the cellular base stations is also installed on-board the vehicle. This extraneous infrastructure is both limiting and extremely expensive. Moreover, the radio transmissions produced on-board the vehicle may interfere with ground-based cellular systems. For example, if mobile devices on-board the vehicle cannot find an adequate cellular band to which they may connect (e.g., when on-board cellular base stations are deactivated), the mobile devices will automatically increase their power, which may interfere with ground-based terrestrial cell sites as well as quickly drain the batteries of the mobile devices.

Some existing terrestrial communications systems are able to provide internet-based network connections to mobile devices while on-board a vehicle. For example, some communications systems are equipped with Wi-Fi capability that enables the mobile devices to access websites and stream multimedia. However, these communications systems are not able to provide mobile devices with terrestrial or native communication features (i.e., cellular-based communications) while the mobile devices are on-board the vehicle.

Accordingly, there is an opportunity to leverage existing communications infrastructure to facilitate cellular-based communications via electronic devices while the electronic devices are connected to a non-terrestrial communications network.

BRIEF SUMMARY OF THE DISCLOSURE

In an embodiment, a method of providing communications to and from a first electronic device connected to a terrestrial network and a second electronic device connected to an on-board communications network is provided. The method includes receiving, from the first electronic device via a service provider network, a first voice- or message-based content that identifies the second electronic device, generating a forward communication (i) including the first voice- or message-based content and (ii) indicating the second electronic device, and transmitting the forward communication to the second electronic device via a satellite communication link. The method further includes receiving a return communication from the second electronic device via a terrestrial communication link, the return communication (i) including a second voice- or message-based content, and (ii) indicating the first electronic device, and transmitting the second voice- or message-based content to the first electronic device via the service provider network.

In another embodiment, a system for providing communications to and from a first electronic device connected to a terrestrial network and a second electronic device connected to an on-board communications network is provided. The system includes a communication module configured to send and receive data, and a data center comprising a memory and a processor, and communicatively connected to the communication module. The data center is configured to receive, from the first electronic device via a service provider network, a first voice- or message-based content that identifies the second electronic device, generate a forward communication (i) including the first voice- or message-based content and (ii) indicating the second electronic device, and transmit, via the communication module, the forward communication to the second electronic device via a satellite communication link. The data center is further configured to receive a return communication from the second electronic device via a terrestrial communication link, the return communication (i) including a second voice- or message-based content, and (ii) indicating the first electronic device, and transmit, via the communication module, the second voice- or message-based content to the first electronic device via the service provider network.

In a further embodiment, a method of providing communications to and from a first electronic device connected to a terrestrial network and a second electronic device connected to an on-board communications network is provided. The method includes receiving, from the first electronic device via a service provider network, a first voice- or message-based content that identifies the second electronic device, generating a forward communication (i) including the first voice- or message-based content and (ii) indicating the second electronic device, and transmitting the forward communication to the second electronic device via a satellite communication link. The method further includes receiving a return communication from the second electronic device via the satellite communication link, the return communication (i) including a second voice- or message-based content, and (ii) indicating the first electronic device, and transmitting the second voice- or message-based content to the first electronic device via the service provider network.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Additionally, any or all of the contents of the present disclosure may operate in conjunction with any or all of the contents of the disclosure of co-pending U.S. patent application Ser. No. 13/675,200 entitled “VEHICLE DATA DISTRIBUTION SYSTEM AND METHOD,” the contents of which are hereby incorporated by reference in their entirety. Further, any or all of the contents of the present disclosure may operate in conjunction with any or all of the contents of the disclosure of co-pending U.S. patent application Ser. No. 13/675,194 entitled “COMMUNICATIONS SYSTEM AND METHOD FOR NODES ASSOCIATED WITH A VEHICLE,” the contents of which are hereby incorporated by reference in their entirety, and any or all of the contents of the present disclosure may operate in conjunction with any or all of the contents of the disclosure of co-pending U.S. patent application Ser. No. 13/675,190 entitled “GROUND SYSTEM FOR VEHICLE DATA DISTRIBUTION,” the contents of which are hereby incorporated by reference in their entirety.

Still further, any or all of the contents of the present disclosure may operate in conjunction with any or all of the contents of the disclosures of co-pending U.S. patent application Ser. No. 14/291,878 entitled “SYSTEMS AND METHODS FOR FACILITATING COMMUNICATIONS ORIGINATING FROM A NON-TERRESTRIAL NETWORK” and co-pending U.S. patent application Ser. No. 14/292,035 entitled “SYSTEMS AND METHODS FOR FACILITATING COMMUNICATIONS DESTINED FOR A NON-TERRESTRIAL NETWORK”, the contents of which are hereby incorporated by reference in their entireties.

FIG. 1illustrates an example representation100of components configured to facilitate cellular-based communications among electronic devices. In particular, the components of the representation100are configured to facilitate text-based communications (e.g., short message service (SMS) messages) between an electronic device105connected to a non-terrestrial-based network and one or more additional devices110connected to a terrestrial-based network. Generally, as referred to herein, a “terrestrial-based” or “ground-based” network refers to any network that electronic devices may connect to while in a terrestrial environment, but may not easily communicate while being transported by a high-speed or high-elevation vehicle such as an airplane. Similarly, a “non-terrestrial-based” or “non-ground-based” network refers to any network that electronic devices may connect to while not in range of a ground-based network or while not able to easily connect to a ground-based network, such as while the electronic devices are being transported by a high-speed or high-elevation vehicle such as an airplane. Generally, the external network includes ground systems and ground computing devices that are essentially fixed in location. Further, the external network includes base stations or infrastructure containing equipment via which devices may wirelessly access the external network may be contained in one or more buildings or other structures that are fixedly attached to the ground or to earth.

Each of the electronic device105and the additional device110may be any type of standalone or portable electronic device capable of communicating via one or more networks. For example, each of the electronic device105and the additional device110may be a mobile phone, a Personal Digital Assistant (PDA), a smart phone, a tablet computer, a multimedia player, a desktop or notebook computer, an MP3 player, a digital broadcast receiver, or any other electronic apparatus. Each of the electronic device105and the additional device110may also have a subscription or plan with a cellular services provider, whereby the cellular services provider supports cellular communications conducted via the electronic device105and/or the additional device110.

As illustrated inFIG. 1, the electronic device105is transported by or otherwise located within a vehicle117. In embodiments, the vehicle117may be owned and/or operated by an individual, or the vehicle may be owned and/or operated by a company, organization or governmental entity. The vehicle117may be one of a fleet of vehicles. The vehicle117may be used to transport passengers who pay for or otherwise are granted passage on the vehicle. The vehicle117may be used to transport executives or staff of a company or organization and their guests. The vehicle117may be used to transport live or inanimate cargo, packages, mail, and/or other types of passengers or cargo. Furthermore, althoughFIG. 1depicts the vehicle117as an aircraft, the techniques and principles described herein equally apply to other types of vehicles such as trucks, automobiles, busses, trains, boats, ships, barges, subway cars, helicopters, ambulances or other emergency vehicles, military vehicles, other air-borne, water-borne, or land-borne vehicles, and vehicles that are suitable for space travel.

The vehicle117is equipped with a wireless access point119and an on-board communications network system121. At any given moment in time, the on-board communications network system121may be in communicative connection with one or more data or communications networks that are disposed, managed, and/or hosted, for the most part (if not entirely), externally to the vehicle117. For example, an external network may be a public, ground-based data or communications network, such as the Internet and/or the PSTN (Public Switched Telephone Network). The external network may also be a ground-based private data and/or communications network. Further, the external network may be a cellular network107that includes a cell site station123. Generally, the external network includes ground systems and ground computing devices that are essentially fixed in location. Further, the external network includes base stations or infrastructure containing equipment via which devices may wirelessly access the external network may be contained in one or more buildings or other structures that are fixedly attached to the ground or to earth.

The electronic device105can connect to the on-board communications network system121via the wireless access point119. Generally, the on-board communications network system121may be disposed, managed, and/or hosted entirely on-board the vehicle117. For example, the on-board communications network system121may be a Wi-Fi network that is contained and operates within the cabin of the vehicle117. The on-board communications network system121may utilize any known communication protocol or combinations thereof, such as a wireless protocol, a wired protocol, other ARINC standard-compatible protocols, or a private protocol. In an example, the on-board communications network system121utilizes an IEEE 802.11 compatible protocol to communicate with the electronic device105. In another example, the on-board communications network system121utilizes a hypertext transfer protocol (HTTP) and a Near Field Communications (NFC)-compatible protocol (e.g., Bluetooth®) to communicate with the electronic device105.

The on-board communications network system121can also facilitate and manage communications between the electronic device105and the cell site station123of the cellular network107. According to embodiments, the on-board communications network system121and the cell site station123may collectively make up an air-to-ground (ATG) communication network for aircraft use. In embodiments, the on-board communications network system121and the cell site station123can facilitate any type of data communication via any wireless standard or technology (e.g., GSM, CDMA, TDMA, WCDMA, LTE, EDGE, OFDM, GPRS, EV-DO, UWB, and others).

The cell site station123of the cellular network107can connect, via one or more various wired or wireless networks, to a ground-based data center129having components for securely facilitating communications between the electronic device105and other electronic devices, such as the additional device110. In particular, the cell site station123includes a session border controller (SBC) and session initiation protocol (SIP) server127(which may be separate servers or combined into the same server) and a registration server114. The registration server114may be any combination of hardware and software elements configured to directly or indirectly communicate with the electronic device105and the additional device110, and facilitate the functionalities and communications described herein. Further, the SBC/SIP server127can facilitate and manage communication sessions among the electronic device105, the additional device(s)110, and the data center129using the SIP signaling communications protocol.

Although the embodiments herein are described as operating with the SIP signaling protocol, it should be appreciated that other standard or proprietary application protocols are envisioned. For example, other envisioned protocols include hypertext transfer protocol (HTTP), simple mail transfer protocol (SMTP), transmission control protocol (TCP), user datagram protocol (UDP), Internet control message protocol (ICMP), internet message access protocol (IMAP), and others.

According to embodiments, the electronic device105can download and install a communication application (not shown inFIG. 1) that enables cellular-based communications when the electronic device105is located in the vehicle117. Further, the electronic device105can use the communication application to register and create an account with the registration server114, as discussed in co-pending application Ser. Nos. 14/291,558 and 14/291,511, to enable the electronic device105to communicate over various air-borne communication networks, such as an air-to-ground (ATG) communication network for aircraft use.

As illustrated inFIG. 1, the registration server114may connect, via a cellular-based network, to a home network111associated with the electronic device105. The cellular-based network may be a wide area network (WAN) configured to facilitate any type of data communication via any standard or technology (e.g., GSM, CDMA, TDMA, WCDMA, LTE, EDGE, OFDM, GPRS, EV-DO, UWB, and others). Generally, the home network111of the electronic device105may be administered or provided by a cellular communications service provider with which the user (i.e., subscriber) of the electronic device105has an agreement to send and receive wireless communications services and features. Accordingly, the home network111of the electronic device105may administrate or manage a home location register (HLR)115and/or a visiting location register (VLR) (not shown inFIG. 1), among other databases or components, to support and manage cellular communication, roaming, and other features for the electronic device105according to the services agreement. Additionally, the cellular radio frequency (RF) communications band utilized by the home network111to wirelessly communicate with mobile devices may be an RF band designated for AMPs, TDMA, CDMA, GSM, PCS, 3G, 4G, 5G, and/or any other terrestrial cellular radio frequency band. Generally, a cellular radio frequency band is a portion of RF spectrum that is allocated by a governmental agency or other body which governs the usage of spectrum. In some networks, more than one cellular RF band may be supported.

The HLR115can include a database that stores identifications of electronic devices that are authorized to communicate via the home network111. In particular, for each authorized device, the HLR115can store the corresponding international mobile subscriber identity (IMSI), which is a unique number that identifies each authorized device (or more particularly, identifies the SIM card of each authorized device). The HLR115can also pair each IMSI with a mobile subscriber integrated services digital network number (MSISDN) that corresponds to a telephone number of the authorized device. The home network111further includes a short message service center (SMSC)102configured to store, forward, convert, and deliver cellular-based messages (e.g., text messages such as SMS messages). In particular, the SMSC102can forward, to the data center129, messages originated by the additional device110and intended for the electronic device105. Further, the SMSC102can send, to the additional device110, messages received from the electronic device105via the data center129.

According to embodiments, the components of the representation100are configured to facilitate the communication of cellular-based messages between and among the electronic device105and the one or more additional devices110. In one embodiment, the data center129can receive, via the on-board communications network system121and the cellular network107, a message from the electronic device105traveling in the vehicle117, whereby the message is intended for the additional device110. Because the message is initiated as an internet-based communication, the message is not configured for delivery to the additional device110as a conventional cellular-based message. Accordingly, the data center129can perform various techniques associated with the message so that the message is configured to be delivered, via the home network111, to the additional device110as a conventional cellular-based message.

In another embodiment, the data center129can receive a message from the additional device110via the home network111, whereby the message is intended for the electronic device105traveling in the vehicle117. Because the message is initiated as a cellular-based communication, the message is not configured for delivery to the electronic device105because the electronic device105is not directly connected to a cellular-based network. Accordingly, the data center129can perform various techniques associated with the message so that the message is configured to be delivered, via the cellular network107and the on-board communications network system121, to the electronic device105as an internet-based message.

FIG. 2illustrates a signal diagram200associated with facilitating the communication of a text-based communication or message that originates from an origination device205connected to a non-ground-based network, such as if the origination device205is located on board a vehicle such as an aircraft. According to embodiments described herein, the text-based communication can be an SMS message, however it should be appreciated that other text-based or multimedia-based communications are envisioned. The signal diagram200includes the originating device205(such as the electronic device105as discussed with respect toFIG. 1), a data center229including an SBC/SIP server227(such as the SBC/SIP server127as discussed with respect toFIG. 1) and a registration server214(such as the registration server114as discussed with respect toFIG. 1), an SMSC212(such as the SMSC112as discussed with respect toFIG. 1), and a destination device210(such as the destination device110as discussed with respect toFIG. 1).

According to embodiments, a user of the originating device205may select a service or product from a list of available services or products that may include various cellular connectivity options for the originating device205that are based on time durations, data limits, or other parameters. For example, the list of services or products can include an option to send and receive unlimited text-based communications during a particular flight.

To initiate the communication of the text-based message, a user can use the originating device205to input (230) the message body and an identification of the recipient. In particular, the identification of the recipient can be an MSIDSN (i.e., telephone number) associated with the destination device210. In some embodiments, the user can initiate the message using a communication application that has already been registered with an on-board communications network system of the vehicle and/or with the registration server214. Further, the communication application can convert the text-based message into an SIP-based message, whereby the SIP message includes a uniform resource indicator (URI) that indicates the IMSI and/or MSISDN associated with the originating device205.

Although not illustrated inFIG. 2, the originating device205can initiate a transport layer security (TLS) connection with the SBC/SIP server427using a digital certificate. In particular, the certificate can be the certificate that the registration server214issues to the originating device205during the device registration technique. The registration server214(acting as the certificate authority (CA)) can validate the certificate and send a success response to the SBC/SIP server227. Responsive to receiving the success response, the SBC/SIP server227can establish the TLS connection with the originating device205.

The originating device205can send (231) the SIP message to the SBC/SIP server227via the established TLS connection. The SBC/SIP server227can decrypt (232) the SIP message and look up (233) the IP address associated with the originating device205. In particular, the IP address can be a care-of address (CoA) that the SBC/SIP server227has previously associated with the originating device205. The SBC/SIP server227can modify (234) the IP address of the originating device205by replacing the IP address included in the SIP message with the CoA associated with the originating device205.

After modifying the IP address, the SBC/SIP server227can send (235) the SIP message with the modified IP address to the registration server214. The registration server214can examine the SIP message and confirm (236) that the originating device205has an active product or service. The registration server214can also convert (237) the SIP message into an SMS message according to the proper communication protocol (e.g., GSM, CDMA, etc.). Further, the registration server214can modify (238) the “from” field of the SMS message to the MSISDN of the originating device205. In particular, the registration server214can use the identification of the originating device205that is specified in the SIP message (e.g., the IMSI of the originating device205) to look up the MSISDN of the originating device205.

After generating the SMS message, the registration server214can send (239) the SMS message to the SMSC202, and the SMSC202can deliver (240) the SMS message to the destination device210. When the destination device210receives the SMS message, the MSISDN included in (238) will enable the SMS message to appear as a conventional cellular-based SMS, instead of a message that originates as an SIP message as in (231). In particular, the appearance of the delivered SMS does not differ from the appearance of an SMS message that is sent from one mobile device to another mobile device via a cellular network.

Upon receiving the SMS message from the SMSC202, the destination device210can present (245) the SMS message in a user interface. In some embodiments, the destination device210can present the body or textual portion of the SMS message via an application installed on the destination device210. Further, the destination device210can send (241) a message received acknowledgement to the SMSC202, which can be respectively forwarded to the registration server214(242), to the SBC/SIP server227(243), and to the originating device205(244).

FIG. 3illustrates a signal diagram300associated with facilitating the delivery of a text-based communication or message that originates from an originating device310connected to a terrestrial-based network. Further, the text-based communication is intended for a destination device305that is connected to a non-terrestrial-based network, such as if the destination device305is located on board a vehicle such as an aircraft. According to embodiments described herein, the text-based communication can be an SMS message, however it should be appreciated that other text-based or multimedia-based communications are envisioned. The signal diagram300includes the destination device305(such as the electronic device105as discussed with respect toFIG. 1), a data center329including an SBC/SIP server327(such as the SBC/SIP server127as discussed with respect toFIG. 1) and a registration server314(such as the registration server114as discussed with respect toFIG. 1), a home network311including an HLR315and an SMSC312(such as the HLR115and the SMSC112as discussed with respect toFIG. 1), and the originating device310(such as the additional device110as discussed with respect toFIG. 1). For purposes of discussion, it should be appreciated that the destination device305has already completed the registration procedure with the registration server314, and has also purchased a product or service that enables text-based communication via the non-terrestrial-based network.

To initiate the communication of the text-based message, a user can use the originating device310to compose the SMS message (e.g., using a conventional text messaging application), specify the recipient (e.g., via including the MSISDN of the destination device305), and select to send the SMS message. In operation, the originating device310sends (330) the SMS message to the SMSC302. Upon receiving the SMS message, the SMSC302requests (331), from the HLR315associated with the destination device305, routing information associated with the MSISDN specified in the SMS message. Because the destination device305has previously registered with the registration server314, the registration server314previously updated the location of the destination device305with the HLR315and therefore the HLR315is “aware” of the associated between the destination device305and the registration server314. Accordingly, the HLR315can send (332) the routing information associated with the destination device305, which can be the routing number of the registration server314.

Using the routing number, the SMSC302can send (333) the SMS message with the MSISDN of the destination device305to the registration server314. The registration server314can examine the MSISDN to confirm (334) that there is an active product or service associated with the destination device305. In particular, a user of the destination device305can have previously selected (e.g., on an in-flight trip), a service or product from a list of available services or products that may include various cellular connectivity options for the destination device305that are based on time durations, data limits, or other parameters. The registration server314can also retrieve (335) an SIP URI associated with the MSISDN of the destination device305. In particular the SIP URI may have been previously associated with the MSISDN during the registration of the destination device305with the registration server314.

The registration server314can convert (336) the SMS message into an SIP message using the SIP URI, according to various techniques or communication protocols (e.g., CDMA, GSM, etc.). The registration server314can also send (337) the SIP message with the SIP URI to the SBC/SIP server327. According to embodiments, the SBC/SIP server327can establish (338) a TLS connection with the destination device305using a digital certificate or according to other techniques. Further, the SBC/SIP server327can send (342) the SIP message to the destination device305via the established TLS connection. The destination device305can present (343) the SIP message to a user of the destination device305. In some embodiments, the destination device305can present the body or textual portion of the SIP message via an application installed on the destination device305. After receiving the SIP message, the destination device305can send (339) a message received acknowledgement to the SBC/SIP server327, which can be respectively forwarded to the registration server314(340) and to the originating device (310).

FIG. 4illustrates an example representation400of components configured to facilitate cellular-based communications among electronic devices. In particular, the components of the representation400are configured to facilitate voice-based communications (e.g., VoIP calls) between an electronic device405connected to a non-terrestrial-based network and one or more additional devices410connected to a terrestrial-based network.

Similar to the electronic device105and the additional device110ofFIG. 1, each of the electronic device405and the additional device410may be any type of standalone or portable electronic device capable of communicating via one or more networks. For example, each of the electronic device405and the additional device410may be a mobile phone, a Personal Digital Assistant (PDA), a smart phone, a tablet computer, a multimedia player, a desktop or notebook computer, an MP3 player, a digital broadcast receiver, or any other electronic apparatus. Each of the electronic device405and the additional device410may also have a subscription or plan with a cellular services provider, whereby the cellular services provider supports cellular communications conducted via the electronic device405and/or the additional device410.

As illustrated inFIG. 4, the electronic device405is transported by or otherwise located within a vehicle417, similar to the vehicle117as discussed with respect toFIG. 1. The vehicle417is equipped with a wireless access point419and an on-board communications network system421. At any given moment in time, the on-board communications network system421may be in communicative connection with one or more data or communications networks that are disposed, managed, and/or hosted, for the most part (if not entirely), externally to the vehicle417. For example, an external network may be a public, ground-based data or communications network, such as the Internet and/or the PSTN (Public Switched Telephone Network). The external network may also be a ground-based private data and/or communications network. Further, the external network may be a cellular network407that includes a cell site station423. Typically, ground systems and ground computing devices may be essentially fixed in location, and base stations or infrastructure containing equipment via which devices may wirelessly access the ground system may be contained in one or more buildings or other structures that are fixedly attached to the ground or to earth.

The electronic device405can connect to the on-board communications network system421via the wireless access point419. Generally, the on-board communications network system421may be disposed, managed, and/or hosted entirely on-board the vehicle417. For example, the on-board communications network system421may be a Wi-Fi network that is contained and operated within the cabin of the vehicle417. The on-board communications network system421may utilize any known communication protocol or combinations thereof, such as a wireless protocol, a wired protocol, other ARINC standard-compatible protocols, or a private protocol. In an example, the on-board communications network system421utilizes an IEEE 802.11 compatible protocol to communicate with the electronic device405. In another example, the on-board communications network system421utilizes a hypertext transfer protocol (HTTP) and a Near Field Communications (NFC)-compatible protocol (e.g., Bluetooth®) to communicate with the electronic device405.

The on-board communications network system421can also facilitate and manage communications between the electronic device405and the cell site station423of the cellular network407. According to embodiments, the on-board communications network system421and the cell site station423may collectively make up an air-to-ground (ATG) communication network for aircraft use. In embodiments, the on-board communications network system421and the cell site station423can facilitate any type of data communication via any wireless standard or technology (e.g., GSM, CDMA, TDMA, WCDMA, LTE, EDGE, OFDM, GPRS, EV-DO, UWB, and others).

The cell site station423of the cellular network407can connect, via one or more various wired or wireless networks, to a ground-based data center429having components for securely facilitating communications between the electronic device405and other electronic devices, such as the additional device410. In particular, the cell site station423includes a SBC/SIP server427(which may be separate servers or combined into the same server) and a registration server414. The registration server414may include any combination of hardware and software elements configured to directly or indirectly communicate with the electronic device405and the additional device410, and facilitate the functionalities and communications described herein. Further, the SBC/SIP server427can facilitate and manage communication sessions among the electronic device405, the additional device(s)4101, and the data center429using the SIP signaling communications protocol.

According to embodiments, the electronic device405can download and install a communication application (not shown inFIG. 1) that enables the cellular-based communications when the electronic device405is located in the vehicle417. Further, the electronic device405can use the communication application to register and create an account with the registration server414. The registration configures the electronic device405to communicate over various air-borne communication networks, such as an air-to-ground (ATG) communication network for aircraft use.

As illustrated inFIG. 4, the registration server414may connect, via a cellular-based network, to a home network411associated with the electronic device405. The cellular-based network may be a wide area network (WAN) configured to facilitate any type of data communication via any standard or technology (e.g., GSM, CDMA, TDMA, WCDMA, LTE, EDGE, OFDM, GPRS, EV-DO, UWB, and others). Generally, the home network411of the electronic device405may be administered or provided by a cellular communications service provider with which the user (i.e., subscriber) of the electronic device405has an agreement to receive wireless communications services and features. Accordingly, the home network411of the electronic device405may administrate or manage an HLR415and/or a VLR (not shown inFIG. 4), among other databases or components, to support and manage cellular communication, roaming, and other features according to the services agreement. Additionally, the cellular radio frequency (RF) communications band utilized by the home network411to wirelessly communicate with mobile devices may be an RF band designated for AMPs, TDMA, CDMA, GSM, PCS, 3G, 4G, 5G, and/or any other terrestrial cellular radio frequency band. Generally, a cellular radio frequency band is a portion of RF spectrum that is allocated by a governmental agency or other body which governs the usage of spectrum. In some networks, more than one cellular RF band may be supported.

The HLR415can include a database that stores identifications of electronic devices that are authorized to communicate via the home network411. In particular, for each authorized device, the HLR415can store the corresponding IMSI, which is a unique number that identifies each authorized device (or more particularly, identifies the SIM card of each authorized device). The HLR415can also pair each IMSI with an MSISDN that corresponds to a telephone number of the authorized device.

The data center429can further be configured to communicate with an SIP trunk provider412. According to embodiments, the SIP trunk provider412enables VoIP and streaming media communications by which internet telephony service providers (ITSPs) deliver telephone services and unified communications to customers equipped for SIP-based communications. Each of the home network411and the SIP trunk provider412(as well as the data center429) may communicate with a mobile switching center (MSC)413. According to embodiments, the MSC413routes voice calls and other messaging services to and from end devices, such as the electronic device405and the additional device(s)410. In particular, the MSC413sets up and releases end-to-end connections, and manages mobility and hand-over requirements during calls, among other services as known in the art.

According to embodiments, the components of the representation400are configured to facilitate voice-based communications between the electronic device405and the one or more additional devices410. In one embodiment, the data center429can receive an SIP message initiated by the electronic device405traveling while in the vehicle417, whereby the SIP message is intended to set up a voice communication with the additional device410. Because the SIP message is initiated as an internet-based communication, the SIP message is not configured to set up a conventional telephone call with the additional device410. Accordingly, the data center429can perform various techniques associated with the message, as well as leverage the SIP trunk provider412and the MSC413, so that an RTP stream may be established between the electronic device405and the additional device410to facilitate the voice-based communication.

In another embodiment, the additional device410can initiate a voice-based communication intended for the electronic device405. The SIP trunk provider412can initiate the voice-based communication setup by sending a message to the data center429. The data center429can perform various techniques associated with the message, as well as leverage the cellular network407, so that an RTP stream may be established between the electronic device405and the additional device410to facilitate the voice-based communication.

FIG. 5illustrates a signal diagram500associated with facilitating a voice-based communication that originates from an originating device505connected to a non-ground-based network, such as if the originating device505is located on board a vehicle such as an aircraft. The voice-based communication can be intended for a destination device510that is connected to a terrestrial-based network. According to embodiments discussed herein, the voice-based communication can be a VoIP call, however it should be appreciated that other voice-based communications are envisioned. The signal diagram500includes the originating device505(such as the electronic device405as discussed with respect toFIG. 4), a data center529including an SBC/SIP server527(such as the SBC/SIP server427as discussed with respect toFIG. 4) and a registration server514(such as the registration server414as discussed with respect toFIG. 4), an SIP trunk provider512(such as the SIP trunk provider412as discussed with respect toFIG. 4), a mobile switching center513(such as the mobile switching center413as discussed with respect toFIG. 4), and the destination device510(such as the additional device410as discussed with respect toFIG. 4). For purposes of discussion, it should be appreciated that the originating device505has already completed the registration procedure with the registration server514, and has also purchased a product or service that enables voice-based communication via the non-ground-based network.

A user of the originating device505can use an application that is registered with the registration server514to initiate the voice-based communication (e.g., a VoIP call). In particular, the user can input an MSISDN (i.e., telephone number) associated with the destination device510and select to initiate the call. Although not illustrated inFIG. 5, the originating device505can establish a TLS connection with the SBC/SIP server527, for example using a digital certificate obtained during registration with the registration server514. The originating device505can send (544) an SIP invitation request associated with the VoIP call to the SBC/SIP server527via the TLS connection. The SIP invitation request can include an identification of the originating device505, such as the IMSI of the originating device505. The SBC/SIP server527can respond (545) to the originating device505with an SIP100trying message. Responsive to receiving the SIP100trying message, the originating device505can allocate (546) an RTP port and listen for a communication on the RTP port.

The SBC/SIP server527can decrypt (547) the SIP message and look up (548) the IP address associated with the originating device505. In particular, the IP address can be a care-of address (CoA) that the SBC/SIP server527has previously associated with the originating device505. The SBC/SIP server527can modify (549) the IP address of the originating device505by replacing the IP address included in the SIP message with the CoA associated with the originating device505. After modifying the IP address, the SBC/SIP server527can send (550) the SIP invite message with the modified IP address to the registration server514. The registration server514can examine the SIP invite message and confirm (552) that the originating device505has an active product or service. The registration server514can also replace (553) the identification of the originating device505(e.g., the IMSI of the originating device505) that is specified in the SIP invite message with the phone number (e.g., MSISDN) associated with the originating device505.

The registration server514can send (554) the SIP invite message with the phone number associated with the originating device505to the SIP trunk provider512, and the SIP trunk provider512can respond (555) to the registration server514with an SIP100trying message. Responsive to receiving the SIP invite message from the registration server514, the SIP trunk provider512can send (556) an initial address message/ISDN user part (IAM/ISUP) setup request to the mobile switching center513, and the mobile switching center513can connect (557) the VoIP call with the destination device510.

As illustrated inFIG. 5, a user of the destination device510can cause the destination device510to answer (558) the call, which triggers a call answered acknowledgement to be sent (559) to the mobile switching center513. The mobile switching center513can forward (560) the call answered acknowledgement to the SIP trunk provider512. Upon receiving the call answered acknowledgement, the SIP trunk provider512can send (561) an SIP200OK message to the registration server514, which can forward (562) the SIP200OK message to the SBC/SIP server527, and which can forward (563) the SIP200OK message to the originating device505to notify the originating device505that the destination device510has answered the call. An RTP stream can be established (564,565) via which voice-based communications may be facilitated between the originating device505and the destination device510.

Although not illustrated inFIG. 5, it should be appreciated that functionalities for handling other various voice-based communication scenarios are envisioned. In particular, if the destination device510does not answer the voice-based call, an SIP480No Response message may be relayed to the originating device505. Further, the originating device505may cancel the call before the destination device510answers the call, in which case SIP cancel messages may be relayed to the various devices and components.

FIG. 6illustrates a signal diagram600associated with facilitating a voice-based communication that originates from an originating device610connected to a terrestrial-based network. Further, the voice-based communication is intended for a destination device605that is connected to a non-terrestrial-based network, such as if the destination device605is located on board a vehicle such as an aircraft. According to embodiments discussed herein, the voice-based communication can be a VoIP call, however it should be appreciated that other voice-based communications are envisioned. The signal diagram600includes the destination device605(such as the electronic device405as discussed with respect toFIG. 4), a data center629including an SBC/SIP server627(such as the SBC/SIP server427as discussed with respect toFIG. 4) and a registration server614(such as the registration server414as discussed with respect toFIG. 4), an SIP trunk provider612(such as the SIP trunk provider412as discussed with respect toFIG. 4), an HLR615(such as the HLR415as discussed with respect toFIG. 4), a mobile switching center613(such as the mobile switching center413as discussed with respect toFIG. 4), and the originating device610(such as the additional device410as discussed with respect toFIG. 4). For purposes of discussion, it should be appreciated that the destination device605has already completed the registration procedure with the registration server414, and has also purchased a product or service that enables voice-based communication via the non-terrestrial-based network.

A user of the originating device610can use the originating device610to initiate the voice-based communication (e.g., a VoIP call), for example via a telephone application. In particular, the user can input a telephone number associated with the destination device605and select to initiate the VoIP call. The originating device610can place (667) the VoIP call, which causes the originating device610to send a request to the HLR615associated with the destination device605. The HLR615examines a destination of the call (i.e., the destination device605) and can request (668) a routing number for the destination device605from the registration server614. The registration server614can allocate a routing number for the destination device605and provide (669) the routing number to the HLR615, which can forward (670) the routing number to the MSC613. After receiving the routing number, the MSC613send (671) an IAM/ISUP setup request indicating the routing number to the SIP trunk provider612.

The SIP trunk provider612can use the IAM/ISUP setup request to generate an SIP invite message that includes the routing number and send (672) the SIP invite message to the registration server614. The registration server614can examine the SIP invite message and confirm (673) that the destination device605has an active product or service. In particular, a user of the destination device605can have previously selected (e.g., on an in-flight trip) a service or product from a list of available services or products that may include various cellular connectivity options for the destination device605that are based on time durations, data limits, or other parameters. The registration server614can also replace (674) the routing number specified in the SIP invite message with an identification associated with the destination device605. In embodiments, the identification of the destination device605can be the IMSI of the destination device605. The registration server614can send (676) the SIP invite message to the SBC/SIP server627and also send (675) an SIP100trying message to the SIP trunk provider612.

According to embodiments, after receiving the SIP invite message, the SBC/SIP server627and the destination device605can establish a TLS connection according to various techniques, such as using a digital certificate previously issued to the destination device605during the registration procedure. Further, the SBC/SIP server627can send (678) the SIP invite message to the destination device605via the established TLS connection. A user of the destination device605can cause the destination device605to answer (679) the call, which causes the destination device to send (680) an SIP200OK message to the SBC/SIP server627. The SBC/SIP server627can forward (681) the SIP200OK message to the registration server614, which forwards (682) the SIP200OK message to the SIP trunk provider612, which forwards (683) the SIP200OK message to the HLR615, which sets up (684) a call request with the originating device610. An RTP stream can be established (685,686) via which voice-based communications may be facilitated between the originating device610and the destination device605.

Although not illustrated inFIG. 6, it should be appreciated that functionalities for handling other various voice-based communication scenarios are envisioned. In particular, if the destination device605does not answer the voice-based call, an SIP480No Response message may be relayed to the originating device610. Further, if the destination device605is busy, an SIP486Busy Here message may be relayed among the various devices and components.

In some embodiments, the voice data from the voice-based calls as described with respect toFIGS. 5 and 6may be converted into text-based data. Generally, passengers of a vehicle such as an airplane may not want to overhear another passenger of the vehicle participating in a voice call. The passengers may further not want to hear the other party of the voice call on the electronic device of the participating passenger on the vehicle (e.g., via a speakerphone feature of the electronic device). Therefore, it may be desirable to convert voice data to text data for at least the participating passenger. Further, it may be desirable to limit the participating passenger's ability to actively participate in a voice call while traveling in the vehicle.

In cases in which a voice-based communication is established between a first device connected to a non-ground-based network and a second device connected to a ground-based network, the first device may enable the user to input text (e.g., via an on-screen keyboard, a peripheral keyboard, or another channel) instead of receiving audio (i.e., speech). The first device may include logic to convert the inputted text into speech, such as through a text-to-speech application as known in the art. Accordingly, the second device can receive the speech converted from the text via the data center and output the converted speech via an audio output component. Similarly, the second device may include logic to convert audio data (i.e., speech) received from the user into text, such as through a speech recognition (SR) application as known in the art. The second device can send the generated text to the data center which forwards the generated text to the first device. Accordingly, instead of outputting received audio data, the first device can present the text that the second device converted from the initial audio data. In some cases, the second device need not convert the audio data and the first device may still output the audio data instead of text, such as in cases in which the audio is output via an earpiece speaker of the first device or via a headset. In still further cases, the voice call may be facilitated as a one-way voice call whereby the first device outputs received audio but does not transmit audio back to the second device (e.g., by muting a microphone).

The audio and text conversion techniques may alternatively be facilitated by other components. In some cases, the on-board communications network system of the vehicle may include modules or applications to perform either or both of the text-to-voice conversion or the voice-to-text conversion. In other cases, the data center (or more particularly, the registration server) may include modules or applications to perform either or both of the text-to-voice conversion or the voice-to-text conversion.

According to embodiments, the text- and voice-based communications may be facilitated via other networks in addition to or as an alternative to the terrestrial network implementation as described with respect toFIGS. 1-6. In one embodiment, a hybrid communications system may be employed to facilitate the text- and voice-based communications, whereby the data center129and the cellular network107as described with respect toFIG. 1may facilitate some communications between electronic devices, and the data center129and a satellite-based network may facilitate other communications between the electronic devices. In another embodiment, the data center129and a satellite-based network may facilitate all of the communications between electronic devices.

FIG. 7is a block diagram depicting an example hybrid communications system700for communicating information or data to and from devices that are being transported by the vehicles702. The system700is configured to deliver data or information to a specific device on-board one of the vehicles702(e.g., the device718on-board the vehicle702x) from a data center705(such as the data center129as described with respect toFIG. 1) or from a hybrid communications distributor704included in the data center705. In some implementations, the hybrid communications system700is configured to deliver feedback information from the vehicle702xto the data center705or the hybrid communications distributor704, and the data center705or the hybrid communications distributor704may use the feedback information to inform subsequent data delivery to the on-board device718or to other on-board devices. In an embodiment, the hybrid communications distributor704and the data center705are communicatively connected to the vehicles702via one or more vehicle data delivery networks706, one or more forward links708, and one or more reverse links710.

One or more of the vehicles702may be owned and/or operated by a specific individual. In some cases, one or more of the vehicles702may be owned and/or operated by a company, organization or government entity. For example, the vehicles702may include a fleet of vehicles that are used to transport passengers who pay for or otherwise are granted passage on one of the vehicles of the fleet. The vehicles702may include one or more vehicles that are used by an organization to transport employees and their guests, in some situations. One or more of the vehicles702may be used to transport live or inanimate cargo, packages, mail, and/or other types of cargo. It is noted that althoughFIG. 7depicts the vehicles702as being airplanes, the techniques and principles described herein equally apply to other types of vehicles such as trucks, automobiles, busses, trains, boats, ships, barges, subway cars, helicopters or other types of aircraft, ambulances or other emergency vehicles, military vehicles, other air-borne, water-borne, or land-borne vehicles, and vehicles that are suitable for space travel.

Each of the vehicles702may be communicatively connected to the data center705via one or more forward wireless communication links708and one or more reverse wireless communication links710. The links708,710may be collectively supported by a multiplicity of radio frequency (RF) bands. Typically, a particular frequency band or portion of RF spectrum supporting the links708,710is allocated (e.g., by a governmental or regulatory body) for a particular type of wireless communications such as satellite communications, ham-radio communications, terrestrial cellular communications, near-field wireless communications, and the like. In some allocated frequency bands, the wireless communications may be transmitted over a forward link and a corresponding reverse link using a respective wireless communication protocol that is defined, designated or otherwise indicated by a standards association and/or by a government or other regulatory body. A particular frequency band may support a point-to-point wireless protocol and/or may support a broadband wireless protocol, for example.

Each frequency band may include one or more channels. The channels may be formed, defined or allocated by frequency division, time division, code division, some other suitable channel division, or some combination of divisions. Signals that are carried on a channel may or may not be multiplexed. Any one or more channels included in a frequency band may support (or may be designated to support) a forward link and/or a reverse link for wireless communications. Additionally, any one or more of the channels included in a frequency band may be used to deliver signaling, data payload, or a combination of signaling and data payload. For example, a particular frequency band may support an in-band protocol in which signaling and payload are transmitted over a same channel within the band, and/or the particular frequency band may support an out-of-band protocol in which the signaling and payload are respectively transmitted over different channels within the band.

A transceiver or modem that is fixedly connected to a vehicle702xmay be tuned to a particular frequency band, and thus, along with a respective antenna, may serve as one end of a communication link over which data may be received onto and/or sent from the vehicle702x. Similarly, a transceiver or modem that is fixedly connected to a structure712external to the vehicle702xmay also be tuned to the particular frequency band, and thus, along with a respective antenna, may serve as the other end of the communication link over which the data is received onto and/or sent from the vehicle702x. The structure712that supports the non-vehicle end of the communication link may be, for example, an entirely stationary terrestrial structure such as a building or tower on the ground, a relatively stationary terrestrial structure such as a barge in an ocean, or a non-terrestrial structure such as a satellite or other structure in space. InFIG. 7, the representations of the structures712are duplicated to more clearly illustrate the forward links708and reverse links710, however, in practice, each structure712may be a unitary structure having a single physical transceiver or modem mounted thereon that services both the respective forward link708and the respective reverse link710. For example, a teleport712bmay include a transceiver that services both the satellite forward link708band the satellite reverse link710bof a particular frequency band allocated for satellite communications. In some instances, a single structure712may include multiple transceivers or modems, each of which may be tuned to a different frequency band.

With further regard to the structures712, in addition to having a transceiver or modem supporting one end of a particular communication link708,710to the vehicle702x, each structure712may include another interface via which a communication path715to the hybrid communications distributor704at the data center705may be communicatively connected. The interface to the communication path715may be a wired or a wireless communications interface.

A vehicle702xmay include one or more fixedly connected modems or transceivers to support one or more communication links708,710over one or more frequency bands, and the vehicle702xmay utilize these modems or transceivers to receive data onto the vehicle702xand/or to transmit data from the vehicle702x. For example, a vehicle702xmay include thereon a transceiver or modem tuned to a frequency band that is allocated for direct communications between vehicles702and ground stations, or on which a direct air-to-ground (ATG) communication link is supported (e.g., 849-851 MHz and 894-896 MHz). Such an ATG communication link is denoted inFIG. 7by the forward link708aand the reverse link710a. A vehicle702xmay additionally or alternatively include thereon a transceiver or modem tuned to a frequency band that is allocated for satellite communications (denoted inFIG. 7by the forward link708band the reverse link710b), such as the L band (e.g., 40 to 60 GHz or 1 to 2 GHz), the Kuband (e.g., 12-18 GHz), the Kaband (e.g., 26.5-40 GHz), and/or other spectrum that is allocated for satellite communications.

Other examples of communication links that may be established with the vehicle702xinclude terrestrial mobile or cellular communication links (denoted inFIG. 7by the references708c/710c), e.g., communication links that support TDMA (Time Division Multiple Access), GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access), Wi-MAX (Worldwide Interoperability for Microwave Access), LTE (Long Term Evolution), and/or other terrestrial mobile communications technologies. Yet another example of a type of communication link that may be established with the vehicle702xis wireless local area network (WLAN) or Wi-Fi™ link supported on a Wi-Fi allocated frequency band (e.g., 2.4 and/or 5 GHz), and using a protocol corresponding to an IEEE (Institute of Electrical and Electronics Engineers) 802.11 standard, as denoted inFIG. 7by reference708cfor a Wi-Fi forward link and reference710cfor a Wi-Fi reverse link. Still other examples types of wireless communication links that may be established with the vehicle702xinclude infrared, microwave, or other optically-based or line-of-sight wireless communication links. It is clear, however, that any suitable wireless communication link including a forward and/or reverse link may support communications between the data center705or the hybrid communications distributor704and a vehicle702x.

In an embodiment, one or more of the transceivers or modems fixedly connected to the vehicle702xmay be operated in a unidirectional mode, while one or more other transceivers or modems fixedly connected to the vehicle702xmay be operated in a bi-directional mode. For example, a transceiver or modem on the vehicle702xthat is tuned to a satellite communications spectrum may utilized in a receive-only mode, while another transceiver or modem on the vehicle702xthat is tuned to an ATG communications spectrum may be utilized in both receive and transmit modes.

Turning now to the hybrid communications distributor704included in the data center705of the system700, the hybrid communications distributor704may comprise, in an embodiment, a set of computer executable instructions that are stored on one or more non-transitory, tangible, computer-readable storage media (e.g., one or more memories or data storage entities), and that are executable by one or more processors of the data center705. (The data center705generally includes one or more computing devices having processors, and is described in more detail in a later section of the present disclosure.) The hybrid communications distributor704may manage data or information delivery, e.g., over the links708and710, to and from a device718that is being transported by a vehicle702x.

The device718may be a device that is fixedly connected to the vehicle702x(e.g., a computing device that is included in a Line Replaceable Unit (LRU) on an aircraft), or the device may be a mobile device such as a smart phone, tablet or laptop that is temporarily being transported by the vehicle, e.g., a mobile computing device belonging to a passenger on-board the vehicle. In an embodiment, the device718is a computing device including at least one memory and at least one processor, and optionally, at least one user interface and at least one wireless network interface. As used herein, the terms “target device,” “recipient device,” and “device” are used interchangeably to refer to a device718that is on-board a vehicle or being transported by the vehicle, and to which data that is external to the vehicle is to be electronically delivered.

The data that is to be delivered to the device718may include any type of data. For example, the data may include user-consumable content data such as a text message, a web page, a media file, streaming data, and/or a response to a previous request received at a user interface of the device718. In some cases, the data that is to be delivered to the device718includes data that is to be presented at a user interface of the device718. In some scenarios, the data that is to be delivered to the device718may be an application, a configuration, an update, or software that the user of the device718has requested to be downloaded.

In an embodiment, the hybrid communications distributor704may select one of the forward links708that are supported by respective one or more allocated frequency bands for delivery of data or information to the device718, and the hybrid communications distributor704may receive feedback data or information from the vehicle702xover a reverse link710supported by a different allocated frequency band. For example, the hybrid communications distributor704may select, from the links708, one particular forward link that is supported by a particular frequency band for forward data delivery to the device718, e.g., the satellite communications forward link708b. The hybrid communications distributor704may receive feedback information from the vehicle702xvia a particular reverse link, from the links710, that is supported by a frequency band other than the particular frequency band over which the forward data was delivered, e.g., the ATG reverse link710a. In some embodiments, the particular reverse link may be selected from the set of reverse links710. Accordingly, in this embodiment, a forward link and a reverse link of different frequency bands are paired or associated for data delivery purposes.

At least because forward link and reverse links are supported by different frequency bands, a different messaging protocol and/or delivery scheme (e.g., broadcast, multicast, unicast) may be used for sending information to the vehicles702than is used for receiving feedback information from the vehicles702. For instance, a broadband protocol may be utilized to deliver data over a selected forward link708b, and a point-to-point protocol may be utilized to deliver data over a reverse link710a. Additionally or alternatively, the hybrid communications distributor704may cause transmissions to be multicast over a forward link708b, and may receive feedback information over a reverse link710ain a unicast format. Such differing frequency bands, messaging protocols, and/or delivery schemes across the forward links708and the reverse links708and the selection(s) thereof may allow the hybrid communications system700to efficiently utilize available spectrum while, at the same time, adhering to existing modem constraints and/or regulatory requirements.

In an embodiment, the hybrid communications distributor704may select more than one forward link from the links708(each of which may be supported by a different frequency band) for distributed or hybrid delivery of data or information that is to be received, as a whole, at the device718on-board the vehicle702x. For instance, the hybrid communications distributor704may select both the satellite communications forward link708band the ATG forward link708ato deliver forward data, as a whole, to the device718, and a first portion of the data may be delivered using the satellite forward link708bwhile a second portion of the data may be delivered using the ATG forward link708a. In some cases, more than two forward links708may be selected for distributed data delivery to the vehicle702x. In this example, the hybrid communications distributor704may receive feedback information from the vehicle702xvia a reverse link that is included in the same frequency band as one of the selected forward links, e.g., the satellite communications reverse link710bor the ATG reverse link710a. Alternatively, the hybrid communications distributor704may receive feedback information from the vehicle702xvia a reverse link that is not included in the same frequency band as any of the selected forward links, e.g., the reverse link710c.

Thus, in view of the above, in general the hybrid communications distributor704may utilize any suitable combination of selected forward links708, reverse links710, messaging protocols, and/or delivery schemes to transmit data to and receive feedback information from the vehicles702in a distributed or hybrid manner. The hybrid communications distributor704and its selection and usage of the one or more forward link(s)708and the reverse link(s)710, messaging protocols, and/or delivery schemes for data delivery between the hybrid communications distributor704and the on-board devices718is discussed in more detail in later sections of this disclosure.

Turning now to the vehicles702, some or all of the vehicles702(e.g., the vehicle702x) may each include a respective on-board node720to manage data that is received onto the vehicle702xand that is intended for delivery to a particular on-board device718. The on-board node720may also manage data that is generated by the on-board devices718and that is to be transmitted from the vehicle702x, in an implementation. Further, within the vehicle702xitself, the on-board node720may manage communications of said data to and from the on-board devices718, e.g., by using one or more communication networks that are contained within the vehicle702x. In an embodiment, the on-board node720may include one or more computing devices that are communicatively connected to one or more transceivers or modems fixedly connected to the vehicle702x, and are also communicatively connected to one or more wired and/or wireless communication networks contained within the vehicle702x. In an embodiment, the on-board node720is included in an on-board data distribution system or device such as the data distribution device described in aforementioned co-pending U.S. patent application Ser. No. 13/675,200 entitled “VEHICLE DATA DISTRIBUTION SYSTEM AND METHOD.”

In some cases, the on-board node720may include a hybrid communications collector722. In an embodiment, the hybrid communications distributor704may comprise a set of computer executable instructions that are stored on a non-transitory, tangible computer-readable storage media (e.g., a memory) and are executable by one or more processors of the on-board node720. The hybrid communications collector722may receive, via one or more of the forward links708and respective modem(s), communications that are provided by the hybrid communications distributor704whose contents are intended for delivery to a particular on-board device718. The hybrid communications collector722may determine the recipient device718, and may cause the contents of the received communications to be delivered via one or more on-board networks to the recipient device718. Additionally, the hybrid communications collector722may cause feedback data or information to be transmitted via one or more reverse links710and their respective modem(s) for delivery to the hybrid communications distributor704. The feedback data or information may include, for example, data or information associated with any one or more communications previously received over one or more of the forward links708, data or information indicative of a state or condition of any one or more of the forward links708, and/or data or information indicative of a state or condition of any one or more of the reverse links710.

Turning now to the vehicle data delivery network706, in an embodiment, at least a portion of the vehicle data delivery network706may be disposed in a terrestrial location, e.g., a packet network router, an optical switch, etc. may be located within a climate-controlled structure on the ground. In an embodiment, at least a portion of the vehicle data delivery network706may be disposed in a non-terrestrial location, e.g., a routing node may be disposed on a satellite or aircraft. The vehicle data delivery network706may include a public network, a private network, or some combination of one or more public networks and one or more private networks. The vehicle data delivery network706may include a communications network, a data network, a packet network, or some combination thereof. The vehicle data delivery network706may include a hosted network, or may be a peer-to-peer or other type of ad-hoc network. Indeed, the vehicle data delivery network706may use any known networking technology or combination(s) thereof for delivering data. For example, the vehicle data delivery network706may use any known networking technology or combination(s) thereof for delivering data between the one or more structures712and the data center705or the hybrid communications distributor704at the data center705. Generally, the vehicle data delivery network706may include a plurality of computing devices that are communicatively connected. One or more portions of the vehicle data delivery network706may be included in the ground based system described in the aforementioned co-pending U.S. patent application Ser. No. 13/675,190 entitled “GROUND SYSTEM FOR VEHICLE DATA DISTRIBUTION,” in an embodiment.

The data center705may be communicatively connected to the vehicle data delivery network706, and may include one or more computing devices in communicative connection so that they collectively appear, to other networks and/or computing devices, as a single logical entity. In an embodiment, the data center705includes the hybrid communications distributor704. The data center705may be located at least partially in a terrestrial environment, e.g., in one or more stationary buildings or structures. For example, one or more portions of the data center705may be included in a ground distribution network, such as the ground distribution network described in aforementioned co-pending U.S. patent application Ser. No. 13/675,190. In an embodiment, at least a portion of the data center705may be located in a non-terrestrial environment, e.g., on an aircraft, satellite, or space station. It is clear, however, that the data center705may be located in any suitable environment, whether stationary, mobile, in a vehicle, terrestrial, or non-terrestrial. In an embodiment, multiple data centers705may be included in the hybrid communications system700for servicing different types of data, different customers, different geographical areas, or any other desired or suitable differentiations.

The data center705, and in particular, the hybrid communications distributor704included in the data center705, may be communicatively connected via one or more gateways730to one or more other networks732. Generally, a gateway730may include one or more computing devices in communicative connection, and may serve as a boundary between the hybrid communications system700and one or more other networks732. In some embodiments, at least some of the computing devices included in the gateway730may also be included in the data center705. The one or more other networks732in communicative connection with the gateway730may include, for example, the Internet, a PSTN (Public Switched Telephone Network), and/or some other public network. Additionally or alternatively, the one or more other networks732may include one or more private networks. The one or more networks732may include any number of wired and/or wireless networks. AlthoughFIG. 7illustrates the data center705being connected to one other network732via one gateway730, the techniques and principles described herein equally apply to hybrid communications systems700having and/or being in communicative connection with any desired number of other networks732via any number of gateways730. In some embodiments of the system700, the gateway730may be omitted.

In an embodiment, the other network732may provide data, e.g., via the gateway730or via a direct connection, data that is to be delivered to a particular device718that is on-board a vehicle702x. In an example, the other network732is the PSTN communicatively connected to a terrestrial, cellular network to which the device718is homed, and the data to be delivered to the device718is a text message or a voice mail forwarded by the home system. In another example, the other network732is communicatively connected, via a gateway730, to one or more computing devices that host a website which a user of the device718requests access, and information associated with the website (e.g., the web page, objects, and links thereon) is to be delivered to the device718for presentation on a user interface of the device718in response to the user request. In yet another example, the other network732is communicatively connected to a streaming media provider, and a streamed video file is the data is to be delivered to the on-board device718for consumption by the device's user at a user interface. Of course, any type of data may be provided to the data center705by any other network732(via the gateway730, if necessary) for delivery to an indicated device718on-board the vehicle702x, e.g., text messages, web pages, media content, streaming data, a response to a previous request received at a user interface of the device718, data that is to be presented at a user interface of the device718, an application, a configuration, or other software that the user of the device718has requested to be downloaded from the other network732. Additionally, return data or information from the on-board device718(e.g., an activation of a user control, a return text message, a request or command, etc.) that is received at the hybrid communications distributor704may be delivered (via the gateway730, if necessary) to the other network732.

FIG. 8illustrates an example method800for providing communications to and from a device being transported by a vehicle. In an embodiment, the method800is performed at least in part by the hybrid communications system700ofFIG. 7, although some or all of the method800may be performed by a communications system other than the system700. In an embodiment, at least a portion of the method800may be performed by the data center705or by the hybrid communications distributor704of the data center705. For ease of discussion, the method800is described below with simultaneous reference to the system700ofFIG. 7, however, this is only one of many embodiments and is understood to be non-limiting.

As previously discussed, the recipient device of the data or information included in the communications may be a computing device that is fixedly connected to a vehicle (e.g., a device that is included in an LRU on an aircraft), or the device may be a mobile computing device such as a smart phone, tablet or laptop computing device that is temporarily being transported by the vehicle. In fact, the device may be any device connected to any on-board communication network that is communicatively connected to the on-board node via which data is received onto the vehicle and/or delivered from the vehicle. For ease of discussion, though, and not for limitation purposes, the method800is described below in the context of an example scenario in which a device718is being transported by a particular vehicle702x.

At block802, content that is to be delivered to a particular device718being transported by a particular vehicle702xmay be received, e.g., from the network732, the vehicle data delivery network706, the data center705, or from any other suitable source. For example, the data center705or the hybrid communications distributor704of the data center705may receive the content that is to be delivered to the device718. The received content may include any type of data that may be consumed by a user of the device718, such as text messages, web pages, media content, streaming data, a response to a previous request received at a user interface of the device718, and/or data that is to be presented at a user interface of the device718. In some cases, the received content may be an application, a configuration, other software that the user of the device718has requested to be downloaded to the device718, or other data.

In an embodiment, the content is received in conjunction with an indication that the received content is to be specifically delivered only to the device718. For example, the received content may be received in one or more packets, messages or other communicated format including a destination address that particularly and singularly indicates or identifies the particular device718. In some cases, the specific device718is the only device being transported by the set of vehicles702that is to receive the content. Upon reception of the content and the indication of the device718, the hybrid communications distributor704may determine that the device718is currently being transported by (e.g., is on-board) the vehicle702x.

At block805, a transmission (e.g., a message, packet, or other suitable communication format) may be caused to be sent, via the vehicle data delivery network706and a forward link708, to the vehicle702xon which the device718is being transported. For example, the hybrid communications distributor704may cause the forward transmission to be sent to the vehicle702x. The forward transmission may include at least a portion of the received content and an indication of the device718to which the content included in the forward transmission is to be delivered. The forward link708may be supported by a first allocated frequency band, e.g., the forward link708aof an ATG communications band, or the forward link708bof a satellite communications band. In an embodiment, the forward link708may be included in a frequency band allocated for broadband communications.

In an embodiment, the forward transmission may be sent as a multicast transmission, e.g., a transmission that is sent to a plurality of destinations (including the vehicle702x) in an essentially parallel manner. The forward transmission may be multicast to multiple vehicles702even though the content included therein is to be delivered to only the device718and not to other devices on-board the vehicle702xor on-board other vehicles702. In an embodiment, the hybrid communications distributor704may include the content to be delivered to the device718and an indication or identifier of the device718in the forward transmission, and the hybrid communications distributor704may cause the forward transmission to be multicast over a forward link, e.g., the forward link708bof the satellite communications band. As such, the multicast transmission may be received by the particular vehicle702xand by one or more other vehicles702that have modems tuned to the frequency band over which the forward transmission is multicast. Each vehicle702that receives the multicast transmission may individually determine, e.g., based on the indication of the device718included in the multicast transmission, whether or not the device718to which the contents carried in the multicast transmission is to be delivered is currently on-board. In an embodiment, multiple contents respectively to be delivered to multiple recipient devices on-board multiple vehicles may be multiplexed into a single forward transmission.

At block808, feedback information or data corresponding to the forward transmission that was sent to the vehicle702xover the forward link may be received. In an embodiment, the feedback information is received at the hybrid communications distributor704via a reverse link supported by a different allocated frequency band than the frequency band supporting the forward link over which the forward transmission was sent. For example, if, at block805, the forward link over which the forward transmission is sent is the forward link708bof the satellite communications link, the reverse link at the block808over which the feedback information is received may be the ATG reverse link710aor the Wi-Fi reverse link710c. In an embodiment, the feedback information is included in a unicast transmission sent over the reverse link. For instance, the unicast transmission may be transmitted from the vehicle702xvia a selected return link710. The feedback information may then be delivered to the hybrid communications distributor704, e.g., via the vehicle data delivery network706using the unicast transmission format or another format.

The feedback information may include information or data corresponding to the forward transmission (block802), in an embodiment. For instance, the feedback information may include signaling information corresponding to the forward transmission received at the vehicle702xover the forward link, e.g., the feedback information may include reverse signaling such as an acknowledgement of a reception of the forward transmission, or an indication that an expected content was not received in the forward transmission. Accordingly, the forward link of one frequency band may serve as a forward data or payload delivery link, and the reverse link of another frequency band may serve as a signaling link corresponding to the forward data or payload delivery link. Such use of forward and reverse links in different frequency bands may allow efficient use of available communication spectrum while adhering to certain hardware/software constraints or regulatory requirements, in some cases.

For example, multiple forward data that is respectively delivered to various devices on board the vehicle702xor the vehicles702may be multiplexed into a single forward transmission over a broadband forward link (e.g., the forward satellite communications link708b). In an embodiment, multiplexed forward transmissions may be multicast to a plurality of vehicles702. Reverse signaling corresponding to the forward transmissions may be transmitted from the vehicle702x(or the vehicles702) over a lower-bandwidth reverse link (e.g., via the reverse ATG link710aor the reverse Wi-Fi link710c) rather than over the corresponding higher bandwidth reverse link (e.g., reverse signaling is not transmitted over the reverse satellite communications link710bin this example). In some cases, forward signaling corresponding to the payload may be transmitted from the hybrid communications distributor704over the lower-bandwidth link (e.g., the forward ATG link708aor the forward Wi-Fi link708c).

In some embodiments, the feedback information may include information corresponding to the availability, bandwidth, and/or quality of transmission of the forward link over which the forward transmission was received. For example, the on-board data distribution node720may determine the quality of the forward link over which the forward transmission was received based on characteristics of the received forward transmission, such as error correction, delay, and/or whether the contents were expected or not expected. In some cases, the on-board data distribution node720may determine the quality of the forward link (and/or the availability or bandwidth of the forward link, for that matter) via other data, such as the strength of signals received over the forward link, information detected by a link monitor, and the like. In a similar manner, the on-board data distribution node720may determine the availability, bandwidth, and/or quality of transmission of other forward links708and/or of any or all of the reverse links710.

At block810, a forward link over which a subsequent transmission is to be delivered to the vehicle702x(e.g., a “subsequent forward link”) may be selected based on the received feedback information. In an embodiment, after the hybrid communications distributor704has received the feedback information (block808), the hybrid communications distributor704may select, based on the received feedback information, a subsequent forward link to use for delivery of a subsequent transmission to the vehicle702x. For example, if the feedback information indicates that a quality of transmission or a bandwidth of one of the forward links has fallen below a threshold, that particular forward link may be removed from the selection pool of forward links, at least until the hybrid communications distributor704receives an indication that the quality or bandwidth of the particular forward link has returned to an acceptable level.

In an embodiment, the subsequent forward link may be selected additionally or alternatively based on a type of content that is included in the subsequent forward transmission. For example, a first forward transmission may include a text message that is to be delivered to the device718, whereas a subsequent forward transmission may include streaming media content that is to be delivered to another device on-board the vehicle702x. In this example, the hybrid communications distributor704may select an ATG forward link708ato deliver the text message (e.g., if the ATG forward link708acurrently has sufficient spare bandwidth to support the relatively small text message), and the hybrid communications distributor704may select the satellite forward link708bto deliver streaming media content, as the satellite forward link708bmay be a broadband connection link having a greater bandwidth or speed than that of the ATG forward link708a, which may better support the relatively larger media content. For example, the bandwidth or speed of the satellite forward link708bmay be two times greater than that of the ATG forward link708a, three times greater, four times greater, five times greater, six times greater, seven times greater, or greater by a factor larger than seven. In some cases, the hybrid communications distributor704may select a forward link based on a latency that may be tolerated for the particular content of the subsequent forward transmission. For example, a non-real time media stream such as a video may be buffered for later or delayed delivery to a recipient device.

At block812, the subsequent forward transmission is caused to be sent to the vehicle702xusing the selected forward link. For example, the subsequent forward transmission may be caused to be sent to the vehicle702xin a manner such as previously discussed with respect to the block805.

Any or all of the method800may be executed while the vehicle702xis any state that indicates a dynamic movement of the vehicle702x, or that indicates that the vehicle702xis en route or between an origination and a destination. For example, the vehicle702xmay be an aircraft, and at least a portion of the method800may be executed while the vehicle702xis in any one of a plurality of flight states, e.g., in-flight, climbing, descending, weight-on-wheels, or any one of a plurality of possible port states.

With regard to “port states,” generally, as used herein, a “port” may be a designated location from which vehicles may depart and at which vehicles may arrive. Examples of ports may include airports, shipping ports, railroad stations, hospitals, shipping terminals, bus terminals, fueling stations, vehicle maintenance or service areas, military bases, aircraft carriers, and the like. As such, a “port state” of a vehicle, as used herein, generally refers to a vehicle state indicating that the vehicle is in the vicinity of (or proximate to) a vehicle port, e.g., the vehicle is taking-off, landing, taxiing, parked, docked, in the harbor, in the freight yard, etc. A port state may indicate that the vehicle is stationary or is not stationary. A port state may be determined, for example, by determining that the vehicle is within a certain distance of a port, e.g., by using a geo-spatial location of the vehicle (e.g., as determined by a Global Positioning System or GPS), and/or by detecting the presence and/or a signal strength of a beacon signal that is transmitted by a transceiver of the port. Of course, vehicles that are not aircraft may nonetheless have the ability to be in a port state, e.g., when a boat is within a harbor or docked at a port, when a truck is at a gas station or weigh station, or any time when a vehicle is not traveling en route between ports.

In an embodiment, the entirety of the method800is executed while the vehicle702xis in a port state. In an embodiment, the entirety of method800is executed while the vehicle702xis in a dynamic movement state (e.g., in-flight, sailing, or moving along a highway). In an embodiment, the entirety of the method800is executed while the vehicle702xis in a stationary state (e.g., parked at a gate, stopped at a rest stop, or halted on a taxi-way).

FIG. 9illustrates an example method820for providing communications to and from a device being transported by a vehicle. In an embodiment, the method820is performed at least in part by the hybrid communications system700ofFIG. 7, although some or all of the method820may be performed by a communications system other than the system700. In an embodiment, at least a portion of the method820is performed by the hybrid communications collector722included in the on-board node720. In an embodiment, the method820may operate in conjunction with a least a part of the method800ofFIG. 8. For ease of discussion, the method820is described below with simultaneous reference to the system700ofFIG. 7and the method800ofFIG. 8, however, this description is only one of many embodiments and is understood to be non-limiting.

As previously discussed, the recipient device of the information or data included in communications received at the vehicle may be any device that is communicatively connected with any on-board communication network that, in turn, is communicatively connected to the on-board node via which the communications are received onto the vehicle. For ease of discussion only and not for limitation purposes, the method820is described below in the context of an example scenario in which the device718is a mobile computing device being transported by a particular vehicle702x.

At block822, a forward transmission including content that is to be delivered to the mobile device718on-board the vehicle702xis received at the vehicle702x. For example, the hybrid communications collector722of the on-board node720may receive a forward transmission including content that is to be delivered to the device718. In an embodiment, the content is to be delivered only to the device718, and not to any other device on-board the vehicle702x. The content may include data that is to be presented at a user interface of the device718, data that is to be stored at or executed by the device718, or any other data that is to be utilized by the device718or by a user of the device718, such as previously discussed.

The forward transmission may be received (block822) over one of a plurality of forward links to the vehicle702xand its respective modem that is fixedly connected to the vehicle702x. The forward link over which the forward transmission is received may be supported by a first allocated frequency band, e.g., the forward link708bof the satellite communications band.

In an embodiment, the forward transmission may be received at the vehicle702x(block822) as a multicast transmission. The multicast transmission may include the content to be delivered to the device718and an indication or identifier of the target or recipient device718. In an embodiment, the content and the indication of the target device718may be multiplexed, in the multicast transmission, with other content that is intended to be delivered to the target device718or to other target devices on-board any of the vehicles702. At the particular vehicle702x, the hybrid communications collector722may recover the content and the indication of the content's target device718after de-multiplexing the multicast transmission, or after using some other suitable technique to extract the desired information from the forward transmission.

Based on the indication of the device718included in the forward transmission, the hybrid communications collector722may determine whether or not the device718to which the content is to be delivered is currently on-board the vehicle702x. If the device to which the content is to be delivered is determined to be not on-board the vehicle702x, no further processing on the received forward transmission may be performed. If the device to which the content is to be delivered is determined to be on-board the vehicle702x, e.g., the device718, the method820may include causing the content of the received transmission to be sent to the recipient or target device718via one or more communication networks contained within the vehicle702x(block825). For example, if the device718is a mobile computing device connected to a Wi-Fi network on-board the vehicle702x, the hybrid communications collector722may include the content in an IEEE 802.11 compatible transmission, and may cause the transmission to be delivered over the on-board Wi-Fi network to the device718. Other examples of on-board data delivery other than Wi-Fi, though, are additionally or alternatively possible. Indeed, the method820may use any means and/or techniques of delivering, within the vehicle702x, the received content to an on-board device, such as any of the means and/or techniques described in the aforementioned co-pending U.S. patent application Ser. No. 13/675,200.

At block828, feedback information may be caused to be transmitted from the vehicle702x. In an embodiment, the feedback information may be transmitted from the vehicle702xusing a reverse link that is supported by a different allocated frequency band than the frequency band supporting the forward link over which the forward transmission was received (block822). For example, if the forward link (block822) is the forward link708bof the satellite communications link, the reverse link over which the feedback information is transmitted (block828) may be the ATG reverse link710aor the Wi-Fi reverse link710c. In an embodiment, the feedback information is included in a unicast transmission sent over the reverse link. For instance, the hybrid communications collector722may cause the unicast transmission may be transmitted from the vehicle702xvia the selected return link710.

As previously discussed with respect toFIG. 8, the feedback information may include information or data corresponding to the received forward transmission (block822) or to other received forward transmissions, information or data corresponding to the forward link over which the forward transmission (block822) was delivered to the vehicle702x, information or data corresponding to other forward links, and/or information or data corresponding to one or more reverse links. For example, the feedback information may include reverse signaling information corresponding to the forward transmission received at the vehicle702xover the forward link (block822), e.g., the feedback information may include an acknowledgement of a reception of the forward transmission, or that an expected content was not received in the forward transmission. As such, in this example, the vehicle702xmay utilize the forward link of one frequency band as a forward data or payload delivery link, and may utilize the reverse link of another frequency band as a signaling link corresponding to the forward data or payload delivery link.

In an embodiment, the vehicle702xmay utilize the forward link (e.g., the forward link of block822) as a unidirectional communication link. For example, the vehicle702xmay cause the transceiver or the modem that is connected to the communications link including the forward link to operate in a receive-only mode. The vehicle702xmay utilize the second communication link as a reverse link corresponding to the unidirectional forward link (e.g., the reverse link of block828). The vehicle702xmay utilize the second communication link as a unidirectional link (e.g., by placing the transceiver or modem connected to the second communication link in a transmit-only mode), or the vehicle702xmay utilize the second communication link as a bi-directional link (e.g., by allowing the transceiver or modem connected to the second communication link to be used in both receive and transmit modes).

It is noted that the vehicle702xmay utilize numerous different configurations and numbers of first and second communication links to realize the hybrid communication techniques discussed herein, e.g., techniques in which communications are delivered to and from devices on-board a vehicle using forward and reverse links of different communications frequency bands. For example, at least some of the techniques described herein may be realized by using one or more full duplex (e.g., bi-directional) communication links as a logical forward link, and by using one or more other full duplex communication links supported by one or more frequency bands different than the frequency band(s) of the logical forward link as a corresponding logical reverse link. In another example, at least some of the techniques described herein may be realized using one or more uni-directional communication links as the logical forward link, and using one or more other uni-directional communication links supported by one or more frequency bands different than the frequency band(s) of the logical forward link as a corresponding logical reverse link. In yet another example, one or more full-duplex communications links may be used as the logical forward link, and one or more uni-directional communications links supported by one or more frequency bands different than the frequency band(s) of the logical forward link are used as a corresponding logical reverse link. In still another example, one or more uni-directional communications links may be used as the logical forward link, and one or more full-duplex communications links supported by one or more frequency bands different than the frequency band(s) of the logical forward link are used a corresponding logical reverse link.

At block830, a subsequent forward transmission may be received at the vehicle702x. The subsequent forward transmission may include additional content that is to be delivered to the device718, or the subsequent forward transmission may include content that is to be delivered to other devices on-board the vehicle702xor on-board other vehicles702. The subsequent forward transmission may be received over one of a plurality of forward links to the vehicle702x, and the forward link over which the subsequent forward transmission is received may have been selected based on the feedback information previously transmitted from the vehicle702x(block828), and/or may have been selected based on a type of the additional content. As such, the forward link of block830may be the same forward link of block822, or may be a different forward link.

The hybrid communications collector722may determine whether or not the device to which the content of the subsequent forward transmission is to be delivered is currently on-board the vehicle702x, e.g., in a similar manner as discussed above with respect to block825. If the device to which the content is to be delivered is determined to be not on-board the vehicle702x, no further processing on the subsequent transmission may be performed. If the device to which the content is to be delivered is on-board the vehicle702x, e.g., the device718, the method820may include causing the content of the received subsequent transmission to be sent to the recipient or target device718via one or more communication networks contained within the vehicle702x(block832), e.g., in a manner similar to that discussed above with respect to the block825.

In an embodiment, after the block832, the method820may include causing subsequent feedback information to be sent from the vehicle702x(not shown). The subsequent feedback information may include data or information corresponding to the subsequent forward transmission, to the forward link over which the subsequent forward transmission was delivered to the vehicle702x, to other forward links, and/or to one or more reverse links. For example, the hybrid communications collector722may cause the subsequent feedback information to be transmitted from the vehicle702xusing a selected reverse link for delivery to the hybrid communications distributor704in a manner similar to that discussed with respect to block828. The hybrid communications distributor704may then utilize the subsequent feedback information to select a next forward link, in an embodiment.

Similar to the method800, any or all portions of the method820may be executed while the vehicle702xis any state that indicates a dynamic movement of the vehicle702x, such as a flight state or a state indicating that the vehicle702xis traveling between ports. Any or all of the method820may be executed while the vehicle702xis any port state. Any or all of the method820may be executed while the vehicle702xis in stationary state (e.g., parked at the gate, docked at a port, or halted on a taxi-way).

A block diagram of an example data communication tunnel1000that may be established in the hybrid communications system700or in another hybrid communications system is provided inFIG. 10. As used herein, the terms “data communication tunnel,” “data tunnel,” and “tunnel” are used interchangeably to refer to an encapsulated transmission path or logical connection, e.g., between a node or data center1002that is external to the vehicle702x, and a node1004that is on-board the vehicle702x. In some cases, the data communication tunnel1000may be an encapsulated transmission path or logical connection having a first endpoint that is external to the vehicle702x. For example, the first endpoint of the data tunnel may be the data center1002or may be a hybrid communications distributor1006at the data center1002. In an embodiment, the hybrid communications distributor1006may be the hybrid communications distributor704ofFIG. 7.

The data communication tunnel1000may have a second endpoint that is disposed on-board the vehicle702x. For example, the second endpoint of the data tunnel1000may be the on-board node1004, or may be an application1008executing on the on-board node1004, such as the hybrid communications collector722executing on the on-board node720. In some cases, the second endpoint of the data tunnel1000may be the recipient device718, or may be the VTA or some other application executing on the recipient device718.

The data tunnel1000may be realized, in an embodiment, by utilizing a tunneling protocol between the two endpoints. The packets or transmissions of the tunneling protocol may be encapsulated within packets or transmissions of other protocol(s) used by communication link(s) supporting the tunnel1000. As an example, referring simultaneously toFIGS. 7 and 10, an example data tunnel between the hybrid communications distributor704and the device718on-board the vehicle702xmay include a data tunnel forward link1010that uses a data tunnel protocol. Forward packets of the data tunnel protocol may be encapsulated by each of the respective protocols used by the various forward links supporting the data tunnel forward link1010e.g., respective protocols used by the vehicle data delivery network706, a selected forward link708, and the Wi-Fi forward link within the cabin of the vehicle702x. Similarly, a data tunnel reverse link1012between the hybrid communications distributor704and the device718may be supported by a Wi-Fi reverse link within the cabin of the vehicle702x, a selected reverse link710, and the vehicle data delivery network706, e.g., each of the respective protocols utilized on these various supporting reverse links encapsulates the data tunnel protocol packets in the reverse direction.

In embodiments where the data tunnel1000is included in the hybrid communications system700, the data tunnel forward link1010may be supported by one or more communication links that differ in protocol and/or frequency band from the one or more communication links supporting the data tunnel reverse link1012. Further, the data tunnel forward link1010and the data tunnel reverse link1012may differ in their respective supporting message delivery schemes (e.g., multicast or unicast), and/or in the number of supporting communication links used (e.g., multiple supporting communication links in the data tunnel forward link1010and one supporting communication link in the data tunnel reverse link1012). Nonetheless, the data tunnel1000between the data center1002and on-board node1004may be, in some cases, logically represented (e.g., in a software application) as having one logical data tunnel forward link1010or forward stream of data, and one logical data tunnel reverse link1012or reverse stream of data, in an embodiment.

Forward data1014, or data sent on the data tunnel forward link1010to the on-board node1004, may include, for example: (i) content1018for delivery to one or more on-board recipient devices that are in communicative connection to the on-board node1004, where the content1018may include any type of data, such as text messages, web pages, media content, streaming data, a response to a previous request received at a user interface of an on-board device, data that is to be presented at a user interface of an on-board device, an application, a configuration, other software that the user of an on-board device has requested to be downloaded, etc.; (ii) signaling information1016corresponding to the content1018and to the delivery of the content1018over the data tunnel1000; (iii) device information1020aidentifying the on-board recipient device or devices to which the content1018is to delivered; and/or (iv) other forward signaling information1016corresponding to usage of the data tunnel1000itself (e.g., availability, quality of transmission, bandwidth management, etc.).

Reverse data1022, or data sent on the data tunnel reverse link1012to the data center1002, may include, for example: (i) feedback information1024corresponding to the delivered content1018and/or corresponding to the usage of data tunnel1000(e.g., availability, quality of transmission, bandwidth management, etc.); (ii) content requests1026from on-board devices, where the content requests1026are generated by a user of an on-board device or by the on-board device itself; and/or (iii) device information1020bidentifying the on-board devices generating the content requests1026.

Although several specific examples of forward data1014and reverse data1022are discussed above, it is understood that the data tunnel forward link1010and the data tunnel reverse link1012may carry any desired type of data between the endpoints of the tunnel1000. Additionally, it is clear that the forward data1014may be split, aggregated, multiplexed, or combined into any number of data structures, packets, or messages, e.g., for the sake of efficiency and timeliness. Similarly, the reverse data1022may additionally or alternatively be split, aggregated, multiplexed, or combined into any number of data structures, packets, or messages. Furthermore, in an embodiment, multiple data tunnels may be established between the two endpoints. For example, the data center1002or the hybrid communications distributor1006included therein may establish multiple data communication tunnels with the node1004on the particular vehicle702x, and/or may establish multiple data communication tunnels with multiple nodes on multiple vehicles702.

FIG. 11illustrates an example method880for delivering content, in a distributed or hybrid manner, to a device that is on-board a vehicle. In an embodiment, the method880is performed at least in part by the hybrid communications system700ofFIG. 7, although some or all of the method880may be performed by a communications system other than the system700. In an embodiment, at least a portion of the method880is performed by the data center705or by the hybrid communications distributor704included in the data center705. In an embodiment, the method880may operate in conjunction with a least a part of one or more of the methods described inFIGS. 8 and 9, and/or with the data tunnel1000ofFIG. 10. For ease of discussion, the method880is described below with simultaneous reference toFIGS. 7-10, however, this description is only one of many embodiments and is understood to be non-limiting. Additionally, for ease of discussion only and not for limitation purposes, the method880is described below in the context of an example scenario in which data is to be delivered to a device718that is on-board a particular vehicle702xof a plurality of vehicles702.

At block882, content that is to be delivered to a device718being transported by a vehicle702xmay be obtained. For example, content that is to be delivered to the device718may be obtained by the data center705or by the hybrid communications distributor704of the data center705, e.g., by receiving the content from an external network732, the vehicle data delivery network706, or other suitable source, or from obtaining the content from the data center705itself or from some other data storage entity. The device718to which the content is to be delivered may be any device previously discussed with respect toFIGS. 7-10, e.g., a mobile computing device being temporarily transported by the vehicle702x, or a computing device that is fixedly connected to the vehicle702x. Similarly, the content to be delivered to the device718may be any type of content previously discussed with respect toFIGS. 7-10, e.g., a web page, streaming data, a text message, a response to a previous request, etc. With respect to the method880, though, the content to be delivered to the device718is to be delivered to the device718as a whole, e.g., an entire web page, a streaming video or movie, etc. In embodiment, the obtained content is to be delivered to the device718as a whole to be presented, as a whole, at a user interface of the device718.

At block885, a first portion of the obtained data may be included in a first transmission, and the first transmission may be caused to be sent via a first forward link to the vehicle702x. At block888, a second portion of the obtained data may be included in the second transmission, and the second transmission may be caused to be sent via a second forward link to the vehicle702x. The first forward link and the second forward link may each be supported by a different communication link on a different frequency band, and thus the first transmission and the second transmission may each be formatted using a different protocol. For example, a first portion of the obtained data may be caused to be sent to the vehicle702xover the satellite forward link708b, and a second portion of the obtained data may be caused to be sent to the vehicle702xover the ATG forward link708a. In an embodiment, the bandwidth or speed of the first forward link may be two times greater than that of the second forward link, three times greater, four times greater, five times greater, six times greater, seven times greater, or greater by a factor larger than seven.

In some embodiments of the method880, at least one of the contents of the first portion of the obtained data or the contents of the second portion of the obtained data may be selected. In an embodiment, the contents of the first or the second portion may be selected based on a content type. For example, if the obtained content is a web page to be displayed at a screen of the target device718, for an optimal user experience, a user desires to see some progress of the loading of the web page. Accordingly, critical elements of the web page (e.g., CSS, HTML, Java script, and other structural elements) may be selected to be delivered to the vehicle702xby a faster forward link (e.g., the ATG forward link708a) so that these critical elements may be received as soon as possible at the device718to begin establishing the web page framework, and to demonstrate to the user that some progress is occurring. On the other hand, larger-sized elements of the web page (e.g., image, video, flash, etc.) may arrive at the user device after the critical elements, and may be inserted into the already-established webpage framework. These larger elements, although not as time-critical to the user experience, nonetheless require high bandwidth due to their size and density and, as such, may be selected to be delivered to the vehicle702xby a high-bandwidth forward link (e.g., the satellite forward link708b).

Generally, the more time sensitive portions (e.g., portions that require a low round trip delay time) of an obtained content may be selected to be delivered over a faster forward link (as compared to other available forward links708), the higher density or larger-sized portions of the obtained content may be selected to be delivered over a higher capacity forward link (as compared to other available forward links708), the portions of the obtained content that require a greater degree of accuracy may be selected to be delivered over a more robust forward link (as compared to other available forward links708), etc. In some situations, a particular content type may be exclusively assigned to one particular type of forward link for delivery, and optionally may be assigned to a back-up type of forward link if the primary forward link is unavailable. In some situations, a particular content type may be assigned to multiple types of forward links, optionally with a priority order of selection, e.g., the highest priority, available forward link is selected for delivery of the certain content type.

In still another example, within a given forward link, certain types of data may be given priority over other types of data. For instance, in a satellite forward link, overflow data from an ATG forward link may be given higher priority than data that has been originally mapped to the satellite forward link, as the overflow ATG traffic may generally be more time sensitive than the satellite traffic.

In some embodiments of the method880, a particular forward link may be selected for a particular type of content data further based on other criteria, such a dynamic characteristic or status of one or more forward links, or on a characteristic of the obtained content as a whole. For example, when the obtained content is a streaming video, streaming media coded picture frames (e.g., I-frames) may be assigned or selected to be delivered over the ATG forward link708a, while the corresponding streaming media predictive frames (e.g., P-frames, B-frames) may be assigned or selected to be delivered over a Kasatellite frequency band. However, the bandwidth allocated for any particular stream within the Kaband may be capped at a certain level. If the streaming media content reaches the cap within the Kaband, subsequent predictive frames of the stream may be delivered via another forward link, e.g., the L satellite frequency band. In another example, a particular type of content data may be assigned or selected to be delivered over an ATG forward link708a, and when the ATG forward link is at a pre-defined capacity, overflow of the particular type of content data may be assigned or selected to be delivered over the satellite forward link708b. In another example, any data stream greater than a certain size may be automatically mapped to be distributively delivered over all available satellite forward links.

In an embodiment, the selection of a particular forward link may be based, at least in part, based on feedback data or information received from the vehicle702x. Feedback information or data may be indicative of a current quality, capacity, or availability of one or more forward links, e.g., as previously described with respect toFIGS. 8-10. The data center705or the hybrid communications distributor704may receive feedback data or information via a reverse link, and may select a subsequent forward link for transmission of a particular portion of obtained content at least partially based on the received feedback information or data, in an embodiment.

Thus, as illustrated by the examples, portions of the content data may be mapped to various forward links based on many levels of granularity and differentiation criteria. For example, as previously indicated, mapping of different portions of content data to different forward links may be based on content type. Mapping may additionally or alternatively be based on a type of application to which the obtained content is to be delivered, and/or based on a stream size in which the obtained content is included. Still additionally or alternatively, mapping of portions of the obtained content to various forward links may be based on, for example, socket types or availability of sockets, a level of service paid for by or otherwise assigned to a user of the recipient device, a quality and/or an availability of various forward links, dynamic resource allocation algorithms, etc. Further, mapping of portions of the obtained content to various forward links may be additionally or alternatively performed at different levels, e.g., at an application level, a packet level, a stream level, a level based on geographical location, a level based on a characteristic of an account of the user, or a level of service acquired by the user.

In an embodiment, the mapping of certain content types to certain forward links are determined a priori and the mappings are stored in a file or other data storage entity that is accessible to the data center705or to the hybrid communications distributor704. In some embodiments, a particular forward link may be selected for a particular type of data content based on the a priori mapping. The mappings of content portions and forward links may be configurable, in an embodiment.

With further regard to the method880, similar to the each of the methods800and820, any of the forward transmissions over any of the forward links708may include multiplexed contents or portions of contents that are to be delivered to the device718and/or to other devices being transported on the vehicles702. Similarly, each of the methods800,820,880may multicast any forward transmission over any forward link708, as desired.

FIG. 12illustrates an example method1200for distributively delivering content to devices being transported by vehicles. In an embodiment, the method1200is performed at least in part by the hybrid communications system700ofFIG. 7, although some or all of the method1200may be performed by a communications system other than the system700. In an embodiment, at least a portion of the method1200is performed by the on-board node720at the vehicle702x, by the hybrid communications collector722included in the on-board node720, by a recipient device718, or by an application executing on the recipient device718such as the VTA. In an embodiment, the method1200may operate in conjunction with at least a part of one or more of the methods described inFIGS. 2-5 and 7, and/or with the data tunnel600ofFIG. 6. For ease of discussion, the method1200is described below with simultaneous reference toFIGS. 7-11, however, this description is only one of many embodiments and is understood to be non-limiting. Additionally, for ease of discussion only and not for limitation purposes, the method1200is described below in the context of an example scenario in which data is to be delivered to a device718that is on-board a particular vehicle702xof a plurality of vehicles702.

At block1202, a first transmission including a first portion of content that is to be received, as a whole by the on-board device718, is received at the vehicle702x. For example, the on-board node720, the hybrid communications collector722, the device718or an application on the device718(e.g., the VTA) receives the first portion of the content. In an embodiment, the content that is to be received, as a whole by the device718, is to be presented, as a whole, at a user interface of the device718. For example, the content that is to be presented as a whole at the user interface of the device718may be a web page, streaming video, a response to a request from a user of the device718, or any other type of content that is to be delivered to the device718such as previously discussed with respect toFIGS. 7-11. The first portion of the content may be received onto the vehicle702xvia a first modem connected to a first forward link (e.g., one of the forward links708) that is supported by a first wireless frequency band, and the first portion of the content may be received in conjunction with an indication of the device718to which the first portion of the content is to be delivered.

At block1205, a second transmission including a second portion of content that is to be received, as a whole by the on-board device718, is received at the vehicle702x. For example, the on-board node720, the hybrid communications collector722, the device718or an application on the device718(e.g., the VTA) receives the second portion of the content. The second portion of the content may be received onto the vehicle702xvia a second modem connected to a second forward link (e.g., another forward link from the set of forward links708) that is supported by a second wireless frequency band different than the first wireless frequency band. The second portion of the content may be received in conjunction with an indication of the device718to which the second portion of the content is to be delivered.

In an embodiment, the first forward link, the second forward link, the first portion of the content, and/or the second portion of the content may have been selected. For example, the first forward link, the second forward link, the first portion of the content, and/or the second portion of the content may have been selected by the data center705or by the hybrid communications distributor704based on the criteria for forward link and/or content portion selection as previously described herein, or based on other criteria.

In an embodiment, based on the indication of the device718included in the first forward transmission, the hybrid communications collector722may determine whether or not the device718to which the first portion of the content is to be delivered is currently on-board the vehicle702x. If the device to which the first portion of the content is to be delivered is determined to be not on-board the vehicle702x, no further processing on the first forward transmission may be performed at the vehicle702x. If the device to which the first portion of the content is to be delivered is determined to be on-board the vehicle702x, e.g., the device718, the method1200may include causing the content of the first received transmission to be sent to the recipient or target device718via one or more communication networks contained within the vehicle702x(block1208). For example, if the device718is a mobile computing device connected to a Wi-Fi network on-board the vehicle702x, the hybrid communications collector722may include the first portion of the content in an IEEE 802.11 compatible transmission, and may cause the transmission to be delivered over the on-board Wi-Fi network to the device718. Other examples of on-board data delivery other than Wi-Fi, though, are additionally or alternatively possible. Indeed, the method1200may use any means and/or techniques of delivering the received content to an on-board device, such as any of the means and/or techniques described in the aforementioned co-pending U.S. patent application Ser. No. 13/675,200.

With regard to the second forward transmission, in an embodiment, based on the indication of the device718included in the second forward transmission, the hybrid communications collector722may determine whether or not the device718to which the second portion of the content is to be delivered is currently on-board the vehicle702x. If the device to which the second portion of the content is to be delivered is determined to be not on-board the vehicle702x, no further processing on the second forward transmission may be performed at the vehicle702x. If the device to which the second portion of the content is to be delivered is determined to be on-board the vehicle702x, e.g., the device718, the method1200may include causing the content of the second received transmission to be sent to the recipient or target device718via one or more communication networks contained within the vehicle702x(block1210). For example, if the device718is a mobile computing device connected to a Wi-Fi network on-board the vehicle702x, the hybrid communications collector722may include the second portion of the content in an IEEE 802.11 compatible transmission, and may cause the transmission to be delivered over the on-board Wi-Fi network to the device718. Other examples of on-board data delivery other than Wi-Fi, though, are additionally or alternatively possible. Indeed, the method1200may use any means and/or techniques of delivering the received content to an on-board device, such as any of the means and/or techniques described in the aforementioned co-pending U.S. patent application Ser. No. 13/675,200.

In an embodiment, the first external forward link708and the forward link of the on-board communication network to which the device718is connected (e.g., the on-board Wi-Fi network or other suitable network) support a first data communication tunnel established by the data center705(or by the hybrid communications distributor704included in the data center705). For example, the first forward link and the forward link of the on-board Wi-Fi network to the device718support a first data tunnel forward link similar to the data tunnel forward link1010ofFIG. 10, and the first portion of the content is delivered to the device718using the first data tunnel forward link.

In an embodiment, the second external forward link708and the on-board forward link to which the device718is connected (e.g., the on-board Wi-Fi network or other suitable network) support a second data communication tunnel established by the data center705(or by the hybrid communications distributor704included in the data center705) that is distinct and separate from the first data communication tunnel. For example, the second external forward link708and the second on-board forward link to the device718support a second data tunnel forward link1010, and the second portion of the content is delivered to the device718using the second data tunnel forward link. In this embodiment, the device718or an application at the device718(e.g., the VTA) may assemble the first portion and the second portion to form the content as a whole at the device718, in some cases, over time. For example, the device718or the application at the device718may first receive the first portion of the content, and begin presenting the first portion of the content at a user interface of the device. When the second portion of the content is received, the device718or the application at the device718may add the second portion of the content to the presented first portion so that the content as a whole is presented at the user interface of the device.

In an embodiment, rather than the device718(or an application thereon) serving as the on-board endpoints of the two established data tunnels to the data center705, the on-board device720or the hybrid communications collector722of the on-board device720serves as the on-board endpoints of two established data tunnels to the data center705(where one of the two established data tunnels delivers the first portion of the content to be delivered to the device718, and the other one of the two established data tunnels delivers the second portion of the content). In this embodiment, rather than the device718(or an application thereon) collecting and assembling the content as a whole, the on-board device720or the hybrid communications collector722collects and assembles the content as a whole, and causes the assembled content to be delivered to the device718, e.g., via an on-board communication network.

In an embodiment, the on-board node720, the hybrid communications collector722, the device718, or an application on the device718may cause feedback information or data to be sent, via a reverse link710, from the vehicle702xto the data center705. Feedback information or data may correspond to the received first portion of the content and/or to the received second portion of the content, for example. In an embodiment, the feedback information or data may be indicative of a current quality, capacity, or availability of one or more forward links and/or of one or more reverse links, e.g., as previously described with respect toFIGS. 8-11.

Thus, as discussed above, a hybrid communications system, such as the example hybrid communications system700, may allow transmission of data and information to devices on-board a vehicle using a forward link and a reverse link, each of which may be supported by a different frequency band and each of which may utilize a different communication protocol. The forward link may differ in frequency band, hardware configuration, protocol, spectrum, etc., as compared with the reverse link corresponding to the reverse direction. In an embodiment, the bandwidth and/or the speed of the forward link may be greater than (and in some cases, significantly greater than) the bandwidth and/or the speed of the reverse link to allow for efficient use of spectrum and modem resources, and for decreased data delivery times. In an embodiment, forward transmissions may be multiplexed and/or multicast. Selection of a forward link for a subsequent transmission may be based on feedback information received via the reverse link, and in some cases, may also be based on a type of the content that is to be delivered. In an embodiment, a hybrid communications system, such as the example hybrid communications system700, may utilize multiple different forward links to deliver content as a whole between a device that is on-board a vehicle and a data center. Selection of portions of contents and/or of the multiple forward links may be based on a content type and optionally other criteria.

FIG. 13illustrates an example on-board system1300in a vehicle1302that may receive information or data onto the vehicle1302(e.g., information or data provided by the data center, the hybrid communications distributor704, or other suitable information distributor), and that may cause feedback information to be delivered from the vehicle1302, e.g., to the data center705or the hybrid communications distributor704. Further, the on-board system1300may cause data to be delivered to and/or received from one or more devices1304being transported by the vehicle1302. In an embodiment, the vehicle1302is the vehicle702x, and the one or more devices1304is one of the devices718.

The example on-board system1300includes an on-board node1306, such as an Auxiliary Computer Power Unit (ACPU), that may be a computing device communicatively connected to one or more external communication links via one or more antennas1308and one or more modems or transceivers1310. In an embodiment, the on-board node1306may be the on-board node720, and may include an instance of the hybrid communications collector722, which is represented inFIG. 13by the block1307.

Each of the one or more antennas1308may receive and transmit signals via a different respective frequency band allocated for wireless communications, e.g., the Kaband, the L band, the Kuband, the WiMAX band, the Wi-Fi band, a terrestrial cellular band, or any other suitable wireless communication frequency band. Each of the antennas1308may be communicatively connected to an associated modem or transceiver1310that is fixedly connected to the vehicle1302and is configured to encode and decode information and data corresponding to signals at the respective antenna1308, in an implementation. The one or more modems or transceivers1310may include a respective modem or transceiver that is compatible with TDMA (Time Division Multiple Access), GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access), LTE (Long Term Evolution) communications, WiMAX, and/or any other terrestrial mobile communications technology. In some embodiments, the one or more modems1310may include a respective modem or transceiver that is compatible with EVDO (Evolution Data Optimized) or Wi-Fi communications technologies. It is clear, however, that the on-board system1300may include any number of antennas1308and any different number of associated modems or transceivers1310to support any desired number of different wireless communication technologies.

In addition, when the vehicle1302is an aircraft, a cockpit electronics node1312may be communicatively coupled to the one or more modems1310. The cockpit electronics node1310may be a LRU configured to collect electronic information from various instruments in the cockpit of the aircraft, e.g., during flight. In some cases, the cockpit electronics node1310may provide collected flight information such as altitude, airspeed, aircraft position, or other flight state information to the hybrid communications obtainer1307, the on-board node1306, or directly to the vehicle data distribution network706, e.g., via a designated return link.

At least some of the devices1304may be mobile computing devices such as smartphones, tablet computers, laptop computers, personal digital assistants, e-readers, etc. that are capable of establishing a wireless communicative connection with the hybrid communications obtainer1307via one or more wireless access points1314, e.g., via a wireless network interface. Some of the devices1304may be wired computing devices that are communicatively connected to the on-board node1306via a wired network1316.

In some implementations, one or more of the devices1304may be an on-board data storage entity1318that may store various types of data which may be distributed to and/or received from other devices1304, e.g., entertainment content, web pages, account information, usage data, applications that may be installed, information identifying the devices1304, payment information (e.g., encrypted financial account information), digital rights management (DRM) keys, and/or any other data that is desired to be stored, at least temporarily, on-board the vehicle1302.

In an embodiment, each of devices1304may include an instance of a vehicle travel application (VTA) installed thereon and particularly configured to support services while the device1304is being transported by the vehicle1302, e.g., when the vehicle1302is traveling en route between ports. For example, the vehicle travel application may be configured to serve as the on-board end of a data tunnel that is established with the data center705or with the hybrid communications distributor704at the data center. In an embodiment, the vehicle travel application may communicate with other applications installed on a particular device1304(e.g., native terrestrial applications) so that the other applications may operate as desired (e.g., in a native manner) while the device1304is being transported by the vehicle1302.

FIG. 14illustrates a block diagram of an example computing device1450that may be utilized in the hybrid communications system700. For example, one or more computing devices1450may be particularly configured to be utilized as at least a portion of the data center705, the vehicle data delivery network706, the on-board node720, or the device718. Additionally, other devices as described herein such as the cockpit electronics node1312may include an embodiment of the computing device1450.

The computing device1450may include, for example, one more central processing units (CPUs) or processors1452, and one or more busses or hubs1453that connect the processor(s)1452to other elements of the computing device1450, such as a volatile memory1454, a non-volatile memory1455, a display controller1456, and an I/O controller1457. The volatile memory1454and the non-volatile memory1455may each include one or more non-transitory, tangible computer readable storage media such as random access memory (RAM), read only memory (ROM), FLASH memory, a biological memory, a hard disk drive, a digital versatile disk (DVD) disk drive, etc.

In an embodiment, the memory1454and/or the memory1455may store instructions1458that are executable by the processor1452. For example, in a computing device particularly configured to be included in the data center705, the instructions1458may be the instructions comprising the hybrid communications distributor704. In another example, in a computing device1450particularly configured to be the on-board node720, the instructions1458may be the instructions comprising the hybrid communications collector722. In yet another example, in a computing device1450particularly configured to be a device718, the instructions1458may be the Vehicle Travel Application (VTA). Indeed, each of the modules, applications and engines described herein can correspond to a different set of machine readable instructions for performing one or more functions described above. These modules need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules can be combined or otherwise re-arranged in various embodiments. In some embodiments, at least one of the memories1454,1455stores a subset of the modules and data structures identified herein. In other embodiments, at least one of the memories1454,1455stores additional modules and data structures not described herein.

In an embodiment, the display controller1456may communicate with the processor (s)1452to cause information to be presented on a connected display device1459. In an embodiment, the I/O controller1457may communicate with the processor(s)1452to transfer information and commands to/from the user interface1460, which may include a mouse, a keyboard or key pad, a touch pad, click wheel, lights, a speaker, a microphone, etc. In an embodiment, at least portions of the display device1459and of the user interface1460are combined in a single, integral device, e.g., a touch screen. Additionally, data or information may be transferred to and from the computing device1450via a network interface1470. In some embodiments, the computing device1450may include more than one network interface1470, such as a wireless interface and a wired interface.

The illustrated computing device1450is only one example of a computing device suitable to be particularly configured for use in the hybrid communications system700. Other embodiments of the computing device1450may be also be for use in the hybrid communications system700, even if the other embodiments have more or fewer components than shown inFIG. 10, have one or more combined components, or have a different configuration or arrangement of the components. Moreover, the various components shown inFIG. 14can be implemented in hardware, a processor executing software instructions, or a combination of both hardware and a processor executing software instructions, including one or more signal processing and/or application specific integrated circuits.

FIG. 15illustrates an example method1500for facilitating communications between a first electronic device connected to a terrestrial network and a second electronic device connected to an on-board communications network, via various communication networks. According to embodiments, the communications may be text- or message-based communications (e.g., an SMS message) or voice-based communications. The method1500may operate in conjunction with any or all portions of the systems, vehicles and/or electronic devices previously discussed with respect toFIGS. 1-14, or the method1500may operate in conjunction with other suitable systems, vehicles, and/or electronic devices. In an embodiment, at least a portion of the method1500may be performed by a data center including an SBC/SIP server and/or a registration server, such as the data center129as described with respect toFIG. 1or the data center705as discussed with respect toFIG. 7.

At a block1505, the data center can receive, from the first electronic device, a first voice- or message-based content that identifies the second electronic device. In particular, the first voice- or message-based content may be an SMS message received from an SMSC or an internet-based voice communication. In embodiments, the data center can further identify, from the first voice- or message-based content, a subscription identification associated with the second electronic device, whereby the subscription identification may be an MSISDN of the second electronic device.

At a block1510, the data center may generate a forward communication that (i) includes the first voice- or message-based content and (ii) indicates the second electronic device. In generating the forward communication, the data center may include the MSISDN of the second electronic device. At a block1515, the data center may transmit the forward communication to the second electronic device via a satellite communication link. In embodiments, the satellite communication link may be one of a Kuband communication link or a Kacommunication link, or another satellite communication link, as discussed with respect toFIG. 7.

At a block1520, the data center may determine whether a hybrid communication network is needed for the return communication. In some embodiments, a hybrid communication network may be utilized when an ATG network is available, such as if the vehicle is traveling over land (e.g., a flight within the United States). In other embodiments, a satellite-only network may be utilized when an ATG network is not available, such as if the vehicle is traveling over water (e.g., an international fight across the Atlantic Ocean). The need for a hybrid communication network may be determined before the vehicle begins its journey to allow the for proper network configuration.

If the data center determines that a hybrid communication network is needed for the return communication (“YES”), the data center may receive (block1525) a return communication from the second electronic device via a terrestrial communication link. In contrast, if the data center determines that a hybrid communication network is not needed for the return communication (“NO”), the data center may receive (block1530) a return communication from the second electronic device via the satellite communication link. In some embodiments, if the return communication is a message-based communication, the return communication may be in the form of a message of a specified protocol. In other embodiments, if the return communication is a voice-based communication, the return communication may be in the form of an internet-based voice communication request.

At a block1535, the data center may transmit a second voice- or message-based content that is included in the return communication to the first electronic device via the service provider network. In cases in which the return communication is a message-based communication, the data center may convert the message into a SMS message before transmitting to the first electronic device. In cases in which the return communication is a voice-based communication, the data center may transmit the internet-based voice communication request to an ITSP for delivery to the first electronic device.

Of course, the applications and benefits of the systems, methods and techniques described herein are not limited to only the above examples. Many other applications and benefits are possible by using the systems, methods and techniques described herein.

Furthermore, when implemented, any of the methods and techniques described herein or portions thereof may be performed by executing software stored in one or more non-transitory, tangible, computer readable storage media or memories such as magnetic disks, laser disks, optical discs, semiconductor memories, biological memories, other memory devices, or other storage media, in a RAM or ROM of a computer or processor, etc.

Thus, many modifications and variations may be made in the techniques, methods, and structures described and illustrated herein without departing from the spirit and scope of the present claims. Accordingly, it should be understood that the methods and apparatus described herein are illustrative only and are not limiting upon the scope of the claims.