TELEMETRY OVER INTERNET PROTOCOL (TMoIP) STANDARD

218-20TELECOMMUNICATIONS ANDTIMING GROUPTELEMETRY OVER INTERNET PROTOCOL (TMoIP) STANDARDABERDEEN TEST CENTERDUGWAY PROVING GROUNDELECTRONIC PROVING GROUNDREAGAN TEST SITEREDSTONE TEST CENTERWHITE SANDS TEST CENTERYUMA PROVING GROUNDNAVAL AIR WARFARE CENTER AIRCRAFT DIVISION PATUXENT RIVERNAVAL AIR WARFARE CENTER WEAPONS DIVISION CHINA LAKENAVAL AIR WARFARE CENTER WEAPONS DIVISION POINT MUGUNAVAL SURFACE WARFARE CENTER DAHLGREN DIVISIONNAVAL UNDERSEA WARFARE CENTER DIVISION KEYPORTNAVAL UNDERSEA WARFARE CENTER DIVISION NEWPORTPACIFIC MISSILE RANGE FACILITY30TH SPACE WING45TH SPACE WING96TH TEST WING412TH TEST WINGARNOLD ENGINEERING DEVELOPMENT COMPLEXNATIONAL AERONAUTICS AND SPACE ADMINISTRATIONDISTRIBUTION A: APPROVED FOR PUBLIC RELEASE,DISTRIBUTION IS UNLIMITED

This page intentionally left blank.

DOCUMENT 218-20TELEMETRY OVER INTERNET PROTOCOL (TMoIP) STANDARDFebruary 2020Prepared byTELECOMMUNICATIONS AND TIMING GROUPPublished bySecretariatRange Commanders CouncilU.S. Army White Sands Missile Range,New Mexico 88002-5110

This page intentionally left blank.

Telemetry over Internet Protocol (TMoIP), RCC Standard 218-20, February 2020Table of ContentsChanges in this Edition. viiPreface . ixAcronyms . xiChapter 1.Introduction and Overview of the Telemetry over Internet Protocol . 1-1Chapter 2.Telemetry Transport Techniques . 2-12.1Telemetry System Overview. 2-12.1.12.1.22.1.32.1.42.1.52.22.3Airborne Instrumentation System . 2-2Common Telemetry RF Link . 2-2TM Ground Station . 2-2Ground Network . 2-3Telemetry over IP . 2-3Motivation for TMoIP. 2-5Challenges for TMoIP. 2-62.3.12.3.22.3.3Downlink Data Requirements . 2-6Uplink Command Requirements. 2-8System Management . 2-8Chapter 3.TMoIP Payload Construction . 3-13.1Overview/Management Elements . 3-13.1.13.1.23.23.33.4High-Level Requirements (Concept of Operations) . 3-1OSI Layered Approach . 3-2OSI Protocol Layer Implementation: TM Terminal . 3-43.4.13.4.23.5Layer 7 – Application . 3-4Layer 6 – Presentation . 3-4Layer 5 (Null) . 3-11Layer 4 - Transport . 3-11Layer 3 . 3-13Layer 2 . 3-15Layer 1 . 3-18TMoIP Packet Design Summary and Discussion . 3-18Chapter 4.4.14.2Layer 1 . 3-4Layers 2 – 7 . 3-4OSI Protocol Layer Implementation: Network Processor . 3-43.5.13.5.23.5.33.5.43.5.53.5.63.5.73.6TMoIP payload . 3-1TMoIP solution . 3-1TMoIP Management . 4-1Management Mechanisms . 4-1QoS . 4-2iii

