WO2018140659A1 - Systems architecture for interconnection of multiple cabin aircraft elements - Google Patents

Abstract

Systems and methods are described for providing data and instruction exchange between disparate aircraft components. A communication subsystem is communicatively coupled to each of the aircraft components with a server communicatively coupled to the subsystem. An interconnectivity middle layer is disposed between the subsystem and server and configured to communicate with each of the aircraft components. Preferred systems utilize topic trees to organize data and facilitate communication.

Description

SYSTEM ARCHITECTURE FOR INTERCONNECTION

OF MULTIPLE AIRCRAFT CABIN ELEMENTS

[0001] This application claims priority to U.S. provisional application having serial no.

62/450148 filed on January 25, 2017. This and all other referenced extrinsic materials are incorporated herein by reference in their entirety. Where a definition or use of a term in a reference that is incorporated by reference is inconsistent or contrary to the definition of that term provided herein, the definition of that term provided herein is deemed to be controlling.

Field of the Invention

[0002] The field of the invention is information system architectures for in-flight use in airplane cabins.

Background

[0003] The background description includes information that may be useful in understanding the present invention. It is not an admission that any of the information provided herein is prior art or relevant to the presently claimed invention, or that any publication specifically or implicitly referenced is prior art.

[0004] Aircraft components and subsystems, such as in-flight entertainment systems, galleys and galley inserts, and flight attendant panels, are becoming increasingly complex. Such components and subsystems frequently incorporate sensors that monitor component and/or supply status, data storage, location sensors, and other components that can provide information useful to optimizing both component and aircraft function. Similarly such components and subsystems are frequently equipped to act on instructions and received data, for example by displaying requested entertainment content, thereby at least partially automating some aspects of customer service and aircraft function.

[0005] Integration of such components and subsystems can both optimize their efficiency and simplify their use. Unfortunately, provision of such components and subsystems from different manufacturers can result in the use of different and in some instances incompatible data formats, communication protocols, and security protocols. As a result, integration and interconnection of such components and subsystems has been challenging.

[0006] Thus, there is still a need for a system architecture that can effectively integrate and/or interconnect aircraft components and subsystems.

Summary of the Invention

[0007] The inventive subject matter comprises a system architecture that provides for efficient interconnection between multiple elements within an aircraft cabin. In some embodiments the system further provides interconnection with systems, devices, and/or services that are external to the aircraft, such as ground-based and/or satellite systems.

[0008] Contemplated systems can provide a communication subsystem that routes information and/or instructions between an aircraft status/control server and various aircraft components and systems, utilizing wired or wireless transfer protocols. In some embodiments, elements of the system that are external to the aircraft can similarly communicate with the aircraft status/control server, and therefore indirectly interact with various aircraft components and subsystems.

[0009] Various objects, features, aspects and advantages of the inventive subject matter will become more apparent from the following detailed description of preferred embodiments, along with the accompanying drawing figures.

Brief Description of The Drawings

[0010] Fig. 1 is a diagram showing information flow through components of one embodiment of the system.

[0011] Fig. 2 is a flow chart of a system coupled with a variety of cabin systems.

[0012] Figs. 3A-3B are left and right portions of a chart of potential aircraft elements and services that could be operable with the system.

[0013] Fig. 4 is a diagram showing an architecture of another embodiment of the system. [0014] Fig. 5 illustrates various examples of topic trees. [0015] Figs. 6A-6B illustrates additional examples of topic trees.

[0016] Figs. 7A-7B illustrates flow charts showing examples of a use of topic trees to prioritize aircraft/ground communication.

[0017] Fig. 8 illustrates a flow chart showing one example of a use of topic trees to coordinate aircraft/ground communication.

[0018] Fig. 9 illustrates one embodiment of a cabin system set-up.

[0019] Fig. 10 is an exemplary block diagram of a system architecture to interconnect a multiplicity of cabin systems.

[0020] Fig. 11 illustrates a diagram of one embodiment of a data collector. Detailed Description

[0021] Throughout the following discussion, numerous references will be made regarding servers, services, interfaces, portals, platforms, or other systems formed from computing devices. It should be appreciated that the use of such terms is deemed to represent one or more computing devices having at least one processor configured to execute software instructions stored on a computer readable tangible, non-transitory medium. For example, a server can include one or more computers operating as a web server, database server, or other type of computer server in a manner to fulfill described roles, responsibilities, or functions. One should appreciate that the systems and methods described herein allow for disparate systems in an aircraft to be

