94
OCTASIC_INTRA- HO_HSDPA_TC_001 Verify that HNB supports Intra frequency Handover for 16 HSDPA/64 call. OCTASIC_INTRA- HO_HSDPA_TC_002 Verify that HNB supports Intra frequency Handover for 4 CS (AMR12.2) + 4 HSDPA/64 call. Test Case ID Test Case Objec tive

2.1 Release Master Tracker

  • Upload
    amuduli

  • View
    225

  • Download
    0

Embed Size (px)

Citation preview

Page 1: 2.1 Release Master Tracker

OCTASIC_INTRA-

HO_HSDPA_TC_001

Verify that HNB supports Intra

frequency Handover for 16

HSDPA/64 call.

OCTASIC_INTRA-

HO_HSDPA_TC_002

Verify that HNB supports Intra

frequency Handover for 4 CS

(AMR12.2) + 4 HSDPA/64 call.

Test

Case

ID

Test

Case

Ob

jec

tive

Page 2: 2.1 Release Master Tracker

OCTASIC_INTRA-

HO_HSDPA_TC_003

Verify that HNB supports Intra

frequency Handover for 4

PS64/64 + 4 HSDAP/64 call.

OCTASIC_INTRA-

HO_HSDPA_TC_004

Verify that HNB supports Intra

frequency Handover for 4 CS64

+ 4 HSDPA/64 call.

Page 3: 2.1 Release Master Tracker

OCTASIC_INTRA-

HO_HSDPA_TC_005

Verify that HNB supports Intra-

frequency Handover for 2

AMR12.2 + 2 CS64 + 4

HSDPA/64.

OCTASIC_INTRA-

HO_HSDPA_TC_006

Verify that HNB supports Intra-

frequency Handover for 2

AMR12.2 + 2 PS64/64 + 4

HSDPA/64.

Page 4: 2.1 Release Master Tracker

OCTASIC_INTRA-

HO_HSDPA_TC_007

Verify that HNB supports Intra-

frequency Handover for 2 CS64

+ 2 PS64/64 + 4 HSDPA/64.

OCTASIC_INTRA-

HO_HSDPA_TC_008

Verify HNB supports setup of

HSDPA calls after the Intra-

frequency HO (16 UE).

Page 5: 2.1 Release Master Tracker

OCTASIC_INTRA-

HO_HSDPA_TC_009

Verify HNB supports Intra-

Frequency HO for 8 HSDPA/64

calls, when already 8 CS

(AMR12.2) calls are active at

HNB2.

OCTASIC_INTRA-

HO_HSDPA_TC_010

Verify setup of CS (AMR12.2)

call after Intra-frequency HO of

16 HSDPA/64 call and vice

versa.

Page 6: 2.1 Release Master Tracker

OCTASIC_INTRA-

HO_HSDPA_TC_011

Verify setup of CS 64 call after

Intra-frequency HO of 16

HSDPA/64 call and vice versa.

OCTASIC_INTRA-

HO_HSDPA_TC_012

Verify setup of PS64/64 call

after Intra-frequency HO of 16

HSDPA/64 call and vice versa.

Page 7: 2.1 Release Master Tracker

OCTASIC_INTRA-

HO_HSDPA_TC_013

Verify Intra frequency HO fails

for HSDPA/64 call, when Intra-

frequency flag is disabled in the

target HNB(HNB2).

OCTASIC_INTRA-

HO_HSDPA_TC_014

Verify Intra-frequency HO fails

for HSDPA call, when Max DCH

user is reached in the target

HNB

OCTASIC_INTRA-

HO_HSDPA_TC_015

Verify Intra-frequency HO fails

for 1 HSDPA call while 16 UEs

are moving to target HNB when

1 UE is already on target HNB.

Page 8: 2.1 Release Master Tracker

OCTASIC_INTRA-

HO_HSDPA_TC_016

Verify that HNB supports Intra

frequency Handover for 16

HSDPA/64 call when CN Send

LOCATION REPORTING

CONTROL message for all UEs

before HO and After

HO.(Service Area)

OCTASIC_INTRA-

HO_HSDPA_TC_017

Verify that HNB supports Intra

frequency Handover for 16

HSDPA/64 call when there are

two target HNBs.

Page 9: 2.1 Release Master Tracker

OCTASIC_INTRA-

HO_HSDPA_TC_018

Verify that HNB supports Intra

frequency Handover for 16

HSDPA/64 call when there are

two target HNB and HO is failed

at Intermediate Target.

OCTASIC_INTRA-

HO_HSDPA_TC_019

Verify the working of HNB for

Intra frequency Handover for 2

HSDPA/64 call for 10 ping pong.

Page 10: 2.1 Release Master Tracker

OCTASIC_INTRA-

HO_HSDPA_TC_020

Verify that HNB supports Intra

frequency Handover for 16

HSDPA/64 call(one direction).

OCTASIC_INTRA-

HO_HSDPA_TC_021

Verify HNB supports setup of

HSDPA calls after the Intra-

frequency HO (16 UE) at source.

Page 11: 2.1 Release Master Tracker

OCTASIC_INTRA-

HO_HSDPA_TC_022

Verify Relocation cancel

procedure for Source HNB when

RB Reconfig failure is received

from the UE which is attached

to the Source HNB. Cause:

configuration unsupported

(Can be Tested with UE

simulator only)

OCTASIC_INTRA-

HO_HSDPA_TC_023

Verify that HNB is

handling(ignoring) the invalid

intra frequency event(1A, 1B,

1D) received in Measurement

report (UE simulator).

OCTASIC_INTRA-

HO_HSDPA_TC_024

Verify the HNB for handling of

Measurement control failure

from the UE (UE simulator is

needed) (cause as "unsupported

measurement").

Page 12: 2.1 Release Master Tracker

OCTASIC_INTRA-

HO_HSDPA_TC_025

Verify HNB is able to handle

flooding of Measurement report

from UE (UE simulator is

needed)

OCTASIC_INTRA-

HO_HSDPA_TC_026

Verify HNB supports CELL

Update received during

maesurement (UE simulator is

needed)

OCTASIC_INTRA-

HO_HSDPA_TC_027

Verify HNB supports CELL

Update received during

relocation (UE simulator is

needed)

OCTASIC_INTRA-

HO_HSDPA_TC_028

Verification of MRAB(AMR 12.2

+ HSDPA/64) HO is not

supported.

Page 13: 2.1 Release Master Tracker

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Attach 16 UEs to HNB1.

5) Trigger HSDPA/64 call from all UEs.

6) Start FTP download of 100 MB file from all UEs. Note down CPU and memory utilization.

7) Move all UEs towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2.

8) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that downloads are

working fine after HO.

9) Bring back all UEs from HNB2 to HNB1 until 1F and 1C occurs and HO is triggered from HNB2 to HNB1. Note down

CPU and memory utilization.

10) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that downloads are

working fine after HO.

11) Repeat step 7 to 10 for three times.

12) Disconnect all HSDPA/64 calls and verify all calls are released properly.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

3) Calculate and update the average CPU and average Memory utilization in the corresponding column.

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Attach 8 UEs to HNB1.

5) Trigger CS (AMR12.2) call from UE#1->UE#2, UE#3->UE#4 and HSDPA/64 call from UE#5 UE#6, UE#7, UE#8.

6) Start 100 MB file download from UE#5 UE#6, UE#7, UE#8. Note down CPU and memory utilization. Verify that CS calls

and downloads are working fine.

7) Move all UEs towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2.

8) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that CS calls and

downloads are working fine after HO.

9) Bring back all UEs from HNB2 to HNB1 until 1F and 1C occurs and HO is triggered from HNB2 to HNB1. Note down

CPU and memory utilization.

10) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that CS calls and

downloads are working fine after HO.

11) Repeat step 7 to 10 for three times.

12) Disconnect all CS and HSDPA/64 calls and verify all calls are released properly.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

3) Calculate and update the average CPU and average Memory utilization in the corresponding column.

Test

Case

Pro

ce

du

res

Page 14: 2.1 Release Master Tracker

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Attach 8 UEs to HNB1.

5) Trigger PS64/64 call from UE#1, UE#2, UE#3, UE#4 and HSDPA/64 call from UE#5, UE#6, UE#7, UE#8.

6) Start 10 MB file download from UE#1, UE#2, UE#3, UE#4 and 100 MB file download from UE#5, UE#6, UE#7, UE#8.

Note down CPU and memory utilization. Verify that downloads are working fine.

7) Move all UEs towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2.

8) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that downloads are

working fine after HO.

9) Bring back all UEs from HNB2 to HNB1 until 1F and 1C occurs and HO is triggered from HNB2 to HNB1. Note down

CPU and memory utilization.

10) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that downloads are

working fine after HO.

11) Repeat step 7 to 10 for three times.

12) Disconnect all HS and PS calls and verify all calls are released properly.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

3) Calculate and update the average CPU and average Memory utilization in the corresponding column.

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Attach 8 UEs to HNB1.

5) Trigger CS64 call from UE#1->UE#2, UE#3->UE#4 and HSDPA/64 call from UE#5, UE#6, UE#7, UE#8.

6) Start 100 MB file download from UE#5, UE#6, UE#7, UE#8. Note down CPU and memory utilization. Verify that CS

calls and downloads are working fine.

7) Move all UEs towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2.

8) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that CS calls and

downloads are working fine after HO.

9) Bring back all UEs from HNB2 to HNB1 until 1F and 1C occurs and HO is triggered from HNB2 to HNB1. Note down

CPU and memory utilization.

10) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that CS calls and

downloads are working fine after HO.

11) Repeat step 7 to 10 for three times.

12) Disconnect all CS and HSDPA/64 calls and verify all calls are released properly.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

3) Calculate and update the average CPU and average Memory utilization in the corresponding column.

Page 15: 2.1 Release Master Tracker

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Attach 8 UEs to HNB1.

5) Trigger AMR12.2 call from UE#1->UE#2, CS64 call from UE#3->UE#4, HSDPA/64 call from UE#5, UE#6, UE#7, UE#8.

6) Start 100 MB file download from UE#5, UE#6, UE#7, UE#8. Note down CPU and memory utilization. Verify that CS

calls and downloads are working fine.

7) Move all UEs towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2.

8) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that CS calls and

downloads are working fine after HO.

9) Bring back all UEs from HNB2 to HNB1 until 1F and 1C occurs and HO is triggered from HNB2 to HNB1. Note down

CPU and memory utilization.

10) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that CS calls and

downloads are working fine after HO.

11) Repeat step 7 to 10 for three times.

12) Disconnect all CS and HS calls and verify all calls are released properly.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

3) Calculate and update the average CPU and average Memory utilization in the corresponding column.

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Attach 8 UEs to HNB1.

5) Trigger AMR12.2 call from UE#1->UE#2, PS64/64 call from UE#3, UE#4, HSDPA/64 call from UE#5, UE#6, UE#7, UE#8.

6) Start 10 MB download from UE#3, UE#4, 100 MB file download from UE#5, UE#6, UE#7, UE#8. Note down CPU and

memory utilization. Verify that CS calls and downloads are working fine.

7) Move all UEs towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2.

8) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that CS calls and

downloads are working fine after HO.

9) Bring back all UEs from HNB2 to HNB1 until 1F and 1C occurs and HO is triggered from HNB2 to HNB1. Note down

CPU and memory utilization.

10) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that CS calls and

downloads are working fine after HO.

11) Repeat step 7 to 10 for three times.

12) Disconnect all CS, PS and HS calls and verify all calls are released properly.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

3) Calculate and update the average CPU and average Memory utilization in the corresponding column.

Page 16: 2.1 Release Master Tracker

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Attach 8 UEs to HNB1.

5) Trigger CS64 call from UE#1->UE#2, PS64/64 call from UE#3, UE#4, HSDPA/64 call from UE#5, UE#6, UE#7, UE#8.

6) Start 10 MB download from UE#3, UE#4, 100 MB file download from UE#5, UE#6, UE#7, UE#8. Note down CPU and

