This document addresses the utilization of telecommand packets and telemetry source packets for the
purposes of remote monitoring and control of subsystems and payloads.
This document does not address mission-specific payload data packets, but the rules contained herein can be
extended to suit the requirements of any mission.
This document does not address audio and video data as they are not contained within either telecommand or
telemetry source packets.
This document is structured as follows. Firstly a set of operational concepts is identified, covering all the
fundamental requirements for spacecraft monitoring and control during satellite integration, testing and flight
operations. A set of services that satisfy these operational concepts is then defined. The detailed specification
of these services includes the structure and contents of the associated service requests (telecommand
packets) and service reports (telemetry source packets).
This document is applicable to any mission, no matter what its domain of application, orbit or ground station
coverage characteristics. However, it is not the intention that the PUS is applicable to a given mission in its
entirety. The operational concepts and corresponding services contained in this document cover a wide
spectrum of operational scenarios and, for a given mission, only a subset of these operational concepts and
services is appropriate.
Choices are made early in the design phase of a new mission resulting in the need to tailor the PUS to suit the
requirements of the particular mission. These choices include:
a) The on-board system design and architecture, in terms of the number of on-board application processes,
their on-board implementation (e.g. the allocation to on-board processors) and their roles (i.e. which
functions or subsystems or payloads they support).
b) Which PUS services are supported by each application process.
NOTE Tailoring (...abbreviated)
EN 14776 addresses the utilization of telecommand packets and telemetry source packets for the purposes of remote monitoring and control of subsystems and payloads. This standard does not address mission-specific payload data packets, but the rules contained herein can be extended to suit the requirements of any mission. This standard does not address audio and video data as they are not contained within either telecommand or telemetry source packets. This standard is structured as follows: Firstly a set of operational concepts is identified, covering all the fundamental requirements for spacecraft monitoring and control during satellite integration, testing and flight operations. A set of services that satisfy these operational concepts is then defined. The detailed specification of these services includes the structure and contents of the associated service requests (telecommand packets) and service reports (telemetry source packets). This standard is applicable to any mission, no matter what its domain of application, orbit or ground station coverage characteristics. However, it is not the intention that the PUS (packet utilization standard) is applicable to a given mission in its entirety. The operational concepts and corresponding services contained in this document cover a wide spectrum of operational scenarios and, for a given mission, only a subset of these operational concepts and services is appropriate.