You are on page 1of 177

Subject Date Ref # NQ-NO/100-001/805-0002

3G and HSDPA Test Procedures 9/27/2006


Title
3G and HSDPA Trial Test Cases and Procedures Page 1 of 177

3G and HSDPA TRIAL


TEST CASES AND PROCEDURES

Version No : 4.0

Date : September 18, 2006

Prepared by : John N. Sabando


Delon S. Villanueva
Emeterio F. Gojar
Sheila M. Indencia

Noted by : Arturo Donato F. Bugayong

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 2 of 177

TABLE OF CONTENTS

TOPIC PAGE

1. Introduction ……………………………………………………………………………….. 7

2. Objectives …………………………………………………………………………………..7

3. Terminology ……………………………………………………………………………….. 7

4. 3G Trial Network Set-Up ………………………………………………………………… 8

5. List of Test Equipment and Tools ………………………………………………………8

6. Test Plan ………………………………………………………………………………....... 8


6.1 Basic Functionality Test …………………………………………………………… 9
6.1.1 CS Testing …………………………………………………………………………… 9
A. Mobility Management ………………………………………………………9
1. IMSI Attach …………………………………………………………….. 9
2. Location Update ………………………………………………………. 9
3. IMSI Detach ……………………………………………………………. 10
4. Authentication ………………………………………………………….. 10
5. Ciphering ……………………………………………………………….. 11
6. Location Update Fail ………………………………………………….. 13
B. Basic Service ……………………………………………………………… 13
1. Mobile to Mobile Speech Call …………………………………………13
2. Speech Call between Mobile and PSTN ……………………………..14
3. Video Call ………………………………………………………………..14
4. Special Service Call …………………………………………………….16
5. Short Message Service ……………………………………………….. 16
6. Call Failure Processing ……………………………………………….. 19
C. Supplementary Service …………………………………………………… 20
1. Call Forwarding ………………………………………………………….20
2. Call Forwarding for Video Call …………………………………………22
3. Call Barring ………………………………………………………………22
4. Call Barring for Video Call …………………………………………….. 23
5. Call Barring for SMS …………………………………………………….23
6. Number Identification …………………………………………………… 24
7. Call Completion ……………………………………………………...….. 24
8. Multiparty Service ………………………………………………………. 26
D. CS Domain Charging (CDR) …………………………..………………….. 26
1. CDR Generating ………………………………………………………… 26
6.1.2 PS Testing …………………………………………………………………………….. 28
A. Mobility Management ………………………………………………………..28
1. Attach ………………………………………………………………..........28
2. Detach ………………………………………….………………………….30
3. Purge ………………………………………………………………………31
4. Routing Area Update ………………………........................................ 31
5. Subscriber Management …………………………………………….…..31
6. Security ………………………………………………………………….. ..32
B. Session Management …………………………………………………….. ..33
1. PDP Context Activation …………………………………………………. 33
2. PDP Context Deactivation ……………………………………………... .35
3. APN Selection Rule ……………………………………………………….35
4. GGSN Address Resolution ……………………………………………….37
C. Reliability and Stability ………………………………………......................38
1. Interface and Link Redundancy ………………………………………… 38

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 3 of 177

2. Transfer Rate ..…………………………………………………………….. 38


D. PS Domain Charging ………………………………………………………… 38
1. M-CDR Generation …………………………………………………….. … 38
2. S-CDR Generation ………………………………………………………… 39
3. S-SMO-CDR and S-SMT-CDR Generation …………………………….. 39
4. G-CDR Generation .............................................................................. 39
E. CG …………………………………………………………………………....... 40
1. CDR Backup ……………………………………………………………….. 40
2. CG Client Function ………………………………………………………….40
6.1.3 RAN Testing …………………………………………………………………………….. 40
A. Bearer Capability CS Domain …………………………………………….... 40
1. Service Bearing CS Domain …………………………………………….. .40
2. Service Bearing PS Domain …………………………………………….. .41
3. Combined Service Bearing …………………………………………........ 42
4. SMS Service Bearing ………………………………………………...... … 42
B. Mobility Management ……………………………………………………….. .43
1. Paging ……………………………………………………………………….43
2. Soft Handover ………………………………………………………………43
3. Hard Handover ……………………………………………………….….... 44
4. Forward Handover ………………………………………………..…….… 46
C. Logical O&M …………………………………………………………..……….46
1. Logic Cell …………………………………………………………………...46
2. Common Transport Channel ……………………………………………..47
3. System Information …………………………………………….............. 48
4. Resource Audit …………………………………………………………… 48
5. Tracing …………………………………………………………….......……49
D. Radio Resource Management and Control …………………………….…. 49
1. Admission Control …….………………………………………………….. 49
2. Congestion Control ……………………………………………………..... 48
3. Load Balancing Control ……………………………………………………50
4. Dynamic Resource Control ……………………………………………….50
5. Power Control ……………………………………………………..……….52
6.1.4 Services ………………………………………………………………………………….53
A. Short Message (SMS) ………………………………………………………..54
1. Authenticating Subscriber ……………………………………………….. 54
2. Accessing SMC …………………………………………………………... 54
3. Submitting and Storing SMs ………………………………………......... 54
4. Forwarding SMs …………………………………………………………... 54
5. Priority Processing ……………………………………………………..... 55
6. Requesting Status Report ……………………………………………….. 55
7. Supporting SMs in English/Tagalog …………………………................56
8. Supporting Long SMs ……………………………………………………. 56
9. Maintenance and Test Function ……………………………………….. 57
10. Database Module Functions …………………………………………… 59
11. License Configuration ………………………………………………...... 60
B. Multimedia Message Services (MMS) …………………………………….. 60
1. Basic Service Flows …………………………………………………….. 60
2. Basic Features ……………………………………………………………. 61
3. Operation and Maintenance …………………………………………….. 67
C. Streaming Services ………………………………………………….…...... 70
1. Media Stream on Demand Service …………………………………….. 70
2. Live Streaming Service ………………………………………………….. 71
3. Supporting Encoding …………………………………………………….. 73
4. Content Management Function ………………………………………….75
5. CP Management Function ………………………………….................. 77
6. Security Management Function ………………………………….......... 78
7. System Maintenance ……………………………………………………. 78
8. Supporting Billing Function ………………………………………………79

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 4 of 177

6.1.4 HSDPA Testing ……………………………………………………………….…..…… 80


A. RAB Mapping ……………………………………………………….……….. 80
1. HSDPA Cell R99 UE Call Establishment – DCH-PS ………………… 80
2. HSDPA Cell R99 UE Call Establishment – DCH-CS ……………...... 80
3. HSDPA Cell HSDPA UE Call Establishment – Emergency……......... 80
4. HSDPA Cell HSDPA UE Call Establishment – SMS………….....…. . 81
5. HSDPA Cell HSDPA UE Call Establishment –H-PS ……………....... 81
6. HSDPA to Multiservice-Multiservice: AMR+HSDPA-PS……….....… 81
7. HSDPA to Multiservice-Multiservice: VP+HSDPA-PS…….....…….. 82
B. Power Management ……………………………………………………….. 82
1. HSDPA flexible power allocation with fixed HS-SCCH power,
OCNS 25% load ……………………………………………………….. 82
2. HSDPA flexible power allocation with fixed HS-SCCH power,
OCNS 50% load ……………………………………………………….. 82
C. Code Management ………………………………………………………….. 83
1. HSDPA RNC Controlled code allocation, R99 takes more ………….. 83
2. HSDPA RNC Controlled code allocation, HSDPA takes more ……. 83
D. Mobility ……………………………………………………………………..…. 84
1. HSDPA to HSDPA Mobility, intra RNC, intra Node B, intra frequency 84
2. HSDPA to HSDPA Mobility, intra RNC, inter frequency ………….… 84
3. HSDPA to non HSDPA Mobility, intra RNC, intra frequency ………. 85
4. HSDPA to non HSDPA Mobility, intra RNC, inter frequency ….…… 85
5. non HSDPA to HSDPA Mobility, intra RNC, intra frequency ………. 86
6. non HSDPA to HSDPA Mobility, intra RNC, inter frequency ……… 86
E. Load Management ……………………………………………..…………….. 87
1. HSDPA CAC …….………………………………………………………… 87
F. Iub Flow Control ………………………………………………………..…….. 88
1. Iub Efficiency for HSDPA, 1 E1 ……………………………………........ 88
2. Iub Efficiency for HSDPA and R99, 1 E1 ………………………………. 88
G. State Switch ………………………………………………………………….. 88
1. HSDPA to FACH and to Idle …………………………………………….. 88
2. FACH to HSDPA …….………………………………………………….. 89
H. RTT ……………………………………………………………………………. 89
1. Ping Packet delay ………………………………………………………… 89
I. Hardware Capacity …………………………………………………………… 90
1. 3*1 with 15 HS-PDSCH/cell ………………………………………………90
2. The HSDPA and R99 mixed cell sharing one carrier …………………. 90
J. Throughput Capacity …………………………………………………………..90
1. Cell throughput in case of 5 HS-PDSCH, Category 12 UE,
CDM4, CQI>16 ………………………………………………………….. 90
2. Cell throughput in case of 10 HS-PDSCH, Category 12 UE,
CDM4, CQI>16 ………………………………………………………….. 91
3. Cell throughput in case of 14 HS-PDSCH, Category 12 UE,
CDM4, CQI>16 ………………………………………………………….. 91
K. System Reliability …………………………………………………….…..….. 92
1. HSDPA system reliability ………………………………………………. 92
L. Iub Standard Interface ………………………………………………..……… 92
1. Common measurement of HSDPA cell-transmitted carrier power of
All codes not used for HS-PDSCH or HS-SCCH transmission ……. 92
2. Common measurement of HSDPA cell-HS-DSCH required
power measurement ……………………………………………………. 93
3. Common measurement of HSDPA cell-HS-DSCH provided bit rate
measurement ………………………………………………………….. .. 93
4. HSDPA cell configuration over Iub interface …….………………………93
5. HSDPA service reconfigured on RL over Iub interface ……………….. 94
M. Configuration …………………………………………………………………. 94
1. Activate/Deactivate HSDPA functionality in a node B ………………… 94
2. Create a new node B with the HSDPA functionality …………………… 94

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 5 of 177

3. Change of HSDPA Configuration Parameters …………………………. 95


4. Iub HSDPA capacity increase/decrease …………………………………95

6.2 Pilot/KPI Tests and Stress Tests ………………………………………………................ 96


6.2.1 General Test Procedures and Guidelines ……………………………………………. 97
6.2.2 INDOOR / OUTDOOR COVERAGE ASSESSMENTS (PILOT TEST) …………… 98
6.2.3 Stress Test (Subjective Measurements) ……………………………………………... 98
6.2.3.1 Voice Call ……………………………………………………………………. … 98
6.2.3.2 SMS ……………………………………………………………………………….. 98
6.2.3.3 Video Call ……………………………………………………………………….. 99
6.2.3.4 WAP Browsing …………………………………………………………….……. 100
6.2.3.5 Internet Browsing ……………………………………………………………….. 101
6.2.3.6 Multimedia Streaming ……………………………………………………….. .. 102
6.2.3.7 Downloading …………………………………………………………….………. 104
6.2.3.8 MMS …………………………………………………………………….............. 104
6.2.3.9 HSDPA …………………………………………………………………………… 105
6.2.4. Objective Measurements of Quality …………………………………………………. 106
A. Per Site Basis …………………………………………………………………………… 106
6.2.4.1 Voice Call Set-up Test …………………………………………………………. 106
6.2.4.2 Voice Call Quality Test …………………………………………………………. 106
6.2.4.3 SMS Test …………………………………………………………………........... 107
6.2.4.4 MMS Test ………………………………………………………………………… 109
6.2.4.5 WAP Test ………………………………………………………………………... 109
B. Whole Network …………………………………………………………………………. 110
6.2.4.6 HSDPA …………………………………………………………………………… 110
A. Stationary and Good Coverage ……………………………………………. 110
B. Stationary and Bad Coverage ……………………………………………… 110
C. Mobile ………………………………………………………………………… 111
D. Ping Tests ……………………………………………………………………. 111
6.2.5 KEY PERFORMANCE INDICATOR (KPIs) …………………………………………. 112

6.3 IOT Tests ……………………………………………………………………………………… 113


6.3.1 Objectives ………………………………………………………………………………. 113
6.3.2 SAMPLE 3G TRIAL NETWORK SETUP FOR IOT ……………………….............. 114
6.3.3 Equipment and Tools …………………………………………………………………... 114
6.3.4 General Test Guidelines and Procedures ……………………………..…………….. 115
6.3.5 IOT Test Scenarios …………………………………………………………………….. 115
6.3.5.1 3G2G Interoperability/Interworking Tests (Same Vendors) ………………….115
A. Basic Function ………………………………………………………………… 115
1. Voice call from GSM to WCDMA ………………………………………… 115
2. Voice call from WCDMA to GSM …………………………………..……. 116
3. SMS from WCDMA to GSM ……………………………………….…….. 117
4. SMS from GSM to WCDMA ……………………………………….…….. 118
B. Roaming ……………………………………………………………............... 119
1. CS Roaming from WCDMA to GSM …………………………………..... 119
2. CS Roaming from GSM to WCDMA ……………………………………. 120
3. CS HPLMN selection from GSM to WCDMA ……………………......... 121
4. PS Roaming from WCDMA to GPRS ……………………………......... 122
5. PS Roaming from GPRS to WCDMA ……………………………….. … 123
6. PS HPLMN selection from GPRS to WCDMA ………………….….. … 124
C. Reselection …………………………………………………………………… 125
1. CS Cell Reselection from WCDMA to GSM …………………………… 125
2. CS Cell Reselection from GSM to WCDMA ……………………………. 126
3. PS Cell Reselection from WCDMA to GPRS ………………………. … 127
4. PS Cell Reselection from GPRS to WCDMA ………………………. … 128
D. Handover ……………………………………………………………….......... 129
1. CS handover from WCDMA to GSM …………………………………… 129
2. CS handover from GSM to WCDMA ………………………….............. 130

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 6 of 177

3. PS handover in Cell_DCH from WCDMA to GPRS ………………….. .131


4. PS handover in Cell_FACH from WCDMA to GPRS ………….……… 132
5. PS handover from GPRS to WCDMA ……………………………..…… 133
6. CS+PS handover from WCDMA to GSM/GPRS …………………....... 134
7. Video Call handover from WCDMA to GSM/GPRS ………………..... 135
8. Reachability Test …………………………………………………………. 135
6.3.5.2 3G2G Interoperability/Interworking Tests (Different Vendors) …………….. 136
6.3.5.3 3G3G Interoperability/Interworking Tests (Different Vendors) …………….. 136

APPENDIX ……………………………………………………………………………….…………… 137


A. Network Elements Information ………………………………………………….………. 137
B. Test Results ……………………………………………………………………….……… 138

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 7 of 177

1. INTRODUCTION

This document is to be used as a reference for testing the 3G and HSDPA services on the
trial network of the different vendors. The results will be used for the evaluation of the
performance of the 3G and HSDPA services and for the recommendation of the vendor/s
that can provide the 3G infrastructure and services suitable to DMPI’s existing mobile
network.

This document describes the test specifications that are relevant to perform on the 3G trial
system. The feasibility of most of the tests depends on the 3G set-up of the vendor.

2. OBJECTIVES

The objectives of the 3G and HSDPA trial are:


a. Evaluate the 3G network functionality.
b. Test the customer experience with the following 3G and/or HSDPA services:
- speech, SMS, WAP
- video phone, video conferencing, video on demand
- web browsing via phone and laptop
- multimedia streaming
- file transfer or downloading
- MMS
c. Verify inter-working with GSM/GPRS network.
d. Test interoperability between different vendor equipments.
e. Evaluate the 3G parameters, KPIs, and tools:
- coverage
- performance
- OSS monitoring tools

3. TERMINOLOGY

BSC - Base Station Controller


BSC – Base Station Subsystem
GGSN – Gateway GPRS Support Node
GPRS – General Packet Radio Service
GSM – Global System for Mobile Communications
G-MSC – Gateway MSC
HSDPA - High-Speed Downlink Packet Access
IOT – Interoperability Tests
ISDN – Integrated Service Digital Network
KPI – Key Performance Indicator
MMS – Multi-Media Services
OSS – Operational Support System
PDN – Public Data Network
PCU – Packet Control Unit
SGSN – Serving GPRS Support Node
SMS – Short Message Services
WAP – Wireless Application Protocol

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 8 of 177

4. 3G TRIAL NETWORK SET-UP

The typical 3G set-up is shown in FIGURE-1.

Figure 1

NOTE: The set-up may vary with each vendor.

5. LIST OF TEST EQUIPMENT AND TOOLS

DMPI will use 3G test tools from an independent vendor, which is not included in the
3G/HSDPA trial. DMPI may allow each vendor to use and recommend 3G test tools.

The test equipment and tools to be utilized during the duration of the test period are:
1. 2G and 3G test phones with 3G-capable SIM cards.
2. HSDPA cards
3. Laptops
4. Outdoor and Indoor Drive Test Tools (Agilent Nitro, NEMO Handy, etc.)
5. Protocol Analyzer (Agilent Distributed Network Analyzer, Nethawk, etc.)
6. WAMS software.
7. Software for measuring throughput (DUMeter, etc.)

6. TEST PLAN

The 3G/HSDPA testing is divided into 3 main parts, namely:


a. Basic Functionality Tests
b. Pilot/KPI Tests and Stress Tests
c. IOT Tests

The results of the tests will be recorded by both DMPI and the vendor. Please refer to the
Appendix for the format of the results.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 9 of 177

6.1 Basic Functionality Tests

The basic functionality tests will verify the call set-up, mobility management (paging,
handover, cell updates), and bearer capability for CS. For PS, the tests will verify PDP
activation, web browsing, ftp, SMS, MMS, and multimedia streaming.

The functionality tests are divided into five parts, namely:

• Circuit Switch Testing


• Packet Switch Testing
• Radio Access Network Testing
• Services Testing
• HSDPA Testing

6.1.1 CS Testing

For CS testing, the tests are divided into 4 main parts:


• Mobility Management
• Basic Service
• Supplementary Service
• CS Domain Charging (CDR)

A. Mobility Management
1. IMSI Attach
a. Same SA
Objective:
Test the function of IMSI attach in one SA.
Test Procedure:
¾ Subscriber A powers off UE.
¾ Subscriber A powers on, and the MS originates IMSI attach in SA1
¾ Verify if subscriber A is attached
Expected Result:
Subscriber is able to attach.

b. Different SA
Objective:
Test the function of IMSI attach in a different SA.
Test Procedure:
¾ Subscriber A powers off UE.
¾ Subscriber A moves to SA2, powers on, and the MS originates IMSI
attach in SA2
¾ Verify if subscriber A is attached
Expected Result:
Subscriber is able to attach.

2. Location Update
a. MS location updates with IMSI
Objective:
Test the function of MS location updates with IMSI.
Test Procedure:
¾ Power on the MS, and the MS originates a IMSI Attach.
¾ Check at the Iu if a LOCATION_UPDATE_REQUEST message was
sent by the MS.
Expected Result:
Subscriber is able to attach and a location update request was sent by the
MS.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 10 of 177

b. Periodic Location Update


Objective:
Test the function of Periodic location update
Test Procedure:
¾ Power on the MS, and the MS originates a IMSI Attach.
¾ Keep the MS in service. The MS originates periodic location update
every 6 minutes.
¾ Check at the Iu if a LOCATION_UPDATE_REQUEST message was
sent by the MS every 6 minutes.
Expected Result:
Subscriber is able to attach and a location update request was sent by the
MS every 6 minutes.

3. IMSI Detach
a. MS location updates with IMSI
Objective:
Test the function of IMSI Detach
Test Procedure:
¾ Power off the MS, and the MS originates an IMSI Detach.
¾ Check at the Iu if an IMSI_DETACH_INDICATION message was sent
by the MS.
Expected Result:
Subscriber is able to.

b. Implicit IMSI detach


Objective:
Test the function of Implicit IMSI Detach
Test Procedure:
¾ Power on the MS, and the MS originates an IMSI Attach.
¾ Take the battery out of the mobile phone to break the communication
with the network.
¾ After 12 minutes, query the state of the subscriber in the VLR.
Expected Result:
Subscriber is detached.

4. Authentication
a. UE authentication in RNC serving area in updating location.
Objective:
Test the function of authentication process in updating location.
Test Procedure:
¾ Power on the UE, and the UE originates an IMSI Attach.
¾ Check at the Iu if the authentication signaling flow is correct.
Expected Result:
The authentication signaling flow is correct.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 11 of 177

UE RNC MSC/VLR HLR

LOCATION_UPDATION_REQUEST

COMMON_ID
SEND_AUTHENTICATION_INFO_REQ
SEND_AUTHENTICATION_INFO_CNF
AUTHENTICATION_REQUEST

AUTHENTICATION_RESPONSE
UPDATE_LOCATION_REQ
INSERT_SUBSCRIBER_DATA_IND

INSERT_SUBSCRIBER_DATA_RSP

UPDATE_LOCATION_CNF
SECURITY_MODE_COMMAND

SECURITY_MODE_COMPLETE

LOCATION_UPDATING_ACCEPT

IU_RELEASE_COMMAND

IU_RELEASE_COMPLETE

5. Ciphering
a. Ciphering in location update
Objective:
Test the function of ciphering process in updating location.
Test Procedure:
¾ Power on the UE, and the UE originates a location update.
¾ Check at the Iuc if the ciphering signaling flow is correct.
Expected Result:
The ciphering signaling flow is correct.

UE RNC MSC/VLR

UPDATION_REQUEST

COMMON_ID

AUTHENTICATION_REQUEST

AUTHENTICATION_RESPONSE

SECURITY_MODE_COMMAND

SECURITY_MODE_COMPLETE

LOCATION_UPDATING_ACCEPT

IU_RELEASE_COMMAND

IU_RELEASE_COMPLETE

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 12 of 177

b. Ciphering in subscriber’s MOC/MTC


Objective:
Test the function of ciphering process in call processing.
Test Procedure:
¾ UE1 originates a call to UE2.
¾ Check at the Iu and Iuc if the ciphering signaling flow is correct.
Expected Result:
The ciphering signaling flow is correct.

UE2 UE1 RNC MSC/VLR HLR

CM_SERVICE_REQUEST
COMMON_ID
AUTHENTICATION_REQUEST
AUTHENTICATION_RESPONSE
SECURITY_MODE_COMMAND
SECURITY_MODE_COMPLETE
SETUP
SEND_ROUTING_INFORMATION_REQ
CALL_PROCEEDING
PROVIDE_ROAMING_NUMBER_IND
PROVIDE_ROAMING_NUMBER_RSP
SEND_ROUTING_INFORMATION_CNF
RAB_ASSIGNMENT_REQUEST
RAB_ASSIGNMENT_RESPONSE

PAGING
PAGING_RESPONSE
COMMON_ID
AUTHENTICATION_REQUEST
AUTHENTICATION_RESPONSE
SECURITY_MODE_COMMAND
SECURITY_MODE_COMPLETE
SETUP
CALL_CONFIRMED

RAB_ASSIGNMENT_REQUEST

RAB_ASSIGNMENT_RESPONSE

ALERTING

CONNECT
CONNECT_ACKNOWLEDGE
CONNECT_ACKNOW LEDGE

DISCONNECT

RELEASE
DISCONNECT
RELEASE
RELEASE_COMPLETE
RELEASE_COMPLETE
IU_RELEASE_COMMAND
IU_RELEASE_COMPLETE
IU_RELEASE_COMMAND
IU_RELEASE_COMPLETE

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 13 of 177

6. Location Update Fail


a. IMSI unknown in HLR
Objective:
Test the function of location update but IMSI unknown in HLR
Test Procedure:
¾ Subscriber A powers on, and the UE originate location update.
¾ UE location update fails.
¾ Check that the HLR fail cause is “Unknown subscriber”.
¾ Query subscriber info at VLR.
Expected Result:
UE does not exist and location update fails.

b. Roaming restrict
Objective:
Test the function of roaming restrict.
Test Procedure:
¾ Make sure that UE is subscribed in HLR.
¾ Configure UE to allow roaming to LAC1, but not to LAC2.
¾ Check that the HLR fail cause is “Unknown subscriber”.
¾ Query subscriber info at VLR.
Expected Result:
UE is detached and location update fails.

B. Basic Service
1. Mobile to Mobile Speech Call
a. Mobile to Mobile Speech Call
Objective:
Test the function mobile to mobile speech call
Test Procedure:
¾ UE A initiates a normal call to UE B
¾ UE B answers and the call is connected
¾ Both parties keep the call for 2 minutes
¾ UE B hangs up
Expected Result:
The call is correctly set-up and speech is clear.

b. Voice calls with 8 AMR


Objective:
Test the function of Voice Calls with 8 AMR Code
Test Procedure:
¾ Configure 12.2K rate as the AMR code.
¾ UE A initiates a normal call to UE B.
¾ UE B alerting, and answers the call.
¾ Keep the call for 2 minues and then disconnect the call.
¾ Repeat the procedure, using different rate each times:
10.2k, 7.95k, 7.4k, 6.7k, 5.9k, 5.15k, 4.75k
Expected Result:
Call is successful and quality may vary according to different AMR codes.

c. TrFO function in 3G End Office


Objective:
Test the function of TrFO in 3G End Office
Test Procedure:
¾ UE A initiates a normal call to UE B.
¾ UE B answers and the call is connected.
¾ Observe the TC resources in MGW
¾ Disconnect the call

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 14 of 177

Expected Result:
In MGW, no TC resources are occupied by this call.

2. Speech Call between Mobile and PSTN (Optional)


a. Mobile to PSTN Speech Call
Objective:
Test the function of mobile to PSTN speech call
Test Procedure:
¾ UE1 initiates a normal call to a local PSTN subscriber, and PSTN
subscriber alerting.
¾ PSTN subscriber answers the call, holds it on for a while, and hangs up
the call
Expected Result:
The call is successful.

b. Mobile to PSTN Speech Call, UE sending DTMF


Objective:
Test the function of DTMF
Test Procedure:
¾ UE1 initiates a normal call to a local PSTN subscriber, and PSTN
subscriber alerting.
¾ PSTN subscriber answers the call, and holds it for 2 minutes.
¾ In the conversation, press a digit key of the mobile phone, and then
release the key.
¾ Observe lu-interface signaling.
Expected Result:
PSTN subscriber can hear a DTMF tone. A START_DTMF message is
observed.

UE1 RNC MSC/VLR HLR PSTN

IAM

ALERTING ACM

CONNECT ANM

CONNECT_ACKNOWLEDGE

START_DTMF

START_DTMF_ACKNOWLEDG
E
STOP_DTMF

STOP_DTMF_ACKNOWLEDGE

c. Mobile to PSTN, more than 15 digits


Objective:
Test the function that the MSC can handle dialing a PSTN number with
more than 15 digits.
Test Procedure:
¾ UE 1 dials the local PSTN subscriber with more than 15 digits.
¾ The PSTN subscriber answers the call, holds it for 2 minutes, and
hangs up the call.
Expected Result:
Call is successful and can support 15 digits.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 15 of 177

d. PSTN to Mobile speech call


Objective:
Test the function of PSTN to Mobile speech call.
Test Procedure:
¾ PSTN subscriber initiates a call to UE1.
¾ UE1 answers, and the call is connected.
¾ UE2 hangs up.
¾ Observe MTP3 signaling.
Expected Result:
Call is successful and signaling is normal.

UE2 RNC MSC/VLR HLR PSTN

IAM
SEND_ROUTING_INFORMATION_REQ
PROVIDE_ROAMING_NUMBER_IND
PROVIDE_ROAMING_NUMBER_RSP

SEND_ROUTING_INFORMATION_CNF

PAGING
PAGING_RESPONSE
COMMON_ID

AUTHENTICATION_REQUEST

AUTHENTICATION_RESPONS E
SECURITY_MODE_COMMAND
SECURITY_MODE_COMPLETE
SETUP

CALL_CONFIRMED
RAB_ASSIGNMENT_REQUEST

RAB_ASSIGNMENT_RESPONSE
ALERTING
ACM
CONNECT
ANM
CONNECT_ACKNOWLEDGE

DISCONNECT
REL
RELEASE
RLC
RELEASE_COMPLETE
IU_RELEASE_COMMAND
IU_RELEASE_COMPLETE

e. PSTN to Mobile speech call with Echo Cancellation


Objective:
Test the function of echo cancellation.
Test Procedure:
¾ Configure 64ms EC.
¾ PSTN subscriber initiates a call to UE1.
¾ UE1 answers, and the call is connected.
¾ UE2 hangs up.
¾ Observe voice quality.
¾ Check in the MGW that there is one EC resources occupied by this call.
¾ Increase the EC value to 128ms and repeat the procedure.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 16 of 177

Expected Result:
Call is successful and one EC resource is occupied.

3. Video Call
a. Mobile to Mobile Video Call
Objective:
Test the function of Mobile to Mobile video call
Test Procedure:
¾ UE1 initiates a video call to UE 2.
¾ UE 2 answers and the call is connected.
¾ Call is kept for 2 minutes and then UE 2 hangs up.
Expected Result:
The video call is successful and the quality is acceptable.

4. Special Service Call


a. Emergency call (no USIM inside UE)
Objective:
Test the function of Emergency Call
Test Procedure:
¾ Take out the USIM from the UE, and power on the UE.
¾ Initiate an emergency call from the UE, e.g. call 112.
¾ The emergency call is connected to the PSTN.
¾ Call is kept for 2 minutes and then UE 2 hangs up.
Expected Result:
The emergency call is successful.

b. Emergency call (USIM inside UE)


Objective:
Test the function of Emergency Call
Test Procedure:
¾ Insert the USIM card into the mobile phone, and power on the UE.
¾ Initiate an emergency call from the UE, e.g. call 112.
¾ The emergency call is connected to the PSTN.
¾ Call is kept for 2 minutes and then UE 2 hangs up.
Expected Result:
The emergency call is successful.

5. Short Message Service


a. Short Message Service (MO)
Objective:
Test the function of Short Message Service (MO)
Test Procedure:
¾ UE A sends a short message “12345” to UE B.
¾ The short message “12345” is sent to UE B from SMC.
¾ Observe the signaling messages.
Expected Result:
The sms is successfully sent by UE A and received by UE B. The
signaling messaging is normal.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 17 of 177

UEa RNC MSC/VLR SMC

CM_SERVICE_REQUEST

COMMON_ID
AUTHENTICATION_REQUEST
AUTHENTICATION_RESPONSE
SECURITY_MODE_COMMAND
SECURITY_MODE_COMPLETE
SMS_CP_DATA
SMS_CP_ACK
MAP_MO_FORWARD_SM
FORWARD_SHORT_MESSAGE_REQ
MAP_MO_FORWARD_SM
FORWARD_SHORT_MESSAGE_CNF
SMS_CP_DATA
SMS_CP_ACK

IU_RELEASE_COMMAND

IU_RELEASE_COMPLETE

b. Short Message Service (MT)


Objective:
Test the function of Short Message Service (MT)
Test Procedure:
¾ UE A sends a short message “12345” to UE B.
¾ The short message “12345” is sent to UE B from SMC.
¾ Observe the signaling messages.
Expected Result:
The sms is successfully sent by UE A and received by UE B. The
signaling messaging is normal.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 18 of 177

UEb RNC MSC/VLR HLR SMC

MAP_SEND_ROUTING_INFO
_FOR_SM
MAP_SEND_ROUTING_INFO
_FOR_SM_ACK
MAP_MT_FORWARD_SM
FORWARD_SHORT_MESSAGE_IND
PAGING

PAGING_RESPONSE
COMMON_ID
AUTHENTICATION_REQUEST
AUTHENTICATION_RESPONSE
SECURITY_MODE_COMMAND
SECURITY_MODE_COMPLETE
SMS_CP_DATA
SMS_CP_ACK
MAP_MT_FORWARD_SM
SMS_CP_DATA FORWARD_SHORT_MESSAGE_RSP
SMS_CP_ACK
IU_RELEASE_COMMAND

IU_RELEASE_COMPLETE

c. Mobile can receive SMMT during speech call


Objective:
Test the function of Mobile receive SMMT during speech call
Test Procedure:
¾ UE B is in a call with PSTN.
¾ UE A sends a short message to UE B.
¾ Observe the signaling messages.
Expected Result:
The sms is successfully received by UE B during a voice call.

d. Mobile can receive SMMT during video call


Objective:
Test the function of Mobile receive SMMT during video call
Test Procedure:
¾ UE A initiates a video call to UE C.
¾ UE C answers the call and holds the call for 2 minutes.
¾ UE B sends a short message to UE A.
Expected Result:
The sms is successfully received by UE A during a video call.

e. SMMT to a UE, out of coverage


Objective:
Test the function that UE B can receive short message sent by UE A
during B’s out of coverage after returning to the service area.
Test Procedure:
¾ UE A is in the service area, but UE B is not in the service area.
¾ UE A sends a short message to UE B.
¾ UE B returns to the service area.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 19 of 177

Expected Result:
The sms is is not received by UE B when out of coverage area. The sms
is successfully received by UE B when back in the coverage area.

f. SMMT to a detached UE, UE can receive SMS when switched on the


mobile.
Objective:
Test the function of that after switching on the mobile phone, UE B can
receive the short message sent by UE A when B’s mobile phone is
switched off.
Test Procedure:
¾ UE A sends a short message to UE B.
¾ UE B powers on.
¾ Check if UE B can receive the short message or not.
Expected Result:
The sms is received by UE B when powered on.

g. SMMT to a memory full UE, UE can receive SMS memory not full
Objective:
Test the function of that UE B can receive short messages when there is
free memory again.
Test Procedure:
¾ UE A keeps sending short messages to UE B until the memory of UE B
is full.
¾ Delete some short messages from UE B.
Expected Result:
The sms is received by UE B when memory is not full. New short
messages can be received as soon as some short messages are deleted.

6. Call Failure Processing


a. Mobile Terminating Call, the UE is busy
Objective:
Test the function of Call Failure Processing when the called UE is busy.
Test Procedure:
¾ UE A is idle, UE B is engaged in a call.
¾ UE A calls UE B.
¾ UE A hears the announcement.
Expected Result:
UE A hears the announcement that the user is busy.

b. Mobile Terminating Call, the UE does not answer


Objective:
Test the function of Call Failure Processing when the called UE does not
answer.
Test Procedure:
¾ UE A and UE B are idle.
¾ UE A calls UE B.
¾ UE B rings and does not answer.
¾ The MSC releases the call after time out and then UE A hears the
announcement.
Expected Result:
UE A hears the announcement that the user does not answer.

c. Mobile Terminating Call, the UE is out of coverage


Objective:
Test the function of Call Failure Processing when the called UE does not
answer.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 20 of 177

Test Procedure:
¾ UE A and UE are idle.
¾ UE A calls UE B.
¾ UE B rings and does not answer.
¾ The MSC releases the call after time out and then UE A hears the
announcement.
Expected Result:
UE A hears the announcement that the user does not answer.

d. Mobile Terminating Call, the UE is switched off


Objective:
Test the function of Call Failure Processing when the called UE is
powered off.
Test Procedure:
¾ UE A and UE B are idle.
¾ UE B is powered off.
¾ UE A initiates a normal call to UE B.
¾ UE A hears the announcement.
Expected Result:
UE A hears the announcement that the subscriber is powered off.

e. Mobile Terminating Call, the UE is NULL


Objective:
Test the function of Call Failure Processing when the called UE number is
NULL.
Test Procedure:
¾ UE A is idle and UE B does not exist in HLR.
¾ UE A initiates a normal call to UE B.
¾ UE A hears the announcement.
Expected Result:
UE A hears the announcement that the called party is null.

C. Supplementary Service
1. Call Forwarding
a. Call Forwarding Unconditional
Objective:
Test the function of Call Forwarding Unconditional
Test Procedure:
¾ UE A initiates a call to UE B
¾ The call is forwarded to the PSTN user C, and PSTN user C answers
the call.
¾ Both parties keep the call for 2 minutes
¾ PSTN user C disconnects the call.
Expected Result:
The call is forwarded to the correct number.

b. Call Forwarding on Mobile Subscriber Busy


Objective:
Test the function of Call Forwarding on Busy
Test Procedure:
¾ UE B is in a call with UE C
¾ UE A initiates a call to UE B
¾ The call is forwarded to the UE D, and UE D answers the call.
¾ Both parties keep the call for 2 minutes
¾ UE D disconnects the call.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 21 of 177

Expected Result:
The call is forwarded to the alternative number when the dialed number is
busy.

c. Call Forwarding on No Reply


