312:
integrated into a system. However, for the service framework to be effective it must ensure that meaningful information associated with mission operations can be exchanged across the service interfaces, not merely data. The service framework must also respect legacy systems. Where an integrated legacy system performs the function of several service framework components, its internal architecture and implementation do not have to be changed. Only those interfaces it exposes to other systems need be ‘wrapped’ to make them compliant with the corresponding service interfaces. The service framework offers a range of interoperable interfaces, from which the most appropriate can be selected: compliance is not dependent on supporting them all. In this way legacy systems can be re-used in conjunction with other compliant components to build a mission specific system. The approach is intended to be
Evolutionary and not Revolutionary.
394:
mission timelines, etc.), these application level services are implemented in terms of a smaller set of generic interaction patterns that allow current status to be observed, operations to be invoked and bulk data transferred. This has two key benefits: it is inherently extensible, as new services can be overlaid on the existing common services; and the investment made in
Mission Operations applications is further isolated from the implementation technology. Technology adapters allow the underlying communications infrastructure to be changed (or bridged) with minimal impact on the applications themselves. This improves long-term maintainability, as missions often outlive the ground technology used to deploy them initially.
661:
data products, activities specifically concerned with the exploitation of mission data (such as mission specific data processing, archiving and distribution) are considered outside the scope of MO. Increasingly, MO functions may be distributed between collaborating agencies and ground segment sites, or partially delegated to autonomous functions on board the spacecraft itself. The MO Service
Framework is concerned with end-to-end interaction between MO application software, wherever it may reside within the space system. It is specifically not concerned with the provision of services for data transport or persistence (storage). It is, however, a user of such services.
296:(SOA) is gradually replacing monolithic architecture as the main design principle for new applications in both private and distributed systems. It is one of the fundamental design principles of network distributed applications where the interfaces, both operations and data objects, must be well defined as the clients are often heterogeneous. SOA is an approach to system design that relies not on the specification of a monolithic integrated system, but instead on the identification of smaller, modular components that communicate only through open, published, service interfaces.
33:
387:
304:
deployment of the service framework over that technology. This in turn makes it possible to replace the infrastructure implementation as well as component implementations. It is also possible to transparently bridge between different infrastructure implementations, where these are appropriate to different communications environments (e.g., space or ground) or simply reflect different agencies’ deployment choices.
573:
433:
326:
226:
128:
660:
These are typically regarded as the functions of the
Mission Control Centre (MCC) and are performed by the mission operations team, supported by the Mission Operations System. MO include the capability to archive and distribute mission operations data. While this may include the handling of mission
299:
The SM&C WG is defining a set of standard services, which constitutes a framework that enables many similar systems to be assembled from compliant ‘plug-in’ components. These components may be located anywhere, provided they are connected via a common infrastructure. This allows components to
393:
A key feature of the
Mission Operations Service Framework is the layering of services. While there are a range of potential services identified corresponding to different types of mission operations information that are exchanged within a system (status parameters, control actions, orbital data,
311:
It is also important to note that the approach does not prescribe the components themselves or their implementation. Only the service interfaces between components are standardised. This allows for innovation, specialisation and differentiation in components, while ensuring they can be rapidly
303:
If services are specified directly in terms of a specific infrastructure implementation, then they are tied to that technology. Instead, by layering the services themselves, the service specifications can be made independent of the underlying technology. Specific technology adapters enable the
188:
There is a general trend toward increasing mission complexity at the same time as increasing pressure to reduce the cost of mission operations, both in terms of initial deployment and recurrent expenditure. Closed, or ‘monolithic’ mission operations system architectures do not allow the
113:
agencies, is defining a service-oriented architecture consisting of a set of standard end-to-end services between functions resident on board a spacecraft or based on the ground, that are responsible for mission operations.
307:
NOTE – Plug-in components communicate only via standard service interfaces through a common infrastructure. The service framework is itself layered and independent of the underlying infrastructure implementation.
493:
Standardisation of a
Mission Operations Service Framework offers a number of potential benefits for the development, deployment and maintenance of mission operations infrastructure:
988:
212:
The result is many parallel system infrastructures that are specific to a given family of spacecraft or operating agency, with little prospect of cross-fertilisation between them.
512:
between missions and the ability to establish common multi-mission infrastructure, therefore reducing training costs of operational teams and time to prepare new missions
62:
419:
The interface between each layer is defined in the CCSDS standards and therefore implementations of the each layer can be replaced without change to other software.
717:
106:
856:
594:
454:
347:
247:
149:
189:
re-distribution of functionality between space and ground, or between nodes of the ground system. This lack of architectural openness leads to:
835:
785:
682:
287:
620:
480:
373:
273:
175:
84:
819:
708:
598:
458:
351:
251:
153:
957:
798:
293:
637:(MO) is used to refer to the collection of activities required to operate spacecraft and their payloads. It includes:
45:
860:
583:
443:
336:
236:
138:
55:
49:
41:
602:
587:
462:
447:
355:
340:
255:
240:
157:
142:
961:
409:
66:
983:
814:
300:
be re-used in different mission-specific deployments: between agencies, between missions, and between systems.
670:
840:
701:
683:
https://web.archive.org/web/20130531013416/http://public.ccsds.org/publications/archive/520x0g3.pdf
17:
110:
879:
734:
686:
780:
402:
386:
759:
749:
548:
increased competition in the provision of commercial tools, leading to cost reduction and
681:
Mission
Operations Services Concept. CCSDS 520.0-G-3. Green Book. Issue 3. December 2010
694:
502:
977:
932:
208:
lack of operational commonality between mission systems, increased training costs.
572:
558:
over the mission lifetime through both component and infrastructure replacement.
432:
325:
286:
225:
127:
508:
standardisation of infrastructure interfaces, even within agencies, leading to
790:
524:
of mission-specific deployment through the integration of re-usable components
205:
inability to replace implementation technology without major system redesign;
744:
937:
923:
650:
orbit and attitude determination, prediction and manoeuvre preparation
918:
913:
538:
more easily between ground segment sites or even from ground to space
889:
545:
rather than a large number of specific inter-component interfaces
897:
884:
739:
641:
monitoring and control of the spacecraft subsystems and payloads
690:
111:
http://www.space.bas.bg/bg/procurement/files/pravilnik%20OP.PDF
566:
515:
standardisation of operational interfaces for spacecraft from
426:
319:
219:
199:
increased cost of mission specific development and deployment;
121:
26:
397:
The layers of the
Mission Operations Service Framework are:
385:
285:
501:
between agencies, at the level of spacecraft, payloads, or
109:(CCSDS), which sees the active participation of the main
647:
planning, scheduling and execution of mission operations
531:
for a given task from a range of compatible components
950:
906:
869:
849:
828:
807:
770:
724:
196:
lack of re-use between missions and ground systems;
653:management of on-board software (load and dump)
54:but its sources remain unclear because it lacks
534:greater flexibility in deployment boundaries:
989:Consultative Committee for Space Data Systems
718:Consultative Committee for Space Data Systems
702:
644:spacecraft performance analysis and reporting
107:Consultative Committee for Space Data Systems
8:
857:Space Communications Protocol Specifications
554:improved long-term maintainability, through
951:Networking, interoperability and monitoring
601:. Unsourced material may be challenged and
461:. Unsourced material may be challenged and
354:. Unsourced material may be challenged and
254:. Unsourced material may be challenged and
202:unavailability of commercial generic tools;
156:. Unsourced material may be challenged and
709:
695:
687:
193:lack of interoperability between agencies;
621:Learn how and when to remove this message
481:Learn how and when to remove this message
374:Learn how and when to remove this message
274:Learn how and when to remove this message
176:Learn how and when to remove this message
85:Learn how and when to remove this message
405:(which includes the MO Common Services)
403:Mission Operations (MO) Services Layer
7:
599:adding citations to reliable sources
459:adding citations to reliable sources
352:adding citations to reliable sources
252:adding citations to reliable sources
154:adding citations to reliable sources
836:Spacecraft Monitoring & Control
99:Spacecraft Monitoring & Control
18:Spacecraft Monitoring & Control
656:delivery of mission data products.
25:
571:
431:
324:
224:
126:
31:
820:Proximity-1 Space Link Protocol
216:The service framework approach
1:
958:Service-oriented architecture
294:Service-oriented architecture
118:Identification of the problem
870:Telemetry modulation systems
861:Performance Enhancing Proxy
1005:
543:limited number of services
962:Message Abstraction Layer
536:functions can be migrated
505:infrastructure components
415:A message transport layer
410:Message Abstraction Layer
815:Command Loss Timer Reset
808:Telemetry command uplink
40:This article includes a
529:select the best product
517:different manufacturers
105:) Working Group of the
69:more precise citations.
760:Adaptive Entropy Coder
390:
290:
541:standardisation of a
389:
289:
671:NanoSat MO Framework
595:improve this section
455:improve this section
348:improve this section
248:improve this section
150:improve this section
841:Beacon mode service
550:vendor independence
829:Telemetry downlink
786:Concatenated codes
635:mission operations
563:Mission operations
423:Potential benefits
391:
291:
42:list of references
971:
970:
850:Telemetry general
781:Binary Golay code
631:
630:
623:
491:
490:
483:
384:
383:
376:
284:
283:
276:
186:
185:
178:
95:
94:
87:
16:(Redirected from
996:
771:Error Correction
725:Data compression
711:
704:
697:
688:
626:
619:
615:
612:
606:
575:
567:
556:system evolution
499:interoperability
486:
479:
475:
472:
466:
435:
427:
379:
372:
368:
365:
359:
328:
320:
316:Service layering
279:
272:
268:
265:
259:
228:
220:
181:
174:
170:
167:
161:
130:
122:
90:
83:
79:
76:
70:
65:this article by
56:inline citations
35:
34:
27:
21:
1004:
1003:
999:
998:
997:
995:
994:
993:
984:Space standards
974:
973:
972:
967:
946:
941:
927:
902:
865:
845:
824:
803:
766:
720:
715:
679:
667:
627:
616:
610:
607:
592:
576:
565:
487:
476:
470:
467:
452:
436:
425:
380:
369:
363:
360:
345:
329:
318:
280:
269:
263:
260:
245:
229:
218:
182:
171:
165:
162:
147:
131:
120:
91:
80:
74:
71:
60:
46:related reading
36:
32:
23:
22:
15:
12:
11:
5:
1002:
1000:
992:
991:
986:
976:
975:
969:
968:
966:
965:
954:
952:
948:
947:
945:
944:
939:
935:
930:
925:
921:
916:
910:
908:
904:
903:
901:
900:
895:
892:
887:
882:
877:
873:
871:
867:
866:
864:
863:
853:
851:
847:
846:
844:
843:
838:
832:
830:
826:
825:
823:
822:
817:
811:
809:
805:
804:
802:
801:
796:
793:
788:
783:
778:
774:
772:
768:
767:
765:
764:
763:
762:
754:
753:
752:
747:
742:
737:
728:
726:
722:
721:
716:
714:
713:
706:
699:
691:
678:
675:
674:
673:
666:
663:
658:
657:
654:
651:
648:
645:
642:
629:
628:
579:
577:
570:
564:
561:
560:
559:
552:
546:
539:
532:
525:
519:
513:
506:
503:ground segment
489:
488:
439:
437:
430:
424:
421:
417:
416:
413:
406:
382:
381:
332:
330:
323:
317:
314:
282:
281:
232:
230:
223:
217:
214:
210:
209:
206:
203:
200:
197:
194:
184:
183:
134:
132:
125:
119:
116:
93:
92:
50:external links
39:
37:
30:
24:
14:
13:
10:
9:
6:
4:
3:
2:
1001:
990:
987:
985:
982:
981:
979:
963:
959:
956:
955:
953:
949:
943:
936:
934:
931:
929:
922:
920:
917:
915:
912:
911:
909:
905:
899:
896:
893:
891:
888:
886:
883:
881:
878:
875:
874:
872:
868:
862:
858:
855:
854:
852:
848:
842:
839:
837:
834:
833:
831:
827:
821:
818:
816:
813:
812:
810:
806:
800:
797:
794:
792:
789:
787:
784:
782:
779:
776:
775:
773:
769:
761:
758:
757:
755:
751:
748:
746:
743:
741:
738:
736:
733:
732:
730:
729:
727:
723:
719:
712:
707:
705:
700:
698:
693:
692:
689:
685:
684:
676:
672:
669:
668:
664:
662:
655:
652:
649:
646:
643:
640:
639:
638:
636:
625:
622:
614:
604:
600:
596:
590:
589:
585:
580:This section
578:
574:
569:
568:
562:
557:
553:
551:
547:
544:
540:
537:
533:
530:
526:
523:
520:
518:
514:
511:
507:
504:
500:
496:
495:
494:
485:
482:
474:
464:
460:
456:
450:
449:
445:
440:This section
438:
434:
429:
428:
422:
420:
414:
411:
407:
404:
400:
399:
398:
395:
388:
378:
375:
367:
357:
353:
349:
343:
342:
338:
333:This section
331:
327:
322:
321:
315:
313:
309:
305:
301:
297:
295:
288:
278:
275:
267:
257:
253:
249:
243:
242:
238:
233:This section
231:
227:
222:
221:
215:
213:
207:
204:
201:
198:
195:
192:
191:
190:
180:
177:
169:
159:
155:
151:
145:
144:
140:
135:This section
133:
129:
124:
123:
117:
115:
112:
108:
104:
100:
89:
86:
78:
68:
64:
58:
57:
51:
47:
43:
38:
29:
28:
19:
680:
659:
634:
632:
617:
608:
593:Please help
581:
555:
549:
542:
535:
528:
522:reduced cost
521:
516:
509:
498:
492:
477:
468:
453:Please help
441:
418:
396:
392:
370:
361:
346:Please help
334:
310:
306:
302:
298:
292:
270:
261:
246:Please help
234:
211:
187:
172:
163:
148:Please help
136:
102:
98:
96:
81:
72:
61:Please help
53:
907:Frequencies
791:Turbo codes
611:August 2022
527:ability to
471:August 2022
364:August 2022
264:August 2022
166:August 2022
75:August 2022
67:introducing
978:Categories
799:LDPC codes
677:References
497:increased
745:JPEG 2000
633:The term
582:does not
442:does not
335:does not
235:does not
137:does not
894:Proposed
859:(SCPS):
795:Proposed
750:122.0.B1
665:See also
103:SM&C
876:Current
777:Current
731:Images
603:removed
588:sources
463:removed
448:sources
356:removed
341:sources
256:removed
241:sources
158:removed
143:sources
63:improve
933:K band
919:S band
914:X band
510:re-use
890:OQPSK
756:Data
412:(MAL)
48:, or
942:band
928:band
898:GMSK
885:QPSK
880:BPSK
740:JPEG
735:ICER
586:any
584:cite
446:any
444:cite
408:The
401:The
339:any
337:cite
239:any
237:cite
141:any
139:cite
97:The
597:by
457:by
350:by
250:by
152:by
980::
52:,
44:,
964:)
960:(
940:a
938:K
926:u
924:K
710:e
703:t
696:v
624:)
618:(
613:)
609:(
605:.
591:.
484:)
478:(
473:)
469:(
465:.
451:.
377:)
371:(
366:)
362:(
358:.
344:.
277:)
271:(
266:)
262:(
258:.
244:.
179:)
173:(
168:)
164:(
160:.
146:.
101:(
88:)
82:(
77:)
73:(
59:.
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
