SPACE/GROUND INTERFACE REQUIREMENTS DOCUMENT EXM-G2-IRD-ESC-00001

Transcription

1 Page: 1/26 ExoMars 2018 Mission SPACE/GROUND INTERFACE REQUIREMENTS DOCUMENT EXM-G2-IRD-ESC Issue 1 Revision 3 15 April 2014 Date and Signature Prepared D. Firre (HSO-ONX) ExoMars Ground Operations Manager Agreed M. Denis (HSO-OPM) ExoMars Ground Segment Manager Approved D. McCoy (SRE-PE) ExoMars Project Manager

2 Page: 2/26 DOCUMENT CHANGE LOG Issue/ Revision Date Modified pages Observations 1 / 0 23/07/13 All Issue of version 1.0 for configuration control reasons. This issue will be further discussed and updated following e.g. the comments received from TAS-I, and a next issue will reflect the outcome of these discussions. Cover page HSO-OPM: M. Denis replaces P. Ferri Added IR-2 new doc number assigned by documentation and configuration management GS-1: DSN added 2.1 GS-9/10/11/13: TBD replaced by Number and duration of contacts 2.1 GS-13: MOI replaced by Mars arrival and Rovers replaced by DM 2.1 GS-5: rephrased 1/1 17/10/ GS-5: Bear's Lakes is mandatory for 2018 mission. requirement rephrased and note removed GS-1: rephrased to include Russian provided ground station GS-2: rephrased to be more generic about ESA LEOP Station network (Perth and Kourou may not be available in 2018, while suitable replacement will be offered) Table of content for SGICD Vol1, section 4.2 updated: Bear's Lakes 64m confirmed, Perth 15m antenna or suitable replacement as Perth will most certainly be closed by the launch of the 2018 mission 1.1 and 1.2 Explicit mention of ESTRACK removed as this document applies to all ground stations (including Bear's Lakes)

3 Page: 3/26 1 / 2 07/04/ [NR 21] CCSDS Pseudo-Noise ranging systems recommended standard updated to latest applicable Blue Book version 2 from Feb GS-11: during interplanetary cruise 3 ground control contacts per week instead of daily contacts (same ops baseline as EXM2016 mission) 2.1 GS-22: new requirement on recovery of level-1 safe mode by ESA ESTRACK only CHF-4.1: requirement rephrased to include possible use of Pseudo-Noise regenerative ranging. Note 2 and Note 3 added on usage of PN ranging Reverted to EXM2016 ranging accuracy requirements (4m range random error and 20m range bias) CHF-4.3: requirement added on minimum duration of ranging measurement sessions if not simultaneous with telemetry downlink. 6 New section covering Surface Assets Relay requirements. Contains only one requirement at this time: REL-1 7 Acronyms list updated: added ECSS, PN, TGO 1 / 3 15/04/14 6 REL-1 rephrased: "two Earth station passes per day" [NR 21] "CCSDS Pseudo-Noise ranging systems recommended standard" reverted to old superseded version to maintain compatibility with EXM CHF-4.1 Note 2 rewritten CHF-4.3 "if the link budget permits" added at beginning of sentence

4 Page: 4/26 Table of Contents 1 INTRODUCTION Purpose and Scope Structure of the Document Design Variables REFERENCE DOCUMENTS Normative References Informative References RF Link Requirements Ground Station Support Frequencies Channel Formats Modulation Uplink Downlink Data Rates Channel Coding Satellite Antennas Operational Utilisation Systems Operational Modes Protocols and Packet Definitions RF and Bit Lock TM and TC Packet Structure Encoding TM and TC Data Compression Virtual Channels Flow Control SG-ICD Contents Requirements Documents Structure Volume Volume Volume Configuration and Change Control Volume Volume Volume

5 Page: 5/26 5 RF Suitcase Surface assets Relay requirements ACRONYMS... 24

6 Page: 6/26 1 INTRODUCTION 1.1 Purpose and Scope The purpose of this document is to identify the interface requirements on the Exomars 2018 Carrier Module necessary for RF communications through the ground stations network to the Mission Control Centre. These requirements are applicable to all Ground to Space links. 1.2 Structure of the Document This document has three main sections. Section 2. Defining the requirements for the RF link between the various Ground Stations and the various Exomars 2018 Carrier Module antennas. Section 3. Recalling the TM and TC frames and packet level and referring to the relevant requirements and interface documentation. Section 4. Definition of the SG-ICD document structure. 1.3 Design Variables. Deleted 1.4 REFERENCE DOCUMENTS Normative References Normative References (NR) are fully applicable in their entirety to this document and are listed below as dated or undated references. These normative references may be cited at appropriate places in the text. For the explicit, dated or versioned, references, subsequent amendments to, or revisions of, any of those references do not apply to this document. The version of any other references to be used is given in the list of documents constituting the contractual baseline. In case of conflict between this document and normative documents listed herein the Contractor shall inform the ESA Project Office for resolution NR-1 ECSS-E-ST-50C Communications - Part 1: Principles and requirementsnr-2 NR-3 Time Code Formats, CCSDS B-4 NR-4 LossLess Compression, CSSDS B-2 NR-5 ECSS-E-ST-50-04C: Space data links Telecommand protocols, synchronization and channel coding NR-6 ECSS-E-ST-50-03C: Space engineering Space data links Telemetry transfer frame protocol NR-7 Deleted

7 Page: 7/26 NR-8 ECSS-E-ST-50-01C: Space engineering Space data links Telemetry synchronization and channel coding NR-9 TM Space Data Link Protocol. CCSDS B-1 Blue Book. Issue 1. Sep NR-10 Space Packet Protocol. CCSDS B-1 Blue Book. Issue 1. Sep NR-11 NR-12 Telemetry and Telecommand Packet Utilisation, ECSS-E-70-41A. NR-13 Space Link Extension Return All Frames (SLE-RAF) Service Specification, CCSDS B-3 NR-14 SLE-Forward CLTU Service Specification, CCSDS B-3 NR-15 Communications Operations Procedure, CCSDS B-2 NR-16 Moved to Informative Documents NR-17 Space Link Extension Return Channel Frames (SLE RFC) Service Specification, CCSDS B-2. NR-18 Radio Frequency and Modulation Systems Part 1, Earth Stations and Spacecraft recommended standard, CCSDS B-21, BLUE BOOK, April 2009, recommendation 2.5.6B (Delta-DOR) and recommendation B (suppressed carrier modulation) NR 19 ECSS-E-ST-50-02C Ranging and Doppler tracking NR 20 Radio Frequency and Modulation ECSS-E-ST-50-05C Rev 2 04 October 2011 NR-21 CCSDS Pseudo Noise (PN) Ranging Systems, Recommended Standards, CCSDS B-1, Blue Book, March NR-22 ExoMars 2018 Mission - Mission Analysis Guidelines (MAG), EXM-G2-TNO-ESC-00003, Issue 1, Rev. 0 Note 1 : Deleted Note 2 : Deleted Note 3 : [TBC] Due to inconsistencies in defining APID in NR-10 & NR-12, preference shall be given to NR-12 ECSS-E-70-41A with related applicable CCSDS TM/TC packets standards Informative References Informative References (IR) are applicable to this document only when specifically called up in the text with references to specific parts of the document that are to be applicable. Otherwise the documents below are listed for information and as an aid for understanding. For the explicit, dated or versioned, references, subsequent amendments to, or revisions of, any of those references do not apply to this document. Other Informative References are listed for information and as an aid for understanding. IR-1 Removed IR-2 ExoMars 2018 Mission and Systems Requirements Document (MSRD), EXM-M2-RSD-ESA IR-3 ExoMars Mission and System Requirements Document, EXM-MS-RS-ESA IR-4 ExoMars 2018 Mission Document Requirement List (DRL), EXM-MS-RS-ESA IR-5 Deleted

8 Page: 8/26 IR-6 Exomars 2018 Operations Interface Requirements Document (OIRD), EXM-G2-IRD-ESC IR-7 Deleted IR-8 ESA Tracking Station (ESTRACK) Facilities Manual (EFM) DOPS-ESTR-OPS-MAN-1001-OPS- ONN IR-9 ExoMars 2018 Mission Preparation and Operations Approach, EXM-GS-TNO-ESA Issue 2 IR-10 Deleted IR-11 Recommendation SFCG 30-1: Use of differential one way ranging tones in the MHz band for category-b SRS missions, July Effective date: 15 June,2011 IR-12 DSN telecommunications link design handbook, DSN No , JPL D-19379

9 Page: 9/26 2 RF LINK REQUIREMENTS All communications, covering all the mission phases, shall be compatible with the ECSS standards for communications, RF links and packet utilisation, as defined in [NR-1], ECSS-E-50-05C Rev2 [NR-20], ECSS-E-70-41A [NR-12]. As far as the contents of the former do not cover regulations addressed in CCSDS standards [NR-9 to NR-10] compatibility with the latter shall be mandatory. 2.1 Ground Station Support GS-1 GS-2 GS-3 GS-4 GS-5 GS-6 GS-7 GS-8 GS-9 GS-10 GS-11 GS-12 GS-13 GS-14 GS-15 GS-16 GS-17 GS-18 GS-19 Any RF link with the Exomars 2018 Carrier Module shall be compatible with the features of the ESTRACK Network as described in [IR-8], NASA Deep Space Network as described in [IR-12] and Russian Deep Space Network (reference document to be defined) while allowing for the implementation of turbo codes. LEOP shall be supported through the ESA Deep Space Antenna Station Network, and LEOP Station Network Nominal post LEOP support shall be supported through the ESA Deep Space Station Network. Post LEOP (backup) support shall nominally be provided through the ESA ESTRACK ground stations. Compatibility with the TNA-1500 Russian ground station at Bear s Lakes for TM, TC, Ranging and Doppler support is mandatory. Compatibility with the ESA DSA shall enable the use of Delta-DOR. During LEOP the Carrier shall be able to operate assuming 24 hours per day of contact with Ground Control. During Near Earth Commissioning the Carrier shall be able to operate assuming daily contact with Ground Control of 8 hrs/day. During the Interplanetary Cruise the Carrier shall be able to operate assuming three Ground Control contacts per week of 4 hours each for non-critical operations. During Mars Arrival and its preparation (incl. DM separation) the Carrier shall be able to operate assuming daily contact with Ground Control of 8 hrs/day. For the last week the contact duration is 20 hrs/day. Note1:The preparation period is estimated to be at least 12 weeks during which also Delta- DOR measurement will be performed TBW (if required) Deleted Deleted Deleted Deleted Deleted

10 Page: 10/26 GS-20 GS-21 GS-22: Deleted Level-1 safe mode (not ultimate safe mode) shall be recoverable by ESA ESTRACK ground stations only. 2.2 Frequencies FRQ-1 FRQ-1.1 FRQ-1.2 FRQ-1.3 FR-1.4 The design of the Exomars 2018 Carrier Module telecommunications system shall be based on the exploitation of RF links in X-band with the following conditions, ground-to-space link (uplink) shall be established in X-band. space-to-ground link (downlink) shall be established in X-band. Deleted (covered by IR [2] (M-SRD) SC-OR-10 TBC). FRQ-2 FRQ-3 FRQ-4 The frequencies exploited for uplink and downlink shall be adequately separated from the frequencies assigned to any other RF system, which may be used, during the active lifetime of Exomars Note: In order to additionally safeguard against potentially harmful interference: separation of assigned frequencies should exceed the criteria applicable to the process of international frequency coordination, and/or relevant transponder performance parameters should be superior to those assumed for international frequency coordination Individual X-band RF frequencies shall be assigned to the Exomars 2018 Carrier Module that may be active simultaneously, Note: The UHF Proximity Systems are excluded from this requirement. Deleted 2.3 Channel Formats All Communications Links CHF-1 The Telecommand format shall be compliant with the Packet Telecommand Standards [NR- 5,6,10]. CHF-1.1 The Managed Parameters, as listed in the standards, shall be defined in the SG-ICD in consultation with ESOC. These relate but are not limited to the following: Authentication use Randomisation of the transfer frame Error detecting and/or correcting mode PLOP used CLTU maximum length Segmentation or non segmentation

11 Page: 11/26 CHF-2 COP protocol used The Telemetry format shall be compliant with the CCSDS Packet Telemetry standards, [NR- 8,9,10] CHF-2.1 The Managed Parameters, as listed in the standards, shall be defined in the SG-ICD in consultation with ESOC. These relate but are not limited to the following: CHF-3 CHF-4 Error control coding Randomisation of the transfer frame Ranging will be required on the Carrier Module until Mars Arrival, and shall be supported through ESA stations. CHF-4.1 Tone/Code ranging signal shall be compatible with [NR-19]. In addition to tone/code ranging, compatibility with pseudo-noise Regenerative Ranging according to [NR-21] is required. Note 1: The ranging, Doppler and Delta DOR performance shall ensure the accuracy requirements for Orbit Determination: 1-σ Range random error for 2-way range 4 m 1-σ Range considered bias for 2-way range 20 m 1-σ 2-way Doppler random error (over 60 seconds) 0.1 mm/s 1-σ Doppler considered bias none 1-σ Delta-DOR random error 5 cm It can be assumed that 1/3 of the error budget is allocated to the GS, 1/3 to the carrier and 1/3 to the propagation elements (apportionment TBC). Note 2: Regenerative ranging according to [NR-21] shall be considered if the performance requirements in CHF.4-1 cannot be achieved by using only code ranging scheme as per [NR- 19]. The use of regenerative ranging will help to reduce the error component due to onboard group delay uncertainty of tone ranging. Only either regenerative PN ranging or tone/code ranging shall be operated at any given time. CHF-4.2 The Delta DOR capability shall be implemented according to [NR-18] using dedicated DOR tones and shall support Delta-DOR measurements. CHF-4.3 If the link budget permits, range measurements shall preferably be simultaneous with telemetry downlink during the duration of each ground control contact. It this is not possible dedicated ranging measurement sessions of a minimum of 30 minutes shall be appendant to any telemetry-only downlink session. 2.4 Modulation Uplink MOD-1 MOD-2 MOD-3 The telecommand modulation shall be compliant with the ECSS Radio Frequency and Modulation standard [NR-2] and the ECSS Ranging & Doppler Tracking standard [NR-11].

12 2.4.2 Downlink Page: 12/ General MOD-4 MOD-5 MOD-6 The telemetry modulation shall be compliant with the ECSS Radio Frequency and Modulation standard [NR-2] and CCSDS Radio Frequency and Modulation standard [NR-18]. Deleted (covered by [NR-2]) Beacon Tones DTE Communications Deleted 2.5 Data Rates DR-1 DR-2 DR-3 DR-4 DR-5 DR-6 DR-7 For a given link budget, an information rate shall be considered as supported, if and only if compliance is achieved with the relevant BER & FER specified in the IR [2] (M-SRD) Uplink data rates shall be selectable in the range bps to 4kbps Downlink data rates shall be selected in the range 8bps to TBD Mbps. 2.6 Channel Coding ENC-1 ENC-2 ENC-3 ENC-4 ENC-5 Any encoding methods applied shall be compliant with the ECSS standards and shall be defined in the SG-ICD Volume 1. Except for standard coding the selected method shall be justified by performance results achieved with pseudo random bit strings as well as simulated science and HKTM. It shall be possible to change the encoding scheme by telecommand without loss of data. 2.7 Satellite Antennas All requirements in this section have been deleted.

13 Page: 13/ Operational Utilisation Systems Operational Modes Modulation Modes TMM-1 The modulation modes shall be compliant with the ECSS and CCSDS Radio Frequency and Modulation standards [NR-20 and NR-18]] and the tailored ECSS Ranging & Doppler Tracking standard [NR-19] Transponder Modes TMO-1 TMO-2 TMO-3 TMO-4 It shall be possible to set the Carrier Module transponder to coherent or non-coherent mode. This shall be done by telecommand. When set to coherent mode, the Carrier Module transmitter shall operate coherent to the receiver as soon as the receiver is locked. If the receiver loses lock, the transmitter shall go to non-coherent state and return to coherent state as soon as the receiver is in lock again. When set to non-coherent mode, the Carrier Module transmitter shall stay non-coherent, irrespective of the receiver s lock status Transponder Operations Downlink Operations DL-1 DL-2 DL-3 It shall be possible on the Carrier Module to radiate the signal generated via any one antenna at a time Beacon Tones DMC Operations DL-4 DL-5 DL Uplink RX-1 Covered by FRQ-1.1 RX-2

