iNET Telemetric Networks May 9, 2011€¦ · • Overview of the Telemetry Network System demonstration system – Project Overview ... TGS Tech. Demo TGS/ROS Development SUB TAS

iNET Telemetric Networks

May 9, 2011Thomas Grace

[email protected]

Naval Air Systems Command

Ben [email protected]

Southwest Research Institute

5/9/2011 1ITEA Workshop 2011

iNET Telemetric Networks

• Participant– Have a basic knowledge of networking concepts

– Involved in flight test, instrumentation, or telemetry

• Participants will gain an understanding of– Telemetric networking principles

– Applicable networking technologies

– Issues associated with building telemetric networks

• Overview of the Telemetry Network System demonstration system– Project Overview

– Telemetric network development

– Component Overview

– System Integration and Testing


Outline

• Session 1: Project Overview– TmNS Overview

– High-Level Capabilities

– High-level Schedule/Milestones

• Session 2: Telemetry Network Demonstration System– TmNS Conceptual Overview

– TmNS Message Flows

– TmNS Data Flows

• Session 3: Telemetry Network System Concepts– System Wide Designs

– System Management

– Spectrum Management

– Metadata

• Session 4: Telemetry Network System Development– TmNS Development

• Development approach

– TmNS Components• TA Subsystem Components

• RF Subsystem Components

• Range Operations Components

• Mission Control Components

• Ground Support Equipment

• Session 5: System Integration and Testing– iNET System Integration Lab

– Mission Control & Range Operations Integration Lab

– RF Subsystem Integration Lab

– TA Subsystem Integration Lab


Session 1:

Project Overview

High Level


Some Terminology

• Integrated Network Enhanced Telemetry (iNET)– The Project

– Currently only covers the Aeronautical Test Environment

– Mission is to enhance existing telemetry systems• Goal is not to replace existing telemetry systems

• Telemetry Network System– Enhancement of existing systems to incorporate standardized networking technologies

– Segments – used for segmenting work with the project• Radio Access Network Segment (RANS)

– Basically everything to create a wireless RF network

• Range Operations Segment (ROS)– Essentially everything necessary to manage the range resources to establish two-way network connectivity

between the mission control room and the Test Article

• Telemetry Ground Segment (TGS)– Fundamentally all the applications for a test mission to utilize the network for mission conduct

• Test Article Segment (TAS)– Basically all network instrumentation on the test article minus the radio

– Subsystems – used to help explain the system from an operational viewpoint• Mission Control Subsystem

– Fundamentally all the applications for a test mission to utilize the network for mission conduct

• Range Operations Subsystem– Essentially everything necessary to manage the resources to establish communications between the Mission

Control Room and the Test Article

• RF Subsystem– Basically all wireless communications between the TA and the Ground

• Test Article Subsystem– Basically all the wired communications on the test article


System Context

Ground SupportEquipment

Test Article #1

Mobile Antenna

Test Article #2

Antenna Site #1

Antenna Site #2

Antenna Site #3

Mission Control RoomRange Operations Center5/9/2011 6ITEA Workshop 2011

Telemetry Network System

Vehicle Data

Acquisition Network

Vehicle Data

Acquisition Network

Vehicle Data

Acquisition Network

RF Network Telemetry

Serial Streaming Telemetry Mission

Control

Range

Operations

Data

Analyst

Data

Analyst


Vehicle Data

Acquisition Network

Vehicle Data

Acquisition Network

Vehicle Data

Acquisition Network



Control

Range

Operations

Data

Analyst

Data

Analyst


Vehicle Data

Acquisition Network

Vehicle Data

Acquisition Network

Vehicle Data

Acquisition Network



Control

Range

Operations

Data

Analyst

Data

AnalystRange 1

Range 2



Vehicle Data

Acquisition Network

Mission

Control

Range

Operations

Data

Analyst

Data

Analyst

Vehicle Data

Acquisition Network

Mission

Control

Range

Operations

Data

Analyst

Data

Analyst

Range 1

Range 2

Aircraft transitioning

from one range to

another


High-Level Capabilities

• Retrieval of Measurement Data from TA– Fetch PCM data

– Fetch Network data

• Remotely Control TA Instrumentation– Manage SST Transmitter

– Manage PCM Data Acquisition System

– Manage Network Data Acquisition System

• Dynamic Allocation of Wireless Resources between TAs– Reallocation of resources within a single RF network

– Reallocation of resources between multiple RF networks

• Handoff Wireless Network Telemetry– Antenna to Antenna Handoff (A2A)

– Network to Network Handoff (N2N)

– Range to Range Handoff (R2R)

• Two-Way Encrypted Voice Communications– Test Article to Ground

– Test Article to Test Article

• Standards being utilized to accomplish these capabilities– Radio Access Network Standard

– Test Article Network Standard

– System Management Standard

– Metadata Standard


Typical Systems Engineering

Technical Reviews


Telemetry of the Future

• System Development and Demonstration– System Definition Review - Complete

– System Requirements Review - Complete

– System Functional Review – Complete

– Preliminary Design Review – Complete

– Detail Design Review – Fall 2011

– Prototype Contracts Awarded – 2011

– Flight Test Demonstration - 2012/2013

• Low-Rate Initial Production and Deployment– IDIQ Contracts – 2012/2013

– Initial Operation Capability – 2013/2014


High-Level Project Schedule

2010

SDR

2013

RANS Technology Demonstrators

2011 2012

SRR

SFR

SSR

PDR

CDR

Adv. Flight Test

SDRSystem Definition Review

SRR System Requirements Review

SFR System Functional Review

SSR Software Spec. Review

PDR Preliminary Design Review

CDRCritical Design Review

SUB Sub-Spiral Review

TRR Test Readiness Review

Calendar

Year

RF SubSystem PDR

TA SubSystem PDR

RO/MC SubSystem PDR

RF SubSystem CDRTA SubSystem CDRRO/MC SubSystem CDR

RANS Development

iSIL Integration & Test SIT

PAX

TAS Technology Demonstrators

SIT System Integ. & Test Review

TRR

TGS Tech. Demo

TGS/ROS Development

SUB

TAS Development

SUB

IDIQ Contracts Award

TmNS Deployment

Dev. Flt. TestTRR EDW


End of Session 1


Session 2:

TmNS Demonstration Overview

Aeronautical Environment


System Overview

Conceptual Overview


System

Ground Support

Equipment

Test Article #1

Mobile Antenna

Test Article #2

Antenna Site #1

Antenna Site #2

Antenna Site #3

Mission Control RoomRange Operations Center


System: TmNS Perspective

• Test Article– Instrumented test article acquiring measurement data

• Antenna Site– One or more directional antennas used to communicate with the test article

• Range Operations Center– Manages the resources operating in a private domain

• RF Network, Antenna Control Unit (ACU), RF PCM Receiver, Range Network Infrastructure

• Mission Control Room– Manages the conduct of the test

• Controls the on board instrumentation

• Retrieves data from the TA data recorder

• Voice communications with TA

• Ground Support Equipment– TA Instrumentation Checkout

• Configures TA instrumentation

• Provides initial TA radio configuration

• Validates TA measurement data


TA Network Concept

Switch

Switch

Network

Recorder

Multifunction

Display

TA

Manager

Time

Source

DAU

DAU

DAU

DAU

Voice

Gateway

Network

Encryptor

Switch

RF

Network

Measurements•Accelerations

•Discrete’s

•Flow

•Forces/Loads

•Positions

•Pressures

•Temperatures

•Torque/Horsepower

•Voltages/Currents

Bus Catalogs•1553

•Arinc 429

•Arinc 664

•Ethernet

•Fibre Channel

•Firewire

•Munitions/Stores

•RS-232/422

TA

Resource

Manager

Local

Data

Storage

Crew

Display

IEEE 1588

Grandmaster

PCM

SystemGateways

TA

CheckoutEthernetDAU–GSE Cart


TA Network Concept

• PCM System– Existing PCM System (e.g. CAIS)

• Includes the PCM transmitter

• Gateways– Enables information flows to and from the TA network and a PCM System

– Realized into two components• PCM Gateways

• Network Gateways

• DAU (Data Acquisition Unit)– Acquires measurements for analog transducers and digital communication buses

• Switch– Ethernet Switch used in interconnect network nodes

• Time Source– Acquires GPS satellite signals and uses the signal to generate IEEE-1588 time for distribution across the network

• Voice Gateway– Provides the ability to communicate with the MC utilizing network voice protocols

• TA Manager– Manages the resources on the TA

• Configuration, control, status

• Network Recorder– Records network traffic

– Provides a means to retrieve TmNS data messages from media

• Multi-Function Display– Provides the ability to display measurements

• Network Encryptor– Provides a means to secure information

• GSE Cart– TA Instrumentation Checkout


RF Network Concept

TA

Radio

Gnd

Radio

Link

Manager(TDMA Controller)

RF

Network

Manager

TA

Network

Range

Network

Gnd

Radio

Gnd

Radio

Gnd

Radio

RF

Resource

Manager

Manages

TDMA

Epochs

Can have more than one TDMA domain

•Based on spectrum availability

Time

SourceIEEE 1588

Grandmaster Ethernet


RF Network Concept

• TA Radio– Accepts/Produces IP datagram's/packets

– Accepts/Generates an RF waveform

– Follows Quality of Service (QoS) rules

• Ground Radio– Accepts/Produces IP datagram's/packets

– Accepts/Generates an RF waveform

– Follows QoS rules

• Range Network– Existing network infrastructure that interconnects the facilities

• Link Manager– Provides a means to manage/control/schedule the TDMA epoch

– Schedules resources to satisfy QoS constraints

• RF Network Manager– Manages the local RF network resources


• Time Source– Acquires GPS satellite signals and uses the signal to generate time

• Such as IEEE-1588 time for distribution


ITEA Workshop 2011

Range Operations

Network Concept

ACU

PCM

ReceiverACU

PCM

ReceiverACU

PCM

ReceiverRange

Network

SST

Proxy

SST

Proxy

SST

Proxy

ACU

PCM

Receiver

SST

Proxy

SST

Manager

RF Network

OPs Manager

Time

Source

IEEE 1588

Grandmaster

Ethernet

RF

Network

Manager

Range

Resource

Manager

Range Network

Manager

RF

Resource

Manager

One per TDMA domain

5/9/2011 23

Range Operations Network Concept

• Antenna Control Unit (ACU)– Used to control the elevation and azimuth of the directional antenna

• PCM Receiver– Used to receive an RF PCM signal, demodulate, and bit synchronize

• SST Proxy– Provides the means to proxy remote management to existing ACU’s and PCM

Receivers

• SST Manager– Provides the means to manage remotely existing ACU’s and PCM Receivers

• RF Network OPs Manager– Provides the means to manage remotely the RF Network

• Range Network– Existing network infrastructure that interconnects the facilities

• Range Network Manager– Provides the means to manage the range network infrastructure

• Time Source– Acquires GPS satellite signals and uses the signal to generate time

