Patent Description:
Vehicles such as commercial aircraft, military aircraft, unmanned aircraft, and the various systems thereon, generate and consume considerable amounts of data. For example, engines are monitored at every stage of operation, which results in generation of significant amounts of data. Such engine monitoring data includes, for example, but not limited to compression ratios, rotation rate (RPM), temperature, and vibration data. In addition, fuel related data, maintenance, Airplane Health Monitoring (AHM), operational information, catering data, In-flight Entertainment Equipment (IFE) updates and passenger data like duty free shopping are routinely and typically generated onboard the aircraft.

At least some of these systems wirelessly connect to a ground system through a central airplane server and central transceiver for data transmission and reception. However, for certain critical systems and critical data are not configured for wireless transfer of data. Therefore, when an aircraft arrives at a gate, much of the data is downloaded manually from the aircraft. Specifically, data recording devices are manually coupled to interfaces on the aircraft and the data is collected from the various data generators or log books for forwarding and processing at a back office. In addition, the back office function transmits updated datasets, for example data related to a next flight(s) of the aircraft, to the aircraft.

Demand for additional communication channels and data transfer is driving rapid change in connection with such communications. Such increased demand is due, for example, to increasing reliance by ground systems upon data from the aircraft, as well as increased communication needs of the flight crew, cabin crew, and passengers. In addition, data diversity along with an increasing number of applications producing and consuming data in support of a wide range of aircraft operational and business processes puts additional demand on communications. However, many of these additional communication channels could require additional holes to be drilled into the aircraft instead of using existing resources. Furthermore, it is crucial that the data transmitted is secured to prevent authorized personnel from accessing secure data or introducing malicious data into the aircraft systems.

<CIT> states according to its abstract methods and systems for terrestrial data transmission between aircrafts and external networks connected to gates at airports. This type of data transmission is performed through an electrical power cable that includes multiple conductors interconnecting electrical components of an aircraft and a gate. Each conductor may be used to establish a separate broadband over power line (BPL) communication channel using its own frequency range that does not overlap with frequency ranges of other channels. As such, no radio frequency (RF) shielding is needed in the cable and any standard multi-conductor cable may be used. A channel management unit is used to control allocation of data domains among different communication channels depending on characteristics of the data domains, characteristics of the channels, and other factors. For example, one channel may be designated for secure data transfer of specific data domains, such as aircraft control data.

<CIT> states according to its abstract methods and apparatus for communicating between an aircraft and a terminal when the aircraft is on the ground. The connection between the aircraft and the terminal is made over a ground power line while the aircraft is being supplied with power. The ground power line comprises one or more wires, which are typically unshielded and cause radio interference. At the transmitting end, multiple copies of the same signal offset in phase relative to one another over the ground power line. Each data stream is coupled to a respective wire in the ground power line. At the receiving end, the multiple copies of the signal are extracted from the respective wires of the ground power line and combined to generate a combined signal with improved signal-to-noise ratio. Radio interference is suppressed by transmitting the data streams in a phase offset manner so that the unwanted emissions cancel.

In an aspect of the invention to which this European patent refers there is provided a broadband over powerline unit as defined in claim <NUM>. In a further aspect of the invention to which this European patent refers there is provided a method for communicating via a BPL connection implemented by a BPL unit as defined in claim <NUM>.

The described embodiments enable secure vehicle broadband communication with a data network. More particularly, the present disclosure is directed to using three-phase power with broadband over powerline (BPL) communications to enable secure and efficient aircraft information exchange. The Communication over Powerline technology may be used to improve the data transmission and increase data security from the airplane to the airline's back office and vice versa.

Described herein are computer systems such as the BPL master and slave computer devices and related computer systems. As described herein, all such computer systems include a processor and a memory. However, any processor in a computer device referred to herein may also refer to one or more processors wherein the processor may be in one computing device or in a plurality of computing devices acting in parallel. Additionally, any memory in a computer device referred to herein may also refer to one or more memories wherein the memories may be in one computing device or in a plurality of computing devices acting in parallel.

Furthermore, while the terms "master" and "slave" are used herein to describe different computer devices, in some embodiments, this different devices may be considered more parallel devices rather than having the master device control the slave device. In some embodiments, the master device may be controlled by the slave device. For the purposes of this disclosure, the slave device is the device on the vehicle and the master device is the device on the ground or at the location that the vehicle is currently docked or stopped.

As used herein, a processor may include any programmable system including systems using micro-controllers, reduced instruction set circuits (RISC), application specific integrated circuits (ASICs), logic circuits, and any other circuit or processor capable of executing the functions described herein. The above examples are not intended to limit in any way the definition and/or meaning of the term "processor.

As used herein, the term "database" may refer to either a body of data, a relational database management system (RDBMS), or to both. As used herein, a database may include any collection of data including hierarchical databases, relational databases, flat file databases, object-relational databases, object-oriented databases, and any other structured or unstructured collection of records or data that is stored in a computer system. The above examples are not intended to limit in any way the definition and/or meaning of the term database. Examples of RDBMS's include, but are not limited to, Oracle® Database, MySQL, IBM® DB2, Microsoft® SQL Server, Sybase®, and PostgreSQL. However, any database may be used that enables the systems and methods described herein. (Oracle is a registered trademark of Oracle Corporation, Redwood Shores, California; IBM is a registered trademark of International Business Machines Corporation, Armonk, New York; Microsoft is a registered trademark of Microsoft Corporation, Redmond, Washington; and Sybase is a registered trademark of Sybase, Dublin, California.

In one embodiment, a computer program is provided, and the program is embodied on a computer readable medium. In an example embodiment, the system is executed on a single computer system, without requiring a connection to a server computer. In a further embodiment, the system is being run in a Windows® environment (Windows is a registered trademark of Microsoft Corporation, Redmond, Washington). In yet another embodiment, the system is run on a mainframe environment and a UNIX® server environment (UNIX is a registered trademark of X/Open Company Limited located in Reading, Berkshire, United Kingdom). The application is flexible and designed to run in various different environments without compromising any major functionality. In some embodiments, the system includes multiple components distributed among a plurality of computing devices. One or more components may be in the form of computer-executable instructions embodied in a computer-readable medium.

As used herein, the terms "software" and "firmware" are interchangeable, and include any computer program stored in memory for execution by a processor, including RAM memory, ROM memory, EPROM memory, EEPROM memory, and non-volatile RAM (NVRAM) memory. The above memory types are examples only and thus, are not limiting as to the types of memory usable for storage of a computer program.

