EN 4660-003:2011

Aerospace series - Modular and Open Avionics Architectures - Part 003: Communications/Network

This standard details the functionality and principle interfaces for the ASAAC (Allied Standard Avionics Architecture Council) Network to ensure the interoperability of Common Functional Modules and design guidelines to assist in implementation of such a network. It is one of a set of standards that define an ASAAC Integrated Modular Avionics (IMA) System.
The purpose of this standard is to establish by means of well defined interfaces and functionality, a network design that is technology transparent, that is open to a multi-vendor market and that can make the best use of Commercial Off The Shelf (COTS) technologies. Therefore, the associated data communication network topology, protocols and technologies are not identified in this document. For these items the document identifies the issues that should be considered when defining a specific network implementation to support the ASAAC architecture and provides guidelines to assist.
Although the physical organisation and implementation of the network shall remain the System Designers choice, in accordance with the best use of the current technology, it is necessary to define interfaces and parameter sets in order to achieve a logical definition of the network with a defined functionality. This definition includes:
-   The generic functionality applicable to all networks.
-   The logical interfaces to the Operating System and Module Support Layers.
-   The physical interfaces to the Common Functional Modules (CFM).
The ASAAC Standards are intended to be independent of specific technologies, including network technologies.

Luft- und Raumfahrt - Modulare und offene Avionikarchitekturen - Teil 003: Kommunikation/Netzwerk

Diese Norm behandelt die Funktionalität und die Hauptschnittstellen für das ASAAC-Netzwerk, mit denen die
Interoperabilität von Standardfunktionsmodulen (CFM) sichergestellt werden soll; darüber hinaus enthält sie
Entwurfsleitlinien zur Unterstützung bei der Implementierung eines derartigen Netzwerks. Sie ist Teil einer
Reihe von Normen, die ein integriertes modulares Avioniksystem (IMA) definieren, das den Vorgaben des
ASAAC-Standards entspricht.
Zweck dieses Dokuments ist es, mittels wohl definierter Schnittstellen und Funktionalitäten einen Netzwerkentwurf
festzulegen, der technologisch transparent und für einen Markt mit einer Vielzahl von Herstellern offen
ist und COTS-Technologien am wirkungsvollsten nutzen kann. Daher sind die zugehörigen Topologien, Protokolle
und Technologien des Datenkommunikationsnetzes in diesem Dokument nicht benannt. Stattdessen
werden die Aspekte vorgestellt, die bei der Definition einer spezifischen Netzwerkimplementierung, die die
ASAAC-Architektur unterstützen soll, berücksichtigt werden sollten, und es sind entsprechende Leitlinien als
Hilfe angegeben.
Obwohl die physikalische Organisation und Implementierung des Netzwerks dem Systemplaner überlassen
bleiben muss, ist es im Sinne der wirkungsvollsten Nutzung der derzeitigen Technologien notwendig, Schnittstellen
und Parametersätze zu definieren, um eine logische Definition des Netzwerks mit einer definierten
Funktionalität zu erhalten: Die Definition umfasst:
⎯ die für alle Netzwerke geltende generische Funktionalität;
⎯ die logischen Schnittstellen zum OS und zu den MSL;
⎯ die physikalischen Schnittstellen zu den CFM.
Die ASAAC-Standards sollen von spezifischen Technologien, einschließlich Netzwerktechnologien, unabhängig
sein. Das vorliegende Dokument benennt in Abschnitt 4 die Hauptschnittstellen für das Netzwerk und gibt
gegebenenfalls Anforderungen an die zu definierenden Netzwerkparameter an. Die für das Netzwerk maßgebenden
Schnittstellen sind die Schnittstelle zwischen Modulunterstützungsschicht/Betriebssystem (MOS),
die physikalische Modulschnittstelle (MPI) und die logische Modulschnittstelle (MLI). Eine generische Definition
von MOS und MPI findet sich an anderer Stelle (siehe Standard für Software in EN 4660-005 und Standard
für Paketierung in EN 4660-004). Die MLI ist eindeutig vom gewählten Netzwerk abhängig. Die Definition
von MOS und MPI ist generisch und bedarf einer Unterstützung durch netzwerkspezifische Informationen. Die
Standards für Software und Paketierung enthalten keine netzwerkabhängigen Informationen. Eine zukünftige
Netzwerkspezifikation wird also nicht nur die jeweilige MLI definieren, sondern auch eine Definition der
spezifischen Aspekte der MPI, der Topologien, Systemeigenschaften usw. bieten müssen.

Série aérospatiale - Architectures Avioniques Modulaires et Ouvertes - Partie 003: Communication/Réseau

