# ARINC 653 Temporal and Spatial Partitioning

> ARINC 653 isolates avionics applications in both memory and time through partition scheduling, controlled communication and health-monitoring policy.

- Author: Muhammet Ali Köker
- Language: en
- Canonical: https://alikoker.com.tr/en/arinc-653-temporal-and-spatial-partitioning
- Translation: https://alikoker.com.tr/arinc-653-zamansal-ve-mekansal-bolumlendirme
- Published: 2022-06-15T12:00:00+03:00
- Modified: 2026-08-30T14:55:00+03:00
- Type: article

In a safety-critical computer, memory isolation alone is not sufficient. If a lower-criticality application consumes CPU at the wrong time, a more critical function can miss its deadline. Isolation therefore has both spatial and temporal dimensions.

My early avionics experience made the difference between “runs fast” and “runs at a predictable time” especially concrete.

## Why IMA needs partitions

Integrated Modular Avionics consolidates applications on shared computing platforms. Hardware can be reduced, but CPU, memory and communication resources must be isolated explicitly.

## Spatial partitioning

A partition must not read or modify memory assigned to another partition. This boundary is enforced by the platform and configuration, not only by application discipline.

## Temporal partitioning

Partitions receive execution windows inside a repeating major frame:

```text
major frame
| P1 | P2 | P3 | P1 | ...
```

The important property is whether each partition receives its configured time window predictably.

## A second scheduler exists inside the partition

The platform schedules partitions; each partition then schedules its own processes. These are different levels of timing analysis.

## Controlled communication

Sampling and queuing ports provide explicit communication paths. Isolation would be incomplete if applications could bypass partition boundaries through uncontrolled shared state.

## Health monitoring is more than logging

Health-monitoring policy can map faults to process-, partition- or module-level actions. The question is not only whether an event is recorded, but what recovery action follows.

## Configuration is part of correctness

Time windows, memory regions, ports and health-monitoring rules are configuration artifacts that can invalidate an otherwise correct application if they are wrong.

## Worst-case behavior over average throughput

A real-time partition is evaluated against execution budget and interference under worst-case assumptions rather than average requests per second.

The broader lesson is that shared hardware can still provide strong isolation when memory, time, communication and failure handling are designed together.

## References

- ARINC653P1-6, *Avionics Application Software Standard Interface*
- TÜBİTAK BİLGEM real-time operating-system adaptation publications

## Cite This Work

Köker, M. A. (2022). ARINC 653 Temporal and Spatial Partitioning. alikoker.com.tr. https://alikoker.com.tr/en/arinc-653-temporal-and-spatial-partitioning

- BibTeX: https://alikoker.com.tr/en/arinc-653-temporal-and-spatial-partitioning.bib
- RIS: https://alikoker.com.tr/en/arinc-653-temporal-and-spatial-partitioning.ris
- CSL-JSON: https://alikoker.com.tr/en/arinc-653-temporal-and-spatial-partitioning.csl.json