ETSI EN 301 927 V1.1.1 (2003-02)

SLOVENSKI STANDARD
01-februar-2006
Satelitske zemeljske postaje in sistemi (SES) – Evropsko sodelovanje pri
standardizaciji vesoljskih zadev (ECSS) - Satelitski vmesniki za obdelavo
programskih podatkov (SSDHI)
Satellite Earth Stations and Systems (SES); European Co-operation for Space
Standardization (ECSS); Satellite Software Data Handling Interfaces (SSDHI)
Ta slovenski standard je istoveten z: EN 301 927 Version 1.1.1
ICS:
33.060.30 Radiorelejni in fiksni satelitski Radio relay and fixed satellite
komunikacijski sistemi communications systems
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

European Standard (Telecommunications series)

Satellite Earth Stations and Systems (SES);
European Co-operation for Space Standardization (ECSS);
Satellite Software Data Handling Interfaces (SSDHI)

2 ETSI EN 301 927 V1.1.1 (2003-02)

Reference
DEN/SES-000-ECSS-2
Keywords
data, interface, LAYER 7, satellite, service
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, send your comment to:
editor@etsi.org
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2003.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI EN 301 927 V1.1.1 (2003-02)
Contents
Intellectual Property Rights.5
Foreword.5
Introduction .5
1 Scope.6
2 References.6
3 Definitions and abbreviations.6
3.1 Definitions.6
3.2 Abbreviations.8
4 Applicability.8
5 Recommendation guidelines.9
5.1 Objectives.9
5.2 Interface covering.9
5.3 Position of the standard proposed services with respect to other standards .10
6 Service specification.12
6.1 Introduction.12
6.2 Conventions.12
6.2.1 Service primitive naming.12
6.2.2 Parameter type and format abbreviations.13
6.3 Standard services.13
7 Services.16
7.1 Memory Management Service .16
7.2 Units power switching and resetting services.18
7.2.1 Device power switch-on service .18
7.2.2 Device power switch-off service .18
7.2.3 Device reset service .19
7.2.4 Device arming service .19
7.2.5 Function enabling service .20
7.3 Specific services.21
7.3.1 Platform Sensor and Actuator services .21
7.3.1.1 Specific sensors.21
7.3.1.1.1 Accelerometer service.21
7.3.1.1.2 Gyro service.22
7.3.1.1.3 Star tracker service .23
7.3.1.1.4 Earth sensor service.24
7.3.1.1.5 Sun Sensor service.26
7.3.1.1.6 Magnetometer service.26
7.3.1.2 Specific actuator.27
7.3.1.2.1 Thruster configuration service.27
7.3.1.2.2 Venting service.27
7.3.1.2.3 Apogee Boost Motor service .28
7.3.1.2.4 Thruster burst service .29
7.3.1.2.5 Plasmic Propulsion service.30
7.3.1.2.6 Wheel service.31
7.3.1.2.7 Pyrotechnic service.32
7.3.1.2.8 Magnetic-torquers service.34
7.3.1.3 Platform management.34
7.3.1.3.1 Battery reconditioning service.34
7.3.1.3.2 Power conditioning service .36
7.3.1.3.3 Stepper motor management service.37
7.3.2 Payload & TTC services .38
7.3.2.1 Synthesizers service.38
ETSI
4 ETSI EN 301 927 V1.1.1 (2003-02)
7.3.2.2 Power amplifiers service .39
7.3.2.3 Channel amplifier.40
7.3.2.4 Switching service.41
7.3.2.5 Digital Transparent Processor service.42
7.4 Simple devices services.45
7.4.1 Pulse command service.45
7.4.2 Temperature acquisition service.46
7.4.3 Pressure acquisition service .46
7.4.4 Current acquisition service .47
7.4.5 Voltage acquisition service.48
7.4.6 Frequency acquisition service.48
8 Design requirements.49
Annex A (informative): End to end example .50
Annex B (informative): Comments and recommendations for usage of the present document.51
B.1 Identifier type definition.51
B.2 Distinction between status and error parameters.51
B.3 Recommendations on services .52
B.4 SOIF services not kept in the present document .52
B.5 Services not defined in the present document .52
Annex C (informative): SOIF description.54
C.1 General.54
C.2 SOIF Command and Data Acquisition Service.55
C.3 Architectural Context.55
C.4 Service Operation - Service User Perspective.56
C.5 Service Operation - Service Providers Perspective.56
Annex D (informative): Parameter type code and format.57
D.1 Encoding formats of parameter types.57
D.2 Parameter type definitions.57
D.2.1 Boolean.57
D.2.2 Enumerated Parameter.57
D.2.3 Unsigned Integer.58
D.2.4 Signed Integer.58
D.2.5 Real.58
D.2.6 Bit-String.59
D.2.7 Octet-String.60
Annex E (informative): Bibliography .61
History .62

