BS ISO 21076:2016从以下方面描述了SCCS体系结构:地面和空间中涉及空间通信的所有关键要素的定义；SCCS服务的概念定义；对提供安全SCCS服务的系统元件和组件的要求；每种元素类型的推荐协议栈配置；安德烈推荐端到端系统配置，以提供互操作和跨支持的空间通信服务。本文件未具体说明:如何实施提供SCCS服务的系统的细节；实施SCCS服务所需的明确技术；应用或任务操作协议，但用于数据传输的协议除外；除参与计划、调度和执行的任务外的任务操作 空间通信；航天器上的交叉支持，空间通信服务除外。本文件包含对其他CCSDS技术工程和建筑的参考 描述如何实现空间通信交叉支持的系统的建议 设计、部署、组织和运营以提供可互操作的SCCS服务。 虽然本文件没有详细说明内部实施方法 是私人事务，它确实建议使用特定的协议和协议栈、服务 接口、元素行为和端到端架构。本文件中引用的一些标准，尤其是与 SSI仍在开发中。它们包含在这里，以便读者能够清楚地理解 它们如何融入整体架构。本文件中与协议相关的部分对 开放系统互连（OSI）基本参考模型（参考文献[4]）。第6.2小节 架构（Architecture）描述文件（ADD）（参考文献[D5]）中包含以下内容的讨论: OSI堆栈以及与每一层相关的功能。 单跳交叉支持的技术范围是提供数据链路层（第2层） 支持太空任务用户的太阳系数据通信服务， 使用一个或多个空间机构的可互操作基础设施。以上服务 数据链路层，如CCSDS文件传递协议（CFDP），跨支持文件服务 （CXFS）或增量差分单向量程（DOR）也可以提供。所有任务 CCSDS兼容、可互操作、单跳部署中的操作应用程序 预计将利用这些底层空间链接和文件通信层。SSI的技术范围是提供互联（第3层）数据 为支持空间任务用户而提供的太阳系通信服务，使用 一个或多个空间机构为实现 个别机构不可能达到的服务水平。 所有任务 CCSDS兼容、互操作、SSI部署中的操作应用程序预计将 利用这些底层空间互连通信层。本文档的时间范围包括当前的、单跳的、安全的、可互操作的交叉连接 支持安装、未来部署可互操作且不断发展的空间网络 基础设施，以及从当前部署到未来的过渡战略 SSI州。本讨论包括任务驱动的考虑因素，例如混合动力的使用 科学/路由任务，以及确定可选配置 被认为是可接受的，因为它们符合本协议中定义的过渡策略 文件任何希望以对等身份参与SSI的机构都应实施互操作 至少到网络层的服务和接口，以及相关的支持服务， 如本文件所述，并在相关CCSDS和互联网标准中规定。 尚未准备好采用SSI的机构，但希望提供符合要求的地面站交叉支持服务，以支持SSI服务的机构，也可以利用本文件提供有关开发数据链路层服务的指导，这些服务既能满足其当前需求，又能与支持SSI的任务进行互操作。交叉引用:CCSDS 910.4-B-2:2005CCDS311.0-M-1:2008IOAG。T.RC。001.V1:2010ISO/IEC 7498-1:1994IOAG。T.SP.001。2.2.2.2.2.2.2.2.2.2.2.2.2.2.2.2.2.1-Y-Y-1-1-1.1.1.1.1.1.1.1.1.1.2.2）2.2.2.2.2.2.2.2.2.2.2.2.2.2.2.2.2.2）C C C C C C C C C C C C C C C（2.2.2.2.2.2.2.2.2.2.2.2.2.2.2.2.2.2.2.2.2.2.2.2）C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C C 1997RFC 792:1981CCSDS 911.5-B-2:2010CCDS505.0-B-1:2010CCDS502.0-B-2:2009CCSDS232.0-B-2:2010CSDS131.0-B-2:2011CCSDS232.1-B-2:2010CSDS401.0-B-23:2013CCSDS301。 2）adadvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv18:2000CCSDS 131.2-B-1:2012CCSDS 131.3-B-1:2013RFC 1930:1996CCSDS 740.0-G-1:2008CCSDS413.0-G-2:2009IOAG。T.RC。002.V1:2010CSDS 901.0-G-1:2013CCSDS 921.1-R-2:2014CCSDS 730.1-G-1:2014CCSDS 130.0-G-3:2014CCSDS 910.11-B-1:2009CCSDS 902.0-G-1:2014CCSDS 912.11-O-1:2012CCSDS 922.1-R-1CCSDS 355.0-R-3:2013CCSDS 734.2-R-3:2014CCSDS 350.4-G-1:2007购买本文件时所有现有的修改件均包括在内。

