1、BSI Standards PublicationBS EN 16603-70-01:2015Space engineering On-boardcontrol proceduresBS EN 16603-70-01:2015 BRITISH STANDARDNational forewordThis British Standard is the UK implementation ofEN 16603-70-01:2015.The UK participation in its preparation was entrusted to Technical Committee ACE/68,
2、 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 application. The British Standards Institutio
3、n 2015.Published by BSI Standards Limited 2015ISBN 978 0 580 86759 0 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 Committee on 31 January 2015.Amendments/corrig
4、enda issued since publicationDate T e x t a f f e c t e dEUROPEAN STANDARD NORME EUROPENNE EUROPISCHE NORM EN 16603-70-01 January 2015 ICS 49.140 English version Space engineering - On-board control procedures Ingnierie spatiale - Procdures automatiques de contrle bord Raumfahrtproduktsicherung - Bo
5、rdseitige Kontrollprozeduren This European Standard was approved by CEN on 23 November 2014. CEN and CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration
6、. Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN and CENELEC member. This European Standard exists in three official versions (English, French, German). A version in any other langua
7、ge made by translation under the responsibility of a CEN and CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the same status as the official versions. CEN and CENELEC members are the national standards bodies and national electrotechnical committees of Aust
8、ria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Swede
9、n, Switzerland, Turkey and United Kingdom. CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels 2015 CEN/CENELEC All rights of exploitation in any form and by any means reserved worldwide for CEN national Members and for CENELEC Members. Ref. No. EN 16603-70-01:2015 EBS EN 16603-70-01:20
10、15Table of contents Foreword 4 Introduction 4 1 Scope . 6 2 Normative references . 7 3 Terms, definitions and abbreviated terms 8 3.1 Terms from other standards 8 3.2 Terms specific to the present standard . 8 3.3 Abbreviated terms. 9 4 The OBCP concept . 11 4.1 Introduction . 11 4.2 Stakeholders an
11、d application areas for OBCPs 11 4.2.1 Stakeholders . 11 4.2.2 Domains of OBCP application . 12 4.3 Types of OBCP . 13 4.4 The OBCP system 14 5 OBCP system capabilities . 17 5.1 OBCP structure 17 5.2 OBCP language capabilities . 18 5.2.1 Introduction . 18 5.2.2 General . 18 5.2.3 Data types . 18 5.2
12、.4 Declarations 19 5.2.5 Assignments . 19 5.2.6 Expressions 19 5.2.7 Flow controls . 20 5.2.8 Waits . 20 5.2.9 External interactions 21 5.2.10 Contingency handling 22 5.3 The OBCP preparation environment . 22 EN 16603-70-01:2015 (E)BS EN 16603-70-01:20155.3.1 OBCP script preparation . 22 5.3.2 Synta
13、x analysis, consistency, dependency and constraint checking . 23 5.3.3 Report generation . 23 5.3.4 Verification and validation . 23 5.3.5 OBCP characterisation 24 5.4 The OBCP execution environment 25 5.4.1 Ground capabilities . 25 5.4.2 OBCP monitoring and control 25 5.4.3 OBCP integrity 28 5.4.4
14、On-board capabilities 28 6 OBCP engineering processes . 33 6.1 Introduction . 33 6.2 Overall management process of the OBCP system 34 6.2.1 Management process 34 6.2.2 OBAP vs. OBSW: criteria and trade-off analysis . 37 6.2.3 OBOP vs. ground-based operations 38 6.2.4 Trade-off between OBCP engine ca
15、pability and engineering effort . 39 6.2.5 Overall organization and management 39 6.3 OBCP engineering 40 Bibliography . 41 Figures Figure 4-1 The OBCP system. 15 Figure 5-1: OBCP state diagram 26 Figure 6-1: Lifecycles of OBCPs originating from the different domains . 34 Figure 6-2: OBCP management
16、 overview 36 Figure 6-3: Synchronisation of OBAP lifecycles with system and OBSW lifecycles 36 EN 16603-70-01:2015 (E)BS EN 16603-70-01:2015Foreword This document (EN 16603-70-01:2015) has been prepared by Technical Committee CEN/CLC/TC 5 “Space”, the secretariat of which is held by DIN. This standa
17、rd (EN 16603-70-01:2015) originates from ECSS-E-ST-70-01C. 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 2015, and conflicting national standards shall be withdrawn at the latest by July 20
18、15. 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 rights. This document has been prepared under a mandate given to CEN by the European Commi
19、ssion 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 applicability (e.g. : aerospace). According to the CEN-CENELEC Internal Regulations, the nat
20、ional 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 Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Li
21、thuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. EN 16603-70-01:2015 (E)BS EN 16603-70-01:2015Introduction On-board control procedures (OBCPs) have been implemented on an ad-hoc basis on several
22、 European missions over the last 25 years, so the validity and utility of the concept has been amply demonstrated. The purpose of the present Standard is to define an OBCP concept that can be applied for any mission and which: fulfils the needs of all categories of user (system engineers, on-board s
23、oftware engineers, AIT engineers, operations engineers); ensures that OBCPs have a development lifecycle that is independent of the remainder of the on-board software (OBSW);. conforms with, and extends, existing ECSS monitoring and control standards, namely ECSS-E-70-41 and ECSS-E-ST-70-31. EN 1660
24、3-70-01:2015 (E)BS EN 16603-70-01:20151 Scope This Standard defines the concept for an OBCP system, identifying the on-board functionality for OBCP execution and the ground functionality for OBCP preparation and subsequent control. This Standard also defines the development lifecycle for OBCPs and i
25、dentifies the relationships of this lifecycle with the overall space system, and in particular with the other elements of the on-board software. This Standard assumes that missions implementing OBCPs are also compliant with ECSS-E-70-41, since a number of services contained therein are invoked in su
26、pport of the operation of OBCPs and their interaction with the ground. This Standard may be tailored for the specific characteristic and constraints of a space project in conformance with ECSS-S-ST-00. EN 16603-70-01:2015 (E)BS EN 16603-70-01:20152 Normative references The following normative docume
27、nts contain provisions which, through reference in this text, constitute provisions of 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 t
28、he possibility of applying the more recent editions of the normative documents indicated below. For undated references, the latest edition of the publication referred to applies. EN reference Reference in text Title EN 16601-00-01 ECSS-S-ST-00-01 ECSS system - Glossary of terms EN 16603-40 ECSS-E-ST
29、-40 Space engineering - Software EN 16603-70 ECSS-E-ST-70 Space engineering - Ground systems and operations EN 16603-70-31 ECSS-E-ST-70-31 Space engineering - Ground systems and operations - Monitoring and control data definition EN 16603-70-41 ECSS-E-70-41 Space engineering - Ground systems and ope
30、rations - Telemetry and telecommand packet utilization EN 16603-70-01:2015 (E)BS EN 16603-70-01:20153 Terms, definitions and abbreviated terms 3.1 Terms from other standards For the purpose of this Standard, the terms and definitions from ECSS-ST-00-01, ECSS-E-ST-70, ECSS-E-ST-70-31 and ECSS-E-70-41
31、 apply, in particular for the following terms: activity event event reporting service ground system on-board parameter operations procedure space project spacecraft 3.2 Terms specific to the present standard 3.2.1 automation replacement of manual operations by computerized mechanisms 3.2.2 on-board
32、control procedure software program designed to be executed by an OBCP engine, which can easily be loaded, executed, and also replaced, on-board the spacecraft NOTE Depending on the context, OBCP can refer to an OBCP in program source code form, or in OBCP code. 3.2.3 OBCP code complete representatio
33、n of an OBCP, in a form that can be loaded on-board for subsequent execution NOTE 1 In previous missions, such code is typically referred to as token code, executable code or bytecode depending on the implementation of the relevant OBCP engine. EN 16603-70-01:2015 (E)BS EN 16603-70-01:2015NOTE 2 In
34、service 18 of ECSS-E-70-41A, OBCP code is referred to as procedure code. 3.2.4 OBCP engine application of the on-board software handling the execution of OBCPs NOTE OBCP operations are initiated by means of ECSS-E-70-41 Service 18 telecommands. 3.2.5 OBCP language programming language in which OBCP
35、source code is expressed by human programmers 3.2.6 OBCP system the entire machinery for the creation (in the ground system), uplinking, and on-board handling of OBCPs 3.2.7 OBCP step sequence of OBCP source code statements constituting the smallest operational unit within an OBCP 3.2.8 on-board sof
36、tware software hosted and executed by any programmable on-board computer or processor 3.2.9 scheduling controlling the allocation of OBSW processor (CPU) time for execution of the various OBSW functions, according to a predefined algorithm NOTE OBSW functions include the OBCP engine and execution of
37、 OBCPs. 3.2.10 survival mode configuration of a spacecraft in which it can remain safely without ground segment intervention for a specified period NOTE Survival mode is also commonly known as safe mode. In survival mode, typically all non-essential on-board units or subsystems are powered off, eith
38、er to conserve power or to avoid interference with other subsystems, and the spacecraft can be (automatically) oriented to a particular attitude with respect to the sun. 3.3 Abbreviated terms The following abbreviations are defined and used within this standard: Abbreviation Meaning AIT assembly, in
39、tegration and test EN 16603-70-01:2015 (E)BS EN 16603-70-01:2015AOCS attitude and orbit control subsystem AR acceptance review CDR critical design review CPDU command pulse distribution unit CPU central processor unit DDR detailed design review EBNF extended Backus-Naur form EEPROM electrically eras
40、able programmable read-only memory EGSE electrical ground support equipment FDIR failure detection, isolation and recovery I/O input/output MCS mission control system OBAP on-board application procedure OBCP on-board control procedure OBOP on-board operations procedure OBSW on-board software PDR pre
41、liminary design review QR qualification review RAM random access memory SDE software development environment SRR system requirements review TRR test results review EN 16603-70-01:2015 (E)BS EN 16603-70-01:20154 The OBCP concept 4.1 Introduction The OBCP concept is that of a procedure to be executed
42、on-board, which can easily be loaded, executed, and also replaced, on-board the spacecraft without modifying the remainder of the on-board software. 4.2 Stakeholders and application areas for OBCPs 4.2.1 Stakeholders Several categories of OBCP stakeholder are identified, each of whom has a distinct
43、role in a space project, with corresponding responsibilities: System engineers (spacecraft and payload); On-board software engineers; AIT engineers; Operations engineers. There is continuous interaction and cooperation between these stakeholders throughout the development and operation lifecycle of
44、a space system, for example: during the spacecraft design phase, operations engineers are involved to ensure the operability of the overall space system; during in-orbit operations, system and software engineers support commissioning and troubleshooting activities. The system or software responsibil
45、ity may be transferred from the satellite prime contractor to the operations organization at some predetermined time after launch (e.g. in the case of long-duration missions). The potential uses for OBCPs are therefore categorized in clause 4.2.2 according to the domain of application rather than st
46、akeholder category. EN 16603-70-01:2015 (E)BS EN 16603-70-01:20154.2.2 Domains of OBCP application 4.2.2.1 System design Typical scenarios where it may be decided to implement on-board functionality as OBCPs rather than as OBSW include: Platform functions To isolate mission-specific platform functio
47、ns from the remainder of the OBSW, e.g. thermal control or battery control. To implement one-shot applications that are deleted after use, e.g. deployment of appendices, firing of pyrotechnics. To accommodate the late specification of the detailed FDIR strategy and to facilitate the tuning of this s
48、trategy during system testing. NOTE It is not the intention to encourage the late definition of the FDIR strategy, but rather to accommodate the reality that the detailed strategy is often late. The decision about whether or not to use OBCPs for FDIR purposes is part of the trade-off addressed in de
49、tail in clause 6. To accommodate the late delivery of, or the subsequent removal, addition or replacement of equipment. To facilitate the tuning of on-board configuration sequences for complex equipment or subsystems following system testing, i.e. these sequences are modified directly avoiding the delays inherent in OBSW modification. Payload functions To accommodate the late definition and tuning of: o complex payload configuration or control sequences; o monitoring algorithms and recovery actions. 4.2.2.2 On-board software design and development
