1、Space engineering - Telemetry and telecommand packet utilizationBS EN 166037041:2017BSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06EUROPEAN STANDARD NORME EUROPENNE EUROPISCHE NORM EN 16603-70-41 October 2017 ICS 49.140 Supersedes EN 14776:2004 English version Space
2、 engineering - Telemetry and telecommand packet utilization Ingnierie spatiale - Utilisation de la tlmtrie et de la tlcommande par paquets Raumfahrttechnik - Telemetrie und Telekommando This European Standard was approved by CEN on 30 June 2017. CEN and CENELEC members are bound to comply with the C
3、EN/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 C
4、entre 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
5、 has 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,
6、 Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom. CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels 2017 CEN/CENELEC All rights of
7、exploitation in any form and by any means reserved worldwide for CEN national Members and for CENELEC Members. Ref. No. EN 16603-70-41:2017 ENational forewordThis British Standard is the UK implementation of EN 166037041:2017.The UK participation in its preparation was entrusted to Technical Committ
8、ee 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 application. The British Standards
9、Institution 2017 Published by BSI Standards Limited 2017ISBN 978 0 580 95152 7ICS 49.140Compliance 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 October 2017.Amendment
10、s/corrigenda issued since publicationDate Text affectedBRITISH STANDARDBS EN 166037041:2017EUROPEAN STANDARD NORME EUROPENNE EUROPISCHE NORM EN 16603-70-41 October 2017 ICS 49.140 Supersedes EN 14776:2004 English version Space engineering - Telemetry and telecommand packet utilization Ingnierie spat
11、iale - Utilisation de la tlmtrie et de la tlcommande par paquets Raumfahrttechnik - Telemetrie und Telekommando This European Standard was approved by CEN on 30 June 2017. CEN and CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving
12、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 Centre or to any CEN and CENELEC member. This European Standard exists in t
13、hree 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 has the same status as the official versions. CEN and CENELEC members are
14、 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, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, N
15、etherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom. CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels 2017 CEN/CENELEC All rights of exploitation in any form and by any means reserved worldwide for CEN natio
16、nal Members and for CENELEC Members. Ref. No. EN 16603-70-41:2017 EBS EN 166037041:2017EN 16603-70-41:2017 (E) 2 Table of contents European Foreword . 6 Introduction 8 1 Scope . 9 2 Normative references . 11 3 Terms, definitions and abbreviated terms 12 3.1 Terms from other standards 12 3.2 Terms sp
17、ecific to the present standard . 12 3.3 Abbreviated terms. 16 3.4 Nomenclature . 17 4 Context and background . 18 4.1 Introduction . 18 4.2 Modelling the PUS 21 5 The PUS foundation model 25 5.1 Introduction . 25 5.2 Convention . 26 5.3 The generic service type abstraction level 26 5.4 The generic s
18、ervice deployment abstraction level . 38 6 Service type system requirements . 55 6.1 ST01 request verification 55 6.2 ST02 device access 63 6.3 ST03 housekeeping 76 6.4 ST04 parameter statistics reporting 109 6.5 ST05 event reporting 119 6.6 ST06 memory management . 124 6.7 ST07 (reserved) 153 6.8 S
19、T08 function management 153 6.9 ST09 time management 155 6.10 ST10 (reserved) 161 BS EN 166037041:2017EN 16603-70-41:2017 (E) 3 6.11 ST11 time-based scheduling 161 6.12 ST12 on-board monitoring 191 6.13 ST13 large packet transfer 221 6.14 ST14 real-time forwarding control . 229 6.15 ST15 on-board st
20、orage and retrieval . 256 6.16 ST16 (reserved) 308 6.17 ST17 test 308 6.18 ST18 on-board control procedure . 311 6.19 ST19 event-action . 331 6.20 ST20 parameter management 341 6.21 ST21 request sequencing . 347 6.22 ST22 position-based scheduling . 357 6.23 ST23 file management 390 7 Space to groun
21、d interface requirements 412 7.1 Introduction . 412 7.2 Convention . 414 7.3 Packet field type code . 415 7.4 The CCSDS Space Packet . 425 8 Service type interface requirements . 432 8.1 ST01 request verification 432 8.2 ST02 device access 437 8.3 ST03 housekeeping 442 8.4 ST04 parameter statistics
22、reporting 459 8.5 ST05 event reporting 462 8.6 ST06 memory management . 465 8.7 ST07 (reserved) 475 8.8 ST08 function management 475 8.9 ST09 time management 476 8.10 ST10 (reserved) . 478 8.11 ST11 time-based scheduling 478 8.12 ST12 on-board monitoring 490 8.13 ST13 large packet transfer 507 8.14
23、ST14 real-time forwarding control . 510 8.15 ST15 on-board storage and retrieval . 520 8.16 ST16 (reserved) . 538 8.17 ST17 test 538 BS EN 166037041:2017EN 16603-70-41:2017 (E) 4 8.18 ST18 on-board control procedure . 540 8.19 ST19 event-action . 548 8.20 ST20 on-board parameter management . 552 8.2
24、1 ST21 request sequencing . 556 8.22 ST22 position-based scheduling . 561 8.23 ST23 file management 574 9 Command Pulse Distribution Unit 584 9.1 Scope . 584 9.2 System requirements 584 9.3 Interface requirements 586 Annex A (informative) IEEE and MIL-STD real formats 588 A.1 IEEE standard format .
25、588 A.1.1 General . 588 A.1.2 Single-precision 589 A.1.3 Double-precision . 589 A.2 United States Air Force military standard format . 591 A.2.1 General . 591 A.2.2 Simple-precision . 591 A.2.3 Extended . 592 Annex B (informative) CRC and ISO checksum 593 B.1 The cyclic redundancy code (CRC) 593 B.1
26、.1 General . 593 B.1.2 Symbols and conventions . 594 B.1.3 Encoding procedure 594 B.1.4 Decoding procedure 594 B.1.5 Verification of compliance . 595 B.1.6 Software implementation . 595 B.2 The ISO checksum . 604 B.2.1 General . 604 B.2.2 Symbols and conventions . 605 B.2.3 Encoding procedure 605 B.
27、2.4 Decoding procedure 606 B.2.5 Verification of compliance . 606 B.2.6 Software implementation . 606 Annex C (informative) Summary of requests and reports for PUS standard services 612 BS EN 166037041:2017EN 16603-70-41:2017 (E) 5 C.1 Convention . 612 C.2 Requests and reports . 612 C.2.1 ST01 reque
28、st verification . 612 C.2.2 ST02 device access 614 C.2.3 ST03 housekeeping 615 C.2.4 ST04 parameter statistics reporting . 617 C.2.5 ST05 event reporting . 618 C.2.6 ST06 memory management 619 C.2.7 ST07 (reserved) . 621 C.2.8 ST08 function management 621 C.2.9 ST09 time management 621 C.2.10 ST10 (
29、reserved) . 622 C.2.11 ST11 time-based scheduling . 622 C.2.12 ST12 on-board monitoring . 624 C.2.13 ST13 large packet transfer 625 C.2.14 ST14 real-time forwarding control . 626 C.2.15 ST15 on-board storage and retrieval . 628 C.2.16 ST16 (reserved) 630 C.2.17 ST17 test 631 C.2.18 ST18 on-board ope
30、rations procedure 631 C.2.19 ST19 event-action . 633 C.2.20 ST20 Parameter management 634 C.2.21 ST21 request sequencing . 634 C.2.22 ST22 position-based scheduling . 636 C.2.23 ST23 file management 638 Annex D (informative) System and interface specification index 640 Bibliography . 641 BS EN 16603
31、7041:2017EN 16603-70-41:2017 (E) 6 European Foreword This document (EN 16603-70-41:2017) has been prepared by Technical Committee CEN-CENELEC/TC 5 “Space”, the secretariat of which is held by DIN. This standard (EN 16603-70-41:2017) originates from ECSS-E-ST-70-41C. This European Standard shall be g
32、iven the status of a national standard, either by publication of an identical text or by endorsement, at the latest by April 2018, and conflicting national standards shall be withdrawn at the latest by April 2018. This document supersedes EN 14776:2004 Space engineering Ground systems and operations
33、 - Telemetry and telecommand packet utilization. The main purpose of the update of EN 14776:2004 was the need: to remove the deficiencies of the previous issue and to inject lessonslearned, to improve the standard to meet the need for future missions, to acknowledge the existence of new ECSS and CCS
34、DS standards and toensure consistency, to implement the updated drafting rules that apply to any ECSSStandards (e.g. naming each requirement to facilitate tailoring,traceability), maintaining backward compatibility when possible.The main changes are: the introduction of the PUS foundation model that
35、: has been used to produce the “standard service types”; shall be used to produce the “mission-specific service types”, i.e.: adding new service types, subservice types, message types,etc; adding capabilities to the ”standard service types”; shall be used to produce the “mission services”, i.e.: cre
36、ating the required services by: “realising the service types”, and inheriting all mandatory subservices and minimumcapabilities; selecting, for each service, the additional capabilities, theoptional subservices, etc; creating the service specific definitions.BS EN 166037041:2017EN 16603-70-41:2017 (
37、E) 7 a proper separation of system versus interface requirements. material common to the three ECSS branches (Space engineering, Space project management and Space product assurance moved to EN 16601-00 (EN version of ECSS-S-ST-00), material specific to product assurance to this standard, reorganiza
38、tion of the content of the document to separate descriptive text and requirements, including clarification, modification of requirements and implementation of change requests, pre-tailoring matrix (Clause 6) added, addition of new DRDs. Attention is drawn to the possibility that some of the elements
39、 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 standardization request given to CEN by the European Commission and the European Free Trade Association. This
40、 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 national standards organizations of the following coun
41、tries 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, Lithuania, Luxembourg, Malta, Netherlands, Norway, Po
42、land, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. BS EN 166037041:2017EN 16603-70-41:2017 (E) 8 Introduction The CCSDS Space Packet Protocol (CCSDS 133.0-B-1) and the ECSS-E-ST-50 series of standards address the end-to-end transport of te
43、lemetry and telecommand data between user applications on the ground and application processes on-board the spacecraft, and the intermediate transfer of these data through the different elements of the ground and space segments. This packet utilization standard (PUS) complements those standards by d
44、efining the application-level interface between ground and space, in order to satisfy the requirements of electrical integration and testing and flight operations. BS EN 166037041:2017EN 16603-70-41:2017 (E) 9 1 Scope This Standard addresses the utilization of telecommand packets and telemetry packe
45、ts for the purposes of remote monitoring and control of spacecraft subsystems and payloads. This Standard does not address mission-specific payload data packets, but the rules contained herein can be extended to suit the requirements of any mission. This Standard does not address audio and video dat
46、a as they are not contained within either telecommand or telemetry packets. This Standard defines a set of services that satisfy all the fundamental operational requirements for spacecraft monitoring and control during spacecraft integration, testing and flight operations, refer to ECSS-E-ST-70-11.
47、It also specifies the structure and contents of the telecommand packets used to transport the requests and the telemetry packets used to transport the reports. This Standard can be used by any mission, no matter what its domain of application, orbit or ground station coverage characteristics. Howeve
48、r, it is not the intention that the PUS should be applied in its entirety to a given mission. The services defined in this Standard cover a wide spectrum of operational scenarios and, for a given mission, only a subset of these services is likely to be appropriate. Choices are made early in the desi
49、gn phase of a new mission resulting in the need to tailor the PUS to suit the requirements of that mission. These choices include: the on-board system design and architecture, in terms of the number of on-board application processes, their on-board implementation (e.g. the allocation to on-board processors) and their roles (i.e. which functions or subsystems or payload
