AIAA G-133-10-2013 Space Plug-and-Play Architecture Guide System Capabilities.pdf

《AIAA G-133-10-2013 Space Plug-and-Play Architecture Guide System Capabilities.pdf》由会员分享，可在线阅读，更多相关《AIAA G-133-10-2013 Space Plug-and-Play Architecture Guide System Capabilities.pdf（18页珍藏版）》请在麦多课文档分享上搜索。

1、 AIAA G-133-10-2013 S-102.2.5-2009 Space Plug-and-Play Architecture Guide System Capabilities AIAA standards are copyrighted by the American Institute of Aeronautics and Astronautics (AIAA), 1801 Alexander Bell Drive, Reston, VA 20191-4344 USA. All rights reserved. AIAA grants you a license as follo

2、ws: The right to download an electronic file of this AIAA standard for storage on one computer for purposes of viewing, and/or printing one copy of the AIAA standard for individual use. Neither the electronic file nor the hard copy print may be reproduced in any way. In addition, the electronic file

3、 may not be distributed elsewhere over computer networks or otherwise. The hard copy print may only be distributed to other employees for their internal use within your organization. Guide AIAA G-133-10-2013 Space Plug-and-Play Architecture Guide System Capabilities Sponsored by American Institute o

4、f Aeronautics and Astronautics Approved August 2013 Abstract The SPA System Capabilities Guide defines the principles upon which the architecture is based, the services that a SPA system provides, and the capabilities that are required of a SPA system. Each requirement in the Capabilities document i

5、s mapped to the other SPA standards where they are discussed in detail. AIAA S-133-10-2013 ii Published by American Institute of Aeronautics and Astronautics 1801 Alexander Bell Drive, Reston, VA 20191 Copyright 2013 American Institute of Aeronautics and Astronautics All rights reserved No part of t

6、his publication may be reproduced in any form, in an electronic retrieval system or otherwise, without prior written permission of the publisher. Printed in the United States of America ISBN 978-1-62410-238-7 AIAA S-133-10-2013 iii Contents Foreword . iv Introduction . vi 1 Scope. 1 2 Tailoring . 1

7、3 Applicable Documents . 1 4 Vocabulary . 1 4.1 Acronyms and Abbreviated Terms . 1 4.2 Terms and Definitions 2 5 SPA Systems . 3 5.1 SPA Principles . 3 5.2 SPA Services . 3 6 Capability Requirements 4 6.1 General Capability . 4 6.2 Standards-Based Interface Capability 4 6.3 Component “Plug” Capabili

8、ty . 5 6.4 Component “Play” Capability . 5 6.5 Network Capability . 5 6.6 Common Time Capability . 6 6.7 Fault Tolerance Capability . 6 6.8 Security Capability . 6 6.9 Power Capability 6 6.10 Test Support Capability 6 Annex A SPA Requirements Mapping (Informative) 7 Tables Table A.1 SPA system capab

9、ility requirements flow-down . 7 AIAA S-133-10-2013 iv Foreword This guide was developed through a partnership of the Air Force Research Laboratory Space Vehicles Directorate, the Air Force Office of Operationally Responsive Space, numerous government contractor teams, independent contractor teams,

10、and academic experts. The Space Plug-and-Play Architecture is a collection of standards developed to facilitate rapid constitution of spacecraft systems using modular components. This document enumerates the principles upon which the SPA approach is based, the services provided by a SPA system, and

11、the requirements for SPA system capabilities. This volume of the SPA System Capability Guide contains information not recorded in previous documentation. It is part of a set of 10 documents describing other components of the SPA standards: SPA Guidebook SPA Networking SPA Logical Interface SPA Physi

12、cal Interface Standard SPA 28V Power Service Standard SPA System Timing Standard SPA Ontology Standard SPA Test Bypass Standard SPA SpaceWire Subnet Adaptation Standard At the time of approval, the members of the AIAA SPA Committee on Standards were: Fred Slane, Chair Space Infrastructure Foundation

13、 Jeanette Arrigo Sierra Nevada Corporation Scott Cannon Utah State University Ken Center PnP Innovations Don Fronterhouse* PnP Innovations Rod Green Design Net Engineering Group Jane Hansen HRP Systems Doug Harris The Aerospace Corporation, ORS Office Paul Jaffe U.S. Naval Research Laboratory Stanle

14、y Kennedy* Comtech Aero-Astro Ronald Kohl R.J. Kohl may include one or multiple SPA applications and/or devices SPA core component a component that provides one or more SPA service SPA device a hardware SPA component SPA gateway a uniquely addressable SPA core component used to bridge between two di

