HK1234901B - Systems and methods for facilitating communications originating from a non-terrestrial network - Google Patents

Description

Systems and methods for facilitating communications originating from non-terrestrial networks

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. application Ser. No. 14/291,878, filed May 30, 2014, entitled “System and Method for Facilitating Communications Originating from Non-Terrestrial Networks,” the disclosure of which is hereby incorporated by reference in its entirety for all purposes.

Technical Field

The present disclosure relates generally to non-terrestrial communications and, in particular, to systems, methods, and techniques for facilitating cellular-based communications from electronic devices while connected to a non-terrestrial communication network.

Background Art

Currently, existing airlines and other transportation companies provide various services to mobile or wireless devices (e.g., mobile phones, smart devices, laptops, tablets, etc.) while they are on a vehicle en route to their destination. However, there are difficulties in transferring terrestrial features or local features to mobile or wireless devices (e.g., roaming, texting, simultaneous calls, etc.) while the vehicle is en route. Typically, in order to support local, terrestrial features of mobile or wireless devices in non-terrestrial environments, cellular base stations such as "picocells" are installed onboard the vehicle, and the mobile device connects to the onboard network via the mobile device's cellular radio and the onboard cellular base station. In some cases, in addition to the cellular base station, hardware is also installed onboard the vehicle. This external infrastructure is both restrictive and extremely expensive. In addition, the radio transmissions generated onboard the vehicle can interfere with ground-based cellular systems. For example, if a mobile device onboard a vehicle is unable to find sufficient cellular band to which the mobile device can connect (e.g., when the onboard cellular base station is out of service), the mobile device will automatically increase its power, which can interfere with ground-based terrestrial cellular base stations and quickly drain the mobile device's battery.

Some existing terrestrial communication systems are capable of providing Internet-based network connectivity to mobile devices onboard a vehicle. For example, some communication systems are equipped with Wi-Fi capabilities that enable mobile devices to access websites and stream multimedia. However, these communication systems are unable to provide terrestrial or local communication features (e.g., cellular-based communications) to mobile devices while they are onboard a vehicle.

Thus, an opportunity exists to leverage existing communications infrastructure to facilitate cellular-based communications via electronic devices when these electronic devices are connected to non-terrestrial communications networks.

Summary of the Invention

In an embodiment, a method for processing a communication request is provided. The method includes receiving a communication request, the communication request (1) being initiated by an electronic device connected to a non-terrestrial network and (2) being intended for use by a destination electronic device, the communication request including an identification of the electronic device. The method further includes identifying, by a processor, a subscription identifier associated with the electronic device using the identification of the electronic device, modifying, by the processor, the communication request to indicate the subscription identifier, and transmitting the modified communication request to a service provider network for delivery to the destination electronic device.

In another embodiment, a system for processing communication requests is provided. The system includes: a communication module and a data center, the communication module being configured to send and receive data, and the data center being communicatively connected to the communication module. The data center is configured to receive a communication request via the communication module, the communication request (1) being initiated by an electronic device connected to a non-terrestrial network and (2) being intended for use by a destination electronic device, the communication request including: an identification of the electronic device. The data center is further configured to use the identification of the electronic device to identify a subscription identification associated with the electronic device, modify the communication request to indicate the subscription identification, and transmit the modified communication request to a service provider network via the communication module for delivery to the destination electronic device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary representation of electronic devices and components that can facilitate text-based communications between electronic devices in accordance with some embodiments.

2 depicts an example signal diagram associated with facilitating text-based communications originating from an electronic device connected to a non-terrestrial network, in accordance with some embodiments.

3 depicts an example signal diagram associated with facilitating text-based communications intended for use by electronic devices connected to non-terrestrial networks, in accordance with some embodiments.

4 illustrates an exemplary representation of electronic devices and components that can facilitate voice-based communications between electronic devices in accordance with some embodiments.

5 depicts an example signal diagram associated with facilitating voice-based communications originating from an electronic device connected to a non-terrestrial network, in accordance with some embodiments.

6 depicts an example signal diagram associated with facilitating voice-based communications intended for use by electronic devices connected to non-terrestrial networks, in accordance with some embodiments.

7 depicts a schematic diagram of a process flow for a data center that facilitates communications originating from electronic devices connected to a non-terrestrial network, according to some embodiments.

8 illustrates a flow diagram of a data center process for facilitating communications for use by electronic devices connected to non-terrestrial networks, according to some embodiments.

Figure 9 is a block diagram of a registration server according to some embodiments.

FIG10 is a block diagram of an electronic device in accordance with some embodiments.

DETAILED DESCRIPTION

Although the following text sets forth a detailed description of several different embodiments, it should be understood that the legal scope of the description is defined by the language of the claims and equivalents set forth at the end of this patent. The detailed description should be construed as merely exemplary and does not describe every possible embodiment, as describing every possible embodiment would be impractical. Numerous alternative embodiments can be implemented using current technology or technology developed after the filing date of this patent and will still fall within the scope of the claims.

It should also be understood that unless a term is expressly limited in this patent using the sentence "As used herein, the term '____' is hereby defined as ..." or similar sentences, it is not intended to limit the meaning of that term beyond its plain or ordinary meaning, either expressly or by implication, and such term should not be construed as limited in scope based on any statement made in any part of this patent (except in the language of the claims). With respect to any term recited in the claims at the end of this patent, it is referred to in this patent in a manner consistent with a single meaning, which is done solely for the sake of clarity so as not to confuse the reader, and it is not intended that such claim term be limited, by implication or otherwise, to that single meaning. Finally, unless a claim element is limited by reciting the word "means" and the function without any structural recitation, it is not intended that the scope of any claim element be construed based on the application of the sixth paragraph of 35 U.S.C. §112.

The systems and methods discussed herein provide efficient and effective technologies that facilitate text-based and voice-based communications between electronic devices. In particular, one of the electronic devices participating in the communication is connected to a non-terrestrial network (e.g., an aerial network) and the other electronic device participating in the communication is connected to a terrestrial network (e.g., a ground-based network). The systems and methods enable non-terrestrial electronic devices to roam in a cellular-based network, send and receive text messages (e.g., SMS messages), and generate and terminate voice calls when the electronic devices are connected to a wireless network on a vehicle such as an airplane. The systems and methods facilitate generating cellular-based communications as if the electronic devices were roaming in a cellular environment. Thus, the phone number (or other subscription identifier) associated with the non-terrestrial device is provided to the terrestrial device so as to provide complete transparency to the user of the terrestrial device. For example, when a voice call initiated by an aerial smartphone is received, the recipient's smartphone will display the phone number of the aerial smartphone.

As a result, the systems and methods enable “feature transparency,” which generally refers to providing features to a wireless device when the wireless device is in a non-terrestrial environment (e.g., when the wireless device is being served by connecting to a wireless access point that is fixedly connected to a structure of a vehicle), such as when the wireless or mobile device is being transported by an aircraft in flight or a ship underway, that originate from or are provided by the wireless device in a terrestrial environment (e.g., when the wireless device is being served by connecting to a cellular base station or wireless access point that is physically or fixedly connected to a terrestrial structure).