Objective:
Test the function of Call Forwarding on No Reply
Test Procedure:
¾ UE A calls UE B.
¾ UE B is alerting, but does not answer the call.
¾ After the timeout, the call is forwarded to the PSTN user C, and PSTN
user C answers, keep the call for a while.
¾ PSTN user C disconnects the call
Expected Result:
The call is forwarded to the alternative number when the dialed number
does not reply.

d. Call Forwarding on Mobile Subscriber Not Reachable


Objective:
Test the function of Call Forwarding on Mobile Subscriber Not Reachable.
Test Procedure:
¾ UE B is powered off.
¾ UE A and PSTN C are idle.
¾ UE A calls UE B.
¾ The call is forwarded to PSTN C.
¾ PSTN C answers and keeps the call for 2 minutes.
¾ PSTN user C disconnects the call
Expected Result:
The call is forwarded to the alternative number when the dialed number is
unreachable.

e. Call Forwarding notification to A-party and B-party


Objective:
Test the function of Call Forwarding notification to party A and party B.
Test Procedure:
¾ UE B is in a call with UE C.
¾ UE A calls UE B.
¾ UE A calls UE B.
¾ The call is forwarded to PSTN D. During the call forwarding process,
UE A hears a call forwarding announcement.
¾ PSTN D answers and keeps the call for 2 minutes.
¾ PSTN user D disconnects the call
Expected Result:
The call forwarding announcement is working.

f. Call Forwarding activation/interrogation/deactivation


Objective:
Test the function of Call Forwarding activation/interrogation/deactivation
Test Procedure:
¾ UE B Register CFU: **21*FTN number#
¾ Query the MSC if the CFU Service is Active.
¾ UE B Deactivation CFU: #21#
¾ UE B Activation CFU: *21#
¾ UE B Interrogation CFU: *#21#
¾ UE B Erasure CFU: ##21#
Expected Result:
Every time the CFU is activated, deactivated, or interrogated, a
notification display appears on the monitor of UE B.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 22 of 177

2. Call Forwarding for Video Call


a. Call Forwarding Unconditional for Video Call
Objective:
Test the function of Call Forwarding for Video Call
Test Procedure:
¾ UE A executes a video call to UE B.
¾ The call is forwarded to the UE C, and UE C answers the call.
¾ Both parties keep the call for 2 minutes
¾ UE A disconnects the call.
Expected Result:
The video call is forwarded to the correct number.

b. Call Forwarding on Mobile Subscriber Busy for Video Call


Objective:
Test the function of Call Forwarding for video call.
Test Procedure:
¾ UE B is in a call with UE C.
¾ UE A initiates a video call to UE B
¾ The video call is forwarded to the UE D, and UE D answers the call.
¾ Both parties keep the call for 2 minutes
¾ UE D disconnects the call.
Expected Result:
The video call is forwarded to the alternative number when the dialed
number is busy.

c. Call Forwarding on No Reply for Video Call


Objective:
Test the function of Call Forwarding for Video Call on No Reply
Test Procedure:
¾ UE A originates a video call to UE B.
¾ UE B is alerting, but does not answer the call.
¾ After the timeout, the video call is forwarded to UE C, and UE C
answers, keeps the call for a while.
¾ UE C disconnects the call.
Expected Result:
The video call is forwarded to the alternative number when the dialed
number does not reply.

d. Call Forwarding on Mobile Subscriber Not Reachable for Video Call


Objective:
Test the function of Call Forwarding on Mobile Subscriber Not Reachable.
Test Procedure:
¾ UE B is powered off.
¾ UE A and PSTN C are idle.
¾ UE A originates a video call to UE B.
¾ The video call is forwarded to UE C.
¾ UE C answers and keeps the call for 2 minutes.
¾ UE C disconnects the call.
Expected Result:
The call is forwarded to the alternative number when the dialed number is
unreachable.

3. Call Barring
a. Barring of All Outgoing Calls
Objective:
Test the function of Barring of All Outgoing Calls

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 23 of 177

Test Procedure:
¾ UE A calls PSTN C.
¾ Call fails and UE A hangs up.
Expected Result:
The call fails and the tone indicates that the call is barred.

b. Barring of All Incoming Calls


Objective:
Test the function of Barring of All Incoming Calls
Test Procedure:
¾ UE A calls UE B.
¾ Call fails and UE A hangs up.
Expected Result:
The call fails and the tone indicates that the incoming call is barred.

c. Call Barring activation/interrogation/deactivation


Objective:
Test the function of call barring activation/interrogation/deactivation.
Test Procedure:
¾ Activation BAOC: *33*0001#
¾ Interrogation BAOC: *#33*0001#
¾ Deactivation BAOC: #33*0001#
¾ Activation BAIC: *35*0001#
¾ Interrogation BAIC: *#35*0001#
¾ Deactivation BAIC: #35*0001#
Expected Result:
The activation, deactivation, and interrogation works.

4. Call Barring for Video Call


a. Barring of All Outgoing Calls for Video Call
Objective:
Test the function of Barring of All Outgoing Calls for Video Call
Test Procedure:
¾ UE A originates a video call to UE B.
¾ Video call fails and UE A hangs up.
Expected Result:
The call fails and the tone indicates that the video call is barred.

b. Barring of All Incoming Calls for Video Call


Objective:
Test the function of Barring of All Incoming Calls for Video Call
Test Procedure:
¾ UE A originates a video call to UE B.
¾ Call fails and UE A hangs up.
Expected Result:
The call fails and the incoming video call is barred.

5. Call Barring for SMS


a. Barring of All Outgoing Calls for SMS
Objective:
Test the function of Barring of All Outgoing Calls for SMS
Test Procedure:
¾ UE A originates a short message to UE B.
Expected Result:
The MO short message fails.
b. Barring of All Incoming Calls for SMS
Objective:
Test the function of Barring of All Incoming Calls for SMS

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 24 of 177

Test Procedure:
¾ UE A originates a short message to UE B.
Expected Result:
To UE A, the MO short message is successful. To UE B, the MT short
message fails.

6. Number Identification
a. MS subscribe CLIR
Objective:
Test the function of MS subscribe CLIR
Test Procedure:
¾ UE A originates a call to UE B.
Expected Result:
The calling number cannot be displayed on UE B. Only “Private Number”
is displayed.

b. Only subscribe CLIP


Objective:
Test the function of only subscribe CLIP
Test Procedure:
¾ UE A originates a call to UE B.
Expected Result:
The calling number is correctly displayed on UE B screen.

7. Call Completion
a. Call Hold
Objective:
Test the function of Call Hold
Test Procedure:
¾ UE A originates a call to UE B.
¾ UE B answers the call.
¾ UE A holds the call.
¾ UE A retrieves the call.
¾ UE A hangs up.
Expected Result:
When the call is put on hold, UE B hears a hold announcement. The call
flow is normal.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 25 of 177

UEb UEa RNC MSC/VLR HLR

CM_SERVICE_REQUEST
COMMON_ID
AUTHENTICATION_REQUEST
AUTHENTICATION_RESPONSE
SECURITY_MODE_COMMAND
SECURITY_MODE_COMPLETE
SETUP
SEND_ROUTING_INFORMATION_REQ
CALL_PROCEEDING
PROVIDE_ROAMING_NUMBER_IND
PROVIDE_ROAMING_NUMBER_RSP
SEND_ROUTING_INFORMATION_CNF
PAGING
PAGING_RESPONSE
COMMON_ID
AUTHENTICATION_REQUEST
AUTHENTICATION_RESPONSE
SECURITY_MODE_COMMAND
SECURITY_MODE_COMPLETE
SETUP
CALL_CONFIRMED
RAB_ASSIGNMENT_REQUEST

RAB_ASSIGNMENT_REQUEST
RAB_ASSIGNMENT_RESPONSE
RAB_ASSIGNMENT_RESPONSE

ALERTING
CONNECT
CONNECT
CONNECT_ACKNOWLEDGE
CONNECT_ACKNOWLEDGE

HOLD
HOLD_ACKNOWLEDGE
FACILITY(1)
RETRIEVE
RETRIEVE_ACKNOWLEDGE
FACILITY(2)

b. Call Waiting
Objective:
Test the function of Call Waiting
Test Procedure:
¾ UE A originates a call to UE B.
¾ UE B answers the call.
¾ UE C intitiates a call to UE B.
¾ Before the call waiting timer expires, UE B releases the call with UE A
and accepts the call from UE C.
¾ UE A hangs up.
Expected Result:
On the screen, UE B notices an incoming call while UE C can hear the
ring back tone.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 26 of 177

c. Multiple Call Hold Swapping


Objective:
Test the function of multiple call hold swapping.
Test Procedure:
¾ UE A originates a call to UE B and UE B answers the call.
¾ UE A holds the call with UE B.
¾ UE A initiates a call to UE C and UE C answers the call.
¾ UE A holds the call with UE C and retrieves the call with UE B.
¾ UE A holds the call with UE B and retrieves the call with UE C.
¾ UE A hangs up.
Expected Result:
The hold calls are not disconnected.

d. SMMO can be initiated by MS who currently holds a call.


Objective:
Test the function of multiple call hold swapping.
Test Procedure:
¾ UE A originates a call to UE B and UE B answers the call.
¾ UE A holds the call with UE B.
¾ UE A sends a short message to UE C.
Expected Result:
The SMS was successfully received by UE C while UE B is on hold.

8. Multiparty Service
a. Six-Way Service
Objective:
Test the function of six-way multiparty service.
Test Procedure:
¾ UE A originates a call to UE B and UE B answers the call.
¾ UE A holds the call with UE B.
¾ UE A initiates a call to UE C and UE C answers the call.
¾ UE A sets up a multi-party service.
¾ UE A holds the multi-party call.
¾ UE A initiates a call to UE D successfully, and then UE A applies the
multi-party service again.
¾ Repeat the same steps mentioned above to UE E and UE F into the
multi-party call.
¾ UE B releases the multi-party call.
Expected Result:
All UEs are in the multi-party call and no UE is dropped.

D. CS Domain Charging (CDR)


1. CDR Generating
a. Bill of MOC
Objective:
Test the function of Bill of MOC
Test Procedure:
¾ UE A originates a call to UE B and UE B answers.
¾ UE A clears the call after 2 minutes.
¾ In the iGWB client, check the bill for the call.
Expected Result:
The call is successful and a Mobile Originating (MO) bill is generated for
UE A and the information is correct for:
• Calling Number
• Called Number
• Served MSISDN (UE A number)
• Served IMSI

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 27 of 177

• Initial Time
• Conversation Duration

b. Bill of MTC
Objective:
Test the function of Bill of MTC
Test Procedure:
¾ UE A originates a call to UE B and UE B answers.
¾ UE A clears the call after 2 minutes.
¾ In the iGWB client, check the bill for the call.
Expected Result:
The call is successful and a Mobile Terminating (MT) bill is generated for
UE B and the information is correct for:
• Calling Number
• Called Number
• Roaming Number
• Served MSISDN (UE A number)
• Served IMSI
• Initial Time
• Conversation Duration

c. Bill of Call Forward


Objective:
Test the function of Bill of Call Forward
Test Procedure:
¾ UE A calls to UE B
¾ The call is forwarded to UE C and UE C answers the call.
¾ UE A clears the call after 2 minutes.
¾ In the iGWB client, check the bill for the call.
Expected Result:
The call is successful. An MO bill is generated for UE A, a forwarding bill
is generated for UE B and an MT bill is generated for UE C. In the
forwarding bill for UE B and the information is correct for:
• Calling Number
• Called Number
• Connected Number (UE C number)
• Served MSISDN (UE B number)
• Served IMSI
• Initial Time
• Conversation Duration

d. Bill of Call Hold and Call Wait


Objective:
Test the function of Bill of Call Forward
Test Procedure:
¾ UE A initiates a call to UE B and UE B answers the call.
¾ UE B holds the call with UE A.
¾ UE C initiates a call to UE B and UE B answers the call.
¾ UE B clears the call after 2 minutes.
¾ In the iGWB client, check the bill for the call.
Expected Result:
The call is successful. Two MTC bills are generated for UE B and the
information is correct for:
• Calling Number
• Called Number
• Served MSISDN (UE B number)
• Served IMSI

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 28 of 177

• Initial Time
• Conversation Duration
• CH_invoked_times
• CW_invoked_times
• CHOLD
• CWAIT

e. Bill of SMS (MO)


Objective:
Test the function of Bill of SMS (MO)
Test Procedure:
¾ UE A sends a short message to UE B.
¾ In the iGWB client, check the bill for the SMS.
Expected Result:
UE B received the SMS and a Mobile Originating (MO) SMS bill is
generated for UE A and the information is correct for:
• MO SMS number
• MT SMS number
• Bytes
• SMC address

f. Bill of SMS (MT)


Objective:
Test the function of Bill of SMS (MT)
Test Procedure:
¾ UE A sends a short message to UE B.
¾ In the iGWB client, check the bill for the SMS.
Expected Result:
UE B received the SMS and a Mobile Originating (MO) SMS bill is
generated for UE A and an MT SMS bill is generated for UE B. IN the MT
SMS bill for UE B, the information is correct for:
• MO SMS number
• MT SMS number
• Bytes
• SMC address

6.1.2 PS Testing

For PS testing, the tests are divided into 5 main parts:


• Mobility Management
• Session Management
• Reliability and Stability
• PS Domain Charging
• CG

A. Mobility Management
1. Attach
a. GPRS attach with IMSI
Objective:
Check if the network can successfully handle the GPRS attach originated
by Normal Subscriber with IMSI
Test Procedure:
¾ No valid P-TMSI is stored in the USIM of the MS and the MS is not
registered in SGSN.
¾ Power on the UE and the UE originates GPRS attach.
¾ Check that UE is attached.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 29 of 177

Expected Result:
The attach messaging is normal.

MS RNC SGSN HLR

Attach Request

Send Authentication Info

Send Authentication Info Ack

Authentication and Ciphering Request

Authentication and Ciphering Response

Security Mode Command

Security Mode Complete

Update Location

Insert Subscriber Data

Insert Subscriber Data Ack

Update Location Ack

Attach Accept

Attach Complete

b. GPRS attach with P-TMSI


Objective:
Check if the network can successfully handle the GPRS attach originated
by Normal Subscriber with P-TMSI
Test Procedure:
¾ A valid P-TMSI is stored in the USIM of the MS and the MS is registered
in SGSN.
¾ Power on the UE and the UE originates GPRS attach.
¾ Check that UE is attached.
Expected Result:
The attach messaging is normal.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 30 of 177

MS RNC SGSN
Attach Request

Authentication and Ciphering Request

Authentication and Ciphering Response

Security Mode Command

Security Mode Complete

Attach Accept

Attach Complete

c. GPRS attach, MS unknown in HLR


Objective:
Check if the network can successfully handle the GPRS attach originated
by Unknown Subscriber
Test Procedure:
¾ No valid P-TMSI is stored in the USIM of the MS, the MS is not
registered in SGSN and no subscription data found in the HLR.
¾ Power on the UE and the UE originates GPRS attach.
¾ Check that UE is attached.
Expected Result:
The attach messaging is normal.
MS RNC SGSN HLR
Attach Request

Send Authentication Info

Send Authentication Info Ack

Attach Reject

Iu Release Command

Iu Release Complete

2. Detach
a. MS initiated Detach
Objective:
Check if the network can successfully handle detach originated by Normal
Subscriber
Test Procedure:
¾ Power on the MS and the MS originates GPRS attach.
¾ Power off the MS, and the MS originates GPRS detach.
Expected Result:
The detach messaging is normal.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 31 of 177

MS RNC SGSN
Detach Request

Iu Release Command

Iu Release Complete

b. SGSN initiated Detach-Implicit


Objective:
Check if the network can successfully handle detach Normal Subscriber
implicitly.
Test Procedure:
¾ Power on the MS and the MS originates GPRS attach.
¾ Pull out UE’s battery, and wait for Mobile Reachable Timer to expire.
Expected Result:
SGSN detaches MS implicitly after timer expires.

3. Purge
a. Purge
Objective:
Check if SGSN can successfully purge Normal Subscriber
Test Procedure:
¾ Power on the MS and the MS originates GPRS attach.
¾ Power off the MS, and the MS originates GPRS detach.
¾ By command purge the MS from SGSN.
Expected Result:
No data for MS is stored in the SGSN.

4. Routing Area Update


a. Intra SGSN Routing Area Update
Objective:
Check if the network can successfully handle the Routing Area Update
originated by normal subscriber.
Test Procedure:
¾ Power on the MS and the MS originates GPRS attach.
¾ The MS roams to another Routing Area within the same SGSN, and
initiates Routing Area Update
Expected Result:
Routing area messaging is normal.
MS RNC SGSN

Routeing Area Update Request

Security Mode Command

Security Mode Complete

Routeing Area Update Accept

Routeing Area Update Complete

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 32 of 177

b. Periodic RA update
Objective:
Check if the network can successfully handle the periodic Routing Area
Update.
Test Procedure:
¾ Power on the MS and the MS originates GPRS attach.
¾ Wait for the periodic routing area update timer to expire.
¾ The MS initiates periodic routing area update.
Expected Result:
Periodic routing area update is working.

5. Subscriber Management
a. HLR modification of subscriber data
Objective:
Check if SGSN can successfully handle modification of subscriber data
from HLR.
Test Procedure:
¾ Power on the MS and the MS originates GPRS attach.
¾ Modify GPRS service for the MS, such as APN.
Expected Result:
Modification of subscriber data is successful.

b. HLR deleting of subscriber data


Objective:
Check if SGSN can successfully handle deleting of subscriber data from
HLR.
Test Procedure:
¾ Power on the MS and the MS originates GPRS attach.
¾ Delete GPRS service for the MS.
Expected Result:
Deleting of subscriber data is successful.

6. Security
a. Authentication
Objective:
Check if the network can successfully implement authentication function.
Test Procedure:
¾ Power on the MS and the MS originates GPRS attach.
Expected Result:
Normal attach procedure.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 33 of 177

MS RNC SGSN HLR

Attach Request

Send Authentication Info

Send Authentication Info Ack

Authentication and Ciphering Request

Authentication and Ciphering Response

Security Mode Command

Security Mode Complete

Update Location

Insert Subscriber Data

Insert Subscriber Data Ack

Update Location Ack

Attach Accept

Attach Complete

b. Ciphering
Objective:
Check if the network can successfully implement ciphering function.
Test Procedure:
¾ Power on the MS and the MS originates GPRS attach.
¾ Delete GPRS service for the MS.
Expected Result:
Attach is successful.

B. Session Management
1. PDP Context Activation
a. PDP Context Activation, transparent mode, static IP address, GTP V1
Objective:
Check if the network can successfully handle the PDP context activation
procedure originated by normal subscriber with transparent mode and
static IP address.
Test Procedure:
¾ The MS is subscribed with a static IP address. The APN in use is
configured as transparent mode. GGSN mapped to the APN in use us
GTP V1.
¾ Power on the MS and the MS originates GPRS attach.
¾ The MS activates PDP context.
Expected Result:
PDP context activation is successful. The PDP activation messaging is
normal.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 34 of 177

MS RNC SGSN GGSN


Activate PDP Context Request

Create PDP Context Request

Create PDP Context Response

RAB Assignment Request

RAB Assignment Response

Activate PDP Context Accept

b. Multiple PDP contexts


Objective:
Check if the network can support multiple PDP contexts for subscriber.
Test Procedure:
¾ The MS is subscribed with 2 PDP contexts with different APNs. The APN
in use is configured as transparent mode. GGSN mapped to the APN in
use us GTP V1.
¾ Power on the MS and the MS originates GPRS attach.
¾ The MS activates PDP context with one of the APNs subscribed.
¾ Connect UE with PC, initiate another PDP context activation procedure
with the other APN subscribed, UE as mobile modem.
Expected Result:
Multiple PDP context activations are successful.
MS RNC SGSN GGSN

Activate PDP Context Request

Create PDP Context Request

Create PDP Context Response

RAB Assignment Request

RAB Assignment Response

Activate PDP Context Accept

Activate PDP Context Request

Create PDP Context Request

Create PDP Context Response

RAB Assignment Request

RAB Assignment Response

Activate PDP Context Accept

c. PDP activation reject due to unknown APN.


Objective:
Check if the network can successfully handle the PDP context activation
procedure originated by normal subscriber with unknown APN.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 35 of 177

Test Procedure:
¾ APN in use is subscribed to the MS but not mapped to any GGSN.
¾ Power on the MS and the MS originates GPRS attach.
¾ The MS activates PDP context with unknown APN.
Expected Result:
PDP context activation is rejected.
MS RNC SGSN

Activate PDP Context Request

Activate PDP Context Reject

Iu Release Command

Iu Release Complete

d. PDP activation reject due to service not subscribed.


Objective:
Check if the network can successfully handle the PDP context activation
procedure originated by normal subscriber with service not subscribed.
Test Procedure:
¾ APN in use is not subscribed to the.
¾ Power on the MS and the MS originates GPRS attach.
¾ The MS activates PDP context with APN not subscribed.
Expected Result:
PDP context activation is rejected.
2. PDP Context Deactivation
a. MS initiated PDP Context Deactivation
Objective:
Check if the network can successfully handle the PDP context deactivation
procedure originated by normal subscriber.
Test Procedure:
¾ Power on the MS and the MS originates GPRS attach.
¾ The MS activates PDP context.
¾ The MS deactivates the PDP context.
Expected Result:
PDP context deactivation is successful. The PDP activation messaging is
normal.
MS RNC SGSN GGSN
Deactivate PDP Context Request

Delete PDP Context Request

Delete PDP Context Response

Deactivate PDP Context Accept

RAB Assignment Request

RAB Assignment Response

b. GGSN initiated PDP Context Deactivation


Objective:
Check if the operator can successfully deactivate PDP context from GGSN.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 36 of 177

Test Procedure:
¾ Power on the MS and the MS originates GPRS attach.
¾ The MS activates PDP context.
¾ Deactivate PDP context from GGSN.
Expected Result:
PDP context deactivation from GGSN is successful.
c. SGSN initiated PDP Context Deactivation
Objective:
Check if the SGSN can successfully initiate PDP context deactivation.
Test Procedure:
¾ Power on the MS and the MS originates GPRS attach.
¾ The MS activates PDP context.
¾ Delete GPRS subscriber data from HLR.
Expected Result:
SGSN initiated PDP context deactivation is successful.

3. APN Selection Rule


a. APN selection rule, No APN in Activate PDP Context Request
Objective:
Check if the network can successfully select APN of PDP context when
there is no APN in Activate PDP Context Request.
Test Procedure:
¾ There is one and only one PDP context subscription for the MS in HLR.
¾ Power on the MS and the MS originates GPRS attach.
¾ The MS activates PDP context without APN in Activate PDP Context
Request.
¾ The MS deactivates the PDP context.
Expected Result:
SGSN selects APN according to PDP context subscription for the MS and
the selected APN is included in Create PDP Context Request sent to
GGSN. The MS activates PDP context successfully.

b. APN selection rule, Wild Card


Objective:
Check if the network can successfully select APN of PDP context when MS
subscribes a PDP context of wild card.
Test Procedure:
¾ There is one and only one PDP context subscription for the MS in HLR
and APN subscription is “*”.
¾ Power on the MS and the MS originates GPRS attach.
¾ The MS activates PDP context with specific APN in Activate PDP
Context Request. The APN in use is a valid APN that is mapped to
GGSN.
¾ The MS deactivates the PDP context.
Expected Result:
SGSN selects the APN included in the Activate PDP context Request sent
by the MS and the selected APN is included in Create PDP Context
Request sent to GGSN. The MS activates PDP context successfully.

c. APN selection rule, MS send APN, APN NI included


Objective:
Check if the network can successfully select APN of PDP context when
there is APN in Activate PDP Context Request, APN NI included.
Test Procedure:
¾ There is one and only one PDP context subscription for the MS in HLR
and APN subscription is not “*”.
¾ Power on the MS and the MS originates GPRS attach.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 37 of 177

¾ The MS activates PDP context with specific APN in Activate PDP


Context Request, APN NI included.
¾ The MS deactivates the PDP context.
Expected Result:
SGSN selects the APN included in the Activate PDP context Request sent
by the MS and the selected APN is included in Create PDP Context
Request sent to GGSN. The MS activates PDP context successfully.

d. APN selection rule, MS send APN in Mixed Case


Objective:
Check if the network can successfully select APN of PDP context when
there is APN in Activate PDP Context Request, APN in mixed case.
Test Procedure:
¾ There is one and only one PDP context subscription for the MS in HLR
and APN subscription is not “*”.
¾ Power on the MS and the MS originates GPRS attach.
¾ The MS activates PDP context with specific APN in Activate PDP
Context Request, APN in lower case, e.g. “test”.
¾ The MS deactivates the PDP context.
¾ The MS activates PDP context with specific APN in Activate PDP
Context Request, APN in upper case, e.g. “TEST”.
¾ The MS deactivates the PDP context.
¾ The MS activates PDP context with specific APN in Activate PDP
Context Request, APN in mixed case, e.g. “TeST”.
¾ The MS deactivates the PDP context.
Expected Result:
The MS activates PDP context successfully.

4. GGSN Address Resolution


a. GGSN address resolution by DNS
Objective:
Check if the network can resolve GGSN address by DNS.
Test Procedure:
¾ APN in use is mapped to GGSN address in DNS server.
¾ Clear DNS cache for the APN.
¾ Power on the MS and the MS originates GPRS attach.
¾ The MS activates PDP context.
Expected Result:
Message sequence is normal.
DNS
MS RNC SGSN GGSN
Server

Activate PDP Context Request

DNS Resolve Request

DNS Resolve Ack

Create PDP Context Request

Create PDP Context Response

RAB Assignment Request

RAB Assignment Response

Activate PDP Context Accept

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 38 of 177

C. Reliability and Stability


1. Interface and Link Redundancy
a. SGSN Gn interface Network Link Redundancy.
Objective:
Check if the SGSN Gn interface network link redundancy function is right.
Test Procedure:
¾ Check if all Gn interfaces are normal.
¾ Pull out one of the Ethernet cables of backup network ports of Gn
interface of SGSN.
¾ Check if Gn interface is normal.
¾ Plug in the Ethernet cable
Expected Result:
The network port recovers in a short time and GGSN status is normal.

b. SGSN Ga interface Network Link Redundancy.


Objective:
Check if the SGSN Ga interface network link redundancy function is right.
Test Procedure:
¾ Check if all Ga interfaces are normal.
¾ Pull out one of the Ethernet cables of backup network ports of Ga
interface of SGSN.
¾ Check if Gn interface is normal.
¾ Plug in the Ethernet cable
Expected Result:
The network port recovers in a short time and CG status is normal.

c. GGSN Gi interface Network Link Redundancy.


Objective:
Check if the GGSN Gi interface network link redundancy function is right.
Test Procedure:
¾ Power on the MS, and the MS originates GPRS attach.
¾ The MS activates PDP context and performs PS data service, such as
FTP download.
¾ Pull out one of the ethernet cables of backup network ports of Gi
interface of GGSN.
¾ Plug in the Ethernet cable.
Expected Result:
The data service continues when one of the Ethernet cables is pulled out.

d. E2E stability test


Objective:
Check the stability of E2E performance.
Test Procedure:
¾ Power on the MS, and the MS originates GPRS attach.
¾ The MS activates PDP context and performs PS data service
continuously for 5 minutes, e.g. Video Streaming.
¾ Check if there are alarms or faults monitored on the SGSN and GGSN,
etc.
Expected Result:
The data service performs successfully.

2. Transfer Rate
a. Uplink/downlink transfer rate.
Objective:
Check if the network can successfully handle the PDP context activation
procedure originated by Normal Subscriber with transparent mode and
static IP address.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 39 of 177

Test Procedure:
¾ Power on the MS, and the MS originates GPRS attach.
¾ Connect UE with PC, initiate PDP context activation procedure with PC,
UE as mobile modem.
¾ The MS performs PS data service mainly downlink, such as FTP
download, record the downlink bit rate with software installed in the
PC.
¾ The MS performs PS data service mainly unlink, such as FTP upload,
record the uplink bit rate with software installed in the PC.
Expected Result:
Uplink and downlink throughputs are measured and data service is
successful.

D. PS Domain Charging
1. M-CDR Generation
a. M-CDR Generation
Objective:
Check if the SGSN can successfully generate M-CDR and send it to CG
after MS GPRS detach.
Test Procedure:
¾ Power on the MS, and the MS originates GPRS attach.
¾ Power off the MS, and the MS originates GPRS detach.
Expected Result:
SGSN generates M-CDR and sends the CDR to CG.

SGSN CG

Data Record Transfer Request

Data Record Transfer Response

2. S-CDR Generation
a. S-CDR Generation
Objective:
Check if the SGSN can successfully generate S-CDR and send it to CG
after PDP deactivation.
Test Procedure:
¾ Power on the MS, and the MS originates GPRS attach.
¾ The MS activates PDP context.
¾ The MS deactivates PDP context.
Expected Result:
SGSN generates M-CDR and sends the CDR to CG.

3. S-SMO-CDR and S-SMT-CDR Generation


a. S-SMO-CDR and S-SMT-CDR Generation
Objective:
Check if the SGSN can successfully generate S-SMO-CDR and S-SMT-
CDR and send it to CG.
Test Procedure:
¾ Power on the MS, and the MS originates GPRS attach.
¾ The MS sends a PS SMS to itself..
¾ The MS deactivates PDP context.
Expected Result:
SGSN generates SMS-MO-CDR and SMS-MT-CDR and sends to CG.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 40 of 177

SGSN CG

Data Record Transfer Request

Data Record Transfer Response

Data Record Transfer Request

Data Record Transfer Response

4. G-CDR Generation
a. G-CDR Generation
Objective:
Check if the GGSN can successfully generate G-CDR and send it to CG
after PDP deactivation.
Test Procedure:
¾ Power on the MS, and the MS originates GPRS attach.
¾ The MS activates PDP context.
¾ The MS deactivates PDP context.
Expected Result:
GGSN generates G-CDR sends the CDR to CG.
GGSN CG

Data Record Transfer Request

Data Record Transfer Response

¾ The MS deactivates PDP context.


Expected Result:
GGSN generates G-CDR sends the CDR to CG.

E. CG
1. CDR Backup
a. CDR Backup
Objective:
Check if the CG can back up the CDR files to the local disk.
Test Procedure:
¾ Modify the configuration file of CG to back up final CDRs to a
destination directory of local disk.
¾ Restart CG to enable modification.
¾ After the CG backs up the final CDRs, browse the destination directory.
Expected Result:
Final CDRs are backed up to the destination directory configured.

2. CG Client Function
a. CG Client Function – User Management
Objective:
Check if the CG can add user, delete user, modify user’s attribute and
check user’s right.
Test Procedure:
¾ Input a non-existent account or the administrator account with wrong
password.
¾ Input correct password to log into the Client as an administrator.
¾ Add a new user account.
¾ Modify the new user’s attributes.
¾ Query the attributes of this account.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 41 of 177

¾ Delete the new user account.


¾ Log on again with the deleted account.
Expected Result:
CG can add user, delete user, modify user’s attribute and check user’s
right.

6.1.3 RAN Testing

For RAN testing, the tests are divided into 4 main parts:
• Bearer Capability Test
• Mobility Management
• Logical O&M
• Radio Resource Management and Control

A. Bearer Capability Test


1. Service Bearing CS Domain
a. AMR Speech Service (12.2K)
Objective:
Test the function of bearing AMR Speech service
Test Procedure:
¾ Set the parameters for 12.2K speech service on UL and DL.
¾ UE1 calls UE2
¾ UE2 rings and answers call. UE1 and UE2 start conversation.
Expected Result:
The call is normal and voice is legible.

b. AMR Speech Service (10.2K)


Objective:
Test the function of bearing AMR Speech service
Test Procedure:
¾ Set the parameters for 10.2K speech service on UL and DL.
¾ UE1 calls UE2
¾ UE2 rings and answers call. UE1 and UE2 start conversation.
Expected Result:
The call is normal and voice is legible.

c. AMR Speech Service (4.5K)


Objective:
Test the function of bearing AMR Speech service
Test Procedure:
¾ Set the parameters for 4.5K speech service on UL and DL.
¾ UE1 calls UE2
¾ UE2 rings and answers call. UE1 and UE2 start conversation.
Expected Result:
The call is normal and voice is legible.

d. CS Transparent Data Service


Objective:
Test the function of bearing CS transparent data service.
Test Procedure:
¾ UE1 calls UE2 by video call.
¾ UE2 answers the video call and holds the call for 2 minutes.
¾ Either UE1 or UE2 ends the video call.
Expected Result:
The video call on both UE1 and UE2 is normal. The video is clear and
the voice is audible.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 42 of 177

2. Service Bearing PS Domain


a. PS Data Service (uplink 64K + downlink 64K)
Objective:
Test the function of bearing PS data service (uplink 64K + downlink 64K)
Test Procedure:
¾ Set the maximum bit rate on the uplink and downlink to 64 Kbps.
¾ UE starts PS service.
¾ UE logs in to an FTP server in the Internet and uploads/downloads files
through the server.
¾ UE logs out to end the PS service after uploading or downloading.
Expected Result:
The UE can access the Internet and upload/download files normally.

b. PS Data Service (uplink 64K + downlink 384K)


Objective:
Test the function of bearing PS data service (uplink 64K + downlink 384K)
Test Procedure:
¾ Set the maximum bit rate on the uplink to 64 Kbps and downlink to 384
Kbps.
¾ UE starts PS service.
¾ UE logs out to end the PS service after uploading or downloading.
Expected Result:
The UE can access the Internet and upload/download files normally.

3. Combined Service Bearing


a. PS Data Service (uplink 64K + downlink 64K)
Objective:
Test the function of bearing 1 AMR speech service (uplink 12.2 Kbps +
downlink 12.2 Kbps) + 1 PS data service (uplink 64K + downlink 384K)
Test Procedure:
¾ Set the maximum bit rate on the uplink to 64 Kbps and downlink to 384
Kbps. Set the AMR speech to 12.2 Kbps.
¾ UE1 starts PS service.
¾ UE1 browses the Internet and downloads files.
¾ UE2 calls UE1.
¾ UE1 answers the call and starts conversation.
¾ Either UE1 or UE2 ends the conversation.
¾ UE logs out of the Internet to end the PS service after files have been
downloaded.
Expected Result:
The UE can access the Internet and download files normally. The
conversation between UE1 and UE2 is normal and clear.

b. 1 CS Transparent Data Service (uplink 64K + downlink 64K)


+ 1 PS Data Service (uplink 64K + downlink 144K)
Objective:
Test the function of bearing 1 CS transparent data service (uplink 64 Kbps
+ downlink 64 Kbps) + 1 PS data service (uplink 64K + downlink 144K)
Test Procedure:
¾ Set the maximum bit rate on the uplink to 64 Kbps and downlink to 144
Kbps.
¾ UE1 starts PS service.
¾ UE1 browses the Internet and downloads files.
¾ Set uplink/downlink 64 Kbps videophone of CS transparent data service
for UE.
¾ UE2 calls UE1 by video call.
¾ UE1 answers the video call and starts conversation.
¾ Either UE1 or UE2 ends the video call.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 43 of 177

¾ UE logs out of the Internet to end the PS service after files have been
downloaded.
Expected Result:
The UE can access the Internet and download files normally. The video
call between UE1 and UE2 is normal and clear.

4. SMS Service Bearing


a. SMS Service on CS Bearing
Objective:
Test the SMS Service on CS Bearing.
Test Procedure:
¾ On HLR, set UE1 and UE2 transmitting SMS service through MSC.
¾ UE1 composes a text message and sends it to UE2.
Expected Result:
UE1 sends the message successfully and UE2 receives the message
correctly.

b. SMS Service on PS Bearing


Objective:
Test the SMS Service on PS Bearing.
Test Procedure:
¾ On HLR, set UE1 and UE2 transmitting SMS service through SGSN.
¾ UE1 composes a text message and sends it to UE2.
Expected Result:
UE1 sends the message successfully and UE2 receives the message
correctly.

B. Mobility Management
1. Paging
a. Page UE in Idle Mode
Objective:
Test the function of page UE in idle mode.
Test Procedure:
¾ UE1 calls UE2
¾ UE2 rings and answers call. UE1 and UE2 start conversation.
Expected Result:
The UE2 rings after being called.

b. Page UE in CELL_DCH State


Objective:
Test the function of paging UE in CELL_DCH state
Test Procedure:
¾ UE1 logs in to the WWW server and browses on the internet.
¾ UE2 calls UE1
¾ UE1 rings and answers call. UE1 and UE2 start conversation.
Expected Result:
The UE1 rings during web browsing and after being called by UE2.

