Patent Description:
Networks located on-board a vehicle face increasing capacity constraints. As vehicles are designed to transport ever more passengers carrying personal electronic devices, and as the internet of things (IoT) increases the number of connected devices on vehicles, on-board vehicle networks must adapt to be able to accommodate the increased number of connected devices. In addition to the number of devices, the services utilized by passengers (e.g., streaming music, video, VPN) require ever increasing amounts of bandwidth. Accordingly, there is a need to provide dual fidelity connectivity on-board vehicles to alleviate the increasing capacity demands associated with on-board networks.

<CIT> relates to a media distribution system for aircraft comprising a processor, an optical encoder/decoder, and an optical backbone. The processor is configured to retrieve digital media from an in-flight media node. The optical encoder/decoder is configured to optically encode the digital media. The optical backbone is configured to carry the encoded digital media between the optical encoder/decoder and a Li-Fi access point at a passenger seat location.

<NPL>" relates to relates to a novel access point assignment (APA) method for hybrid LiFi and WiFi networks in consideration of LiFi channel blockage. Using the signal strength strategy (SSS) method, which always assigns a user to the AP offering the highest signal-to-noise ratio (SNR), would cause users to be more attracted to WiFi. This could lead to traffic overload in WiFi. The document proposes that users of the hybrid network should be segmented into three categories - (<NUM>) a group that is WiFi only, (<NUM>) a group that is LiFi only, and (<NUM>) a group that can switch between LiFi and WiFi. When a user has a high occurrence rate of channel blockage and if the occupation rate of channel blockage is high, the user is better to be always connected to WiFi, and otherwise it should stay in the LiFi network. For those users having low occurrence rate but high occupation rate, it is worth switching them to WiFi when channel blockage occurs. Users should be assigned to the LiFi network or the WiFi network based on the occurrence rate, the occupation rate, and the blockage degree of LiFi blockage for that user.

In one embodiment, a system for providing dual fidelity communications on-board a vehicle that includes a plurality of seats having corresponding seatback devices installed thereat is provided. The system includes (<NUM>) a radio frequency (RF) router operatively connected to one or more wireless access points distributed throughout the vehicle; and (<NUM>) a light fidelity (LiFi) router operatively connected to a plurality of lights disposed within respective passenger service units. Each of the lights are configured to emit light directed towards a photo-detector located at a seat corresponding to the respective passenger service unit. The system also includes a network controller operatively connected to the RF router and the LiFi router. The network controller is configured to (i) identify data streams associated with devices on-board the vehicle, wherein one or more of the data streams are associated with seatback devices on-board the vehicle; (ii) analyze the identified data streams to determine a metric associated with the one or more data streams; and (iii) based on the metric associated with a particular data stream associated with a particular seatback device, route data packets that form the particular data stream to one of the RF router or the LiFi router for transmission the particular seatback device.

In another embodiment, a dual fidelity access point disposed within a vehicle that includes a plurality of seats having corresponding seatback devices installed thereat is provided. The dual fidelity access points includes (<NUM>) one or more transceivers configured to communicate with the plurality of devices via a radio frequency (RF) communication protocol; and (<NUM>) one or more light emitting diodes (LEDs) configured to emit light in accordance with a light fidelity (LiFi) communication protocol. The emitted light is detected by photo-detectors operatively connected to respective seatback devices. The dual fidelity access point also includes (<NUM>) a bus interface communicatively coupled to a network controller; and (<NUM>) a controller configured to (i) obtain, via the bus interface, data packets addressed to devices within a footprint of the dual fidelity access point; (ii) identify data streams associated with the data packets, wherein one or more of the data streams are associated with seatback devices on-board the vehicle; (iii) analyze the data streams to determine a metric associated with the one or more data streams; and (iv) based on the metric for a particular data stream associated with a particular seatback device, communicate the data packets that form the particular data stream to the particular seatback device via one of the one or more transceivers or the one or more LEDs.

In yet another embodiment, a system for providing dual fidelity communications on-board a vehicle is provided. The system includes (<NUM>) a wired communications interface operatively connected to vehicle control equipment located in a vehicle control deck; and (<NUM>) a light fidelity (LiFi) router operatively connected to one or more of lights disposed within the vehicle control deck. The one or more lights are configured to emit light directed towards a photo-detector operatively connected to the vehicle control equipment. The system also includes (<NUM>) one or more transceivers configured to exchange data with an external base station; and (<NUM>) a network controller operatively connected to the wired communications interface and the LiFi router. The network controller is configured to (i) obtain, via the one or more transceivers, vehicle control data; (ii) routing a first portion of the vehicle control data to the vehicle control equipment via the wired communications interface; and (iii) routing a second portion of the vehicle control data to the vehicle control equipment via the LiFi router.

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

It should be understood that, unless a term is expressly defined in this patent using the sentence "As used herein, the term '____' is hereby defined to mean. " or a similar sentence, there is no intent to limit the meaning of that term, either expressly or by implication, beyond its plain or ordinary meaning, and such term should not be interpreted to be limited in scope based on any statement made in any section of this patent (other than the language of the claims). To the extent that any term recited in the claims at the end of this disclosure is referred to in this disclosure in a manner consistent with a single meaning, that is done for sake of clarity only so as to not confuse the reader, and it is not intended that such claim term be limited, by implication or otherwise, to that single meaning.

Light fidelity (LiFi) communication involves encoding data by using a modulation technique, such as on-off keying (OOK) or color shift keying (CSK), and controlling lights, such as light emitting diodes (LEDs), to emit light indicative of the encoded data in accordance with the modulation technique. The light emitted by the LEDs is detected by a photo-detector and decoded into the underlying data. As one example of LiFi communication, IEEE <NUM>. <NUM> sets forth a LiFi communication standard currently under development. However, other protocols that rely upon encoding light to represent data are also envisioned. LiFi is generally associated with Visual Light Communications (VLC). However, as the name suggests, VLC is generally associated with the visible light spectrum (<NUM> - <NUM>), whereas LiFi may include light in the infrared (IR) spectrum (such as the near infrared spectrum) and ultraviolet (UV) spectrum (such as the UV-B spectrum).

