SAE ARD 5668-2007 1760 Routing Protocol Requirements《1760路由选择协议要求》.pdf

《SAE ARD 5668-2007 1760 Routing Protocol Requirements《1760路由选择协议要求》.pdf》由会员分享，可在线阅读，更多相关《SAE ARD 5668-2007 1760 Routing Protocol Requirements《1760路由选择协议要求》.pdf（23页珍藏版）》请在麦多课文档分享上搜索。

1、_ SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirely voluntary, and its applicability and suitability for any particular use, including any patent infringement arising there

2、from, is the sole responsibility of the user.” SAE reviews each technical report at least every five years at which time it may be reaffirmed, revised, or cancelled. SAE invites your written comments and suggestions. Copyright 2007 SAE International All rights reserved. No part of this publication m

3、ay be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of SAE. TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada) Tel: 724-776-4970 (outside USA)

4、 Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.org ARD5668 AEROSPACE RESOURCE DOCUMENT Issued 2007-02 1760 Routing Protocol Requirements RATIONALE The MIL-STD-1553 data bus was established over 30 years ago and is a basic part of the avionics architecture of numerous

5、 military aircraft. This bus is incorporated as a fundamental part of the aircraft-store interface defined in the standard for the Aircraft/Store Electrical Interconnection System MIL-STD-1760, which uses the majority of the definitions from MIL-STD-1553, but restricts certain applications. In recen

6、t years, the bus structure evolved from a single bus to hierarchical busses to distribute workload between avionic computers and to overcome the limitation of addressable remote terminals. However, neither MIL-STD-1553 nor MIL-STD-1760 define the methods by which information may be transferred throu

7、gh multi-layer, hierarchical topologies. Some initial work was carried out to incorporate a peeling protocol definition in MIL-STD-1760, but was suspended, as the approach being taken was considered inadequate following the introduction of intelligent store carriage systems. In addition, the NATO NI

8、AG ALWI II study completed in 2004 also identified the need for routing functions “to be added to the existing MIL-STD-1760 to cope with intelligent carriage store systems”. SAE ARD5668 - 2 - INTRODUCTION It is intended to define a routing protocol or a family of routing protocols for a network laye

9、r service (OSI layer 3, see Figure 1) between hierarchical data busses (starting with MIL-STD-1553) within a MIL-STD-1760 Carriage Store. This document establishes the requirements for the preparation of appropriate routing protocols. Application OrientedNetwork OrientedInterconnection mediaApplicat

10、ionprocessApplicationprocessOSIENETransportNetworkData LinkPhysicalSessionPresentationApplicationTransportNetworkData LinkPhysicalSessionPresentationApplicationNetworkData LinkPhysicalInterconnection mediaframespacketsmessages/filessync/bitswaveformsmessages/files/foldersFIGURE 1 - OSI PROTOCOL LAYE

11、RS SAE ARD5668 - 3 - TABLE OF CONTENTS 1. SCOPE 4 2. APPLICABLE DOCUMENTS 4 2.1 SAE Publications. 4 2.2 Military Standards . 4 2.3 Other Publications. 4 2.4 Abbreviations List 5 3. PROBLEM SUMMARY . 6 3.1 Contemporary Store Carriage Installations. 6 3.1.1 Minimum Components 6 3.1.2 Carriage Stores.

12、7 3.1.3 Miniature Munition Carriage Systems. 7 3.1.4 Fibre Channel 7 3.2 Aircraft Avionic Systems and Store Management 8 3.3 Consideration of MIL-STD-1553 . 8 3.4 Aircraft Operations in Networked Theatre 9 4. TECHNICAL REFERENCE MODEL 9 5. 1553 SERVICE (SNDC) 10 5.1 1553 Connectionless Mode Data Tra

13、nsmission . 11 5.2 1553 Connection Mode Data Transmission 12 5.3 Global Time Distribution 14 6. NETWORK SERVICE (SNIC). 16 6.1 Network Connectionless Mode Data Transmission 16 6.2 Network Connection Mode Data Transmission 17 6.3 Global Time Distribution 19 7. TRANSACTION TABLE CONFIGURATION 21 8. TR

14、ANSMISSION COMBINATIONS 21 9. REQUIREMENTS . 22 FIGURE 1 OSI PROTOCOL LAYERS . 2 FIGURE 2 CARRIAGE STORE DECOMPOSITION 8 FIGURE 3 GASIF SCENARIO WITH CARRIAGE STORE AS BC-RT BRIDGE. 10 FIGURE 4 SEND CL-MODE PACKET SERVICE PROCEDURE (1553) 11 FIGURE 5 RECEIVE CL-MODE PACKET SERVICE PROCEDURE (1553).

15、12 FIGURE 6 SEND CO-MODE PACKET SERVICE PROCEDURE (1553) 13 FIGURE 7 CREATE CONNECTION SERVICE PROCEDURE (1553) 13 FIGURE 8 DESTROY CONNECTION SERVICE PROCEDURE (1553). 14 FIGURE 9 SET GLOBAL TIME SERVICE PROCEDURE (1553) 15 FIGURE 10 GET GLOBAL TIME SERVICE PROCEDURE (1553) . 15 FIGURE 11 TIME SYNC

