Patent Description:
A number of preferences of cockpit displays, particularly a navigation display, are pilot/user selectable. Modern navigation displays include a multitude of data layers including radar weather, uplink weather, ground level mapping information, aeronautical information, flight plan information, sensor information and various other possible layers/categories of information. Many layers include a plurality of user selectable display preferences such as whether to display a particular display feature and the form of the display feature. Generally, display settings are selected during flight, which places a time and cognitive burden on the flight crew. The ideal display settings may be phase of flight and crew dependent, which could lead to more changes of display settings throughout a particular flight, which further increases the burden on the flight crew.

Hence, it is desirable to provide systems and methods that allow pilot customization of display preferences having greater automation in setting up and executing the display preferences so as to reduce the workload of the pilot during the flight. Yet further, it would be desirable for pilot customization of display and non-display cockpit features that are semi- or fully automatically executed. Furthermore, other desirable features and characteristics of the present invention will become apparent from the subsequent detailed description and the appended claims, taken in conjunction with the accompanying drawings and the foregoing technical field and background.

Documents cited during prosecution include <CIT>; <CIT>; and <CIT>.

Aspects and embodiments of the invention are defined in the appended claims. Methods and systems are disclosed herein for generating a user and phase of flight dependent cockpit display. The methods and systems generate a display for a display device using display settings included in a user profile and a current phase of flight. The display settings include preferences defining a range of a map to be displayed that are different for different phases of flight, and preferences defining a level of declutter of a map to be displayed that are different for different phases of flight.

Systems and methods disclosed herein provide a user profile adjustable cockpit allowing pilot user experience to be enhanced by semi or automatic execution of pilot preferences for each phase of flight. Cockpit display and other settings may be configured by a pilot prior to take-off. At least some of the settings are set up so as to be different depending upon the phase of flight. An on-board computer system detects when the phase of flight changes and automatically changes the cockpit settings and, optionally, issues a prompt to confirm one or more of the cockpit settings that are subject to change. The, preferences include a range of a map of a navigation display and, optionally, the form and status of a vertical situation display (VSD) and/or a level of declutter of a map of the navigation display are set up so as to differ between phases of flight. Decluttering of the phase of flight includes removal of entire layers or categories of features of the map and/or removal of sub-features of a given layer or category of features of the map. Numerous examples of layers of map features and sub-features of the layers are described herein. Many other cockpit features may be pilot defined and vary depending on phase of flight, as will be described further herein.

The user profile adjustable cockpit disclosed herein enables pilots to customize, save and call up preferred cockpit settings including navigation and other displays. The cockpit settings may be defined in a user computer such as a tablet computer, a smartphone computer, a laptop, a desktop computer and other computing device. The user computer may be a portable device. The settings defined in the user computer are uploaded to an on-board computer system for implementation of the display and other cockpit settings. A database of user profiles that have been set up in this way may be stored in a cloud computer for access by the user computer and/or the on-board computer system.

In embodiments, the systems described herein provide a capability for airlines to define standard operating procedures (SOP) related cockpit settings and to push fleetwide default settings. For example, airline specific cockpit settings may be included as a default when creating a flight plan, which may be adjusted by a user/pilot. The default cockpit settings may be stored in the cloud databases of user profiles.

In exemplary embodiments described herein, the cockpit, e.g. navigation display, settings and selections are saved in a user profile file. The cockpit settings can be loaded by recalling the profile from the user computer or from the cloud computer. The flight crew can also save settings into a user profile in-flight and subsequently restore their desired preferences for the current or subsequent flights by simply selecting the user profile. Once the user profile is selected and loaded, preferences (such as navigation display preferences) are enabled and executed when phase of flight and/or other flight conditions are met.

<FIG> is a block diagram of an exemplary user profile adjustable cockpit system <NUM>. The system <NUM> enables cockpit features to be automatically adjusted to preferences set in a user profile file. In a particular example, navigation display settings are adjusted to preferences set in the user profile. At least some of the preferences are phase of flight dependent and adjustments are made depending on a currently detected phase of flight. In accordance with the embodiment of <FIG>, the system <NUM> includes a cockpit system <NUM> located in a cockpit of an aircraft <NUM>. The system <NUM> includes a cloud computer <NUM> and a user computer <NUM>.

In embodiments, the aircraft <NUM> includes a cockpit, one or more engines, and a fuselage. The aircraft <NUM> can be a multicopter (or rotary-wing), fixed-wing or a tilt-wing aircraft. The aircraft <NUM> can be an airplane or a helicopter or other aircraft with powered rotors, such as cyclogyros/cyclocopters and tiltrotors. The aircraft <NUM> may be combustion fuel, fully electric or hybrid powered and can include jet engines or propellers. The aircraft <NUM> may be a VTOL (Vertical Take-Off and Landing) or eVTOL (electric VTOL).