Importantly, the frequency of light associated with LiFi communications does not overlap with the frequencies associated with radio frequency (RF) communications. For example, the near IR band is centered near <NUM> THz and most WiFi communication systems operate at <NUM> or <NUM>. Accordingly, a network operator can co-locate a LiFi communication system and a RF communication system with minimal cross-interference. It should be appreciated that the term "RF communication" refers to any wireless radio frequency communication scheme, including IEEE <NUM>, long term evolution (LTE), new radio (NR), Bluetooth, ZigBee, constrained application protocol (CoAP), Z-Wave, and so on. Accordingly, in embodiments described herein, a LiFi communication system and a RF communication system may be integrated into a dual fidelity communication system on-board a vehicle.

<FIG> depicts an example centralized dual fidelity communication system <NUM> that integrates LiFi communications with passenger service units <NUM> on-board a vehicle. For ease of explanation, the systems described herein are for the most part described herein as being on-board an aircraft. However, the techniques and principles described herein equally apply to other types of vehicles that accommodate multiple passengers, such as buses, trains, boats, ships, subway cars, military transport vehicles, other air-borne, water-borne, or land-borne vehicles, and vehicles that are suitable for space travel.

The centralized dual fidelity communication system <NUM> includes a number of seats <NUM>, one, some, or all of which carry a respective seatback device <NUM>. Seatback devices <NUM> may be in-flight entertainment devices that enable passengers to watch movies and/or television programming (e.g., via IPTV), for example. Alternatively, or in addition, seatback devices <NUM> may enable passengers to access various other services, such as Internet browsing, placing drink and/or food orders, and/or ordering "duty-free" items. As seen in <FIG>, each of seatback devices <NUM> are positioned on a back surface of one of seats <NUM>. For example, seatback device <NUM>-<NUM> is affixed to the back of seat <NUM>-<NUM>. The seatback devices <NUM> may be physically coupled to a mounting unit affixed to seats <NUM> via screws, clips, and/or other suitable types of hardware.

In an alternative embodiment, seatback devices <NUM> may instead be positioned in a manner different than that shown in <FIG>. For example, seatback device <NUM>-<NUM> may instead be affixed to an armrest of seat <NUM>-<NUM> (e.g., via an extendable and/or rotatable arm that can be positioned by a passenger sitting in seat <NUM>-<NUM>).

Above each of the seats <NUM>, the centralized dual fidelity communication system <NUM> includes a passenger service unit (PSU) <NUM> that includes various interfaces (e.g., a service call button, a seatbelt indicator, a reading light, a reading light toggle button, a standby light) with which a passenger sitting at a seat <NUM> may interact. For example, the reading light in the PSU <NUM>-<NUM> above seat <NUM>-<NUM> may be arranged to provide an illumination light to the passenger sitting in the seat <NUM>-<NUM>. As described herein, the PSU <NUM> may be configured to support LiFi communications via the reading light. In one embodiment, the reading light include two LEDs, one LED for communicating light in the visible spectrum when the passenger has enabled the reading light and one LED for communicating light outside of the visible spectrum when the passenger has disabled the reading light. In these embodiments, when the reading light is enabled, both LEDs may be configured to communicate data simultaneously. In other embodiments, the PSU <NUM> includes one or more LEDs, separate from the reading light, dedicated to performing LiFi communications.

Regardless of the particular arrangement of the LEDs that are configured to provide LiFi communications within the PSU <NUM>, the seats <NUM> also include a respective photo-detector <NUM> operatively connected to the seatback device <NUM>. The photo-detector <NUM> may be arranged on top of a head portion the seat <NUM>, on top of the seatback device <NUM>, on top of a mount in which the seatback device <NUM> rests, on a substrate disposed between the respective head portions of two adjacent seats <NUM>, or any other location within a line of sight from the LED. In an alternative embodiment, the photo-detector <NUM>-<NUM> may be located in an arm rest portion of the seat <NUM>-<NUM> to detected LiFi communications from an LED at the PSU <NUM>-<NUM>. To reduce spectral interference, the PSU <NUM> may be arranged to communicate with adjacent seatback devices <NUM>-<NUM> (e.g., another seat in the same row as the seat <NUM>-<NUM>) using different spectrums of light.

The LEDs included in the PSUs <NUM> are communicatively coupled to a LiFi router <NUM>. In one embodiment, the LiFi router <NUM> is coupled to the PSUs <NUM> via an optical connection, such as a power over Ethernet (PoE) connection. In these embodiments, the LiFi router <NUM> may be arranged to generate the optical signals communicated by the PSUs <NUM>. In other embodiments, the LiFi router <NUM> is coupled to the PSUs <NUM> via a copper connection. In these embodiments, the PSUs <NUM> may include a converter configured to sense control signals from the LiFi router <NUM> and produce encoded optical signals to be communicated via the LEDs of the PSU <NUM>.

In some embodiments, the centralized dual fidelity communication system <NUM> supports a reverse LiFi communications link. In these embodiments, the seatback devices <NUM> are operatively connected to one or more LEDs configured to emit light that is sensed at a photo-detector operatively connected to the PSUs <NUM>. It should be appreciated that the optical components that support forward link communications may be disposed in different locations associated with the seats <NUM> and/or the PSUs <NUM> than the optical components that support reverse link communications. For example, the photo-detector <NUM>-<NUM> that detects light from the PSU <NUM>-<NUM> may be located on the top of the seat <NUM>-<NUM>; whereas the LED operatively connected to the seatback device <NUM>-<NUM> may be disposed in the armrest of the seat <NUM>-<NUM>. The PSUs <NUM> may be configured to route the optical signals sensed by the photo-detector of the PSU <NUM> to the LiFi router <NUM> for processing.