Telemetry over Internet Protocol (TMoIP), RCC Standard 218-20, February 20204.2.14.2.24.3Network Performance . 4-34.3.14.3.24.3.34.44.5Layer 2 Mechanisms . 4-2Layer 3 Mechanisms . 4-3Packet Delay Variation . 4-3Delay . 4-3Network Errors. 4-3IPv4 to IPv6 Migration . 4-4Multicast Support . 4-5Appendix A. Recommendations for TM Terminal Layer 1 . A-1Appendix B. Considerations for Legacy Asynchronous Transfer ModeInterworking. B-1Appendix C. Summary of Managed Objects . C-1Appendix D. Application Notes . D-1Appendix E. Citations . E-1Appendix F. References .F-1List of FiguresFigure 2-1.Figure 2-2.Figure 3-1.Figure 3-2.Figure 3-3.Figure 3-4.Figure 3-5.Figure 3-6.Figure 3-7.Figure 3-8.Figure 3-9.Figure 3-10.Generic TM System . 2-1Ground Network Functional Blocks . 2-3OSI Layers for TM Terminal and Network Processor. 3-3TMoIP Layer 6 implementation. 3-5TMoIP 218-10 Control Word . 3-6TMoIP 218-P Control Word . 3-7TMoIP 218-20 Control Word . 3-8TMoIP 218-20 Control Word (12-Byte Detail) . 3-9TMoIP Layer 4 - Layer 6 implementation . 3-11TMoIP Layer 3 - Layer 6 Implementation . 3-13TMoIP Layer 2 - Layer 6 Implementation . 3-16TMoIP Packet Layout . 3-19Table 3-1.Table 3-2.Table 3-3.Table 3-4.Table 3-5.Table 3-6.Table 3-7.Table 3-8.Table 3-9.High-Level Requirements . 3-2TMoIP OSI Protocol Layer Implementation . 3-3TMoIP 218-10 Control Word . 3-7TMoIP 218-P Control Word . 3-7TMoIP 218-20 Control Word . 3-8Packet Size Tradeoffs . 3-9Clock Recovery. 3-10UDP Header Field Descriptions. 3-11UDP Header Field Requirements. 3-12List of Tablesiv

Telemetry over Internet Protocol (TMoIP), RCC Standard 218-20, February 2020Table 3-10.Table 3-11.Table 3-12.Table 3-13.Table 3-14.Table 3-15.Table 3-16.Table 4-1.Table 4-2.Table 4-3.Table 4-4.Table 4-5.Table 4-6.Table A-1.Table B-1.Table C-1.Table C-2.Table C-3.Table C-4.IP Header Field Descriptions . 3-13IPv4 Header Field Requirements . 3-14Ethernet Overhead Fields . 3-16Ethernet Overhead Field Requirements . 3-17TMoIP Layer 1 Requirements . 3-18TMoIP Packet Summary . 3-19Sample Payload Calculations . 3-20Management Mechanisms . 4-1Layer 2 QoS Mechanisms . 4-2Layer 3 QoS Mechanisms . 4-3Network Performance - Dropped Packets. 4-4IPv4/IPv6 Requirements . 4-4Multicast Packets . 4-6Recommendations and Guidelines for the Layer 1 (Physical Layer)Implementation of the TM Terminal . A-1Request for Comments (RFC) 2684 Optimal Payloads .B-1Alarms .C-1Configuration Parameters .C-1TM Statistics .C-2Ethernet Statistics.C-2v

Telemetry over Internet Protocol (TMoIP), RCC Standard 218-20, February 2020This page intentionally left blank.vi

Telemetry over Internet Protocol (TMoIP), RCC Standard 218-20, February 2020Changes in this EditionThis document is an updated version of and replaces Range Commanders Council (RCC)Document 218-10. The RCC Timing and Telecommunications Group (TTG) made an extensiveeffort to produce a well-coordinated and useful document. The following is a summary of thechanges made in this version, 218-20.a. TMoIP control word additions(1)64-bit timestamp with nanosecond resolution(2)Time source reference flag for Universal Coordinated Time or International AtomicTime(3)Payload shaping for minor frames and data quality(4)Frame sync status for payload shaped frames(5)Fragmentation indication for managing shaped payloads and maximumtransmission unitb. TMoIP control word subtractions(1)Identify failures in local TM interface(2)Fault signaling capability across the network(3)LEN fieldc. Reserved a control word version to preserve proprietary variants.d. Bit rates and changes in bit rates shall be calculated using packet timestamps andalgorithms. For compliance, no proprietary packets or bits shall be used.e. Removal of real-time protocol from timing as an option for clock recovery.f. Removed many references to range use of ATM.vii

Telemetry over Internet Protocol (TMoIP), RCC Standard 218-20, February 2020This page intentionally left blank.viii