• Such as IEEE-1588 time for distribution


Mission Control

Network Concept

Range

Network

Network

Encryptor

MC

Manager

Telemetry

Processing

System

Display

Processing

System

Network

Recorder

Local

Data

Storage

MC

Resource

Manager

Time

SourceIEEE 1588

Grandmaster

MCR

Network

Existing

System

Existing

System

Ethernet

Instrumentation

Operations

Workstation

Voice

Gateway

Voice

Distribution

System


Mission Control Network Concept

• Network Encryptor– Provides a means to secure information

• MCR Network– Existing network infrastructure that interconnects the network components

• MC Manager– Provides the ability to manage network resources within the MCR


• Time Source– Acquires GPS satellite signals and uses the signal to generate IEEE-1588 time for distribution

• Voice Gateway– Provides the ability to communicate with the TA utilizing network voice protocols

• Voice Distribution System– Provides the ability to distribute voice throughout the MCR

• Network Recorder– Records network traffic

– Provides a means to retrieve TmNS data messages from media

• Telemetry Processing System– Provides the ability to manage data requests from users to the TA

– Processes telemetry data for utilization within the MCR

• Display Processing System– Processes data for display


ITEA Workshop 20115/9/2011

System Preliminary Design

RF NetworkOps

Manager

Network Recorder

SSTTransmitter

PCMGateway

Network Switch

Mu

ltifu

nctio

n

Dis

pla

y

Network

DAU

Network Switch

GPS Antenna

PTPTime

Server

Network Switch

TmNSData

Server

NetworkRecorder

Diplexer

OmniAntenna

TA Radio

Gnd Radio

Network Encryptor

Network Encryptor

Network Switch

RangeResourceManager

Key Manager

Key Manager

Preliminary Design of the TmNS Demonstration System

SSTManager

GPS Antenna

PTPTime

Server

NetworkGateway Network

Router/ Switch

Network Router

TAManager

VoiceGateway

TmNSData

Selector

NetworkProcessing

(Red)

NetworkProcessing

(Black)

VoiceGateway

GndRadio

Network Router/Switch

OmniAntenna

Network Encryptor

PCM

Network

DAU

PCM

Network Switch/PTP Time Sever

Network Switch

Network Switch

To SST

GSE?

Captive

Weapon

IOEWorkstation

GPS Antenna

PTPTime

ServerMissionControl

Processor

RTPSTelemetryAdapter

Network Switch

Existing MCR

IADSDisplaySystem

LinkManager

RFNetworkManager



SST Manager

Proxy

QueueManager


Network Switch

RangeNetworkManager

Network Switch

IRIG B DC

Range Network

COTS

Modified COTS

Development

IRIG

B D

C

Existing

PCM Data System

Test Article

Antenna Site

Network

GSE Mission Control Room

Existing Antenna Site

AntennaFeed

DirectionalAntenna

Range Operations

Center

PTPTime

Server

GPSAntenna

To Rec/BS

To

AC

U

27

28ITEA Workshop 20115/9/2011

System Overview

GSE Red Network

Range Operations Network

TEST ARTICLE

ANTENNA SITE

RANGE

OPERATIONS

MISSION CONTROL

GSE RED

CART

TA Voice

Gateway

TITLE

TmNS Demo

System Overview

REVISED

3/30/2011

DRAWN BY

Carl Reinwald

TA Red Network

Existing PCM

System

PCM

PCM

PCM

GSE BLACK CART

LEGENDNetwork

Recorder

Network

Data Acquisition

Units (DAUs)

Onboard

TA Manager

Bulk

Encryptor

Multifunction

Display

Network

Gateway

PCM

Gateway

Onboard

TA Manager

GSE Network

Proc (Red)

Network

Simulators

Non-TmNS

DeviceGSE Black Network

SST Proxy

Ground Radios Ground Antennae

RF Network Ops Manager SST Manager

SST Receivers

Antenna Control Units

Private Network

IRIG B

IOE

Workstation

(GSE Net Proc Red)

Voice

Gateway

Voice

GatewayNetwork

Recorder

Mission Control

ManagerBulk

DecryptorTelemetry Processor

(MCS / RTPS)

TPA

Network

SST

MANAGEMENT

DOMAIN COLORS

Mission

Control

RF

Network

Test

Article

IEEE-1588

Time Source

Includes Routers and

Switches

TmNS

DEVICE

TmNS

End Node

TmNS

Manager

Icon’s color indicates

Management Domain

iNET PROGRAM MANAGER

Bruce Lipe

REV

B

Link

Manager

RF Network

Manager

Antenna Site Network

TA Radio

(IR2)

Ground

Radio

IADS Caching

Data Server

IADS Workstations

IADS Display System

Network

Analzyer

Range

Network

Mission Control (MCR) Network

TA Black Network

EXISTING GSE

CART

1

0

1

1

0

1

0

1

1

0

iNET SYSTEM ENGINEER

Thomas Grace

GSE

Antenna

TA

Antenna

GPS

Antenna

GPS

Antenna

ETHERNET

GPS RF

RF

PCM

CONNECTIONS

Network

Encryptor

Network

Encryptor

Network

Encryptor

Diplexer

Notes:

Red and Black GSE Carts are only connected to the

Test Article when the Test Article is in the hangar.

One RFNM and LM required per TDMA domain; each

RFNM / LM pair may be located at either an Antenna

Site or the Range Operations Center.

2

1

2

1

GPS

Antenna

GPS

Antenna

GSE Network

Proc (Black)

GPS

Antenna

GPS

Antenna

SST

Transmitter

GPS

Antenna

Test Changes and Impacts

• Telemetry Network System– Supports a wide range of capabilities

– No one single CONOPS• However, need core functionality to support basic functions

• Test Mission Conduct– Changes test mission conduct

– Increases fidelity in the test data• Ability to fill in unknowns

• Ability to verify data

– Requires increase of situational awareness in the control room• Able to analyze more data – current and post event

• Test Article Data System– Manageable remotely

– Able to reconfigure to satisfy test conditions

– Able to gain direct access to more test data

• Range/Test Operations– Requires tighter coupling between range operations and test operations

• During test mission conduct

• More fidelity required during test planning

• Roles– Potentially adds new roles

• At least increase role responsibilities

– Test Conductor/Director• Ensure test team is focused on current test events

– Instrumentation Engineer• More of a role in the mission control room

• Ensure the test data is decision quality data

• Configuration Management– Able to change test configuration

– Change needs to managed


System Message Flows

Major Interactions


System Physical Hierarchy

TmNS

(SDD)

Range2Range 1

TA3 TA4TA1 TA2

Peripherals

Network

Devices

Mission

Control

Facility

Mobile

Asset

Range

Operations

Center

TA3GSE

LAN

Network

Recorder

Network DAUs

Switches

Network

Encryptor

TA Radio

Switches

Routers

MCR1

Tm Processor

Ground TA

ManagerApps

Hardware

Network Switches

Voice Gateway

Ground Radio

Network Analyer

Ground TA

ManagerInstrumentation

Checkout Tool

1588 Time Server

Computers

Network Encryptor

MDL Authoring

ToolNetwork

Visualization Tool

TA Manager

Time Source

Gateways

Peripherals

Network

Devices

Network

Recorder

Network DAUs

Switches

Network

Encryptor

TA Radio

TA Manager

Time Source

Gateways

Peripherals

Network

Devices

Network

Recorder

Network DAUs

Switches

Network

Encryptor

TA Radio

TA Manager

Time Source

Gateways

Peripherals

Network

Devices

Network

Recorder

Network DAUs

Switches

Network

Encryptor

TA Radio

TA Manager

Time Source

Gateways

Network

Encryptor

Antenna

Sites

Ant1

Feed

Gnd

Radio

Ant2

Feed

Gnd

Radio

Ant3

Feed

Gnd

Radio

Ant4

Feed

Gnd

Radio

MCR2

Tm ProcessorGround TA

Manager

MCR3

Tm Processor

Ground TA

Manager

MCR4

Tm Processor

Ground TA

Manager

SDREN

R2R and N2N Handoff

Range

Network

Switches

Routers

Range

Operations

Center

Range

Network

Apps

Network Manager

RF Network Ops

Manager

Switches

Routers

Ant M

Feed

Gnd

Radio

Apps

RF Network Ops

ManagerRF Net Manager

& Link Manager

Network

Encryptor

Network

Encryptor

Network

Encryptor

SST Manager

Network

Visualization Tool

Network Manager

RF Network Ops

Manager

SST Manager

Network

Visualization Tool


System Hierarchy

TmNS

(SDD)

Gnd

Antenna

Feed

RANS

Antennas

RF

Network

Mgmt

Radio

Gnd

RadioRF Net

Manager

TA

Radio

TA

AntennaLink

Manager

TGS

Gnd

SST

GndTime

Source

Resource

Mgmt

SST

Receiver

Control

Synced Time

Source

MC

Apps

FetchData

Range

Network

WAN

Fix SST

Dropouts

Ant.

Control

SST

Manager

Gateways

TAS

TA

SST

TATime

Source

TA

NetworkPeripherals

Synced Time

Source

GSE

Gnd TA

Manager

Network

DAUs

Network

Recorders

MultifunctionDisplays

Network

Encryptor

Switch

Router

Xmitter

ROS

Network

Manager

MC

Network

Network

Encryptor

Switch

RouterMC

Manager

GndTime

Source

Synced Time

Source

RF

Network

Ops

Manager

Voice

Gateway

Instr

Checkout

Network

Visual

Network

Visual

Network

Visual


ITEA Workshop 2011

System Context Diagram

Telemetry Network

System (TmNS)

Demonstration

System (SDD)

Test Article

Power

TmNS Demonstration System Context Diagram

Acquisition

Sources/Sinks

Instrumentation

Engineering

Environment

Ground

Power

Equipment

Manufactures

Range

Operations

Center

Data

Processing

Test

Planning

Key

Management

Mission

Control

Facility

Signals/

Interference

Install/

Maintain

Measurand/

Signals

28VdcS

ign

als

/

Inte

rfe

ren

ce

120Vac

@60Hz

Support/

Repair

Support/

Maintenance

Measurands/

Parameters

Resources/

Priorities

Other Test Articles

Time Reference

Communication Relays

Security Threats

Test Engineers

Data Analysts

Range Control

Other Ranges

Keys

Awareness

Commands/

Messages

Re

qu

est/

Re

sp

on

se

s

Commands/

Messages

Request/

Responses

5/9/2011 33

ITEA Workshop 2011

TmNS Message Flow

Test

Article

Segment

(TAS)

Radio

Access

Network

Segment

(RANS)

Telemetry

Ground

Segment

(TGS)

Telemetry

Network System

(TmNS)

Demonstration

System

(SDD)

Segment-Level Message Flow of TmNS SDD

Range

Operations

Segment

(ROS)

IP D

ata

Tim

e D

ata

IP Data

Time Data

SM

Da

taSM

Da

ta

PCM Data

(SST)

IP D

ata

SM Data

Tim

e D