The system and method can be facilitated by a backend registration server and a communication application installed on the electronic device. During registration of the electronic device with the registration server, the registration server sends location updates of the electronic device to the home network of the electronic device user, and the home network updates its home location register (HLR) accordingly. As a result, the location of the electronic device is known within the terrestrial mobile network, and the electronic device is configured to roam and send and receive text messages and voice calls using local subscription information.

In some aspects, a user interacts with a registered electronic device to initiate a text-based or voice-based communication to a destination device. The electronic device initiates the communication by sending an Internet-based message to a registration server, which locates an account for the electronic device and performs other functions based on the received message. If the initial communication is a text-based communication, the registration server delivers the message to the destination device via the electronic device's home network. If the initial communication is a voice-based communication, the registration server communicates with a Session Initiation Protocol (SIP) trunk provider to establish a flow between the electronic device and the destination device, via which the voice communication can be facilitated.

In some embodiments, a device connected to a ground-based network may initiate a text-based communication or a voice-based communication intended for use by an electronic device located in a non-terrestrial environment. In this case, a registration server may receive the associated communication and modify the communication with identification information associated with the electronic device. If the initial communication is a text-based communication, the registration server sends the communication to the onboard communication system for delivery to the electronic device. If the initial communication is a voice-based communication, the registration server facilitates a SIP-based invitation to the electronic device, which initiates a flow between the electronic device and the destination device, via which the voice communication may be facilitated.

The systems and methods provide numerous advantages and benefits. Specifically, the systems and methods enable electronic devices to send and receive cellular-based communications when not connected to a cellular network, thereby increasing user usability and general communication capabilities. Furthermore, the systems and methods enable service providers to provide electronic devices with access to cellular-based connectivity, thereby serving as a source of revenue generation. Additionally, registration of electronic devices with a registration server provides increased security for subscribers and limits instances of "spoofing." It will be appreciated that other advantages and benefits of the systems and methods are also contemplated.

FIG1 illustrates an example representation 100 of components configured to facilitate cellular-based communications between electronic devices. Specifically, the components of representation 100 are configured to facilitate text-based communications (e.g., Short Message Service (SMS) messages) between an electronic device 105 connected to a non-terrestrial-based network and one or more additional devices 110 connected to a terrestrial-based network. Generally, as referred to herein, a "terrestrial-based" or "ground-based" network refers to any network to which electronic devices in a terrestrial environment can connect, but to which the electronic devices cannot readily communicate while being transported by high-speed or high-altitude vehicles, such as aircraft. Similarly, a "non-terrestrial-based" or "non-terrestrial-based" network refers to any network to which electronic devices that are not within the range of, or cannot readily connect to, a terrestrial-based network can connect, such as when being transported by high-speed or high-altitude vehicles, such as aircraft. Typically, an external network includes terrestrial systems and terrestrial computing devices that are substantially fixed in location. Furthermore, the external network includes a base station or infrastructure containing equipment that allows wireless access to the external network via these devices. The base station or infrastructure may be contained in one or more buildings or other structures that are fixedly attached to the ground or land.

Each of the electronic device 105 and the additional device 110 can be any type of standalone or portable electronic device capable of communicating via one or more networks. For example, each of the electronic device 105 and the additional device 110 can be a mobile phone, a personal digital assistant (PDA), a smartphone, a tablet computer, a multimedia player, a desktop or laptop computer, an MP3 player, a digital broadcast receiver, or any other electronic device. Each of the electronic device 105 and the additional device 110 can also have a subscription or plan with a cellular service provider, whereby the cellular service provider supports cellular communications via the electronic device 105 and/or the additional device 110.

As shown in Figure 1, electronic device 10 is transported by vehicle 117 or is positioned in vehicle 117 in addition.In an embodiment, vehicle 117 can be owned and/or operated by an individual, or vehicle 117 can be owned and/or operated by a company, organization or government entity.Vehicle 117 can be an airplane in a group of airplanes.Vehicle 117 can be used for passengers who pay for transportation or passengers who are authorized to pass through on the vehicle.Vehicle 117 can be used for administrative officers or employees of a transportation company or organization and their guests.Vehicle 117 can be used for transporting fresh or inanimate goods, parcels, mail and/or other types of passengers or goods.In addition, although Figure 1 describes vehicle 117 as an airplane, the technology and principles described herein are equally applied to other types of vehicles, such as trucks, cars, buses, trains, boats, ships, barges, subway cars, helicopters, ambulances or other emergency vehicles, military vehicles, other airborne, water or land vehicles, and vehicles that are suitable for space travel.

Vehicle 117 is equipped with a wireless access point 119 and an onboard communication network system 121. At any given moment, onboard communication network system 121 can be communicatively connected to one or more data or communication networks that are largely, if not entirely, located, managed, and/or hosted outside of vehicle 117. For example, the external network can be a public, ground-based data or communication network, such as the Internet and/or the PSTN (Public Switched Telephone Network). The external network can also be a ground-based, private data and/or communication network. Further, the external network can be a cellular network 107 including a cellular base station 123. Typically, the external network includes ground systems and ground computing devices that are essentially fixed in place. Further, the external network includes base stations or infrastructure containing equipment that can be wirelessly accessed via these devices. The base stations or infrastructure can be contained in one or more buildings or other structures fixedly attached to the ground or land.

The electronic device 105 can connect to the onboard communication network system 121 via the wireless access point 119. Typically, the onboard communication network system 121 can be deployed, managed, and/or hosted entirely onboard the vehicle 117. For example, the onboard communication network system 121 can be a Wi-Fi network that is contained within and operates within the passenger cabin of the vehicle 117. The onboard communication network system 121 can utilize any known communication protocol or combination thereof, such as a wireless protocol, a wired protocol, other ARINC standard-compliant protocols, or a proprietary protocol. In an example, the onboard communication network system 121 utilizes an IEEE 802.11-compliant protocol to communicate with the electronic device 105. In another example, the onboard communication network system 121 utilizes a Hypertext Transfer Protocol (HTTP) and a Near Field Communication (NFC)-compliant protocol (e.g., NFC) to communicate with the electronic device 105.

The onboard communication network system 121 may also facilitate and manage communications between the electronic device 105 and the cellular base station 123 of the cellular network 107. According to an embodiment, the onboard communication network system 121 and the cellular base station 123 may collectively constitute an air-to-ground (ATG) communication network for use by the aircraft. In an embodiment, the onboard communication network system 121 and the cellular base station 123 may 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, etc.).

The cellular base stations 123 of the cellular network 107 can be connected to a ground-based data center 129 via one or more different wired or wireless networks. The ground-based data center 129 has components for securely facilitating communications between the electronic device 105 and other electronic devices, such as the additional device 110. Specifically, the cellular base stations 123 include a session border controller (SBC) and a session initiation protocol (SIP) server 127 (which can be separate servers or combined into the same server), as well as a registration server 114. The registration server 114 can be any combination of hardware and software elements configured to communicate directly or indirectly with the electronic device 105 and the additional device 110 and facilitate the functions and communications described herein. Further, the SBC/SIP 127 can facilitate and manage communication sessions between the electronic device 105, the additional device 110, and the data center 129 using the SIP signaling protocol.

Although the embodiments herein are described as operating using the SIP signaling protocol, it should be appreciated that other standard or proprietary application protocols are contemplated. For example, other contemplated 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 the like.