Furthermore, as used herein, the term "real-time" refers to at least one of the time of occurrence of the associated events, the time of measurement and collection of predetermined data, the time to process the data, and the time of a system response to the events and the environment. In the embodiments described herein, these activities and events occur substantially instantaneously.

The systems and processes are not limited to the specific embodiments described herein. In addition, components of each system and each process can be practiced independent and separate from other components and processes described herein. Each component and process also can be used in combination with other assembly packages and processes.

<FIG> is a block diagram of a power and digital communication transmission system <NUM> in accordance with an exemplary embodiment of the disclosure. In the exemplary embodiment, power and digital communication transmission system <NUM> includes an electrical aircraft umbilical <NUM> comprising a supply end <NUM>, a plug end <NUM>, and an electrical conductor <NUM> extending there between. Plug end <NUM> is configured to mate with a vehicle such as an aircraft <NUM> such that electrical power is supplied to aircraft <NUM> through electrical conductor <NUM> from supply end <NUM>. The electrical energy used to power commercial airplanes on the ground is 115Vac, <NUM>, three-phase power, and includes a neutral line. In the exemplary embodiment, supply end <NUM> couples to a ground power system <NUM> at an airport terminal gate <NUM>. Ground power system <NUM> is configured to receive electrical power from a power supply through a power supply conduit <NUM>. In other embodiments, ground power system <NUM> is located on a pier to couple to a boat, barge, or ship (not shown). In still other embodiments, ground power system <NUM> is positioned at a garage or service facility and is configured to couple to a wheeled vehicle, for example, but not limited to a car, a recreational vehicle (RV), or a train. Additionally, ground power system <NUM> may comprise another vehicle, such as a space vehicle, undersea or sea surface vehicle wherein one or both vehicles are moving with respect to each other and/or their surroundings while coupled through umbilical <NUM>.

Power and digital communication transmission system <NUM> also includes a first interface device <NUM> electrically coupled to supply end <NUM>. In the exemplary embodiment, first interface device <NUM> is electrically coupled to supply end <NUM> through power supply conduit <NUM> and ground power system <NUM>, where interface device <NUM> is electrically coupled to the power supply conduit <NUM> through which ground power system <NUM> receives electrical power. In an alternative embodiment, first interface device <NUM> is electrically coupled to supply end <NUM> downstream of ground power system <NUM>. In one embodiment, ground power system <NUM> is a distributed power system operating at voltages that are incompatible with aircraft <NUM>. In such embodiments, a point of use power system <NUM> is utilized to step the voltage to a level that is compatible with aircraft <NUM>. In another alternative embodiment, first interface device <NUM> is electrically coupled to electrical conductor <NUM> internal to ground power system <NUM>. First interface device <NUM> is also coupled to a network <NUM> through a wired network access point <NUM> or a wireless communication link <NUM>.

Power and digital communication transmission system <NUM> also includes a second interface device <NUM> electrically coupled to plug end <NUM> when umbilical <NUM> is coupled to aircraft <NUM>. In the exemplary embodiment, second interface device <NUM> is electrically coupled to an onboard power bus <NUM> through plug end <NUM> through an umbilical plug <NUM> that traverses through a wall of a fuselage <NUM> of aircraft <NUM>. Second interface device <NUM> is also coupled to an onboard network <NUM> through an onboard wired network access point <NUM> or an onboard wireless communication link <NUM>. In some situations, onboard wireless link <NUM> may be unable to transmit from the vehicle to outside of the vehicle due to attenuation from the vehicle itself. Examples of onboard wireless link <NUM> may include, but are not limited to, <NUM> or low data rate wireless such as IoT applications over BLE, Zigbee, Wi-Fi, and Bluetooth.

First interface device <NUM> is configured to transmit and receive data carrier signals though electrical conductor <NUM> while power is supplied to aircraft <NUM> through electrical conductor <NUM>. First interface device <NUM> is also configured to convert the data carrier signals from and to a predetermined data format on the network. Second interface device <NUM> is electrically coupled to plug end <NUM> when umbilical <NUM> is coupled to aircraft <NUM>. Second interface device <NUM> (e.g., a receiver and a transmitter, onboard transceiver) is configured to transmit and receive the data carrier signals via umbilical <NUM> between first interface device <NUM> and onboard network <NUM> while power is supplied to aircraft <NUM> through electrical conductor <NUM>. In the exemplary embodiment, each of first interface device <NUM> and second interface device <NUM> are configured to detect a communication link established through the electrical conductor and report the link to system <NUM>. Interface devices <NUM> and <NUM> are electrically matched with the characteristics of umbilical <NUM> including but not limited to wire size, shielding, length, voltage, load, frequency, and grounding.

In the exemplary embodiment, the predetermined data format is compatible with various network protocols including but not limited to, Internet network protocol, gatelink network protocol, Aeronautical Telecommunications Network (ATN) protocol, and Aircraft Communication Addressing and Reporting System (ACARS) network protocol.

In the exemplary embodiment, high-speed network service to aircraft <NUM> while parked in a service location such as an airport terminal gate is provided through a conductor of the aircraft ground power umbilical using for example, but not limited to Broadband over Power Line (BPL), X10, or similar technology. Use of this technology permits the airports and airlines to add a simple interface to the aircraft umbilical at the gate and for aircraft manufacturers to provide a matching interface within the aircraft to permit broadband Internet service to the aircraft through an aircraft power link in the umbilical.

Broadband over Power Line (BPL) is a technology that allows Internet data to be transmitted over power lines. (BPL is also sometimes called Power-line Communications or PLC. ) Modulated radio frequency signals that include digital signals from the Internet are injected/added/modulated onto the power line using, for example, inductive or capacitive coupling. These radio frequency signals are injected into or superimposed onto the alternating current power waveform that is transmitted via the electrical power conductor at one or more specific points. The radio frequency signals travel along the electrical power conductor to a point of use. Little, if any, modification is necessary to the umbilical to permit transmission of BPL. The frequency separation in the umbilical substantially minimizes crosstalk and/or interference between the BPL signals and other wireless services. BPL permits higher speed and more reliable Internet and data network services to the aircraft than wireless methods. Using BPL also eliminates the need to couple an additional separate cable to aircraft <NUM> because it combines aircraft electrical power and Internet/data services over the same wire. System <NUM> uses for example, an approximately <NUM> to approximately <NUM> frequency or X10 similar ranges with the exact frequency range use defined and engineered by the characteristics and shielding of umbilical <NUM> and the allowable RFI/EMI levels in that particular environment.