ata

5/9/2011 34

ITEA Workshop 2011

Peripherals

Ground

Support

Equipment

(GSE)

TA Gateways

(Serial Streaming Telemetry)

Test Article

Network

(RED)

TA

Time

Source

Radio

Access

Network

Segment

(RANS)

Network

Encryptor

ExistingInstrumentation

System

SM Data

IP Data

Time Data

SM Data

IP Data

Time Data

IP Data

Tim

e D

ata

IP

Da

ta

GPS SIgnal

SM

Da

ta

Tim

e D

ata

SM

Da

ta

PCM Data

Config Data

IP D

ata

SM

Da

ta

SST

Transmitter

IRIG B

PCM Data

To Gnd SST

IP Data

TA

Time

Source

SM

Da

ta

Test Article

Network

(Black)

SM Data

Time Data

Tim

e

Da

ta

GP

S S

Ign

al

TAS Message Flow

5/9/2011 35

365/9/2011

RANS Message Flow

TA

Antenna

Gnd

Antenna

TA

Radio

RF Network

Management

Test

Article

Segment

(TAS)

Gnd

Radio

RF Network

Management

Range

Operations

Segment

(ROS)

DataData

IP D

ata

Tim

e

Da

taData

SM

Da

ta

IP D

ata

Tim

e

Da

ta

SM

Da

ta

IP

Da

ta

Logically Connected

SM

Da

ta

Time

Data

ITEA Workshop 2011

ITEA Workshop 2011

ROS Message Flow

Radio

Access

Network

Segment

(RANS)

SM Data

IP Data

SM Data

IP Data

Tim

e D

ata

SM

Da

ta

Time Data

Telemetry

Ground

Segment

(TGS)

Range

Network

Local Area Network

RF Network

OPs

Manager

Synchronized

Time Source

Tim

e

Da

ta

SM

Da

ta

SST

Manager SM

Data

Spectrum

Assignment

Manager

Gnd

SST(Serial Streaming Telemetry)

SM Data

Time Data

PCM Data

IP Data

Range

Network

Manager

SM Data

SM Data

GPS SIgnal

5/9/2011 37

ITEA Workshop 2011

TGS Message Flow

Range

Operations

Segment

(ROS)

MC

Time

Source

Network

Encryptor

IP D

ata

IP Data

Tim

e

Da

ta

IRIG B

Network

Recorder

Telemetry

Processing

System

Mission

Control

Manager

MCR

Network

SM

Da

ta

Tim

e D

ata

IP Data

SM Data

Time Data

IP Data

SM Data

Time Data

5/9/2011 38

TmNS Message Flows

• Three basic types of flows in system– All use the same communication pathway

• Management– Used for configuring, statusing, and reporting

• Time– Distribution of time through the network

• IP Data (Measurements)– Two delivery mechanisms defined

• Latency/Throughput Critical Data

– Connectionless service

• Reliability Critical Data

– Connection oriented service


TmNS Data Flows

•Outline

–TmNS Terminology and Data Transport

–Combined SST and TmNS Data Flows

–Summary


Applications

• Lossless Telemetry– SST Backfill – retrieve lost SST data from recorder

– TmNS Backfill – retrieve lost TmNS data from recorder

– TmNS Direct – lossless data direct to ground

• Remote Control of Instrumentation System– Reconfigure Instrumentation

– Recorder Control (start / stop)

• Efficient Spectrum Utilization– Dynamic Spectrum Allocation

– SST Transmitter Reconfiguration (power and frequency)

• TmNS provides a bidirectional network to support these and other capabilities


TmNS Technical Definitions

• TmNS: Telemetry Network System

• TmNS Data Message– A “container” for holding and transporting data

• measurement data, bus data, etc.

• End Node– A network device that produces and/or consumes TmNS Data Messages

• Network Device– A device that merely propagates TmNS Data Messages (i.e. router, switch, etc.)

– Neither produces nor consumes TmNS Data Messages

• Network Recorder– An End Node that records TmNS Data Messages and can replay TmNS Data

Messages back on demand

• Network Gateway– An End Node that provides a bidirectional data gateway between the TmNS and

a PCM system


TmNS Network Protocols

• For network transport of TmNS Data Messages, the

TmNS uses the Internet Protocol (IP) Suite

• TmNS uses two data transport protocols:

– Transmission Control Protocol (TCP)

– User Datagram Protocol (UDP)

• TmNS Data Messages are encapsulated in either TCP

packets or UDP datagrams and then encapsulated into

IP packets

TmNS Data

MessageTCP Packet Encapsulation

TmNS Data

Message

TCP

Header

UDP Datagram Encapsulation

TmNS Data

Message

UDP

Header

UDP/IP Encapsulation

TmNS Data

Message

UDP

Header

IP

Header

TCP/IP Encapsulation

TmNS Data

Message

TCP

Header

IP

Header


Reliability Critical (RC)

Data Delivery Protocol• Reliability Critical (RC) Data Delivery Protocol

– TmNS Data Messages transported via TCP

• TCP Pros:

– Reliable delivery

• retransmits lost packets

– Ensures proper ordered data delivery

– “Robust” protocol

• TCP Cons:

– Non-deterministic data latency

• due to retransmission of packets

– “Robust” protocol

• requires network overhead


Latency/Throughput Critical (LTC)

Data Delivery Protocol• Latency/Throughput Critical (LTC) Data Delivery

Protocol– TmNS Data Messages transported via UDP

• UDP Cons:– Data delivery not guaranteed

• packets can be dropped

– Data can arrive out of order• TmNS messages have sequence numbers

• UDP Pros:– Relatively low, deterministic data latency

– Efficient multiple consumer support• Able to utilize multicast delivery

– “Simplistic” protocol• less network overhead than TCP

– Controlling network configuration increases reliability


Example: Classification of TmNS Data Flows

• LTC Data Delivery Data Flows

– LTC-AQ

• Data originates directly from an acquisition source

– LTC-NAQ

• Data does not originate directly from an acquisition source

– (ex: simulation data recorder retrieved data)

• RC Data Delivery Data Flows

– RC-DR

• Data Retrieval, retrieval of recorded TmNS Data Messages

– RC-NRT

• Near Real Time, lossless transmission of acquired data


Test Article

TmNS Data Flows

• End Nodes multicast LTC-AQ messages

• End nodes – DAUs, Recorders, Displays, etc.

• Network Recorder records LTC-AQ messages

• Network Recorder plays back RC-DR messages on demand

Note:

• Network Recorder could also play back LTC-NAQ messages for simulation

End

Nodes

Network

Recorder

Ethernet

TmNS Transceiver

to Ground Station

RC-DR Data

LTC-AQ Data

LTC-AQ Data

Network

Gateway

Test Article

SubnetLTC-NAQ Data

LTC-NAQ Data

Router

LTC-AQ Data transmitted to Ground Station

only if ground application subscribes to

specific multicast address


ITEA Workshop 2011

SST & TmNS Data Transport:

SST Only Option• Pulse Code Modulation (PCM)

– Data transmitted as a serial bit stream of binary-coded time-

division multiplexed (TDM) words

• PCM data sent to Data Recorder may be different than

PCM data sent to SST Transmitter

– Normally all PCM data send to SST Transmitter is recorded

• Current data transport mechanism

PCM

Controller

SST Transmitter to

Mission Control

DAUsData

Recorder

PCM Data to

PCM Recorder

PCM Data to

SST Transmitter

5/9/2011 48


SST + RC-DR

• PCM data sent to SST Transmitter and Network Gateway

• Network Gateway builds and multicasts LTC-AQ messages with PCM packages

• Network Recorder records LTC-AQ messages


Notes:

• Only PCM data available to Mission Control

• Requires SST Backfill process with RC Data Retrieval to obtain lossless PCM

• PCM Data sent to Data Recorder may also be recorded on Network Recorder

Network

Recorder

Network

Gateway

PCM

Controller

SST Transmitter to

Mission Control

TmNS Radios

to Mission Control

Ethernet

LTC-AQ Data,

PCM Package

RC-DR Data,

PCM Package

Router

DAUsData

Recorder

PCM Data to

SST Transmitter

PCM Data to

PCM Recorder

Option 1



SST + RC-DR



• End Nodes (EN) multicast LTC-AQ messages with EN Packages

• Network Recorder records LTC-AQ messages; both PCM and EN Packages


Notes:

• PCM data available to Mission Control

• All recorded TmNS End Node data available via RC Data Retrieval

End

Nodes

Network

Recorder

Ethernet

Network

Gateway

LTC-AQ Data,

PCM Package

TmNS Radio

to Mission Control

RC-DR Data,

PCM PackageRC-DR Data,

EN PackageRouter

NO LTC-AQ Data

going to Ground Station

PCM

Controller

SST Transmitter to

Mission Control

DAUsData

Recorder

PCM Data to

Network Gateway

PCM Data to

Data Recorder

LTC-AQ Data,

EN Package

Option 2


ITEA Workshop 2011


SST + RC-DR + LTC-AQ




• Network Recorder records LTC-AQ messages, both PCM and EN Packages


Notes:

• PCM data and selected End Node data directly available to Mission Control

• All recorded TmNS End Node data available via RC Data Retrieval

LTC-AQ Data now

going to Ground Station

End

Nodes

Network

Recorder

Ethernet

Network

Gateway

LTC-AQ Data,

PCM Package

TmNS Radio

to Mission Control

RC-DR Data,

PCM PackageRC-DR Data,

EN PackageRouter

PCM

Controller

SST Transmitter to

Mission Control

DAUsData

Recorder

LTC-AQ Data,

EN Package

PCM Data to

Network Gateway

5/9/2011 51

ITEA Workshop 2011


SST + Full TmNS Flow




• Network Recorder records LTC-AQ messages, both PCM and EN Packages


• Network Gateway prepares TmNS Messages for insertion into a PCM structure

Note:

Network Gateway (illustrated here) will be implemented in two different components

PCM Gateway will take a PCM source and send to a TmNS data sink

Network Gateway will take TmNS data messages and send to a PCM sink

LTC-AQ Data,

EN Package

Network

Data

End

Nodes

Network

Recorder

RC-DR Data,

PCM Package

Ethernet

Network

Gateway

LTC-AQ Data,

PCM Package

TmNS Radio

to Mission Control

RC-DR Data,

EN Package

LTC-AQ Data,

EN Package

Router

PCM

Controller

SST Transmitter to

Mission Control

DAUsData

Recorder

PCM Data to

Data Recorder

SST Transmitter to

Mission Control

PCM Data to

Network Gateway

5/9/2011 52

SST & TmNS Data Transport

Summary• For Minimal Latency, potential for transmission loss

– PCM Data Source

• Typically use SST

– TmNS Data Source

• Typically use LTC-AQ

• For Lossless Data, potential for transmission delays

– PCM Data Source

• Use SST + RC-DR (SST Backfill)

– TmNS Data Source

• Use LTC-AQ + RC-DR (TmNS Backfill)

• Use RC-NRT – no planned implementations