The centralized dual fidelity communication system <NUM> also includes a number of wireless access points <NUM>, which are communicatively coupled (e.g., via a wired connection) to a RF router <NUM>. While <FIG> shows two wireless access points 110A and 110B, more or fewer may be included on-board the vehicle. Wireless access points <NUM> operate according to one or more wireless communication protocols to provide RF communications to devices, such as the seatbacks devices <NUM>, located within the cabin of the vehicle.

Each of the seatback devices <NUM> includes a controller <NUM>, a display <NUM>, an RF interface <NUM>, a LiFi interface <NUM>, and a program storage <NUM>. Controller <NUM> may be a single processor device (e.g., chip) or may include multiple processor devices, and generally controls the operation of the respective seatback device <NUM> by executing instructions stored in the program storage <NUM>. The display <NUM> includes a screen and associated hardware (and possibly firmware, etc.) for presenting visual content to a passenger, and may utilize any suitable display technology. For example, the display <NUM> may be an LED display, OLED display, LCD display, and so on. The RF interface <NUM> includes hardware, firmware, and/or software that enables the respective seatback devices <NUM> to communicate (transmit and receive data) via one or more of wireless access points <NUM> using the appropriate wireless protocols. Similarly, the LiFi interface <NUM> includes hardware, firmware, and/or software that enables the respective seatback devices <NUM> to communicate (transmit and receive data) via a LiFi communication link supported by the respective photo-detectors <NUM> and, in some embodiments, a reverse LiFi link LED.

The program storage <NUM> includes one or more types of non-volatile memory (e.g., a hard disk, solid state memory, etc.), and stores one or more passenger applications <NUM> and a connectivity application <NUM>. The passenger applications <NUM> are generally configured to facilitate the provision of content and/or services via the respective seatback device <NUM>. For example, the passenger applications <NUM> may include a browser application configured to provide Internet browsing capabilities, an in-transit entertainment application configured to display movies or other programming, and/or a mapping application configured to provide route information to the passenger. The connectivity application <NUM> may be configured to control whether data generated by the passenger apps <NUM> is routed to the network controller via the RF interface <NUM> or the LiFi interface <NUM>. For example, the connectivity application <NUM> may detected that the photo-detector <NUM> or the reverse LiFi link LED is blocked and transmit an indication to the network controller <NUM>. Accordingly, the connectivity application <NUM> enables the seatback device <NUM> to utilize the LiFi interface <NUM> to receive forward communications and the RF interface <NUM> to transmit reverse communications, or vice versa.

In the implementation shown in <FIG>, a network controller <NUM> (e.g., an Airborne Control Processor Unit (ACPU)) is coupled to the RF router <NUM> and the LiFi router <NUM>. While <FIG> depicts the RF router <NUM> and the LiFi router <NUM> as being external to the network controller <NUM>, in some embodiments, at least one of the RF router <NUM> and the LiFi router <NUM> are a component of the network controller <NUM>. The network controller <NUM> is also coupled to an external modem <NUM>, which is in turn coupled to an antenna <NUM>. The modem <NUM> and the antenna <NUM> may generally be configured to enable the network controller <NUM> to communicate with systems/nodes/devices that are not located on the vehicle, e.g., via one or more satellite and/or air-to-ground long-range communication links. In some implementations, the centralized dual fidelity communication system <NUM> includes more than one external modem <NUM> and/or more than one antenna <NUM>. In still other implementations (e.g., where no off-vehicle connectivity is required), the external modem <NUM> and the antenna <NUM> are not included in the centralized dual fidelity communication system <NUM>.

The network controller <NUM> may include one or more computing devices, and may generally manage various communication-related (and possibly other) operations. If the seatback devices <NUM> are configured to provide Internet browsing capabilities, real-time programming, and/or other services requiring access to remote content, for example, the network controller <NUM> may receive passenger selections (made at setback devices <NUM>) via wireless access points <NUM> or a photo-detector of the PSUs <NUM>, retrieve the corresponding content from a ground source via modem <NUM> and antenna <NUM>, and provide the retrieved content to seat-back passenger units <NUM> via wireless access points <NUM>. As another example, if the seatback devices <NUM> are also (or instead) configured to vehicle-based services, such as passenger orders (e.g., for food and/or drinks), in-transit entertainment, vehicle-localized messaging and/or gaming, the network controller <NUM> may receive passenger selections (made at the seatback devices <NUM>) via wireless access points <NUM> or a photo-detector of the PSUs <NUM>, and route the data packets to a media server <NUM> associated with the vehicle-based service.

The network controller <NUM> may generally be configured to route data packets addressed to devices, including the seatback devices <NUM>, located within the cabin of the vehicle. For example, the data packets may be received from the external modem <NUM> and/or the media servers <NUM>. The network controller <NUM> may analyze network conditions associated with the RF network and/or the LiFi network to determine whether to route the data packet to the RF router <NUM> or the LiFi router <NUM>. Additionally or alternatively, the network controller <NUM> may analyze one or more characteristics associated with the data packet addressed to the seatback device <NUM> to determine whether to route the data packet to the RF router <NUM> or the LiFi router <NUM>. Prior to routing the data packet to the RF router <NUM> or the LiFi router <NUM>, the network controller <NUM> may associate the data packet with an indicator identifying a particular seatback device <NUM> to which the data packet should be delivered. Accordingly, when the RF router <NUM> or the LiFi router <NUM> receives the data packet, the RF router <NUM> or the LiFi router <NUM> respectively routes the data packet to the wireless access point <NUM> or PSU <NUM> communicatively coupled to the identified seatback device <NUM> for transmissions to the identified seatback device <NUM>.

<FIG> depicts an example distributed dual fidelity communication system <NUM> that integrates LiFi communications and RF communications at one or more dual fidelity access points <NUM> disposed throughout the vehicle. While LiFi communications have been described by some as a point-to-point communication protocol, the light emitted by LEDs actually reflects off surfaces in the environment. This is particularly true in smaller environments that have light-colored and/or reflective surfaces, such as a vehicle cabin. Accordingly, even if an LED is not directed at a particular photo-detector <NUM> associated with a particular seatback device <NUM>, the particular photo-detector <NUM> may still detect the encoded light produced by the LED. Thus, similarly to the wireless access points <NUM> providing RF communications to a plurality of devices within the vehicle cabin, a centralized light access point is able to provide LiFi communications to a plurality of LiFi-compatible devices within the vehicle cabin.