15、fferent SPA network spaces SPA network an addressable and routable physically connected infrastructure composed of standard SPA transports for the purpose of transporting SPA messages and encapsulated data between SPA endpoints and SPA gateways. The SPA network is made available as a SPA service to

16、SPA components through a standard interface. SPA processor resource a SPA device containing a processor that advertises itself via xTEDS as a discoverable, shared resource for executing SPA applications. SPA services SPA-specific capabilities and functionality available to SPA components by SPA core

17、 components through a standard interface. AIAA S-133-10-2013 3 SPA system an integrated collection of interoperating SPA components SSI SPA Services Infrastructure (SSI) consists all SPA core components that provide SPA services to the system Time latency the time lapse between issuance of the PPS t

18、iming signal and receipt by each consumer (component or endpoint) xTEDS an electronic data sheet used as the SPA component interface specification; see IEEE 1451 family for examples. 5 SPA Systems The Space Plug-and-Play Architecture (SPA) is centered on the idea that components for any networked sy

19、stem can be added to the network and will have the ability to communicate with the system without separately installing drivers, software interfaces, or other interface mechanisms. In order to distinguish the SPA concept from other “plug-and-play” approaches the principles of a SPA system and the se

20、rvices provided by that system are outlined below. 5.1 SPA Principles The following principles bound the SPA system and differentiate this approach from other plug-and-play systems. a) SPA components shall only communicate on the SPA network through standard transporting messages with encapsulated d

21、ata. b) SPA components shall conform to an approved SPA-x interface (-U, -S, -1, -O, etc.) such that they operate without modification when integrated with a compatible SPA-x infrastructure. c) Components shall be self-describing with sufficient detail for the purpose of correctly matching SPA compo

22、nents in roles of producers and consumers of data and services (IAW an approved xTEDS schema and Common Data Dictionary). d) SPA data producers and consumer needs are matched through a standard query service. e) SPA networks are topology agnostic and self-organizing. f) A SPA device shall be physica

23、lly mountable on a compliant SPA structure according to one of the applicable SPA mechanical standards. 5.2 SPA Services All SPA systems provide the following services that meet the requirements of the SPA principles. Command/response messages SPA components send command messages to initiate an acti

24、on, and send response messages to respond to command messages. A SPA components xTEDS details the command and response messages supported by the component. AIAA S-133-10-201X 4 Component detection A SPA system automatically detects hardware or software components that are added to the system. Compon

25、ent detects dependency failure SPA components detect or are notified when a component that they are subscribed to is unable to provide the data requested. Components register SPA components register with the network, informing the system as to the data the component produces, the operational modes t

26、hat it has available (if applicable), and the data that it will consume. Components self identity SPA components provide information about their functions and use to the system. This may be done directly or the device may provide a pointer to information stored elsewhere but the device must enable t

27、he system to learn of its capabilities without external manipulation. Publish/subscribe messages SPA components publish data through messages. SPA components can subscribe to data messages as needed. Standard mechanical and electrical interfaces SPA systems provide standard mechanical and electrical

28、 interfaces for SPA devices. Standard 28V power interface SPA systems provide standard 28V power interface for all SPA devices. System monitors component status - A SPA system monitors component status (fully operational, dependency failures, component failure, etc.). System provides common time to

29、component A SPA system must provide common time to the system components. 6 Capability Requirements The capability requirements defined in this document are numbered. Annex A shows the mapping of each numbered requirement to the SPA standard document that addresses that requirement. 6.1 General Capa

30、bility (SPA001) SPA devices shall be designed to reject internal heat through conduction to their mounting surface or radiation to the surroundings. (SPA002) System configuration data required by a SPA component shall be available from a configuration source within the SPA system. 6.2 Standards-Base

31、d Interface Capability (SPA003) A SPA component interface shall be described by an xTEDS which conforms to the SPA Ontology Standard (AIAA S-133-7-2013). (SPA004) SPA components shall utilize SPA standard messages that are independent of programming languages to access SPA services in accordance wit

32、h the SPA Logical Interface Standard (AIAA S-133-3-2013). (SPA005) SPA devices shall comply with a standardized mounting interface which is designed to withstand the loads associated with launch, ascent and on-orbit operations. (SPA006) The SPA mounting surface shall allow SPA devices to be placed a

33、t multiple locations on the spacecraft structure to provide flexibility in spacecraft configurations. AIAA S-133-10-2013 5 (SPA007) SPA devices shall provide a SPA compliant connector as specified in the SPA Physical Interface Standard (AIAA S-133-4-2013). 6.3 Component “Plug” Capability (SPA008) Th