communicatively coupled to allow for remote status monitoring and/or control, for example.

[0022] It should be noted that any language directed to a computer should be read to include any suitable combination of computing devices, including servers, interfaces, systems, databases, agents, peers, engines, controllers, or other types of computing devices operating individually or collectively. One should appreciate the computing devices comprise a processor configured to execute software instructions stored on a tangible, non-transitory computer readable storage medium (e.g., hard drive, solid state drive, RAM, flash, ROM, etc.). The software instructions preferably configure the computing device to provide the roles, responsibilities, or other functionality as discussed below with respect to the disclosed apparatus. In especially preferred embodiments, the various servers, systems, databases, or interfaces exchange data using standardized protocols or algorithms, possibly based on HTTP, HTTPS, AES, public-private key exchanges, web service APIs, known financial transaction protocols, or other electronic information exchanging methods. Data exchanges preferably are conducted over a packet- switched network, the Internet, LAN, WAN, VPN, or other type of packet switched network.

[0023] The following discussion provides many example embodiments of the inventive subject matter. Although each embodiment represents a single combination of inventive elements, the inventive subject matter is considered to include all possible combinations of the disclosed elements. Thus if one embodiment comprises elements A, B, and C, and a second embodiment comprises elements B and D, then the inventive subject matter is also considered to include other remaining combinations of A, B, C, or D, even if not explicitly disclosed.

[0024] As used herein, and unless the context dictates otherwise, the term "coupled to" is intended to include both direct coupling (in which two elements that are coupled to each other contact each other) and indirect coupling (in which at least one additional element is located between the two elements). Therefore, the terms "coupled to" and "coupled with" are used synonymously.

[0025] Groupings of alternative elements or embodiments of the invention disclosed herein are not to be construed as limitations. Each group member can be referred to and claimed individually or in any combination with other members of the group or other elements found herein. One or more members of a group can be included in, or deleted from, a group for reasons of convenience and/or patentability. When any such inclusion or deletion occurs, the

specification is herein deemed to contain the group as modified thus fulfilling the written description of all Markush groups used in the appended claims.

[0026] Although the below embodiments discuss the system's use in an aircraft, it is

contemplated that the system could be used in other vehicles including, for example, boats, trains, and busses.

[0027] Embodiments of the inventive concept include both physical and virtual components. Physical components can include, for example, cabin components and/or subsystems. Such cabin components can transmit and/or receive data via a wireless (e.g. WiFi, Bluetooth, etc.) and/or wired (e.g. USB, Ethernet, etc.) connection that allow the cabin components to receive command data from and report status data to other system elements. Other physical cabin components may include, for example, a human machine interface (HMI), such as a tablet PC, a smart phone, a smart watch, or other portable computing device, in-flight entertainment system, or a flight attendant call panel. Virtual components of the system can receive data from relevant system components, process the received data, and/or produce a result or other data as a result of such processing. The HMI can serve to display information via a user interface related to various cabin components and services, and can also serve to send commands to any of the cabin components either automatically or based on a user' s input. The system can further include a data hub, which serves to route data to between designated components.

[0028] Systems of the inventive concept can be in communication with an external shared computing resource (e.g. a ground cloud). Such a ground cloud can receive data from the system (for example, over an air-to-ground data link or a ground link), and can send commands to any of the cabin components. The flow of information between various components of one embodiment of system 100 is depicted in Figure 1.

[0029] Another example of a system 200 of the inventive concept is shown in Figure 2. System 200 is advantageously configured to interconnect a multiplicity of aircraft cabin elements. These cabin elements typically have a wide range of communication needs and protocols (e.g. , from few event-based to high-frequent messages), computational and power resources (e.g. , battery- powered wireless sensors, larger LRUs like seat actuators, electrical inserts, and IFE servers, or mobile equipment like trolleys), and possibly a multitude (at least today) of wired and wireless communication interfaces (e.g. , ARINC, CAN, Ethernet, RS485, WiFi, etc.).

