Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Note: Requirements which are in scope for Jakarta release are marked "Yes" in the column "In Scope"

S.No

Requirements

Description

Type

Priority

Owner

Organization

Impacted Components

In Scope

Comments

Remarks


E2E Slicing Solution

 

 

 

 

 

 

 

 

1

Support for mMTC, uRLLC Slices

eMBB 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.

Enhancement

1

Ahila

Wipro

SO, SDN-R, New Policies



2

Activate, Deactivate flows support in external  RAN NSSMF

To support the activate and deactivate actions in E2E Network Slicing with External NSSMFs (option2). Currently, instantiation and termination are supported.

Enhancement

2

Yogendra

Aarna Networks


Yes

 

 Deferred to K-release

3

Capacity based NSI/NSSI Selection

In 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 in NSI/NSSI selection based on this criteria.

New

2

Ahila

Wipro

SO, OOF, DCAE

Yes

Completed

4

Core, RAN Endpoints Discovery at NSMF

Hardcoded 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

New

1

Ahila

Wipro

SO (NSMF), SDN-R

Yes

Deferred to K-release

5

NSI 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

Enhancement

1

Ahila

Wipro

SO, OOF



6

IBN based E2E Slicing

Communication service request is given as business intent and it should be integrated with the existing E2E slice flow.

New

3

Dong Wang

China Telecom



Descoped for this release

7

CSIT Continuation (SO, SDN-R)

CSIT test cases for SO and SDNC component testing

Carry forward

1

Ahila

Wipro


Yes

 

8

Use case Automation

E2E network Slicing use case test automation

New

1

Ahila

Wipro


Yes

 

 In progress. It will be continued in the next release.

9

Populate 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 Slice

New

2





Proposed by Yogendra. 


02-11-2021: Received a comment from Lin and Alessandro that this feature is not significant in the market. so deferring this requirement for now


RAN Slicing

1

cm-handle registration with CPS-DMI Plugin - Integration

cm-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-release

New

1

Ahila

Wipro

SDN-R

Yes

 

 Completed

2

Instantiation of RAN NFs and initial configuration (stretch goal)

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/CNFs

New

3

 

 

 

 

Owner not identified yet.

3

CPS Integration with SDN-R

RANSlice allocate and reconfigure rpcs to be integrated with CPS for RAN configurations persistence

Carry forward

1

Ahila

Wipro

SDN-R

Yes

 

 Completed

4

CPS Integration Stabilization

Validate and bug fix of CPS integration for RAN slice lifecycle

Carry forward

1

Ahila

Wipro

SDN-R

Yes

 

 RAN slice Termination - RRM Policy update is deferred to next release

5

CPS-TBDMT enhancement to integrate with NCMP

CPS Core is directly invoked from TBDMT. The call should go via NCMP to CPS-Core

Enhancement

1

Ahila

Wipro

CPS-TBDMT

Yes

 

 Descoped, as this interface is not possible for primary yang model with the current architecture




 

 

 

 

 

 

 


Core Slicing

1

ETSI aligned Core NSSMF

Leverage Core NSSMF to be in an alignment with SOL-005 APIs while supporting the existing Non-ETSI (3GPP) interfaces

New

3

 

 

 

 

Owner not identified yet.

2

New NFs are not getting instantiated for allocateNSSI request having same NSST

Not able to create more than one non-shared Core Slice. It needs a fix at ExtAPI/NBI

Enhancement

1

 

 

 

 Yes

Solution given by Sanchita, and will be implemented & tested by Alessandro & Team

Completed

3

CSIT for core slicing

CSIT test cases for Core NSSMF


1

 

 

 

 

Owner not identified yet.


Transport Slicing

1

Support for modify-deallocate in TN-NSSMF


Enhancement

1

Henry Yu

Huawei



Deferred

2

TN NSSMF enhancements according to IETF latest specification


Enhancement

3

Henry Yu

Huawei

SO, SDN-R

Yes

 

 Deferred

3

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


New

1

Ahila

Wipro

SO, Policy

Yes

 

 Completed

4

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


New

1

Ahila

Wipro

SO, Policy

Yes

 

 Completed

5

CSIT for transport slicing



1

Henry Yu

Huawei


Yes

 

 Deferred

6

Transport Slicing enhancement to support IBN based E2E slicing


New

1

Henry Yu

Huawei


Yes

 

 Covered as part of CCVPN use case

7

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


New

1

Henry Yu

Huawei


Yes

 

 Covered as part of CCVPN use case


Closed Loop

 

 

 

 

 

 

 

 

1

IBN based Closed loop

Make use of intents/ML models for closed loop

New

3

Dong Wang

China Telecom

DCAE

Yes

Completed

ml-prediction-ms is under review

2

Closed loop updates over A1 interface - enhancements

Done 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 enhancements

Enhancement

1

Ahila

Wipro

SDN-R, RAN Simulator



3

CPS Integration Stabilization

Validate and enhance CPS integration for closed loop

Carry forward

1

Ahila

Wipro

SDN-R

Yes

 

 Completed

 



 

 





 

 

KPI Monitoring

1

KPI Computation MS Remaining Requirements (Mark Scott’s comments)

https://jira.onap.org/browse/DCAEGEN2-2801

Carry forward

1

Ahila

Wipro

KPI MS




DCAE specific









1

CBS SDK latest version usage:







Yes

Completed

2

No-root access to DB from APPlication - TCA-gen2 MS, PM-Mapper







Yes

Deferred

3

Use integration image version for DCAE components







Yes

Completed

4

Dmaap SDK








Not confirmed yet