In the exemplary embodiment of <FIG>, the cockpit system <NUM> includes an on-board computer system <NUM>, one or more display devices <NUM> and cockpit environment actuators <NUM>. The on-board computer system <NUM> is loaded with at least one user profile that has phase dependent cockpit preferences set by a user. Preferences of the one or more display devices <NUM> are adjusted based on current phase of flight determined by the on-board computer system <NUM> and the loaded at least one user profile. In some embodiments, other cockpit environment features are adjusted by the on-board computer system <NUM>, via the cockpit environment actuators <NUM>, based on the loaded user profile and, optionally, based on the phase of flight.

The on-board computer system <NUM> includes a flight management system <NUM>, a display computer <NUM>, an on-board database of user profiles <NUM>, a user interface <NUM>, and a cockpit environment control module <NUM>. In embodiments, the on-board computer system <NUM>, the cloud computer <NUM> and the user computer <NUM> include processors <NUM>, <NUM>, <NUM> that implement functions of the user profile adjustable cockpit system <NUM> of <FIG> and steps of the methods <NUM>, <NUM> of <FIG> and <FIG> according to example embodiments of the present disclosure. The processors <NUM>, <NUM>, <NUM> can include any suitable processing device, such as a microprocessor, microcontroller, integrated circuit, logic device, or other suitable processing device. One or more memory device(s) are included in the various computers of <FIG> and include one or more computer-readable media, including, but not limited to, non-transitory computer-readable media, RAM, ROM, hard drives, flash drives, or other memory devices. The one or more memory device(s) can store information accessible by the processors <NUM>, <NUM>, <NUM>, including one or more computer program(s), which include computer-readable instructions that can be executed by the processors <NUM>, <NUM>, <NUM>. The instructions can be any set of instructions that, when executed by the processor <NUM>, <NUM>, <NUM>, cause the processors <NUM>, <NUM>, <NUM> to perform operations for providing automated (or semi-automated) cockpit settings adjustments as described herein. The instructions can be software written in any suitable programming language or can be implemented in hardware.

In various embodiments, the FMS <NUM>, in cooperation with a navigation system (not shown) and a navigation database (not shown), provides real-time flight guidance for the aircraft <NUM>. The FMS <NUM> is configured to compare the instantaneous position and heading of the aircraft <NUM> with the prescribed flight plan data for the aircraft <NUM>. To this end, in various embodiments, the navigation database supports the FMS <NUM> in maintaining an association between a respective airport, its geographic location, runways (and their respective orientations and/or directions), instrument procedures (e.g., approach procedures, arrival routes and procedures, takeoff procedures, and the like), airspace restrictions, and/or other information or attributes associated with the respective airport (e.g., widths and/or weight limits of taxi paths, the type of surface of the runways or taxi path, and the like). Accordingly, in various embodiments, the FMS <NUM> may be a source for the real-time aircraft state data of the aircraft <NUM>. Based on a flight plan entered into the FMS <NUM> by a pilot through the user interface <NUM> and/or from an automated application, a computer of the FMS calculates the distances and courses between all waypoints in the entered route. During flight, the FMS provides precise guidance between each pair of waypoints in the route, along with real-time information about aircraft course, groundspeed, distance, estimated time between waypoints, fuel consumed, and fuel/flight time remaining (when equipped with fuel sensor(s)) and other information. Of particular relevance to the present disclosure is that the FMS <NUM> provides information on a current phase of flight of the aircraft <NUM> based at least partly on the current location of the aircraft <NUM> and the flight plan. The phase of flight data provided by the FMS <NUM> allows the processor <NUM> to retrieve the appropriate phase of flight dependent cockpit settings from the on-board database of user profiles <NUM> and to output instructions to adjust display and/or other cockpit environment settings based on the retrieved phase of flight dependent cockpit settings. In additional or alternative embodiments, the phase of flight is determined other than by the FMS <NUM>. In one example, wheel weight sensors can indicate take-off and touchdown, which would allow take-off and arrival flight phases to be determined. An oceanic flight phase could be determined from oceanic images from a camera.

In embodiments, the user interface <NUM> provides input to one or more system(s) of the aircraft <NUM>. The user interface <NUM> includes any device suitable to accept input from a user for interaction with the systems of the aircraft <NUM>. For example, the user interface <NUM> includes one or more of a keyboard, joystick, multi-way rocker switches, mouse, trackball, touch screen, touch pad, data entry keys, a microphone suitable for voice recognition, and/or any other suitable device. The user interface <NUM> allows a user (e.g. a pilot or other member of the flight crew) to manage loading of a flight plan from the user computer <NUM> including the user profiles as to cockpit preferences. The user interface <NUM> may allow a user to enter adjustments to the cockpit settings that have been loaded and to cause saving of the changes. Yet further, the user interface <NUM> allows a user to respond to one or prompts concerning whether new cockpit settings should be automatically executed when the aircraft <NUM> is transitioning between phases of flight.

