Versions Compared

Key

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

Jira reference: 
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-632

Test lab: Winlab

Summary: The following test cases are deferred to Istanbul. Remaining tests are completed.

  • Test cases related to terminating RAN NSSI
  • Testcases related to interactions with TN NSSMF for FH/BH NSSI reuse
  • A couple of minor aspects related to SDN-R and its interaction with RAN are also deferred to Istanbul

Legend:

Status
titleNOT STARTED
 IN PROGRESS DEFERRED COMPLETED

Italics - Regression test cases

S. No.TopicTest Case DescriptionPriorityDependency/IssueTesterStatusRemarks
RAN_01Service/template designSuccessful design of RAN NSST, RAN NF NSST, RAN Slice Profile and RAN NF Slice Profile Templates1

Status
colour

Blue

Green
title

NOT STARTED

COMPLETED


RAN_02
Service instantiation (Option 1) - New NSI, new RAN NSSI
Provide RAN subnet capabilities when queried by NSSMF adaptor1
Service instantiation (Option 1) - New NSI, new RAN NSSIWhen triggered by NSSMF Adaptor with allocateNSSI for allocating a new RAN NSSI, RAN NSSMF (SO) triggers OOF for RAN NSSI selection, OOF provides Slice Profiles for RAN NF, TN FH and TN MH NSSIs (i.e., creation of a new RAN NSSI).
31COM_07AN_05
1

Status
colourGreen
titleCOMPLETED


RAN_03Service instantiation (Option 1) - New NSI, new RAN NSSISO (RAN NSSMF) creates new RAN NF NSSI and configuring it by calling SDN-R. AAI is also updated with relevant Slice Profile info.
31RAN_03Reshmasree, PriRAN_04
1
Deepika S

Status
colourGreen
titleCOMPLETED


RAN_04Service instantiation (Option 1) - New NSI, new RAN NSSISDN-R updates Config DB with the details of the new RAN NSSI and S-NSSAI and other configuration details (e.g., RRM Policy, Slice Profile) for the new S-NSSAI
32
1
,

  / Ahila

NOT YET TESTED

Status
colourGreen
titlecompleted


RAN_
06RAN_04
05Service instantiation (Option 1) - New NSI, new RAN NSSISDN-R configures RAN NFs (CUs, DUs, Near-RT RICs) with the info related to the new RAN NSSI/S-NSSAI (by sending suitable (netconf) messages to RAN-Sim) and updates SO of the completion.
32
1
, AhilaIN PROGRESS

  / Ahila P

Status
colourGreen
titlecompleted

There are some minor issues in RAN-Sim, but from SDN-R perspective it is OK.
RAN_
07
06Service instantiation (Option 1) - New NSI, new RAN NSSISO (RAN NSSMF) triggers SO (TN NSSMF) for allocation of FH and MH NSSIs. It passes the respective Slice Profiles (determined by OOF), and static values of endpoints for FH and MH to TN NSSMF.
32RAN_06Reshmasree, Priyadharshini

COMPLETED

RAN_08Reshmasree, Priyadharshini
1
Deepika S

Status
colourGreen
titleCOMPLETED

Skipped SDNC workflow for the Transport domain integration with ACTN simulator, please follow:  SO-3444



RAN_07Service instantiation (Option 1) - New NSI, new RAN NSSISO (RAN NSSMF) makes suitable updates to AAI about Slice Profiles, RAN NF NSSI, etc.
32RAN_07
1

Status
colourGreen
titleCOMPLETED


RAN_
09RAN_10
08Service instantiation (Option 1) - New NSI, new RAN NSSIUpon reception of completion indication from TN NSSMF (for FH and MH subnets), SO (RAN NSSMF) informs NSSMF Adaptor of SO about completion of RAN NSSI creation
32RAN_07Reshmasree, Priyadharshini

PARTIALLY COMPLETED

1

Status
colourGreen
titleCOMPLETED

Skipped SDNC workflow for the Transport domain integration with ACTN simulator, please follow:  SO-3444
RAN_09Service instantiation (Option 1) - New NSI, reuse RAN NSSIWhen triggered by NSSMF Adaptor with allocateNSSI for allocating a new RAN NSSI, SO (RAN NSSMF) triggers OOF for RAN NSSI selection, OOF provides existing RAN NSSI (i.e., reuse of an existing RAN NSSI).1
5

Status

2IN PROGRESS

colour

COM_07Reshmasree, Priyadharshini

Green
titleCOMPLETED