According to an embodiment, the electronic device 105 can download and install a communication application (not shown in FIG1 ) that enables cellular-based communications when the electronic device 105 is located in the vehicle 117. Further, the electronic device 105 can register with the registration server 114 using the communication application and create an account to enable the electronic device 105 to communicate via various airborne communication networks, such as an air-to-ground (ATG) communication network used by aircraft.

As illustrated in FIG1 , registration server 114 can be connected to a home network 111 associated with electronic device 105 via a cellular-based network. A cellular-based network can 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, etc.). Typically, home network 111 of electronic device 105 can be operated or provided by a cellular communication service provider with which the user (i.e., subscriber) of electronic device 105 has an agreement to transmit and receive wireless communication services and features. Accordingly, home network 111 of electronic device 105 can operate or manage a home location register (HLR) 115 and/or a visitor location register (VLR) (not shown in FIG1 ), among other databases or components, to support and manage cellular communications, roaming, and other features for electronic device 105 according to the service agreement. Additionally, the cellular radio frequency (RF) communication bands used by home network 111 for wireless communication with mobile devices may be RF bands designated for AMP, TDMA, CDMA, GSM, PCS, 3G, 4G, 5G, and/or any other terrestrial cellular radio bands. Typically, a cellular radio band is a portion of the RF spectrum that is allocated by a government agency or other entity that controls spectrum usage. In some networks, more than one cellular RF band may be supported.

HLR 115 may include a database that stores the identities of electronic devices authorized to communicate via home network 111. Specifically, for each authorized device, HLR 115 may store a corresponding International Mobile Subscriber Identity (IMSI), which is a unique code that identifies each authorized device (or, more specifically, the SIM card that identifies each authorized device). HLR 115 may also pair each IMSI with a Mobile Subscriber Integrated Services Digital Network number (MSISDN) that corresponds to the authorized device's telephone number. Home network 111 further includes a Short Message Service Center (SMSC) 102 configured to store, forward, convert, and deliver cellular-based messages (e.g., text messages, such as SMS messages). Specifically, SMSC 102 may forward messages originating from attached device 110 and intended for electronic device 105 to data center 129. Further, SMSC 102 may transmit messages received from electronic device 105 via data center 129 to attached device 110.

According to an embodiment, components of representation 100 are configured to facilitate the communication of cellular-based messages between and among the electronic device 105 and one or more additional devices 110. In one embodiment, the data center 129 can receive messages from the electronic device 105 traveling in the vehicle 117 via the onboard communication network system 121 and the cellular network 107, whereby the messages are intended for use by the additional devices 110. Because the messages originate as Internet-based communications, the messages are not configured for delivery to the additional devices 110, as are conventional cellular-based messages. Therefore, the data center 129 can perform various techniques associated with the messages, such that the messages are configured for delivery to the additional devices 110, via the home network 111, as are conventional cellular-based messages.

In another embodiment, the data center 129 may receive a message from the attached device 110 via the home network 111, whereby the message is intended for use by the electronic device 105 traveling in the vehicle 117. Because the message is initiated as a cellular-based communication, the message is not configured for delivery to the electronic device 105, as the electronic device 105 is not directly connected to the cellular-based network. Therefore, the data center 129 may perform various techniques associated with the message such that the message is configured for delivery to the electronic device 105 via the cellular network 107 and the onboard communication network system 121, such as an Internet-based message.

FIG2 illustrates a signal flow framework 200 associated with facilitating a text-based communication or message originating from a source device 205 connected to a non-terrestrial network, such as if the source device 205 is located on a vehicle such as an airplane. According to the embodiments described herein, the text-based communication may be an SMS message, however, it should be appreciated that other text-based or multimedia-based communications are contemplated. The signal flow framework 200 includes a source device 205 (such as the electronic device 105 discussed with respect to FIG1 ), a data center 229 including an SBC/SIP server 227 (such as the SBC/SIP server 127 discussed with respect to FIG1 ), a registrar 214 (such as the registrar 114 discussed with respect to FIG1 ), an SMSC 212 (such as the SMSC 112 discussed with respect to FIG1 ), and a destination device 210 (such as the destination device 110 discussed with respect to FIG1 ).

According to an embodiment, a user of source device 205 may select a service or product from a list of available services or products, which may include various cellular connectivity options for source device 205 based on duration, data limits, or other parameters. For example, the list of services or products may include sending and receiving unlimited text-based communications during a particular flight.

To initiate a text-based message communication, a user may use source device 205 to enter (230) a message body and an identification of a recipient. Specifically, the identification of the recipient may be an MSIDSN (i.e., a telephone number) associated with destination device 210. In some embodiments, the user may initiate a message using a communication application that has registered with the vehicle's onboard communication network system and/or registration server 214. Further, the communication application may convert the text-based message into a SIP-based message, whereby the SIP message includes a Uniform Resource Identifier (URI) indicating the IMSI and/or MSISDN associated with source device 205.

Although not shown in FIG2 , source device 205 can use a digital certificate to initiate a Transport Layer Security (TLS) connection with SBC/SIP server 427. Specifically, the certificate can be the certificate issued to source device 205 by registration server 214 during device registration. Registration server 214 (acting as a certification authority (CA)) can verify the certificate and send a success response to SBC/SIP server 227. In response to receiving the success response, SBC/SIP server 227 can establish a TLS connection with source device 205.

Source device 205 may send (231) a SIP message to SBC/SIP server 227 via the established TLS connection. SBC/SIP server 227 may decrypt (232) the SIP message and look up (233) an IP address associated with source device 205. Specifically, the IP address may be a care-of address (CoA) that SBC/SIP server 227 previously associated with source device 205. SBC/SIP server 227 may modify (234) the IP address of source device 205 by replacing the IP address included in the SIP message with the CoA associated with source device 205.

After modifying the IP address, SBC/SIP server 227 may send (235) a SIP message with the modified IP address to registrar server 214. Registrar server 214 may inspect the SIP message and confirm (236) that source device 205 has a valid product or service. Registrar server 214 may also convert (237) the SIP message into an SMS message according to a suitable communication protocol (e.g., GSM, CDMA, etc.). Further, registrar server 214 may modify (238) the "from" field of the SMS message to the MSISDN of source device 205. In particular, registrar server 214 may use the identity of source device 205 specified in the SIP message (e.g., the IMSI of source device 205) to look up the MSISDN of source device 205.

After generating the SMS message, registration server 214 may send (239) the SMS message to SMSC 202, and SMSC 202 may deliver (240) the SMS message to destination device 210. When destination device 210 receives the SMS message, the MSISDN included (238) in the SMS message will cause the SMS message to appear as a regular cellular-based SMS, rather than as a SIP message as generated in (231). In particular, the appearance of the delivered SMS is no different than the appearance of an SMS message sent from one mobile device to another via a cellular network.

Upon receiving the SMS message from SMSC 202, destination device 210 may present (245) the SMS message in a user interface. In some embodiments, destination device 210 may present the body or text portion of the SMS message via an application installed on destination device 210. Further, destination device 210 may send (241) a message receipt confirmation to SMSC 202, which may be forwarded to registration server 214 (242), SBC/SIP server 227 (243), and to source device 205 (244), respectively.