The on-board database of user profiles <NUM> provides a local storage of one or more user profiles for use by the on-board computer system <NUM> to determine cockpit settings during different phases of flight. The on-board database of user profiles <NUM> is stored on memory (not shown) of the on-board computer system <NUM>, which has been described above. The on-board database of user profiles <NUM> may include user profiles (to be described further below) of the current flight crew. In some embodiments, the on-board database of user profiles <NUM> is more extensive and includes a record of flight crew members that have previously operated on the aircraft <NUM> and uploaded a user profile. In some embodiments, the one or more user profiles in the on-board database of user profiles <NUM> is uploaded from the cloud computer <NUM> via a global network. In other embodiments, the one or more user profiles in the on-board database of user profiles <NUM> is uploaded from the user computer <NUM> via a local network connection (e.g. a WiFi network of the aircraft <NUM>), Near-Field Communication (NFC), Bluetooth, other wireless connection or a cabled connection. In yet further embodiments, the user profile is included in the on-board database of user profiles <NUM> by a historical upload from a past flight or by direct creation of the user profile via the user interface <NUM>.

The on-board computer system <NUM> may retrieve a list of user profiles from the cloud computer <NUM>, the on-board database of user profiles <NUM> or from the user computer <NUM> for display to the user via the display device <NUM>. The user may select the user profile to be used for the current flight via the user interface <NUM>. The user may need to enter a password or code in order to load the user profile. In other embodiments, the selection of the user profile is made automatically when a user is identified by the on-board computer system <NUM> by facial recognition technology, by detection of an electronic device of the user (e.g. an electronic flight bag (EFB) device), by the user logging in to the on-board computer system <NUM>, etc..

The display computer <NUM> receives data concerning the phase of flight from the FMS <NUM> (or other source) and also receives a selected user profile from the on-board database of user profiles <NUM>. The user profile has at least some display settings that are phase of flight dependent. The currently applicable display settings are extracted from the user profile based on the current phase of flight and the display computer <NUM> adjusts the currently executed display settings based on the extracted display settings. The display computer <NUM> may invoke a display settings update process continuously, intermittently or only when a change of phase of flight is detected. Various display settings may be defined in the user profile and adjusted by the display computer <NUM> in dependence on phase of flight, as will be described more fully below. In examples, the display settings include preferences as to defining a range of a map to be displayed that are different for different phases of flight and preferences defining a level of declutter of a map to be displayed that are different for different phases of flight. The display computer <NUM> generates various types of displays (e.g. PFD, navigation display, vertical display, etc) using the updated display settings and outputs the displays to the display devices <NUM> for presentation to the user. The cockpit environment control module <NUM> receives the user profile from the on-board database of user profiles <NUM> and optionally the phase of flight data from the FMS <NUM> or other source when there is flight dependency on the non-display based cockpit settings. The cockpit environment control module <NUM> outputs instructions to the cockpit environment actuators <NUM> for adjusting cockpit features. In one example, cockpit lighting may be changed through lighting control actuators included in the cockpit environment actuators <NUM>. Cockpit lighting may be phase of flight dependent. In other examples, seat distance relative to an instrument panel, seat height, seat angle and/or other seat features may be adjusted by seat motors included in cockpit environment actuators <NUM>.

The processor <NUM> is described in greater detail above. The processor <NUM> is shown as a separate component from the display computer <NUM>, the cockpit environment control module <NUM> and the FMS <NUM> for conceptual reasons. Separate processors may be included in each of the flight management system <NUM>, the display computer <NUM> and the cockpit environment control module <NUM> or a central processor <NUM> may be provided as shown. Further, although the display computer <NUM> and the cockpit environment control module <NUM> are illustrated as being separate features of the on-board computer system <NUM>, they may be integrated together into a single computer or module.

In embodiments, the display device <NUM> (or plural display devices <NUM>) includes a head down display (HDD), a head up display (HUD), a wearable HUD, a portable display or any combination thereof. The display device <NUM> may be a VSD, a navigation display, a PFD or any combination thereof. The display device <NUM> receives display data generated by the display computer <NUM>, which has been generated based on the currently active display settings. Of particular relevance to the present disclosure is a navigation display <NUM> including a lateral navigation view including a range ring (described further below) and a map and a VSD that can be of various aspect ratios and size formats. The display computer <NUM> generates displays that change depending on the phase of flight and according to the display settings in the user profile including an adjusted range for the range ring and corresponding scale of the map in the lateral view, adjusted declutter of the map and adjusted aspect ratio and/or size of the VSD and/or whether the VSD is displayed.

The cockpit environment actuators <NUM> can be any suitable electrical, pneumatic, hydraulic and/or spring actuators including servomotors, binary switches and variable switches. The type of actuator used will depend on the cockpit feature being controlled. Non-display cockpit features for control by the cockpit environment actuators <NUM> are described further below.