La présente norme définit la fonctionnalité et les principales interfaces du réseau ASAAC (Allied Standard Avionics Architecture Council) pour assurer l’interopérabilité des Modules fonctionnels communs et elle fournit des lignes directrices de conception pour faciliter la mise en oeuvre d’un tel réseau. Elle fait partie d’un ensemble de normes qui définit un système avionique modulaire intégré ASAAC (Allied Standard Avionics Architecture Council).
Le but de la présente norme est d'établir au moyen d'interfaces et d'une fonctionnalité bien définie, une conception de réseau qui soit transparente du point de vue technologique, ouverte à un marché multivendeur et qui puisse faire le meilleur usage des technologies liées aux articles sur étagère (COTS). Par conséquent, la topologie, les protocoles et les technologies du réseau de communication de données associées ne sont pas identifiés dans le présent document. Pour ces éléments, le document identifie les questions qu'il convient de prendre en compte quand on définit une mise en oeuvre de réseau spécifique pour assurer le soutien de l'architecture ASAAC et fournir les lignes directrices pour y parvenir.
Bien que l’organisation physique et la mise en oeuvre d’un réseau restent du domaine du choix du concepteur du système, conformément à l’utilisation optimale de la technologie courante, il est nécessaire de définir des interfaces et des paramètres pour obtenir une définition logique de réseau qui a une fonctionnalité définie. Cette définition comprend :
-   La fonctionnalité générique applicable à tous les réseaux.
-   Les interfaces logiques dédiées au système d'exploitation et aux couches de support de modules.
-   Les interfaces physiques dédiées aux Modules fonctionnels communs (CFM).
Les normes ASAAC sont destinées à être indépendantes des technologies spécifiques, y compris les technologies des réseaux. Ce document identifie les principales interfaces relatives au réseau, dans l'Article 4, et si approprié, il fournit les exigences sur les paramètres du réseau à définir. Les interfaces correspondant au réseau sont l’interface entre la couche support de module et le système d’exploitation (MOS), l'interface physique de modules (MPI) et l'interface logique de modules (MLI). Les MOS et MPI sont définis génériquement ailleurs (normes pour le Software voir l'EN 4660-005 et le Packaging voir l'EN 4660-004). La MLI est clairement une fonction du réseau choisi. Les définitions du MOS et de la MPI sont génériques et nécessiteront d'être soutenues par des informations spécifiques au réseau. Il n'existe pas d'informations dépendantes du réseau dans les normes pour le Software et le Packaging. Donc, une spécification future de réseau ne définira pas uniquement la MLI spéciale, mais elle nécessitera aussi de définir les aspects spécifiques de la MLI, les topologies, les propriétés du système, etc.
1.1   Relation avec les autres Normes ASAAC
La définition des interfaces complètes de communications et de réseau est divisée en parties et elle est couverte par les normes ASAAC suivantes :
-   Interfaces physiques de réseau – Normes ASAAC pour le Packaging.
-   Fonctions de communication de module à module – Normes ASAAC pour le Software.
-   Interface de réseau du système d'exploitation – Normes ASAAC pour le Software.
-   Architecture du logiciel du CFM – Normes ASAAC pour le Software.
-   Exigences et propriétés physiques du réseau qui définissent l'aptitude et le comportement requis pour assurer le soutien des communications CFM vers CFM, dans le présent document.

Aeronavtika - Modularne in odprte letalske elektronske arhitekture - 003. del: Komunikacije/omrežje

1.1 Splošno
Ta standard podrobno opisuje funkcionalnosti in glavne vmesnike za omrežje ASAAC (Svet za povezane standarde letalske arhitekture), da zagotovi interoperabilnost splošnih funkcionalnih modulov in smernice pri načrtovanju za pomoč pri implementaciji takega omrežja. Je eden izmed niza standardov, ki določa integriran modularni letalski (IMA) sistem ASAAC.
Namen tega standarda je z dobro določenimi vmesniki in funkcionalnostjo vzpostaviti načrt omrežja, ki je tehnološko pregleden, odprt za trg z več dobavitelji in lahko kar najbolje izkoristi komercialne nespecializirane (COTS) tehnologije. Zato povezana omrežna topologija podatkovne komunikacije, protokoli in tehnologije niso določeni v tem dokumentu. Za te postavke dokument opredeljuje vprašanja, ki jih je treba upoštevati, kadar definiramo določeno implementacijo omrežja za podporo arhitekture ASAAC, in za pomoč podaja smernice.
Čeprav bo fizična organizacija in implementacija omrežja ostala izbira načrtovalca sistema v skladu z najboljšo uporabo trenutne tehnologije, je treba določiti vmesnike in nize parametrov, da dosežemo logično definicijo omrežja z določeno funkcionalnostjo. Ta definicija vključuje:
- splošno funkcionalnost, ki velja za vsa omrežja,
- logične vmesnike za delovni sistem in plasti podpore modula,
- fizične vmesnike za splošne funkcionalne module (CFM).
Standardi ASAAC so neodvisni od nekaterih tehnologij, vključno z omrežnimi tehnologijami. Ta dokument v točki 4 določa glavne vmesnike za omrežje in, kjer je primerno, podaja zahteve za omrežne parametre, ki jih je treba določiti. Vmesniki, pomembni za omrežje, so plast podpore modula za delovni sistem (MOS), fizičnega vmesnika modula (MPI) in logični vmesnik modula (MLI). (...)