ETSI
5 ETSI EN 301 927 V1.1.1 (2003-02)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
All published ETSI deliverables shall include information which directs the reader to the above source of information.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Satellite Earth
Stations and Systems (SES).
National transposition dates
Date of adoption of this EN: 21 February 2003
Date of latest announcement of this EN (doa): 31 May 2003
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 30 November 2003
Date of withdrawal of any conflicting National Standard (dow): 30 November 2003

Introduction
Shorter and shorter communications satellites development cycles and compatibility requested with off the shelf
equipments requires interface standardization to be able to introduce a new equipment very late in satellite development
cycle. The present document will allow the development of On Board Software (OBSW) independently of the choice of
satellite equipment. It will be used to standardize the software specifications of the Interface between the application
software and the communication services. It shall help the standardization of equipment interface.
The present document addresses ISO OSI application layer services [1].
Currently, no application layer services standard exists for the Data System of geostationary communication satellites.
The aim of the present document is to respond to such requirements. Nevertheless, there are complementary agency
standards existing or in progress (see bibliography).
Integration or adaptation of new services, due to technology evolution, will be implemented through the maintenance of
the present document. The contents of the present document are subject to continuing work within TC-SES and may
change following formal TC-SES approval. Should TC-SES modify the contents of the present document it will then be
republished by ETSI with an identifying change of release date and an increase in version number as follows:
Version 1.m.n, where:
m The second digit (m) is incremented for all other types of changes, i.e. technical enhancements,
corrections, updates, etc.
n The third digit (n) is incremented when editorial only changes have been incorporated in the
specification.
ETSI
6 ETSI EN 301 927 V1.1.1 (2003-02)
1 Scope
The present document applies to Geostationary Communications Satellite architectures based on ISO OSI Reference
Model or SOIF Reference Model, but could also be applied to other types of satellites.
The present document sets out the minimum definition, services and interfaces requirements of the satellite
communication application layer.
The present document is complementary to Spacecraft Onboard Interfaces (SOIF).
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
[1] ISO/IEC 7498-1 (1994): "Information Technology - Open Systems Interconnection - Basic
Reference Model: The Basic Model".
[2] IEEE Standard 754-1985: "IEEE Standard for Binary Floating-Point Arithmetic".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Application Layer Service (ALS): entity which provides application software with a capability to operate devices,
with a warranty of performance
application software: on-board software implementing the satellite control functions
NOTE: A service is implemented by hardware and/or software. Application layer services for the control of
devices are defined in terms of:
the functions provided by the service;
a service access point;
the management parameters.
ETSI
7 ETSI EN 301 927 V1.1.1 (2003-02)
autonomy: ability of a system to provide without external intervention, mission services on a given period of time and
in a limited context: nominal or under anomaly conditions
NOTE: Three types of autonomy are defined:
reflex autonomy: characterizes the capability to perform predefined actions under triggering
events. This kind of autonomy, already in use, is performed through automation mechanisms, with
predefined sequences of states and triggering events (failure detection, isolation and recovery, etc.).
function autonomy: characterizes the capability of the satellite to perform automatic function on
board, implementing on board closed loops to maintain function performances without ground
intervention. Thermal regulation, batteries management, and attitude control are some examples of
function autonomy.
decision autonomy: characterizes the capability of the satellite to manage and update its schedule
of activities or tasks, taking into account events (expected or not) occurring during the mission
(Autonomous navigation, mission (re)scheduling, etc.).
Data Handling System (DHS): on-board system including computers and interface units hosting the application
software and providing communications between on-board units and with the ground
devices: devices are the onboard components that onboard application software control in order to perform the
operational objectives of the spacecraft
EXAMPLE: Sensors and actuators, Telemetry Command and Ranging (TCR) devices or other mission specific
devices.
st
J2000: earth centred co-ordinate reference system with an epoch of January 1 2000
primitive: a signal (e.g. a send request) which is passed across the service access point in order to use the service
capabilities
NOTE: The primitive may have associated parameters.
Service Access Point (SAP): the interface provided to a service through which users access the capabilities of the
service
NOTE: The service access points are defined in terms of a set of primitives.
spacelink interface: ground to satellite communication link for monitoring and control

