Patent Grant
10222766
The present patent application is directed to a system and a method of operation of the system incorporating a graphical user interface on a mobile computing device that is assignable to a member of a crew (i.e., an attendant) in a vehicle cabin (also referred to herein as a “crew GUI,” “crew input/output node,” or “crew IO node”). The crew IO node provides control over one or more functions within the cabin of the vehicle. The crew member may be a flight attendant (or other crew member) and the vehicle may be an aircraft.
As should be apparent to those skilled in the art, there are a number of functions that may be controlled within the cabin of an aircraft. The functions may be divided into at least two categories: (1) functions related to environment, and (2) functions related to passenger comfort and entertainment.
Environmental functions include, but are not limited to, things such as cabin temperature, the intensity of the cabin lighting, and the degree to which the window shades are open, among other variables.
Functions related to passenger comfort include those related to actuation of a personal reading light, control over the air flow through an overhead vent, positioning of the passenger seat (i.e., upright or reclined), and a remote call for a flight attendant (i.e., a flight attendant call button).
Other functions that are associated with passenger comfort include, but are not limited to control over media type (i.e., audio and/or video), content, and volume. With respect to content, selectivity may be provided so that a passenger may select a genre of music (i.e., jazz music or pop music) or a genre of movies (i.e., comedy or drama), among other variations. As should be apparent to any passenger, individuals may control the volume of the media that has been selected.
At present, selected environmental functions typically are adjusted by the flight crew for the comfort of all passengers within the aircraft. For example, temperature typically is controlled at a central location within the aircraft cabin, via a thermostat or similar temperature control device. Similarly, the main cabin lighting in the aircraft typically is controlled via a central panel available to the flight crew. As a result, the flight crew can turn on, turn off, or dim the main lights within the aircraft cabin for all of the passengers.
As should be apparent to the airplane traveler, functions associated with passenger comfort and entertainment typically are accessible directly from the passenger's seat.
This basic operational approach to aircraft cabin functions has been employed for many years. As presently configured, the control systems for the environment and for passenger comfort and entertainment within an aircraft operate independently from one another.
Recently, a desire has developed to improve the manner in which aircraft cabin functions are controlled. Specifically, a desire has arisen to develop controls for one or more functions within the cabin of an aircraft from one or more consolidated IO nodes.
The present invention provides a GUI and a method of operation of a GUI that is available to a member of a flight crew via a mobile computing device.
In one contemplated embodiment, the crew IO node is mobile and provides control to crew members over one or more functions within an aircraft cabin, regardless of the location of the crew member within the cabin.
The present invention provides for a method of operation for a system incorporating a graphical user interface in a mobile computing device for a crew member within a cabin of an aircraft. The method includes displaying a menu for at least one controllable parameter, receiving a selection of the controllable parameter, displaying at least one control for the selected controllable parameter, receiving a control input for the selected controllable parameter, and adjusting the selected controllable parameter consistent with the control input. The controllable parameter include a plurality of controllable parameters selected from a group encompassing light intensity, light color, temperature, and the degree of openness of at least one window shade.
It is contemplated that the method also may include placing the graphical user interface into a sleep mode if selection of a controllable parameter is not received.
With respect to the method, it is contemplated that the plurality of controllable parameters also may include at least one of media type, media, content, and media volume and that the plurality of controllable parameters may be associated with at least one of the entire cabin of the aircraft, at least one zone within the cabin of the aircraft, or at least one seat within the cabin of the aircraft.
Moreover, the plurality of controllable parameters may be controllable via an interface presenting an isometric view of at least a portion of the cabin of the aircraft.
In an alternative embodiment, it is contemplated that the method may include prioritizing the control input received from the mobile computing device in relation to control inputs received from any other input device, thereby avoiding conflicts between the control inputs.
For the method, it is contemplated that light intensity, temperature, the degree of openness of the at least one window shade, and media volume may be adjustable between a predetermined minimum and a predetermined maximum. In addition, light color may be adjustable between a predetermined warm color and a predetermined cool color.
It is contemplated that the media content may include a video library, an audio library, and a map view. A map view is contemplated to encompass a global map view and a local map view.
Concerning the method, it is contemplated that the displaying of the menu for the controllable parameter includes displaying a light icon, a media icon, a thermostat icon, and a window shade icon. As such, the light icon may be one of a cabin light icon, a table light icon, and a reading light icon.
For the method of the present invention, the crew member device may be at least one of a personal computer, tablet, and smartphone.
The present invention also contemplates a system incorporating a graphical user interface in a mobile computing device for a crew member within a cabin of an aircraft. The system includes a first display for displaying at least one controllable parameter, an input for receiving a selection of the controllable parameter, a second display for displaying at least one control for the selected controllable parameter, wherein the input receives a control input for the selected controllable parameter, and a controller for adjusting the selected controllable parameter consistent with the control input. The controllable parameter includes a plurality of controllable parameters selected from a group encompassing light intensity, light color, temperature, and the degree of openness of at least one window shade.
With respect to the system, it is contemplated that the plurality of controllable parameters also may include at least one of media type, media, content, and media volume and that the plurality of controllable parameters may be associated with at least one of the entire cabin of the aircraft, at least one zone within the cabin of the aircraft, or at least one seat within the cabin of the aircraft.
In addition, with respect to the system, the plurality of controllable parameters may be controllable via an interface presenting an isometric view of at least a portion of the cabin of the aircraft.
Also concerning the system, it is contemplated that the control input received from the mobile computing device may be prioritized in relation to control inputs received from any other input device, thereby avoiding conflicts between the control inputs.
The present invention also provides for an executable computer program product providing instructions for operation of a system incorporating a graphical user interface for a mobile computing device for a crew member device within a cabin of an aircraft. The instructions include displaying a menu for at least one controllable parameter, receiving a selection of the controllable parameter, displaying at least one control for the selected controllable parameter, receiving a control input for the selected controllable parameter, and adjusting the selected controllable parameter consistent with the control input. The controllable parameter includes a plurality of controllable parameters selected from a group that may include light intensity, light color, temperature, and the degree of openness of at least one window shade.
It is contemplated that the executable computer program product will operate such that the plurality of controllable parameters also include at least one of media type, media, content, and media volume and that the plurality of controllable parameters are associated with at least one of the entire cabin of the aircraft, at least one zone within the cabin of the aircraft, or at least one seat within the cabin of the aircraft.
In addition, the program product is contemplated to function such that the plurality of controllable parameters is controllable via an interface presenting an isometric view of at least a portion of the cabin of the aircraft.
Concerning the executable computer program product, the instructions also may include prioritizing the control input received from the mobile computing device in relation to control inputs received from any other input device, thereby avoiding conflicts between the control inputs.
Still further aspects of the present invention will be made apparent from the drawings and description that follows.
The present invention will now be described in connection with the figures appended hereto, in which:
The present invention will now be described in connection with one or more embodiments. The discussion of any one embodiment is not intended to be restrictive or limiting of the present invention. To the contrary, the embodiments described are intended to be illustrative of the broad scope of the present invention.
Among other aspects, the present invention addresses controls for parameters on board an aircraft including environmental functions and functions related to passenger comfort. As noted above, environmental functions include, but are not limited to, things such as cabin temperature, the intensity of the cabin lighting, and the degree to which the window shades are open, among other variables. Functions related to passenger comfort include those related to actuation of a personal reading light, control over the air flow through an overhead vent, positioning of the passenger seat (i.e., upright or reclined), and a remote call for a flight attendant (i.e., a flight attendant call button). Other functions that are associated with passenger comfort include, but are not limited to control over media type (i.e., audio and/or video), content, and volume. With respect to content, selectivity may be provided so that a passenger may select a genre of music (i.e., jazz music or pop music) or a genre of movies (i.e., comedy or drama), among other variations. Individuals may control the volume of the media that has been selected.
As should be apparent, and as will be made more apparent in the discussion that follows, the labels “environment” and “passenger comfort” when applied to specific functions that are controllable in an aircraft are merely provided to assist with an understanding of the present invention. Use of either of the labels is not intended to be limiting, as the labels are not considered to be mutually exclusive of one another or of other functions that are not highlighted herein. For example, control over the degree to which the window shades are opened qualifies as control over an environmental function and also over aspects of passenger comfort. The lights in the aircraft belong to the same, crossover category.
With respect to the present invention, the terms “front” (or “fore”), “rear” (or “aft”), left (or “port”), and right (or “starboard”) are used in the conventional fashion when referring to an aircraft. These conventions refer to the front, rear, left, and right sides of an aircraft as determined by its normal, forward direction of travel.
In addition, reference is made to members of the flight crew on board the aircraft. The term “flight crew” is intended to be generic to any member of the flight crew, including the pilot, co-pilot, and/or flight attendants. In other words, the term “flight crew” is intended to refer to persons other than passengers on board the aircraft.
The term “bulkhead” is used in the discussion of the present invention. A bulkhead is wall that is disposed within the aircraft. A bulkhead may or may not be a structural component of the aircraft.
It is contemplated that the crew IO node (or crew GUI) of the present invention may be provided on a corporate or private aircraft. In other words, it is contemplated that the present invention may be employed in an aircraft that typically has limited seating by comparison with a commercial, passenger aircraft. While corporate, business, or personal aircraft encompass the primary focus of the crew IO node of the present invention, the present invention is not limited just to such aircraft. To the contrary, the present invention may be employed in any aircraft, including commercial passenger aircraft, without departing from the scope of the present invention.
In addition, while the crew IO node of the present invention is contemplated to be employed on an aircraft, it is noted that the present invention may be employed in any other suitable environment. For example, the present invention may be practiced on a passenger car of a train, on board a ship, or any other suitable environment that should be apparent to those skilled in the art.
It is contemplated that the crew IO node of the present invention will be used in conjunction with a distributed architecture 10, one embodiment of which is illustrated in
The term “processor” is intended to broadly encompass any device capable of executing machine-readable instructions. In other words, the term “processor 14” is intended to refer to any device or component that processes instructions and data. As an example, semiconductor chips within a computer are considered to fall within the definition of the term “processor 14.”
While it is contemplated that the processor 14 will be a single component of the distributed architecture 10, the distributed architecture 10 is not intended to be limited solely to such a construction. The processor 14 may include multiple devices that are separate from one another, but cooperate together to process data and execute instructions. For example, the processor 14 may include a semiconductor processing chip and/or any other peripheral devices that support the operation of the semiconductor processing chip. Alternatively, the processor 14 may encompass processing chips that are located in separate systems, but which are operatively connected to provide the desired functionality.
As also illustrated in
While the distributed architecture 10 is described in terms of a CPU 12, a processor 14, and a controller 16 (among other components), it is noted that this configuration is not intended to be illustrative of the breadth of the present invention. The configuration is not intended to exclude any possible server/client configurations. For example, the CPU 12 may be a server on which a client is resident. The controller 16 may be the client. In another configuration, the CPU 12 may be a server that provides access to an independent client. In still another configuration, the CPU 12 may be a router.
As should be apparent, there are many appellations that may be applied to the components comprising the distributed architecture 10. Those variations and equivalents are intended to be encompassed by the scope of the present invention.
As illustrated in
It is noted that the distributed architecture 10 contemplated for use with the crew IO node of the present invention also may be connected to other systems and processors on board the aircraft. For example, the distributed architecture 10 may receive input from a flight computer on board the aircraft. These other input devices are not illustrated for simplicity. It is noted, however, that other inputs may be provided to the distributed architecture 10, as should be apparent to those skilled in the art.
The distributed architecture 10 is intended to be specific to the passengers and flight crew on an aircraft. As a result, the CPU 12 is contemplated to connect to at least two IO nodes: (1) a passenger IO node 20 and (2) a crew IO node 22. The passenger IO node 20 receives input from and provides output to the passenger. The crew IO node 22 receives input from and provides output to members of the flight crew. Both the passenger IO node 20 and the crew IO node 22 connect to the controller 16, through which selected inputs and outputs are directed.
The passenger IO node 20 is contemplated to encompass any suitable input/output device that may be available to a passenger. Similarly, the crew IO node 22 is intended to encompass any suitable input/output device that may be available to a member of the flight crew. In other words, while the present invention will be described in connection with specific devices, the present invention is not intended to be limited thereby. Other devices may be provide or substituted for the devices described herein without departing from the scope of the present invention.
In addition, as will be made more apparent in the discussion that follows, the passenger IO node 20 and the crew IO node 22 are contemplated to provide overlapping functionality. Therefore, the discussion of a particular functionality with respect to one IO node 20, 22 does not preclude the same functionality from being provided via the other of the IO nodes 20, 22.
As illustrated in
Additionally, the communication lines are illustrated as two-way communication channels. While depicted as two-way communication channels, it is noted that one-way communication channels may be employed without departing from the scope of the present invention. In addition, it is also contemplated that the communication channels 24 may encompass one or more busses that channel multiple channels of communication along a single communication line 24.
The distributed architecture 26 is directed to a location-oriented approach rather than a person-oriented approach, as detailed in connection with the distributed architecture 10. The person-oriented approach that is employed for the distributed architecture 10 encompasses an architecture where an IO node is associated with an individual, such as a passenger or a member of the flight crew. The location-oriented approach for the distributed architecture 26 encompasses an architecture that relies, at least in part, on IO nodes that are placed at specific locations with the aircraft.
As will be made apparent in discussion that follows, there is an overlap between the first distributed architecture 10 and the second distributed architecture 26.
As illustrated in
As illustrated in
As suggested by the nomenclature employed, the IO nodes 28, 30, 32, 34 are provided at specific locations in the aircraft. The person-specific IO nodes 20, 22 are contemplated to be portable devices that are associated with individuals and, as such, are not associated with any fixed structure within the aircraft.
As illustrated in
It is noted that the window IO node 34 and the table IO node 32 are but two examples of nodes where limited space is available for control inputs and/or outputs. The present invention should not be understood to be limited to the nodes 32, 34 that are shown and described herein.
To facilitate the discussion of the distributed architectures 10, 26, a top view of an aircraft 36 is illustrated in
As illustrated in
The cabin 48 includes a cockpit 50, a galley 52, and a passenger area 54. The cabin 48 also includes a forward lavatory 56, a first passenger seating area 58, a second passenger seating area 60, a third passenger seating area 62, a first bedroom 64, a second bedroom 66, and an aft lavatory 68.
The first passenger seating area 58 is positioned adjacent to the galley 52 and the forward lavatory 56. The first passenger seating area 58 is immediately aft of the door 70 that provides ingress into and egress out of the aircraft 36. A first bulkhead 72 separates the area adjacent to the door 70 from the first passenger seating area 58.
The first passenger seating area 58 is defined by one passenger seat 74 and a stowable table 76. The passenger seat 74 is contemplated to be a reclining seat. However, the passenger seat 74 need not recline. The stowable table 76 is contemplated to be stowable in a side compartment adjacent to the passenger seat 74. As required by applicable aviation laws, the table 76 must be stowed for taxi, take-off, and landing.
It is noted that the first passenger seating area 58 may be reserved for one or more crew members and, therefore, be understood to be a crew seating area 58. Since the type of individual that uses the seating area 58 is not critical to operation of the present invention, the seating area 58 will be referred to herein as the first passenger seating area 58. It is also noted that, while other seating areas are indicated as being for passengers, crew members may use these areas together with the passengers.
A second bulkhead 78 separates the first passenger seating area 58 and forward lavatory 56 from the second passenger seating area 60.
The second passenger seating area 60 includes four passenger seats 74 that are positioned on opposite sides of a central aisle. Two seats 74 face one another across a table 76 on the right side 44 of the aircraft 36. Similarly, two seats 74 face one another across a stowable table 76 on the left side 42 of the aircraft.
The third passenger seating area 62 is defined by six passenger seats 74, a stowable table 76, and a stowable conference table 80. Two seats 74 face one another across the stowable table 76 on the right ride 44 of the aircraft 36. Four seats 74 face one another (in two pairs) across a stowable conference table 78. As illustrated, when the tables 76, 80 are deployed, they are contemplated to form a single conference table that extends across the width of the cabin 48.
As is apparent from
The first bedroom 64 is separated from the third passenger seating area 62 by a third bulkhead 82. The first bedroom 64 includes a divan 84 on the left side 42 of the aircraft 36 and a cabinet 86, such as a media cabinet, on the right side 44 of the cabin 48. It is contemplated that the divan 84 will function both as a couch (or a sofa) and a bed, depending upon its use or configuration.
The second bedroom 66 is separated from the first bedroom 64 by a fourth bulkhead 88. The second bedroom 66 includes a divan 84 on the right side 44 of the aircraft 36. A seat 74 and stowable table 76 are provided on the left side 42 of aircraft 36. Also on the left side 42 is a cabinet 90, which may be provided with a media center, including a monitor or a television.
A fifth bulkhead 92 separates the second bedroom 66 from the rear lavatory 68.
It is noted that the fuselage 46 includes a plurality of windows 94.
In addition, at least four monitors 96 (i.e., video output screens) are provided in the aircraft 36 at various locations. The monitors 96 are contemplated to be positioned to provide video information and entertainment to the passengers in the aircraft 36. It is contemplated that entertainment also may be provided to the passengers via entertainment devices that are associated with the passenger seats 74.
As illustrated, the cabin 48 also includes several side ledges 98 that extend along the length of selected ones of the passenger seating areas 58, 60, 62. Where they are provided, the side ledges 98 are disposed between the passenger seat 74 and the wall of the fuselage 46. As is apparent from
It is noted that the term “side ledge” is intended to encompass other furniture within the cabin 48 of the aircraft 36 in addition to the typical side ledge 98 that is identified in
As should be apparent to those skilled in the art, the configuration for the cabin 48 of the aircraft 36 that is provided in
With renewed reference to the distributed architectures 10, 26, either architecture 10, 26 (or any variant thereof) may be employed onboard the aircraft 36. For purposes of the discussion herein, the aircraft 36 includes the second distributed architecture 26.
In this architecture, the passenger IO node 20 is contemplated to be a mobile electronic device, as discussed above. Mobile electronic devices include, but are not limited to, portable computers, tablets, and smartphones. As will be made apparent from the discussion that follows, it is contemplated that the passenger IO node 20 will be capable of receiving and storing a software program, such as an “app.” The app may be specific to a particular aircraft or airline, as required or desired. The app is contemplated to provide the software needed for proper interface with the controller 16 for operation of the distributed architecture 26. In other words, the software resident on the passenger IO node 20 is contemplated to be configured to provide input to the CPU 12 and to receive output from the CPU 12.
The crew IO node 22 also is contemplated to be a mobile device, such as a portable computer, tablet, or smartphone. As with the passenger IO node 20, the crew IO node 22 is contemplated to be provided with a suitable app (or resident software) for interface with the CPU 12.
Where the mobile IO nodes 20, 22 are tablets, it is contemplated that the tablets 20, 22 will be provided with the delivery to the customer of the aircraft 36. In this embodiment, when a passenger boards the aircraft 36, the passenger will be assigned one of the mobile devices for use during the flight. Similarly, when the flight crew embarks on the aircraft 36, members of the flight crew will be assigned one of the mobile devices.
Alternatively, it is contemplated that a passenger may bring his or her own mobile device on board the aircraft 36. If so, the passenger (and/or crew member) may be prompted to download suitable software (i.e., the app) for interface with the controller 16 prior to boarding the aircraft. Similarly, the members of the flight crew may bring their own mobile devices on board the aircraft 36. If so, members of the flight crew also may be prompted to download suitable software on the personal device. In a further contemplated embodiment, the passenger (and/or crew member) may be prompted to download suitable software after boarding the aircraft, for example. It is noted that the apps (i.e., the software) downloaded by the passenger and the crew may be the same or may be separate apps, as required or as desired.
As also discussed above, the aircraft 36 may include additional IO nodes.
As noted above, the crew IO node 22 is the focus of the present invention. While the crew IO node 22 is contemplated to be embodied is an electronic tablet device with a touch-sensitive surface, the crew IO node 22 may be any other suitable alternative device without departing from the scope of the present invention. Moreover, while the present invention is described as a mobile device, meaning that it is not structurally secured to the aircraft 36, the crew IO node 22 may be affixed in the aircraft 36 without departing from the scope of the present invention.
It is noted that the crew IO node 22 and the passenger IO node 20 that is contemplated to work together with the crew IO node 22 share similar functionality. More specifically, the crew IO node 22 is contemplated to include all of the functionality available on the passenger IO node 20 and also to include additional functionality that is specific to members of the flight crew and operation of the aircraft 36. As a result, the passenger IO node 20 is discussed below, with the understanding that a discussion of the crew IO node 22 encompasses the same functionality.
It is noted that the term “user” is employed to refer to passengers and flight crew members, since both categories of persons are contemplated to be users of the present invention. As such, where the term “passenger” or “flight crew member” are used, the term is not intended to exclude use by any other user, as required or as desired.
In this illustrated embodiment, the passenger IO node 20 is disposed on a retractable stand 134 that extends from the side ledge 98 adjacent to the passenger seat 74. The passenger IO node 20 is removably disposed in the stand 134. In other words, the passenger IO node 20, as embodied in the tablet 132, is not integrally connected to the stand 134. A table 76 also is illustrated in this view, to provide context for the present invention.
As should be apparent, the stand 134 need not extend from the side ledge 98. It is contemplated that the stand 134 may extend from one of the arm rests on the passenger seat 74. Alternatively, the stand 134 may extend from the table 76. As should be apparent to those skilled in the art, the exact location where the stand 134 is positioned is not critical to the present invention.
As noted above, functions associated with passenger comfort fall into two general categories: (1) media functions and (2) cabin-related environmental functions. As such, the passenger IO node 20 is contemplated to provide an interface to the user that includes these two groups of functions.
For purposes of the discussion of the present invention, it is noted that the designation “tablet 130” may refer to either the passenger IO node 20 or the crew IO node 22. Both IO nodes 20, 22 may be embodied in a tablet. For this reason, the designation “tablet 130” is applied to both nodes 20, 22. It is noted, as discussed in greater detail below, that the crew IO node 22 includes control over functionality that may not be accessed or controlled by a passenger.
In the illustrated embodiment, the media submenu 138 includes four options: (1) a video icon 142, (2) a music icon 144, (3) a television icon 146, and (4) a map view icon 148. Each of these separate options is accessible by touching the surface 150 of the crew IO node 22. As should be apparent, the icons 142-148 that are available via the media submenu 138 are merely representative of the types of media that may be accessible by that menu.
The cabin submenu 136 includes nine options: (1) a cabin lighting icon 152, (2) a window shade icon 150, (3) an audio icon 152, (4) a thermostat icon 154, (5) a video icon 156, (6) a presets icon 158, a table light icon 164, (8) a reading light icon 166, and (9) a seat icon 168. Each of these separate options also is available by touching the surface 150 of the crew IO node 22. As with the media submenu 138, the icons 152-168 that are included in the cabin submenu 140 are intended to be exemplary of the types of icons that may be available through the cabin submenu 140.
As should be apparent, the media submenu 138 and the cabin submenu 140 do not present mutually exclusive functionalities. Some functions with the cabin 48 of the aircraft 36 may be accessed from either submenu 138, 140. In other words, the menu trees for both submenus 138, 140 are contemplated to be interrelated and redundant.
The main menu 136 also includes a flight status bar 170, which extends along a top edge of the main menu 136. The flight status bar 170 provides a visual indication of the total duration of the flight, time elapsed since take off, and time remaining until landing. As should be apparent, the flight status bar 170 may provide additional information that may be of interest to the passenger.
The four icons in the media submenu 138 provide access to the four types of entertainment that are available to the passenger on board the aircraft 36.
The video icon 142 provides access to a listing of the video entertainment available to the passenger on board the aircraft 36 as well as other functionality, as discussed below.
The audio icon 144 provides access to a listing of the audio (i.e., music) entertainment available to the passenger on board the aircraft 36. Other functionality also may be made available via the audio icon 144, as discussed herein.
The television icon 146 provides access to a listing of the television programming that may be available to the passengers. Television programming is contemplated to encompass pre-recorded content. However, it is contemplated that television programming also may include real-time television programming for aircraft 36 that are equipped to receive television programming during flight.
In one contemplated embodiment, the map view icon 148 is contemplated to provide a view of the geographic position of the aircraft 36. As such, the crew and/or passenger may identify where the aircraft 36 is in its flight plan. The map view icon 148 also is contemplated to permit access to local geographic maps so that the crew and/or passenger may locate geographic points of interest, for example, at the destination location.
The cabin lighting icon 152 is intended to provide access to control over the main lighting in the cabin 48 of the aircraft 36. The main lighting in the cabin 48 is the overhead lighting and is the lighting in the general passenger area of the aircraft 36. The main cabin lighting in the aircraft 36 is distinguishable from other lighting that may be provided, such as a personal reading light, positioned over the passenger's seat 74 or a table reading light positioned over a table 76, 80 within the aircraft 36.
The window shade icon 154 provides control over one or more of the window shades that cover the windows 94 in the aircraft 36. The window shade icon 154 provides control over the degree to which the window shades in the aircraft 36 are opened or closed.
With respect to the window shades, it is noted that the window shades may be of any particular type without departing from the scope of the present invention. For example, the window shades may be made from a sheet of material that moves (via a motor, for example) in front of the window to block the transmission of light therethrough. Alternatively, the window shades may be made from an electrochromic material. Electrochromic materials respond to signals by altering their color and/or opacity.
The audio icon 156 is similar to the audio icon 144, by providing access to the audio menu, as discussed further herein.
The thermostat icon 158 provides access to a menu that permits the crew and/or passenger to control the temperature within the cabin 48 of the aircraft 36.
The video icon 160 is similar to the video icon 142. This icon also provides access to the functionality of the video menu, as discussed further herein.
The presets icon 162 provides access to predetermined settings related to the cabin 48 of the aircraft 36. By accessing the presents icon 162, the crew and/or passenger may select from several preset environments within the aircraft to facilitate activities such as sleep, meetings, or entertainment viewing, as discussed below.
The table light icon 166 provides control over a light that may be positioned above a stowable table 76 or a conference table 80, as may be provided in the cabin 48 of the aircraft 36.
The reading light icon 164 provides access to control over one or more reading lights above the passenger seats 74 in the cabin 48.
The seat icon 168 provides control over the comfort position of one or more of the seats 74 in the aircraft 36. Via the seat icon 168, the user may adjust the seat 74 between fully upright and fully reclined positions. The term “user” is used herein to refer to any person that has access to the functionality provided by the present invention on board an aircraft 36.
The video submenu 172 includes at least four separate regions, each of which provides access to different, related functionality.
As shown, the video submenu 172 includes a media bar 174 that provides access to the different types of media that are available to the user. Since the user originally selected the video icon 142, the video submenu 172 defaults to the video programming available to the user. The media bar 174 permits the user to change to a different media selection without having to return to the main menu 136.
The video submenu also includes an available devices section 176, a search bar section 178, and a library section 180.
The available devices section 176 provides a listing of the various video devices (i.e., the monitors 96) that are accessible on the aircraft. By selecting one or more of the icons associated with the available video devices 96, the user may select which of the monitors 96 will display the selected video content. For example, the user may elect to have a selected movie played on a nearby monitor 96 as well as a remote monitor in one of the bedrooms 64, 66. In this manner, the user may watch a movie from the user's seat 74 while his or her children watch the same movie in their bedroom 64, for example.
The search bar section 178 is provided so that the user may input search words to locate specific video media within the library on board the aircraft 36.
The library section 180 provides a listing of all of the video content that is available to the user.
If the user accesses the audio icon 144 on the main menu 136, the user will be directed to the audio submenu 192. In this illustration, the audio submenu 192 encompasses audio programs that are available to the user. However, the audio submenu 192 should not be understood to be limited solely to music content.
The audio submenu 192 includes at least four separate regions, each of which provides access to different, related functionality.
As shown, the audio submenu 192 includes the media bar 174 that provides access to the different types of media that are available to the user. Since the user originally selected the audio icon 144, the audio submenu 192 defaults to the audio programming available to the user. The media bar 174 permits the user to change to a different media selection without having to return to the main menu 136.
The audio submenu 192 also includes an available devices section 176, a search bar section 178, and a library section 180.
Submenus of the audio submenu 192 are contemplated to operate in the same manner as the viewing options GUI 186, discussed above. Specifically, audio programming may be played on one or more devices or within one or more zones in the aircraft 36. Accordingly, further discussion of this functionality is not repeated here.
If real time television stations are not available, the television submenu 194 is contemplated to default to a pre-recorded television shows library. In such a case, the television submenu 194 is contemplated to operate in the same manner as the video submenu 172 or the audio submenu 192.
Submenus of the television submenu 194 are contemplated to operate in the same manner as the viewing options GUI 186, discussed above. Specifically, television programming may be played on one or more devices or within one or more zones in the aircraft 36. Accordingly, further discussion of this functionality is not repeated here.
Two controls over the cabin lighting are provided via the cabin lights GUI 202. The user is provided with control over the intensity (or brightness) of the cabin lights via the intensity control menu 210. Cabin light intensity is contemplated to be controllable from a minimum of 0 lumens to a predetermined maximum. The user also may be provided with control over the color of the cabin lights via a color control menu 212. Color refers to the “warmness” of the light, as should be apparent to those skilled in the art. Warmer light includes more yellow light elements. Cool light includes a bluer appearance. It is contemplated that the user may be provided control over the coolness or warmness of the light, as indicated by the color control menu 212. Both the intensity control menu 210 and the color control menu 212 are contemplated to be presented as slider bars, with slider elements 214, 216, that assist the passenger to appreciate where the controls are in relation to the extremes.
The cabin lights GUI 202 also includes a window shades up icon 214 and a window shades down icon 216. These icons provide control over the degree of openness of one or more of the window shades in the cabin 48. The table light icon 164 also is provided to the user. As should be apparent, other controls for other lighting also may be provided on the cabin lights GUI 202. Control over any lights in the cabin 48 is contemplated to include control over the intensity of the light and the warmness or coolness of the light. With respect to the warmness (i.e., the yellow or amber content) or coolness (i.e., the blue content) of the light, it is contemplated that the user will adjust the color of the light between two standard colors for the light. As should be apparent, the colors may be set according to standards for lighting or they may be selected by the aircraft owner or user, as appropriate.
In an alternate embodiment, it is contemplated that the user may be provided with even greater control over the color of the lights in the aircraft 36. It is contemplated, for example, that the user may be able to control the red, green, and blue (“RGB”) values for the lights in the cabin 48. If so, RGB controllers are anticipated to be displayed on the tablet 130. As should be apparent, for control over the color of the lights, it is contemplated that the lights will be light emitting diodes (“LEDs”), where control over the saturation of the RGB values for the LEDs is permissible. As should be apparent, other light sources may be employed without departing from the scope of the present invention.
Control over the degree of openness of the window shades is contemplated to be provided via a control bar 222 with a slider 224. The slider 224 is contemplated to provide control over the window shades from a fully closed to a full opened condition.
As noted above, the crew IO node 22 is contemplated to include all of the functionality discussed in connection with the passenger IO node 20. In addition, the crew IO node 22 is contemplated to include functionality that is specific to members of the flight crew and the operation of the aircraft 36.
In the paragraphs that follow, the additional functionality of the crew IO node 22 is discussed. As noted above, the crew IO node 22 also is contemplated to be embodied in a tablet 130.
It is noted that the crew main menu 252 need not be provided with the crew cabin submenu 254. Functionality associated with the icons 256-264 that are in the crew cabin submenu 254 may be provided via a separate menu that is available only to the crew via the crew IO node 22.
The scheduling GUI 266 also includes an events recorder 270 that records the events that occur during the flight. In the illustrated example, a flight attendant call 272 was made early in the flight. The flight attendant call 272, which was made by one of the passengers via the passenger IO node 20, for example, is recorded in the events recorder 270 to keep a running log of what occurred during the flight.
The scheduling GUI 266 also may include an altitude record 274 that provides a visual output of the vertical position of the aircraft 36 during the flight. The altitude record 274 may be provided with specific logic to prevent certain activities from occurring if those activities do not comply with applicable aviation guidelines. For example, if movies may be played only after the aircraft 36 reaches a particular altitude, the crew IO node 22 may be programmed to prevent the playing of any media until such time that the aircraft 36 has reached a suitable altitude.
The method 288 begins at step 290. From the start 290, the method 288 proceeds to step 292 where the method 288 optionally receives input activating the user interface associated with the crew IO node 22. As noted above, this includes, but is not limited to, activation of the tablet 130.
It is contemplated that the tablet 130 might not provide any display until activated. As noted above, a user may activate the tablet 130 by touching the touch-sensitive surface 150 thereof. Alternatively, a switch (not shown) may be provided to turn on or turn off the tablet 130.
Separately, it is contemplated that the tablet 130 may operate such that the tablet 130 remains in a constant on mode of operation. In this contemplated mode of operation, the tablet 130 may provide a display at all times during flight.
From optional step 292, the method 288 proceeds to step 294, where a menu for controllable parameters is displayed. The menu includes, but is not limited to, a display of the cabin light icon 152, the window shade icon 154, the audio icon 156, the thermostat icon 158, the video icon 160, the presets icon 162, the table light icon 164, the reading light icon 166, and the seat icon 168. As discussed above, each of these icons is associated with a controllable parameter on board the aircraft 36. As also noted, the crew main menu 252 is contemplated to include additional icons associated with the crew cabin submenu 254.
The method 288 then proceeds to step 296, where a selection of one of the controllable parameters is received by the method 288. As noted above, the input may be received when a person taps on a particular icon 152-168 and/or 256-264. In an alternative contemplated operation, the user may use a swiping motion to access the menus associated with the icons 152-168 and/or 256-264. Specifically, the user may use a swiping motion, by dragging his or her finger across the surface 150 of the tablet 130, to navigate through the different menus associated with each of the icons 152-168 and/or 256-264.
If no input is received at step 296, the method 288 proceeds to an optional step 298 where the tablet 130 is placed into a sleep mode. In the sleep mode, the tablet 130 may go dark. Alternatively, it may continue to display the screen last selected by a user. In still another embodiment, the tablet 130 may default to the crew main menu 252.
If the user selects one of the controllable parameters by selecting one of the icons 152-168 and/or 256-264, the method 288 proceeds to step 300. At step 300, the method 288 displays the controls appropriate for the selected controllable parameter. For example, if the table light icon 164 is selected, the light intensity menu 210 may be displayed. A color light menu 212 also may be displayed as another lighting option for the table light.
Once the control(s) are displayed, the method 288 proceeds to step 302. At step 302, the method 288 receives control input(s) from the user to adjust one or more of the controllable parameters in the cabin 48 of the aircraft 36.
After receiving the input at step 302, the method 288 proceeds to step 304, where the selected, controllable parameters are adjusted according to the input provided by the user.
After step 304, the method 288 is contemplated to return to step 294 and display the crew main menu 252.
As noted above, it is contemplated that the tablet 130 will operate after being awakened by a person's touch. In keeping with this mode of operation, it is contemplated that the tablet 130 will enter into a sleep mode (or go dark) after the expiry of a predetermined time period. For example, if the tablet 130 has not received tactile input for a period of 2 minutes, the tablet 130 will be instructed to enter into the sleep mode where it will await the next command.
As illustrated in
After being awakened at step 310, the method 306 proceeds to step 312, where the tablet 130 displays a menu of parameters that are controllable within the cabin 48 of the aircraft 36. As noted above, the controllable parameters may be divided into two separate categories including, but not limited to, a media submenu 138, a cabin submenu 140, and a crew submenu 254. As should be apparent, the media submenu 138, the cabin submenu 140, and the crew submenu 254 are contemplated embodiments of the present invention but should not be understood to be limiting of the present invention.
The method 306 then proceeds to step 314, where the method 306 awaits receipt of the selection of media controls. If the user selects an option under the media submenu 138, the method 306 proceeds to the media subroutine 316, which is illustrated in
If the user does not select one of the options available in the media submenu 138, the method 306 proceeds to step 320. If the user selects one of the options associated with cabin parameters, the method 306 proceeds to the cabin subroutine 322 via the connector 324. The cabin subroutine 322 is illustrated in
It is noted that steps 314 and 320 are illustrated in series. However, these steps 314, 320 need not occur in the order presented. Moreover, the steps 314, 320 need not occur in series. It is contemplated that the steps 314, 320 may operate in parallel or in any other suitable order without departing from the scope of the present invention.
If the user does not select one of the cabin parameters in step 320, the method 306 proceeds to step 326, where the method 306 places the tablet 130 into a sleep mode. As noted, this step 326 is optional. It is contemplated that the tablet 130 may not enter a sleep mode. Instead, it is contemplated that the tablet 130 may remain in a constant on condition during operation of the aircraft 36.
The media subroutine 316 starts at step 328, where the method 306 awaits selection of video control(s). If video control(s) are selected, the method 306 proceeds to the video subroutine 330 via the connector 332. The video subroutine 330 is illustrated in
If the user does not select the video control(s), the method 306 proceeds to step 334, where the method 306 awaits selection of the audio control(s). If the user selects the audio controls(s), the method 306 proceeds to the audio subroutine 336 via the connector 338. The audio subroutine 336 is illustrated in
If the user does not select the audio control(s) in step 334, the method 306 proceeds to step 340, where the method 306 awaits selection of the television control(s). If the user selects the television control(s), the method 306 proceeds to the television subroutine 342 via the connector 344. The television subroutine 342 is illustrated in
If the user does not select the television control(s), the method 306 proceeds to step 346, where the method 306 awaits selection of the map view control(s). If the user selects the map view control(s), the method 306 proceeds to the map subroutine 348 via the connector 350.
As should be apparent, while the steps 328, 334, 340, 346 are illustrated in a particular order, the present invention does not require that the steps 328, 334, 340, 346 be executed in this order. The steps 328, 334, 340, 346 may be executed in any order without departing from the scope of the present invention. In an alternative contemplated embodiment, the steps 328, 334, 340, 346 may proceed in parallel.
If the user does not select the map view control(s), the method 306 proceeds to step 352, where the method 306 optionally places the tablet 130 into sleep mode. From step 352, the method 306 returns to step 310 via the connector 354.
The cabin subroutine 322 connects to the portion of the method 306 illustrated in
The cabin subroutine 322 then proceeds to step 356, where the subroutine 322 authenticates if the user of the tablet 130 is a flight crew member. If the person operating the tablet 130 is a flight crew member, the method 306 proceeds to step 358. At step 358, the method 306 makes flight crew control(s) available to the flight crew member. It is noted that, if the user is authenticated as a flight crew member, the tablet 130 transitions to a crew IO node 22 and additional functionality becomes available to the flight crew member, as noted above.
In connection with the activation of flight crew options at step 358, the method 306 makes available the functionality designated by the connector 360. The connector 360 provides access to the flight crew subroutine 362, which is illustrated in
At step 364, the method 306 awaits receipt of the selection of cabin light control(s). The cabin light control(s) are made available if the user accesses the cabin light icon 152. If the method 306 receives the cabin light control(s), the method 306 proceeds to the cabin light subroutine 366 via the connector 368. The cabin light subroutine 366 is illustrated in
If the method 306 does not receive any selection of cabin light control(s), the method 306 proceeds to step 370. At step 370, the method awaits input of window shade control(s). The window shade control(s) are available through activation of the window shade icon 154, for example. If the method 306 receives input for the window shade control(s), the method proceeds to the window shade subroutine 372 via the connector 374. The window shade subroutine 372 is illustrated in
If the method 306 does not receive inputs for the window shade control(s), the method 306 proceeds to step 376, where the method 306 awaits input for audio control(s). If the user accesses the audio control(s), the method 306 proceeds to the audio subroutine 336 via the connector 338. The audio subroutine 336 is illustrated in
If the method 306 does not receive any selection of audio control(s) in step 376, the method proceeds to step 378, where the method 306 awaits selection of the thermostat controls. If the method 306 receives a selection of the thermostat control(s), such as by receiving a selection of the thermostat icon 158, the method 306 proceeds to the thermostat subroutine 380, which is illustrated in
If the method 306 does not receive a selection of the thermostat control(s), the method proceeds, via the connector 384, to step 386, which is illustrated in
If the method receives a selection of video control(s) at step 386, the method 306 proceeds to the video subroutine 330, which is illustrated in
If the method 306 does not receive the selection of video control(s) at step 386, the method proceeds to step 392. At step 392, the method awaits selection of the presets control(s) via the tablet 130. The user may access the presets control(s) by selecting the presets icon 162, for example. If the user accesses the presets control(s), the method 306 transitions to the presets subroutine 394 via the connector 396. The presets subroutine 394 is illustrated in
If the method 306 does not receive any input indicating the selection of the presets control(s), the method proceeds to step 398. At step 398, the method 306 determines if the user provides input selecting the table light control(s). If so, the method 306 proceeds to the table light subroutine 400, which is illustrated in
If the method 306 does not receive any input from the user that the user has selected the table light icon 164, the method 306 proceeds to step 404 where the method 306 awaits input of the selection of the reading light control(s). If the user selects the reading light control(s) by accessing the reading light icon 166, for example, the method proceeds to the reading light subroutine 406 via the connector 408. The reading light subroutine 406 is illustrated in
If the method 306 does not receive any input from the user selecting the reading light control(s), the method 306 proceeds to step 410. At step 410, the method 306 awaits input of the selection of the seat control(s). The seat controls may be accessed by selecting the seat icon 168. If the method 306 receives the selection of the seat control(s), the method 306 proceeds to step 412 via the connector 414. The seat subroutine is illustrated in
If the method 306 does not receive input regarding the seat, the method 306 proceeds to step 416, where the method 306 optionally places the tablet 130 into a sleep mode. From step 416, the method 306 returns to step 310 via the connector 354.
It is noted that the steps 364, 370, 376, 378, 386, 392, 398, 404, 410 need not be executed in the order described in connection with
The video subroutine 330 starts at step 418, which follows from the connector 332 that is illustrated in
At step 418, the method 306 displays the video library 180, which is contemplated to encompass all of the video files that are accessible by the user. The video files may be stored in the database 18, for example. While the video files may be displayed in any particular order and according to any particular sorting parameter(s), it is contemplated that the video files will be presented in alphabetical order.
From step 418, the method 306 proceeds to step 420 where the method 306 determines if there has been a selection of specific video content.
If specific video content has been selected, the method 306 proceeds to step 422. At step 422, the selected video content is played to the user until the video content is exhausted. In other words, at step 422, the video content is anticipated to be played from the beginning to the end of the video file. As should be apparent, control options may be provided to the user to start, stop, advance, and retard the play back of the video file at any point during the playback of the video content. As indicated above, the video content may be provided in the form of an electronic file, a file read from a storage medium (i.e., a digital video disk), etc.
After the video file is played, the method 306 returns to step 310 via the connector 354. Since the user has control over the playback of the video content, the method 306 may return to the step 310 at any time after the user elects to stop the playback, as appropriate.
If the user does not select a particular video from the video library 180, the method proceeds to step 424, where the method 306 awaits the user's selection of search controls. The search controls and search terms may be entered, for example, in the search GUI 182.
If the user enters search parameters, the method 306 proceeds to step 426 where the method 306 displays search control(s). In this step 426, the search controls and search terms may be entered, for example, in the search GUI 182. Searching is contemplated to be performed based on words, phrases, or other suitable search parameters.
At step 428, the method 306 receives the search parameter(s) from the user.
From step 428, the method 306 proceeds to step 430, where the method 306 displays the result(s) of the search to the user.
After the search results are displayed, the method returns to step 420, where the user is permitted to select one of the results from the results that are displayed at step 430.
If the method 306 does not receive the selection of search control(s) at step 424, the method proceeds to step 432, where the method 306 receives a selection of volume controls. If the user does not select the volume controls, the method returns to step 310 via the connector 354. If the user does select the volume controls, the method 306 proceeds to step 434, where the volume controls are displayed to the user.
At step 436, the method 306 receives input for the volume controls.
The method 306 then proceeds to step 438, where the method 306 adjusts the volume according to the input provided by the user.
After step 438, the method 306 returns to step 310 via the connector 354.
The audio subroutine 336 starts at step 440, which follows from the connector 338 that is illustrated in
At step 440, the method 306 displays the audio library 180 in the audio submenu 192, which is contemplated to encompass all of the audio files that are accessible by the user. The audio files may be stored in the database 18, for example. While the audio files may be displayed in any particular order and according to any particular sorting parameter(s), it is contemplated that the audio files will be presented in alphabetical order.
From step 440, the method 306 proceeds to step 442 where the method 306 determines if there has been a selection of specific audio content.
If specific audio content has been selected, the method 306 proceeds to step 444. At step 444, the selected audio content is played to the user until the audio content is exhausted. In other words, at step 444, the audio content is anticipated to be played from the beginning to the end of the audio file. As should be apparent, control options may be provided to the user to start, stop, advance, and retard the play back of the audio file at any point during the playback of the audio content. As indicated above, the audio content may be provided in the form of an electronic file, a file read from a storage medium (i.e., a compact disk, digital audio disk, or mp3 file, etc.).
After the audio file is played, the method 306 returns to step 310 via the connector 354. Since the user has control over the playback of the audio content, the method 306 may return to the step 306 at any time after the user elects to stop the playback, as appropriate.
If the user does not select a particular audio from the audio library 180, the method proceeds to step 446, where the method 306 awaits the user's selection of search controls. The search controls and search terms may be entered, for example, in the search GUI 192.
If the user enters search parameters, the method 306 proceeds to step 448 where the method 306 displays search control(s). In this step 448, the search controls and search terms may be entered, for example, in the search GUI 192. Searching is contemplated to be performed based on words, phrases, or other suitable search parameters.
At step 450, the method 306 receives the search parameter(s) from the user.
From step 450, the method 306 proceeds to step 452, where the method 306 displays the result(s) of the search to the user.
After the search results are displayed, the method returns to step 442, where the user is permitted to select one of the results from the results that are displayed at step 452.
If the method 306 does not receive the selection of search control(s) at step 446, the method proceeds to step 454, where the method 306 receives a selection of volume controls. If the user does not select the volume controls, the method returns to step 310 via the connector 354. If the user does select the volume controls, the method 306 proceeds to step 456, where the volume controls are displayed to the user.
At step 458, the method 306 receives input for the volume controls.
The method 306 then proceeds to step 460, where the method 306 adjusts the volume according to the input provided by the user.
After step 460, the method 306 returns to step 310 via the connector 354.
The television subroutine 342 of the method 306 of the present invention starts with a display of the television submenu 194 at step 462. One contemplated embodiment of the television submenu 194 is shown in
After the display of the television library in step 462, the method 306 proceeds to step 464, where the method 306 awaits receipt of the selection of television content. Television content may include the selection of a particular television channel or pre-recorded television content. If the method 306 receives selected television content from the user, the method 306 proceeds to step 466, where the selected television content is played. After the selected television content is played, the method 306 returns to step 310 via the connector 354.
If the method 306 does not receive a selection of television content, the method proceeds to step 468 where the method receives a selection of search controls. If the method 306 does not receive a selection of search controls, the method 306 returns to step 310 via the connector 354.
If the method 306 receives a selection of search controls, the method 306 proceeds to step 470 where the method displays search controls.
At step 472, the method 306 receives input of search parameters. The user may search for specific content, for a genre of television programs, etc.
After receiving the search parameters, the method 306 proceeds to step 474, where the method displays the search results. The user may then select content from the displayed results. As such, the method returns to step 464 from step 474.
The method 306 proceeds to step 478 where the method 306 awaits receipt of a selection of a local map view. If the method 306 does not receive any selection of a local map view, the method 306 proceeds to step 480.
At step 480, the method 306 awaits selection of local map search parameters via the local map GUI 200. The local map GUI 200 may be configured to receive search parameters associated with the destination of the flight, for example. The user may wish to search for restaurants, museums, and other points of interest at the destination location for the flight, for example.
If the method 306 does not receive a selection of local map search parameters at step 480, the method 306 returns to step 310 via the connector 354.
If the method 306 receives a selection of local map search parameters at step 480, the method 306 proceeds to step 482. At step 482, the method 306 displays the results for the local map search.
The cabin lights subroutine 366 begins at step 484, which is connected to step 364, for example, via the connector 368. At step 484, the method 306 displays the controls for cabin light intensity and/or color. As noted above, the intensity of the cabin lights may be altered to provide a desirable brightness for the lights in the cabin 48. In addition, it is contemplated that the color of the cabin lights may be adjusted between “warm” and “cool” tones.
After step 484, the method 306 proceeds to step 486 where the method receives controls from the user over the cabin lights. The control inputs may be over light intensity and/or color. Controls may be possible via a suitable touch-sensitive control bar, as discussed above.
At step 488, the method 306 adjusts the cabin light intensity and/or color based on the inputs received from the user.
The window shade subroutine 372 begins at step 490, which follows the connector 374. At step 490, the method displays the controls for input of the degree to which one or more of the window shades is to be opened. The control may be by a control slider as discussed above.
At step 492, the method receives control input from a user regarding the degree to which the window shades are to be opened on the aircraft 36. As noted above, the control may be provided over a single window shade or a group of window shades.
At step 494, the method 306 adjusts the degree to which the window shades are opened based on the input provided by the user.
At step 496, the method 306 displays the control inputs for controlling the temperature on board the aircraft 36. The thermostat controls are contemplated to include a control bar a slider, but the controls are not limited to this arrangement.
At step 498, the method 306 receives input for the thermostat controls. Specifically, the method 306 receives temperature inputs for one or more of the regions within the cabin 48 of the aircraft 36.
At step 500, the method 306 adjusts the temperature within the cabin 48 of the aircraft 36 according to the control inputs provided by the user. The method then returns to step 310 via the connector 354.
This portion of the method 306 has already been described.
The presets subroutine 394 begins at step 502 where the method 306 displays the control inputs for the presets. One contemplated embodiment for this display is the presets GUI 234 that is illustrated in
At step 504, the method 306 receives input for the control presets. As discussed above, one of the presets may include a lighting level and environmental controls that are suitable for viewing a meeting. Another preset may include environmental controls for assisting with sleep.
At step 506, the method 306 adjusts that cabin parameters according to the inputs provided by the user.
The table light subroutine 400 begins at step 508, where the method 306 displays the controls for the table light. The controls may include a control bar and slider as previously described. The controls may include one or both of intensity of the table light and the color, as discussed above.
From step 508, the method 306 proceeds to step 510 where the method 306 receives input regarding the intensity and/or color of the table light. The input may be provided by the user.
At step 512, the method 306 adjusts the table light according to the input received at step 510.
At step 514, the controls for the reading light are displayed by the method 306 of the present invention. The controls are contemplated to encompass a control bar with a slider as discussed herein. Of course, other control schemes may be employed without departing from the scope of the present invention.
At step 516, the method 306 receives input concerning the light intensity and/or color.
At step 518, the method 306 adjusts the light intensity and/or color in accordance with the inputs received at step 516.
The seat subroutine 412 starts at step 520, where the method 306 displays the controls that are associated with the seat input(s).
The method proceeds to step 522, where the method 306 awaits a request from a user to change his or her seat assignment. If the method 306 receives a request for a passenger to change his or her seat assignment, the method 306 proceeds to step 524. At step 524, the method changes the seat assignment for the passenger according to the input received. A change in seat assignment includes a change in any preferences and settings previously provided for the seat of origin to the changes seat. Accordingly, it is contemplated that, if a passenger changes his or her seat 74, the comfort parameters previously entered will be transferred to the passenger's new seat 74.
If the method 306 does not receive a request for a passenger to change seats, the method 306 proceeds to step 526. At step 526, the method receives input from the user to adjust the seat. If the method 306 does not receive input to adjust the seat 74, the method proceeds to step 310 via the connector 354. If the method 306 receives input to adjust the seat, the method 306 proceeds to step 528. At step 528, the method 306 adjusts the seat 74 according to the input provided. After the seat 74 is adjusted, the method 306 returns to step 310 via the connector 354.
The crew cabin subroutine 362 begins at step 530, where the crew main menu is displayed. The crew main menu may be configured consistently with the crew main menu 252 that is illustrated in
After the display step 530, the crew cabin subroutine 362 proceeds to step 532, where the method 306 awaits input regarding scheduling associated with the functionality that is controllable within the cabin 48 of the aircraft 36.
If a flight crew member accesses an input function for the crew cabin subroutine 362 at step 532, the method proceeds to step 534 where the scheduling GUI 266 is displayed. Through this display, the crew member may control various functions within the cabin 48 of the aircraft 36.
It is contemplated that input may be provided in an interactive manner via the scheduling GUI 266 that is illustrated in
As with other subroutines described herein, after step 534, it is contemplated that the method 306 may return to step 310 via the connector 354.
If no-one selects the scheduling inputs at step 532, the method 306 proceeds to step 536, where the method awaits selection of inputs regarding notes. If a member of the flight crew accesses this feature, the method 306 proceeds to step 538, where the method 306 displays the notes GUI 276, such as the one illustrated in
The notes GUI 276 is provided so that the flight crew may enter specific notes regarding a flight. As indicated in
After notes are added, the method 306 is contemplate to return to step 310 via the connector 354.
If the flight crew does not select the notes GUI 276, the method 306 is contemplated to proceed to step 540. At step 540, the method 306 awaits receipt of a selection of the report icon 260.
If the report icon 260 is selected, the method proceeds to step 542, where the report GUI 280 is displayed. Once contemplated embodiment of the report GUI 280 is provided in
As before, at the conclusion of step 542, the method 306 is contemplated to return to step 310 via the connector 354.
If the method 306 does not receive a selection of the reports input(s), the method 306 proceeds to step 544, where the method awaits receipt of the selection of control panel inputs. Control panel inputs are accessible be selecting the control panel icon 262, for example.
If a flight crew member accesses the control panel icon 262, the method 306 proceeds to step 546 where the method displays the control panel GUI 282. One example of the control panel GUI 282 is provided in
The control panel GUI 282 is contemplated to provide an interface that permits the flight crew member to turn on or turn off specific components on the aircraft 36. For example, the flight crew member may wish to turn on the hot water heater that provides hot water to the lavatories on the aircraft 36.
After the flight crew member provides any input for the controllable parameters that are available at step 546, the method 306 is contemplated to return to step 310 via the connector 354.
If no selection is made for the control panel, the method 306 is contemplated to proceed to step 548, where the method 306 awaits selection of the passenger manifest inputs.
If the passenger manifest inputs are accessed, such as via the passenger manifest icon 264, the method 306 proceeds to step 550.
At step 550, the passenger manifest GUI 286 is displayed. The passenger manifest GUI 286 is contemplated to provide an interactive menu so that the flight crew member may access and enter personal information about the persons on board the aircraft.
After receipt of any entries at step 550, the method 306 is contemplated to return to step 310 via the connector 354.
If the method 306 does not receive any selection of inputs at steps 532, 536, 540, 544, 548, the method 306 is contemplated to return to step 310 via the connector 354.
As should be apparent from
As discussed above, inputs provided by any of the IO nodes 20, 22 and 28-34 are first provided to the controller 16. The reason for this is simple: the controller 16 provides overall control for the functions that are available to passengers in the cabin 48. Without a centralized control, it is possible that passengers might issue instructions that are contrary to one another. The controller 16 may be programmed to address these conflicts or issue an alarm when conflicts arise.
As noted above, it is contemplated that the controller 16 will incorporate a command hierarchy that will resolve any conflicts between the various inputs received from the various nodes 20, 22, 28, 30, 32, 34. The command hierarchy may be based on the status of the person (i.e., crew versus passenger) or based on the location of the IO node (i.e., window IO node 34 versus bulkhead IO node 28). It is also noted that the command and control functions need not be incorporated solely in the controller 16 but may be incorporated into other features without departing from the scope of the present invention.
As also noted above, the present invention contemplates reliance on an isometric view of the cabin 48 of the aircraft 36. The isometric view permits a user to select specific controllable features and zones within the aircraft 36. For example, the user may select one of the passenger seating areas 58, 60, 62 over which control is to be asserted. Alternatively, the user may select an individual seat 74 over which controls are to be asserted. Still further, by selecting a suitable icon from an isometric view of the cabin 48 of the aircraft 36, the user may assert control over one or more of the monitors 96 within the aircraft 36. The isometric view of the cabin 48 of the aircraft 36 provides an easily understood interface for a user to direct inputted commands and assert control over one or more controllable parameters within the cabin 48 of the aircraft 36.
As noted above, the present invention is not intended to be limited solely to the embodiment(s) described herein. To the contrary, those skilled in the art should appreciate that the present invention may be embodied in one or more variations and equivalents to the embodiment(s) described herein. The present invention is intended to encompass those variations and equivalents.
This United States Non-Provisional Patent Application relies for priority on U.S. Provisional Patent Application Ser. No. 61/759,159, filed on Jan. 31, 2013, the entire contents of which are incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4501013 | Sato | Feb 1985 | A |
| 5555458 | Large | Sep 1996 | A |
| 6249913 | Galipeau et al. | Jun 2001 | B1 |
| 6343127 | Billoud | Jan 2002 | B1 |
| 6448907 | Naclerio | Sep 2002 | B1 |
| 6988246 | Kopitzke et al. | Jan 2006 | B2 |
| 7114171 | Brady, Jr. et al. | Sep 2006 | B2 |
| 7500716 | Guerin et al. | Mar 2009 | B2 |
| 7509587 | Kopitzke et al. | Mar 2009 | B2 |
| 7878586 | Kneller et al. | Feb 2011 | B2 |
| 7908158 | Stirlen et al. | Mar 2011 | B2 |
| 8037500 | Margis et al. | Oct 2011 | B2 |
| 8065463 | Porath et al. | Nov 2011 | B2 |
| 8082569 | Brady, Jr. et al. | Dec 2011 | B2 |
| 8380393 | Ohtomo | Feb 2013 | B1 |
| 8613385 | Hulet et al. | Dec 2013 | B1 |
| 20010023499 | Wakahara | Sep 2001 | A1 |
| 20020022896 | Dugan | Feb 2002 | A1 |
| 20030132345 | Lehmann | Jul 2003 | A1 |
| 20040139467 | Rogerson et al. | Jul 2004 | A1 |
| 20040142658 | McKenna | Jul 2004 | A1 |
| 20040145612 | Kopitzke et al. | Jul 2004 | A1 |
| 20050001838 | Gregorio et al. | Jan 2005 | A1 |
| 20050002198 | Blechschmidt | Jan 2005 | A1 |
| 20050018172 | Gelfond et al. | Jan 2005 | A1 |
| 20050039305 | Chirumbolo | Feb 2005 | A1 |
| 20050185399 | Beermann et al. | Aug 2005 | A1 |
| 20050121978 | McAvoy | Sep 2005 | A1 |
| 20050280524 | Boone | Dec 2005 | A1 |
| 20060030311 | Cruz | Feb 2006 | A1 |
| 20060045107 | Kucenas et al. | Mar 2006 | A1 |
| 20060092129 | Choquet et al. | May 2006 | A1 |
| 20060099959 | Staton | May 2006 | A1 |
| 20060155429 | Boone et al. | Jul 2006 | A1 |
| 20070042772 | Salkini | Feb 2007 | A1 |
| 20070061847 | Callahan et al. | Mar 2007 | A1 |
| 20070107277 | Simms et al. | May 2007 | A1 |
| 20070141899 | Saini | Jun 2007 | A1 |
| 20070179737 | Kalokitis | Aug 2007 | A1 |
| 20070236926 | Guard et al. | Oct 2007 | A1 |
| 20080055836 | Lamoree | Mar 2008 | A1 |
| 20080104642 | Galipeau | May 2008 | A1 |
| 20080144158 | Stavaeus et al. | Jun 2008 | A1 |
| 20080157997 | Bleacher et al. | Jul 2008 | A1 |
| 20080230653 | Mitchell et al. | Sep 2008 | A1 |
| 20080234893 | Mitchell et al. | Sep 2008 | A1 |
| 20090079705 | Sizelove et al. | Mar 2009 | A1 |
| 20090083805 | Sizelove et al. | Mar 2009 | A1 |
| 20090127078 | Hostmann et al. | Mar 2009 | A1 |
| 20090109036 | Schalla | Apr 2009 | A1 |
| 20090112638 | Kneller | Apr 2009 | A1 |
| 20090113494 | Weidel | Apr 2009 | A1 |
| 20090119431 | Porath et al. | May 2009 | A1 |
| 20090206070 | Ortner et al. | Aug 2009 | A1 |
| 20090249408 | Smallhorn | Oct 2009 | A1 |
| 20090288123 | Havlovick et al. | Nov 2009 | A1 |
| 20090319902 | Kneller | Dec 2009 | A1 |
| 20100060736 | Shi et al. | Mar 2010 | A1 |
| 20100060739 | Salazar | Mar 2010 | A1 |
| 20100064327 | Lynch et al. | Mar 2010 | A1 |
| 20100070089 | Harrod et al. | Mar 2010 | A1 |
| 20100159879 | Salkini et al. | Jun 2010 | A1 |
| 20100176632 | Alford et al. | Jul 2010 | A1 |
| 20100187354 | Helfrich | Jul 2010 | A1 |
| 20100193633 | Budinger et al. | Aug 2010 | A1 |
| 20100313146 | Nielsen | Dec 2010 | A1 |
| 20110004832 | Canal et al. | Jan 2011 | A1 |
| 20110082616 | Small et al. | Apr 2011 | A1 |
| 20110126242 | Cline et al. | May 2011 | A1 |
| 20110160937 | Caillaud | Jun 2011 | A1 |
| 20110162015 | Holyoake et al. | Jun 2011 | A1 |
| 20110164429 | Heym et al. | Jul 2011 | A1 |
| 20110174926 | Margis et al. | Jul 2011 | A1 |
| 20120060524 | Al-Ali | Mar 2012 | A1 |
| 20120110517 | Sparks et al. | May 2012 | A1 |
| 20120130547 | Fadell et al. | May 2012 | A1 |
| 20120131504 | Fadell et al. | May 2012 | A1 |
| 20120132746 | Sizelove | May 2012 | A1 |
| 20120254932 | Hudson et al. | Oct 2012 | A1 |
| 20130005336 | Ayotte | Jan 2013 | A1 |
| 20130027954 | Boomgarden et al. | Jan 2013 | A1 |
| 20130063340 | Mondragon et al. | Mar 2013 | A1 |
| 20130093220 | Pajic | Apr 2013 | A1 |
| 20130161971 | Bugno et al. | Jun 2013 | A1 |
| 20130185662 | Quattrocolo et al. | Jul 2013 | A1 |
| 20130235000 | Lee et al. | Sep 2013 | A1 |
| 20130290902 | Martin et al. | Oct 2013 | A1 |
| 20140067208 | Klappert et al. | Mar 2014 | A1 |
| 20140085337 | Velten et al. | Mar 2014 | A1 |
| 20140109080 | Ricci | Apr 2014 | A1 |
| 20140239677 | Laib et al. | Aug 2014 | A1 |
| 20140309868 | Ricci | Oct 2014 | A1 |
| 20140324299 | Sorensen | Oct 2014 | A1 |
| 20150058777 | Graumann et al. | Feb 2015 | A1 |
| 20150253750 | Eronen et al. | Sep 2015 | A1 |
| 20150261379 | Kneuper et al. | Sep 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 102006006363 | Aug 2007 | DE |
| 102007043379 | Apr 2009 | DE |
| 102011112944 | Mar 2013 | DE |
| 2003182351 | Jul 2003 | JP |
| WO 0052550 | Sep 2000 | WO |
| WO 2009062974 | May 2009 | WO |
| Entry |
|---|
| Frequent Flying, “Vintage Airline Seat Map Eastern Air Lines Boeing 727-100”, Jan. 18, 2012,2 pages, downloaded http:/ /frequentlyflying.boardingarea.com/vintage-airline-seat -map-eastern-air-lines-boeing-727-100/. |
| Rockwell Collins, “Bombardier CES H D” brochure, 147-1351-000 10/11, © 2011 Rockwell Collins Inc, 8 pages. |
| Rosen Aviation, “Ultra CMS Technical Manual,” Revision Date Mar. 11, 2010, Copyright 2010, Document No. 102350 Rev A, 28 pages. |
| Honeywell “Ovation Select 200C Personal Control Unit” brochure, A60-1 090-000-000, Mar. 2009, © 2009 Honeywell International Inc., 4 pages. |
| U.S. Appl. No. 14/164,858, filed Jan. 27, 2014, Distributed Architecture for a System and a Method of Operation of the System Incorporating a Graphical User Interface Controlling Functions in a Vehicle Cabin. |
| U.S. Appl. No. 14/164,932, filed Jan. 27, 2014, System and a Method of Operation of the System Incorporating a Graphical User Interface in a Bulkhead of a Vehicle Cabin. |
| U.S. Appl. No. 14/165,004, filed Jan. 27, 2014, System and a Method of Operation of the System Incorporating a Graphical User Interface in a Side Ledge of a Vehicle Cabin. |
| U.S. Appl. No. 14/165,032, filed Jan. 27, 2014, System and a Method of Operation of the System Incorporating a Graphical User Interface on a Mobile Computing Device for a Passenger in a Vehicle Cabin. |
| U.S. Appl. No. 14/165,068, filed Jan. 27, 2014, System and Method of Operation of the System Incorporating a Graphical User Interface on a Mobile Computing Device for a Member of a Flight Crew in a Vehicle Cabin. |
| International Search Report and Written Opinion dated Jul. 25, 2016, for International Patent Application No. PCT/IB2015/0059051. |
| International Search Report and Written Opinion dated Jul. 27 2016, for International Patent Application No. PCT/IB2015/0059049. |
| International Search Report and Written Opinion dated Aug. 2, 2016, for International Patent Application No. PCT/IB2015/0059050. |
| International Search Report and Written Opinion dated Aug. 3, 2016, for International Patent Application No. PCT/IB2015/0059052. |
| Airliners.Net, “A320 FWD Flight Attendant Panei” Tech Ops Forum, Mar. 17, 2007, 7 pages, downloaded from: http://www.airliners.net/aviationforums/tech_ops/read.main/186678/. |
| Airbus, “US Airways Flight 1549 A320-214 N106US Landing on the Hudson River”, report submitted to the NTSB on Jan. 15, 2009, 54 pages. |
| Elo Touch Solutions, “Touch is in the air” (describing and depicting a Flight Attendant Panel), Google date: Oct. 3, 2006, 2 pages, downloaded from: http://www.elotouch.com/Solutions/Transportation/air.asp. |
| Heller, Christoph et al., “Spectrum Sensing for Congitive Wireless Applications inside Aircraft Cabins,” 31st IEEE/AIAA Digital Avionics Systems Conference (DASC), Oct. 14-18, 2012, pp. 7E2-1-7E2-9. |
| International Search Report and Written Opinion dated Sep. 23, 2016, for International Patent Application No. PCT/IB2015/0059053. |
| Airbus 319 seat map (8/120 configuration), United Airlines, Copyright 2015 United Airlines, Nov. 6, 2015. |
| Airbus, Single Aisle Technical Training manual Maintenance Course: T1 Lights, select pages (pp. 1, 2, 4-6, 16-20, back cover), Oct. 2005. |
| JetPhotos.Net, Airbus A320-232 Bulkhead photo, United Airlines, Serial # 503, Mar. 5, 2003, 2 pages. Downloaded from: http//www.jetphotos.net/photo/109418. |
| SeatGuru, Bulkheads explained: pros and cons, Internet Archive record of https://www.seatguru.com/articles/bulkheads.php from Jan. 30, 2012. |
| Woods, Martin; The A318: enhancing the A320 Family, in FAST29, Airbus Technical Digest, Dec. 2001, pp. 8-13. |
| YouTube Screen Shots, Enhanced Fap—Airbus 320, uploaded by cesar soto on Sep. 12, 2007 at https://www.youtube.com/watch?v-IW8ql_3NUjg. |
| U.S. Appl. No. 14/165,032, filed Jan. 4, 2016. |
| U.S. Appl. No. 14/164,932, filed Apr. 18, 2016. |
| Elo Touch Solutions, “In Flight Entertainment/Cabin Management” (http://www.elotouch.com/Solutions/Transportation/air.asp for a description of an early (2006) “Flight Attendant Panel (FAP)”), 2006. |
| Heller et al., “Spectrum Sensing for Cognitive Wireless Applications Inside Aircraft Cabin,” 31st Digital Avionics Systems Conference, Oct. 14-18, 2012. |
| http://www.airliners.net/aviationforums/tech_ops/read.main/186678/2007 description of (the mounting and operation of) the Airbus Flight Attendant Panel (FAP), Mar. 17-21, 2007. |
| Number | Date | Country | |
|---|---|---|---|
| 20160062327 A1 | Mar 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61759159 | Jan 2013 | US |