The user computer <NUM> can be any of a variety of electronic devices including a smartphone, a tablet, a laptop, a desktop computer and the like. The user computer <NUM> is, in embodiments, a portable EFB device allowing a user to set up cockpit preferences that are, at least partly, phase of flight dependent. The user may set up the cockpit preferences offboard, e.g. prior to a flight and, in many cases, remote from the aircraft <NUM>. The user computer <NUM> includes one or more processors <NUM>, a flight planning app <NUM>, a user interface <NUM>, a user display device <NUM> and a local database of user profiles <NUM>. The processor <NUM> has been described in more detail above. The flight planning app <NUM> is a computer application including computer program instructions for execution by the processor <NUM>. The flight planning app <NUM> allows a user to plan various aspects of a scheduled flight (such as the route), which are outside the scope of the present disclosure. Of particular relevance to the present disclosure is that the flight planning app <NUM> controls creation, editing and saving of user profiles. Various exemplary display interfaces generated by the flight planning app <NUM> will be described below with respect to <FIG>. The user interface <NUM> provides a device allowing user entry of cockpit settings. The user interface <NUM> can be any one of conventional devices including a keyboard (virtual or physical), a mouse, a trackball, a touchscreen, a touchpad, etc.. The user display device <NUM> is provided to allow display of presentation of a user profile and adjustable cockpit settings associated therewith. The user can interact with the presentations, via the user interface <NUM>, to create, edit, delete and save user profiles.

Once user profiles have been created or edited, they may be saved in the local database of user profiles <NUM>. The flight planning app <NUM> controls an interface with the on-board computer system <NUM> so that a user profile can be transferred to the on-board computer system <NUM> in response to a request from the on-board computer system <NUM> or in response to a request based on a user selection via at least one of the user interfaces <NUM>, <NUM>. The flight planning app <NUM> controls an interface with the cloud computer <NUM> so that the user can access user profiles stored in a cloud database of user profiles <NUM> and upload local user profiles to the cloud database of user profiles <NUM>. The flight planning app <NUM> thus allows a user to create new profiles to be saved in one or more of the local database of user profiles <NUM> and the cloud database of user profiles <NUM>, load existing user profiles from one or more of the local database of user profiles <NUM> and the cloud database of user profiles <NUM>, edit existing user profiles that have been loaded and save the edited user profiles to the local database of user profiles <NUM> and the cloud database of user profiles <NUM>. Although the flight planning app <NUM> is described with respect to the user computer <NUM>, it is envisaged that the same app, or the same functionality in another app, could additionally or alternatively be provided on the onboard computer system <NUM>.

The flight planning app <NUM> may provide access to a default user profile, which is stored on the local database of user profiles <NUM> or on the cloud database of user profiles <NUM>. The default user profile may be determined based on an airline carrier for the flight plan being created by the user. Each airline carrier may have preferred cockpit settings that are phase of flight dependent. The pilot may adjust the default settings through the user interface <NUM>. In addition to basing the user profile on a default user profile, the flight planning app <NUM> may also allow the user to load other user's profiles (when access is allowed) as a basis for the current user. The flight planning app <NUM> may also allow the user to delete their own profiles and optionally any profiles over which the user has administration rights. A user may have more than one user profile. For example, a user may wish to create different user profiles for different flights so that user profiles suited to particular types of flights (e.g. over ocean, short haul, long haul, etc.) can be saved and conveniently loaded. The flight planning app <NUM> may further control access rights to user profiles stored on the local database of user profiles <NUM> and/or the cloud database of user profiles <NUM>. User profiles may have different access rights for other users including not accessible, viewable, viewable and loadable and/or viewable, loadable and editable. These access rights may be user dependent and the user account is controlled through a user authentication process including password, pin, code sent to a personal device from a central management server, facial recognition, fingerprint recognition, etc.. Similar user authentications may be required to allow editing of a user's profile.

With additional reference to the exemplary user profile adjustable cockpit system <NUM> of <FIG>, the cloud computer <NUM> includes the cloud database of user profiles <NUM> and the processor <NUM>. The processor <NUM>, and associated hardware such as network interfaces and data storage (not shown), provides for data management for storing, retrieving and transferring data from the cloud database of user profiles <NUM> to remote devices including the user computer <NUM> and the on-board computer system <NUM>. Data communications between the cloud computer <NUM>, the user computer <NUM> and the on-board computer system <NUM> are over a secured network communication such as a secured internet communication. The cloud database of user profiles <NUM> includes records of user profiles <NUM> that each include a plurality of user defined cockpit settings profiles <NUM> for respective phases of flight. In one exemplary data structure, each user profile includes a first user defined cockpit settings profile <NUM> defining cockpit preferences <NUM> for a first phase of flight (e.g. on ground), a second user defined cockpit settings profile <NUM> defining cockpit preferences <NUM> for a second phase of flight (e.g. departure), etc.. Other data structures are possible provided that differing display preferences are stored in each user profile for different phases of flight. It should be appreciated that only one or some of the cockpit (display) preferences <NUM> may differ between two or more phases of flight. Further, there may be more than two phases of flight and at least one of the cockpit (display) preferences <NUM> may differ for a subset (e.g. two or more phases of flight) of the total number of phases of flight that have been defined in the user profile <NUM> whilst display preferences <NUM> for a different subset (e.g. two or more phases of flight) of the total number of phases of flight are the same.