In an embodiment, symmetrical hi-broadband BPL is used in umbilical <NUM> to transmit data communication signals at communication speeds with aircraft <NUM> at rates in the tens or hundreds of megabits per second (Mbps). Because the BPL link is dedicated to only one aircraft <NUM> and not shared as wireless is, actual throughput can be from two to ten times the wireless throughput in the same environment. In addition, the throughput is stable and reliable in airport environments, whereas the existing wireless Gatelink services vary with the amount of RF interference and congestion at each airport.

In the exemplary embodiment, each of the three phases of power may be used to transmit and receive data. For the purpose of this discussion, the three phases may be described as Phase A, Phase B, and Phase C. Each of these three phases may transmit separate data simultaneously. As described herein, Phase A may transmit flight critical safety data, while Phase B may be transmitting airline specific data and Phase C is transmitting entertainment data, such as movies and audio. In one embodiment, Phase A transmits data within the frequency of <NUM>-<NUM>, Phase B transmits data from <NUM>-<NUM>, and Phase C transmits between <NUM>-<NUM>. In the exemplary embodiment, the three phases ae separated based on frequency band, time, and encryption.

Furthermore, the data may be transmitted using Ground Base Management Protocol (GBMP)/Simple Network Management Protocol (SNMP). For example, the GBMP/SNMP may use four messages to communicate, such as TRAP, GET, GET-RESPONSE, and SET. In this example, the TRAP message may be used for situations such as failure on power, strange messages, and the wrong private key.

In addition, the data transmitted over the powerline may be encrypted. In the exemplary embodiment, the first interface device <NUM> may encrypt the data prior to it being transmitted over the power conduit <NUM>. In this embodiment, second interface device <NUM> decrypts the data as received and routes it to the appropriate location. In some embodiments, data over each of the three phases is encrypted differently, such as by using a different private/public key pair. When data is transmitted from the second interface device <NUM> to the first interface device <NUM>, the second interface device <NUM> encrypts the data and the first interface device <NUM> decrypts the data as described herein.

<FIG> illustrates a block diagram of a master control system <NUM> in the power and digital communication transmission system <NUM> shown in <FIG>. In the exemplary embodiment, the master control system <NUM> includes a master control unit <NUM>. In the exemplary embodiment, the master control unit <NUM> is coupled to the electrical power conduit <NUM> and functions as the first interface device <NUM> (shown in <FIG>).

The master control unit <NUM> includes a central processing unit (CPU) <NUM> in communication with a powerline circuit board <NUM> (also known as a powerline transceiver). The powerline circuit board <NUM> allows the CPU <NUM> to communicate with other devices through a powerline and BPL connection <NUM>. The BPL connection <NUM> uses powerlines similar to the electrical aircraft umbilical <NUM> (shown in <FIG>).

The master control unit <NUM> also includes a Wi-Fi card <NUM> (also known as a Wi-Fi transceiver) for communicating with remotes devices via a first wireless connection <NUM>. The master control unit <NUM> further includes a cell modem card <NUM> (also known as a cellular modem) for communicating with remoted devices via a second wireless connection <NUM>. In some embodiments, master control unit <NUM> includes a removable memory <NUM>. The removable memory <NUM> includes any memory card and device that may be removable attached to master control unit including, but not limited to, universal serial bus (USB) flash drives, external hard drives, and non-magnetic media. The CPU <NUM> is in communication with and in control of powerline circuit board <NUM>, Wi-Fi card <NUM>, cell modem card <NUM>, and removable memory <NUM>. While the above describes Wi-Fi and cellular connections cards <NUM> and <NUM> may also connect wirelessly through other methodologies, including, but not limited to, <NUM>, AeroMACS, WiMAX, Whitespace and Bluetooth.

In the exemplary embodiment, the CPU <NUM> detects that a connection has been made with another device over the BPL connection <NUM>, such as to second interface device <NUM> (shown in <FIG>). The CPU <NUM> receives a plurality of data via BPL connection <NUM> and the powerline transceiver <NUM>. The CPU <NUM> determines a destination for the plurality of data. In some embodiments, the destination is another computer. In other embodiments, the destination is a plurality of computers or a computer network. In some embodiments, the destination is one or more computer systems associated with the airline, the airport, and/or an operations back office. The master control unit <NUM> is remote from the destination. In the exemplary embodiment, the master control unit <NUM> able to remotely connect to the destination via one or more wireless networks. In these embodiments, the CPU <NUM> determines whether to route the plurality of data through the first wireless transceiver (i.e., the Wi-Fi card <NUM>) or the second wireless transceiver (i.e., the cell modem card <NUM>). The first and second wireless transceivers may also connect using <NUM>, AeroMACS, WiMAX, Whitespace, and Bluetooth.

In some embodiments, the CPU <NUM> tests the signal strength of the first wireless connection <NUM> and the second wireless connection <NUM>. The CPU <NUM> compares the signal strength of the first wireless connection <NUM> and the second wireless connection <NUM> to determine which connection to use to transmit the plurality of data to the destination. Then the CPU <NUM> routes the plurality of data to the destination using the determined wireless connection. In some further embodiments, master control unit <NUM> also considers the reliability of the first and second wireless connections <NUM> and <NUM> in determining which wireless connection to use
In some embodiments, if the signal strength of the first wireless connection <NUM> and the second wireless connection <NUM> are both below corresponding predetermined thresholds, then the CPU <NUM> stores the plurality of data on the removable memory <NUM>. In some further embodiments, the CPU <NUM> transmits the plurality of data to the destination at a subsequent time when the signal strength of one of the first wireless connection <NUM> and the second wireless connection <NUM> exceeds the respective predetermined threshold.

In some further embodiments, the CPU <NUM> audits the voltage, current, and phase of the BPL connection <NUM> to determine if the connection is within parameters. The CPU <NUM> may determine whether or not to transmit the plurality of data based on the audit. Furthermore, the CPU <NUM> may determine whether or not to receive the data over the BPL connection <NUM> if the CPU <NUM> determines that the connection is not within parameters. This ensures that the BPL connection <NUM> is properly connected prior to transmitting a plurality of data to ensure both the security of the connection and the integrity of the data being received by the master control unit <NUM>.

In some further embodiments, the master control unit <NUM> transmits data over the BPL connection <NUM> to the slave unit about future aircraft operations, such as, but not limited to, software updates for one or more systems, additional movies and/or other entertainment options, flight paths, and weather information. In these embodiments, the master control unit <NUM> may have received the data for uploading to the slave unit from the airport, the airline, or an operations back office.

In some additional embodiments, master control unit <NUM> is stored on aircraft <NUM>. When aircraft <NUM> lands at an airport that does not have an existing BPL system, master control unit <NUM> is deployed to connect to one or more wireless networks at the airport. In some further embodiments, the master control unit <NUM> is secured with a password to ensured access by authorized users.