memory utilization. Verify that CS calls and downloads are working fine.

7) Move all UEs towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2.

8) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that CS calls and

downloads are working fine after HO.

9) Bring back all UEs from HNB2 to HNB1 until 1F and 1C occurs and HO is triggered from HNB2 to HNB1. Note down

CPU and memory utilization.

10) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that CS calls and

downloads are working fine after HO.

11) Repeat step 7 to 10 for three times.

12) Disconnect all CS, PS and HS calls and verify all calls are released properly.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

3) Calculate and update the average CPU and average Memory utilization in the corresponding column.

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Attach 16 UEs to HNB1.

5) Trigger HSDPA/64 call from all UEs.

6) Start FTP download of 100 MB file from all UEs. Note down CPU and memory utilization.

7) Move all UEs towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2.

8) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that downloads are

working fine after HO.

9) Disconnect all calls.

10) Trigger HSDPA/64 call from all UEs and Start FTP download of 100 MB file from all UEs.

11) Bring back all UEs from HNB2 to HNB1 until 1F and 1C occurs and HO is triggered from HNB2 to HNB1. Note down

CPU and memory utilization.

12) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that downloads are

working fine after HO.

13) Repeat step 7 to 12 for three times.

14) Disconnect all HS calls and verify all calls are released properly.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

3) Calculate and update the average CPU and average Memory utilization in the corresponding column.

Page 17: 2.1 Release Master Tracker

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Attach UE#1, UE#2, UE#3, UE#4, UE#5, UE#6, UE#7, UE#8 to HNB2 and UE#9, UE#10, UE#11, UE#12, UE#13, UE#14,

UE#15, UE#16 to HNB1.

5) Trigger CS (AMR12.2) call from UE#1->UE#2, UE#3->UE#4, UE#5->UE#6, UE#7->UE#8 and HSDPA/64 call from UE#9,

UE#10, UE#11, UE#12, UE#13, UE#14, UE#15 and UE#16.

6) Start 100 MB file download from UE#9, UE#10, UE#11, UE#12, UE#13, UE#14, UE#15 and UE#16. Note down CPU and

memory utilization. Verify that CS calls and downloads are working fine.

7) Move all HSDPA/64 UEs towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2.

8) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that CS calls and

downloads are working fine after HO.

9) Bring back all HSDPA/64 UEs from HNB2 to HNB1 until 1F and 1C occurs and HO is triggered from HNB2 to HNB1.

Note down CPU and memory utilization.

10) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that downloads are

working fine after HO.

11) Repeat step 7 to 10 for three times.

12) Disconnect all CS and HSDPA/64 calls and verify all calls are released properly.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

3) Calculate and update the average CPU and average Memory utilization in the corresponding column.

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Attach 16 UEs to HNB1.

5) Trigger HSDPA/64 call from all UEs.

6) Start FTP download of 50 MB file from all UEs. Note down CPU and memory utilization.

7) Note down CPU and memory utilization. Verify voice quality for the calls.

8) Move all UEs towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2.

9) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that calls are working

fine after HO.

10) Bring back all UEs from HNB2 to HNB1 until 1F and 1C occurs and HO is triggered from HNB2 to HNB1. Note down

CPU and memory utilization.

11) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that calls are

working fine after HO.

12) Disconnect all calls and verify all calls are released properly.

13) Trigger CS (AMR12.2) call from UE#1->UE#2, UE#3->UE#4, UE#5->UE#6, UE#7->UE#8, UE#9->UE#10, UE#11->UE#12,

UE#13->UE#14 and UE#15->UE#16.

14)Move 8 UEs towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2. Move another 8 UEs

towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2.

15) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that calls are

working fine after HO.

16) Bring back 8 UEs from HNB2 to HNB1 until 1F and 1C occurs and HO is triggered from HNB2 to HNB1. Bring back

another 8 UEs from HNB2 to HNB1 until 1F and 1C occurs and HO is triggered from HNB2 to HNB1. Note down CPU and

memory utilization.

17) Repeat Step 5 to 12.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

Page 18: 2.1 Release Master Tracker

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Attach 16 UEs to HNB1.

5) Trigger HSDPA/64 call from all UEs.

6) Start FTP download of 50 MB file from all UEs. Note down CPU and memory utilization.

7) Note down CPU and memory utilization. Verify voice quality for the calls.

8) Move all UEs towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2.

9) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that calls are working

fine after HO.

10) Bring back all UEs from HNB2 to HNB1 until 1F and 1C occurs and HO is triggered from HNB2 to HNB1. Note down

CPU and memory utilization.

11) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that calls are

working fine after HO.

12) Disconnect all calls and verify all calls are released properly.

13) Trigger CS 64 call from UE#1->UE#2, UE#3->UE#4, UE#5->UE#6, UE#7->UE#8, UE#9->UE#10, UE#11->UE#12, UE#13-

>UE#14 and UE#15->UE#16.

14) 7) Move 8 UEs towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2. Move another 8 UEs

towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2.

15) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that calls are

working fine after HO.

16) Bring back 8 UEs from HNB2 to HNB1 until 1F and 1C occurs and HO is triggered from HNB2 to HNB1. Bring back

another 8 UEs from HNB2 to HNB1 until 1F and 1C occurs and HO is triggered from HNB2 to HNB1. Note down CPU and

memory utilization.

17) Repeat Step 5 to 12.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Attach 16 UEs to HNB1.

5) Trigger HSDPA/64 call from all UEs.

6) Start FTP download of 50 MB file from all UEs. Note down CPU and memory utilization.

7) Move all UEs towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2.

8) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that calls are working

fine after HO.

9) Bring back all UEs from HNB2 to HNB1 until 1F and 1C occurs and HO is triggered from HNB2 to HNB1. Note down

CPU and memory utilization.

10) Disconnect all calls and verify all calls are released properly.

11) Trigger PS64/64 call from all UEs.

12) Start FTP download of 10 MB file from all UEs. Note down CPU and memory utilization.

13) Move 8 UEs towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2. Move another 8 UEs

towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2.

14) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that calls are

working fine after HO.

15) Bring back 8 UEs from HNB2 to HNB1 until 1F and 1C occurs and HO is triggered from HNB2 to HNB1. Bring back

another 8 UEs from HNB2 to HNB1 until 1F and 1C occurs and HO is triggered from HNB2 to HNB1. Note down CPU and

memory utilization.

16) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that calls are

working fine after HO.

17) Repeat Step 5 to 10.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

3) Calculate and update the average CPU and average Memory utilization in the corresponding column.

Page 19: 2.1 Release Master Tracker

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS. Disable the Intra Frequency flag in

HNB2 using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Attach UE1 to HNB1.

5) Trigger HSDPA/64 call from UE#1. Start FTP download of 100 MB files.

6) Note down CPU and memory utilization.

7) Move UE towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2.

8) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that calls are working

fine after HO.

9) Bring back UE from HNB2 to HNB1.

10) Verify that measurement is not triggered and HO is not success from HNB2 to HNB1. RLF may be observed at HNB1

and CELL UPADTE may be observed at HNB1 and HNB2.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

3) Update the CPU and Memory utilization in the corresponding column.

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Attach 16 UEs to HNB2 and UE#17 to HNB1.

5) Trigger HSDPA/64 call from all UEs.

6) Start FTP download of 100 MB file from all UEs. Note down CPU and memory utilization.

7) Note down CPU and memory utilization. Verify downloads are proper.

8) Move UE#17 towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2.

9) Verify uu interface, HNB console and wireshark log for measurement and HO. HO should not be success due to MAX

DCH and check the cause value in the message Relocation Failure. RLF may be observed at HNB1 and CELL UPADTE may

be observed at HNB1 or HNB2 for 17th UE.

10) Disconnect all HS calls and verify all calls are released properly.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

3) Update the CPU and Memory utilization in the corresponding column.

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Attach 16 UEs to HNB1 and UE#17 to HNB2.

5) Trigger HSDPA/64 call from all UEs.

6) Start FTP download of 100 MB file from all UEs. Note down CPU and memory utilization.

7) Note down CPU and memory utilization. Verify downloads are proper.

8) Move all UEs form HNB#1 to HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2.

9) Verify uu interface, HNB console and wireshark log for measurement and HO. HO should be success for 15 UE and it

should fail for 1 UE due to MAX DCH and check the cause value in the log. RLF may be observed at HNB1 and CELL

UPADTE may be observed at HNB1 or HNB2

10) Disconnect all HS calls and verify all calls are released properly.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

3) Update the CPU and Memory utilization in the corresponding column.

Page 20: 2.1 Release Master Tracker

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Attach all 16 UEs to HNB1.

5) Trigger HSDPA/64 call from all UEs.

6) Start FTP download of 100 MB file from all UEs. Note down CPU and memory utilization.

7) Trigger RANAP: Location Reporting Control message from CN for all UEs at HNB1.

8) Verify HNB1 triggers RRC: Measurement Control for UE Positioning towards all UEs and receives Measurement

Report message from all UEs with Location information(LI may not be accurate as HO testing will be done inside LAB).

9) Move all UEs towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2.

10) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that downloads are

working fine after HO.

11) Trigger RANAP: Location Reporting Control message from CN for all UEs at HNB2.

12) Verify HNB2 triggers RRC: Measurement Control for UE Positioning towards all UEs and receives Measurement

Report message from all UEs with Location information(LI may not be accurate as HO testing will be done inside LAB).

13) Bring back all UEs from HNB2 to HNB1 until 1F and 1C occurs and HO is triggered from HNB2 to HNB1. Note down

CPU and memory utilization.

14) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that downloads are

working fine after HO.

15) Trigger RANAP: Location Reporting Control message from CN for all UEs at HNB1.

16) Verify HNB1 triggers RRC: Measurement Control for UE Positioning towards all UEs and receives Measurement

Report message from all the UEs with Location information(LI may not be accurate as HO testing will be done inside

LAB).

17) Disconnect all HSDPA/64 calls and verify all calls are released properly.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

3) Update the CPU and Memory utilization in the corresponding column.Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Three HNBs are configured with all the Intra HO related parameters using HMS. Neighbour's configuration in HNBs

should be such that HNB1's neighbour is HNB2, HNB2's neighbour is HNB3 and HNB3's neighbour is HNB1.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1, HNB2 and HNB3 (All HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Attach 16 UEs to HNB1.

5) Trigger HSDPA/64 call from all UEs.

6) Start FTP download of 100 MB file from all UEs. Note down CPU and memory utilization.

7) Move all UEs towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2.

8) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that downloads are

working fine after HO.

9) Move all UEs towards HNB3 until 1F and 1C occurs and HO is triggered from HNB2 to HNB3.

10) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that downloads are

working fine after HO.

11) Move all UEs towards HNB1 until 1F and 1C occurs and HO is triggered from HNB3 to HNB1.

12) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that downloads are

working fine after HO.

13) Disconnect all HSDPA/64 calls and verify all calls are released properly.

Post Condition:

1) HNB1, HNB2 and HNB3 do not crash or hang.

2) Save all the relevant logs in the Log Server.

3) Calculate and update the average CPU and average Memory utilization in the corresponding column.

Page 21: 2.1 Release Master Tracker

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Three HNBs are configured with all the Intra HO related parameters using HMS. Neighbour's configuration in HNBs

should be such that HNB1's neighbour is HNB2 and HNB3, HNB2's neighbour is HNB3 and HNB3's neighbour is HNB1

and HNB2. IMSI configuration of UEs should not be done HNB2's white list and CSG Feature should be enabled on HNB2.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1, HNB2 and HNB3 (All HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Attach 16 UEs to HNB1.

5) Trigger HSDPA/64 call from all UEs.

6) Start FTP download of 100 MB file from all UEs. Note down CPU and memory utilization.

7) Move all UEs towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2. Verify that relocation

should fail for all UEs as IMSI is not present. Now Immediately move all the UE towards HNB3.

8) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that downloads are

