1、American National StandardDeveloped byINCITS Technical Reportfor Information Technology Fibre Channel Avionics Environment Upper Layer Protocol(FC-AE-1553)INCITS TR-42-2007INCITS TR-42-2007Reaffirmed as INCITS/TR-42-2007 (R2017)INCITS TR-42-2007INCITS Technical Reportfor Information TechnologyFibre
2、Channel Avionics Environment Upper Layer Protocol(FC-AE-1553)SecretariatInformation Technology Industry CouncilAbstractThis report selects and restricts logical options from various Fibre Channel standards such that any devicecomplying with one of the profiles in this report should interoperate with
3、 other devices that comply with thesame profile. This report addresses requirements for switches and loops to support real-time avionics ap-plications.Published byAmerican National Standards Institute25 West 43rd Street, New York, New York 10036Copyright 2007 by Information Technology Industry Counc
4、il (ITI)All rights reserved.No part of this publication may be reproduced in anyform, in an electronic retrieval system or otherwise, without prior written permission of the publisher.Printed in the United States of AmericaINCITS Technical Report SeriesThis Technical Report is one in a series produc
5、ed by the International Committeefor Information Technology Standards (INCITS). The secretariat for INCITS is heldby the Information Technology Industry Council (ITI), 1250 Eye Street, NW, Suite200, Washington, DC 2005.As a by-product of the standards development process and the resources ofknowledg
6、e devoted to it, INCITS from time to time produces Technical Reports.Such Technical Reports are not standards, nor are they intended to be used assuch.INCITS Technical Reports are produced in some cases to disseminate thetechnical and logical concepts reflected in standards already published or unde
7、rdevelopment. In other cases, they derive from studies in areas where it is foundpremature to develop a standard due to a still changing technology, orinappropriate to develop a rigorous standard due to the existence of a number ofviable options, the choice of which depends on the users particular r
8、equirements.These Technical Reports, thus, provide guidelines, the use of which can result ingreater consistency and coherence of information processing systems.When the draft Technical Report is completed, the Technical Committee approvalprocess is the same as for a draft standard. Processing by IN
9、CITS is also similarto that for a draft standard.PatentStatementCAUTION: The developers of this Technical Report have requested that holdersof patents that may be required for the implementation of the standard, disclosesuch patents to the publisher. However, neither the developers nor the publisher
10、have undertaken a patent search in order to identify which, if any, patents mayapply to this Technical Report. As of the date of publication of this Technical Report and following calls for theidentification of patents that may be required for the implementation of theTechnical Report, no such claim
11、s have been made. No further patent search isconducted by the developer or the publisher in respect to any Technical Report itprocesses. No representation is made or implied that licenses are not required toavoid infringement in the use of this Technical Report.TABLE OF CONTENTS Foreword . vi Introd
12、uction xii 1 Scope 1 2 Normative References. 1 2.1 OVERVIEW1 2.2 APPROVED REFERENCES.2 2.3 REFERENCES UNDER DEVELOPMENT2 3 Definitions and conventions 2 3.1 OVERVIEW2 3.2 DEFINITIONS .2 3.2.1 Introduction .2 3.2.2 Command Sequence 2 3.2.3 Data Sequence .2 3.2.4 Exchange 3 3.2.5 First/Middle/Last (FM
13、L) .3 3.2.6 Frame3 3.2.7 Information Category.3 3.2.8 Network Controller (NC)3 3.2.9 Network Terminal (NT)3 3.2.10 Sequence3 3.2.11 Sequence Initiative3 3.2.12 Status Sequence.3 3.3 EDITORIAL CONVENTIONS .3 3.3.1 Introduction .3 3.3.2 Binary notation 4 3.3.3 Hexadecimal notation4 3.4 ABBREVIATIONS A
14、ND ACRONYMS 4 3.5 APPLICABILITY AND USE OF THIS DOCUMENT5 4 FC-AE-1553 Profile . 6 4.1 SCOPE .6 4.2 INTRODUCTION6 4.3 MAPPING LEGACY 1553 APPLICATIONS TO FC-AE-15537 4.4 FC-AE-1553 ULP FEATURES.9 4.4.1 Information Units.9 4.4.2 Exchange Formats15 4.4.2.1 Introduction 15 4.4.2.2 FC-AE-1553 Network Co
15、ntroller to Network Terminal Transfers (Write-Type Commands) .15 4.4.2.2.1 Introduction .15 4.4.2.2.2 NT Burst Size Request = 0b and Delayed NT Burst Size Request = 0b 15 4.4.2.2.3 NT Burst Size Request = 1b and Delayed NT Burst Size Request = 0b 16 4.4.2.2.4 Delayed NT Burst Size Request = 1b and N
16、T Burst Size Request = 0b19 4.4.2.3 Network Terminal to Network Controller Transfers (Read-Type Commands) 20 4.4.2.4 Network Terminal to Network Terminal Transfers (Third Party Transfers) .21 4.4.2.4.1 Introduction .21 4.4.2.4.2 Burst Size Request = 0b, Delayed NT Burst Size Request = 0b21 4.4.2.4.3
17、 NT Burst Size Request = 1b, Delayed NT Burst Size Request = 0b23 4.4.2.4.4 Originating NC is also receiving NT, with NT Burst Size Request = 1b, Delayed NT Burst Size Request = 0b.25 4.4.2.4.5 Delayed NT Burst Size Request = 1b, NT Burst Size Request = 0b26 4.4.2.4.6 Case where originating NC is al
18、so receiving NT, with Delayed NT Burst Size Request = 1b, NT Burst Size Request =0b28 4.4.2.5 Mode Command Without Data Word Transfers .30 4.4.2.6 Transmit Mode Command with Data Word Transfers .31 i INCITS TR-42-2007 4.4.2.7 Receive Mode Command with Data Word Transfers.31 4.4.2.8 Network Controlle
19、r to Multiple Network Terminals Transfers (Broadcast or Multicast) 32 4.4.2.9 Network Terminal to Multiple Network Terminal Transfers 33 4.4.2.10 Mode Command to Multiple NTs Without Data Word Transfers 35 4.4.2.11 Mode Command (Receive) to Multiple NTs with Data Word Transfers36 4.4.3 FC-AE-1553 UL
20、P Profile .37 4.4.4 MIL-STD-1553 ULP Mapping to FC-AE-1553 .40 4.4.4.1 MIL-STD-1553 Command Word Mapping to FC-AE-155340 4.4.4.1.1 Introduction .40 4.4.4.1.2 R_CTL.40 4.4.4.1.3 Routing Bits.40 4.4.4.1.4 Information Category Bits40 4.4.4.1.5 Destination Identifier (D_ID)40 4.4.4.1.6 Broadcast and Mul
21、ticast Exchanges .41 4.4.4.1.7 CS_CTL 42 4.4.4.1.8 Source Identifier (S_ID).43 4.4.4.1.9 TYPE Field43 4.4.4.1.10 Parameter Field.43 4.4.4.1.11 NT Burst Size Request43 4.4.4.1.12 Delayed NT Burst Size Request43 4.4.4.1.13 Receive RDMA44 4.4.4.1.14 Transmit RDMA.44 4.4.4.1.15 Suppress Status45 4.4.4.1
22、.16 NT-to-NT .45 4.4.4.1.17 T/R*.45 4.4.4.1.18 NC MONITOR FOR NT-TO-NT TRANSFERS45 4.4.4.1.19 MULTICAST45 4.4.4.1.20 Subaddress/Mode.46 4.4.4.1.21 Data Byte Count/Mode Code 47 4.4.4.1.22 Transmitting NT Status Word for NT-to-NT Transfers.47 4.4.4.1.23 Multicast Address or Other Port_ID.48 4.4.4.1.24
23、 Other Subaddress.48 4.4.4.2 FC-AE-1553 Mode Codes.49 4.4.4.2.1 Introduction 49 4.4.4.2.2 Dynamic Network Control hex 00 00 00 00 (T/R* = 1b)49 4.4.4.2.3 Synchronize (without data word) hex 00 00 00 01 (T/R* = 1b).49 4.4.4.2.4 Transmit Status Sequence hex 00 00 00 02 (T/R* = 1b)49 4.4.4.2.5 Initiate
24、 Self-Test hex 00 00 00 03 (T/R* = 1b)49 4.4.4.2.6 Transmitter Shutdown hex 00 00 00 04 (T/R* = 1b).49 4.4.4.2.7 Override Transmitter shutdown hex 00 00 00 05 (T/R* = 1b).50 4.4.4.2.8 Inhibit Terminal Flag (T/F) hex 00 00 00 06 (T/R* = 1b).50 4.4.4.2.9 Override Inhibit Terminal Flag hex 00 00 00 07
25、(T/R* = 1b).50 4.4.4.2.10 Reset Network Terminal hex 00 00 00 08 (T/R* = 1b) .50 4.4.4.2.11 Transmit Vector Word hex 00 00 00 10 (T/R* = 1b).50 4.4.4.2.12 Synchronize (with data word) hex 00 00 00 11 (T/R* = 0b)50 4.4.4.2.13 Transmit Last Command Sequence hex 00 00 00 12 (T/R* = 1b) .50 4.4.4.2.14 T
26、ransmit Built In Test (BIT) Word hex 00 00 00 13 (T/R* = 1b) .50 4.4.4.2.15 Selected Transmitter Shutdown hex 00 00 00 14 (T/R* = 0b)51 4.4.4.2.16 Override Selected Transmitter Shutdown hex 00 00 00 15 (T/R* = 0b) .51 4.4.4.2.17 Transmit RT Address hex 00 00 00 16 (T/R* = 1b)51 4.4.4.2.18 Transmit N
27、T_C-D/S_BURST_TOV hex 00 00 00 17 (T/R* = 1b).51 4.4.4.3 MIL-STD-1553B Status Word Mapping to FC-AE-155351 4.4.4.3.1 Introduction .51 4.4.4.3.2 No Response by MIL-STD-1553 RT, bit 14.52 4.4.4.3.3 MIL-STD-1553 RT Format Error, bit 13.53 4.4.4.3.4 Burst Size Acknowledge, bit 12.53 4.4.4.3.5 Port Login
28、 Required, bit 11 .53 4.4.4.3.6 Message Error Bit, bit 10.54 4.4.4.3.7 Instrumentation Bit, bit 9 .54 4.4.4.3.8 Service Request Bit, bit 854 4.4.4.3.9 Broadcast Command Received Bit, bit 4.54 4.4.4.3.10 Busy Bit, bit 3 54 ii INCITS TR-42-2007 4.4.4.3.11 Subsystem Flag Bit, bit 2 54 4.4.4.3.12 Dynami
29、c Network Control Acceptance Bit, bit 154 4.4.4.3.13 Terminal Flag Bit, bit 0 55 4.4.4.4 FC-AE-1553 ULP Timers 55 4.4.4.4.1 Introduction 55 4.4.4.4.2 NT_C/S_TOV .55 4.4.4.4.3 NT_C-D/S_BURST_TOV .55 4.4.4.4.4 NC_CS _TOV.55 4.4.4.4.5 NC_C-D/S_BURST_TOV.55 4.4.4.4.6 C-S/D_RX _TOV 55 4.4.4.4.7 C-S/D _RX
30、 _TOV .56 4.4.4.5 NT Sequence(s) Validation and Response .58 4.4.4.6 NC Timeouts .65 4.4.4.7 Use of ABTS and RRQ .66 Annex A FC-AE-1553 Process Login . 67 A.1 Overview of Process Login and Process Logout. 67 A.2 PRLI 68 A.2.1 Use of PRLI by FC-AE-1553 . 68 A.2.2 Process_Associator requirements. 68 A
31、.2.3 New or repeated Process Login . 68 A.2.4 PRLI Payload Page Length and Payload Length Fields 68 A.2.5 PRLI request FC-AE-1553 Service Parameter page format. 69 A.2.6 Operation of PRLI Service Parameters which Are Common to NC and NT . 74 A.3 PRLO 74 Annex B FC-AE-1553 Fibre Channel Profile . 76
32、B.1 Introduction 76 B.2 FC-FS-2 and FC-AL-2 Features for FC-AE-1553 76 B.3 Point-to-Point and Link Protocols. 79 B.4 Arbitrated Loop-Specific Features. 79 B.5 Fabric Login. 80 B.5.1 Introduction .80 B.5.2 Fabric Login Common Service Parameters .80 B.5.3 Fabric Login Class Specific Service Parameters
33、81 B.6 Port Login . 81 B.6.1 Introduction .81 B.6.2 Classes of Service Supported.81 B.6.3 N_Port Login Common Service Parameters 81 B.6.4 N_Port Login Class 3 Service Parameters.81 B.7 Basic Link Services . 82 B.8 Broadcast and Multicast Support. 82 B.9 FC-FS Header Fields. 82 B.9.1 R_CTL FIELD .82
34、iii INCITS TR-42-2007 B.9.2 TYPE FIELD .82 B.9.3 OPTIONAL HEADERS .82 B.9.4 FRAME CONTROL (F_CTL) .82 B.9.5 SEQUENCE IDENTIFIER (SEQ_ID)83 B.9.6 DATA FIELD CONTROL (DF_CTL) .83 B.9.7 SEQUENCE COUNT (SEQ_CNT)83 B.9.8 ORIGINATOR EXCHANGE IDENTIFIER (OX_ID) 83 B.9.9 RESPONDER EXCHANGE IDENTIFIER (RX_ID
35、).83 B.10 Extended Link Services . 83 B.11 Well Known Address Support 83 Annex C Bridging from FC-AE-1553 Networks to MIL-STD-1553 Buses 84 LIST OF FIGURES Figure 1 Network Controller To Network Terminal Transfers: 16 Figure 2 Network Controller To Network Terminal Transfers: 17 Figure 3 Network Con
36、troller To Network Terminal Transfers: 19 Figure 4 Network Terminal-to-Network Controller 21 Figure 5 NT-to-NT Transfers: NT Burst Size Request = 0b, Delayed NT Burst Size Request = 0b .22 Figure 6 NT-to-NT Transfers: NT Burst Size Request = 1b, Delayed NT Burst Size Request = 0b .24 Figure 7 NT-to-
37、NT Transfers: Originating NC is also receiving NT, with NT Burst Size Request =1b, Delayed NT Burst Size Request = 0b 25 Figure 8 NT-to-NT Transfers: Delayed NT Burst Size Request = 1b, NT Burst Size Request = 0b .27 Figure 9 NT-to-NT Transfers: Originating NC is also receiving NT, with Delayed NT B
38、urst Size Request = 1b, NT Burst Size Request =0b29 Figure 10 Mode Command without Data Word.31 Figure 11 Transmit Mode Command with Data Word 31 Figure 12 Receive Mode Command with Data Word .32 Figure 13 NC-to-NTs Transfers (Broadcast or Multicast) .33 Figure 14 Network Terminal to Multiple Networ
39、k Terminals.34 Figure 15 Transmit Mode Command without Data Word to Multiple Network Terminals.36 Figure 16 Receive Mode Command with Data Word to Multiple Network Terminals36 Figure 17 FC-AE-1553 ULP Timers57 Figure 18 FC-AE-1553 Network to MIL-STD-1553 Bus Bridge 84 LIST OF TABLES Table 2 - Termin
40、ology Equivalents Between MIL-STD-1553 and Fc-Ae-1553.7 Table 3 - Comparison Of MIL-STD-1553 And FC-AE-1553 Command Field Sizes.7 Table 4 - Information Units Transmitted By The Network Controller To Network Terminal, and Transmissions by The Transmitting NT For NT-To-NT or NT-to-NTs Transfers.10 Tab
41、le 5 Information Units Initiated From The Network Terminal, Excluding Transmissions By The Transmitting NT for NT-to-NT or NT-to-NTs Transfers14 Table 6 - FC-4 Profile for FC-AE-1553 .37 Table 7 - FC-AE-1553 Command Sequence Header .42 Table 8 - Multicast Address or Other Port_ID Field 48 Table 9 -
42、FC-AE-1553 Status Sequence Header .52 Table 10 - Correct Values For F_CTL Field Bits.58 Table 11 - Values For D_ID Field (For Broadcast); NT-to-NT Transfer, T/R*, Tx RDMA, and Rx RDMA Bits; Subaddress, Byte Count/Mode Code, And Other Subaddress Fields.60 Table 12 - Correct Values For Fourth Word of
43、AC-AE-1553 Header Extension 64 Table 13 - Correct Values For Multicast Address or Other Port_ID Field.64 iv INCITS TR-42-2007 Table A.1 - FC-AE-1553 PRLI Service Parameter Page, PRLI Request And Accept.69 Table A.2 - FC-AE-1553 PRLI Service Parameters Corresponding Words/Bits .74 Table B.1 - FC-FS a
44、nd FC-AL-2 Features for FC-AE-155376 Table C.1 - Use Of FC-AE-1553 Subaddress and/or Other Subaddress Field for Command Sequences Involving Bridging to MIL-STD-1553 RTs 85 v viForeword (This foreword is not part of American National Standard INCITS TR-42-2007.)The original Fibre Channel Avionics Env
45、ironment (FC-AE) Technical Report, INCITSTR-31-2002, is a set of protocols and profiles that specify Fibre Channel options fordevices that could be used in commercial and military aerospace applications. Sub-sequent to the publication of INCITS TR-31-2002, the FC-AE-2 task group deter-mined that it
46、was best to allow protocols and profiles defined in FC-AE to be updatedindependently. The Fibre Channel FC-AE-1553 Technical Report is the first updateto the FC-AE-1553 protocol since FC-AE was released. This technical report is rec-ommended for new designs but does not obsolete 4.3 of INCITS TR-31-
47、2002.This technical report was developed by Technical Committee T11 of AccreditedStandards Committee INCITS during 2004-2006. The final approval process startedin 2006.Requests for interpretation, suggestions for improvements or addenda, or defect re-ports are welcome. They should be sent to the INC
48、ITS Secretariat, Information Tech-nology Industry Council, 1250 Eye Street, NW, Suite 200, Washington, DC 20005-3922.This technical report was processed and approved for submittal to ANSI by the Inter-national Committee for Information Technology Standards (INCITS). Committee ap-proval of the techni
49、cal report does not necessarily imply that all committee membersvoted for its approval. At the time it approved this technical report, INCITS had thefollowing members:Karen Higginbottom, ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeAdobe Systems, Inc. Leslie BixelSteve Ziles (Alt.)AIM Global Dan MullenCharles Biss (Alt.)Apple Computer, Inc. David MichaelElectr