In the exemplary embodiment, the master control unit <NUM> executes three virtual machines (VM) <NUM>, <NUM>, and <NUM>. Each one of these virtual machines is configured to transmit and receive data over the BPL connection <NUM> using a different phase. For the purposes of this discussion, VM <NUM> is associated with Phase A, VM <NUM> with Phase B, and VM <NUM> with Phase C. In the exemplary embodiment, the three VMs <NUM>, <NUM>, and <NUM> allow for a software solution rather than requiring three pairs of hardware adapters for transmitting over the three phases. This allows a single pair of hardware adapters to be used and guided by the virtual machines.

In some embodiments, the three VMs <NUM>, <NUM>, and <NUM> are executed by separate processors. In other embodiments, a single processor may execute more than one of the VMs. Furthermore, in some embodiments, the three VMs <NUM>, <NUM>, and <NUM> may be combined into a single virtual machine.

In the exemplary embodiment, each VM <NUM>, <NUM>, and <NUM> encodes each message with a tag to represent either which Phase the message is to be transmitted on or which VM the message is associated with. In the exemplary embodiment, the three VM are each associated with a priority, VM <NUM> transmits and receives high priority data, VM <NUM> transmits and receives medium priority data, and VM <NUM> transmits and receives low priority data. In this embodiment, high priority information is, for example, flight critical safety data, such as avionics data, and passenger personal data. Medium priority data is airline proprietary data, airline surveillance data, and other airplane data less critical than that considered high priority. Low priority data includes entertainment data, such as video, audio, and movies. While the examples described herein use priority to separate the three VMs/Phases, other schemes may be used and the data may be divided up based on other criteria in other embodiments.

In the exemplary embodiment, data that is being transmitted over the BPL connection <NUM> is encrypted to prevent unauthorized access. In the exemplary embodiment, the master control unit <NUM> encrypts all data prior to transmission using a first encryption method, such as, but not limited to, <NUM>-AES (advanced encryption standard) and private/public key encryption. In some embodiments, only the payload is encrypted. In other embodiments, the entire message is encrypted. This embodiment may be used with frame based transmission.

In addition to the encryption provided by the master control unit <NUM>, the VMs <NUM>, <NUM>, and <NUM> may also encrypt the data. In the exemplary embodiment, high priority data is encrypted using another encryption method, such as, but not limited to, <NUM>-AES. This means that the high priority data is doubly encrypted. In this embodiment, the medium priority data may be encrypted using a different encryption method, such as, but not limited to, <NUM>-AES. In the exemplary embodiment, low priority data is not additionally encrypted. For example, high priority data is first encrypted by VM <NUM> and then additionally encrypted by the master control unit <NUM> prior to transmission. In other embodiments, other encryption methods and schemes for encrypting the data being transmitted over the three phases may be used.

In addition to transmitting the data, the three VMs <NUM>, <NUM>, and <NUM> receive and decrypt data transmitted over the BPL connection <NUM> to the master control unit <NUM>.

In the exemplary embodiment, the three VMs <NUM>, <NUM>, and <NUM> are in communication with each other. If one of the VMs <NUM>, <NUM>, and <NUM> finishes transmitting its data, that VM notifies the others to allow them to use the bandwidth of its assigned phase. For example, if VM <NUM> finishes transmitting the medium priority data, while the other two VMs <NUM> and <NUM> are still transmitting their data, then VM <NUM> will send a message to VMs <NUM> and <NUM>. In this embodiment, VM <NUM> will start transmitting the high priority data over Phase A and Phase B, while VM <NUM> continues to use Phase C. In this example, VM <NUM> will encrypt the data that is to be transmitted over Phases A and B using the same encryption method. In the embodiment, described herein, the extra bandwidth is allocated base on priority. However, in other embodiments, different methods of allocating bandwidth may be used.

In some further embodiments, the CPU <NUM> allocates the bandwidth for the three phases. In these embodiments, when the CPU <NUM> determines that VM <NUM> is no longer transmitting, the CPU <NUM> allocates the bandwidth on Phase B to VM <NUM>. In other embodiments, CPU <NUM> knows how much data each VM <NUM>, <NUM>, and <NUM> has to transmit and determines how best to allocate the bandwidth based on the corresponding amounts of data.

<FIG> illustrates a block diagram of a slave system <NUM> in the power and digital communication transmission system <NUM> shown in <FIG>. In the exemplary embodiment, the slave system <NUM> includes a slave unit <NUM> that may be onboard a vehicle. In the exemplary embodiment, the slave unit <NUM> is similar to the second interface device <NUM> (shown in <FIG>).

The slave unit <NUM> includes a processor or central processing unit (CPU) <NUM> in communication with a powerline circuit board <NUM> (also known as a powerline transceiver). The powerline circuit board <NUM> allows the CPU <NUM> to communicate with other devices through a BPL connection <NUM>. The BPL connection <NUM> uses powerlines similar to the electrical aircraft umbilical <NUM> (shown in <FIG>).

In some embodiments, the slave unit <NUM> includes a removable memory <NUM>. Removable memory <NUM> includes any memory card and device that may be removable attached to master control unit including, but not limited to universal serial bus (USB) flash drives, external hard drives, and non-magnetic media. The processor or CPU <NUM> is in communication with and in control of powerline circuit board <NUM> and removable memory <NUM>. In some embodiments, slave unit <NUM> is onboard an aircraft <NUM> and has a connection <NUM> to a plurality of systems aboard the aircraft. In these embodiments, slave unit <NUM> receives data from the plurality of systems about the operation of the aircraft.

In the exemplary embodiment, the CPU <NUM> receives a plurality of data from the plurality of systems over connection <NUM>. The CPU <NUM> determines whether a connection has been made with another device over the BPL connection <NUM>, such as to master control unit <NUM> (shown in <FIG>). If a connection has been made, the CPU <NUM> transmits, via the powerline transceiver <NUM>, the plurality of data to the BPL master control unit <NUM>. If there is no connection, the CPU <NUM> stores the plurality of data in the removable memory <NUM>.

In an exemplary embodiment, the processor or CPU <NUM> of slave unit <NUM> onboard the aircraft determines if the aircraft <NUM> is on the ground prior to determining whether or not the powerline transceiver <NUM> is connected to the master control unit <NUM>. In some embodiments, the CPU <NUM> continuously receives data from the plurality of systems. The CPU <NUM> stores that data in the removable memory <NUM>. When the CPU <NUM> determines that the aircraft is on the ground and connected to a master control unit <NUM>, the CPU <NUM> transfers the data from the removable memory <NUM> to the master control unit <NUM> via the BPL connection <NUM>.