working fine after HO.

9) Bring back all UEs towards HNB2 until 1F and 1C occurs and HO is triggered from HNB3 to HNB2. Verify that

relocation should fail for all UEs as IMSI is not present. Now Immediately move all the UE towards HNB1

10) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that downloads are

working fine after HO. Note down CPU and memory utilization.

11) Disconnect all HSDPA/64 calls and verify all calls are released properly.

Post Condition:

1) HNB1, HNB2 and HNB3 do not crash or hang.

2) Save all the relevant logs in the Log Server.

3) Calculate and update the average CPU and average Memory utilization in the corresponding column.

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Attach UE#1 and UE#2 to HNB1.

5) Trigger HSDPA/64 call from all UEs.

6) Start FTP download of 100 MB file from all UEs. Note down CPU and memory utilization.

7) Move all UEs towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2.

8) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that downloads are

working fine after HO.

9) Bring back all UEs from HNB2 to HNB1 until 1F and 1C occurs and HO is triggered from HNB2 to HNB1. Note down

CPU and memory utilization.

10) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that downloads are

working fine after HO.

11) Repeat step 7 to 10 for ten times.

12) Disconnect all HSDPA/64 calls and verify all calls are released properly.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

3) Calculate and update the average CPU and average Memory utilization in the corresponding column.

Page 22: 2.1 Release Master Tracker

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Attach 16 UEs to HNB1.

5) Trigger HSDPA/64 call from all UEs.

6) Start FTP download of 20 MB file from all UEs. Note down CPU and memory utilization.

7) Move all UEs towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2.

8) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that downloads are

working fine after HO.

9) Disconnect all HSDPA/64 calls after completion of download and verify all calls are released properly.

10) Detach all the UEs (make it offline) and bring back to HNB1.

11) Attach all 16 UE to HNB1 (change profile from offline to general), verify all UEs are attached to HNB1.

12) Repeat step 5 to 11 for three times.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

3) Calculate and update the average CPU and average Memory utilization in the corresponding column.

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Attach 16 UEs to HNB1.

5) Trigger HSDPA/64 call from all UEs.

6) Start FTP download of 20 MB file from all UEs. Note down CPU and memory utilization.

7) Move all UEs towards HNB2 until 1F and 1C occurs and HO is triggered from HNB1 to HNB2.

8) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that downloads are

working fine after HO.

9) Bring back all UEs from HNB2 to HNB1 until 1F and 1C occurs and HO is triggered from HNB2 to HNB1. Note down

CPU and memory utilization.

10) Verify uu interface, HNB console and wireshark log for successful measurement and HO. Verify that downloads are

working fine after HO.

11) Disconnect all HS calls and verify all calls are released properly.

12) Repeat step 5 to 11 for three times.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

3) Calculate and update the average CPU and average Memory utilization in the corresponding column.

Page 23: 2.1 Release Master Tracker

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Configure 1 UE for HSDPA/64 call in UE simulator and attach UE instance to HNB1.

5) Trigger HSDPA/64 call from UE#1 and start downloading file of size 10mb.

6) Verify measurement control message and RB reconfig message are sent from HNB1 to the UE#1.

7) Simulate UE#1 sending RB Reconfig failure to the HNB1 with cause configuration unsupported.

8) Verify HNB1 initiate Relocation cancel message towards CN.

9) Verify HNB2 clears the UE context when CN initiates Iu release procedure towards HNB2 after getting Relocation

cancle from HNB1.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Configure 1 UE for HSDPA/64 call in UE simulator and attach UE instance to HNB1.

5) Trigger HSDPA/64 call from UE simulator and download 10mb of data.

6) Trigger measurement report with event 1A from UE. verify that measurement should be ignored and there should not

be any impact on existing call.

7) Trigger measurement report with event 1B from UE. verify that measurement should be ignored and there should not

be any impact on existing call.

8) Trigger measurement report with event 1D from UE. verify that measurement should be ignored and there should

not be any impact on existing call.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Configure 1 UE for HSDPA/64 call in UE simulator and attach UE instance to HNB.

5) Trigger HSDPA/64 call from UE simulator and download 10mb of data.

6) Trigger measurement failure from UE to HNB with cause as "unsupported measurement".

7) Verify the HNB1 for handling of Measurement control failure from the UE.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

Page 24: 2.1 Release Master Tracker

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Configure 1 UE for HSDPA/64 call in UE simulator and attach UE instance to HNB.

5) Trigger HSDPA/64 call from UE simulator and download 10mb of data.

6) Trigger continuous measurement report(approx 100 times during 1st complete measurement procedure) for 1C using

UE simulator.

7) Verify the HNB1 honors one measurement report and ignores all other measurement report.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Configure 1 UE for HSDPA/64 call in UE simulator and attach UE instance to HNB.

5) Trigger HSDPA/64 call from UE simulator and download 10mb of data.

6) Trigger Cell update just after sending the Measurement report for 1F and before 1C.

7) Verify that call gets droped and HNB1 cleans up tha UE context.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

Pre Condition:

1) CNE, HMS Server, SecurityGw is up and running.

2) Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1) Start capturing all the relevant logs.

2) Bring up HNB1 and HNB2 (Both HNBs are connected to same HNBGW). Verify that HNBs are up and operational.

3) Verify CPU and memory utilization through out the testcase. They should not exceed 80%.

4) Configure 1 UE for HSDPA/64 call in UE simulator and attach UE instance to HNB.

5) Trigger HSDPA/64 call from UE simulator and download 10mb of data.

6) Trigger Cell update during relocation procedure(After sending measurement report for 1C).

7) Verify that call gets droped and HNB1 cleans up tha UE context.

Post Condition:

1) HNB1 and HNB2 do not crash or hang.

2) Save all the relevant logs in the Log Server.

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1". Configure all the HO related parameters in HNB1 and HNB2 using HMS.

Test Steps:

1. Bring up HNB1 and HNB2 and verify they are operational.

2. Attach 2 UEs to HNB1.

3. Trigger AMR12.2 call from UE1 to UE2.

4. Trigger HSDPA/64 call from both the UEs and start ftp download of 20MB file.

5. Move the UEs from HNB1 to HNB2.

6. Verify that HNB1 should not trigger HO, and the call will get disconnected eventually due to RL-Failure or Cell-Update.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the test case logs in the log repository/server.

Page 25: 2.1 Release Master Tracker

Te

st

Ca

se

ID

(60

Ch

ar

ma

x L

en

gth

)

Te

st

Ca

se

Ob

jec

tiv

e

OCTASIC_MRAB_TC_01 Verification of 8UE MRAB Call - CS AMR12.2

call + PS 64/64 call (Only Download).

Page 26: 2.1 Release Master Tracker

OCTASIC_MRAB_TC_02 Verification of 8 UE MRAB calls - CS AMR12.2

call + HSDPA/64 call (Only Download)

OCTASIC_MRAB_TC_03 Verification of 8 UE CS AMR12.2 call + 4UE PS

64 call+ 4UE HSDPA/64 call ( Only Download)

Page 27: 2.1 Release Master Tracker

OCTASIC_MRAB_TC_04 Verification of 8UE CS AMR12.2+ 8UE

HSDPA/64 call move out of coverage area.

(HTTP download)

OCTASIC_MRAB_TC_05 Verification of 8UE MRAB Call - CS AMR12.2

call + PS 64/64 call (Download and upload).

Page 28: 2.1 Release Master Tracker

OCTASIC_MRAB_TC_06 Verification of 8 UE MRAB calls - CS AMR12.2

call + HSDPA/64 call (Download and upload)

OCTASIC_MRAB_TC_07 Verify 8 CS AMR12.2 call + 8 MRAB calls (CS

AMR12.2 call + PS 64/64)

Page 29: 2.1 Release Master Tracker

OCTASIC_MRAB_TC_08 Verify 8 CS AMR12.2 call + 8 MRAB calls (CS

AMR12.2 call + HSDPA/64)

OCTASIC_MRAB_TC_09 Verify MRAB call 8 CS video call+ 8 PS64/64

call ( CS Over PS) - Download only

Page 30: 2.1 Release Master Tracker

OCTASIC_MRAB_TC_10 Verify MRAB call 8 CS video call+ 8 HSDPA/64

call (CS over PS) - Only download

OCTASIC_MRAB_TC_11 Verify 8 CS video call and 8 MRAB call - CS

AMR12.2 + PS64/64.

Page 31: 2.1 Release Master Tracker

OCTASIC_MRAB_TC_12 Verify 8 CS video call and 8 MRAB call - CS

AMR12.2 + HSDPA/64

OCTASIC_MRAB_TC_13 Verify 8 PS64/64 call (SRAB) and 8 MRAB call -

AMR12.2 + PS64/64

Page 32: 2.1 Release Master Tracker

OCTASIC_MRAB_TC_14 Verify 8 PS64/64 call (SRAB) and 8 MRAB call -

AMR12.2 + HSDPA/64

OCTASIC_MRAB_TC_15 Verify 8 HSDPA/64 call (SRAB) and 8 MRAB

call - AMR12.2 + ps64/64

Page 33: 2.1 Release Master Tracker

OCTASIC_MRAB_TC_16 Verify 8 HSDPA/64 call (SRAB) and 8 MRAB

call - AMR12.2 + HSDPA/64

OCTASIC_MRAB_TC_17 Verify 8 CS AMR12.2 call (SRAB) and 4 MRAB

call (AMR12.2 + PS64/64) and 4 MRAB calls (

AMR12.2 +HSDPA/64)

Page 34: 2.1 Release Master Tracker

OCTASIC_MRAB_TC_18 Verify 8 CS video call (SRAB) and 4 MRAB call

(AMR12.2 + PS64/64) and 4 MRAB calls (

AMR12.2 +HSDPA/64)

OCTASIC_MRAB_TC_19 Verify 8 PS64/64 (SRAB) +4 MRAB (AMR12.2

+ps64) + 4 MRAB (AMR12.2 + HSDPA/64)

Page 35: 2.1 Release Master Tracker

OCTASIC_MRAB_TC_20 Verify 8 HSDPA/64 (SRAB) +4 MRAB (AMR12.2

+ps64) + 4 MRAB (AMR12.2 + HSDPA/64)

OCTASIC_MRAB_TC_21 Verify 4 AMR12.2 call (SRAB) + 4 video

call(SRAB) +4MRAB(AMR12.2+ps64) + 4

MRAB(AMR12.2 +HSDPA)

Page 36: 2.1 Release Master Tracker

OCTASIC_MRAB_TC_22 Verify 4 CS AMR12.2 call (SRAB) + 4 PS64/64

(SRAB) +4 MRAB(AMR12.2 +ps64) + 4 MRAB

(AMR12.2 + HSDPA/64)

OCTASIC_MRAB_TC_23 Verify 4 CS AMR12.2 call (SRAB) + 4 HSDPA/64

(SRAB) +4 MRAB(AMR12.2 +ps64) + 4 MRAB

(AMR12.2 + HSDPA/64)

Page 37: 2.1 Release Master Tracker

OCTASIC_MRAB_TC_24 Verify 4 CS video call (SRAB) + 4 PS64/64

(SRAB) +4 MRAB(AMR12.2 +ps64) + 4 MRAB

(AMR12.2 +hsdpa)

OCTASIC_MRAB_TC_25 Verify 4 CS video call (SRAB) + 4 HSDPA/64

(SRAB) +4 MRAB(AMR12.2 +ps64) + 4 MRAB

(AMR12.2 +hsdpa)

Page 38: 2.1 Release Master Tracker

OCTASIC_MRAB_TC_26 Verify 4 PS64/64 (SRAB) + 4 HSDPA/64 (SRAB)

+4 MRAB(AMR12.2 +ps64/64) + 4 MRAB

(AMR12.2 +hsdpa)

OCTASIC_MRAB_TC_27 Verify 8 MRAB call ( AMR12.2 + HS). - Make

and break AMR12.2 call when HS is active

Page 39: 2.1 Release Master Tracker