As illustrated in <FIG>, the distributed dual fidelity communication system <NUM> includes one or more dual-fidelity access points <NUM> disposed throughout the vehicle cabin and configured to provide both RF communications and LiFi communications to devices therein. While <FIG> shows two dual-fidelity access points 160A and 160B, more or fewer may be included on-board the vehicle. Each dual-fidelity access point <NUM> include a controller <NUM>, a bus interface <NUM>, an RF interface <NUM>, and a LiFi interface <NUM>. The controller <NUM> may be a single processor device (e.g., chip) or may include multiple processor devices, and generally controls the operation of dual-fidelity access point <NUM> by executing instructions stored in a memory thereat. The RF interface <NUM> includes hardware, firmware, and/or software that enables the dual-fidelity access point <NUM> to communicate (transmit and receive data) using the appropriate wireless protocols. To this end, the RF interface <NUM> may operate in a similar manner as the wireless access point <NUM> of <FIG>.

The LiFi interface <NUM> includes hardware, firmware, and/or software that enables the dual-fidelity access point <NUM> to communicate (transmit and receive data) via a LiFi communication link supported by the photo-detectors <NUM> and, in some embodiments, reverse LiFi link LEDs. The LiFi interface <NUM> may be configured to establish simultaneous communications with several of the seatback devices <NUM>. Accordingly, the LiFi interface may include multiple LEDs configured to emit light using different portions of the light spectrum. For example, orthogonal frequency division multiplexing (OFDM) techniques that are used to avoid cross-channel interference in LTE networks can be implemented by the LiFi interface <NUM> to avoid spectral interference. To this end, the LiFi interface <NUM> may be configured to transmit composite light signals that carry a plurality of light-encoded data packets at different light spectrums. For example, a single LED may include a signal for the seatback device <NUM>-<NUM> within the red spectrum, a signal for the seatback device <NUM>-<NUM> within the green spectrum, and a signal for the seatback device <NUM>-<NUM> within the blue spectrum. In this example, the composite light may appear white to the passengers; however a tunable light filter included in the LiFi interface <NUM> of the seatback devices <NUM> may be configured to extract, from the light detected by the photo-detector <NUM>, the portion of the light at the particular spectrum associated with the communications between the seatback device <NUM> and the dual-fidelity access point <NUM>.

The bus interface <NUM> is configured to exchange data with the network controller <NUM> via a communication bus therebetween. For example, the communication bus may be an Ethernet connection, a PoE connection, a power line communication (PLC) connection, or any other known arrangement for connecting vehicle access points to a centralized network controller. In some embodiments, the bus interface <NUM> includes a first interface for receiving data packets to be routed over the RF interface <NUM> and a second interface for receiving data packets to be routed over the LiFi interface <NUM>. The controller <NUM> may be configured to analyze data received over the bus interface <NUM> to determine whether to route the data packets over the RF interface <NUM> or the LiFi interface <NUM>. In some embodiments, the controller <NUM> determines the particular interface of the bus interface <NUM> via which the data packet was received and/or identifies a flag appended to the data packet by the network controller <NUM> to determine which of the RF interface <NUM> or the LiFi interface <NUM> to route the data packet. Additionally or alternatively, the controller <NUM> may analyze one or more characteristics of the data packet and/or network conditions associated with the RF network and/or the LiFi network to determine which of the RF interface <NUM> or the LiFi interface <NUM> to route the data packet.

Similar to the centralized dual fidelity communication system <NUM>, the network controller <NUM> obtains data packets addressed to devices within the vehicle cabin from one of the media servers <NUM> or from an external model <NUM> that supports off-vehicle communications via the antenna <NUM>. In some embodiments, the network controller <NUM> determines whether the data packets should be routed over an RF interface <NUM> or a LiFi interface <NUM> of a dual-fidelity access point <NUM>. In these embodiments, the network controller <NUM> may be configured to append a flag indicative of the determined interface and/or route the data packet over a particular bus connected to the dual-fidelity access point <NUM>. In other embodiments, the network controller <NUM> identifies which of the dual-fidelity access points <NUM> the data packet should be routed (e.g., based on a location of the device to which the data is addressed), which in turn determines which of the RF interface <NUM> or the LiFi interface <NUM> to route the data. The seatback devices <NUM> in the distributed dual fidelity communication system <NUM> may be configured in the same manner as described with respect to the centralized dual fidelity communication system <NUM>.

<FIG> illustrates an example environment <NUM> in which the centralized dual fidelity communication system <NUM> includes seatback devices <NUM> configured in a master-slave arrangement. It should be appreciated that the configuration of seatback devices <NUM> may also be implemented in the distributed dual fidelity communication system <NUM>. In the environment <NUM>, rather than each seatback device <NUM> being operatively coupled to a respective photo-detector <NUM>, a single photo-detector <NUM> is utilized to sense light-encoded data packets addressed to any of the seatback devices <NUM> located in a seating unit (such as the seating unit comprised of the seat <NUM>-<NUM>, the seat <NUM>-<NUM>, and the seat <NUM>-<NUM>).

Accordingly, the network controller <NUM> may be configured to route data packets addressed to any of the seatback devices <NUM>-<NUM>, <NUM>-<NUM>, or <NUM>-<NUM> to the PSU <NUM>, which utilizes an LED of a LiFi interface to emit light directed at the photo-detector <NUM>. In alternate embodiments, the network controller <NUM> may be configured to route data packets addressed to any of the seatback devices <NUM>-<NUM>, <NUM>-<NUM>, or <NUM>-<NUM> to the dual fidelity access point <NUM> associated with a network footprint that includes the photo-detector <NUM>. In the environment <NUM>, the photo-detector <NUM> is disposed on a substrate located between the head portions of the seats <NUM>-<NUM> and <NUM>-<NUM>; however, in alternate embodiments, the photo-detector <NUM> may be disposed in any location associated with the seat unit where the photo-detector <NUM> is able to sense light emitted from the PSU <NUM>.

