Refine Your Search

Topic

Search Results

Standard

Statement on Requirements for Real-Time Communication Protocols (RTCP)

1996-04-01
HISTORICAL
AIR4886
The purpose of this document is to establish the requirements for Real-Time Communication Protocols (RTCP). Systems for real-time applications are characterized by the presence of hard deadlines where failure to meet a deadline must be considered a system fault. These requirements have been driven predominantly, but not exclusively, by aerospace type military platforms and commercial aircraft, but are generally applicable to any distributed, real-time, control systems. These requirements are primarily targeted for the Transport and Network Layers of peer to peer protocols, as referenced in the Open System Interconnect Reference Model (2.2.1 and 2.2.2), developed by the International Standards Organization (ISO). These requirements are intended to complement SAE AS4074 (2.1.1) and AS4075 (2.1.2), and future SAE communications standards.
Standard

Statement on Requirements for Real-Time Communication Protocols (RTCP)

2016-10-21
CURRENT
AIR4886A
The purpose of this document is to establish the requirements for Real-Time Communication Protocols (RTCP). Systems for real-time applications are characterized by the presence of hard deadlines where failure to meet a deadline must be considered a system fault. These requirements have been driven predominantly, but not exclusively, by aerospace type military platforms and commercial aircraft, but are generally applicable to any distributed, real-time, control systems. These requirements are primarily targeted for the Transport and Network Layers of peer to peer protocols, as referenced in the Open System Interconnect Reference Model (2.2.1 and 2.2.2), developed by the International Standards Organization (ISO). These requirements are intended to complement SAE AS4074 (2.1.1) and AS4075 (2.1.2), and future SAE communications standards.
Standard

Modular Avionics Backplane Functional Requirements and Consensus Items (MABFRACI)

2012-05-03
CURRENT
AIR4980A
The original purpose of this document was to establish interface requirements for modular avionics backplanes to be prototyped up to 1995. The document was issued as ARD50011 in September 1992. It is being reissued as an SAE Aerospace Information Report (AIR) in order to: a Preserve the requirements for more than 2 years b Support design of retrofits and avionics systems to be fielded in the years 1995 to 2000 c Provide a baseline for updating the requirements of future integrated systems These requirements were and are intended to promote standardization of modular avionic backplane interfaces. These requirements have been driven predominantly, but not exclusively, by aerospace type military platforms.
Standard

MODULAR AVIONICS BACKPLANE FUNCTIONAL REQUIREMENTS AND CONSENSUS ITEMS (MABFRACI)

1996-11-01
HISTORICAL
AIR4980
The original purpose of this document was to establish interface requirements for modular avionics backplanes to be prototyped up to 1995. The document was issued as ARD50011 in September 1992. It is being reissued as an SAE Aerospace Information Report (AIR) in order to: a Preserve the requirements for more than 2 years b Support design of retrofits and avionics systems to be fielded in the years 1995 to 2000 c Provide a baseline for updating the requirements of future integrated systems These requirements were and are intended to promote standardization of modular avionic backplane interfaces. These requirements have been driven predominantly, but not exclusively, by aerospace type military platforms.
Standard

Linear Token Passing Multiplex Data Bus User's Handbook

1992-12-30
HISTORICAL
AIR4288
This document is intended to explain, in detail, the rationale behind the features and functions of the AS4074, Linear, Token-passing, Bus (LTPB). The discussions also address the considerations which a system designer should take into account when designing a system using this bus. Other information can be found in these related documents:
Standard

Linear Token Passing Multiplex Data Bus User's Handbook

2012-05-03
CURRENT
AIR4288A
This document is intended to explain, in detail, the rationale behind the features and functions of the AS4074, Linear, Token-passing, Bus (LTPB). The discussions also address the considerations which a system designer should take into account when designing a system using this bus. Other information can be found in these related documents: AIR4271 - Handbook of System Data Communication AS4290 - Validation Test Plan for AS4074
Standard

IEEE-1394b for Military and Aerospace Vehicles - Applications Handbook

2019-08-12
CURRENT
AIR5654A
This Handbook is intended to accompany or incorporate AS5643, AS5643/1, AS5657, AS5706, and ARD5708. In addition, full understanding of this Handbook also requires knowledge of IEEE-1394-1995, IEEE-1394a, and IEEE-1394b standards. This Handbook contains detailed explanations and architecture analysis on AS5643, bus timing and scheduling considerations, system redundancy design considerations, suggestions on AS5643-based system configurations, cable selection guidance, and lessons learned on failure modes.
Standard

IEEE-1394b Interface Requirements for Military and Aerospace Vehicle Applications

2016-04-04
CURRENT
AS5643B
IEEE-1394b, Interface Requirements for Military and Aerospace Vehicle Applications, establishes the requirements for the use of IEEE Std 1394™-2008 as a data bus network in military and aerospace vehicles. The portion of IEEE Std 1394™-2008 standard used by AS5643 is referred to as IEEE-1394 Beta (formerly referred to as IEEE-1394b.) It defines the concept of operations and information flow on the network. As discussed in 1.4, this specification contains extensions/restrictions to “off-the-shelf” IEEE-1394 standards and assumes the reader already has a working knowledge of IEEE-1394. This document is referred to as the “base” specification, containing the generic requirements that specify data bus characteristics, data formats, and node operation.
X