In some further embodiments, the CPU <NUM> audits the voltage, current, and phase of the BPL connection <NUM> to determine if the connection is within parameters. The CPU <NUM> may determine whether or not to transmit the plurality of data based on the audit. Furthermore, the CPU <NUM> may determine whether or not to receive the data over the BPL connection <NUM> if the CPU <NUM> determines that the connection is not within parameters. This ensures that the BPL connection <NUM> is properly made prior to transmitting a plurality of data to ensure both the security of the connection and the integrity of the data being transmitted to and received from the master control unit <NUM>.

In some further embodiments, the master control unit <NUM> transmits data over the BPL connection <NUM> to the slave unit <NUM> about future aircraft operations, such as, but not limited to, software updates for one or more systems, additional movies and/or other entertainment options, flight paths, and weather information. In some embodiments, the slave unit <NUM> routes the data to the appropriate systems on the vehicle. In other embodiments, the slave unit <NUM> acts as a pass-through to the vehicle's network.

In some further embodiments, the slave unit <NUM> is secured with a password to ensured access by authorized users.

In the exemplary embodiment, the slave unit <NUM> executes three virtual machines (VM) <NUM>, <NUM>, and <NUM>. Each one of these virtual machines is configured to transmit and receive data over the BPL connection <NUM> using a different phase. For the purposes of this discussion, VM <NUM> is associated with Phase A, VM <NUM> with Phase B, and VM <NUM> with Phase C. In the exemplary embodiment, the three VMs <NUM>, <NUM>, and <NUM> allow for a software solution rather than requiring three pairs of hardware adapters for transmitting over the three phases. This allows a single pair of hardware adapters to be used and guided by the virtual machines.

In the exemplary embodiment, each VM <NUM>, <NUM>, and <NUM> encodes each message with a tag to represent either which Phase the message is to be transmitted on or which VM the message is associated with. As described herein, in the exemplary embodiment, the three VMs are each associated with a priority, VM <NUM> transmits and receives high priority data, VM <NUM> transmits and receives medium priority data, and VM <NUM> transmits and receives low priority data. In this embodiment, high priority information is, for example, flight critical safety data, such as avionics data, and passenger personal data. Medium priority data is airline proprietary data, airline surveillance data, and other airplane data less critical than that considered high priority. Low priority data includes entertainment data, such as video, audio, and movies.

In the exemplary embodiment, data that is being transmitted over the BPL connection <NUM> is encrypted to prevent unauthorized access. In the exemplary embodiment, the slave unit <NUM> encrypts all data prior to transmission using a first encryption method, such as, but not limited to, <NUM>-AES (advanced encryption standard) and private/public key encryption. In some embodiments, only the payload is encrypted. In other embodiments, the entire message is encrypted. This embodiment may be used with frame based transmission.

In addition to the encryption provided by the slave unit <NUM>, the VMs <NUM>, <NUM>, and <NUM> may also encrypt the data. In the exemplary embodiment, high priority data is encrypted using another encryption method, such as, but not limited to, <NUM>-AES. This means that the high priority data is doubly encrypted. In this embodiment, the medium priority data may be encrypted using a different encryption method, such as, but not limited to, <NUM>-AES. In the exemplary embodiment, low priority data is not additionally encrypted. For example, high priority data is first encrypted by VM <NUM> and then additionally encrypted by the slave unit <NUM> prior to transmission. In other embodiments, other encryption methods and schemes for encrypting the data being transmitted over the three phases may be used.

In addition to transmitting data, the three VMs <NUM>, <NUM>, and <NUM> receive and decrypt data transmitted over the BPL connection <NUM> to the slave unit <NUM>.

<FIG> illustrates a simplified flow diagram of a three-phase data transfer system <NUM> using the power and digital communication transmission system <NUM> shown in <FIG>. In the exemplary embodiment, system <NUM> includes a first device <NUM> in communication with a second device <NUM> over a BPL connection <NUM>. First device may be similar to first interface device <NUM> (shown in <FIG>) and master control unit <NUM> (shown in <FIG>). Second device <NUM> may be similar to second interface device <NUM> (shown in <FIG>) and slave unit <NUM> (shown in <FIG>). BPL connection <NUM> may be similar to BPL connection <NUM> (shown in <FIG>) and BPL connection <NUM> (shown in <FIG>) and uses powerlines similar to the electrical aircraft umbilical <NUM> (shown in <FIG>).

In the exemplary embodiment, first device <NUM> and second device <NUM> are configured to communication over BPL connection <NUM>. The data communicated from the first device <NUM> to the second device <NUM> may be provided from an airline office or other ground based computing devices. The data communicated from the second device <NUM> to the first device <NUM> may be provided by the aircraft <NUM> (shown in <FIG>) itself. For example, this data may be from flight recorders, aircraft sensors, and other computer devices onboard the aircraft <NUM>. In some embodiments, the first device <NUM> and the second device <NUM> include hardware adapters (not shown) to allow them to communicate over the BPL connection <NUM>. In other embodiments, the first device <NUM> and the second device <NUM> are each in communication with a hardware adapter, such as a BPL modem or a powerline transceiver <NUM> and <NUM> (shown in <FIG> and <FIG> respectively).

First device <NUM> includes three virtual machines <NUM>, <NUM>, and <NUM>, which are each associated with a different phase of the BPL connection <NUM>. VM <NUM> is associated with Phase A <NUM>, VM <NUM> is associated with Phase B <NUM>, and VM <NUM> is associated with Phase C <NUM>. Second device <NUM> includes three virtual machines <NUM>, <NUM>, and <NUM>, which are each associated with a different phase of the BPL connection <NUM>. VM <NUM> is associated with Phase A <NUM>, VM <NUM> is associated with Phase B <NUM>, and VM <NUM> is associated with Phase C <NUM>.

In the exemplary embodiment, when an aircraft <NUM> lands, an umbilical <NUM> is connected to that aircraft <NUM>. Second device <NUM> is onboard the aircraft <NUM> and first device <NUM> is associated with one or more computers on the ground, such as at the gate. Once BPL connection <NUM> is established, second device <NUM> begins to transmit (or download) the data from the aircraft computers to the first device <NUM> and the computers on the ground.

In the exemplary embodiment, VM <NUM> transmits the high priority data over Phase A <NUM>. VM <NUM> transmits the medium priority data over Phase B <NUM>. VM <NUM> transmits the low priority data over Phase C <NUM>. VM <NUM> encrypts the high priority data using a first encryption method. VM <NUM> encrypts the medium priority data using a second encryption method that is different from the first encryption method. VM <NUM> does not encrypt the low priority data. The powerline transceiver (or other hardware/software in the BPL connection <NUM>) of the second device <NUM> encrypts the data prior to transmission using a third encryption method, that may be different from the first and the second encryption methods. This means that the high priority data and the medium priority data have been encrypted twice. The low priority data has only been encrypted once.

