Ground segment
# Ground segment

A ground segment consists of all the ground-based elements of a space system used by operators and support personnel, as opposed to the space segment and user $segment.^{:1}$ The ground segment enables management of a spacecraft, and distribution of payload data and telemetry among interested parties on the ground. The primary elements of a ground segment are:

* Ground (or Earth) stations, which provide radio interfaces with $spacecraft^{:142}$
* Mission control (or operations) centers, from which spacecraft are $managed^{:20}$
* Remote terminals, used by support $personnel^{:142}$
* Spacecraft integration and test facilities
* Launch $facilities^{:21}$
* Ground networks, which allow for communication between the other ground $elements^{:142}$

These elements are present in nearly all space missions, whether commercial, military, or scientific. They may be located together or separated geographically, and they may be operated by different $parties.^{:25}$ Some elements may support multiple spacecraft $simultaneously.^{:480,481}$

## Elements

### Ground stations

Ground stations provide radio interfaces between the space and ground segments for telemetry, tracking, and command (TT&C), as well as payload data transmission and $reception.^{:4}$ Tracking networks, such as NASA's Near Earth Network and Space Network, handle communications with multiple spacecraft through $time-sharing.^{:22}$

Ground station equipment may be monitored and controlled remotely. There are often backup stations from which radio contact can be maintained if there is a problem at the primary ground station which renders it unable to operate, such as a natural disaster. Such contingencies are considered in a Continuity of Operations plan.

**Transmission and reception**

Signals to be uplinked to a spacecraft must first be extracted from ground network packets, encoded to baseband, and modulated, typically onto an intermediate frequency (IF) carrier, before being up-converted to the assigned radio frequency (RF) band. The RF signal is then amplified to high power and carried via waveguide to an antenna for transmission. In colder climates, electric heaters or hot air blowers may be necessary to prevent ice or snow buildup on the parabolic dish.

Received ("downlinked") signals are passed through a low-noise amplifier (often located in the antenna hub to minimize the distance the signal must travel) before being down-converted to IF; these two functions may be combined in a low-noise block downconverter. The IF signal is then demodulated, and the data stream extracted via bit and frame synchronization and decoding. Data errors, such as those caused by signal degradation, are identified and corrected where possible. The extracted data stream is then packetized or saved to files for transmission on ground networks. Ground stations may temporarily store received telemetry for later playback to control centers, often when ground network bandwidth is not sufficient to allow real-time transmission of all received telemetry.

A single spacecraft may make use of multiple RF bands for different telemetry, command, and payload data streams, depending on bandwidth and other requirements.

**Passes**

The timing of passes, when a line of sight exists to the spacecraft, is determined by the location of ground stations, and by the characteristics of the spacecraft orbit or trajectory. The Space Network uses geostationary relay satellites to extend pass opportunities over the horizon.

**Tracking and ranging**

Ground stations must track spacecraft in order to point their antennas properly, and must account for Doppler shifting of RF frequencies due to the motion of the spacecraft. Ground stations may also perform automated ranging; ranging tones may be multiplexed with command and telemetry signals. Ground station tracking and ranging data are passed to the control center along with spacecraft telemetry, where they are often used in orbit determination.

### Mission control centers

Mission control centers process, analyze, and distribute spacecraft telemetry, and issue commands, data uploads, and software updates to spacecraft. For crewed spacecraft, mission control manages voice and video communications with the crew. Control centers may also be responsible for configuration management and data $archival.^{:483}$ As with ground stations, there are often backup control facilities available to support continuity of operations.

**Telemetry processing**

Control centers use telemetry to determine the status of a spacecraft and its $systems.^{:485}$ Housekeeping, diagnostic, science, and other types of telemetry may be carried on separate virtual channels. Flight control software performs the initial processing of received telemetry, including:

* Separation and distribution of virtual $channels^{:393}$
* Time-ordering and gap-checking of received frames (gaps may be filled by commanding a retransmission)
* Decommutation of parameter values, and association of these values with parameter names called mnemonics
* Conversion of raw data to calibrated (engineering) values, and calculation of derived $parameters^{:483}$
* Limit and constraint checking (which may generate alert $notifications)^{:479}^{:484}$
* Generation of telemetry displays, which may be take the form of tables, plots of parameters against each other or over time, or synoptic displays (sometimes called mimics) – essentially flow diagrams that present component or subsystem interfaces and their $state.^{:484}$

A spacecraft database provided by the spacecraft manufacturer is called on to provide information on telemetry frame formatting, the positions and frequencies of parameters within frames, and their associated mnemonics, calibrations, and soft and hard $limits.^{:486}$ The contents of this database—especially calibrations and limits—may be updated periodically to maintain consistency with onboard software and operating procedures; these can change during the life of a mission in response to upgrades, hardware degradation in the space environment, and changes to mission $parameters.^{:399}$

**Commanding**

