An Architecture for AFSCN G dAFSCN Ground Interface Modernization

Dr Bharathi DeviDr. Bharathi DeviSMC/LAAFB

Dr. Lance WilliamsThe AerospaceThe Aerospace

GSAW 2012

© 2012 by SMC/LAAFB. Published by The Aerospace Corporation with permission.UNCLASSIFIED

Overview

• Background• Limitations of the current architecture• Limitations of the current architecture• Proposed changes• ImplicationsImplications• Prior related work• Conclusions• References

2UNCLASSIFIEDGSAW 2012

Background

• AFSCN ground network is almost 50 years old• Has many obsolete and proprietary protocols and• Has many obsolete and proprietary protocols and

equipments hindering its efficiency• Satellite Control and Network Systems Division

(SMC/SN) has identified many areas for modernization• Ground interface modernizationGround interface modernization• Compatible Sat C2

• GIG WAN ATM to IP transition is scheduled for 2014

3UNCLASSIFIEDGSAW 2012

AFSCN after IP transition

DISA AFSCN CommSegment

AFSPCDCC

IPKG

SOC C2system

gCiscoMSPP

OCNCisco3845 WANIUKG system

508 serial interfaceproprietary

interface

3845

DISA“GIG”

Cisco7606

CiscoMSPP

IPKG

WANIU RTS

RGFDCC

Cisco3845

MSPP

4

IPserial

UNCLASSIFIEDGSAW 2012

Limitations Addressed

• SOC to RTS interface is serial, based on link layer protocols EXU or IBM’s ADCCPprotocols EXU or IBM s ADCCP• Sustainment is costly• Seamless interface with other networks impossible• Interface not extensible

• Proprietary edge devices to translate serial interface, called WANIUcalled WANIU

• No centralized Network Management System (NMS) and the server associated with that

5UNCLASSIFIEDGSAW 2012

Elements of the Architecture

• Implementation of an open standard ground interface in AFSCN range segmentin AFSCN range segment• TCP/IP based on CCSDS/SLE (ANSI/AIAA S-123,124-

2007) for SV telemetry and commands• HTTP/XML for RTS monitor and control

• Implementation of the same interface in serial-to-WAN converter for legacy serial usersWAN converter for legacy serial users

• Implement network operations server for RTS administrative software for RTS status and NMS for

knetwork management

6UNCLASSIFIEDGSAW 2012

Open Standards Interface

• ANSI/SLE• Unframed telemetry• Unframed telemetry• Analog timing• Ternary command streams• Binary command streams• Command echo streams

XML/HTTP• XML/HTTP• RTS control and monitor

7UNCLASSIFIEDGSAW 2012

Architectural implications of the open standard interface

• Flexibility in interface implementation• In existing systems• In existing systems• In new systems

• Allows vendor choice for user C2 systemsy• Eliminates reliance on proprietary multiplexers

• Reduces sustainment costs

8UNCLASSIFIEDGSAW 2012

Changes to proprietary interfaces

•Requires serial to IP conversion in legacy WANIU boxes at range and SOC

Changes•RTS:•Serial converters removed from range segment

•Software changes to the RTS to implement SLE

•Software changes to implement XML

Current

Software changes to implement XML interface for monitoring

•SOC:•Alternative non-serial interface offered to SOCs

9UNCLASSIFIEDGSAW 2012

Range Architecture Changes

Single T&C data sessionfrom the active user

The active user connects directly to the RTS for SV T&C and RTS M&C. Inactive users have no access to RTS M&C data. Network admin uses telephone

C&S

TT&CCI

RBC / ARTS

ActiveUser

RTS M&C SV T&CSV T&C

TT&CCI

C&SC&SCI

InactiveUser

InactiveUser

Networkadmin

RTS M&C

Single T&C data sessionfrom the active user

The active user connects directly to the RTS for SV T&C and RTS M&C. Inactive users access RTS M&C data through the Current

C&SCI