14 Page: 14/26 RX-3 At any one time, the direct Ground to Carrier Module TC links shall be supported by one uplink frequency only Delta-DOR DOR-1 The transponders of the Exomars 2018 Carrier Module shall support Delta-DOR Changes of Data Rates DRC-1 Fixed sets of data rates shall be assigned to uplink and downlink operations. DRC-2 DRC-3 DRC-4 DRC-5 DRC-6 Data rates shall be selectable from these sets by transmitting a single telecommand. Data rates changes on the up- and downlink shall be independent of each other and not lead to a loss of data. It shall be possible to command the telemetry modulation index. It shall be possible to command the value of the ranging modulation index. without loss of data It shall be possible to command the value of the X-Band Delta DOR tones modulation index Changes of On-Board Antenna Assignments CHA-1 Switching the transponder to antenna assignments shall be executable by a single telecommand. CHA-2 Switches in the antenna switching matrix shall also be commandable individually by direct command.

15 Page: 15/26 3 PROTOCOLS AND PACKET DEFINITIONS 3.1 RF and Bit Lock PRO-1 PRO-2 PRO-3 The locking of the RF carrier and bit lock on board shall comply with the applicable ECSS standards [NR-20] and be compatible with the capabilities of the ESTRACK ground network [IR-08] relevant to the stations called up in the section 2.1 of this document. Carrier lock shall be maintained for the applicable minimum carrier loop SNR received onboard and for all anticipated Doppler shift and Doppler rate conditions. Bit Lock shall be maintained while commanding is ongoing with a bit transition density down to 3%, and the applicable link margin is not violated. 3.2 TM and TC Packet Structure PKT-1 The packet definition and usage shall meet the packet utilisation standard and the packet requirements as specified in [NR-12] and in the OIRD [IR-6]. PKT-2 Detailed definitions of all packets transferable across the RF links to and from Exomars 2018 Carrier Module shall be provided by the Prime Contractor in SGICD Volume 2 and 3. PKT Encoding TM and TC The encoding TM and TC requirements are defined in SGICD Volume Data Compression COM-1 COM-2 Compression techniques (e.g. lossy, lossless) may be applied to large data files. Such techniques shall meet CCSDS [NR-4] standards and be clearly defined in the SG-ICD. Note: Data compression is not foreseen on the Exomars 2018 Carrier Module. If data compression is used by any user, decompression will have to be performed by the user of compression (e.g. PIs or SOC). For compressed data the given BER and FER may affect the decompressed data QoS, This should be taken into account by any user of compression Deleted 3.5 Virtual Channels The Virtual Channels requirements are defined in [IR-6].