The first device <NUM> receives the data transmitted from the second device <NUM>. The received data is decrypted by the powerline transceiver <NUM> associated with the first device <NUM> using the third method and routed to one of the three VMs <NUM>, <NUM>, and <NUM> based on the associated priority. For example, each data packet may contain a tag that states which priority it belongs to. In other embodiments, each VM <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> has an Internet Protocol (IP) associated with it and the data packet contains the IP address of the destination VM. The receiving VM decrypts the data, if necessary, and routes the data to the appropriate location. For example, airline specific data may be routed to one or more computers associated with the airline back office.

If one of the three VMs <NUM>, <NUM>, and <NUM> transmits all of its data before at least one of the other two are finished, then that VM's phase may be used by one of the other two VMs. For example, if VM <NUM> completes transmitting all of the high priority data, then VM <NUM> will begin transmitting the medium priority data on Phases A <NUM> and B <NUM>. VM <NUM> will transmit the medium priority on both Phases <NUM> and <NUM> using the second encryption method. The first device <NUM> will recognize the data on Phases A <NUM> and B <NUM> as medium priority data and route that data to VM <NUM>. In this example, VM <NUM> could also transmit the medium priority data on Phase A <NUM> and allow VM <NUM> to transmit low priority data on Phases B <NUM> and C <NUM>, simultaneously. In another example, if VMs <NUM> and <NUM> have both completed their transmission, then VM <NUM> may use all three Phases <NUM>, <NUM>, and <NUM>, simultaneously. In some embodiments, how the different VMs may determine how to transmit data and which Phase to use may be based on one or more attributes the data being transmitted over the BPL connection <NUM>, the size of the data being transmitted, and user preferences.

When all of the VMs <NUM>, <NUM>, and <NUM> of second device <NUM> are finished transmitting data from the aircraft <NUM>, first device <NUM> begins transmitting data to the aircraft <NUM>. First device <NUM> uses the same methodology as described above for second device <NUM>, just the roles are reversed.

In some embodiments, the different VMs <NUM>, <NUM>, and <NUM> may begin transmitting at different times. For example, VMs <NUM> and <NUM> may begin transmitting at time zero, while VM <NUM> doesn't begin transmitting until five minutes later. This may allow one of the other VMs <NUM> and <NUM> to use the unused Phase B <NUM> for those five minutes. In other examples, VM <NUM> may begin transmitting at time zero. VM <NUM> may begin transmitting five minutes after VM <NUM>. VM <NUM> may begin transmitting five minutes after VM <NUM>. This may allow the transmitting VMs to use the unused bandwidth on the other phases. <FIG> illustrates an example configuration of a client system shown in <FIG> and <FIG>, in accordance with one embodiment of the present disclosure. User computer device <NUM> is operated by a user <NUM>. User computer device <NUM> may include first interface device <NUM>, second interface device <NUM> (both shown in <FIG>), master control unit <NUM> (shown in <FIG>), slave unit <NUM> (shown in <FIG>), first device <NUM>, and second device <NUM> (both shown in <FIG>). User computer device <NUM> includes a processor <NUM> for executing instructions. In some embodiments, executable instructions are stored in a memory area <NUM>. Processor <NUM> may include one or more processing units (e.g., in a multi-core configuration). Memory area <NUM> is any device allowing information such as executable instructions and/or transaction data to be stored and retrieved. Memory area <NUM> may include one or more computer-readable media. User computer device <NUM> also includes at least one media output component <NUM> for presenting information to user <NUM>. Media output component <NUM> is any component capable of conveying information to user <NUM>. In some embodiments, media output component <NUM> includes an output adapter (not shown) such as a video adapter and/or an audio adapter. An output adapter is operatively coupled to processor <NUM> and operatively couplable to an output device such as a display device (e.g., a cathode ray tube (CRT), liquid crystal display (LCD), light emitting diode (LED) display, or "electronic ink" display) or an audio output device (e.g., a speaker or headphones). In some embodiments, media output component <NUM> is configured to present a graphical user interface (e.g., a web browser and/or a client application) to user <NUM>. A graphical user interface may include, for example, one or more settings for connecting to another device via a power cable and/or receiving authentication information. In some embodiments, user computer device <NUM> includes an input device <NUM> for receiving input from user <NUM>. User <NUM> may use input device <NUM> to, without limitation, select and/or enter a setting for a network. Input device <NUM> may include, for example, a keyboard, a pointing device, a mouse, a stylus, a touch sensitive panel (e.g., a touch pad or a touch screen), a gyroscope, an accelerometer, a position detector, a biometric input device, and/or an audio input device. A single component such as a touch screen may function as both an output device of media output component <NUM> and input device.

User computer device <NUM> may also include a communication interface <NUM>, communicatively coupled to a remote device such as master control unit <NUM>, slave unit <NUM>, first device <NUM>, or second device <NUM>. Communication interface <NUM> may include, for example, a wired or wireless network adapter and/or a wireless data transceiver for use with a mobile telecommunications network.

Stored in memory area <NUM> are, for example, computer-readable instructions for providing a user interface to user <NUM> via media output component <NUM> and, optionally, receiving and processing input from input device <NUM>. The user interface may include, among other possibilities, a web browser and/or a client application. Web browsers enable users, such as user <NUM>, to display and interact with media and other information typically embedded on a web page or a website from master control unit <NUM>, slave unit <NUM>, first device <NUM>, or second device <NUM>. A client application allows user <NUM> to interact with, for example, master control unit <NUM>, slave unit <NUM>, first device <NUM>, or second device <NUM>. For example, instructions may be stored by a cloud service and the output of the execution of the instructions sent to the media output component <NUM>.

<FIG> illustrates an example configuration of a server system shown in <FIG> and <FIG>, in accordance with one embodiment of the present disclosure. Server computer device <NUM> may include, but is not limited to, first interface device <NUM>, second interface device <NUM> (both shown in <FIG>), master control unit <NUM> (shown in <FIG>), slave unit <NUM> (shown in <FIG>), first device <NUM>, and second device <NUM> (both shown in <FIG>). Server computer device <NUM> also includes a processor <NUM> for executing instructions. Instructions may be stored in a memory area <NUM>. Processor <NUM> may include one or more processing units (e.g., in a multi-core configuration).

