1. ESA UNCLASSIFIED – For Official Use Workshop #23 Pasadena, USA 24 rd March 2015 Sam Cooper Common services update (part 1)

2. CCSDS Common service| 24Mar15| ESA | Slide 2 ESA UNCLASSIFIED – For Official Use Overview  Common services are being updated in line with latest COM  Expanding to cover the automatic configuration use case  Common services are:  Directory Service lookup  Login Operator log in  Replay Replay session management and control  Interaction Application and Operator interaction  Configuration Service provider configuration management Part 1 Part 2

3. CCSDS Common service| 24Mar15| ESA | Slide 3 ESA UNCLASSIFIED – For Official Use Login service Area IdentifierService IdentifierArea Number Service Number Area Version CommonLogin321 Interaction PatternOperation IdentifierOperation Number Support in Replay Capability Set REQUESTlogin1No 1 SUBMITlogout2No REQUESTreportRoles3No 2 REQUESThandover4No 3  The Login service defines the primary mechanism for the submission of authentication details to a deployment specific security system  It supports operations to allow a user to:  Login  Logout  Report available roles  Handover to another user  The service is closely tied to the Access Control aspect of the MAL

4. CCSDS Common service| 24Mar15| ESA | Slide 4 ESA UNCLASSIFIED – For Official Use Interaction service Area IdentifierService IdentifierArea Number Service Number Area Version CommonInteract331 Interaction PatternOperation IdentifierOperation Number Support in Replay Capability Set INVOKEraiseAcknowledge1No 1 SUBMITrespondAcknowledge2No INVOKEraiseConfirm3No 2 SUBMITrespondConfirm4No INVOKEraiseChoice5No 3 SUBMITrespondChoice6No INVOKEgetValues7No 4 SUBMITrespondValues8No REQUESTlistActiveInteractions9Yes 5 SUBMITcancelInteraction10No 6  The interact service allows interactions to be raised by one consumer that can be completed by another consumer  Application needs input  Another application provides that input  The expected use is for software components to request decision input or extra information from user of the system  Users/operators provide input via an MMI (MMI)

5. CCSDS Common service| 24Mar15| ESA | Slide 5 ESA UNCLASSIFIED – For Official Use Replay service Area IdentifierService IdentifierArea Number Service Number Area Version CommonReplay341 Interaction PatternOperation IdentifierOperation Number Support in Replay Capability Set SUBMITpauseReplay1No 1 SUBMITresumeReplay2No SUBMITforwardStep3No 2 SUBMITbackwardStep4No SUBMITupdateReplay5No 3 REQUESTlistActiveReplays6No 4 INVOKEaddReplay7No 5 SUBMITremoveReplay8No  The Replay service allows a consumer to create, control and delete replay sessions  A replay session is a read-only duplicate of an existing live or simulation session  As well as specifying the initial replay time, the replay can be controlled in a similar way to a video player:  Play  Pause  Fast forward  Rewind  Single step  Jump to specific time etc.

6. CCSDS Common service| 24Mar15| ESA | Slide 6 ESA UNCLASSIFIED – For Official Use Directory service  The Directory service allows:  Service providers to publish information about which services they provide  Consumers to look up service provider address and capability information  Provider information is made available using the publishService operation  Consumers query the directory using the lookupService operation  Provider information is removed using the withdrawService operation  A new operation is proposed to allow a consumer to retrieve the service XML Area IdentifierService IdentifierArea Number Service Number Area Version CommonDirectory311 Interaction PatternOperation IdentifierOperation Number Support in Replay Capability Set REQUESTlookupService1Yes 1 REQUESTpublishService2No 2 SUBMITwithdrawService3No REQUESTgetServiceXML4Yes3

7. CCSDS Common service| 24Mar15| ESA | Slide 7 ESA UNCLASSIFIED – For Official Use Directory service XML  The getServiceXML operation allows a consumer to request the MO XML specification of a service  Would support standard as well as proprietary services  Would return a File of the XML  XML needs to be supplied by the service provider when adding its details to the Directory service  There is an issue that a MO XML file holds Areas rather than specific services  Requesting service X would return the complete area  Could return a filtered file but that gets complicated when data types shared across services  Proposal is just to return what is associated

8. CCSDS Common service| 24Mar15| ESA | Slide 8 ESA UNCLASSIFIED – For Official Use Open points  Suggestion to rename Directory service to Discovery service  Also to rename operations: publishService  registerService/addService withdrawService  deregisterService/removeService  Should getServiceXML operation actually be part of the Configuration service

9. CCSDS Common service| 24Mar15| ESA | Slide 9 ESA UNCLASSIFIED – For Official Use End of part 1