R9 E2E Testing
- Swaminathan Seetharaman
- Ahila P
- LTE Next Generation
- Deepika S
Legend:
NOT STARTED IN PROGRESS DEFERRED COMPLETED
E2E Integration Tests
Responsibles: @Ahila P, @Ratna Shankers:@Deepika S, @LTE Next Generation
Option 1: RAN NSSMF shall be responsible for entire RAN subnet, including RAN NFs, FH and MH. All 3 NSSMFs are within ONAP.
S.No. | Topic | Description | Dependency | Tester | Status | Remarks | Progress update |
|---|---|---|---|---|---|---|---|
1 | Service Design | Design of CST, and necessary templates for 1 type of service (e.g., eMBB): NST, NSST for RAN, RAN NF, Core & TN, Service Profile and Slice Profiles | @Deepika S | COMPLETED | |||
2 | Design of necessary templates for 2nd type of service (e.g., mMTC): NST, NSST for RAN, RAN NF, Core & TN, Service Profile and Slice Profiles | @Deepika S | DEFERRED | For mMTC, the performance requirements needs to be finalized, this will be deferred to next release. | |||
3 | Service instantiation | See below table for (a) to (g) | @Deepika S | COMPLETED | Assumption is manual intervention does not override ONAP selection | ||
4 | Service instantiation with manual intervention | For scenario (c) in below table, operator shall override via NSMF portal in UUI the selection of reusable NSI and indicate creation of new NSI. | (c) for service instantiation should work first | @LTE Next Generation | deferred | ||
5 | Service activation | Activate a service - this should result in activation of new NSI and associated new NSSIs. | (a) or (b) for service instantiation should work first. | @LTE Next Generation | deferred | ||
6 | Activate a service - this should result in activation of S-NSSAI, and the activate command should pass to all the NSSMFs | (c) for service instantiation should work first | @LTE Next Generation | deferred | |||
7 | Service deactivation | Dectivate a service - this should result in deactivation of new NSI and associated new NSSIs. | Test case 5 should be completed | @LTE Next Generation | deferred | ||
8 | Dectivate a service - this should result in deactivation of S-NSSAI, and the deactivate command should pass to all the NSSMFs | Test case 6 should be completed | @LTE Next Generation | deferred | |||
9 | Service termination | Terminate a service - this should terminate NSI and ALL associated NSSIs. Note: The proper configuration updates should be sent to the RAN NFs. | At least 1 service instantiation test case should be completed | @Deepika S | deferred | CN NSSMF - deallocateNSSI WF needs to be fixed | |
10 | Terminate a service - this should terminate NSI but terminate only RAN NSSI and TN BH NSSI, and not Core NSSI (Assumption: RAN NSSI terminated => RAN NF NSSI terminated, TN FH and MH NSSIs terminated) Note: The proper configuration updates should be sent to the RAN and Core NFs, and to TN NSSMF (for FH and MH NSSIs, using deallocateNSSI API). | At least 1 service instantiation test case involving reuse should be completed | @Deepika S | COMPLETED | This can happen when only 1 Service Profile is linked to NSI and 1 Slice Profile each is linked to RAN & TN BH NSSIs, but > 1 Slice Profile is linked to Core NSSI. | ||
Terminate a service - this should terminate NSI but terminate only Core NSSI and TN BH NSSI, and not RAN NSSI (Assumption: RAN NSSI not terminated => RAN NF NSSI not terminated, TN FH and MH NSSIs not terminated) Note: The proper configuration updates should be sent to the RAN NFs and TN NSSMF (for FH and MH NSSIs, using modifyNSSI API). | At least 1 service instantiation test case involving reuse should be completed | @Deepika S | deferred | This can happen when only 1 Service Profile is linked to NSI and 1 Slice Profile each is linked to Core & TN BH NSSIs, but > 1 Slice Profile is linked to RAN NSSI. | CN NSSMF - deallocateNSSI WF needs to be fixed | ||
12 | Terminate a service - this should terminate NSI but terminate only Core NSSI and TN BH NSSI, and not RAN NSSI (Assumption: RAN NSSI not terminated => RAN NF NSSI not terminated, TN FH and MH NSSIs not terminated) Note: The proper configuration updates should be sent to the RAN NFs, Core NFs and TN NSSMF (for FH and MH NSSIs, using modifyNSSI API). | At least 1 service instantiation test case involving reuse should be completed | @Deepika S | deferred | This can happen when only 1 Service Profile is linked to NSI and > 1 Slice Profile each is linked to RAN, Core & TN BH NSSIs. | CN NSSMF - deallocateNSSI WF needs to be fixed | |
13 | KPI Computation | Operator should be able to view a KPI within a given time range (a KPI that is computed by KPI MS) via UUI | KPI Computation MS policies should be configured properly, DES termplates should be set up | @LTE Next Generation | deferred | ||
14 | Closed Loop | Initiate PM data generation from RAN and show the Closed Loop action triggered by ONAP, and updates done in RAN (using RAN-Sim) | @Niranjana Y | COMPLETED | |||
15 | Intelligent Slicing | Initiate PM data generation from RAN and show ML-based Closed Loop action triggered by ONAP, and updates done in RAN (using RAN-Sim) | @Niranjana Y | COMPLETED |
Service Instantiation scenarios (test case 3 above)
Notes:
Should involve call to NSMF, calls to NSSMFs (allocate or modifyNSSI API calls), and then SB calls/actions on NSSI constituents. In case of RAN NSSI, it should involve calls to TN (for FH and MH) and RAN NF NSSI creation/update.
TN NSSMF supports reuse of TN NSSI only when the NSI is reused. This is because, the interface from SO (TN NSSMF) to OOF for TN NSSI selection is not yet implemented.
Similarly deallocateNSSI call to TN NSSI shall result in TN NSSI being terminated.
S.No. | Priority | Input service | NSI | RAN NSSI | Core NSSI | TN BH NSSI | Tester | Status | Remarks |
|---|---|---|---|---|---|---|---|---|---|
a | 1 | eMBB like service parameters No sharing | New | New | New | New | @Deepika S | COMPLETED | |
b | 1 | eMBB like service parameters Sharing allowed | New | New | New | New | @Deepika S | COMPLETED | Pre-requisite: There is no existing shareable suitable NSI or NSSIs |
c | 1 | eMBB like service parameters Sharing allowed | Reuse | X | X | X | @Deepika S | COMPLETED | X = don't care as automatically all NSSIs are reused |
d | 1 | eMBB or mMTC like service parameters Sharing allowed | New | Reuse | New | New | @Deepika S | COMPLETED | Pre-requisite: There is an existing RAN NSSI that is suitable and can be reused. This requires either providing the service parameters in such a way RAN NSSI is reused, or creating a suitable and shareable RAN NSSI upfront. |
e | 1 | eMBB or mMTC like service parameters Sharing allowed | New | New | Reuse | New | @Deepika S | COMPLETED | Pre-requisite: There is an existing Core NSSI that is suitable and can be reused. This requires either providing the service parameters in such a way Core NSSI is reused, or creating a suitable and shareable Core NSSI upfront. |
f | 2 | eMBB or mMTC like service parameters Sharing allowed | New | Reuse | Reuse | New | @Deepika S | COMPLETED | Pre-requisite: There is an existing RAN & Core NSSI that is suitable and can be reused. This requires either providing the service parameters in such a way RAN & Core NSSI are reused, or creating suitable and shareable RAN & Core NSSIs. |
g | 2 | eMBB or mMTC like service parameters. with coverageArea more than what is already supported in a suitable existing and shareable NSI Sharing allowed | New | New | New | New | @Deepika S | DEFERRED | Pre-requisite: There should be a suitable existing NSI that is shareable, but whose coverageArea is smaller or does not have full overlap with the new service request. |
(Stretch Goal) Option 2: RAN NSSMF shall be responsible for RAN NFs alone. FH and MH are not included. Only TN NSSMF is within ONAP.
<Note: This section is being updated>
Remark: Core NSSMF can be inside ONAP or outside ONAP for this Option. Only RAN NSSMF has to be outside ONAP.
S.No. | Topic | Description | Dependency | Tester | Status | Remarks |
|---|---|---|---|---|---|---|
1 | Service Design | Design of CST, and necessary templates for 1 type of service (e.g., eMBB): NST, NSST for RAN, RAN NF, Core & TN, Service Profile and Slice Profiles | COMPLETED | |||
2 | Design of necessary templates for 2nd type of service (e.g., mMTC): NST, NSST for RAN, RAN NF, Core & TN, Service Profile and Slice Profiles | DEFERRED | For mMTC, the performance requirements needs to be finalized, this will be deferred to next release. | |||