Processor <NUM> is operatively coupled to a communication interface <NUM>, such that server computer device <NUM> is capable of communicating with a remote device such as another server computer device <NUM>, master control unit <NUM>, slave unit <NUM>, first device <NUM>, and second device <NUM>. For example, communication interface <NUM> may receive weather information from computer devices connected to the master control unit <NUM> via the Internet.

Processor <NUM> may also be operatively coupled to a storage device <NUM>. Storage device <NUM> is any computer-operated hardware suitable for storing and/or retrieving data, such as, but not limited to, data associated with a database. In some embodiments, storage device <NUM> is integrated in server computer device <NUM>. For example, server computer device <NUM> may include one or more hard disk drives as storage device <NUM>. In other embodiments, storage device <NUM> is external to server computer device <NUM> and may be accessed by a plurality of server computer devices <NUM>. For example, storage device <NUM> may include a storage area network (SAN), a network attached storage (NAS) system, and/or multiple storage units such as hard disks and/or solid state disks in a redundant array of inexpensive disks (RAID) configuration.

In some embodiments, processor <NUM> is operatively coupled to storage device <NUM> via a storage interface <NUM>. Storage interface <NUM> is any component capable of providing processor <NUM> with access to storage device <NUM>. Storage interface <NUM> may include, for example, an Advanced Technology Attachment (ATA) adapter, a Serial ATA (SATA) adapter, a Small Computer System Interface (SCSI) adapter, a RAID controller, a SAN adapter, a network adapter, and/or any component providing processor <NUM> with access to storage device <NUM>.

Processor <NUM> executes computer-executable instructions for implementing aspects of the disclosure. In some embodiments, processor <NUM> is transformed into a special purpose microprocessor by executing computer-executable instructions or by otherwise being programmed. For example, processor <NUM> is programmed with the instructions such as are illustrated below.

<FIG> is a flow chart of a process <NUM> for communicating using the power and digital communication transmission systems <NUM> and the three-phase data transfer system <NUM> shown in <FIG> and <FIG>. In the exemplary embodiment, process <NUM> is performed by at least one of first interface device <NUM>, second interface device <NUM>, master control unit <NUM> (shown in <FIG>), slave unit <NUM> (shown in <FIG>), first device <NUM>, or second device <NUM> (both shown in <FIG>).

In the exemplary embodiment, first device <NUM> executes <NUM> a first virtual machine <NUM> and a second virtual machine <NUM> (both shown in <FIG>). The first virtual machine <NUM> is associated with a first Phase <NUM> of a BPL connection <NUM> (both shown in <FIG>). The second virtual machine <NUM> is associated with a second Phase <NUM> (shown in <FIG>) of the BPL connection <NUM>. In the exemplary embodiment, the first device <NUM> also executes a third virtual machine <NUM> associated with the third Phase <NUM> (both shown in <FIG>).

In the exemplary embodiment, the first device <NUM> receives <NUM> a first plurality of data for transmission via the BPL connection <NUM> from the first virtual machine <NUM>. The first device <NUM> receives <NUM> a second plurality of data for transmission via the BPL connection <NUM> from the second virtual machine <NUM>. In some embodiments, the first device <NUM> receives a third plurality of data for transmission via the BPL connection <NUM> from the third virtual machine <NUM>.

In the exemplary embodiment, the first device <NUM> transmits <NUM> the first plurality of data over the BPL connection <NUM> via a first phase of a power line (such as electrical power conduit <NUM> shown in <FIG>) associated with BPL connection <NUM>. The fist device <NUM> transmits <NUM> the second plurality of data over the BPL connection <NUM> via a second phase of the power line associated with BPL connection <NUM>. In some embodiments, the first device <NUM> transmits the third plurality of data over the BPL connection <NUM> via a third phase of the power line associated with BPL connection <NUM>. In some embodiments, the first device <NUM> transmits the first plurality of data, the second plurality of data, and the third plurality of data, simultaneously.

In some embodiments, the first device <NUM> determines that the first plurality of data is finished transmitting. The first device <NUM> then transmits the remaining second plurality of data via the first phase <NUM> and the second phase <NUM>. In some further embodiments, the first device <NUM> determines that the first plurality of data and the second plurality of data are finished transmitting. The first device <NUM> then transmits the remaining third plurality of data via the first phase <NUM>, the second phase <NUM>, and the third phase <NUM>.

In some embodiments, the first plurality of data is associated with a first priority and the second plurality of data is associated with a second priority. The first priority and the second priority are encoded in the transmissions via the BPL connection <NUM>. In some further embodiments, the third plurality of data is associated with a third priority that is also encoded in its transmissions over the BPL connection <NUM>.

In some embodiments, the first virtual machine <NUM> encrypts the first plurality of data using a first encryption method. The second virtual machine <NUM> encrypts the second plurality of data using a second encryption method. In these embodiments, the second encryption method is different from the first encryption method. In some additional embodiments, the powerline transceiver <NUM> associated with the first device <NUM> is configured to encrypt data to be transmitted using a third encryption method.

The first device <NUM> receives a fourth plurality of data via the powerline transceiver <NUM>. The first device <NUM> determines which virtual machine to route the fourth plurality of data. Then the first device <NUM> routes the fourth plurality of data to the corresponding virtual machine.

<FIG> is a flow chart of an exemplary process <NUM> for managing data traffic over the three-phase data transfer system <NUM> shown in <FIG>. In the exemplary embodiment, process <NUM> is performed by at least one of first interface device <NUM>, second interface device <NUM>, master control unit <NUM> (shown in <FIG>), slave unit <NUM> (shown in <FIG>), first device <NUM>, or second device <NUM> (both shown in <FIG>).

In the exemplary embodiment, process <NUM> begins <NUM> with the system <NUM> transmitting high priority data <NUM> over Phase A <NUM> (shown in <FIG>), transmitting medium priority data <NUM> over Phase B <NUM> (shown in <FIG>), and transmitting low priority data <NUM> over Phase C <NUM> (shown in <FIG>).

The system <NUM> checks to determine whether the high priority data transmission is complete <NUM>. If not, then the system <NUM> continues transmitting high priority data <NUM>. If yes, then the system <NUM> checks if medium priority data is still being transmitted <NUM>. If yes, then the system <NUM> transmits medium data <NUM> over Phases A <NUM> and B <NUM>. If not, then the system <NUM> checks if low priority data is still being transmitted <NUM>. If yes, then the system <NUM> transmits low priority data <NUM> over Phases A <NUM>, B <NUM>, and C <NUM>.

