1、ETSI EN 301 927 1.1.1 (2003-02) European Sfandard (Telecommunicafions 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 VI .I .I (2003-02) Reference DEN/SES-OOO-ECSS-2 Keyw
2、ords data, intetface, LAYER 7, satellite, service ETSI 650 Route des Lucioles F-O6921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 O0 Fax: +33 4 93 65 47 16 Siret No 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-prfecture de Grasse (06) No 7803/88 Important no
3、tice Individual copies of the present document can be downloaded from: http:lwmv.etsi .arq 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 Porta
4、ble 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
5、 on the current status of this and other ETSI documents is available at ha p:/pa rta I. etsi I a rgltbistat uslstatus .as p If you find errors in the present document, send your comment to: Cori vriaht Notifica tion No part may be reproduced except as authorized by written permission. The copyright
6、and the foregoing restriction extend to reproduction in all media. O European Telecommunications Standards Institute 2003. All rights reserved. DECTTM, PLUGTESTSTMand UMTSTMare Trade Marks of ETSI registered for the benefit of its Members. TIPHONTM and the TIPHON logo are Trade Marks currently being
7、 registered by ETSI for the benefit of its Members. 3GPPTM 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 VI .I .I (2003-02) Contents Intellectual Property Rights . .5 Foreword . 5 Introduction . .5 1 2 3 3.1 3.2 4 5
8、5.1 5.2 5.3 6 6.1 6.2 6.2.1 6.2.2 6.3 7 7.1 7.2 7.2.1 7.2.2 7.2.3 7.2.4 7.2.5 7.3 7.3.1 Scope 6 References . .6 Definitions and abbreviations. . .6 Definitions . . 6 Abbreviations . 8 Applicability. . .8 Recommendation guidelines . .9 . . 9 . 9 d services with respect to other standards .10 Objectiv
9、es. Interface cover Position of the Introduction . . 12 Conventions . . 12 . 12 . 13 Standard services . . 13 Services 16 Memory Management Service . 16 Units power switching and resetting services . 18 Device power switch-on service . 18 Service specification .12 Service primitive naming . Paramete
10、r type and format abbreviations . 7.3.1.1 7.3.1.1.1 7.3.1.1.2 7.3.1.1.3 7.3.1.1.4 7.3.1.1.5 7.3.1.1.6 7.3.1.2 7.3.1.2.1 7.3.1.2.2 7.3.1.2.3 7.3.1.2.4 7.3.1.2.5 7.3.1.2.6 7.3.1.2.7 7.3.1.2.8 7.3.1.3 7.3.1.3.1 7.3.1.3.2 7.3.1.3.3 7.3.2 7.3.2.1 Device power switch-off service . Device reset service . D
11、evice arming service . Function enabling service Platform Sensor and Actuator services . 18 . 19 . 19 . 20 . 21 Accelerometer service . 21 Star tracker service . . 23 Earth sensor service .24 Sun Sensor service . 26 Specific services. . . 21 Specific sensors . 21 Gyro service . .22 Magnetometer serv
12、ice . 26 Specific actuator . . 27 Tlmster configuration service . 27 Venting service. .27 Apogee Boost Motor service . 28 Tlmster burst service . 29 Plasmic Propulsion se . 30 Wheel service . 31 Pyrotechnic service .32 Magnetic-torquers s .34 Power conditioning service . 36 . 34 . 34 .37 ETSI 4 ETSI
13、 EN 301 927 VI . 1 . 1 (2003-02) 7.3.2.2 7.3.2.3 7.3.2.4 7.3.2.5 7.4 7.4.1 7.4.2 7.4.3 7.4.4 7.4.5 7.4.6 Power amplifiers service . 39 Channel amplifier 40 Switching service 41 Digital Transparent Processor service . 42 Simple devices services 45 Pulse command service . 45 Temperature acquisition se
14、rvice . 46 Pressure acquisition service 46 Current acquisition service . 47 Voltage acquisition service . 48 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 pre
15、sent 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.l
16、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.l Encoding formats of parameter Spes .
17、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 VI .I .I (2003-02) Intellectual P
18、roperty 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 O00 3 14: “Intellectual Property Rights (7PRs
19、); Essential, orpotentially Essential, IPRs notlJied to ETSI in respect ofETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (5). All published ETSI deliverables shall include information which directs the reader to the above source of
20、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: Date of latest announcement of this EN (doa): Date of latest publication of new
21、 National Standard or endorsement of this EN (dop/e): Date of withdrawal of any conflicting National Standard (dow): 21 February 2003 3 1 May 2003 30 November 2003 30 November 2003 Introd U ction Shorter and shorter communications satellites development cycles and compatibility requested with off th
22、e 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 s
23、oftware specifications of the Interface between the application software and the communication services. It shall help the standardization of equipment interface. The present document addresses IS0 OS1 application layer services i. Currently, no application layer services standard exists for the Dat
24、a 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 i
25、mplemented 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 mod the contents of the present document it will then be republished by ETSI with an identiSlin
26、g 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. The third digit (n) is incremented when editorial only changes have been incorpo
27、rated in the specification. n ETSI 6 ETSI EN 301 927 VI .I .I (2003-02) 1 Scope The present document applies to Geostationary Communications Satellite architectures based on IS0 OS1 Reference Model or SOIF Reference Model, but could also be applied to other types of satellites. The present document
28、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 Re fe re nces The following documents contain provisions which, through reference in this text, con
29、stitute provisions of the present document. References are either specific (identified by date of publication andor 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 doc
30、uments which are not found to be publicly available in the expected location might be found at InttD:/doctsox.etsi .o-rpRefercncc. il ISO/IEC 7498-1 (1994): “Information Technology - Open Systems Interconnection - Basic Reference Model: The Basic Model“. 21 IEEE Standard 754-1985: “IEEE Standard for
31、 Binary Floating-point Arithmetic“ 3 3.1 Definitions and abbreviations De fi nit ions 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
32、 of performance application software: on-board software implementing the satellite control functions NOTE: A service is implemented by hardware andor software. Application layer services for the control of devices are defined in terms of . . a service access point; the functions provided by the serv
33、ice; . the management parameters. ETSI 7 ETSI EN 301 927 VI .I .I (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: . re
34、flex 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
35、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. dec
36、ision 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 inc
37、luding 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
38、: Sensors and actuators, Telemetry Command and Ranging (TCR) devices or other mission specific device s. 52000: earth centred Co-ordinate reference system with an epoch of January lst 2000 primitive: a signal (e.g. a send request) which is passed across the service access point in order to use the s
39、ervice 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
40、to satellite communication link for monitoring and control . . ; $i i . , . i $. File transfer service. Command and Data Acquisition service; The present document does not address in particular: Task management; On-board scheduling; Satellite System FDIR. User Application Layer definition: This laye
41、r 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 r
42、euse capability. User application services implementation can call (see figure 3): Application Interface services; Other user application layer 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 9
43、27 VI .I .I (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 datab
44、ase 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 service
45、s; - - SOIF or non SOIF application layer services; Any other lower layer services with exposed Service Access Point. User application Control Management Application layer Interfaces with the application Transport layer Organisation of the complete successful communication Network layer Network subl
46、ayer Data link layer Physical layer n management Networking Convergence interface nn _ n Data link layer PlatForm ant Equipemen Data Base Convergence interface Network Data Base U SOIF layered model Figure 3: SSDHI position with respect to. other services ETSI 12 ETSI EN 301 927 VI .I .I (2003-02) 6
47、 Service specification 6.1 I n trod u ction 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 equipme
48、nt functionality dependent. They are defiied 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, Fre
49、quency, 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