General Information

• Status: Withdrawn
• Publication Date: 22-Feb-2011
• Withdrawal Date: 20-Aug-2019
• ICS: 49.090 - On-board equipment and instruments
• Technical Committee: ASD-STAN - Aerospace
• Drafting Committee: ASD-STAN/D 1 - General
• Current Stage: 9960 - Withdrawal effective - Withdrawal
• Completion Date: 21-Aug-2019
• Ref Project: SIST EN 4660-003:2011 - Aerospace series - Modular and Open Avionics Architectures - Part 003: Communications/Network

Relations

• Replaced By: EN 4660-003:2019 - Aerospace series - Modular and Open Avionics Architectures - Part 003: Communications/Network
• Effective Date: 08-Jun-2022

Standards Content (Sample)

SLOVENSKI STANDARD
01-december-2011
Aeronavtika - Modularne in odprte letalske elektronske arhitekture - 003. del:
Komunikacije/omrežje
Aerospace series - Modular and Open Avionics Architectures - Part 003:
Communications/Network
Luft- und Raumfahrt - Modulare und offene Avionikarchitekturen - Teil 003:
Kommunikation/Netzwerk
Série aérospatiale - Architectures Avioniques Modulaires et Ouvertes - Partie 003:
Communication/Réseau
Ta slovenski standard je istoveten z: EN 4660-003:2011
ICS:
49.090 2SUHPDLQLQVWUXPHQWLY On-board equipment and
]UDþQLKLQYHVROMVNLKSORYLOLK instruments
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD
EN 4660-003
NORME EUROPÉENNE
EUROPÄISCHE NORM
February 2011
ICS 49.090
English Version
Aerospace series - Modular and Open Avionics Architectures -
Part 003: Communications/Network
Série aérospatiale - Architectures Avioniques Modulaires et Luft- und Raumfahrt - Modulare und offene
Ouvertes - Partie 003: Communication/Réseau Avionikarchitekturen - Teil 003: Kommunikation/Netzwerk
This European Standard was approved by CEN on 26 June 2010.

CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European
Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national
standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN member.

This European Standard exists in three official versions (English, French, German). A version in any other language made by translation
under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management Centre has the same
status as the official versions.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland,
Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom.

EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2011 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN 4660-003:2011: E
worldwide for CEN national Members.

Contents Page
Foreword .3
0 Introduction .4
0.1 Purpose .4
0.2 Document structure .5
1 Scope .5
1.1 Relationship with other ASAAC Standards .6
2 Normative references .6
3 Terms, Definitions and Abbreviations .7
3.1 Terms and definitions .7
3.2 Abbreviations .7
4 Network Definition .8
4.1 Overview .8
4.2 Specific Network Requirements .9
4.3 MOS - Communications Services Interface . 12
4.4 Module Physical Interface . 12
4.5 Module Logical Interface . 12
4.6 MLI - Network Properties . 13
5 Discussion of Issues related to the Network . 17
5.1 Issues relating to the Network Structure . 17
5.2 Issues related to the MOS Communication Services. 18
5.3 Issues relating to the Overall Network . 19
Figures
Figure 1 — ASAAC Standards Documentation Hierarchy . 4
Figure 2 — Software and Communications Model . 9
Figure 3 — ASAAC Communication Interfaces . 16
Tables
Table 1 — Architecture Requirements. 9
Table 2 — System Requirements . 11

Foreword
This document (EN 4660-003:2011) has been prepared by the Aerospace and Defence Industries Association
of Europe - Standardization (ASD-STAN).
After enquiries and votes carried out in accordance with the rules of this Association, this Standard has
received the approval of the National Associations and the Official Services of the member countries of ASD,
prior to its presentation to CEN.
This European Standard shall be given the status of a national standard, either by publication of an identical
text or by endorsement, at the latest by August 2011, and conflicting national standards shall be withdrawn at
the latest by August 2011.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights.
According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following
countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech
Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain,
Sweden, Switzerland and the United Kingdom.

