ICD-CS-605_Rev_B.doc

PREPARED BY

Deborah A. Barchichat

APPROVALS

ENGINEERING

SEIT IPT – Harry Brown

AUTHORITY

WBS 413

CS IPT – Ardell Nease

5/27/2008

TOTAL PAGES

SUBJECT: CHANGE/RELEASE

PSDR/NR

EFFECT ON RELEASE TO FILES

INTERFACE CONTROL DOCUMENT

FOR THE

GPS BLOCK IIF SATELLITE TELECOMMUNICATIONS SIMULATOR (STS)

CONTRACT NO. F04701-96-C-0025

Prepared for:

U.S. AIR FORCE

HEADQUARTERS SPACE & MISSILE SYSTEMS CENTER

LOS ANGELES, CA 90009-2960

Prepared by:

THE BOEING COMPANY

SPACE & INTELLIGENCE SYSTEMS

2201 SEAL BEACH BLVD

SEAL BEACH, CA 90740

Distribution D. Distribution authorized to DOD and US DOD contractors only. (Reason: Administrative or Operational Use) (Date of Determination: 28 September 1995). Other requests for this document shall be referred to NAVSTAR Global Positioning System Joint Program Office ( SMC/CZ).

WARNING: This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C. 2571 et seq.) or Executive Order 12470. Violation of these export control laws is subject to severe criminal penalties. Dissemination of this document is controlled under DOD directive 5230.25 and AFI 61-204. Include this notice with any reproduced part of this document.

DESTRUCTION NOTICE: For classified documents, follow DOD 5220.22M, National Industrial Security Program Operating Manual. For unclassified limited documents, destroy by any method that will prevent disclosure of the contents or reconstruction of the document.

This Document contains information

EXEPT FROM MANDATORY DISCLOSURE

UNDER THE FOIA

EXEMPTIONS (b)(4) and (b)(5) apply

Document Revision & Version History

TABLE OF CONTENTS:

11.0 SCOPE

32.0 APPLICABLE DOCUMENTS

32.1 Government Documents

42.2 Non-Government Documents

53.0 INTERFACE REQUIREMENTS

53.1 STS and STS Support Systems Overview

63.1.1 STS Functionality

73.1.2 Operating Modes

73.2 Control Segment Overview

73.2.1 OCS Overview

93.2.2 LADO Overview

103.3 Interface Definition

103.3.1 Interface Identification

113.3.1.1 STS/Operational Control System (OCS)

133.3.1.2 STS/LADO via EVCF/AFSCN

143.3.1.3 STS/NAVSTAR Processing Facility (NPF)

143.3.1.4 STS Facility and Power

163.3.1.4.1 Voice Communications

163.3.1.4.2 Modem Data Communication

173.3.2 Interface Characteristics

173.3.2.1 Signal Characteristics for GPS CCAFS Links for IIF STS

193.3.2.2 Engineering Development Units (EDUs) Interface

203.4 Functional Interfaces

213.4.1 TT&C Interfaces

213.4.1.1 Telemetry Services

213.4.1.2 SGLS Pseudo Random Noise (PRN) Ranging Services

213.4.1.3 Uplink Command Services

213.4.1.4 Communications Security (COMSEC) Equipment

213.4.1.5 TT&C Performance

213.4.2 Navigation Services and Simulator Navigation Performance

223.4.3 NDS Service

223.4.4 Crosslink UHF Services

234.0 RESERVED

235.0 NOTES

235.1 RF Characteristics

245.1.1 RF Power

245.1.2 Frequency Plan (L-Band, UHF and S-Band)

275.1.2.1 STS RFIS Transmit Signal Levels

285.1.3 RF Transmission Cables

285.1.4 RF Connector Panel RF Connectors

285.2 Simulator Specific Support Equipment Performance

285.2.1 Local Area Network (LAN)

285.2.2 Workstations, Disk Storage, Printer, and Related Commercial Off-The-Shelf Software

295.2.3 Attitude Determination & Control Subsystem (ADCS) Simulation Software

295.2.4 STS System Displays/Control

295.2.5 Tolerance and Limits

295.2.6 Editing Capabilities

295.2.7 Page Printout and Plotting Capabilities.

295.2.8 Display Conversions

305.2.9 Data Archival Functions and Miscellaneous Archival Capabilities

305.2.10 Post-Processing Capabilities

316.0 ABBREVIATIONS AND ACRONYMS

1Appendix A: STS Shelf and Panel Assembly Drawings A-

1Appendix B: Simulator Command and Measurement List (CML) Reference Data B-

List of Figures:

2Figure 1-1 STS to CS Functional Interfaces

6Figure 3-1 Satellite Telecommunications Simulator (STS) Elements

8Figure 3-3 Telecommunications Simulator Test Station (TSTS) Elements

11Figure 3-4 TSTS Connectivity Interface Diagram

12Figure 3-5 GPS TSTS Links for IIF SV and STS

14Figure 3-6 Development GPS and AFSCN Interfaces

15Figure 3-7 Shelter “C” and the physical layouts of the STS and Supporting Consoles

23Figure 5-1 - RFIS Subsystems

25Figure 5-2 - RFIS S Band Signal Distribution

26Figure 5-3 - RFIS L-Band Signal Distribution

27Figure 5-4 - RFIS UHF-Band Signal Distribution

2Drawing 1: Shelf Assembly-GPS IIF STS L-Band RF

3Drawing 2: Shelf Assembly-GPS IIF STS L-Band RF A-

4Drawing 3: Shelf Assembly-GPS IIF STS L-Band RF A-

5Drawing 4: Shelf Assembly-GPS IIF STS L-Band RF A-

6Drawing 5: Shelf Assembly-GPS IIF STS L-Band RF A-

7Drawing 6: Shelf Assembly-GPS IIF STS S-Band RF A-

