Integrity monitoring

• US 9,189,195 B2
• Filed: 02/06/2012
• Issued: 11/17/2015
• Est. Priority Date: 10/16/2006
• Status: Active Grant

• Current Assignee: Nighthawk Flight Systems Incorporated
• Original Assignee: Sandel Avionics Inc.
• Inventors: Block, Gerald J.
• Primary Examiner(s): Rones, Charles
• Assistant Examiner(s): RUSSELL, ANDREW D
• Application Number:
  US13/366,926
• Publication Number:
  US 20120203997A1
• Time in Patent Office: 1,380 Days
• Field of Search: 711/170
• US Class Current: 1/1
• CPC Class Codes: G01C 23/00 Combined instruments indicating more than one navigational value, e.g. for aircraft; Combined measuring devices for measuring two or more variables of movement, e.g. distance, speed or acceleration
• CPC Class Codes: G01C 23/005 Flight directors indicating arrangements specially adapted for rotary gyroscopes G01C19/32
• CPC Class Codes: G01C 25/00 Manufacturing, calibrating, cleaning, or repairing instruments or devices referred to in the other groups of this subclass testing, calibrating or compensating compasses G01C17/38
• CPC Class Codes: G06F 12/0284 Multiple user address space allocation, e.g. using different base addresses interprocessor communication G06F15/163
• CPC Class Codes: G06F 12/14 Protection against unauthorised use of memory or access to memory
• CPC Class Codes: G06F 12/1441 for a range
• CPC Class Codes: G06F 3/147 using display panels
• CPC Class Codes: G06F 9/5077 Logical partitioning of resources; Management or configuration of virtualized resources specific details on emulation or internal functioning of virtual machines G06F9/455
• CPC Class Codes: G09G 2380/12 Avionics applications

Abstract

Systems and methods are described here to provide a degree or level of certification to a resident application such as an operating system, e.g., Linux®. In a Linux® implementation, the operating system provides a robust environment including many seasoned communication stacks, e.g., TCP/IP, USB, and the like. However, Linux® is not certified to the level necessary to be a part of many avionics applications. To eliminate the need to certify all of such an operating system, such certification being highly costly, the avionics application itself may be protected so that the operating system cannot alter the application'"'"'s operating environment, e.g., application code and data, once the application is loaded and running. In this case, only the application requires certification at the highest level, and not the operating system such as Linux®.

Claims

1. A method of operating an avionics component, comprising:

a. configuring settings of a memory management unit to allocate a region of memory for an operating system and a region of memory for an application, the two regions non-overlapping;

b. running an operating system for the avionics component, within a memory region allocated to the operating system;

c. running the application, the application associated with the avionics component within a memory region allocated to the application; and

d. monitoring, at predefined intervals, the memory management unit to ensure the operating system cannot alter memory allocated to the application;

e. wherein the memory management unit is monitored to ensure that the operating system cannot write to memory allocated to the application.

2. The method of claim 1, wherein the memory management unit is monitored to ensure the operating system cannot address memory allocated to the application.

3. The method of claim 1, wherein if the monitoring indicates that the settings are such that the operating system can alter memory associated with the application, then further comprising causing an alert.

4. The method of claim 3, wherein the alert is visible or audible.

5. The method of claim 4, wherein the alert is a substantially blank screen.

6. The method of claim 1, wherein the application is selected from the group consisting of:

an altimeter, an airspeed indicator, a navigational indicator, and an attitude indicator.

7. The method of claim 1, wherein the monitoring includes monitoring a plurality of memory management units.

8. The method of claim 1, wherein the memory management unit, operating system, and application, are associated with the same avionics component.

9. The method of claim 1, wherein the memory management unit configures memory allocation such that application memory is unaddressable by the operating system.

10. A non-transitory computer-readable medium containing instructions for causing a computer to execute the method of claim 1.

11. An avionics component, comprising:

a. memory containing instructions for causing instantiation of an operating system;

b. memory containing instructions for causing instantiation of an application;

c. memory, configured by settings, containing instructions for separating the memories containing instructions for causing instantiation of an operating system and instantiation of an application; and

d. memory containing instructions for checking, at predefined intervals, the operation of the memory configured by settings, to ensure the operating system cannot write to memory allocated to the application.