OCTASIC_MRAB_TC_28 Verify 4 AMR12.2 call (SRAB) + 4 HSDPA

call(SRAB) +8 MRAB (AMR12.2+ HSDPA/64)

and 17th trying to Trigger Emergency call.

OCTASIC_MRAB_TC_29 Verify 8 CS AMR12.2 call Intra Frequency HO.

And then trigger 8 MRAB calls at the target

side

OCTASIC_MRAB_TC_30 Verify HNB does not support MRAB Intra HO.

Page 40: 2.1 Release Master Tracker

OCTASIC_MRAB_TC_31 Verify RAB Assignment failure for 2nd RAB(PS

domain), while establishing MRAB calls.(UE

simulator)

OCTASIC_MRAB_TC_32 Verify RAB Assignment failure for 2nd RAB(CS

domain), while establishing MRAB calls.(UE

simulator)

Page 41: 2.1 Release Master Tracker

OCTASIC_MRAB_TC_33 Verify Security Mode Failure for 2nd RAB

during MRAB call establishment

OCTASIC_MRAB_TC_34 Verify Uu Timer expiry during 2nd RAB

establishment.(PS over CS)

Page 42: 2.1 Release Master Tracker

OCTASIC_MRAB_TC_35 Verify HNB handling for Security Mode Failure

for 2nd RAB(CS domain) during MRAB call

establishment

OCTASIC_MRAB_TC_36 Verify Uu Timer expiry during 2nd RAB

establishment.(CS over PS)

Page 43: 2.1 Release Master Tracker

OCTASIC_MRAB_TC_37 Verify 9th UE triggering MRAB call when

already 8 UE MRAB calls are active.

OCTASIC_MRAB_TC_38 Verify PS call release when Signalling

Connection Release is initiated by UE which is

in MRAB call.

Page 44: 2.1 Release Master Tracker

OCTASIC_MRAB_TC_39 Verify Battery removal from UE during MRAB

call is active.

OCTASIC_MRAB_TC_40 Verification of 8 UE CS AMR12.2 call + 4UE PS

64/64 call+ 4UE HSDPA/64 call (Download and

upload)

Page 45: 2.1 Release Master Tracker

OCTASIC_MRAB_TC_41 Verify 1 HSUPA call and 8 UE MRAB (CS

AMR12.2 + PS64/64)

OCTASIC_MRAB_TC_42 Verify 8 PS64/64 call Intra Frequency HO. And

then trigger 8 MRAB calls at the target side

OCTASIC_MRAB_TC_43 Verification of call models without rebooting

HNB

Page 46: 2.1 Release Master Tracker

OCTASIC_MRAB_TC_44 Verification of 8 UE MRAB calls - CS AMR12.2

call + HSDPA/64 call (HTTP Download)

OCTASIC_MRAB_TC_45 Verify MRAB call Voice+ PS384/64 is not

supported.

Page 47: 2.1 Release Master Tracker

OCTASIC_MRAB_TC_46 Verification of 8 UE MRAB calls - CS AMR12.2

call + HSDPA/64 call (Only Download) -

configure 10 code for HS call.

Page 48: 2.1 Release Master Tracker

OCTASIC_MRAB_TC_47 Verification of 8 UE MRAB calls - CS AMR12.2

call + HSDPA/64 call (Only Download) -

Keeping some UEs nearer to HNB and some

far from HNB.

Page 49: 2.1 Release Master Tracker

Te

st

Ca

se

Pro

ce

du

res

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger AMR 12.2 calls from UE#1 to UE#2, UE#3 to UE#4, UE#5 to UE#6 and UE#7 to UE#8. Verify all

the AMR 12.2 calls established successfully.

4. Trigger PS64/64 call from UE#1,UE#2,UE#3,UE#4,UE#5,UE#6,UE#7 and UE#8. Verify all the PS64/64

calls established successfully.

5. Start FTP download of 2Mb file for all UEs. Verify data throughput.

6. Disconnect PS64/64 call after the completion of download from all the UEs.

7. Disconnect AMR12.2 calls. Verify all the calls are released successfully.

8. Repeat the steps 3 to 7 for 3 iterations.

9. Trigger PS 64/64 call from all the UEs.Start FTP download of 2Mb file for all UEs. Verify data

throughput.

10. Trigger AMR12.2 call from all the UEs.

11.Disconnect PS64/64 call after the completion of download of file from all the UEs.

12.Disconnect AMR12.2 calls for all the UEs.Verify all the calls are released successfully.

13. Repeat the steps 9 to 12 for 3 iterations.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 50: 2.1 Release Master Tracker

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger AMR12.2 calls from UE#1 to UE#2, UE#3 to UE#4, UE#5 to UE#6 and UE#7 to UE#8. Verify

AMR 12.2 calls established successfully.

4. Trigger HSDPA/64 call from UE#1,UE#2,UE#3,UE#4,UE#5,UE#6,UE#7 and UE#8. Verify MRAB calls

established successfully.

5. Start FTP download of 20MB file for all UEs. Verify the data throughput.

6. Disconnect HSDPA/64 call after the completion of download.

7.Disconnect all AMR12.2 calls. Verify all the calls are released successfully.

8. Repeat the steps 3 to 7 for 3 iterations.

9. Trigger HSDPA/64 call from all the UEs and then trigger AMR12.2 call from all the UEs as above step

3. Verify MRAB calls established successfully.

10. Start FTP download of 20MB file for all UEs. Verify data throughput.

11. Disconnect HS call after the completion of download for all the UEs.

12. Disconnect all AMR12.2 calls. Verify all the calls are released successfully.

13. Repeat the steps 9 to 12 for 3 iterations.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger HSDPA/64 call from UE#1, UE#2, UE#3 and UE#4 and start FTP download of 20MB file.

4. Trigger PS64/64 call from UE#5, UE#6, UE#7 and UE#8 and start FTP download 2Mb file.

5. Trigger AMR12.2 calls from UE#1 to UE#2, UE#3 to UE#4, UE#5 to UE#6 and UE#7 to UE#8.

6. Disconnect PS64/64 and HS calls after the completion of download from all the UEs.

7. Disconnect all AMR12.2 calls.

8. Repeat step 3 to 7 for 3 times.

9. Trigger AMR12.2 call from all the UEs as mentioned in step 5 and then trigger HSDPA/64 and PS

64/64 call from all the UEs as mentioned in step 3 & 4.

10. Start FTP download of 20MB for UE#1,UE#2,UE#3 and UE#4 and start FTP download of 2Mb file

for UE#5,UE#6,UE#7 and UE#8.

11. Disconnect PS and HS calls after the completion of download from all the UEs.

12. Disconnect AMR12.2 calls. Verify all the calls released successfully.

13. Repeat the steps 9 to 12 for 3 times.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 51: 2.1 Release Master Tracker

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger AMR12.2 calls from UE#1 to UE#2, UE#3 to UE#4, UE#5 to UE#6 and UE#7 to UE#8.

4. Trigger a HSDPA/64 call from UE#1,UE#2,UE#3,UE#4,UE#5,UE#6,UE#7 and UE#8.

5. Start HTTP download of 20MB file for all UEs.

6. Move all MO UEs out of coverage area , observe AMR12.2 call and HS call released.

7. Bring back MO UE into coverage area. Disconnect all the active HS calls.

8. Repeat the steps 3 to 7 for 3 times.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger AMR 12.2 calls from UE#1 to UE#2, UE#3 to UE#4, UE#5 to UE#6 and UE#7 to UE#8. Verify all

the AMR 12.2 calls established successfully.

4. Trigger PS64/64 call from UE#1,UE#2,UE#3,UE#4,UE#5,UE#6,UE#7 and UE#8. Verify all the PS64/64

calls established successfully.

5. Start FTP download of 2Mb and upload of 500kb file for all UEs. Verify data throughput.

6. Disconnect PS64/64 call after the completion of download and upload from all the UEs.

7. Disconnect AMR12.2 calls. Verify all the calls are released successfully.

8. Repeat the steps 3 to 7 for 3 iterations.

9. Trigger PS 64/64 call from all the UEs and trigger AMR12.2 call from all the UEs. Verify all the calls

established successfully.

10. Start FTP download of 2Mb file and upload of 500kb for all UEs. Verify data throughput.

11.Disconnect PS64/64 call after the completion of download and upload of file from all the UEs.

12.Disconnect AMR12.2 calls for all the UEs.

13. Repeat the steps 9 to 12 for 3 iterations.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 52: 2.1 Release Master Tracker

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger AMR12.2 calls from UE#1 to UE#2, UE#3 to UE#4, UE#5 to UE#6 and UE#7 to UE#8. Verify

AMR 12.2 calls established successfully.

4. Trigger HSDPA/64 call from UE#1,UE#2,UE#3,UE#4,UE#5,UE#6,UE#7 and UE#8. Verify MRAB calls

established successfully.

5. Start FTP download of 20MB and upload of 500kb file for all UEs. Verify the data throughput.

6. Disconnect HSDPA/64 call after the completion of download and upload.

7.Disconnect all AMR12.2 calls. Verify all the calls are released successfully.

8. Repeat the steps 3 to 7 for 3 iterations.

9. Trigger HSDPA/64 call from all the UEs and then trigger AMR12.2 call from all the UEs as above step

3 and step 4. Verify MRAB calls established successfully.

10. Start FTP download of 20MB and upload of 500kb file for all UEs. Verify data throughput.

11. Disconnect HS call after the completion of download and upload for all the UEs.

12. Disconnect all AMR12.2 calls. Verify all the calls are released successfully.

13. Repeat the steps 9 to 12 for 3 iterations.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger AMR12.2 calls from UE#1 to UE#2, UE#3 to UE#4, UE#5 to UE#6 and UE#7 to UE#8.

4. Trigger PS64/64 call from UE#9 ..... UE#16 UEs. Start FTP download of 2Mb for these UEs.

5. Trigger CS AMR12.2 call from UE#9 to UE#10.... UE#15-UE#16.

6. Verify MRAB calls established successfully. verify the data throughput.

7. Disconnect PS call after the completion of download from all the UEs.

8. Disconnect AMR12.2 calls from UE#10,UE#12, UE#14 and UE#16.

9. Disconnect all the SRAB CS AMR12.2 call.

10. Repeat the steps 3 to 9 for 3 times.

11. Repeat the testcase 3 times, by triggering MRAB call PS over CS.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 53: 2.1 Release Master Tracker

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger AMR12.2 calls from UE#1 to UE#2, UE#3 to UE#4, UE#5 to UE#6 and UE#7 to UE#8.

4. Trigger a HSDPA/64 call from UE#9 ... UE#16.Start FTP download of 20MB and upload of 500kb for

all UEs.

5. Trigger CS AMR12.2 call from UE#9-UE#10...UE#15-UE#16.

6. Disconnect HS calls after the completion of download and upload from all the UEs

7. Disconnect CS call from UE#10,UE#12,UE#14,UE#16.

8. Disconnect AMR12.2 calls from UE#2, UE#4, UE#6 and UE#8.

9. Repeat the steps 3 to 8 for 3 times.

10. Repeat the testcase for 3 times, by making MRAB call HS over CS

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3.Trigger PS64/64 call from UE#1,UE#2

4. Start FTP download of 2Mb file for all UEs.

5. Trigger CS video calls from UE#1 to UE#2. Verify HNB should not admit video call, as MRAB video is

not supported.

6. Disconnect PS call after the completion of download from all the UEs.

7. Verify there is no impact on PS64/64 call.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 54: 2.1 Release Master Tracker

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger a HSDPA call from UE#1,UE#2,UE#3,UE#4,UE#5,UE#6,UE#7 and UE#8.

4. Start FTP/HTTP download of 20MB file for all UEs.

5. Trigger video calls from UE#1 to UE#2, UE#3 to UE#4, UE#5 to UE#6 and UE#7 to UE#8. Verify HNB

should not admit video call, as MRAB video is not supported.