In some embodiments, there may be the central cloud database of user profiles <NUM> on the cloud computer <NUM> and the user computer <NUM> and/or the on-board computer system may be dumb terminals that merely access the central cloud database of user profiles <NUM> without locally storing any significant part of the database. In other embodiments, the user computer <NUM> stores the local database of user profiles <NUM>, which is periodically synchronized with parts of the cloud database of user profiles <NUM> that are relevant to the user ID of the user computer <NUM>. The on-board computer system <NUM> may only synchronize database records that are relevant to the current flight plan for storage on the on-board database of user profiles <NUM>. The data synchronization for the on-board database of user profiles <NUM> is, in one embodiment, with the user computer <NUM> and, in other embodiments, is with the cloud computer <NUM>.

<FIG> shows an exemplary presentation of adjustable display settings <NUM>. The presentation of adjustable display settings <NUM> may be displayed on the display device <NUM> of the cockpit system <NUM> under control of the display computer <NUM> (and an optional flight planning app). Additionally or alternatively, the presentation of adjustable display settings <NUM> may be displayed on the user display device <NUM> of the user computer <NUM> under the control of the flight planning app <NUM>. The presentation of adjustable display settings <NUM> includes presentations of various elements including phases of flight <NUM>, selected display settings <NUM>, options for display settings <NUM>, type of display setting being adjusted <NUM>, selectable options for the display settings and buttons <NUM>. In the example of <FIG>, the presentation of the type of display setting being adjusted <NUM> indicates map range. The presentation of phases of flight <NUM> includes ground, departure, enroute, oceanic, arrival and missed approach. However, any subset of two or more of these or other phases of flight may be provided such as simply in-air and on-ground. The presentation of selected display settings <NUM> indicates the currently selected map range during each phase of flight. In the example provided, the user has selected a map range of <NUM> nautical miles (NM) for ground, <NUM> for departure, <NUM> for enroute, <NUM> for oceanic, <NUM> for arrival and <NUM> for missed approach. These map ranges may be adjusted for each phase of flight for the user through the user interface <NUM>. In the exemplary embodiment, the user is provided with the presentation of selectable map ranges for display settings <NUM>, which includes various common values for the user entry including <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM>. More or less of these options may be selectable and other selectable map ranges may be presented. In other embodiments, a particular value may be entered by the user through a virtual numeric keypad or other way of entering a custom value through the user interface <NUM> or the user interface <NUM> rather than selecting from a list of options. The buttons <NUM> allow the user to save the selected display settings for the map range. These display settings for each phase of flight will be saved under a user profile <NUM> in the cloud database of user profiles <NUM>, the on-board database of user profiles <NUM>, the local database of user profiles <NUM> or any combination thereof. The buttons <NUM> may also include back and next buttons, which can be selected to allow a user to move between different adjustable display settings such as map range as exemplified in <FIG>, VSD state as exemplified in <FIG> and/or level of declutter. Examples of display settings that can be user defined and that may differ depending on phase of flight are described further below.

<FIG> shows another exemplary presentation of adjustable display settings <NUM> in which the presentation of the type of display setting being adjusted <NUM> indicates a VSD state. Accordingly, whilst the presentation of <FIG> prompts a user to define map range display settings, the presentation of <FIG> prompts the user to define VSD state display settings. The presentation of selectable options for the VSD state display settings include off, standard, medium and tall. In this way, the presence of the VSD, the size and/or the aspect ratio of the VSD can be adjusted for each phase of flight. In the exemplary embodiment of <FIG>, the following VSD state display settings have been selected by the user through the user interface <NUM> or the user interface <NUM>: standard for ground and departure phases of flight, medium for enroute and missed approach phases of flight, tall for oceanic phase of flight and off for arrival phase of flight. It should be appreciated that less or more or different phases of flight may be included and less or more or different VSD states may be included.