FIG3 illustrates a signal flow framework 300 associated with facilitating the delivery of a text-based communication or message originating from a source device 310 connected to a ground-based network. Furthermore, the text-based communication is intended for use by a destination device 305 connected to a non-ground-based network, such as if the destination device 305 is located on a vehicle such as an airplane. According to the embodiments described herein, the text-based communication may be an SMS message, however, it should be appreciated that other text-based or multimedia communications are contemplated. Signal flow framework 300 includes a destination device 305 (such as the electronic device 105 discussed with respect to FIG. 1 ), a data center 329 including an SBC/SIP server 327 (such as the SBC/SIP server 127 discussed with respect to FIG. 1 ), a registration server 314 (such as the registration server 114 discussed with respect to FIG. 1 ), a home network 311 including an HLR 315 and an SMSC 312 (such as the HLR 115 and SMSC 112 discussed with respect to FIG. 1 ), and a source device 310 (such as the additional device 110 discussed with respect to FIG. 1 ). For purposes of this discussion, it should be appreciated that destination device 305 has already completed a registration process with registration server 314 and has also purchased a product or service that enables text-based communications via a non-terrestrial network.

To initiate a text message-based communication, a user may use source device 310 to compose an SMS message (e.g., using a conventional text messaging application), specify a recipient (e.g., by including the MSISDN of destination device 305), and select to send the SMS message. In operation, source device 310 sends (330) the SMS message to SMSC 302. Upon receiving the SMS message, SMSC 302 requests (331) routing information associated with the MSISDN specified in the SMS message from HLR 315 associated with destination device 305. Because destination device 305 has previously registered with registration server 314, registration server 314 previously updated the location of destination device 305 with HLR 315, and thus HLR 315 is "aware" of the association between destination device 305 and registration server 314. Accordingly, HLR 315 may send (332) routing information associated with destination device 305, which may be a routing number for registration server 314.

Using the routing number, SMSC 302 can send 333 an SMS message with the MSISDN of destination device 305 to registration server 314. Registration server 314 can check the MSISDN to confirm 334 that there is a valid product or service associated with destination device 305. In particular, the user of destination device 305 may have previously selected a service or product from a list of available services or products (e.g., during a flight trip), which may include various cellular connectivity options for destination device 305 based on duration, data limit, or other parameters. Registration server 314 can also retrieve 335 a SIP URI associated with the MSISDN of destination device 305. In particular, the SIP URI may have been previously associated with the MSISDN during registration of destination device 305 with registration server 314.

The registration server 314 may convert (336) the SMS message into a SIP message having a SIP URI according to various technologies or communication protocols (e.g., CDMA, GSM, etc.). The registration server 314 may also send (337) the SIP message having the IP URL to the SBC/SIP server 327. According to an embodiment, the SBC/SIP server 327 may establish (338) a TLS connection with the destination device 305 using a digital certificate or according to other techniques. Further, the SBC/SIP server 327 may send (342) the SIP message to the destination device 305 via the established TLS connection. The destination device 305 may present (343) the SIP message to a user of the destination device 305. In some embodiments, the destination device 305 may present the body or text portion of the SIP message via an application installed on the destination device 305. After receiving the SIP message, destination device 305 may send (339) a message receipt confirmation to SBC/SIP server 327, which may be forwarded to registration server 314 (340) and source device (310), respectively.

4 illustrates an example representation 400 of components configured to facilitate cellular-based communications between electronic devices. In particular, the components of representation 400 are configured to facilitate voice-based communications (e.g., VoIP phones) between an electronic device 405 connected to a non-terrestrial-based network and one or more additional devices 410 connected to a terrestrial-based network.

Similar to the electronic device 105 and the additional device 110 of FIG1 , each of the electronic device 405 and the additional device 410 can be any type of standalone or portable electronic device capable of communicating via one or more networks. For example, each of the electronic device 405 and the additional device 410 can be a mobile phone, a personal digital assistant (PDA), a smartphone, a tablet computer, a multimedia player, a desktop or laptop computer, an MP3 player, a digital broadcast radio, or any other electronic device. Each of the electronic device 405 and the additional device 410 can also have a subscription or plan with a cellular service provider, whereby the cellular service provider supports cellular communications via the electronic device 405 and/or the additional device 410.

As illustrated in FIG4 , electronic device 405 is transported by or otherwise located within vehicle 417, similar to vehicle 117 as discussed with respect to FIG1 . Vehicle 417 is equipped with a wireless access point 419 and an onboard communication network system 421. At any given moment, onboard communication network system 421 may be communicatively connected to one or more data or communication networks that are largely, if not entirely, located, managed, and/or hosted external to vehicle 417. For example, the external network may be a public, ground-based data or communication 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 communication network. Further, the external network may be a cellular network 407 including a cellular base station 423. Typically, the ground system and ground computing devices may be substantially fixed in location, and the base stations or infrastructure containing the devices through which these devices can wirelessly access the ground system may be contained in one or more buildings or other structures fixedly attached to the ground or land.

The electronic device 405 can be connected to the onboard communication network system 421 via the wireless access point 419. Typically, the onboard communication network system 421 can be deployed, managed, and/or hosted entirely onboard the vehicle 417. For example, the onboard communication network system 421 can be a Wi-Fi network contained within and operating within the cabin of the vehicle 417. The onboard communication network system 421 can utilize any known communication protocol or combination thereof, such as a wireless protocol, a wired protocol, other ARINC standard-compliant protocols, or a proprietary protocol. In one example, the onboard communication network system 421 utilizes an IEEE 802.11-compliant protocol to communicate with the electronic device 405. In another example, the onboard communication network system 421 utilizes a Hypertext Transfer Protocol (HTTP) and a Near Field Communication (NFC)-compliant protocol (e.g., NFC) to communicate with the electronic device 405.

The onboard communication network system 421 may also facilitate and manage communications between the electronic device 405 and a cellular base station 423 of the cellular network 407. According to an embodiment, the onboard communication network system 421 and the cellular base station 423 may collectively constitute an air-to-ground (ATG) communication network for use by the aircraft. In an embodiment, the onboard communication network system 421 and the cellular base station 423 may 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, etc.).

The cellular base station 423 of the cellular network 407 can be connected to a ground-based data center 429 via one or more different wired or wireless networks. The ground-based data center 429 has components for securely facilitating communications between the electronic device 405 and other electronic devices (such as the additional device 410). In particular, the cellular base station 423 includes an SBC/SIP server 427 (which can be separate servers or combined into the same server) and a registration server 414. The registration server 414 can be any combination of hardware and software elements configured to communicate directly or indirectly with the electronic device 405 and the additional device 410 and facilitate the functions and communications described herein. Further, the SBC/SIP 427 can facilitate and manage communication sessions between the electronic device 405, the additional device 410, and the data center 129 using the SIP signaling communication protocol.

According to an embodiment, electronic device 405 may download and install a communication application (not shown in FIG1 ) that enables cellular-based communications when electronic device 405 is located in vehicle 417. Further, electronic device 405 may use the communication application to register and create an account with registration server 114. This registration configures electronic device 405 to be able to communicate via various airborne communication networks, such as an air-to-ground (ATG) communication network used by aircraft.

As shown in FIG4 , registration server 414 can be connected to home network 411 associated with electronic device 405 via a cellular-based network. A cellular-based network can 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, etc.). Typically, home network 411 of electronic device 405 can be operated or provided by a cellular communication service provider with which the user (i.e., subscriber) of electronic device 405 has an agreement to receive wireless communication services and features. Accordingly, home network 411 of electronic device 405 can operate or manage HLR 415 and/or VLR (not shown in FIG4 ), among other databases or components, to support and manage cellular communications, roaming, and other features according to the service agreement. Additionally, the cellular radio frequency (RF) communication band used by home network 411 for wireless communication with mobile devices may be an RF band designated for AMP, TDMA, CDMA, GSM, PCS, 3G, 4G, 5G, and/or any other terrestrial cellular radio band. Typically, a cellular radio band is a portion of the RF spectrum that is allocated by a government agency or other entity that controls spectrum usage. In some networks, more than one cellular RF band may be supported.

HLR 415 may include a database that stores the identities of electronic devices that are authorized to communicate via home network 411. In particular, for each authorized device, HLR 415 may store a corresponding IMSI, which is a unique code that identifies each authorized device (or more specifically, the SIM card that identifies each authorized device). HLR 415 may also pair each IMSI with an MSISDN that corresponds to the telephone number of the authorized device.

Data center 429 may further be configured to communicate with SIP trunk provider 412. According to some embodiments, SIP trunk provider 412 enables VoIP and streaming communications through which Internet telephony service providers (ITSPs) deliver telephony services and unified communications to customers equipped with SIP-based communications. Each of home network 411 and SIP trunk provider 412 (as well as the data center) may communicate with mobile switching center (MSC) 413. According to some embodiments, MSC 413 routes voice calls and other messaging services to and from end devices, such as electronic device 405 and attached device 410. In particular, MSC 413 creates and releases end-to-end connections and manages mobility and handoff requirements during calls, among other services known in the art.

According to some embodiments, the components of representation 400 are configured to facilitate voice-based communications between electronic device 405 and one or more additional devices 410. In one embodiment, data center 429 may receive a SIP message initiated by electronic device 405 while traveling in a vehicle, whereby the SIP message is intended to establish voice communications with additional device 410. Because the SIP message is initiated as an Internet-based communication, the SIP message is not configured to establish a conventional telephone call with additional device 410. Accordingly, data center 429 may perform various techniques associated with the message and utilize SIP trunk provider 412 and MSC 413 so that an RTP stream may be established between electronic device 405 and additional device 410 to facilitate voice-based communications.

In another embodiment, the additional device 410 can initiate voice-based communication intended for use by the electronic device 405. The SIP trunk provider 412 initiates the voice-based communication setup by sending a message to the data center 429. The data center 429 can perform various techniques associated with the message and utilize the cellular network 407 to enable an RTP stream to be established between the electronic device 405 and the additional device 410 to facilitate the voice-based communication.

FIG5 illustrates a signal flow framework 500 associated with facilitating voice-based communications originating from a source device 505 connected to a non-terrestrial network, such as if the source device 505 is airborne on a vehicle such as an aircraft. The voice-based communications are intended for use by a destination device 510 connected to a terrestrial network. According to the embodiments discussed herein, the voice-based communications may be VoIP calls, however, it should be appreciated that other voice-based communications are contemplated. Signal flow framework 500 includes a source device 505 (such as electronic device 405 as discussed with respect to FIG4 ), a data center 529 including an SBC/SIP server 527 (such as SBC/SIP server 427 as discussed with respect to FIG4 ), a registration server 514 (such as registration server 414 as discussed with respect to FIG4 ), a SIP trunk provider 512 (such as SIP trunk provider 412 as discussed with respect to FIG4 ), a mobile switching center 513 (such as mobile switching center 413 as discussed with respect to FIG4 ), and a destination device 510 (such as additional device 410 as discussed with respect to FIG4 ). For the purposes of this discussion, it should be appreciated that source device 505 has already completed a registration process with registration server 514 and has also purchased a product or service that enables voice-based communications via a non-terrestrial network.

5 , the source device 505 may establish a TLS connection with the SBC/SIP server 527, for example, using a digital certificate obtained during registration with the registration server 514. The source device 505 may send (544) a SIP INVITE request associated with the VoIP call to the SBC/SIP server 527 via the TLS connection. The SIP INVITE request may include an identification of the source device 505, such as the IMSI of the source device 505. The SBC/SIP server 527 may respond (545) to the source device 505 with a SIP 100 TRYING message. In response to receiving the SIP 100 TRYING message, the source device 505 may allocate (546) an RTP port and listen for communications on the RTP port.

The SBC/SIP server 527 may decrypt (547) the SIP message and look up (548) the IP address associated with the source device 505. Specifically, the IP address may be a care-of address (CoA) that the SBC/SIP server 527 previously associated with the source device 505. The SBC/SIP server 527 may modify (549) the IP address of the source device 505 by replacing the IP address included in the SIP message with the CoA associated with the source device 505. After modifying the IP address, the SBC/SIP server 527 may send (550) a SIP invite message with the modified IP address to the registration server 514. The registration server 514 may inspect the SIP invite message and confirm (552) that the source device 505 has a valid product or service. Registration server 514 may also replace ( 553 ) the identity of source device 505 (eg, the IMSI of source device 505 ) specified in the SIP Invite message with a telephone number associated with source device 505 (eg, MSISDN).

Registrar 514 may send (554) a SIP Invite message with a telephone number associated with source device 505 to SIP trunk provider 512, and SIP trunk provider 512 may respond (555) to registrar 514 with a SIP Try message. In response to receiving the SIP Invite message from registrar 514, SIP trunk provider 512 may send (556) an Initial Address Message/ISDN User Part (IAM/ISUP) setup request to mobile switching center 513, and mobile switching center 513 connects (557) the VoIP call with destination device 510.

5 , a user of destination device 510 may prompt destination device 510 to answer (558) the call, which triggers a call answered confirmation to be sent (559) to mobile switching center 513. Mobile switching center 513 may forward (560) the call answered confirmation to SIP trunk provider 512. Upon receiving the call answered confirmation, SIP trunk provider 512 may send (561) a SIP 200 OK message to registrar server 514, which may forward (562) the SIP 200 OK message to SBC/SIP server 527, and SBC/SIP server 527 may forward (563) the SIP 200 OK message to source device 505 to notify source device 505 that destination device 510 has answered the call. An RTP stream may be established (564, 565) via which voice-based communication may be facilitated between source device 505 and destination device 510.

Although not shown in FIG5 , it should be appreciated that functionality for handling various other voice-based communication scenarios is contemplated. Specifically, if the destination device 510 does not answer the voice-based call, a SIP 480 NO response message may be returned to the sending device 505. Furthermore, the source device 505 may cancel the call before the destination device 510 answers it, in which case a SIP cancel message may be returned to the various devices and components.

