...

Seshu Kumar Mudiganti

Adrian OSullivan

Agenda

1. Need for E2EST and its usage
2. Use of allotted resources vs shared service concept

Notes and Actions

1. Chuyi Guo presented about the E2EST, its need and its use.
   • E2EST is needed mainly to:
     1. Overcome the limitation in SO in reusing the E2E service creation APIs/interface to "allocate" a slice (which maps to the 3GPP specified allocateNsi operation) - which can result in 'creating' a new NSI or in reusing an existing NSI
     2. Include the S-NSSAI generated by the CSMF upon receiving a communication service creation request.
   • If E2EST is not present, current ONAP SO implementation will have to be modified, e.g., to create new workflows, APIs, etc. to support the allocateNsi operation.
2. There was quite some discussion on when S-NSSAI is generated, and who generates it. An action was defined to check further reg. this.
3. The need for E2EST was discussed further, and no consensus was reached as 2 contrasting views exist: One is to use E2EST as explained above, and the other is to use the shared service/service reference approach in which case E2EST may not be needed. It was agreed that we will check possible alternatives further, and also discuss with Seshu reg. the SO aspects. In any case, a conclusion should be reached by Mon on the way forward for Frankfurt.
4. Use of allotted resources was proposed by Chuyi Guo and Chen Chuanyu. Borislav had shared his views reg. the limitations and challenges w.r.to the use of allotted resources, and also explained an alternative approach from the bottom up (sharing from NSST level upwards). However, a consensus was not reached. So, a consensus should be reached by Mon for this point also.
5. For the aspects above requiring a conclusion to be reached by 16th Dec, Swami to contact the respective persons for preparing relevant inputs before the next meeting on 16th.

Recording