1、BSI Standards PublicationBS EN 16603-70-31:2015Space engineering Groundsystems and operations Monitoring and control datadefinitionBS EN 16603-70-31:2015 BRITISH STANDARDNational forewordThis British Standard is the UK implementation ofEN 16603-70-31:2015.The UK participation in its preparation was
2、entrusted to Technical Committee ACE/68, Space systems and operations.A list of organizations represented on this committee can be obtained on request to its secretary.This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct appli
3、cation. The British Standards Institution 2015.Published by BSI Standards Limited 2015ISBN 978 0 580 86758 3 ICS 49.140 Compliance with a British Standard cannot confer immunity from legal obligations.This British Standard was published under the authority of the Standards Policy and Strategy Commit
4、tee on 31 January 2015.Amendments/corrigenda issued since publicationDate T e x t a f f e c t e dEUROPEAN STANDARD NORME EUROPENNE EUROPISCHE NORM EN 16603-70-31 January 2015 ICS 49.140 English version Space engineering - Ground systems and operations - Monitoring and control data definition Ingnier
5、ie spatiale - Systmes sol et oprations - Dfinition des donnes de commande et contrle Raumfahrttechnik - Bodensysteme und Bodenbetrieb - berwachung und Definitionen zu Steuerdaten This European Standard was approved by CEN on 23 November 2014. CEN and CENELEC members are bound to comply with the CEN/
6、CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC Management Cent
7、re or to any CEN and CENELEC member. This European Standard exists in three official versions (English, French, German). A version in any other language made by translation under the responsibility of a CEN and CENELEC member into its own language and notified to the CEN-CENELEC Management Centre ha
8、s the same status as the official versions. CEN and CENELEC members are the national standards bodies and national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hu
9、ngary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom. CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels 2015 CEN/CENELEC All rights of exploitatio
10、n in any form and by any means reserved worldwide for CEN national Members and for CENELEC Members. Ref. No. EN 16603-70-31:2015 EBS EN 16603-70-31:2015Table of contents Foreword 8 Introduction 8 1 Scope . 10 2 Normative references . 11 3 Terms, definitions and abbreviated terms 12 3.1 Terms from ot
11、her standards 12 3.2 Terms specific to the present standard . 12 3.3 Abbreviated terms. 13 4 Background and context 15 4.1 The space system model 15 4.2 Monitoring and control view of the SSM 16 4.2.1 Introduction . 16 4.2.2 Standard SSM definitions 16 4.2.3 Product-specific SSM tailoring 18 5 Conve
12、ntions 20 5.1 Data definition . 20 5.2 Railroad diagrams. 21 5.3 Case sensitivity . 22 5.4 Names 22 5.5 Data types 24 5.5.1 General . 24 5.5.2 Simple Data Types 25 5.5.3 Complex Data Types . 37 6 Monitoring and control data requirements . 38 6.1 Data exchange . 38 6.2 Specification of complex data t
13、ypes 39 6.2.1 General . 39 6.2.2 Activity call 39 EN 16603-70-31:2015 (E)BS EN 16603-70-31:20156.2.3 Expression 40 6.2.4 Interpretation function . 40 6.2.5 Procedure . 41 6.2.6 Synthetic parameter 41 6.2.7 Value set . 42 6.3 Product data . 42 6.3.1 Introduction . 42 6.3.2 Product configuration data
14、43 6.4 Data population 47 6.5 System element data 49 6.5.1 Introduction . 49 6.5.2 System element generic data 50 6.5.3 System data 51 6.5.4 Application process data . 53 6.5.5 Service data 55 6.5.6 MAP data 93 6.5.7 VC data . 93 6.5.8 Functions 94 6.5.9 Memory data . 95 6.5.10 Memory sub-block data
15、 . 95 6.5.11 Store data . 96 6.5.12 CPDU data 97 6.5.13 On/Off device data 97 6.5.14 Register load device data 98 6.5.15 Sensor data. 98 6.6 Reporting data 99 6.6.1 Introduction . 99 6.6.2 General . 99 6.6.3 Parameters . 101 6.6.4 Compound parameters . 104 6.6.5 Synthetic reporting data 106 6.6.6 Ch
16、ecking data . 106 6.7 Activities . 111 6.7.1 General . 111 6.7.2 Activity argument value set . 114 6.7.3 Activity execution data 114 6.7.4 Telecommands . 118 EN 16603-70-31:2015 (E)BS EN 16603-70-31:20156.7.5 Procedures . 123 6.8 Events 125 Annex A (informative) PUS service tailoring . 126 A.1 Intro
17、duction . 126 A.2 Telecommand verification service . 127 A.2.1 The PUS service model 127 A.2.2 Service tailoring data . 128 A.2.3 Service requests and reports 129 A.3 Device command distribution service 131 A.3.1 The PUS service model 131 A.3.2 Service tailoring data . 133 A.3.3 Service requests and
18、 reports 134 A.4 Housekeeping and diagnostic data reporting service 134 A.4.1 The PUS service model 134 A.4.2 Service tailoring data . 136 A.4.3 Service requests and reports 142 A.5 Parameter statistics reporting service . 148 A.5.1 The PUS service model 148 A.5.2 Service tailoring data . 148 A.5.3
19、Service requests and reports 150 A.6 Event reporting service . 151 A.6.1 The PUS service model 151 A.6.2 Service tailoring data . 152 A.6.3 Service requests and reports 152 A.7 Memory management service . 153 A.7.1 The PUS service model 153 A.7.2 Service tailoring data . 154 A.7.3 Service requests a
20、nd reports 156 A.8 Function management service 158 A.8.1 The PUS service model 158 A.8.2 Service tailoring data . 158 A.8.3 Service requests and reports 159 A.9 Time management service 159 A.9.1 The PUS service model 159 A.9.2 Service tailoring data . 160 A.9.3 Service requests and reports 160 A.10
21、On-board operations scheduling service . 161 EN 16603-70-31:2015 (E)BS EN 16603-70-31:2015A.10.1 The PUS service model 161 A.10.2 Service tailoring data . 162 A.10.3 Service requests and reports 164 A.11 On-board monitoring service . 169 A.11.1 The PUS service model 169 A.11.2 Service tailoring data
22、 . 169 A.11.3 Service requests and reports 173 A.12 Large data transfer service . 177 A.12.1 The PUS service model 177 A.12.2 Service tailoring data . 177 A.12.3 Service requests and reports 180 A.13 Packet forwarding control service . 182 A.13.1 The PUS service model 182 A.13.2 Service tailoring da
23、ta . 182 A.13.3 Service requests and reports 184 A.14 On-board storage and retrieval service . 187 A.14.1 The PUS service model 187 A.14.2 Service tailoring data . 188 A.14.3 Service requests and reports 192 A.15 Test service 195 A.15.1 The PUS service model 195 A.15.2 Service tailoring data . 195 A
24、.15.3 Service requests and reports 196 A.16 On-board operations procedure service 196 A.16.1 The PUS service model 196 A.16.2 Service tailoring data . 196 A.16.3 Service requests and reports 197 A.17 Event/action service 200 A.17.1 The PUS service model 200 A.17.2 Service tailoring data . 200 A.17.3
25、 Service requests and reports 202 Annex B (informative) Data type definitions . 204 B.1 Conventions 204 B.2 Comments 205 B.3 Data types and data items 205 B.3.1 Definitions . 205 B.3.2 EBNF Representation . 206 EN 16603-70-31:2015 (E)BS EN 16603-70-31:2015B.4 Activity Call . 214 B.5 EXPL - Expressio
26、n Language . 214 B.5.1 Definitions . 214 B.5.2 EBNF Representation . 216 B.6 IFL - Interpretation Function Language . 218 B.6.1 Definition . 218 B.6.2 EBNF Representation . 220 B.7 SPEL - Synthetic Parameter Expression Language 222 B.7.1 Definitions . 222 B.7.2 Bit-manipulation functions . 227 B.7.3
27、 EBNF Representation . 228 B.8 PLUTO Procedure Language. 232 B.9 VAL Value Language . 233 B.9.1 Definition . 233 B.9.2 EBNF Representation . 234 Bibliography . 236 Figures Figure 4-1: Example product delivery system element hierarchy 16 Figure 4-2: Monitoring and control knowledge associated with a
28、system element 18 Figure 5-1: Example railroad diagram . 21 Figure A-1 : Diagram convention for PUS packet structures . 127 Figure A-2 : Tailoring choices for the telecommand verification service 129 Figure A-3 : Tailoring choices for the device command distribution service 133 Figure A-4 : Tailorin
29、g choices for the housekeeping and diagnostic data reporting service (View 1) 137 Figure A-5 Tailoring choices for the parameter statistics reporting service . 149 Figure A-6 : Tailoring choices for the event reporting service . 152 Figure A-7 : Tailoring choices for the memory management service (V
30、iew 1) . 154 Figure A-8 : Tailoring choices for the function management service . 158 Figure A-9 : Tailoring choices for the time management service . 160 Figure A-10 : Tailoring choices for the on-board operations scheduling service (View 1) 162 Figure A-11 : Tailoring choices for the on-board moni
31、toring service (View 1) . 170 Figure A-12 : Tailoring choices for the large data transfer service (View 1) 178 Figure A-13 : Tailoring choices for the packet forwarding control service (View 1) 183 Figure A-14 : Tailoring choices for the on-board storage and retrieval service (View 1) 189 Figure A-1
32、5 : Tailoring choices for the on-board operations procedure service 197 EN 16603-70-31:2015 (E)BS EN 16603-70-31:2015Figure A-16 Tailoring choices for the event/action service 201 EN 16603-70-31:2015 (E)BS EN 16603-70-31:2015Foreword This document (EN 16603-70-31:2015) has been prepared by Technical
33、 Committee CEN/CLC/TC 5 “Space”, the secretariat of which is held by DIN. This standard (EN 16603-70-31:2015) originates from ECSS-E-ST-70-31C. This European Standard shall be given the status of a national standard, either by publication of an identical text or by endorsement, at the latest by July
34、 2015, and conflicting national standards shall be withdrawn at the latest by July 2015. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CEN and/or CENELEC shall not be held responsible for identifying any or all such patent right
35、s. This document has been prepared under a mandate given to CEN by the European Commission and the European Free Trade Association. This document has been developed to cover specifically space systems and has therefore precedence over any EN covering the same scope but with a wider domain of applica
36、bility (e.g. : aerospace). According to the CEN-CENELEC Internal Regulations, the national standards organizations of the following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republi
37、c of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. EN 16603-70-31:2015 (E)BS EN 16603-70-31:2015Introduction As
38、 described in ECSS-S-ST-00 and ECSS-E-ST-10, the development of a space system is an incremental task involving different entities, who can participate as customer or supplier at different levels of space system integration. Documentation and data of different types is exchanged between supplier and
39、 customer. The purpose of this Standard is to define the data to be provided by the supplier to the customer in order to be able to monitor and control the product delivered. Formally, this data is part of the user manual for the corresponding element of the space system (see ECSS-E-ST-70). EN 16603
40、-70-31:2015 (E)BS EN 16603-70-31:20151 Scope This Standard defines the monitoring and control data that a supplier delivers together with a product in order to allow a customer to perform space system integration, testing and mission operations. The requirements in this Standard are defined in terms
41、 of what data is provided by the supplier to the customer. How this data is provided (e.g. using spreadsheet data or XML) is outside of scope. The Standard assumes that missions conform to the following ECSS standards: ECSS-E-ST-50 and ECSS-E-ST-70; ECSS-E-ST-70-41; ECSS-E-ST-70-32. This standard ma
42、y be tailored for the specific characteristics and constrains of a space project in conformance with ECSS-S-ST-00. EN 16603-70-31:2015 (E)BS EN 16603-70-31:20152 Normative references The following normative documents contain provisions which, through reference in this text, constitute provisions of
43、this ECSS Standard. For dated references, subsequent amendments to, or revision of any of these publications do not apply, However, parties to agreements based on this ECSS Standard are encouraged to investigate the possibility of applying the more recent editions of the normative documents indicate
44、d below. For undated references, the latest edition of the publication referred to applies. EN reference Reference in text Title EN 16603-50 ECSS-E-ST-50 Space engineering - Communications EN 16603-70 ECSS-E-ST-70 Space engineering - Ground systems and operations - EN 16603-70-01 ECSS-E-ST-70-01 Spa
45、ce engineering - On board control procedures EN 16603-70-11 ECSS-E-ST-70-11 Space engineering - Space segment operability EN 16603-70-32 ECSS-E-ST-70-32 Space engineering - Test and operations procedure language EN 16603-70-41 ECSS-E-ST-70-41 Space engineering - Telemetry and telecommand packet util
46、ization EN 16603-70-31:2015 (E)BS EN 16603-70-31:20153 Terms, definitions and abbreviated terms 3.1 Terms from other standards For the purpose of this Standard, the terms and definitions from ECSS-S-ST-00-01 and ECSS-E-ST-70 apply, in particular for the following terms: anomaly assembly availability
47、 contingency procedure emergency mission procedure space system subsystem system test validation verification 3.2 Terms specific to the present standard 3.2.1 activity space system monitoring and control function 3.2.2 compound parameter record comprised of any sequence of reporting data, arrays of
48、reporting data and sub-records that are interpreted together NOTE E.g.: an anomaly report generated by the space segment comprising an anomaly report ID and a set of associated parameters. EN 16603-70-31:2015 (E)BS EN 16603-70-31:20153.2.3 event occurrence of a condition or set of conditions that ca
49、n arise during the course of a test session or mission phase 3.2.4 parameter lowest level of elementary information that has a meaning for monitoring the space system 3.2.5 reporting data data used for assessing the functioning of the space system NOTE Reporting data can consist of a parameter (a simple type) or a compound parameter (a complex type). 3.2.6 resource stock or supply, either depletable or shareable in nature, that can be drawn upon, or provided by, an element of the space system during operation 3.2.7 space system model representation of the space syste