RAN_
11
10Service instantiation (Option 1) - New NSI, reuse RAN NSSISO (RAN NSSMF) calls OOF a second time for obtaining the Slice Profiles for RAN NF NSSI, TN FH and MH NSSIs. Slice Profile details are then updated in AAI.
52RAN_10Reshmasree, PriyadharshiniIN PROGRESS
1

Status
colourGreen
titleCOMPLETED


RAN_
12IN PROGRESS
11Service instantiation (Option 1) - New NSI, reuse RAN NSSISO (RAN NSSMF) calls SDN-R for configuring the existing RAN NF NSSI (reuse) with the new S-NSSAI and Slice Profile
52RAN_11Reshmasree, Priyadharshini
1

Status
colourGreen
titleCOMPLETED


RAN_
13
12Service instantiation (Option 1) - New NSI, reuse RAN NSSISDN-R updates Config DB with the details of the RAN NSSI and S-NSSAI and other configuration details (e.g., RRM Policy, Slice Profile) for the new S-NSSAI
52RAN_12
1
, AhilaNOT YET TESTED

  / Ahila P

Status
colourGreen
titlecompleted


RAN_
14RAN_13
13Service instantiation (Option 1) - New NSI, reuse RAN NSSISDN-R sends relevant (netconf) messages to RAN-Sim for updating the RAN NFs (CUs, DUs, Near-RT RICs) with details of the new S-NSSAI, RRM Policy updates, Slice Profile, etc.
52
1
, AhilaNOT YET TESTED

  / Ahila P

Status
colourGreen
titlecompleted

There are some minor issues in RAN-Sim, but from SDN-R perspective it is OK.
RAN_
15
14Service instantiation (Option 1) - New NSI, reuse RAN NSSISO (RAN NSSMF) calls SO (TN NSSMF) for configuring the existing TN FH/MH NSSIs (reuse) with the new S-NSSAI and respective Slice Profiles using modifyNSSI API.
5NOT YET TESTED
1
2RAN_12Reshmasree, Priyadharshini

DEFERRED

This test case is only partially completed. So, it is deferred to Istanbul
RAN_
16
15Service instantiation (Option 1) - Reuse existing NSI

When triggered by NSSMF Adaptor with modifyNSSI for reusing an existing NSI, SO (RAN NSSMF) triggers OOF for obtaining the Slice Profiles of RAN NF, TN FH and TN MH subnets for updating the respective NSSIs. Slice Profile details are then updated in AAI.

(Remaining flows are similar to test cases RAN_

12

11 to RAN_

15

14)

7IN PROGRESS
1
2COM_20Reshmasree, Priyadharshini

DEFERRED

This test case is only partially completed. So, it is deferred to Istanbul
RAN_
17Reshmasree, Priyadharshini
16Service activation (Option 1)When triggered by NSSMF Adaptor with activateNSSI for activating the RAN NSSI, SO (RAN NSSMF) triggers SDN-R for activating the S-NSSAI in the RAN NFs.
91COM_24
1

Status
colourGreen
titleCOMPLETED


RAN_
18
17Service activation (Option 1)SDN-R sends relevant (netconf) messages to RAN NFs (RAN-Sim) (CUs, DUs, Near-RT RICs) for activation of the S-NSSAI.
9
2
RAN_17

, AhilaNOT YET TESTED

  / Ahila P

Status
colourGreen
titlecompleted


RAN_
19
18Service activation (Option 1)SO (RAN NSSMF) triggers SO (TN NSSMF) for activating the TN FH and TN MH NSSIs.
91RAN_17Reshmasree, Priyadharshini

IN PROGRESS

RAN_20
1

Status
colourGreen
titleCOMPLETED

Skipped SDNC workflow for the Transport domain integration with ACTN simulator, please follow:  SO-3444
RAN_19Service deactivation (Option 1)When triggered by NSSMF Adaptor with deactivateNSSI for deactivating the RAN NSSI, SO (RAN NSSMF) triggers SDN-R for deactivating the S-NSSAI in the RAN NFs.1
10

Status

2Reshmasree, Priyadharshini

colour

COM_25

Green
titleCOMPLETED


RAN_
21
20Service deactivation (Option 1)SDN-R sends relevant (netconf) messages to RAN NFs (RAN-Sim) (CUs, DUs, Near-RT RICs) for deactivation of the S-NSSAI.
10
2
RAN_20

, AhilaNOT YET TESTED

  / Ahila P

Status
colourGreen
titlecompleted


RAN_
22
21Service deactivation (Option 1)SO (RAN NSSMF) triggers SO (TN NSSMF) for deactivating the TN FH and TN MH NSSIs.
102RAN_20Reshmasree, Priyadharshini

