A portable ARINC 653 standard interface
A portable ARINC 653 standard interface
复制标题
DOI：
10.1109/dasc.2008.4702767
复制
发表时间：
2008-12
期刊：
影响因子：
--
通讯作者：
S. Santos;José Rufino;T. Schoofs;C. Tatibana;James Windsor
中科院分区：
文献类型：
--
作者：
S. Santos;José Rufino;T. Schoofs;C. Tatibana;James Windsor
ARINC 653规范定义了操作系统（OS）必须保证的功能，以执行强大的空间和时间分区以及系统的航空电子应用程序编程接口。标准应用程序接口-ARINC 653应用程序执行程序（APEX）-被定义为一组兼容操作系统必须向航空电子应用程序开发人员提供的软件服务。ARINC 653规范定义了APEX的接口和行为，但将实现细节留给了操作系统供应商。本文描述了一种与操作系统无关的可移植APEX接口的设计方法。POSIX作为一种可用于各种现代操作系统的编程接口，将用于实现APEX层。通过这种方式，APEX的标准化更进了一步：不仅服务的定义是标准化的，而且它与底层操作系统的接口也是标准化的。因此，APEX操作不依赖于特定的操作系统，而是依赖于一组定义良好的标准化组件。
The ARINC 653 specification defines the functionality that an operating system (OS) must guarantee to enforce robust spatial and temporal partitioning as well as an avionics application programming interface for the system. The standard application interface - the ARINC 653 application executive (APEX) - is defined as a set of software services a compliant OS must provide to avionics application developers. The ARINC 653 specification defines the interfaces and the behavior of the APEX but leaves implementation details to OS vendors. This paper describes an OS independent design approach of a portable APEX interface. POSIX, as a programming interface available on a wide range of modern OS, will be used to implement the APEX layer. This way the standardization of the APEX is taken a step further: not only the definition of services is standardized but also its interface to the underlying OS. Therefore, the APEX operation does not depend on a particular OS but relies on a well defined set of standardized components.