End of Session 2


Session 3:

TmNS System Concepts

An Overview


System Concepts and

Design Decisions

Outline

–General Concepts

–Design Decisions

–Standardization


General Concepts

• TmNS:

– augments pre-existing PCM data delivery

mechanisms with bidirectional communication

– is made up of a network of networks

– is an enhancement rather than replacement

• melded with pre-existing devices, approaches, and

technologies

• “boldly goes where others have gone before”

– is an open system

– is formed from a collection of components that can be

interconnected in a variety of ways


System-Wide Design Decisions

(guided by the concepts)• TmNS components

– Standards Language• NetworkNodes, NetworkDevices, EndNodes

– Generally connected via Ethernet

– Modeled after “Network Appliances”• access points, network attached storage, …

– Networking concepts in pre-existing telemetry acquisition devices are adopted

• Some new features supporting bidirectional control are added

– Documented in Component Development Specifications (CDS)



(guided by the concepts)• TmNS utilizes an IP network

– Chosen based on the success of the IETF hourglass

– Flight test should be a seamless part of the overall range network

– Ample pre-existing tools and libraries for management are available

– Standardized dynamic routing can be utilized

– Reliable peer-to-peer communication, point to multi-point transmission (multicast/unicast), and broadcast are supported

– Standardized Quality of Service (QoS) via DiffServ



(guided by the concepts)

• Encourage components to be interoperable

across vendors through standardization

– RF communication format and protocol


– Configuration via Metadata

– Message formats and protocols


Working Groups Documented

Standardized Approach• Created formal standard documents

– Included stakeholders: users, vendors, designers, military, commercial

– Standards documents cover a wide variety of options

– Component Development Specifications (CDS) specify standards document sections of interest

• System Management Standard Working Group (SMSWG) – A unified approach for discovery, configuration, statusing, and control of

devices connected anywhere within the TmNS

– Primary technology utilized• SNMP with TmNS specific MIBs

• Metadata Standard Working Group (MDSWG) – A method for describing system configuration (Metadata) in a common

fashion

– Primary Technology utilized• XML with a telemetry schema

– SMSWG standard describes standardized mechanisms for coordinating Metadata updates for individual components


Working Group Process

• Radio Access Network (RAN) Standard describes the bidirectional RF communication utilized by the TmNS,– Primary underlying technologies utilized:

• SOQPSK waveform

• IP Routing

• Test Article Standard Working Group (TASWG) – Focused on the test article network fabric, devices, and

network protocols and test article acquisition

– Primary underlying technologies utilized:• Classic internet IP

• TmNS data messages and delivery mechanisms


System Management

Outline

–Overview of system management

–Components of system management


Outline

• Introduction to System Management

• Network Management Architectures

– Provides a brief overview of centralized, distributed,

hierarchical system management architectures

• Spectrum Management

• Peripheral Management

– Provides a brief overview of the control mechanisms

and configuration aspects


5/9/2011 ITEA Workshop 2011

What does System Management do?

• Manages Network Devices

– Switches, Routers, Peripherals, Radios, etc.

• Configures Test

– Device settings and policies

• Provides Test Status

– Data rates

• Communicates Errors and Warnings

– Time source errors, data drops

• Control of Peripherals

– Control recorders, data sources, data sinks

65

Scope of System Management

• System Management is:

– Interfaces and functions allocated to the TmNS allowing for coordinated configuration, control, statusing, and fault management

• Includes the implementation of resource assignments

– Interfaces required to hook in range-specific processes for managing spectrum and wireless resources

• System Management is not:

– A manager

• It is the hooks that allows a variety of manager concepts to be implemented.

– An automatic spectrum assignment algorithm

• Spectrum assignment manager does the assignment algorithm

– An application

• Ranges provide system manager applications

– A mandated system management flow or process

• Process flow is range-specific


What is System Management?

• System:

Instrumentality that combines interrelated

interacting components designed to work as a

coherent unit.

Management:

The guidance and control of action

required to execute a process.

System Management guides and controls a collection of

interacting components to achieve a desired result in a

coherent manner.


What is the System?

iNET

Ground

Systems

RF

Environment

Network Resource

Peripheral Applications

Configuration

Management

Spectrum Resource

TmNS Peripherals

Test

Article

“Management”


Function of System Management

• Designed to simplify the operation of large networks; this includes:– controls strategic assets from a central position

– aids in strategically planning for network growth

– provides remote system management

– operates independently of the system it monitors

– supports multiple protocols

– operates as transparently as possible

– improves services• maintaining network stability

• tuning network performance

– balance various needs• including applications, systems, and technologies

– troubleshooting problems that might arise

– reduce downtime with fast response time

– control costs


System Management System

• A typical model of system management systems

consists of:

– a manager (s)

• the central controller

– the managed device

• network devices like routers and gateways which

interconnect sub-networks

– a protocol for communications, such as SNMP

• between network devices and the controller

• a set of parameters to be monitored and controlled


Components of a Management System

• Manager (s)

• Managed Device

– agent

– management

database

• Management protocol


System Management Standard

Technology Picture


Spectrum Management

Outline

–Overview of spectrum allocation issues

–Network and Spectral parameters


Spectrum Resource Challenges

• Diminishing availability of spectrum for TM

– Reassignment to other uses

– Increasing number of “competitors” for available spectrum

– More simultaneous units under test

• Demands of new telemetric networks

– Dynamic bandwidth allocation

– Dynamic sharing of spectrum between aircraft

– Dynamic quality of service (QOS) assignments

– Additional control parameters

• It’s a hostile environment!

– Once working, wired networks tend to continue to work

– Fixed wireless networks can be fine-tuned


What is Spectrum Resource Management?

• Provides interfaces to the user for status, configuration, and control of the available spectrum bandwidth

• Status– Link state, utilization, data rates, dropped packets,

errors, network topology, connected nodes, etc.

• Configuration– Link speed, routing, IP address, service setup,

firmware load, etc.

• Control– Enable/disable, reset, etc.


What is Spectrum Resource Management?

Spectrum

Time

SST

Aircraft 1

SST

Aircraft 2

Time Slot 1 – A1 to Ground

Time Slot 2 – Ground to A1



Time Slot 5 – Unassigned





Time Slot 5 – Unassigned

2.35 GHz 2.36 GHz 2.37 GHz 2.39 GHz

0 Secs

0.1 Secs


Spectrum Management Complications

• Consider Radio Access Network– TDMA parameters

• Slot time

• Slot allocation

• Frame gaps and guard times

– Modulation• Waveform

• Symbol rate

• Center frequency

– Power control• How far am I from my Hub?

– Antenna control• Where am I pointing in relationship to the test article?


Other Considerations

• Spectrum use must be coordinated among test articles

• Spectrum use must be coordinated among test ranges

– Range to Range handoff

– Ranges with spectral overlap

• QoS requirements of a test article are dynamic based on

data telemetry requirements

• Spectrum needs of a test article depend on its QoS

requirements

• Status monitoring of Spectrum resource parameters

required to determine system health and provide

feedback for control


Spectrum Management Approach

• Complexity and interdependence of spectrum

management parameters requires a centralized control

component

• Some aspects (e.g. slot allocation) may have response

time requirements that may require localized control

components

• Spectrum management depends on QoS and bandwidth

requirements of data sources

– Requires tight coupling between Network and Spectrum

management

• Exact mechanisms will be worked out on the Range.


Spectrum Management Summary

• Spectrum management driven by spectrum

allocation issues and new demands of

networked telemetry

• New systems have a number of parameters to

control

– TDMA, Modulation, Power, Antenna

• Interrelation of NM and SM parameters require a

close coupling of the two systems


Metadata

Outline

–For telemetric networks

–Components of metadata


Metadata for

Telemetric Networks• What is Metadata?

– Information that describes a test system from multiple aspects

– Describe test requirements

– Describe the design of a test system

– Describe the configuration of the test system• instrumentation, telemetry, network equipment, etc.

– Describe how test data is formatted, encapsulated, and stored

• What language is Metadata?– Most modern forms use XML and a schema definition

– A common metadata language is useful in the case that people, tools, hardware, and software applications will exchange information about a test

• without a common language for describing the test, interoperability between the elements in a test system is not likely

• What is a common Metadata common language?– Defines a common set of terms, concepts, and rules for which metadata descriptions are

created• basically an agreement in which how to exchange information

• XML schema is an example

• What Metadata is not?– Not a language for capturing measurement data

– Large part is describing the test configuration documented in a configuration file(s)


Metadata for

Telemetric Networks (2)• How is Metadata used?

– Metadata describing the configuration information in a common

language and documented in a standard file structure will:

• Allow a system manager application to configure the networks and

devices for basic network interoperability

• Metadata will be consumed by the end nodes (instrumentation and

telemetry devices) to configure the network interfaces for the test

– Metadata will describe the network data formats to ground

system application that will extract measurements from data

flows, or otherwise consume test data flows

– Metadata will describe the system management polices and

potentially the mapping between the system management

standard interfaces and the actual device specific interfaces


Metadata for

Telemetric Networks (3)

• Why is Metadata important to iNET?

– A common metadata language is crucial to iNET because of the

many users, hardware developers, and application developers

need a common language for exchanging information about the

test.

• Without a common language, users, vendors, and integrators will

develop their own disjointed and specialized files for storing test

setup and device configuration information.

– The lack of a standard metadata language will allow the past

practice of stovepipe designs to continue to proliferate, will limit

competition between vendors and application providers, and will

keep upward pressure on integration cost for tests.


Main Components of Metadata

• Language Standard

– The letters, words and some rules for forming

sentences

– Language modeling is a balance of generality for

extensibility and specificity for simplicity.

– Documented as a model, schema, and language

guide

• Instance Documents

– The books written in the language

– May adhere to additional rules (constraints)


ITEA Workshop 2011

Metadata Supports Applications

System

Management

Instrumentation

Design

Archival

Data Analysis

Ground

Processing

Instance docs

meta

da

ta

Instance docs

Instance docs

Instance docs

Instance docsNetworked

Devices

meta

da

ta

5/9/2011 86

UML model


Top-level Elements in the schema


Top-level elements

• Message Definition domains

– Data Streams (Available Data Outlets)

• Transport attributes

– Measurements

• The primary thing carried by an instrumentation network

– Messages

• A grouping of packages

– Networks

• The infrastructure

– Packages

• A grouping of data – measurement samples or other


End of Session 3


Session 4:

TmNS Development

System Design and Development


TmNS Development Approach


Background

• System Development and Demonstration (SDD)– Development: analysis, design, develop, mature

– Demonstration: system integration, interoperability, utility, maturity

• Acquisition Strategy– Evolutionary approach

• Field an operationally useful and supportable capability in the shortest time as possible

• Deliver initial capability with explicit intent of delivering improved or updated capabilities in the near future

– Continue maturing system between SDD and IOC

– Provide range support after IOC

• Evolve from Simulators to Technology Demonstrators to Prototypes

– Simulators & Technology Demonstrators built in parallel with System Development• Simulators

