1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationBS EN 4660-002:2011Aerospace series Modular and Open AvionicsArchitecturesPart 002: Common Functional ModulesBS EN 4660-002:2011 BRITISH STANDARDNational forewordThis British Sta
2、ndard is the UK implementation of EN 4660-002:2011.The UK participation in its preparation was entrusted to TechnicalCommittee ACE/6, Aerospace avionic electrical and fibre optictechnology.A list of organizations represented on this committee can beobtained on request to its secretary.This publicati
3、on does not purport to include all the necessaryprovisions of a contract. Users are responsible for its correctapplication. BSI 2011ISBN 978 0 580 62442 1ICS 49.090Compliance with a British Standard cannot confer immunity fromlegal obligations.This British Standard was published under the authority
4、of theStandards Policy and Strategy Committee on 31 March 2011.Amendments issued since publicationDate Text affectedBS EN 4660-002:2011EUROPEAN STANDARD NORME EUROPENNE EUROPISCHE NORM EN 4660-002 February 2011 ICS 49.090 English Version Aerospace series - Modular and Open Avionics Architectures - P
5、art 002: Common Functional Modules Srie arospatiale - Architectures Avioniques Modulaires et Ouvertes - Partie 002: CFM Luft- und Raumfahrt - Modulare und offene Avionikarchitekturen - Teil 002: CFM This European Standard was approved by CEN on 26 June 2010. CEN members are bound to comply with the
6、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
7、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
8、 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, Rom
9、ania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG Management Centre: Avenue Marnix 17, B-1000 Brussels 2011 CEN All rights of exploitation in any form and by any means reserved
10、 worldwide for CEN national Members. Ref. No. EN 4660-002:2011: EBS EN 4660-002:2011EN 4660-002:2011 (E) 2 Contents Page Foreword 40 Introduction 50.1 Purpose .50.2 Document structure .61 Scope 61.1 Relationship with other ASAAC Standards 62 Normative references 73 Terms, definitions and abbreviatio
11、ns 73.1 Terms and definitions .73.2 Abbreviations .83.3 Conventions used in this Standard 104 CFM Definition . 104.1 Generic CFM 114.2 Module Support Unit. 134.3 Module Processing Capability . 204.4 Network Interface Unit (NIU) and Routing Unit (RU) . 294.5 Module Power Supply Element . 294.6 Module
12、 Physical Interface (MPI . 315 Common Functional Module Interfaces . 315.1 Module Logical Interface (MLI) 315.2 Module Physical Interface (MPI) 315.3 MOS Interface 326 CFM System Support and Guidelines. 326.1 Fault Management 336.2 Fault Detection 336.3 Fault Masking 336.4 Fault Confinement 336.5 Sa
13、fety and Security. 34Annex A (informative) Performance Sheet for all Common Functional Modules 36A.1 Data Processor Module 36A.2 Signal Processing Module . 37A.3 Graphic Processing Module 38A.4 Mass Memory Module 38A.5 Network Support Module . 39A.6 Power Conversion Module . 39Figures Page Figure 1
14、ASAAC Standard Documentation Hierarchy . 5 Figure 2 Functional representation of a generic CFM . 11 Figure 3 IMA Common Functional Modules Graphical Composition . 21 Figure 4 The Power Supply Distribution functions of the PCM . 26 Figure 5 Power Supply Element functions . 30 Figure 6 Software Archit
15、ecture Model - Three Layer Stack 32 BS EN 4660-002:2011EN 4660-002:2011 (E) 3 Tables Page Table 1 CFM Embedded Information Read Only . 14 Table 2 CFM Embedded Information Read / Write 15 Table 3 PCM output characteristics . 27 Table 4 PSE input voltage characteristics 30 Table A-1 Performance sheet
16、for a DPM . 36 Table A-2 Performance sheet for a SPM 37 Table A-3 Performance sheet for a GPM . 38 Table A-4 Performance sheet for a MMM 38 Table A-5 Performance sheet for a NSM . 39 Table A-6 Performance sheet for a PCM . 39 BS EN 4660-002:2011EN 4660-002:2011 (E) 4 Foreword This document (EN 4660-
17、002: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 Servic
18、es 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 lates
19、t 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 stan
20、dards 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,
21、Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. BS EN 4660-002:2011EN 4660-002:2011 (E) 5 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 o
22、pen architecture standards, concepts and 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 drivers for the
23、 ASAAC Programme are: 1. Reduced life cycle costs. 2. Improved mission performance. 3. Improved operational performance. The 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 requir
24、ed to implement the core within avionics systems, The guidelines for system implementation through application of the standards. The document hierarchy is given hereafter: (in this figure, the current document is highlighted) Guidelines for System Issues System Management Fault Management Initialisa
25、tion / Shutdown Configuration / Reconfiguration Time Management Security Safety Standards for Architecture Standards for Common Functional Modules Standards for Communications and Network Standards for Packaging Standards for Software Figure 1 ASAAC Standard Documentation Hierarchy BS EN 4660-002:20
26、11EN 4660-002:2011 (E) 6 0.2 Document structure The document contains the following clauses: Clause 1, scope of the document. Clause 2, normative references. Clause 3, the terms, definitions and abbreviations. Clauses 4 and 5 provide CFM concept definition, requirements and standards. Clause 6 provi
27、des guidelines for implementation of standards. Performance sheets for each of the CFMs are attached to the end of the document. These sheets contain a list of attributes to be defined by the system designer and used by the CFM provider. 1 Scope This standard defines the functionality and principle
28、interfaces for the Common Functional Module (CFM) to ensure the interoperability of Common Functional Modules and provides design guidelines to assist in implementation of such a CFM. It is one of a set of standards that define an ASAAC (Allied Standard Avionics Architecture Council) Integrated Modu
29、lar Avionics System. This definition of interfaces and functionality allows a CFM design that is interoperable with all other CFM to this standard, that is technology transparent, that is open to a multi-vendor market and that can make the best use of COTS technologies. Although the physical organis
30、ation and implementation of a CFM should remain the manufacturers choice, in accordance with the best use of the current technology, it is necessary to define a structure for each CFM in order to achieve a logical definition of the CFM with a defined functionality. This definition includes: The Gene
31、ric CFM, which defines the generic functionality applicable to the complete set of CFMs. The generic functionality is defined in 4.1. The processing capability, which defines the unique functionality associated with each CFM type within the set. This functionality is defined in 4.3. The logical and
32、physical interfaces that enable CFMs to be interoperable and interchangeable, these are defined in Clause 6. The functionality required by a CFM to support the operation of the System is defined in Clause 6. 1.1 Relationship with other ASAAC Standards The definition of the complete CFM is partitione
33、d and is covered by the following ASAAC standards: CFM Mechanical properties and physical Interfaces ASAAC Standards for Packaging. CFM Communication functions ASAAC Standards for Software. CFM Network interface ASAAC Standards for Communications and Network. CFM Software architecture ASAAC Standard
34、s for Software. CFM Functional requirements This document. BS EN 4660-002:2011EN 4660-002:2011 (E) 7 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 lat
35、est edition of the referenced document (including any amendments) applies. ISO 1540, Aerospace Characteristics of aircraft electrical systems EN 4660-001, Aerospace series Modular and Open Avionics Architectures Part 001: Architecture EN 4660-003, Aerospace series Modular and Open Avionics Architect
36、ures Part 003: Communications/Network 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 ASAAC2-GUI-32450-001-CPG Issue 01, Final Draft of Guidelines for System Issues 1) V
37、olume 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. 3 Terms, definitions and abbreviations 3.1 Terms and definitions Use of “shall”, “should” and “may” with
38、in the standards observe the following rules: The word SHALL in the text express 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 fo
39、llowed unless good reasons are stated for not doing so. 1) Published by: Allied Standard Avionics Architecture Council. BS EN 4660-002:2011EN 4660-002:2011 (E) 8 The word MAY in the text expresses a permissible practice or action. It does not express a requirement of the standard. Open System: A sys
40、tem with characteristics that comply with specified, publicly maintained, readily available standards and that therefore can be connected to other systems that comply with these same standards. 3.2 Abbreviations 2D : Two Dimensional 3D : Three Dimensional A3 : Advanced Avionics Architecture AGT : Ab
41、solute Global Time ALT : Absolute Local Time APOS : Application to Operating System Interface ASAAC : Allied Standard Avionics Architecture Council BIT : Built-in Test CBIT : Continuous BIT CFM : Common Functional Module CORBA : Common Object Request Broker Architecture COTS : Commercial Off The She
42、lf CRC : Cyclic Redundancy Check dc : Direct Current DPM : Data Processing Module DSP : Digital Signal Processor EDAC : Error Detection And Correction FFT : Fast Fouriert Transformation FIR : Finite Impulse response Filter FMECA : Fault Mode Effect and Criticality Analysis GPM : Graphic Processing M
43、odule GSM : Generic System Management HW : Hardware HDD : Head-Down Display HMD : Helmet Mounted Display HUD : Head-Up Display IBIT : Initiated BIT ID : Identification BS EN 4660-002:2011EN 4660-002:2011 (E) 9 IDL : Interface Definition Language IEEE : Institute of Electrical and Electronics Enginee
44、rs IFFT : Inverse Fast Fourier Transformation IMA : Integrated Modular Avionics ISO : International Standards Organisation ITM : Integrated Test and Maintenance JTAG : Joint Test Action Group MC : Module Controller MIS : Module Initialisation Support MLI : Module Logical Interface MMM : Mass Memory
45、Module MOS : Module Support Layer to Operating System Interface MPI : Module Physical Interface MSL : Module Support Layer MSU : Module Support Unit MTP : Maintenance Test Port N/A : Not Applicable NIU : Network Interface Unit NSM : Network Support Module OMG : Object Management Group O/P : Output O
46、S : Operating System OSL : Operating System Layer PBIT : Power-up / power-down BIT PCM : Power Conversion Module PCU : Power Conversion Unit PE : Processing Element PMS : Power Management System PSA : Power Switch Array PSE : Power Supply Element PU : Processing Unit RC : Reference Clock RLT : Relat
47、ive Local Time BS EN 4660-002:2011EN 4660-002:2011 (E) 10 RTBP : Runtime Blueprints RU : Routing Unit SPM : Signal Processing Module TC : Transfer Connection TLS : Three Layer Stack Vdc : Voltage dc 3.3 Conventions used in this Standard The Interface Definition Language (IDL) as defined in the Commo
48、n Object Request Broker Architecture (CORBA) 2.3 is used to express the MOS services as programming language independent services in this document. The conventions used in this document are as follows: 3.3.1 Special Fonts Words that have a special meaning appear in specific fonts or font styles. All
49、 code listings, reserved words and the name of actual data structures, constants, and routines are shown in Courier. 3.3.2 Naming Conventions Parameter and variable names contain only words with lower case letters, which are separated by underscore. Example vc_message NOTE Upper and lower case letters are treat