0 Introduction
0.1 Purpose
This document was produced under the ASAAC Phase II Contract.
The purpose of the ASAAC Programme is to define and validate a set of open architecture standards,
concepts & guidelines for Advanced Avionics Architectures (A3) in order to meet the three main ASAAC
drivers. The standards, concepts and guidelines produced by the Programme are to be applicable to both new
aircraft and update programmes
The three main goals for the ASAAC Programme are:
1. Reduced life cycle costs.
2. Improved mission performance.
3. Improved operational performance.
The ASAAC Standards are organised as a set of documents including:
A set of agreed standards that describe, using a top down approach, the Architecture overview to all
interfaces required to implement the core within avionics system.
The guidelines for system implementation through application of the standards.
The document hierarchy is given hereafter: (in this figure the document is highlighted)

Standard for Architecture
Guidelines for System Issues
Standard for Software
• System Management
• Fault Management
• Initialisation / Shutdown
• Configuration / Reconfiguration
• Time Management
Standard for Packaging
• Security
• Safety
Standard for Communications and
Network
Standard for Common Functional Modules

Figure 1 — ASAAC Standards Documentation Hierarchy
0.2 Document structure
The document contains the following clauses:
Clause 1, Scope of the document
Clause 2, Normative references
Clause 3, Terms, definitions and abbreviations,
Clause 4, Network definition
Clause 5, Discussion of issues related to the network.
1 Scope
This standard details the functionality and principle interfaces for the ASAAC (Allied Standard Avionics
Architecture Council) Network to ensure the interoperability of Common Functional Modules and design
guidelines to assist in implementation of such a network. It is one of a set of standards that define an ASAAC
Integrated Modular Avionics (IMA) System.
The purpose of this standard is to establish by means of well defined interfaces and functionality, a network
design that is technology transparent, that is open to a multi-vendor market and that can make the best use of
Commercial Off The Shelf (COTS) technologies. Therefore, the associated data communication network
topology, protocols and technologies are not identified in this document. For these items the document
identifies the issues that should be considered when defining a specific network implementation to support the
ASAAC architecture and provides guidelines to assist.
Although the physical organisation and implementation of the network shall remain the System Designers
choice, in accordance with the best use of the current technology, it is necessary to define interfaces and
parameter sets in order to achieve a logical definition of the network with a defined functionality. This definition
includes:
 The generic functionality applicable to all networks.
 The logical interfaces to the Operating System and Module Support Layers.
 The physical interfaces to the Common Functional Modules (CFM).
The ASAAC Standards are intended to be independent of specific technologies, including network
technologies. This document identifies the principle interfaces for the Network, in Clause 4, and where
appropriate, provides requirements on network parameters to be defined. The interfaces relevant to the
network are the Module Support Layer to Operating System (MOS), Module Physical Interface (MPI) and
Module Logical Interface (MLI). The MOS and MPI are generically defined elsewhere (Standards for Software
see EN 4660-005 and Packaging see EN 4660-004). The MLI is clearly a function of the selected network.
The MOS and MPI definitions are generic and will need to be supported by network specific information.
There is no network-dependent information in the Software or Packaging standards. So a future network
specification will not only define the particular MLI, but will also need to define the specific aspects of the MPI,
topologies, system properties etc.
1.1 Relationship with other ASAAC Standards
The definition of the complete Communications and Network Interfaces is partitioned and is covered by the
following ASAAC standards:
 Network physical Interfaces – ASAAC Standards for Packaging.
 Module to Module Communication functions – ASAAC Standards for Software.
 Operating System to Network interface – ASAAC Standards for Software.
 CFM Software Architecture – ASAAC Standards for Software.
 Network physical requirements and properties that define the capability and behaviour required to support
CFM to CFM communications – This document.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO/IEC 7498-1, Open System Interconnect Basic Reference Model
EN 4660-001, Aerospace series — Modular and Open Avionics Architectures — Part 001: Architecture
EN 4660-002, Aerospace series — Modular and Open Avionics Architectures — Part 002: Common
Functional Modules
EN 4660-004, Aerospace series — Modular and Open Avionics Architectures — Part 004: Packaging
EN 4660-005, Aerospace series — Modular and Open Avionics Architectures — Part 005: Software
MIL-STD-1553B, Multiplex Data Bus
1)
ASAAC2-GUI-32450-001-CPG Issue 01, Final Draft of Guidelines for System Issues.
— Volume 1 — System Management.
— Volume 2 — Fault Management.
— Volume 3 — Initialisation and Shutdown.
— Volume 4 — Configuration / Reconfiguration.
— Volume 5 — Time Management.
— Volume 6 — Security.
— Volume 7 — Safety.
1) In preparation at the date of publication of this standard.
3 Terms, Definitions and Abbreviations
3.1 Terms and definitions
Use of “shall”, “should” and “may” within the standards observe the following rules:
 The word SHALL in the text expresses a mandatory requirement of the standard.
 The word SHOULD in the text expresses a recommendation or advice on implementing such a
requirement of the standard. It is expected that such recommendations or advice will be followed
...