16、HRONIZATION SERVICE PROCEDURE (1553). 16 FIGURE 12 NETWORK SEND CL-MODE PACKET SERVICE PROCEDURE 17 FIGURE 13 NETWORK RECEIVE CL-MODE PACKET SERVICE PROCEDURE. 17 FIGURE 14 NETWORK SEND CO-MODE PACKET SERVICE PROCEDURE 18 FIGURE 15 NETWORK CREATE CONNECTION SERVICE PROCEDURE 18 FIGURE 16 NETWORK DES

17、TROY CONNECTION SERVICE PROCEDURE. 19 FIGURE 17 SET GLOBAL NETWORK TIME SERVICE PROCEDURE . 20 FIGURE 18 GET GLOBAL NETWORK TIME SERVICE PROCEDURE . 20 FIGURE 19 NETWORK TIME SYNCHRONIZATION SERVICE PROCEDURE. 21 FIGURE 20 SUPPORTED TRANSMISSION MODE COMBINATIONS 22 SAE ARD5668 - 4 - 1. SCOPE This d

18、ocument defines the requirements for routing protocols through a MIL-STD-1760 carriage store. It includes Miniature Mission Store Interfaces. This document begins with outlines of current carriage configurations, continues by describing typical emerging hierarchical topologies and why it is that the

19、 existing standards are inadequate. Different protocols are then discussed, with the document concluding with a set of recommended requirements and metrics for routing protocols to be included in MIL-STD-1760. This document complies with the OSI Basic Reference Model (ITU-T Rec. X.200 | ISO/IEC 7498

20、-1) in that it describes operations and mechanisms that are assignable to layers as specified in the OSI Basic Reference Model. This document also complies with the Generic Aircraft-Store Interface Framework (GASIF), SAE AIR5532. 2. APPLICABLE DOCUMENTS The following publications form a part of this

21、 document to the extent specified herein. The latest issue of SAE publications shall apply. The applicable issue of other publications shall be the issue in effect on the date of the purchase order. In the event of conflict between the text of this document and references cited herein, the text of t

22、his document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained. 2.1 SAE Publications Available from SAE International, 400 Commonwealth Drive, Warrendale, PA 15096-0001, Tel: 877-606-7323 (inside USA and Cana

23、da) or 724-776-4970 (outside USA), www.sae.org. AIR5532 Generic Aircraft/Store Interface Framework AS5652 10 Megabit/Sec Network Configuration Digital Time Division Command/Response Multiplex Data Bus AS5653 High Speed Network for MIL-STD-1760 AS15531 Aircraft Internal Time Division Command/Reponse

24、Multiplex Data Bus 2.2 Military Standards MIL-STD-1553 Aircraft Internal Time Division Command/Reponse Multiplex Data Bus MIL-STD-1760 Aircraft/Store Electrical Interconnection System MIL-STD-3014 Mission Data Exchange Format 2.3 Other Publications ISO/IEC7498-1 OSI Basic Reference Model ISO 8648 In

25、formation Processing Systems Open Systems Interconnection Internal Organisation of the Network Layer NIAG ALWI II Study, Final Report dated 16 March 2004 UAI-PSICD-R01 Universal Armament Interface Platform to Store Interface Control Document 22 May 2006 SAE ARD5668 - 5 - 2.4 Abbreviations List ALWI

26、Aircraft, Launcher and Weapon Interoperability NATO North Atlantic Treaty Organisation AEIS Aircraft/Store Electrical Interconnection System NCO Network Centric Operations AIR Aerospace Information Report NE Network Environment AS Aerospace Standard NIAG NATO Industrial Advisory Group ASI Aircraft S

27、tation Interface NS Network Service BC Bus Controller OSI Open Standard Interconnect C2 Command and Control OSIE OSI Environment CL Connectionless QoS Quality of Service CO Connection Req Request CON Conncection Resp Response Conf Confirmation RS Recommended Standard CSI Carriage Store Interface RT

28、Remote Terminal CSSI Carriage Store Station Interface RTCP Realtime Communication Protocol DAT Data SAE Society of Automotive Engineers EBR Enhanced Bit Rate SAP Service Access Point FC Fibre Channel SNAc Subnetwork Access GASIF Generic Aircraft Store Interface Framework SNDC Subnetwork-dependent Co

29、nvergence IEC International Electrotechnical Commission SNIC Subnetwork-independent Convergence Ind Indication SS Session Service ISO International Standardisation Organisation TS Transport Service ITU International Telecommunication Unit TT Transaction Table LAN Local Area Network UAI Universal Arm

30、ament Interface MIL-STD Military Standard WAN Wide Area Network MMSI Miniature Mission Store Interface MSI Mission Store Interface MSCI Miniature Store Carriage Interface SAE ARD5668 - 6 - 3. PROBLEM SUMMARY MIL-STD-1760 provides standardization requirements for carriage stores that address all aspe