Telemetry over Internet Protocol (TMoIP), RCC Standard 218-20, February 2020PrefaceThe Telecommunications and Timing Group (TTG) of the Range Commanders Council(RCC) prepared this Standard. This Standard replaces RCC Standard 218-10, Telemetry overInternet Protocol (TMoIP) Standard. This Standard provides the ranges with a standards-basedsolution for the ground transport of serial streaming telemetry from multiple vendors and animprovement in cost competitiveness.Chapter 4 contains recommendations for implementing the ground network. Twoappendixes provide information for TMoIP implementation. Appendix F provides additionalinsight into the management aspects of TMoIP. Appendix G, while not in the scope of theTMoIP requirements, provides information to the user to enable the deployment of a networkinfrastructure that supports the TMoIP implementation.Any range that uses telemetry will benefit from this Standard. The purpose of the TTGeffort is the identification of the needs of the Major Range and Test Facility Base (MRTFB)community for telemetry (TM) transmission and development of a standard to ensure futureinteroperability of commercial solutions. This document presents a common standard for use byindustry to ensure interoperability and a more cost effective solution for the ranges. Use of thisdocument will also eliminate the need to rely on a single source for critical equipment in thesupport of range missions within the MRTFB.Please direct any questions to:Secretariat, Range Commanders CouncilATTN: TEWS-RCC1510 Headquarters AvenueWhite Sands Missile Range, New Mexico 88002-5110Phone: DSN 258-1107COM (575) 678-1107E-mail usarmy.wsmr.atec.list.rcc@mail.milix

Telemetry over Internet Protocol (TMoIP), RCC Standard 218-20, February 2020This page intentionally left blank.x

Telemetry over Internet Protocol (TMoIP), RCC Standard 218-20, February oSUDPVIDVLANairborne instrumentation systemasynchronous transfer modecommunications distribution hubCanonical Format Indicatorcommand line interfacecommercial off-the-shelfdata quality encapsulationdifferentiated servicesDigital Signal 3differentiated services code pointFederal Information Processing StandardsHyperText Transfer ProtocolHyperText Transfer Protocol SecureInternet Assigned Numbers AuthorityInstitute of Electrical and Electronics EngineersInternet Group Management ProtocolInternet ProtocolInternet Protocol SecurityInternet Protocol version 4Internet Protocol version 6Lucent connector; local connectormedia access controlmaximum transmission unitOpen Standard Interconnectprovider edgePrecision Time ProtocolQuality of Serviceradio frequencyRequest for CommentsSession Announcement Protocolsubscriber connector; square connector; standard connectorSession Description ProtocolSimple Network Management ProtocolSynchronous Optical NetworkingSecure ShellSpanning Tree ProtocolTransmission Control Protocoltime-division multiplexingtelemetryTelemetry over Internet ProtocolType of ServiceUser Datagram ProtocolVLAN identifiervirtual local area networkxi

Telemetry over Internet Protocol (TMoIP), RCC Standard 218-20, February 2020This page intentionally left blank.xii

Telemetry over Internet Protocol (TMoIP), RCC Standard 218-20, February 2020CHAPTER 1Introduction and Overview of the Telemetry over Internet ProtocolThis document provides specifications and guidance for the ground network segments,which includes the telemetry (TM) terminal, network processor, and the ground networksubsystems of a TM range network. This document is for use by equipment vendors in designingproducts that enable the transport of TM data over Internet Protocol (IP) networks. The“Transmission over Internet Protocol (TMoIP) solution”, discussed in Chapter 2, addresses theground network elements listed below. The ground network functional blocks, first identified inChapter 2, are discussed in detail in subsequent chapters. The requirements andrecommendations for the TM terminal and network processor elements are located in Chapter 3.In addition, Chapter 4 addresses the ground network implementation via a set ofrecommendations regarding implementation elements that will enhance the robustness of theTMoIP solution.a. TM Terminal. The TM terminal interface provides connectivity to the TM stream. TheTM stream interface is described by a set of electrical characteristics (such as waveformamplitude and frequency) and mechanical characteristics (such as connector type). Thisdocument defines the range of TM stream types to be supported, including thecharacteristics associated with Layer 1 (Physical Layer) of the Open StandardInterconnect (OSI) model (see Section 3.3).b. Network Processor. The network processor furnishes the bulk of the TMoIP solution, andconsists of the TM stream interface, the TM stream processing, and the ground networkinterface. The scope of this document is to define the requirements for the networkprocessor associated with OSI Layer 7 through OSI Layer 1.While this document refers to TMoIP, the requirements for the networkprocessor at OSI Layer 1 and OSI Layer 2 are also within the scope of theTMoIP implementation.c. Ground Network Link. This link provides IP network connectivity and transport of theTMoIP traffic. The ground network includes the network end equipment, typically an IPswitch or router, and the interconnecting network. In some cases, the interconnectingnetwork may not be an IP network, but may be a Synchronous Optical Networking(SONET) or asynchronous transfer mode (ATM) implementation. In these cases, thenetwork end equipment may include functionality to perform the required adaptationfrom the IP switch/router to the native network format.1-1