8Drawing 7: Shelf Assembly-GPS IIF STS S-Band RF A-

9Drawing 8: Shelf Assembly-GPS IIF STS S-Band RF A-

10Drawing 9: Shelf Assembly-GPS IIF STS S-Band RF A-

11Drawing 10: Shelf Assembly-GPS IIF STS S-Band RF A-

12Drawing 11: Panel Assembly-GPS IIF STS 3 Bay RF I/O A-

13Drawing 12: Panel Assembly-GPS IIF STS 3 Bay RF I/O

List of Tables:

16Table 3-1 – Simulator Facility Characteristics

18Table 3-2 - Signal Interface Characteristics for GPS IIF STS

19Table 3-3 - Satellite Telecommunications Simulator (STS) Box Redundancy

24Table 5-1 - STS Transmission Levels and Frequency at the RFIS

28Table 5-2 – RFIS Input Signal Levels

1.0 SCOPE

This Interface Control Document (ICD) establishes the specific technical characteristics for the interfaces between the GPS Block IIF Satellite Telecommunications Simulator (STS) and the Global Positioning System (GPS) Control Segment (CS). The ICD contains specific information on the connectivity within Shelters B and C in the Telecommunications Simulator Test Station (TSTS) facility. The interface between the STS Special Test Equipment (STE) and the STS remote terminal (STSRT) is also defined.

The STS is a part of the GPS support equipment whose function is to allow the GPS Control Segment (CS) to validate the telemetry, command, user and upload protocol interfaces with the GPS Block IIF SV. The STS interfaces with the CS through the Ground Antenna (GA) and/or the Ground Antenna Test Set (GATS) and Monitor Station (MS) and/or the Monitor Station Test Simulator (MSTS) at CCAFS. The STS interfaces with LADO through the EVCF (Eastern Vehicle Checkout Facility) as well. STS operators at CCAFS interface with the STS using 5 workstations which are co-located with the STS in Shelter C. An STS operator at a remote facility can interface with the STS via a Remote Terminal (STSRT); the location of this STSRT is presently in the shelter "C" control room. STS generated signals can be switched to the local OCS/GATS/GA site, local OCS/MSTS/MS site, GPS User Equipment, NAVSTAR Processing Facility (NPF), and Defense Satellite Communication System (DSCS) Processing Facility (DPF) by using the Radio Frequency Interface Subsystem (RFIS) in Shelter B.

The simulator is functionally identical to the Space Vehicle Navigation Payload (NPL) and L-Band Subsystem (LBS) and Telemetry, Tracking, and Command (TT&C) Subsystems, except that:

(1) The Simulator doesn’t carry the L-Band Subsystem high power amplifiers or helix antenna;

(2) The Simulator doesn’t carry the TT&C antennas;

(3) The Simulator doesn’t provide for full NPL and TT&C redundancy.

(4) The STS Command and Measurement List (CML) is functionally equivalent to that which is provided to the Space Vehicles (SVs) with some minor differences.

The Simulator operates identically to the SV in terms of navigation upload reception and downlink signal data transmission, format, and TT&C command reception and downlink.

Figure 1-1 depicts the SV Simulators (STS, MTS, and TSM) Interfaces to the other elements of the Control Segment. All three SV simulators interface thru the RF Interface Subsystem (RFIS) to the Control Segment Elements (OCS and LADO). The interfaces defined for each of the SVs is also defined by its applicable ICD, as shown in the figure.

In addition to the S-band, L-band, and UHF RF signals, the STS also provides local test direct interfaces to the NPF Ground Support Equipment which includes the L-Band Test Set/Modernization Space Vehicle L-Band Test Set (MSVLBTS), S-band Test Set, Crosslink Test Set (XLTS), and the Burst Detector Augmentation Automated Tester (BAT) located in the NPF. The RFIS provides the interface from the STS to the OCS and LADO (via the EVCF).

Figure 1-1 STS to CS Functional Interfaces

In addition, Figure 1-1 identifies other characteristics/activities at the interfaces as follows::

· EVCF is not physically part of the OCS

· LADO connectivity via EVCF

· The OCS to Satellite Simulator interface occurs at the RFIS

· Signal Characteristics to GATS 1 and 2, MSTS 1 and 2

· The ICD document number for each simulator interface

· The TSTS is shown to be a functional part of the OCS because the GATS and MSTS subsystem contain SW and HW that is functionally identical to the OCS Cape GA and Cape MS. However, the TSTS is operated and maintained under contract to the GPS GPSW SMC/GPG. The STS, MTS, and TSM physically reside at the CCAFS within the Telecommunications Simulator Test Station facility, Shelters C & D (see Figure 3-3).

2.0 APPLICABLE DOCUMENTS

2.1 Government Documents

The following documents of the exact issue shown form a part of this document to extent specified herein. The effective version of the Interface Requirements Specifications (IRSs), Interface Control Documents (ICDs) and other specifications/documents to be invoked (as specified herein) shall be the “GPS Block IIF contractual baseline version”.

Safety/Regulations

Eastern and Western Range 127-1 Range Safety Requirements, 31 October 1997, and Changes 1 & 2, 31 December 1999.

Interface Control Documents ICD-GPS-200 Navstar GPS Space Segment/Navigation User Interfaces

ICD-GPS-203 (S) Navstar GPS Selective Availability and Anti-Spoofing Requirements (SECRET)

ICD-GPS-206 (S) Navstar GPS Space Segment/NDS User Segment Interfaces (SECRET) ICD-GPS-210 Navstar GPS/Air Force Satellite Control Network (AFSCN) Interfaces ICD-GPS-637 Navstar GPS Space Vehicle (II/IIA)/Space Vehicle (IIR)/Space Vehicle (IIF)