As illustrated, the seatback device <NUM>-<NUM> is communicatively coupled to the seatback devices <NUM>-<NUM> and <NUM>-<NUM> via respective slave interfaces <NUM>. The slave interface <NUM> may be any wired or wireless communications interface. For example, the slave interface <NUM> may be a wired connection between the master and slave seatback devices. As another example, the slave interface may be a Bluetooth or ZigBee connection between the master and slave seatback devices. The connectivity application <NUM> of the seatback device <NUM>-<NUM> may be configured to store a network address associated with the seatback devices <NUM>-<NUM> and <NUM>-<NUM> and an indication of the particular slave interface <NUM> via which the seatback devices <NUM>-<NUM> and <NUM>-<NUM> are communicatively coupled to the seatback device <NUM>-<NUM>.

The connectivity application <NUM> of the seatback device <NUM>-<NUM> may be configured to analyze any data packets detected by the photo-detector <NUM> to determine which of the seatback devices <NUM>-<NUM>, <NUM>-<NUM>, or <NUM>-<NUM> to which the data packet is addressed. For example, the address of the destination seatback device <NUM> may be included in the header of the data packet. Accordingly, the connectivity application <NUM> may be configured to compare the address from the data packet to the addresses associated with the slave seatback devices <NUM>-<NUM> and <NUM>-<NUM>, as well as its own address. If the address indicated by the data packet matches an address associated with a slave seatback device, the connectivity application <NUM> routes the data packet over the corresponding slave interface <NUM>.

Similarly, the connectivity application <NUM> may be configured to obtain data packets generated by the seatback devices <NUM>-<NUM> and <NUM>-<NUM> via the respective slave interfaces <NUM>. In some embodiments, the connectivity application <NUM> may package the data packets generated at the seatback device <NUM>-<NUM> with any data packets obtained via the slave interfaces <NUM> into a composite data packet that is unpackaged at the network controller <NUM> for individual processing. Additionally or alternatively, the connectivity application <NUM> may route data packets associated with a first one of the seatback devices <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM> over the RF interface <NUM> data packets associated with a second one of the seatback devices <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM> over the LiFi interface <NUM>.

<FIG> depicts an example method <NUM> for providing dual fidelity communications on-board a vehicle (e.g., an aircraft, bus, train, subway, military transport vehicle, space craft, etc.). More particularly, the method <NUM> relates to routing data over one of a RF network or a LiFi network that provide network connectivity within the vehicle. The method <NUM> may be implemented by a network controller, such as the network controller <NUM> of any one of <FIG>, <FIG>, and <FIG>, for example. Various components of <FIG>, <FIG>, and <FIG> are referred to in the description of the method <NUM> for purposes of providing specific, non-limiting examples.

The method <NUM> begins when the network controller identifies data streams associated with devices on-board the vehicle (block <NUM>). The identified data streams may include data packets exchanged between a seatback device (e.g., the seatback devices <NUM>) and a media server associated with in-vehicle services (e.g., the media servers <NUM>) or an external content provider. Accordingly, the network controller may be configured to obtain a plurality of data packets from the media servers and/or an external modem (e.g., the external modem <NUM>) that supports communications with external content providers. The network controller may then analyze the obtained data packets to identify a particular stream of data associated with each data packet.

As an example, many types of communications include a session identifier that identifies data exchanged by a particular application executing on a device and the corresponding content server. In some scenarios, the same seatback device may concurrently support multiple communication sessions with different content servers. The session identifier are typically included in a header of the composite data packets. Accordingly, the network controller may be configured to identify the data stream based on analyzing the session identifier included in a data packet header. For some types of communications, the underlying data is obscured from analysis by the network controller, such as encrypted communication services or a virtual private network (VPN) service. For these types of communication, the network controller may identify the data stream based upon the origination and/or destination addresses included in the data packet.

At block <NUM>, the network controller analyzes the identified data streams to determine a metric associated with the data streams that include a seatback device as an endpoint. The metric may be indicative of an amount of data required to transmit the data stream or minimum performance level for the service supported by the data stream. The metric is indicative of an amount of bandwidth required to transmit the data packets that form the particular data stream and/or all of the identified data streams and/or is indicative of a particular application executing on the seatback device that is transmitting or receiving the data packets.

In some embodiments, the LiFi network is utilized to provide communications to devices located in nulls or "dead zones" associated with the RF network. In these embodiments, the metric may additionally or alternatively be indicative of a connection quality between the seatback device associated with the data packet and the RF access point. Accordingly, the metric may be based on at least one of signal strength, signal to noise ratio, carrier to noise ratio, receive power, transmit power, packet loss rate, and/or round trip time.

At block <NUM>, based on the determined metric, the network controller routes the data packets associated with data streams to one of an LTE router (e.g., the LTE router <NUM>) or a LiFi router (e.g., the LiFi router <NUM>) for transmission to the addressed seatback device. For example, in some implementations, the LiFi network may be less reliable than the RF network. Accordingly, if the metric indicates the data stream is bandwidth intensive (e.g., by determining the metric is above a threshold bandwidth) and/or associated with a streaming media application (e.g., video on demand, satellite TV, video conferencing), the network controller may route the data packets that form the data stream to the RF router. Conversely, if the metric indicates the data stream is not bandwidth intensive (e.g., by determining the metric is below a threshold bandwidth) and/or not associated with a streaming media application, the network controller may route the data packets that form the data stream to the LiFi router.

