ARCHITECTURE STUDY FOR FUTURE AIR FORCE SATELLITE CONTROL NETWORK

Transcription

1 ARCHITECTURE STUDY FOR FUTURE AIR FORCE SATELLITE CONTROL NETWORK -PRELIMINARY INVESTIGATION- GSAW February, 2001 Prepared By CARL SUNSHINE, TIEN M. NGUYEN, JOHN C. CHIANG, AND YOGI KRIKORIAN THE AEROSPACE CORPORATION EL SEGUNDO, CALIFORNIA Program Office: Dr. Carl Sunshine: (310) Technical Division: Dr. Tien Nguyen: (310) Dr. John Chiang (310)

2 AFSCN STANDARDS AND PROTOCOLS GOALS OBJECTIVES: ENHANCE INTEROPERABILITY WITH OTHER SATELLITE CONTROL SYSTEMS SUPPORT GREATER USE OF COTS EQUIPMENT AND SERVICES ADD ASTRODYNAMIC STANDARDS TO ORBIT ANALYSIS AREA ADD STANDARD WAN INTERFACE TO NEW (AND SOC) ADD USB AND CCSDS SPACE-TO-GROUND LINK TO ADD STANDARD SCHEDULING AND NET STATUS INTERFACES 2

3 BACKGROUND STANDARDS AND PROTOCOLS TASK IDENTIFIED AS KEY ELEMENT OF AFSCN EVOLUTION INITIAL STUDY WORK TO SURVEY CURRENT INDUSTRY AND OTHER GOV T PRACTICES AND ASSESS/ANALYZE DEMONSTRATION AND TEST EFFO WHERE NEEDED TO RESOLVE ISSUES/UNCERTAINTIES ACQUISITION/DEVELOPMENT OF NEEDED SOFTWARE/HARDWARE AND INTEGRATION INTO NEW AND OTHER AFSCN ELEMENTS 3

4 STUDY METHODOLOGY PROMISING STANDARDS MODIFY THE DESIGN FUTURE AFSCN STANDARDS & PROTOCOLS CONSTRUCT THE INITIAL DESIGN INFLUENCE THE FUTURE STANDARDS OR MAKE RECOMMENDATIONS TO CCSDS AND SCPS LEGEND: AFSCN S FUTURE REQUIREMENTS REVIEW REQUIREMENTS CCSDS, INTERNET AND ISO RECOMMENDATIONS: SPACE-SPACE SPACE-GROUND GROUND-GROUND AFSCN = AIR FORCE SATELLITE CONTROL NETWORK CCSDS = CONSULTATIVE COMMITTEE FOR SPACE DATA SYSTEM SCPS = SPACE COMMUNICATIONS PROTOCOL STANDARDS ISO = INTERNATIONAL STANDARDS ORGANIZATION 4

5 EVOLUTION VISION CCSDS & INTERNET RECOMMENDATIONS: SPACE-SPACE SPACE-GROUND GROUND-GROUND USERS: - NASA / USB - NOAA - OTHERS AFSCN/SGLS USERS: - DoD - NASA / SGLS - NOAA EVOLUTION PROCESS CCSDS & INTERNET RECOMMENDATIONS LEGEND: SGLS = SPACE-GROUND LINK SUBSYSTEM DoD = DEPARTMENT OF DEFENSE FUTURE AFSCN STANDARDS & PROTOCOLS USERS: - DoD - NASA - NOAA - OTHERS AFSCN-UNIQUE LEGACY 5

6 LEGEND: AFSCN ARCHITECTURE EVOLUTION Centralized Control, Centralized Execution, Point to Point Links SOCs Today Comm Satellite AFSCN Control Node Mission Satellite AFSCN NCC SOC After Comm Upgrades (2003) = REMOTE TRACKING STATION NCC = NETWORK CONTROL CENTER SOC = SPACE OPERATION CENTER WAN/IU = WIDE AREA NETWORK/INTERFACE UNIT DISN = DEFENSE INTEGRATED SWITCHING NETWORK Centralized Control, Decentralized Execution, DISN Network Mission Satellite WANIU DISN ATM 2007 WANIU AFSCN Network Management SOCs Schedule Other Govt Commercial Centralized Scheduling, Decentralized Execution, Multi-User WAN Service Other Govt WAN Service Std User Interface DoD, Other Govt, Commercial Satellite Commercial AFSCN Dedicated 6

7 KEY INTERFACES DETERMINE PROTOCOL AND STANDARDS FOR 5 LINKS: LINK 1: -SOC LINK 2: SOC-NCC (does not need standardization) LINK 3: -NCC LINK 4: S/V- (space to ground link) LINK 5: S/V-SOC (through ) Link 5 Link 4 S/V SOC Link 1 WAN Link 3 Network Control Center Link 2 LEGEND: S/V = SPACE VEHICLE NCC = NETWORK CONTROL CENTER 7