Commands sent to spacecraft are formatted according to the spacecraft database, and are validated against the database before being transmitted via a ground station. Commands may be issued manually in real time, or they may be part of automated or semi-automated procedures uploaded in their $entirety.^{:485}$ Typically, commands successfully received by the spacecraft are acknowledged in $telemetry,^{:485}$ and a command counter is maintained on the spacecraft and at the ground to ensure synchronization. In certain cases, closed-loop control may be performed. Commanded activities may pertain directly to mission objectives, or they may be part of housekeeping. Commands (and telemetry) may be encrypted to prevent unauthorized access to the spacecraft or its data.

Spacecraft procedures are generally developed and tested against a spacecraft simulator prior to use with the actual $spacecraft.^{:488}$

**Analysis and support**

Mission control centers may rely on "offline" (i.e., non-real-time) data processing subsystems to handle analytical $tasks^{:21}^{:487}$ such as:

* Orbit determination and maneuver planning
* Conjunction assessment and collision avoidance $planning^{:478–479}$
* Mission planning and $scheduling^{:489–491}$
* On-board memory $management^{:247–249}$
* Short- and long-term trend $analysis^{:21}$
* Path planning, in the case of planetary rovers

Dedicated physical spaces may be provided in the control center for certain mission support roles, such as flight dynamics and network $control,^{:475}$ or these roles may be handled via remote terminals outside the control center. As on-board computing power and flight software complexity have increased, there is a trend toward performing more automated data processing on board the $spacecraft.^{:2–3}$

**Staffing**

Control centers may be continuously or regularly staffed by flight controllers. Staffing is typically greatest during the early phases of a $mission,^{:21}$ and during critical procedures and periods, such as when a spacecraft is in eclipse and unable to generate power. Increasingly commonly, control centers for uncrewed spacecraft may be set up for "lights-out" (or automated) operation, as a means of controlling costs. Flight control software will typically generate notifications of significant events – both planned and unplanned – in the ground or space segment that may require operator intervention.

### Remote terminals

Remote terminals are interfaces on ground networks, separate from the mission control center, which may be accessed by payload controllers, telemetry analysts, instrument and science teams, and support personnel, such as system administrators and software development teams. They may be receive-only, or they may transmit data to the ground network.

Terminals used by service customers, including ISPs and end users, are collectively called the "user segment", and are typically distinguished from the ground segment. User terminals including satellite television systems and satellite phones communicate directly with spacecraft, while other types of user terminals rely on the ground segment for data receipt, transmission, and processing.

### Integration and test facilities

Space vehicles and their interfaces are assembled and tested at integration and test (I&T) facilities. Mission-specific I&T provides an opportunity to fully test communications between, and behavior of, both the spacecraft and the ground segment prior to $launch.^{:480}$

### Launch facilities

Vehicles are delivered to space via launch facilities, which handle the logistics of rocket launches. Launch facilities are typically connected to the ground network to relay telemetry prior to and during launch. The launch vehicle itself is sometimes said to constitute a "transfer segment", which may be considered distinct from both the ground and space $segments.^{:21}$

### Ground networks

Ground networks handle data transfer and voice communication between different elements of the ground $segment.^{:481–482}$ These networks often combine LAN and WAN elements, for which different parties may be responsible. Geographically separated elements may be connected via leased lines or virtual private $networks.^{:481}$ The design of ground networks is driven by requirements on reliability, bandwidth, and security. Delay-tolerant networking protocols may be used.

Reliability is a particularly important consideration for critical systems, with uptime and mean time to recovery being of paramount concern. As with other aspects of the spacecraft system, redundancy of network components is the primary means of achieving the required system reliability.

Security considerations are vital to protect space resources and sensitive data. WAN links often incorporate encryption protocols and firewalls to provide information and network security. Antivirus software and intrusion detection systems provide additional security at network endpoints.

## Costs

Costs associated with the establishment and operation of a ground segment are highly variable, and depend on accounting methods. According to a study by Delft University of Technology, the ground segment contributes approximately 5% to the total cost of a space system. According to a report by the RAND Corporation on NASA small spacecraft missions, operation costs alone contribute 8% to the lifetime cost of a typical mission, with integration and testing making up a further 3.2%, ground facilities 2.6%, and ground systems engineering $1.1%.^{:10}$

Ground segment cost drivers include requirements placed on facilities, hardware, software, network connectivity, security, and staffing. Ground station costs in particular depend largely on the required transmission power, RF band(s), and the suitability of preexisting $facilities.^{:703}$ Control centers may be highly automated as a means of controlling staffing costs.

* ↑ Based on a model described in Space Mission Analysis and Design, third edition, by James W. Wertz and Wiley J. Larson

## Images

* Antenna belonging to the Deep Space Network
* Space Telescope Operations Control Center at Goddard Space Flight Center, during servicing of the Hubble Space Telescope
* Integration of flight hardware at a JAXA facility in Tsukuba, Japan
* Decommissioned launch site at the Guiana Space Centre