2. Soft Handover
a. AMR Speech Service Soft Handover
Objective:
Test the function of soft handover for AMR speech service.
Test Procedure:
¾ NodeB1 and NodeB2 are configured to handle two intra-frequency
neighboring cells, CELL1 and CELL2.
¾ UE1 camps on CELL1 in idle mode.
¾ UE1 calls UE2
¾ UE2 rings and answers call. UE1 and UE2 start conversation.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 44 of 177

¾ UE1 moves from CELL1 to CELL2 to trigger a soft handover.


Expected Result:
The conversation is still legible while UE1 is moving to CELL2.

UE NodeB2 RNC

RL Setup Req

RL Setup Rsp

Active Set Update

Active Set Update Complete

b. Video Telephone Service Soft Handover


Objective:
Test the function of soft handover for video telephone service.
Test Procedure:
¾ NodeB1 and NodeB2 are configured to handle two intra-frequency
neighboring cells, CELL1 and CELL2.
¾ UE1 camps on CELL1 in idle mode.
¾ UE2 camps on CELL1 in idle mode.
¾ UE1 starts video telephone and calls UE2.
¾ UE2 rings and answers call. UE1 and UE2 start conversation.
¾ UE1 moves from CELL1 to CELL2 to trigger a soft handover.
Expected Result:
The conversation is still legible and video is normal while UE1 is moving
to CELL2.

c. PS Service Soft Handover


Objective:
Test the function of soft handover for PS service.
Test Procedure:
¾ NodeB1 and NodeB2 are configured to handle two intra-frequency
neighboring cells, CELL1 and CELL2.
¾ UE camps on CELL1 in idle mode.
¾ UE visits the WWW server and surfs in the Internet.
¾ UE1 moves from CELL1 to CELL2 to trigger a soft handover.
Expected Result:
Surfing in the Internet is normal without interruption while UE1 is moving
to CELL2.

d. Combined Service Soft Handover


Objective:
Test the function of soft handover for CS and PS combined service.
Test Procedure:
¾ NodeB1 and NodeB2 are configured to handle two intra-frequency
neighboring cells, CELL1 and CELL2.
¾ UE1 camps on CELL1 in idle mode.
¾ UE1 visits the WWW server and surfs in the Internet.
¾ UE2 calls UE1.
¾ UE1 answers the call and starts conversation.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 45 of 177

¾ UE1 moves from CELL1 to CELL2 to trigger a soft handover.


Expected Result:
Surfing in the Internet is normal without interruption and the conversation
is legible while UE1 is moving to CELL2.

3. Hard Handover
a. Intra-Frequency Hard Handover

Objective:
Test the function of intra-frequency hard handover.
Test Procedure:
¾ NodeB1 and NodeB2 are configured to handle two intra-frequency
neighboring cells, CELL1 and CELL2.
¾ UE camps on CELL1 in idle mode.
¾ UE visits the WWW server and surfs in the Internet.
¾ UE moves from CELL1 to CELL2 to trigger an intra-frequency hard
handover.
Expected Result:
While UE is moving to CELL2, surfing in Internet keeps normal without
interruption.

UE NodeB1 NodeB2 RNC

RL Setup Req
RL Setup Rsp
Physical Channel Reconfiguration

Physical Channel Reconfiguration Complete


RL Del Req
RL Del Rsp

b. Speech Service Inter-Frequency Hard Handover


Objective:
Test the function of inter-frequency hard handover for AMR speech
service.
Test Procedure:
¾ NodeB1 and NodeB2 are configured to handle two inter-frequency
neighboring cells, CELL1 and CELL2.
¾ UE1 camps on CELL1 in idle mode.
¾ UE2 calls UE1.
¾ UE1 answers the call and start the conversation.
¾ UE moves from CELL1 to CELL2 to trigger an inter-frequency hard
handover.
Expected Result:
While UE is moving to CELL2, conversation is normal.

c. Video Telephone Inter-Frequency Hard Handover


Objective:
Test the function of inter-frequency hard handover for video telephone
service.
Test Procedure:
¾ NodeB1 and NodeB2 are configured to handle two inter-frequency
neighboring cells, CELL1 and CELL2.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 46 of 177

¾ UE1 camps on CELL1 in idle mode.


¾ UE2 camps on CELL2 in idle mode.
¾ UE1 starts video telephone and calls UE2.
¾ UE2 answers the video call and start the conversation.
¾ UE1 moves from CELL1 to CELL2 to trigger an inter-frequency hard
handover.
Expected Result:
While UE1 is moving to CELL2, conversation is normal and the picture is
clear.

d. PS Service Inter-Frequency Hard Handover


Objective:
Test the function of intra-frequency hard handover for PS service.
Test Procedure:
¾ NodeB1 and NodeB2 are configured to handle two intra-frequency
neighboring cells, CELL1 and CELL2.
¾ UE camps on CELL1 in idle mode.
¾ UE visits the WWW server and surfs in the Internet.
¾ UE moves from CELL1 to CELL2 to trigger an intra-frequency hard
handover.
Expected Result:
While UE is moving to CELL2, surfing in Internet keeps normal without
interruption.

e. Combined Service Inter-Frequency Hard Handover


Objective:
Test the function of intra-frequency hard handover for CS and PS service.
Test Procedure:
¾ NodeB1 and NodeB2 are configured to handle two intra-frequency
neighboring cells, CELL1 and CELL2.
¾ UE1 camps on CELL1 in idle mode.
¾ UE1 visits the WWW server and surfs in the Internet.
¾ UE2 calls UE1.
¾ UE1 answers call and start the conversation.
¾ UE moves from CELL1 to CELL2 to trigger an inter-frequency hard
handover.
Expected Result:
While UE is moving to CELL2, surfing in Internet keeps normal without
interruption and the voice conversation is legible.

4. Forward Handover
a. Cell Update Triggered by Cell Reselection
Objective:
Test the function of cell update triggered by cell reselection.
Test Procedure:
¾ NodeB1 is configured to handle two intra-frequency neighboring cells,
CELL1 and CELL2.
¾ UE camps on CELL1 in idle mode.
¾ UE logs in to the WWW server and browses the Internet.
¾ UE does not perform the data transmission for more than three minutes.
Then it transits from DCH to FACH state.
¾ UE moves from CELL1 to CELL2 to trigger a cell reselection, which
triggers a cell update.
¾ RNC sends the cell update acknowledge message to cell and the cell
update completes.
¾ UE logs out of the WWW server and returns to idle mode.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 47 of 177

Expected Result:
The uplink and downlink data transmission remains normal before and
after cell update.
UE UTRAN

CELL UPDATE

CELL UPDATE CONFIRM

C. Logical O&M
1. Logic Cell
a. Cell Setup
Objective:
Test the function of cell setup in Node B.
Test Procedure:
¾ Cell is deactivated.
¾ UE has no 3G signal and cannot originate a call
¾ Configure the cell.
¾ UE has 3G signal and can originate a call.
Expected Result:
The cell data was correctly configured.

b. Cell Reconfiguration
Objective:
Test the function of cell reconfiguration in Node B.
Test Procedure:
¾ Cell is configured.
¾ Reconfigure the cell. Modify the PCPICH power.
Expected Result:
The cell data was correctly reconfigured.

c. Cell Deletion
Objective:
Test the function of cell deletion in Node B.
Test Procedure:
¾ Cell is configured correctly in Node B.
¾ UE originates a call and the conversation is normal.
¾ Remove the cell.
Expected Result:
The cell data was deleted. The 3G signal disappeared and the call was
disconnected.

d. Cell Block
Objective:
Test the function of cell block.
Test Procedure:
¾ Cell is configured correctly in Node B.
¾ UE originates a call and the conversation is normal.
¾ Block the cell.
Expected Result:
The cell blocked and the call was disconnected.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 48 of 177

e. Cell Unblock
Objective:
Test the function of cell unblock.
Test Procedure:
¾ The cell has been blocked successfully.
¾ UE cannot originate a call.
¾ Unblock the cell
¾ UE originates a call and the conversation is normal.
Expected Result:
When the cell is unblocked, the UE can originate a call.

2. Common Transport Channel


a. Common Transport Channel Setup
Objective:
Test the function of common transport channel setup in Node B.
Test Procedure:
¾ Add the SCCPCH and FACH channels in the cell.
¾ Configure other parameters of the channels.
Expected Result:
The common transport channels were correctly configured.

b. Common Transport Channel Reconfiguration


Objective:
Test the function of common transport channel reconfiguration in Node B.
Test Procedure:
¾ Modify some parameters in SCCPCH and FACH channels.
¾ Check if the parameters were modified.
Expected Result:
The common transport channel parameters were correctly changed.

c. Common Transport Channel Reconfiguration


Objective:
Test the function of common transport channel deletion in Node B.
Test Procedure:
¾ Remove an SCCPCH common physical channel.
¾ Query the state of the SCCPH common physical channel.
Expected Result:
The SCCPH common transport channel was deleted.

3. System Information
a. System Information Update
Objective:
Test the function of system information update.
Test Procedure:
¾ The RNC request the Node B for the system update.
¾ Node B broadcasts the system information periodically on BCH.
Expected Result:
The Node B broadcasts the system information to RNC.

RNC NodeB

SYSTEM INFORMATION UPDATE REQUEST

SYSTEM INFORMATION UPDATE RESPONSE

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 49 of 177

4. Resource Audit
a. Cell Resource Audit
Objective:
Test the function of cell resource audit between RNC and Node B.
Test Procedure:
¾ Input the command for querying the resources of the cell.
Expected Result:
The data shows the resources of the cell.

RNC NodeB

AUDIT REQUEST

AUDIT RESPONSE

5. Tracing
a. Uu Interface Tracing
Objective:
Test the function of Uu interface tracing.
Test Procedure:
¾ Initiate a call and view the messages over the Uu interface.
Expected Result:
The trace messages from the Uu interface are seen.

b. Iub Interface Tracing


Objective:
Test the function of Iub interface tracing.
Test Procedure:
¾ Initiate a call and view the messages over the Iub interface.
Expected Result:
The trace messages from the Iub interface are seen.

c. Iu Interface Tracing
Objective:
Test the function of Iu interface tracing.
Test Procedure:
¾ Initiate a call and view the messages over the Iu interface.
Expected Result:
The trace messages from the Iu interface are seen.

d. Single User Tracing


Objective:
Test the function single user tracing.
Test Procedure:
¾ Initiate a call and view the messages of a single user.
Expected Result:
The trace messages from a single user is seen.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 50 of 177

D. Radio Resource Management and Control


1. Admission Control
a. CS Call Admission Control
Objective:
Test the function of CS call admission control.
Test Procedure:
¾ Node B is configured to handle CELL1.
¾ UE1, UE2, UE3, and UE4 camp on CELL1 and in idle state.
¾ Configure CELL1 to handle 2 calls.
¾ UE1 calls UE2 at a rate of 12.2 Kbps.
¾ UE3 calls UE4 at a rate of 12.2 Kbps.
¾ UE1 ends the call
Expected Result:
Only UE1 can connect, while UE3 cannot connect.

b. PS Call Admission Control


Objective:
Test the function of PS call admission control.
Test Procedure:
¾ Node B is configured to handle CELL1.
¾ UE1 and UE2 camp on CELL1 and in idle state.
¾ Configure CELL1 to handle 2 PS calls.
¾ UE1 activates PS UL/DL 64K services, logs in to the WWW server, and
browses on the internet.
¾ UE2 activates PS UL/DL 64K services, logs in to the WWW server, and
browses on the internet.
Expected Result:
Only UE1 can setup the PS call, while UE2 fails.

2. Congestion Control
a. Congestion Control
Objective:
Test the function of cell congestion control
Test Procedure:
¾ RNC is configured to handle Node B.
¾ Node B is configured to handle CELL1.
¾ UE camps on CELL1 in idle state.
¾ Set the QOS parameters in HLR: Uplink/Downlink Max bit rate to 64
Kbps.
¾ UE starts PS service and performs an FTP download.
¾ Monitor DL throughput and bandwidth.
¾ Trigger cell congestion by modifying the thresholds to a lower value.
Expected Result:
Throughput will decrease from 64 Kbps when congestion occurs.

3. Load Balancing Control


a. Intra-frequency Load Balancing Control
Objective:
Test the function of intra-frequency load balancing
Test Procedure:
¾ The Node B is configured with two cells: CELL1 and CELL2 which are
intra-frequency neighbor cells.
¾ Node B is configured to handle CELL1.
¾ UE1, UE2, and UE3 camps on CELL1 and are in idle state.
¾ UE1 calls UE2 to start an AMR speech service.
¾ UE3 logs in to a web Server and starts web browsing.
¾ UE1 and UE2 move to the edge of the cell.
¾ Change the DL load of CELL1 to simulate the heavy load state.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 51 of 177

¾ Observe the change of the pilot transmit power of CELL1


¾ Observe the process of handover from CELL1 to CELL2 of UE1 and
UE2.
Expected Result:
Observe the cell PCPICH pilot transmit power: RNC will decrease the cell
PCPICH pilot transmit power after the cell load is modified.
After the cell PCPICH pilot transmit power decreases, UE1 and UE2 at
the edge of CELL1 are handed over to CELL2.

4. Dynamic Resource Control


a. AMRC
Objective:
Test the function of AMRC.
Test Procedure:
¾ UE1 and UE2 are in idle state.
¾ Set the AMR voice rate range of UE1 on MSC to 12.2K.
¾ UE3 logs in to a web Server and starts web browsing.
¾ UE1 calls UE2
¾ UE2 answers call and starts the conversation.
¾ UE1 moves to the edge of the cell.
¾ UE1 ends the conversation.
Expected Result:
When UE1 moves to the edge of the cell, the data rate is adjusted to 4750
bits/s.

b. Dynamic Channel Configuration – Rate Adjustment


Objective:
Test the function of AMRC.
Test Procedure:
¾ Set the uplink/downlink max bit rate QOS parameter to 128 Kbps.
¾ UE starts the PS service (128K).
¾ UE logs in to an FTP server on the Internet to perform FTP service.
Both upload and download are normal. The bit rate increases from the
intermediate bit rate (full coverage bit rate) to the maximum bit rate.
¾ UE stops the FTP service. The bit rate decreases from the maximum
bit rate to the bit rate threshold
¾ UE restarts the FTP service. The bit rate increases to the maximum bit
rate.
¾ UE logs out of the FTP server and ends the PS service.
Expected Result:
The bit rate of the UE changes according to service situations and the
FTP service is normal.

c. Dynamic Channel Configuration – State Transition


Objective:
Test the state transition function of dynamic channel configuration.
Test Procedure:
¾ Set the uplink/downlink max bit rate QOS parameter to 128 Kbps.
¾ UE starts the PS service (128K).
¾ UE logs in to an FTP server on the Internet to perform FTP service.
Both upload and download are normal. The bit rate increases from the
intermediate bit rate (full coverage bit rate) to the maximum bit rate.
¾ UE stops the FTP service. The bit rate decreases from the maximum
bit rate to the bit rate threshold
¾ UE does not perform FTP service for a period greater than 180
seconds, the length of the timer for the transition from DCH to FACH.
Then, UE transits from DCH to FACH state.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 52 of 177

¾ UE does not perform the FTP service for another period (greater than
180 seconds, the length of the timer for the transition from FACH to
PCH). Then, UE transits from FACH to PCH state.
¾ When continuing to use the FTP service, UE transits from PCH to
FACH state and then from PCH to DCH state. The service is normal.
¾ UE logs out of the FTP server and ends the PS service.
Expected Result:
The UE transits from DCH to FACH to PCH, and vice versa.

UE NodeB RNC

RL Recfg Prep
RL Recfg Ready
RB Recfg
RL Recfg Commit
RB Recfg Complete

DCH TO DCH

UE NodeB RNC

RB Recfg

RB Recfg Complete
RL Del Req

RL Del Rsp

DCH TO FACH

UE RNC

RB Recfg

RB Recfg Complete

FACH TO PCH

5. Power Control
a. Uplink Outloop Power Control
Objective:
Test the function of uplink outloop power control.
Test Procedure:
¾ RNC is configured to handle Node B.
¾ Node B is configured to handle CELL1.
¾ UE1 and UE2 camps on CELL1 in idle mode.
¾ Outloop power control is enabled.
¾ UE1 calls UE2.
¾ UE2 answers call and starts the conversation.
¾ Monitor UE UL BLER and UL SIRTarget.
¾ UE moves in the cell. The radio link quality varies accordingly.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 53 of 177

¾ UE1 ends the conversation.


Expected Result:
The UL BLER value fluctuates based on the UL BLER target value. The
UL SIRtarget value increases when the UL BLER value is greater than the
UL BLER target value; decreases, when smaller.
b. Uplink Inner Loop Power Control
Objective:
Test the function of uplink inner loop power control.
Test Procedure:
¾ RNC is configured to handle Node B.
¾ Node B is configured to handle CELL1.
¾ UE1 and UE2 camps on CELL1 in idle mode.
¾ Outloop power control is enabled.
¾ UE1 calls UE2.
¾ UE2 answers call and starts the conversation.
¾ Monitor UE Transmit Power, UL SIR and UL SIRTarget at RNC side.
¾ Move UE away from Node B, and then towards Node B.
¾ UE1 ends the conversation.
Expected Result:
When UE moves away from Node B, UE transmit power increases and
the uplink SIR is approximate to the SIR Target.
When UE moves towards Node B, UE transmit power decreases and the
uplink SIR is approximate to the SIR Target.

c. Downlink Power Balancing


Objective:
Test the function of power balancing among DL radio link in soft handover.
Test Procedure:
¾ RNC is configured to handle two intra-frequency neighboring cells,
CELL1 and CELL2.
¾ UE camps on CELL1 in idle mode.
¾ Downlink power balancing is enabled.
¾ UE1 originates a call in CELL1 and remains in connected mode.
¾ UE moves from CELL1 to CELL2, which triggers soft handover, CELL2
is added into the active set.
¾ UE maintains connected to the two radio links.
Expected Result:
NodeB sends the measurement reports periodically. When the DL code
Tx power values of the two radio links exceed the high threshold, RNC
sends the DL power control command to NodeB.
The conversation is normal and the voice is clear.

6.1.4 Services Testing

For Services testing, the tests are divided into 3 main parts:
• Short Message Services (SMS)
• Multimedia Message Services (MMS)
• Video Call Services

NOTE: Some of the services may not be tested, depending on the 3G set-up of
the vendor. The procedure may vary for each vendor.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 54 of 177

A. Short Message Services (SMS)


1. Authenticating Subscriber
a. Authenticating the calling party
Objective:
Authenticating the calling party
Test Procedure:
¾ The SMC and the wireless system work normally.
¾ MS1 belongs to the SMC.
¾ MS2 has not been registered in the SMC.
¾ Send a short message from MS1 to MS3.
¾ Send a short message from MS2 to MS3.
¾ Observe and record the phenomenon.
Expected Result:
It is displayed on MS1 that the short message is submitted successfully.
It is displayed on MS2 that the short message is sent unsuccessfully

2. Accessing SMC
a. MS-to-MS SMS
Objective:
MS-to-MS SMS
Test Procedure:
¾ The SMC and the wireless system work normally.
¾ MS1 belongs to the SMC.
¾ MS2 belongs to the SMC.
¾ Enter the domestic MSISDN of MS2 on MS1.
¾ Send a short message to this MSISDN.
¾ Start the short message query function of the SMC MT console that
MS1 belongs to.
¾ Query the MT console for the short message sent from MS1.
Expected Result:
The following query result should be obtained.
MS1 sends a short message to MS2, and the sending time and
contents of the short message are consistent with the actual situation.

3. Submitting and Storing SMs


a. Submitting and storing MS-to-MS SMs
Objective:
Submitting and storing MS-to-MS short message.
Test Procedure:
¾ The SMC and the wireless system work normally.
¾ MS1 belongs to the SMC.
¾ MS2 belongs to the SMC.
¾ Send a short message from MS1 to MS2
¾ Start the short message query function of the SMC MT console that
MS1 belongs to.
¾ Query the short message sent from MS1.
Expected Result:
The following query result should be obtained.
MS1 sends a short message to MS2, and the sending time and
contents of the short message are consistent with the actual situation.
.
4. Forwarding SMs
a. Forwarding after receiving SM prompt
Objective:
Forwarding after receiving SM prompt.
Test Procedure:
¾ The SMC and the wireless system work normally.
¾ MS1 belongs to the SMC.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 55 of 177

¾ MS2 belongs to the SMC.


¾ Switch off MS2.
¾ Send a short message from MS1 to MS2 can be viewed.
¾ Switch on MS2.
¾ View MS2.
Expected Result:
The short message sent from the SMC to MS2 can be viewed.

b. Retrying forwarding SMs automatically


Objective:
Retrying forwarding SMs automatically.
Test Procedure:
¾ The SMC and the wireless system work normally.
¾ MS1 belongs to the SMC.
¾ MS2 belongs to the SMC.
¾ The automatic forwarding-retry function of the SMC has been set, and
the time is T1.
¾ Switch off MS2.
¾ Send a short message from MS1 to MS2.
¾ After waiting for T1, from the signalling monitor observe the signallings
sent from the SMC.
Expected Result:
It can be viewed that the SMC queries the MS2 status from the HLR
and retries forwarding the short message every T1.

5. Priority Processing
a. Sending SMs of high priority first.
Objective:
Sending SMs of high priority first.
Test Procedure:
¾ The SMC and the wireless system work normally.
¾ MS1 belongs to the SMC.
¾ MS2 belongs to the SMC.
¾ Switch off MS2.
¾ Send 3 short messages of low priority from the DEMO to MS2.
¾ Send a short message of high priority from the DEMO to MS2.
¾ Switch on MS2
¾ From the signalling monitor, observe the short message delivery
sequences from MS2.
Expected Result:
The short message of high priority is received first, then the short
message of low priority.

b. Forwarding SMs of high priority forcibly when MS is temporarily absent.


Objective:
Sending SMs of high priority high priority forcibly when MS is
temporarily absent.
Test Procedure:
¾ The SMC and the wireless system work normally.
¾ MS1 belongs to the SMC.
¾ MS2 belongs to the SMC.
¾ Switch off MS2.
¾ Send a short message of low priority from the DEMO to MS2.
¾ Send a short message of high priority from the DEMO to MS2.
Expected Result:
It can be seen that the SMC attempts to forward the short message of
high priority forcibly.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 56 of 177

6. Requesting Status Report


a. Status report-forwarding notification (successful forwarding).
Objective:
Status report-forwarding notification (successful forwarding).
Test Procedure:
¾ The SMC and the wireless system work normally.
¾ MS1 belongs to the SMC.
¾ MS2 belongs to the SMC.
¾ MS1 supports entering the attribute of request for the status report.
¾ Send a short message from MS1 to MS2, and set the attribute of
request for the status report as YES.
¾ Observe the information displayed on MS1.
Expected Result:
MS2 receives the short message sent from MS1.
MS1 receives the status report of the short message from the SMC,
that is, forwarding notification (successful forwarding).

b. Status report-unforwarding notification (permanent failure).


Objective:
Status report-unforwarding notification (permanent failure).
Test Procedure:
¾ The SMC and the wireless system work normally.
¾ MS1 belongs to the SMC.
¾ MS2 belongs to the SMC.
¾ MS1 supports entering the attribute of request for the status report.
¾ Close the short message service of MS2 in HLR.
¾ Send a short message from MS1 to MS2, and set the attribute of
request for the status report as YES.
¾ Observe the information displayed on MS1.
Expected Result:
MS1 receives the status report sent from the SMC, that is,
unforwarding notification (permanent failure).

7. Supporting SMs in English/Tagalog


a. Supporting SMs in English.
Objective:
Supporting SMs in English
Test Procedure:
¾ The SMC and the wireless system work normally.
¾ MS1 belongs to the SMC.
¾ MS2 belongs to the SMC.
¾ The SMC and the wireless system work normally.
¾ MS1 belongs to the MSC.
¾ MS2 belongs to the MSC.
Expected Result:
MS2 receives this short message.
The contents of this short message are displayed correctly.

b. Supporting SMs in Tagalog.


Objective:
Supporting SMs in Tagalog.
Test Procedure:
¾ The SMC and the wireless system work normally.
¾ MS1 belongs to the MSC.
¾ MS2 belongs to the MSC.
¾ Send a short message in Tagalog from MS1 to MS2.
¾ Observe the reception by MS2.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 57 of 177

Expected Result:
MS2 receives this short message.
The contents of this short message are displayed correctly.

c. Supporting SMs in both English and Tagalog.


Objective:
Supporting SMs in both English and Tagalog
Test Procedure:
¾ The SMC and the wireless system work normally.
¾ MS1 belongs to the SMC.
¾ MS2 belongs to the SMC and supports the display both in English and
Tagalog
¾ Send a short message in both English and Tagalog from MS1 to MS2.
¾ Observe the reception by MS2.
Expected Result:
MS2 receives this short message.
The contents of this short message are displayed correctly.

8. Supporting Long SMs


a. Supporting long SMs of over 140 bytes.
Objective:
Supporting long SMs of over 140 bytes or 160 ASCII characters (7-bit
code), 140 ASCII characters (8-bit code) or 70 dual-byte characters (16-
bit code).
Test Procedure:
¾ The SMC and the wireless system work normally.
¾ MS1 belongs to the SMC.
¾ MS2 belongs to the SMC.
¾ Send a long short message from the DEMO or MS1 supporting long
short message to MS2.
¾ Observe the reception by MS2.
Expected Result:
MS2 receives this short message.
The contents of this short message are displayed correctly

9. Maintenance and Test Function


a. Setting system parameters-setting country code.
Objective:
Setting system parameters-OCOS and TCOS setting.
Test Procedure:
¾ The SMC and the wireless system work normally.
¾ Log in to the MT console.
¾ Select the (System/System Parameter Setting) menu.
¾ Modify environment parameters (country code).
¾ Select Confirm and click <Refresh>.
Expected Result:
Modifying parameters succeeds.
The default values of OCOS and TCOS are consistent with the set
values.

b. Setting system parameters-modifying the deleting mode.


Objective:
Setting system parameters-modifying the deleting mode.
Test Procedure:
¾ The SMC and the wireless system work normally.
¾ Log in to the MT console.
¾ Select the (System/System Parameter Setting) menu.
¾ Select an item of wrong type, such as Absent Subscriber.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 58 of 177

¾ Click <Modify Deleting Mode> and modify the deleting mode.


¾ Click <OK>.

Expected Result:
Modifying parameters succeeds.
The modified deleting mode comes into effect.

c. System resource monitor-number of SMs.


Objective:
System resource monitor-number of SMs.
Test Procedure:
¾ The SMC and the wireless system work normally.
¾ Log in to the MT.
¾ Enter (Monitor/Test/System Resource Monitor).
¾ Select “Number of SMs”, ‘Number of SM entities”, “Number of
registered subscriber”, and then start monitor.
¾ Observe what is displayed in the window.
Expected Result:
The SM number monitoring function is provided normally.
The number of SMs, number of SM entities and number of registered
subscribers existing in the SMC are displayed in the window.

d. Querying SMs-querying SMs in the SME


Objective:
Querying SMs-querying SMs in the SME.
Test Procedure:
¾ The SMC and the wireless system work normally.
¾ Log in to the MT.
¾ Select the (Monitor/Test/SM Monitor) menu.
¾ Select the SM type (MO or MT). Set the time segment (start time and
end time) for observing.
¾ Observe what is displayed in the window.
Expected Result:
The short messages can be viewed.
The displayed short message attributes include the following: SM ID,
source address Type of Number (TON), source address Numbering
Plan Identification (NPI), destination address, SM priority, data coding
scheme (DCS), timing time, timeout time, expiry time, SM status, error
number, delivery times, message id, teleservice id, privacy, language
indicator, From MC Address, reference id, callback number, SM
Content, SMC.

e. Querying SMs-querying SMs in the memory


Objective:
Querying SMs-querying SMs in the memory.
Test Procedure:
¾ The SMC and the wireless system work normally.
¾ Log in to the MT.
¾ Select the (Monitor/Test/SM Monitor).
¾ Select the Query SM tab and select Query Memory.
¾ Enter the user number in the User ISDN No bar.
¾ Click <F3> or click <Query>.
¾ Observe what is displayed in the window.
Expected Result:
The short messages existing in the memory of the SMC can be viewed
The displayed short message attributes include the following: SM ID,
Service type, source address Type of Number (TON), source address,
Numbering Plan Identification (NPI), source address, destination

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 59 of 177

address TON, destination address NPI, destination address, address


type of MOMSC, MOMSC address, MTMSC address, address type of
SMC, SMC address, scheduling mode, SM priority, RD, SR, RP, UDHI,
Message Index, data coding scheme (DCS), timing time, timeout time,
expiry time, SM status, error number, delivery times, message id,
teleservice id, privacy, language indicator, From MC Address,
reference id, callback number, SM Content, SMC.

f. Querying SMs-querying SMs in the database


Objective:
Querying SMs-querying SMs in the database.
Test Procedure:
¾ The SMC and the wireless system work normally.
¾ Short messages exist in the database of the SMC.
¾ Log in to the MT.
¾ Select the (Monitor/Test/SM Monitor).
¾ Select the Query SM tab and select Query database.
¾ Enter the user number in the User ISDN No bar.
¾ Select Query time segment (no more than three months).
¾ Click <F3> or click <Query>.
¾ Observe what is displayed in the window.
Expected Result:
The short messages existing in the memory of the SMC can be viewed
The displayed short message attributes include the following: SM ID,
Service type, source address Type of Number (TON), source address,
Numbering Plan Identification (NPI), source address, destination
address TON, destination address NPI, destination address, address
type of MOMSC, MOMSC address, MTMSC address, address type of
SMC, SMC address, scheduling mode, SM priority, RD, SR, RP, UDHI,
Message Index, data coding scheme (DCS), timing time, timeout time,
expiry time, SM status, error number, delivery times, message id,
teleservice id, privacy, language indicator, From MC Address,
reference id, callback number, SM Content, SMC

g. Account Management
Objective:
Account Management.
Test Procedure:
¾ The SMC and the wireless system work normally.
¾ Enter the account administration window of the maintenance and test
console.
¾ Perform such operations as adding account deleting account numbers,
refreshing the displayed information.
¾ Observe what is displayed in the window.
Expected Result:
Various accounts, such as gateway account and service account, are
managed in a unified way through the account management function.
The MT console can successfully perform the operations above to
account numbers.

h. Interface Management
Objective:
Interface Management.
Test Procedure:
¾ The SMC and the wireless system work normally.
¾ Log in to the MT.
¾ Enter the account management window.
¾ Conduct the operations of adding and deleting intefaces.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 60 of 177

Expected Result:
Various interfaces, such as gateway interface, DEMO interface, MT
interface, are managed in a unified way through the interface
management function.
The user can conduct such interface management operations as
querying, adding, deleting, refreshing, confirming.

10. Database Module Functions


a. Database module function.
Objective:
Database module function
Test Procedure:
¾ The SMC and the wireless system work normally.
¾ The database runs normally.
¾ The database module file is configured correctly.
¾ Start the database module.
¾ Set the message route to the test tool RECV, log in to the account
RECV of the SMC, log in to the SMSC and receive short messages
¾ Send several short messages to the SMSC with the demo.
¾ Query the messages in the history database of the SMC.
Expected Result:
The database module is successfully connected with the history
database of the SMC.
The short messages delivered with success or permanent failure are
stored in the history database of the SMC through DBDaemon.
11. License Configuration
a. Reading legal license file.
Objective:
Reading legal license file.
Test Procedure:
¾ FTP the legal License.lic file to the SMSC computer.
¾ Start the active SMSC.
¾ Observe the current SMC running mode in (System/Browser License
SMC) on the SMC MT console.
¾ Submit the message using the test tool SubmitDemo and observe the
restrictions of SMC on all parameters of the message.
¾ Set the message route to the test tool RECV, log in to the account
RECV of the SMC, log in to the SMSC and receive short messages
Expected Result:
We observe from the SMC MT console that the SMC runs in the normal
mode.
All parameters in the common mode observed from the MT console
are consistent with those set in the license file.
The SMC controls the message submission based on parameters set in
the license file. If the value exceeds the set value, submitting the
message fails.

B. Multimedia Message Services (MMS)


1. Basic Service Flows
a. MMS UA to MMS UA in the Single MMSC (MM/DR/RR)
Objective:
To test whether MMS can be retrieved immediately if they are sent
from MMS terminal 1 to MMS terminal 2 via the same MMSC.
Test Procedure:
¾ The MMSC, WAP, GW, WCDMA network and wireless environment
work well.
¾ MMS terminals 1 and 2 are registered subscribers of the MMSC.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 61 of 177

¾ MMS terminal 1 has requested read report if the terminal support the
setting of read report. (Optional)
¾ MMS terminal 1 has requested delivery report.
¾ MMS terminal 2 has been set to get the MM instantly.
¾ Send an MM composed of text, voice and image from MMS terminal 1
to MMS terminal 2.
¾ Check the message status and related information in the MMSC.
Expected Result:
The MM reaches the MMSC successfully.
MMS terminal 2 can receive the MM successfully and display normally.
MMS terminal 2 can receive the prompt of red report request (Optional)
MMS terminal 1 can receive a delivery report showing that the MM has
been sent successfully.

b. MMS UA to Email (MM/DR)


Objective:
To test sending MMS from an MMS terminal to an Email address
through the MMSC.
Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless environment
work well.
¾ The Email gateway or Email server works well.
¾ MMS terminal 1 is a registered subscriber of the MMSC.
¾ MMS terminal 1 has enabled the function of requesting delivery report.
¾ MMS terminal 1 sends an MM composed of text, voice and image to an
Email account (for example, Yahoo Mailbox).
¾ Check the message status and related information in the MMSC.
¾ Check whether the message has been received and displayed normally
at the Email account.
Expected Result:
The MM reaches the MMSC successfully.
The MM can received and displayed normally at the Email client such
as outlook.
MMS terminal 1 can receive a delivery report showing that the MM has
been sent successfully.

c. Email to MMS UA (MM)


Objective:
To test sending MMS from an MMS terminal to an Email address
through the MMSC.
Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless environment
work well.
¾ The Email gateway or Email server works well.
¾ MMS terminal 1 is a registered subscriber of the MMSC.
¾ An email account (for example, Yahoo Mailbox) sends an MM
composed of text, voice and image to MMS terminal 1.
¾ Check the message status and related information in the MMSC.
¾ Check whether the message has been received and displayed normally
at MMS terminal 1.
Expected Result:
The MM reaches the MMSC successfully.
The MM can receive and displayed normally at the MMS terminal 1.

2. Basic Features
a. Multiple recipients
Objective:
To test sending MMS from MMS terminal 1 to MMS terminal 2, an

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 62 of 177

Email account, or an ICP application through the MMSC.


Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless environment
work well.
¾ The Email gateway and Email server work well.
¾ MMS terminals 1 and 2 are registered subscribers of the MMSC.
¾ MMS terminal 1 requests for delivery report.
¾ Send an MM composed of text and image from MMS terminal 1 to
Email account, and to MMS terminal 2.
¾ Check the message status and related information in the MMSC.
¾ Check whether the message has been received the MMS terminal 2,
and Email box.
Expected Result:
The MM reaches the MMSC successfully.
MMS terminal 2 can receive the MM successfully and display normally.
The MM can receive and displayed normally at the Email account.
MMS terminal 1 can receive two delivery reports, which respectively
indicate the delivery results of terminal 2 and the Email account.

b. Validity Period
Objective:
To test the correctness of the validity period setting.
Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless environment
work well.
¾ MMS terminals 1 and 2 are registered subscribers of the MMSC.
¾ MMS terminal 1 has enabled the function of requesting delivery report.
¾ Set the validity period to one hour or a shorter period like 1 minute.
¾ MMS terminal 2 is switched off.
¾ Send an MM composed of text and image from MMS terminal 1 to MMS
terminal 2.
¾ Check the message status and related information in the MMSC.
¾ MMS terminal 2 is switched on after the MM is expired. (For example 3
minutes)
Expected Result:
The MM reaches the MMSC successfully.
When the specified validity period reaches, the MMSC will delete MM
MMS terminal 2 is switched on after the specified validity period. When
retrieving the MM, it is prompted that the MM is outdated (expired).

c. Specify the Earliest deliver Time


