Date:  


Participants

Ahila P 

@Alex D

@Aniello Paolo Malinconico

Alessandro Gerardo D'Alessandro 

Borislav Glozman 

Deepika S 

Dong Wang 

Emmanuelle Delfour 

Fei Zhang 

Klaus Negle 

Marcin Sebastian Krasowski 

Raffaele Passannanti 

Rajendra Prasad Mishra 

Saravanan Ayyadurai 

Timo Perala 

Yogendra Pal 


Agenda

  1. E2E Testing Status - Service Activation/Deactivation, Termination
  2. Istanbul Release - Integration Testing Preparation & Contribution
  3. Requirements planning for Jakarta release
  4. Update on action items from the previous meeting
  5. AOB?

Notes and Actions

  1. Elaborate the J-Release requirements - Ahila P 
  2. Config DB issues - Alessandro Gerardo D'Alessandro to send a mail with the issues faced
  3. E2E Slice instance creation - Core NSSMF - CBA package correct version - Deepika S to share the correct version of CBA package, TN and RAN NSSMF - Alessandro Gerardo D'Alessandro to check and report if the same issue persists for TN & RAN NFs
  4. TN NSSMF - Call from SDN-R to AAI to retrieve RAN NFs returns improper result. Alessandro Gerardo D'Alessandro to share the details in mail
  5. M4 update - 1. Integration test cases are updated at R9 Integration Testing 2. Documentation - In Progress

J-release Requirements:

S.NoRequirementsDescriptionTypePriorityOwnerOrganizationContributorsComments
E2E Slicing Solution
1Support for mMTC, uRLLC SliceseMBB slice type is supported in the previous release. This requirement is to accommodate the modification in the existing system to support mMTC and uRLLC performance requirements.Enhancement1AhilaWipro

2Activate, Deactivate flows support in external  RAN NSSMFTo support the activate and deactivate actions in E2E Network Slicing with External NSSMFs (option2). Currently, instantiation and termination are supported.Enhancement2YogendraAarna Networks

3Capacity based NSI/NSSI SelectionIn case of shared scenario (reuse existing slice), NSI/NSSI can be shareable only if sufficient resources are available in the network. OOF should return the solution for NSI/NSSI selection based on this criteria.New2AhilaWipro
How to calculate the RAN NFs capacity?
4Core, RAN Endpoints Discovery at NSMFHardcoded RAN and CN endpoints are used in the previous releases. Discover the Core and RAN endpoints from the network and fed it to TN NSSMF New1AhilaWipro

5NSI Selection based on the coverage Area

eMBB or mMTC like service parameters. with coverageArea more than what is already supported in a suitable existing and shareable NSI  Sharing allowed


Enhancement1AhilaWipro

6IBN based E2E SlicingCommunication service request is given as business intent and it should be integrated with the existing E2E slice flow.New3Dong WangChina Telecom
Descoped for this release
7CSIT Continuation (SO, SDN-R)CSIT test cases for SO and SDNC component testingCarry forward1AhilaWipro

8Use case AutomationE2E network Slicing use case test automationNew1AhilaWipro

9Populate sNSSAI in the UUI to complete the pending actions Enable the user to select the sNSSAIs in UUI to complete the pending actions pertaining to that SliceNew2


Proposed by Yogendra. Under discussion









RAN Slicing
1cm-handle registration with CPS-DMI Plugin - Integrationcm-handle should be registered with CPS for every RAN NF instance. Karaf feature to do the registration is completed in I-release, integration with CPS is planned for J-releaseNew1AhilaWipro

2Instantiation of RAN NFs and initial configuration RAN Network Functions (CUCP, CUUP, DU) are assumed as pre-instantiated and pre-configured since Guilin release. This needs to be created/instantiated as VNFs/CNFsNew3


Owner not identified yet.
3CPS Integration with SDN-RRANSlice allocate and reconfigure rpcs to be integrated with CPS for RAN configurations persistenceCarry forward1AhilaWipro

4CPS Integration StabilizationValidate and bug fix of CPS integration for RAN slice lifecycleCarry forward1AhilaWipro

5CPS-TBDMT enhancement to integrate with NCMPCPS Core is directly invoked from TBDMT. The call should go via NCMP to CPS-CoreEnhancement1AhilaWipro










Core Slicing
1ETSI aligned Core NSSMFLeverage Core NSSMF to be in an alignment with SOL-005 APIs while supporting the existing Non-ETSI (3GPP) interfacesNew3


Owner not identified yet.
2New NFs are not getting instantiated for allocateNSSI request having same NSSTNot able to create more than one non-shared Core Slice. It needs a fix at ExtAPI/NBIEnhancement1


Cannot be done, as ExtAPI is in unmaintained state
3CSIT for core slicingCSIT test cases for Core NSSMF
1


Owner not identified yet.









Transport Slicing
1Support for modify-deallocate in TN-NSSMF
Enhancement1Henry YuHuawei

2TN NSSMF enhancements according to IETF latest specification
Enhancement3Henry YuHuawei

3Implementing the call to OOF (SelectNSSI API) for allocateNSSI (to enable TN NSSI reuse even when NSI is created newly) in TN NSSMF
New1Henry YuHuawei

4Implement the call to OOF (terminateNxi API) for deallocate NSSI (to enable TN NSSI NOT terminated even when NSI is terminated) in TN NSSMF
New1Henry YuHuawei

5CSIT for transport slicing

1Henry YuHuawei

6Transport Slicing enhancement to support IBN based E2E slicing
New1Henry YuHuawei

7

Closed-loop enhancement in CCVPN to support Transport Slicing’s closed-loop


New1Henry YuHuawei

Closed Loop
1IBN based Closed loopMake use of intents/ML models for closed loopNew3Dong WangChina Telecom

2Closed loop updates over A1 interface - enhancementsDone at POC level in I-release. It will be further enhanced to make use of A1-PMS for A1 policy instance creation and requires RAN Simulator enhancementsEnhancement1AhilaWipro

3CPS Integration StabilizationValidate and enhance CPS integration for closed loopCarry forward1AhilaWipro










KPI Monitoring
1KPI Computation MS Remaining Requirements (Mark Scott’s comments)https://jira.onap.org/browse/DCAEGEN2-2801Carry forward1AhilaWipro










Recording

  • No labels