16 Page: 16/ Flow Control. FLC-1 The TM packet transmission down each TM link shall be carefully managed such that 1. no data coming from the mass memory is lost (i.e. it is flow controlled). 2. Real-time packets are downlinked in a timely manner. FLC-2 FLC-3 Deleted FLC-4 Deleted FLC-5 Deleted FLC-6 Deleted

17 Page: 17/26 4 SG-ICD CONTENTS REQUIREMENTS. 4.1 Documents DOC-1 DOC-1.1 Deleted DOC-1.2 Deleted DOC-1.3 Deleted DOC-2 DOC-3 DOC-4 Three SG-ICD volumes shall be produced. SG-ICD Volume 1: RF & Coding levels - shall be produced by the Prime contractor and contain the information related to the frequencies, modulation, bit rate etc of the RF carrier, bit stream and any stream encoding for the Exomars 2018 mission i.e. all Space to Earth RF links for all the elements. Note: This requirement is complemented by DOC-5. DOC-4.1 Deleted DOC-5 DOC-6 DOC-7 DOC-8 SG-ICD Volume 2: Generic Frame and Packet Level - Shall be produced and maintained by the Prime contractor. This Volume contains all TM/TC Frame details, plus the Packet level details for all and only those Packet Services which are applicable to all on-board packetised users (e.g. Service 1 for TC acknowledge, Service 5 for events, etc.). Note: On-board packetised users are all units which encode and decode TM and TC packets SG-ICD Volume 3: Individual TM/TC ICDs Shall be produced by the relevant subcontractor or PI team. Each on-board packetised user has its own TM/TC ICD, listing - at the same level as the SG-ICD Volume 2 - the Packet Services applicable to it. This includes standard services (e.g. Service 11, 12 for DMS) and private services. SG-ICD volume 1 book keeper role shall be assumed by ESOC and this document shall be a working interface control document under change control, with changes agreed between all parties. The contractor shall maintain the book keeper role of the SG-ICD volume 2 & 3 and it shall continue being a working ICD under change control, with changes agreed between all parties. All sub-system specific TM/TC ICDs shall be combined within volume 3 of the SG-ICD. These shall be delivered in a later design phase 4.2 Structure It is recommended that the following section types are included in the various volumes of the SG-ICDs, and completed appropriately to provide all the necessary information. This is not a rigid definition but it does contain place for all the needed information Volume 1 SG-ICD Volume 1, Space to Ground Interface Control Document. This defines the frequencies, modulations, link budgets, data stream encodings, etc, for the connection between ground and space RF equipment.