31、cts of the electrical interfaces except transfer of the AS15531 CSI-to-CSSI messages intended for the Mission Store and transfer of the AS15531 CSSI-to-CSI messages from the Mission Store intended for the host platform. This has begun to allow implementation of schemes which solve point design issue

32、s, but, may not address enough of the problem to represent solutions that are as interoperable as needed. Some implementations can present significant processing and message duty cycle burdens upon the integrated system while other implementations architecturally “flatten” the logical appearance of

33、the system which imposes limitations in the quantity of mission stores and carriage stores that are supported. Goals for solving this problem should address (1) use of up to two layers of carriage store entities in the host platform to mission store path, (2) an implementation architecture which bes

34、t supports commonality in both host platform and mission store software such that the operational performance of the messaging is the same as if the mission store were directly attached to the ASI with no carriage store(s) present, (3) there shall be no changes to the mission store. As aircraft syst

35、ems and store carriage configurations become more complex, it becomes increasingly desirable to define a Network Service and Network Protocol or family of protocols to facilitate Open System Interconnection (OSI) between aircraft application processes and store application processes within an aircra

36、ft Local Area Network (LAN). Such a Network Service must provide acceptable Quality of Service (QoS) within a MIL-STD-1760 environment, including planned and foreseeable MIL-STD-1760 technology insertions. It should be assumed that the physical address space on individual 1553 busses will frequently

37、 be highly populated, and that nearly always some physical addresses on the communicating network segments will be duplicated. In the development of the Network Service and Network Protocol, consideration should also be given to the future support of Network Centric Operations (NCO) involving end sy

38、stems outside of the host aircraft within a Wide Area Network (WAN). The first step in the development of the Network Protocol is the definition of routing protocols for MIL-STD-1760 carriage stores and miniature store carriage systems. 3.1 Contemporary Store Carriage Installations This section intr

39、oduces common store carriage configurations that are currently within the definitions contained in MIL-STD-1760. 3.1.1 Minimum Components MIL-STD-1760 is an Aircraft-store Electrical Interconnection System (AEIS) that currently includes the MIL-STD-1553 data bus (1553). The minimum components of the

40、 AEIS are: An aircraft with Aircraft Station Interfaces (ASI); Aircraft umbilicals, each connected to one ASI; Mission stores, each with a Mission Store Interface (MSI) and connected to one aircraft umbilical. The AEIS 1553 bus is dual-redundant (Bus A, Bus B). The aircraft is the Bus Controller (BC

41、) and each mission store is a Remote Terminal (RT). The aircraft may have subsystems that are RTs on the AEIS 1553 bus also. The AEIS supports the five 1553 information transfer formats: BC-to-RT; BC-to-RT broadcast; RT-to-BC; SAE ARD5668 - 7 - RT-to-RT; RT-to-RT broadcast. 3.1.2 Carriage Stores It

42、is possible to carry multiple mission stores at an aircraft station using a carriage store. The Carriage Store Interface (CSI) is connected to the aircraft umbilical instead of the MSI. The carriage store has Carriage Store Station Interfaces (CSSIs), each with a carriage store umbilical. One missio

43、n store may be connected to one carriage store umbilical via its MSI. There is no standard protocol for passing 1553 data between the aircraft and mission store through a carriage store. However two methods are well known: The carriage store is a bus repeater. That is, the carriage store has an elec

44、trical circuit which bridges between the 1553 Physical Layer bus on the aircraft side of the AEIS and the 1553 Physical Layer bus on the mission store side of the AEIS. A single 1553 logical bus exists on both sides of the carriage store. The carriage store is a BC-RT bridge. That is, a different ph

45、ysical and logical bus exists on each side of the carriage store. The carriage store is an RT on the aircraft AEIS 1553 bus and a BC on the hierarchically lower AEIS 1553 bus that interfaces with the mission stores. This method requires a routing protocol, as discussed herein. MIL-STD-1760 allows th

46、ere to be more than one carriage store. 3.1.3 Miniature Munition Carriage Systems A specific type of MIL-STD-1760 mission store is a system comprising a miniature store carriage system and miniature mission stores. An optional component in the system is a subpack. A subpack is released by the miniat

47、ure store carriage system and contains multiple miniature mission stores within it. The miniature store carriage system provides one Miniature Store Carriage Interface (MSCI) for each miniature mission store that can be carried and one MSCI for each subpack that can be carried (if required). The mat

48、ing half of the MSCI is the Miniature Mission Store Interface (MMSI). This interface system is based on the SAE standard AS5652: 10 Megabit/Sec Network Configuration Digital Time Division Command/Response Multiplex Data Bus. The AS5652 logical bus is based on 1553 transmitting at 10Mbit/s and suppor

49、ts these information transfer formats: BC-to-RT; BC-to-RT broadcast; RT-to-BC. The AS5652 Physical Layer is based on RS-485 and is point-to-point. The miniature store carriage system is the logical hub. The miniature mission stores and subpacks are AS5652 RTs. For passing data between the aircraft and miniature mission store (or subpack), the miniature store carriage system is a BC-RT bridge. That is, the system