Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Legend:

NOT STARTED IN PROGRESS DEFERRED COMPLETED

E2E Integration Tests


  1. Instantiation - create new NSI (not-shared, no match with shared, all matching are not-shared, different coverageArea so not matching)
    1. RAN NSSI - new, Core NSSI - new, TN BH NSSI - new
      1. RAN NF NSSI - new, ??
    2. RAN NSSI - reuse, Core NSSI - new, TN BH NSSI - new
    3. RAN NSSI - new, Core NSSI - reuse, TN BH NSSI - new
    4. RAN NSSI - new, Core NSSI - new, TN BH NSSI - reuse
    5. RAN NSSI - reuse, Core NSSI - reuse, TN BH NSSI - new
    6. RAN NSSI - reuse, Core NSSI - new, TN BH NSSI - reuse
    7. RAN NSSI - new, Core NSSI - reuse, TN BH NSSI - reuse
    8. 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)
  2. Instantiation - reuse existing NSI
  3. Activation
  4. Deactivation
  5. Termination


Test Automation

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.TopicDescriptionDependencyTesterStatusRemarks
1.Service Design

1a. 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

1b. 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



NOT STARTED


2.Service instantiationSee below table










NSIRAN NSSICore NSSITN NSSI




Option 2: RAN NSSMF shall be responsible for RAN NFs alone. FH and MH are not included. Only TN NSSMF is within ONAP.

Note: Core NSSMF can be inside ONAP or outside ONAP for this Option. Only RAN NSSMF has to be outside ONAP.

S.No.TopicDescriptionDependencyTesterStatusRemarks





















  • No labels