18 Page: 18/26 TABLE OF CONTENTS 1 INTRODUCTION AND SCOPE 1.1 Scope 1.2 Operations Scenario Cruise Entry, Descent and Landing Mars Surface 2 TELECOMMUNICATION SYSTEM 2.1 Down Link Frequencies Telemetry Channel Formats Ranging Signal DOR Tones Modulation Telemetry Bit Rates Coding 2.2 Up-Link (On-Board Reception) Frequencies Telecommand Format Standard Ranging Signal Code Ranging PN Regenerative Ranging Modulation Telecommand Bit Rates 3 OPERATIONAL UTILISATION 3.1 Operational Modes Modulation Modes Transponder Modes Antenna Switching 3.2 Command Operations Procedure (COP-1) 4 PERFORMANCE 4.1 Exomars 2018 Carrier Module Up Link Parameters (On-Board Reception) Down Link Parameters Transponder Requirements 4.2 Ground Stations Perth 15m, Australia or suitable LEOP replacement (New Norcia AA) Cebreros 35m, Spain New Norcia 35m, Australia Malargüe 35m, Argentina Bear's Lakes 64m, Russia Deleted Station Configuration 4.3 Required Links Required Link Performance Atmospheric Attenuation Solar Plasma & Solar Thermal Noise Ground Station Network Link Budget Formats and Definitions 4.4 RF Compatibility Test APPENDIX 1 LINK BUDGET FORMAT APPENDIX 2 TELEMETRY BIT/SYMBOL RATE DEFINITION A2.1 Concatenated encoding A2.2 Turbo encoding