BS ISO 21076:2016 describes SCCS architecture in terms of the following:definitions of all key elements, on ground and in space, that are involved in space communications;definitions of concepts that characterize SCCS services;requirements on system elements and components that provide secure SCCS services;recommended protocol stack configurations for each element type; andrecommended end-to-end system configurations to provide interoperable and cross-supportable space communications services.This document does not specify:the details of how to implement systems that provide SCCS services;explicit technologies needed to implement SCCS services;application or mission operations protocols except for those used for data transfer;mission operations except for those involved in planning, scheduling, and executing space communications;spacecraft onboard cross support, except for space communication services.This document contains references to other CCSDS technical engineering and architectural recommendations describing how systems doing space communication cross support should be engineered, deployed, organized, and operated to provide interoperable SCCS services. While this document does not specify detailed internal implementation approaches, which are a private matter, it does recommend specific protocols and protocol stacks, service interfaces, element behaviors, and end-to-end architectures.Some of the standards that are referenced in this document, especially those relating to the SSI, are still in development. They are included here so the reader gets a clear understanding of how they fit into an overall architecture.The protocol-related parts of this document make liberal reference to the layers defined in the Open Systems Interconnection (OSI) Basic Reference Model (reference [4]). Subsection 6.2 of the Architecture Description Document (ADD) (reference [D5]) contains a discussion of the OSI stack and the functions associated with each layer.The technical scope of single-hop cross support is the provision of Data Link Layer (Layer 2) data communications services across the Solar System in support of space mission users, using the interoperable infrastructure of one or more space agencies. Services above the Data Link Layer, such as CCSDS File Delivery Protocol (CFDP), Cross-Support File Service (CXFS), or Delta-Differential One-way Range (DOR), may also be provided. All mission operations application in CCSDS-compliant, interoperable, single-hop deployments are expected to utilize these underlying space link and file communications layers.The technical scope of the SSI is the provision of internetworked (Layer 3) data communications services across the Solar System in support of space mission users, using the confederated and interoperable infrastructure of one or more space agencies to achieve a level of service that individual agencies would otherwise be unlikely to achieve. All mission operations application in CCSDS-compliant, interoperable, SSI deployments are expected to utilize these underlying space internetworking communications layers.The temporal scope of this document covers current, single-hop, secure interoperable cross support installations, future deployments of an interoperable and evolving space networking infrastructure, and the transition strategies to evolve from current deployments to a future SSI state. Included in this discussion are mission-driven considerations, such as use of hybrid science/routing missions, as well as identification of optional configurations that are considered acceptable because they are in line with the transition strategies defined in this document.Any agency that wishes to participate as a peer in the SSI should implement interoperable services and interfaces at least up to the Network Layer, along with related support services, as described in this document and specified in the relevant CCSDS and Internet standards.Agencies that are not yet ready to adopt the SSI themselves, but that wish to offer compliant ground station cross support services that can support SSI services, may also take advantage of this document for guidance on developing Data Link Layer services that will both meet their immediate needs and also interoperate with SSI-enabled missions.Cross References:CCSDS 910.4-B-2:2005CCSDS 311.0-M-1:2008IOAG.T.RC.001.V1:2010ISO/IEC 7498-1:1994IOAG.T.SP.001.V1:2010CCSDS 351.0-M-1:2012CCSDS 352.0-B-1:2012CCSDS 231.0-B-2:2010CCSDS 732.0-B-2:2006CCSDS 132.0-B-1:2003ISO/IEC 10746-3:1996RFC 5050:2007RFC 5326:2008CCSDS 133.1-B-2:2009RFC 6257:2011CCSDS 313.0-Y-1:2011CCSDS 320.0-B-6:2013CCSDS 912.1-B-3:2010CCSDS 911.1-B-3:2010CCSDS 911.2-B-2:2010CCSDS 506.0-M-1:2011RFC 2228:1997RFC 792:1981CCSDS 911.5-B-2:2010CCSDS 505.0-B-1:2010CCSDS 502.0-B-2:2009CCSDS 232.0-B-2:2010CCSDS 131.0-B-2:2011CCSDS 232.1-B-2:2010CCSDS 401.0-B-23:2013CCSDS 301.0-B-4:2010CCSDS 414.1-B-2:2014CCSDS 503.0-B-1:2007CCSDS 506.1-B-1:2013CCSDS 727.0-B-4:2007CCSDS 508.0-B-1:2013CCSDS 735.1-B-1:2011CCSDS 133.0-B-1:2003CCSDS 211.0-B-5:2013CCSDS 211.1-B-4:2013CCSDS 211.2-B-2:2013CCSDS 702.1-B-1:2012RFC 2616:1999RFC 2507:1999CCSDS 913.1-B-1:2008RFC 4301:2005RFC 4303:2005RFC 2818:2000CCSDS 131.2-B-1:2012CCSDS 131.3-B-1:2013RFC 1930:1996CCSDS 740.0-G-1:2008CCSDS 413.0-G-2:2009IOAG.T.RC.002.V1:2010CCSDS 901.0-G-1:2013CCSDS 921.1-R-2:2014CCSDS 730.1-G-1:2014CCSDS 130.0-G-3:2014CCSDS 910.11-B-1:2009CCSDS 902.0-G-1:2014CCSDS 912.11-O-1:2012CCSDS 922.1-R-1CCSDS 355.0-R-3:2013CCSDS 734.2-R-3:2014CCSDS 350.4-G-1:2007All current amendments available at time of purchase are included with the purchase of this document.