Objective:
To test sending MMS from MMS terminal 1 and Application to MMS
terminal 2 through the MMSC at the specified time.
Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless environment
work well.
¾ MMS terminals 1 and 2 are registered subscribers of the MMSC.
¾ MMS terminal 1 has enabled the function of requesting delivery report.
¾ MMS terminal 2 has been set to get the MM instantly.
¾ Counting how many seconds for sending from MMS terminal 1 to MMS
terminal 2.
¾ Send an MM composed of text and image from MMS terminal 1 to MMS
terminal 2.
¾ Check the message status and related information in the MMSC.
Expected Result:
The MM reaches the MMSC successfully.
The MMSC delivers the MM less than 1 minute depending how big the

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 63 of 177

MM is.
MMS terminal 2 can receive the MM successfully and display normally.
MMS terminal 1 can receive a delivery report showing that the MM has
been delivered successfully.

d. Maximum Number of Receptions


Objective:
To test the function of checking the number of recipients
Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless environment
work well.
¾ MMS terminals 1, 2,3 and 4 are registered subscribers of the MMSC.
¾ The maximum number of supported recipients has been set to 2. If the
number reaches the specified value, the excessive recipients are
cancelled.
¾ The SP is a registered application of the MMSC.
¾ Send an MM from MMS terminal 1 to MMS terminals 2, 3 and 4
simultaneously.
¾ Send an MM from SP to MMS terminals 2, 3, 4, and 4 simultaneously
¾ Check the message status and related information in the MMSC.
Expected Result:
MMS terminal 1 sends the MMSC successfully.
SP sends the MM successfully.
MMS terminal 2, 3 receive the MM successfully.
MMS terminal 4 fails to receive the MM.

e. Auto provisioning and refreshing of subscriber


Objective:
To test the functions of updating the subscriber information in database
automatically and auto provisioning for new subscriber.
Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless environment
work well.
¾ MMS terminal 1 is a registered subscriber of the MMSC.
¾ MMS terminal 1 is defined as a non-MMS terminal in the subscriber
database.
¾ MMS terminal 2 belongs to this MMSC, but there is no related
information for it in database.
¾ Send an MM from MMS terminal 1 to MMS terminals 2, 3 and 4
simultaneously.
¾ Send an MM from mobile terminal 1 to mobile terminal 2.
¾ Observe whether the MM is sent successfully by mobile terminal 1 and
received by mobile terminal 2.
¾ Check whether the information of mobile terminal 1 has been refreshed
in the subscriber database, and whether the information of mobile
terminal 2 has been added.
¾ Delete the information of mobile terminal 1 from the subscriber
database. Then repeat steps 1-3.
Expected Result:
Mobile terminal 2 can receive the MM correctly.
The information of mobile terminals 1 and 2 has been refreshed in the
subscriber database. That is, the terminal type of mobile terminal 1 has
been changed to MMS terminal and the correct user agent value is set,
and the information of mobile terminal 2 has been added.

f. System-Level Blacklist
Objective:
To test whether the MMSC can deny MMS to or from the subscribers in

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 64 of 177

the system-level blacklist.


Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless environment
work well.
¾ MMS terminals 1 and 2 are registered subscribers of the MMSC.
¾ MMS terminal 1 has been listed in the system-level blacklist.
¾ Send an MM from MMS terminal 1 to MMS terminals 2.
¾ Check the message status in the MMSC.
¾ Send an MM from MMS terminal 2 to MMS terminal 1. Repeat step 2.
Expected Result:
The MMSC denies the MM sent to or from MMS terminal 1.

g. User-Level Blacklist
Objective:
To test whether the system supports the user-level blacklist.
Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless environment
work well.
¾ MMS terminals 1 and 2 are registered subscribers of the MMSC.
¾ MMS terminal 1 has been set as a subscriber in the user-level blacklist
by MMS terminal 2.
¾ Send an MM from MMS terminal 1 to MMS terminals 2.
¾ Check the message status in the MMSC.
Expected Result:
The MMSC rejects MMS terminal 1 sending the MM to MMS terminal 2.

h. Delivery Report, Terminal-to-Terminal


Objective:
To test whether the MMSC supports the terminal-to-terminal delivery
report.
Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless environment
work well.
¾ MMS terminals 1 and 2 are registered subscribers of the MMSC.
¾ Send an MM from MMS terminal 1 to MMS terminals 2.
¾ MMS terminal 2 has been set to get the MM instantly.
¾ MMS terminal 2 has been set to allow sending delivery report.
¾ MMS terminal 1 has enabled the function of requesting delivery report.
¾ Check the message status and related information in the MMSC.
¾ Set not to allow sending delivery report on MMS terminal 2. Repeat
steps 1 and 2.
Expected Result:
The MM reaches the MMSC successfully.
MMS terminal 2 can receive the MM successfully and display normally.
MMS terminal 1 receives or fails to receive a delivery report depending
upon the setting on MMS terminal 2.

i. Limit the MM message size at the MM1 interface.


Objective:
To test the function of limiting MM message size at the MM1 interface.
Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless environment
work well.
¾ MMS terminals 1 and 2 are registered subscribers of the MMSC.
¾ The allowed maximum size of the multimedia message has been set to
100 KB.
¾ Send an MM of 90 KB (less than 100 KB) from MMS terminal 1 to MMS
terminal 2.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 65 of 177

¾ Check the message status and related information in the MMSC.


¾ Send an MM of 105 KB (more than 100 KB) from MMS terminal 1 to
MMS terminal 2. Check the message status and related information in
the MMSC.
Expected Result:
For the MM less than the specified the maximum size, MMS terminal 2
can receive successfully, and display it normally.
For the MM greater than the specified the maximum size, the system
denies it and returns the failure response message.

j. Recipient number format


Objective:
To test the recipient number formats supported by the MMSC.
Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless environment
work well.
¾ MMS terminals 1 and 2 are registered subscribers of the MMSC.
¾ Send an MM from mobile terminal 1 to mobile terminal 2. The recipient
number is an 8-digit mobile phone number.
¾ Check the message status and related information in the MMSC.
¾ Set the reception number as “+852” plus an 8-digit mobile phone
number, and resend the MM.
Expected Result:
The MM reaches the MMSC successfully.
The MMSC can identify the three recipient number formats and deliver
a notification message to the recipient.
Mobile terminal 2 can receive the MM successfully and display it normally.

k. Traffic Control
Objective:
To test the traffic control function of the MMSC.
Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless environment
work well.
¾ MMS terminals 1 and 2 are registered subscribers of the MMSC.
¾ The maximum number of MMs processed in the MMSC is set to 3
pieces per second. The license of the MMSC is 3600 piece per hour.
¾ Use a simulation tool to submit numerous MMS to the MMSC. The
submission speed exceeds 5 pieces per second.
¾ Observe whether the MMS are submitted successfully.
Expected Result:
The MMSC rejects the MMS that are beyond its processing capability.
The MMSC rejects the MMS that are beyond the MMSC license.

l. Terminal-to-Terminal Performance
Objective:
To test the terminal-to-terminal performance.
Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless environment
work well.
¾ The MMS terminal simulators are registered subscribers of the MMSC.
¾ MMS terminal 2 is a registered subscriber of the MMSC.
¾ Set the number of MMS sent per second on mobile terminal simulator1.
¾ Send MMS from mobile terminal simulator 1 to mobile terminal 1
continuously for 15 times.
¾ Check the message status and related information in the MMSC.
¾ Through the keywords in the MMSC log, calculate the total number of
MMS. Through the start time in log, obtain the length of time needed

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 66 of 177

by the MMSC to send the MMS. Then calculate the average


processing capability of the system.
¾ Through the keywords in the MMSC log, calculate the MM success
ratio.
¾ Modify the number of MMS sent per second on mobile terminal
simulator 1.
Expected Result:
The MM reaches the MMSC successfully.
Mobile terminal 2 can receive the MMS successfully.

m. System Blacklist in MM3 interface.


Objective:
To test System Blacklist function at the MM3 interface.
Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless environment
work well.
¾ MMS terminal 1 is a subscriber of the local MMSC.
¾ Email account 1 is a valid account of Email Domain 1.
¾ Email account 2 is a valid account of Email Domain 2.
¾ Both Email accounts 1 and 2 can send and receive Email normally.
¾ The MM3 interface is configured to use blacklist, which contains Email
Domain 1.
¾ Email Domain 2 is not in the blacklist of MM3 interface.
¾ The Email account 1 sends an Email to MMS terminal 1.
¾ The Email account 2 sends an Email to MMS terminal 1.
Expected Result:
In step 8, the submission is failed.
In step 9, the submission is successful.

n. System Whitelist in MM3 interface.


Objective:
To test System Whitelist function at the MM3 interface.
Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless environment
work well.
¾ MMS terminal 1 is a registered subscriber of the local MMSC.
¾ Email domain 1 and 2 can send and receive Email normally.
¾ The MM3 interface is configured to use Whitelist, which contains the
Email Domain 1. The Email domain 2 is not in the Whitelist.
¾ The Email account 1 of Email Domain 1 sends an MM to MMS terminal
1.
¾ The Email account 2 of Email Domain 2 sends an MM to MMS terminal
1.
Expected Result:
In step 5, the Email account 1 sends the MM successfully.
In step 6, the Email account 2 sends the MM failed.

o. Limit the MM message size at the MM3 interface.


Objective:
To verify limiting the MM message size function at the MM3 interface.
Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless environment
work well.
¾ MMS terminal 1 is a subscriber of the local MMSC. The Email account
can send and receive Email normally.
¾ The system has been set to support the MM max size of 100 KB.
¾ The MM3 interface has been set to support the MM max size of 100 KB.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 67 of 177

¾ The Email account sends an MM to terminal 1, with the size of


attachments being no more than 100 KB.
¾ The Email account sends an MM to terminal 1, with the size of
attachments (including image, text, audio file and the other files with
unknown format) being more than 300 KB.
Expected Result:
In step 1, the Email account sends the MM successfully.
In step 2, the Email account sends the MM failed.

p. Service Deny for specified Number Segment.


Objective:
To test the services deny function for specified Number segment.
Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless environment
work well.
¾ MMS terminal 1 is a subscriber of the local MMSC.
¾ The number segment that terminal 2 belongs to has not been
configured on the MMSC.
¾ MMS terminal 1 sends an MM to MMS terminal 2.
Expected Result:
MMS terminal 1 submit the MM failed.

3. Operation and Maintenance


a. Maintenance of user account privilege.
Objective:
To test the function of maintaining the user account privilege.
Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless environment
work well.
¾ The customer management system is connected normally with the
database.
¾ Start the IE browser, enter the URL address of the Customer
Management System.
¾ Log in Customer Management System as super administrator.
¾ Create a new operator, and grant right of “VAS administrator” to the
new operator.
¾ Log out the Customer Management System, and log in Customer
Management System using the new operator;
¾ Check the privilege of the new created operator.
Expected Result:
The new created operator has only the right of maintaining value-added
services (VAS).

b. Maintenance of customer management system operators.


Objective:
To test the function of maintaining the customer management system
operators.
Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless environment
work well.
¾ The customer management system is connected normally with the
database.
¾ Start the IE browser, enter the URL address of the customer
management system, and then log in to the customer management
system.
¾ Enter the old password and new password to change the operator
password.
¾ Log in again, and check whether the new password has taken effect.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 68 of 177

¾ Add an operator. Then log in using the new operator name and
password, and check whether the settings have taken effect.
¾ Modify the descriptive information of an operator. Then query this
operator, and check whether the modification has taken effect.
¾ Delete an operator. Then log in using the operator name and password,
and check whether deletion has taken effect.
Expected Result:
After an operator’s password is changed, to log in to the system, the
operator must enter the new password.
Operators can be added, deleted and modified successfully, and these
operations can take effect in real time.

c. Maintenance of System-Level Blacklisted Subscriber


Objective:
To test whether the system-level blacklisted subscriber can be
managed and maintained through the customer management
system.
Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless environment
work well.
¾ The customer management system is connected normally with the
database.
¾ Start the IE browser, enter the URL address of the customer
management system, and then log in to the customer management
system.
¾ Add the subscriber to the system-level blacklist. When this
subscriber sends or receives an MM, check whether the setting has
taken effect.
¾ Query system-level blacklisted subscriber, and check whether the
database query results is correct
¾ Modify the descriptive information of a system-level blacklisted
subscriber. Then query and check whether the modification has
taken effect
¾ Remove a subscriber from the system-level blacklist. When this
subscriber sends or receives an MM, check whether the deletion
has taken effect.
Expected Result:
¾ After a subscriber is added to the system-level blacklist, the MMSC
will reject the MM send from or destined for the subscriber.
¾ When the system-level blacklisted subscribers are queried through
the customer management system, the query result is consistent
with the information in the database
¾ After the descriptive information of a system-level blacklisted
subscriber is modified and queried again, the displayed information
is correct.
¾ The de-blacklisted subscriber can send and receive MMs normally.

d. Maintenance of UA Profile
Objective:
To test whether the user agent profile can be managed and
maintained through the customer management system.
Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless
environment work well.
¾ The customer management system is connected normally with
the database.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 69 of 177

¾ Start the IE browser, enter the URL address of the customer


management system, and then log in to the customer
management system
¾ Add terminal type
¾ Query terminal type
¾ Delete terminal type
¾ Modify terminal type
Expected Result:
¾ After a terminal type is added to the User Agent Profile and
queried agent, the displayed information is correct
¾ After a terminal type is deleted from the User Agent Profile and
queried agent, the displayed information is correct.
¾ After the descriptive information of the terminal type is modified
and queried again, the displayed information is correct.

e. System Parameter Maintenance


Objective:
To test whether the system parameters can be maintained through
the customer management system.
Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless
environment work well.
¾ The customer management system is connected normally with
the database.
¾ Start the IE browser; enter the URL address of the customer
management system, and the log in to the customer
management system.
¾ Modify the parameters that can take effect in the real time, such
as address hiding.
¾ Send an MM to verify whether modified parameters have taken
effect.
Expected Result:
¾ The system parameters can be maintained through the
customer management system.
¾ After the parameters are modified, there is no need to restart
the system.
¾ The modified parameters have taken effect.

f. MMSC startup and shutdown


Objective:
To test whether MMS system is working completely
Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless
environment work well.
¾ The customer cannot send MM from MMSC terminal 1 to
MMSC terminal 2.
¾ Run “MMS status” command in the unix platform
¾ Run “MMS start” command in the unix platform
¾ Redo step 1
Expected Result:
¾ All MMS module are listed, and shown “not running”
¾ MMS module will start normally
¾ All MMS module are listed and shown “running”
¾ When all the MMS module are running, the customer can send
MM from MMSC terminal 1 to MMSC terminal 2 successfully.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 70 of 177

g. Restart process when killed


Objective:
The test whether the Module of the MMMSC will start
automatically when it killed.
Test Procedure:
¾ The MMSC, WAP GW, WCDMA network and wireless
environment work well.
¾ Customer can send MM from terminal MM1 to MM2.
¾ List all the MMS module with “MMS Status” command
¾ Kill one of the MMS module with “mms stop (id)” command
¾ Redo step 3
Expected Result:
¾ It shown the list of all MMS module in the unix platform
¾ Once you run mms stop command it will shown “it will shown
“Stop the module ….. Succeed”
¾ Then MMS module will start automatically.
¾ The MMS module work all running.

C. Streaming Services
1. Media Stream on Demand Service
a. Supporting the Flow of Media Streams Played on Demand
Objective:
To verify that the video server supports the media streams played on
demand
Test Procedure:
¾ WCDMA 3G network work normally.
¾ Video server works normally.
¾ CP-related devices work normally, and they have published contents to
the video server network.
¾ The subscriber accesses the streaming service portal website.
¾ On the streaming service web page, select the contents to be played.
¾ Observe the status of the service being played on the test terminal.
Expected Result:
The subscriber can access the streaming service portal website. The
subscriber can select desired contents on the streaming service web page
normally. After the subscriber selects the contents, the test terminal can
establish connection with the streaming server correctly. The media
streams play normally.

b. Supporting to Pause the Streams Being Played on Demand


Objective:
To verify that the video server supports to pause the streams being
played on demand
Test Procedure:
¾ WCDMA 3G network work normally.
¾ Video server works normally.
¾ CP-related devices work normally, and they have published contents to
the video server network.
¾ The subscriber accesses the streaming service portal website.
¾ On the streaming service web page, select the contents to be played.
¾ Pause the contents being played.
¾ Replay the selected contents.
¾ Observe the status of the service being played on the test terminal.
Expected Result:
The subscriber can access the streaming service portal website normally.
The subscriber can select desired contents on the streaming service web
page normally. After the subscriber selects the contents to be played, the

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 71 of 177

test terminal can establish connection with the streaming server correctly.
The media streams are played normally. After the pause, the subscriber
replays the contents again, and the server should resume the playing
from where the contents were paused.

c. Supporting to Interrupt the Streams Media Being Played on Demand

Objective:
To verify that the video server supports to interrupt the streaming service.
Test Procedure:
¾ WCDMA 3G network work normally.
¾ Video server works normally.
¾ CP-related devices work normally, and they have published contents to
the video server network.
¾ The subscriber accesses the streaming service portal website.
¾ On the streaming service web page, select the contents to be played.
¾ Stop the contents being played.
Expected Result:
The subscriber accesses the streaming service portal website normally.
After the subscriber selects the contents to be played, the test terminal
can establish connection with the streaming server correctly. The media
streams are played normally. Once the subscriber selects to stop, the
media streams should stop being played to the subscriber. If press to
play again, the media streams will be played from the beginning.

d. Supporting to Perform Forward Query and Backward Query Operations on


the Media Stream Being Played on Demand
Objective:
To verify that the video server supports the forward query and backward
query operations on the streaming service.
Test Procedure:
¾ WCDMA 3G network work normally.
¾ Video server works normally.
¾ CP-related devices work normally, and they have published contents to
the video server network.
¾ The subscriber accesses the streaming service portal website.
¾ On the streaming service web page, select the contents to be played.
¾ During the play, the subscriber performs the forward query and
backward query operations from time to time.
Expected Result:
After performing the forward/backward seek operation, the media
contents can be played normally.

e. Supporting to Play Streams on Demand Continuously


Objective:
To verify that the video server supports to play streams on demand
continuously for a long time.
Test Procedure:
¾ WCDMA 3G network work normally.
¾ Video server works normally.
¾ CP-related devices work normally, and they have published contents to
the video server network.
¾ The subscriber accesses the streaming service portal website through
the WAP service platform.
¾ On the streaming service web page, select the contents to be played.
¾ Keep playing at 5 minutes.
¾ Observe the status of the service being played on the test terminal.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 72 of 177

Expected Result:
The subscriber can access the streaming service portal website through
the WAP service platform normally. The subscriber can select desired
contents on the streaming service web page normally. After the
subscriber selects the contents, the test terminal can establish connection
with the streaming server correctly.

2. Live Streaming Service


a. Supporting the Live Streaming Service Flow
Objective:
To verify that the video server supports live streaming service.
Test Procedure:
¾ WCDMA 3G network work normally.
¾ Video server works normally.
¾ CP-related devices work normally, and they have published contents to
the video server network.
¾ The subscriber accesses the streaming service portal website.
¾ On the streaming service web page, select the live programs to be
played.
¾ Observe the status of the service being played on the test terminal.
Expected Result:
The subscriber can access the streaming service portal website normally.
The subscriber can select desired live programs on the media stream
service web page normally. After the subscriber selects the live programs
to be played, the test terminal can establish connection with the streaming
server correctly. The media streams are played normally.

b. Supporting to Pause/Stop and Continue the Live Streaming Service


(Depends on the handset)
Objective:
To verify that the video server supports to pause/stop the live streaming
service being played.
Test Procedure:
¾ WCDMA 3G network work normally.
¾ Video server works normally.
¾ CP-related devices work normally, and they have published contents to
the video server network.
¾ The subscriber accesses the streaming service portal website.
¾ On the streaming service web page, select the live programs to be
played.
¾ During the play, press PAUSE to pause the contents being played.
¾ Replay the selected contents.
¾ Observe the status of the service being played on the test terminal.
Expected Result:
The subscriber can access the streaming service portal website normally.
The subscriber can select desired contents on the streaming service web
page normally. After the subscriber selects the live programs to be
played, the test terminal can establish connection with the streaming
server correctly. The media streams are played normally, and the
contents are paused/stopped after pressing PAUSE/STOP. After the
pause/stop, the subscriber reselects the live programs to replay it, and the
server should play the contents currently published by the live program
source.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 73 of 177

c. Supporting to Receive Multiple Live Streams from the Encoder


Objective:
To verify that the video server supports to receive multiple live streams
from the encoder.
Test Procedure:
¾ WCDMA 3G network work normally.
¾ Video server works normally.
¾ CP-related devices work normally, and they have published contents to
the video server network.
¾ The subscriber accesses the streaming service portal website.
¾ On the streaming service web page, select the live programs to be
played by the encoder.
¾ Repeat the above selections several times.
¾ The media streams are played normally at the test terminal.
Expected Result:
The subscriber can access the streaming service portal website normally.
The subscriber can select desired contents on the streaming service web
page normally. After the subscriber selects the live programs to be
played, the test terminal can establish connection with the streaming
server correctly. The media streams are played normally, and the
contents are paused/stopped after pressing PAUSE/STOP. After the
pause/stop, the subscriber reselects the live programs to replay it, and the
server should play the contents currently published by the live program
source.

d. Supporting to Play Live Streams Continuously


Objective:
To verify that the video server supports to play live streams continuously.
Test Procedure:
¾ WCDMA 3G network work normally.
¾ Video server works normally.
¾ CP-related devices work normally, and they have published contents to
the video server network.
¾ The subscriber accesses the streaming service portal website.
¾ On the streaming service web page, select the live programs to be
played.
¾ Keep playing at least 5 minutes.
¾ Observe the status of the service being played on the test terminal.
Expected Result:
The subscriber can access the streaming service portal website normally.
The subscriber can select desired contents on the streaming service web
page normally. After the subscriber selects the live programs to be
played, the test terminal can establish connection with the streaming
server correctly. The media streams are still played normally after 5
minutes.

3. Supporting Encoding
a. Supporting File Format of 3gp/mp4
Objective:
To verify that the video server supports play in 3gp/mp4 file format.
Test Procedure:
¾ WCDMA 3G network work normally.
¾ Video server works normally.
¾ CP-related devices work normally, and they have published contents to
the video server network.
¾ The subscriber accesses the streaming service portal website.
¾ On the streaming service web page, select to play the media files in the
.3gp and .mp4 formats.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 74 of 177

¾ Observe the status of the service being played on the test terminal.
Expected Result:
The subscriber can access the streaming service portal website normally.
The subscriber can select desired contents on the media stream service
web page normally. After the subscriber selects the live programs to be
played, the test terminal can establish connection with the streaming
server correctly. The media stream files in different formats are played
normally.

b. Supporting Video Encoding Format of H.263/MPEG-4


Objective:
To verify that the video server supports H.263/MPEG-4 video encoding
format.
Test Procedure:
¾ WCDMA 3G network work normally.
¾ Video server works normally.
¾ CP-related devices work normally, and they have published contents to
the video server network.
¾ The subscriber accesses the streaming service portal website.
¾ On the streaming service web page, select to play the desired contents.
¾ Observe the status of the service being played on the test terminal.
Expected Result:
The subscriber can access the streaming service portal website normally.
The subscriber can select desired contents on the media stream service
web page normally. After the subscriber selects the live programs to be
played, the test terminal can establish connection with the streaming
server correctly. The media stream files in different formats are played
normally.

c. Supporting Audio Encoding Format of AMR-NB/AAC-LC


Objective:
To verify that the video server supports AMR-NB/AAC-LC audio encoding
format.
Test Procedure:
¾ WCDMA 3G network work normally.
¾ Video server works normally.
¾ CP-related devices work normally, and they have published contents to
the video server network.
¾ The subscriber accesses the streaming service portal website.
¾ On the streaming service web page, select to play the desired contents.
¾ Observe the status of the service being played on the test terminal.
Expected Result:
The subscriber can access the streaming service portal website normally.
The subscriber can select desired contents on the media stream service
web page normally. After the subscriber selects the live programs to be
played, the test terminal can establish connection with the streaming
server correctly. The media stream files in different formats are played
normally.

d. Supporting Conversion Between Multiple Media File Formats (avi, mpg,


mp3) – Live Stream Encoding
Objective:
To verify that the video server supports conversion of multiple media file
formats.
Test Procedure:
¾ WCDMA 3G network work normally.
¾ Video server works normally.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 75 of 177

¾ CP-related devices work normally, and they have published contents to


the video server network.
¾ The streaming encoder server converts media files into the media
streams playable at the test terminal, and the media file format can be
AVI, MPG.
¾ On the streaming service web page, select to play the desired contents.
¾ Observe the status of the service being played on the test terminal.
Expected Result:
The subscriber can play the media streams normally.

e. Supporting Export Type in File Format of 3GP


Objective:
To verify that the video server supports export type in 3GP file format.
Test Procedure:
¾ WCDMA 3G network work normally.
¾ The TV program collection and encoding systems work normally; the
video server network works normally.
¾ CP-related devices work normally, and they have published contents to
the video server network.
¾ The streaming encoder server converts the signals from the live
program source into the media streams playable at the test terminal,
and the export type is 3GP/MP4.
¾ On the streaming service web page, select to play the live contents.
¾ Observe the status of the service being played on the test terminal.
Expected Result:
The test terminal can play the media streams normally.

f. Supporting Output of Audio Only/Video Only


Objective:
To verify that the video server supports output of audio only/video only.
Test Procedure:
¾ WCDMA 3G network work normally.
¾ The TV program collection and encoding systems work normally; the
video server network works normally.
¾ CP-related devices work normally, and they have published contents to
the video server network.
¾ The subscriber accesses the streaming service portal website.
¾ The streaming encoder server converts the signals from the live
program source into the media streams playable at the test terminal,
and the output file format is 3GP/MP4
¾ Select “Audio only” or “Video Only”.
¾ On the streaming service web page, select to play the live contents.
¾ Observe the status of the service being played on the test terminal.
Expected Result:
The test terminal can play the media streams normally.

g. Supporting Multiple Video Encoding Format (MPEG-4, H.263)


Objective:
To verify that the video server supports multiple video encoding formats
Test Procedure:
¾ WCDMA 3G network work normally.
¾ The TV program collection and encoding systems work normally; the
video server network works normally.
¾ CP-related devices work normally, and they have published contents to
the video server network.
¾ The subscriber accesses the streaming service portal website.
¾ The streaming encoder server converts the signals from the live
program source into the media streams playable at the test terminal.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 76 of 177

¾ Select different video input encoding formats (MPEG-4, H.263).


¾ On the streaming service web page, select to play the live contents.
¾ Observe the status of the service being played on the test terminal.
Expected Result:
The test terminal can play the media streams normally.

4. Content Management Function


a. Supporting to Published On-Demand Media Files to Video servers

Objective:
To verify the function of publishing on-demand media files to Video
servers
Test Procedure:
¾ WCDMA 3G network work normally.
¾ Video server network works normally.
¾ CP-related devices work normally.
¾ The collection and encoding devices work normally, and they can
publish contents directly to the video server network in a brief flow.
¾ Streaming servers work normally.
¾ The CP operator logs in to Portal, enters the Content Management main
tab, and selects the published on-demand media service category.
¾ In the Release On-demand Content tab, input the general attribute
parameter values of the related contents to be published (For
example, content name, director, content description, content length),
and fill out the correct distribution control options and content URL.
¾ The CP operator fills out the distribution parameters in a normal
procedure.
¾ Set the current system time as the published time, and submit the
distribution request.
Expected Result:
On-demand media files can be published on the video server and the
subscriber can play the published media files.

b. Supporting to Published Live Contents


Objective:
To verify the function of publishing on-demand media files to Video
servers
Test Procedure:
¾ WCDMA 3G network work normally.
¾ Video server network works normally.
¾ CP-related devices work normally.
¾ The collection and encoding devices work normally, and they can
publish contents directly to the video server network in a brief flow.
¾ Streaming servers work normally.
¾ The subscriber logs in as a CP operator, and accesses the Portal main
tab.
¾ Access the interface of publishing contents.
¾ Input all items correctly in the content published interface.
¾ Submit the published contents.
Expected Result:
Live media files can be published on the video server. During play of live
programs, the mobile test terminal subscriber can watch the live
programs.

c. Supporting to Censor Contents


Objective:
To verify that the video server supports to censor the contents

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 77 of 177

Test Procedure:
¾ WCDMA 3G network work normally.
¾ Video server network works normally.
¾ The test terminal is registered as certified subscriber of streaming
service.
¾ CP-related devices work normally.
¾ The collection and encoding devices work normally, and they have
published contents to the video server network.
¾ The CP operator fills out the distribution parameters in a normal
procedure and then submits the distribution request.
¾ The contents are distributed successfully.
¾ Log to the system and censor one of the published contents.
¾ Check the status of the published content.
¾ Approve the censored content.

Expected Result:
Subscriber cannot play the files which are censored.

d. Supporting to Delete Media File on the Streaming Server


Objective:
To verify that the video server supports to delete the media file on the
streaming server.
Test Procedure:
¾ WCDMA 3G network work normally.
¾ Video server network works normally.
¾ The test terminal is registered as certified subscriber of streaming
service.
¾ CP-related devices work normally, and can publish contents directly to
the video server network in a brief flow.
¾ The CP operator can publish media contents to the video server
network.
¾ Log in to the portal and delete one of the content.
Expected Result:
The deleted content cannot be viewed.

e. Supporting to Delete Live Content Files


Objective:
To verify that the video server supports deletion of live content files.
Test Procedure:
¾ WCDMA 3G network works normally.
¾ The collection and encoding devices can work normally.
¾ The CP can publish contents directly to the video server network in a
brief flow.
¾ The CP operator has published the live contents.
¾ Log in to the portal and delete one of the live contents.
Expected Result:
The deleted live content cannot be viewed.

5. CP Management Function
a. Supporting Multiple Level Operators Function
Objective:
To verify the video server supports multiple level operators
Test Procedure:
¾ The CP portal can support several level accounts like System
administrator, etc.
¾ Create/delete/modify different level accounts.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 78 of 177

Expected Result:
Each operation is successful and each account can log into the Portal.
Each level account info can be modified.

b. Managing (Adding/Deleting/Suspending/Resuming) CP Account


Objective:
To verify the video server supports management of the CP account.
Test Procedure:
¾ The video server network works normally.
¾ Log in to the portal interface and register a group of CPs and the CP
administrator for each CP.
¾ Select a CP, and perform the deletion function.
¾ Select a CP, and perform the pause function.
¾ Select the suspended CP, and perform the resume function.
Expected Result:
Can log in to portal and publish and manage the contents after adding the
CP. Cannot log in to the portal after deleting the CP. Cannot login to the
portal after pausing the CP. Can log in to the portal after resuming the
CP.

6. Security Management Function


a. Supporting User Management (Adding/Deleting/Modify)
Objective:
To verify the video server supports User registration functions.
Test Procedure:
¾ Video server network works normally.
¾ Log in to the OMC interface.
¾ Add details for a user like user name, login name and password for
login. Add other details and register the user.
¾ Check that the user has been added.
¾ Delete a use.
¾ Modify a user.
Expected Result:
Deleted user cannot log in to the OMC. Added user can log in to the
OMC.

7. System Maintenance
a. Supporting Application Startup/Stop
Objective:
To verify the video server supports startup/stop applications.
Test Procedure:
¾ Turn on the computer.
¾ Display all the services.
¾ Observe the status of the application running.
¾ Start the application.
¾ Stop the application.
Expected Result:
The application is started or stopped.

b. Supporting Database Startup/Stop


Objective:
To verify the video server supports startup/stop Database.
Test Procedure:
¾ Video server network works normally.
¾ Turn on the computer.
¾ Display all the services.
¾ Observe the status of the Database running.
¾ Start the application.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 79 of 177

¾ Stop the application.


Expected Result:
The database is started or stopped.

c. Supporting Configuration Backup and Restore


Objective:
To verify the video server supports configuration backup and restore.
Test Procedure:
¾ Video server network works normally.
¾ Log in to the system.
¾ Backup/restore all the necessary configuration files.

Expected Result:
The backup files will exist in backup directory.

d. Supporting Database Backup and Restore


Objective:
To verify the video server supports Database backup and restore.
Test Procedure:
¾ Video server network works normally.
¾ Log in to the system.
¾ Backup/restore all the Database.
Expected Result:
The Database backup files will exist in backup directory. The Database is
restored.

8. Supporting Billing Function


a. Supporting Generating CDR
Objective:
To verify that the CDR file can be generated.
Test Procedure:
¾ WCDMA 3G network works normally.
¾ Video server network works normally.
¾ The test terminal is registered as certified subscriber of streaming
service.
¾ CP-related devices work normally, and they have published contents to
the video server network.
¾ The subscriber accesses the media stream contents website.
¾ Select a content to be played.
¾ Play the selected media stream content completely.
¾ Select the other media stream content to be played.
¾ After playing the content for five seconds, the subscriber stops play.
¾ View the CDR information generated at the streaming service platform.
Expected Result:
The CDR information for both the content completely played and the
content partially played is correct. For the content the subscriber stops
viewing, the CDR includes the following information as a minimum
request: duration of played content, data traffic played, start time and end
time of the content played on demand, filename of the played file, flag
which indicates completion type.

b. Supporting Generating CDR for Aborted Play


Objective:
Supporting the billing function in case of aborted play.
Test Procedure:
¾ WCDMA 3G network works normally.
¾ Video server network works normally.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 80 of 177

¾ The test terminal is registered as certified subscriber of WAP service


and streaming service.
¾ CP-related devices work normally, and they have published contents to
the video server network.
¾ The subscriber accesses the media stream contents website.
¾ Select a content to be played.
¾ During the play, the subscriber ends the streaming, e.g. the signals of
the MS are lost, pull out the battery, out of service, answers a phone
call, handsets failed.
¾ View the CDR information generated at the streaming service platform.
Expected Result:
The CDR information generated after the user ends the streaming. The
CDR generated when the streaming connection is abnormally cut off,
includes the following information as a minimum request: duration of
played content, data traffic played, no flag indicates normal completion of
play, start time and end time of the content played on demand, file name
of the played file.
6.1.5 HSDPA Testing

For HSDPA testing, the tests are divided into 13 main parts:
• RAB mapping
• Power Management
• Code management
• Mobility
• Load management
• Iub flow control
• State switch
• RTT
• Hardware capacity
• Throughput capacity
• System reliability
• Iub standard interface
• Configuration

A. RAB mapping
1. HSDPA Cell R99 UE Call Establishment – DCH-PS
Objective:
To verify that HSDPA Cell UE R99 PS Call establishment
Test Procedure:
¾ WCDMA system is in normal operation.
¾ The HSDPA cell is set up.
¾ UE support R99 and is in idle mode.
¾ UE starts PS service.
¾ UE logs in to an FTP server in the Internet and uploads/downloads files
through the Server.
¾ UE logs out to end the PS service after uploading or downloading.
Expected Result:
UE can access the Internet and can upload/download files normally.

2. HSDPA Cell R99 UE Call Establishment – DCH-CS


Objective:
To verify that HSDPA Cell UE R99 CS Call establishment
Test Procedure:
¾ WCDMA system is in normal operation.
¾ The HSDPA cell is set up.
¾ UE1 and UE2 support R99 and are in idle mode.
¾ UE1 calls UE2.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 81 of 177

¾ UE2 rings and answers call. UE1 and UE2 start conversation.
¾ Either UE1 or UE2 hooks up to end the conversation.
Expected Result:
The call is normal. The voice is legible.

3. HSDPA Cell HSDPA UE Call Establishment – Emergency


Objective:
To verify that HSDPA Cell UE Emergency Call establishment
Test Procedure:
¾ WCDMA system is in normal operation.
¾ The HSDPA cell is set up.
¾ The MSC Server is configured to route emergency call to police or to a
PSTN user.
¾ The UE should support to establish an SOS call.
¾ Insert USIM card into mobile phone, and power on.
¾ UE initiates an emergency call, e.g. call 112.
¾ The emergency call is connected to PSTN.
¾ Check the Iu interface message.
Expected Result:
The UE location is successful. The emergency call can be established
successfully. UE and PSTN can talk with each other. The RAB
assignment message indicates that it is an emergency call.

4. HSDPA Cell HSDPA UE Call Establishment – SMS


Objective:
To verify that HSDPA Cell UE SMS service.
Test Procedure:
¾ WCDMA system is in normal operation.
¾ The HSDPA cell is set up.
¾ UE1 and UE2 support R99 and are in idle mode.
¾ On HLR, set UE1 and UE2 transmitting SMS service through MSC.
¾ UE1 composes a text message and send it to UE2.
¾ UE2 receives the short message.
Expected Result:
UE1 sends the message successfully. UE2 receives the message
correctly.