19 Page: 19/ Volume 2 SG-ICD Volume 2, Generic TM and TC Frame & Packet Interface Control Document. This is a generic TM & TC ICD covering all the PUS services to be used by all packetised elements of the Exomars 2018 Composite and how the frames and packets are to be constructed for each of these services. TABLE OF CONTENTS 1 INTRODUCTION 2 REFERENCE DOCUMENTS 2.1 NORMATIVE REFERENCES 2.2 INFORMATIVE REFERENCES 3 TM/TC DOCUMENTATION ORGANISATION 4 SYNTHESIS OF THE TM/TC ICD'S 5 PACKET AND TRANSPORT FRAME STRUCTURE 5.1 TELECOMMAND SOURCE PACKETS Packet Header Packet Data Field 5.2 TELECOMMAND SEGMENTS Sequence Flags Multiplexer Access Point (MAP) Identifier Packet Aggregation 5.3 TELECOMMAND FRAME 5.4 TELEMETRY SOURCE PACKET Source Packet Header Packet Data Field 5.5 TELEMETRY TRANSFER FRAME 6 TM/TC SERVICES AND STRUCTURES For each service applicable to all packetised elements of the Exomars 2018 Composite, one section per service type, one sub-section per service sub-type 7 APPLICABILITY OF SERVICE TYPES AND SUB-TYPES APPENDIX 1 CONVENTIONS A1.1 BIT NUMBERING CONVENTIONS A1.2 FIELD ALIGNMENT CONVENTIONS A1.3 PACKET NUMBERING CONVENTIONS APPENDIX 2 APPLICATION PROCESS ID ASSIGNMENT APPENDIX 3 THE CRC CHECKSUM ALGORITHMS A3.1 CYCLIC REDUNDANCY CODE A3.2 XOR ROTATE ALGORITHM APPENDIX 4 ACRONYMS AND GLOSSARY OF TERMS A4.1 ACRONYMS A4.2 GLOSSARY OF TERMS APPENDIX 5 PARAMETER TYPES AND STRUCTURES A5.1 INTRODUCTION A5.2 ENCODING FORMATS OF PARAMETER TYPES A5.3 PARAMETER TYPE DEFINITIONS APPENDIX 6 STANDARD SPACECRAFT TIME SOURCE PACKET APPENDIX 7 IDLE PACKET STRUCTURE APPENDIX 8 ON-BOARD DATA COMPRESSION APPENDIX 9 ALLOCATION OF EVENT AND FAILURE IDs Volume 3 SG-ICD Volume 3, Individual TM & TC Interface Control Document.