<FIG> illustrate an exemplary sequence of presentations <NUM>, <NUM>, <NUM> for creating a user profile to be stored in one or more of the databases of user profiles <NUM>, <NUM>, <NUM>. The presentations <NUM>, <NUM>, <NUM> of <FIG> may be displayed on the display device <NUM> of the cockpit system <NUM> or the user display device <NUM> of the user computer <NUM>. The user profile may be created or saved with respect to a particular flight plan for loading to the on-board computer system <NUM> during execution of that flight plan. <FIG> shows a presentation for creating a new profile <NUM> including a field (a data entry box in the exemplary embodiment) where a user entry of a profile name or profile ID can be input using at least one of the user interfaces <NUM>, <NUM>. The presentation for creating a new profile <NUM> includes a customize button <NUM> whereby an entirely new profile process can be initiated. The presentation for creating a new profile <NUM> includes selectable profile sources <NUM> from which a user profile can be adapted from, or copied from, an already existing user profile. In one option, the selectable profile sources <NUM> include a default user profile, which may be airline carrier specific. In another option, the selectable profile sources <NUM> includes a current user profile option. The current user profile may allow saving of current cockpit settings (e.g. in-flight or at the end of flight) for one or more phases of flight through the user interface <NUM> of the cockpit system <NUM> or through the user interface <NUM> of the user computer <NUM> when tethered to the on-board computer system <NUM>. In another option, the user profile may be copied from a pre-existing user profile retrieved from at least one of the databases of user profiles <NUM>, <NUM>, <NUM>. For example, flight crew members in a network of flight crew members may be able to load and copy each other's user profiles. The network may be based on flight crew for a particular airline carrier, a social network, and the like. The save button <NUM> may be selected in order to save the user profile to at least one of the databases of user profiles <NUM>, <NUM>, <NUM>.

<FIG> shows a presentation for selecting categories and phases of flight <NUM> for user defined cockpit settings assuming that the customize button <NUM> has been selected. A plurality of selectable phases of flight <NUM> and a plurality of selectable categories of display settings <NUM> can be selected through one of the user interfaces <NUM>, <NUM>. The selectable phases of flight include on-ground and in-air in the example embodiment, but more or different selectable phases of flight may be provided. Further, display preferences are divided into the following categories in the exemplary embodiment: aeronautical, flight plan, geopolitical, terrain, weather and map range. Any subset of two or more of these categories may be provided and more, less or different categories may be provided. The presentation for selecting categories and phases of flight <NUM> of <FIG> allows a user to select a combination of phase of flight and category of display preferences for entry of display preferences in the subsequent screen of <FIG>. In <FIG>, the user has selected on ground and aeronautical, which results in a presentation of selectable aeronautical display preferences <NUM>. In the exemplary embodiment, the following display preferences (e.g. display widgets or layers to be displayed) can be toggled on or off: VOR course layer, VOR layer, Non-direction beacon (NDB), low airways, high airways, intersections, airspace, airports, Special Use Airspace (SUA), etc..

It should be appreciated that the categorization of display preferences of <FIG> is not necessary. This feature is provided to conceptually sort the data and make it easier to manage for a user when there are a large number of display preferences that can be user defined. By selecting which layers of data to display on a navigation map as shown in <FIG>, a level of declutter of the navigation map can be user defined. The level of declutter can be user defined to differ for different phases of flight. In <FIG>, each layer of display data is able to be toggled by a user. In other embodiments, the user may be presented with selectable levels of navigation map declutter without a detailed breakdown of each layer of display feature. For example, the user may be presented with options of: declutter level <NUM> (declutter land data), declutter level <NUM> (declutter land and SUA data) and declutter level <NUM> (declutters large NAV data remaining). These declutter levels progressively remove layers of display features and thus are ordered from low declutter (with less display layers removed) to high declutter (with more display layers removed). Other numbers of levels of declutter could be provided than three including two or four or more.

<FIG> illustrates an exemplary navigation display during a flight. The on-board computer system <NUM> is executing the features and processes described herein whereby cockpit settings, particularly display settings, based on one or more user profiles from the on-board database of user profiles <NUM> are being executed by the display computer <NUM> and/or the cockpit environmental control module <NUM>. At least one of the display settings is phase of flight dependent such that when the phase of flight is detected to change by the on-board computer system <NUM>, the at least one display setting is correspondingly adjusted. In the example of <FIG>, the navigation display <NUM> (which is a lateral presentation) presents a map <NUM>, an ownship location indicator <NUM>, a range ring <NUM> (or partial range ring) disposed about the ownship location indicator <NUM> to indicate the scale of the map <NUM> and waypoints <NUM> connected by flight segment lines <NUM>. In the example of <FIG>, the aircraft <NUM> is traversing a transition between an enroute phase of flight and an arrival phase of flight as detected by the FMS <NUM>. According to the user profile, the map range should change from <NUM> to <NUM> when changing from the enroute phase of flight to the arrival phase of flight. The scale of the map is automatically or semi-automatically changed when the phase of flight changes. Further, the scale indicator <NUM> will change from <NUM> to <NUM>, whilst the range ring <NUM> may stay the same size. In a semi-automatic embodiment, a prompt for change of cockpit settings <NUM> is displayed asking the user to confirm or cancel a cockpit setting change prescribed by the user profile. In the example of <FIG>, the prompt <NUM> asks whether the map range should be changed from <NUM> to <NUM> in accordance with the map range settings in the user profile. The user responds to apply or cancel the change through user interface <NUM>. In other embodiments, the change in cockpit settings is implemented automatically without first prompting for confirmation by the user. In other embodiments, some cockpit settings changes may be implemented automatically and some implemented semi-automatically. In other embodiments, all cockpit settings changes are semi-automatically implemented using a single prompt and in other embodiments individual prompts are provided for each change in individual or grouped settings. Whether to implement the changes automatically or semi-automatically may also be a user definable parameter for all settings changes, for individual settings changes or for grouped settings changes.

In the following, a non-limiting list of cockpit display settings that may be adjustable is provided. Any one or any combination of these cockpit display settings may be defined in a user profile and may or may not be phase of flight dependent. One example cockpit display setting is the Vertical Profile (VSD) status, which may be defined as any one or more of: on/off, standard size, medium size or expanded size in order of size or different aspect ratios may be defined such as horizontal or vertical (e.g. broad or tall). Another example is lateral map mode, which may be defined as north up, heading up or track up. A further example is to center to aircraft or center to waypoint. These cockpit display settings may be grouped or categorized under navigation settings.

In further examples, the following map layers (or any one or combination thereof) may be toggled on/off in order to change a level of declutter and may be defined differently with respect to different phases of flight: terrain, traffic, flight plan, fixes (or waypoints), airways, airspaces and boundaries.

In yet further examples, the following type, amount and/or source of weather data to be displayed on the map may be toggled on/off. In terms of weather data sources any one or combination of the following weather data sources may be defined to be displayed or not displayed depending on the phase of flight: significant weather data, satellite weather data, radar weather data, uplinked weather data and nexrad. The user profile may also define types of weather data in detail including the ability to toggle on or off the following weather data features (or any one or combination thereof): lightning, turbulence, turbulence (VSD), icing, icing (VSD), storm tops, satellite, winds, Clear Air Turbulence (CAT), echo tops, Temporary Flight Restriction (TFR), Airman's Meteorological information (AIRMET), AIREP, PIREP, Significant Meteorological Information (SIGMET), freezing, METAR, Terminal Aerodrome Forecast (TAF), satellite and RADAR. By changing whether to display weather data from different sources and/or different types (features) of weather data, a level of declutter of the navigation map is changed depending on phase of flight. These display features may be categorized as weather.

In yet further examples, the following map layers (or one or any combination thereof) may be toggled on or off and may be user defined in a phase of flight dependent way: boundaries layer, cities layer, major roadways layer, minor roadways layer and railways layer. By adjusting which, if any, of these layers are displayed and defining the number of layers differently for different phases of flight, a level of declutter of the map display can be changed. These display layers may be categorized as geopolitical.

In other examples, the following map layers (or any one or combination thereof) may be toggled on or off depending on phase of flight and user definition in the user profile: VOR Course layer, VOR layer, Non-Direcitonal Beacon (NDB) layer, airways HI ALT layer, airways LOW ALT layer, intersection layer, terminal airspace layer, airports layer, and SUA Airspace layer. By changing which of these layers are displayed, if any, a level of declutter of the map is adjusted. These layers may be categorized as aeronautical layers.

In examples, the following map layers (or any one or combination thereof) may be switched on or off according to the user profile and phase of flight: an airborne traffic layer such as Traffic Collision Avoidance System (TCAS) and/or Automatic Dependent Surveillance Broadcast (ADS-B In), uplink weather layer, airborne weather layer, Situational Awareness (SA) terrain layer, threat terrain layer, Lightening Storm Scope (LSS) layer. These are examples of decluttering by turning on or off display features for the category of sensor layers.

In yet further examples, the user profile may include phase dependent user defined display preferences including lateral map range, whether to display surface alert indications, whether to display a taxi path and/or a mode of the VSD including flight plan (FPLN) or tracking (TRK).

In further examples, non-display cockpit settings may also be defined in the user profile, which may or may not be phase of flight dependent. Such cockpit settings include (one or any combination of): cockpit display window configuration, environmental settings e.g. temperature, lighting, seat adjustments, input mode preference e.g. voice, touch, gesture, camera for the user interface <NUM>, automation mode selections, active/enabled applications and functions, and authentication preferences.

<FIG> is a process flow chart detailing a method <NUM> for defining a user profile and <FIG> is a process flow chart detailing a method <NUM> for generating a cockpit display based on the user profile. Methods <NUM>, <NUM> are executed by the user profiled adjustable cockpit system <NUM> of <FIG>. The methods may be implemented by distributed processors <NUM>, <NUM>, <NUM> across the on-board computer system <NUM>, the user computer <NUM> and the cloud computer <NUM>. The order of operation within the methods <NUM>, <NUM> are not limited to the sequential execution as illustrated in the figures but may be performed in one or more varying orders as applicable and in accordance with the present disclosure. Steps of the methods <NUM>, <NUM> are performed by the one or more processors <NUM>, <NUM>, <NUM> executing computer programming instructions (not shown).