Single M&C data sessionfrom the active user Serial

DSP

RBC ActiveUser

RTS M&C SV T&CSV

T&C

NetOps serverCurrent

M&Cagent

Epochserver

NetOpsServer

InactiveUser

InactiveUser

RTS

RTS M&C

Epoch

10

Networkadmin

RTS M&Cinterface

Two M&C data sessionsfrom the active userand NetOps server

IP

Future

UNCLASSIFIEDGSAW 2012

Network Management Element

• Centralized network management at the NOCs• Centralized network management at the NOCs• Distributes RTS status to non-active AFSCN users• Provides centralized administrative control of RTSs• Provides network management for AFSCN

11UNCLASSIFIEDGSAW 2012

Interface Modernization

WANIUWANIU SOC C2t

RBCAFSCN NOW

WANIU systemARTS

508 interfaceproprietary interface

proprietary interface508 interface

Legacy serialSOC C2

RBC

open standard interface

Serial-WANadapter

open standard interface

systemRBC adapter

Modern IPSOC C2system

ARTS(upgraded with

RBC core)

NetOps ServerMulti-le

Netw

pathbre

opens

)

Serial

12

evel access

work status

eakerservice

RTS

M&

CerviceAFSCN FUTURE IP

UNCLASSIFIEDGSAW 2012

Prior Proof-of-Concept Demonstration(status presented to GSAW 2007 Session 9)

• Civil Reserve Space Service project executed 2003-2006 • Developed ANSI standards for translation from legacy serial TT&C

interfaces (ICD 508) to CCSDS SLE • ANSI/AIAA S-123-2007 and ANSI/AIAA S-124-2007

• Demonstration in 2007 to connect NOAA Wallops and Fairbanks t ki t ti d J h H ki APL t ti t AFSCNtracking stations, and John Hopkins APL station, to AFSCN • Collaboration led by SMC/SN• Implemented ANSI standards in COTS front-end processors from 2

vendorsvendors • Successfully performed hundreds of satellite contacts on test

satellites• Demonstrated• Demonstrated

• interconnectivity to NOAA CDA stations• Interface coordination of US Govt. networks facilitated by agreement on

open standards

13

• Support of AFSCN-unique performance requirements

UNCLASSIFIEDGSAW 2012

Capability enhancements

• Will add broader range of RTS monitor and control points than the dozen or so supported on the currentpoints than the dozen or so supported on the current serial interface

• Packaging of unframed encrypted telemetry in time-tagged ANSI/SLE frames guarantees perfect time/data correlation

• Will provide unified capabilities as dictated in DoD IWill provide unified capabilities as dictated in DoD I 8100.04

• Enables federation with other ground systems

14UNCLASSIFIEDGSAW 2012

Changes to business logic

• SOC users retain real time control and status of RTS, but with more control and status pointsbut with more control and status points

• NOC gets electronic real time control and status (currently only by telephone)

• RTS status provided to non-active AFSCN users (not currently flying a satellite)

15UNCLASSIFIEDGSAW 2012

Conclusions

• Identified the current limitations of the AFSCN• Identified the current limitations of the AFSCN architecture

• Proposed an open architecture based interfaces for the AFSCN ground systems that will overcome the limitations of the current network

• Discussed implications of the architecture• Discussed implications of the architecture

16UNCLASSIFIEDGSAW 2012

References

1. Pietras, J., “Air Force Satellite Control Network Interoperability,” Space Internet Workshop #4, June 2004.

2. CCSDS SLE Development related: ANSI/AIAA S-123-2007 and ANSI/AIAA S-124-2007.

3. Ledlow, L., Spindler, J., & Williams, L., “harmonization of USG Satellite Ground Systems ” GSAW 2007Satellite Ground Systems,” GSAW 2007.

4. Pietras, J., “Application of ANSI Standards for Ground Transfer of Space Vehicle Command and Telemetry,” GSAW 2007.

17UNCLASSIFIEDGSAW 2012