FIG6 illustrates a signal flow framework 600 associated with facilitating voice-based communications originating from a source device 610 connected to a ground-based network. Further, the voice-based communications are intended for use with a destination device 605 connected to a non-ground-based network, such as if the destination device 605 is located onboard a vehicle such as an aircraft. According to the embodiments discussed herein, the voice-based communications may be VoIP calls, however, it should be appreciated that other voice-based communications are contemplated. Signal flow framework 600 includes a destination device 605 (such as electronic device 405 as discussed with respect to FIG. 4 ), a data center 629 including an SBC/SIP server 627 (such as SBC/SIP server 427 as discussed with respect to FIG. 4 ), a registration server 614 (such as registration server 414 as discussed with respect to FIG. 4 ), a SIP trunk provider 612 (such as SIP trunk provider 412 as discussed with respect to FIG. 4 ), an HLR 615 (such as HLR 415 as discussed with respect to FIG. 4 ), a mobile switching center 613 (such as mobile switching center 413 as discussed with respect to FIG. 4 ), and a source device 610 (such as additional device 410 as discussed with respect to FIG. 4 ). For purposes of this discussion, it should be understood that destination device 605 has already completed a registration process with registration server 414 and has also purchased a product or service that enables voice-based communications via a non-terrestrial network.

6. The user of source device 610 may use source device 610 to initiate a voice-based communication (e.g., a VoIP call), for example, via a phone application. Specifically, the user may enter a phone number associated with destination device 605 and select to initiate a VoIP call. Source device 610 may place (667) the VoIP call, which causes source device 610 to send a request to HLR 615 associated with destination device 605. HLR 615 examines the destination of the call (i.e., destination device 605) and may request (668) a routing number for destination device 605 from registration server 614. Registration server 614 may allocate a routing number for destination device 605 and provide (669) the routing number to HLR 615, which may forward (670) the routing number to MSC 613. Upon receiving the routing number, MSC 613 may send (671) an IAM/ISUP setup request indicating the routing number to SIP trunk provider 612.

The SIP trunk provider 612 may use the IAM/SIUP setup request to generate a SIP invite message including a routing number and send (672) the SIP invite message to the registration server 614. The registration server 614 may examine the SIP invite message and confirm (673) that the destination device 605 has a valid product or service. In particular, the user of the destination device 605 may have previously (e.g., during a flight) selected a service or product from a list of available services or products, which may include various cellular connectivity options for the destination device 605 based on duration, data limits, or other parameters. The registration server 614 may also replace (674) the routing number specified in the SIP invite message with an identifier associated with the destination device 605. In an embodiment, the identifier of the destination device 605 may be the IMSI of the destination device 605. The registration server 614 may send (676) the SIP invite message to the SBC/SIP server 627 and also send (675) a SIP 100 trying message to the SIP trunk provider 612.

According to some embodiments, after receiving the SIP Invite message, the SBC/SIP server 627 and the destination device 605 may establish a TLS connection according to various techniques, such as using a digital certificate previously issued to the destination device 605 during the registration process. Further, the SBC/SIP server 627 may send (678) the SIP Invite message to the destination device 605 via the established TLS connection. The user of the destination device 605 may prompt the destination device 605 to answer (679) the call, which prompts the destination device to send (680) a SIP 200 OK message to the SBC/SIP server 627. The SBC/SIP server 627 may forward (681) the SIP 200 OK message to the registrar server 614, which may forward (682) the SIP 200 OK message to the SIP trunk provider 612, which may forward (683) the SIP 200 OK message to the HLR 615, which may create (684) a call request with the source device 610. An RTP stream may be established (685, 686), via which voice-based communication may be facilitated between the sending device 610 and the destination device 605.

6 , it should be appreciated that functionality for handling various other voice-based communication scenarios is contemplated. Specifically, if the destination device 605 does not answer the voice-based call, a SIP 480 NO response message may be returned to the source device 610. Furthermore, if the destination device 605 is busy, a SIP 486 Busy Here message may be returned between various devices and components.

In some embodiments, voice data from a voice-based call as described with respect to Figures 5 and 6 can be converted into text-based data. Typically, a passenger on a vehicle such as an airplane may not want to overhear a conversation with another passenger on the vehicle who is participating in a voice call. Further, a passenger may also not want to hear the other party to a voice call on a participating passenger's electronic device on the vehicle (e.g., via a hands-free feature of the electronic device). Therefore, it may be desirable to convert the voice data into text data, at least for the participating passenger. Furthermore, it may be desirable to limit the participating passenger's ability to actively participate in a voice call while traveling in the vehicle.

In the case where voice-based communication is established between a first device connected to a non-terrestrial network and a second device connected to a terrestrial network, the first device may enable a user to input text (e.g., via an on-screen keyboard, a peripheral keyboard, or another channel) instead of receiving audio (i.e., voice). The first device may include logic for converting the input text into voice, such as through a text-to-speech application known in the prior art. Thus, the second device may receive the voice converted from the text via a data center and output the converted voice via an audio output component. Similarly, the second device may include logic for converting the audio data (i.e., voice) received from the user into text, such as through a speech recognition (SR) application known in the prior art. The second device may send the generated text to the data center, which forwards the generated text to the first device. Thus, instead of outputting the received audio data, the first device may present the text converted by the second device from the original audio data. In some cases, the second device does not need to convert the audio data and the first device may still output audio data instead of text, such as in the case where the audio is output via the earphone speaker of the first device or via headphones. In 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 the audio back to the second device (eg, through a muted headset).

Audio and text conversion technologies may be optionally facilitated by other components. In some cases, the vehicle's onboard communication network system may include a module or application that performs either or both text-to-speech conversion and speech-to-text conversion. In other cases, the data center (or more specifically, the registration server) may include a module or application that performs either or both text-to-speech conversion or speech-to-text conversion.

FIG7 illustrates an example method 700 for facilitating initiating communication by connecting to a non-terrestrial (i.e., airborne) communication network. Depending on the embodiment, the communication may be text-based communication (e.g., an SMS message) or voice-based communication (e.g., a VoIP call). Method 700 may operate in conjunction with any or all of the systems, vehicles, and/or electronic devices previously discussed with respect to FIG1-6 , or method 700 may operate in conjunction with other suitable systems, vehicles, and/or electronic devices. In an embodiment, at least a portion of method 700 may be performed by a data center including an SBC/SIP server and/or a registrar, such as data center 129 described with respect to FIG1 or data center 429 described with respect to FIG4 .

At block 705, the data center may receive a communication request initiated by an electronic device connected to a non-terrestrial network, wherein the communication request includes an identification of the electronic device and an IP address associated with the electronic device. In some embodiments, if the communication corresponds to text-based communication, the communication request may be a SIP message, and the data center may be configured to convert the SIP message into an SMS message. In particular, the SIP message may include body text data, and the data center may convert the SIP message by appending the body text data to the SMS message. In other embodiments, if the communication corresponds to voice-based communication, the communication request may be an internet-based voice communication request. Depending on the embodiment, the identification of the electronic device may be the IMSI of the electronic device.

At block 710, the data center may use the IP address received in the communication request to identify the care-of address (CoA) of the electronic device. Further, at block 715, the data center may modify the communication request to include the CoA of the electronic device. In an embodiment, the data center may maintain a database that associates the IP address of a particular electronic device with the CoA of the electronic device. At block 720, the data center may use the identification of the electronic device to identify a subscription identification associated with the electronic device. In accordance with an embodiment, the data center may match the IMSI of the electronic device with the MSISDN of the electronic device.