8 PROPOSED ARCHITECTURE FOR TELEMETRY NETWORK New CCSDS TLM Packets C TLM A CCSDS/Packet TLM (Future) USB CCSDS/SLE Processor IP I/F New WAN services New SOC Bit-Serial TLM (Current System) SGLS CCSDS TLM Packets Analog IRIG-B SGLS/CCSDS Converter LEGEND: C -- Control A -- Annotation TLM -- Telemetry SOC -- Satellite Operation Center DISN -- Defense Integrated Switching Network WANIU -- Wide Area Network Interface Unit -- Remote Tracking Station User Data and Clock WANIU DISN WAN WANIU SOC Analog IRIG-B Old SOC 8

9 SPACE LINK EXTENSION (SLE) SERVICES PROVIDED BY SLE SLE PROVIDES THE FOLLOWING SERVICES: MANAGEMENT SERVICES: SCHEDULING MONITORING CONTROLLING SLE TRANSFER SERVICES SPACE MISSION DATA EXCHANGE MODEL SPACE ELEMENT MANAGEMENT DATA EXCHANGE SPACE ELEMENT SLE MANAGEMENT DATA EXCHANGE SATELLITE OPERATION CENTER (SLE MDOS) INLCLUDES: - SPACE MISSION USERS - SPACE MISSION MANAGEMENT FORWARD AND RETURN DATA EXCHANGE 9

10 SPACE LINK EXTENSION (SLE) APPLICATIONS TO AFSCN INVESTIGATE USE OF SLE PROTOCOLS FOR FUTURE AFSCN APPLICATIONS: MANAGEMENT SERVICES (STILL BEING DEFINED): SOC-NCC LINK (E.G., SCHEDULING) SOC- LINK (E.G., POINTING ANGLES, PASS SETUP) DATA TRANSFER PROVIDE TIME TAGGING FOR TELEMETRY DATA PROVIDE TIMED RELEASE OF COMMANDS FROM 10

11 SOME RESULTS TO DATE PRELIMINARY INVESTIGATION ON USE OF CCSDS STANDARDS BETWEEN SOC AND Bit Error Rate used as primary evaluation criterion For commanding, may need double tail in Telecommand to avoid retransmission For telemetry across WAN, may need retransmission, which complicates real-time delivery CONTINUE INVESTIGATION OF SCPS AND SLE FOR USE IN FUTURE NATIONAL SATELLITE CONTROL NETWORK Planning tests of security, timeliness, data quality over standard WAN services 11

12 TEAM MEMBERS PROGRAM OFFICE: Dr. CARL SUNSHINE (LEAD), WAYNE OTSUKI, Dr. BILL DENG, GILBERT TAKAHASHI, Dr. ASHOK MATHUR TECHNICAL DIVISION: Dr. TIEN M. NGUYEN (LEAD) AND Dr. JOHN CHIANG (CO-LEAD): CCSDS STANDARDS AND PROTOCOLS, SPACE LINK EXTENSION PROTOCOLS, END-TO-END ARCHITECTURE, COTS SYSTEMS SURVEY, WIDE AREA NETWORK INTERFACE Dr. JAMES YOH: AFSCN REQUIREMENTS, COTS SYSTEMS SURVEY TOM TAM: SCPS PROTOCOLS DONALD LANZINGER: NETWORKING PERFORMANCE ISSUES AND SECURITY YOGI KRIKORIAN: WIDE AREA NETWORK INTERFACE AND CCSDS PROTOCOLS 12

13 DESCRIPTION OF THE 5 LINKS INTERFACE DESCRIPTION 1.a From to SOC S/V command echo data message or S/V telemetry data Status and test report messages and Retransmit request message 1. -SOC Measured spacecraft angular position messages and Ranging data 1.b From SOC to Configuration messages for pretest, readiness test and performance test A equipment setting messages and Antenna pointing message 2.a From SOC to NCC Contact request and S/V orbital data Network status 2. SOC-NCC 2.b From NCC to SOC Contact Schedule Network Status 3.a From to NCC Status and test report messages and Test response messages Maintenance request 3. -NCC 3.b From NCC to Contact schedule and Maintenance schedule Reconfiguration directives and Orbital information 4.a From to S/V Command startup messages (acquisition and Lock-on) Ranging signals and Other uplink Data 4. S/V- 4.b From S/V to RTC Command verification and S/V status and SOH Ranging signal return and Other telemetry data or data 5.a From SOC to S/V Command sequences and command uploads 5. S/V-SOC Other Uplink data (via ) 5.b From S/V to SOC Telemetry Other data Legends: A = Automated SOH = State of Health 13