US20200086993A1 - Passenger chair component monitoring system - Google Patents
Passenger chair component monitoring system Download PDFInfo
- Publication number
- US20200086993A1 US20200086993A1 US16/135,157 US201816135157A US2020086993A1 US 20200086993 A1 US20200086993 A1 US 20200086993A1 US 201816135157 A US201816135157 A US 201816135157A US 2020086993 A1 US2020086993 A1 US 2020086993A1
- Authority
- US
- United States
- Prior art keywords
- diagnostic
- usage information
- inflight entertainment
- server
- master
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B64—AIRCRAFT; AVIATION; COSMONAUTICS
- B64D—EQUIPMENT FOR FITTING IN OR TO AIRCRAFT; FLIGHT SUITS; PARACHUTES; ARRANGEMENTS OR MOUNTING OF POWER PLANTS OR PROPULSION TRANSMISSIONS IN AIRCRAFT
- B64D11/00—Passenger or crew accommodation; Flight-deck installations not otherwise provided for
- B64D11/0015—Arrangements for entertainment or communications, e.g. radio, television
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B64—AIRCRAFT; AVIATION; COSMONAUTICS
- B64D—EQUIPMENT FOR FITTING IN OR TO AIRCRAFT; FLIGHT SUITS; PARACHUTES; ARRANGEMENTS OR MOUNTING OF POWER PLANTS OR PROPULSION TRANSMISSIONS IN AIRCRAFT
- B64D11/00—Passenger or crew accommodation; Flight-deck installations not otherwise provided for
- B64D11/0015—Arrangements for entertainment or communications, e.g. radio, television
- B64D11/00155—Individual entertainment or communication system remote controls therefor, located in or connected to seat components, e.g. to seat back or arm rest
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B64—AIRCRAFT; AVIATION; COSMONAUTICS
- B64D—EQUIPMENT FOR FITTING IN OR TO AIRCRAFT; FLIGHT SUITS; PARACHUTES; ARRANGEMENTS OR MOUNTING OF POWER PLANTS OR PROPULSION TRANSMISSIONS IN AIRCRAFT
- B64D11/00—Passenger or crew accommodation; Flight-deck installations not otherwise provided for
- B64D11/0015—Arrangements for entertainment or communications, e.g. radio, television
- B64D11/00151—Permanently mounted seat back monitors
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B64—AIRCRAFT; AVIATION; COSMONAUTICS
- B64D—EQUIPMENT FOR FITTING IN OR TO AIRCRAFT; FLIGHT SUITS; PARACHUTES; ARRANGEMENTS OR MOUNTING OF POWER PLANTS OR PROPULSION TRANSMISSIONS IN AIRCRAFT
- B64D11/00—Passenger or crew accommodation; Flight-deck installations not otherwise provided for
- B64D11/06—Arrangements of seats, or adaptations or details specially adapted for aircraft seats
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B64—AIRCRAFT; AVIATION; COSMONAUTICS
- B64D—EQUIPMENT FOR FITTING IN OR TO AIRCRAFT; FLIGHT SUITS; PARACHUTES; ARRANGEMENTS OR MOUNTING OF POWER PLANTS OR PROPULSION TRANSMISSIONS IN AIRCRAFT
- B64D11/00—Passenger or crew accommodation; Flight-deck installations not otherwise provided for
- B64D11/06—Arrangements of seats, or adaptations or details specially adapted for aircraft seats
- B64D11/0624—Arrangements of electrical connectors, e.g. for earphone, internet or electric supply
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/21—Server components or server architectures
- H04N21/214—Specialised server platform, e.g. server located in an airplane, hotel, hospital
- H04N21/2146—Specialised server platform, e.g. server located in an airplane, hotel, hospital located in mass transportation means, e.g. aircraft, train or bus
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B64—AIRCRAFT; AVIATION; COSMONAUTICS
- B64D—EQUIPMENT FOR FITTING IN OR TO AIRCRAFT; FLIGHT SUITS; PARACHUTES; ARRANGEMENTS OR MOUNTING OF POWER PLANTS OR PROPULSION TRANSMISSIONS IN AIRCRAFT
- B64D45/00—Aircraft indicators or protectors not otherwise provided for
- B64D2045/0085—Devices for aircraft health monitoring, e.g. monitoring flutter or vibration
Definitions
- Vehicles for mass transport can include, but are not limited to, aircrafts, boats, trains, and busses.
- the passenger cabins in these types of vehicles are typically designed for long travel durations (e.g., one or more hours of travel).
- the passenger cabins can include reclining chairs that allow passengers to rest or sleep comfortably during travel.
- Passenger chairs can include mechanical linkages that allow the chairs to recline or reposition and possibly one or more actuators (e.g., electric motors, pneumatic linear actuators, or the like) that assist with reclining or repositioning processes.
- actuators e.g., electric motors, pneumatic linear actuators, or the like
- the passenger chair components there is a need for systems and methods of monitoring the passenger chair components for fault detection, isolation, repair, and/or prevention.
- embodiments of the inventive concepts disclosed herein are directed to a system for monitoring passenger chair components.
- the system includes a seat control module communicatively coupled with one or more components of a passenger chair.
- the system may further include an inflight entertainment unit communicatively coupled to the seat control module.
- the inflight entertainment unit can be configured to receive diagnostic and usage information associated with the one or more components from the seat control module.
- the system may further include an aircraft server communicatively coupled to the seat control module and/or to the inflight entertainment unit.
- the aircraft server can be configured to receive the diagnostic and usage information from the seat control module and/or the inflight entertainment unit, and can be further configured to transmit the diagnostic and usage information to a ground server.
- the system can include a plurality of seat control modules communicatively coupled with components of respective passenger chairs.
- the system may also include a plurality of inflight entertainment units communicatively coupled to respective ones of the seat control modules.
- the inflight entertainment units can be configured to receive diagnostic and usage information associated with the components from the (respective) seat control modules.
- the aircraft server communicatively coupled to the seat control modules and/or the inflight entertainment units.
- the aircraft server can be configured to receive the diagnostic and usage information from the seat control modules and/or the inflight entertainment units, and can be further configured to transmit the diagnostic and usage information to a ground server.
- embodiments of the inventive concepts disclosed herein are directed to a method of monitoring passenger chair components.
- diagnostic and usage information is collected from a plurality of seat control modules communicatively coupled with components of respective passenger chairs.
- the diagnostic and usage information can be permanently or temporarily stored on an aircraft server and then transmitted from the aircraft server to a ground server.
- the ground server may be configured to generate an alert and/or instruction based on the diagnostic and usage information.
- FIG. 1 illustrates an example environment in which a system for monitoring passenger chair components can be employed, in accordance with an example embodiment of this disclosure
- FIG. 2 is a block diagram illustrating a system of electronic components for a passenger chair, in accordance with an example embodiment of this disclosure
- FIG. 3 is a block diagram illustrating a system for monitoring passenger chair components, in accordance with an example embodiment of this disclosure
- FIG. 4 is a block diagram illustrating a system for monitoring passenger chair components, in accordance with an example embodiment of this disclosure.
- FIG. 5 is a flow diagram illustrating an example implementation of a method of monitoring passenger chair components.
- inventive concepts are not limited in their application to the details of construction and the arrangement of the components or steps or methodologies set forth in the following description or illustrated in the drawings.
- inventive concepts disclosed herein may be practiced without these specific details.
- well-known features may not be described in detail to avoid unnecessarily complicating the instant disclosure.
- inventive concepts disclosed herein are capable of other embodiments or of being practiced or carried out in various ways. Also, it is to be understood that the phraseology and terminology employed herein is for the purpose of description and should not be regarded as limiting.
- a letter following a reference numeral is intended to reference an embodiment of the feature or element that may be similar, but not necessarily identical, to a previously described element or feature bearing the same reference numeral (e.g., 1 , 1 a , 1 b ).
- Such shorthand notations are used for purposes of convenience only, and should not be construed to limit the inventive concepts disclosed herein in any way unless expressly stated to the contrary.
- any reference to “one embodiment,” or “some embodiments” means that a particular element, feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the inventive concepts disclosed herein.
- the appearances of the phrase “in some embodiments” in various places in the specification are not necessarily all referring to the same embodiment, and embodiments of the inventive concepts disclosed may include one or more of the features expressly described or inherently present herein, or any combination of sub-combination of two or more such features, along with any other features which may not necessarily be expressly described or inherently present in the instant disclosure.
- embodiments of the inventive concepts disclosed herein are directed to a system and method for monitoring passenger chair components and reporting diagnostic and usage information (e.g., faults, test data, use data, or the like) to a remote server (e.g., ground server).
- diagnostic and usage information e.g., faults, test data, use data, or the like
- a remote server e.g., ground server.
- Passenger chairs in aircrafts and other vehicles are incorporating increasingly complex structures that include mechanical linkages, actuators, and/or electrical elements for reclining and/or repositioning the chairs. These components may fail over time, either from wearing down or due to damage (e.g., from an impact or from exposure to debris or moisture). Consequently, there is a need for systems and methods of monitoring the passenger chair components for fault detection, isolation, repair, and/or prevention.
- Systems and methods for monitoring passenger chair components are disclosed herein and are described with reference to example embodiments illustrated in FIGS. 1 through 5 .
- FIG. 1 illustrates an example environment 100 (e.g., an aircraft cabin) that includes a plurality of passenger chairs 102 .
- a passenger chair 102 includes an upper body support member 104 (e.g., a backrest) and a seat 106 .
- the upper body support member 104 and the seat 106 may be separate structures disposed adjacent to one another.
- the upper body support member 104 and the seat 106 can have one or more shared components.
- the upper body support member 104 and the seat 106 can have a shared cushion or covering, one or more shared mechanical linkages, and/or one or more shared actuators.
- the upper body support member 104 may be configured to move relative to the seat 106 .
- the upper body support member 104 can be configured to transition between upright and reclined positions.
- the seat 106 is also repositionable.
- the seat 106 may be configured to move forward/backward, upward/downward, and/or tilt.
- the seat 106 and the upper body support member 104 may be simultaneously actuated to transition from a sitting to a laying position.
- the seat 106 may actuate forwards while the upper body support member 104 reclines to place the passenger chair 102 in a bed-like configuration.
- the passenger chair 102 can also include one or more armrests 108 or armrest consoles adjacent to (e.g., on a left or right side) of the seat 106 .
- the passenger chairs 102 can have respective inflight entertainment (IFE) devices 110 .
- IFE inflight entertainment
- each passenger chair 102 may have an IFE unit 110 embedded within a portion of the passenger chair 102 (e.g., within the backrest), stowed within the armrest 108 , or coupled to or stowed within another fixture or wall structure that is in viewing range of the passenger chair 102 .
- a group of two or more passenger chairs 102 have access to a shared IFE unit 110 .
- the IFE devices 110 may include a media display devices (e.g., a LCDs, LED displays, OLED displays, or the like) for viewing streamed or recorded content (e.g., TV shows, movies, etc.), travel updates (e.g., flight tracking map, altitude, speed, outside air temperature, distance/time to destination, weather updates, or the like).
- An IFE unit 110 for a passenger chair 102 may be integrated (e.g., at least partially embedded) within or coupled to the passenger chair 102 , another passenger chair (e.g., within a backrest of another passenger chair 102 in front of the passenger chair), a wall structure, a console, or the like.
- the IFE devices 110 can also include audio output devices (e.g., speakers, audio output jacks, and/or wireless transmitters (e.g., Bluetooth audio transmitters)).
- the IFE devices 110 include touchscreen displays or other user input devices that can be used to navigate the IFE device menus, play, pause, stop, fast forward, and/or rewind, and/or interact with game media (e.g., video games, trivia games, etc.).
- FIG. 2 A system 200 of electronic components for a passenger chair 102 is illustrated in FIG. 2 , in accordance with an example embodiment of this disclosure.
- the system 200 can include a power supply unit (PSU) 202 configured to receive electrical power from a power source (e.g., electrical outlet, battery, or the like).
- a power control module (PCM) 204 may be coupled to the PSU 202 and configured to distribute electrical power from the PSU 202 to electrical components of the passenger chair 102 .
- PSU power supply unit
- PCM power control module
- the PCM 204 can distribute electrical power from the PSU 202 to a seat control module 206 , one or more actuator(s) 214 (e.g., electrical motors, servos, and/or linear actuators for repositioning the seat 106 , upper body support member 104 , headrest, and/or any other actuatable components), lights and/or peripheral devices 216 (e.g., reading lights, personal ambient lighting, fan(s), automated window shades, or other passenger accessible electronic devices), and/or a passenger control unit 218 (e.g., mechanical user interface controls, capacitive touch or other pressure/proximity based user interface, and/or any other input device that enables the passenger to control the actuator(s) 214 , lights and/or peripheral devices 216 , IFE unit 110 , and/or any other electronic component accessible to the passenger).
- actuator(s) 214 e.g., electrical motors, servos, and/or linear actuators for repositioning the seat 106 , upper body
- the PCM 204 may be configured to directly power the one or more actuators 214 , lights and/or peripheral devices 216 , and/or passenger control unit 218 .
- the PCM 214 is configured to indirectly power one or more of the components by powering the seat control module 206 , which in turn powers one or more of the one or more actuators 214 , lights and/or peripheral devices 216 , and/or passenger control unit 218 .
- the seat control module 206 is configured to control the one or more actuators 214 , lights and/or peripheral devices 216 , and/or passenger control unit 218 .
- the seat control module 206 can be configured to send control signals to the one or more actuators 214 or the lights and/or peripheral devices 216 (e.g., based on default or preprogrammed settings (e.g., takeoff/landing settings) or based on passenger inputs that are entered via the passenger control unit 218 ).
- the seat control module 206 can also be configured to collect data including, but not limited to, inputs received via the passenger control unit 218 and/or current settings or diagnostic data (e.g., test data, fault data, etc.) received from the one or more actuators 214 or the lights and/or peripheral devices 216 .
- diagnostic data e.g., test data, fault data, etc.
- the seat control module 206 includes a controller 208 , memory 210 , and communication interface 212 .
- the controller 208 provides processing functionality for at least the seat control module 206 and can include any number of processors, micro-controllers, circuitry, field programmable gate array (FPGA) or other processing systems, and resident or external memory for storing data, executable code, and other information accessed or generated by the seat control module 206 .
- the controller 208 can execute one or more software programs embodied in a non-transitory computer readable medium (e.g., memory 210 ) that implement techniques described herein.
- the controller 208 is not limited by the materials from which it is formed or the processing mechanisms employed therein and, as such, can be implemented via semiconductor(s) and/or transistors (e.g., using electronic integrated circuit (IC) components), or the like.
- the memory 210 can be an example of tangible, computer-readable storage medium that provides storage functionality to store various data and/or program code associated with operation of the seat control module 206 /controller 208 , such as software programs and/or code segments, or other data to instruct the controller 208 , and possibly other components of the seat control module 206 /system 200 , to perform the functionality described herein.
- the memory 210 can store data, such as a program of instructions for operating the seat control module 206 /system 200 , including its components (e.g., controller 208 , communication interface 212 , actuator(s) 214 , lights and/or peripheral devices 216 , etc.).
- memory 210 can be integral with the controller 208 , can comprise stand-alone memory, or can be a combination of both.
- Some examples of the memory 210 can include removable and non-removable memory components, such as random-access memory (RAM), read-only memory (ROM), flash memory (e.g., a secure digital (SD) memory card, a mini-SD memory card, and/or a micro-SD memory card), solid-state drive (SSD) memory, magnetic memory, optical memory, universal serial bus (USB) memory devices, hard disk memory, external memory, or the like.
- RAM random-access memory
- ROM read-only memory
- flash memory e.g., a secure digital (SD) memory card, a mini-SD memory card, and/or a micro-SD memory card
- SSD solid-state drive
- magnetic memory magnetic memory
- optical memory optical memory
- USB universal serial bus
- the communication interface 212 can be operatively configured to communicate with components of the seat control module 206 .
- the communication interface 212 can be configured to retrieve data from the controller 208 or other devices (e.g., PCM 204 , actuator(s) 214 , lights and/or peripheral devices 216 , passenger control unit 218 , etc.), transmit data for storage in the memory 210 , retrieve data from storage in the memory 210 , and so forth.
- the communication interface 212 can also be communicatively coupled with the controller 208 to facilitate data transfer between components of the seat control module 206 /system 200 and the controller 208 .
- the communication interface 212 is described as a component of the seat control module 206 , one or more components of the communication interface 212 can be implemented as external components communicatively coupled to the seat control module 206 via a wired and/or wireless connection.
- the seat control module 206 can also include and/or connect to one or more input/output (I/O) devices (e.g., via the communication interface 212 ), such as the passenger control unit 218 or any other I/O device (e.g., a mouse, a trackball, a trackpad, a joystick, a line select device, a touchpad, a touchscreen, a keyboard, a keypad, a microphone (e.g., for voice commands), or the like).
- the communication interface 212 includes or is coupled to a transmitter, receiver, transceiver, physical connection interface, or any combination thereof.
- FIGS. 3 and 4 illustrate example embodiments of a system 300 for monitoring components (e.g., PSU 202 , PCM 204 , seat control module 206 , actuator(s) 214 , lights and/or peripheral devices 216 , passenger control unit 218 , etc.) of passenger chairs 102 and reporting diagnostic and usage information to a ground server 318 .
- diagnostic and usage information that can be collected and reported include, but are not limited to, errors/faults (e.g., no signal detected, actuator/positioning errors, power instability, non-functioning lights and/or peripheral device, etc.), test data, settings, user preferences, and/or usage information (e.g., settings, preferences, inputs, and/or actions) collected over time.
- the communication interface 212 may facilitate connectivity between the seat control module 206 and an IFE unit 110 .
- the communication interface 212 can be configured to communicate directly with the IFE unit 110 (e.g., via an ad-hoc connection), or may be configured to communicate with the IFE unit 110 over a network (e.g., a wired/wireless network).
- the seat control module 206 is configured to communicate with an IFE unit 110 that is integrated (e.g., at least partially embedded) within the passenger chair 110 , coupled to the passenger chair 110 , or integrated within or coupled to another structure (e.g., a console, another chair, a wall structure, or a fixture) that is in proximity to the passenger chair 110 (e.g., in viewing range of the passenger chair 110 , such as, but not limited to, the backrest of another passenger chair that is directly in front of the passenger chair 110 ).
- an IFE unit 110 that is integrated (e.g., at least partially embedded) within the passenger chair 110 , coupled to the passenger chair 110 , or integrated within or coupled to another structure (e.g., a console, another chair, a wall structure, or a fixture) that is in proximity to the passenger chair 110 (e.g., in viewing range of the passenger chair 110 , such as, but not limited to, the backrest of another passenger chair that is directly in front of the passenger chair 110 ).
- the IFE unit 110 includes a display 302 and/or an audio output device.
- the IFE unit 110 can also include a respective controller 304 , memory 306 , and communication interface 308 .
- the controller 304 provides processing functionality for at least the IFE unit 110 and can include any number of processors, micro-controllers, circuitry, field programmable gate array (FPGA) or other processing systems, and resident or external memory for storing data, executable code, and other information accessed or generated by the IFE unit 110 .
- the controller 304 can execute one or more software programs embodied in a non-transitory computer readable medium (e.g., memory 306 ) that implement techniques described herein.
- the controller 304 is not limited by the materials from which it is formed or the processing mechanisms employed therein and, as such, can be implemented via semiconductor(s) and/or transistors (e.g., using electronic integrated circuit (IC) components), or the like.
- the memory 306 can be an example of tangible, computer-readable storage medium that provides storage functionality to store various data and/or program code associated with operation of the IFE unit 110 /controller 304 , such as software programs and/or code segments, or other data to instruct the controller 304 , and possibly other components of the IFE unit 110 , to perform the functionality described herein.
- the memory 306 can store data, such as a program of instructions for operating the IFE unit 110 , including its components (e.g., display 302 , controller 304 , communication interface 308 , etc.). It should be noted that while a single memory 306 is described, a wide variety of types and combinations of memory (e.g., tangible, non-transitory memory) can be employed.
- the memory 306 can be integral with the controller 304 , can comprise stand-alone memory, or can be a combination of both. Some examples of the memory 306 can include removable and non-removable memory components, such as random-access memory (RAM), read-only memory (ROM), flash memory (e.g., a secure digital (SD) memory card, a mini-SD memory card, and/or a micro-SD memory card), solid-state drive (SSD) memory, magnetic memory, optical memory, universal serial bus (USB) memory devices, hard disk memory, external memory, or the like.
- RAM random-access memory
- ROM read-only memory
- flash memory e.g., a secure digital (SD) memory card, a mini-SD memory card, and/or a micro-SD memory card
- SSD solid-state drive
- magnetic memory magnetic memory
- optical memory optical memory
- USB universal serial bus
- the communication interface 308 can be operatively configured to communicate with components of the IFE unit 110 .
- the communication interface 308 can be configured to retrieve data from the controller 304 or other devices (e.g., seat control module 206 , aircraft server 310 , and/or another IFE unit (e.g., master/slave IFE unit)), transmit data for storage in the memory 306 , retrieve data from storage in the memory 306 , and so forth.
- the communication interface 308 can also be communicatively coupled with the controller 304 to facilitate data transfer between components of the IFE unit 110 and the controller 304 .
- the communication interface 308 is described as a component of the IFE unit 110 , one or more components of the communication interface 308 can be implemented as external components communicatively coupled to the IFE unit 110 via a wired and/or wireless connection.
- the IFE unit 110 can also include and/or connect to one or more input/output (I/O) devices (e.g., via the communication interface 308 ), such as display 302 , the passenger control unit 218 , or any other I/O device (e.g., a mouse, a trackball, a trackpad, a joystick, a line select device, a touchpad, a touchscreen, a keyboard, a keypad, a microphone (e.g., for voice commands), or the like).
- the communication interface 308 includes or is coupled to a transmitter, receiver, transceiver, physical connection interface, or any combination thereof.
- the communication interface 308 may facilitate connectivity between the IFE unit 110 and an aircraft server 310 .
- the communication interface 308 can be configured to communicate directly with the aircraft server 310 (e.g., via an ad-hoc connection), or may be configured to communicate with the aircraft server 310 over a network (e.g., a wired/wireless network).
- the communication interface 308 may facilitate connectivity between the IFE unit 110 and a ground server 318 .
- the communication interface 308 can be configured to receive wireless communications from the ground server 318 (e.g., over an internet connection, cellular communications link, satellite communications link, or the like).
- the connectivity between the IFE unit 110 and the ground server 318 is established by the aircraft server 310 .
- the aircraft server 310 can be configured to communicate information received from the IFE unit 110 (e.g., diagnostic and usage information received from one or more seat control modules 206 ) to the ground server 318 .
- the aircraft server 310 includes a controller 312 , memory 314 , and a communication interface 316 .
- the controller 312 provides processing functionality for at least the aircraft server 310 and can include any number of processors, micro-controllers, circuitry, field programmable gate array (FPGA) or other processing systems, and resident or external memory for storing data, executable code, and other information accessed or generated by the aircraft server 310 .
- the controller 312 can execute one or more software programs embodied in a non-transitory computer readable medium (e.g., memory 314 ) that implement techniques described herein.
- the controller 312 is not limited by the materials from which it is formed or the processing mechanisms employed therein and, as such, can be implemented via semiconductor(s) and/or transistors (e.g., using electronic integrated circuit (IC) components), or the like.
- the memory 314 can be an example of tangible, computer-readable storage medium that provides storage functionality to store various data and/or program code associated with operation of the aircraft server 310 /controller 312 , such as software programs and/or code segments, or other data to instruct the controller 312 , and possibly other components of the aircraft server 310 , to perform the functionality described herein.
- the memory 314 can store data, such as a program of instructions for operating the aircraft server 310 , including its components (e.g., controller 312 , communication interface 316 , etc.). It should be noted that while a single memory 314 is described, a wide variety of types and combinations of memory (e.g., tangible, non-transitory memory) can be employed.
- the memory 314 can be integral with the controller 312 , can comprise stand-alone memory, or can be a combination of both. Some examples of the memory 314 can include removable and non-removable memory components, such as random-access memory (RAM), read-only memory (ROM), flash memory (e.g., a secure digital (SD) memory card, a mini-SD memory card, and/or a micro-SD memory card), solid-state drive (SSD) memory, magnetic memory, optical memory, universal serial bus (USB) memory devices, hard disk memory, external memory, or the like.
- RAM random-access memory
- ROM read-only memory
- flash memory e.g., a secure digital (SD) memory card, a mini-SD memory card, and/or a micro-SD memory card
- SSD solid-state drive
- magnetic memory magnetic memory
- optical memory optical memory
- USB universal serial bus
- the communication interface 316 can be operatively configured to communicate with components of the aircraft server 310 .
- the communication interface 316 can be configured to retrieve data from the controller 312 or other devices (e.g., IFE unit(s) 110 , ground server 318 , etc.), transmit data for storage in the memory 314 , retrieve data from storage in the memory 314 , and so forth.
- the communication interface 316 can also be communicatively coupled with the controller 312 to facilitate data transfer between components of the aircraft server 310 and the controller 312 .
- the communication interface 316 is described as a component of the aircraft server 310 , one or more components of the communication interface 316 can be implemented as external components communicatively coupled to the aircraft server 310 via a wired and/or wireless connection.
- the aircraft server 310 can also include and/or connect to one or more input/output (I/O) devices (e.g., via the communication interface 316 ), such as a display, a mouse, a trackball, a trackpad, a joystick, a line select device, a touchpad, a touchscreen, a keyboard, a keypad, a microphone (e.g., for voice commands), or the like.
- the communication interface 316 includes or is coupled to a transmitter, receiver, transceiver, physical connection interface, or any combination thereof.
- the ground server 318 also includes a controller 322 , memory 324 , and a communication interface 326 .
- the controller 322 provides processing functionality for at least the ground server 318 and can include any number of processors, micro-controllers, circuitry, field programmable gate array (FPGA) or other processing systems, and resident or external memory for storing data, executable code, and other information accessed or generated by the ground server 318 .
- the controller 322 can execute one or more software programs embodied in a non-transitory computer readable medium (e.g., memory 324 ) that implement techniques described herein.
- the controller 322 is not limited by the materials from which it is formed or the processing mechanisms employed therein and, as such, can be implemented via semiconductor(s) and/or transistors (e.g., using electronic integrated circuit (IC) components), or the like.
- the memory 324 can be an example of tangible, computer-readable storage medium that provides storage functionality to store various data and/or program code associated with operation of the ground server 318 /controller 322 , such as software programs and/or code segments, or other data to instruct the controller 322 , and possibly other components of the ground server 318 , to perform the functionality described herein.
- the memory 324 can store data, such as a program of instructions for operating the ground server 318 , including its components (e.g., controller 322 , communication interface 326 , etc.). It should be noted that while a single memory 324 is described, a wide variety of types and combinations of memory (e.g., tangible, non-transitory memory) can be employed.
- the memory 324 can be integral with the controller 322 , can comprise stand-alone memory, or can be a combination of both. Some examples of the memory 324 can include removable and non-removable memory components, such as random-access memory (RAM), read-only memory (ROM), flash memory (e.g., a secure digital (SD) memory card, a mini-SD memory card, and/or a micro-SD memory card), solid-state drive (SSD) memory, magnetic memory, optical memory, universal serial bus (USB) memory devices, hard disk memory, external memory, or the like.
- RAM random-access memory
- ROM read-only memory
- flash memory e.g., a secure digital (SD) memory card, a mini-SD memory card, and/or a micro-SD memory card
- SSD solid-state drive
- magnetic memory magnetic memory
- optical memory optical memory
- USB universal serial bus
- the communication interface 326 can be operatively configured to communicate with components of the ground server 318 .
- the communication interface 326 can be configured to retrieve data from the controller 322 or other devices (e.g., aircraft server 310 ), transmit data for storage in the memory 324 , retrieve data from storage in the memory 324 , and so forth.
- the communication interface 326 can also be communicatively coupled with the controller 322 to facilitate data transfer between components of the ground server 318 and the controller 322 . It should be noted that while the communication interface 326 is described as a component of the ground server 318 , one or more components of the communication interface 326 can be implemented as external components communicatively coupled to the ground server 318 via a wired and/or wireless connection.
- the ground server 318 can also include and/or connect to one or more input/output (I/O) devices (e.g., via the communication interface 326 ), such as a display, a mouse, a trackball, a trackpad, a joystick, a line select device, a touchpad, a touchscreen, a keyboard, a keypad, a microphone (e.g., for voice commands), or the like.
- I/O input/output
- the communication interface 326 includes or is coupled to a transmitter, receiver, transceiver, physical connection interface, or any combination thereof.
- the seat control module 206 is configured to collect diagnostic and usage information from one or more components (e.g., PSU 202 , PCM 204 , the seat control module 206 itself, actuator(s) 214 , lights and/or peripheral devices 216 , passenger control unit 218 , any combination thereof, etc.) of a respective passenger chair 102 .
- the seat control module 206 is configured to transmit the diagnostic and usage information (e.g., faults, errors, test data, usage data (e.g., usage statistics), user settings/preferences, current settings, any combination thereof, etc.) to a respective IFE unit 110 that is communicatively coupled to the seat control module 206 .
- diagnostic and usage information e.g., faults, errors, test data, usage data (e.g., usage statistics), user settings/preferences, current settings, any combination thereof, etc.
- the IFE unit 110 is configured to receive information from one seat control module 206 . In other embodiments, the IFE unit 110 may be configured to receive information from two or more seat control modules 206 , for example, where the IFE unit 110 is configured to be viewed and/or accessed by a group of passengers.
- the seat control module 206 may be configured to periodically push (e.g., transmit) diagnostic and usage information to the IFE unit 110 .
- the seat control module 206 can also (or alternatively) be configured to transmit diagnostic and usage information to the IFE unit 110 based upon a schedule, in response to triggering event (e.g., startup, restart, detected error/fault), and/or in response to a query/request for information from the IFE unit 110 or a query/request received via the IFE unit 110 (e.g., a query/request from the aircraft server 310 and/or the ground server 318 ).
- triggering event e.g., startup, restart, detected error/fault
- a query/request for information from the IFE unit 110 or a query/request received via the IFE unit 110 e.g., a query/request from the aircraft server 310 and/or the ground server 318 .
- the aircraft server 310 is configured to receive diagnostic and usage information collected by one or more IFE units 110 from respective seat control modules 206 or respective groups of seat control modules 206 .
- the one or more IFE units 110 can be configured to transmit the diagnostic and usage information (e.g., faults, errors, test data, usage data (e.g., usage statistics), user settings/preferences, current settings, any combination thereof, etc.) to the aircraft server 310 periodically, based upon a schedule, in response to triggering event (e.g., startup, restart, detected error/fault), and/or in response to a query/request received from the aircraft server 310 or received via the aircraft server 310 (e.g., from the ground server 318 ).
- triggering event e.g., startup, restart, detected error/fault
- the one or more IFE units 110 are communicatively coupled to the aircraft server 310 via secure server router 332 .
- the system 300 further includes an aviation message router 330 for communications between the IFE units 110 and the aircraft server 310 and/or communications between the aircraft server 310 and the ground server 318 , which may be communicatively coupled to another aviation message router 334 .
- Aviation message router 330 and aviation message router 334 may include trusted labelers that attach a label, certificate, or security code to the communications, or embed the label, certificate, or security code within the communications, transmitted from the aircraft server 310 to the ground server 318 , or vice versa.
- the aviation message routers 330 and 334 are configured to encode or encrypt the communications and/or transmit the communications in a trusted format.
- the aviation message router 330 utilizes the secure server router 332 for air/ground connectivity (e.g., for communication with the ground server 318 and/or for onboard communications).
- the system 300 includes a plurality of IFE units 110 that are configured to collect diagnostic and usage information from the seat control modules 206 of respective passenger chairs 102 and/or groups of passenger chairs 102 .
- the IFE units 110 can then independently transmit the collected diagnostic and usage information to the aircraft server 310 .
- one of the IFE units 110 can be a head/master IFE unit (e.g., IFE unit 328 ) that is configured to receive the diagnostic and usage information collected by the other IFE units 110 and transmit the diagnostic and usage information (possibly including the diagnostic and usage information that the head/master IFE unit 328 itself collected) to the aircraft server 310 .
- the aircraft server 310 After collecting diagnostic and usage information from the one or more IFE units 110 , or from the seat control modules 206 themselves, the aircraft server 310 is configured to transmit the diagnostic and usage information to the ground server 318 .
- the aircraft server 310 can be configured to transmit the diagnostic and usage information (e.g., faults, errors, test data, usage data (e.g., usage statistics), user settings/preferences, current settings, any combination thereof, etc.) to the ground server 318 periodically, based upon a schedule, in response to triggering event (e.g., startup, restart, detected error/fault), and/or in response to a query/request received from the ground server 318 .
- triggering event e.g., startup, restart, detected error/fault
- the ground server 318 may be configured to maintain a log or database that is updated based upon the diagnostic and usage information received from the aircraft server 310 .
- the ground server 318 can also be configured to generate an alert (e.g., warning, error/fault notification, etc.) and/or an instruction (e.g., repair instruction/message, control signal, etc.) based upon the diagnostic and usage information.
- the aircraft server 310 may also be configured to generate alerts and/or instructions based upon the diagnostic and usage information (e.g., for errors/faults that can be corrected inflight or errors/faults that require the passenger to be relocated to prevent harm).
- the aircraft server 310 can also be configured to transmit at least some of the diagnostic and usage information to one or more mobile devices 336 (e.g., tablets, smartphones, notebook computers, wearable devices such as smart watches or activity trackers, etc.).
- the aircraft server 310 can be configured to transmit the diagnostic and usage information (e.g., faults, errors, test data, usage data (e.g., usage statistics), user settings/preferences, current settings, any combination thereof, etc.) to a flight attendant mobile device 336 periodically, based upon a schedule, in response to triggering event (e.g., startup, restart, detected error/fault), and/or in response to a query/request received from the mobile device 336 .
- triggering event e.g., startup, restart, detected error/fault
- the mobile device 336 can be configured with a mobile application (“App”) that provides access to the diagnostic and usage information.
- the diagnostic and usage information can include status information, such as, but not limited to, safety belt status (e.g., buckled or unbuckled), chair position status (e.g., upright or reclined), passenger tray status (e.g., stowed or deployed), and so forth. This allows a flight attendant to conveniently monitor passenger statuses via the flight attendant's mobile device 336 .
- the mobile device 336 may be configured to generate an alert (e.g., warning, error/fault notification, etc.) based upon the diagnostic and usage information, for example, for errors/faults that can be corrected inflight or errors/faults or statuses (e.g., unbuckled safety belt, etc.) that require flight attendant intervention.
- an alert e.g., warning, error/fault notification, etc.
- the diagnostic and usage information for example, for errors/faults that can be corrected inflight or errors/faults or statuses (e.g., unbuckled safety belt, etc.) that require flight attendant intervention.
- FIG. 5 illustrates an example implementation of a method 400 that employs a system for monitoring passenger chair components, such as the system 300 described above.
- operations of disclosed processes e.g., method 400
- the method 400 includes collecting diagnostic and usage information from a plurality of seat control modules 206 communicatively coupled with components (e.g., PSU 202 , PCM 204 , the seat control module 206 itself, actuator(s) 214 , lights and/or peripheral devices 216 , passenger control unit 218 , any combination thereof, etc.) of respective passenger chairs 102 (block 402 ).
- IFE units 110 can be configured to collect diagnostic and usage information from the seat control modules 206 of respective passenger chairs 102 or respective groups of passenger chairs 206 .
- the diagnostic and usage information can be permanently or temporarily stored on an aircraft server 310 (block 404 ).
- the diagnostic and usage information can be transmitted from the IFE units 110 to the aircraft server 310 , which then stores the diagnostic and usage information (e.g., in memory 314 ).
- each of the IFE units 110 is configured to transmit the information collected by the IFE unit 110 to the aircraft server 310 .
- a head/master IFE unit 328 may receive diagnostic and usage information collected by the other IFE units 110 and can be configured to then transmit the diagnostic and usage information to the aircraft server 310 .
- the seat control modules 206 can be communicatively coupled with the aircraft server 310 and configured to transmit the diagnostic and usage information to the aircraft server 310 (i.e., without routing the information through IFE units 110 ).
- the diagnostic and usage information is transmitted to a ground server 318 (block 406 ).
- the aircraft server 310 can be configured to transmit the diagnostic and usage information (e.g., faults, errors, test data, usage data (e.g., usage statistics), user settings/preferences, current settings, any combination thereof, etc.) to the ground server 318 periodically, based upon a schedule, in response to triggering event (e.g., startup, restart, detected error/fault), and/or in response to a query/request received from the ground server 318 .
- triggering event e.g., startup, restart, detected error/fault
- the method 400 further includes generating an alert and/or instruction based on the diagnostic and usage information (block 408 ).
- the ground server 318 may be configured to generate an alert (e.g., warning, error/fault notification, etc.) and/or an instruction (e.g., repair instruction/message, control signal, etc.) based upon the diagnostic and usage information.
- the method 400 may further include any step or operation implied or required by the embodiments of system 300 described herein.
- the system 300 can also include any additional component or functionality expressed or implied by the method 400 .
- implementations of the methods according to the inventive concepts disclosed herein may include one or more of the steps described herein. Further, such steps may be carried out in any desired order and two or more of the steps may be carried out simultaneously with one another. Two or more of the steps disclosed herein may be combined in a single step, and in some implementations, one or more of the steps may be carried out as two or more sub-steps. Further, other steps or sub-steps may be carried in addition to, or as substitutes to one or more of the steps disclosed herein.
- inventive concepts disclosed herein are well adapted to carry out the objects and to attain the advantages mentioned herein as well as those inherent in the inventive concepts disclosed herein. While presently preferred embodiments of the inventive concepts disclosed herein have been described for purposes of this disclosure, it will be understood that numerous changes may be made which will readily suggest themselves to those skilled in the art and which are accomplished within the broad scope and coverage of the inventive concepts disclosed and claimed herein.
Abstract
Description
- Vehicles for mass transport can include, but are not limited to, aircrafts, boats, trains, and busses. The passenger cabins in these types of vehicles are typically designed for long travel durations (e.g., one or more hours of travel). As such, the passenger cabins can include reclining chairs that allow passengers to rest or sleep comfortably during travel.
- Passenger chairs can include mechanical linkages that allow the chairs to recline or reposition and possibly one or more actuators (e.g., electric motors, pneumatic linear actuators, or the like) that assist with reclining or repositioning processes. Because of the increasingly complex mechanical linkages, actuators, and/or electrical elements built into such chairs, there is a need for systems and methods of monitoring the passenger chair components for fault detection, isolation, repair, and/or prevention.
- In one aspect, embodiments of the inventive concepts disclosed herein are directed to a system for monitoring passenger chair components. In embodiments, the system includes a seat control module communicatively coupled with one or more components of a passenger chair. The system may further include an inflight entertainment unit communicatively coupled to the seat control module. The inflight entertainment unit can be configured to receive diagnostic and usage information associated with the one or more components from the seat control module. The system may further include an aircraft server communicatively coupled to the seat control module and/or to the inflight entertainment unit. The aircraft server can be configured to receive the diagnostic and usage information from the seat control module and/or the inflight entertainment unit, and can be further configured to transmit the diagnostic and usage information to a ground server.
- In embodiments, the system can include a plurality of seat control modules communicatively coupled with components of respective passenger chairs. The system may also include a plurality of inflight entertainment units communicatively coupled to respective ones of the seat control modules. The inflight entertainment units can be configured to receive diagnostic and usage information associated with the components from the (respective) seat control modules. The aircraft server communicatively coupled to the seat control modules and/or the inflight entertainment units. The aircraft server can be configured to receive the diagnostic and usage information from the seat control modules and/or the inflight entertainment units, and can be further configured to transmit the diagnostic and usage information to a ground server.
- In another aspect, embodiments of the inventive concepts disclosed herein are directed to a method of monitoring passenger chair components. In implementations of the method, diagnostic and usage information is collected from a plurality of seat control modules communicatively coupled with components of respective passenger chairs. The diagnostic and usage information can be permanently or temporarily stored on an aircraft server and then transmitted from the aircraft server to a ground server. In some implementations, the ground server may be configured to generate an alert and/or instruction based on the diagnostic and usage information.
- This Summary is provided solely as an introduction to subject matter that is fully described in the Detailed Description and Drawings. The Summary should not be considered to describe essential features nor be used to determine the scope of the Claims. Moreover, it is to be understood that both the foregoing Summary and the following Detailed Description are example and explanatory only and are not necessarily restrictive of the subject matter claimed.
- Implementations of the inventive concepts disclosed herein may be better understood when consideration is given to the following detailed description thereof. Such description makes reference to the included drawings, which are not necessarily to scale, and in which some features may be exaggerated and some features may be omitted or may be represented schematically in the interest of clarity. Like reference numerals in the drawings may represent and refer to the same or similar element, feature, or function. In the drawings:
-
FIG. 1 illustrates an example environment in which a system for monitoring passenger chair components can be employed, in accordance with an example embodiment of this disclosure; -
FIG. 2 is a block diagram illustrating a system of electronic components for a passenger chair, in accordance with an example embodiment of this disclosure; -
FIG. 3 is a block diagram illustrating a system for monitoring passenger chair components, in accordance with an example embodiment of this disclosure; -
FIG. 4 is a block diagram illustrating a system for monitoring passenger chair components, in accordance with an example embodiment of this disclosure; and -
FIG. 5 is a flow diagram illustrating an example implementation of a method of monitoring passenger chair components. - Before explaining at least one embodiment of the inventive concepts disclosed herein in detail, it is to be understood that the inventive concepts are not limited in their application to the details of construction and the arrangement of the components or steps or methodologies set forth in the following description or illustrated in the drawings. In the following detailed description of embodiments of the instant inventive concepts, numerous specific details are set forth in order to provide a more thorough understanding of the inventive concepts. However, it will be apparent to one of ordinary skill in the art having the benefit of the instant disclosure that the inventive concepts disclosed herein may be practiced without these specific details. In other instances, well-known features may not be described in detail to avoid unnecessarily complicating the instant disclosure. The inventive concepts disclosed herein are capable of other embodiments or of being practiced or carried out in various ways. Also, it is to be understood that the phraseology and terminology employed herein is for the purpose of description and should not be regarded as limiting.
- As used herein a letter following a reference numeral is intended to reference an embodiment of the feature or element that may be similar, but not necessarily identical, to a previously described element or feature bearing the same reference numeral (e.g., 1, 1 a, 1 b). Such shorthand notations are used for purposes of convenience only, and should not be construed to limit the inventive concepts disclosed herein in any way unless expressly stated to the contrary.
- Further, unless expressly stated to the contrary, “or” refers to an inclusive or and not to an exclusive or. For example, a condition A or B is satisfied by anyone of the following: A is true (or present) and B is false (or not present), A is false (or not present) and B is true (or present), and both A and B are true (or present).
- In addition, use of the “a” or “an” are employed to describe elements and components of embodiments of the instant inventive concepts. This is done merely for convenience and to give a general sense of the inventive concepts, and “a’ and “an” are intended to include one or at least one and the singular also includes the plural unless it is obvious that it is meant otherwise.
- Finally, as used herein any reference to “one embodiment,” or “some embodiments” means that a particular element, feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the inventive concepts disclosed herein. The appearances of the phrase “in some embodiments” in various places in the specification are not necessarily all referring to the same embodiment, and embodiments of the inventive concepts disclosed may include one or more of the features expressly described or inherently present herein, or any combination of sub-combination of two or more such features, along with any other features which may not necessarily be expressly described or inherently present in the instant disclosure.
- Broadly, embodiments of the inventive concepts disclosed herein are directed to a system and method for monitoring passenger chair components and reporting diagnostic and usage information (e.g., faults, test data, use data, or the like) to a remote server (e.g., ground server). Passenger chairs in aircrafts and other vehicles are incorporating increasingly complex structures that include mechanical linkages, actuators, and/or electrical elements for reclining and/or repositioning the chairs. These components may fail over time, either from wearing down or due to damage (e.g., from an impact or from exposure to debris or moisture). Consequently, there is a need for systems and methods of monitoring the passenger chair components for fault detection, isolation, repair, and/or prevention. Systems and methods for monitoring passenger chair components are disclosed herein and are described with reference to example embodiments illustrated in
FIGS. 1 through 5 . -
FIG. 1 illustrates an example environment 100 (e.g., an aircraft cabin) that includes a plurality ofpassenger chairs 102. In embodiments, apassenger chair 102 includes an upper body support member 104 (e.g., a backrest) and aseat 106. In some embodiments, the upperbody support member 104 and theseat 106 may be separate structures disposed adjacent to one another. Alternatively, the upperbody support member 104 and theseat 106 can have one or more shared components. For example, the upperbody support member 104 and theseat 106 can have a shared cushion or covering, one or more shared mechanical linkages, and/or one or more shared actuators. The upperbody support member 104 may be configured to move relative to theseat 106. For example, the upperbody support member 104 can be configured to transition between upright and reclined positions. In some embodiments, theseat 106 is also repositionable. For example, theseat 106 may be configured to move forward/backward, upward/downward, and/or tilt. Theseat 106 and the upperbody support member 104 may be simultaneously actuated to transition from a sitting to a laying position. For example, theseat 106 may actuate forwards while the upperbody support member 104 reclines to place thepassenger chair 102 in a bed-like configuration. In some embodiments, thepassenger chair 102 can also include one ormore armrests 108 or armrest consoles adjacent to (e.g., on a left or right side) of theseat 106. - The passenger chairs 102 (or a group of passenger chairs 102) can have respective inflight entertainment (IFE)
devices 110. For example, eachpassenger chair 102 may have anIFE unit 110 embedded within a portion of the passenger chair 102 (e.g., within the backrest), stowed within thearmrest 108, or coupled to or stowed within another fixture or wall structure that is in viewing range of thepassenger chair 102. In some embodiments, a group of two or more passenger chairs 102 have access to a sharedIFE unit 110. TheIFE devices 110 may include a media display devices (e.g., a LCDs, LED displays, OLED displays, or the like) for viewing streamed or recorded content (e.g., TV shows, movies, etc.), travel updates (e.g., flight tracking map, altitude, speed, outside air temperature, distance/time to destination, weather updates, or the like). AnIFE unit 110 for apassenger chair 102 may be integrated (e.g., at least partially embedded) within or coupled to thepassenger chair 102, another passenger chair (e.g., within a backrest of anotherpassenger chair 102 in front of the passenger chair), a wall structure, a console, or the like. TheIFE devices 110 can also include audio output devices (e.g., speakers, audio output jacks, and/or wireless transmitters (e.g., Bluetooth audio transmitters)). In some embodiments, theIFE devices 110 include touchscreen displays or other user input devices that can be used to navigate the IFE device menus, play, pause, stop, fast forward, and/or rewind, and/or interact with game media (e.g., video games, trivia games, etc.). - A
system 200 of electronic components for apassenger chair 102 is illustrated inFIG. 2 , in accordance with an example embodiment of this disclosure. Thesystem 200 can include a power supply unit (PSU) 202 configured to receive electrical power from a power source (e.g., electrical outlet, battery, or the like). A power control module (PCM) 204 may be coupled to thePSU 202 and configured to distribute electrical power from thePSU 202 to electrical components of thepassenger chair 102. For example, thePCM 204 can distribute electrical power from thePSU 202 to aseat control module 206, one or more actuator(s) 214 (e.g., electrical motors, servos, and/or linear actuators for repositioning theseat 106, upperbody support member 104, headrest, and/or any other actuatable components), lights and/or peripheral devices 216 (e.g., reading lights, personal ambient lighting, fan(s), automated window shades, or other passenger accessible electronic devices), and/or a passenger control unit 218 (e.g., mechanical user interface controls, capacitive touch or other pressure/proximity based user interface, and/or any other input device that enables the passenger to control the actuator(s) 214, lights and/orperipheral devices 216,IFE unit 110, and/or any other electronic component accessible to the passenger). ThePCM 204 may be configured to directly power the one ormore actuators 214, lights and/orperipheral devices 216, and/orpassenger control unit 218. In some embodiments, thePCM 214 is configured to indirectly power one or more of the components by powering theseat control module 206, which in turn powers one or more of the one ormore actuators 214, lights and/orperipheral devices 216, and/orpassenger control unit 218. - The
seat control module 206 is configured to control the one ormore actuators 214, lights and/orperipheral devices 216, and/orpassenger control unit 218. For example, theseat control module 206 can be configured to send control signals to the one ormore actuators 214 or the lights and/or peripheral devices 216 (e.g., based on default or preprogrammed settings (e.g., takeoff/landing settings) or based on passenger inputs that are entered via the passenger control unit 218). Theseat control module 206 can also be configured to collect data including, but not limited to, inputs received via thepassenger control unit 218 and/or current settings or diagnostic data (e.g., test data, fault data, etc.) received from the one ormore actuators 214 or the lights and/orperipheral devices 216. - In embodiments, the
seat control module 206 includes acontroller 208,memory 210, andcommunication interface 212. Thecontroller 208 provides processing functionality for at least theseat control module 206 and can include any number of processors, micro-controllers, circuitry, field programmable gate array (FPGA) or other processing systems, and resident or external memory for storing data, executable code, and other information accessed or generated by theseat control module 206. Thecontroller 208 can execute one or more software programs embodied in a non-transitory computer readable medium (e.g., memory 210) that implement techniques described herein. Thecontroller 208 is not limited by the materials from which it is formed or the processing mechanisms employed therein and, as such, can be implemented via semiconductor(s) and/or transistors (e.g., using electronic integrated circuit (IC) components), or the like. - The
memory 210 can be an example of tangible, computer-readable storage medium that provides storage functionality to store various data and/or program code associated with operation of theseat control module 206/controller 208, such as software programs and/or code segments, or other data to instruct thecontroller 208, and possibly other components of theseat control module 206/system 200, to perform the functionality described herein. Thus, thememory 210 can store data, such as a program of instructions for operating theseat control module 206/system 200, including its components (e.g.,controller 208,communication interface 212, actuator(s) 214, lights and/orperipheral devices 216, etc.). It should be noted that while asingle memory 210 is described, a wide variety of types and combinations of memory (e.g., tangible, non-transitory memory) can be employed. Thememory 210 can be integral with thecontroller 208, can comprise stand-alone memory, or can be a combination of both. Some examples of thememory 210 can include removable and non-removable memory components, such as random-access memory (RAM), read-only memory (ROM), flash memory (e.g., a secure digital (SD) memory card, a mini-SD memory card, and/or a micro-SD memory card), solid-state drive (SSD) memory, magnetic memory, optical memory, universal serial bus (USB) memory devices, hard disk memory, external memory, or the like. - The
communication interface 212 can be operatively configured to communicate with components of theseat control module 206. For example, thecommunication interface 212 can be configured to retrieve data from thecontroller 208 or other devices (e.g.,PCM 204, actuator(s) 214, lights and/orperipheral devices 216,passenger control unit 218, etc.), transmit data for storage in thememory 210, retrieve data from storage in thememory 210, and so forth. Thecommunication interface 212 can also be communicatively coupled with thecontroller 208 to facilitate data transfer between components of theseat control module 206/system 200 and thecontroller 208. It should be noted that while thecommunication interface 212 is described as a component of theseat control module 206, one or more components of thecommunication interface 212 can be implemented as external components communicatively coupled to theseat control module 206 via a wired and/or wireless connection. Theseat control module 206 can also include and/or connect to one or more input/output (I/O) devices (e.g., via the communication interface 212), such as thepassenger control unit 218 or any other I/O device (e.g., a mouse, a trackball, a trackpad, a joystick, a line select device, a touchpad, a touchscreen, a keyboard, a keypad, a microphone (e.g., for voice commands), or the like). In embodiments, thecommunication interface 212 includes or is coupled to a transmitter, receiver, transceiver, physical connection interface, or any combination thereof. -
FIGS. 3 and 4 illustrate example embodiments of asystem 300 for monitoring components (e.g.,PSU 202,PCM 204,seat control module 206, actuator(s) 214, lights and/orperipheral devices 216,passenger control unit 218, etc.) of passenger chairs 102 and reporting diagnostic and usage information to aground server 318. Examples of diagnostic and usage information that can be collected and reported include, but are not limited to, errors/faults (e.g., no signal detected, actuator/positioning errors, power instability, non-functioning lights and/or peripheral device, etc.), test data, settings, user preferences, and/or usage information (e.g., settings, preferences, inputs, and/or actions) collected over time. - As shown in
FIG. 3 , thecommunication interface 212 may facilitate connectivity between theseat control module 206 and anIFE unit 110. For example, thecommunication interface 212 can be configured to communicate directly with the IFE unit 110 (e.g., via an ad-hoc connection), or may be configured to communicate with theIFE unit 110 over a network (e.g., a wired/wireless network). In some embodiments, theseat control module 206 is configured to communicate with anIFE unit 110 that is integrated (e.g., at least partially embedded) within thepassenger chair 110, coupled to thepassenger chair 110, or integrated within or coupled to another structure (e.g., a console, another chair, a wall structure, or a fixture) that is in proximity to the passenger chair 110 (e.g., in viewing range of thepassenger chair 110, such as, but not limited to, the backrest of another passenger chair that is directly in front of the passenger chair 110). - In embodiments, the
IFE unit 110 includes adisplay 302 and/or an audio output device. TheIFE unit 110 can also include arespective controller 304,memory 306, andcommunication interface 308. Thecontroller 304 provides processing functionality for at least theIFE unit 110 and can include any number of processors, micro-controllers, circuitry, field programmable gate array (FPGA) or other processing systems, and resident or external memory for storing data, executable code, and other information accessed or generated by theIFE unit 110. Thecontroller 304 can execute one or more software programs embodied in a non-transitory computer readable medium (e.g., memory 306) that implement techniques described herein. Thecontroller 304 is not limited by the materials from which it is formed or the processing mechanisms employed therein and, as such, can be implemented via semiconductor(s) and/or transistors (e.g., using electronic integrated circuit (IC) components), or the like. - The
memory 306 can be an example of tangible, computer-readable storage medium that provides storage functionality to store various data and/or program code associated with operation of theIFE unit 110/controller 304, such as software programs and/or code segments, or other data to instruct thecontroller 304, and possibly other components of theIFE unit 110, to perform the functionality described herein. Thus, thememory 306 can store data, such as a program of instructions for operating theIFE unit 110, including its components (e.g.,display 302,controller 304,communication interface 308, etc.). It should be noted that while asingle memory 306 is described, a wide variety of types and combinations of memory (e.g., tangible, non-transitory memory) can be employed. Thememory 306 can be integral with thecontroller 304, can comprise stand-alone memory, or can be a combination of both. Some examples of thememory 306 can include removable and non-removable memory components, such as random-access memory (RAM), read-only memory (ROM), flash memory (e.g., a secure digital (SD) memory card, a mini-SD memory card, and/or a micro-SD memory card), solid-state drive (SSD) memory, magnetic memory, optical memory, universal serial bus (USB) memory devices, hard disk memory, external memory, or the like. - The
communication interface 308 can be operatively configured to communicate with components of theIFE unit 110. For example, thecommunication interface 308 can be configured to retrieve data from thecontroller 304 or other devices (e.g.,seat control module 206,aircraft server 310, and/or another IFE unit (e.g., master/slave IFE unit)), transmit data for storage in thememory 306, retrieve data from storage in thememory 306, and so forth. Thecommunication interface 308 can also be communicatively coupled with thecontroller 304 to facilitate data transfer between components of theIFE unit 110 and thecontroller 304. It should be noted that while thecommunication interface 308 is described as a component of theIFE unit 110, one or more components of thecommunication interface 308 can be implemented as external components communicatively coupled to theIFE unit 110 via a wired and/or wireless connection. TheIFE unit 110 can also include and/or connect to one or more input/output (I/O) devices (e.g., via the communication interface 308), such asdisplay 302, thepassenger control unit 218, or any other I/O device (e.g., a mouse, a trackball, a trackpad, a joystick, a line select device, a touchpad, a touchscreen, a keyboard, a keypad, a microphone (e.g., for voice commands), or the like). In embodiments, thecommunication interface 308 includes or is coupled to a transmitter, receiver, transceiver, physical connection interface, or any combination thereof. - The
communication interface 308 may facilitate connectivity between theIFE unit 110 and anaircraft server 310. For example, thecommunication interface 308 can be configured to communicate directly with the aircraft server 310 (e.g., via an ad-hoc connection), or may be configured to communicate with theaircraft server 310 over a network (e.g., a wired/wireless network). Thecommunication interface 308 may facilitate connectivity between theIFE unit 110 and aground server 318. For example, thecommunication interface 308 can be configured to receive wireless communications from the ground server 318 (e.g., over an internet connection, cellular communications link, satellite communications link, or the like). In embodiments, the connectivity between theIFE unit 110 and theground server 318 is established by theaircraft server 310. For example, theaircraft server 310 can be configured to communicate information received from the IFE unit 110 (e.g., diagnostic and usage information received from one or more seat control modules 206) to theground server 318. - In embodiments, the
aircraft server 310 includes acontroller 312,memory 314, and acommunication interface 316. Thecontroller 312 provides processing functionality for at least theaircraft server 310 and can include any number of processors, micro-controllers, circuitry, field programmable gate array (FPGA) or other processing systems, and resident or external memory for storing data, executable code, and other information accessed or generated by theaircraft server 310. Thecontroller 312 can execute one or more software programs embodied in a non-transitory computer readable medium (e.g., memory 314) that implement techniques described herein. Thecontroller 312 is not limited by the materials from which it is formed or the processing mechanisms employed therein and, as such, can be implemented via semiconductor(s) and/or transistors (e.g., using electronic integrated circuit (IC) components), or the like. - The
memory 314 can be an example of tangible, computer-readable storage medium that provides storage functionality to store various data and/or program code associated with operation of theaircraft server 310/controller 312, such as software programs and/or code segments, or other data to instruct thecontroller 312, and possibly other components of theaircraft server 310, to perform the functionality described herein. Thus, thememory 314 can store data, such as a program of instructions for operating theaircraft server 310, including its components (e.g.,controller 312,communication interface 316, etc.). It should be noted that while asingle memory 314 is described, a wide variety of types and combinations of memory (e.g., tangible, non-transitory memory) can be employed. Thememory 314 can be integral with thecontroller 312, can comprise stand-alone memory, or can be a combination of both. Some examples of thememory 314 can include removable and non-removable memory components, such as random-access memory (RAM), read-only memory (ROM), flash memory (e.g., a secure digital (SD) memory card, a mini-SD memory card, and/or a micro-SD memory card), solid-state drive (SSD) memory, magnetic memory, optical memory, universal serial bus (USB) memory devices, hard disk memory, external memory, or the like. - The
communication interface 316 can be operatively configured to communicate with components of theaircraft server 310. For example, thecommunication interface 316 can be configured to retrieve data from thecontroller 312 or other devices (e.g., IFE unit(s) 110,ground server 318, etc.), transmit data for storage in thememory 314, retrieve data from storage in thememory 314, and so forth. Thecommunication interface 316 can also be communicatively coupled with thecontroller 312 to facilitate data transfer between components of theaircraft server 310 and thecontroller 312. It should be noted that while thecommunication interface 316 is described as a component of theaircraft server 310, one or more components of thecommunication interface 316 can be implemented as external components communicatively coupled to theaircraft server 310 via a wired and/or wireless connection. Theaircraft server 310 can also include and/or connect to one or more input/output (I/O) devices (e.g., via the communication interface 316), such as a display, a mouse, a trackball, a trackpad, a joystick, a line select device, a touchpad, a touchscreen, a keyboard, a keypad, a microphone (e.g., for voice commands), or the like. In embodiments, thecommunication interface 316 includes or is coupled to a transmitter, receiver, transceiver, physical connection interface, or any combination thereof. - In embodiments, the
ground server 318 also includes acontroller 322,memory 324, and acommunication interface 326. Thecontroller 322 provides processing functionality for at least theground server 318 and can include any number of processors, micro-controllers, circuitry, field programmable gate array (FPGA) or other processing systems, and resident or external memory for storing data, executable code, and other information accessed or generated by theground server 318. Thecontroller 322 can execute one or more software programs embodied in a non-transitory computer readable medium (e.g., memory 324) that implement techniques described herein. Thecontroller 322 is not limited by the materials from which it is formed or the processing mechanisms employed therein and, as such, can be implemented via semiconductor(s) and/or transistors (e.g., using electronic integrated circuit (IC) components), or the like. - The
memory 324 can be an example of tangible, computer-readable storage medium that provides storage functionality to store various data and/or program code associated with operation of theground server 318/controller 322, such as software programs and/or code segments, or other data to instruct thecontroller 322, and possibly other components of theground server 318, to perform the functionality described herein. Thus, thememory 324 can store data, such as a program of instructions for operating theground server 318, including its components (e.g.,controller 322,communication interface 326, etc.). It should be noted that while asingle memory 324 is described, a wide variety of types and combinations of memory (e.g., tangible, non-transitory memory) can be employed. Thememory 324 can be integral with thecontroller 322, can comprise stand-alone memory, or can be a combination of both. Some examples of thememory 324 can include removable and non-removable memory components, such as random-access memory (RAM), read-only memory (ROM), flash memory (e.g., a secure digital (SD) memory card, a mini-SD memory card, and/or a micro-SD memory card), solid-state drive (SSD) memory, magnetic memory, optical memory, universal serial bus (USB) memory devices, hard disk memory, external memory, or the like. - The
communication interface 326 can be operatively configured to communicate with components of theground server 318. For example, thecommunication interface 326 can be configured to retrieve data from thecontroller 322 or other devices (e.g., aircraft server 310), transmit data for storage in thememory 324, retrieve data from storage in thememory 324, and so forth. Thecommunication interface 326 can also be communicatively coupled with thecontroller 322 to facilitate data transfer between components of theground server 318 and thecontroller 322. It should be noted that while thecommunication interface 326 is described as a component of theground server 318, one or more components of thecommunication interface 326 can be implemented as external components communicatively coupled to theground server 318 via a wired and/or wireless connection. Theground server 318 can also include and/or connect to one or more input/output (I/O) devices (e.g., via the communication interface 326), such as a display, a mouse, a trackball, a trackpad, a joystick, a line select device, a touchpad, a touchscreen, a keyboard, a keypad, a microphone (e.g., for voice commands), or the like. In embodiments, thecommunication interface 326 includes or is coupled to a transmitter, receiver, transceiver, physical connection interface, or any combination thereof. - In embodiments, the
seat control module 206 is configured to collect diagnostic and usage information from one or more components (e.g.,PSU 202,PCM 204, theseat control module 206 itself, actuator(s) 214, lights and/orperipheral devices 216,passenger control unit 218, any combination thereof, etc.) of arespective passenger chair 102. Theseat control module 206 is configured to transmit the diagnostic and usage information (e.g., faults, errors, test data, usage data (e.g., usage statistics), user settings/preferences, current settings, any combination thereof, etc.) to arespective IFE unit 110 that is communicatively coupled to theseat control module 206. In some embodiments, theIFE unit 110 is configured to receive information from oneseat control module 206. In other embodiments, theIFE unit 110 may be configured to receive information from two or moreseat control modules 206, for example, where theIFE unit 110 is configured to be viewed and/or accessed by a group of passengers. Theseat control module 206 may be configured to periodically push (e.g., transmit) diagnostic and usage information to theIFE unit 110. Theseat control module 206 can also (or alternatively) be configured to transmit diagnostic and usage information to theIFE unit 110 based upon a schedule, in response to triggering event (e.g., startup, restart, detected error/fault), and/or in response to a query/request for information from theIFE unit 110 or a query/request received via the IFE unit 110 (e.g., a query/request from theaircraft server 310 and/or the ground server 318). - The
aircraft server 310 is configured to receive diagnostic and usage information collected by one ormore IFE units 110 from respectiveseat control modules 206 or respective groups ofseat control modules 206. For example, the one ormore IFE units 110 can be configured to transmit the diagnostic and usage information (e.g., faults, errors, test data, usage data (e.g., usage statistics), user settings/preferences, current settings, any combination thereof, etc.) to theaircraft server 310 periodically, based upon a schedule, in response to triggering event (e.g., startup, restart, detected error/fault), and/or in response to a query/request received from theaircraft server 310 or received via the aircraft server 310 (e.g., from the ground server 318). - As shown in
FIG. 4 , in some embodiments, the one ormore IFE units 110 are communicatively coupled to theaircraft server 310 viasecure server router 332. In some embodiments, thesystem 300 further includes anaviation message router 330 for communications between theIFE units 110 and theaircraft server 310 and/or communications between theaircraft server 310 and theground server 318, which may be communicatively coupled to anotheraviation message router 334.Aviation message router 330 andaviation message router 334 may include trusted labelers that attach a label, certificate, or security code to the communications, or embed the label, certificate, or security code within the communications, transmitted from theaircraft server 310 to theground server 318, or vice versa. In other embodiments, theaviation message routers aviation message router 330 utilizes thesecure server router 332 for air/ground connectivity (e.g., for communication with theground server 318 and/or for onboard communications). - In some embodiments, the
system 300 includes a plurality ofIFE units 110 that are configured to collect diagnostic and usage information from theseat control modules 206 of respective passenger chairs 102 and/or groups of passenger chairs 102. TheIFE units 110 can then independently transmit the collected diagnostic and usage information to theaircraft server 310. Alternatively, one of theIFE units 110 can be a head/master IFE unit (e.g., IFE unit 328) that is configured to receive the diagnostic and usage information collected by theother IFE units 110 and transmit the diagnostic and usage information (possibly including the diagnostic and usage information that the head/master IFE unit 328 itself collected) to theaircraft server 310. - After collecting diagnostic and usage information from the one or
more IFE units 110, or from theseat control modules 206 themselves, theaircraft server 310 is configured to transmit the diagnostic and usage information to theground server 318. For example, theaircraft server 310 can be configured to transmit the diagnostic and usage information (e.g., faults, errors, test data, usage data (e.g., usage statistics), user settings/preferences, current settings, any combination thereof, etc.) to theground server 318 periodically, based upon a schedule, in response to triggering event (e.g., startup, restart, detected error/fault), and/or in response to a query/request received from theground server 318. Theground server 318 may be configured to maintain a log or database that is updated based upon the diagnostic and usage information received from theaircraft server 310. In embodiments, theground server 318 can also be configured to generate an alert (e.g., warning, error/fault notification, etc.) and/or an instruction (e.g., repair instruction/message, control signal, etc.) based upon the diagnostic and usage information. In some embodiments, theaircraft server 310 may also be configured to generate alerts and/or instructions based upon the diagnostic and usage information (e.g., for errors/faults that can be corrected inflight or errors/faults that require the passenger to be relocated to prevent harm). - In some embodiments, the
aircraft server 310 can also be configured to transmit at least some of the diagnostic and usage information to one or more mobile devices 336 (e.g., tablets, smartphones, notebook computers, wearable devices such as smart watches or activity trackers, etc.). For example, theaircraft server 310 can be configured to transmit the diagnostic and usage information (e.g., faults, errors, test data, usage data (e.g., usage statistics), user settings/preferences, current settings, any combination thereof, etc.) to a flight attendantmobile device 336 periodically, based upon a schedule, in response to triggering event (e.g., startup, restart, detected error/fault), and/or in response to a query/request received from themobile device 336. In embodiments, themobile device 336 can be configured with a mobile application (“App”) that provides access to the diagnostic and usage information. The diagnostic and usage information can include status information, such as, but not limited to, safety belt status (e.g., buckled or unbuckled), chair position status (e.g., upright or reclined), passenger tray status (e.g., stowed or deployed), and so forth. This allows a flight attendant to conveniently monitor passenger statuses via the flight attendant'smobile device 336. Further, the mobile device 336 (via the App) may be configured to generate an alert (e.g., warning, error/fault notification, etc.) based upon the diagnostic and usage information, for example, for errors/faults that can be corrected inflight or errors/faults or statuses (e.g., unbuckled safety belt, etc.) that require flight attendant intervention. -
FIG. 5 illustrates an example implementation of amethod 400 that employs a system for monitoring passenger chair components, such as thesystem 300 described above. In general, operations of disclosed processes (e.g., method 400) may be performed in an arbitrary order, unless otherwise provided in the claims. - The
method 400 includes collecting diagnostic and usage information from a plurality ofseat control modules 206 communicatively coupled with components (e.g.,PSU 202,PCM 204, theseat control module 206 itself, actuator(s) 214, lights and/orperipheral devices 216,passenger control unit 218, any combination thereof, etc.) of respective passenger chairs 102 (block 402). For example,IFE units 110 can be configured to collect diagnostic and usage information from theseat control modules 206 of respective passenger chairs 102 or respective groups of passenger chairs 206. - The diagnostic and usage information can be permanently or temporarily stored on an aircraft server 310 (block 404). For example, the diagnostic and usage information can be transmitted from the
IFE units 110 to theaircraft server 310, which then stores the diagnostic and usage information (e.g., in memory 314). In an embodiment, each of theIFE units 110 is configured to transmit the information collected by theIFE unit 110 to theaircraft server 310. In another embodiment, a head/master IFE unit 328 may receive diagnostic and usage information collected by theother IFE units 110 and can be configured to then transmit the diagnostic and usage information to theaircraft server 310. In yet another embodiment, theseat control modules 206 can be communicatively coupled with theaircraft server 310 and configured to transmit the diagnostic and usage information to the aircraft server 310 (i.e., without routing the information through IFE units 110). - After the diagnostic and usage information has been collected and/or stored by the
aircraft server 310, the diagnostic and usage information is transmitted to a ground server 318 (block 406). For example, theaircraft server 310 can be configured to transmit the diagnostic and usage information (e.g., faults, errors, test data, usage data (e.g., usage statistics), user settings/preferences, current settings, any combination thereof, etc.) to theground server 318 periodically, based upon a schedule, in response to triggering event (e.g., startup, restart, detected error/fault), and/or in response to a query/request received from theground server 318. - In some implementations, the
method 400 further includes generating an alert and/or instruction based on the diagnostic and usage information (block 408). For example, theground server 318 may be configured to generate an alert (e.g., warning, error/fault notification, etc.) and/or an instruction (e.g., repair instruction/message, control signal, etc.) based upon the diagnostic and usage information. - The
method 400 may further include any step or operation implied or required by the embodiments ofsystem 300 described herein. Thesystem 300 can also include any additional component or functionality expressed or implied by themethod 400. - It is to be understood that implementations of the methods according to the inventive concepts disclosed herein may include one or more of the steps described herein. Further, such steps may be carried out in any desired order and two or more of the steps may be carried out simultaneously with one another. Two or more of the steps disclosed herein may be combined in a single step, and in some implementations, one or more of the steps may be carried out as two or more sub-steps. Further, other steps or sub-steps may be carried in addition to, or as substitutes to one or more of the steps disclosed herein.
- From the above description, it is clear that the inventive concepts disclosed herein are well adapted to carry out the objects and to attain the advantages mentioned herein as well as those inherent in the inventive concepts disclosed herein. While presently preferred embodiments of the inventive concepts disclosed herein have been described for purposes of this disclosure, it will be understood that numerous changes may be made which will readily suggest themselves to those skilled in the art and which are accomplished within the broad scope and coverage of the inventive concepts disclosed and claimed herein.
Claims (18)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/135,157 US10611481B1 (en) | 2018-09-19 | 2018-09-19 | Passenger chair component monitoring system |
EP19197718.0A EP3626615B1 (en) | 2018-09-19 | 2019-09-17 | Passenger chair component monitoring system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/135,157 US10611481B1 (en) | 2018-09-19 | 2018-09-19 | Passenger chair component monitoring system |
Publications (2)
Publication Number | Publication Date |
---|---|
US20200086993A1 true US20200086993A1 (en) | 2020-03-19 |
US10611481B1 US10611481B1 (en) | 2020-04-07 |
Family
ID=67988916
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/135,157 Active US10611481B1 (en) | 2018-09-19 | 2018-09-19 | Passenger chair component monitoring system |
Country Status (2)
Country | Link |
---|---|
US (1) | US10611481B1 (en) |
EP (1) | EP3626615B1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20200317342A1 (en) * | 2019-03-27 | 2020-10-08 | Astronics Connectivity Systems & Certification Corp. | Distributed cabin network architecture |
US11495062B2 (en) * | 2019-04-02 | 2022-11-08 | The Boeing Company | Seat component fault determination and prediction |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB9909825D0 (en) * | 1998-09-08 | 1999-06-23 | Airnet Global Holdings Limited | Communications system for aircraft |
US20020138625A1 (en) * | 2001-03-21 | 2002-09-26 | David Bruner | Method and apparatus for inflight electronic commerce |
US7027767B2 (en) | 2001-12-17 | 2006-04-11 | The Boeing Company | Mobile platform local area network using direct infrared |
US7114171B2 (en) * | 2002-05-14 | 2006-09-26 | Thales Avionics, Inc. | Method for controlling an in-flight entertainment system |
CA2566382A1 (en) * | 2004-05-27 | 2005-12-15 | Thales Avionics, Inc. | System and method for remote diagnostics for an in-flight entertainment system |
US8776146B2 (en) | 2004-12-28 | 2014-07-08 | Livetv, Llc | Aircraft in-flight entertainment system including a distributed digital radio service and associated methods |
ATE554001T1 (en) | 2008-09-08 | 2012-05-15 | Thales Avionics Inc | SYSTEM AND METHOD FOR PROVIDING A LIVE MAP DISPLAY IN A VEHICLE |
US8457846B2 (en) | 2010-05-14 | 2013-06-04 | Crane Co. | Modular seat actuation control system and communication method |
DE102012217795A1 (en) * | 2012-09-28 | 2014-04-03 | Lufthansa Technik Ag | Software, communication system and method in an aircraft |
DE102012024641A1 (en) | 2012-12-15 | 2014-06-18 | Bühler Motor GmbH | Seat drive system of a vehicle |
EP3241748B1 (en) | 2016-05-06 | 2018-12-19 | Airbus Operations GmbH | Seat module with wireless communication module, vehicle seat with seat module, aircraft and method for operating a seat module |
WO2018140659A1 (en) | 2017-01-25 | 2018-08-02 | Systems And Software Enterprises, Llc | Systems architecture for interconnection of multiple cabin aircraft elements |
-
2018
- 2018-09-19 US US16/135,157 patent/US10611481B1/en active Active
-
2019
- 2019-09-17 EP EP19197718.0A patent/EP3626615B1/en active Active
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20200317342A1 (en) * | 2019-03-27 | 2020-10-08 | Astronics Connectivity Systems & Certification Corp. | Distributed cabin network architecture |
US11495062B2 (en) * | 2019-04-02 | 2022-11-08 | The Boeing Company | Seat component fault determination and prediction |
Also Published As
Publication number | Publication date |
---|---|
EP3626615B1 (en) | 2022-07-20 |
US10611481B1 (en) | 2020-04-07 |
EP3626615A1 (en) | 2020-03-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8457846B2 (en) | Modular seat actuation control system and communication method | |
EP3626615B1 (en) | Passenger chair component monitoring system | |
US10160544B2 (en) | Aircraft occupant health, safety, and comfort management | |
EP2770488A1 (en) | A passenger services system for an aircraft | |
US9533764B2 (en) | Seat device for an aircraft or spacecraft | |
US10773806B2 (en) | Seat actuation control through in-flight entertainment system | |
US11535373B2 (en) | Methods and systems for remote piloting a two-pilot aircraft for extended flights | |
EP3241748B1 (en) | Seat module with wireless communication module, vehicle seat with seat module, aircraft and method for operating a seat module | |
CA3168080A1 (en) | System and method for controlling an aircraft seat and its environment via a wireless connection | |
US9889934B2 (en) | Digital crew assist | |
EP3617070A1 (en) | Passenger tray with integrated user interface device | |
US10070372B2 (en) | Multi-mode mobile device | |
US10418021B2 (en) | Noise reduction device, noise reduction system, and noise reduction control method | |
US10507740B2 (en) | Control device for the comfort equipment of a passenger transport vehicle seat module, seat module and system for controlling comfort equipment | |
US10745146B2 (en) | Systems and methods for determination of seating system status | |
US20190190631A1 (en) | Systems and methods for pairing a plurality of wireless interfaces in a vehicle | |
US20230034020A1 (en) | Passenger seat voice recording unit | |
US20200202838A1 (en) | Noise-reduction in aircraft |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: ROCKWELL COLLINS, INC., IOWA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PHAN, THAO;UDRISTE, DANIEL;CIEMIER, CHRISTOPHER;SIGNING DATES FROM 20180918 TO 20180919;REEL/FRAME:046908/0335 |
|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |