Method for intermixing graphics applications using display intermix server for cockpit displays

[0001] The subject matter described herein relates generally to cockpit displays in aircraft, and more particularly, embodiments of the subject matter relate to systems and methods for intermixing graphics layers for graphics applications associated with avionics or aircraft subsystems.

[0002] Aircraft cockpit displays include numerous cockpit instruments and controls that compete for cockpit space and pilot attention. Electronic instrument displays are used in place of traditional mechanical gauges and utilize computer displays to display flight related information as needed. These electronic cockpit displays often use software for integrating the computer displays with external (or peripheral) systems, such as avionics or other aircraft sensors and systems. Often, these peripheral systems have associated software (e.g., graphics applications) for managing the graphics functionality and interfacing with the electronic cockpit display software.

[0003] During the life of these peripheral systems (e.g., avionics or aircraft subsystems), upgrading existing graphics applications often requires making changes to the peripheral systems. For example, as technology evolves, it may be desirable to upgrade or add new graphical features (adding new display function or changing the layout, appearance or behavior of display objects) to the existing graphics applications. However, changing the peripheral system is cost-prohibitive, because many peripheral systems must comply with legally mandated standards for safety and reliability. This increases the complexity of interfacing and integration, along with added development time and cost. Thus, although it may be possible to improve cockpit displays and enhance the user experience (e.g., allowing pilots or crew members to customize the look and feel, accommodating personal preferences or needs, or introducing interactivity), current systems often make upgrading the graphics impractical or infeasible.

[0004] Some airlines or equipment manufacturers have invested large amounts of development time and cost to create cockpit display solutions using proprietary architectures, which may require a unique graphics application architecture. These approaches may result in minimal reuse of already proven features and applications that are already in service and certified under applicable standards. Thus, current solutions require additional investment and, in some cases, even result in the need to develop entirely new systems.

[0005] A method is provided for intermixing a first graphics application having a first graphics layer and a second graphics application having a second graphics layer. The method comprises streaming a first graphics command from the first graphics application to a first memory location, where the first graphics command corresponds to the first graphics layer. The method also comprises streaming a second graphics command from the second graphics application to a second memory location, where the second graphics command corresponds to the second graphics layer. The method further comprises ordering the first graphics command and the second graphics command based on a priority scheme for the first graphics layer and the second graphics layer. The method may also comprise providing the ordered graphics commands to a rendering interface.

[0006] An apparatus is provided for a display system. The display system comprises a command buffer corresponding to a graphics layer and being configured to receive and store a first graphics command. A graphics programming interface is configured to provide the first graphics command to the command buffer and obtain the first graphics command from the command buffer. A display intermix server is configured to obtain the first graphics command from the graphics programming interface and order the first graphics command among a plurality of graphics commands corresponding to a plurality of graphics layers based on a priority scheme. Ordering the first graphics command and the plurality of graphics commands results in ordered graphics commands, and the display intermix server is configured to provide the ordered graphics commands to a rendering interface.

[0017] The following detailed description is merely exemplary in nature and is not intended to limit the subject matter of the application and uses thereof. Furthermore, there is no intention to be bound by any theory presented in the preceding background or the following detailed description.

[0018] Techniques and technologies may be described herein in terms of functional and/or logical block components, and with reference to symbolic representations of operations, processing tasks, and functions that may be performed by various computing components or devices. Such operations, tasks, and functions are sometimes referred to as being computer-executed, computerized, software-implemented, or computer-implemented. In practice, one or more processor devices can carry out the described operations, tasks, and functions by manipulating electrical signals representing data bits at memory locations in the system memory, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to the data bits. It should be appreciated that the various block components shown in the figures may be realized by any number of hardware, software, and/or firmware components configured to perform the specified functions. For example, an embodiment of a system or a component may employ various integrated circuit components, e.g., memory elements, digital signal processing elements, logic elements, look-up tables, or the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices.

[0019] When implemented in software or firmware, various elements of the systems described herein are essentially the code segments or instructions that perform the various tasks. The program or code segments can be stored in a processor-readable medium or transmitted by a computer data signal embodied in a carrier wave over a transmission medium or communication path. The “processor-readable medium” or “machine-readable medium” may include any medium that can store or transfer information. Examples of the processor-readable medium include an electronic circuit, a semiconductor memory device, a ROM, a flash memory, an erasable ROM (EROM), a floppy diskette, a CD-ROM, an optical disk, a hard disk, a fiber optic medium, a radio frequency (RF) link, or the like. The computer data signal may include any signal that can propagate over a transmission medium such as electronic network channels, optical fibers, air, electromagnetic paths, or RF links. The code segments may be downloaded via computer networks such as the Internet, an intranet, a LAN, or the like.

[0020] The following description refers to elements or nodes or features being “connected” or “coupled” together. As used herein, unless expressly stated otherwise, “connected” means that one element/node/feature is directly joined to (or directly communicates with) another element/node/feature, and not necessarily mechanically. Likewise, unless expressly stated otherwise, “coupled” means that one element/node/feature is directly or indirectly joined to (or directly or indirectly communicates with) another element/node/feature, and not necessarily mechanically. Thus, although the drawings may depict one exemplary arrangement of elements, additional intervening elements, devices, features, or components may be present in an embodiment of the depicted subject matter.

[0021] For the sake of brevity, conventional techniques related to processing, data transmission, rendering, computer program interfacing, and other functional aspects of the systems (and the individual operating components of the systems) may not be described in detail herein. Furthermore, the connecting lines shown in the various figures contained herein are intended to represent exemplary functional relationships and/or physical couplings between the various elements. It should be noted that many alternative or additional functional relationships or physical connections may be present in an embodiment of the subject matter.

[0022] Technologies and concepts discussed herein relate to electronic display systems used in aircraft cockpits to provide information and data relating to the various aircraft systems or avionics to aircraft pilots and/or crew. A display intermix server may be used to integrate graphics applications, provide interactivity, and minimize costs of acquiring new aircraft systems, upgrading existing aircraft systems, or adding new display functions. It should be appreciated that although the subject matter may be described herein in the context of an aviation environment for purpose of explanation, the subject matter is not limited to aviation systems and aircraft. The subject matter described herein also applies to other embedded systems such as spacecraft, ships and marine systems, automotive systems and other ground vehicles, remote control stations, industrial control systems, and the like.

[0023] Operative Environment

[0024] As shown in FIG. 1, an aircraft display system 100 may include, without limitation, an external module 102, a client application 104, a cockpit display system 106, and a display device 108. The aircraft display system 100 may be used to provide information or data from various external modules 102 to aircraft pilots and/or crew via the display device 108 during operation of an aircraft. These and possibly other components may be coupled as needed to support the operation of the aircraft display system 100 as described in greater detail below.

[0025] Referring again to FIG. 1, in an exemplary embodiment, the external module 102 is coupled to a client application 104 (or user application), which is in turn coupled to the cockpit display system 106. In an exemplary embodiment, the cockpit display system 106 is coupled to the display device 108, and may be configured to perform various tasks and functions as described in greater detail below.

[0026] In accordance with one embodiment, the external module 102 may comprise avionics, an aircraft subsystem, a line-replaceable unit (LRU), external control logic, or another comparable module. In an exemplary embodiment, the external module 102 provides data from or information regarding one or more aircraft subsystems (such as control, monitoring, communication, navigation, weather, and/or anti-collision systems) as is known in the art. The external module 102 may be implemented as hardware, software, or a combination thereof which may be embedded on one or more circuit boards and/or circuit card assemblies. Although the depicted aircraft display system 100 includes one external module 102, in practice, numerous external modules 102 may be present. In an exemplary embodiment, the external module 102 provides functional data pertaining to aircraft subsystems to a corresponding client application 104 which generates a graphical display in response to the functional data, as described in greater detail below.

[0027] In an exemplary embodiment, the client application 104 functions as an interfacing mechanism between the cockpit display system 106 and the external module 102. The client application 104 may be implemented as hardware, software, or a combination thereof which may be embedded on one or more circuit boards and/or circuit card assemblies. The client application 104 may be located alone in hardware (e.g., circuit board or circuit card), or share hardware with the external module 102 or the cockpit display system 106. In practice, numerous client applications 104 may be present, and each may have a corresponding external module 102. In an exemplary embodiment, the client application 104 processes the functional data provided by the external module 102 and provides various graphics commands and/or control parameters to the cockpit display system 106. The cockpit display system 106 processes the commands and/or parameters from the client application 104 for rendering on a display device 108. The cockpit display system 106 may further provide processing capabilities for subdividing the display on the display device 108 into smaller display areas or windows. Although only one display device 108 is shown in FIG. 1, in practical embodiments, one or more display devices 108 may be present.

[0028] Referring now to FIG. 2, in an exemplary embodiment, a cockpit display framework 200 includes, without limitation, a graphics application 202, a graphics programming interface 204 (GPI), a shared command buffer 206, a display intermix server 208, and a display device 210. The cockpit display framework 200 may be configured to receive control commands (e.g., functional data and/or inputs) from external modules 212, 214 and/or a human machine interface 216 (HMI). In an exemplary embodiment, the GPI 204 comprises numerous application program interfaces (APIs) and includes, without limitation, a graphics API 218, a buffer API 220, and a display API 222. Some of the elements of FIG. 2 are identical to their counterparts described above in reference to FIG. 1, and the description will not be redundantly repeated in the context of FIG. 2.

[0029] In an exemplary embodiment, the HMI 216 is configured to receive interactive events from a user (e.g., pilot, copilot, crew). In various embodiments, the HMI 216 may be a touch screen, a cursor, a mouse, a keyboard, a knob, a control panel, a mechanical instrument, or another comparable means for interfacing with a user. The HMI 216 is configured to broadcast and/or provide information or control commands to the graphics application 202 and the display intermix server 208 in response to interactive events, as discussed in greater detail below.

[0030] In an exemplary embodiment, the graphics application 202 is coupled to and/or configured to receive control commands from an external control module 212 and/or the human machine interface 216. The graphics application 202 is further coupled to the GPI 204, which in turn is coupled to the shared command buffer 206 via the buffer API 220. The graphics application 202 is coupled to the display intermix server 208 (e.g., via a bus interface or shared memory) and communicates with the display intermix server 208 as described below. The display intermix server is also coupled to the GPI 204. The display intermix server 208 may be coupled to and/or configured to receive control commands from an external control module 214 and/or the human machine interface 216. The display API 222 may be coupled to the display device 210. In an exemplary embodiment, the display intermix server 208 is coupled to a layering registry 226 and the graphics application 202 is coupled to a routing registry 224, as described in greater detail below.

[0031] It should be understood that FIG. 2 depicts a simplified version of the cockpit display framework 200, and that in practice, multiple instances and various combinations of the respective elements may be present depending on the embodiment. For example, numerous instances of graphics applications 202 may be present and associated with an instance of the display intermix server 208. There may be more than one display device 210, and each display device 210 may be associated with a separate instance of display intermix server 208. In an exemplary embodiment, the display device 210 may be subdivided into one or more windows, each window having an instance of display intermix server 208 associated therewith.

[0032] Referring again to FIG. 2, in an exemplary embodiment, the graphics application 202 is configured to interface between a corresponding external control module 212 and the display intermix server 208, as described in greater detail below. In an exemplary embodiment, the graphics application 202 includes one or more graphics layers associated with the graphics application 202 (i.e., owned by the graphics application 202). A graphics layer is a logical grouping of graphical objects or widgets, which may or may not be interactive, as will be understood in the art. The graphics application 202 manages the graphics layers and widgets and the manner and order of rendering in response to control commands and other system parameters. In an exemplary embodiment, the graphics application 202 is coupled to a routing registry 224, for managing the rendering of the graphics layers associated with the graphics application 202, as described in greater detail below.

[0033] In an exemplary embodiment, the graphics programming interface 204 (GPI) is configured to interface between the graphics application 202, the shared command buffer 206, the display intermix server 208, and other computing devices or systems using one or more application program interfaces (APIs). In an exemplary embodiment, the graphics API 218 is configured to receive a high-level graphics command (e.g., from the graphics application 202) and convert the high-level graphics command to a graphics command comprising a display list, texture, primitive chain, or any other graphics structure that may be used for future rendering. The buffer API 220 is configured to transmit data between applications and/or memory locations (e.g., the shared command buffer 206), as will be appreciated in the art. The display API 222 is configured to receive graphics commands and provide functionality for rendering on a display device 210 and/or interfacing with a device driver for the display device 210.

[0034] Referring now to FIG. 2 and FIG. 3, in an exemplary embodiment, the shared command buffer 206 includes a plurality of memory locations or buffers for maintaining and/or storing graphics commands from the graphics application 202 and/or display intermix server 208. In an exemplary embodiment, each graphics layer has a separate command buffer and/or memory location for the graphics commands corresponding to the respective graphics layer, as described below. Thus, in an exemplary embodiment, for n number of graphics layers, there are n different shared command buffer 206 locations. The routing registry 224 provides information for mapping graphics commands for a graphics layer from the graphics application 202 to the location in the shared command buffer 206 that corresponds to the graphics layer, as described below. In accordance with one embodiment, if it is not desirable or necessary to intermix the graphics application 202, the routing registry 224 may provide information to the graphics application 202 such that the graphics commands are streamed to the display device 210 via the GPI 204 without use of the shared command buffer 206. In an exemplary embodiment, each graphics application 202 has a routing registry 224 associated therewith, although in other embodiments, a plurality of graphics applications 202 may share one routing registry 224.

[0035] Referring now to FIG. 2 and FIG. 4, in an exemplary embodiment, the display intermix server 208 manages the priority of rendering for the graphics applications 202 and graphics layers, as described in greater detail below. The display intermix server 208 may use one or more data structures to manage the priority of rendering the graphics commands based on a priority scheme defined in the layering registry 226, as described in greater detail below. For example, as shown in FIG. 4 and described below, the display intermix server 208 may implement a hierarchical tree 400, wherein each node corresponding to a graphics layer of a graphics application 202 comprises the contents of the shared command buffer 206 for the respective graphics layer, which are ordered according to the priority scheme in the layering registry 226. Depending on the embodiment, the display intermix server 208 may also function as a graphics application by interfacing with a corresponding external module 214. In such an embodiment, the display intermix server 208 may include information for one or more graphics layers associated with the display intermix server 208 and maintained as nodes in the hierarchical tree based on the priority scheme defined in the layering registry 226. The display intermix server 208 may also be compliant with standards, such as Aeronautical Radio, Incorporated (ARINC) standard number 661 (ARINC 661), for communicating and interfacing with graphics applications 202 and/or external modules 214. In an exemplary embodiment, the display intermix server 208 manages the priority and order of rendering across all graphics applications 202 and graphics layers in accordance with a priority scheme defined in the layering registry 226 coupled to the display intermix server 208, as described in greater detail below.

[0036] Depending on the embodiment, the display intermix server 208 and the graphics application 202 may exist in the same computing platform. In an exemplary embodiment, for real time applications, each shall maintain its own space and time partitions. For example, the graphics API 218 may be configured to implement space and time partitioning. The specific methods for generating time and space partitioned display lists, textures, and/or primitive chains will not be described herein. For example, U.S. Pat. No. 6,980,216 entitled “GRAPHICS DRIVER AND METHOD WITH TIME PARTITIONING,” assigned to the assignee of the present application and incorporated by reference herein, discloses an exemplary method of generating time-partitioned primitive chains. The graphics applications 202 and display intermix server 208 may have time and space boundaries defined for compliance to regulatory requirements or any other safety requirements in safety critical systems like cockpit displays, as will be understood.

[0037] Intermixing Graphics Applications and Graphics Layers

[0038] Referring now to FIG. 5, in an exemplary embodiment, a cockpit display framework 200 may be configured to perform an intermix definition process 500 and additional tasks, functions, and operations described below. The various tasks may be performed by software, hardware, firmware, or any combination thereof. For illustrative purposes, the following description may refer to elements mentioned above in connection with FIG. 1, FIG. 2, FIG. 3 and FIG. 4. In practice, the tasks, functions, and operations may be performed by different elements of the described system, such as the graphics application 202, the GPI 204, the display intermix server 208, the graphics API 218, the buffer API 220, or the display API 222. It should be appreciated that any number of additional or alternative tasks may be included, and may be incorporated into a more comprehensive procedure or process having additional functionality not described in detail herein. Further, the intermix definition process 500 is not limited to cockpit display framework 200, and may be adapted for other frameworks, as will be understood.

[0039] Referring again to FIG. 5, and with continued reference to FIG. 1, FIG. 2, FIG. 3 and FIG. 4, the intermix definition process 500 may be performed as a preliminary procedure, for example, during an initialization or pre-configuration routine for the system. Alternatively, process 500 might be initiated in response to a signal or command indicating that the aircraft or a given subsystem thereof has been turned on. In an exemplary embodiment, the intermix definition process 500 is configured to define a priority scheme for the order of rendering and the intermixing of graphics applications and/or graphics layers (task 502). In an exemplary embodiment, the display intermix server 208 manages the priority of graphics layers using the layering registry 226. The rules for layering and/or the priority scheme may be also predefined and/or provided during initialization (e.g., installation or creation) of the display intermix server 208. For example, the priority scheme may be obtained by interpreting a binary file (or byte codes or scripts generated by a user-friendly tool) provided to the display intermix server 208. The priority scheme may be statically determined and fixed for the duration or operation, or may change based on the run-time contexts triggered by some internal and/or external control logic (e.g., external modules 212, 214), for example, in the scenario of reversion or the like. In accordance with one embodiment, where a single layering registry 226 is shared across multiple instances of display intermix servers 208, the layering registry also maintains the association between graphics applications 202 and their respective display intermix server 208.

[0040] In an exemplary embodiment, the intermix definition process 500 is configured to enable adding new graphics features, layers, or applications. The intermix definition process 500 is configured to determine if a new graphics layer or a new graphics application is to be added (task 504). For example, it may be desirable to update graphics features of an existing graphics application by adding a new graphics layer to the graphics application, or adding a new graphics application altogether. Alternatively, new graphical features may be added by adding a new graphics layer associated with the display intermix server.

[0041] In an exemplary embodiment, the intermix definition process 500 is configured to provide information about the new graphics application 202 (or the graphics application 202 associated or owning the new graphics layer) to the display intermix server 208 (task 506). In accordance with one embodiment, the priority scheme or rules of layering (or intermixing) is coded as part of the graphics application(s) 202 and provided to the display intermix server 208 (e.g., via a bus interface). The rules for layering and/or the priority scheme may be also defined by the functional requirements of the graphics application which may be provided during initialization (e.g., installation or creation of the graphics application 202) or normal execution.

[0042] In an exemplary embodiment, if a new graphics layer or a new graphics application is to be added, the intermix definition process 500 is configured to update the priority scheme to include the new graphics layer(s) (task 508). In an exemplary embodiment, the intermix definition process 500 is configured to redefine the priority scheme for the order of rendering and the intermixing of graphics applications and graphics layers by updating the layering registry 226 with the information about the new graphics application 202 or graphics layer. The display intermix server 208 is configured to maintain the layering registry 226 such that it reflects the updated priority scheme for intermixing the new graphics layers and/or graphics applications with existing graphics layers and/or applications.

[0043] Referring now to FIG. 5 and FIG. 6, it should be appreciated that new graphics applications or new graphics layers may be intermixed with little or no changes to existing applications. For example, as shown in FIG. 6, in order to add a new graphics layer 610 (or a new graphics application) to be intermixed with an existing certified graphics application 600, the intermix definition process 500 allows the new graphics layer 610 (or new graphics application) to be added by merely updating the routing registry 224 and layering registry 226 while the certified graphics application 600 remains unchanged. Thus, because the existing certified graphics application 600 is not modified, the increased development costs and potential need for recertification of existing applications can be avoided or minimized using the proposed scheme and framework. The loop defined by tasks 504, 506, and 508 may repeat as needed to enable intermixing as many graphics layers or graphics applications 202 as desired.

[0044] Referring now to FIG. 7, in an exemplary embodiment, a cockpit display framework 200 may be configured to perform a display intermix process 700 and additional tasks, functions, and operations described below. The various tasks may be performed by software, hardware, firmware, or any combination thereof. For illustrative purposes, the following description may refer to elements mentioned above in connection with FIG. 1, FIG. 2, FIG. 3, FIG. 4 and FIG. 5. In practice, the tasks, functions, and operations may be performed by different elements of the described system, such as the graphics application 202, the GPI 204, the display intermix server 208, the graphics API 218, the buffer API 220, or the display API 222. It should be appreciated any number of additional or alternative tasks may be included, and may be incorporated into a more comprehensive procedure or process having additional functionality not described in detail herein.

[0045] Referring again to FIG. 7, and with continued reference to FIG. 1, FIG. 2, FIG. 3, FIG. 4 and FIG. 5, the display intermix process 700 may be initiated in response to a signal or command indicating that the aircraft or a given subsystem thereof has been turned on. In an exemplary embodiment, the display intermix process 700 is configured to receive a control command (task 702). In accordance with one or more embodiments, the control command is provided to a graphics application 202 and/or the display intermix server 208 by an external module 212, 214 or the HMI 216. Alternatively, the graphics application 202 or display intermix server 208 may include logic to generate the control command based on functional data provided by the external module 212, 214 or HMI 216.

[0046] In alternative embodiments, the display intermix process 700 may be configured to prompt an interactive intermixing process (task 704), as described in greater detail below with reference to FIG. 8. The interactive intermixing process may be performed in response to a control command and/or functional data provided by the HMI 216 in response to an interactive event. In the case of overlapping interactive graphics layers (or graphical objects), the interactive intermixing process arbitrates among a plurality of graphics applications 202 to identify the graphics application 202 that should respond to the interactive event, as discussed below.

[0047] In an exemplary embodiment, the display intermix process 700 is configured to generate a high-level graphics command based on the control command and/or functional data (task 706). For example, the graphics application 202 may generate a high-level graphics command for a graphics layer associated with the graphics application 202 based on the control command provided by the external module 212. In an exemplary embodiment, the display intermix process 700 is configured to convert the high-level graphics command to a lower-level graphics command (task 708). For example, the graphics API 218 may receive the high-level graphics command from a graphics application 202 and convert the high-level graphics command to a graphics command comprising display list, texture, and/or primitive chain that may be used for future rendering, as will be understood.

[0048] In an exemplary embodiment, the graphics command is stored in a memory location (e.g., shared command buffer 206) corresponding to the respective graphics layer (task 710). The graphics application 202 may be configured to stream the graphics command to a memory location (e.g., shared command buffer 206) associated with the corresponding graphics layer via the GPI 204. In an exemplary embodiment, the routing registry 224 contains information for mapping graphics commands for a respective graphics layer to the shared command buffer 206 (e.g., buffer memory location) that corresponds to the graphics layer. The graphics application 202 may be configured to obtain information regarding the proper command buffer 206 location from the routing registry 224, and provide the information to the GPI 204 along with the high-level graphics command. The buffer API 220 may route (e.g., store) the graphics command to the proper command buffer 206 using the information from the routing registry 224 provided to the GPI 204.

[0049] In an exemplary embodiment, the display intermix process 700 is configured to notify the display intermix server 208 of a change in the graphics application 202 in response to the control command (task 712). In an exemplary embodiment, the graphics application 202 provides a message and/or control parameters to the display intermix server 208 (e.g., via a bus interface or shared memory). For example, if the display intermix server 208 and the graphics application 202 are ARINC 661 compliant, the graphics application 202 transmits a graphical object including various parameters (such as the type and identity of the widget, position, visibility) according to the ARINC 661 specification. The graphics application 202 may also be configured to provide the display intermix server 208 with information identifying the proper command buffer 206 and the type of content (such as a display list or texture) stored in the shared command buffer 206. Other parameters may also be included or modified to enable interactivity, as discussed in greater detail below.

[0050] In an exemplary embodiment, the display intermix server 208 is configured to obtain the graphics command from the shared command buffer 206 (task 714). For example, the display intermix server 208 may receive the shared command buffer 206 location for a respective graphics layer from the graphics application 202, and provide the buffer location information to the buffer API 220 to obtain the graphics command. In some embodiments, where the display intermix server 208 has a graphics layer associated therewith, the display intermix server 208 may manage the graphics commands corresponding to the graphics layer owned by the display intermix server without use of the shared command buffer 206.

[0051] In an exemplary embodiment, the display intermix server 208 is configured to order the obtained graphics command among a plurality of graphics commands corresponding to the graphics applications 202 (and each individual graphics layer associated therewith) associated with the display intermix server 208 (task 716). The display intermix server 208 may use one or more data structures to manage the priority of rendering the graphics commands based on the priority scheme defined in the layering registry 226. For example, as discussed above in reference to FIG. 4, in an exemplary embodiment, the display intermix server 208 implements a hierarchical tree, wherein each node corresponding to a graphics application 202 comprises the contents of the shared command buffer 206 for the respective graphics layer, which are ordered according to the priority scheme in the layering registry 226. As shown, if the display intermix server 208 owns a graphics layer, the graphics layer may be interleaved between layers corresponding to graphics applications 202. In accordance with one embodiment, if the display intermix server 208 is ARINC 661 compliant, a graphical object may be instantiated for every ARINC 661 widget and arranged in the hierarchical tree as per the ARINC 661 definition file.

[0052] Referring again to FIG. 7, in an exemplary embodiment, the display intermix server 208 is configured to provide the ordered graphics commands for the graphics applications 202 (and layers associated therewith) to a rendering interface (e.g., the GPI 204 or display API 222) (task 718). In an exemplary embodiment, the display API 222 is configured to receive and/or process the graphics commands (which are in the form of display lists, primitive chains, textures, etc.) for rendering on the display device 210. In practice, the display API 222 may interface with a device driver (not shown) for rendering the graphics commands on the display device 210, which will be understood in the art and therefore not described in detail herein. The loop defined by tasks 702, 704, 706, 708, 710, 712, 714, 716, and 718 may repeat indefinitely during operation of an aircraft (or a given subsystem thereof) to provide intermixed graphics applications (or graphics layers) and enable interactivity as described below.

[0053] Intermixing Interactivity

[0054] Referring now to FIG. 8, in an exemplary embodiment, a cockpit display framework 200 may be configured to perform an interactive intermix process 800 and additional tasks, functions, and operations described below. The various tasks may be performed by software, hardware, firmware, or any combination thereof. For illustrative purposes, the following description may refer to elements mentioned above in connection with to FIG. 1, FIG. 2, FIG. 3, FIG. 4, FIG. 5 and FIG. 7. In practice, the tasks, functions, and operations may be performed by different elements of the described system, such as the graphics application 202, the GPI 204, the display intermix server 208, the graphics API 218, the buffer API 220, or the display API 222. It should be appreciated any number of additional or alternative tasks may be included, and may be incorporated into a more comprehensive procedure or process having additional functionality not described in detail herein.

[0055] Referring again to FIG. 8, and with continued reference to FIG. 1, FIG. 2, FIG. 3, FIG. 4, FIG. 5 and FIG. 7, in an exemplary embodiment, an interactive intermix process 800 is configured to begin in response to an interactive event and/or control command received from the HMI 216 (e.g., task 704 in FIG. 7). Depending on the HMI 216, the interactive event may be a mouse click, turning a knob on a control panel, a touch sensed by a touch screen, a keyboard entry, or another comparable user input. The HMI 216 is configured to broadcast or provide information regarding the event (such as the location or coordinates of event on a display screen, the type of event, the device generating the event, etc.), the instances of graphics application 202 and display intermix server 208 associated with the HMI 216.

[0056] In an exemplary embodiment, each instance of graphics application 202 and display intermix server 208 is coupled to the HMI 216 and configured to receive information corresponding to the HMI event (task 802). In an exemplary embodiment, the graphics application 202 and display intermix server 208 are configured to determine whether or not the HMI event corresponds to an interactive graphical object within a layer owned by the graphics application or the display intermix server 208, respectively (task 804). For example, the graphics application 202 may perform a Hit test, by comparing the information from the HMI event (such as location and/or coordinates) and determining if the HMI event overlaps or occurred in the same area as an interactive object (i.e., Hit the interactive object) within a graphics layer owned by the graphics application 202 (or display intermix server 208).

[0057] In an exemplary embodiment, if a graphics application 202 determines that the HMI event produced a Hit within a graphics layer owned by the graphics application 202, the graphics application 202 is configured to notify the display intermix server 208 that the HMI event produced a Hit (task 806). This may be done by sending a message or other data to the display intermix server 208 (e.g., via a bus interface or shared memory).

[0058] Referring now to FIG. 8 and FIG. 9, in accordance with one embodiment, if the display intermix server 208 is ARINC 661 compliant, the graphics application 202 may be configured to notify the display intermix server 208 by using a custom parameter for a graphical object or widget provided to the display intermix server 208. For example, a custom widget may be created to include additional parameters to enable intermixing interactivity, such as those shown in FIG. 9. The custom widget need not be the only widget in a graphics layer, and there may be other widgets or many other instances of custom widgets in a graphics layer. The custom widget may provide details regarding its owner (e.g., graphics application), content or type of graphics commands associated with the custom widget, parameters to enable or disable interactivity (e.g., masking). It should be understood that the parameters shown in FIG. 9 are merely exemplary, and various possible combinations of parameters or alternative methods may be employed to implement the subject matter described herein.

[0059] In an exemplary embodiment, the display intermix server 208 is configured to determine the graphics application 202 that should respond to the HMI event (task 808). For example, the display intermix server 208 may have a plurality of graphics applications 202 associated with the display intermix server 208. The HMI event may occur at a location and/or coordinates that correspond to interactive objects in different graphics layers that are owned by different graphics applications 202 (e.g., interactive objects in different graphics layers that overlap). In this situation, the display intermix server 208 may receive a notification of a Hit from more than one graphics application 202. In an exemplary embodiment, the display intermix server 208 is configured to determine which graphics application 202 should respond to the HMI event based upon the priority scheme or rules of layering defined in the layering registry 226.

[0060] In accordance with one embodiment, the display intermix server 208 notifies the graphics application 202 to respond to the HMI event (task 810). If no interactive objects overlap among different graphics layers, the display intermix server 208 may notify the graphics application 202 producing the Hit to respond to the HMI event. In the situation where there is an overlap of interactive objects among graphics layers owned by different graphics applications 202, the display intermix server 208 may notify the graphics application 202 owning the graphics layer with highest priority (based on the priority scheme in the layering registry 226) among those producing a Hit to respond to the HMI event. The interactive intermix process 800 may be configured such that all other graphics applications 202 do not respond to the HMI event (e.g., by providing a separate notification not to respond). In accordance with another embodiment, if the HMI event produces a Hit in a graphics layer owned by the display intermix server 208, the display intermix server 208 may respond to the event if the graphics layer owned by the display intermix server 208 has the highest priority among those producing a Hit.

[0061] Referring to FIG. 7 and FIG. 8, the interactive intermix process 800 may be configured to be integrated with the display intermix process 700 as part of the interactive intermixing process (task 704), such that the loop defined by tasks 702, 704, 706, 708, 610, 712, 714, 716, and 718 is implemented using the graphics command generated based on the HMI event. In an exemplary embodiment, the graphics application 202 (or the display intermix server 208) that receives notification to respond to the HMI event proceeds to generate graphics commands (e.g., task 706) based on the HMI event.

[0062] In accordance with one embodiment, an exception to the interactive intermix process 800 occurs in the situation of an interactive pop-up message or menu owned by a graphics application 202 and/or the display intermix server 208. In an exemplary embodiment, it is desirable that pop-up messages or menus are displayed over other interactive objects and have priority over other objects, which could potentially conflict with the priority scheme or rules of layering. For example, an interactive pop-up object in a graphics layer owned by a graphics application 202 may overlap an interactive object in a graphics layer having higher priority and owned by another graphics application 202 (or the display intermix server 208). In an exemplary embodiment, the interactive intermix process 800 is configured such that the graphics application 202 (e.g., the interactive pop-up menu or message) is notified to respond to the HMI event while the display intermix server 208 (or other graphics applications) does not respond to the event, even though the graphics layer owned by the display intermix server 208 may have higher priority than the layer owned by the graphics application 202.

[0063] In another scenario, there may be an interactive pop-up object owned by a graphics application 202 that overlaps an interactive pop-up object owned by the display intermix server 208 (or another graphics application 202). In an exemplary embodiment, the interactive intermix process 800 is configured such that the interactive pop-up objects are combined or merged by generating a popup message listing overlapping interactive pop-up objects from graphics applications 202 well as the display intermix server 208. For example, a graphics application 202 may transmit the contents of the interactive pop-up object to the display intermix server 208 (e.g., via a message over a bus interconnection). The display intermix server 208 may then be configured to generate an integrated interactive pop-up object with contents from one or more graphics applications 202 and/or the display intermix server 208. In an exemplary embodiment, the integrated contents are ordered according to the priority scheme defined in the layering registry 226 for the respective layers. In an alternative embodiment, graphics applications 202 may respond to the HMI event and generate graphics commands corresponding to the interactive pop-up object and notify the display intermix server 208 of the location and the number of items in the interactive pop-up object. The display intermix server 208 may then construct an integrated interactive pop-up object by rendering additional interactive pop-up objects as a continuum of the interactive pop-up object generated by the graphics application 202 (e.g., append graphically).

[0064] One advantage of the system and/or method described above is that seamless intermixing of new graphics features with existing graphics application as well as with new graphics applications may be achieved with limited changes to existing or proven graphics applications. Upgrading or adding new features to existing graphics applications may be accomplished with minimal changes to already proven and certified graphics application software. Additionally, the systems and methods provide flexibility and control in defining the cockpit display.

[0065] While at least one exemplary embodiment has been presented in the foregoing detailed description, it should be appreciated that a vast number of variations exist. It should also be appreciated that the exemplary embodiment or exemplary embodiments are only examples, and are not intended to limit the scope, applicability, or configuration of the subject matter in any way. Rather, the foregoing detailed description will provide those skilled in the art with a convenient road map for implementing an exemplary embodiment of the subject matter. It being understood that various changes may be made in the function and arrangement of elements described in an exemplary embodiment without departing from the scope of the subject matter as set forth in the appended claims.