Figure 1: Example of Spacecraft System
ETSI
8 ETSI EN 301 927 V1.1.1 (2003-02)
Service: Application Layer Service
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ABM Apogee Boost Motor
ACC ACCelerometer
ALSS Application Layer Services Standard
BSV Bi Stable Valve
CAMP Channel AMPlifier
DHS Data Handling System
DTP Digital Transparent Processor
EEPROM Electrically Erasable Programmable Read Only Memory
EPC Encapsulated Power Converter
ES Earth Sensor
EUC Engineering Unit Conversion
FDIR Failure Detection Isolation and Recovery
GYRO GYROscope
HW HardWare
ICD Interface Control Document
ISO International Standard Organization
MSV Mono Stable Valve
MT Magneto Torquer
OBSW On-Board SoftWare
OSI Open System Interconnection
PCU Power Conditioning Unit
PFC Parameter Format Code
PP Plasmic Propulsion
PTC Parameter Type Code
PUS Packet Utilization Standard
PYRO PYROtechnic
RAM Random Access Memory
ROM Read Only Memory
RW Reaction Wheel
SAP Service Access Point
SDB System Data Base
SM Stepper Motor
SOIF Spacecraft Onboard InterFaces
SS Sun Sensor
SSDHI Satellite Software Data Handling Interfaces
STR Star TRacker
SW SoftWare
TC Tele Command
TCR Telemetry, Command and Ranging
TOM Thruster Orientation Mechanism
TWTA Travelling Wave Tube Amplifier
4 Applicability
The present document can be applied to all classes of spacecraft including in particular communications satellites.
ETSI
9 ETSI EN 301 927 V1.1.1 (2003-02)
5 Recommendation guidelines
5.1 Objectives
The main recommendation drivers are:
• Development optimization:
- Standardization data format.
- Using common formats for key commands across different data buses.
- Planning optimization by minimising development time.
- Cost by reducing engineering process on specification and development of application layer services.
- Minimising risk basing the development on validated requirements.
- Increasing potential for flight equipment, software (SW) and test equipment reuse.
- Overlapping of software development with hardware development:
It will be possible to optimize this process by applying the present document which provides
requirements independent of any hardware configuration.
This concept allows to freeze application layer Interface Control Document (ICD) to guarantee
hardware independence.
• Performance constraints:
- Real time.
- Memory size.
- Load of onboard communication data bus.
- Device Observability.
- Device Commandability.
- Number and type of units to interface.
- Operations complexity.
5.2 Interface covering
Data communication on satellite requires electrical and data interfaces onboard. These interfaces include:
• Hardware interfaces:
- Electrical interfaces (power, command, acquisition, pyrotechnic, etc.) to devices.
- Onboard communication data buses.
• Software interfaces:
- Software drivers controlling devices and communication on data buses.
- Application software interfaces.
The application layer is the highest layer of the reference OSI [1] and SOIF (see bibliography) models (see figure 2). In
the OSI Reference Model, the application software is not included in the reference model application layer, since this
software is the user of the communications services provided by the OSI Reference Model.
ETSI
10 ETSI EN 301 927 V1.1.1 (2003-02)
The present document provides recommendations to interface application services between themselves and to other
OSI/SOIF layers. In particular, it defines the services to interface devices with application software independent of
lower layer levels (particularly the electrical interface).