IN PROGRESS

RAN_23IN PROGRESS
1

Status
colourGreen
titleCOMPLETED

Skipped SDNC workflow for the Transport domain integration with ACTN simulator, please follow:  SO-3444
RAN_22Service termination (Option 1)When triggered by NSSMF Adaptor with modifyNSSI for removing S-NSSAI, SO (RAN NSSMF) triggers SDN-R for removing the S-NSSAI in the RAN NFs. Slice Profile of RAN NF NSSI is also removed.
112COM_29Reshmasree, Priyadharshini
1

Status
colourGreen
titleCOMPLETED


RAN_
24RAN_23
23Service termination (Option 1)SDN-R makes relevant updates to ConfigDB (removal of S-NSSAI and RAN NF Slice Profile, RRM Policy update)
112
1
,

  / Ahila

NOT YET TESTED

DEFERRED

This test case is partially completed (Slice Profile removal is not yet checked). So it is deferred to Istanbul.
RAN_
25
24Service termination (Option 1)SDN-R sends relevant (netconf) messages to RAN-NFs (CUs, DUs, Near-RT RICs) of S-NSSAI removal, and update of RRM Policy, etc.
11
2
RAN_24

, AhilaNOT YET TESTED

  / Ahila P

DEFERRED

This test case is partially completed - there are some minor issues in RAN-Sim.
RAN_
26
25Service termination (Option 1)SO (RAN NSSMF) triggers SO (TN NSSMF) for updating the TN FH and TN MH NSSIs. Slice Profiles of TN FH and MH NSSIs are also removed.
11NOT YET TESTED
1
2RAN_23Reshmasree, Priyadharshini
TN NSSMF

DEFERRED

TN NSSMF interactions are deferred to Istanbul.
RAN_
27
26Service termination (Option 1)

When triggered by NSSMF Adaptor with deallocateNSSI API, SO (RAN NSSMF) calls OOF to determine if RAN NSSI has to be terminated. OOF returns RAN NSSI should not be terminated. (Remaining steps are the same as in test cases RAN_

23

22 to RAN_

26

25)

12NOT YET TESTED
2
COM_30Reshmasree, Priyadharshini

DEFERRED


RAN_
28
27Service termination (Option 1)When triggered by NSSMF Adaptor with deallocateNSSI API, SO (RAN NSSMF) calls OOF to determine if RAN NSSI has to be terminated. OOF returns RAN NSSI should be terminated.
12RAN_29
3
2COM_30Reshmasree, Priyadharshini

NOT YET TESTED


DEFERRED

Deferred to Istanbul release. OOF has some problems and can not support Option1 model. Waiting for OOF changes to be tested
RAN_28Service termination (Option 1)SO (RAN NSSMF) calls OOF to determine if RAN NF NSSI has to be terminated. OOF returns that RAN NF NSSI should be terminated.
12RAN_30
3
2RAN_28Reshmasree, Priyadharshini

NOT YET TESTED


DEFERRED

Deferred to Istanbul release. OOF has some problems and can not support Option1 model. Waiting for OOF changes to be tested
RAN_29Service termination (Option 1)

SO (RAN NSSMF) triggers SDN-R for removing the S-NSSAI in the RAN NFs. Slice Profile of RAN NF NSSI and RAN NF NSSI are also removed.

(SDN-R actions are covered in test cases RAN_

24

23 and RAN_

25

24)

12NOT YET TESTED
1
2RAN_29Reshmasree, Priyadharshini

DEFERRED

Deferred to Istanbul release. OOF has some problems and can not support Option1 model. Waiting for OOF changes to be tested
RAN_30Service termination (Option 1)SO (RAN NSSMF) triggers SO (TN NSSMF) with deallocateNSSI API call for deallocation of TN FH and TN MH NSSIs
12NOT YET TESTED
1
2RAN_29Reshmasree, Priyadharshini

DEFERRED

Deferred to Istanbul release. OOF has some problems and can not support Option1 model. Waiting for OOF changes to be tested
RAN_31Service termination (Option 1)

When OOF returns that RAN NSSI should be terminated, SO (RAN NSSMF) calls OOF to determine if RAN NF NSSI has to be terminated. OOF returns that RAN NF NSSI should not be terminated.

(RAN NF NSSI update actions are covered by RAN_

23

22 to RAN_

25

24, and TN FH and MH NSSI actions are covered by RAN_30)

12NOT YET TESTED
3
2RAN_28Reshmasree, Priyadharshini

DEFERRED

Deferred to Istanbul release. OOF has some problems and can not support Option1 model. Waiting for OOF changes to be tested