5. HSDPA Cell HSDPA UE Call Establishment – H-PS


Objective:
To verify that HSDPA Cell UE HSDPA PS Call Establishment.
Test Procedure:
¾ WCDMA system is in normal operation.
¾ The HSDPA cell is set up.
¾ UE support HSDPA and is in idle mode.
¾ UE starts HSDPA PS service.
¾ UE logs in to an FTP server in the Internet and uploads/downloads files
through the Server.
¾ UE logs out to the end the HSDPA PS service after uploading or
downloading.
Expected Result:
UE can access the Internet and upload/download files normally.

6. HSDPA To MultiService-Multiservice: AMR+HSDPA-PS


Objective:
To verify that the system support CS+HSDPA PS Service.
Test Procedure:
¾ WCDMA system is in normal operation.
¾ The HSDPA cell is set up.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 82 of 177

¾ UE1 support HSDPA and is in idle mode.


¾ UE2 support R99 and is in idle mode.
¾ UE1 is subscribed HSDPA in the HLR. For example, set the PS UL/DL
BE traffic bit rate to 64K/2048K.
¾ 1 HSDPA Catalog 12 UE is used in this test case, its average reported
CQI > 16.
¾ UE1 initiates a PS data service, and the RNC sets up the service on the
HS-DSCH.
¾ UE1 transfers data through FTP.
¾ UE2 calls UE1.
¾ UE1 rings and hooks off. UE1 and UE2 start talking.
¾ Either UE1 or UE2 hooks up to end the conversation.
¾ The UE deactivates the PDP context to release the link when data
transfer ends.
Expected Result:
The PS service over the HS-DSCH is set up. The high speed can be
observed by DU meter or other tools. The call is normal and the voice is
legible.

7. HSDPA To MultiService-Multiservice: VP+HSDPA-PS


Objective:
To verify that the system support VP+HSDPA PS Service.
Test Procedure:
¾ WCDMA system is in normal operation.
¾ The HSDPA cell is set up.
¾ UE1 support HSDPA and is in idle mode.
¾ UE2 support R99 and is in idle mode.
¾ UE1 is subscribed HSDPA in the HLR. For example, set the PS UL/DL
BE traffic bit rate to 64K/2048K.
¾ UE1 supports VP + HSDPA PS Service.
¾ 1 HSDPA Catalog 12 UE is used in this test case, its average reported
CQI > 16.
¾ UE1 initiates a PS data service, and the RNC sets up the service on the
HS-DSCH.
¾ UE1 transfers data through FTP.
¾ UE2 starts VP and calls UE1
¾ UE1 rings and hooks off to start the conversation.
¾ Either UE1 or UE2 hooks up to end the conversation.
¾ The UE deactivates the PDP context to release the link when data
transfer ends.
Expected Result:
The PS service over the HS-DSCH is set up. The high speed can be
observed by DU meter or other tools. The conversation keeps legible and
the picture keeps clear.

B. Power Management
1. HSDPA flexible power allocation with fixed HS-SCCH power, OCNS 25%
load
Objective:
To verify that HSDPA flexible power allocation algorithm could use the
remaining power left by R99.
Test Procedure:
¾ WCDMA system is in normal operation.
¾ The HSDPA cell is set up.
¾ Make sure HSDPA power allocation is dynamic.
¾ CCH total power is about 20% and DCH power margin is set to 10%.
¾ 3 HSDPA Catalog 12 UEs are used in this test case, the average
reported CQI is around 16.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 83 of 177

¾ Configure HSDPA power algorithm to dynamic power allocation.


¾ Configure HS-SCCH power to fixed power allocation.
¾ Configure OCNS load to 45%.
¾ 3 HSDPA UEs initiate PS data service, and the RNC setups the service
on the HS-DSCH.
Expected Result:
HSDPA uses the remain power left by R99, which is around 45%. If
OCNS load could not make HSDPA UEs use out of the remain power left
by R99, try to use intra-frequency neighbor cells interference.

2. HSDPA flexible power allocation with fixed HS-SCCH power, OCNS 50%
load
Objective:
To verify that HSDPA flexible power allocation algorithm could use the
remaining power left by R99.
Test Procedure:
¾ WCDMA system is in normal operation.
¾ The HSDPA cell is set up.
¾ Make sure HSDPA power allocation is dynamic.
¾ CCH total power is about 20% and DCH power margin is set to 10%.
¾ 3 HSDPA Catalog 12 UEs are used in this test case, the average
reported CQI is around 16.
¾ Configure HSDPA power algorithm to dynamic power allocation.
¾ Configure HS-SCCH power to fixed power allocation.
¾ Configure OCNS load to 70%.
¾ 3 HSDPA UEs initiate PS data service, and the RNC setups the service
on the HS-DSCH.
Expected Result:
HSDPA uses the remain power left by R99, which is around 20%. If
OCNS load could not make HSDPA UEs use out of the remain power left
by R99, try to use intra-frequency neighbor cells interference.

C. Code Management
1. HSDPA RNC controlled code allocation, R99 takes more
Objective:
To verify that HSDPA dynamic code allocation algorithm is correct, when
R99 user initiates the R99 service, the code resource will be occupied by
R99.
Test Procedure:
¾ WCDMA system is in normal operation.
¾ The HSDPA cell is set up.
¾ Make sure HSDPA power allocation is dynamic.
¾ Configure code allocation algorithm to “RNC controlled dynamic code
allocation” and its parameters “maximum number code for HSDPA” to
14, and the minimum number to 6, set HS-SCCH codes to 3, and set
free SF threshold to SF16.
¾ 3 HSDPA Catalog 12 UEs are used in this test case, the average
reported CQI is > 16.
¾ 2 R99 UEs are used in this test case.
¾ Configure HSDPA code algorithm to dynamic allocation.
¾ 3 HSDPA UEs initiate PS data service, and start data transmission, the
RNC setups the service on the HS-DSCH.
¾ 2 R99 UEs setup VP calls in the cell.
Expected Result:
HSDPA consumes about 13 codes. After the setup, one code SF16 is
taken from HSDPA.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 84 of 177

2. HSDPA RNC controlled code allocation, HSDPA takes more


Objective:
To verify that HSDPA dynamic code allocation algorithm is correct, when
R99 user terminates the R99 service, the code resource will be allocated
for HSDPA.
Test Procedure:
¾ WCDMA system is in normal operation.
¾ The HSDPA cell is set up.
¾ Make sure HSDPA power allocation is dynamic.
¾ Configure code allocation algorithm to “RNC controlled dynamic code
allocation” and its parameters “maximum number code for HSDPA” to
14, and the minimum number to 6, set HS-SCCH codes to 3, and set
free SF threshold to SF16.
¾ 3 HSDPA Catalog 12 UEs are used in this test case, the average
reported CQI is > 16.
¾ 2 R99 UEs are used in this test case.
¾ Configure HSDPA code algorithm to dynamic allocation.
¾ 3 HSDPA UEs initiate PS data service, and start data transmission, the
RNC setups the service on the HS-DSCH.
¾ 2 R99 UEs setup VP calls in the cell.
¾ Release the VP calls.
Expected Result:
HSDPA consumes about 13 codes. After the setup, one code SF16 is
taken from HSDPA. After release the call, RNC allocates one more code
SF16 for HSDPA.

D. Mobility
1. HSDPA to HSDPA Mobility, Intra RNC, intra Node B, Intra frequency
Objective:
To verify the HSDPA service to ensure continuity when intra-frequency HS-
DSCH cell change in the same Node B does not necessarily lead to
reestablishment of HS-DSCH carriers.
Test Procedure:
¾ WCDMA system is in normal operation.
¾ WCDMA subscriber A is subscribed in the HLR. For example, set the
PS UL/DL BE traffic bit rate to 64K/2048K. Make sure that the DL BE
traffic threshold on HSDPA is no larger than the subscribed DL bit
rate.
¾ Two intra-frequency HSDPA cells are set up in the same Node B.
Configure intra-frequency neighboring CELL 1 and CELL 2 with both
of them working as HSDPA cell.
¾ Enable soft handover.
¾ 1 HSDPA Catalog 12 UE is used in this test case, the average reported
CQI > 16.
¾ The UE initiates a PS data service on CELL 1, and the RNC sets up the
service on the HS-DSCH.
¾ The UE under test moves from CELL 1 to CELL 2 until RNC receive 1A
event report from UE.
¾ The UE under test moves from CELL 1 to CELL 2 again until RNC
receive 1D or 1B event report from UE.
¾ The UE deactivates the PDP context to release the link when data
transfer ends.
Expected Result:
The PS service set up normal. RNC receives 1A event report then
initiates soft handover procedure. The TRUE scramble indicates the
currently serving cell. Cell Changing is completed with Physical channel

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 85 of 177

reconfiguration. Network resources occupied are released after service


ends.

2. HSDPA to HSDPA Mobility, Intra RNC, inter frequency


Objective:
To verify the HSDPA service when inter-frequency HS-DSCH cell change
in different NodeBs does not necessarily lead to reestablishment of HS-
DSCH carriers.
Test Procedure:
¾ WCDMA system is in normal operation.
¾ WCDMA subscriber A is subscribed in the HLR. For example, set the
PS UL/DL BE traffic bit rate to 64K/2048K. Make sure that the DL BE
traffic threshold on HSDPA is no larger than the subscribed DL bit
rate.
¾ Two inter-frequency HSDPA cells are set up in the same Node B
controlled by the same RNC. Configure inter-frequency neighboring
CELL 1 and CELL 2 with both of them working as HSDPA cell.
¾ Enable hard handover.
¾ 1 HSDPA Catalog 12 UE is used in this test case, the average reported
CQI > 16.
¾ The UE initiates a PS data service on CELL 1, and the RNC sets up the
service on the HS-DSCH.
¾ The UE under test moves from CELL 1 to CELL 2 until RNC receive 2D
event report from UE.
¾ The UE under test reports inter-frequency measurement event report to
RNC.
¾ The UE deactivates the PDP context to release the link when data
transfer ends.
Expected Result:
The PS service set up normal. RNC receives 2D event report then
initiates compress mode procedure. RNC receives inter-frequency
measurement event report from UE, and decides to make inter-frequency
handover. Network resources occupied are released after service ends.

3. HSDPA to non HSDPA Mobility, Intra RNC, intra frequency


Objective:
To verify that the RB carried by the HSDPA switches from HSDSCH to
DCH after the handover from HSDPA supportive cell to non HSDPA
supportive cell.
Test Procedure:
¾ WCDMA system is in normal operation.
¾ WCDMA subscriber A is subscribed in the HLR. For example, set the
PS UL/DL BE traffic bit rate to 64K/2048K.
¾ Configure intra-frequency neighboring CELL 1 and CELL 2 with CELL 1
working as a R5 cell and CELL2 as a R99 cell.
¾ Enable soft handover.
¾ 1 HSDPA Catalog 12 UE is used in this test case, the average reported
CQI > 16.
¾ The UE initiates a PS data service on CELL 1, and the RNC sets up the
service on the HS-DSCH.
¾ The UE under test moves from CELL 1 to CELL 2 until RNC receive 1A
event report from UE.
¾ The UE under test moves from CELL1 to CELL2 again until RNC
receive 1B event report from UE.
¾ The UE deactivates the PDP context to release the link when data
transfer ends.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 86 of 177

Expected Result:
The PS service set up normal. RNC receives 1A event report then
initiates soft handover procedure. Channel switching from HS-DSCH to
DCH. Network resources occupied are released after service ends.

4. HSDPA to non HSDPA Mobility, Intra RNC, inter frequency


Objective:
To verify that the RB carried by the HSDPA switches from HSDSCH to
DCH after the handover from HSDPA supportive cell to non HSDPA
supportive cell.
Test Procedure:
¾ WCDMA system is in normal operation.
¾ WCDMA subscriber A is subscribed in the HLR. For example, set the
PS UL/DL BE traffic bit rate to 64K/2048K.
¾ Configure inter-frequency neighboring CELL 1 and CELL 2 with CELL 1
working as a R5 cell and CELL2 as a R99 cell.
¾ Enable hard handover.
¾ 1 HSDPA Catalog 12 UE is used in this test case, the average reported
CQI > 16.
¾ The UE initiates a PS data service on CELL 1, and the RNC sets up the
service on the HS-DSCH.
¾ The UE under test moves from CELL 1 to CELL 2 until RNC receive 2D
event report from UE.
¾ The state of UE under test switches from HSDPA to DCH.
¾ The UE under test reports inter-frequency measurement event report to
RNC.
¾ The UE deactivates the PDP context to release the link when data
transfer ends.
Expected Result:
The PS service set up normal. RNC receives 2D event report then
initiates compress mode procedure. RNC receives inter-frequency
measurement event report from UE, and decides to make inter-frequency
handover. Network resources occupied are released after service ends.

5. Non HSDPA to non HSDPA Mobility, Intra RNC, intra frequency


Objective:
To verify that the service is switched from the DCH to the HSDSCH after
the handover from non HSDPA supportive cell to HSDPA supportive cell.
Test Procedure:
¾ WCDMA system is in normal operation.
¾ WCDMA subscriber A is subscribed in the HLR. For example, set the
PS UL/DL BE traffic bit rate to 64K/2048K.
¾ Configure intra-frequency neighboring CELL 1 and CELL 2 with CELL 1
working as a R5 cell and CELL2 as a R99 cell.
¾ Enable soft handover.
¾ 1 HSDPA Catalog 12 UE is used in this test case, the average reported
CQI > 16.
¾ The UE initiates a PS data service on CELL 1, and the RNC sets up the
service on the DCH.
¾ The UE under test moves from CELL 1 to CELL 2 until RNC receive 1A
event report from UE.
¾ The UE stays in the same place where it received 1A event report.
¾ The UE deactivates the PDP context to release the link when data
transfer ends.
Expected Result:
The PS service set up normal. Network resources occupied are released
after service ends.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 87 of 177

6. Non HSDPA to HSDPA Mobility, Intra RNC, inter frequency


Objective:
To verify that the RB carried by the HSDPA switches from DCH to HS-
DSCH after the handover from non HSDPA supportive cell to HSDPA
supportive cell.
Test Procedure:
¾ WCDMA system is in normal operation.
¾ WCDMA subscriber A is subscribed in the HLR. For example, set the
PS UL/DL BE traffic bit rate to 64K/2048K.
¾ Configure inter-frequency neighboring CELL 1 and CELL 2 with CELL 1
working as a R99 cell and CELL2 as a R5 cell.
¾ Enable hard handover.
¾ 1 HSDPA Catalog 12 UE is used in this test case, the average reported
CQI > 16.
¾ The UE initiates a PS data service on CELL 1, and the RNC sets up the
service on the DCH.
¾ The UE under test moves from CELL 1 to CELL 2 until RNC receive 2D
event report from UE.
¾ The UE under test reports inter-frequency measurement event report to
RNC.
¾ The state of UE under test switches from DCH to HSDPA.
¾ The UE deactivates the PDP context to release the link when data
transfer ends.
Expected Result:
The PS service set up normal. RNC receives 2D event report then
initiates compress mode procedure. RNC receives inter-frequency
measurement event report from UE, and decides to make inter-frequency
handover. Network resources occupied are released after service ends.

E. Load Management
1. HSDPA CAC
Objective:
To verify the HSDPA Admission Control function.
Test Procedure:
¾ WCDMA system is in normal operation.
¾ The cell 1 under test supports HSDPA functions and the cell HSDPA
state is available.
¾ WCDMA subscribers are subscribed in the HLR. For example, set the
PS UL/DL BE traffic bit rate to 64K/2048K.
¾ Five codes for HS-PDSCH and one code for HS-SCCH are configured
at least. The DL power is dynamically allocated.
¾ The capability of all UEs under test is category 12 or above.
¾ HSDPA Admission Control function is enabled.
¾ HSDPA Admission user number is set to 3.
¾ 4 HSDPA Catalog 12 UE is used in this test case, the average reported
CQI is around 16.
¾ The first UE, the second UE, and the third UE initiates HSDPA PS data
service one by one.
¾ The fourth UE want to initiate HSDPA PS data service too.
Expected Result:
RNC setup these services on the HS-DSCH. Because of the HSDPA
admission control algorithm, RNC doesn’t setup the service on the HS-
DSCH, but admits it setup on DCH RB.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 88 of 177

F. Iub flow control


1. IUB Efficiency for HSDPA, 1 E1
Objective:
To verify Iub bandwidth utilization efficiency and user throughput vs.
HSDPA users with extreme limited IUB configuration.
Test Procedure:
¾ WCDMA system is in normal operation.
¾ The cell under test supports HSDPA functions and the cell HSDPA state
is available.
¾ 14 codes for HS-PDSCH and 3 codes for HS-SCCH are configured The
HSDPA power is dynamically allocated.
¾ HSDPA and R99 services share 1 E1 Iub transmission.
¾ For each user, its average reported CQI > 16.
¾ 3 HSDPA Catalog 12 UEs are used in this test case.
¾ The 3 UEs initiates a PS data service each, and the RNC sets up the
services on the HS-DSCH.
¾ Download large files with stable data source (larger than 20 MB) from
the server through FTP by each HSDPA UE.
¾ Record the average DL throughput of the 3 UEs, and calculate the
average cell throughput in the DL and Iub transmission efficiency.
Expected Result:
The PS services over the HS-DSCH are set-up. No UE automatically
deactivates the PDP context or disrupts its connection during the test.

2. IUB Efficiency for HSDPA and R99, 1 E1


Objective:
To verify Iub bandwidth utilization efficiency with limited IUB configuration;
and bandwidth allocation between HSDPA and R99 users.
Test Procedure:
¾ WCDMA system is in normal operation.
¾ The cell under test supports HSDPA functions and the cell HSDPA state
is available.
¾ Configure 8 codes for HS-PDSCH and 3 codes for HS-SCCH. The
HSDPA power is dynamically allocated and code is statistically
allocated.
¾ HSDPA and R99 services share 1 E1 Iub transmission.
¾ For each user, its average reported CQI > 16.
¾ 3 HSDPA Catalog 12 UEs and 3 R99 UEs are used in this test case.
¾ 3 R99 UEs initiates a 64K/384K PS data service each, and the RNC
sets up the services on the DCH.
¾ At the same time, 3 HSDPA UEs initiate a PS data service each, and
the RNC sets up the services on HS-DSCH.
¾ Download large files with stable data source (larger than 20 MB) from
the server through FTP by all the 6 users.
¾ Record the average DL throughput of the 3 HSDPA UEs and 3 R99
UEs by DUMETER or other tools, and calculate the average cell
throughput in the DL.
Expected Result:
The services over the HS-DSCH are set-up. No UE automatically
deactivates the PDP context or disrupts its connection during the test.
The 3 R99 services are not impacted by the 3 HSDPA services. The Iub
bandwidth of the R99 services is always assured.

G. State switch
1. HSDPA to FACH and to Idle
Objective:

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 89 of 177

To verify that the channel is switched from HSDSCH to FACH, when there
is no traffic for the service set up over HSDSCH, and when PS Inactive
detective timer expired, switch to IDLE.
Test Procedure:
¾ WCDMA system is in normal operation.
¾ The cell under test supports HSDPA functions and the cell HSDPA state
is available.
¾ WCDMA subscriber A is subscribed in the HLR. For example, set the
PS UL/DL BE traffic bit rate to 64K/2048K. Make sure that the DL BE
traffic threshold on HSDPA is no larger than the subscribed DL bit
rate.
¾ Enable the UE state transition algorithm switch.
¾ Set PS inactive detective timer.
¾ 1 HSDPA Catalog 12 UE is used in this test case, the average reported
CQI > 16.
¾ The UE initiates a PS data service, and the RNC sets up the service on
the HS-DSCH.
¾ The UE doesn’t transfer any data through FTP.
¾ The channel is switched to the FACH state when there is no traffic over
HSDSCH due to halted service.
¾ Keep on UE non-data transfer until the channel is switched to the IDLE
state.
Expected Result:
The single PS service over the HS-DSCH is set-up. Channel switching
from HS-DSCH to FACH. During non-data transfer, the Iu connection is
released successfully, and the PDP context should be reserved by SGSN,
then Channel switching from FACH to IDLE.

2. FACH to HSDPA
Objective:
To verify that burst traffic is switched from FACH to HSDSCH.
Test Procedure:
¾ WCDMA system is in normal operation.
¾ The cell under test supports HSDPA functions and the cell HSDPA state
is available.
¾ WCDMA subscriber A is subscribed in the HLR. For example, set the
PS UL/DL BE traffic bit rate to 64K/2048K.
¾ Enable the UE state transition algorithm switch.
¾ 1 HSDPA Catalog 12 UE is used in this test case, the average reported
CQI > 16.
¾ The UE initiates a PS data service, and the RNC sets up the service on
the HS-DSCH.
¾ The UE doesn’t transfer any data through FTP. The channel is
switched to the FACH state first.
¾ The UE transfers data through FTP. The channel is switched to the
HSDSCH state because of burst traffic.
¾ The UE deactivates the PDP context to release the link when data
transfer ends.
Expected Result:
The single PS service over the HS-DSCH is set-up. Channel switching
from FACH to HS-DSCH. Network resources occupied are released after
the service ends.

H. RTT
1. Ping Packet Delay
Objective:
Measure the ping packet delay at UE for ping sizes 32, 256, and 1024
bytes. The PS UL 64 kbps/PS DL HSDPA is used for this test.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 90 of 177

Test Procedure:
¾ WCDMA system is in normal operation.
¾ All cells support HSDPA over the drive path.
¾ 1 HSDPA Catalog 12 UE is used in this test case, the average reported
CQI > 16.
¾ Activate a PDP context with a HSDPA mobile (UL64K)
¾ Using Window’s Command Prompt, launch successive 32 bytes ping
packets during 1 minute.
¾ Measure the following metrics: Number of packets sent, Number of
Packets received, Percentage of Loss, Minimum RTT, Maximum RTT,
and Average RTT.
¾ Repeat steps 2 and 3 for ping packet sizes of 256, 1024 bytes.
Expected Result:
Ping is successful and there is no packet loss.

I. Hardware Capacity
1. 3*1 with 15 HS-PDSCH/cell
Objective:
To verify the capability of HSDPA 3X1 with 15 HS-PDSCH/cell.
Test Procedure:
¾ Configure HSDPA 3X1 with 15 HS-PDSCH/cell, these three cells are
intra-frequency in the same Node B but on different sectors.
¾ After the cells have been created, activate them, and activate the
HSDPA function.
¾ Monitor the cell code tree of these three cells.
Expected Result:
The cells and their HSDPA function are activated successfully. The
monitor shows 15 HS-PDSCH/cell clearly.

J. HSDPA and R99 mixed cell sharing one carrier


1. 3*1 with 15 HS-PDSCH/cell
Objective:
To verify if the system could support the configuration of HSDPA and R99
mixed cell only occupy one carrier.
Test Procedure:
¾ Test system could support HSDPA function.
¾ Test UEs support HSDPA function.
¾ Setup R99 cell.
¾ Configure HSDPA parameters, finish power and code allocation of HS-
PDSCH and HS-SCCH by physical shared channel reconfiguration in
the cell. Configure 5 HS-PDSCH channels and 1 HS-SCCH channel,
downlink power is allocated dynamically.
¾ Test UE initiates PS I/B service, and this traffic is carried on HS-DSCH
channel.
Expected Result:
Setup R99+R5 one carrier cell successfully. All traffics are setup and
release normally.

K. Throughput capacity
1. Cell throughput in case of 5 HS-PDSCH, Category 12 UE, CDM4, CQI>16
Objective:
To get Cell Peak Traffic over 5 HS-PDSCHs, Category 12 UE, CDM4
CQI>16.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 91 of 177

Test Procedure:
¾ WCDMA system is in normal operation.
¾ The cell under test supports HSDPA functions and the cell HSDPA state
is available.
¾ WCDMA subscribers are subscribed in the HLR. Set the PS UL/DL BE
traffic bit rate to 64K/2048K.
¾ 5 codes for HS-PDSCH and 4 codes for HS-SCCH are configured. The
DL power is dynamically allocated.
¾ 6 HSDPA Catalog 12 UEs are used in this test case, the average
reported CQI > 16.
¾ The six UEs initiate PS data services, and the RNC sets up the services
on the HS-DSCH.
¾ Download large files with stable data source (larger than 20 MB) from
the server through FTP by using the six UEs under test.
¾ Test UE deactivates the PDP context to release the link when data
transfer ends.
Expected Result:
DUMETER or other tools can observe the speed of six UEs respectively.
Each of the six UEs can transfer data through FTP normally. Calculate
and record the Cell Peak Traffic over 5 HS-PDSCHs.

2. Cell throughput in case of 10 HS-PDSCH, Category 12 UE, CDM4, CQI>16


Objective:
To get Cell Peak Traffic over 10 HS-PDSCHs, Category 12 UE, CDM4
CQI>16.
Test Procedure:
¾ WCDMA system is in normal operation.
¾ The cell under test supports HSDPA functions and the cell HSDPA state
is available.
¾ WCDMA subscribers are subscribed in the HLR. Set the PS UL/DL BE
traffic bit rate to 64K/2048K.
¾ 10 codes for HS-PDSCH and 4 codes for HS-SCCH are configured.
The DL power is dynamically allocated.
¾ 6 HSDPA Catalog 12 UEs are used in this test case, the average
reported CQI > 16.
¾ Iub transmission configuration should not be less than 12 Mbps.
¾ The six UEs initiate PS data services, and the RNC sets up the services
on the HS-DSCH.
¾ Download large files with stable data source (larger than 20 MB) from
the server through FTP by using the six UEs under test.
¾ Test UE deactivates the PDP context to release the link when data
transfer ends.
Expected Result:
DUMETER or other tools can observe the speed of six UEs respectively.
Each of the six UEs can transfer data through FTP normally. Calculate
and record the Cell Peak Traffic over 10 HS-PDSCHs.

3. Cell throughput in case of 14 HS-PDSCH, Category 12 UE, CDM4, CQI>16


Objective:
To get Cell Peak Traffic over 14 HS-PDSCHs, Category 12 UE, CDM4
CQI>16.
Test Procedure:
¾ WCDMA system is in normal operation.
¾ The cell under test supports HSDPA functions and the cell HSDPA state
is available.
¾ WCDMA subscribers are subscribed in the HLR. Set the PS UL/DL BE
traffic bit rate to 64K/2048K.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 92 of 177

¾ 14 codes for HS-PDSCH and 4 codes for HS-SCCH are configured.


The DL power is dynamically allocated.
¾ 6 HSDPA Catalog 12 UEs are used in this test case, the average
reported CQI > 16.
¾ Iub transmission configuration should not be less than 12 Mbps.
¾ The six UEs initiate PS data services, and the RNC sets up the services
on the HS-DSCH.
¾ Download large files with stable data source (larger than 20 MB) from
the server through FTP by using the six UEs under test.
¾ Test UE deactivates the PDP context to release the link when data
transfer ends.
Expected Result:
DUMETER or other tools can observe the speed of six UEs respectively.
Each of the six UEs can transfer data through FTP normally. Calculate
and record the Cell Peak Traffic over 14 HS-PDSCHs.

L. System reliability
1. HSDPA system reliability
Objective:
To verify the system reliability of holding traffic for long time.
Test Procedure:
¾ RNC initiates physical shared channel reconfiguration by the HSDPA
capability indicated in the messages resource status indication and
Audit response, and finishes the power and code allocation of HS-
PDSCH and HS-SCCH. Configure 5 HS-PDSCH channel codes and
1 HS-SCCH channel codes, and downlink power is allocated
dynamically.
¾ 1 HSDPA Catalog 12 UE is used in this test case, the average reported
CQI > 21.
¾ Iub transmission configuration: no less than 6 Mbps.
¾ UE initiates PS DL 2048K HSDPA background traffic, the traffic is setup
on the HS-DSCH channel.
¾ 5 codes for HS-PDSCH and 4 codes for HS-SCCH are configured. The
DL power is dynamically allocated.
¾ 6 HSDPA Catalog 12 UEs are used in this test case, the average
reported CQI > 16.
¾ The six UEs initiate PS data services, and the RNC sets up the services
on the HS-DSCH.
¾ Download large files with stable data source (larger than 20 MB) from
the server through FTP by using the six UEs under test.
¾ Test UE deactivates the PDP context to release the link when data
transfer ends.
Expected Result:
DUMETER or other tools can observe the speed of six UEs respectively.
Each of the six UEs can transfer data through FTP normally. Calculate
and record the Cell Peak Traffic over 5 HS-PDSCHs.

M. Iub standard interface


1. Common measurement of HSDPA cell – transmitted carrier power of all
codes not used for HS-SCCH transmission
Objective:
To verify HSDPA cell common measurement message follows the
requirement of protocol.
Test Procedure:
¾ Setup cell successfully.
¾ RNC initiates physical shared channel reconfiguration by the HSDPA
capability indicated in the messages resource status indication and

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 93 of 177

Audit response, and finishes the power and code allocation of HS-
PDSCH and HS-SCCH.
¾ Monitor Iub interface with protocol analyzer.
¾ RNC initiates HSDPA cell common measurement, Common
Measurement Type is transmitted carrier power of all codes not used
for HS-PDSCH or HS-SCCH transmission, Measurement Report
Characteristics Type is On Demand or Periodic or Event.
¾ Monitor Iub interface with protocol analyzer.
¾ Node B common measurement initialization procedure is successful,
Node B reports common measurement follow the Report
Characteristics Type.
Expected Result:
Make sure the common measurement message follows the requirement
of protocol 3GPP 25.433 V5.13.0 chapter 9.1.21 by protocol analyzer.

2. Common measurement of HSDPA cell – HS-DSCH required power


measurement
Objective:
To verify HSDPA cell common measurement message follows the
requirement of protocol.

Test Procedure:
¾ Setup cell successfully.
¾ RNC initiates physical shared channel reconfiguration by the HSDPA
capability indicated in the messages resource status indication and
Audit response, and finishes the power and code allocation of HS-
PDSCH and HS-SCCH.
¾ Monitor Iub interface with protocol analyzer.
¾ RNC initiates HSDPA cell common measurement, Common
Measurement Type is HS-DSCH required power measurement,
Measurement Report Characteristics Type is On Demand or Periodic
or Event.
¾ Monitor Iub interface with protocol analyzer.
¾ Node B common measurement initialization procedure is successful,
Node B reports common measurement follow the Report
Characteristics Type.
Expected Result:
Make sure the common measurement message follows the requirement
of protocol 3GPP 25.433 V5.13.0 chapter 9.1.21 by protocol analyzer.

3. Common measurement of HSDPA cell – HS-DSCH provided bit rate


measurement
Objective:
To verify HSDPA cell common measurement message follows the
requirement of protocol.
Test Procedure:
¾ Setup cell successfully.
¾ RNC initiates physical shared channel reconfiguration by the HSDPA
capability indicated in the messages resource status indication and
Audit response, and finishes the power and code allocation of HS-
PDSCH and HS-SCCH.
¾ Monitor Iub interface with protocol analyzer.
¾ RNC initiates HSDPA cell common measurement, Common
Measurement Type is HS-DSCH provided bit rate measurement,
Measurement Report Characteristics Type is On Demand or Periodic
or Event.
¾ Monitor Iub interface with protocol analyzer.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 94 of 177

¾ Node B common measurement initialization procedure is successful,


Node B reports common measurement follow the Report
Characteristics Type.
Expected Result:
Make sure the common measurement message follows the requirement
of protocol 3GPP 25.433 V5.13.0 chapter 9.1.21 by protocol analyzer.

4. HSDPA cell configuration over Iub interface


Objective:
To verify HSDPA cell common measurement message follows the
requirement of protocol.
Test Procedure:
¾ Setup cell successfully.
¾ RNC initiates physical shared channel reconfiguration by the HSDPA
capability indicated in the messages resource status indication and
Audit response, and finishes the power and code allocation of HS-
PDSCH and HS-SCCH.
¾ Monitor Iub interface with protocol analyzer.
¾ RNC initiates physical shared channel reconfiguration request by the
HSDPA capability indicated in the messages resource status
indication and Audit response, and finishes the power and code
allocation of HS-PDSCH and HS-SCCH.
¾ Node B responds with message physical shared channel
reconfiguration response.
¾ Monitor Iub interface with protocol analyzer.
¾ Node B common measurement initialization procedure is successful,
Node B reports common measurement follow the Report
Characteristics Type.
Expected Result:
Make sure the interface message follows the requirement of protocol
3GPP 25.433 V5.13.0 chapter 8.2.18 by protocol analyzer.

5. HSDPA service reconfigured on RL over Iub interface


Objective:
To verify HSDPA service reconfigured on RL over Iub interface follows the
requirement of protocol.
Test Procedure:
¾ Setup cell successfully.
¾ RNC initiates physical shared channel reconfiguration by the HSDPA
capability indicated in the messages resource status indication and
Audit response, and finishes the power and code allocation of HS-
PDSCH and HS-SCCH.
¾ Monitor Iub interface with protocol analyzer.
¾ UE initiates PS data traffic in the HSDPA cell.
¾ RNC setups a HS-DSCH channel through sending RL reconfiguration
prepare message to Node B.
¾ Node B responds with message RL reconfiguration ready.
Expected Result:
Make sure the interface message follows the requirement of protocol
3GPP 25.433 V5.13.0 chapter 8.3 by protocol analyzer.

N. Configuration
1. Activate/Deactivate HSDPA functionality in a Node B
Objective:
To purpose of this test is to Activate / Deactivate HSDPA function.
Test Procedure:
¾ RNC and Node B are in normal operation.
¾ Cell with HSDPA exits and is in normal state.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 95 of 177

¾ Log in to the O&M system.


¾ Deactivate the HSDPA functionality of a cell.
¾ Activate the HSDPA functionality of a cell.
¾ Initiate a HSDPA service.
Expected Result:
The cell’s HSDPA service will be stopped and will be recovered. The
service is normal.

2. Create a new node B with the HSDPA functionality


Objective:
The purpose of this test is to check the procedure to create a new NodeB
with the HSDPA function.
Test Procedure:
¾ RNC and Node B are in normal operation.
¾ Log in to the O&M system.
¾ Node B with local cell type of HSDPA is in normal state.
¾ Iub interface data is negotiated and planned.
¾ Transport line has been connected between RNC and Node B.
¾ Configure Node B data and Node B congestion control algorithm
parameters.
¾ Configure the Iub interface data.
¾ Configure a cell data.
¾ Activate the cell’s HSDPA functionality.
¾ Upload configuration file to Node B, and activate the configuration.
¾ Query the state of Iub ports and AAL2 adjacent.
¾ Query the state of the cell.
¾ Initiate a HSDPA service.
Expected Result:
Node B startup normally. The state of Iub ports and AAL2 adjacent is
available. The state of the cell is available. The service is normal.

3. Change of HSDPA Configuration Parameters


Objective:
The purpose of this test is to change of HSDPA Configuration Parameters.
Test Procedure:
¾ RNC and Node B are in normal operation.
¾ Cell with HSDPA exits and is in normal state.
¾ Log in to the O&M system.
¾ Change the HSDPA Configuration Parameters
¾ Initiate a HSDPA service.
Expected Result:
The service is normal.

4. Iub HSDPA capacity increase/decrease


Objective:
The purpose of this test is to provide and execute the Iub capacity
increase/decrease procedure.
Test Procedure:
¾ RNC and Node B are in normal operation.
¾ Cell with HSDPA exits and is in normal state.
¾ The AAL2 path type of HSDPA is configured on IMA group.
¾ Log in to the O&M system.
¾ Add a new greater ATM traffic record in RNC. Then add an IMA link
into the IMA group bearing the HSDPA AAL2 path in RNC and Node
B.
¾ Delete the HSDPA AAL2 path and add the AAL2 path using the greater
ATM traffic in RNC and Node B.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 96 of 177

¾ Initiate a HSDPA service.


Expected Result:
The operation doesn’t impact on service in UTRAN.
The operation will interrupt the HSDPA service.
The service is normal.

6.2 Pilot/KPI Tests and Stress Tests

The pilot/KPI tests will measure the quality and performance of the network and
services. The stress tests will validate subscriber experience and possible problem
while using the mentioned 3G services.

The measurements will be compared to the acceptable values recommended by


different standard bodies. For user experience, the performance will be measured
subjectively and objectively. For accuracy, the performance will be measured
objectively.

The performance will be gauged according to throughput, delay, clarity, and


recommended 3G Key Performance Indicators (KPIs).

6.2.1 General Test Procedures and Guidelines:

¾ The monitoring tool of the vendor for gathering statistics must be up and
running.
¾ Documents on the procedure and the results table will be provided to the
testers.
¾ A DMPI engineer will assist the engineer of the vendor at each node B sites.
Each tester is given 1 test phone with a USIM each.
¾ Handsets/test phones need to be configured before the test.
¾ There are four basic things to be configured on the test phone
• Enable 3G mode on the phone.
• GPRS Settings
• MMS Settings
• Streaming Settings
The vendor needs to assist with the configuration and must submit the
procedure on how to configure the test phones.
¾ Tester to proceed to the test points in the specified location before the start
of each test sequence.
¾ A 3G icon will be seen if the tester is in a 3G coverage area.
¾ Using the 3G handset, the following services will be tested:
™ Voice call
™ SMS
™ Video Call
™ PS Services (Web Browsing, Internet Browsing, Multimedia Streaming,
Downloading, and MMS)

¾ Using the laptop with an HSDPA card, the PS services will also be tested.
¾ Tester to download large file at high speed downlink speed
¾ Tester to conduct a voice calls while engaged in downloading file.
¾ The results will be written in the table, according to site and test scenarios.
¾ The validity of the results will be verified by both DMPI and the vendor. The
signatures of the tester and vendor will be affixed to the results.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 97 of 177

6.2.2 INDOOR / OUTDOOR COVERAGE ASSESSMENTS (PILOT TEST)

Objective:
This assessment is conducted to identify the signal level strength and
signal quality in the areas to be verified, be it an outdoor or indoor
location.

Test Procedure:
¾ Tester/s are deployed in different buildings and institution which may
include Malls, Hotels, Hospitals, and Offices.
¾ Tester will be checking the signal level and signal quality in the different
areas or streets or floor. For indoor assessments and outdoor
assessments, test points are based on the Criteria and Guidelines as
provided by Radio Network Planning.
¾ The Radio Network Planning Criteria and Guidelines include Standard
Coverage Areas and Optional Coverage Areas. Testers are required to
complete the Standards Coverage Areas during the assessments.
¾ DMPI and the supplier shall conduct different drive test where the
testers situated in each point will plot the RSSI and SIR. DMPI will use a
third-party drive test tool while the vendor can use their own drive test
tool.
¾ DMPI and supplier will compare the plot of each drive test.

Expected Result:
The coverage plots are accurate and acceptable to DMPI.
The plots for voice should include quality, level, C/I or its 3G equivalence.
The plots for data should include throughput. The results should also be
tabulated:

VOICE
RX Quality RX Level C/I

DATA
Throughput (kbps)

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 98 of 177

6.2.3 Stress Test (Subjective Measurements)

6.2.3.1 Voice Call: Site A ______________ Site B _______________


Phone Type _________ Phone Type __________

Scenario: Sun Cellular 3G to Sun Cellular 3G

Test Execution:

A. For Continuous Mode


¾ Tester A to dial Tester B number
¾ Call will be terminated after 5 minutes
¾ This will be repeated thrice at each of the test point
¾ Record observation/comments and results

Test Results
Expected Results
Location 1st Test 2nd Test 3rd Test
Clear Voice
Choppy Voice
Disconnected before completion
of 5 minutes Voice Call
Unable to Connect

B. For Call Gen Mode


¾ Tester A to dial Tester B Number
¾ Call will be terminated after 2 minutes
¾ A 15-seconds pause is required before the next test sequence
¾ This will be repeated thrice at each of the test point.
¾ Record observation/comments and results

Test Results
Expected Results
Location 1st Test 2nd Test 3rd Test
Clear Voice
Choppy Voice
Disconnected before completion
of 2 minutes Voice Call
Established connection of voice
call in 3 consecutive attempts.
Unable to Connect

6.2.3.2 SMS:

Scenario: Sun Cellular 3G to Sun Cellular 3G

Test Execution:

Settings of 3G test handset for SMS are subject for verification with vendor.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 99 of 177

A. For SMS
¾ Tester A to create text message
¾ In the “To:” icon, indicate the cell phone number or access number to
which the message will be sent during the test
¾ Monitor if the text message created was successfully sent
¾ This will be repeated thrice at each of the test point
¾ Record observation/comments and results

Test Results
Expected Results
Location 1st Test 2nd Test 3rd Test
Tester A able to send SMS to
Tester B
Unable to send SMS

6.2.3.3 Video Call: Site A ______________ Site B _____________


Phone Type _________ Phone Type __________

Scenario 1: Sun Cellular 3G to Sun Cellular 3G

Test Execution:

A. For Continuous Mode


¾ Tester A to dial contact number of Tester B
¾ Tester A to click on “Call” option
¾ Tester A to choose “Video Call” option
¾ Wait until the video call will be connected
¾ Video Call will be terminated after 5 minutes
¾ This will be repeated thrice at each of the test point
¾ Record observation/comments and results

Test Results
Expected Results
Location 1st Test 2nd Test 3rd Test
Clear Video and Voice

Clear Video but Choppy Voice


Disconnected before completion
of 5 minutes Video call
Distorted Video and Choppy Voice
No 3G Icon even after several
manual network selection
Poor Video and Choppy Voice
Poor Video but Good Voice
Unable to Connect

B. For Call Gen Mode


¾ Tester A to dial contact number of Tester B
¾ Tester A to click on “Call” option
¾ Tester A to choose “Video Call” option

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 100 of 177

¾ Wait until the Video Call will be connected


¾ Video Call will be terminated after 2 minutes
¾ A 15-seconds pause is required before the next test sequence
¾ This will be repeated thrice at each of the test point.
¾ Record observation/comments and result

Test Results
Expected Results
Location
1st Test 2nd Test 3rd Test
Clear Video and Voice
Clear Video but Choppy Voice
Disconnected before completion
of 2 minutes Video call
Distorted Video and Choppy Voice
No 3G Icon even after several
manual network selection
Poor Video and Choppy Voice
Poor Video but Good Voice
Established connection of Video
call in 3 consecutive attempts.
Unable to Connect

6.2.4.4 WAP Browsing:

Test Execution:

Settings of 3G test handset for WAP browsing are subject for verification with
vendor.

A. For WAP Browsing


¾ Tester A to connect and browse the WAP page via WAP for 5
minutes.
¾ Web address to be typed would be: http://www.suncellular.com.ph
¾ Page will connect and tester can begin browsing
¾ This will be repeated thrice at each of the test point.
¾ Record observation/comments and results

Test Results
Expected Results
Location
1st Test 2nd Test 3rd Test
Continuous Connection
Disconnected before completion
of 5 minutes WAP browsing
No 3G Icon even after several
manual network selection
Unable to Connect

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 101 of 177

6.2.4.5 Internet Browsing:

Test Execution:

Settings of 3G test handset for Internet browsing are subject for verification with
vendor.

A. For Internet Browsing


¾ Tester to connect and browse the internet via phone internet browser for 5
minutes.
¾ Each Tester will use a different link
• http://www.yahoo.com
• http://www.google.com
• http://www.friendster.com
• http://www.inq7.net
• http://www.cnn.com
• http://www.suncellular.com.ph
¾ Page will connect and tester can begin browsing
¾ This will be repeated thrice at each of the test point.
¾ Record observation/comments and results

Test Results
Expected Results
Location
1st Test 2nd Test 3rd Test
Continuous Connection
Disconnected before completion
of 5 minutes Internet browsing
No 3G Icon even after several
manual network selection
Unable to Connect

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 102 of 177

6.2.4.6 Multimedia Streaming:

Settings of 3G test handset for Multimedia Streaming are subject for verification
with vendor.

Test Execution:

A. For Live Video Streaming


¾ Tester A to view multimedia live video via streaming
¾ URL to be accessed is still for verification with the vendor.
¾ Page will connect and tester can begin to view the video stream
¾ This will be repeated thrice at each of the test point
¾ Record observation/comments and results

Test Results
Expected Results
Location 1st Test 2nd Test 3rd Test
Clear Video and Audio
Frequent Buffering
Disconnected before completion
of 6 min-streaming
Distorted Image
No 3G Icon even after several
manual network selection
Poor Video and Choppy Audio
Poor Video but Clear Audio
Unable to Connect

B. For Video Streaming On Demand


¾ Tester A to view multimedia (video on demand) via streaming
¾ URL to be accessed is still for verification with the vendor
¾ Page will connect and tester can begin to view the video stream
¾ This will be repeated thrice at each of the test point
¾ Record observation/comments and results

Test Results
Expected Results
Location 1st Test 2nd Test 3rd Test
Clear Video and Audio
Frequent Buffering
Disconnected before completion
of 6 min-streaming
Distorted Image
No 3G Icon even after several
manual network selection
Poor Video and Choppy Audio
Poor Video but Clear Audio
Unable to Connect

C. For Live TV Streaming


¾ Tester A to view multimedia (i.e., radio TV) via streaming
¾ URL to be accessed is still for verification with the vendor
¾ Page will connect and tester can begin to view the video stream
¾ This will be repeated thrice at each of the test point
¾ Record observation/comments and results

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 103 of 177

Test Results
Expected Results
Location 1st Test 2nd Test 3rd Test
Clear Video and Audio
Frequent Buffering
Disconnected before completion
of 6 min-streaming
Distorted Image
No 3G Icon even after several
manual network selection
Poor Video and Choppy Audio
Poor Video but Clear Audio
Unable to Connect

6.2.3.7 Downloading

Test Execution:

Settings of 3G test handset for WAP browsing are subject for verification with
vendor.

A. For Downloading
¾ Tester A to connect and browse the internet via WAP for 2 minutes.
¾ Web address to be typed would be:
www.suncellular.com.ph/sunwap/test/truewav.wav
¾ Tester will be prompted to save
¾ Record observation/comments and results

Test
Location Expected Results Results
Continuous Connection
Disconnected before completion of 2
minutes WAP browsing
Able to download file
Unable to download file
No 3G Icon even after several manual
network selection
Unable to Connect

6.2.3.8 MMS

Scenario: Sun Cellular 3G to Sun Cellular 3G

Test Execution:

Settings of 3G test handset for MMS are subject for verification with vendor.

A. For MMS
¾ Tester A to create multimedia message
¾ In the “To:” icon, indicate the cell phone number or access number to
which the message will be sent during the test
¾ Monitor if the multimedia created was successfully sent

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 104 of 177

¾ This will be repeated thrice at each of the test point


¾ Record observation/comments and results

Test Results
Expected Results
Location 1st Test 2nd Test 3rd Test
Tester A able to send MMS
Unable to send MMS

6.2.2.3.9 HSDPA

Test Execution:

Settings of 3G test laptop for HSDPA are subject for verification with
vendor.

A. For HSDPA
¾ Tester A will use Laptop to be connected to the internet using 3G HSDPA
data card.
¾ Tester A will then access http://www.microsoft.com
¾ On the download page, click Home & Office and the Office XP Service
Pack 3 (SP3) file will be accessed.
¾ Tester will be prompted to save.

Test
Location Expected Results Results
Continuous Connection
Disconnected before completion of HSDPA
downloading
Able to download file
Unable to download file
No 3G Icon even after several manual
network selection
Unable to Connect

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 105 of 177

6.2.4 Objective Measurements of Quality

The tests will be performed on a per site basis and also on a whole network
point of view.

A. Per Site Basis

6.2.4.1 Voice Call Set-up Test

Objective:
This test is done to measure the speed connection from calling party
(originating call) to the receiving party (terminating call).

Test Procedure:
¾ The tester is equipped with Agilent Drive Test tool (with pre-installed
WAMS software) and two 3G phones.
¾ Before starting the test, tester/s will note down the CID and the RSCP
(in dbm) of the serving Node B in the routes/areas to be tested. This will
be recorded in the Call Set-up Test Form.
¾ Time to be recorded is the numbers of seconds to establish the circuit
switched voice call.
¾ Tester/s will record the call set-up time in the call set-up Test form.
¾ For each route/area, it is recommended the testers conduct 10
repetitions to obtain more samples during the test.
¾ The specific test points will depend in the routes/area to be checked.

Expected Result:

Test Location: ______________ Cell ID: ____________


Phone Type ________________

Call Set-up Time RSSI (Rx LEV)


Trial
(seconds) (dbm)
Trial 1
Trial 2
Trial 3
Trial 4
Trial 5
Trial 6
Trial 7
Trial 8
Trial 9
Trial 10

6.2.4.2 Voice Call Quality Test

Objective:
¾ This test is done to check the call quality in the routes/areas to be
tested.

Test Procedure:
¾ The tester is equipped with Agilent Drive Test tool and two 3G
phones.
¾ One tester will make the call and the other tester will receive the call.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 106 of 177

¾ During the call in each test point, the tester will record the RSCP (in
dbm), Ec/Io in db, Tx Power in dB and CID. This will be recorded in
the Call Quality Test Form.
¾ For each route/area, it is recommended the testers conduct 10
repetitions to obtain more samples during the test.

Expected Result:

Test Location: ______________ Cell ID: ____________


Phone Type: _______________

RSCP Rx LEV Tx Power


Trial Ec/Io (db)
(dbm) (dbm)

Trial 1
Trial 2
Trial 3
Trial 4
Trial 5
Trial 6
Trial 7
Trial 8
Trial 9
Trial 10

6.2.4.3 SMS Test

Objective:

SMS test is used to measure the availability and performance of the SMS
service.

Test Procedure:
The test supports two types of configuration:
• One phone sends SMS to itself
¾ Before starting the test, the tester/s will record the CID of the
serving Node B in the routes/areas where the SMS will originate
and will be received.
¾ The tester will send a SMS to itself.
¾ The tester will record the Send Time, Receive Time, and Total
Time. This will be recorded in the SMS Test form.
¾ For each route/area, it is recommended the testers conduct 10
repetitions to obtain more samples during the test.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 107 of 177

Expected Result:

Test Location: ______________ Cell ID: ____________

Send Time Receive Total


Trial
(s) Time (s) Time (s)

Trial 1
Trial 2
Trial 3
Trial 4
Trial 5
Trial 6
Trial 7
Trial 8
Trial 9
Trial 10

Test Procedure:
• One phone sends SMS to another phone connected to the same
PC
¾ Before starting the test, the tester/s will record the CID of the
serving Node B in the routes/areas where the SMS will originate
and will be received.
¾ The tester will send a SMS to another phone connected to the
same PC.
¾ The tester will record the Send Time, Receive Time, and Total
Time. This will be recorded in the SMS Test form.
¾ For each route/area, it is recommended the testers conduct 10
repetitions to obtain more samples during the test.
Expected Result:
Test Location: ______________ Cell ID: ____________
Phone Type: _______________

Send Time Receive Total


Trial
(s) Time (s) Time (s)

Trial 1
Trial 2
Trial 3
Trial 4
Trial 5
Trial 6
Trial 7
Trial 8
Trial 9
Trial 10

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 108 of 177

6.2.4.4 MMS Test

Objective:
The MMS test is used to measure the availability and performance of a MMS
service. The test currently supports MMS transactions over the WAP.

Test Procedure:
MMS test must meet the following criteria.
ƒ Phone SIMs should be MMS capable
ƒ Test SIMs should be GPRS enable

¾ Before starting the test, the tester/s will record the CID of the
serving Node B in the routes/areas where the MMS will
originate and will be received.
¾ The tester will send a MMS to another phone connected to the
same PC.
¾ The tester will record the Tx Upload Time, Tx Upload Rate, Rx
Download Time, Rx Download Rate, and Total Test Time. This
will be recorded in the MMS Test form.
¾ For each route/area, it is recommended the testers conduct 3
repetitions to obtain more samples during the test.

Expected Result:

Test Location: ______________ Cell ID: ____________


Phone Type: _______________

Tx Upload Tx Upload Rx Upload Rx Upload Total Test


Trial
Time (s) Rate (s) Time (s) Rate (s) Time(s)
Trial 1
Trial 2
Trial 3

6.2.4.5 WAP Test


Objective:

WAP test is an important test in the mobile environment due to widespread use
of WAP-based technology. The WAP test downloads a web page from a server
in a manner similar to a WAP browser. However, the WAP test differs from a
browser because the test takes measurements that are indicators of QoS
provided by a WAP service.

Test Procedure:
• Test SIMs should be GPRS enable
¾ Before starting the test, the tester/s will record the CID of the serving
Node B in the routes/areas where the WAP test will originate and will be
received.
¾ Tester A to connect and browse the WAP page for 5 minutes.
¾ Web address to be typed would be: http://www.suncellular.com.ph
¾ The tester will record the Total Response Time, Gateway connect Time,
Data Transfer Time and Gateway Disconnect Time. This will be
recorded in the WAP Test form.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 109 of 177

Expected Result:

Test Location: ______________ Cell ID: ____________


Phone Type: _______________

Total Gateway Data Gateway


Trial Response Connect Transfer Disconnect
Time (s) Time (s) Time (s) Time (s)
Trial 1
Trial 2
Trial 3

B. Whole Network

The testers will perform the tests indicated in sections 6.2.4.1 to 6.2.4.6 using a drive
test tool. The results will be plotted and also tabulated.

6.2.4.6 HSDPA

Objective:
These tests are done to measure the throughput and download time using
HSDPA.

A. Stationary and Good Coverage

Procedure:
¾ Tester will stay on one site with good coverage.
¾ Tester A will use Laptop to be connected to the internet using 3G HSDPA
data card.
¾ Freeware software for measuring throughput is loaded on the laptop.
¾ Tester A will then access http://www.microsoft.com
¾ On the download page, click Home & Office and the Office XP Service
Pack 3 (SP3) file will be accessed.
¾ Tester will be prompted to save.
¾ Record the Average and Maximum Throughput (Kbps) and download
time.

Test Location: ______________ Cell ID: ____________


HSDPA Card Type: _______________

Throughput (kbps) Download


Trial
Average Maximum Time
Trial 1
Trial 2
Trial 3
Trial 4

B. Stationary and Bad Coverage

Procedure:
¾ Tester will stay at one site with bad coverage (edge of cell).
¾ Tester A will use Laptop to be connected to the internet using 3G HSDPA
data card.
¾ Freeware software for measuring throughput is loaded on the laptop.
¾ Tester A will then access http://www.microsoft.com

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 110 of 177

¾ On the download page, click Home & Office and the Office XP Service
Pack 3 (SP3) file will be accessed.
¾ Tester will be prompted to save.
¾ Record the Average and Maximum Throughput (Kbps) and download
time.
Test Location: ______________ Cell ID: ____________
HSDPA Card Type: _______________

Throughput (kbps) Download


Trial
Average Maximum Time
Trial 1
Trial 2
Trial 3
Trial 4

C. Mobile

Procedure:
¾ Tester will use a HSDPA drive test tool for mobility or a Laptop to be
connected to the internet using 3G HSDPA data card. Tester needs to be
mobile.
¾ Freeware software for measuring throughput is loaded on the laptop.
¾ Tester A will then access http://www.microsoft.com
¾ On the download page, click Home & Office and the Office XP Service
Pack 3 (SP3) file will be accessed.
¾ Tester will be prompted to save.
¾ Record the Average and Maximum Throughput (Kbps) and download
time.

Throughput (kbps) Download


Trial
Average Maximum Time
Trial 1
Trial 2
Trial 3
Trial 4

D. Ping Tests
¾ Tester will use a Laptop to be connected to the internet using 3G HSDPA
data card.
¾ Ping http://www.microsoft.com website for a duration of 5 minutes
¾ Record the Average and Maximum Latency/Delay for byte sizes of 32,
256, and 1024 bytes.

Latency/Delay (seconds) Accepted


Trial
Average Maximum Value
32 Bytes 70 ms
256 Bytes 70 ms
1024 Bytes 70 ms

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 111 of 177

6.2.5 KEY PERFORMANCE INDICATOR (KPIs)

The basic principle for the network performance shall be that the Supplier maintains the
KPI levels of the trial network, and thereafter continuously strive in order to meet
increasingly stringent Service Level requirement for the demo.

The Key Performance Indicator (KPIs) defined below shall be achieved and verified by
the OSS of the vendor. The KPIs shall be achieved in all areas fulfilling the radio
coverage conditions.

Objective:
This assessment is used to verify that the 3G KPIs satisfy the specified
threshold for each KPIs.

Test Procedure:
¾ The monitoring tool of the vendor should be working.
¾ The vendor shall indicate the formulas for each of the KPIs based on
their counters.
¾ The statistics used for the computation shall be good for at least a week
of monitoring.
¾ The vendor shall gather the statistics and determine the results, with the
help of DMPI.

Expected Result:

Test Location: ______________ Cell ID: ____________

Service bearer KPI Threshold Test Results


Call Setup Success Rate 96%
Voice Call
Call Drop Rate 3%
Call Setup Success Rate 96%
Video Call
Call Drop Rate 3%
Call Setup Success Rate 96%
Call Drop Rate 3%
PS (GPRS)
Throughput 90% of the Max RAB
throughput
Call Setup Success Rate 96%
Call Drop Rate 3%
HSDPA
Throughput Average to be
proposed by supplier
3G to 3G Handover
Handover
Success Rate
2G to 3G Handover
Handover
Success Rate

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 112 of 177

6.3 IOT Tests

This document is used as a reference for testing the 3G and 2G interoperability services
on the trial network of the different vendors.

The results will be used for the evaluation of the performance of the 3G and 2G
interoperability services for the purpose of recommendation of appropriate vendor that
can provide the 3G infrastructure and services suitable to DMPI’s existing mobile
network.

This document describes the test specifications that are relevant to perform on the 3G
trial system. The feasibility of most of the tests cases rely on the 3G set-up (3G
Equipment under trial) of the vendor and the availability of the 2G test bed.
Interoperability testing is a way of securing interworking of equipment from different
vendors. This will also assess the commitments to open standards and natural next
phase in the UMTS standardization work and to determine how competent the offered
technology in 2G / 3G radio network, as well as circuit and packet – switch networks,
and the uniqueness end-to-end solution.

6.3.1 Objectives

The objectives of the IOT tests are:

- To be aware of interoperability problems that may arise in a mixed 2G /


3G network environment.

- To understand the requirement and restrictions imposed on a dual mode


(2G / 3G) terminal in terms of Signaling, Measurements, Mobility
management and Call handling.
ƒ Adoption of UTRAN protocols and interfaces in GSM/EDGE
Radio Access Network - GERAN (e.g. PDCP, RRC, Iu and Iur-g).
ƒ Adoption of the UTRAN bearer concepts in GERAN (RABs, Radio
bearers and flexible layer one).

- To understand how Quality of Service (QoS) and security issues are


handled for CS and PS service when handover take place between 2G
and 3G networks.
ƒ 2G vs. 3G QoS mechanism for CS and PS services (negotiation,
parameter, limitations, etc.)
ƒ Signaling flows for handover UTRAN to/from GSM BSS, including
failed handover cases, for CS and PS services.
ƒ System Information parameter for controlling the cell re-selection
and reporting behavior of the UE in a mixed 2G/3G environment
are examined.

- To have an understanding of the signaling flows needed to perform


2G/3G handovers.

- To verify ME / SIM Capabilities


ƒ Selection of PLMN and radio access technology (RAT)
ƒ Provision / retrieval of Classmark information
ƒ Interaction between ME and SIM / USIM.

- To test different handover scenarios


ƒ Signaling flows for handover UTRAN to/from GSM BSS, including
failed handover cases, for CS and PS services.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 113 of 177

ƒ Handover related timers in MSC, SGSN, RAN, and MS / UE.


ƒ Impact of handover on specific CS services (e.g. Multimedia)
ƒ Impact of handover on QoS for PS connections.

- To test Core Network Interworking (During Handover)


ƒ Protocol conversion and fallback mechanism
ƒ Forwarding (and buffering) of data between CN nodes.
ƒ Distribution of classmark information between CN nodes.
ƒ Mapping between 2G and 3G QoS parameter

6.3.2 SAMPLE 3G TRIAL NETWORK SETUP FOR IOT

In order to test 2G to 3G interoperability, there should be overlapping 2G and


3G coverage in one area. The 2G network used for the trial will be either the
DMPI 2G test bed located at Libis or the vendor’s 2G test network. The set-up
will be discussed and agreed upon by DMPI and the vendor.

6.3.3 Equipment and Tools


An independent vendor (Agilent) with the capability to test the mixed
network would be appropriate for verifying the performance of each and
every 3G vendor participant to inhibit predisposition.

All test equipment and tools that will be used for measurement and testing
for trial, which is commercially available from the vendor’s product list,
should not be included as basis to gather information, results, and
verifications for DMPI 3G personnel. In case that the protocol analyzer of
the independent vendor is not available, the vendor may provide their
recommended protocol analyzer.

The list of tools needed for the IOT is:

1. Drive-test tool (3G capable)


2. Signaling Advisor (3G capable)
3. 3G capable test phones
4. 2G capable test phones
5. SIM and USIM cards

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 114 of 177

6.3.4 General Test Guidelines and Procedures

DMPI engineer will assist the engineer of a particular vendor at the 2G-3G
test site and during coverage verification.
Each participants in the trial testing should be given a 3G and 2G test
phones.
Handsets / Test phone already configured prior to test.
Things to be configured
Enable 3G mode on the phone
GPRS Settings
SMS/MMS Settings
Following service to be tested in using 3G handsets
Voice call
SMS
Video call
PS services (Web Browsing, Downloading, Multimedia Streaming and
MMS)

6.3.5 IOT Test Scenarios


The IOT test scenarios are indicated below.

6.3.5.1 3G2G Interoperability/Interworking Tests (Same Vendor)


The 3G2G interoperability/interworking tests are divided into 4 main
parts, namely:
• Basic Function
• Roaming
• Cell Reselection
• Handover

A. Basic Function
1. Voice call from GSM to WCDMA
Objective:
Test the function of the GSM to WCDMA speech call
Test Procedure:
¾ Subscriber A is a WCDMA user, and camp on WCDMA
network.
¾ Subscriber B is a GSM user, and camp on GSM network.
¾ Use a protocol analyzer to capture traces at the link connecting
3G to 2G.
¾ B initiates a voice call to A.
¾ A answers the call and keeps the call for 2 minutes.
¾ B hangs up.
Expected Result:
The call is correctly set-up. The voice is clear and call is released
normally.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 115 of 177

UE RNC MSC/VLR HLR 2G MSC

SEND_ROUTING_IN
PROVIDE_ROAMIN FORMATION_REQ
G_NUMBER_IND
PROVIDE_ROAMIN
G_NUMBER_RSP SEND_ROUTING_INF
ORMATION_CNF

PAGING IAM

PAGING_RESPONSE
COMMON_ID
AUTHENTICATION_REQUEST
AUTHENTICATION_RESPONSE
SECURITY_MODE_COMMAND
SECURITY_MODE_COMPLETE
SETUP

CALL_CONFIRMED
RAB_ASSIGNMENT_REQUEST

RAB_ASSIGNMENT_RESPONSE
ALERTING
ACM
CONNECT
ANM
CONNECT_ACKNOWLEDGE

DISCONNECT
REL
RELEASE
RLC
RELEASE_COMPLETE
IU_RELEASE_COMMAND
IU_RELEASE_COMPLETE

2. Voice call from WCDMA to GSM


Objective:
Test the function of the WCDMA to GSM speech call
Test Procedure:
¾ Subscriber A is a WCDMA user, and camp on WCDMA
network.
¾ Subscriber B is a GSM user, and camp on GSM network.
¾ Use a protocol analyzer to capture traces at the link connecting
3G to 2G.
¾ A initiates a voice call to B.
¾ B answers the call and keeps the call for 2 minutes.
¾ B hangs up.
Expected Result:
The call is correctly set-up. The voice is clear and call is released
normally.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 116 of 177

UE1 RNC MSC/VLR 2G HLR 2G MSC

CM_SERVICE_REQUEST
COMMON_ID
AUTHENTICATION_REQUEST
AUTHENTICATION_RESPONSE
SECURITY_MODE_COMMAND
SECURITY_MODE_COMPLETE
SETUP SEND_ROUTING_I
PROVIDE_ROAMIN
NFORMATION_RE
CALL_PROCEEDING G_NUMBER_IND
Q

SEND_ROUTING_IN PROVIDE_ROAMIN
FORMATION_CNF G_NUMBER_RSP

RAB_ASSIGNMENT_REQUEST
RAB_ASSIGNMENT_RESPONSE
IAM

ACM
ALERTING
ANM
CONNECT

CONNECT_ACKNOWLEDGE

3. SMS from WCDMA to GSM


Objective:
Test the function of Short Message Service from WCDMA to GSM.
Test Procedure:
¾ UE A has registered the SMS service. Set the correct short
message center address in UE A.
¾ UE A has their locations updated successfully in VLR.
¾ Use a protocol analyzer to capture traces in MSC server or at
the link connecting 3G to 2G.
¾ UE A sends a short message “12345” to a GSM user.
¾ Check the traces.
Expected Result:
UE A can send the short message successfully.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 117 of 177

UEa RNC MSC/VLR SMC

CM_SERVICE_REQUEST

COMMON_ID
AUTHENTICATION_REQUEST
AUTHENTICATION_RESPONSE

SECURITY_MODE_COMMAND
SECURITY_MODE_COMPLETE

SMS_CP_DATA
SMS_CP_ACK
MAP_MO_FORWARD_SM
FORWARD_SHORT_MESSAGE_REQ
MAP_MO_FORWARD_SM
FORWARD_SHORT_MESSAGE_CNF
SMS_CP_DATA

SMS_CP_ACK

IU_RELEASE_COMMAND

IU_RELEASE_COMPLETE

4. SMS from GSM to WCDMA


Objective:
Test the function of Short Message Service (MT).
Test Procedure:
¾ UE A has registered the SMS service. Set the correct short
message center address in UE A.
¾ UE A has their locations updated successfully in VLR.
¾ Use a protocol analyzer to capture traces in MSC server or at
the link connecting 3G to 2G.
¾ A GSM user sends a short message “12345” to UE A.
¾ Check the traces.
Expected Result:
UE B can receive the short message successfully.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 118 of 177

UE A RNC MSC/VLR HLR SMC

MAP_SEND_ROUTING_INF
O_FOR_SM
MAP_SEND_ROUTING_INF
O_FOR_SM_ACK

MAP_MT_FORWARD_SM
FORWARD_SHORT_MESSAGE_IND
PAGING

PAGING_RESPONSE
COMMON_ID
AUTHENTICATION_REQUES
T
AUTHENTICATION_RESPONSE
SECURITY_MODE_COMMAND
SECURITY_MODE_COMPLETE
SMS_CP_DATA

SMS_CP_ACK
MAP_MT_FORWARD_SM
SMS_CP_DATA FORWARD_SHORT_MESSAGE_RSP
SMS_CP_ACK
IU_RELEASE_COMMAND

IU_RELEASE_COMPLETE

B. Roaming
1. CS Roaming from WCDMA to GSM
Objective:
Check whether UE can perform Inter-System roaming from
WCDMA to GSM.
Test Procedure:
¾ The GSM and WCDMA system are both configured correctly
and operate normally.
¾ The user of WCDMA is subscribed in HLR.
¾ The user can camp on WCDMA network, and now power off.
¾ Use a protocol analyzer to capture traces at the link connecting
3G to 2G or in HLR.
¾ UE supports dual mode, and power on in the area which has
only GSM coverage.
¾ Check and verify the correctness of signaling flow messages
from traces.
¾ Check that the current MSC/VLR number is a 2G MSC/VLR
number.
Expected Result:
The Location Area Updating request is accepted by the GSM
network and the UE is registered to GSM network.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 119 of 177

3G MSC/VLR 3G HLR 2G MSC/VLR BSC/MS

Send_authentication_info_req Location_Update req.

Send_authentication_info_respone Authentication_req.
Authentication_resp.
Update_Location
Cancel_Location

Cancel_Location ack Insert_Subscriber_data

Insert_Subscriber_data ack

Update_Location ack Security_mode_command


Security_mode_complete

Location_Update_Accept

2. CS Roaming from GSM to WCDMA


Objective:
Check whether UE can perform Inter-System roaming from GSM
to WCDMA.
Test Procedure:
¾ The GSM and WCDMA system are both configured correctly
and operate normally.
¾ The user of WCDMA is subscribed in HLR.
¾ The user can camp on GSM network, and now power off.
¾ Use a protocol analyzer to capture traces at the link connecting
3G to 2G or in HLR.
¾ UE supports dual mode, and power on in the area which has
only WCDMA coverage, or in the area which has stronger
WCDMA coverage than GSM.
¾ Check and verify the correctness of signaling flow messages
from traces.
¾ Check that the current MSC/VLR number is a 3G MSC/VLR
number.
¾ Check that the user’s state is “attach”.
Expected Result:
The Location Area Updating request is accepted by the WCDMA
network and the UE is registered to WCDMA network.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 120 of 177

2G MSC/VLR 3G HLR 3G MSC/VLR RNC/UE

Location_Update req.

Identity_req
Identity_resp.
Send_authentication_info_req
Send_authentication_info_respone Authentication_req.
Update_Location Authentication_resp.
Cancel_Location

Cancel_Location ack Insert_Subscriber_data

Insert_Subscriber_data ack

Update_Location ack Security_mode_command


Security_mode_complete

Location_Update_Accept

3. CS HPLMN selection from GSM to WCDMA


Objective:
Check whether UE can perform HPLMN selection from GSM to
WCDMA which has different PLMN.
Test Procedure:
¾ The GSM and WCDMA system are both configured correctly
and operate normally, and the PLMN are different.
¾ The user of WCDMA is subscribed in HLR.
¾ The user is camped on GSM network.
¾ Use a protocol analyzer to capture traces at the link connecting
3G to 2G or link to HLR.
¾ UE supports dual mode, and move to the area where the
WCDMA coverage is restored.
¾ Check and verify the correctness of signaling flow messages
from traces.
¾ Check that the current MSC/VLR number is a 3G MSC/VLR
number.
¾ Check that the user’s state is “attach”.
Expected Result:
The user send Location Area Updating request to 3G network,
and is accepted by the WCDMA network and the UE is registered
to WCDMA network.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 121 of 177

2G MSC/VLR 3G HLR 3G MSC/VLR RNC/UE

Location_Update req.

Identity_req
Identity_resp.
Send_authentication_info_req
Send_authentication_info_respone Authentication_req.
Update_Location Authentication_resp.
Cancel_Location

Cancel_Location ack Insert_Subscriber_data

Insert_Subscriber_data ack

Update_Location ack Security_mode_command


Security_mode_complete

Location_Update_Accept

4. PS Roaming from WCDMA to GPRS


Objective:
Check whether UE can perform Inter-System roaming from
WCDMA to GSM/GPRS.
Test Procedure:
¾ Cell 1 is in WCDMA and cell 2 is in GSM/GPRS.
¾ Verify that the MS has right subscription information in HLR.
¾ Use a protocol analyzer to capture traces at the link connecting
3G to SGSN.
¾ Power on UE and check that the MS is attached to WCDMA
network.
¾ Power off UE and check that the MS is detached to WCDMA
network.
¾ MS moves from Cell 1 to Cell 2. Power on UE.
¾ Verify that the MS is attached to GPRS network.
¾ Check that the user’s state is “attach”.
Expected Result:
The signaling messages flow is correct and there is no MS
information in 3G SGSN.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 122 of 177

MS 2G SGSN 3G SGSN HLR

Attach Request

Identif ication Request

Identif ication Response

Identity Request (Note 1)

Identity Response

Send Authentication Inf o (Note 2)

Send Authentication Inf o Ack

A uthentication and Ciphering Response (Note 3)

A uthentication and Ciphering Request

Update Location

Cancel Location

Cancel Location Ack

Insert Subscriber Data

Insert Subscriber Data Ack

Update Location A ck

Attach Accept

Attach Complete

Note 1: If New SGSN can't get IMSI from Old SGSN, it will get IMSI from MS.
Note 2: If the numb er of authentication sets is not enough, SGSN will initiate SendAuthenticationInfo procedure to get authentication sets.
Note 3: If the corresponding parameters of security function are configured, SGSN will initiate corresponding security procedure.

5. PS Roaming from GPRS to WCDMA


Objective:
Check whether UE can perform Inter-System roaming from
GSM/GPRS to WCDMA.
Test Procedure:
¾ Cell 1 is in WCDMA and cell 2 is in GSM/GPRS.
¾ Verify that the MS has right subscription information in HLR.
¾ Use a protocol analyzer to capture traces at the link connecting
3G to SGSN.
¾ Power on UE in cell 2 and check that the MS is attached to
GPRS network.
¾ Power off UE and check that the MS is detached from the
GPRS network.
¾ MS moves from Cell 2 to Cell 1. Power on UE.
¾ Verify that the MS is attached to the WCDMA network.
¾ Check that there is no MS information in 2G SGSN.
Expected Result:
The signaling messages flow is correct and there is no MS
information in 2G SGSN.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 123 of 177