At block 725, the data center may determine whether there is an active product or service associated with the subscription identifier. In an embodiment, the active product or service may correspond to a service or product selected by the electronic device, such as various cellular connectivity options for the electronic device based on duration, data limit, or other parameters. If there is no active product or service ("No"), the process may terminate or proceed to other functions.

If a valid product or service exists ("yes"), processing may proceed to block 730, where the data center may modify the communication request to indicate a subscription identity. In an embodiment, the data center may replace the IMSI with the MSISDN in the origin field (or similar parameter) of the communication request. Thus, when the communication is delivered to the destination electronic device, the communication may appear as a cellular-based communication originating from the electronic device, as if it were connected to a cellular-based network.

At block 735, the data center may transmit the modified communication request to the service provider network for delivery to the destination electronic device. If the communication request corresponds to a voice-based communication request, the data center may transmit the modified voice-based communication request to the ITSP for delivery to the destination electronic device. If the communication request corresponds to a SIP message (and is converted to an SMS message), the data center may transmit the modified SMS message to the SMSC for delivery to the destination electronic device.

At block 740, the data center may receive confirmation that the communication request was delivered to the destination electronic device, and at block 745, the data center may forward the confirmation for delivery to the electronic device. In some embodiments, the data center may send a SIP 200 OK message via a TLS connection for delivery to the electronic device. In some embodiments, if the communication corresponds to voice-based communication, an RTP port may be established between the electronic device and the destination electronic device, via which the voice-based communication may be facilitated.

FIG8 illustrates an example method 800 for facilitating communication of an electronic device intended to be connected to a non-ground (i.e., air-based) communication network. Further, communication can be initiated by a source electronic device connected to a ground-based network. Depending on the embodiment, the communication can be text-based communication (e.g., SMS message) or voice-based communication. Method 800 can be operated in conjunction with any or all of the systems, vehicles, and/or electronic devices discussed above with respect to FIG1-FIG6, or method 800 can be operated in conjunction with other suitable systems, vehicles, and/or electronic devices. In an embodiment, at least a portion of method 800 can be performed by a data center including an SBC/SIP server and/or a registration server, such as the data center 129 described with respect to FIG1 or the data center 429 described with respect to FIG4.

At block 805, the data center may receive a communication request initiated by an electronic device connected to a terrestrial network, whereby the communication request includes a subscription identifier of a destination electronic device. In some embodiments, if the communication corresponds to a voice-based communication, the data center may receive a request for a routing number associated with the destination electronic device from a service provider network associated with the destination electronic device. The data center may provide the routing number to the service provider network. Further, the communication request may be in the form of a SIP INVITE request from a SIP trunk provider via an MSC, wherein the SIP INVITE request includes the routing number. In other embodiments, if the communication corresponds to a text-based communication, the communication request may be an SMS message received from an SMSC. Further, the subscription identifier of the electronic device received in the communication request may be the MSISDN of the destination electronic device.

At block 810, the data center may determine whether there is an active product or service associated with the subscription identifier. In an embodiment, the active product or service may correspond to a service or product selected by the destination device, such as various cellular connectivity options for the destination electronic device based on duration, data limit, or other parameters. If there is no active product or service ("No"), the process may terminate or proceed to other functions.

If there is a valid product or service ("yes"), processing may proceed to box 815, where the data center may use the subscription identifier to identify the identifier of the destination electronic device. The identifier of the destination electronic device may be the IMSI of the destination electronic device. At box 820, the data center may generate a SIP message indicating the identifier of the destination electronic device. In some embodiments, if the communication request is received as an SMS message, the data center may convert the SMS message into a SIP message. In particular, the SMS message may include body text data, and the data center may convert the SMS message by appending the body text data to the SIP message. Further, the data center may obtain a SIP URI associated with the MSISDN of the destination electronic device and may include the SIP URI in the generated SIP message. In other embodiments, if the communication request corresponds to a voice-based communication, the data center may generate a SIP message that replaces the routing number corresponding to the destination electronic device with the IMSI of the destination electronic device.

At box 825, the data center may establish a TLS protocol session with the destination electronic device. At box 830, the data center may transmit the SIP message to the onboard communication network via the TLS protocol session for delivery to the destination electronic device. In some embodiments, if the communication request corresponds to text-based communication, the data center may transmit a SIP message including a SIP URI to the onboard communication network for delivery to the destination electronic device. In other embodiments, if the communication request corresponds to voice-based communication, the data center may transmit a SIP invite message to the onboard communication network for delivery to the destination electronic device. At box 835, the data center may receive a SIP OKAY response indicating that the destination electronic device has received the SIP message. In some embodiments, if the communication corresponds to voice-based communication, an RTP port may be established between the electronic device and the destination electronic device, via which voice-based communication may be facilitated.

FIG9 illustrates a block diagram of an example registration server 914 that can operate in accordance with any of the systems, methods, techniques, and concepts discussed herein (and/or any one or more portions thereof). In an embodiment, the registration server 914 can be any of the registration servers 114, 214, 314, 414, 514, 614 discussed with respect to FIG1-6.

The registration server 914 may include a processor 996 (which in some embodiments may be referred to as a controller, microcontroller, or microprocessor) for executing computer-executable instructions, a program memory 991 for permanently storing data related to the computer-executable instructions, a random access memory (RAM) or other suitable memory 997 for temporarily storing data related to the computer-executable instructions, and input/output (I/O) circuits or components 998, all of which may be interconnected via an address/data bus or suitable bus 999. As used herein, the terms "computer-executable instructions," "computer-executable instructions," and "instructions" are used interchangeably.

Registration server 914 may include one or more network interfaces 904, via which registration server 914 can wirelessly connect to one or more corresponding networks 989 or devices. Typically, network interface 904 enables registration server 914 to connect to devices and entities via corresponding cellular radio frequency (RF) bands (e.g., AMP, TDMA, CDMA, GSM, PCS, 3G, 4G, 5G) and/or any other terrestrial cellular radio frequency bands. For example, registration server 914 may communicate with electronic devices via a terrestrial base station or a small cell using one of network interfaces 904. Generally, as used herein, the term "cellular radio band" refers to a portion of the RF spectrum allocated by a government agency or other entity that regulates spectrum use. One or more network interfaces 904 enable registration server 914 to communicate via one or more cellular radio bands (e.g., in a terrestrial environment) and may include one or more corresponding transceivers. Although not shown in FIG. 9 , registration server 914 may also include one or more wireless network interfaces that enable registration server 914 to communicate via non-cellular-based networks (such as a local area network).

9 , it should be appreciated that, although only one processor 996 is shown, the registration server 914 may include multiple processors 996. Similarly, the memory of the registration server 914 may include multiple RAMs (random access memories) 997, multiple program memories 991, and/or one or more other data storage entities or one or more other types of memories 905. For example, the RAM 997, program memories 991, and/or data storage entities 905 may be implemented as one or more semiconductor memories, magnetically readable memories, optically readable memories, biological memories, and/or other tangible, non-transitory computer-readable storage media.

Additionally, I/O circuitry 998 may be connected to display device 902. For example, display device 902 may enable a user or administrator of registration server 914 to manage communication facilities. Registration server 914 may also include other elements common to general purpose computing devices (not shown).