OSI mapping SOIF mapping
Application layer
Application layer
Presentation layer
Session layer
Transport layer
Transport layer
Network layer Network layer
Data link layer
Data link and physical
layer
Physical layer
Figure 2: OSI and SOIF layers mapping
5.3 Position of the standard proposed services with respect to
other standards
The present document implies the provision of certain underlying services, that could be provided by SOIF
(see annex C):
• Command and Data Acquisition service;
• Time service;
• File transfer service.
The present document does not address in particular:
• Task management;
• On-board scheduling;
• Satellite System FDIR.
User Application Layer definition:
This layer contains satellite application services like AOCS management, Control and Data management and FDIR
management, unit management, etc. This layer shall be independent of the underneath layers in term of equipment
manufacturer and transmission protocol/media. The goal is to provide user application reuse capability.
User application services implementation can call (see figure 3):
• Other user application layer services;
• Application Interface services;
• SOIF or non SOIF application layer services (see annex C);
• Any other lower layer services with exposed Service Access Point.
ETSI
11 ETSI EN 301 927 V1.1.1 (2003-02)
Application Interface Services definition:
These services provide satellite function or equipment oriented services with an interface independent of the equipment
manufacturer or of the transmission protocol/physical link.
The service implementation requires the equipment database in order to make the link between the standardized
interface and the equipment function.
Although the service implementation is equipment dependent, the objective is to use common services provided by
e.g. the SOIF application layer.
These services can call:
- Other application interface services;
- SOIF or non SOIF application layer services;
- Any other lower layer services with exposed Service Access Point.
AOCS CDMS
Unit Other
FDIR
Attitude and Orbit Control and Data
User application
Management applications
Control Management
Application interface services
Application interface
Proprietary services
SSDHI services
services
based or not on SOIF
based or not on SOIF
(Satellite function oriented, can be transparent)
Platform and
Equipement
SOIF interface
Data
Base
Time
Proprietary
File Transfer Messaging C&DA
Distribution
Service
Service Service Service
Application layer Service
Interfaces with the application
Confirmed Unconfirmed
Stream
Datagram Datagram
Transport layer Service
Service Service
Organisation of the complete successful
communication
Security service
Network Inter
management Networking
Network layer
service service
Convergence interface Convergence interface Convergence interface
Intra
Network
Networking
Network sublayer
Data
service
Base
Data link layer Data link layer
Physical layer
Physical layer
SOIF layered model
Figure 3: SSDHI position with respect to. other services
ETSI
12 ETSI EN 301 927 V1.1.1 (2003-02)
6 Service specification
6.1 Introduction
This service specification covers all onboard satellite applications.
Generic services are provided according to onboard satellite complexity increase: memory management, etc.
Specific services cover Platform and Payload devices. These services are equipment functionality dependent. They are
defined according to the state of the art.
Evolution of these services will be done according to the integration of new equipment.
Simple device services are used for low level command (Pulse) or low level acquisition (Pressure, Temperature,
Current, Voltage, Frequency, etc.).
For raw data acquisition it is recommended to use directly Command and Acquisition services, or eventually File
Transfer provided by SOIF, or proprietary services.
Units redundancy concepts and management are performed in the User Application Layer, and thus it is not addressed
in the present document.
6.2 Conventions
6.2.1 Service primitive naming
Inside a service one or more primitive can be defined.
These primitives provide data exchange between the application software and the service.
The following naming convention suffixes are used according to the transaction direction:
• XXXXX_RQ: Request primitive issued by the service user to the service provider.
• XXXXX_IND: Indication primitive issued by the service provider to the service user. This primitive may be
associated to a previous request primitive.
The following naming convention prefixes can be used for a better primitive understanding:
• SET: Prefix for a configuration primitive: equipment configuration setting, command execution, device switch
on or off.
• GET: Prefix for an acquisition primitive: data acquisition, status acquisition.
Application software
Request Indication
XXX_R
XXX_IN
SET_XXX_ SET_XXX_I
GET_XXX_ GET_XXX_I
SSDHI services
Figure 4: Primitives naming
ETSI
13 ETSI EN 301 927 V1.1.1 (2003-02)
6.2.2 Parameter type and format abbreviations
Parameter types are those defined in the PUS Packet Utilization Standard (see bibliography). A summary is given in
annex D.
Within the specification of a service, the following abbreviations are used.
Table 1: Parameter type
Parameter type Abbreviation
Boolean parameter 'Boolean'
Enumerated parameter 'Enumerated'
Integer parameter
Unsigned Integer 'Unsigned Integer'
Signed Integer 'Signed Integer'
Real Parameter 'Real'
Bitstring Parameter
Fixed length bit string 'Fixed BitString'
Variable length bit string 'Variable BitString'
OctetString Parameter
Fixed length octet string 'Fixed OctetString'
Variable length octet string 'Variable OctetString'