– Used by teams and vendors for initial development

– Used as a reference to validate technology demonstrators and prototypes

• Technology Demonstrators– Modifications to existing hardware platforms to support the standards

– Evolves into prototypes in compliance with system development

– Incremental releases of hardware and software

– Advanced Prototypes• Complies with system development process

• Used to demonstrate the capabilities identified in the TCRD


Background

• Exit Criteria for SDD

– Technology demonstrated in relevant operational

environment

– Demonstrate useful and meaningful capabilities

– Acceptable interoperability and operational

supportability

– Mature software capability

– No significant manufacturing risk


Development Activities

• System Development– System Engineering

• Analysis, design, develop, mature

• Specification development

• Results of reviews feed into ongoing development efforts

• Concurrent Efforts– Demonstrators built in parallel with design reviews

• Core hardware technologies considered mature

• Hardware updates considered manageable

• Incremental releases of hardware and software for system design insertions– Goal every six months

• Not risk free but manageable

– Efforts culminate into advanced prototypes

• Timeline– Work broken into manageable efforts

– Sub-Spirals used to identify milestones


Development Items

• Simulators– Utilized to directly support development activities

– Utilized by teams and vendors for initial development

– Utilized to help mature standardized interfaces

– Used as a reference to validate technology demonstrators and prototypes

– Used to increase the number of network nodes

• Technology Demonstrators– Modifications to existing hardware platforms to support the standards

• Core hardware technologies considered mature

• Hardware updates considered manageable

• Incremental releases of hardware and software

– Risk Reduction• Exercise the standards to form the TmNS interfaces

– As issues are found items will be sent back to the developer for modifications

– Evolve into prototypes in compliance with system development• Provides a level of understanding and confidence to better estimate prototypes


Development Items

• Advanced Prototypes– Represents the product baseline

• Matured technology demonstrators

– Complies with development specifications

• System Specification, Component Development Specifications, Software Requirements Specifications

– System designs/specifications from CORE tool are used for prototype development

– Used for qualification testing and advanced flight testing

– Used to demonstrate test requirements capabilities

• Reference Applications– Used for testing and integration of system components

– Not necessarily meant to be operational applications


Evolutionary Development

• Sub-Spirals– Used to evolve from

• Simulators to Technology Demonstrators to Advanced Prototypes

– Sub-Spirals A&B serve as maturing process for prototypes delivered in Sub-Spiral C

• Sub-Spiral A– Aim is to develop tools/simulators to help in the development and validation of the system

– Award contracts for technology demonstrators

– Begin integration of simulators and some technology demonstrators

• Sub-Spiral B– Test technology demonstrators to comply with relevant portions of the standards

– Continue system integration

– Insert changes from design process

– Provide realism into technical performance measures

– Provide feedback to developers on technology demonstrators

– Award contracts for advanced prototypes

• Sub-Spiral C– Continue testing technology demonstrators as needed, if any

– Test and integrate advanced prototypes

– Insert changes from design process

– Provide feedback to developers on prototypes and reference applications

– Prepare for Developmental Flight Test

– Prepare for Advanced Flight Test


Development Activities

Integration Activities

Technology Demonstration Component Development

Final System

Integration & Test

Iterative testing of Tech

Demonstrators

Iterative testing of Adv.

Prototypes


Flight Test

• Developmental: conduct at Edwards (Summer 2012)– Primary intent is to exercise the RF Network

• Demonstrate interoperability, mobility, and concurrent operations with four representative TAs

• Demonstrate Antenna to Antenna handoffs

– Secondary objectives• Utilize minimal Mission Control, Range Operations, and TA components

– Exercise basic data retrieval

– Exercise voice communications

• Advanced: conduct at Pax (Spring 2013)– Primary intent is to exercise the TmNS capabilities

• Demonstrate concurrent typical flight test utilizing four test articles– Exercise system from Transducer on TA to Data Display in MCR

– Conduct normal SST operations

– Demonstrate TmNS enhanced capabilities

» Exercise data retrieval via TmNS

» Exercise control TA instrumentation via TmNS

» Perform SST back-fill

» Exercise voice communications

» A2A, N2N, R2R handoffs

– Test missions will support challenging flight test maneuverers


System Components

An Overview


Component Interfaces

• Component– Hardware device (typically one box)

– Documented in a Component Development Specification • Includes functional, physical, and environmental aspects

• Augmented (when appropriate) with a Software Requirements Specification

• Interface– Physical Interfaces

• Hardware interface that is described by mechanical and electrical properties and protocols for signaling

• Standardized interface that is decoupled from the functional capabilities of the components

– Enables developers of components flexibility in adding capabilities to the system

– i.e. Ethernet

– Logical Interfaces• Typically a software interface that communicate will a logical entity within a component

• Transported by physical interfaces


TmNS Component Groupings

• Test Article Subsystem

• RF Network Subsystem

• Range Operations Subsystem

• Mission Control Subsystem

• Ground Support Equipment


Legend

Interfaces

Physical End PointPhysical Interface Name

Logical Interface Name(Logical End Point)

Component Name

Logical Interface Name(Logical End Point)


Test Article Subsystem


Test Article Subsystem Components

• Network DAU

• Network Recorder

• Onboard TA Manager (OTAM)

• TA Voice Gateway (TA-VG)

• Ground Voice Gateway (G-VG)

• PCM Gateway

• Network Gateway (NGW)

• Multifunction Display

• TA Network Switch

• TA Network Router

• TA Network Encryptor


TA Subsystem Components

• Unless shown otherwise, the following

components have the following common

functions

– Parse MDL


– IEEE 1588 time synchronization

– Logging



TA Subsystem Components

Network DAU Capability/Functionality

• Acquires data from various Test Article input sources (exact mix TBD until TA selected)– MIL-STD-1553

– ARINC-429

– Discretes

– Analog

• Timestamps data based on IEEE-1588 synchronized time

• Assembles timestamped data into TmNS Data Messages as described by MDL

• Marks TmNS Data Messages with DSCP as described by MDL

• Sends TmNS Data Messages using LTC delivery protocol to destinations described by MDL



Network DAU

Interfaces

TA Red Network

Network DAUComponent

Wired or Optical Ethernet Physical Interface

TA Acquisition Source

Acquisition Physical Interface (DAU – TA Acquisition Source)

Data Acquisition

LTC DataSource(TA Recorder, MFD, NGW, GSE NP Red, IOE WS, MCS TPA, RTPS TPA)

Vendor Specific Configuration(GSE NP Red, IOE WS)

System Management(OTAM, GSE NP Red, IOE WS)

IEEE 1588 Time Synchronization(TA Switch) User

Debug(HTTP)

Network Recorder Capability/Functionality

• Receives TmNS Data Messages using LTC delivery protocol

• Records received TmNS Data Messages on removable solid state media

• Provides RC Data Source capability– Supports retrieval requests for messages, packages, and

measurements

– Assembles requested data into TmNS Data Messages as described by MDL

– Marks the TmNS Data Messages of requested data with DSCP as described by MDL

– Sends the TmNS Data Messages of requested data using RC delivery protocol as described by MDL

• Provides FTP server for storage of MDL and other general files on same media as used for TmNS Data Message storage


112ITEA Workshop 2011

Network Recorder

Interfaces

TA Red Network

Network RecorderComponent


RC DataSource(MFD, GSE NP Red, IOE WS, MCS TPA, RTPS TPA)

Vendor Specific Configuration(GSE NP Red, IOE WS)

LTC DataSink(DAU, PCM GW)



Debug(HTTP)

5/9/2011

Onboard TA Manager

Capability/Functionality

• Discovers TA devices

• Discovers and verifies TA network topology

• Configures TA devices

• Controls TA devices

• Statuses TA devices

• Can be managed by a higher level manager

through consolidated management

• Provides basic HTTP user interface


Onboard TA Manager

Interfaces

TA Red/Black Network


System Management(DAU, TA Recorder, MFD, NGW, TA VG, NGW, PCM GW)

Onboard TA ManagerComponent


Debug(HTTP)


TA Voice Gateway


• Adapts between TA pilot analog two-way audio

and Voice over IP (VoIP)

• Listens for VoIP connection from Ground Voice

Gateway

• Supports three-way voice communications

between TA pilot, chase plane pilot, and MC

• Utilizes standard SIP/RTP VoIP protocols



TA Voice Gateway

Interfaces

TA Red Network



TA Voice GatewayComponent

TA Voice Distribution

System

Analog Voice Physical Interface (TA Voice – TA Voice Distribution System)

Analog Voice Input

Analog Voice Output

VoIP Control Channel(Gnd VG)

VoIP Data Channel(Gnd VG)


Debug(HTTP)

116

Ground Voice Gateway

Capability/Functionality• Adapts between MC analog two-way audio and Voice

over IP (VoIP)

• Originates and maintains VoIP connections to TA Voice Gateways

• Merges audio from TA Voice Gateways and MC

• Supports three-way voice communications between TA pilot, chase plane pilot, and MC

• Utilizes standard SIP/RTP VoIP protocols

• COTS device: Following common capabilities not required– MDL

– IEEE 1588


– Logging



Ground Voice Gateway

Interfaces

GSE Red Network/ MCR Network

Wired or Optical Ethernet Physical InterfaceGround Voice Gateway

Component

Ground Voice Distribution

System

Analog Voice Physical Interface (Gnd Voice –Gnd Voice Distribution System)

Analog Voice Input

Analog Voice Output

VoIP Control Channel 2(TA VG)

VoIP Data Channel 2(TA VG)

VoIP Control Channel 1(TA VG)

VoIP Data Channel 1(TA VG)

User Debug(HTTP)

118

PCM Gateway Capability/Functionality

• Receives and decommutates PCM stream– NRZ-L data/clock per IRIG 106-09 chapter 4

• Selects a portion of the PCM data according to the MDL

• Timestamps data based on IEEE-1588 synchronized time

• Assembles timestamped data into TmNS Data Messages as described by MDL

• Marks TmNS Data Messages with DSCP as described by MDL

• Sends TmNS Data Messages using LTC delivery protocol as described by MDL



PCM Gateway

Interfaces

PCM GatewayComponent


TA SST

RS-232/422 NRZ-L Bi-Phase L Serial PCM Physical Interface (PCM Gateway – TA SST)

PCM Stream

TA Red Network


IEEE 1588 Time Synchronization(TA Switch)

LTC DataSource(TA Recorder, MFD, NGW, GSE NP Red, IOE WS, MCS TPA, RTPS TPA)

User Debug(HTTP)

120

Network Gateway Capability/Functionality

• Receives TmNS Data Messages using LTC

delivery protocol

• Receives TmNS Data Messages using RC

delivery protocol

• Selects a portion of measurements from TmNS

Data Messages as described by MDL

• Generates a PCM stream containing the

selected measurements and CRC as described

by MDL

– NRZ-L data/clock per IRIG 106-09 chapter 4


5/9/2011

Network Gateway

Interfaces

Network GatewayComponent


TA SST Transmitter

RS-232/422 NRZ-L Bi-Phase L Serial PCM Physical Interface (Network Gateway – TA SST)

PCM Stream

LTCDataSink(DAU, PCM GW)

TA Red Network



Debug(HTTP)


Multifunction Display


• Receives TmNS Data Messages using LTC

delivery protocol

• Receives TmNS Data Messages using RC

delivery protocol

• Selects a portion of measurements from TmNS

Data Messages as described by MDL

• Displays selected measurements to user


Multifunction Display

Interfaces

UserUser Physical Interface (MFD – User)


Meas. Display

Multifunction DisplayComponent TA Red

Network




Debug(HTTP)


TA Network Switch (100 Mbps)


• Interconnects TA components

• Provides at least 5 10/100 Ethernet ports

• Transports Ethernet frames between connected network components

• Synchronizes internal clock to GPS

• Distributes IEEE 1588 time to connected network components

• Generates IRIG-B time code signal

• Can serve as an IEEE 1588 time master

• Provides a mirror port capability




Interfaces

GPSSignal

IRIG-B Time Signal


Component

TA GPSAntenna


IRIG-B Time Source Physical Interface

(TA Switch – Existing Instrumentation)

Existing Instrumentation

5

GPS Input Physical Interface (TA GPSAntenna)

TA Red Network/ GSE Red Network/

Peripherals



Debug(HTTP)

126



• Interconnects TA components

• Provides at least 4 10/100/1000 Ethernet ports

• Transports Ethernet frames between connected network components

• Synchronizes internal clock to GPS

• Distributes IEEE 1588 time to connected network components

• Generates IRIG-B time code signal

• Can serve as an IEEE 1588 time master

• Provides a mirror port capability




Interfaces

GPSSignal

IRIG-B Time Signal

TA Network Switch (1000 Mbps)Component

TA GPSAntenna



(TA Switch 1G – Existing Instrumentation)

4

GPS Input Physical Interface (TA GPSAntenna)


Existing Instrumentation

IEEE 1588 Time Synchronization(DAU, TA Recorder, NGW, PCM GW, MFD, OTAM, TA VG)

User Debug(HTTP)

TA Red Network/ GSE Red Network/

TA Components

128

TA Network Router


• Interconnects subnets

• Provides at least 3 10/100 Ethernet ports

• Routes IP packets between connected network

components


TA Network Router

Interfaces

TA Network RouterComponent


3

TA Red Network

System Management(OTAM, GSE NP Red, IOE WS) User

Debug(HTTP)


TA Network Encryptor

Capability/Functionality• Provides Type 1 encryption device capabilities

– National Security Agency's High Assurance Internet Protocol Interoperability Specification (HAIPE IS) version 3.0 or later

• Encrypts IP packets from TA

• Decrypts IP packets to TA

• COTS device: Following common capabilities not required– MDL

– IEEE 1588


– Logging


TA Network Encryptor

Interfaces

TA Network EncryptorComponent

Wired or Optical Ethernet Plain-Text Physical Interface

TA Red Network

Wired or Optical Ethernet Cipher-Text Physical Interface

TA Black Network


RF Network Subsystem


RF Network Subsystem Components

• RF Network Manager (RFNM)

• Link Manager (LM)

• Ground Radio (Radio-G)

• TA Radio

– Integrated Radio and RFNE (IR2)

• SST Transmitter

• Ground Station Tracking Antenna

• TA Antenna



RF Network Subsystem Components

RF Network Manager

Capability/Functionality• The RFNM is responsible for the optimized control and coordination of the

components that form one RAN

– The RFNM coordinates operations of all RAN components through direct interaction with

ground RAN components

– The RFNM coordinates RAN operations of the multiple Test Articles using the RAN by

communicating with peer RFNM functionality in the TA Radio components on the Test

Articles

– The RFNM serves as the single operational interface point of RAN control for other parts of

the TmNS (i.e., the ROS RF Network Operations Manager), coordinating all low level

operations

• System Manager for RAN components

– Ingest and Create RFNM/RANS MDL descriptions, perform initialization & statusing

• Coordinates details of inter-range and intra-range handovers

• Coordinates any/all low-level updates to RF Link and RAN data delivery mechanisms

• Coordinates/implements changes to RAN network forwarding configurations

• Provides FTP Client & Server


ITEA Workshop 2011

RF Network Manager Interfaces


RF Network Manager

Component

Wired or Optical Ethernet

Physical Interface

RFNM(Gnd Radio, TA Radio, LM)

RANOps Control (RFNO)

System Management(Gnd Radio, TA Radio, LM, RFNO)

User Debug(HTTP)

5/9/2011 137

Link Manager Capability/Functionality

• The LM is responsible for optimized control and coordination of radio operation across multiple radios in the Radio Access Network (RAN)

– Dynamically allocates the RF network capacity provided to all tests using the RAN so as to efficiently share the constrained RF resource

– Provides Time Division Multiple Access (TDMA) controller functionality to allocate slots for RF transmission among all uplinks and downlinks between radios located in Ground Stations and on Test Articles

• It provides the radios with operational parameters required to coordinate RF link establishment, handovers, and efficient operation

– Establishes, maintains and releases RF uplinks and downlinks

– Coordinates uplink and downlink RF transmission power control

– Applies radio link configuration settings and obtains and reports RF link status

– Determines the amount of RF transmission capacity to be allocated for each uplink and downlink in the Radio Access Network based on a combination of operational performance settings (e.g. priority, minimum capacity guarantees) and periodic measures of offered traffic load

– Coordinates radio link reconfiguration in support of intra-TmNS and inter-TmNS handovers

• SNMP agent; Ingests and Create RANS/LM MDL descriptions, initializes & provide status; Provides FTP Client


ITEA Workshop 2011

Link Manager

Component


Physical Interface

Link Manager

Interfaces

Queue Status(Gnd Radio, TA Radio)

System Management (RFNM, RFNO)

RFNM(RFNM)

Link Coordination(TA Radio)

Link Manager(Gnd Radio)

User Debug(HTTP)


5/9/2011 139

Ground Radio

Capability/Functionality• The Ground Radio performs RF transmission and reception between

the Ground and a Test Article – Burst transmission and reception; Physical layer modulation and

demodulation

– LDPC Forward Error Correction coding/decoding

– HDLC packet framing

– AES Link Layer encryption per FIPS-140-2

• Performs link control functions as directed by the RAN Link Manager

• Accepts and responds to RF Network Management commands

• Performs IP forwarding functionality for RF interface, wired interface, and internal network applications

• Performs optimized data delivery using Traffic Engineering (TE) Queues

• Acts as Queue Manager to provide management, control and statusing of TE Queue structures

• Provides SNMP agent; Ingests and Create RANS/Radio/QM MDL descriptions, initializes & provide status; Provides FTP Client


Antenna Site Network/ GSE Black Network

Gnd Radio

Component

RF Transceiver Physical Interface

Ground Antenna


Ground Radio

Interfaces

RFNM (RFNM)


IEEE 1588 Time Synchronization(RO Time Source)

Ethernet Transceiver(Range Network)

Link Manager(LM)

RF Transceiver(TA Radio)

Queue Status (LM)

User Debug(HTTP)


TA Radio (IR2)

Capability/Functionality• The TA Radio software combines functions of a Radio with RANS

functions required on a Test Article for RFNM, LM, QM and TE Queues– The RFNM and LM software in the TA Radio performs the peer protocol

with the corresponding RFNM and LM software on the ground

– QM and TE Queue software in the TA Radio provides queue management and operation, as well as support to LM software in the TA Radio

• The TA Radio performs RF transmission and reception between the Ground and a Test Article– Burst transmission and reception; Physical layer modulation and

demodulation

– LDPC Forward Error Correction coding/decoding

– HDLC packet framing

– AES Link Layer encryption per FIPS-140-2

• Performs link control functions as directed by the RAN Link Manager

• Accepts and responds to RF Network Management commands


TA Radio (IR2)

Capability/Functionality (cont.)

• Performs IP forwarding functionality for RF interface, wired interface, and internal network applications

• Performs optimized data delivery using Traffic Engineering (TE) Queues

• Acts as Queue Manager to provide management, control, and statusing of TE Queue structures

• Provides intermediate relay capabilities for remote Test Article

• Provides SNMP agent

• Ingests and creates RANS/TA Radio MDL descriptions, initializes & provide status

• Provides FTP client


ITEA Workshop 2011

TA Radio

Component



TA Antenna

TA Radio (IR2)

Interfaces

User Debug(HTTP)

RFNM (RFNM)


RF Transceiver(Gnd Radio)

Link Coordination (LM)


RFNM (RFNM)

User Debug(HTTP)

TA Black Network

Ethernet Transceiver(TA Switch)


5/9/2011 144

SST Transmitter Capability/Functionality

• Implement COTS PCM transmitter functionality

– IRIG-106-09 Chapter 2 and Appendix A section 7.0

• Enhanced with common TmNS functions


5/9/2011

SST Transmitter

Interfaces

SST TransmitterComponent


External PCM Source/Network Gateway

RS-232/422 NRZ-L Bi-Phase L Serial PCM Physical Interface

PCM Stream

SST Modulated Signal Physical Interface

TA Antenna

SST Modulated Signal

TA Black Network

System Management(SST Manager)


User Debug(HTTP)


Ground Station Tracking Antenna


• Ground Station Tracking Antenna Component

– GSTA Systems include the pedestal, pedestal interface

unit, dish, feed(s), antenna control unit and associated

interfaces required to exchange RF signals between radio

transceivers and the wireless communication medium

– Antenna Control Unit (ACU) functionality is usually not

physically part of the Ground Station Tracking Antenna

and is usually located in a separate physical unit nearby

• The ACU functionality, which is expected to be provided by an

unmodified COTS device, is represented as part of the GSTA to

simplify the overall SDD system description. Logical control of

the ACU is covered in the SRS for the SST Management

Proxies


Ground Station Tracking AntennaInterfaces

Wireless Communication

Medium


Component

RF Wireless Medium Physical Interface


ACU Wired Ethernet Physical Interface

TA Antenna

Gnd Radio

SST Proxy


Test Article Antenna


• Test Article Antenna Component

– Responsible for providing the RF interface between

the transmission medium, the TA Radio Component

and the SST Transmitter

– Will also include appropriate diplexer functionality to

combine and split the RF signals across multiple

inputs and outputs

• TA Antenna Component can be considered as a "TA

Antenna System"

– Anticipated to be mounted external and internal to the

airborne test platform commensurate with existing

installation methods



Interfaces

Wireless Communication

Medium


Component

RF Wireless Medium Physical Interface


SST Modulated Signal Physical Interface

SST Transmitter

TA Radio



Range Operations Subsystem


Range Operations Subsystem Components

• Commercial Off the Self (COTS) Components

– Range Ops Network Switch

– Range Ops Network Router

– Range Ops Time Source

• RF Network Operations Manager (RFNO)

• SST Manager

• SST Proxy



Range Operations Subsystem Components

Range Ops Network Switch

Interfaces

Range Ops Network

Switch

Component


Physical Interface

Note: Using COTS Product with IEEE 1588 support to meet timing requirements of Radio-G

Antenna Site Network/ Range Ops Network/

RANS/ROS Components

IEEE 1588 Time Synchronization(Gnd Radio, RFNM, LM, RFNO, SST Manager, SST Proxy)


Range Ops Network Router

Interfaces

Range Ops Network

Router

Component


Physical Interface

Note: Using COTS Product

Antenna Site Network/ Range Ops Network


Range Ops Time Source

Interfaces

IRIG-B

Time Signal

Range Ops

Time Source Component



Physical Interface

IRIG-B Distribution

IEEE 1588 Time Synchronization(Gnd Radio, RFNM, LM, RFNO, SST Manager, SST Proxy)


GPS Signal

GPS Antenna

GPS Input Physical Interface

If GPS Antenna is unavailable, use IRIG-B

Antenna Site Network/ Range Ops Network


RF Network Operations Manager

Capability/Functionality• The RFNO Manager is responsible for the optimized control and

coordination of all TmNS Radio Access Networks resident on a test range

• Handles high-level configuration and coordination of RAN operations– GUI for ROS operator interactions

• Adds range-wide scope to RAN operations – Provides centralized control interface for multiple unrelated tests

– Coordinates the operations between multiple RANs (Inter-range and Intra-range)

• System Manager for RANS components– Ingest and Create RFNO and RANS MDL descriptions, perform initialization &

statusing

• Coordinates inter-range and intra-range handovers

• Coordinates any/all updates to RF Link and RAN data delivery mechanisms

• Coordinates changes to RAN/ROS network forwarding configurations

• Provides FTP Client & Server, MDL Authoring Tool, Network Visualization Tool



Interfaces

User



Component

User Physical Interface


User(GUI)

RANOps Coordination (RFNO)

RANOps Control (RFNM)

System Management(Gnd Radio, TA Radio, LM, RFNM)


SST Manager Capability/Functionality

• Provide the ability to setup SST Receivers and Antenna Control Units– Assumes the SST Transmitters have been pre-configured

• Provides the ability to control an “Association” of devices as a single entity (i.e., change the attributes of all devices in an “Association” simultaneously)– An “Association” is the combination of a single SST

Transmitter and its associated (zero or more) SST Receivers and Antenna Control Units

• Maintains a list of known SST Transmitters, SST Receivers and Antenna Control Units

• Hosts MDL Authoring Tool and Network Visualization Tool


SST Manager Capability/Functionality

• Key Transmitter Capabilities (manage & status)– Frequency

– Modulation

– Randomization

– Power (low/high)

– Temperature

• Key Receiver (both L3 and SEMCO) Capabilities (manage & status)– Frequency

– Modulation

– Derandomization

– Signal strength

– Bit Rate

• Key Antenna Control Unit (TCS ACU) Capabilities (manage & status)– Tracking Mode

– Tracking Band

– Antenna pointing information


SST Manager

Interfaces

User Debug (HTTP)

SST Manager ComponentRange Operations

Network


Physical Interface


System Management(SST Proxy, SST Transmitter)


SST Proxy Capability/Functionality

• Provides a TmNS System Management

interface for the following devices:

– L3 RCB-2000 Dual Channel Receiver / Combiner

– SEMCO RC600A-2 Telemetry Receiver Combiner

– TCS ACU-M1 Antenna Control Unit

• Supports multiple devices via the TmNS Adapter

application

• Is managed by the SST Manager


Antenna Control Unit(TCS ACU-M1)

SST Proxy

Interfaces

User Debug (HTTP)

SST Proxy Component

Antenna Site Network/

Private Network


Physical Interface

System Management(SST Manager)

SST Receiver(L-3 RCB 2000)

Antenna Control Unit(TCS ACU-M1)

SST Receiver(SEMCO RC600-A2)

PAXEAFB


2


Mission Control Subsystem


Mission Control Subsystem Components

• IOE Workstation

• Commercial Off the Self (COTS) Components– MC Network Switch

– MC Network Router

– MC Network Encryptor

– MC Time Source

• MC Network Recorder

• Mission Control Manager

• MCS Telemetry Processor Adapter

• RTPS Telemetry Processor Adapter

• IADS Display System



MC Subsystem Components

Instrumentation Operations Engineer (IOE)

Workstation Capability/Functionality

• Same capabilities as GSE Network Processing

System (Red)

• Install GSE Network Processing System (Red) in

MC and call it the IOE Workstation

• See GSE brief for Capabilities/Functions and

Interfaces


MC Network Switch

Interfaces

MC Network SwitchComponent

Wired or Optical EthernetPhysical Interface

MCR Network



MC Network Router

Interfaces

MC Network

Router

Component


Physical Interface


MCR Network


MC Network Encryptor

Interfaces

MC Network EncryptorComponent

Wired or Optical Ethernet Plain-Text Physical Interface

MCR Network

Wired or Optical Ethernet Cipher-Text Physical Interface

MCR Network



MC Time Source

Interfaces

IRIG-B

Time Signal

MC Time Source Component


MCR Network


MC IRIG-B Distribution

IEEE 1588 Time Synchronization(MC Time Source)



MC Network Recorder


• Same capabilities as TA Network Recorder

Component except targeted for Ground

environment


ITEA Workshop 2011

MC Network Recorder

Interfaces

MCR Network

MC Network RecorderComponent


RC DataSource

Vendor Specific Configuration(MC Manager)

LTC DataSink(MCS TPA, RTPS TPA)

System Management(MC Manager)

IEEE 1588 Time Synchronization(MC Time Switch) User

Debug(HTTP)

5/9/2011 173

Mission Control Manager Capabilities

• Functions as a TmNS Network Node Manager for Mission Control Devices– Discovers Mission Control TmNS Devices

– Configures and Controls Mission Control TmNS Devices

– Provides Status Displays for Mission Control TmNS Devices

• Provides status displays for Telemetry Processor Adapters– MCS TPA

– RTPS TPA

• Hosts MDL Authoring Tool

• Hosts Network Visualization Tool

• Hosts Vendor Applications


Mission Control Manager

Interfaces

User

MCR Network



User (HTTP)

Mission Control ManagerComponent

System Management(MC Recorder, MCS TPA, RTPS TPA)


Vendor Specific Configuration(MC Recorder)


MCS TPA Capability/Functionality

• Implement TmNS Network Node functionality

• Obtain requested TmNS Data

– Support TmNS LTC and RC Data Delivery

• Deliver all received TmNS Data to MC Recorder

• Maintain Data Request Queue


MCS TPA Capability/Functionality

• Convert MDL Instance Document into suitable

MCS configuration files

• Verify setup MDL Instance Document matches

current TA MDL Instance Document

• Process IADS Display System (IADS DS) data

requests

• Convert received TmNS data into Telemetry

Processor format and deliver data to IADS DS

• Provide PCM Backfill



MCS TPA

Interfaces

User

MCR Network



User

(GUI)

MCS Telemetry Processor Adapter

Component

MCS Management(MCS MCP)

IADS Data(IADS DS)

Decom Control(MCS Decom)

ION Bus Physical Interface (MCS TPA – MCS ION Bus)

IONBus

Processed Data(MCS Nodes)

Existing MCS Telemetry Processor

IEEE 1588 Time Synchronization(MC Time Source) LTC DataSource

(MC Recorder)


LTC DataSink(TA Recorder, DAU)

RC DataSink(TA Recorder)

PCM Data(MCS Decom)

178

RTPS TPA Capability/Functionality

• Implement TmNS Network Node functionality

• Obtain requested TmNS Data

– Support TmNS LTC and RC Data Delivery

• Deliver all received TmNS Data to MC Recorder

• Maintain Data Request Queue


RTPS TPA Capability/Functionality

• Convert MDL Instance Document into suitable

Vista 550 configuration files

• Verify setup MDL Instance Document matches

current TA MDL Instance Document

• Process IADS Display System (IADS DS) data

requests

• Convert received TmNS data into Telemetry

Processor format and deliver data to IADS DS

• Provide PCM Backfill



RTPS TPA

Interfaces

User

MCR Network



User

(GUI)

RTPS Telemetry Processor Adapter

Component

IADS Data(IADS DS)

Existing RTPS Vista 550 Telemetry Processor


LTC DataSource(MC Recorder)


LTC DataSink(TA Recorder, DAU)


RTPS PCM Ingest

(Vista 550)

RTPS Processed Data

(Vista 550)

Vista 550 Physical Interface(s) (RTPS TPA – Vista 550)

RTPS Config

(Vista 550)

181

IADS Display System


• Provide user interface to request TmNS-

available data

• Display received TmNS data seamlessly with

other telemetered data

• Display pristine PCM backfill data


ITEA Workshop 2011

Existing IADS Display System

IADS Display System

Interfaces

MCR Network

Wired or Optical EthernetPhysical InterfaceIADS Display System

Component

IADS Data(MCS TPA, RTPS TPA)

5/9/2011 183

Ground Support Equipment

Overly Simplified View


Ground Support Equipment Components

• GSE Networking Processing System (Red)

• GSE Networking Processing System (Black)



GSE Components

GSE Networking Processing System (Red)

Capability/Functionality• Hosts applications and support tools to allow initial setup,

checkout, and pre-flight of TA red side components

• Hosts Ground TA Manager Application– Discovers TA devices

– Discovers and verifies TA network topology

– Configures TA devices

– Controls TA devices

– Statuses TA devices

– Can be managed by a higher level manager through consolidated management

– Can manage TA components either directly or through consolidated management interface to Onboard TA Manager (if present)

– Provides detailed graphical user interface (GUI)




• Hosts Instrumentation Checkout Application

– Receives TmNS Data Messages using LTC delivery

protocol

– Receives TmNS Data Messages using RC delivery

protocol

– Displays information about the TmNS Data Messages

to the user including

• TmNS Data Message header, packages, measurements




• Hosts Vendor Applications

– Provides a transitional path to full MDL processing on

EndNodes

• Reduces developmental risk for demonstration system

– Process an MDL file containing instrumentation

requirements

– Augment the MDL file with as-built information for the

device specifics of a particular device




• Hosts the MDL Authoring Tool Application to

build/modify GSE/TA Red Network configuration

files

• Hosts the Network Visualization Tool Application

to display GSE/TA Red Network current

configuration and status



Interfaces

User(GUI)User


Component


GSE Network

User Physical InterfaceIEEE 1588 Time Synchronization(GSE Switch, TA Switch)

System Management(OTAM or TA Components)



Vendor Specific Configuration(DAU, TA Recorder)


GSE Networking Processing System (Black)


• Hosts applications and support tools to provide a self-contained representative instance of RF Network and Range Ops infrastructure and control capabilities to support the TA instrumentation and preflight process– Hosts RF Network Operations Manager to provide a high-level

operator GUI and orchestrate overall GSE/TA RF component initialization and control

– Hosts RF Network Manager to initialize and manage GSE cart and TA RF Network components

– Hosts Link Manager to control operation of GSE cart Ground Radio operation on GSE cart and IR2 on Test Article

– Hosts SST Manager Application to configure TA SST Transmitter

– Hosts MDL Authoring Tool to build/modify GSE/TA ROS & RF Network configuration files

– Hosts Network Visualization Tool to display GSE/TA Black Network current configuration and status


GSE Networking Processing System (Black)

Interfaces

User(GUI)User

GSE Networking Processing System (Black) Component


User Physical Interface IEEE 1588 Time Synchronization(GSE Switch, TA Switch)

GSENetwork

System Management(Gnd Radio, TA Radio, SST Proxy, SST Transmitter, OTAM)

RFNM(Gnd Radio, TA Radio)

Queue Status(Gnd Radio, TA Radio)

Link Coordination(TA Radio)

Link Manager(Gnd Radio)

User Debug(HTTP)


End of Session 4


Session 5:

System Integration and Testing

High Level


System Testing Approach

• Overall approach documented and guided by System Test Plan

• Organized into three major overlapping phases– Test Plan Authoring

– Test Setup

– Test Implementation

• Utilize iNET System Integration Lab (iSIL) at SwRI

• Develop System Management and Metadata framework for distribution– Provides baseline representation of system standards

• Reuse test tools developed by teams, reference applications, and simulators– Provides baseline representation of standards

– Provides example software to community

• Work closely with teams– Provide test plans to teams before testing

– Cooperative testing among teams

– Provide constructive feedback to teams to speed resolution of issues


System Integration and Test Approach

• Integrate components from subsystems into an

overall system

– RF Network, Range Network, TA Network, MCR Network

• Provide lab testing of system

• Validate system is ready for

– Developmental Flight Test

– Advanced Flight Test

• Build increasing fidelity of system

– Use software simulators and COTS initially

– Replace with prototypes as they become available

– Three sub-spirals of capability


iSIL Approach

• Build up representative configurations– Currently have some test article hardware

• Focus on end-to-end control and data flow

• Utilize existing flight hardware where possible– Switches, adapt EndNodes with Proxies

• Utilize COTS hardware as needed until prototypes are available– Switches, routers, general PCs as device simulators

• Augment network size and loading with simulators

• Measure throughput, latency, timing accuracy, jitter, network link utilization, and data loss


iNET System Integration Lab (iSIL)

Ground Station

Test Articles and Simulated Nodes


Mission Control and Range Operations

Test and Integration• Test & Integration labs at both Edwards & Pax in work

• Mix of iNET and Range investment

• Primary purpose: full capabilities to support flight tests

• Initial uses: component and sub-system integration– Reduces risk for flight test, and system integration at iSIL

• Edwards (MCS / IADS)

• Dedicated System at antenna site, B4795

• May loop back thru range network to add ground test fidelity

• Pax (RTPS Vista 550 / IADS)

• Shared System at main RTPS site, B2118 (iNETprimary user)

• Potential to schedule some operational range assets– Example: TA recorder (or sim) at antenna site accessed via

range network from MCR iNET lab at B2118.

EAFB Bldg 4795 iNET Demo Lab5/9/2011 200ITEA Workshop 2011

RF Network

Test and Integration• Support development of

RF Subsystem – Reference Implementations

– Technology Demonstrators

– Advanced Prototypes

• Support unit and subsystem test of – Radios / IR2

– LM, RFNM, RFNO

• Support RF Subsystem Integration prior to System Integration at iSIL

General purpose laptops used to support varied reconfigurations based on specific test/integration needs


TA Network

Test and Integration• Build four representative test

articles in iSIL at SwRI– Simulators initially – replace with

hardware and software as it becomes available

• Utilize COTS hardware as needed until all flight hardware available– Switches, routers, general PCs as

device simulators

• Augment network size and loading with simulators

• Add capabilities as planned in spirals– Follow test plans to validate new

capabilities with regression testing for risk items

–Test Articles and Simulated Nodes


End of Session 5


Thank You!

We appreciate your questions, comments,

and interest.


Back Up Slides



System Overview

GSE Red Network


TEST ARTICLE

ANTENNA SITE

RANGE

OPERATIONS

MISSION CONTROL

GSE RED

CART

TA Voice

Gateway

TITLE

TmNS Demo

System Overview

REVISED

3/30/2011

DRAWN BY

Carl Reinwald

TA Red Network

Existing PCM

System

PCM

PCM

PCM

GSE BLACK CART

LEGENDNetwork

Recorder

Network

Data Acquisition

Units (DAUs)

Onboard

TA Manager

Bulk

Encryptor

Multifunction

Display

Network

Gateway

PCM

Gateway

Onboard

TA Manager

GSE Network

Proc (Red)

Network

Simulators

Non-TmNS

DeviceGSE Black Network

SST Proxy

Ground Radios Ground Antennae

RF Network Ops Manager SST Manager

SST Receivers

Antenna Control Units

Private Network

IRIG B

IOE

Workstation

(GSE Net Proc Red)

Voice

Gateway

Voice

GatewayNetwork

Recorder

Mission Control

ManagerBulk

DecryptorTelemetry Processor

(MCS / RTPS)

TPA

Network

SST

MANAGEMENT

DOMAIN COLORS

Mission

Control

RF

Network

Test

Article

IEEE-1588

Time Source

Includes Routers and

Switches

TmNS

DEVICE

TmNS

End Node

TmNS

Manager

Icon’s color indicates

Management Domain

iNET PROGRAM MANAGER

Bruce Lipe

REV

B

Link

Manager

RF Network

Manager


TA Radio

(IR2)

Ground

Radio

IADS Caching

Data Server

IADS Workstations

IADS Display System

Network

Analzyer

Range

Network

Mission Control (MCR) Network

TA Black Network

EXISTING GSE

CART

1

0

1

1

0

1

0

1

1

0

iNET SYSTEM ENGINEER

Thomas Grace

GSE

Antenna

TA

Antenna

GPS

Antenna

GPS

Antenna

ETHERNET

GPS RF

RF

PCM

CONNECTIONS

Network

Encryptor

Network

Encryptor

Network

Encryptor

Diplexer

Notes:

Red and Black GSE Carts are only connected to the

Test Article when the Test Article is in the hangar.

One RFNM and LM required per TDMA domain; each

RFNM / LM pair may be located at either an Antenna

Site or the Range Operations Center.

2

1

2

1

GPS

Antenna

GPS

Antenna

GSE Network

Proc (Black)

GPS

Antenna

GPS

Antenna

SST

Transmitter

GPS

Antenna

Acronym List


A2A Antenna to Antenna (Handoff)

ACU Antenna Control Unit

AES Advanced Encryption Standard

API Application Programming Interface

ARINC Aeronautical Radio, Inc.

ARQ Automatic Repeat-reQuest

AS Advanced Server

BER Bit-Error Rate

CAIS Common Airborne Instrumentation System

CDR Critical Design Review

CDS Component Development Specification

CONOP Concept of Operation

COTS Commercial Off-the-Shelf

CRC Cyclic Redundancy Check

CSCI Computer Software Configuration Item

DAU Data Acquisition Unit

DiffServ Differentiated Services

DSCP DiffServ Codepoint

FCAPS Fault, Configuration, Accounting, Performance, Security

FTP File Transfer Protocol

GND Ground

GPS Global Positioning System

GSE Ground Support Equipment

GSTA Ground Station Tracking Antenna

GUI Graphical User Interface

GW Gateway

HAIPE IS High Assurance Internet Protocol Interoperability Specification

HDLC High-Level Data Link Control

HTTP Hypertext Transfer Protocol

HWCI Hardware Configuration Item

IADS DS IADS Display System

ICMP Internet Control Message Protocol

IDIQ Indefinite Delivery/Indefinite Quantity

IEEE Institute of Electrical and Electronics Engineers

IETF Internet Engineering Task Force

iNET integrated Network-Enhanced Telemetry

IOC Initial Operational Capabilities

IOE Instrumentation Operations Engineer

IOE WS IOE Workstation

IP Internet Protocol

IR2 Integrated Radio and RFNE

IRIG Inter-Range Interoperability Group

iSIL iNET System Integration Lab

LDPC Low-Density Parity Check

LLCM Link Layer Control Messages

LM Link Manager

LoS Line of Sight

LRU Line-Replaceable Unit

LTC Latency/Throughput Critical

Mbps Megabits per second

MAC Media Access Control

MC Mission Control

MCR Mission Control Room

MCS Mission Control Subsystem

MDID Message Definition Identifier

MDL Metadata Description Language

MDSWG Metadata Standard Working Group

MFD Multifunction Display

MIB Management Information Base

MOE Measures of Effectiveness

MOP Measures of Performance

MOS Measures of Suitability

MTBF Mean Time Between Failure

N2N Network to Network (Handoff)

NDI Non-Developmental Items

NGW Network Gateway

NRZ-L Non-Return-to-Zero Level

OTAM Onboard Test Article Manager

OTH Over the Horizon

PC Personal Computer

PCM Pulse-Coded Modulation

PDR Preliminary Design Review

PGM Precision-Guided Munition

PES Project Engineering Station

PTP Precision Time Protocol

PTPD PTP Daemon 208ITEA Workshop 20115/9/2011


QM Queue Manager

QoS Quality of Service

R2R Range to Range (Handoff)

RAN Radio Access Network

RANS Radio Access Network Segment

RC Reliability Critical

RCC Range Commander’s Council

RF Radio Frequency

RFC Request for Comments

RFNE RF Network Element

RFNM RF Network Manager

RFNO RF Network Operations

RHEL Red Hat Enterprise Linux

RO Range Operations

ROC Range Operations Center

ROS Range Operations Segment

RTPS Realtime Telemetry Processing System

RTSP Real-Time Streaming Protocol

SDD System Development and Demonstration

SIP Session Initiation Protocol

SM System Management

SMSWG System Management Standard Working Group

SNMP Simple Network Management Protocol

SOQPSK Shaped-Offset Quadrature Phase Shift Keying

SREQ System Requirements

SRR System Requirements Review

SRS Software Requirements Specification

SRU Shop-Replaceable Unit

SST Serial Streaming Telemetry

TA Test Article

TAS Test Article Segment or Test Article Standard

TASWG Test Article Standard Working Group

TBD To Be Determined

TCP Transmission Control Protocol

TCRD Test Capabilities Requirements Document

TCS Telemetry and Communication Systems, Inc.

TDMA Time Division Multiple Access

TE Traffic Engineering

TES Test Engineering Station

TGS Telemetry Ground Segment

TMATS Telemetry Attributes Transfer Standard

TmNS Telemetry Network System

TPA Telemetry Processor Adapter

TPM Technical Performance Measures

UDP User Datagram Protocol

URI Uniform Resource Identifier

VG Voice Gateway

VoIP Voice over IP

WAN Wide Area Network

WBS Work Breakdown Structure

XML eXtensible Markup Language