ICD-GPS-620 Navstar GPS IIF Space Vehicle/Nudet Detection System Interface and Classified Appendix A ICD-GPS-601 Navstar GPS Block IIF Space to Control Segment Interfaces ICD-GPS-700 Navstar GPS Military-Unique Space Segment/User Segment Interfaces

ICD-GPS-703 (S) Navstar GPS Military-Unique Space Segment/User Segment Classified Interface (SECRET) IS-GPS-705 GPS Space Segment/User Segment L5 Interfaces Telecommunications Simulator Test Station (TSTS) Satellite Telecommunications Simulator (STS) to Shelter C Interface Agreement, Rev B, 06 Mar 2003 - The Charles Stark Draper Laboratory IRS-GPS-SS/OU-02 Space to NDS User (IRS 02) and Classified Appendix A

Specifications Telecommunications Simulator Test Station (TSTS) Interface Specification (IS-TSTS-530), Rev H, Dated: 30 Mar 2004, -The Charles Stark Draper Laboratory AFSCN SIS-000502D-Range Segment and Space Vehicles (AFSCN )

AFSCN SIS-000503A-CCS (Command and Control Segment) to the AFSCN.

AFSCN SIS-000508E-Range/Communication Segment and Command and Control Center (CCC) AFSCN SIS-000509D-Standardized Interface Specification between AFSCN Resource Management Segment (RMS) and Command Control Centers.

Other Government Documents COMSEC Equipment NSA Communications Security Equipment Documentation (CSED):

Compromising Emanations Standard for Cryptographic Equipment - KG-30A/TSEC

January 1971 Functional Security Requirements Specification (FSRS) for Block IIF U/L, CARDHOLDER Device, CARDHOLDER FSRS, 1 September 1995 Functional Security Requirements Specification (FSRS) for Block IIF D/L, PEGASUS (KGV-227) Device, PEGASUS FSRS, 1 September 1995 Telecommunications Security Requirements Document (TSRD) for the Embedment of the CARDHOLDER and PEGASUS Cryptographic Chips into the Navstar Block IIF Satellite, Navstar TSRD, 25 October 1995 Communications Security Equipment System Document for the SYS-U-KI-17 Program: Appendix A, KI-17 PEGASUS CP CARD Appendix B, KI-17 Cardholder Cryptographic Algorithm ICD, K KI-17-CSESD SYS-U-R10, 9 Nov 2000

2.2 Non-Government Documents

Specifications

Boeing GPS IIF Satellite Telecommunications Simulator (STS) Configuration Item Specification- MF-0006-102, 12/03/03 Version 5.2.2 -SS-OCS-611-V5.2.2, Rev A, Prime Item Specification for the Operational Control System GPS Block IIF System of the Navstar Global Positioning System, 5 February 2007 23009395 GPS Block IIF STS Users Guide CDRL-029A5 Block IIF Orbital Operations Handbook (OOH) SS-LADO-612 Rev E (LADO Element Specification), 6 April 2007

3.0 INTERFACE REQUIREMENTS

The STS interfaces with the following elements of the GPS control segment via the TSTS: OCS/MCS and LADO. The STS also has a direct fiber interface to NPF, which is not part of the Control Segment, to utilize the IIF test sets in the NPF in support of special test and troubleshooting efforts. The following sections discuss the detailed interface between the STS and each of these elements. Connectivity between the STS and these elements is established within the TSTS by the RF Interface Subsystem (RFIS) and TSTS Communications Box. Additional Connectivity is also provided by the Red Shelter Communications Box within the OCS GA/MS site. From these communication boxes, connections are made to the EVCF/LADO, MCS, and the NPF.

3.1 STS and STS Support Systems Overview

The STS is a part of the GPS support equipment whose function is to allow the GPS Control Segment (CS) to validate the telemetry, command, user and upload protocol interfaces with the GPS Block IIF SV. Before discussing the STE Interface, a description of the STS, itself, may be useful. The STS support systems include the 3-bay console and related workstations, internal VME chassis and related VME processors and I/O boards, GSE power sources, related System Interconnect Panels (SIP), test sets, and all cabling to and from the 3 bay console to the STS fixture. See Appendix A for reference drawings. The workstations, Simulation LAN, disk storage/printer, related SV0 COTS software, ADCS simulation software, and the related Data Display PC stations/software are the same as the IIF SV0 design. All software is a reuse of the SV0 development activities. A 3-Bay console is delivered as part of the STS. The STS 3-Bay console includes 2 COTS VME chassis, one for the vehicle simulation and one for the ground simulation. The VME simulation chassis houses the real time simulation processor and I/O ground support boards. The ground simulation chassis houses the S-Band antenna functionality and contains a Microdyne Receiver (MR) and Hewlett Packard Signal Generator (SG) for facilitating test verification of the S-Band uplink and downlink processes. (The MR and SG is a non deliverable item.) The SIP contains connection terminal blocks giving test point access to all signals that are shared between the Vehicle/STS fixture and the 3-bay. One connection terminal block connects to each Space Vehicle connector that directly interfaces with the 3-bay. One connection terminal block connects to each 3-bay connector that directly interfaces with the Vehicle. Each connection terminal block gives access to test points for all signals contained within that block. Each interconnect block can be verified per the related detail wire list. The SIP also contains load banks and rails for the simulation of the various sensor/effectors.

a. The Satellite Telecommunication Simulator Remote Terminal (STSRT) interfaces with the STS via the STE for “housekeeping” functions and SCP/NDU fast program loads.

b. The remote PC encryption devices, and communication line are GFE hardware used to provide secure communication to the STS via the STSRT.

c. The STE is compatible with the GFE encryption device and communication line that will be used to send and receive serial data to the STS Remote Terminal (STSRT).

d. The STE is capable of receiving and sending data to the STSRT. The STS Users Guide contains a complete list and definition of STE file types and formats.