For each parameter type (PTC) the present document specifies the parameter type (PTC) and format (PFC).
6.3 Standard services
The standard services listed in table 2 are described in the following clauses.
Table 2: SSDHI standard services
Service name/Primitive name Request and Indication primitives

Memory Management Service
Load memory using base plus offset LOAD_MEMORY_BO_RQ
LOAD_MEMORY_BO_IND
Dump memory using base plus offset DUMP_MEMORY_BO_RQ
DUMP_MEMORY_BO_IND
Check memory using base plus offset CHECK_MEMORY_BO_RQ
CHECK_MEMORY_BO_IND
Device power switch on service
Device power switch ON SET_DEVICE_POWER_ON_RQ
SET_DEVICE_POWER_ON_IND
Device power switch off service
Device power switch OFF SET_DEVICE_POWER_OFF_RQ
SET_DEVICE_POWER_OFF_IND
Device reset service
Device reset SET_DEVICE_RESET_RQ
SET_DEVICE_RESET_IND
Device arming service
Device arming SET_DEVICE_ARMING_RQ
SET_DEVICE_ARMING_IND
Device disarming SET_DEVICE_DISARMING_RQ
SET_DEVICE_DISARMING_IND
Function enabling service
Device function enabling SET_DEVICE_FUNCTION_ENABLE_RQ
SET_DEVICE_FUNCTION_ENABLE_IND
Device function disabling SET_DEVICE_FUNCTION_DISABLE_RQ
SET_DEVICE_FUNCTION_DISABLE_IND
Accelerometer service
Incremental speed acquisition GET_ACC_INC_RQ
GET_ACC_INC_IND
ETSI
14 ETSI EN 301 927 V1.1.1 (2003-02)
Service name/Primitive name Request and Indication primitives
Gyroscope service
Incremental delta angle acquisition GET_GYRO_ANG_RQ
GET_GYRO_ANG_IND
Star Tracker service
Quaternion acquisition GET_STR_QUAT_RQ
GET_STR_QUAT_IND
Earth sensor service
Attitude data acquisition GET_ES_DATA_RQ
GET_ES_DATA_IND
Acquisition mode selection SET_ES_MODE_RQ
SET_ES_MODE_IND
Array inhibition SET_ES_ARRAY_RQ
SET_ES_ARRAY_IND
Sun sensor service
Sun sensor data acquisition GET_SUN_SENSOR_DATA_RQ
GET_SUN_SENSOR_DATA_IND
Magnetometer service
Magnetometer data acquisition GET_MAGNETOMETER_RQ
GET_MAGNETOMETER_IND
Thruster configuration service