Similarly, in some implementations, the LiFi network serves as a offloading network for when the RF network is overloaded. Accordingly, if the network controller determines that a metric indicative of an aggregate amount of bandwidth required to transmit each of the identified data streams exceeds a threshold bandwidth, the network controller may then route the data packets that form the particular individual data streams to the LiFi router. For example, the network controller may select the particular individual data streams based on the data stream requiring bandwidth below the bandwidth threshold and/or not being associated with a streaming media application.

In implementations where the LiFi network is used to mitigate nulls or "dead zones" associated with the RF network, the network controller may identify data streams associated with a seatback device having a connection quality metric below a threshold connection quality. Accordingly, the network controller may be configured to route the data packets that form the identified data streams to the LiFi router.

It should be appreciated that the network controller and/or connectivity applications (e.g., the connectivity application <NUM>) at the seatback devices may be configured to support hybrid fidelity communications. For example, in embodiments configured with a LiFi reverse link, the network controller may route forward data packets for a data stream to the RF router for transmission to the seatback device and receive reverse data packets for the data stream from the seatback device via the LiFi router, and vice versa.

In some embodiments, when the network controller routes the data packets to the LiFi router, the network controller is also configured to indicate which spectrum of light should be utilized to encode the data packet. For example, if the network controller is routing data packets associated with two seatback devices located proximate to one another (e.g., located in the same seat unit or in an adjacent row), the network controller may indicate that data packets that form the data streams to the proximate seatback devices should be encoded using two different, non-overlapping light spectra. As another example, the network controller may be configured to receive indications of whether or not a reading light associated with the same seat as the seatback device associated with the data stream is enabled. If the network controller determines that the reading light is enabled, the network controller may indicate that the data packet should be encoded using light within the visible light spectrum. Conversely, if the network controller determines that the reading light is disabled, the network controller may indicate that the data packet should be encoded using light within the infrared or ultraviolet light spectra. Accordingly, when the LiFi router and/or a PSU associated with the addressed seatback receives the data packet, the LiFi router and/or the PSU may be configured to encode the data packet using the spectrum of light indicated by the network controller.

While the foregoing description describes implementing the method <NUM> at the centralized dual fidelity communication system <NUM> and/or <NUM> of <FIG> and <FIG>, respectively, the method <NUM> may be adapted for implementation at the distributed dual fidelity communication system <NUM> of <FIG>. To this end, rather than routing the data packets to one of the RF router <NUM> or the LiFi router <NUM>, the network controller <NUM> may route the data packets over a particular bus interface between the dual-fidelity access point <NUM> and/or modify the data packets to include an indication of whether the dual-fidelity access point <NUM> should route the data packet over the RF interface <NUM> or the LiFi interface <NUM> prior to routing the data packets to the dual-fidelity access point <NUM>.

<FIG> depicts an example method <NUM> for providing dual fidelity communications on-board a vehicle (e.g., an aircraft, bus, train, subway, military transport vehicle, space craft, etc.). More particularly, the method <NUM> relates to routing data over one of a RF network via one or more transceivers or a LiFi network via one or more LEDs. The method <NUM> may be implemented by a dual-fidelity access point, such as the dual fidelity access point <NUM> of <FIG>, for example. Various components of <FIG>, <FIG>, and <FIG> are referred to in the description of the method <NUM> for purposes of providing specific, non-limiting examples.

The method <NUM> begins when the dual fidelity access point obtains, via a bus interface, data packets address to devices within a footprint of the dual fidelity access point (block <NUM>). The bus interface may be configured to communicative couple the dual fidelity access point and a network controller (e.g., the network controller <NUM>). For example, the bus interface may be a PoE interface.

At block <NUM>, the dual fidelity access point identifies data streams associated with the data packets. The data streams may include data streams associated with one or more seatback devices (e.g., the seatback devices <NUM>). The dual fidelity access point may then analyze the obtained data packets to identify a particular stream of data associated with each data packet. For example, the dual fidelity access point may be configured to identify the data stream based on analyzing the session identifier included in a data packet header and/or the origination and/or destination addresses included in the data packet.

At block <NUM>, the dual fidelity access point analyzes the identified data streams to determine a metric associated with the data streams. The metric may be indicative of an amount of data required to transmit the data stream or minimum performance level for the service supported by the data stream. The metric is indicative an amount of bandwidth required to transmit the data packets that form the particular data stream and/or all of the identified data streams and/or is indicative of a particular application executing on the seatback device that is transmitting or receiving the data packets.

In some embodiments, the LiFi network is utilized to provide communications to devices located in nulls or "dead zones" associated with the RF network. In these embodiments, the metric may additionally or alternatively be indicative of a connectional quality between the seatback device associated with the data packet and the one or more transceivers of the dual fidelity access point. Accordingly, the metric may be based on at least one of signal strength, signal to noise ratio, carrier to noise ratio, receive power, transmit power, packet loss rate, and/or round trip time.

At block <NUM>, based on the determined metric, the dual fidelity access point communicates the data packets that form the data streams to the destination seatback device via one or more transceivers of an RF interface (e.g., the RF interface <NUM>) or one or more LEDs of a LiFi interface (e.g., the LiFi interface <NUM>) for transmission to the addressed seatback device. For example, in some implementations, the LiFi network may be less reliable than the RF network. Accordingly, if the metric indicates the data stream is bandwidth intensive (e.g., by determining the metric is above a threshold bandwidth) and/or associated with a streaming media application (e.g., video on demand, satellite TV, video conferencing), the dual fidelity access point may communicate the data packets that form the data stream via the one or more transceivers. Conversely, if the metric indicates the data stream is not bandwidth intensive (e.g., by determining the metric is below a threshold bandwidth) and/or not associated with a streaming media application, the network controller may communicate the data packets that form the data stream via the one or more LEDs.

Similarly, in some implementations, the LiFi network serves as an offloading network for when the RF network is overloaded. Accordingly, if the dual fidelity access point determines that a metric indicative of an aggregate amount of bandwidth required to transmit each of the identified data streams exceeds a threshold bandwidth, the dual fidelity access point may then communicate the data packets that form the particular individual data streams via the one or more LEDs. For example, the dual fidelity access point may select the particular individual data streams based on the data stream requiring bandwidth below the bandwidth threshold and/or not being associated with a streaming media application.