34、e SPA system shall provide the ability to register a new SPA component during spacecraft operations without a priori knowledge of their physical or network location. (SPA009) The SPA system shall provide the ability to re-register a previously registered SPA component that has been updated. (SPA010)

35、 The SPA system shall provide the ability to unregister a previously registered SPA component. (SPA011) Each SPA component within a SPA system shall be identified with a universally unique identifier (UUID) in accordance with the SPA Logical Interface Standard (AIAA S-133-3-2013). (SPA012) A SPA com

36、ponent shall provide an xTEDS to register in the SPA system. 6.4 Component “Play” Capability (SPA013) A SPA component shall become discoverable within the SPA system when it registers and is uniquely addressable. (SPA014) The SPA system shall make no distinction (in a data sense) between SPA compone

37、nts (specifically, having a SPA device coupled with at least one SPA application) and SPA applications. (SPA015) A SPA components xTEDS shall be made available during discovery in response to a query message. (SPA016) The SPA system shall provide the ability to discover SPA components during spacecr

38、aft operations without a priori knowledge of their physical or network location. NOTE The SPA network is optionally permitted to store and load a set configuration without undergoing topology discovery. (SPA017) The SPA system shall provide the ability for a SPA component to utilize another SPA comp

39、onent during spacecraft operations without a priori knowledge of their physical or network location. 6.5 Network Capability (SPA018) The SPA system shall not require external data sources to operate. (SPA019) SPA components shall be usable at any location on the network with a matching subnet protoc

40、ol. (SPA020) SPA gateways shall be used to negotiate between heterogeneous SPA standard transport networks. (SPA021) The SPA system shall provide the ability to route SPA messages and data on a variety of SPA standard transports. (SPA022) Configuration of the SPA network shall be implemented as an a

41、utomated system-wide protocol without tailoring for the specific application. (SPA023) The SPA system shall support QoS mechanisms in accordance with the SPA Network Standard. NOTE QoS is selectable (optional) in the SPA Networking Standard (AIAA S-133-2-2013) and the SPA SpaceWire Subnet Adaptation

42、 Standard (AIAA S-133-9-2013). AIAA S-133-10-201X 6 (SPA024) The SPA system shall support SPA message packet integrity checking in accordance with the SPA Logical Interface Standard (AIAA S-133-3-2013). (SPA025) The SPA system shall route messages and data between SPA components across the SPA netwo

43、rk. 6.6 Common Time Capability (SPA026) The SPA system shall be capable of providing the current synchronized system time. (SPA027) SPA devices shall be capable of handling the receipt of a timestamp and sync signal distributed on all supported subnet varieties as defined by SPA. (SPA028) The SPA sy

44、stem shall be capable of arbitrating the master clock source. 6.7 Fault Tolerance Capability (SPA029) A SPA core component shall be able to detect an internal fault condition. (SPA030) A SPA core component shall attempt fault recovery upon detection of an interface fault condition. (SPA031) A SPA co

45、re component shall attempt fault reporting upon detection of an internal fault condition. (SPA032) The SPA system shall provide for the self-healing of a failed network route by dynamically determining and providing transparent adaptation to alternate networking routes if alternate routes are availa

46、ble. (SPA033) A SPA component shall detect a dependency failure. (SPA034) A SPA component shall respond with operational status when requested. (SPA035) The SPA system shall monitor the operational status of all SPA components. (SPA036) The SPA system shall provide notification of the operational st

47、atus of all SPA components. 6.8 Security Capability The SPA standards do not address system security. Any system-level security issues that arise out of the SPA design approach that are specifically inherent to SPA may be addressed in the future. 6.9 Power Capability (SPA037) SPA devices shall be de

48、signed to operate over a specified voltage range and maximum current draw. (SPA038) SPA devices shall withstand specified over-voltage, under-voltage, transient and ripple conditions without permanent damage or degradation. (SPA039) SPA devices shall comply with primary power, secondary power and di

49、gital grounds in the overall spacecraft grounding requirement. (SPA040) The SPA system shall provide power at the specified voltages, to connected SPA components. 6.10 Test Support Capability (SPA041) The SPA system shall support a mechanism to allow SPA device data interfaces to be manipulated for the purposes of rapid testing. AIAA S-133-10-2013 7 Annex A SPA Requirements Mapping (Informative) Table 1 shows how each of the requirements in the SPA System Capabilities Standard flow down to the other SPA standards. The referenced document c