6. Disconnect PS call after the completion of download from all the UEs

7. Verify there is no impact on HS calls.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger video call from 8 UEs UE#1-UE#2… UE#7-UE#8.

4. Trigger CS AMR12.2 call from UE#9-UE#10….. UE#15-UE#16.

5. Trigger PS64/64 call from UE#9... UE#16 and start FTP download of 2mb files.

6. Disconnect all the ps64 call after completion of download.

7. Disconnect all the AMR12.2 call.

8. Disconnect all the video calls.

9 Repeat the steps from 3 to 8 for 3 times.

10. Repeat the steps testcase by triggering MRAB call - CS over PS for 3 times.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 55: 2.1 Release Master Tracker

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger video call from 8 UEs UE#1-UE#2… UE#7-UE#8.

4. Trigger CS AMR12.2 call from UE#9-UE#10….. UE#15-UE#16.

5. Trigger HSDPA/64 call from UE#9..... UE#16 and start FTP download of 20MB file

6. Disconnect all the video calls.

7. Disconnect all the HS calls after completion of download.

8. Disconnect all the AMR12.2 call.

9 Repeat the steps from 3 to 8 for 3 times.

10. Repeat the testcase by triggering MRAB call - CS over HS for 3 times.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger PS64/64 call from UE#1… UE#8 and start download of 2mb file and upload of 500kb file.

4. Trigger CS AMR12.2 call from UE#9-UE#10.. UE#15-UE16.

5. Trigger PS64/64 call from UE#9.. UE#16. start download of 2mb file and upload of 500kb

6. disconnect all the ps64 calls after completion of download and upload.

7. Disconnect all the AMR12.2 calls.

8. Repeat the steps from 3 to 7 for 3 times.

9. Repeat the steps from 3 to 7 by making MRAB call PS over CS for 3times.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 56: 2.1 Release Master Tracker

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger PS64/64 call from UE#1… UE#8 and start download of 2mb file

4. Trigger CS AMR12.2 call from UE#9-UE#10.. UE#15-UE16.

5. Trigger HSDPA/64 call from UE#9.. UE#16. start download of 20MB file

6. Disconnect all the SRAB PS64/64 call after completing of download.

7. disconnect all the HSDPA/64 calls after completion of download.

8. Disconnect all the AMR12.2 calls.

9. Repeat the steps from 3 to 8 for 3 times.

10. Repeat the testcase by making MRAB call PS over CS for 3times.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger HSDPA/64 call from UE#1… UE#8 and start download of 20MB file

4. Trigger CS AMR12.2 call from UE#9-UE#10.. UE#15-UE16.

5. Trigger PS64 call from UE#9.. UE#16. Start download 2mb file.

6. Disconnect all the HS and ps64/64 calls after completion of download

7. Disconnect all the AMR12.2 calls.

8. Repeat the steps from 3 to 7 for 3 times.

9. Repeat the testcase by making MRAB call PS over CS for 3times.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 57: 2.1 Release Master Tracker

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger HSDPA/64 call from UE#1… UE#8 and start download of 20MB file and upload of 500kb file.

4. Trigger CS AMR12.2 call from UE#9-UE#10.. UE#15-UE16.

5. Trigger HSDPA/64 call from UE#9.. UE#16. Start download of 20MB file and upload of 500kb file.

6. Disconnect all the SRAB HSDPA/64 call after completing of download and upload.

7. disconnect all the HSDPA/64 calls after completion of download and upload.

8. Disconnect all the AMR12.2 calls.

9. Repeat the steps from 3 to 8 for 3 times.

10. Repeat the testcase by making MRAB call PS over CS for 3times.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger 16 CS AMR12.2 calls from UE#1- UE#2…. UE#15-UE#16.

4. Trigger 4 PS64/64 call from UE#9….. UE#12. start download 2Mb

5. Trigger 4 HSDPA/64 call from UE#13.... UE#16. Start download a 20MB

6. Disconnect the PS 64/64 call from UE#9... UE#12 after completion of download

7. Disconnect the AMR12.2 call from UE#10 and UE#12.

8. Disconnect HS call after completion of download.

9. Disconnect all the SRAB AMR12.2 calls.

10. Repeat the steps from 3 to 9 for 3 times

11. Repeat the testcase for 3 times by making CS over PS MRAB call

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 58: 2.1 Release Master Tracker

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger 8 CS Video calls from UE#1- UE#2…. UE#7-UE#8.

4. Trigger 4 PS64/64 call from UE#9….. UE#12. start download of 2Mb.

5. Trigger 4 HSDPA/64 call from UE#13.... UE#16. Start download of 20MB

6. Trigger AMR12.2 call from UE#9-UE#10.... UE#15-UE#16.

7. Disconnect the PS 64 call from UE#9... UE#12 after completion of download

8.Disconnect HS call after completion of download

9. Disconnect all the 8 AMR12.2 calls

10. Disconnect all the Video calls.

11. Repeat the steps from 3 to 10 for 3 times

12. Repeat the testcase for 3 timers by triggering PS over CS MRAB call.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger 12 PS64/64 call from UE#1….. UE#12. Start download of 2mb file.

4. Trigger AMR12.2 call from UE$9-UE#10, UE#11-UE#12.

5. Trigger 4 HSDPA/64 call from UE#13.... UE#16. Start download 20MB.

6. Trigger AMR12.2 call from UE#13-UE#14 and UE#15-UE#16.

7. Disconnect 4 PS 64 call from UE#9... UE#12 after completion of download.

8.Disconnect HS call after completion of download.

9. Disconnect all the 8 AMR12.2 calls

10. Disconnect all the SRAB PS64 calls.

11. Repeat the steps from 3 to 10 for 3 times

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 59: 2.1 Release Master Tracker

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger 8 HSDPA/64 call from UE#1….. UE#8. start download of 20MB

4 Trigger 8 AMR12.2 call from UE$9-UE#10, UE#15-UE#16.

5. Trigger 4 PS64/64 call from UE#9... UE#12. Start download of 2mb file.

6. Trigger 4 HSDPA/64 call from UE#13.... UE#16. Start download a 20MB .

7. Disconnect 4 PS 64/64 call from UE#9... UE#12 after completion of download.

8.Disconnect HS call from UE#13.... UE#16 after completion of download .

9. Disconnect all the 8 AMR12.2 calls.

10. Disconnect all the SRAB HSDPA/64.

11. Repeat the steps from 3 to 10 for 3 times

12. Repeat the testcase for 3times by making PS over CS MRAB call.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger 4 SRAB AMR12.2 call.

4. Trigger 4 SRAB Video call.

5. Trigger 4 MRAB call ( PS64 call over CS AMR12.2 call) with another 4 UEs. For PS call start download

of 2mb.

6. Trigger MRAB call (HSDPA/64 over CS AMR12.2 call ) with another set of UEs. For HS call , start

download of 20MB.

7. Disconnect SRAB AMR12.2 calls.

8. Disconnect SRAB video calls.

9 Disconnect the PS64 MRAB calls after completion of download . and then disconnect AMR12.2 calls.

10. Disconnect HS MRAB calls after completion of download. and then disconnect AMR12.2 calls.

11. Repeat the steps 3 to 10 for 3 times.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 60: 2.1 Release Master Tracker

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger 4 CS AMR12.2 calls (SRAB).

4. Trigger 4 PS64 calls. Start download of 2mb file.

5. Trigger 4 MRAB call (PS over CS) with combination of CS AMR12.2 call and PS64 call using another 4

UEs. Start download of 2mb.

6. Trigger 4 MRAB call (PS over CS) with combination of CS AMR12.2 call and HSdpa/64 call with

another set of 4 UEs. Start download 20MB.

7. Disconnect SRAB 4 PS64 calls after completion of download.

8. Disconnect SRAB 4 CS AMR12.2 calls.

9. Disconnect 4 PS64 (MRAB) call after completion download then disconnect AMR12.2 calls.

10. Disconnect 4 HSDPA calls(MRAB) after completion download then disconnect AMR12.2 calls.

Verify all the calls released successfully.

11. Repeat the steps 3 to 10 for 3 times.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger 4 CS AMR12.2 calls (SRAB).

4. Trigger 4 HSDPA/64 calls. Start download 20MB file.

5. Trigger 4 MRAB call (PS over CS) with combination of CS AMR12.2 call and PS64/64 call using

another 4 UEs. Start download of 2mb file.

6. Trigger 4 MRAB call (PS over CS) with combination of CS AMR12.2 call and HSdpa/64 call with

another set of 4 UEs. Start download of 20MB.

7. Disconnect SRAB 4 HS calls after completion of download.

8. Disconnect SRAB 4 CS AMR12.2 calls.

9. Disconnect 4 PS64 (MRAB) call after completion of download then disconnect AMR12.2 calls.

10. Disconnect 4 HSDPA calls(MRAB) after completion of download then disconnect AMR12.2 calls.

11. Repeat the steps 3 to 10 for 3 times.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 61: 2.1 Release Master Tracker

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger 4 cs Video calls (SRAB).

4. Trigger 4 PS64/64 calls. Start download of 2mb file.

5. Trigger 4 MRAB call (PS over CS) with combination of CS AMR12.2 call and PS64 call using another 4

UEs. Start download of 2mb file.

6. Trigger 4 MRAB call (PS over CS) with combination of CS AMR12.2 call and HSdpa/64 call with

another set of 4 UEs. Start download 20MB.

7. Disconnect SRAB 4 PS64 calls after completion of download.

8. Disconnect SRAB 4 cs video calls.

9. Disconnect 4 PS64 (MRAB) call after completion of download then disconnect AMR12.2 calls.

10. Disconnect 4 HSDPA calls(MRAB) after completion of download then disconnect AMR12.2 calls.

11. Repeat the steps 3 to 10 for 3 times.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger 4 cs video calls UE#1... UE#4(SRAB).

4. Trigger 4 HSDPA/64 calls UE#5.. UE#8. Start download 20MB.

5. Trigger 4 MRAB call (PS over CS) with combination of CS AMR12.2 call and PS64 call using UE#9..

UE#12. Start download of 2mb file.

6. Trigger 4 MRAB call (PS over CS) with combination of CS AMR12.2 call and HSdpa/64 call with

another set of 4 UEs, UE#13... UE#16. Start download of 20MB.

7. Disconnect SRAB 4 HS calls after completion of download.

8. Disconnect SRAB 4 cs video calls.

9. Disconnect 4 PS64 (MRAB) call after completion of download then disconnect AMR12.2 calls.

10. Disconnect 4 HSDPA calls(MRAB) after completion of download then disconnect AMR12.2 calls.

11. Repeat the steps 3 to 10 for 3 times.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 62: 2.1 Release Master Tracker

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger 4 PS64/64 (SRAB) from UE#1..UE#4.Start download of 2mb file.

4. Trigger 4 HSDPA/64 calls using UE#5... UE#8. Start download 20MB .

5. Trigger 4 MRAB call (PS over CS) with combination of CS AMR12.2 call and PS64/64 call using

UE#9...UE#12. Start download of 2mb file.

6. Trigger 4 MRAB call (PS over CS) with combination of CS AMR12.2 call and HSdpa/64 call with

UE#13.... UE#16. Start download of 20MB.

7. Disconnect SRAB 4 HS calls after completion of download.

8. Disconnect SRAB 4 PS64 calls.

9. Disconnect 4 PS64/64 (MRAB) call after completion of download then disconnect AMR12.2 calls.

10. Disconnect 4 HSDPA calls(MRAB) after completion of download then disconnect AMR12.2 calls.

11. Repeat the steps 3 to 10 for 3 times.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger CS AMR12.2 call using 8 UEs.

4. Trigger 8 HSDPA call over the CS AMR12.2 call using the same UEs. Start download of 20MB

5. disconnect the AMR12.2 call from all UEs.

6. Again trigger CS AMR12.2 call over hsdpa call for all the 8 UEs.

7. Disconnect hsdpa call after completion of download.