In step <NUM>, method <NUM> includes a step <NUM> of receiving a selection to create a new user profile or to edit an existing user profile. Step <NUM> may be performed off-board or on-board the aircraft <NUM> and may be performed using the user interface <NUM> of the user computer <NUM> or the user interface <NUM> of the on-board computer system <NUM>. Often, step <NUM> will be performed off-board as part of a flight planning process on the user computer <NUM>.

In step <NUM>, a presentation is output on one of the display devices <NUM>, <NUM> to display a presentation relating to user profile creation or editing. An exemplary such presentation is shown in <FIG>. In step <NUM>, a selection of source of user profile is received. The selection is made through one of the user interfaces <NUM>, <NUM>. The source of user profile may be a default user profile or an existing user profile from the same user or from another user, which is stored in one or more of the databases of user profiles <NUM>, <NUM>, <NUM>. The source of user profile may also be to customize a new user profile. When a default or existing user profile is selected, the user may have the option to adjust the user profile and save it as a different user profile or to overwrite the previous user profile if the user has the necessary permissions to edit.

In step <NUM>, and assuming selection of an editing process of an existing user profile or a creation process of a new user profile, user defined display preferences are received. The user enters the user defined display preferences through one of the user interfaces <NUM>, <NUM>. The user defined display preferences include at least one or some preferences that are phase of flight dependent. In examples, the display preferences include user defined selections as to at least one of: presence of one or more map layers (which implicitly affects a level of declutter of the map), a scale of the lateral map, a level of declutter of the map and a size and/or aspect ratio of a vertical profile or VSD. Other cockpit environment features may also be set in the user profile.

In step <NUM>, the user profile is saved to one of the databases of user profiles <NUM>, <NUM>, <NUM>. In step <NUM>, the user profile is transferred to the cockpit system <NUM> for execution during a flight. In one embodiment, the user profile is transferred from the local data of user profiles <NUM> on the user computer <NUM>, which may an EFB device. The transfer may be over a local Wifi network of the aircraft <NUM>, over a Bluetooth connection, over a wired connection or in any other way. The user may select, via one of the user interfaces <NUM>, <NUM>, which user profile to transfer. In another embodiment, the user profile is saved in association with a particular flight plan such that the user profile is automatically transferred upon loading of a flight plan to the cockpit system <NUM>.

Referring to <FIG>, a method <NUM> of generating a cockpit display based on the user profile is described. The method <NUM> (or at least part thereof) may be performed periodically throughout a flight and may be instigated prior to take-off.

In step <NUM>, the user profile is loaded. That is, the user profile transferred to the on-board computer system <NUM> (and optionally stored in the on-board database of user profiles <NUM>) is loaded (or at least the current display preferences are loaded) for implementation by the display computer <NUM>. In step <NUM>, a current phase of flight is detected in a number of ways including phase of flight information being supplied by the FMS <NUM>. In step <NUM>, the display computer <NUM> generates a cockpit display for output on the display device <NUM> (e.g. the navigation display <NUM>) based on the user profile and the phase of flight. The generated display includes, in embodiments, a navigation map including various map layers at a first level of declutter, at a first lateral map range and with a first VSD format. The generated display is based on display preferences as to level of declutter, lateral map range and VSD format included in the user profile for the current phase of flight. In step <NUM> a change of phase of flight is detected. In step <NUM>, the display settings are changed based on the changed phase of flight and the user profile. In embodiments, the generated display includes, in embodiments, a navigation map including various map layers at a second level of declutter, at a second lateral map range and/or with a second VSD format. The generated display is based on display preferences as to level of declutter, lateral map range and/or VSD format included in the user profile for the newly detected phase of flight. That is, at least one of these display preferences changes as a result of display preferences being defined in the user profile differently for the previous phase of flight than the current phase of flight. In some embodiments, a prompt is presented requesting a user to accept or reject the change of display preferences as shown in <FIG>.

Claim 1:
A cockpit display system (<NUM>), comprising:
a display device (<NUM>);
a user device (<NUM>);
at least one processor (<NUM>) in operable communication with the display device and the user device, the at least one processor configured to execute program instructions, wherein the program instructions are configured to cause the at least one processor to:
generate a presentation (<NUM>) of adjustable display settings on the display device, the presentation of adjustable display settings including a plurality of phase of flight elements (<NUM>) and selectable values (<NUM>) for a range of a map for each of the plurality of phase of flight elements;
receive user entry, via the user device, of values for the range of the map for different phases of flight;
save the values for the range of the map in association with a respective one of the plurality of phases of flight in a user profile (<NUM>);
retrieve the user profile, wherein the user profile includes user defined display settings profiles (<NUM>), and wherein each user defined display settings profile is associated with a respective phase of flight;
retrieve phase of flight data;
select one of the user defined display settings profiles based on the phase of flight data;
generate a display for the display device using display settings included in the selected one of the user defined display settings profiles, wherein the display settings include the saved values for the range of a map to be displayed, wherein the saved values are different for different phases of flight.