Memory 991 stores an operating system 993 that can facilitate the functionality discussed herein. Processor 996 can cooperate with memory 991 to execute operating system 993 and a set of application programs 994 comprising computer-executable electronic instructions for facilitating various registration and communication facilitation features. In particular, the set of application programs 994 can include a communication service application 906 configured to facilitate text-based and voice-based communications as discussed herein. It should be appreciated that other application programs are contemplated.

In some embodiments, computer-executable instructions for a collection of applications 994 may be configured to cause the registration server 914 to perform one or more portions of one or more methods described herein. The computer-executable instructions may be stored on a tangible, non-transitory computer-readable storage medium, such as on the memory 991 or on some other suitable storage. Furthermore, the computer-executable instructions may be executed by one or more processors 996. The computer-executable instructions may be downloaded to or otherwise communicated to the registration server 914.

FIG10 illustrates a block diagram of an example electronic device that can operate according to any of the systems, methods, techniques, and concepts discussed herein (and/or any one or more portions thereof). Electronic device 1005 can be, for example, a smartphone, a smart device, a laptop, a tablet computer, an electronic reading device, or any other communication or computing device configured for wireless communication. In an embodiment, electronic device 1005 can be any of the electronic devices 105, 205, 305, 405, 505, 605 (or any of the additional devices 110, 210, 310, 410, 510, 610) described with respect to FIG1-6 .

The electronic device 1005 may include a processor 1096 (which in some embodiments may be referred to as a controller, microcontroller, or microprocessor) for executing computer-executable instructions, a program memory 1091 for permanently storing data related to the computer-executable instructions, a random access memory (RAM) or other suitable memory 1097 for temporarily storing data related to the computer-executable instructions, and input/output (I/O) circuits or components 1098, all of which may be interconnected via an address/data bus or suitable bus 1099. As used herein, the terms "computer-executable instructions," "computer-executable instructions," and "instructions" may be used interchangeably.

The electronic device 1005 may include one or more wireless network interfaces 1001, via which the electronic device 1005 may wirelessly connect to one or more networks 1089 or devices. In an embodiment, the one or more wireless network interfaces 1001 enable the electronic device 1005 to wirelessly connect to one or more other networks or devices, including or contained in a terrestrial or non-terrestrial environment. For example, via one of the wireless network interfaces 1001, the electronic device 1005 may be communicatively connected to a non-terrestrial local area network (e.g., a non-terrestrial wireless local area network (LAN) hosted onboard a vehicle) using a wireless Ethernet protocol. Additionally or alternatively, via one of the wireless network interfaces 1001, the electronic device 1005 may be communicatively connected to a local area wireless network or device using a near field communication (NFC) protocol (e.g., Bluetooth). Generally, the one or more wireless network interfaces 1001 may support any radio frequency band other than a cellular radio frequency band, and the one or more wireless network interfaces 1001 may include one or more corresponding transceivers. In an embodiment, the wireless network interface 1001 communicates with a wireless access point, such as a wireless access point on an aircraft, which allows the electronic device 1005 to connect to the onboard network.

The electronic device 1005 may further include one or more cellular radio interfaces 1004 to support communication via corresponding cellular radio frequency (RF) bands (e.g., AMP, TDMA, CDMA, GSM, PCS, 3G, 4G, 5G) and/or any other terrestrial cellular radio frequency bands. For example, the electronic device 1005 may communicate with a terrestrial base station or with a small cell using one or more cellular network interfaces 1004. Further, the electronic device 1005 may communicate with a registration server (such as the registration server 914 described with respect to FIG. 9 ) via a WAN using one of the cellular network interfaces 1004. Generally, as used herein, the term "cellular radio frequency band" refers to a portion of the RF spectrum allocated by a government agency or other entity that manages spectrum use. The cellular network interface 1004 may allow the electronic device 1005 to communicate via one or more cellular radio frequency bands (e.g., in a terrestrial environment) and may include one or more corresponding transceivers. In one embodiment, the one or more wireless network interfaces 1004 are not used by the electronic device 1005 to communicate in a non-terrestrial environment. In one embodiment, the one or more wireless network interfaces 1001 and the one or more cellular network interfaces 1004 can each be independently enabled and disabled.

10 , it should be appreciated that, although only one processor 1096 is shown, the electronic device 1005 may include multiple processors 1096. Similarly, the memory of the electronic device 1005 may include multiple RAMs (random access memories) 1097, multiple program memories 1091, and/or one or more other data storage entities or one or more other types of memories 1006. For example, the RAMs 1097, program memories 1091, and/or data storage entities 1006 may be implemented as one or more semiconductor memories, magnetically readable memories, optically readable memories, biological memories, and/or other tangible, non-transitory computer-readable storage media.

In addition, although I/O circuit 1098 is shown as a single frame, it should be appreciated that I/O circuit 1098 can include multiple different types of I/O circuits or connectors. For example, a first I/O circuit can correspond to display device 1002, and a first I/O circuit or a second I/O circuit can correspond to user interface 1003. The user interface 1003 combined with display device 1002 can include various I/O components (for example, capacitance or resistance touch sensing input panel, key, button, lamp, LED, cursor control device, tactile device, etc.). In some embodiments, display device 1002 can be a touch screen using a single display technology or a combination of display technologies, and can include a thin, transparent touch sensor component that is superimposed on the display portion visible to the user. For example, these displays include capacitance display, resistance display, surface acoustic wave (SAW) display, optical imaging display, etc. User interface 1003 can further include audio components such as microphone and/or speaker. Electronic device 1005 can also include other elements shared with general computing device (not shown).

Memory 1091 stores an operating system 1093 capable of facilitating the functionality discussed herein. A processor 1096 can cooperate with memory 1091 to execute operating system 1093 and a set of applications 1094 comprising computer-executable electronic instructions for facilitating various registration features. In particular, the set of applications 1094 can include a communication application 1006 configured to facilitate communications as discussed herein. For example, communication application 1006 can initiate and receive text-based and voice-based communications. It should be appreciated that other applications are contemplated, such as a dedicated SMS messaging application.

In some embodiments, the computer-executable instructions for the set of applications 1094 can be configured to enable the electronic device 1005 to perform one or more portions of one or more methods described herein. The computer-executable instructions can be stored on a tangible, non-transitory computer-readable storage medium, such as on the memory 1091 or some other suitable storage. Furthermore, the computer-executable instructions can be executed by one or more processors 1096. The computer-executable instructions can be downloaded to or otherwise transferred to the electronic device 1005.

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

Furthermore, while the foregoing text sets forth detailed descriptions of many different embodiments, it should be understood that the scope of this patent is defined by the text of the claims set forth at the end of this patent. The detailed description is to be construed as merely exemplary and does not describe every possible embodiment, as describing every possible embodiment would be impractical, if not impossible. Numerous alternative embodiments may be implemented using current technology or technology developed after the filing date of this patent, which will still fall within the scope of the claims. Therefore, various modifications and variations may be made to the techniques and structures described and illustrated herein without departing from the spirit and scope of the claims. Therefore, it should be understood that the methods and apparatus described herein are illustrative only and do not limit the scope of the claims.