MS RNC 3G SGSN 2G SGSN HLR

Attach Request

Identification Request

Identification Response

Identity Request (Note 1)

Identity Response

Send Authentication Info (Note 2)

Send Authentication Info Ack

Security Mode Command (Note 3)

Security Mode Command


Security Mode Complete

Security Mode Complete

Authentication and Ciphering Response (Note 3)

Authentication and Ciphering Request

Update Location

Cancel Location

Cancel Location Ack

Insert Subscriber Data

Insert Subscriber Data Ack

Update Location Ack

Attach Accept

Attach Complete

Note 1: If New SGSN can't get IMSI from Old SGSN, it will get IMSI from MS.
Note 2: If the number of authentication sets is not enough, SGSN will initiate SendAuthenticationInfo procedure to get authentication sets.
Note 3: If the corresponding parameters of security function are configured, SGSN will initiate corresponding security procedure.

6. PS HPLMN selection from GPRS to WCDMA


Objective:
Check whether UE can perform HPLMN selection from
GSM/GPRS to WCDMA which has different PLMN.
Test Procedure:
¾ Cell 1 is in WCDMA and cell 2 is in GSM/GPRS.
¾ Verify that the MS has right subscription information in HLR.
¾ Use a protocol analyzer to capture traces at the Iu, Gr, and Gn
interfaces.
¾ Power on UE in cell 2, and verify MS is attached to GPRS
network.
¾ MS moves from Cell 2 to Cell 1.
¾ Verify that the MS is attached to the WCDMA network.
¾ Check that there is no MS information in 2G SGSN.
Expected Result:
The signaling messages flow is correct and there is no MS
information in 2G SGSN.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 124 of 177

New Old
MS BSS SRNS GGSN HLR
3G-SGSN 2G-SGSN

Routeing Area Update Request

Common ID

SGSN Context Request

SGSN Context Response

Send Authentication Info (Note 1)

Send Authentication Info Ack

Authentication and Ciphering Request (Note 2)

Authentication and Ciphering Response

Security Mode Command

Security Mode Command

Security Mode Complete

Security Mode Complete

SGSN Context Acknowledge

Update GPRS Location

Cancel Location

Cancel Location Ack

Insert Subscriber Data

Insert Subscriber Data Ack

Update GPRS Location Ack

Routeing Area Update Accept

Routeing Area Update Complete

Note 1: If the number of authentication sets is not enough, SGSN will initiate SendAuthenticationInfo procedure to get authentication sets.
Note 2: If the corresponding parameters of security function are configured, SGSN will initiate corresponding security procedure.

C. Cell Reselection
1. CS Cell Reselection from WCDMA to GSM
Objective:
Check whether UE can perform cell reselection from WCDMA to
GSM.
Test Procedure:
¾ The GSM and WCDMA system are both configured correctly
and operate normally.
¾ The user of WCDMA is subscribed in HLR.
¾ The user can camp on WCDMA network.
¾ Use a protocol analyzer to capture traces at the link connecting
3G to 2G in HLR.
¾ UE supports dual mode, and move to the area where the GSM
coverage is stronger than WCDMA.
¾ Check and verify the correctness of signaling flow messages
from traces.
¾ Check that the current MSC/VLR number is a 2G MSC/VLR
number.
Expected Result:
The Location Area Updating request is accepted by the GSM
network and the UE is registered to GSM network.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 125 of 177

3G MSC/VLR 3G HLR 2G MSC/VLR BSC/MS

Send_authentication_info_req Location_Update req.

Send_authentication_info_respone Authentication_req.
Authentication_resp.
Update_Location
Cancel_Location

Cancel_Location ack Insert_Subscriber_data

Insert_Subscriber_data ack

Update_Location ack Security_mode_command


Security_mode_complete

Location_Update_Accept

2. CS Cell Reselection from GSM to WCDMA


Objective:
Check whether UE can perform cell reselection from GSM to
WCDMA.
Test Procedure:
¾ The GSM and WCDMA system are both configured correctly
and operate normally.
¾ The user of WCDMA is subscribed in HLR.
¾ The user can camp on GSM network.
¾ Use a protocol analyzer to capture traces at the link connecting
3G to 2G in HLR or links to HLR.
¾ UE supports dual mode, and move to the area where the
WCDMA coverage is stronger than GSM.
¾ Check and verify the correctness of signaling flow messages
from traces.
¾ Check that the current MSC/VLR number is a 3G MSC/VLR
number.
¾ Check that the user’s status is “Attached”.
Expected Result:
The user sends a Location Area Updating request to the 3G
network, and is accepted by the WCDMA network and, the UE is
registered to the WCDMA network.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 126 of 177

2G MSC/VLR 3G HLR 3G MSC/VLR RNC/UE

Location_Update req.

Identity_req
Identity_resp.
Send_authentication_info_req
Send_authentication_info_respone Authentication_req.
Update_Location Authentication_resp.
Cancel_Location

Cancel_Location ack Insert_Subscriber_data

Insert_Subscriber_data ack

Update_Location ack Security_mode_command


Security_mode_complete

Location_Update_Accept

3. PS Cell Reselection from WCDMA to GPRS


Objective:
Check whether UE can perform cell reselection from WCDMA to
GPRS.
Test Procedure:
¾ Cell 1 in WCDMA and Cell 2 in GSM/GPRS are configured as
adjacent cells in both systems.
¾ Verify that the MS has right subscription information in HLR.
¾ Use a protocol analyzer to capture traces at the link connecting
3G to SGSN.
¾ Power on UE and verify that the MS is attached to the WCDMA
network.
¾ MS moves from Cell 1 to Cell 2, and initiates Routing Area
Updating.
¾ Verify that MS is attached to 2G SGSN.
Expected Result:
The signaling message flow is correct and that the MS is attached
to 2G SGSN.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 127 of 177

New Old
MS BSS SRNS GGSN HLR
2G-SGSN 3G-SGSN

Routeing Area Update Request

SGSN Context Request

SGSN Context Response

Send Authentication Info (Note 1)

Send Authentication Info Ack

Authentication and Ciphering Request (Note 2)

Authentication and Ciphering Response

SGSN Context Acknowledge

Update GPRS Location

Cancel Location

Iu Release Command(Note 3)

Iu Release Complete

Cancel Location Ack

Insert Subscriber Data

Insert Subscriber Data Ack

Update GPRS Location Ack

Routeing Area Update Accept

Routeing Area Update Complete

Note 1: If the number of authentication sets is not enough, SGSN will initiate SendAuthenticationInfo procedure to get authentication sets.
Note 2: If the corresponding parameters of security function are configured, SGSN will initiate corresponding security procedure.

4. PS Cell Reselection from GPRS to WCDMA


Objective:
Check whether UE can perform cell reselection from GPRS to
WCDMA.
Test Procedure:
¾ Cell 1 in WCDMA and Cell 2 in GSM/GPRS are configured as
adjacent cells in both systems.
¾ Verify that the MS has right subscription information in HLR.
¾ Use a protocol analyzer to capture traces at the link connecting
3G to SGSN.
¾ Power on UE and verify that the MS is attached to the GPRS
network.
¾ MS moves from Cell 2 to Cell 1, and initiates Routing Area
Updating.
¾ Verify that MS is attached to 3G SGSN.
Expected Result:
The signaling message flow is correct and that the MS is attached
to 3G SGSN.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 128 of 177

New Old
MS BSS SRNS GGSN HLR
3G-SGSN 2G-SGSN

Routeing Area Update Request

Common ID

SGSN Context Request

SGSN Context Response

Send Authentication Info (Note 1)

Send Authentication Info Ack

Authentication and Ciphering Request (Note 2)

Authentication and Ciphering Response

Security Mode Command

Security Mode Command

Security Mode Complete

Security Mode Complete

SGSN Context Acknowledge

Update GPRS Location

Cancel Location

Cancel Location Ack

Insert Subscriber Data

Insert Subscriber Data Ack

Update GPRS Location Ack

Routeing Area Update Accept

Routeing Area Update Complete

Note 1: If the number of authentication sets is not enough, SGSN will initiate SendAuthenticationInfo procedure to get authentication sets.
Note 2: If the corresponding parameters of security function are configured, SGSN will initiate corresponding security procedure.

D. Handover
1. CS handover from WCDMA to GSM
Objective:
Check whether UE can perform Inter-System service handover
from WCDMA to GSM.
Test Procedure:
¾ The GSM and WCDMA system are both configured correctly
and operate normally.
¾ A WCDMA cell 1 and a GSM cell 2 are configured as adjacent
cell.
¾ UE is a dual-mode phone which can support both GSM and
WCDMA network.
¾ UE1 and UE2 camp on 3G network in Cell 1.
¾ Use a protocol analyzer to capture traces at the link connecting
3G to 2G in MSC Server and at the Uu and Iu interface in RNC.
¾ Establish a UE1 to UE2 voice call successfully.
¾ UE 1 moves away from Cell 1 to Cell 2 to trigger inter-system
handover from WCDMA to GSM.
¾ Check and verify the correctness of signaling flow messages
from traces.
Expected Result:
The voice call has not been affected during the handover
procedure.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 129 of 177

BSC 2G MSC 3G MSC RNC UE

PREPARE HANDOVER RELOCATION REQUIRED


HANDOVER REQUEST REQUEST

HANDOVER RESPONSE
ack. PREPARE HANDOVER
RESPONSE
IAM
ACM HANDOVER FROM
RELOCATION COMMAND
UTRAN COMMAND
HANDOVER DETECT PROCESS SIGNALLING

HANDOVER COMPLETE SEND END SIGNAL


ANM
IU RELEASE COMMAND
IU RELEASE COMPLETE

2. CS handover from GSM to WCDMA


Objective:
Check whether UE can perform Inter-System service handover
from GSM to WCDMA.
Test Procedure:
¾ The GSM and WCDMA system are both configured correctly
and operate normally. The GSM network can support handover
to WCDMA.
¾ A WCDMA cell 1 and a GSM cell 2 are configured as adjacent
cell.
¾ UE is a dual-mode phone which can support both GSM and
WCDMA network.
¾ UE1 and UE2 camp on 2G network in Cell 2.
¾ Use a protocol analyzer to capture traces at the link connecting
3G to 2G in MSC Server and at the Uu and Iu interface in RNC.
¾ Establish a UE1 to UE2 voice call successfully.
¾ UE 1 moves away from Cell 2 to Cell 1 to trigger inter-system
handover from GSM to WCDMA.
¾ Check and verify the correctness of signaling flow messages
from traces.
Expected Result:
The voice call has not been affected during the handover
procedure.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 130 of 177

RNC 3G MSC 2G MSC BSC UE

PREPARE HANDOVER HANDOVER REQUIRED


RELOCATION REQUEST REQUEST

RELOCATION
RESPONSE ack. PREPARE HANDOVER
RESPONSE
IAM
ACM
HANDOVER COMMAND HANDOVER COMMAND
RELOCATION DETECT PROCESS SIGNALLING
RELOCATION
SEND END SIGNAL
COMPLETE
ANM
RELEASE
RELEASE COMPLETE

3. PS handover in Cell_DCH from WCDMA to GPRS


Objective:
Check whether UE can perform Inter-System PS handover in
Cell_DCH mode from WCDMA to GPRS.
Test Procedure:
¾ Cell 1 in WCDMA and cell 2 in GSM/GPRS are configured as
adjacent cell in both system.
¾ Verify that the MS has right subscription information in HLR.
¾ Use a protocol analyzer to capture traces at the link connecting
3G to SGSN.
¾ Power on UE and verify that the MS is attached to the WCDMA
network.
¾ MS successfully activates a PDP context and starts data
transfer, such as downloads files, browses the website or uses
WAP service.
¾ Verify that the PDP state of the MS is Active.
¾ MS moves from Cell 1 to Cell 2, and initiates Routing Area
Updating.
¾ Check and verify the correctness of signaling flow messages
from traces.
¾ Verify the MS information in the 2G SGSN that the PDP Context
is Active and the data transfer is normal.
Expected Result:
The data session has not been affected during the handover
procedure.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 131 of 177

New Old
MS BSS SRNS GGSN HLR
2G-SGSN 3G-SGSN

Cell Change Order From UTRAN

Routeing Area Update Request

SGSN Context Request

SRNS Context Request

SRNS Context Response

SGSN Context Response

Send Authentication Info (Note 1)

Send Authentication Info Ack

Authentication and Ciphering Request (Note 2)

Authentication and Ciphering Response

SGSN Context Acknowledge

SRNS Data Forward Command

Forward Packets

Forward Packets

Update PDP Context Request

Update PDP Context Response

Update GPRS Location

Cancel Location

Iu Release Command

Iu Release Complete

Cancel Location Ack

Insert Subscriber Data

Insert Subscriber Data Ack

Update GPRS Location Ack

Routeing Area Update Accept

Routeing Area Update Complete

Note 1: If the number of authentication sets is not enough, SGSN will initiate SendAuthenticationInfo procedure to get authentication sets.
Note 2: If the corresponding parameters of security function are configured, SGSN will initiate corresponding security procedure.

4. PS handover in Cell_FACH from WCDMA to GPRS


Objective:
Check whether UE can perform Inter-System PS handover in
Cell_FACH mode from WCDMA to GPRS.
Test Procedure:
¾ Cell 1 in WCDMA and cell 2 in GSM/GPRS are configured as
adjacent cells in both systems.
¾ Verify that the MS has right subscription information in HLR.
¾ Use a protocol analyzer to capture traces at the Iu, Gr, and Gn
interfaces in 3G SGSN.
¾ Power on UE and verify that the MS is attached to the WCDMA
network.
¾ MS successfully activates a PDP context and starts data
transfer, such as downloads files, browses the website or uses
WAP service.
¾ Verify that the PDP state of the MS is Active.
¾ Stop data transfer for a while to trigger RRC state transition,
and UE will enter CELL_FACH mode.
¾ MS moves from Cell 1 to Cell 2, and initiates Routing Area
Updating.
¾ Check and verify the correctness of signaling flow messages
from traces.
¾ Verify the MS information in the 2G SGSN that the PDP Context
is Active and the data transfer is normal.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 132 of 177

Expected Result:
The data session has not been affected during the handover
procedure.
New Old
MS BSS SRNS GGSN HLR
2G-SGSN 3G-SGSN

Routeing Area Update Request

SGSN Context Request

SRNS Context Request

SRNS Context Response

SGSN Context Response

Send Authentication Info (Note 1)

Send Authentication Info Ack

Authentication and Ciphering Request (Note 2)

Authentication and Ciphering Response

SGSN Context Acknowledge

SRNS Data Forward Command

Forward Packets

Forward Packets

Update PDP Context Request

Update PDP Context Response

Update GPRS Location

Cancel Location

Iu Release Command

Iu Release Complete

Cancel Location Ack

Insert Subscriber Data

Insert Subscriber Data Ack

Update GPRS Location Ack

Routeing Area Update Accept

Routeing Area Update Complete

Note 1: If the number of authentication sets is not enough, SGSN will initiate SendAuthenticationInfo procedure to get authentication sets.
Note 2: If the corresponding parameters of security function are configured, SGSN will initiate corresponding security procedure.

5. PS handover from GPRS to WCDMA


Objective:
Check whether UE can perform Inter-System PS
handover/reselection from GPRS to WCDMA.
Test Procedure:
¾ Cell 1 in WCDMA and cell 2 in GSM/GPRS are configured as
adjacent cells in both systems.
¾ Verify that the MS has right subscription information in HLR.
¾ Use a protocol analyzer to capture traces at the link connecting
3G to SGSN.
¾ Power on UE and verify that the MS is attached to the GPRS
network.
¾ MS successfully activates a PDP context and starts data
transfer, such as downloads files, browses the website or uses
WAP service.
¾ Verify in 2G SGSN that the PDP state of the MS is Active.
¾ MS moves from Cell 1 to Cell 2, and initiates Routing Area
Updating.
¾ Check and verify the correctness of signaling flow messages
from traces.
¾ Verify that the MS is attached to 3G SGSN and that the MS
PDP Context is Active and the data transfer is normal.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 133 of 177

Expected Result:
The data session is still active and has not been affected during
the handover procedure.

New Old
MS BSS SRNS GGSN HLR
3G-SGSN 2G-SGSN

Routeing Area Update Request

Common ID

SGSN Context Request

SGSN Context Response

Send Authentication Info (Note 1)

Send Authentication Info Ack

Authentication and Ciphering Request (Note 2)

Authentication and Ciphering Response

Security Mode Command

Security Mode Command

Security Mode Complete

Security Mode Complete

SGSN Context Acknowledge


Forward Packets

Update PDP Context Request

Update PDP Context Response

Update GPRS Location

Cancel Location

Cancel Location Ack

Insert Subscriber Data

Insert Subscriber Data Ack

Update GPRS Location Ack

Routeing Area Update Accept

Routeing Area Update Complete

Service Request

RAB Assignment Request

RB Setup

RB Setup Complete
RAB Assignment Response

Note 1: If the number of authentication sets is not enough, SGSN will initiate SendAuthenticationInfo procedure to get authentication sets.
Note 2: If the corresponding parameters of security function are configured, SGSN will initiate corresponding security procedure.

6. CS+PS handover from WCDMA to GSM/GPRS


Objective:
Check whether UE can perform Inter-System PS+CS handover
from WCDMA to GSM/GPRS.
Test Procedure:
¾ The GSM/GPRS and WDCMA system are both configured
correctly and operate normally.
¾ A WCDMA cell 1 and a GSM/GPRS cell 2 are configured as
adjacent cell.
¾ UE1 and UE 2 are dual-mode phones which can support both
GSM/GPRS and WCDMA network.
¾ UE1 and UE2 camp on 3G network in Cell 1.
¾ Use a protocol analyzer to capture traces at the link connecting
to 2G network in MSC Server and at Uu and Iu interfaces in
RNC.
¾ UE activates a PDP context and starts data transfer, such as
downloads files, browses a website or uses WAP service.
¾ Establish a UE1 to UE2 voice call successfully.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 134 of 177

¾ UE moves away from Cell 1 to Cell 2 to trigger inter-system


handover from WCDMA to GSM.
¾ Check and verify the correctness of signaling flow messages
from traces.
¾ UE ends the call.
Expected Result:
The UE data transfer and voice calls are normal and are not
affected by the handover procedure. After the voice call is ended,
the data transfer is recovered.

BSC 2G MSC 3G MSC RNC UE

PREPARE HANDOVER RELOCATION REQUIRED


HANDOVER REQUEST REQUEST

HANDOVER RESPONSE
ack. PREPARE HANDOVER
RESPONSE
IAM
ACM HANDOVER FROM
RELOCATION COMMAND
UTRAN COMMAND
HANDOVER DETECT PROCESS SIGNALLING

HANDOVER COMPLETE SEND END SIGNAL


ANM
IU RELEASE COMMAND
IU RELEASE COMPLETE

7. Video Call handover from WCDMA to GSM/GPRS


Objective:
Check whether UE can perform Inter-System Video Call handover
from WCDMA to GSM/GPRS.
Test Procedure:
¾ The GSM/GPRS and WDCMA system are both configured
correctly and operate normally.
¾ A WCDMA cell 1 and a GSM/GPRS cell 2 are configured as
adjacent cell.
¾ UE1 and UE 2 are dual-mode phones which can support both
GSM/GPRS and WCDMA network.
¾ UE1 and UE2 camp on 3G network in Cell 1.
¾ Use a protocol analyzer to capture traces at the link connecting
to 2G network in MSC Server and at Uu and Iu interfaces in
RNC.
¾ UE1 initiates a video call to UE2.
¾ The video call session is normal.
¾ UE1 moves away from Cell 1 to Cell 2 to trigger inter-system
handover from WCDMA to GSM.
¾ Check and verify the correctness of signaling flow messages
from traces.
Expected Result:
The video call drops when UE1 moves from Cell 1 to Cell 2.

8. Reachability Test
Objective:
Check whether UE can be reached after moving from WCDMA to
GSM.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 135 of 177

Test Procedure:
¾ The GSM and WCDMA system are both configured correctly
and operate normally.
¾ A WCDMA cell 1 and a GSM cell 2 are configured as adjacent
cell.
¾ UE is a dual-mode phone which can support both GSM and
WCDMA network.
¾ UE1 camp on 3G network in Cell 1.
¾ UE1 moves from 3G network to 2G network.
¾ Phone is now camped to 2G network.
¾ UE2 sends SMS to UE1.
¾ UE2 calls UE1
Expected Result:
The SMS was received by UE1 and UE1 can be reached by UE1.

6.3.5.2 3G2G Interoperability/Interworking Tests (Different Vendors)


There is also a need to verify if DMPI’s existing 2G network can work
well with the different vendors 3G equipment.

The different scenarios that DMPI would like to test are:


• Huawei’s 2G network to Vendor B’s 3G network
• Huawei’s 2G network to Vendor C’s 3G network
• Ericsson’s 2G network to Vendor A’s 3G network
• Ericsson’s 2G network to Vendor C’s 3G network.

The test cases will be similar to Section 6.3.5.3.

6.3.5.3 3G3G Interoperability/Interworking Tests (Different Vendors)


It is also very important to test interoperability between different
vendors. The feasibility of these tests needs cooperation and
coordination with the different vendors.

The scenarios that DMPI would like to test are:


• Vendor A Node B to Vendor B RNC
• Vendor A Node B to Vendor C RNC
• Vendor B Node B to Vendor A RNC
• Vendor B Node B to Vendor C RNC
• Vendor C Node B to Vendor A RNC
• Vendor C Node B to Vendor B RNC
• Vendor A RNC to Vendor B RNC
• Vendor A RNC to Vendor C RNC
• Vendor B RNC to Vendor C RNC

The test cases should be agreed upon by both vendors.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 136 of 177

APPENDIX

A. NETWORK ELEMENTS INFORMATION

Network
HW Version Software Version
Element

Node B

RNC
SGSN
GGSN
HLR
SMSC
MMSC
BTS
MSC
MGW

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 137 of 177

B. TEST RESULTS

Test Category Test Item Expected Results

CS TESTING IMSI attach in same service Test the function of IMSI attach in □ Passed
area (SA) one SA. □ Failed
A. Mobility □ Untested
Management

IMSI Attach IMSI attach in different Test the function of IMSI attach in □ Passed
service area (SA) a different SA. □ Failed
□ Untested

Location Update MS location updates with Test the function of MS location □ Passed
IMSI updates with IMSI □ Failed
□ Untested

Periodic location update Test the function of Periodic □ Passed


location update □ Failed
□ Untested

IMSI Detach MS location updates with Test the function of IMSI Detach □ Passed
IMSI □ Failed
□ Untested

Implicit IMSI detach Test the function of Implicit IMSI □ Passed


Detach □ Failed
□ Untested

Authentication UE authentication in RNC Test the function of authentication □ Passed


serving area in updating process in updating location □ Failed
location □ Untested

Ciphering Ciphering in location update Test the function of ciphering □ Passed


process in updating location □ Failed
□ Untested

Ciphering in subscriber’s Test the function of ciphering □ Passed


MOC/MTC process in call processing □ Failed
□ Untested

Location Update IMSI unknown in HLR Test the function of location □ Passed
Fail update but IMSI unknown in HLR □ Failed
□ Untested

Roaming restrict Test the function of roaming □ Passed


restrict □ Failed
□ Untested

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 138 of 177

B. Basic Service Mobile to Mobile Speech Call Test the function mobile to mobile □ Passed
speech call □ Failed
Mobile to Mobile □ Untested
Speech Call

Voice calls with 8 AMR Test the function of Voice Calls □ Passed
with 8 AMR Code □ Failed
□ Untested

TrFO function in 3G End Test the function of TrFO in 3G □ Passed


Office End Office □ Failed
□ Untested

Speech Call Mobile to PSTN Speech Call Test the function of mobile to □ Passed
between Mobile PSTN speech call □ Failed
and PSTN □ Untested

Mobile to PSTN Speech Call, Test the function of DTMF □ Passed


UE sending DTMF □ Failed
□ Untested

Mobile to PSTN, more than 15 Test the function that the MSC can □ Passed
digits handle dialing a PSTN number □ Failed
with more than 15 digits □ Untested

PSTN to Mobile speech call Test the function of PSTN to □ Passed


Mobile speech call □ Failed
□ Untested

PSTN to Mobile speech call Test the function of echo □ Passed


with Echo Cancellation cancellation □ Failed
□ Untested

Video Call Mobile to Mobile Video Call Test the function of Mobile to □ Passed
Mobile video call □ Failed
□ Untested

Special Service Emergency call (no USIM Test the function of Emergency □ Passed
Call inside UE) Call □ Failed
□ Untested

Emergency call (USIM inside Test the function of Emergency □ Passed


UE) Call □ Failed
□ Untested

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 139 of 177

Short Message Short Message Service (MO) Test the function of Short Message □ Passed
Service Service (MO) □ Failed
□ Untested

Short Message Service (MT) Test the function of Short Message □ Passed
Service (MT) □ Failed
□ Untested

Mobile can receive SMMT Test the function of Mobile receive □ Passed
during speech call SMMT during speech call □ Failed
□ Untested

Mobile can receive SMMT Test the function of Mobile receive □ Passed
during video call SMMT during video call □ Failed
□ Untested

SMMT to a UE, out of Test the function that UE B can □ Passed


coverage receive short message sent by UE □ Failed
A during B’s out of coverage after □ Untested
returning to the service area

SMMT to a detached UE, UE Test the function of that after □ Passed


can receive SMS when switching on the mobile phone, UE □ Failed
switched on the mobile B can receive the short message □ Untested
sent by UE A when B’s mobile
phone is switched off

SMMT to a memory full UE, Test the function of that UE B can □ Passed
UE can receive SMS memory receive short messages when there □ Failed
not full is free memory again □ Untested

Call Failure Mobile Terminating Call, the Test the function of Call Failure □ Passed
Processing UE is busy Processing when the called UE is □ Failed
busy □ Untested

Mobile Terminating Call, the Test the function of Call Failure □ Passed
UE does not answer Processing when the called UE □ Failed
does not answer □ Untested

Mobile Terminating Call, the Test the function of Call Failure □ Passed
UE is out of coverage Processing when the called UE □ Failed
does not answer □ Untested

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 140 of 177

Mobile Terminating Call, the Test the function of Call Failure □ Passed
UE is switched off Processing when the called UE is □ Failed
powered off □ Untested

Mobile Terminating Call, the Test the function of Call Failure □ Passed
UE is NULL Processing when the called UE □ Failed
number is NULL □ Untested

C. Supplementary Call Forwarding Test the function of Call □ Passed


Service Unconditional Forwarding Unconditional □ Failed
□ Untested
Call Forwarding

Call Forwarding on Mobile Test the function of Call □ Passed


Subscriber Busy Forwarding on Busy □ Failed
□ Untested

Call Forwarding on No Reply Test the function of Call □ Passed


Forwarding on No Reply □ Failed
□ Untested

Call Forwarding on Mobile Test the function of Call □ Passed


Subscriber Not Reachable Forwarding on Mobile Subscriber □ Failed
Not Reachable □ Untested

Call Forwarding notification Test the function of Call □ Passed


to A-party and B-party Forwarding notification to party A □ Failed
and party B □ Untested

Call Forwarding Test the function of Call □ Passed


activation/interrogation/ Forwarding □ Failed
deactivation activation/interrogation/ □ Untested
deactivation

Call Forwarding Call Forwarding Unconditional Test the function of Call □ Passed
for Video Call for Video Call Forwarding for Video Call □ Failed
□ Untested

Call Forwarding on Mobile Test the function of Call □ Passed


Subscriber Busy for Video Forwarding for video call □ Failed
Call □ Untested

Call Forwarding on No Reply Test the function of Call □ Passed


for Video Call Forwarding for Video Call on No □ Failed
Reply □ Untested

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 141 of 177

Call Forwarding on Mobile Test the function of Call □ Passed


Subscriber Not Reachable for Forwarding on Mobile Subscriber □ Failed
Video Call Not Reachable □ Untested

Call Barring Barring of All Outgoing Calls Test the function of Barring of All □ Passed
Outgoing Calls □ Failed
□ Untested

Barring of All Incoming Calls Test the function of Barring of All □ Passed
Incoming Calls □ Failed
□ Untested

Call Barring Test the function of call barring □ Passed


activation/interrogation/ activation/interrogation/ □ Failed
deactivation deactivation □ Untested

Call Barring for Barring of All Outgoing Calls Test the function of Barring of All □ Passed
Video Call for Video Call Outgoing Calls for Video Call □ Failed
□ Untested

Barring of All Incoming Calls Test the function of Barring of All □ Passed
for Video Call Incoming Calls for Video Call □ Failed
□ Untested

Call Barring for Barring of All Outgoing Calls Test the function of Barring of All □ Passed
SMS for SMS Outgoing Calls for SMS □ Failed
□ Untested

Barring of All Incoming Calls Test the function of Barring of All □ Passed
for SMS Incoming Calls for SMS □ Failed
□ Untested

Number MS subscribe CLIR Test the function of MS subscribe □ Passed


Identification CLIR □ Failed
□ Untested

Only subscribe CLIP Test the function of only subscribe □ Passed


CLIP □ Failed
□ Untested

Call Completion Call Hold Test the function of Call Hold □ Passed
□ Failed
□ Untested

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 142 of 177

Call Waiting Test the function of Call Waiting □ Passed


□ Failed
□ Untested

Multiple Call Hold Swapping Test the function of multiple call □ Passed
hold swapping □ Failed
□ Untested

SMMO can be initiated by MS Test the function of multiple call □ Passed


who currently holds a call hold swapping □ Failed
□ Untested

Multiparty Six-Way Service Test the function of six-way □ Passed


Service multiparty service □ Failed
□ Untested

D. CS Domain Bill of MOC Test the function of Bill of MOC □ Passed


Charging (CDR) □ Failed
□ Untested
CDR Generating

Bill of MTC Test the function of Bill of MTC □ Passed


□ Failed
□ Untested

Bill of Call Forward Test the function of Bill of Call □ Passed


Forward □ Failed
□ Untested

Bill of Call Hold and Call Test the function of Bill of Call □ Passed
Wait Forward □ Failed
□ Untested

Bill of SMS (MO) Test the function of Bill of SMS □ Passed


(MO) □ Failed
□ Untested

Bill of SMS (MT) Test the function of Bill of SMS □ Passed


(MT) □ Failed
□ Untested

PS TESTING GPRS attach with IMSI Check if the network can □ Passed
successfully handle the GPRS □ Failed
A. Mobility attach originated by Normal □ Untested
Management Subscriber with IMSI

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 143 of 177

Attach GPRS attach with P-TMSI Check if the network can □ Passed
successfully handle the GPRS □ Fail
attach originated by Normal □ Untested
Subscriber with P-TMSI

GPRS attach, MS unknown in Check if the network can □ Passed


HLR successfully handle the GPRS □ Failed
attach originated by Unknown □ Untested
Subscriber

Detach MS initiated Detach Check if the network can □ Passed


successfully handle detach □ Failed
originated by Normal Subscriber □ Untested

SGSN initiated Detach- Check if the network can □ Passed


Implicit successfully handle detach Normal □ Failed
Subscriber implicitly □ Untested

Purge Purge Check if SGSN can successfully □ Passed


purge Normal Subscriber □ Failed
□ Untested

Routing Area Intra SGSN Routing Area Check if the network can □ Passed
Update Update successfully handle the Routing □ Failed
Area Update originated by normal □ Untested
subscriber

Periodic RA update Check if the network can □ Passed


successfully handle the periodic □ Failed
Routing Area Update □ Untested

Subscriber HLR modification of Check if SGSN can successfully □ Passed


Management subscriber data handle modification of subscriber □ Failed
data from HLR □ Untested

HLR deleting of subscriber Check if SGSN can successfully □ Passed


data handle deleting of subscriber data □ Failed
from HLR □ Untested

Security Authentication Check if the network can □ Passed


successfully implement □ Failed
authentication function □ Untested

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 144 of 177

Ciphering Check if the network can □ Passed


successfully implement ciphering □ Failed
function □ Untested

B. Session PDP Context Activation, Check if the network can □ Passed


Management transparent mode, static IP successfully handle the PDP □ Failed
address, GTP V1 context activation procedure □ Untested
PDP Context originated by normal subscriber
Activation with transparent mode and static IP
address

Multiple PDP contexts Check if the network can support □ Passed


multiple PDP contexts for □ Failed
subscriber □ Untested

PDP activation reject due to Check if the network can □ Passed


unknown APN successfully handle the PDP □ Failed
context activation procedure □ Untested
originated by normal subscriber
with unknown APN

PDP activation reject due to Check if the network can □ Passed


service not subscribed successfully handle the PDP □ Failed
context activation procedure □ Untested
originated by normal subscriber
with service not subscribed

PDP Context MS initiated PDP Context Check if the network can □ Passed
Deactivation Deactivation successfully handle the PDP □ Failed
context deactivation procedure □ Untested
originated by normal subscriber

GGSN initiated PDP Context Check if the operator can □ Passed


Deactivation successfully deactivate PDP □ Failed
context from GGSN □ Untested

SGSN initiated PDP Context Check if the SGSN can □ Passed


Deactivation successfully initiate PDP context □ Failed
deactivation □ Untested

APN Selection APN selection rule, No APN Check if the network can □ Passed
Rule in Activate PDP Context successfully select APN of PDP □ Failed
Request context when there is no APN in □ Untested
Activate PDP Context Request

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 145 of 177

APN selection rule, Wild Card Check if the network can □ Passed
successfully select APN of PDP □ Failed
context when MS subscribes a □ Untested
PDP context of wild card

APN selection rule, MS send Check if the network can □ Passed


APN, APN NI included successfully select APN of PDP □ Failed
context when there is APN in □ Untested
Activate PDP Context Request,
APN NI included

APN selection rule, MS send Check if the network can □ Passed


APN in Mixed Case successfully select APN of PDP □ Failed
context when there is APN in □ Untested
Activate PDP Context Request,
APN in mixed case

GGSN Address GGSN address resolution by Check if the network can resolve □ Passed
Resolution DNS GGSN address by DNS □ Failed
□ Untested

C. Reliability and SGSN Gn interface Network Check if the SGSN Gn interface □ Passed
Stability Link Redundacy network link redundancy function □ Failed
is right □ Untested
Interface and
Link Redundancy
SGSN Ga interface Network Check if the SGSN Ga interface □ Passed
Link Redundancy network link redundancy function □ Failed
is right □ Untested

GGSN Gi interface Network Check if the GGSN Gi interface □ Passed


Link Redundancy network link redundancy function □ Failed
is right □ Untested

E2E stability test Check the stability of E2E □ Passed


performance □ Failed
□ Untested

Transfer Rate Uplink/Downlink transfer rate Check if the network can □ Passed
successfully handle the PDP □ Failed
context activation procedure □ Untested
originated by Normal Subscriber
with transparent mode and static IP
address

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 146 of 177

D. PS Domain M-CDR Generation Check if the SGSN can □ Passed


Charging successfully generate M-CDR and □ Failed
send it to CG after MS GPRS □ Untested
M-CDR detach
Generation

S-CDR S-CDR Generation Check if the SGSN can □ Passed


Generation successfully generate S-CDR and □ Failed
send it to CG after PDP □ Untested
deactivation

S-SMO-CDR and S-SMO-CDR and S-SMT- Check if the SGSN can □ Passed
S-SMT-CDR CDR Generation successfully generate S-SMO-CDR □ Failed
Generation and S-SMT-CDR and send it to □ Untested
CG

G-CDR G-CDR Generation Check if the GGSN can □ Passed


Generation successfully generate G-CDR and □ Failed
send it to CG after PDP □ Untested
deactivation

E. CG CDR Backup Check if the CG can back up the □ Passed


CDR files to the local disk □ Failed
CDR Backup □ Untested

CG Client CG Client Function – User Check if the CG can add user, □ Passed
Function Management delete user, modify user’s attribute □ Failed
and check user’s right □ Untested

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 147 of 177

RAN TESTING AMR Speech Service (12.2k) Test the function of bearing AMR □ Passed
Speech service □ Failed
A. Bearer Capability □ Untested
Test

Service Bearing AMR Speech Service (10.2K) Test the function of bearing AMR □ Passed
CS Domain Speech service □ Failed
□ Untested

AMR Speech Service (4.5K) Test the function of bearing AMR □ Passed
Speech service □ Failed
□ Untested

CS Transparent Data Service Test the function of bearing CS □ Passed


transparent data service □ Failed
□ Untested

Service Bearing PS Data Service Test the function of bearing PS □ Passed


PS Domain (uplink 64K + downlink 64K) data service (uplink 64K + □ Failed
downlink 64K) □ Untested