In implementations where the LiFi network is used to mitigate nulls or "dead zones" associated with the RF network, the dual fidelity access point may identify data streams associated with a seatback device having a connection quality metric below a threshold connection quality. Accordingly, the dual fidelity access point may be configured to communicate the data packets that form the identified data streams via the one or more LEDs.

It should be appreciated that the network controller and/or connectivity applications (e.g., the connectivity application <NUM>) at the seatback devices may be configured support hybrid fidelity communications. For example, the dual fidelity access point may communicate forward data packets for a data stream via the one or more LEDs and receive reverse data packets for the data stream via the one or more transceivers. Similarly, in embodiments configured with a LiFi reverse link, the dual fidelity access point may communicate forward data packets for a data stream via the one or more transceivers and receive reverse data packets for the data stream via one or more photo-detectors. In some embodiments, if the dual fidelity access point is communicating data packets via the one or more LEDS to two seatback devices located proximate to one another (e.g., located in the same seat unit or in an adjacent row), the dual fidelity access point may encode using two different, non-overlapping light spectra. In some embodiments, two different LEDs are utilized to emit the light at the non-overlapping spectra. In other embodiments, a single LED is configured to emit a composite light signal that includes both non-overlapping spectra.

Turning now to <FIG>, illustrated is an example dual-fidelity communication system <NUM> for providing communications to a vehicle flight deck. Generally, vehicle flight decks include RF sensitive equipment. Accordingly, RF communications may be prohibited within the vehicle flight deck to prevent interference with the RF sensitive equipment. However, LiFi communications do not generally cause RF interference. Thus, a LiFi communication system may be permitted to operate in vehicle flight decks where RF communication systems are prohibited. It should be appreciated that the dual-fidelity communication system <NUM> may be implemented in the same vehicle that implements one of the centralized dual fidelity communication system <NUM> of <FIG> and/or the distributed dual fidelity communication system <NUM> of <FIG>. Accordingly, the components described with respect to the dual-fidelity communication system <NUM> may additionally be configured to perform any action performed by the component as described with respect to <FIG>.

The dual-fidelity communication system <NUM> is configured to provide both wired communications and LiFi communications to the vehicle control equipment <NUM> located in the vehicle control deck. In the dual-fidelity communication system <NUM>, the network controller <NUM> is configured to support vehicle control communications with an external control system. For example, the vehicle control communications may be based on the ACARS communication protocol and/or other communication protocols that support communication of vehicle operation data (such as LTE or satellite protocols). The network controller <NUM> is configured to obtain the vehicle operation data via one or more external modems <NUM> that is configured to transmit and/or receive data via the antenna <NUM>.

To isolate the vehicle control equipment <NUM> from sources of RF interference, the vehicle control equipment <NUM> is connected to the network controller <NUM> via a wired communication interface (such as an Ethernet or a secure bus interface). In addition to the traditional wired connection to the network controller <NUM>, the vehicle control equipment <NUM> is communicatively coupled to one or more photo-detectors <NUM>. For example, the vehicle control equipment <NUM> may be communicatively coupled to a photo-detector <NUM>-<NUM> built or retrofitted into the vehicle control equipment <NUM> or attached via a communication port (e.g., via dongle inserted into a USB port), to the vehicle control equipment <NUM>. Additionally or alternatively, the vehicle control equipment <NUM> may be communicatively coupled to a photo-detector <NUM>-<NUM> disposed in a seat located in the vehicle control deck (e.g., in a manner similar to how the photo-detector <NUM>-<NUM> is disposed at the seat <NUM>-<NUM>). Accordingly, the vehicle control equipment <NUM> is configured to receive vehicle control data via the traditional wired interface and/or via the photo-detector <NUM>.

As illustrated, the network control <NUM> is communicatively coupled to the LiFi router <NUM> which is configured to provide LiFi communications to devices located on board the vehicle, including in the vehicle control deck. When the network controller <NUM> routes vehicle control data to the LiFi router <NUM>, the LiFi router <NUM> may be configured to encode the vehicle control data using a particular spectrum of light. The LiFi router <NUM> may then route the encoded light to one or more LEDs <NUM> located in the vehicle control deck for transmission to the vehicle control equipment <NUM> via the photo-detector <NUM>. In some embodiments, a reverse link for vehicle control data is provided via one or more LEDs communicatively coupled to the vehicle control equipment <NUM> and a photo-detector located in the vehicle control deck that is communicatively coupled to the LiFi router <NUM>.

<FIG> depicts an example method <NUM> for providing dual fidelity communications on-board a vehicle (e.g., an aircraft, bus, train, subway, military transport vehicle, space craft, etc.). More particularly, the method <NUM> relates to routing vehicle control data to vehicle control equipment (e.g., the vehicle control equipment <NUM>) over one of a traditional wired interface or a LiFi network via one or more LEDs (e.g., the LEDs <NUM>). The method <NUM> may be implemented by a network controller, such as the network controller <NUM> of <FIG>, <FIG>, <FIG>, or <FIG> for example. Various components of <FIG>, <FIG>, <FIG>, and <FIG> are referred to in the description of the method <NUM> for purposes of providing specific, non-limiting examples.

The method <NUM> begins when the network controller obtains, via one or more external modems, vehicle control data addressed to vehicle control equipment located in the vehicle control deck (block <NUM>). In response the receiving the vehicle control data, the network controller may be configured to segment the vehicle control data into a first portion to be routed over the traditional wired interface and a second portion to be routed via a LiFi router (e.g., the LiFi router <NUM>). For example, the network controller may determine that the bandwidth required to transmit the vehicle control data to the vehicle control equipment exceeds a threshold bandwidth. Accordingly, the network controller may identify a set of data packets that, if offloaded to a secondary network, would reduce the bandwidth required to transmit the remaining data packets below the threshold bandwidth. In this example, the network controller may be configured to include the remaining data packets in the first portion of the vehicle control data and the offloaded set of data packets in the second portion of the vehicle control data.

