Skip to end of metadata
Go to start of metadata
You are viewing an old version of this content. View the current version.
Compare with Current
View Version History
« Previous
Version 4
Next »
Carry over tests from H-release
S.No | Topic | Description | Dependency | Tester | Status | Remarks |
---|
NSMF_18 | Service instantiation (Option 1) - Reuse existing NSI | NSMF (SO) triggers OOF for obtaining Slice Profiles for the new Service Profile when an existing NSI is reused, and OOF provides the Slice Profiles. |
|
|
| A fix was provided in SO (NSMF) (SO-3629) which will officially be available on H-release-MNT. |
NSMF_16 | Service instantiation (Option 2) - New NSI | NSMF (SO) triggers External RAN NSSMF with modifyNSSI operation via the NSSMF adaptor (it also sends info of NSSI to be reused), and RAN NSSI is updated successfully. RAN EP info is updated in AAI by NSMF Adaptor. |
|
|
|
|
NSMF_17 | Service instantiation (Option 1) - Reuse existing NSI | NSMF (SO) triggers OOF for NSI selection (passing Service Profile, NST and sub-net capabilities), resulting in OOF providing details of existing NSI to be reused in the response. |
|
|
|
|
NSMF_18 | Service instantiation (Option 1) - Reuse existing NSI | NSMF (SO) triggers OOF for obtaining Slice Profiles for the new Service Profile when an existing NSI is reused, and OOF provides the Slice Profiles. |
|
|
|
|
Integration Testing Matrix
- Design - Option 1, Option 2
- Instantiation - create new NSI (not-shared, no match with shared, all matching are not-shared, different coverageArea so not matching)
- RAN NSSI - new, Core NSSI - new, TN BH NSSI - new
- RAN NF NSSI - new, ??
- RAN NSSI - reuse, Core NSSI - new, TN BH NSSI - new
- RAN NSSI - new, Core NSSI - reuse, TN BH NSSI - new
- RAN NSSI - new, Core NSSI - new, TN BH NSSI - reuse
- RAN NSSI - reuse, Core NSSI - reuse, TN BH NSSI - new
- RAN NSSI - reuse, Core NSSI - new, TN BH NSSI - reuse
- RAN NSSI - new, Core NSSI - reuse, TN BH NSSI - reuse
- RAN NSSI - reuse, Core NSSI - reuse, TN BH NSSI - reuse (but all 3 are not part of same NSI, otherwise that NSI would have been reused)
- Instantiation - reuse existing NSI
- Activation
- Deactivation
- Termination