20 Page: 20/26 This contains one sub-volume per module. This sub-volume may be further split per subsystem in order to keep its size manageable. The document should contain detailed information on each of the detailed TM and TC packets and parameters, including their generation conditions, use and constraints. TABLE OF CONTENTS 1. INTRODUCTION 2. REFERENCE DOCUMENTS 2.1 NORMATIVE REFERENCES 2.2 INFORMATIVE REFERENCES 3. GENERIC TM/TC ICD 3.1 APPLICABILITY OF THE SG-ICD TO SUB 3.2 ROUTING OF TM PACKETS 3.3 TC PACKET VERIFICATION 3.4 ON-BOARD TIME SYNCHRONISATION 3.4 OCTET ORDERING OF THE PACKET TRANSMISSION 4. GENERAL DESCRIPTION 4.1 SYSTEM OVERVIEW 4.2 RELATION TO OTHER SYSTEMS 4.3 FAULT DETECTION, ISOLATION AND RECOVERY 4.4 SUB-SYSTEM SOFTWARE MODES 5. TM & TC SERVICES AND PACKET STRUCTURE 5.1 TELECOMMANDS & TELEMETRY LIST This section shall list all TM and TC service types and subtypes implemented on the vehicle subsystem. 5.2 APPLICABILITY OF TM AND TC PER SOFTWARE MODE 5.3 TELECOMMAND AND TELEMETRY SOURCE PACKETS This section shall include for each TC: - its function/description - its detailed structure - its execution conditions and any constraint for use by ground - its effect on telemetry - each object shall be referenced by its database mnemonic This section shall include for each TM: - its function/description - its detailed structure - its generation conditions - each object shall be referenced by its database mnemonic 6. APPENDIX A ABBREVIATIONS 7. APPENDIX B FAILURE AND EVENT CODE CAUSE DESCRIPTION This appendix may become a stand-alone document referenced in SGICD Vol. 3 if it becomes too large. This document shall include for each failure code (service 1) and event (service 5) a description of the reported condition, its possible causes, and the associated action whenever taken on-board. Whenever possible, the document shall include specific references to other SW documentation describing the associated behaviour in detail. 4.3 Configuration and Change Control. The 3 volumes of the SG-ICD shall be kept under configuration control Volume 1 Volume 1 of the SG-ICD shall be written by the European Prime Contractor at the end of Phase B2. This shall then be passed over to ESA/ESOC who shall from Issue 1 onwards maintain this document under formal change control. All updates shall be agreed between the Prime Contractor and ESA Exomars 2018 Project//ESOC.

