Transcript SOIS TCOAS WG

SOIS TCOAS WG
Spring 2005 Report
Goals for the Week
• Review and issue Device Access Red Book
• Review and issue Time Distribution Red Book
• Consider overlap between MTS and AMS and
resolve way forward, determining schedule
• Map MTS QoS onto TCONS QoS
• Review concept paper on FTS and CFDP,
determine if CFDP can be adopted as FTS
• Agree concept for Device Data Pooling and
Device Virtualisation and determine schedule for
production of Red Books
Red Books Voted Forward
• Device Access Service (now)
• Time Distribution Service (11th May 2005)
Device Access Service
• CS1: Spacecraft command and data acquisition service
that enables onboard applications to read and write
simple onboard devices
• Goal 2 in charter, definition 1st July 2005, prototyping
July - Sept 2005
• Red Book review completed at meeting
– Separate Red Book to specify interoperability protocol
• Need to determine who will be participating in
prototyping and interoperability testing then determine
schedule for completing by Fall 2005
• Known issues – none
• Proposed resolution –
– forward for issue
– Draft Device Access Service Protocol Specification Red Book
during prototyping & interoperability testing for review Fall 2005
Time Distribution Service
• Access to local time source
• Goal 3 in charter, definition 1st July 2004, prototyping
July - October 2005
• Draft Red Book reviewed (incomplete) during meeting
• Need to determine who will be participating in
prototyping testing then determine schedule for
completing by Fall 2005
• Proposed resolution:
– rename Time Access Service
– TDS Red Book draft distributed for TCOAS review immediately
after meeting
– All reviewers to submit to TCOAS chair comments by 29th April.
– TDS teleconference review on Wed 4th May (8.30 am PDT etc..)
– Forward for issue 11th May 2005
Message Transfer Service
• On-board message transfer service that enables applications hosted
onboard a spacecraft to communicate with each other using
asynchronous ad-hoc messaging
• Goal 4 in charter, definition 1st July 2004, prototyping July - October
2005
• Overlap between MTS, AMS and MOIMS SM&C discussed.
Agreement to work on joint concept paper
• Review concept paper and determine what will provide protocol. Aim
for draft Red Book by Sept 2005. Red Book review Fall 2005 &
prototyping and interoperability testing until Spring 2006
• Issues:
– connectionless vs. connection-oriented service
– QoS mapping onto TCONS (or others) QoS
• Proposed resolutions:
– Support cross-area working (S.Fowell representing TCOAS)
– Subsequently determine direction and continue development – aim for
Red Book draft by Fall 2005
– Can only talk about maping onto TCONS QoS when it is published and
we have time to prepare!
File Transfer Service
• Not clear what service is aimed at
• Only listed in charter schedule not goals, interoperability
testing July - Sept 2005
• Concept paper produced and individual reviews, failed to
hold review meeting
• Known issues:
– No goal for this service – is it a filestore access service or a file
transfer service?
• Proposed resolutions:
– Agree goal within TCOAS & update charter (by 1st May 2005)
– Update concept paper to address whether CFDP meets this goal
(by 1st June 2005)
– Produce Red Book for Fall 2005 meeting
– Review Red Book at Fall 2005 meeting
Device Data Pooling Service
• CS6: A data pool is a periodically maintained software
image of the states of a number of devices on the
spacecraft. This service maintains a data pool so that
flight software can access the data in the data pool
without explicitly requesting a read of the real device
• Not explicit in charter!
• No progress made during meeting
• Review Red Book & interoperability testing until Spring
2006 (6 months slip)
• Known issues – none
• Proposed resolution –
– Schedule for concept paper 31st July 2005
– draft Red Book during Fall 2005 meeting
Device Virtualisation Service
• CS5: Device virtualisation involves the provision of
virtual generic images of real physical devices. The user
application communicates directly with the device image,
and the service implementation translates these
accesses to the virtual device into the appropriate
accesses to the real device
• Not explicit in charter!
• No progress made during meeting
• Review Red Book & interoperability testing until Spring
2006
• Known issues – none
• Proposed resolution –
– Schedule for concept paper 31st July 2005
– draft Red Book during Fall 2005 meeting
Review of Progress Against
Charter
Date
Milestone
Progress
1 January 2004
Concept document
Not started.
1 July 2004
C&DA CS1 definition
Achieved 15th April 2005
July 2004
- October 2005
C&DA prototyping
April – Sept 2005 (need to identify resources)
1 July 2004
Time distribution specification
Will be achieved 11th May 2005
April 2005 – October 2005
Time distribution prototyping
April – Sept 2005 (need to identify resources)
1 July 2004
Messaging transfer services definition
Not achieved. Concept paper on relationship between
MTS, AMS and SM&C 6th June 2005. Can only
determine schedule following this
April 2005 – October 2005
Messaging transfer services prototyping
See above.
1 July 2004
File transfer services definition
Not achieved. Goal specified by 1st May 2005. Concept
paper 1st June 2005. Red Book draft Sept 2005
April 2005 – October 2005
File transfer services prototyping
Sept 2005 – April 2006
October 2005
Red Book 1
Individual red books
Plan of Work for Next Inter-Plenary
• Prototype and Interoperability testing of Device Access
Service
• Complete review and issue Red Book for Time
Distribution Service
• Prototype of Time Distribution Service
• Concept paper for generic Messaging
• Draft Red Book for Message Transfer Service
(provisional)
• Define goal, update concept paper and draft Red Book
for File Transfer Service
• Write concept paper and draft Red Book for Device Data
Pooling Service
• Write concept paper and draft Red Book for Device
Virtualisation Service
Any Issues Arising
• TCOAS WG will support the cross area
scoping of messaging (rep. by S.Fowell)
• Observation: having only two or three
authors in a working meeting is good for
making progress, only review meetings
should have more people ;o))