e. The STE contains a printer to support maintenance and equipment repair.

f. The STE contains a computer system (STS Controller) that controls the functions outlined in a. through e.

STS generated navigation signals are provided to User Equipment (UE) of the GPS User Segment (US). Figure 3-1 is a Block Diagram of the STS Simulator Elements.

Figure 3-1 Satellite Telecommunications Simulator (STS) Elements The STS usage includes (but will not be limited to):

1. Telemetry, Tracking, and Command (TT&C) compatibility

a. Transmission to and reception by the STS of commands and data uploads. This includes uploads to the navigation system processor (the Navigation Data Unit [NDU]) and the SV bus processor (the Spacecraft Control Processor [SCP]).

b. Telemetry data from the STS, including NDU and SCP processor memory dumps, is transmitted to, and received by, elements of the CS.

2. Navigation payload (L1, L2) transmission compatibility.

3. Global Burst Detector (GBD) payload (L3) compatibility.

4. Cross link transmission capability.

5. Support SS/US (L5) compatibility

6. Support S-band capability

7. End-to-end system testing

8. Support on-orbit anomaly investigations.

3.1.1 STS Functionality

The STS provides an accurate representation of the GPS Block IIF SV TT&C and navigation payload (L-Band subsystems) interfaces. These interfaces are defined in ICD-GPS-601 Block IIF SS/CS (Space Segment to Control Segment Interfaces for the Navstar Global Positioning System [GPS] [Block IIF]), ICD-GPS-200 (Navstar GPS Space Segment/Navigation User Interfaces), ICD-GPS-203 (Navstar GPS Selective Availability and Anti-Spoofing Requirements) and ICD-GPS-637 (Navstar GPS Space Vehicle (II/IIA)/Space Vehicle (IIR)/Space Vehicle (IIF).

The STS contains a TT&C subsystem and a Navigation Payload System (NPS). The STS also contains GFE hardware to simulate the Global Burst Detector (GBD) system as the interface defined in ICD GPS-620.

The STS is being developed in accordance with the Boeing GPS IIF Satellite Telecommunications Simulator (STS) Configuration Item Specification (MF-0006-102).

3.1.2 Operating Modes

The STS operates in two different modes: local and remote, and utilizes a selectable electronic switchbox that determines its mode of operation. The “Local” mode of operation provides command, control and feedback for the STS utilizing one of the five workstations in Shelter C. The “Local” mode uses the local test/direct interfaces with the Spacecraft Processor (SCP), by-passing the transponder, allowing direct communications to and from the SCP via either Universal Asynchronous Receiver Transmitter (UART), MIL-STD-1553B, or directly into the transponder/SCP interface for configuring or troubleshooting the STS. The “Remote” mode of operation provides command, control and telemetry for the STS utilizing the CS, FSE, and GSE. The “Remote” mode uses the S-band/L-band telemetry via the RFIS-GA/MS interfaces for normal test or training communications with the STS.

3.2 Control Segment Overview

The Control Segment (CS) controls, communicates with, and monitors GPS space vehicles on-orbit and other GPS and external elements. The CS is composed of four elements: the Operational Control System (OCS), the Launch and early orbit, Anomaly resolution, and Disposal Operations (LADO) system; the Integrated Mission Operations Support Center (IMOSC); and the GPS IIF System Simulator. The STS does not interface with the System Simulator. The STS has the capability to send and receive* command and telemetry data when connected to the OCS or LADO (via EVCF). The IMOSC collects STS telemetry when the STS is connected to the NMCS. The IMOSC also collects STS telemetry when the STS is connected to LADO and the the STS telemetry is fanned-out to the IMOSC via Mod 3/4 (Note: The Mod 3/4 fanout is only necessary when LADO is conducting the contact - it is not needed for NMCS contacts).. *(The STS has the capability to capture and log its own telemetry for use in playback mode). The NPF shown in this ICD is shown for clarity - it is not part of the Control Segment.

3.2.1 OCS Overview

The Operational Control System (OCS) (See Figure 3-2) is an element of the Control Segment that supports the mission and objectives of the GPS Program. The OCS includes all ground facilities (Master Control Station (MCS), the Ground Antennas (GAs), and the dedicated OCS Monitor Stations (MSs) required to support satellite operations from the time the satellites are deployed by the Launch and early orbit, Anomaly resolution, and Disposal Operations (LADO) element until the end of their useful life, including pre-launch checkout. The OCS monitors, maintains, commands and controls the GPS satellite constellation. This includes monitoring the performance of the L-band navigation down links, updating the navigation message, monitoring the Space Vehicle (SV) State-of-Health (SOH), performing SV maintenance tasks, and providing any needed commanding of the NDS payload for the satellite constellation. The OCS includes remote Monitor Stations (MS) and Ground Antennas (GA). The OCS operations are performed primarily via a Master Control Station (MCS), Monitor Stations (MSs), and Ground Antennas (GAs). The NMCS, located at Schriever AFB (SAFB), Colorado, is operated and maintained 24 hours per day, seven days a week, and serves as the mission control center for GPS operations.

The TSTS provides a high-fidelity testing environment for new Space Vehicle (SV) compatibility testing with new OCS software releases prior to launch, connectivity for compatibility test of a production satellite prior to launch, as well as a testbed for GA and MS hardware upgrades. The test assets to accomplish these functions are housed in four contiguous shelters, collectively known as the TSTS, which are located at Cape Canaveral Air Force Station (CCAFS), Cape Canaveral, FL. The TSTS physical element architecture is depicted in Figure 3-3. Primary operations for the GPS Block IIF SV interface are conducted within Shelter C and are documented in this ICD-CS-605.

Figure 3-2 Operational Control System

Figure 3-3 Telecommunications Simulator Test Station (TSTS) Elements TSTS Shelter A houses a test asset for the GA function, known as Ground Antenna Test Set #1 (GATS1), a test asset for the MS function, known as Monitor Station Test Simulator #1 (MSTS1), and related support equipment. GATS1 and MSTS1 are functionally equivalent to the operational GAs and MSs, respectively. They utilize the same interfaces with the MCS and SVs as the operational GAs and MSs and use the same computer programs. The TSTS also has provisions to accommodate L-Band user equipment, consisting of an L3 receiver, L5 receivers, and multiple L1, L2 receivers.

TSTS Shelter B houses a second suite of test assets for the GA and MS functions, known as Ground Antenna Test Set #2 (GATS2) and Monitor Station Test Simulator #2 (MSTS2), the Radio Frequency Interface System (RFIS), the Auxiliary Antenna System (AAS), and related support equipment. GATS2 and MSTS2 systems are functionally equivalent to the operational GAs and MSs, respectively. They utilize the same interfaces with the MCS and SVs as the operational GAs and MSs and use the same computer programs. The RFIS controls the distribution of S-Band, L-Band, and UHF signals among the GPS test assets at CCAFS and controls the operation of the Antenna Transfer Switch (ATS). The Auxiliary Antenna Subsystem (AAS) contains a UHF-Band antenna and an L-Band antenna, both of which are mounted on the roof of Shelter B, for receiving UHF-Band downlink and L-Band navigation signals from on-orbit SVs.

TSTS Shelter C will house the Satellite Telecommunications Simulator (STS) for Block IIF SVs, and its related support equipment. While physically located within Shelter C, the STS is treated as an external entity and its interface to the TSTS is specified in the GPS IIF Satellite Telecommunications Simulator (STS) Configuration Item Specification, document number MF-0006-102, TSTS Interface Specification IS-TSTS-530.

There are 9 direct interfaces routed from the STS in Shelter C to the Interface in the NPF via fiber optics link.

TSTS Shelter D houses the Telecommunications Simulator (TSM) for Block IIA SVs, the Modernized Telecommunications Simulator (MTS) for Block IIR SVs. As with the STS, the TSM and the MTS are treated as external entities, and their interfaces to the TSTS is specified within their respective ICDs. The TSTS shelters are modular in construction and capable of expansion to house additional test assets, such as future GA/MS simulators or telecommunications simulators, as required.

TSTS Shelter E houses the S-Band Antenna High Power Amplifier (HPA) and Black Shelter Equipment Upgrade (BSEU) equipment racks (as depicted in Figure 3.3). The TSTS S-Band Antenna HPA only transmits into a dummy load. There is a suite of racks (four each – two HPA and two BSEU) that interface with both GATS1 and GATS2 test assets.

Although the satellite simulators are physically located within Shelters C and D, they are treated as external entities and their interfaces to the TSTS are specified in the TSTS Interface Specification, Document No. IS-TSTS-530.

The acquirer/owner of the TSTS asset is the Control Segment of The GPS Joint Program Office, SMC/GPG. The TSTS is managed by the Control Segment of the GPS GPSW, SMC/GPG. The TSTS is operated and maintained, under contract to SMC/GPG, by Boeing and supported by the Charles Stark Draper Laboratory, Inc.

3.2.2 LADO Overview

The Launch/early orbit, Anomaly resolution, and Disposal Operations (LADO) system is an element of the Navstar Global Positioning System (GPS) Control Segment (CS). The LADO system includes all ground facilities required to support satellite operations from the time the satellites are deployed using the Air Force Satellite Control Network (AFSCN) until the end of their useful life. LADO functions include launch/early orbit (L/EO), anomaly resolution, and disposal operations for all GPS SVs. LADO provides the capability and means to rapidly respond to constellation sustainment and individual satellite situations in order to mitigate impacts to OCS operations. The AFSCN interface is documented in ICD-GPS-210 Navstar GPS/Air Force Satellite Control Network (AFSCN) Interfaces. The document for the element specification for the LADO system and Boeing’s configuration item is SS-LADO-612.

LADO operations will be performed via a primary space operations center (SOC). The primary SOC, located at Schriever Air Force Base (SAFB) Colorado, will be operated and maintained 24 hours per day, seven days a week, and serves as the mission control center for GPS LADO operations. LADO will have access to the AFSCN ARTS for receiving SV telemetry, ARTS command, control, and status messages, and transmission of SV commands and SV memory image loads. Additional to the primary SOC is a backup SOC also located at SAFB. The backup SOC provides identical functionality and capabilities as the primary SOC. Operational data consistency between the two SOCs will be maintained.

LADO capabilities will compliment the OCS (NMCS and AMCS) capabilities and the following mission phases will be supported:

1. Launch and Early Orbit (L/EO). L/EO includes pre-launch, launch and insertion, transfer orbit and circularized orbit operations. Prior to launch, Compatibility and Pad testing through the Eastern Vehicle Checkout Facility (EVCF) is accomplished.

2. On-Orbit Operations. After completion of the L/EO major events sequence, the SV is transitioned to on-orbit operations. SV bus operations are conducted in parallel with payload operations, and include monitoring satellite bus performance, state of health and ensuring proper orbital position to meet mission requirements.

3. Anomaly Resolution. Anomaly resolution is the response to abnormal satellite health and status indications that could jeopardize the satellite and/or mission operations. Anomaly resolution includes contingency planning, detection, assessment, notification, analysis, corrective action planning and execution, and historical data archival.

4. Disposal Operations. At the end of the satellites useful mission life, it is taken out of the operational constellation and maneuvered to an altitude above the operational constellation.

3.3 Interface Definition

The Simulator is used for compatibility testing of SV communications equipment with Operational Control System (OCS) and the Air Force Satellite Control Network (AFSCN). The OCS interfaces with the STS through the Ground Antenna (GA) and Monitor Station (MS) via the RFIS. The AFSCN has an Eastern Vehicle Checkout Facility (EVCF), which can be accessed by LADO via the RFIS. These facilities are located at the Eastern Launch Site (ELS) at Cape Canaveral Air Force Station (CCAFS), Florida.

The OCS is responsible for S-Band primary upload of the Simulator NDU processor. In addition, the OCS/MS monitors the Simulator L-Band transmissions for upload verification and Simulator telemetry monitoring.

3.3.1 Interface Identification

The STS has RF interfaces with the RFIS and the related MS/MSTS and GA/GATS via RF hardline, and does not radiate or receive RF signals via antennas. Additional connectivity provided by the TSTS and Red Shelter communication boxes to the OCS/GA/MS site, the NPF, and EVCF are shown in Figure 3-4.

Figure 3-4 TSTS Connectivity Interface Diagram

The STS, MTS, and TSM physically reside at the CCAFS within the Telecommunications Simulator Test Station facility, Shelters C & D. The EVCF/ARTS is both an AFSCN operational asset, as well as a test asset. The Cape GA is both an OCS operational asset, as well as a test asset. The configuration depicted in Figure 3-4 shows the connectivity from the TSTS facility, in particular the STS within it, through the GA or EVCF as an STS test configuration only.

3.3.1.1 STS/Operational Control System (OCS)

The STS interfaces with the OCS through the Ground Antenna (GA/GATS) and Monitor Station (MS/MSTS) at CCAFS. Hard-line connectivity to the Monitor Station and to the Ground Antenna (GA) is established through the RFIS for L-Band and S-Band links. Hard-line connectivity will also be established through the RFIS for UHF links to other simulators or SVs (TSM/MTS/IIF SV in NPF or IIR SV in the DSCS Processing Facility (DPF).

Note: There are no airlinks planned for the simulator testing. The OCS uploads the Simulator NDU processor via GA S-Band SGLS compatible up- link received by the Simulator TT&C Subsystem. The format of the upload sequence is as defined in ICD-GPS-601 Block IIF SS/CS. The OCS commands the Monitor Station to acquire the Simulator L-Band transmissions and collect data as requested.

The Monitor Station receives the Simulator L-Band transmissions via hard-line, and processes these signals for subsequent transmissions of the data requested by the OCS. The MS interfaces with the OCS via GSE communications. The signal format of the L-Band transmissions is in accordance with ICD-GPS-601 Block IIF SS/CS.

The STS provides the ability to transmit via hard-line the equivalent modulated L-Band signals as defined in ICD-GPS-200, ICD-GPS-203, ICD-GPS-700, ICD-GPS-703, IS-GPS-705, and ICD-GPS-601 Block IIF SS/CS; except for L-Band output power levels. The signal formats of the L-Band transmission are in accordance with ICD-GPS-200. The telemetry and command formats words are in accordance with ICD-GPS-601 Block IIF SS/CS.

Figure 3-5 provides a more detailed functional representation of the STS/SV TSTS circuits, along with the connectivity between the TSTS facility and the NPF. The RF interfaces also connect through S-band, L-Band, and UHF to the NAVSTAR Processing Facility (NPF) via the NPF communications box.

Note: The NPF shown in Figure 3-5 is shown for clarity - it is not part of the Control Segment.

Figure 3-5 GPS TSTS Links for IIF SV and STS Assumptions:

5. Encryption/decryption devices required will be supplied by the government (GFE), assuming all S-Band data from the STS is protected by encryption/decryption devices (Transponders/KI-17s) and is unclassified

6. All RFIS I/O impedances are 50 ohms.

7. Spares requirements for the fiber lines will be determined by the range at the Cape

8. The RFIS will support switching required to share the planned S-Band and UHF lines (TSTS to NPF) between the STS and the IIF SV

9. Fiber lines, transmitters, receivers, and communication interface will be GFE for all lines between the TSTS and NPF

10. Boeing will be responsible to design and install switching/interfaces required for assets inside the NPF under the IIF effort. This will not include the interface rack in the communications room

11. All RF and TTL signals will use N-Type connectors, and the RS422 signals will use DB-25 connectors at the Simulator room I/O panel in shelter C.

3.3.1.2 STS/LADO via EVCF/AFSCN

LADO will interface with the STS via the Air Force Satellite Communications Network (AFSCN) communication path to the Eastern Vehicle Checkout Facility (EVCF). The EVCF is one of many Automated Remote Tracking Stations (ARTS) and is accessed by LADO in a fashion similar to the other operational ARTS sites. The AFSCN CCS is to be decommissioned for operations and all AFSCN users that require AFSCN launch resources need to provide their own command and control (C&C) functions. Upon decommissioning of the CCS, the AFSCN C&C functions for the GPS program will be accomplished by the LADO system. The AFSCN interfaces are documented in ICD-GPS-210 Navstar GPS/Air Force Satellite Control Network (AFSCN) Interface Document.

Functionally, the AFSCN is divided into four Segments: the Range Segment (RS), the Communications Segment (CS), the Resource Management Segment (RMS), and the Command and Control Segment (CCS). The RS includes antennas, the Control and Status (C&S) processor, and Telemetry, Tracking, and Command (TT&C) at the Automated Remote Tracking Stations (ARTS). The AFSCN RS processor receives down linked unprocessed telemetry and tracking data. The AFSCN RS transmits and receives data via the AFSCN CCS. Current AFSCN documentation defines interfaces between the AFSCN Command and Control Segment (CCS) and the ARTS equipment. The AFSCN Standardized Interface Specification (SIS) documents and defines the interface between the AFSCN and its external users. The interface between the Range Segment and Space Vehicles is documented in AFSCN SIS-000502D. This SIS defines the interfaces between the AFSCN ground antennas at the Remote Ground Facilities (RGFs) and the SV including the GPS satellites. This SIS contains all of the signal characteristics of all services on the S-Band link between the SV and the ground antenna, including detailed information about the applicable RGFs and quantities that are necessary for link budget calculations.

The AFSCN CS provides communication services between the CCC and the RS. The AFSCN CS distributes information such as SV telemetry, voice, and timing, and exists within and between all AFSCN sites. The AFSCN Range/Communication Segment and Command and Control Center (CCC) CS interface is documented in AFSCN SIS-000508E. This SIS encompasses the logical and physical interfaces between the Range Segment (RS) and the Communication Segment (CS), and the Command and Control Centers (CCCs) such as LADO. More specifically, this SIS addresses the commands that the CCCs send to SVs and the telemetry that the SVs relay back to the users/CCCs.

The RMS provides a Command and Control Center (CCC) an avenue to schedule and coordinate AFSCN CUE resource support. SIS-000509D is the Standardized Interface Specification between AFSCN Resource Management Segment (RMS) and Command Control Centers. This SIS documents user interfaces to Resource Management Segment (RMS) systems and functions. The RMS manages and allocates AFSCN resources to meet the needs of its users.

The CCS provides the Command and Control features to the AFSCN. This interface is documented in AFSCN SIS-000503A. Figure 3-6 describes the relationships between the AFSCN interfaces and the GPS vehicles.

Under the Block IIF contract, the GPS CS is transitioning to a distributed architecture consisting of the AEP OCS and the new LADO system (AFSCN CCS replacement), both of which have interfaces to the satellite support facilities [“legacy” Block IIR/IIR-M Operational Support

System (OSS) and new Block II/IIA/IIF Integrated Mission Operations Support Center

(IMOSC)].

SIS-000503

*Note: CCS is to be replaced by LADO Figure 3-6 Development GPS and AFSCN Interfaces

3.3.1.3 STS/NAVSTAR Processing Facility (NPF)

· In addition to the S-band, L-band, and UHF RF signals, the STS also has direct interfaces to the NPF Ground Support Equipment which includes the Modernization Space Vehicle L-Band Test Set (MSVLBTS), S-band Test Set, Crosslink Test Set (XLTS), and the Burst Detector Augmentation Automated Tester (BAT) located in the NPF.

These direct interfaces are routed from the STS in Shelter C to the NPF communications room via the NPF fiber optics link. To support the direct (Does not go thru the RFIS) fiber optics link between the NPF and the STS/Shelter C, there exists a COTS fiber optics interface box housing the transmitters and receivers at the NPF, commonly called the "Communications" closet. In a rack at Shelter C, there exist the corresponding receivers and transmitters to complete the STS direct fiber optics link. The NPF is a GFE facility. Currently there are no plans to connect the BAT interface, although, that interface is available for future use.

3.3.1.4 STS Facility and Power

This Section of the document addresses various characteristics of the facility, including location and power. The designated facility for the STS is the Telecommunications Simulator Test Station (TSTS), Shelter C at CCAFS as shown in Figure 3-7. This facility provides housing, communications, environmental control, security, and electrical power for the STS operation. The TSTS Shelter C facility interfaces with the Simulator, by providing the physical environment, communications, and electrical power for its operation.

Figure 3-7 Shelter “C” and the physical layouts of the STS and Supporting Consoles The STS electrical power interface is in accordance with Table 3-1.

Table 3-1 – Simulator Facility Characteristics

The Shelter C simulator room will provide a minimum of -70 dB attenuation to S, L and UHF frequencies typically used by the GPS SVs.

The equipment will be located in the Shelter C simulator room. The Shelter C simulator room will provide a minimum of -70 dB attenuation to S, L and UHF frequencies typically used by the GPS SVs.

The placement of the equipment within this room will allow the rear doors on the cabinets to be opened without moving the equipment.

1 workstation and 3 PCs in the Monitor Room.

Printer – Located on the workstation table in the monitor room. (Provided by Boeing)

208 VAC, Two Phase, 30 amp. The STS 3-Bay will be provided with a power cord terminated in a L6-30P style plug. Shelter C will provide the required power via a mating socket.

Red Power.

Red or Black power. 208 VAC single phase, 10 amps peak. The Chiller power cord will be terminated in a Hubbell 3331-CG plug provided by Boeing. Shelter C will provide the required power via a mating socket.

115 VAC Red power will connect to Shelter “C” for PCs, workstations and printers.

Printer – Not to exceed 100 lbs

The length of the STS fixture will not exceed 125 inches.

The width of the STS fixture will not exceed 78 inches.

Three standard 19 inch racks placed side-by-side.

The STS 3Bay will be designed such that it can be moved into and between the TSTS Shelter C rooms via a doorway which is 81 inches wide by 82 inches tall.

Printer – Approximately 24 inches wide, 24 inches high, and 24 inches deep.

45 to 75% RH 15 to 35 Deg C

45 to 75% RH 15 to 35 Deg C

45 to 75% RH 15 to 35 Deg C

45 to 75% RH

3.3.1.4.1 Voice Communications

The government provides (GFE) a secure communication line [via a local area network (LAN)] for a local STS operator to coordinate his operations with the MCS, as well as the capability to communicate with the STS facility room and the external computer room. Note: The Simulator itself has no voice communication capabilities. Intercommunication is provided by the facility where the Simulator is used.

3.3.1.4.2 Modem Data Communication

The government provides (GFE) a communications line to the STS [via a LAN].

3.3.2 Interface Characteristics

The STS interfaces with the CS for functional operation of the GPS Block IIF bus and payload through the following interfaces:

· S-Band interface provides the capability for the CS to transmit commands and uploads to the STS via hardline and receive GPS Block IIF telemetry from the STS via RF hardline through the GA/GATS or AFSCN (EVCF) interfaces.

· L-Band interface provides the capability for the CS to receive L-Band navigation data via the MS/MSTS. Connectivity will be available to connect additional L-Band receivers via hard-line to verify navigation data, L3 (GBD) data, and L5 signals.

· STSRT interface provides the capability to access the STE to transfer program loads to the SCP/NDU and change simulated data.

· The UHF interface provides a path to transmit/receive CTDU data formats through the RFIS to other simulators or SVs.

· The GA/GATS will uplink the commands and the NDU data uploads to the STS as defined in ICD-GPS-601 Block IIF SS/CS and in Boeing Specification MF0006-102: GPS IIF STS.

· The STS, supported by the EDUs (Engineering Development Units), responds to uplinked commands and data uploads by updating the status telemetry for those commands. Telemetry is downlinked to the GA/GATS or AFSCN (EVCF) via S-band. Telemetry values for non-resident hardware are simulated as static values.

3.3.2.1 Signal Characteristics for GPS CCAFS Links for IIF STS The signal characteristics for STS direct interface to NPF, S Band, L Band and UHF interface to RFIS, and STS internal to TSTS signals are as referenced in Table 3-2. These signals correlate to those STS signals depicted in Figure 3-5.

Table 3-2 - Signal Interface Characteristics for GPS IIF STS

Red*

Transmitter power = 0.6 Watts Black

STS Remote Terminal (STSRT) (Internal to TSTS complex)

Red

* Note – Provisions will be made to guarantee the security classification during test – Outside plant fiber links are authorized for unclassified transmission only. There are no current plans to connect the BAT interface signals. These are reserved for possible future use.

The direct signals included in Table 3-2 are in addition to IIF SV and STS RFIS requirements for S-Band, L-Band, and UHF Crosslink and would be directly available to the NPF for use with the LBTS, XLTS, and BAT, but would not necessarily be available to facilities other than the NPF. (Reference Figure 3-5) The STS provides the S-band and L-Band navigation signals to the RFIS via RF hardline. The navigation signals comply with the requirements of ICD-GPS-200 (navigation), ICD-GPS- 700 (Military User Navigation), ICD-GPS-203 (anti-spoofing and selective availability), and ICD-GPS-703 (Military Unique Space Segment to User Segment). The STS provides the L3 GBD data as defined in ICD-GPS-620 Navstar GPS IIF Space Vehicle/Nudet Detection System Interface and Classified Appendix A.

For UHF Interface, the STS provides a path via the RFIS and closed loop fiber links for CTDU message verification as defined in ICD-GPS-637 (GPS SV/SV (II/IIA/IIR/IIF).

3.3.2.2 Engineering Development Units (EDUs) Interface

The STS Engineering Development Units (EDUs) are mounted on an SV simulated structure. The STS EDUs are controlled by an EDU flight harness that represents the actual SV harness configuration. Table 3-3 indicates whether or not the units are redundant.

Table 3-3 - Satellite Telecommunications Simulator (STS) Box Redundancy

(Yes/No) Notes

In addition to these EDUs, the following sensors, effectors, and GFE units are simulated. Simulated Sensors and Effectors states/status are presented in the normal telemetry downlink (Power status (On/Off), rates, positions, etc.)

Sensors (All Redundancies Modeled)

Analog Sun Detectors (ASD)

Static Earth Sensor (STES)

Rate Gyro Package (RGP)

Effectors (All Redundancies Modeled)

Reaction Control System (RCS) and fuel tanks/mass properties

Reaction Wheel Assembly (RWA)

Electromagnetic Assemblies (EMA)

Solar Array Drive (SAD) and deployment mechanisms

Thermal Control Subsystem (TCS) – all temps set to nominal

Heaters and thermistors (One variable thermistor is available) use fixed resistive loads

Attitude Determination and Control Subsystem (ADCS) loads use fixed resistive

GFE

Burst Detector Augmentation (BDA) receive antenna deployment mechanisms

Burst Detector Processor (BDP) – PC based emulation if no GFE available

Radio Frequency Assembly (RFA)/Dipole Switch

3.4 Functional Interfaces

The STS will have the following functional interfaces: electrical interfaces, TSTS RFIS interfaces, local facility interfaces and power requirements. In addition, there will be a direct interface to the NPF SV test station and test sets. (Boeing Specification MF0006-102-GPS IIF STS). A PC will be hooked into the Local Area Network (LAN) to control and `provide a path for a 1553 data uplink. This communication line provides the capability to remotely uplink data without the MCS.

The STS Functional Interfaces are as follows:

a. TT&C (S-Band)

1. Command and data uploads and

2. Telemetry

3. SGLS PRN Ranging

b. Navigation services to support payload transmission tests GBD message formats and CTDU Data formats

c. SCP/NDU processor uploads (via S-Band or the STSRT); and

The STS may additionally be used for:

· Verification of uplink command and/or data load sequences prior to their transmission to operational SVs;

· Exercise of SV redundancy algorithms via alteration of static telemetry values; and

· Real-time exercise of auto navigation algorithms (with and without supporting ranging data).

3.4.1 TT&C Interfaces

3.4.1.1 Telemetry Services

The Simulator provides a SGLS downlink carrier capability in accordance with Boeing GPS IIF Satellite Telecommunications Simulator (STS) Configuration Item Specification- MF-0006-102, 12/03/03, and with ICD-GPS-601 Block IIF SS/CS.

The telemetry data includes simulated SV health and status information, actual NAV Payload/L-Band Subsystem/TT&C Subsystem status information, encryption Command decoder verification responses and SCP/NDU-processor upload verification responses.

3.4.1.2 SGLS Pseudo Random Noise (PRN)…