As another example, the network controller may segment the vehicle control data based on the particular item of vehicle control equipment the vehicle control data is associated with and/or the particular type of data indicated by the vehicle control data. For example, voice communications to and from a vehicle operator may be routed over the traditional wired interface and positioning and/or heading data may be routed via the LiFi router. In this example, the data packets that form the voice communications are included in the first portion of the vehicle control data and the data packets that indicate the positioning and/or heading data are included in the second portion of the vehicle control data. In this example, by offloading the non-voice data to the LiFi network, a higher quality voice connection between a vehicle operator and an external vehicle control center may be established.

After the network controller has segmented the vehicle control data, the network controller is configured to route the first portion of the vehicle control data over the traditional wired connection (block <NUM>) and the second portion of the vehicle control data to the LiFi router (block <NUM>). In embodiments that include a reverse LiFi link in the vehicle control deck, the network controller may also be configured to obtain internally-generated vehicle control data via the traditional wired interface and the LiFi router. In these embodiments, the network controller may be configured to aggregate the internally-generated vehicle control data into a single data stream between the network controller and an external vehicle control center. Accordingly, in these embodiments, the network controller may route the internally-generated vehicle control data to one or more external modems (e.g., the external modem <NUM>) for transmission to the external vehicle control center.

<FIG> is a block diagram of an example network controller <NUM> that may be utilized in a system for providing dual fidelity communications to seatback devices within a passenger vehicle. The network controller <NUM> may include, for example, one more processors <NUM>, and one or more buses or hubs <NUM> that connect the processor(s) <NUM> to other elements of the network controller <NUM>, such as a volatile memory <NUM>, a non-volatile memory <NUM>, a display controller <NUM>, and an I/O controller <NUM>. The volatile memory <NUM> and the non-volatile memory <NUM> may each include one or more non-transitory, tangible computer readable storage media such as random access memory (RAM), read only memory (ROM), FLASH memory, a biological memory, a hard disk drive, solid state memory, a digital versatile disk (DVD) disk drive, etc..

In an embodiment, the volatile memory <NUM> and/or the non-volatile memory <NUM> may store instructions <NUM> that are executable by the processor(s) <NUM>. For example, the instructions <NUM> may instruct the network controller <NUM> to perform the methods <NUM> or <NUM>, as described above. Each of the modules, applications and engines described herein can correspond to a different set of machine readable instructions for performing one or more functions described above. These modules need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules can be combined or otherwise re-arranged in various embodiments. In some embodiments, at least one of the memories <NUM>, <NUM> stores a subset of the modules and data structures identified herein. In other embodiments, at least one of the memories <NUM>, <NUM> stores additional modules and data structures not described herein.

In an embodiment, display controller <NUM> may communicate with processor (s) <NUM> to cause information to be presented on a connected display device <NUM>. In an embodiment, the I/O controller <NUM> may communicate with the processor(s) <NUM> to transfer information and commands to/from a user interface <NUM>, which may include a mouse, a keyboard or key pad, a touch pad, click wheel, lights, a speaker, a microphone, etc. In an embodiment, at least portions of the display device <NUM> and of the user interface <NUM> are combined in a single, integral device, e.g., a touch screen. Additionally, data or information may be transferred to and from the network controller <NUM> via network interface <NUM>. In some embodiments, the network controller <NUM> may include an RF interface (e.g., an interface via which the network controller <NUM> is communicatively coupled to an RF router, such as the RF router <NUM>), a LiFi interface (e.g., an interface via which the network controller <NUM> is communicatively coupled to a LiFi router, such as the LiFi router <NUM>), an external communications interface (e.g., an interface via which the network controller <NUM> is communicatively coupled to one or more external modems, such as the external modems <NUM>), and a wired interface (e.g., an interface via which the network controller <NUM> is communicatively coupled to vehicle control equipment, such as the vehicle control equipment <NUM>).

The illustrated network controller <NUM> is only one example of a computing device suitable to be particularly configured for use in one of systems <NUM>, <NUM>, <NUM>, and <NUM>. Other embodiments of the network controller <NUM> may also, or instead, be used in one of systems <NUM>, <NUM>, <NUM>, and <NUM>, even if the other embodiments have more, fewer and/or different components than those shown in <FIG>, have one or more combined components, or have a different configuration or arrangement of the components. Moreover, the various components shown in <FIG> can be implemented in hardware, a processor executing software instructions, or a combination of both hardware and a processor executing software instructions, including one or more signal processing and/or application-specific integrated circuits.

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

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

Claim 1:
A system (<NUM>) for providing dual fidelity communications on-board a vehicle that includes a plurality of seats (<NUM>) having corresponding seatback devices (<NUM>) installed thereat, the system (<NUM>) comprising:
a radio frequency, RF, router operatively connected to one or more wireless access points (<NUM>) distributed throughout the vehicle;
a light fidelity, LiFi, router operatively connected to a plurality of lights disposed within respective passenger service units, wherein each of the lights are configured to emit light directed towards a photo-detector (<NUM>) located at a seat (<NUM>) corresponding to the respective passenger service unit; and
a network controller (<NUM>) operatively connected to the RF router and the LiFi router, wherein the network controller (<NUM>) is configured to:
identify data streams associated with devices on-board the vehicle, wherein one or more of the data streams are associated with seatback devices (<NUM>) on-board the vehicle;
analyze data packets included in the identified data streams to determine a metric associated with the one or more data streams, wherein the metric is indicative of at least (a) an amount of bandwidth required to transmit the data packets that form a particular data stream associated with a particular seatback device (<NUM>), (b) an aggregate amount of bandwidth required to transmit the data packets that form the identified data streams, or (c) an application associated with the particular data stream; and
based on the metric associated with the particular data stream , route data packets that form the particular data stream to one of the RF router or the LiFi router for transmission to the particular seatback device (<NUM>).