1、INCITS TR-31-2002INCITS Technical Reportfor Information Technology Fibre Channel Avionics Environment (FC-AE)Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-INCITS TR-31-2002 INC
2、ITS Technical Report for Information Technology Fibre Channel Avionics Environment (FC-AE) Secretariat Information Technology Industry Council Abstract This report selects and restricts logical options from various Fibre Channel standards such that any device complying with one of the profiles in th
3、is report should interoperate with other devices that comply with the same profile. This report addresses requirements for switches and loops to support real-time avionics applications. Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproducti
4、on or networking permitted without license from IHS-,-,-INCITS Technical Report Series This Technical Report is one in a series produced by the American National Standards Committee, INCITS, Information Technology. The secretariat for INCITS is held by the Information Technology Industry Council (IT
5、I), 1250 Eye Street, NW, Suite 200, Washington DC 20005. As a by-product of the standards development process and the resources of knowledge devoted to it, INCITS from time to time produces Technical Reports. Such Technical Reports are not standards, nor are they intended to be used as such. INCITS
6、Technical Reports are produced in some cases to disseminate the technical and logical concepts reflected in standards already published or under development. In other cases, they derive from studies in areas where it is found premature to develop a rigorous standard due to the existence of a number
7、of viable options, the choice of which depends on the users particular requirements. These Technical Reports, thus, provide guidelines, the use of which can result in greater consistency and coherence of information processing systems. When the draft Technical Report is completed, the Technical Comm
8、ittee approval process is the same as for a draft standard. Processing by INCITS is also similar to that for a draft standard. PATENT STATEMENT CAUTION: The developers of this Technical Report have requested that holders of patents that may be required for the implementation of the Technical Report
9、disclose such patents to the publisher. However, neither the developers nor the publisher have undertaken a patent search in order to identify, which if any, patents may apply to this Technical Report. As of the date of publication of this Technical Report and following calls for the identification
10、of patents that may be required for the implementation of the Technical Report, no such claims have been made. No further patent search is conducted by the developer or the publisher in respect to any Technical Report it processes. No representation is made or implied that licenses are not required
11、to avoid infringement in the use of this Technical Report. Published by American National Standards Institute 25 W. 43rd Street, New York, New York 10036 Copyright 2002 by American National Standards Institute All rights reserved No part of this publication may be reproduced in any form, in an elect
12、ronic retrieval system or otherwise, without prior written permission of the publisher. Printed in the United States of America Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-ii
13、i Contents 1. Introduction . 1 2. Normative References 1 2.1 Approved references. 2 2.2 References under development 2 3. Definitions and conventions 3 3.1 Definitions 3 3.1.1 Implicit LIP 3 3.1.2 Anonymous Subscriber Messaging (ASM). 3 3.1.3 Fibre Channel Lightweight Protocol (FCLP).3 3.1.4 Remote
14、Direct Memory Access (RDMA) 3 3.1.5 Network Controller (NC) . 3 3.1.6 Network Terminal (NT) . 3 3.1.7 Command Frame 3 3.1.8 Data Frames. 3 3.1.9 Status Frame 3 3.1.10 Bus Identifier (B_ID) . 3 3.2 Editorial conventions . 4 3.2.1 Binary notation 4 3.2.2 Hexadecimal notation . 4 3.3 Abbreviations and
15、acronyms. 5 3.4 Applicability and use of this document 6 4. Profiles 7 4.1 Scope 7 4.2 Anonymous Subscriber Messaging (ASM) . 7 4.2.1 ASM Basic Services . 7 4.2.1.1 Link Protocols. 12 4.2.1.2 Arbitrated Loop 12 4.2.1.3 Addressing . 13 4.2.1.4 Class 1 . 13 4.2.1.5 Class 2 . 13 4.2.1.6 Class 3 . 13 4.
16、2.1.7 Class 4 . 13 4.2.1.8 Class 6 . 13 4.2.1.9 Priority 14 4.2.1.10 TYPE Field. 14 4.2.1.11 R_CTL Field. 14 Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-iv 4.2.1.12 F_CTL 14
17、4.2.1.13 SEQ_ID 14 4.2.1.14 DF_CTL 14 4.2.1.15 X_ID Interlock 14 4.2.1.16 Basic Link Services 14 4.2.1.17 Extended Link Services . 14 4.2.1.18 Fabric Login . 15 4.2.1.19 N_Port Login/Logout 15 4.2.1.20 Exchange Management . 15 4.2.1.21 Hunt Groups. 15 4.2.1.22 Clock Synchronization . 15 4.2.2 ASM St
18、ructure and Concepts. 15 4.2.2.1 Payload Structure 15 4.3 MIL-STD-1553. 17 4.3.1 Scope 17 4.3.1.1 Introduction 17 4.3.1.2 Mapping legacy 1553 applications to FC-AE-1553 . 18 4.3.2 FC-AE-1553 ULP Features 19 4.3.2.1 Information Units 19 4.3.2.2 Exchange (Message) Formats. 22 4.3.3 MIL-STD-1553 ULP Pr
19、ofile. 27 4.3.4 MIL-STD-1553 ULP Mapping to FC-AE-1553 31 4.3.4.1 MIL-STD-1553 Command Word Mapping to FC-AE-1553 31 4.3.4.2 R_CTL:. 32 4.3.4.3 Destination Identifier (D_ID). 32 4.3.4.4 Source Identifier (S_ID) . 32 4.3.4.5 TYPE Field. 32 4.3.4.6 NT-to-NT 32 4.3.4.7 NC Monitor for NT-to-NT Transfers
20、 . 32 4.3.4.8 T/R* 32 4.3.4.9 Transmitting or Receiving NT Address for NT-to-NT Transfers. . 32 4.3.4.10 Sub-address / Mode. 33 4.3.4.11 Data Word Count / Mode Code . 33 4.3.4.12 1553 Bus Select Enable. 33 4.3.4.13 1553 Bus B/A* 34 4.3.4.14 RT Address for MIL-STD-1553 RT 34 4.3.4.15 FC-AE-1553 Mode
21、Codes 34 Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-v 4.3.4.16 MIL-STD-1553B Status Word Mapping to FC-AE-1553 36 4.3.4.17 MIL-STD-1553 RT Addresses 38 4.3.4.18 No Response
22、by MIL-STD-1553 RT (bit 6 of Status Frame Header Word 9) . 38 4.3.4.19 1553 RT Format Error (bit 5 of Status Frame Header Word 9) . 39 4.3.5 FC-FS and FC-AL-2 Features for FC-AE-1553 39 4.3.5.1 Fabric-Specific Features 43 4.3.5.2 Arbitrated Loop-Specific Features . 44 4.3.5.3 N_Port Login 45 4.3.5.4
23、 FC-FS Header Fields . 47 4.3.5.5 Fabric Reject/Fabric Busy 48 4.3.5.6 Port Reject/Port Busy. 48 4.3.5.7 Basic Link Services 48 4.3.5.8 Extended Link Services . 48 4.3.5.9 Well Known Address Support 48 4.4 Virtual Interface (VI) 49 4.4.1 FC-VI Features for FC-AE-VI . 49 4.4.1.1 Connection Models 50
24、4.4.1.2 Transfer Models . 50 4.4.1.3 FCVI_Attributes 50 4.4.1.4 FCVI_Addressing. 50 4.4.2 FC-FS and FC-AL-2 Features for FC-AE-VI 51 4.4.2.1 Link Protocols. 57 4.4.2.2 Arbitrated Loop 57 4.4.2.3 Fabric Login . 58 4.4.2.4 N_Port Login 59 4.4.2.5 Fabric Reject/Fabric Busy 60 4.4.2.6 Port Reject/Port B
25、usy. 60 4.4.2.7 Well Known Address Support 60 4.4.2.8 Basic Link Services 60 4.4.2.9 Extended Link Services . 61 4.5 Fibre Channel Lightweight Protocol (FCLP) 62 4.5.1 FC-AE-FCLP Command Primitives 62 4.5.1.1 Setup Channel Command 62 4.5.1.2 Setup Channel Acknowledgement. 63 4.5.1.3 Send Data Comman
26、d 63 4.5.1.4 Close Channel Command 64 4.5.1.5 Return APIDs Command . 64 Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-vi 4.5.2 FCP Features for FC-AE-FCLP 64 4.5.2.1 Process Lo
27、gin Service Parameters . 66 4.5.2.2 Process Login Service Response Parameters 66 4.5.2.3 FCP Command IU 67 4.5.2.4 FCP Transfer Ready IU . 67 4.5.2.5 FCP Data IU. 67 4.5.2.6 FCP Response IU 67 4.5.3 FC-FS and FC-AL-2 Features for FC-AE-FCLP. 68 4.5.3.1 Link Protocols. 72 4.5.3.2 Arbitrated Loop 73 4
28、.5.3.3 Fabric Login . 73 4.5.3.4 N_Port Login 74 4.5.3.5 Well Known Address Support 75 4.5.3.6 Basic Link Services 75 4.5.3.7 Extended Link Services . 75 4.6 Remote Direct Memory Access (RDMA). 76 4.6.1 RDMA Enhancement to FCP 76 4.6.2 FCP Features for FC-AE-RDMA 76 4.6.2.1 Process Login Service Par
29、ameters . 78 4.6.2.2 FCP Command IU 79 4.6.2.3 FCP Transfer Ready IU . 79 4.6.2.4 FCP Data IU. 79 4.6.2.5 FCP Response IU 79 4.6.3 FC-FS and FC-AL-2 Features for FC-AE-RDMA . 81 4.6.3.1 Link Protocols. 87 4.6.3.2 Arbitrated Loop 87 4.6.3.3 Fabric Login . 88 4.6.3.4 N_Port Login 89 4.6.3.5 Fabric Rej
30、ect/Fabric Busy 90 4.6.3.6 Port Reject/Port Busy. 90 4.6.3.7 Well Known Address Support 90 4.6.3.8 Basic Link Services 90 4.6.3.9 Extended Link Services . 90 Annex A. 92 Bridging from FC-AE-1553 Networks to MIL-STD-1553 Buses 92 A.1 Bridging Between Legacy MIL-STD-1553 Buses and FC-AE-1553 Networks
31、92 Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-vii Figures Figure 1 ASM Header Format. 15 Figure 2 Network Controller To Network Terminal 22 Figure 3 Network Terminal-to-Netw
32、ork Controller . 22 Figure 4 NT to NT Transfers 23 Figure 5 Mode Command without Data Word . 24 Figure 6. Transmit Mode Command with Data Word 24 Figure 7 Receive Mode Command with Data Word 25 Figure 8 Controller to Multiple Remote Terminals . 25 Figure 9 Network Terminal to Multiple Network Termin
33、als26 Figure 10 Transmit Mode Command without Data Word to Multiple Network Terminals 26 Figure 11 Receive Mode Command with Data Word to Multiple Network Terminals 27 Figure 12 RDMA Parameter Field Usage Command IU 76 Figure A.13 FC-AE-1553 Network to MIL-STD-1553 Bus Bridge. 92 Tables Table 1 Summ
34、ary of Implementation and Use of Features 6 Table 2 FC-FS and FC-AL-2 Features for FC-AE-ASM . 7 Table 3 Terminology Equivalents between MIL-STD-1553 and FC-AE-1553 17 Table 4 Comparison of MIL-STD-1553 and FC-AE-1553 Command Field Sizes 18 Table 5 Information Units Initiated from the Network Contro
35、ller to Network Terminal . 19 Table 6 Information Units Initiated from the Network Terminal 21 Table 7 MIL-STD-1553B Notice 2 Profile for FC-AE-1553. 27 Table 8 FC-AE-1553 Command Frame Header.31 Table 9 FC-AE-1553 Status Frame Header 37 Table 10 FC-FS and FC-AL-2 Features for FC-AE-1553. 39 Table 1
36、1 FC-VI Features for FC-AE-VI. 49 Table 12 FC-FS and FC-AL-2 Features for FC-AE-VI51 Table 13 FCLP Command Codes. 62 Table 14 FCP Features for FC-AE-FCLP. 64 Table 15 FC-FS and FC-AL-2 Features for FC-AE-FCLP 68 Table 16 FCP Features for FC-AE-RDMA 77 Table 17 FC-FS and FC-AL-2 Features for FC-AE-RD
37、MA 81 Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or netw
38、orking permitted without license from IHS-,-,-INCITS Technical Report INCITS TR-31-2002 INCITS Technical Report for Information Technology Fibre Channel Avionics Environment (FC-AE) 1. Introduction Fibre Channel Avionics Environment (FC-AE) is a group of profiles that specify Fibre Channel options f
39、or devices connected by fabric and/or loop topologies that are pertinent to their use in commercial and military aerospace industries. The primary areas of interest include avionic command, control, instrumentation, simulation, signal processing, and sensor/video data distribution. These application
40、 areas are characterized by a variety of requirements, among them a need for high reliability, fault tolerance, and deterministic behavior to support real-time control/response. This report is intended to serve as an implementation guide whose primary objective is to maximize the likelihood of inter
41、operability between conforming implementations. This report Prohibits or requires features that are optional, and Prohibits the use of some non-optional features in the referenced ANSI standards. A second objective of this Technical Report is to simplify implementations and their associated docu-men
42、tation, testing, and support requirements. This means that there will be some optional features, which are not mutually exclusive but are still Prohibited or required solely for the purpose of this simplification. This Technical Report does not define internal characteristics of conformant implement
43、ations. This Technical Report incorporates features from the standards described below. Where needed, changes have been proposed to the appropriate INCITS technical committees to ensure this Technical Report remains a strict subset of ANSI standards. 2. Normative References The following standards c
44、ontain provisions, which through reference in the text constitute provisions of this Technical Report. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this Technical Report are encouraged to investigate the poss
45、ibility of applying the most recent editions of the standards listed below. Copies of the following documents can be obtained from ANSI: Approved ANSI standards, approved and draft international and regional standards (ISO, IEC, CEN/CENELEC), and approved foreign standards (including BSI, JIS, and D
46、IN). For further information, contact ANSI Customer Service Department at 212-642-4900 (phone), 212-302-1286 (fax) or via the World Wide Web at http:/www.ansi.org. Additional availability contact information is provided below as needed. Copyright American National Standards Institute Provided by IHS
47、 under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-INCITS TR-31-2002 2 2.1 Approved references 1 ANSI X3.230 1994, Information Technology Fibre Channel Physical and Signaling Interface (FC-PH) 2 ANSI X3.297 1997, Information Technology Fibre Ch
48、annel Physical and Signaling Interface 2 (FC-PH-2) 3 ANSI X3.303 1998, Information Technology Fibre Channel Physical and Signaling Interface 3 (FC-PH-3) 4 ANSI X3.272 1996, Information Technology Fibre Channel Arbitrated Loop (FC-AL) 5 INCITS.332 - 1999, Information Technology Fibre Channel Arbitrat
49、ed Loop - 2 (FC-AL-2) 6 ANSI X3.289 1996, Information Technology Fibre Channel Fabric Generic (FC-FG) 7 INCITS 348, Information Technology Fibre Channel Generic Services - 3 (FC-GS-3) 8 ANSI X3.269 1996, Information Technology Fibre Channel Protocol for SCSI (FCP) 9 MIL-STD-1553B Military Standard, Digital Time Division