8 Disconnect AMR12.2 calls.

9. Repeat the steps 3 to 8 for 3 times.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 63: 2.1 Release Master Tracker

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set PSCALLPREEMPTION for Preemption allowed flag.

3. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB. Attach 17 UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger CS AMR12.2 call from UE#1-UE#2,UE#3-UE#4.

4. Trigger HSDPA/64 call from UE#5.... UE#8. Start download of 20MB file for all the UEs.

5. Trigger CS AMR12.2 call from UE#9- UE#10...UE#15-UE#16.

6. Trigger HSDPA/64 call from UE#9...... UE#16. Start download of 20MB file. Verify MRAB call

established successfully.

7. Trigger emergency call from UE#17.

8. Verify the RAB preemption for HS calls.

Post Condition

1. Verify HNB does not crash/hang.

2. Verify MRAB calls are not affected (TBD)

3. Store the testcase logs in the log repository/server.Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

3. Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1. Bring the HNB1 and HNB2 up and verify they are operational. Attach UEs to the HNB1.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger 8 CS AMR12.2 call.

4. Move all the 8 UEs from HNB1 towards HNB2. verify 1F, 1C events are triggered. And HO is

successful for all the UEs.

5. At the HNB2, trigger HSDPA/64 call over CS AMR12.2 call for all the 8 UEs. Start download of 20MB

file.

6. Disconnect all the HS calls after completion of download.

7. Bring back all the 8 UEs towards HNB1. Verify 1F, 1C events are triggered and HO is successful.

8. Disconnect all the AMR12.2 calls.

9. Repeat the steps from 3 to 8 for 3 times

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

TBD - No clarity Handling of this scenario.

Page 64: 2.1 Release Master Tracker

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Attach 2 UEs to the HNB.

4. Trigger CS AMR12.2 call using 2 UEs.

5. Trigger HSDPA/64 call from UE#1.

6. Trigger RB Setup Fail message from UE, while HS call establishment.

7.Verify HNB sends RAB Assignment Failure(Cause: Failure in Radio Interface procedure) to CN.

8. HNB sends Signalling Conn Release to UE for PS domain.

Post condition:

1. HNB does not crash.

2. Verify CS AMR12.2 call is not affected by the RAB assignment fail for PS domain.

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Attach 2 UEs to the HNB.

4. Trigger HS call using 2 UEs. Start download for the 2 UEs. (20MB file)

5. Trigger CS AMR12.2 call from UE#1 to UE#2.

6. Trigger RB Setup Fail message from UE#1 during AMR12.2 call establishment.

7.Verify HNB sends RAB Assignment Failure(Cause: Failure in Radio Interface procedure) to CN.

8. HNB sends Signalling Conn Release to UE for CS domain.

Post condition:

1. HNB does not crash.

2. Verify HS call is not affected by the RAB assignment fail for CS domain.

Page 65: 2.1 Release Master Tracker

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Attach 2 UEs to the HNB.

4. Trigger CS AMR12.2 call using 2 UEs.

5. Trigger HSDPA/64 call from UE#1.

6. Trigger Security Mode failure from UE#1, while HS call establishment.

7.Verify HNB sends Security mode Reject(Cause : Failure in the Radio Interface Procedure) to CN.

8.HNB sends Signalling Connection Release to UE#1 (PS domain).

Post condition:

1.Verify HNB does not crash.

2. Verify CS AMR12.2 call is not affected.

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Attach 2 UEs to the HNB.

4. Trigger CS AMR12.2 call from UE#1 -UE#2.

5. Trigger HS call from UE#1.

6. During HS call establishement,Using UE simulator, Don’t send any response from UE for RB setup

message.

7. Verify at HNB, Uu timer expiry.(TBD - need to check timer value from Dev team).

8. After timer expiry , verify HNB sends RAB Assignment Failure(Cause: Failure in Radio interface

Procedure) to CN and Signalling Connection Release to UE.

Post condition:

1. Verify HNB does not crash.

2. Verify AMR12.2 call is not affected.

Page 66: 2.1 Release Master Tracker

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Attach 2 UEs to the HNB.

4. Trigger HSDPA/64 call from UE#1. start downloading.

5. Trigger CS AMR12.2 call using 2 UEs.

6. Trigger Security Mode failure from UE#1, while CS call establishment.

7.Verify HNB sends Security mode Reject (Cause : Failure in the Radio Interface Procedure) to CN.

8.Verify Iu Release procedure is triggered from CN.

9. HNB sends Signalling Connection Release to UE#1 CS domain.

Post condition:

1.Verify HNB does not crash.

2. Verify HS call is not affected.

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Attach 2 UEs to the HNB.

4. Trigger HSDPA call from UE#1.

5. Trigger CS AMR12.2 call from UE#1 to UE#2.

6. During CS call establishement,Using UE simulator, Don’t send any response from UE#1 for RB setup

message.

7. Verify at HNB, Uu timer expiry.(TBD - need to check timer value form Dev team).

8. After timer expiry , verify HNB sends RAB Assignment Failure to CN and Signalling Connection

Release to UE.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 67: 2.1 Release Master Tracker

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger HSDPA/64 call from 8 UEs and start download of 20MB file.

4. Trigger CS AMR12.2 call using 8 UEs on top of HSDPA calls.

5. Attach UE#9 and UE#10 and trigger CS AMR12.2 call.

6. after successful establishment of AMR12.2 call, start HSDPA call from UE#9.

7. Verify Signalling Connection Release is sent from HNB to UE#9 for PS domain.

Postcondition:

1. Verify HNB does not crash.

2. Verify All the 8 MRAB calls are not affected, when 2nd RAB for 9th UE

fails to establish.Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Attach 8 UEs to HNB.

4. Trigger CS AMR12.2 call from 8 UEs.

5. Trigger HSDPA/64 call from all the 8 UEs. Start download of 20MB file .

6. Using UE simulator, simulate such that, there is no data traffic for some 4 UEs.

7. Verify HNB habdling for Signalling Connection Release initiated from UE for PS domain.

8.Verify PDP deactivation and Iu release procedure for these UEs.

Postcondition:

1. Verify HNB does not crash.

2. Verify Other 4 UE MRAB calls do not affected.

3. Verify CS AMR12.2 calls for the UEs, which received Signalling Connection Release of PS domain are

not affected.

Page 68: 2.1 Release Master Tracker

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Attach 2 UEs to the HNB.

4. Trigger CS AMR12.2 call from UE#1- UE#2.

5. Trigger HSDPA/64 call from UE#1, UE#2. start download 20MB file.

6. Remove battery from UE#1.

7. Verify call release and resources are cleaned successfully.

Postcondition:

1. Verify HNB does not crash.

2. Verify HSDPA call in UE#2 is not affected.

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger HSDPA/64 call from UE#1, UE#2, UE#3 and UE#4 and start FTP download of 20MB and

upload of 500kb file.

4. Trigger PS64/64 call from UE#5, UE#6, UE#7 and UE#8 and start FTP download 2Mb and upload of

500kb file.

5. Trigger AMR12.2 calls from UE#1 to UE#2, UE#3 to UE#4, UE#5 to UE#6 and UE#7 to UE#8.

6. Disconnect PS64/64 and HS calls after the completion of download and upload from all the UEs.

7. Disconnect all AMR12.2 calls.

8. Repeat step 3 to 7 for 3 times.

9. Trigger AMR12.2 call from all the UEs as mentioned in step 5.Trigger HSDPA and PS 64/64 call from

all the UEs as mentioned in step 3&4 .

10. Start FTP download of 20MB and upload of 500kb for UE#1,UE#2,UE#3 and UE#4 and start FTP

download of 2Mb and upload of 500kb file for UE#5,UE#6,UE#7 and UE#8.

11. Disconnect PS and HS calls after the completion of download and upload from all the UEs.

12. Disconnect AMR12.2 calls. Verify all the calls released successfully.

13. Repeat the steps 9 to 12 for 3 times.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 69: 2.1 Release Master Tracker

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger HSUPA call from UE#1. and start upload of 10Mb file.

4. Trigger CS AMR12.2 call from UE#2- UE#3....UE#9

5. Trigger PS64/64 call from UE#2... UE#9 and start FTP download of 2mb files.

6. Disconnect all the PS64/64 call after completion of download.

7. Disconnect all the AMR12.2 call.

8. Disconnect HSUPA calls.

9 Repeat the steps from 3 to 7 for 3 times.

10. Repeat the steps testcase by triggering MRAB call - CS over PS for 3 times.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

3. Two HNBs are configured with all the Intra HO related parameters using HMS.

Test Steps:

1. Bring the HNB1 and HNB2 up and verify they are operational. Attach UEs to the HNB1.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger 8 PS64/64 call. Start download of 2Mb file for all the UEs

4. Move all the 8 UEs from HNB1 towards HNB2. verify 1F, 1C events are triggered and HO is successful

for all the UEs.

5. At the HNB2, trigger CS AMR12.2 call over PS64/64 call for all the 8 UEs.

6. Disconnect all the AMR12.2 calls.

7. Bring back all the 8 UEs towards HNB1. Verify 1F, 1C events are triggered and HO is successful.

8. Disconnect all the PS64/64 calls

9. Repeat the steps from 3 to 8 for 3 times.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Execute these call models one after another without rebooting HNB and check all pre condition and

post condition steps in the following test cases.

OCT_MRAB_TC_01

OCT_MRAB_TC_02

OCT_MRAB_TC_03

OCT_MRAB_TC_07

Page 70: 2.1 Release Master Tracker

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger AMR12.2 calls from UE#1 to UE#2, UE#3 to UE#4, UE#5 to UE#6 and UE#7 to UE#8. Verify

AMR 12.2 calls established successfully.

4. Trigger HSDPA/64 call from UE#1,UE#2,UE#3,UE#4,UE#5,UE#6,UE#7 and UE#8. Verify MRAB calls

established successfully.

5. Start HTTP download of 20MB file for all UEs. Verify the data throughput.

6. Disconnect HSDPA/64 call after the completion of download.

7.Disconnect all AMR12.2 calls. Verify all the calls are released successfully.

8. Repeat the steps 3 to 7 for 3 iterations.

9. Trigger HSDPA/64 call from all the UEs and then trigger AMR12.2 call from all the UEs as above step

3. Verify MRAB calls established successfully.

10. Start FTP download of 20MB file for all UEs. Verify data throughput.

11. Disconnect HS call after the completion of download for all the UEs.

12. Disconnect all AMR12.2 calls. Verify all the calls are released successfully.

13. Repeat the steps 9 to 12 for 3 iterations.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

Test Steps:

1. Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger AMR12.2 calls from UE#1 to UE#2, Verify AMR 12.2 calls established successfully.

4. Trigger 384/64 call from UE#1 .

5. Verify HNB does not support MRAB call - PS384/64 over AMR12.2 call. (TBD).

6. Verify AMR12.2 call is working fine.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 71: 2.1 Release Master Tracker

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

2. Set the flag "MRABEnable = 1".

3. Configure 10 Code for HSDPA Call Model .

Test Steps:

1. Bring the HNB up and verify it is operational.

Use JDSU Tool to Configure all Ue category -9 , attach all UEs to HNB

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger AMR12.2 calls from UE#1 to UE#2, UE#3 to UE#4, UE#5 to UE#6 and UE#7 to UE#8. Verify

AMR 12.2 calls established successfully.

4. Trigger HSDPA/64 call from UE#1,UE#2,UE#3,UE#4,UE#5,UE#6,UE#7 and UE#8. Verify MRAB calls

established successfully.

5. Start FTP download of 20MB file for all UEs. Verify the data throughput(9.6Mbps as mentioned in

the PRD - TBD).

6. Disconnect HSDPA/64 call after the completion of download.

7.Disconnect all AMR12.2 calls. Verify all the calls are released successfully.

8. Repeat the steps 3 to 7 for 3 iterations.

9. Trigger HSDPA/64 call from all the UEs and then trigger AMR12.2 call from all the UEs as above step