The system <NUM> checks to determine whether the medium priority data transmission is complete <NUM>. If not, then the system <NUM> continues transmitting medium priority data <NUM>. If yes, then the system <NUM> checks if high priority data is still being transmitted <NUM>. If yes, then the system <NUM> transmits high data <NUM> over Phases A <NUM> and B <NUM>. If not, then the system <NUM> checks if low priority data is still being transmitted <NUM>. If yes, then the system <NUM> transmits low priority data <NUM> over Phases A <NUM>, B <NUM>, and C <NUM>.

The system <NUM> checks to determine whether the low priority data transmission is complete <NUM>. If not, then the system <NUM> continues transmitting low priority data <NUM>. If yes, then the system <NUM> checks if high priority data is still being transmitted <NUM>. If yes, then the system <NUM> transmits high data <NUM> over Phases A <NUM> and C <NUM>. If not, then the system <NUM> checks if medium priority data is still being transmitted <NUM>. If yes, then the system <NUM> transmits medium priority data <NUM> over Phases A <NUM>, B <NUM>, and C <NUM>.

The above process <NUM> is an exemplary process for managing data traffic. Other processes may be used in other situations, such as other methods of cauterizing the data being transmitted.

At least one of the technical solutions to the technical problems provided by this system may include: (i) improved security for BPL systems; (ii) improved data transfer speeds for BPL systems; (iii) increased reliability for BPL systems; (iv) allow for secure data transfers to and from vehicles; (v) increased flexibility in data transfer systems; (vi) dynamic bandwidth allocation; and (vi) increased security for aircraft systems.

The methods and systems described herein may be implemented using computer programming or engineering techniques including computer software, firmware, hardware, or any combination or subset thereof. As disclosed above, at least one technical problem with prior systems is that there is a need for systems for a cost-effective and reliable manner for BPL communications. The system and methods described herein address that technical problem. The technical effects may be achieved by performing at least one of the following steps: (a) executing a first virtual machine and a second virtual machine; (b) receiving, via the first virtual machine, a first plurality of data for transmission via the BPL connection; (c) receiving, via the second virtual machine, a second plurality of data for transmission via the BPL connection; (d) transmitting, via the BPL connection, the first plurality of data via a first phase of a power line associated with BPL connection; and (e) transmitting, via the BPL connection, the second plurality of data via a second phase of the power line associated with BPL connection.

Although described with respect to an aircraft broadband power line application, embodiments of the disclosure are also applicable to other vehicles such as ships, barges, and boats moored at a dock or pier and also wheeled vehicles parked in a service area.

The above-described methods and systems for transmitting power and digital communication to provide high speed Internet service support directly to the aircraft while at the gate are cost-effective, secure and highly reliable. The methods and systems include integration and use of BPL or X10 similar technology into the aircraft and airport infrastructure to support broadband Internet and data services to the aircraft with minimal infrastructure impacts and cost. The integration of BPL, X10, or similar technology into the airport and aircraft permit using the existing aircraft gate umbilical to provide the aircraft with high-speed and high reliability Internet and data services from the airport gate. Accordingly, the methods and systems facilitate transmitting power and digital communication in a secure, cost-effective, and reliable manner.

The computer-implemented methods discussed herein may include additional, less, or alternate actions, including those discussed elsewhere herein. The methods may be implemented via one or more local or remote processors, transceivers, servers, and/or sensors (such as processors, transceivers, servers, and/or sensors mounted on vehicles or mobile devices, or associated with smart infrastructure or remote servers), and/or via computer-executable instructions stored on non-transitory computer-readable media or medium. Additionally, the computer systems discussed herein may include additional, less, or alternate functionality, including that discussed elsewhere herein. The computer systems discussed herein may include or be implemented via computer-executable instructions stored on non-transitory computer-readable media or medium.

As used herein, the term "non-transitory computer-readable media" is intended to be representative of any tangible computer-based device implemented in any method or technology for short-term and long-term storage of information, such as, computer-readable instructions, data structures, program modules and sub-modules, or other data in any device. Therefore, the methods described herein may be encoded as executable instructions embodied in a tangible, non-transitory, computer readable medium, including, without limitation, a storage device and/or a memory device. Such instructions, when executed by a processor, cause the processor to perform at least a portion of the methods described herein. Moreover, as used herein, the term "non-transitory computer-readable media" includes all tangible, computer-readable media, including, without limitation, non-transitory computer storage devices, including, without limitation, volatile and nonvolatile media, and removable and non-removable media such as a firmware, physical and virtual storage, CD-ROMs, DVDs, and any other digital source such as a network or the Internet, as well as yet to be developed digital means, with the sole exception being a transitory, propagating signal.

As described above, the described embodiments enable secure vehicle broadband communication with a data network. More particularly, the present disclosure is directed to using broadband over powerline (BPL) communications to enable aircraft information exchange to occur at increased speeds and where conventional data exchange services may not be available. More specifically, a master control unit on the ground and a slave unit on the aircraft set-up a two-way communication channel over one or more powerlines and ensure the security and the integrity of the data being transferred over the powerline. The master control unit also ensures that the data is transmitted to its intended destination via the most efficient wireless network.

Claim 1:
A broadband over powerline, BPL, unit (<NUM>) comprising:
at least one processor (<NUM>) ;
at least one memory device (<NUM>) in communication with the at least one processor (<NUM>); and
a powerline transceiver (<NUM>) in communication with the at least one processor (<NUM>),
wherein the at least one processor (<NUM>) is programmed to transmit and receive data over a power line (<NUM>) via the powerline transceiver (<NUM>), wherein the power line (<NUM>) is a three-phase power line (<NUM>), and wherein the at least one processor (<NUM>) is further programmed to:
execute a first virtual machine (<NUM>), a second virtual machine (<NUM>), and a third virtual machine (<NUM>), wherein the first virtual machine (<NUM>) is associated with a first phase (<NUM>) of the three-phase power line (<NUM>), wherein the second virtual machine (<NUM>) is associated with a second phase (<NUM>) of the three-phase power line (<NUM>), and wherein the third virtual machine (<NUM>) is associated with a third phase (<NUM>) of the three-phase power line (<NUM>);
receive, via the first virtual machine (<NUM>), a first plurality of data for transmission via the powerline transceiver (<NUM>);
receive, via the second virtual machine (<NUM>), a second plurality of data for transmission via the powerline transceiver (<NUM>);
receive, via the third virtual machine (<NUM>), a third plurality of data for transmission via the powerline transceiver (<NUM>);
transmit, via the powerline transceiver (<NUM>), the first plurality of data via a first phase;
transmit, via the powerline transceiver (<NUM>), the second plurality of data via a second phase; and
transmit, via the powerline transceiver (<NUM>), the third plurality of data via a third phase.