21 Page: 21/ Volume 2 Volume 2 of the SG-ICD shall be written by the Prime Contractor and delivered at the end of phase B2. It shall be kept under formal change control by the Prime Contractor with all updates agreed between the prime contractor and ESA Exomars 2018 Project//ESOC prior to implementation Volume 3 Volume 3 of the SG-ICD shall be written by the relevant Sub-Contrators and be provided by the Prime Contractor throughout the Phase C/D phase. It is linked directly to the carrier module databases and shall be generated from the carrier module database. The configuration control of this volume 3 is maintained with the carrier module database.

22 Page: 22/26 5 RF SUITCASE. Moved to IR [6] (OIRD) section 5.11.

23 Page: 23/26 6 SURFACE ASSETS RELAY REQUIREMENTS. REL-1: It shall be assumed for the purpose of the relay coverage study that operations of the two surface assets with the TGO will be supported by ESA ESTRACK and Roscosmos Ground Stations for two Earth station passes per day.

24 Page: 24/26 7 ACRONYMS AIV Assembly, Integration and Verification (on-ground) AP Application Process APID Application ID ACN Attitude Control and Navigation AOCS Attitude and Orbit Control System AUT Autonomy CCSDS Consultative Committee for Space Data Systems CPDU Command Pulse Distribution Unit CTR Control DM Descent Module DMC Descent Module Composite DMS Data Management Subsystem DSN NASA Deep Space Network DSA ESA Deep Space Antenna DSS ESA Deep Space Station Network DVC Device Commanding ECSS European Cooperation for Space Standardization EDLS Entry Descent and Landing Systems EDM EDL Demonstrator Module EQM Engineering Qualification Model (of spacecraft) ESA European Space Agency ESOC European Space Operations Centre ESP EDM Surface Platform EVRP Event Reporting EXM Exomars 2018 EXUM Exomars 2018 User Manual EXUMC EXOMARS 2018 User Manual Content EXUMD EXOMARS 2018 User Manual Delivery FD Flight Dynamics FDDB Flight Dynamics Data Base FDDC Flight Dynamics Database Content FDDD Flight Dynamics Database Delivery FER Frame Error Rate FID Function Identifier FMECA Failure Mode Effects Criticality Analysis FOM Flight Operations Manual FTA Fault Tree Analysis FTS in-flight Testing