3. Verify MRAB calls established successfully.

10. Start FTP download of 20MB file for all UEs. Verify data throughput.

11. Disconnect HS call after the completion of download for all the UEs.

12. Disconnect all AMR12.2 calls. Verify all the calls are released successfully.

13. Repeat the steps 9 to 12 for 3 iterations.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 72: 2.1 Release Master Tracker

Pre Condition

1. CN,Security Gateway and HMS are up and operational.

Test Steps:

1. Bring the HNB up and verify it is operational

Use JDSU Tool to Configure all Ue category -10 , attach all UE to HNB

( configure 4 UE s In Near Region of HNB and remaining 4 to be on Boundary region)

2. Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3. Trigger AMR12.2 calls from UE#1 to UE#2, UE#3 to UE#4, UE#5 to UE#6 and UE#7 to UE#8. Verify

AMR 12.2 calls established successfully.

4. Trigger HSDPA/64 call from UE#1,UE#2,UE#3,UE#4,UE#5,UE#6,UE#7 and UE#8. Verify MRAB calls

established successfully.

5. Start FTP download of 20MB file for all UEs. Verify the data throughput.

6. Disconnect HSDPA/64 call after the completion of download.

7.Disconnect all AMR12.2 calls. Verify all the calls are released successfully.

8. Repeat the steps 3 to 7 for 3 iterations.

9. Trigger HSDPA/64 call from all the UEs and then trigger AMR12.2 call from all the UEs as above step

3. Verify MRAB calls established successfully.

10. Start HTTP download of 20MB file for all UEs . Open streaming application as well for all UEs.

Verify data throughput.

11. Disconnect HS call after the completion of download for all the UEs.

12. Disconnect all AMR12.2 calls. Verify all the calls are released successfully.

13. Repeat the steps 9 to 12 for 3 iterations.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 73: 2.1 Release Master Tracker

Tes

t C

as

e I

D

Tes

t C

as

e O

bje

cti

ve

OCTASIC_16HSDPA_01 Verification of 16 HSDPA/64 calls

OCTASIC_16HSDPA_02 Verification of 8 UE AMR12.2 calls

and 8 HSDPA/64 calls

Page 74: 2.1 Release Master Tracker

OCTASIC_16HSDPA_03 Verification of 8 UE CS Video calls

and 8 HSDPA/64 calls

OCTASIC_16HSDPA_04 Verification of 8 PS64/64 calls and 8

HSDPA/64 calls.

Page 75: 2.1 Release Master Tracker

OCTASIC_16HSDPA_05 Verification of 8 UE AMR12.2 calls, 4

PS64/64 calls and 4 HSDPA/64 calls.

OCTASIC_16HSDPA_06 Verification of 8 UE CS Video calls, 4

PS64/64 calls and 4 HSDPA/64 calls.

Page 76: 2.1 Release Master Tracker

OCTASIC_16HSDPA_07 Verification of 4 UE AMR12.2 calls,4

UE CS Video calls , 4 PS64/64 calls

and 4 HSDPA/64 calls

OCTASIC_16HSDPA_08 Verification of 4 UE AMR12.2 calls, 4

UE CS Video calls and 8 HSDPA/64

calls

Page 77: 2.1 Release Master Tracker

OCTASIC_16HSDPA_09 Verification of 8 UE AMR12.2 calls, 4

PS64/64 calls and 4 HSDPA/64 calls

(connect and disconnect PS/HS call

when CS call active).

OCTASIC_16HSDPA_10 Verification of 4 UE AMR12.2 calls,4

UE CS Video calls ,4 PS64/64 calls

and 4 HSDPA/64 calls (connect and

disconnect CS call when PS/HS call

active).

Page 78: 2.1 Release Master Tracker

OCTASIC_16HSDPA_11 Verification of Location area update

and Routing Area Update messages

during 4 UE AMR12.2 calls,4 UE CS

Video calls, 4 PS64/64 calls and 4

HSDPA/64 calls.

OCTASIC_16HSDPA_12 Verification of 16 HSDPA/64 call with

different UE categories(5,

6,7,8,9,10) using UE simulator -

(Note - Test One category of UE for

one iteration)

Page 79: 2.1 Release Master Tracker

OCTASIC_16HSDPA_13 Verify HSDPA/64 call when UEs are

away from HNB but within coverage

area - using UE simulator

OCTASIC_16HSDPA_14 Verify 16 HSDPA/64 calls with HTTP

download

Page 80: 2.1 Release Master Tracker

OCTASIC_16HSDPA_15 Verify 1 UE HSUPA call with upload

and 15 HSDPA/64 call with download

OCTASIC_16HSDPA_16 Verify 8 AMR12.2 calls, 7 HSDPA/64

calls and 1 HSUPA call

Page 81: 2.1 Release Master Tracker

OCTASIC_16HSDPA_17 Verify 17th UE triggering HSDPA/64

call when 16 HSDPA/64 calls are

active.

OCTASIC_16HSDPA_18 Verify 16 HSDPA/64 calls with

streaming application ( UE

Simulator)

Page 82: 2.1 Release Master Tracker

OCTASIC_16HSDPA_19 Verify 8 UEs HSDPA/64 calls making

download(HTTP) and other 8 UEs

HSDPA/64 calls making upload and

download(FTP) at a time.

OCTASIC_16HSDPA_20 Verify 1UE HSDPA/64 call moved out

of coverage area and bring back to

coverage area

Page 83: 2.1 Release Master Tracker

OCTASIC_16HSDPA_21 Verify Below call models without

rebooting the HNB in sequence:

1. 16 AMR12.2 Calls.

2. 16 PS64/64 calls.

3. 16 CS Video calls.

4. 16 HSDPA/64 calls.

OCTASIC_16HSDPA_22 Verify 16 HSDPA/64 call - download

using iperf over TCP

Page 84: 2.1 Release Master Tracker

Tes

t C

as

e P

roce

du

res

Pre Condition

1) CN,Security Gateway and HMS are up and operational.

Test Steps:

1) Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2) Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3) Trigger HSDPA/64 calls from UE#1, UE#2, UE#3, UE#4, UE#5, UE#6, UE#7, UE#8, UE#9,

UE#10, UE#11, UE#12, UE#13, UE#14 ,UE#15 and UE#16.

4)Make FTP download of 20MB and upload of 2MB file for all the UEs. Verify data throughput

and record it.(0.96Mbps per code in DL and 64kbps in UL - Theoritical values as per PRD)

5) Disconnect the HSDPA/64 calls from all the UEs after download and upload complete.

6) Repeat steps 3 to 5, for 2 hour.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1) CN,Security Gateway and HMS are up and operational.

Test Steps:

1) Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2) Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3) Trigger HSDPA/64 calls from UE#1, UE#2 , UE#3 and UE#4, UE#5, UE#6, UE#7 and UE#8.

4)Make FTP download 20MB and upload of 2MB file for UE#1 to UE#8. Verify data throughput

and record it. (0.96Mbps per code in DL and 64kbps in UL - Theoritical values as per PRD)

5)Trigger AMR12.2 calls from UE#9 to UE#10, from UE#11 to UE#12, from UE#13 to UE#14 and

UE#15 to UE#16.

6) Disconnect the HSDPA/64 calls from UE#1 to UE#8 after download and upload completes.

7) Disconnect the AMR12.2 calls.

8) Repeat steps 3 to 7, for 3 iterations.

9)Verify triggering 8 UE AMR12.2 calls and then 8 HSDPA/64 calls for next 3 iterations.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 85: 2.1 Release Master Tracker

Pre Condition

1) CN,Security Gateway and HMS are up and operational.

Test Steps:

1) Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2) Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3) Trigger HSDPA/64 calls from UE#1, UE#2, UE#3, UE#4, UE#5, UE#6, UE#7 and UE#8.

4)Make FTP download 20MB and upload of 2MB file from UE#1 to UE#8.Verify data throughput

and record it. (0.96Mbps per code in DL and 64kbps in UL - Theoritical values as per PRD)

5)Trigger CS Video calls from UE#9 to UE#10, UE#11 to UE#12, UE#13 to UE#14 and UE#15 to

UE#16.

6) Disconnect the HSDPA/64 calls from UE#1 to UE#8 after download and upload complete.

7)Disconnect the CS Video calls.

8) Repeat steps 3 to 7, for 3 iterations.

9)Verify triggering 8 UE CS video calls and then 8 HSDPA/64 calls for 3 iterations.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1) CN,Security Gateway and HMS are up and operational.

Test Steps:

1) Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2) Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3) Trigger PS64/64 calls from UE#1, UE#2 , UE#3 , UE#4, UE#5, UE#6, UE#7 and UE#8.

4) Make FTP download 5mb and upload 2MB file for UE#1 to UE#8.

5)Trigger HSDPA/64 calls from UE#9, UE#10, UE#11, UE#12, UE#13, UE#14, UE#15 and UE#16.

6)Make FTP download 20MB and upload 2MB file for UE#9 to UE#16.

7) Disconnect the PS64/64 and HSDPA/64 calls from all the UEs after download and upload

complete.

8) Repeat steps 3 to 7 for 3 iterations.

9) Verify first 8 HSDPA/64 calls then 8 PS64/64/64 calls for next 3 iterations.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 86: 2.1 Release Master Tracker

Pre Condition

1) CN,Security Gateway and HMS are up and operational.

Test Steps:

1) Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2) Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3) Trigger PS64/64 calls from UE#1, UE#2, UE#3 and UE#4.

4)Make FTP download 5mb and upload 2MB file from UE#1 to UE#4.

5) Trigger HSDPA/64 calls from UE#5, UE#6, UE#7, and UE#8.

6)Make FTP download 20MB and upload 2MB file from UE#5 to UE#8.

7) Trigger AMR12.2 calls from UE#9 to UE#10, UE#11 to UE#12, UE#13 to UE#14 and UE#15 to

UE#16.

8) Disconnect the PS64/64 and HSDPA/64 calls from UE#1 to UE#8 after download and upload

completes.

9) Disconnect the AMR12.2 calls.

10) Repeat steps 3 to 9, for 3 iteration.

11) Verify 8 UE AMR12.2 calls first, then 4 PS64/64 and 4 HSDPA/64 calls with remaining UEs,

for 3 iterations.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1) CN,Security Gateway and HMS are up and operational.

Test Steps:

1) Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2) Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3) Trigger PS64/64 calls from UE#1, UE#2, UE#3 and UE#4.

4)Make a ftp download 5mb and upload 2MB file from UE#1 to UE#4.

5) Trigger HSDPA/64 calls from UE#5, UE#6, UE#7, and UE#8.

6)Make FTP download 20MB and upload 2MB file from UE#5 and UE#8.

7) Trigger CS Video calls from UE#9 to UE#10, UE#11 to UE#12, UE#13 to UE#14 and UE#15 to

UE#16.

8) Disconnect the PS64/64 and HSDPA/64 calls from UE#1 to UE#8 after download and upload

complete.

9) Disconnect the CS Video calls.

10) Repeat steps 3 to 9, for 3 iteration.

11) Verify 8 UE CS video calls first, then 4 PS64/64 and 4 HSDPA/64 calls with remaining UEs, for

3 iterations.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 87: 2.1 Release Master Tracker

Pre Condition

1) CN,Security Gateway and HMS are up and operational.

Test Steps:

1) Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2) Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3) Trigger PS64/64/64 calls from UE#1, UE#2, UE#3 and UE#4.

4)Make FTP download 5mb and upload 2MB file from UE#1 to UE#4.

5)Trigger HSDPA/64 calls from UE#5, UE#6, UE#7 and UE#8.

6)Make a ftp download 20MB and upload 2MB file from UE#5 to UE#8.

7) Trigger AMR12.2 calls from UE#9 to UE#10 and UE#11 to UE#12.

8) Trigger CS Video calls from UE#13 to UE#14 and UE#15 to UE#16.

9) Disconnect the PS64/64 and HSDPA/64 calls from all the UEs after completion of download

and upload.