Thruster BSV valve setting SET_THRUSTER_BSV_VALVE_RQ
SET_THRUSTER_BSV_VALVE_IND
Venting service
Start venting SET_VENTING_START_RQ
SET_VENTING_START_IND
Stop venting SET_VENTING_STOP_RQ
SET_VENTING_STOP_IND
Apogee boost motor service
ABM switch On SET_ABM_ON_RQ
SET_ABM_ON_IND
ABM switch Off SET_ABM_OFF_RQ
SET_ABM_OFF_IND
Thruster burst service
Thruster MSV command SET_THRUSTER_MSV_VALVE_RQ
SET_THRUSTER_MSV_VALVE_IND
Plasmic propulsion service
Plasmic propulsion start SET_PP_START_RQ
SET_PP_START_IND
Plasmic propulsion stop SET_PP_STOP_RQ
SET_PP_STOP_IND
Wheel service
Speed or torque command SET_RW_RQ
SET_RW_IND
Speed acquisition GET_RW_RQ
GET_RW_IND
Pyrotechnic service
Pyro selection SET_PYRO_SELECT_RQ
SET_PYRO_SELECT_IND
Pyro deselecting SET_PYRO_DESELECT_RQ
SET_PYRO_DESELECT_IND
Pyro firing SET_PYRO_FIRING_RQ
SET_PYRO_FIRING_IND
Magnetic torquers service
Torquer current command SET_MT_CURRENT_RQ
SET_MT_CURRENT_IND
Battery reconditioning service
Battery start reconditioning SET_BATT_RECOND_START_RQ
SET_BATT_RECOND_START_IND
Battery stop reconditioning SET_BATT_RECOND_STOP_RQ
SET_BATT_RECOND_STOP_IND
Battery reconditioning load change SET_BATT_RECOND_LOAD_RQ
SET_BATT_RECOND_LOAD_IND
ETSI
15 ETSI EN 301 927 V1.1.1 (2003-02)
Service name/Primitive name Request and Indication primitives
Power conditioning service
Charge current intensity setting SET_PCU_CHARGE_INT_RQ
SET_PCU_CHARGE_INT_IND
Stepper motor management service
Stepper motor motion command SET_SM_MOTION_RQ
SET_SM_MOTION_IND
Stepper motor reference position setting SET_SM_REFERENCE_RQ
SET_SM_REFERENCE_IND
Stepper motor position acquisition GET_SM_SENSOR_RQ
GET_SM_SENSOR_IND
Synthesizer service
Frequency setting SET_FREQUENCY_RQ
SET_FREQUENCY_IND
Power amplifier service
TWTA autorestart setting SET_TWTA_AUTORESTART_RQ
SET_TWTA_AUTORESTART_IND
TWTA status acquisition GET_TWTA_STATUS_RQ
GET_TWTA_STATUS_IND
Channel amplifier service
CAMP configuration setting SET_CAMP_CONFIG_RQ
SET_CAMP_CONFIG_IND
Switching service
Switch configuration setting SET_SWITCH_CONFIG_RQ
SET_SWITCH_CONFIG_IND
Switch configuration acquisition GET_SWITCH_CONFIG_RQ
GET_SWITCH_CONFIG_IND
DTP service
Links setting ON SET_DTP_LINK_ON_RQ
SET_DTP_LINK_ON_RQ
Links setting OFF SET_DTP_LINK_OFF_RQ
SET_DTP_LINK_OFF_RQ
DTP link configuration setting SET_DTP_CONFIG_RQ
SET_DTP_CONFIG_IND
DTP link power acquisition GET_DTP_POWER_RQ
GET_DTP_POWER_IND
DTP link configuration acquisition GET_DTP_CONFIG_RQ
GET_DTP_CONFIG_IND
Pulse command service
Pulse command SET_PULSE_RQ
SET_PULSE_IND
Temperature acquisition service
Temperature acquisition GET_TEMPERATURE_RQ
GET_TEMPERATURE_IND
Pressure acquisition service
Pressure acquisition GET_PRESSURE_RQ
GET_PRESSURE_IND
Current acquisition service
Current acquisition GET_CURRENT_RQ
GET_CURRENT_IND
Voltage acquisition service
Voltage acquisition GET_VOLTAGE_RQ
GET_VOLTAGE_IND
Frequency acquisition service
Frequency acquisition GET_FREQUENCY_RQ
GET_FREQUENCY_IND
ETSI
16 ETSI EN 301 927 V1.1.1 (2003-02)
7 Services
7.1 Memory Management Service
This service is based on PUS Memory Management Service (see Bibliography).
This service shall be use for onboard memory block management (RAM, ROM, EEPROM, etc.). This service shall
provide the capability for loading, dumping and checking the contents of contiguous memory blocks.
The PUS non contiguous memory block management is not defined in this service.
The following primitives are defined:
• Load memory using base plus offset;
• Dump memory using base plus offset;
• Check memory using base plus offset.
Load memory using base plus offset:
This primitive shall be used to load data into a memory block defined by means of a base reference plus offset.
LOAD_MEMORY_BO_RQ(Device_Id, Base, Offset, Data)
Device_Id = Device logical Identifier, Type = Unsigned Integer (PFC = 12)
The device_Id identifies the destination memory block according to satellite architecture.
Base = Base reference, Type = Unsigned Integer (PFC = 14)
This base shall be used as the zero reference for the offset.
Offset = Offset from the base reference, Type = Signed Integer (PFC = 14)
Data = Data block to load, Type = Variable OctetString (PFC = 0)
On receipt of this primitive, the service shall send commands to an underlying communication service to:
• calculate the checksum (ISO standard 16 bits checksum cf annex 3 PUS)
• load the data block according to the transmitted base and offset
• read the loaded block and compare the checksum with the previous one
LOAD_MEMORY_BO_IND (Device_Id, Checksum, Error)
Device_Id = Device logical Identifier, Type = Unsigned Integer (PFC = 12)
Checksum = Checksum status
1 = Checksum error or loading fail
0 = Checksum OK
Error = Error flag, Type = Boolean
1 = acquisition not performed
0 = acquisition performed
Dump memory using base plus offset:
This primitive shall be used to dump data from a memory block defined by means of a base reference plus offset.
DUMP_MEMORY_BO_RQ(Device_Id, Base, Offset, Length)
Device_Id = Device logical Identifier, Type = Unsigned Integer (PFC = 12)
The device_Id identifies the source memory block according to satellite architecture.
ETSI
17 ETSI EN 301 927 V1.1.1 (2003-02)
Base = Base reference, Type = Unsigned Integer (PFC = 14)
This base shall be used as the zero reference for the offset
Offset = Offset from the base reference, Type = Signed Integer (PFC = 14)
Length = Number of octets to be dumped, Type = Unsigned Integer (PFC = 14)
On receipt of this primitive, the service shall send commands to an underlying communication service to dump the
memory block.
DUMP_MEMORY_BO_IND (Device_Id, Base, Offset, Data, Error)
Device_Id = Device logical Identifier, Type = Unsigned Integer (PFC = 12)
Base = Base reference, Type = Unsigned Integer (PFC = 14)
This base shall be used as the zero reference for the offset
Offset = Offset from the base reference, Type = Signed Integer (PFC = 14)
Data = Dumped data block to load, Type = Variable OctetString (PFC = 0)
Error = Error flag, Type = Boolean
1 = acquisition not performed
0 = acquisition performed
Check memory using base plus offset:
This primitive shall be used to check a memory block defined by a base, an offset and a length.
CHECK_MEMORY_BO_RQ(Device_Id, Base, Offset, Length)
Device_Id = Device logical Identifier, Type = Type = Unsigned Integer (PFC = 12)
The device_Id identifies the source memory block according to satellite architecture.
Base = Base reference, Type = Unsigned Integer (PFC = 14)
This base shall be used as the zero reference for the offset
Offset = Offset from the base reference, Type = Signed Integer (PFC = 14)
Length = Number of octets to be dumped, Type = Unsigned Integer (PFC = 14)
On receipt of this primitive, the service shall send commands to an underlying communication service to:
• read the memory block
• calculate the checksum (ISO standard 16 bit checksum cf annex 3 of PUS)
• report the calculated checksum
CHECK_MEMORY_BO_IND (Device_Id, Checksum, Error)
Device_Id = Device logical Identifier, Type = Unsigned Integer (PFC = 12)
Checksum = Memory block calculated checksum, Type = Unsigned Integer (PFC = 12)
Error = Error flag, Type = Boolean
1 = acquisition not performed
0 = acquisition performed
ETSI
18 ETSI EN 301 927 V1.1.1 (2003-02)
7.2 Units power switching and resetting services
7.2.1 Device power switch-on service
This service shall be used for all the device switch-ons. It concerns simple devices without any configuration to apply
up to large configurable equipment.
The service operations are the following:
• Power ON the device;
• Initialize the device if required;
• Get global status flag.
SET_DEVICE_POWER_ON_RQ (Device_Id)
Device_Id = Device logical Identifier, Type = Unsigned Integer (PFC = 12)
On receipt of this primitive, the service shall send commands to an underlying communication layer to switch ON and
initialize the device.
This service shall manage specific timing constraints linked to device switch ON procedure.
SET_DEVICE_POWER_ON_IND (Device_Id, Status, Error)
Device_Id = Device logical Identifier, Type = Unsigned Integer (PFC = 12)
Status = Device logical status:, Type = Enumerated Parameter (PFC = 2)
00 = OFF: the device is power OFF
01 = Initialization in progress
10 =
...