25 Page: 25/26 GNC HKTM ICD ID IF INFT LEOP LSB MM MOC MOI MOIS MPS MSB NRO MTL NDIU OBCP OBMF OBMT OBSM OBSR OBSW OBTM PACK PERP PFM PI PID PN PRT PTXC PUS RAM RCS RD RF ROM Guidance Navigation and Control House Keeping Telemetry Interface Control Document Identification Interface In-Flight Testing Launch and Early Orbit Phase Least Significant Bit Memory Management Mission Operations Centre Mars Orbit Insertion Manufacturing & Operations Information System Mission Planning System Most Significant Bit NASA Relay Orbiter Mission Time Line Network Data Interface Unit On-Board Control Procedure On-Board Monitoring Function On-Board Mission Timeline On-Board Software Management On-Board Storage and Retrieval On-Board SoftWare On-Board Time Management Packet (Telecommand or Telemetry) Periodic Reporting Proto Flight Model (of spacecraft) Principal Investigator Parameter Identification Number Pseudo-Noise Packet Routing Table Packet Transmission Control Packet Utilisation Standard Random Access Memory Reaction Control System (of spacecraft) Reference Document Radio Frequency Read Only Memory

26 Page: 26/26 RTU S/C S2K SDB SDBC SDBD SDE SEU SG-ICD SG-IRD SID SLE SPR SRD SSMM SSR STR STRP SVF SVT TBC TBD TC TCV TGO TIM TM TPN UTC VC Remote Terminal Unit Spacecraft SCOS-2000 (SpaceCraft Operating System) Spacecraft Data Base Spacecraft Data Base Content Spacecraft Data Base Delivery Software Development Environment Single Event Upset Space to Ground Interface Control Document Space to Ground Interface Requirements Document Structure ID Satellite Link Extension Software Problem Report Software Requirements Document Solid State Mass Memory Solid State Recorder Star Tracker Statistic Reporting Software Validation Facility System Validation Test To Be Confirmed To Be Defined Telecommand Telecommand Verification Trace Gas Orbiter (Exomars 2016 Orbiter) Timing Telemetry Telemetry Packet Number Universal Time Coordinated Virtual Channel