[0030] As shown in Figure 2, a communication subsystem 202 provides communication between a data hub (e.g. , an aircraft status/control server 204), cabin components (e.g. in-flight entertainment (IFE) 206, galley 208, seats 210, lighting 212, etc.), human machine interfaces (e.g. flight attendant panels 214), applications (e.g. an in-flight server (ZiHS) 220, and a ground cloud 230. Certain components of the system 200 can communicate with each other directly, for example galley inserts 216 and trolleys 218 can communicate directly with the galley 208. Such communication can be one-way or bidirectional. In some embodiments, ground components in communication with the data hub 204 can be in further communication with virtual components, such as airline services 232, caterer services 234, and/or a virtual server 236.

[0031] Systems of the inventive concept can provide support for a broad range of aircraft elements and services, such as collectively shown in Figures 3A-3B.

[0032] For example, aircraft elements such as in-flight entertainment, seat functions, lighting, galley sensors and components, trolleys, wireless access points, mobile power supplies, lavatory components, overhead compartments, and various cabin electronics can be supported. Similarly various services such as meal ordering, galley preparation, galley insert maintenance and control, object localization, stock management, pre-departure tests, and checking of automated systems can be implemented using the systems and methods described herein.

[0033] System 200 can provide support for both wired and wireless sensors, using any suitable communication protocol. Similarly, system 200 can connect with both (i) end nodes and (ii) data collectors that communicate with the end nodes, thereby providing a highly flexible architecture that supports system partitioning. Such connections and communications can be secured, as necessary or desired. In preferred embodiments system 200 provides fault tolerance, for example, by incorporating redundant components in order to improve reliability. Accordingly, system 200 can include provisions for alerting authorized users (e.g. pilots, crew, and

maintenance personnel) of non-recoverable faults. Accordingly, system 200 is configured to facilitate maintenance and troubleshooting of the connected components and cabin systems. System 200 is advantageously scalable and able to integrate different types of cabin services and elements without the necessity of modifying the system architecture of the system or the cabin services. To that end, system 200 can provide improved traffic to selected networked

components (e.g. to improve the quality of service (QoS) users experience in their use of the component), depending on the nature of the component.

[0034] Interconnection between various technologies and products developed by different vendors is facilitated by the utilization of open standards on the system 200. Suitable hardware open standards include Industry Standard Architecture (ISA), Peripheral Component

Interconnect (PCI), Accelerated Graphics Port (AGP), PCI Industrial Computer Manufacturers Group (PCIMG), synchronous dynamic random-access memory (SDRAM) and its variants, Universal Serial Bus (USB), and DiSEqC. Suitable data file formats include Computer Graphic Metafile (CGM), Darwin Information Typing Architecture (DITA), Hypertext Markup Language (HTML), Extensible HTML (XHTMAL), HTML5, Open Office XML, Ogg, Theora, Opus, OpenDocument format (ODF), Portable Document Format (PDF/X), Portable Network Graphics (PNG), and Scalable Vector Graphics (SVG). Suitable communication protocols include Internet Protocol (IP), Transmission Control Protocol (TCP), OMA Data Synchronization and Device Management, and XMPP. Interconnections between various technologies and varied products is similarly facilitated by minimizing the number of requirements for the connecting elements of the system, and prioritizing adoption of conventions over simplifying system configuration.

[0035] An example of an architecture 400 of system 200 is shown in Figure 4. As shown, a control server 402 (e.g. an Aircraft Status/Control server) can receive inputs from and provide outputs to a variety of aircraft and non-aircraft components and/or subsystems. Such

components and/or subsystems include an aircraft galley data collector 410 (which can receive data from galley sensors 412 and inserts 414), aircraft lighting data collectors 420, aircrafts seats 430, and satellite link (e.g., ARTNC XYZ) translators 440. Data and/or instruction transfer can be accomplished using wired or wireless protocols, and can be secured. In a preferred embodiment IPv6 protocols are utilized in combination with transport layer security (such as (D)TLS). Similarly, control server 402 can communicate with various information sources, include a database 450, a satellite link 452, and/or a cellular telephone network 454 (e.g. via an LTE link), providing data monitoring, presentation of satellite data, and ground link

communication. Towards that end the control server 402 can implement software providing data representation and interconnectivity, data authentication and/or permissions, and data/message queues. The control server 402 can also exchange information with applications and/or services, such as predictive maintenance applications 462, a head end server 464, and flight attendant panels 460 (which can in turn receive information related to status and stocking of the aircraft).

[0036] To facilitate diffusion of data during operation of the system 200, data can be organized into topic trees. Such topic trees can be organized based on physical, logical, and/or functional characteristics. For example, a galley topic tree can include an oven subtopic (e.g. /galley/ 1 /oven/2). Similarly, a head server topic tree can include a service and/or customer offer subtopic (e.g. /zihs/service_round/l/offer). A topic tree can include one or more (sub)tree, which can represent an additional element or functionality. In operation, an entity or component of the system (such as a service or a cabin subsystem) can post data to a topic, retrieve data from a topic, and/or subscribe to or observe data changes within the topic. Similarly, such an entity or component can own or otherwise be associated with a unique topic tree, and can publish to other topics if permitted (e.g. via authentication and authorization). Interoperation of system components that communicate through the system is provided defining a set of mandatory topics (i.e. must be monitored or addressed) and a set of topics that are optional. Such topic trees can include elements that provide secure data usage. For example, data can be provided in an encrypted form, or access to specified topic trees can be controlled by subscription. Such a subscription can be indicated by terminating a topic tree in a specified manner (e.g. "/secure") to indicate that they are special or require a subscription through core services. Examples of typical topic trees are shown in Figures 5 and 6A-6B.

[0037] Although topic trees discussed above are related to concrete subject matter, topic trees can be abstract and permit interaction with various elements of the aircraft environment. For example, an abstract topic tree can incorporate cabin environment data (e.g. information about passengers, specific cabin elements, etc.) or specific flight data (e.g. information about the aircraft, flight phase, time zone, etc.).

[0038] In some embodiments a topic tree structure can be used to coordinate and/or facilitate communication between the aircraft and ground installations. For example, organization of data or information in a topic tree fashion can be used to prioritize communication and/or data transfer between the aircraft and ground installations in response to specific events or conditions (e.g. "urgent" events), or on the completion of a specific task (e.g. landing of the aircraft).

Examples are shown below in Figures 7 and 8.

[0039] An example cabin system set-up shown in Figure 9 is further used to present possible use cases/applications made possible by system 200.

[0040] As an example, for a cabin system setup, an integrated human machine interface (HMI) can be provided on the flight attendant panel for all attached cabin-systems, showing Business Class seat position information such as obtained by various sensors (e.g. , for safety check for Taxi, Take-off, and Landing (TTL)), Economy Class seat position information (e.g. , back rest, table) that can be provided by battery-powered wireless sensors for example for safety check for TTL, Trolley sensors (e.g. , temperature) information display such as provided by sensors on the trolleys, status monitoring and control of electrical galley inserts, control of galley and cabin lights, and display of relevant cabin-system failure information on the flight attendant panel.

[0041] Note that as contemplated system 200 can also provide for the various components of the cabin system to be interconnected and communicate by means of topic trees independent of (a) the respective suppliers of the individual cabin systems, and (b) independent of the underlying communication network architecture and topology.

[0042] The block diagram shown in Figure 10 illustrates an exemplary implementation of system 200 to interconnect a multiplicity of cabin systems using an IP-based communication subsystem and CoAP (Constrained Application Protocol) as a uniform data communication interface. In this example, two generic cabin systems CS 1 and CS2 and a S/W service SRV1 (server) on a computer platform are assumed.

[0043] It is assumed here that both cabin-systems CS 1 and CS2 provide only legacy, possibly non-IP, interfaces and that Data Collectors DC 1 and DC2, respectively, implement the interface and protocol translation between cabin-systems CS 1 and CS2 and the IP network for CoAP- based data exchange between cabin-systems CS 1 and CS2 and SRV1.

[0044] To minimize network configuration requirements, cabin-systems CS 1 and CS2 and all other cabin systems and services to be monitored/controlled should communicate through the data hub 1000, which maintains a routing table for all available CoAP resources (represented as topic trees) and the associated cabin systems and services.

[0045] In that way any CoAP request from computer/server 1010 (consisting of a CoAP method and a topic tree element) from a cabin-system is directed to the data hub 1000, which forwards the request to the corresponding cabin system CS 1 or CS2. In this manner, data is separated from the network architecture in the sense of a Service oriented architecture (SOA). Registration of the CoAP resources and cabin system CS 1, for example, is implemented in the data collector DCl by the data hub handler 1020.

[0046] An example could be a centralized health monitoring service that registers (OBSERVE method) for the health monitoring-relevant data of the desired cabin systems by use of the respective topic tree elements. Through OBSERVE the health monitoring service will automatically receive any health monitoring information that is published by the observed cabin- systems.

[0047] Figure 11 shows more details of a possible implementation of a data collector 1100 for interfacing a generic cabin-system with the IP based communication sub-system. Such data collector could be used as the data collectors DCl and/or DC2 in Figure 10 and with system 200.

[0048] The data collector 1100 can include, for example:

[0049] (a) a plurality of interfaces 1110 to connect with one or more cabin systems/components that implement the specific communication protocols and data formatting to communicate with the attached cabin-system(s). Such interfaces can include but are not limited to RS232, USB, Ethernet, and so forth.

[0050] (b) cabin-system logic 1120 stored within the data collector 1100 that is used to handle data exchange with the attached cabin-system(s) over the interface 1110 on the one side and with the CoAP interface on the other side. For example, the logic 1120 can be used to manage posting information received over the interface 1110 in the CoAP server and also request data from another cabin-system via the CoAP client interface.

[0051] The CoAP layers 1130 and protocol layers are included within the data collector 1100 to comply with the respective standards. Datagram Transport Layer Security (DTLS) is preferably included for security of communication.

[0052] A system wide (S/W) service (SRV1 in the example) is implemented in a similar way except that the parts related to cabin-system specific interfaces are not needed. [0053] It should be apparent to those skilled in the art that many more modifications besides those already described are possible without departing from the inventive concepts herein. The inventive subject matter, therefore, is not to be restricted except in the spirit of the appended claims. Moreover, in interpreting both the specification and the claims, all terms should be interpreted in the broadest possible manner consistent with the context. In particular, the terms "comprises" and "comprising" should be interpreted as referring to elements, components, or steps in a non-exclusive manner, indicating that the referenced elements, components, or steps may be present, or utilized, or combined with other elements, components, or steps that are not expressly referenced. Where the specification claims refers to at least one of something selected from the group consisting of A, B, C .... and N, the text should be interpreted as requiring only one element from the group, not A plus N, or B plus N, etc.

Claims

CLAIMS What is claimed is:

1. A system for providing data and instruction exchange between aircraft components, comprising:

a plurality of aircraft components, wherein each of the plurality of aircraft components is configured to receive or transmit information;

a data collector communicatively coupled to each of the plurality of aircraft components via one or more interfaces;

a server communicatively coupled to the data collector and configured to receive data from the plurality of aircraft components and send commands to the one or more components;

a user interface communicatively coupled to the server and configured to allow data from the plurality of aircraft components to be viewed and instruct the commands to be sent to the one or more components;

wherein the data collector comprises a set of topic trees configured to facilitate

communication between the aircraft components and the data collector, and wherein the server is configured to organize data in a topic tree architecture using the set of topic trees.

2. The system of claim 1, wherein communication between the server and data collector is provided wirelessly.

3. The system of claim 1, wherein communication between the server and data collector is provided using a physical data link.

4. The system of any of claims 1 to 3, wherein the aircraft components are selected from the group consisting of a trolley, a galley insert, an in-flight entertainment system, a seat system, a lighting system, a flight attendant panel, a satellite feed translator, a satellite link, a cellular phone system link, and a database.

5. The system of any of claims 1 to 4, wherein the server further comprises a data

representation middle layer.

6. The system of any of claims 1 to 5, wherein the server further comprises an

authentication/permissions middle layer.

7. The system of any of claims 1 to 6, wherein the server further comprises a response/request queue or a publish/subscribe queue.

8. The system of any of claims 1 to 7, wherein the server is communicatively coupled with an external service.

9. The system of claim 1, wherein the topic tree is configured as a physical topic tree.

10. The system of claim 1, wherein the topic tree is configured as a logical topic tree.

11. The system of claim 1, wherein the topic tree is configured as a functional topic tree.

12. The system of any of claims 9 to 11, wherein the topic tree is encrypted.

13. The system of any of claims 9 to 12, wherein the topic tree facilitates communication between the aircraft when in flight and ground equipment.