10) Disconnect the AMR12.2 calls and video calls.

11) Repeat steps 3 to 10, for 3 iteration.

12) Verify the testcase in below sequence of call models for 3 iterations.

1. Video call

2. AMR12.2 call

3. PS64/64

4. HSDPA/64 call

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1) CN,Security Gateway and HMS are up and operational.

Test Steps:

1) Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2) Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3) Trigger HSDPA/64 calls from UE#1, UE#2, UE#3, UE#4, UE#5, UE#6, UE#7 and UE#8.

4)Make FTP download 20MB and upload 2MB file from UE#1 to UE#8.

5)Trigger AMR12.2 calls from UE#9 to UE#10 and UE#11 to UE#12.

6)Trigger CS Video calls from UE#13 to UE#14 and UE#15 to UE#16.

7) Disconnect all the HSDPA/64 calls after download and upload complete.

8) Disconnect AMR12.2 calls and video calls.

9) Repeat steps 3 to 8, for 3 iteration.

10) Verify the testcase in below sequence of call models for 3 iterations.

1. Video call

2. AMR12.2 call

3.HSDPA/64 call

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 88: 2.1 Release Master Tracker

Pre Condition

1) CN,Security Gateway and HMS are up and operational.

Test Steps:

1) Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2) Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3) Trigger AMR12.2 calls from UE#1 to UE#2, UE#3 to UE#4,UE#5 to UE#6, UE#7 to UE#8.

4)Trigger PS64/64 calls from UE#9, UE#10, UE#11 and UE#12.

Make FTP download 5mb and upload 2MB file from UE#1 to UE#4.

5) Trigger HSDPA/64 calls from UE#13,UE#14,UE#15,UE#16 .

6)Make FTP download 20MB and upload 2MB file from UE#5 to UE#8.

7) Disconnect the PS64/64 and HSDPA/64 calls from UE#1 to UE#8 after download and upload

completes.

8) Repeat steps 4 to 6, 3 times.

9) Disconnect the AMR12.2 calls.

11) Repeat steps 3 to 9, for 3 iterations.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1) CN,Security Gateway and HMS are up and operational.

Test Steps:

1) Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2) Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3) Trigger PS64/64 calls from UE#1, UE#2, UE#3 and UE#4.

4)Make FTP download 5mb and upload 2MB file from UE#1 to UE#4.

5) Trigger HSDPA/64 calls from UE#5, UE#6, UE#7 and UE#8.

6)Make FTP download 20MB and upload 2MB file from UE#5 to UE#8.

7) Trigger AMR12.2 calls from UE#9 to UE#10 and UE#11 to UE#12.

8) Trigger CS Video calls from UE#13 to UE#14 and UE#15 to UE#16. Keep the calls active for 5

minutes.

9) Disconnect and connect the AMR12.2 calls and video calls for 3 times.

10) Disconnect the PS64/64 and HSDPA/64 calls from all the UEs after completion of download

and upload.

11) Repeat steps 3 to 10, for 3 iteration.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 89: 2.1 Release Master Tracker

Pre Condition

1) CN,Security Gateway and HMS are up and operational.

Test Steps:

1) Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2) Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3) Trigger PS64/64 calls from UE#1, UE#2, UE#3 and UE#4.

4) Make FTP download 5mb and upload 2MB file from UE#1 to UE#4.

5) Trigger HSDPA/64 calls from UE#5, UE#6, UE#7 and UE#8.

6)Make FTP download 20MB and upload 2MB file from UE#5 to UE#8.

7) Trigger AMR12.2 calls from UE#9 to UE#10 and UE#11 to UE#12.

8) Trigger CS Video calls from UE#13 to UE#14 and UE#15 to UE#16. Keep the calls active for 5

minutes.

9) Wait for Location area update for UE#9.... UE#16 and Routing Area Update messages for

UE#1..... UE#8.

10) Disconnect the PS64/64 and HSDPA/64 calls from all the UEs after completion of download

and upload.

11) Disconnect the AMR12.2 calls and video calls.

11) Repeat steps 3 to 10, for 3 iteration.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1) CN,Security Gateway and HMS are up and operational.

Test Steps:

1) Bring the HNB up and verify it is operational. Attach UEs to the HNB with different category of

UEs(5, 6,7,8,9,10).

2) Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3) Trigger HSDPA/64 calls from UE#1, UE#2, UE#3, UE#4, UE#5, UE#6, UE#7, UE#8, UE#9,

UE#10, UE#11, UE#12, UE#13, UE#14 ,UE#15 and UE#16.

4)Make FTP download of 20MB and upload of 2MB file for all the UEs. Verify data throughput

and record it.(0.96Mbps per code in DL and 64kbps in UL - Theoritical values as per PRD)

5) Disconnect the HSDPA/64 calls from all the UEs after download and upload complete.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 90: 2.1 Release Master Tracker

Pre Condition

1) CN,Security Gateway and HMS are up and operational.

Test Steps:

1) Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2) Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3) Trigger HSDPA/64 calls from UE#1, UE#2, UE#3, UE#4, UE#5, UE#6, UE#7, UE#8, UE#9,

UE#10, UE#11, UE#12, UE#13, UE#14 ,UE#15 and UE#16.

4)Make FTP download of 20MB and upload of 2MB file for all the UEs.

5) Move the UEs away from HNB but within coverage area using UE simulator.

Cell update and RLF may occur. Verify HNB handles Cell update with cause5,6. This can be

simulated using JDSU - DMTS tool

6) Disconnect the HSDPA/64 calls from all the UEs after download and upload complete.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1) CN,Security Gateway and HMS are up and operational.

Test Steps:

1) Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2) Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3) Trigger HSDPA/64 calls from UE#1, UE#2, UE#3, UE#4, UE#5, UE#6, UE#7, UE#8, UE#9,

UE#10, UE#11, UE#12, UE#13, UE#14 ,UE#15 and UE#16.

4)Make HTTP download of 20MB file for all the UEs. Verify data throughput and record

it.(0.96Mbps per code in DL and 64kbps in UL - Theoritical values as per PRD)

5) Disconnect the HSDPA/64 calls from all the UEs after download complete.

6) Repeat steps 3 to 5, for 2 hour.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 91: 2.1 Release Master Tracker

Pre Condition

1) CN,Security Gateway and HMS are up and operational.

Test Steps:

1) Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2) Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3) Trigger HSUPA call from UE#1 and start FTP uploading 10 Mb file.

4)Trigger HSDPA/64 calls from UE#2, UE#3, UE#4, UE#5, UE#6, UE#7, UE#8, UE#9, UE#10,

UE#11, UE#12, UE#13, UE#14 ,UE#15 and UE#16. Make HTTP download of 20MB file for all the

UEs. Verify data throughput and record it.(0.96Mbps per code in DL and 64kbps in UL -

Theoritical values as per PRD)

5) Disconnect the HSUPA call and HSDPA/64 calls after download completed.

6) Repeat steps 3 to 5, for 2 hour.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1) CN,Security Gateway and HMS are up and operational.

Test Steps:

1) Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2) Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3) Trigger HSUPA call from UE#1 and start FTP uploading 10 Mb file.Verify data throughput and

record it.

4)Trigger HSDPA/64 calls from UE#2, UE#3, UE#4, UE#5, UE#6, UE#7, UE#8, . Make HTTP

download of 20MB file for all the UEs. Verify data throughput and record it.(0.96Mbps per code

in DL and 64kbps in UL - Theoritical values as per PRD)

5) Trigger AMR12.2 call from UE#9-UE#10, UE#11-UE#12, UE#13- UE#14 , and UE#15-UE#16

6) Disconnect the HSUPA call and HSDPA/64 calls after download and upload completes.

7)Disconnect AMR12.2 calls.

8) Repeat steps 3 to 7, for 2 hour.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 92: 2.1 Release Master Tracker

Pre Condition

1) CN,Security Gateway and HMS are up and operational.

Test Steps:

1) Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2) Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3) Trigger HSDPA/64 calls from UE#1, UE#2, UE#3, UE#4, UE#5, UE#6, UE#7, UE#8, UE#9,

UE#10, UE#11, UE#12, UE#13, UE#14 ,UE#15 and UE#16.

4)Make FTP download of 20MB and upload of 2MB file for all the UEs.

5) Trigger HSDPA/64 call from UE#17.

6) Verify UE#17 HSDPA/64 call gets rejected by the HNB.

7) Verify other 16 HSDPA/64 calls are not affected.

8)Disconnect the HSDPA/64 calls from all the UEs after download and upload complete.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1) CN,Security Gateway and HMS are up and operational.

Test Steps:

1) Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2) Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3) Trigger HSDPA/64 calls from UE#1, UE#2, UE#3, UE#4, UE#5, UE#6, UE#7, UE#8, UE#9,

UE#10, UE#11, UE#12, UE#13, UE#14 ,UE#15 and UE#16.

4)Start streaming over UDP for all the UEs. Verify data throughput and record it.

(0.96Mbps per code in DL and 64kbps in UL - Theoritical values as per PRD)

5) Disconnect the HSDPA/64 calls from all the UEs after download completes.

6) Repeat steps 3 to 5, for 2 hour.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 93: 2.1 Release Master Tracker

Pre Condition

1) CN,Security Gateway and HMS are up and operational.

Test Steps:

1) Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2) Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3) Trigger HSDPA/64 calls from UE#1, UE#2, UE#3, UE#4, UE#5, UE#6, UE#7, UE#8, UE#9,

UE#10, UE#11, UE#12, UE#13, UE#14 ,UE#15 and UE#16.

4)Start HTTP download for UE#1... UE#8. Verify data throughput and record it.

5) Start FTP upload and download of 2MB file and 20MB file respectively for UE#9.. UE#16.

Verify data throughput and record it.(0.96Mbps per code in DL and 64kbps in UL - Theoritical

values as per PRD)

6)Disconnect the HSDPA/64 calls from all the UEs after download and upload complete.

7) Repeat steps 3 to 6, for 2 hour.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition:

1. CNE, HMS Server, Security Gw is up and running.

Test Steps:

1) Bring the HNB up and verify it is operational.

2) Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3) Attach 1 UE to HNB.

4) Trigger HSDPA/64 call from UE#1 .

5) Make a http download of 100 MB file from UE#1.

6) Move the UE out of coverage area and verify HSDPA call should be dropped, move back UE to

coverage area .

8) Repeat steps 5 to 6, for 3 iterations.

Post Condition:

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Page 94: 2.1 Release Master Tracker

Pre Condition

1) CN,Security Gateway and HMS are up and operational.

Test Steps:

1) Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2) Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3) Trigger AMR12.2 calls using 16 UEs. Keep all the calls active for 10min.

4) Disconnect all the 16 AMR12.2 calls.

5) Trigger PS64/64 calls using 16 UEs. Start download of 2MB file for all the UEs.

6) Disconnect all the PS64/64 call after completion of download.

7) Trigger 16 CS video calls using 16 UEs. Keep the calls active for 10min.

8) Disconnect all the video calls.

9) Trigger 16 HSDPA/64 calls from all the 16 UEs. Start HTTP download of 20MB file for all the

UEs.

10) Disconnect all the HS calls after completion of download.

11) Repeat steps 3 to 10, for 3 iterations.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.

Pre Condition

1) CN,Security Gateway and HMS are up and operational.

Test Steps:

1) Bring the HNB up and verify it is operational. Attach UEs to the HNB.

2) Start verifying that CPU and Memory utilization is ≤ 80% throughout the testcase.

3) Trigger HSDPA/64 calls from UE#1, UE#2, UE#3, UE#4, UE#5, UE#6, UE#7, UE#8, UE#9,

UE#10, UE#11, UE#12, UE#13, UE#14 ,UE#15 and UE#16.

4) Start download for all the UEs using iperf over TCP.

5) Disconnect the HSDPA/64 calls from all the UEs after download and upload complete.

6) Repeat steps 3 to 5, for 2 hour.

Post Condition

1. Verify HNB does not crash/hang.

2. Store the testcase logs in the log repository/server.