[Css-csts] SLE SM mapping - Annex D

[Paula Quintela]

Hi Yves,

I have reviewed your technical note "CCSDS Service Management References in the SLE API books" and after a few e-mail exchanges within the SMWG, here are the main conclusions.

1) There are potentially 3 new RAF and RCF parameters to be added to the SLE SM Specification book to support the configuration of service instances:
- size of online frame buffer (the online frame buffer is used in the complete online delivery mode)
- number of frames to be discarded in case the online frame buffer gets full
- maximum data rate limitation ('metering')

Questions: How often are these parameters meant to change? Do they change on a service instance basis?

Assumption: Given that these parameters are related to parameters such as transferBufferSize and latencyLimit, they will be placed in the same data sets of the Configuration Profile data structure. This allows their value to be changed on a service instance basis.


2) Need clarification of the meaning of CLTU service parameters: expected-cltu-identification and expected-event-invocation-identification.

Questions: Why are they listed in Table 3-1 - Setting of Forward CLTU Service Configuration Parameters, given that they are CLTU-START and CLTU-THROW-EVENT operation parameters? What role is SM expected to play in their setting?

Assumption: For the time being we have assumed that there is no need for corresponding parameters in SLE-SM.


3) Support for THROW-EVENT operation. Need to discuss this issue with CSTS WG.


4) Service Management support is also expected for the following:

- recovery from production interruption
- transitions to/from production-status = halted
- mechanism for making available to user, via Service Management, notifications logged while association was not available (please see NOTE 1 of section 4.1.5.4 of CLTU book - 912x1b2).

Assumption: Support for the mechanisms listed above are meant to be provided by some "local management system", and hence are outside the scope of SLE-SM.


5) The known limitations of SLE-SM (form of initiation of R-AF and R-CF, offline delivery mode and support for ROCF and FSP services) are outside the scope of SLE SM Specification Red1.


Please let us know if you do not agree with the listed assumptions.

Hopefully, we will be ale to clear these points at the meeting in Atlanta.

See you next week,

kind regards,

Paula.