PS Data Service Test the function of bearing PS □ Passed


(uplink 64K + downlink data service (uplink 64K + □ Failed
384K) downlink 384K) □ Untested

Combined PS Data Service Test the function of bearing 1 □ Passed


Service Bearing (uplink 64K + downlink 64K) AMR speech service (uplink 12.2 □ Failed
Kbps + downlink 12.2 Kbps) + 1 □ Untested
PS data service (uplink 64K +
downlink 384K)

1 CS Transparent Data Service Test the function of bearing 1 CS □ Passed


(uplink 64K + downlink 64K) transparent data service (uplink 64 □ Failed
+ 1 PS Data Service (uplink Kbps + downlink 64 Kbps) + 1 PS □ Untested
64K + downlink 144K) data service (uplink 64K +
downlink 144K)

SMS Service SMS Service on CS Bearing Test the SMS Service on CS □ Passed
Bearing Bearing □ Failed
□ Untested

SMS Service on PS Bearing Test the SMS Service on PS □ Passed


Bearing □ Failed
□ Untested

B. Mobility Page UE in Idle Mode Test the function of page UE in □ Passed


Management idle mode □ Failed
□ Untested
Paging

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 148 of 177

Page UE in CELL_DCH State Test the function of paging UE in □ Passed


CELL_DCH state □ Failed
□ Untested

Soft Handover AMR Speech Service Soft Test the function of soft handover □ Passed
Handover for AMR speech service □ Failed
□ Untested

Video Telephone Service Soft Test the function of soft handover □ Passed
Handover for video telephone service □ Failed
□ Untested

PS Service Soft Handover Test the function of soft handover □ Passed


for PS service □ Failed
□ Untested

Combined Service Soft Test the function of soft handover □ Passed


Handover for CS and PS combined service □ Failed
□ Untested

Hard Handover Intra-Frequency Hard Test the function of intra- □ Passed


Handover frequency hard handover □ Failed
□ Untested

Speech Service Inter- Test the function of inter- □ Passed


Frequency Hard Handover frequency hard handover for AMR □ Failed
speech service □ Untested

Video Telephone Inter- Test the function of inter- □ Passed


Frequency Hard Handover frequency hard handover for video □ Failed
telephone service □ Untested

PS Service Inter-Frequency Test the function of intra- □ Passed


Hard Handover frequency hard handover for PS □ Failed
service □ Untested

Combined Service Inter- Test the function of intra- □ Passed


Frequency Hard Handover frequency hard handover for CS □ Failed
and PS service □ Untested

Forward Cell Update Triggered by Cell Test the function of cell update □ Passed
Handover Reselection triggered by cell reselection □ Failed
□ Untested

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 149 of 177

C. Logical O&M Cell Setup Test the function of cell setup in □ Passed
Node B □ Failed
Logic Cell □ Untested

Cell Reconfiguration Test the function of cell □ Passed


reconfiguration in Node B □ Failed
□ Untested

Cell Deletion Test the function of cell deletion in □ Passed


Node B □ Failed
□ Untested

Cell Block Test the function of cell block □ Passed


□ Failed
□ Untested

Cell Unblock Test the function of cell unblock □ Passed


□ Failed
□ Untested

Common Transport Common Transport Channel Test the function of common □ Passed
Channel Setup transport channel setup in Node B □ Failed
□ Untested

Common Transport Channel Test the function of common □ Passed


Reconfiguration transport channel reconfiguration □ Failed
in Node B □ Untested

Common Transport Channel Test the function of common □ Passed


Reconfiguration transport channel deletion in Node □ Failed
B □ Untested

System System Information Update Test the function of system □ Passed


Information information update □ Failed
□ Untested

Resource Audit Cell Resource Audit Test the function of cell resource □ Passed
audit between RNC and Node B □ Failed
□ Untested

Tracing Uu Interface Tracing Test the function of Uu interface □ Passed


tracing □ Failed
□ Untested

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 150 of 177

Iub Interface Tracing Test the function of Iub interface □ Passed


tracing □ Failed
□ Untested

Iu Interface Tracing Test the function of Iu interface □ Passed


tracing □ Failed
□ Untested

Single User Tracing Test the function single user □ Passed


tracing □ Failed
□ Untested

D. Radio Resource CS Call Admission Control Test the function of CS call □ Passed
Management and admission control □ Failed
Control □ Untested

Admission
Control PS Call Admission Control Test the function of PS call □ Passed
admission control □ Failed
□ Untested

Congestion Congestion Control Test the function of cell congestion □ Passed


Control control □ Failed
□ Untested

Load Balancing Intra-frequency Load Test the function of intra- □ Passed


Control Balancing Control frequency load balancing □ Failed
□ Untested

Dynamic AMRC Test the function of AMRC □ Passed


Resource Control □ Failed
□ Untested

Dynamic Channel Test the function of AMRC □ Passed


Configuration – Rate □ Failed
Adjustment □ Untested

Dynamic Channel Test the state transition function of □ Passed


Configuration – State dynamic channel configuration □ Failed
Transition □ Untested

Power Control Uplink Outloop Power Control Test the function of uplink outloop □ Passed
power control □ Failed
□ Untested

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 151 of 177

Uplink Inner Loop Power Test the function of uplink inner □ Passed
Control loop power control □ Failed
□ Untested

Downlink Power Balancing Test the function of power □ Passed


balancing among DL radio link in □ Failed
soft handover □ Untested

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 152 of 177

SERVICES Authenticating the calling Authenticating the calling party □ Passed


party □ Failed
A. Short Message □ Untested
Services (SMS)

Authenticating
Subscriber

Accessing SMC MS-to-MS SMS MS-to-MS SMS □ Passed


□ Failed
□ Untested

Submitting and Storing Submitting and storing MS-to- Submitting and storing MS-to-MS □ Passed
SMs MS SMs short message □ Failed
□ Untested

Forwarding SMs Forwarding after receiving SM Forwarding after receiving SM □ Passed


prompt prompt □ Failed
□ Untested

Retrying forwarding SMs Retrying forwarding SMs □ Passed


automatically automatically □ Failed
□ Untested

Priority Processing Sending SMs of high priority Sending SMs of high priority first □ Passed
first □ Failed
□ Untested

Forwarding SMs of high Sending SMs of high priority high □ Passed


priority forcibly when MS is priority forcibly when MS is □ Failed
temporarily absent temporarily absent. □ Untested

Requesting Status Status report-forwarding Status report-forwarding □ Passed


Report notification (successful notification (successful □ Failed
forwarding). forwarding). □ Untested

Status report-unforwarding Status report-unforwarding □ Passed


notification (permanent notification (permanent failure). □ Failed
failure). □ Untested

Supporting SMs in Supporting SMs in English Supporting SMs in English □ Passed


English/Tagalog □ Failed
□ Untested

Supporting SMs in Tagalog. Supporting SMs in Tagalog. □ Passed


□ Failed
□ Untested

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 153 of 177

Supporting SMs in both Supporting SMs in both English □ Passed


English and Tagalog. and Tagalog. □ Failed
□ Untested

Supporting Long SMs Supporting long SMs of over Supporting long SMs of over 140 □ Passed
140 bytes bytes or 160 ASCII characters (7- □ Failed
bit code), 140 ASCII characters (8- □ Untested
bit code) or 70 dual-byte characters

Maintenance and Test Setting system parameters- Setting system parameters-OCOS □ Passed
Function setting country code and TCOS setting. □ Failed
. □ Untested

Setting system parameters- Setting system parameters- □ Passed


modifying the deleting mode modifying the deleting mode □ Failed
□ Untested

System resource monitor- System resource monitor-number □ Passed


number of SMs of SMs □ Failed
□ Untested

Querying SMs-querying SMs Querying SMs-querying SMs in □ Passed


in the SME the SME □ Failed
□ Untested

Querying SMs-querying SMs Querying SMs-querying SMs in □ Passed


in the memory the memory □ Failed
□ Untested

Querying SMs-querying SMs Querying SMs-querying SMs in □ Passed


in the database the database □ Failed
□ Untested

Account Management Account Management □ Passed


□ Failed
□ Untested

Interface Management Interface Management □ Passed


□ Failed
□ Untested

Database Module Database module function. Database module function. □ Passed


Functions □ Failed
□ Untested

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 154 of 177

License Configuration Reading legal license file Reading legal license file □ Passed
□ Failed
□ Untested

B .Multimedia MMS UA to MMS UA in the To test whether MMS can be □ Passed


Message Services Single MMSC (MM/DR/RR) retrieved immediately if they are □ Failed
(MMS) sent from MMS terminal 1 to □ Untested
MMS terminal 2 via the same
Basic Service Flows MMSC.

MMS UA to Email (MM/DR) To test sending MMS from an □ Passed


MMS terminal to an Email address □ Failed
through the MMSC. □ Untested

Email to MMS UA (MM) To test sending MMS from an □ Passed


MMS terminal to an Email address □ Failed
through the MMSC. □ Untested

Basic Features Multiple recipients To test sending MMS from MMS □ Passed
terminal 1 to MMS terminal 2, an □ Failed
Email account, or an ICP □ Untested
application through the MMSC

Validity Period To test the correctness of the □ Passed


validity period setting □ Failed
□ Untested

Specify the Earliest deliver To test sending MMS from MMS □ Passed
Time terminal 1 and Application to □ Failed
MMS terminal 2 through the □ Untested
MMSC at the specified time.

Maximum Number of To test the function of checking the □ Passed


Receptions number of recipients □ Failed
□ Untested

Auto provisioning and To test the functions of updating □ Passed


refreshing of subscriber the subscriber information in □ Failed
database □ Untested
automatically and auto
provisioning for new subscriber.

System-Level Blacklist To test whether the MMSC can □ Passed


deny MMS to or from the □ Failed
subscribers in □ Untested
the system-level blacklist.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 155 of 177

User-Level Blacklist To test whether the system □ Passed


supports the user-level blacklist □ Failed
□ Untested

Delivery Report, Terminal-to- To test whether the MMSC □ Passed


Terminal supports the terminal-to-terminal □ Failed
delivery report. □ Untested

Limit the MM message size at To test the function of limiting □ Passed


the MM1 interface. MM message size at the MM1 □ Failed
interface. □ Untested

Recipient number format To test the recipient number □ Passed


formats supported by the MMSC □ Failed
□ Untested

Traffic Control To test the traffic control function □ Passed


of the MMSC □ Failed
□ Untested

Terminal-to-Terminal To test the terminal-to-terminal □ Passed


Performance performance □ Failed
□ Untested

System Blacklist in MM3 To test System Blacklist function □ Passed


interface at the MM3 interface □ Failed
□ Untested

System Whitelist in MM3 To test System Whitelist function □ Passed


interface at the MM3 interface □ Failed
□ Untested

Limit the MM message size at To verify limiting the MM □ Passed


the MM3 interface message size function at the MM3 □ Failed
interface □ Untested

Service Deny for specified To test the services deny function □ Passed
Number Segment. for specified Number segment. □ Failed
□ Untested

Operation and Maintenance of user account To test the function of maintaining □ Passed
Maintenance privilege the user account privilege □ Failed
□ Untested

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 156 of 177

Maintenance of customer To test the function of maintaining □ Passed


management system operators the customer management system □ Failed
operators. □ Untested

Maintenance of System-Level To test whether the system-level □ Passed


Blacklisted Subscriber blacklisted subscriber can be □ Failed
managed and maintained through □ Untested
the customer management system.

Maintenance of UA Profile To test whether the user agent □ Passed


profile can be managed and □ Failed
maintained through the customer □ Untested
management system.

System Parameter To test whether the system □ Passed


Maintenance parameters can be maintained □ Failed
through the customer management □ Untested
system.

MMSC startup and shutdown To test whether MMS system is □ Passed


working completely □ Failed
□ Untested

Restart process when killed The test whether the Module of the □ Passed
MMMSC will start automatically □ Failed
when it killed □ Untested

C. Streaming Services Supporting the Flow of Media To verify that the video server □ Passed
Streams Played on Demand supports the media streams played □ Failed
Media Stream on on demand □ Untested
Demand Service

Supporting to Pause the To verify that the video server □ Passed


Streams Being Played on supports to pause the streams being □ Failed
Demand played on demand □ Untested

Supporting to Interrupt the To verify that the video server □ Passed


Streams Media Being Played supports to interrupt the streaming □ Failed
on Demand service. □ Untested

Supporting to Perform To verify that the video server □ Passed


Forward Query and Backward supports the forward query and □ Failed
Query Operations on the backward query operations on the □ Untested
Media Stream Being Played streaming service
on Demand

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 157 of 177

Supporting to Play Streams on To verify that the video server □ Passed


Demand Continuously supports to play streams on □ Failed
demand continuously for a long □ Untested
time.

Live Streaming Supporting the Live Streaming To verify that the video server □ Passed
Service Service Flow supports live streaming service. □ Failed
□ Untested

Supporting to Pause/Stop and To verify that the video server □ Passed


Continue the Live Streaming supports to pause/stop the live □ Failed
Service (Depends on the streaming service being played. □ Untested
handset)

Supporting to Receive To verify that the video server □ Passed


Multiple Live Streams from supports to receive multiple live □ Failed
the Encoder streams from the encoder. □ Untested

Supporting to Play Live To verify that the video server □ Passed


Streams Continuously supports to play live streams □ Failed
continuously. □ Untested

Supporting Encoding Supporting File Format of To verify that the video server □ Passed
3gp/mp4 supports play in 3gp/mp4 file □ Failed
format □ Untested

Supporting Video Encoding To verify that the video server □ Passed


Format of H.263/MPEG-4 supports H.263/MPEG-4 video □ Failed
encoding format. □ Untested

Supporting Audio Encoding To verify that the video server □ Passed


Format of AMR-NB/AAC-LC supports AMR-NB/AAC-LC audio □ Failed
encoding format. □ Untested

Supporting Conversion To verify that the video server □ Passed


Between Multiple Media File supports conversion of multiple □ Failed
Formats (avi, mpg, mp3) – media file formats. □ Untested
Live Stream Encoding

Supporting Export Type in To verify that the video server □ Passed


File Format of 3GP supports export type in 3GP file □ Failed
format □ Untested

Supporting Output of Audio To verify that the video server □ Passed


Only/Video Only supports output of audio □ Failed
only/video only □ Untested

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 158 of 177

Supporting Multiple Video To verify that the video server □ Passed


Encoding Format (MPEG-4, supports multiple video encoding □ Failed
H.263) formats □ Untested

Content Management Supporting to Published On- To verify the function of □ Passed


Function Demand Media Files to Video publishing on-demand media files □ Failed
servers to Video servers □ Untested

Supporting to Published Live To verify the function of □ Passed


Contents publishing on-demand media files □ Failed
to Video servers □ Untested

Supporting to Censor Contents To verify that the video server □ Passed


supports to censor the contents □ Failed
□ Untested

Supporting to Delete Media To verify that the video server □ Passed


File on the Streaming Server supports to delete the media file on □ Failed
the streaming server. □ Untested

Supporting to Delete Live To verify that the video server □ Passed


Content Files supports deletion of live content □ Failed
files □ Untested

CP Management Supporting Multiple Level To verify the video server supports □ Passed
Function Operators Function multiple level operators □ Failed
□ Untested

Managing To verify the video server supports □ Passed


(Adding/Deleting/Suspending/ management of the CP account □ Failed
Resuming) CP Account □ Untested

Security Management Supporting User Management To verify the video server supports □ Passed
Function (Adding/Deleting/Modify) User registration functions □ Failed
□ Untested

Security Management Supporting Application To verify the video server supports □ Passed
Function Startup/Stop startup/stop applications □ Failed
□ Untested

Supporting Database To verify the video server supports □ Passed


Startup/Stop startup/stop Database □ Failed
□ Untested

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 159 of 177

Supporting Configuration To verify the video server supports □ Passed


Backup and Restore configuration backup and restore □ Failed
□ Untested

Supporting Database Backup To verify the video server supports □ Passed


and Restore Database backup and restore □ Failed
□ Untested

Supporting Billing Supporting Generating CDR To verify that the CDR file can be □ Passed
Function generated □ Failed
□ Untested

Supporting Generating CDR Supporting the billing function in □ Passed


for Aborted Play case of aborted play. □ Failed
□ Untested

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 160 of 177

HSDPA Cell R99 UE Call To verify that HSDPA CELL UE


HSDPA Testing Establishment - DCH-PS R99 PS CALL □ Passed
ESTABLISHMENT □ Failed
A. RAB Mapping □ Untested

HSDPA Cell R99 UE Call To verify that HSDPA Cell UE


Establishment - DCH-CS R99 CS Call Establishment □ Passed
□ Failed
□ Untested

HSDPA Cell HSDPA UE Call To verify that HSDPA Cell UE


Establishment-Emergency Emergency Call Establishment □ Passed
□ Failed
□ Untested

HSDPA Cell HSDPA UE Call To verify that HSDPA Cell UE


Establishment-SMS SMS service. □ Passed
□ Failed
□ Untested

HSDPA Cell HSDPA UE To verify that HSDPA Cell UE


Call Establishment-H-PS HSDPA PS Call Establishment □ Passed
□ Failed
□ Untested

HSDPA to Multiservice- To verify that the system support


Multiservice AMR+HSDPA- CS+HSDPA PS Service □ Passed
PS □ Failed
□ Untested

HSDPA to Multiservice- To verify that the system support


Multiservice VP+HSDPA-PS VP+HSDPA PS Service □ Passed
□ Failed
□ Untested

HSDPA flexible power To verify that HSDPA flexible


B. Power Management allocation with fixed HS- power allocation algorithm could □ Passed
SCCH power, OCNS 25% use the remain power left by R99 □ Failed
load □ Untested

HSDPA flexible power To verify that HSDPA flexible


allocation with fixed HS- power allocation algorithm could □ Passed
SCCH power, OCNS 50% use the remain power left by R99 □ Failed
load □ Untested

HSDPA RNC controlled code To verify that HSDPA dynamic


C. Code Management allocation, R99 takes more code allocation algorithm is □ Passed
correct, when R99 user initiates the □ Failed
R99 service, the code resource will □ Untested
be occupied by R99.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 161 of 177

HSDPA RNC controlled code To verify that HSDPA dynamic


allocation, HSDPA takes more code allocation algorithm is □ Passed
correct, when R99 user terminates □ Failed
the R99 service, the code resource □ Untested
will be allocated for HSDPA.

HSDPA to HSDPA Mobility, To verify the HSDPA service to


D. Mobility Intra-RNC, Intra-NodeB, ensure continuity when intra- □ Passed
Intra- frequency frequency HS-DSCH cell change □ Failed
in the same NodeB does not □ Untested
necessarily leads to
reestablishment of HS-DSCH
carriers.
To verify that if the signaling
procedure is correct, check the
signaling plane time delay and user
plane time delay.
HSDPA to HSDPA Mobility, To verify the HSDPA service
Intra-RNC, Inter-frequency when inter-frequency HS-DSCH □ Passed
cell change in different NodeBs □ Failed
does not necessarily lead to □ Untested
reestablishment of HS-DSCH
carriers.
To verify that if the signaling
procedure is correct, check the
signaling plane time delay and user
plane time delay.
HSDPA to non HSDPA To verify that the RB carried by
Mobility, intra RNC,intra the HSDPA switches the service □ Passed
frequency from HSDSCH to DCH after the □ Failed
handover from HSDPA supportive □ Untested
cell to non HSDPA supportive cell.
To verify that if the signaling
procedure is correct, check the
signaling plane time delay and user
plane time delay.
HSDPA to non HSDPA To verify that the RB carried by
Mobility, Intra-RNC, Inter- the HSDPA switches the service □ Passed
frequency from HSDSCH to DCH after the □ Failed
handover from HSDPA supportive □ Untested
cell to non HSDPA supportive cell.
To verify that if the signaling
procedure is correct, check the
signaling plane time delay and user
plane time delay.
Non HSDPA to HSDPA To verify that the service is
Mobility, Intra-RNC, Intra- switched from the DCH to the □ Passed
frequency HSDSCH after the handover from □ Failed
non HSDPA supportive cell to □ Untested
HSDPA supportive cell.
To verify that if the signaling

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 162 of 177

procedure is correct, check the


signaling plane time delay and user
plane time delay.

Non HSDPA to HSDPA To verify that the RB carried by


Mobility, Intra-RNC, Inter- the HSDPA switches the service □ Passed
frequency from DCH to HS-DSCH after the □ Failed
handover from non HSDPA □ Untested
supportive cell to HSDPA
supportive cell.
To verify that if the signaling
procedure is correct, check the
signaling plane time delay and user
plane time delay.
HSDPA CAC To verify HSDPA Admission
E. Load Management Control function. □ Passed
□ Failed
□ Untested

IUB Efficiency for HSDPA 1 To verify Iub bandwidth utilization


F. Iub Flow Control E1 efficiency and user throughput vs. □ Passed
HSDPA users with extreme limited □ Failed
IUB configuration. □ Untested

IUB Efficiency for HSDPA To verify Iub bandwidth utilization


and R99,1 E1 efficiency with limited IUB □ Passed
configuration; and bandwidth □ Failed
allocation between HSDPA and □ Untested
R99 users.
HSDPA to FACH and to Idle To verify that the channel is
G. State Switch switched from HSDSCH to FACH □ Passed
when there is no traffic for the □ Failed
service set up over HSDSCH, and □ Untested
when PS Inactive detective timer
expired, switch to IDLE.
FACH to HSDPA To verify that burst traffic is
switched from FACH to HSDSCH. □ Passed
□ Failed
□ Untested

Ping Packet Delay Measure the ping packet delay at


H. RTT UE for ping sizes 32, 256 and 1024 □ Passed
bytes. The PS UL 64 kbps/PS DL □ Failed
HSDPA is used for this test. □ Untested

3*1 with 15 HS-PDSCH/cell To verify the capability of


I. Hardware Capacity HSDPA 3X1 with 15 HS- □ Passed
PDSCH/cell. □ Failed
□ Untested

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 163 of 177

The HSDPA and R99 mixed To verify that if the system could
cell sharing one carrier support the configuration of □ Passed
HSDPA and R99 mixed cell only □ Failed
occupy one carrier. □ Untested

Cell throughput in case of 5 To get Cell Peak Traffic over 5


J. Throughput HS-PDSCH, Category 12 UE, HS-PDSCHs, Category 12 UE, □ Passed
Capacity CDM4, CQI>16 CDM4 CQI>16. □ Failed
□ Untested

Cell throughput in case of 10 To get Cell Peak Traffic over 10


HS-PDSCH, Category 12 UE, HS-PDSCHs, Category 12 UE, □ Passed
CDM4, CQI>16 CDM4 CQI>16. □ Failed
□ Untested

Cell throughput in case of 14 To get Cell Peak Traffic over 14


HS-PDSCH, Category 12 UE, HS-PDSCHs, Category 12 UE, □ Passed
CDM4, CQI>16 CDM4 CQI>16. □ Failed
□ Untested

HSDPA System Reliability To verify the system reliability of


K. System Reliability holding traffic for long time □ Passed
□ Failed
□ Untested

Common measurement of To verify HSDPA cell common


L. Iub Standard HSDPA cell - transmitted measurement message follows the □ Passed
Interface carrier power of all codes not requirement of protocol. □ Failed
used for HS-PDSCH or HS- □ Untested
SCCH transmission

Common measurement of To verify HSDPA cell common


HSDPA Cell - HS-DSCH measurement message follows the □ Passed
required power measurement requirement of protocol. □ Failed
□ Untested

Common measurement of To verify HSDPA cell common


HSDPA Cell - HS-DSCH measurement message follows the □ Passed
provided bit rate measurement requirement of protocol. □ Failed
□ Untested

HSDPA cell configuration To verify HSDPA cell


over Iub interface configuration over Iub interface □ Passed
follows the requirement of □ Failed
protocol. □ Untested

HSDPA service reconfigured To verify HSDPA service


on RL over Iub interface reconfigured on RL over Iub □ Passed
interface follows the requirement □ Failed
of protocol. □ Untested

Activate / Deactivate HSDPA The purpose of this test is to


M. Configuration funcionality in a nodeB Activate / Deactivate HSDPA □ Passed
function □ Failed
□ Untested

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 164 of 177

Create a new nodeB with the The purpose of this test is to check
HSDPA funcionlity the procedure to create a new □ Passed
NodeB with the HSDPA function □ Failed
□ Untested

Change of HSDPA The purpose of this test is to


Configuration Parameters change of HSDPA Configuration □ Passed
Parameters □ Failed
□ Untested

Iub HSDPA capacity The purpose of this test is to


increase/decrease provide and execute the Iub □ Passed
capacity increase/decrease □ Failed
procedure □ Untested

Coverage

PLOTS

VOICE
RX Quality RX Level C/I

DATA
Throughput (kbps)

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 165 of 177

Stress Test (Subjective Measurements)


Voice Call
A. For Continuous Mode:

Results
Test Location Expected Results
1st Test 2nd Test 3rd Test
Clear Voice
Choppy Voice
Disconnected before completion
of 5 minutes Voice Call
Unable to Connect

B. For Call Gen Mode:

Results
Test Location Expected Results
1st Test 2nd Test 3rd Test
Clear Voice
Choppy Voice
Disconnected before completion
of 2 minutes Voice Call
Established connection of voice
call in 3 consecutive attempts.
Unable to Connect

SMS

Results
Test Location Expected Results
1st Test 2nd Test 3rd Test
Tester A able to send SMS to
Tester B
Unable to send SMS

Video Call

A. For Continuous Mode

Site A ______________ Site B _____________


Phone Type _________ Phone Type __________

Results
Test Location Expected Results
1st Test 2nd Test 3rd Test
Clear Video and Voice

Clear Video but Choppy Voice


Disconnected before completion
of 5 minutes Video call
Distorted Video and Choppy Voice
No 3G Icon even after several
manual network selection
Poor Video and Choppy Voice

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 166 of 177

Poor Video but Good Voice


Unable to Connect

B. For Call Gen Mode

Site A ______________ Site B _____________


Phone Type _________ Phone Type __________

Results
Test Location Expected Results
1st Test 2nd Test 3rd Test
Clear Video and Voice
Clear Video but Choppy Voice
Disconnected before completion
of 2 minutes Video call
Distorted Video and Choppy Voice
No 3G Icon even after several
manual network selection
Poor Video and Choppy Voice
Poor Video but Good Voice
Established connection of Video
call in 3 consecutive attempts.
Unable to Connect

WAP Browsing

Results
Test Location Expected Results
1st Test 2nd Test 3rd Test
Continuous Connection
Disconnected before completion
of 5 minutes WAP browsing
No 3G Icon even after several
manual network selection
Unable to Connect

Internet Browsing

Results
Test Location Expected Results
1st Test 2nd Test 3rd Test
Continuous Connection
Disconnected before completion
of 5 minutes Internet browsing
No 3G Icon even after several
manual network selection
Unable to Connect

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 167 of 177

Multimedia Streaming

A. For Live Video Streaming

Results
Test Location Expected Results
1st Test 2nd Test 3rd Test
Clear Video and Audio
Frequent Buffering
Disconnected before completion
of 6 min-streaming
Distorted Image
No 3G Icon even after several
manual network selection
Poor Video and Choppy Audio
Poor Video but Clear Audio
Unable to Connect

B. For Video Streaming On Demand

Results
Test Location Expected Results
1st Test 2nd Test 3rd Test
Clear Video and Audio
Frequent Buffering
Disconnected before completion
of 6 min-streaming
Distorted Image
No 3G Icon even after several
manual network selection
Poor Video and Choppy Audio
Poor Video but Clear Audio
Unable to Connect

C. For Live TV Streaming

Results
Test Location Expected Results
1st Test 2nd Test 3rd Test
Clear Video and Audio
Frequent Buffering
Disconnected before completion
of 6 min-streaming
Distorted Image
No 3G Icon even after several
manual network selection
Poor Video and Choppy Audio
Poor Video but Clear Audio
Unable to Connect

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 168 of 177

Downloading

Test Location Expected Results Results


Continuous Connection
Disconnected before completion of 2 minutes WAP
browsing
Able to download file
Unable to download file
No 3G Icon even after several manual network
selection
Unable to Connect

MMS

Results
Test Location Expected Results
1st Test 2nd Test 3rd Test
Tester A able to send MMS
Unable to send MMS

HSDPA

Test Location Expected Results Results


Continuous Connection

Disconnected before completion of HSDPA downloading


Able to download file
Unable to download file

No 3G Icon even after several manual network selection


Unable to Connect

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 169 of 177

Pilot/KPI Tests and Voice Call Set-up Test This test is done to measure the □ Passed
Stress Tests speed connection from calling □ Failed
party (originating call) to the □ Untested
receiving party (terminating call).

Voice Call Quality Test This test is done to check the call □ Passed
quality in the routes/areas to be □ Failed
tested. □ Untested

SMS Test SMS test is used to measure the □ Passed


availability and performance of the □ Failed
SMS service. □ Untested

MMS Test The MMS test is used to measure □ Passed


the availability and performance of □ Failed
a MMS service. The test currently □ Untested
supports MMS transactions over
the WAP

WAP Test The WAP test downloads a web □ Passed


page from a server in a manner □ Failed
similar to a WAP browser. □ Untested
However, the WAP test differs
from a browser because the test
takes measurements that are
indicators of QoS provided by a
WAP service.

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 170 of 177

Objective Measurements of Quality

Voice Call Set-up Test

Test Location: ______________ Cell ID: ____________


Phone Type ________________

Trial Call Set-up Time (seconds) RSSI (Rx LEV) (dbm)

Trial 1
Trial 2
Trial 3
Trial 4
Trial 5
Trial 6
Trial 7
Trial 8
Trial 9
Trial 10

Voice Call Quality Test

Test Location: ______________ Cell ID: ____________


Phone Type ________________

Signal-to-Interference
Trial RSSI Rx LEV (dbm) Tx Power (dbm)
Ratio (db)

Trial 1
Trial 2
Trial 3
Trial 4
Trial 5
Trial 6
Trial 7
Trial 8
Trial 9
Trial 10

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 171 of 177

SMS Test

A. One phone sends SMS to itself

Test Location: ______________ Cell ID: ____________


Phone Type ________________

Trial Send Time (s) Receive Time (s) Total Time (s)

Trial 1
Trial 2
Trial 3
Trial 4
Trial 5
Trial 6
Trial 7
Trial 8
Trial 9
Trial 10

B. One phone sends SMS to another phone connected to the same PC

Test Location: ______________ Cell ID: ____________


Phone Type ________________

Trial Send Time (s) Receive Time (s) Total Time (s)

Trial 1
Trial 2
Trial 3
Trial 4
Trial 5
Trial 6
Trial 7
Trial 8
Trial 9
Trial 10

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 172 of 177

MMS Test

Test Location: ______________ Cell ID: ____________


Phone Type ________________

Tx Upload Tx Upload Rx Upload Rx Upload Total Test


Trial
Time (s) Rate (s) Time (s) Rate (s) Time(s)
Trial 1
Trial 2
Trial 3

WAP Test

Test Location: ______________ Cell ID: ____________


Phone Type ________________

Gateway
Total Response Gateway Connect Data Transfer Time
Trial Disconnect Time
Time (s) Time (s) (s)
(s)
Trial 1
Trial 2
Trial 3

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 173 of 177

HSDPA

A. Stationary and Good Coverage

Test Location: ______________ Cell ID: ____________


HSDPA Card Type ________________

Throughput (kbps)
Trial Download Time
Average Maximum
Trial 1
Trial 2
Trial 3
Trial 4

B. Stationary and Bad Coverage

Test Location: ______________ Cell ID: ____________


HSDPA Card Type ________________

Throughput (kbps)
Trial Download Time
Average Maximum
Trial 1
Trial 2
Trial 3
Trial 4

C. Mobile

Throughput (kbps)
Trial Download Time
Average Maximum
Trial 1
Trial 2
Trial 3
Trial 4

D. Ping Tests

Latency/Delay (seconds)
Trial Accepted Time
Average Maximum
32 Bytes 70 ms
256 Bytes 70 ms
1024 Bytes 70 ms

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 174 of 177

KEY PERFORMANCE INDICATOR (KPIs)

Service bearer KPI Threshold Test Results


Call Setup Success Rate 96%
Voice Call
Call Drop Rate 3%
Call Setup Success Rate 96%
Video Call
Call Drop Rate 3%
Call Setup Success Rate 96%
Call Drop Rate 3%
PS (GPRS)
Throughput 90% of the Max RAB
throughput
Call Setup Success Rate 96%
Call Drop Rate 3%
HSDPA
Throughput Average to be proposed by
supplier
3G to 3G Handover
Handover
Success Rate
2G to 3G Handover
Success Rate

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 175 of 177

IOT

IOT Test Scenarios Voice call from GSM to Test the function of the GSM to □ Passed
WCDMA WCDMA speech call □ Failed
3G2G Interoperability/ □ Untested
Inter-working Tests

A. Basic Function Voice call from WCDMA to Test the function of the WCDMA □ Passed
GSM to GSM speech call □ Failed
□ Untested

SMS from WCDMA to GSM Test the function of Short Message □ Passed
Service from WCDMA to GSM. □ Failed
□ Untested

SMS from GSM to WCDMA Test the function of Short Message □ Passed
Service (MT). □ Failed
□ Untested

B. Roaming CS Roaming from WCDMA Check whether UE can perform □ Passed


to GSM Inter-System roaming from □ Failed
WCDMA to GSM. □ Untested

CS Roaming from GSM to Check whether UE can perform □ Passed


WCDMA Inter-System roaming from GSM □ Failed
to WCDMA. □ Untested

CS HPLMN selection from Check whether UE can perform □ Passed


GSM to WCDMA HPLMN selection from GSM to □ Failed
WCDMA which has different □ Untested
PLMN

PS Roaming from WCDMA Check whether UE can perform □ Passed


to GPRS Inter-System roaming from □ Failed
WCDMA to GSM/GPRS. □ Untested

PS Roaming from GPRS to Check whether UE can perform □ Passed


WCDMA Inter-System roaming from □ Failed
GSM/GPRS to WCDMA. □ Untested

PS HPLMN selection from Check whether UE can perform □ Passed


GPRS to WCDMA HPLMN selection from □ Failed
GSM/GPRS to WCDMA which □ Untested
has different PLMN.

C. Cell Reselection CS Cell Reselection from Check whether UE can perform □ Passed
WCDMA to GSM cell reselection from WCDMA to □ Failed
GSM. □ Untested

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 176 of 177

CS Cell Reselection from Check whether UE can perform □ Passed


GSM to WCDMA cell reselection from GSM to □ Failed
WCDMA. □ Untested

PS Cell Reselection from Check whether UE can perform □ Passed


WCDMA to GPRS cell reselection from WCDMA to □ Failed
GPRS. □ Untested

PS Cell Reselection from Check whether UE can perform □ Passed


GPRS to WCDMA cell reselection from GPRS to □ Failed
WCDMA. □ Untested

D. Handover CS handover from WCDMA Check whether UE can perform □ Passed


to GSM Inter-System service handover □ Failed
from WCDMA to GSM. □ Untested

CS handover from GSM to Check whether UE can perform □ Passed


WCDMA Inter-System service handover □ Failed
from GSM to WCDMA. □ Untested

Check whether UE can perform


PS handover in Cell_DCH Inter-System PS handover in □ Passed
from WCDMA to GPRS Cell_DCH mode from WCDMA to □ Failed
GPRS □ Untested

PS handover in Cell_FACH Check whether UE can perform □ Passed


from WCDMA to GPRS Inter-System PS handover in □ Failed
Cell_FACH mode from WCDMA □ Untested
to GPRS.

PS handover from GPRS to Check whether UE can perform □ Passed


WCDMA Inter-System PS □ Failed
handover/reselection from GPRS □ Untested
to WCDMA

CS+PS handover from Check whether UE can perform □ Passed


WCDMA to GSM/GPRS Inter-System PS+CS handover □ Failed
from WCDMA to GSM/GPRS. □ Untested

Video Call handover from Check whether UE can perform □ Passed


WCDMA to GSM/GPRS Inter-System Video Call handover □ Failed
from WCDMA to GSM/GPRS □ Untested

Reachability Test Check whether UE can receive □ Passed


SMS and voice calls after moving □ Failed
from 3G network to 2G network □ Untested

STRICTLY CONFIDENTIAL
Subject Date Ref # NQ-NO/100-001/805-0002
3G and HSDPA Test Procedures 9/27/2006
Title
3G and HSDPA Trial Test Cases and Procedures Page 177 of 177

Signatories:

_______________________ _________________________
DMPI Representative Vendor Representative

STRICTLY CONFIDENTIAL

You might also like