Suncell 3G and HSDPA Trial Test Procedures

Subject 3G and HSDPA Test Procedures

Date 9/27/2006

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

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

3G and HSDPA TRIAL TEST CASES AND PROCEDURES

repared by : John N. Sabando Delon S. Villanueva

Emeterio F. Gojar Sheila M. Indencia

oted by : Arturo Donato F. Bugayong

V 4.0 ersion No : Date : September 18, 2006 P N

STRICTLY CONFIDENTIAL


Date 9/27/2006

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


OPIC PAGE

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

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

6.1.1 CS Test

TABLE OF CONTENTS

T 1 2 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 ing …………………………………………………………………………… 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 ing …………………………………………………………………………….. 28 6.1.2 PS Test 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



Date 9/27/2006

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

Title 3G and HSDPA Trial Test Cases and Procedures 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 sting …………………………………………………………………………….. 40 6.1.3 RAN Te 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 ce ………………………………………………………………………………….53 6.1.4 Servi s 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



Date 9/27/2006

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

Title 3G and HSDPA Trial Test Cases and Procedures of 177 6.1.4 HSDP A 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. H

.…. . 81 5. H

SDPA Cell HSDPA UE Call Establishment – Emergency……......... 80 4. HSDPA Cell HSDPA UE Call Establishment – SMS…………....

SDPA 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 Load Management E. ……………………………………………..…………….. 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



Date 9/27/2006

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


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

B. Whole Network

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

…………………………………………………………………………. 110

3 IOT Tests6.3.1 Obje v6.3.2 SAM E6.3.3 Equipme6.3.4 Gene l6.3.5 IOT T 6.3.5.1 G

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. ……………………………………………………………………………………… 113 cti es ………………………………………………………………………………. 113 PL 3G TRIAL NETWORK SETUP FOR IOT ……………………….............. 114 nt and Tools …………………………………………………………………... 114 ra Test Guidelines and Procedures ……………………………..…………….. 115 est Scenarios …………………………………………………………………….. 115 3 2G 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



Date 9/27/2006

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


4. PS handover in Cell_FACH from WCDMA to GPRS ………….……… 132

8. Reachability Test …………………………………………………………. 135 6.3.5.2 3G2G Interoperability/Interworking Tests (Different Vendors)

3. PS handover in Cell_DCH from WCDMA to GPRS ………………….. .131 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

…………….. 136 6.3.5.3 3G3G Interoperability/Interworking Tests (Different Vendors) …………….. 136 APPENDIX ……………………………………………………………………………….…………… 137

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



Date 9/27/2006

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

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

n the ial network of the different vendors. The results will be used for the evaluation of the

e 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

system. h the tests depends on the 3G set-up of the vendor.

2. OBJEC E

The obj iv l are: a. Evaluate the 3G network functionality.

3G and/or HSDPA services:

on demand via phone and laptop

ming ding

- MMS ing with GSM/GPRS network.

d. Test interoperability between different vendor equipments. s, KPIs, and tools:

3.

oller

pport Node

ommunications

et Access

igital Network

DN – Public Data Network

SMS – Short Message Services

WAP – Wireless Application Protocol

This document is to be used as a reference for testing the 3G and HSDPA services otrperformance of th

network. This document describes the test specifications that are relevant to perform on the 3G trial

T e feasibility of most of

TIV S

ect es of the 3G and HSDPA tria

b. Test the customer experience with the following- speech, SMS, WAP - video phone, video conferencing, video- web browsing- multimedia strea- file transfer or downloa

c. Verify inter-work

e. Evaluate the 3G parameter- coverage - performance - OSS monitoring tools

TERMINOLOGY

BSC - Base Station Contr

BSC – Base Station Subsystem

GGSN – Gateway GPRS Su

GPRS – General Packet Radio Service

GSM – Global System for Mobile C

G-MSC – Gateway MSC

HSDPA - High-Speed Downlink Pack

IOT – Interoperability Tests

ISDN – Integrated Service D

KPI – Key Performance Indicator

MMS – Multi-Media Services

OSS – Operational Support System

P

PCU – Packet Control Unit

SGSN – Serving GPRS Support Node



Date 9/27/2006

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

Title 3G and HSDPA Trial Test Cases and Procedures of 177 4. 3G TRIAL NETWORK SET-UP

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

Figure 1

or.

5. IST OF TEST EQUIPMENT AND TOOLS

DM w ich is not included in the 3G ay allow each vendor to use and recommend 3G test tools. Th are:

4. Outdoor and Indoor Drive Test Tools (Agilent Nitro, NEMO Handy, etc.) 5. Protocol Analyzer (Agilent Distributed Network Analyzer, Nethawk, etc.) 6. WAMS software.

for measuring throughput (DUMeter, etc.) 6.

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

c. IOT Tests

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

NOTE: The set-up may vary with each vend

L

PI ill use 3G test tools from an independent vendor, wh/HSDPA trial. DMPI m

e test equipment and tools to be utilized during the duration of the test period1. 2G and 3G test phones with 3G-capable SIM cards. 2. HSDPA cards 3. Laptops

7. Software

TEST PLAN

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

The resu



Date 9/27/2006

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


6.1

e t (paging, andover, cell updates), and bearer capability for CS. For PS, the tests will verify PDP

streaming.

The fun ed into five parts, namely:

g ork Testing

• Services Testing sting

Basic Functionality Tests The basic functionality tests will verify the call set-up, mobility managem nhactivation, web browsing, ftp, SMS, MMS, and multimedia

ctionality tests are divid

• Circuit Switch Testing • Packet Switch Testin• Radio Access Netw

• HSDPA Te

6.1.1 CS Testing For CS divided into 4 main parts:

• Supplementary Service rging (CDR)

A. ement

testing, the tests are• Mobility Management • Basic Service

• CS Domain Cha

Mobility Manag 1. IMSI Attach

in one SA.

e MS originates IMSI attach in SA1 ched

Expected Result: able to attach.

in a different SA.

S ers off UE. ers on, and the MS originates IMSI

ched Expected Result:

to attach.

te

a. Same SA Objective:

Test the function of IMSI attachTest Procedure:

Subscriber A powers off UE. Subscriber A powers on, and th Verify if subscriber A is atta

Subscriber is

b. Different SA Objective:

Test the function of IMSI attachTest Procedure:

ubscriber A pow Subscriber A moves to SA2, pow

attach in SA2 Verify if subscriber A is atta

Subscriber is able

2. Location Upda

P nd the MS originates a IMSI Attach. _UPDATE_REQUEST message was

cted Result: Subscriber is able to attach and a location update request was sent by the

a. MS location updates with IMSI Objective:

Test the function of MS location updates with IMSI. Test Procedure:

ower on the MS, a Check at the Iu if a LOCATION

sent by the MS. Expe

MS.



Date 9/27/2006

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


and the MS originates a IMSI Attach.

e_UPDATE_REQUEST message was

ubscriber is able to attach and a location update request was sent by the

nutes.

b. Periodic Location Update Objective:

Test the function of Periodic location update Test Procedure:

Power on the MS, Keep the MS in service. The MS originates periodic location update

very 6 minutes. Check at the Iu if a LOCATION

sent by the MS every 6 minutes. Expected Result: SMS every 6 mi

3. IMSI Detach

P MS, and the MS originates an IMSI Detach. ACH_INDICATION message was sent

Expected Result: .

P d the MS originates an IMSI Attach. cation

the state of the subscriber in the VLR. xpected Result:

tached.

a. MS location updates with IMSI Objective:

Test the function of IMSI Detach Test Procedure:

ower off the Check at the Iu if an IMSI_DET

by the MS.

Subscriber is able to

b. Implicit IMSI detach Objective:

Test the function of Implicit IMSI Detach Test Procedure:

ower on the MS, an Take the battery out of the mobile phone to break the communi

with the network. After 12 minutes, query

ESubscriber is de

4. Authentication

on.

riginates an IMSI Attach. ng flow is correct.

Expected Result: ication signaling flow is correct.

a. UE authentication in RNC serving area in updating location. Objective:

Test the function of authentication process in updating locatiTest Procedure:

Power on the UE, and the UE o Check at the Iu if the authentication signali

The authent



Date 9/27/2006

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


SECURITY_MODE_COMMAND

UE MSC/VLR HLR

LOCATION_UPDATION_REQUEST

RNC

LOCATION_UPDATING_ACCEPT

IU_RELEASE_COMMAND

IU_RELEASE_COMPLETE

SEND_AUTHENTICATION_INFO_REQ

SEND_AUTHENTICATION_INFO_CNFAUTHENTICATION_REQUEST

AUTHENTICATION_RESPONSE

UPDATE_LOCATION_REQ

INSERT_SUBSCRIBER_DATA_RSP

INSERT_SUBSCRIBER_DATA_IND

UPDATE_LOCATION_CNF

SECURITY_MODE_COMPLETE

COMMON_ID

5. Ciphering

a. Test the function of ciphering process in updating location. Test Procedure:

Power on the UE, and the UE originates a location update. signaling flow is correct.

t.

Ciphering in location update Objective:

Check at the Iuc if the ciphering Expected Result: The ciphering signaling flow is correc


UE MSC/VLR

UPDATION_REQUEST

RNC

COMMON_ID

AUTHENTICATION_REQUEST


SECURITY_MODE_COMPL

LOCATION_UPDATING_ACCEPT

IU_RELEASE_COMMAND

IU_RELEASE_COMPLETE

ETE



Date 9/27/2006

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


n subscriber’s MOC/MTC rocess in call processing.

ure:

iphering signaling flow is correct.

b. Ciphering i Objective:

Test the function of ciphering p Test Proced

UE1 originates a call to UE2. Check at the Iu and Iuc if the c

Expected Result: The ciphering signaling flow is correct.

UE2 UE1 MSC/VLR HLR

CM_SERVICE_REQUEST

AUTHENTICATION_REQUESTAUTHENTICATION_RESPONSE

RNC


SECURITY_MODE_COMPLETESETUP

SEND_ROUTING_INFORMATION_REQPRCALL_PROCEEDING OVIDE_ROAMING_NUMBER_IND

PROVIDE_ROAMING_NUMBER_RSP

COMMON_ID

RAB_ASSIGNMENT_REQUEST

RAB_ASSIGNMENT_RESPONSE

N_CNFSEND_ROUTING_INFORMATIO


PAGINGPAGING_RESPONSE

COMMON_IDAUTHENTICATION_REQUEST


COMPLETE


SECURITY_MODE_SETUP

CALL_CONFIRMED


ALERTING

CONNECTECONNECT_ACKNOWLEDG

LEDGECONNECT_ACKNOW

DISCONNECT

RELEASE

DISCONNECT

RELEASE

RELEASE_COMPLETE

R

ND

ELEASE_COMPLETE

ASE_COMMAIU_RELE

IU_RELEASE_COMMAND

IU_RELEASE_COMPLETE

IU_RELEASE_COMPLETE



Date 9/27/2006

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


6. Location Update Fail a.

Ob ction of location update but IMSI unknown in HLR est 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:

Ma t UE is subscribed in HLR. Config ming to LAC1, but not to LAC2. Che R fail cause is “Unknown subscriber”. Query

Expected Result: UE is detached and location update fails.

B.

le Speech Call

IMSI unknown in HLR jective: Test the funT

ke sure thaure UE to allow roa

ck that the HLsubscriber info at VLR.

Basic Service 1. Mobile to Mobi

ile speech call

the call is connected minutes

Expected Result: nd speech is clear.

Code

rate as the AMR code. l to UE B.

call. nnect the call.

Repeat the procedure, using different rate each times:

esult: according to different AMR codes.

c. Office

call to UE B.

Disconnect the call

a. Mobile to Mobile Speech Call Objective:

Test the function mobile to mobTest Procedure:

UE A initiates a normal call to UE B UE B answers and Both parties keep the call for 2 UE B hangs up

The call is correctly set-up a

b. Voice calls with 8 AMR Objective:

Test the function of Voice Calls with 8 AMRTest Procedure:

Configure 12.2K UE A initiates a normal cal UE B alerting, and answers the Keep the call for 2 minues and then disco

10.2k, 7.95k, 7.4k, 6.7k, 5.9k, 5.15k, 4.75k Expected RCall is successful and quality may vary TrFO function in 3G EndObjective: Test the function of TrFO in 3G End Office Test Procedure:

UE A initiates a normal UE B answers and the call is connected. Observe the TC resources in MGW



Date 9/27/2006

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


ween Mobile and PSTN (Optional)

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

2. Speech Call bet

l PSTN subscriber, and PSTN

hile, and hangs up

The call is successful.

ing DTMF

nd PSTN

or 2 minutes. hone, and then

Expected Result: tone. A START_DTMF message is

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.

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 locasubscriber alerting. PSTN subscriber answers the call, holds it on for a wthe call

Expected Result:

b. Mobile to PSTN Speech Call, UE send Objective:

Test the function of DTMF Test Procedure:

UE1 initiates a normal call to a local PSTN subscriber, asubscriber alerting. PSTN subscriber answers the call, and holds it f In the conversation, press a digit key of the mobile prelease the key. Observe lu-interface signaling.

PSTN subscriber can hear a DTMFobserved.

UE1 MSC/VLR HLRRNC PSTN

IAM

ALERTING

CONNECT

CONNECT_ACKNOWLEDGE

ACM

ANM

START_DTMF

START_DTMF_ACKNOWLEDG ESTOP_DTMF

STOP_DTMF_ACKNOWLEDGE



Date 9/27/2006

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


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 success ing is normal. ful and signal

MSC/VLR HLRRNC

SEND_ROUTING_INFORMATION_REQ

PROVIDE_R

PROVIDE_R

OAMING_NUMBER_IND

OAMING_NUMBER_RSP

ALERTING

R

SEND_ROUTING_INFORMATION_CNF

AB_ASSIGNMENT_RESPONSE

UE2

PAGING

PAGING_RESPONSE

COMMON_ID

PSTN

IAM


EAUTHENTICATION_RESPONS



CALL_CONF

CONNECT

CONNECT_ACKNOWLEDGE

IRMED


ACM

ANM

DISCONNECT

RELEASE

RELEASE_COMPLETE

REL

RLC

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.



Date 9/27/2006

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


Expected Result:

Call is successful and one EC resource

3. Video Call

is occupied.

a. Mobile to Mobile Video Call Objective: Test the function of Mobile to 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

Mobile video call

a. Em o USIM inside UE) Ob Te n of Emergency Call Test Procedure:

Take o SIM from th 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)

he UE. the UE, e.g. call 112.

PSTN. hangs up.

ergency call (njective: st the functio

ut the U e UE, and power on the UE.

Objective: ction of Emergency Call Test the fun

Test Procedure: mobile phone, and power on t Insert the USIM card into them Initiate an emergency call fro

The emergency call is connected to the UE 2 Call is kept for 2 minutes and then

Expected Result: The emergency call is successful.

5. Short Message Service ge Service (MO) a. Short Messa

Objective: age Service (MO) Test the function of Short Mess

Test Procedure: UE A sends a short message “12345” to UE B.

E B from SMC. The short message “12345” is sent to U Observe the signaling messages.

Expected Result: he sms is successfully sent by UE A and received by UE B. TT he

signaling messaging is normal.



Date 9/27/2006

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


b.

ge “12345” to UE B. UE B from SMC.

UEa MSC/VLR SMC

CM_SERVICE_REQUEST

Short Message Service (MT) Objective: Test the function of Short Message Service (MT)

est Procedure: T UE A sends a short messa The short message “12345” is sent to

he signaling messages. Observe tExpected Result:

UE A and received by UE B. The The sms is successfully sent bysignaling messaging is normal.



RNC



MAP_MO_FORWARD_SM SAGE_REQ FORWARD_SHORT_MES

SMS_CP_ACKSMS_CP_DATA

SMS_CP_DATA

COMMON_ID

SMS_CP_ACK

IU_RELEASE_COMMAND

IU_RELEASE_COMPLETE

MAP_MO_FORWARD_SM RT_MESSAGE_CNF FORWARD_SHO



Date 9/27/2006

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


c. eech call ll Test Procedure:

th PSTN. t message to UE B.

ges.

voice call.

video call

call for 2 minutes.

ring a video call.

receive short message sent by UE A r returning to the service area.

UEb VLR

Mobile can receive SMMT during spObjective: Test the function of Mobile receive SMMT during speech ca

UE B is in a call wi UE A sends a shor Observe the signaling messa

esult: Expected RThe sms is successfully received by UE B during a

d. M gobile can receive SMMT durinObjective: 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 UE B sends a short message to UE A.

Expected Result: The sms is successfully received by UE A du

e. SMMT to a UE, out of coverage Objective: T nest the function that UE B ca

during B’s out of coverage afteTest 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.

MSC/ HLR

MAP_MT_FORWARD_SM FORWARD_SHORT_MESSAGE_IND

MAP_SEND_ROUTING_INFO _FOR_SM_ACK


RNC



SMS_CP_ACK

SMS_CP_DATA

SMS_CP_DATA

SMS_CP_ACK

IU_RELEASE_COMMAND

IU_RELEASE_COMPLETE

SMC

MAP_SEND_ROUTING_INFO _FOR_SM

PAGING

PAGING_RESPONSE

COMMON_ID


MAP_MT_FORWARD_SM FORWARD_SHORT_MESSAGE_RSP



Date 9/27/2006

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


essfully received by UE B when back in the coverage area.

can receive SMS when switched on the

itching on the mobile phone, UE B can ssage sent by UE A when B’s mobile phone is

hort message or not.

ived by UE B when powered on.

ory not full

essages to UE B until the memory of UE B

UE B.

emory is not full. New short s some short messages are deleted.

6. Call Failure Processing

Expected Result: The sms is is not received by UE B when out of coverage area. The sms is succ

f. SMMT to a detached UE, UE mobile.

Objective: Test the function of that after sw

receive the short meswitched off. Test Procedure:

UE A sends a short message to UE B. UE B powers on. Check if UE B can receive the s

Expected Result: The sms is rece

g. SMMT to a memory full UE, UE can receive SMS mem 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 mis full. Delete some short messages from

Expected Result: The sms is received by UE B when mmessages can be received as soon a

a. Mobile Terminating Call, the UE is busy

ction of Call Failure Processing when the called UE is busy.

in a call.

nouncement.

b.

rocessing when the called UE does not

est Procedure:

UE B.

er time out and then UE A hears the

t the user does not answer.

c. ut of coverage

rocessing when the called UE does not

Objective: Test the fun

Test Procedure: UE A is idle, UE B is engaged UE A calls UE B. UE A hears the an

Expected Result: UE A hears the announcement that the user is busy.

Mobile Terminating Call, the UE does not answer Objective: Test the function of Call Failure Panswer. T

UE A and UE B are idle. UE A calls UE B rings and does not answer. The MSC releases the call aftannouncement.

Expected Result: UE A hears the announcement tha Mobile Terminating Call, the UE is oObjective: Test the function of Call Failure Panswer.



Date 9/27/2006

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


est Procedure:

s and does not answer. UE A hears the

d. E is switched off

e called UE is powered off.

UE B are idle.

UE B. nt.

e. E is NULL

r is

est Procedure: R.

tes a normal call to UE B.

alled party is null.

C. Supple

1. Ca

T UE A and UE are idle. UE A calls UE B. UE B ring The MSC releases the call after time out and thenannouncement.

Expected Result: UE A hears the announcement that the user does not answer. Mobile Terminating Call, the UObjective: Test the function of Call Failure Processing when th

Test Procedure: UE A and UE B is powered off. UE A initiates a normal call to UE A hears the announceme

Expected Result: UE A hears the announcement that the subscriber is powered off. Mobile Terminating Call, the UObjective: Test the function of Call Failure Processing when the called UE numbeNULL. T

UE A is idle and UE B does not exist in HL UE A initia UE A hears the announcement.

Expected Result: UE A hears the announcement that the c

mentary Service ll Forwarding

a. Forwarding Unconditional est Procedure:

forwarded to the PSTN user C, and PSTN user C answers

minutes ects the call.

ber.

b. ng on Busy

call with UE C UE A initiates a call to UE B

rwarded to the UE D, and UE D answers the call. r 2 minutes

onnects the call.

Call Forwarding Unconditional Objective: Test the function of Call T

UE A initiates a call to UE B The call is

the call. Both parties keep the call for 2 PSTN user C disconn

Expected Result: The call is forwarded to the correct num

Call Forwarding on Mobile Subscriber Busy Objective: Test the function of Call ForwardiTest Procedure:

UE B is in a

The call is fo Both parties keep the call fo UE D disc



Date 9/27/2006

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


the alternative number when the dialed number is

Objective: arding on No Reply

ure:

answer the call. he call is forwarded to the PSTN user C, and PSTN

or a while. all

The call is forwarded to the alternative number when the dialed number

ing on Mobile Subscriber Not Reachable.

. call for 2 minutes.

Expected Result: lternative number when the dialed number is

ication to party A and party B.

UE A calls UE B. g process,

rs a call forwarding announcement.

call

nt is working.

Objective: Forwarding activation/interrogation/deactivation

ister CFU: **21*FTN number#

he CFU is activated, deactivated, or interrogated, a

Expected Result: The call is forwarded tobusy.

c. Call Forwarding on No Reply

Test the function of Call Forw Test Proced

UE A calls UE B. UE B is alerting, but does not After the timeout, tuser C answers, keep the call f PSTN user C disconnects the c

Expected Result:

does not reply.

d. Call Forwarding on Mobile Subscriber Not Reachable Objective:

Test the function of Call ForwardTest 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 PSTN user C disconnects the call

The call is forwarded to the aunreachable.

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

Test the function of Call Forwarding notifTest Procedure:

UE B is in a call with UE C. UE A calls UE B.

The call is forwarded to PSTN D. During the call forwardinUE A hea PSTN D answers and keeps the call for 2 minutes. PSTN user D disconnects the

Expected Result: The call forwarding announceme

f. Call Forwarding activation/interrogation/deactivation Test the function of Call

Test Procedure: UE B Reg 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 tnotification display appears on the monitor of UE B.



Date 9/27/2006

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


2. Ca ll Forwarding for Video Call

a. Video Call n of Call Forwarding for Video Call est Procedure:

call to UE B. ed to the UE C, and UE C answers the call.

es keep the call for 2 minutes

correct number.

b. est the function of Call Forwarding for video call.

a call with UE C.

the UE D, and UE D answers the call. inutes

he video call is forwarded to the alternative number when the dialed

ing on No Reply for Video Call

ding for Video Call on No Reply

call to UE B. oes not answer the call.

eo call is forwarded to UE C, and UE C he call for a while.

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

Call Forwarding Unconditional for Objective: Test the functioT

UE A executes a video The call is forward Both parti UE A disconnects the call.

Expected Result: The video call is forwarded to the

Call Forwarding on Mobile Subscriber Busy for Video Call Objective: T

Test Procedure: UE B is in UE A initiates a video call to UE B The video call is forwarded to Both parties keep the call for 2 m UE D disconnects the call.

Expected Result: Tnumber is busy.

c. Call Forward Objective: Test the function of Call Forwar

Test Procedure: UE A originates a video UE B is alerting, but d After the timeout, the vidanswers, keeps t UE C disconnects the call.

Expected Result: The video call is

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



Date 9/27/2006

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


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 vid to UE B. Video call fails

Expected Resu The call fails and the tone indicates that the video call is barred.

b. Barring of All In all

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.

esult: and the incoming video call is barred.

eo call and UE A hangs up. lt:

coming Calls for Video C

Expected R The call fails 5. Call Barring for SMS

a. Barring of All Outgoing Calls for SObjective:

MS ll Outgoing Calls for SMS

b.

of Barring of All Incoming Calls for SMS

Test the function of Barring of ATest Procedure:

UE A originates a short message to UE B. ected Result: Exp

The MO short message fails. Barring of All Incoming Calls for SMS Objective: Test the function



Date 9/27/2006

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


inates a short message to UE B.

is successful. To UE B, the MT short

6. Nu

Test Procedure: UE A orig

Expected Result: To UE A, the MO short messagemessage fails. mber Identification

a. f MS subscribe CLIR

xpected Result: rivate Number”

.

e CLIP

he calling number is correctly displayed on UE B screen.

MS subscribe CLIR Objective: Test the function oTest Procedure:

UE A originates a call to UE B. EThe calling number cannot be displayed on UE B. Only “Pis displayed

b. Only subscribe CLIP Objective: Test the function of only subscribTest Procedure:

UE A originates a call to UE B. Expected Result: T

7. Call Completion a. Call Hold Objective: Test the function of Call Hold

E ll

fl

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. xpected Result:

When the call is put on hold, UE B hears a hold announcement. The caow is normal.



Date 9/27/2006

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


Exp On call while UE C can hear the ring

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.

ected Result: sthe creen, UE B notices an incoming

back tone.

UEa MSC/VLR HLR

CM_SERVICE_REQUEST


RNC



SEND_ROUTING_INFORMATION_REQPROCALL_PROCEEDING

SETUP

VIDE_ROAMING_NUMBER_INDPPROVIDE_ROAMING_NUMBER_RS

COMMON_ID




UEb

PAGINGPAGING_RESPONSE

COMMON_IDAUTHENTICATION_REQUESTAU

URITY_MODE_COMMANDCURITY_MODE_COMPLETE

THENTICATION_RESPONSESECSE

SETUPCALL_CONFIRMED



ALERTINGCONNECT

CONNECTCONNECT_ACKNOWLEDGE

ONNECT_ACKNOWLEDGEC

HOLDHOLD_ACKNOWLEDGE

FACILITY(1)RETRIEVE

RETRIEVE_ACKNOWLEDGE

FACILITY(2)



Date 9/27/2006

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


c. Mult ping Obje Test the function of multiple call hold swapping. Tes

U B and UE B answers the call. U ll with UE B. UE A initiates a call to UE C and UE C answers the call.

call with UE C and retrieves the call with UE B. UE B and retrieves the call with UE C.

d. T

U UE B and UE B answers the call. U UE B. U ge to UE C.

Exp ccessfully received by UE C while UE B is on hold.

iple Call Hold Swapctive:

t Procedure: call to UE E A originates a

aE A holds the c

UE A holds the s the call with UE A hold

UE A hangs up. Expected Result:

The hold calls are not disconnected.

ntly holds a call. SMMO can be initiated by MS who curreObjective: Test the function of multiple call hold swapping.

es ro t P cedure: E A originates a call to

call with E A holds theE A sends a short messa

cted Result: eThe SMS was su

8. Multiparty Service a. Six-Way Service Objective:

T

U y call. UE A initiates a call to UE D successfully, and then UE A applies the m R mentioned above to UE E and UE F into the

B releases the multi-party call.

dropped. D. CS

1. C R

est 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.

E A holds the multi-part

ulti-party service again.epeat the same steps

multi-party call. UE

Expected Result: All UEs are in the multi-party call and no UE is

Domain Charging (CDR) D Generating

a i Test the function of Bill of MOC

E A originates a call to UE B and UE B answers.

fter 2 minutes. B client, check the bill for the call.

ile Originating (MO) bill is generated for

. B ll of MOC Objective:

Test Procedure:

U UE A clears the call a In the iGW

Expected Result: The call is successful and a MobUE A and the information is correct for:

• Calling Number • Called Number• Served MSISDN (UE A number) • Served IMSI



Date 9/27/2006

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


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: MO bill is generated for UE A, a forwarding bill

d for UE B and an MT bill is generated for UE C. In the

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

• Initial Time • Conversation Duration

The call is successful. Anis generateforwarding 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



Date 9/27/2006

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


• 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:

O

UE B. l for the SMS.

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

• MO SMS number SMS number • MT

• Bytes • SMC address

f. Bill of SMS (MT) bjective:

Test the function of Bill of SMS (MT) Test Procedure:

UE A sends a short message to In the iGWB client, check the bil

Expected Result:

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

• Mobility Management • Session Management • Reliability and Stability

Domain Charging

1. At

• PS• CG

A. Mobility Management

tach a. GPRS attach with IMSI

O C ch originated

b

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.

bjective: heck if the network can successfully handle the GPRS attay Normal Subscriber with IMSI

Test Procedure:



Date 9/27/2006

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


Expected Result: The attach messaging is normal. MS SGSN HLR

Attach Request

Update Location

Attach Accept

Insert Subscriber Data

Update Location Ack

Attach Complete

Insert Subscriber Data Ack

RNC

Authentication and Ciphering Request

Authentication and Ciphering Response

Security Mode Command

Security Mode Complete

Send Authentication Info

Send Authentication Info Ack

Objective: k can successfully handle the GPRS attach originated

ure:

red

originates GPRS attach.

T

b. GPRS attach with P-TMSI Check if the networ

by Normal Subscriber with P-TMSI Test Proced

A valid P-TMSI is stored in the USIM of the MS and the MS is registein SGSN. Power on the UE and the UE Check that UE is attached.

Expected Result: he attach messaging is normal.



Date 9/27/2006

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


MS SGSN

Attach Request

Attach Accept

Attach Complete

RNC





c. GP O C ully handle the GPRS attach originated

Test Procedure: e USIM of the MS, the MS is not

in SGSN and no subscription data found in the HLR.

ck that UE is attached.

RS attach, MS unknown in HLR bjective: heck if the network can successf

by Unknown Subscriber

No valid P-TMSI is stored in thregistered Power on the UE and the UE originates GPRS attach. Che

Expected Result: The attach messaging is normal.

MS SGSN HLR

Attach Request

RNC

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.



Date 9/27/2006

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


MS SGSN

Detach Request

RNC

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. ff the MS, and the MS originates GPRS detach.

SGSN. 4. Rou

Power o By command purge the MS from SGSN.

Expected Result: No data for MS is stored in the

ting Area Update a. I

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. another Routing Area within the same SGSN, and

ea Update

a messaging is normal.

ntra SGSN Routing Area Update Objective:

The MS roams toinitiates Routing Ar

Expected Result: Routing are

MS SGSN

Routeing Area Upd

RNC

ate Request

Routeing Area Update Accept

Routeing Area Update Complete





Date 9/27/2006

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


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: uccessfully handle modification of subscriber data

ubscriber data is successful.

scriber data from

.

Delete GPRS service for the MS. Expected Result:

Deleting of subscriber data is successful. 6. Security

Check if SGSN can s. from HLR

Test Procedure: S originates GPRS attach. Power on the MS and the M

Modify GPRS service for the MS, such as APN. Expected Result:

Modification of s

b. HLR deleting of subscriber data Objective:

Check if SGSN can successfully handle deleting of subHLR.

Test Procedure: Power on the MS and the MS originates GPRS attach

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.



Date 9/27/2006

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


SGSN HLRMS

Attach Request

Update Location

Attach Accept


Update Location Ack

Attach Complete


RNC







PRS attach.

B. Session Management 1. PDP Context Activation

b. Ciphering

Check if the

Objective: network can successfully implement ciphering function.

Test Procedure: Power on the MS and the MS originates G Delete GPRS service for the MS.

Expected Result: Attach is successful.

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 activation messaging is PDP context activation is successful. The

normal.



Date 9/27/2006

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


MS SGSN GGSN

Activate

RNC

PDP Context Request

Activate PDP Context Accept

RAB Assignment Request

Create PDP Context Request

Create PDP Context Response

b. Mu

er.

T Cw

Expected Result: Mu sful.

RAB Assignment Response

ltiple PDP contexts Ob ctive:

Check if the network can supje

port multiple PDP contexts for subscrib 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 inuse us GTP V1. Power on the MS and the MS originates GPRS attach.

he MS activates PDP context with one of the APNs subscribed. onnect UE with PC, initiate another PDP context activation procedure ith the other APN subscribed, UE as mobile modem.

ltiple PDP context activations are succes

MS SGSN GGSN

Activa

RNC

te PDP Context Request






Activate PDP Context Request





Obj Che t activation

pro .


c. PDP activation reject due to unknown APN. ective: ck if the network can successfully handle the PDP contexcedure originated by normal subscriber with unknown APN



Date 9/27/2006

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


Teut not mapped to any GGSN.

s GPRS attach. with unknown APN.

st Procedure: APN in use is subscribed to the MS b Power on the MS and the MS originate The MS activates PDP context

Expected Result: PDP context activation is rejected.

MS SGSNRNC


Activate PDP Context Reject

Iu Release Command

Iu Release Complete

activation reject due to service not subscribed. d. PDP Ob

Che proce t subscribed. Te

h. N not subscribed.

jective: ck if the network can successfully handle the PDP context activation

dure originated by normal subscriber with service nost Procedure:

APN in use is not subscribed to the. Power on the MS and the MS originates GPRS attac The MS activates PDP context with AP

Expected Result: PDP context activation is rejected.

2. PDP Context Deactivation a. MS initiated PDP Context Deactiva Objective:

tion

ctivation

ssful. The PDP activation messaging is

Check if the network can successfully handle the PDP context dea

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 succenormal.

MS SGSN GGSN

Deactivate PDP Context Request

Deactivate PDP Context Accept

RNC


Delete PDP Context Request

Delete PDP Context Response


b. GGSN initiated PDP Context Deactivation

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



Date 9/27/2006

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


S originates GPRS attach.

PDP context from GGSN.

GSN is successful. c. S

O Ch successfully initiate PDP context deactivation. T

S originates GPRS attach.

Expected Result: essful.

Test Procedure: Power on the MS and the M The MS activates PDP context. Deactivate

Expected Result: PDP context deactivation from GGSN initiated PDP Context Deactivationbjective: eck if the SGSN can

est Procedure: Power on the MS and the M The MS activates PDP context. Delete GPRS subscriber data from HLR.

SGSN initiated PDP context deactivation is succ

3. APN Selection Rule a. APN selection rule, No APN in Activate PDP Context Request

O C n

the xt Request. T

DP context subscription for the MS in HLR. riginates GPRS attach.

ext Request.

esult:

reate PDP Context Request sent to

b. APN selection rule, Wild Card O Ch n successfully select APN of PDP context when MS

s ild card. T

and APN subscription is “*”. and the MS originates GPRS attach.

tivates PDP context with specific APN in Activate PDP valid APN that is mapped to

S context Request sent

Request sent to GGSN. The MS activates PDP context successfully.

I included Objective: network can successfully select APN of PDP context when

ontext Request, APN NI included. ure:

S and the MS originates GPRS attach.

bjective: heck if the network can successfully select APN of PDP context whe

re is no APN in Activate PDP Conteest Procedure:

There is one and only one P Power on the MS and the MS o The MS activates PDP context without APN in Activate PDP Cont

The MS deactivates the PDP context. Expected RSGSN selects APN according to PDP context subscription for the MS and the selected APN is included in CGGSN. The MS activates PDP context successfully.

bjective: eck if the network ca

ubscribes a PDP context of west Procedure:

There is one and only one PDP context subscription for the MS in HLR

Power on the MS The MS acContext Request. The APN in use is a GGSN. The MS deactivates the PDP context.

Expected Result: GSN selects the APN included in the Activate PDP

by the MS and the selected APN is included in Create PDP Context

c. APN selection rule, MS send APN, APN N Check if the

there is APN in Activate PDP C Test Proced

There is one and only one PDP context subscription for the MS in HLRand APN subscription is not “*”. Power on the M



Date 9/27/2006

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


t with specific APN in Activate PDP

E st sent

by tReq sent to GGSN. The MS activates PDP context successfully.

d. AP O C n

t in Activate PDP Context Request, APN in mixed case. Test Procedure:

d only one PDP context subscription for the MS in HLR cription is not “*”.

and the MS originates GPRS attach. ctivates PDP context with specific APN in Activate PDP

e PDP context. t with specific APN in Activate PDP

with specific APN in Activate PDP

The MS deactivates the PDP context. Expected Result: The MS activates PDP context successfully.

4. GGSN Address Resolution

The MS activates PDP contexContext Request, APN NI included. The MS deactivates the PDP context. xpected Result:

SGSN selects the APN included in the Activate PDP context Requehe MS and the selected APN is included in Create PDP Context uest

N selection rule, MS send APN in Mixed Case

bjective: heck if the network can successfully select APN of PDP context whe

here is APN

There is one anand APN subs Power on the MS The MS aContext Request, APN in lower case, e.g. “test”. The MS deactivates th The MS activates PDP contexContext Request, APN in upper case, e.g. “TEST”. The MS deactivates the PDP context. The MS activates PDP context Context Request, APN in mixed case, e.g. “TeST”.

a. GGSN address resolution by DNS Objective: Check if the network can resolve GGSN Test Procedure:

GSN address in DNS server. for the APN.

the MS and the MS originates GPRS attach.

address by DNS.

APN in use is mapped to G Clear DNS cache Power on The MS activates PDP context.

Expected Result: Message sequence is normal.

MS SGSN GGSN



RNC





DNSServer

DNS Resolve Request

DNS Resolve Ack



Date 9/27/2006

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


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

t: short time and GGSN status is normal.

network link redundancy function is right.

ckup network ports of Ga

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.

riginates GPRS attach. data service, such as

FTP download. Pull out one of the ethernet cables of backup network ports of Gi

f GGSN. thernet cable.

esult: is pulled out.

d. O e.

riginates GPRS attach.

continuously for 5 minutes, e.g. Video Streaming. are alarms or faults monitored on the SGSN and GGSN,

esult:

Expected Resul The network port recovers in a b. SGSN Ga interface Network Link Redundancy.

Objective: Check if the SGSN Ga interface Test Procedure:

Check if all Ga interfaces are normal. Pull out one of the Ethernet cables of bainterface of SGSN. Check if Gn interface is normal.

Test Procedure: Power on the MS, and the MS o The MS activates PDP context and performs PS

interface o Plug in the E

Expected R The data service continues when one of the Ethernet cables

E2E stability test bjective:

Check the stability of E2E performanc Test Procedure:

Power on the MS, and the MS o The MS activates PDP context and performs PS data service

Check if there etc.

Expected R The data service performs successfully.

2. Transfer Rate a.

Ob C tion

p al Subscriber with transparent mode and s

Uplink/downlink transfer rate. jective:

heck if the network can successfully handle the PDP context activarocedure originated by Normtatic IP address.



Date 9/27/2006

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


GPRS attach.

P context activation procedure with PC,

MS performs PS data service mainly downlink, such as FTP download, record the downlink bit rate with software installed in the

. The MS performs PS data service mainly unlink, such as FTP upload,

in the PC.

hputs are measured and data service is

D. PS Dom

Test Procedure: Power on the MS, and the MS originates Connect UE with PC, initiate PDUE as mobile modem. The

PC

record the uplink bit rate with software installedExpected Result: Uplink and downlink througsuccessful.

ain Charging 1. M-CDR Generation a. M-CDR Generation

nerate M-CDR and send it to CG

Objective: SGSN can successfully ge Check if the

after MS GPRS detach. Test Procedure:

Power on the MS, and the MS originates GPRS attach. S, and the MS originates GPRS detach. Power off the M

Expected Result: ds the CDR to CG. SGSN generates M-CDR and sen

SGSN CG

Data Record Transfer Request

2. S-C

Data Record Transfer Response

DR Generation

a. S-CDR Generation Objective:

ssfully generate S-CDR and send it to CG

.

Check if the SGSN can succe

activation. after PDP de Test Procedure:

originates GPRS attach Power on the MS, and the MS The MS activates PDP context.

ates PDP context. The MS deactivExpected Result:

ds the CDR to CG. SGSN generates M-CDR and sen

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

R and S-SMT- Objective: Check if the SGSN can successfully generate S-SMO-CD

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

xt. The MS deactivates PDP conteExpected Result: SGSN generates SMS-MO-CDR and SMS-MT-CDR and sends to CG.



Date 9/27/2006

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


SGSN CG





4. G-CDR Generation a. G-CDR Generation Objective:

P context.

he CDR to CG.

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 PD

Expected Result: GGSN generates G-CDR sends t

GGSN CG


ata Record Transfer Response

text.

GG .

E. CG 1. C

D

The MS deactivates PDP con

Expected Result: SN generates G-CDR sends the CDR to CG

DR Backup

a. Test Procedure:

G to back up final CDRs to a

After the CG backs up the final CDRs, browse the destination directory.

ory configured.

CDR Backup Objective: Check if the CG can back up the CDR files to the local disk.

Modify the configuration file of Cdestination directory of local disk. Restart CG to enable modification.

Expected Result: Final CDRs are backed up to the destination direct

2. CG Client Function a

che ’s right.

r account with wrong

ect password to log into the Client as an administrator.

. CG Client Function – User Management Objective:

Check if the CG can add user, delete user, modify user’s attribute and ck user

Test Procedure: Input a non-existent account or the administratopassword. Input corr Add a new user account. Modify the new user’s attributes. Query the attributes of this account.



Date 9/27/2006

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


ed account.

.1.3 RA

Delete the new user account. Log on again with the delet

Expected Result: CG can add user, delete user, modify user’s attribute and check user’s right.

6 N Testing

tests are divided into 4 main parts:

• •

A.

Ser g CS Domain

For RAN testing, the• Bearer Capability Test • Mobility Management

Logical O&M Radio Resource Management and Control

Bearer Capability Test vice Bearin1.

a. AMR Speech Service (12.2K)

ce

ersation.

ng AMR Speech service

n UL and DL.

UE1 and UE2 start conversation.

R Speech service

L and DL.

rvice.

s.

T mal. The video is clear and

Test the fun

Objective: ction of bearing AMR Speech servi

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 conv

Expected Result: The call is normal and voice is legible.

b. AMR Speech Service (10.2K) Objective:

Test the function of beari Test Procedure:

Set the parameters for 10.2K speech service o UE1 calls UE2 UE2 rings and answers call.


c. AMR Speech Service (4.5K) Objective: Test the function of bearing AM

Test Procedure: Set the parameters for 4.5K speech service on U UE1 calls UE2 UE2 rings and answers call. UE1 and UE2 start conversation.


d. CS Transparent Data Service Objective: Test the function of bearing CS transparent data se Test Procedure:

UE1 calls UE2 by video call. UE2 answers the video call and holds the call for 2 minute Either UE1 or UE2 ends the video call.

Expected Result: video call on both UE1 and UE2 is norhe

the voice is audible.



Date 9/27/2006

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


2. Service Bearing PS Domain a. P nlink 64K)

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. ter uploading or downloading.

esult: mally.

3. Co

S Data Service (uplink 64K + dow Objective:

UE logs out to end the PS service afExpected R

The UE can access the Internet and upload/download files nor

mbined Service Bearing ata Service (uplink 64K + downlink 64K a. PS D )

O T ch service (uplink 12.2 Kbps +

d 84K) T

k to 384 o 12.2 Kbps.

ses the Internet and downloads files.

and starts conversation.

after files have been

T oad files normally. The s normal and clear.

b. 1

+ O T tion of bearing 1 CS transparent data service (uplink 64 Kbps

+ downlink 64 Kbps) + 1 PS data service (uplink 64K + downlink 144K)

aximum bit rate on the uplink to 64 Kbps and downlink to 144

S nt data service

bjective: est the function of bearing 1 AMR speeownlink 12.2 Kbps) + 1 PS data service (uplink 64K + downlink 3est Procedure:

Set the maximum bit rate on the uplink to 64 Kbps and downlinKbps. Set the AMR speech t

UE1 starts PS service. UE1 brow UE2 calls UE1. UE1 answers the call Either UE1 or UE2 ends the conversation. UE logs out of the Internet to end the PS servicedownloaded.

Expected Result: UE can access the Internet and downlhe

conversation between UE1 and UE2 i

CS Transparent Data Service (uplink 64K + downlink 64K) 1 PS Data Service (uplink 64K + downlink 144K) bjective: est the func

Set the m

Test Procedure:

Kbps. UE1 starts PS service. UE1 browses the Internet and downloads files.

et uplink/downlink 64 Kbps videophone of CS transparefor UE. UE2 calls UE1 by video call. UE1 answers the video call and starts conversation. Either UE1 or UE2 ends the video call.



Date 9/27/2006

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


e been

load files normally. The video all between UE1 and UE2 is normal and clear.

UE logs out of the Internet to end the PS service after files havdownloaded.

Expected Result: The UE can access the Internet and downc

4. SMS Service Bearing

a. SMS Service on CS Bearing

U s it to UE2.

s the message

b

T 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

Objective: Test the SMS Service on CS Bearing. Test Procedure:

On HLR, set UE1 and UE2 transmitting SMS service through MSC. E1 composes a text message and send

Expected Result: UE1 sends the message successfully and UE2 receivecorrectly.

. SMS Service on PS Bearing Objective:

est the SMS

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:

O :

Tses on the internet.

nversation.

The UE2 rings after being called. b. Page UE in CELL_DCH State

bjective Test the function of paging UE in CELL_DCH state

est Procedure: E1 logs in to the WWW server and brow U

UE2 calls UE1 UE1 rings and answers call. UE1 and UE2 start co

Expected Result: The UE1 rings during web browsing and after being called by UE2.

2. Soft Handover a. AMR Speech Service Soft Handover

service.

nd CELL2. mode.

U 2 start conversation.

Objective: Test the function of soft handover for AMR speech

Test Procedure: NodeB1 and NodeB2 are configured to handle two intra-frequency

neighboring cells, CELL1 a UE1 camps on CELL1 in idle UE1 calls UE2

E2 rings and answers call. UE1 and UE



Date 9/27/2006

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


trigger a soft handover.

oving to CELL2.

UE1 moves from CELL1 to CELL2 toExpected Result: The conversation is still legible while UE1 is m

UE NodeB2 RNC

RL Setup Req

RL Setup Rsp

Active Set Update

Active Set Update Complete

b. Vid ver

Test Procedure:

intra-frequency ring cells, CELL1 and CELL2.

mode.

U 2 start conversation. ger a soft handover.

oving

c. PS S andover

NodeB1 and NodeB2 are configured to handle two intra-frequency cells, CELL1 and CELL2.

he Internet. er.

to

d. Co Te

UE1 answers the call and starts conversation.

eo Telephone Service Soft Hando Objective:

Test the function of soft handover for video telephone service.

NodeB1 and NodeB2 are configured to handle twoneighbo

UE1 camps on CELL1 in idle mode. UE2 camps on CELL1 in idle UE1 starts video telephone and calls UE2.

E2 rings and answers call. UE1 and UE trig UE1 moves from CELL1 to CELL2 to

Expected Result: s still legible and video is normal while UE1 is mThe conversation i

to CELL2.

ervice Soft HObjective:

Test the function of soft handover for PS service. Test Procedure:

neighboring UE camps on CELL1 in idle mode.

he WWW server and surfs in t UE visits t UE1 moves from CELL1 to CELL2 to trigger a soft handov

Expected Result: Surfing in the Internet is normal without interruption while UE1 is moving

CELL2.

mbined Service Soft Handover Objective:

st 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.



Date 9/27/2006

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


L2 to trigger a soft handover.

rnet is normal without interruption and the conversation is legible while UE1 is moving to CELL2.

3. Hard Handover

UE1 moves from CELL1 to CELExpected Result: Surfing in the Inte

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 boring cells, CELL1 and CELL2. ps on CELL1 in idle mode. the WWW server and surfs in the Internet. s from CELL1 to CELL2 to trigger an intra-frequency hard

urfing in Internet keeps normal without

neigh UE cam UE visits UE movehandover.

Expected Result: While UE is moving to CELL2, s

interruption.

UE NodeB2 RNCNodeB1

RL Setup Req

RL Setup Rsp

Physical Channel Reconfiguration

Physical Channel Reconfiguration Complete

RL Del Req

RL Del Rsp

ice Inter-Frequency Hard Handover

rd handover for AMR speech

B2 are configured to handle two inter-frequency

CELL2.

1. UE1 answers the call and start the conversation.

s from CELL1 to CELL2 to trigger an inter-frequency hard

onversation is normal.

c.

y hard handover for video telephone

Test Procedure: NodeB1 and NodeB2 are configured to handle two inter-frequency

neighboring cells, CELL1 and CELL2.

b. Speech Serv

Objective: Test the function of inter-frequency ha

service. Test Procedure:

NodeB1 and Nodeneighboring cells, CELL1 and

UE1 camps on CELL1 in idle mode. UE2 calls UE

UE movehandover.

Expected Result: While UE is moving to CELL2, c

Video Telephone Inter-Frequency Hard Handover Objective: Test the function of inter-frequencservice.



Date 9/27/2006

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


n CELL1 in idle mode. s on CELL2 in idle mode.

calls UE2. d start the conversation.

ger an inter-frequency hard

d the picture is

d. PS Service Inter-Frequency Hard Handover ard handover for PS service.

ure: ncy

2.

ernet. 2 to trigger an intra-frequency hard

Expected Result: While UE is moving to CELL2, surfing in Internet keeps normal without

interruption.

ervice Inter-Frequency Hard Handover

rd handover for CS and PS service.

andle two intra-frequency CELL2.

UE1 visits the WWW server and surfs in the Internet.

ers call and start the conversation.

al without is legible.

4. Forward Handover

UE1 camps o UE2 camp UE1 starts video telephone and UE2 answers the video call an UE1 moves from CELL1 to CELL2 to trighandover.

Expected Result: While UE1 is moving to CELL2, conversation is normal anclear.

Objective: Test the function of intra-frequency h

Test Proced NodeB1 and NodeB2 are configured to handle two intra-freque

neighboring cells, CELL1 and CELL UE camps on CELL1 in idle mode. UE visits the WWW server and surfs in the Int UE moves from CELL1 to CELLhandover.

e. Combined S

Objective: Test the function of intra-frequency ha

Test Procedure: NodeB1 and NodeB2 are configured to h

neighboring cells, CELL1 and UE1 camps on CELL1 in idle mode.

UE2 calls UE1. UE1 answ UE moves from CELL1 to CELL2 to trigger an inter-frequency hardhandover.

Expected Result: While UE is moving to CELL2, surfing in Internet keeps norminterruption and the voice conversation

a. Cell Update Triggered by Cell Reselection

tion of cell update triggered by cell reselection.

le two intra-frequency neighboring cells,

and browses the Internet. n 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.

Objective: Test the func Test Procedure:

NodeB1 is configured to handCELL1 and CELL2.

UE camps on CELL1 in idle mode. UE logs in to the WWW server UE does not perform the data transmission for more tha



Date 9/27/2006

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


Expected Result: d downlink data transmission remains normal before and The uplink an

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.

has 3G signal and can originate a call.

a was correctly configured.

ation in Node B.

Cell is configured. l. Modify the PCPICH power.

esult:

c. Test Procedure:

correctly in Node B. tes a call and the conversation is normal.

e call was

d. Cell Block

tion of cell block.

Node B.

The cell blocked and the call was disconnected.

UEExpected Result:

The cell dat b. Cell Reconfiguration

Objective: Test the function of cell reconfigur

Test Procedure:

Reconfigure the celExpected R

The cell data was correctly reconfigured.

Cell Deletion Objective:

Test the function of cell deletion in Node B.

Cell is configured UE origina Remove the cell.

Expected Result: The cell data was deleted. The 3G signal disappeared and thdisconnected.

Objective:

Test the func Test Procedure:

Cell is configured correctly in UE originates a call and the conversation is normal. Block the cell.

Expected Result:



Date 9/27/2006

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


lock.

ure:

riginate a call. 2. Co nnel

e. Cell Unblock Objective: Test the function of cell unb

Test Proced 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 o

mmon Transport Cha a. p

Test the function of common transport channel setup in Node B.

CCPCH and FACH channels in the cell.

ectly configured. b. C l Reconfiguration

Te transport channel reconfiguration in Node B.

channels. Check if the parameters were modified.

t: ort channel parameters were correctly changed.

n

annel deletion in Node B.

sical channel.

Expected Result:

3. Sy

Common Transport Channel Setu Objective: Test Procedure:

Add the S Configure other parameters of the channels.

Expected Result: The common transport channels were corr

ommon Transport ChanneObjective:

st the function of commonTest Procedure:

Modify some parameters in SCCPCH and FACH

Expected Resul The common transp

c. Common Transport Channel Reconfiguratio

Objective: Test the function of common transport chTest Procedure:

Remove an SCCPCH common phy Query the state of the SCCPH common physical channel.

The SCCPH common transport channel was deleted.

stem Information a.

Test the function of system information update.

ystem update. oadcasts the system information periodically on BCH.

tem information to RNC.

System Information Update Objective: Test Procedure:

The RNC request the Node B for the s Node B br

Expected Result: The Node B broadcasts the sys

RNC NodeB

SYSTEM INFORMATION UPDATE REQUEST

SYSTEM INFORMATION UPDATE RESPONSE



Date 9/27/2006

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


4. Re

source Audit a. Ce urce Audit

The data shows the resources of the cell.

ll ResoObjective:

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:

RNC NodeB

AUDIT REQUEST

AUDIT RESPONSE

5. Tracing a. Uu Interface Traci

ive:

messages over the Uu interface.

b.

O Te

The trace me c.

interface.

Te

T

ng bjectO

Test the function of Uu interface tracing. ure: Test Proced

Initiate a call and view theExpected Result:

The trace messages from the Uu interface are seen.

Iub Interface Tracing bjective: st the function of Iub interface tracing.

Test Procedure: Initiate a call and view the messages over the Iub interface.

Expected Result: ssages from the Iub interface are seen.

Iu Interface Tracing Objective: Test the function of Iu interface tracing.

est Procedure: T Initiate a call and view the messages over the Iu

esult: Expected R The trace messages from the Iu interface are seen. d. Single User Tracing

Objective: Test the function single user tracing.

st Procedure: Initiate a call and view the messages of a single user.

Expected Result: he trace messages from a single user is seen.



Date 9/27/2006

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


D. Radi 1. Adm

o Resource Management and Control ission Control

a. CS Te

CELL1. .

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 d in idle state. Configure CELL1 S 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

Call Admission Control Objective:

st the function of CS call admission control. Test Procedure:

Node B is configured to handle UE1, UE2, UE3, and UE4 camp on CELL1 and in idle state

CELL1 an to handle 2 P

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.

ntrol

3. Load Balancing Co a. Intra-frequency Load Balancing Control

s: CELL1 and CELL2 which are

L1 and are in idle state. start an AMR speech service.

wsing. .

Objective: Test the function of intra-frequency load balancing Test Procedure:

The Node B is configured with two cellintra-frequency neighbor cells. Node B is configured to handle CELL1. UE1, UE2, and UE3 camps on CEL UE1 calls UE2 to UE3 logs in to a web Server and starts web bro UE1 and UE2 move to the edge of the cell Change the DL load of CELL1 to simulate the heavy load state.



Date 9/27/2006

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


lot transmit power of CELL1 er from CELL1 to CELL2 of UE1 and

dified.

it power decreases, UE1 and UE2 at

Observe the change of the pi Observe the process of handovUE2.

Expected Result: Observe the cell PCPICH pilot transmit power: RNC will decrease the cell PCPICH pilot transmit power after the cell load is moAfter the cell PCPICH pilot transmthe edge of CELL1 are handed over to CELL2.

4. Dynamic Resource Control a.

he conversation.

tion – Rate Adjustment

rnet to perform FTP service. m the

ses to the maximum bit

e situations and the

c. Dynamic Channel Configuration – State Transition

e transition function of dynamic channel configuration.

er to 128 Kbps.

rnet to perform FTP service. nload are normal. The bit rate increases from the

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.

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 t 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 4750bits/s.

b. Dynamic Channel Configura 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 InteBoth upload and download are normal. The bit rate increases frointermediate 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 increarate. UE logs out of the FTP server and ends the PS service.

Expected Result: The bit rate of the UE changes according to servicFTP service is normal.

Objective: Test the stat Test Procedure:

ate QOS parametSet the uplink/downlink max bit r UE starts the PS service (128K).

server on the Inte UE logs in to an FTPBoth upload and dowintermediate 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



Date 9/27/2006

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


TP service for another period (greater than the timer for the transition from FACH to m FACH to PCH state.

ing to use the FTP service, UE transits from PCH to H to DCH state. The service is normal. and ends the PS service.

FACH to PCH, and vice versa.

UE does not perform the F180 seconds, the length ofPCH). Then, UE transits fro When continuFACH state and then from PC UE logs out of the FTP server

Expected Result: The UE transits from DCH to

UE NodeB RNC

RL Recfg Prep

RL Recfg Ready

RL Recfg Commit

RB Recfg

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

5. Po

FACH TO PCH

wer Control a. Objective:

Uplink Outloop Power Control

ndle Node B. red to handle CELL1.

le mode. ower control is enabled.

e conversation.

adio link quality varies accordingly.

Test the function of uplink outloop power control. Test Procedure:

RNC is configured to ha Node B is configu UE1 and UE2 camps on CELL1 in id Outloop p UE1 calls UE2. UE2 answers call and starts th Monitor UE UL BLER and UL SIRTarget. UE moves in the cell. The r



Date 9/27/2006

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


.

t value. The increases when the UL BLER value is greater than the

n smaller.

control.

om Node B, and then towards Node B.

he SIR Target. the

cing

mong DL radio link in soft handover.

intra-frequency neighboring cells,

is enabled. d remains in connected mode.

Nod ent reports periodically. When the DL code links exceed the high threshold, RNC

al and the voice is clear.

UE1 ends the conversationExpected Result: The UL BLER value fluctuates based on the UL BLER targeUL SIRtarget valueUL BLER target value; decreases, whe

b. Uplink Inner Loop Power Control Objective:

Test the function of uplink inner loop power ure: Test Proced

RNC is configured to handle Node B. e CELL1. Node B is configured to handl

UE1 and UE2 camps on CELL1 in idle mode. d. Outloop power control is enable

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 fr UE1 ends the conversation.

Expected Result: When UE moves away from Node B, UE transmit power increases and the uplink SIR is approximate to tWhen UE moves towards Node B, UE transmit power decreases and uplink SIR is approximate to the SIR Target.

c. Downlink Power Balan Objective:

tion of power balancing a Test the func Test Procedure:

wo RNC is configured to handle tCELL1 and CELL2.

mode. UE camps on CELL1 in idle Downlink power balancing

call in CELL1 an UE1 originates a UE moves from CELL1 to CELL2, which triggers soft handover, CELL2 is added into the active set.

nnected to the two radio links. UE maintains coExpected Result:

eB sends the measuremTx power values of the two radio sends the DL power control command to NodeB. The conversation is norm

6.1.4 Services Testing

Fo d into 3 main parts:

• •

NOTE: t-up of

ices testing, the tests are divide•

r ServShort Message Services (SMS)

ces (MMS) Multimedia Message ServiVideo Call Services

Some of the services may not be tested, depending on the 3G sethe vendor. The procedure may vary for each vendor.



Date 9/27/2006

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


A. Short Message Services (SMS) 1. Authenticating Subscriber a. Authenticating the calling party

system work normally.

S 3.

ubmitted successfully.

Accessing SMC

Objective: Authenticating the calling party

Test Procedure: The SMC and the wireless MS1 belongs to the SMC. MS2 has not been registered in the SMC. Send a short message from MS1 to MS3.

end a short message from MS2 to MS Observe and record the phenomenon.

Expected Result: It is displayed on MS1 that the short message is sIt is displayed on MS2 that the short message is sent unsuccessfully

2.

at

sent from MS1.

ng time and contents of the short message are consistent with the actual situation.

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 th

MS1 belongs to. Query the MT console for the short message

Expected Result: The following query result should be obtained. MS1 sends a short message to MS2, and the sendi

3. Submitting and Storing SMs a. Submitting and storing MS-to-MS SMs

S short message.

system work normally.

MS1 to MS2 ery function of the SMC MT console that

m MS1.

The following query result should be obtained. to MS2, and the sending time and

the short message are consistent with the actual situation. .

Objective: Submitting and storing MS-to-M

Test Procedure: The SMC and the wireless MS1 belongs to the SMC. MS2 belongs to the SMC. Send a short message from Start the short message qu

MS1 belongs to. Query the short message sent fro

Expected Result: MS1 sends a short message

contents of

4. Forwarding SMs a. prompt.

m work normally. MS1 belongs to the SMC.

Forwarding after receiving SM prompt Objective: Forwarding after receiving SMTest Procedure:

The SMC and the wireless syste



Date 9/27/2006

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


Switch on MS2.

esult: can be viewed.

b. Test Procedure:

nction of the SMC has been set, and

Switch off MS2. m MS1 to MS2.

monitor observe the signallings m the SMC.

and retries forwarding the short message every T1.

5. Pr

MS2 belongs to the SMC. Switch off MS2. Send a short message from MS1 to MS2 can be viewed.

View MS2. Expected R

The short message sent from the SMC to MS2

Retrying forwarding SMs automatically Objective: Retrying forwarding SMs automatically.

The SMC and the wireless system work normally. MS1 belongs to the SMC. MS2 belongs to the SMC. The automatic forwarding-retry fu

the time is T1.

Send a short message fro After waiting for T1, from the signalling

sent froExpected Result: It can be viewed that the SMC queries the MS2 status from the HLR

iority Processing

a. irst. Tes

m work normally.

Send 3 short messages of low priority from the DEMO to MS2. riority from the DEMO to MS2.

signalling monitor, observe the short message delivery

en the short b. temporarily absent.

priority forcibly when MS is

C and the wireless system work normally.

MS1 belongs to the SMC.

MS2. MS2.

priority from the DEMO to MS2.

attempts to forward the short message of

Sending SMs of high priority fObjective: Sending SMs of high priority first.

t Procedure: The SMC and the wireless syste MS1 belongs to the SMC. MS2 belongs to the SMC. Switch off MS2.

Send a short message of high p Switch on MS2 From the

sequences from MS2. Expected Result: The short message of high priority is received first, th message of low priority.

Forwarding SMs of high priority forcibly when MS isObjective: Sending SMs of high priority high

temporarily absent. Test Procedure:

The SM

MS2 belongs to the SMC. Switch off Send a short message of low priority from the DEMO to Send a short message of high

Expected Result: It can be seen that the SMC high priority forcibly.



Date 9/27/2006

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


6. Requesting Status Report a. warding notification (successful forwarding). bjective: on (successful forwarding).

ally. MS1 belongs to the SMC.

s entering the attribute of request for the status report. and set the attribute of

as YES.

C, that g).

b. tion (permanent failure).

The SMC and the wireless system work normally.

ngs to the SMC. quest for the status report.

ice of MS2 in HLR. he attribute of

tatus report as YES.

MS rt sent from the SMC, that is,

Status report-forO Status report-forwarding notificati

Test Procedure: The SMC and the wireless system work norm

MS2 belongs to the SMC. MS1 support Send a short message from MS1 to MS2,

request for the status report 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 SM

is, forwarding notification (successful forwardin

Status report-unforwarding notifica Objective: Status report-unforwarding notification (permanent failure). Test Procedure:

MS1 belongs to the SMC. MS2 belo MS1 supports entering the attribute of re Close the short message serv Send a short message from MS1 to MS2, and set t

request for the s Observe the information displayed on MS1.

Expected Result: 1 receives the status repo

unforwarding notification (permanent failure).

7. Supporting SMs in English/Tagalog

to the SMC. The SMC and the wireless system work normally.

ngs to the MSC.

e. b.

rmally.

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

MS1 belongs to the MSC. MS2 belo

Expected Result: MS2 receives this short messag

The contents of this short message are displayed correctly.

Supporting SMs in Tagalog. Objective: Supporting SMs in Tagalog. Test Procedure:

The SMC and the wireless system work no 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.



Date 9/27/2006

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


Test Procedure:

rmally. ngs to the SMC.

isplay both in English and

from MS1 to MS2.

tly.

8. Sup

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

The SMC and the wireless system work no MS1 belo MS2 belongs to the SMC and supports the d

Tagalog Send a short message in both English and Tagalog Observe the reception by MS2.

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

porting Long SMs a. bytes. bytes or 160 ASCII characters (7-bit

The contents of this short message are displayed correctly

d Test Function

Supporting long SMs of over 140 Objective: Supporting long SMs of over 140code), 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.

9. Maintenance an rs-setting country code.

.

The SMC and the wireless system work normally.

S ode).

sh>.

ters-modifying the deleting mode.

rs-modifying the deleting mode.

onsole. tting) menu.

a. Setting system paramete Objective:

Setting system parameters-OCOS and TCOS settingTest Procedure:

Log in to the MT console. elect the (System/System Parameter Setting) menu.

Modify environment parameters (country c Select Confirm and click <Refre

Expected Result: Modifying parameters succeeds. The default values of OCOS and TCOS are consistent with the set values. b. Setting system parame

Objective: Setting system paramete

Test Procedure: The SMC and the wireless system work normally. Log in to the MT c Select the (System/System Parameter Se Select an item of wrong type, such as Absent Subscriber.



Date 9/27/2006

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


nd modify the deleting mode.

r of SMs.

urce monitor-number of SMs.

tem work normally.

esource Monitor). “Number of

then start monitor.

Exp gistered re displayed in the window.

SMs in the SME

ss system work normally. he MT.

M Monitor) menu. ). Set the time segment (start time and

ed in the window.

The sou mbering sch id, teleservice id, privacy, language t, SMC. e

: The SMC and the wireless system work normally.

est/SM Monitor).

user number in the User ISDN No bar.

The displayed short message attributes include the following: SM ID, ss, Numbering Plan Identification (NPI), source address, destination

Click <Modify Deleting Mode> a Click <OK>.

Expected Result:

Modifying parameters succeeds. The modified deleting mode comes into effect. c. System resource monitor-numbe

Objective: System reso

Test Procedure: The SMC and the wireless sys Log in to the MT. Enter (Monitor/Test/System R Select “Number of SMs”, ‘Number of SM entities”,

registered subscriber”, and Observe what is displayed in the window.

ected Result: The SM number monitoring function is provided normally. The number of SMs, number of SM entities and number of re subscribers existing in the SMC a

d. Querying SMs-querying

Objective: Querying SMs-querying SMs in the SME.

Test Procedure: The SMC and the wirele Log in to t Select the (Monitor/Test/S Select the SM type (MO or MT

end time) for observing. Observe what is display

Expected Result: short messages can be viewed.

The displayed short message attributes include the following: SM ID, rce address Type of Number (TON), source address Nu

Plan Identification (NPI), destination address, SM priority, data codingeme (DCS), timing time, timeout time, expiry time, SM status, error

number, delivery times, message indicator, From MC Address, reference id, callback number, SM Conten

. Querying SMs-querying SMs in the memory Objective: Querying SMs-querying SMs in the memory. Test Procedure

Log in to the MT. Select the (Monitor/T Select the Query SM tab and select Query Memory. Enter the 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

Service type, source address Type of Number (TON), source addre



Date 9/27/2006

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


typ TMSC address, address type of y, RD, SR, RP, UDHI, timeout time, tele nguage indicator, From MC Address, f

less system work normally.

Short messages exist in the database of the SMC.

(Monitor/Test/SM Monitor).

er in the User ISDN No bar. o more than three months).

Observe what is displayed in the window.

be viewed Num ss, destination s SM g mode, SM priority, RD, SR, RP, UDHI, me (DCS), timing time, timeout time, ery times, message id, , callback number, SM Content, SMC

g Objective:

ure:

ministration window of the maintenance and test

rs, he displayed information.

ma t function. h. I

Test Procedure: he wireless system work normally. T.

account management window.

address TON, destination address NPI, destination address, address e of MOMSC, MOMSC address, M

SMC, SMC address, scheduling mode, SM priorit Message Index, data coding scheme (DCS), timing time, expiry time, SM status, error number, delivery times, message id,

service id, privacy, la reference id, callback number, SM Content, SMC.

. Querying SMs-querying SMs in the database Objective: Querying SMs-querying SMs in the database. Test Procedure:

The SMC and the wire

Log in to the MT. Select the Select the Query SM tab and select Query database. Enter the user numb Select Query time segment (n Click <F3> or click <Query>.

Expected Result: The short messages existing in the memory of the SMC can The displayed short message attributes include the following: SM ID, Service type, source address Type of Number (TON), source address,

bering Plan Identification (NPI), source addre address TON, destination address NPI, destination address, addres type of MOMSC, MOMSC address, MTMSC address, address type of

C, SMC address, schedulin Message Index, data coding sche

expiry time, SM status, error number, deliv teleservice id, privacy, language indicator, From MC Address, reference id

. Account Management

Account Management. Test Proced

The SMC and the wireless system work normally. Enter the account ad

console. Perform such operations as adding account deleting account numbe

refreshing t Observe what is displayed in the window.

Expected Result: Various accounts, such as gateway account and service account, are

naged in a unified way through the account managemen The MT console can successfully perform the operations above to account numbers.

nterface Management Objective: Interface Management.

The SMC and t Log in to the M Enter the Conduct the operations of adding and deleting intefaces.



Date 9/27/2006

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


ch as gateway interface, DEMO interface, MT management function. operations as

10. D

Expected Result: Various interfaces, su

interface, are managed in a unified way through the interface

The user can conduct such interface management querying, adding, deleting, refreshing, confirming.

atabase Module Functions base module function. a. Data

Test Procedure: em work normally.

ages Send several short messages to the SMSC with the demo.

essages in the history database of the SMC. esult:

the history

stor tory database of the SMC through DBDaemon.

11. L

Objective: Database module function

The SMC and the wireless syst 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 mess

Query the mExpected R

The database module is successfully connected with database of the SMC.

The short messages delivered with success or permanent failure are ed in the his

icense Configuration a.

F se.lic file to the SMSC computer.

he SMC MT console. test tool SubmitDemo and observe the

f the message.

We observe from the SMC MT console that the SMC runs in the normal rs in the common mode observed from the MT console parameters set in alue exceeds the set value, submitting the

B. Multimedi 1. Ba

Reading legal license file. Objective: Reading legal license file. Test Procedure:

TP the legal Licen Start the active SMSC. Observe the current SMC running mode in (System/Browser License

SMC) on t Submit the message using the

restrictions of SMC on all parameters o 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:

mode. All paramete are consistent with those set in the license file. The SMC controls the message submission based on the license file. If the v message fails.

a Message Services (MMS) sic Service Flows

a. M To MMS can be retrieved immediately if they are sent Test Procedure:

nt

bscribers of the MMSC.

MS UA to MMS UA in the Single MMSC (MM/DR/RR) Objective:

test whether from MMS terminal 1 to MMS terminal 2 via the same MMSC.

The MMSC, WAP, GW, WCDMA network and wireless environmework well.

MMS terminals 1 and 2 are registered su



Date 9/27/2006

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


terminal 1 has requested read report if the terminal support the

et to get the MM instantly. Send an MM composed of text, voice and image from MMS terminal 1

message status and related information in the MMSC.

MSC successfully. MMS terminal 2 can receive the prompt of red report request (Optional)

b. MMS (MM/DR) through the MMSC.

t

. subscriber of the MMSC.

uesting delivery report. ed of text, voice and image to an

Email account (for example, Yahoo Mailbox). mation in the MMSC.

ether the message has been received and displayed normally

MSC successfully. as o he MM has

c. Em Obj through the MMSC.

M A , Yahoo Mailbox) sends an MM

C d information in the MMSC. s been received and displayed normally

2. Basic Features

MMS setting of read report. (Optional)

MMS terminal 1 has requested delivery report. MMS terminal 2 has been s

to MMS terminal 2. Check the

Expected Result: The MM reaches the M 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 sent successfully.

UA to EmailObjective: To test sending MMS from an MMS terminal to an Email address

Test Procedure: The MMSC, WAP GW, WCDMA network and wireless environmen

work well. The Email gateway or Email server works well MMS terminal 1 is a registered MMS terminal 1 has enabled the function of req MMS terminal 1 sends an MM compos

Check the message status and related infor Check wh

at the Email account. Expected Result:

The MM reaches the M The MM can received and displayed normally at the Email client such

utlook. MMS terminal 1 can receive a delivery report showing that t been sent successfully.

ail to MMS UA (MM) ective:

To test sending MMS from an MMS terminal to an Email address

Test Procedure: The MMSC, WAP GW, WCDMA network and wireless environment

work well. The Email gateway or Email server works well.

MS terminal 1 is a registered subscriber of the MMSC. n email account (for examplecomposed of text, voice and image to MMS terminal 1. heck the message status and relate

Check whether the message haat MMS terminal 1.

Expected Result: The MM reaches the MMSC successfully. The MM can receive and displayed normally at the MMS terminal 1.

a. Multiple recipients Objective:

To test sending MMS from MMS terminal 1 to MMS terminal 2, an



Date 9/27/2006

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


plication through the MMSC.

C.

from MMS terminal 1 to

related information in the MMSC. terminal 2,

and Email box.

ches the MMSC successfully. ormally. nd displayed normally at the Email account.

indi sults of terminal 2 and the Email account.

b. V Obj

twork and wireless environment

MMS terminals 1 and 2 are registered subscribers of the MMSC. ction of requesting delivery report.

lidity period to one hour or a shorter period like 1 minute.

n MM composed of text and image from MMS terminal 1 to MMS

MMS terminal 2 is switched on after the MM is expired. (For example 3

c. Speci liver Time

and Application to MMS

ork and wireless environment

work well. ers of the MMSC.

inal 1 has enabled the function of requesting delivery report.

y seconds for sending from MMS terminal 1 to MMS

Send an MM composed of text and image from MMS terminal 1 to MMS

Expected Result: The MMSC delivers the MM less than 1 minute depending how big the

Email account, or an ICP ap 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 MMS MMS terminal 1 requests for delivery report. Send an MM composed of text and image

Email account, and to MMS terminal 2. Check the message status and Check whether the message has been received the MMS

Expected Result: The MM rea MMS terminal 2 can receive the MM successfully and display n The MM can receive a

MMS terminal 1 can receive two delivery reports, which respectively cate the delivery re

alidity Period

ective: To test the correctness of the validity period setting. Test Procedure:

The MMSC, WAP GW, WCDMA nework well.

MMS terminal 1 has enabled the fun Set the va MMS terminal 2 is switched off. Send a

terminal 2. Check the message status and related information in the MMSC.

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).

fy the Earliest deObjective:

To test sending MMS from MMS terminal 1 terminal 2 through the MMSC at the specified time. Test Procedure:

The MMSC, WAP GW, WCDMA netw

MMS terminals 1 and 2 are registered subscrib MMS term MMS terminal 2 has been set to get the MM instantly. Counting how man

terminal 2.

terminal 2. Check the message status and related information in the MMSC.

The MM reaches the MMSC successfully.



Date 9/27/2006

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


MMbee uccessfully.

The MMSC, WAP GW, WCDMA network and wireless environment

inals 1, 2,3 and 4 are registered subscribers of the MMSC. 2. If the

he specified value, the excessive recipients are

The SP is a registered application of the MMSC.

S , and 4 simultaneously

MM successfully.

fully.

e. A bjective:

ctions of updating the subscriber information in database ly and auto provisioning for new subscriber.

W, WCDMA network and wireless environment

MMS terminal 1 is a registered subscriber of the MMSC. r

M

S 2, 3 and 4

al 1 to mobile terminal 2. d

Check whether the information of mobile terminal 1 has been refreshed d whether the information of mobile

l 2 has been added. om the subscriber

peat steps 1-3.

Mob 2 can receive the MM correctly. minal 1 has

f. S

To

MM is. MMS terminal 2 can receive the MM successfully and display normally.

S terminal 1 can receive a delivery report showing that the MM has n delivered s

d. Maximum Number of Receptions Objective: To test the function of checking the number of recipients Test Procedure:

work well. MMS term The maximum number of supported recipients has been set to

number reaches tcancelled.

Send an MM from MMS terminal 1 to MMS terminals 2, 3 and 4 simultaneously. end an MM from SP to MMS terminals 2, 3, 4

Check the message status and related information in the MMSC. Expected Result:

S terminal 1 sends the MMSC SP sends the MM successfully.

MMS terminal 2, 3 receive the MM success MMS terminal 4 fails to receive the MM.

uto provisioning and refreshing of subscriber O

To test the fun automatical Test Procedure:

The MMSC, WAP Gwork well.

MMS terminal 1 is defined as a non-MMS terminal in the subscribedatabase. MS terminal 2 belongs to this MMSC, but there is no related information for it in database. end an MM from MMS terminal 1 to MMS terminals simultaneously.

Send an MM from mobile termin Observe whether the MM is sent successfully by mobile terminal 1 an

received by mobile terminal 2.

in the subscriber database, antermina

Delete the information of mobile terminal 1 frdatabase. Then re

Expected Result: ile terminal

The information of mobile terminals 1 and 2 has been refreshed in the subscriber database. That is, the terminal type of mobile ter been changed to MMS terminal and the correct user agent value is set, and the information of mobile terminal 2 has been added.

ystem-Level Blacklist Objective:

test whether the MMSC can deny MMS to or from the subscribers in



Date 9/27/2006

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


the Tes

ell.

M has been listed in the system-level blacklist. l 1 to MMS terminals 2.

1. Repeat step 2.

or from MMS terminal 1.

Tes e:

ss environment

e MMSC. ist

S from MMS terminal 1 to MMS terminals 2.

terminal 2.

h l

To test whether the MMSC supports the terminal-to-terminal delivery

dure: environment

Send an MM from MMS terminal 1 to MMS terminals 2.

.

C .

ps 1 and 2.

The MM reaches the MMSC successfully. M successfully and display normally.

t depending

T edia message has been set to

terminal 2.

system-level blacklist. t Procedure:

The MMSC, WAP GW, WCDMA network and wireless environment work w

MMS terminals 1 and 2 are registered subscribers of the MMSC.MS terminal 1

Send an MM from MMS termina Check the message status in the MMSC. Send an MM from MMS terminal 2 to MMS terminal

Expected Result: The MMSC denies the MM sent to

g. User-Level Blacklist Objective:

To test whether the system supports the user-level blacklist. t Procedur

The MMSC, WAP GW, WCDMA network and wirelework well.

MMS terminals 1 and 2 are registered subscribers of th MMS terminal 1 has been set as a subscriber in the user-level blackl

by MMS terminal 2. end an MM

Check the message status in the MMSC. Expected Result:

The MMSC rejects MMS terminal 1 sending the MM to MMS

. Delivery Report, Terminal-to-TerminaObjective:

report. Test Proce

The MMSC, WAP GW, WCDMA network and wirelesswork well.

MMS terminals 1 and 2 are registered subscribers of the MMSC.

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.

heck the message status and related information in the MMSC Set not to allow sending delivery report on MMS terminal 2. Repeat

steExpected Result:

MMS terminal 2 can receive the M MMS terminal 1 receives or fails to receive a delivery repor

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:


MMS terminals 1 and 2 are registered subscribers of the MMSC. he allowed maximum size of the multim100 KB.

Send an MM of 90 KB (less than 100 KB) from MMS terminal 1 to MMS



Date 9/27/2006

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


. S from MMS terminal 1 to

ation in

Exp d the maximum size, MMS terminal 2 size, the system enies it and returns the failure response message.

ber format

umber formats supported by the MMSC.

T AP GW, WCDMA network and wireless environment

C. S inal 1 to mobile terminal 2. The recipient

related information in the MMSC. lus an 8-digit mobile phone

number, and resend the MM.

ully. can identify the three recipient number formats and deliver

receive the MM successfully and display it normally.

k. Traffi

To ic control function of the MMSC.

T CDMA network and wireless environment

T mber of MMs processed in the MMSC is set to 3 our.

U o the MMSC. The .

submitted successfully.

The MMSC rejects the MMS that are beyond its processing capability. he MMSC rejects the MMS that are beyond the MMSC license.

rminal Performance

erminal-to-terminal performance.

MMS terminal 2 is a registered subscriber of the MMSC.

imulator1. S

sly for 15 times.

T ywords in the MMSC log, calculate the total number of

Check the message status and related information in the MMSCend an MM of 105 KB (more than 100 KB) MMS terminal 2. Check the message status and related informthe MMSC. ected Result:

For the MM less than the specifie can receive successfully, and display it normally.

For the MM greater than the specified the maximumd

j. Recipient num

Objective: To test the recipient n

Test Procedure: he MMSC, Wwork well.

MMS terminals 1 and 2 are registered subscribers of the MMSend an MM from mobile termnumber is an 8-digit mobile phone number.

Check the message status and Set the reception number as “+852” p

Expected Result: The MM reaches the MMSC successf The MMSC a notification message to the recipient.

Mobile terminal 2 can

c Control Objective:

test the traffTest Procedure:

he MMSC, WAP GW, Wwork well.

MMS terminals 1 and 2 are registered subscribers of the MMSC. he maximum nupieces per second. The license of the MMSC is 3600 piece per hse a simulation tool to submit numerous MMS tsubmission speed exceeds 5 pieces per second

Observe whether the MMS are Expected Result:

T

l. Terminal-to-Te Objective:

To test the t Test Procedure:


The MMS terminal simulators are registered subscribers of the MMSC.

Set the number of MMS sent per second on mobile terminal send MMS from mobile terminal simulator 1 to mobile terminal 1 continuou

Check the message status and related information in the MMSC. hrough the keMMS. Through the start time in log, obtain the length of time needed



Date 9/27/2006

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


uccessfully.

m. S Objective:

To test System Blacklist function at the MM3 interface.

AP GW, WCDMA network and wireless environment

unt 1 is a valid account of Email Domain 1. valid account of Email Domain 2.

The ace is configured to use blacklist, which contains Email

Em is not in the blacklist of MM3 interface.

TheExpected Result:

In pIn ste

n. Sys Objec

To tes Test

The GW, WCDMA network and wireless environment

MM Em can send and receive Email normally.

s configured to use Whitelist, which contains the

The rminal .

The l 1.

E c In ste

In step 6, the Email account 2 sends the MM failed.

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

the MM message size function at the MM3 interface. T

ronment

M l account can normally.

T The M s been set to support the MM max size of 100 KB.

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 successratio.

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 s ystem Blacklist in MM3 interface.

Test Procedure: The MMSC, W

work well. MMS terminal 1 is a subscriber of the local MMSC. Email acco Email account 2 is a Both Email accounts 1 and 2 can send and receive Email normally.

MM3 interfDomain 1.

ail Domain 2 The Email account 1 sends an Email to MMS terminal 1.

Email account 2 sends an Email to MMS terminal 1.

ste 8, the submission is failed. p 9, the submission is successful.

tem Whitelist in MM3 interface. tive: t System Whitelist function at the MM3 interface.

Procedure: MMSC, WAP

work well. S terminal 1 is a registered subscriber of the local MMSC. ail domain 1 and 2

The MM3 interface iEmail Domain 1. The Email domain 2 is not in the Whitelist.

Email account 1 of Email Domain 1 sends an MM to MMS te1

Email account 2 of Email Domain 2 sends an MM to MMS termina

xpe ted Result: p 5, the Email account 1 sends the MM successfully.

Objective: To verify limiting

est Procedure: The MMSC, WAP GW, WCDMA network and wireless envi

work well. MS terminal 1 is a subscriber of the local MMSC. The Emai

send and receive Email he system has been set to support the MM max size of 100 KB.

M3 interface ha



Date 9/27/2006

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


Tatta

The E MM to terminal 1, with the size of image, text, audio file and the other files with

ore than 300 KB. Exp e

In s 1 ends the MM successfully. In step 2, the Email account sends the MM failed.

p. Service D Objectiv

To test ent. Tes r

The M ment ork well.

the local MMSC. egment that terminal 2 belongs to has not been

erminal 2. Expected Result: MMS

3. Operatio n

he Email account sends an MM to terminal 1, with the size of chments being no more than 100 KB. mail account sends an

attachments (includingunknown format) being mect d Result:

tep , the Email account s

eny for specified Number Segment. e:

the services deny function for specified Number segmt P ocedure:

MSC, WAP GW, WCDMA network and wireless environw

MMS terminal 1 is a subscriber of The number s

configured on the MMSC. MMS terminal 1 sends an MM to MMS t

terminal 1 submit the MM failed.

n a d Maintenance e of user accou a. Maintenanc nt privilege.

Objectiv To test t Test Pro

Thwork

The cudata

nter the URL address of the Customer M

Log in C super administrator. Cre a

new o Log t in Customer

Management System using the new operator; created operator.

lt: g value-added

b. Maintenance nt system operators. Objec To test th ining the customer management system opera Test c

The , WCDMA network and wireless environment

The s h the da

Sta e er msyste

Enter the old password and new password to change the operator password.

Log in again, and check whether the new password has taken effect.

e: he function of maintaining the user account privilege. cedure:

e MMSC, WAP GW, WCDMA network and wireless environment well. stomer management system is connected normally with the base.

Start the IE browser, eanagement System.

ustomer Management System asate new operator, and grant right of “VAS administrator” to the

perator. ou the Customer Management System, and log

Check the privilege of the newExpected ResuThe new created operator has only the right of maintaininservices (VAS).

of customer managemetive:

e function of maintators. Pro edure: MMSC, WAP GW

work well. cu tomer management system is connected normally wittabase.

rt th IE browser, enter the URL address of the customanagement system, and then log in to the customer management

m.



Date 9/27/2006

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


g the new operator name and pa ck whether the settings have taken effect.

Mod y this op e modification has taken effect.

Del en log in using the operator name and password, an

ExpectedAfter a , the opera mOpera s operations ct in real time.

c. Maintena Objec

T s er can be m omer management system. Test Procedure:

, WAP GW, WCDMA network and wireless environment

ally with the ase.

nagement system, and then log in to the customer management

level blacklist. When this es an MM, check whether the setting has

isted subscriber, and check whether the

is added to the system-level blacklist, the MMSC will reject the MM send from or destined for the subscriber.

ried through stomer management system, the query result is consistent

riptive information of a system-level blacklisted ed again, the displayed information

ber can send and receive MMs normally.

d. Ma

r management system.

Add an operator. Then log in usinssword, and cheify the descriptive information of an operator. Then quererator, and check whether th

ete an operator. Thd check whether deletion has taken effect.

Result: n operator’s password is changed, to log in to the system

tor ust enter the new password. tor can be added, deleted and modified successfully, and these

can take effe

nce of System-Level Blacklisted Subscriber tive:

o te t whether the system-level blacklisted subscribanaged and maintained through the cust

The MMSCwork well.

The customer management system is connected normdatab

Start the IE browser, enter the URL address of the customer masystem.

Add the subscriber to the system-subscriber sends or receivtaken effect.

Query system-level blackldatabase 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

When the system-level blacklisted subscribers are quethe cuwith the information in the database

After the descsubscriber is modified and queriis correct.

The de-blacklisted subscri

intenance of UA Profile Objective:

To test whether the user agent profile can be managed and maintained through the custome Test Procedure:


The customer management system is connected normally with the database.



Date 9/27/2006

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


Query terminal type

Modify terminal type Result:

ayed information is correct from the User Agent Profile and

yed information is correct.

displayed information is correct.

arameters can be maintained through

Start the IE browser; enter the URL address of the customer

dify the parameters that can take effect in the real time, such

parameters have taken

s can be maintained through the

are modified, there is no need to restart

f. M

The MMSC, WAP GW, WCDMA network and wireless

he customer cannot send MM from MMSC terminal 1 to

mand in the unix platform mand in the unix platform

rt normally

dule are running, the customer can send

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

Delete terminal type

Expected After a terminal type is added to the User Agent Profile and

queried agent, the displ After a terminal type is deleted

queried agent, the displa After the descriptive information of the terminal type is modified

and queried again, the

e. System Parameter Maintenance Objective: To test whether the system p the customer management system. Test Procedure:


The customer management system is connected normally withthe database.

management system, and the log in to the customer management system.

Moas address hiding.

Send an MM to verify whether modified effect.

Expected Result: The system parameter

customer management system. After the parameters

the system. The modified parameters have taken effect.

MSC startup and shutdown Objective: To test whether MMS system is working completely Test Procedure:

environment work well. T

MMSC terminal 2. Run “MMS status” com Run “MMS start” com Redo step 1

Expected Result: All MMS module are listed, and shown “not running” MMS module will sta All MMS module are listed and shown “running” When all the MMS mo

MM from MMSC terminal 1 to MMSC terminal 2 successfully.



Date 9/27/2006

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


CDMA network and wireless environment work well.

Customer can send MM from terminal MM1 to MM2. module with “MMS Status” command

ms stop (id)” command edo step 3

MMS module in the unix platform

and it will shown “it will shown Succeed”

rk all running.

C. Streaming Services 1. Me

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, W

List all the MMS Kill one of the MMS module with “m R

Expected Result: It shown the list of all Once you run mms stop comm

“Stop the module ….. Then MMS module will start automatically. The MMS module wo

dia Stream on Demand Service a. ams Played on Demand

Video server works normally. ts to

riber accesses the streaming service portal website.

f the service being played on the test terminal.

rvice portal website. The ntents on the streaming service web page

esta treaming server correctly. The media

b. Sup Pause the Streams Being Played on Demand pports to pause the streams being

ts to

.

e 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

Supporting the Flow of Media StreObjective: To verify that the video server supports the media streams played on demand Test Procedure:

WCDMA 3G network work normally.

CP-related devices work normally, and they have published contenthe video server network.

The subsc On the streaming service web page, select the contents to be played. Observe the status o

Expected Result: The subscriber can access the streaming sesubscriber can select desired conormally. After the subscriber selects the contents, the test terminal can

blish connection with the sstreams play normally.

porting toObjective: To verify that the video server suplayed on demand Test Procedure:

WCDMA 3G network work normally. Video server works normally. CP-related devices work normally, and they have published conten

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. Observ



Date 9/27/2006

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


correctly. treams are played normally. After the pause, the subscriber

tents were paused.

c. dia Being Played on Demand To supports to interrupt the streaming service.

V lly. have published contents to

reaming service portal website.

y. nal

a

in, the media streams will be played from the beginning.

ward Query Operations on tream Being Played on Demand

upports the forward query and backward ice.

V . tents to

T riber accesses the streaming service portal website. ge, select the contents to be played.

om time to time.

e. S : o verify that the video server supports to play streams on demand

ime.

rk work normally.

ally, and they have published contents to

treaming service portal website through

O b page, select the contents to be played.

test terminal can establish connection with the streaming serverThe media sreplays the contents again, and the server should resume the playing from where the con

Supporting to Interrupt the Streams Me Objective:

verify that the video server Test Procedure:

WCDMA 3G network work normally. ideo server works norma

CP-related devices work normally, and they the video server network.

The subscriber accesses the st 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 normallAfter the subscriber selects the contents to be played, the test termican establish connection with the streaming server correctly. The medistreams are played normally. Once the subscriber selects to stop, the media streams should stop being played to the subscriber. If press to play aga

d. Supporting to Perform Forward Query and Backthe Media S

Objective: To verify that the video server s

query operations on the streaming servTest Procedure:

WCDMA 3G network work normally. ideo server works normally

CP-related devices work normally, and they have published conthe video server network.

he subsc On the streaming service web pa During the play, the subscriber performs the forward query and

backward query operations frExpected Result: After performing the forward/backward seek operation, the media contents can be played normally.

upporting to Play Streams on Demand Continuously Objective Tcontinuously for a long t

Test Procedure: WCDMA 3G netwo Video server works normally. CP-related devices work norm

the video server network. The subscriber accesses the s

the WAP service platform. n the streaming service we

Keep playing at 5 minutes. Observe the status of the service being played on the test terminal.



Date 9/27/2006

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


reaming service portal website through

2. Live Streaming Service

Expected Result: The subscriber can access the stthe 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 connectionwith the streaming server correctly.

a. Supporting the Live Streaming Service Flow

t the video server supports live streaming service.

A 3G network work normally.

d they have published contents to

O b page, select the live programs to be

reaming service portal website normally.

g

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

the handset)

t the video server supports to pause/stop the live streaming

cedure: rmally.


T streaming service portal website. be

. eb

test terminal can establish connection with the streaming erver correctly. The media streams are played normally, and the

lects the live programs to replay it, and the ld play the contents currently published by the live program

Objective: To verify tha Test Procedure:

WCDM Video server works normally. CP-related devices work normally, an

the video server network. The subscriber accesses the streaming service portal website.

n the streaming service weplayed.

Observe the status of the service being played on the test terminal. Expected Result: The subscriber can access the stThe 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 streaminserver correctly. The media streams are played normally.

Supporting(Depends on

Objective: To verify tha

service being played. Test Pro

WCDMA 3G network work no Video server works normally. CP-related devices work norm

the video server network. he subscriber accesses the

On the streaming service web page, select the live programs to 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 normallyThe subscriber can select desired contents on the streaming service wpage normally. After the subscriber selects the live programs to be played, thescontents are paused/stopped after pressing PAUSE/STOP. After the pause/stop, the subscriber reseserver shousource.



Date 9/27/2006

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


c. Obj s

from Test Procedure:

lly, and they have published contents to

The subscriber accesses the streaming service portal website. e live programs to be

y the encoder.

normally at the test terminal.

. The on the streaming service web

play tablish connection with the streaming

conpau e live programs to replay it, and the

d. bjective:

ay live streams continuously. ure:

d they have published contents to

T ervice portal website.

l. ExpThe ervice portal website normally.

nts on the streaming service web

5

Supporting to Receive Multiple Live Streams from the Encoder ective:

To verify that the video server supports to receive multiple live stream the encoder.

WCDMA 3G network work normally. Video server works normally. CP-related devices work norma

the video server network.

On the streaming service web page, select thplayed b

Repeat the above selections several times. The media streams are played

Expected Result: The subscriber can access the streaming service portal website normally

subscriber can select desired contentspage normally. After the subscriber selects the live programs to be

ed, the test terminal can esserver correctly. The media streams are played normally, and the

tents are paused/stopped after pressing PAUSE/STOP. After the se/stop, the subscriber reselects th

server should play the contents currently published by the live programsource. Supporting to Play Live Streams Continuously O

To verify that the video server supports to pl Test Proced

WCDMA 3G network work normally. Video server works normally. CP-related devices work normally, an

the video server network. he subscriber accesses the streaming s

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 termina

ected Result: subscriber can access the streaming s

The subscriber can select desired contepage 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 minutes.

3. Supporting Encoding a. Supporting File Format of 3gp/mp4

upports play in 3gp/mp4 file format.

V

in the

Objective: To verify that the video server s

Test Procedure: WCDMA 3G network work normally.

ideo 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

.3gp and .mp4 formats.



Date 9/27/2006

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


l.

lly. contents on the media stream service

programs to be layed, the test terminal can establish connection with the streaming

am files in different formats are played

ideo Encoding Format of H.263/MPEG-4

that the video server supports H.263/MPEG-4 video encoding

ts to

ing service portal website.

O

The rmally. Theweb

g serv The media stream files in different formats are played

c. B/AAC-LC audio encoding

rmat.

rk work normally.

ated devices work normally, and they have published contents to

g service portal website. lect to play the desired contents.

ing played on the test terminal.

The y. ntents on the media stream service

played, the test terminal can establish connection with the streaming rent formats are played

d. ultiple Media File Formats (avi, mpg,

at the video server supports conversion of multiple media file

rmats.

rk work normally.

Observe the status of the service being played on the test terminaExpected Result: The subscriber can access the streaming service portal website normaThe subscriber can select desiredweb page normally. After the subscriber selects the livepserver correctly. The media strenormally.

b. Supporting V Objective:

To verifyformat. Test Procedure:

WCDMA 3G network work normally. Video server works normally. CP-related devices work normally, and they have published conten

the video server network. The subscriber accesses the stream On the streaming service web page, select to play the desired contents.

bserve the status of the service being played on the test terminal. Expected Result:

subscriber can access the streaming service portal website no subscriber can select desired contents on the media stream service page normally. After the subscriber selects the live programs to be

played, the test terminal can establish connection with the streaminer correctly.

normally.

Supporting Audio Encoding Format of AMR-NB/AAC-LC Objective: To verify that the video server supports AMR-Nfo

Test Procedure: WCDMA 3G netwo Video server works normally. CP-rel

the video server network. The subscriber accesses the streamin On the streaming service web page, se Observe the status of the service be

Expected Result: subscriber can access the streaming service portal website normall

The subscriber can select desired coweb page normally. After the subscriber selects the live programs to be

server correctly. The media stream files in diffenormally. Supporting Conversion Between Mmp3) – Live Stream Encoding Objective: To verify thfo

Test Procedure: WCDMA 3G netwo Video server works normally.



Date 9/27/2006

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



media files into the media n be

. , select to play the desired contents.

Exp

e. t type in 3GP file format.

WCDMA 3G network work normally. encoding systems work normally; the

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

ing encoder server converts the signals from the live l,

type is 3GP/MP4. page, select to play the live contents.

played on the test terminal.

f. S Obj nly. Test Procedure:

encoding systems work normally; the .

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

riber accesses the streaming service portal website.

dia streams playable at the test terminal, 4

Observe the status of the service being played on the test terminal.

g. MPEG-4, H.263) bjective:

er supports multiple video encoding formats

rk work normally. rmally; the

normally. ntents to

twork. rtal website.

The streaming encoder server converts the signals from the live program source into the media streams playable at the test terminal.

CP-related devices work normthe video server network.

The streaming encoder server convertsstreams playable at the test terminal, and the media file format caAVI, MPG

On the streaming service web page Observe the status of the service being played on the test terminal.

ected Result: The subscriber can play the media streams normally.

Supporting Export Type in File Format of 3GPObjective: To verify that the video server supports exporTest Procedure:

The TV program collection and video server network works normally.

the video server network. The stream

program source into the media streams playable at the test terminaand the export

On the streaming service web Observe the status of the service being

Expected Result: The test terminal can play the media streams normally.

upporting Output of Audio Only/Video Only ective:

To verify that the video server supports output of audio only/video o

WCDMA 3G network work normally. The TV program collection and

video server network works normally

the video server network. The subsc The streaming encoder server converts the signals from the live

program source into the meand the output file format is 3GP/MP

Select “Audio only” or “Video Only”. On the streaming service web page, select to play the live contents.

Expected Result: The test terminal can play the media streams normally. Supporting Multiple Video Encoding Format (O

To verify that the video serv Test Procedure:

WCDMA 3G netwo The TV program collection and encoding systems work no

video server network works CP-related devices work normally, and they have published co

the video server ne The subscriber accesses the streaming service po



Date 9/27/2006

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


oding formats (MPEG-4, H.263).

e test terminal. xpected Result:

Select different video input enc On the streaming service web page, select to play the live contents. Observe the status of the service being played on th

EThe test terminal can play the media streams normally.

4. Content Management Function a. Supporting to Published On-Demand Media Files to Video servers Obj dia files to Video

ally.

ublish contents directly to the video server network in a brief flow. Streaming servers work normally.

tal, enters the Content Management main gory.

ease On-demand Content tab, input the general attribute r

ctor, content description, content length), trol options and content URL.

bution parameters in a normal

S , and submit the

t: a files can be published on the video server and the

media files.

b. Published Live Contents bjective:

f publishing on-demand media files to Video

ure:

ormally. ormally.

ing devices work normally, and they can etwork in a brief flow.

rk normally. as a CP operator, and accesses the Portal main

ntents. Input all items correctly in the content published interface.

esult: ing play of live

al subscriber can watch the live

c. server supports to censor the contents

ective: To verify the function of publishing on-demand meservers Test Procedure:

WCDMA 3G network work norm Video server network works normally. CP-related devices work normally. The collection and encoding devices work normally, and they can

p

The CP operator logs in to Portab, and selects the published on-demand media service cate

In the Relparameter values of the related contents to be published (Foexample, content name, direand fill out the correct distribution con

The CP operator fills out the distriprocedure. et the current system time as the published timedistribution request.

Expected ResulOn-demand medisubscriber can play the published Supporting toO

To verify the function oservers

Test Proced WCDMA 3G network work normally. Video server network works n CP-related devices work n The collection and encod

publish contents directly to the video server n Streaming servers wo The subscriber logs in

tab. Access the interface of publishing co

Submit the published contents. Expected R Live media files can be published on the video server. Durprograms, the mobile test terminprograms. Supporting to Censor Contents Objective: To verify that the video



Date 9/27/2006

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


ally.

lly. The test terminal is registered as certified subscriber of streaming

d devices work normally.

deo server network. n parameters in a normal

submits the distribution request.

Log to the system and censor one of the published contents. d content.

nnot play the files which are censored.

on the Streaming Server erver supports to delete the media file on the

rver network works normally. The test terminal is registered as certified subscriber of streaming

rmally, and can publish contents directly to o server network in a brief flow.

to the video server

e content.

e. Ob es.

lly.

the live contents.

5. CP

Test Procedure: WCDMA 3G network work norm Video server network works norma

service. CP-relate The collection and encoding devices work normally, and they have

published contents to the vi The CP operator fills out the distributio

procedure and then The contents are distributed successfully.

Check the status of the publishe Approve the censored content.

Expected Result: Subscriber ca

d. Supporting to Delete Media File Objective: To verify that the video sstreaming server. Test Procedure:

WCDMA 3G network work normally. Video se

service. CP-related devices work no

the vide The CP operator can publish media contents

network. Log in to the portal and delete one of th

Expected Result: The deleted content cannot be viewed.

Supporting to Delete Live Content Files jective:

To verify that the video server supports deletion of live content filTest Procedure:

WCDMA 3G network works normally. The collection and encoding devices can work norma The CP can publish contents directly to the video server network in a

brief flow. The CP operator has published Log in to the portal and delete one of the live contents.

Expected Result: The deleted live content cannot be viewed. Management Function

Supporting Multiple Level Operato a. rs Function bjective:

el operators ure:

System

ounts.

O To verify the video server supports multiple lev Test Proced

The CP portal can support several level accounts likeadministrator, etc.

Create/delete/modify different level acc



Date 9/27/2006

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


Eac l and each account can log into the Portal.

b. Tes

T rmally.

to the portal after deleting the CP. Cannot login to the

r pausing the CP. Can log in to the portal after resuming the CP.

6. S Function

Expected Result: h operation is successfu

Each level account info can be modified.

Managing (Adding/Deleting/Suspending/Resuming) CP Account Objective: To verify the video server supports management of the CP account.

t Procedure: he video server network works no

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 theCP. Cannot log inportal afte

ecurity Management

a ent (Adding/Deleting/Modify) video server supports User registration functions.

rks normally. C interface. user like user name, login name and password for

ails and register the user. been added.

t log in to the OMC. Added user can log in to the

. Supporting User Managem Objective: To verify the Test Procedure:

work wo Video server net Log in to the OM

ails for a Add detlogin. Add other det

Check that the user has Delete a use. Modify a user.

Expected Result: Deleted user cannoOMC.

7. System Maintenance Application Startup/Stop Objective:

a. Supporting

To verify the video server supports startup/stop aTest Procedure:

pplications.

tion.

Turn on the computer. Display all the services. Observe the status of the application running. Start the application.

top the application. SExpected Result: The application is started or stopped.

b. Supporting Database Startup/Stop Objective:

e video server supports startup/stop Database. Test Procedure:

To verify th

Video server network works normally. Turn on the computer. Display all the services. Observe the status of the Database running. Start the applica



Date 9/27/2006

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


c. upporting Configuration Backup and Restore e video server supports configuration backup and restore.

ssary configuration files.

Expected Result:

d. abase backup and restore.

Expected Result: irectory. The Database is

Stop the application. Expected Result: The database is started or stopped. S

Objective: To verify th

Test Procedure: Video server network works normally. Log in to the system. Backup/restore all the nece

The backup files will exist in backup directory. Supporting Database Backup and Restore Objective: To verify the video server supports DatTest Procedure:

Video server network works normally. Log in to the system. Backup/restore all the Database.

The Database backup files will exist in backup drestored.

8. Supporting Billing Function a.

lly. s certified subscriber of streaming

-related devices work normally, and they have published contents to the video server network.

tents website. ontent to be played.

content to be played. , the subscriber stops play.

enerated at the streaming service platform.

content completely played and the

view s the following information as a minimum d end

time played on demand, filename of the played file, flag

b. Supporting Generating CDR for Aborted Play the billing function in case of aborted play.

ormally.

Supporting Generating CDR Objective: To verify that the CDR file can be generated. Test Procedure:

WCDMA 3G network works normally. Video server network works norma The test terminal is registered a

service. CP

The subscriber accesses the media stream con Select a c Play the selected media stream content completely. Select the other media stream After playing the content for five seconds View the CDR information g

Expected Result: The CDR information for both thecontent partially played is correct. For the content the subscriber stops

ing, the CDR includerequest: duration of played content, data traffic played, start time an

of the contentwhich indicates completion type.

Objective: Supporting

Test Procedure: WCDMA 3G network works n Video server network works normally.



Date 9/27/2006

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


ubscriber of WAP service

S ent to be played.

ost, pull out the battery, out of service, answers a phone

formation generated at the streaming service platform.

treaming. The

incl ng information as a minimum request: duration of , no flag indicates normal completion of

e

6.1.5 HSDPA

The test terminal is registered as certified sand 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. elect a cont

During the play, the subscriber ends the streaming, e.g. the signals of the MS are lcall, handsets failed.

View the CDR inExpected Result: The CDR information generated after the user ends the sCDR generated when the streaming connection is abnormally cut off,

udes the followiplayed content, data traffic playedplay, start time and end time of the content played on demand, file namof the played file.

Testing Fo

ping

• • • • • • • • • •

A. RAB

1. HS

r HSDPA testing, the tests are divided into 13 main parts: • RAB map• Power Management • Code management

Mobility Load management Iub flow control State switch RTT Hardware capacity Throughput capacity System reliability Iub standard interface Configuration

mapping DPA Cell R99 UE Call Establishment – DCH-PS

O T Test Procedure:

eration.

rver in the Internet and uploads/downloads files rver.

pected Result: ess the Internet and can upload/download files normally.

bjective: o verify that HSDPA Cell UE R99 PS Call establishment

WCDMA system is in normal op The HSDPA cell is set up. UE support R99 and is in idle mode. UE starts PS service. UE logs in to an FTP se

through the Se UE logs out to end the PS service after uploading or downloading.

Ex UE can acc 2. HSDPA Cell R99 UE Call Establishment – DCH-CS Objective:

To verify that HSDPA Cell UE R99 CS Call establishment T est 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.



Date 9/27/2006

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


3. HS hment – Emergency

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.

DPA Cell HSDPA UE Call Establis Objective:

o verify that HSDPA Cell UE Emergency Call establishment est Procedure:

T T

WCDMA system is in normal operation.

The MSC Server is configured to route emergency call to police or to a ser.

le phone, and power on. ll, e.g. call 112.

N. age.

ass hat it is an emergency call. 4. HS

The HSDPA cell is set up.

PSTN u The UE should support to establish an SOS call. Insert USIM card into mobi UE initiates an emergency ca The emergency call is connected to PST Check the Iu interface mess

Expected Result: The UE location is successful. The emergency call can be established successfully. UE and PSTN can talk with each other. The RAB

ignment message indicates t

DPA Cell HSDPA UE Call Establishment – SMS O

T Test

eration.

UE1 composes a text message and send it to UE2.

e short message.

the message successfully. UE2 receives the message

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

bjective: o verify that HSDPA Cell UE SMS service.

Procedure: WCDMA system is in normal op 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.

UE2 receives thExpected Result:

UE1 sends correctly.

Objective: T all Establishment. T

U U U the Internet and uploads/downloads files

U e HSDPA PS service after uploading or

6. HS +HSDPA-PS

o verify that HSDPA Cell UE HSDPA PS Cest Procedure:

WCDMA system is in normal operation. The HSDPA cell is set up.

E support HSDPA and is in idle mode. E starts HSDPA PS service. E logs in to an FTP server inthrough the Server. E logs out to the end thdownloading.

Expected Result: UE can access the Internet and upload/download files normally.

DPA To MultiService-Multiservice: AMR O

Test Procedure:

WCDMA system is in normal operation. The HSDPA cell is set up.

bjective: To verify that the system support CS+HSDPA PS Service.



Date 9/27/2006

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


ort R99 and is in idle mode.

Catalog 12 UE is used in this test case, its average reported

the service on the

U E T ontext to release the link when data

Exp up. The high speed can be

d the voice is

7. HS -PS

UE1 support HSDPA and is in idle mode. UE2 supp UE1 is subscribed HSDPA in the HLR. For example, set the PS UL/DL

BE traffic bit rate to 64K/2048K. 1 HSDPA

CQI > 16. UE1 initiates a PS data service, and the RNC sets up

HS-DSCH. UE1 transfers data through FTP. UE2 calls UE1.

E1 rings and hooks off. UE1 and UE2 start talking. ither UE1 or UE2 hooks up to end the conversation. he UE deactivates the PDP ctransfer ends. ected Result:

The PS service over the HS-DSCH is setobserved by DU meter or other tools. The call is normal anlegible.

DPA To MultiService-Multiservice: VP+HSDPA O

T P+HSDPA PS Service.

is set up. UE1 support HSDPA and is in idle mode. UE2 support R99 and is in idle mode.

is subscribed HSDPA in the HLR. For example, set the PS UL/DL

orts VP + HSDPA PS Service.

the RNC sets up the service on the

U E The UE deactivates the PDP context to release the link when data

Exp The set up. The high speed can be

other tools. The conversation keeps legible and

B. Pow

1. HSDPA ith fixed HS-SCCH power, OCNS 25%

bjective: o verify that the system support V

Test Procedure: WCDMA system is in normal operation. The HSDPA cell

UE1BE traffic bit rate to 64K/2048K.

UE1 supp 1 HSDPA Catalog 12 UE is used in this test case, its average reported

CQI > 16. UE1 initiates a PS data service, and

HS-DSCH. UE1 transfers data through FTP. UE2 starts VP and calls UE1

E1 rings and hooks off to start the conversation. ither UE1 or UE2 hooks up to end the conversation.

transfer ends. ected Result:

PS service over the HS-DSCH is observed by DU meter orthe picture keeps clear.

er Management flexible power allocation w

load Obje

Trema

T W is in normal operation.

.

reported CQI is around 16.

ctive: o verify that HSDPA flexible power allocation algorithm could use the

ining power left by R99. est Procedure:

CDMA system 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



Date 9/27/2006

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


igure HS-SCCH power to fixed power allocation. Configure OCNS load to 45%.

C setups the service HS-DSCH.

ld not make HSDPA UEs use out of the remain power left

cy neighbor cells interference.

2. HS

Configure HSDPA power algorithm to dynamic power allocation. Conf

3 HSDPA UEs initiate PS data service, and the RNon the

Expected Result: HSDPA uses the remain power left by R99, which is around 45%. If OCNS load couby R99, try to use intra-frequen DPA flexible power allocation with fixed HS-SCCH power, OCNS 50%

load Obje

To verify that HSDPA flexible power allocation algorithm could use the r

Test W

p.

CCH total power is about 20% and DCH power margin is set to 10%.

C er to fixed power allocation.

3 HSDPA UEs initiate PS data service, and the RNC setups the service

Expected Result: ft by R99, which is around 20%. If

r left

C. Cod

1. HSDPA RNC controlled code allocation, R99 takes more

ctive:

emaining power left by R99. Procedure: CDMA system is in normal operation.

The HSDPA cell is set u Make sure HSDPA power allocation is dynamic.

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. onfigure HS-SCCH pow

Configure OCNS load to 70%.

on the HS-DSCH.

HSDPA uses the remain power leOCNS load could not make HSDPA UEs use out of the remain poweby R99, try to use intra-frequency neighbor cells interference.

e Management

Objective: t HSDPA dynamic code allocation algorithm is correct, when

y

: operation.

C ntrolled dynamic code

codes to 3, and set F16.

QI is > 16.

C amic allocation.

on the HS-DSCH.

Exp s

taken from HSDPA.

To verify thaR99 user initiates the R99 service, the code resource will be occupied bR99. Test Procedure

WCDMA system is in normal The HSDPA cell is set up. Make sure HSDPA power allocation is dynamic.

onfigure code allocation algorithm to “RNC coallocation” and its parameters “maximum number code for HSDPA” to 14, and the minimum number to 6, set HS-SCCHfree SF threshold to S

3 HSDPA Catalog 12 UEs are used in this test case, the average reported C

2 R99 UEs are used in this test case. onfigure HSDPA code algorithm to dyn

3 HSDPA UEs initiate PS data service, and start data transmission, the RNC setups the service

2 R99 UEs setup VP calls in the cell. ected Result:

HSDPA consumes about 13 codes. After the setup, one code SF16 i



Date 9/27/2006

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


2. HS on, HSDPA takes moreDPA RNC controlled code allocati Objective:

o verify that HSDPA dynamic code allocation algorithm is correct, when 99 user terminates the R99 service, the code resource will be allocat

TR ed for HSDPA.

system is in normal operation.

cation algorithm to “RNC controlled dynamic code “maximum number code for HSDPA” to

HS-SCCH codes to 3, and set

3 case, the average

2 orithm to dynamic allocation.

s the service on the HS-DSCH.

R

HS 3 codes. After the setup, one code SF16 is e

D. Mobility 1. HS C, intra Node B, Intra frequency

Test Procedure: WCDMA The HSDPA cell is set up. Make sure HSDPA power allocation is dynamic. Configure code allo

allocation” and its parameters 14, and the minimum number to 6, set free SF threshold to SF16. HSDPA Catalog 12 UEs are used in this test reported CQI is > 16. R99 UEs are used in this test case.

Configure HSDPA code alg 3 HSDPA UEs initiate PS data service, and start data transmission, the

RNC setup 2 R99 UEs setup VP calls in the cell.

elease the VP calls. Expected Result:

DPA consumes about 1taken from HSDPA. After release the call, RNC allocates one more codSF16 for HSDPA.

DPA to HSDPA Mobility, Intra RN

Objective: o verify the HSDPA service to ensure continuity when intra-frequencSCH cell change in the same Node B does not necessarily lead to

eestablishment of HS-DSCH carriers.

T y HS-Dr

Test Procedure:

subscriber A is subscribed in the HLR. For example, set the

up in the same Node B.

1 the average reported

the HS-DSCH.

report from UE.

Expected Result: NC receives 1A event report then

ll. Cell Changing is completed with Physical channel

WCDMA system is in normal operation. WCDMA

PS UL/DL BE traffic bit rate to 64K/2048K. Make sure that the DL BEtraffic threshold on HSDPA is no larger than the subscribed DL bit rate.

Two intra-frequency HSDPA cells are setConfigure intra-frequency neighboring CELL 1 and CELL 2 with both of them working as HSDPA cell.

Enable soft handover. HSDPA Catalog 12 UE is used in this test case,CQI > 16.

The UE initiates a PS data service on CELL 1, and the RNC sets up the service on

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

The UE deactivates the PDP context to release the link when data transfer ends.

The PS service set up normal. Rinitiates soft handover procedure. The TRUE scramble indicates the currently serving ce



Date 9/27/2006

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


d after service

2. HS

reconfiguration. Network resources occupied are releaseends. DPA to HSDPA Mobility, Intra RNC, inter frequency

en inter-frequency HS-DSCH cell change

i d to reestablishment of HS-D

Test

W or example, set the t rate to 64K/2048K. Make sure that the DL BE

e RNC. Configure inter-frequency neighboring

E

16. sets up the

T t moves from CELL 1 to CELL 2 until RNC receive 2D

ort to

xpected Result: The PS service set up normal. RNC receives 2D event report then

s mode procedure. RNC receives inter-frequency ent event report from UE, and decides to make inter-frequency Network resources occupied are released after service ends.

ra RNC, intra frequency

Objective: To verify the HSDPA service wh

n different NodeBs does not necessarily leaSCH carriers.

Procedure: WCDMA system is in normal operation.

CDMA subscriber A is subscribed in the HLR. FPS UL/DL BE traffic bitraffic 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 samCELL 1 and CELL 2 with both of them working as HSDPA cell. nable hard handover.

1 HSDPA Catalog 12 UE is used in this test case, the average reported CQI >

The UE initiates a PS data service on CELL 1, and the RNCservice on the HS-DSCH.

he UE under tesevent report from UE.

The UE under test reports inter-frequency measurement event repRNC.


E

initiates compresmeasuremhandover.

3. HSDPA to non HSDPA Mobility, Int O

TDCH from HSDPA supportive cell to non HSDPA s

Test

W r example, set the

nd CELL 2 with CELL 1 cell.

1 UE is used in this test case, the average reported

T ata service on CELL 1, and the RNC sets up the

CELL 1 to CELL 2 until RNC receive 1A


bjective: o verify that the RB carried by the HSDPA switches from HSDSCH to

after the handoverupportive cell.

Procedure: WCDMA system is in normal operation.

CDMA subscriber A is subscribed in the HLR. FoPS UL/DL BE traffic bit rate to 64K/2048K.

Configure intra-frequency neighboring CELL 1 aworking as a R5 cell and CELL2 as a R99

Enable soft handover. HSDPA Catalog 12CQI > 16.

he UE initiates a PS dservice on the HS-DSCH.

The UE under test moves from event report from UE.

The UE under test moves from CELL1 to CELL2 again until RNC receive 1B event report from UE.



Date 9/27/2006

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


sult: l. RNC receives 1A event report then

t handover procedure. Channel switching from HS-DSCH to

ra RNC, inter frequency

Expected Re The PS service set up norma

initiates sofDCH. Network resources occupied are released after service ends.

4. HSDPA to non HSDPA Mobility, Int O

TDCH dover from HSDPA supportive cell to non HSDPA s

Test

. For example, set the

1 LL2 as a R99 cell.

1 e, the average reported

T

D

The state of UE under test switches from HSDPA to DCH. uency measurement event report to

es 2D event report then

mea nt report from UE, and decides to make inter-frequency s.

5. Non HS HSDPA Mobility, Intra RNC, intra frequency

bjective: o verify that the RB carried by the HSDPA switches from HSDSCH to

after the hanupportive cell.

Procedure: WCDMA system is in normal operation. WCDMA subscriber A is subscribed in the HLR

PS UL/DL BE traffic bit rate to 64K/2048K. Configure inter-frequency neighboring CELL 1 and CELL 2 with CELL

working as a R5 cell and CE Enable hard handover.

HSDPA Catalog 12 UE is used in this test casCQI > 16.

he 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 2event report from UE.

The UE under test reports inter-freqRNC.


Expected Result: The PS service set up normal. RNC receivinitiates compress mode procedure. RNC receives inter-frequency

surement evehandover. Network resources occupied are released after service end

DPA to non O

T to the HSDSCH after t

T W on.

ell.

1 rted

ice on CELL 1, and the RNC sets up the

A

1A event report. The UE deactivates the PDP context to release the link when data

r ends.

vice set up normal. Network resources occupied are released after service ends.

bjective: o verify that the service is switched from the DCH

he handover from non HSDPA supportive cell to HSDPA supportive cell.est Procedure:

CDMA system is in normal operati 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 c Enable soft handover.

HSDPA Catalog 12 UE is used in this test case, the average repoCQI > 16.

The UE initiates a PS data servservice on the DCH.

The UE under test moves from CELL 1 to CELL 2 until RNC receive 1event report from UE.

The UE stays in the same place where it received

transfeExpected Result:

The PS ser



Date 9/27/2006

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


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

PA switches from DCH to HS-on HSDPA supportive cell to HSDPA

s T

W is in normal operation.

C 1 g as a R99 cell and CELL2 as a R5 cell.

in this test case, the average reported

The UE initiates a PS data service on CELL 1, and the RNC sets up the

T t moves from CELL 1 to CELL 2 until RNC receive 2D

The UE deactivates the PDP context to release the link when data

to make inter-frequency handover. Network resources occupied are released after service ends.

Objective: To verify that the RB carried by the HSDDSCH after the handover from nupportive cell. est Procedure:

CDMA system WCDMA subscriber A is subscribed in the HLR. For example, set the

PS UL/DL BE traffic bit rate to 64K/2048K. onfigure inter-frequency neighboring CELL 1 and CELL 2 with CELLworkin

Enable hard handover. 1 HSDPA Catalog 12 UE is used

CQI > 16.

service on the DCH. he UE under tesevent 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.

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

E. Load Management 1. HSDPA CAC O

T Test Procedure:

T s and the cell HSDPA

BE traffic bit rate to 64K/2048K.

power is dynamically allocated.

H is enabled.

4 t case, the average reported

The first UE, the second UE, and the third UE initiates HSDPA PS data

ervices on the HS-DSCH. Because of the HSDPA admission control algorithm, RNC doesn’t setup the service on the HS-

SCH, but admits it setup on DCH RB.

bjective: o verify the HSDPA Admission Control function.

WCDMA system is in normal operation. he cell 1 under test supports HSDPA functionstate is available.

WCDMA subscribers are subscribed in the HLR. For example, set the PS UL/DL

Five codes for HS-PDSCH and one code for HS-SCCH are configured at least. The DL

The capability of all UEs under test is category 12 or above. SDPA Admission Control function

HSDPA Admission user number is set to 3. HSDPA Catalog 12 UE is used in this tesCQI is around 16.

service one by one. The fourth UE want to initiate HSDPA PS data service too.

Expected Result: RNC setup these s

D



Date 9/27/2006

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


1. IUBF. Iub flow control

Efficiency for HSDPA, 1 E1 O

THSDPA users with extreme limited IUB configuration.

T

T HSDPA functions and the cell HSDPA state

1namically allocated.

rted CQI > 16. t 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.

HS-DSCH are set-up. No UE automatically

the PDP context or disrupts its connection during the test.

, 1 E1

bjective: o verify Iub bandwidth utilization efficiency and user throughput vs.

est Procedure: WCDMA system is in normal operation.

he cell under test supportsis available.

4 codes for HS-PDSCH and 3 codes for HS-SCCH are configured The HSDPA power is dy

HSDPA and R99 services share 1 E1 Iub transmission. For each user, its average repo 3 HSDPA Catalog 12 UEs are used in this tes

Expected Result: The PS services over the

deactivates

2. IUB Efficiency for HSDPA and R99 O

To ve uration; a

Test

DPA functions and the cell HSDPA state

codes for HS-SCCH. The HSDPA power is dynamically allocated and code is statistically

es share 1 E1 Iub transmission. user, its average reported CQI > 16.

S data service each, and the RNC DCH.

data service each, and S-DSCH.

files with stable data source (larger than 20 MB) from

R

The HS-DSCH are set-up. No UE automatically srupts its connection during the test.

b 99 services is always assured.

bjective: rify Iub bandwidth utilization efficiency with limited IUB config

nd bandwidth allocation between HSDPA and R99 users. Procedure:

WCDMA system is in normal operation. The cell under test supports HS

is available. Configure 8 codes for HS-PDSCH and 3

allocated. HSDPA and R99 servic For each 3 HSDPA Catalog 12 UEs and 3 R99 UEs are used in this test case. 3 R99 UEs initiates a 64K/384K P

sets up the services on the At the same time, 3 HSDPA UEs initiate a PS

the RNC sets up the services on H Download large

the server through FTP by all the 6 users. ecord 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: services over the

deactivates the PDP context or diThe 3 R99 services are not impacted by the 3 HSDPA services. The Iubandwidth of the R

G. State switch

1. HSDPA to FACH and to Idle Objective:



Date 9/27/2006

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


ched from HSDSCH to FACH, when there i CH, and when PS Inactive d

Test Procedure:

T DPA functions and the cell HSDPA state

W the HLR. For example, set the L BE

SDPA is no larger than the subscribed DL bit

Enable the UE state transition algorithm switch.

1 ge reported

T PS data service, and the RNC sets up the service on

r

Keep on UE non-data transfer until the channel is switched to the IDLE

esult:

DSCH to FACH. During non-data transfer, the Iu connection is DP context should be reserved by SGSN,

. 2. FACH t

To verify that the channel is swits no traffic for the service set up over HSDSetective timer expired, switch to IDLE.

WCDMA system is in normal operation. he cell under test supports HSis available. CDMA subscriber A is subscribed inPS UL/DL BE traffic bit rate to 64K/2048K. Make sure that the Dtraffic threshold on Hrate.

Set PS inactive detective timer. HSDPA Catalog 12 UE is used in this test case, the averaCQI > 16.

he UE initiates athe HS-DSCH.

The UE doesn’t transfer any data through FTP. The channel is switched to the FACH state when there is no traffic ove

HSDSCH due to halted service.

state. Expected R

The single PS service over the HS-DSCH is set-up. Channel switching from HS-released successfully, and the Pthen Channel switching from FACH to IDLE

o HSDPA O

To ve d from FACH to HSDSCH. T

W state

t the

Enable the UE state transition algorithm switch.

on

ta through FTP. The channel is

The UE deactivates the PDP context to release the link when data

esult:

H to HS-DSCH. Network resources occupied are released after

H. RTT

1. Ping P

bjective: rify that burst traffic is switche

est Procedure: CDMA system is in normal operation.

The cell under test supports HSDPA functions and the cell HSDPAis available.

WCDMA subscriber A is subscribed in the HLR. For example, sePS UL/DL BE traffic bit rate to 64K/2048K.

1 HSDPA Catalog 12 UE is used in this test case, the average reportedCQI > 16.

The UE initiates a PS data service, and the RNC sets up the servicethe HS-DSCH.

The UE doesn’t transfer any daswitched to the FACH state first.

The UE transfers data through FTP. The channel is switched to the HSDSCH state because of burst traffic.

transfer ends. Expected R

The single PS service over the HS-DSCH is set-up. Channel switching from FACthe service ends.

acket Delay

O Meas E for ping sizes 32, 256, and 1024

bytes. The PS UL 64 kbps/PS DL HSDPA is used for this test.

bjective: ure the ping packet delay at U



Date 9/27/2006

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


T W

1 UE is used in this test case, the average reported

U mand Prompt, launch successive 32 bytes ping

M mber of TT,

TT. acket sizes of 256, 1024 bytes.

est Procedure: CDMA system is in normal operation.

All cells support HSDPA over the drive path. HSDPA Catalog 12 CQI > 16.

Activate a PDP context with a HSDPA mobile (UL64K) sing Window’s Compackets during 1 minute. easure the following metrics: Number of packets sent, NuPackets received, Percentage of Loss, Minimum RTT, Maximum Rand Average R

Repeat steps 2 and 3 for ping pExpected Result: Ping is successful and there is no packet loss.

I. Hardware Capacity 1. 3*1 with 15 HS-PDSCH/cell O

To ve Test

C

After the cells have been created, activate them, and activate the

M ell code tree of these three cells.

mon early.

J. HSDPA rrier 1. 3*1

bjective: rify the capability of HSDPA 3X1 with 15 HS-PDSCH/cell.

Procedure: onfigure HSDPA 3X1 with 15 HS-PDSCH/cell, these three cells are intra-frequency in the same Node B but on different sectors.

HSDPA function. onitor the c

Expected Result: The cells and their HSDPA function are activated successfully. The

itor shows 15 HS-PDSCH/cell cl

and R99 mixed cell sharing one ca with 15 HS-PDSCH/cell

Obje T

mixe ne carrier. T

T

Sfinish power and code allocation of HS-

l,

Test UE initiates PS I/B service, and this traffic is carried on HS-DSCH

lly. All traffics are setup and mally.

K. ThrCH, Category 12 UE, CDM4, CQI>16

ctive: o verify if the system could support the configuration of HSDPA and R99

d cell only occupy oest Procedure:

est system could support HSDPA function. Test UEs support HSDPA function.

etup R99 cell. Configure HSDPA parameters,

PDSCH and HS-SCCH by physical shared channel reconfiguration in the cell. Configure 5 HS-PDSCH channels and 1 HS-SCCH channedownlink power is allocated dynamically.

channel. Expected Result: Setup R99+R5 one carrier cell successfurelease nor

oughput capacity

1. Cell throughput in case of 5 HS-PDS O

TCQI>

bjective: o get Cell Peak Traffic over 5 HS-PDSCHs, Category 12 UE, CDM4

16.



Date 9/27/2006

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


Test W al operation.

s and the cell HSDPA state

W

5 gured. The

T ata services, and the RNC sets up the services

Test UE deactivates the PDP context to release the link when data

esult: or other tools can observe the speed of six UEs respectively.

ulate k Traffic over 5 HS-PDSCHs.

DSCH, Category 12 UE, CDM4, CQI>16

Procedure: CDMA system is in norm

The cell under test supports HSDPA functionis available. CDMA subscribers are subscribed in the HLR. Set the PS UL/DL BE traffic bit rate to 64K/2048K. codes for HS-PDSCH and 4 codes for HS-SCCH are confiDL power is dynamically allocated.

6 HSDPA Catalog 12 UEs are used in this test case, the average reported CQI > 16.

he six UEs initiate PS don 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.

transfer ends. Expected RDUMETEREach of the six UEs can transfer data through FTP normally. Calcand record the Cell Pea

2. Cell throughput in case of 10 HS-P O

TCQI>

Test W al operation.

s and the cell HSDPA state

W BE

10 HS-PDSCH and 4 codes for HS-SCCH are configured.

Iu ration should not be less than 12 Mbps. rvices, and the RNC sets up the services

the server through FTP by using the six UEs under test.

ta ds.

esult: tively.

transfer data through FTP normally. Calculate over 10 HS-PDSCHs.

3. Cel

bjective: o get Cell Peak Traffic over 10 HS-PDSCHs, Category 12 UE, CDM4

16. Procedure: CDMA system is in norm

The cell under test supports HSDPA functionis available. CDMA subscribers are subscribed in the HLR. Set the PS UL/DLtraffic bit rate to 64K/2048K. codes forThe DL power is dynamically allocated.

6 HSDPA Catalog 12 UEs are used in this test case, the average reported CQI > 16. b transmission configu

The six UEs initiate PS data seon the HS-DSCH.

Download large files with stable data source (larger than 20 MB) from

Test UE deactivates the PDP context to release the link when datransfer en

Expected RDUMETER or other tools can observe the speed of six UEs respecEach of the six UEs canand record the Cell Peak Traffic l throughput in case of 14 HS-PDSCH, Category 12 UE, CDM4, CQI>16

Obje To g

CQI> T

T tate

WCDMA subscribers are subscribed in the HLR. Set the PS UL/DL BE

ctive: et Cell Peak Traffic over 14 HS-PDSCHs, Category 12 UE, CDM4 16.

est Procedure: WCDMA system is in normal operation.

he cell under test supports HSDPA functions and the cell HSDPA sis available.

traffic bit rate to 64K/2048K.



Date 9/27/2006

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


6 s are used in this test case, the average

es on the HS-DSCH.

ource (larger than 20 MB) from ver through FTP by using the six UEs under test.

ta

an observe the speed of six UEs respectively.

and

L. Syst 1. HS

14 codes for HS-PDSCH and 4 codes for HS-SCCH are configured. The DL power is dynamically allocated.

HSDPA Catalog 12 UEreported 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 servic

Download large files with stable data sthe ser

Test UE deactivates the PDP context to release the link when datransfer ends.

Expected Result: DUMETER or other tools cEach of the six UEs can transfer data through FTP normally. Calculate

record the Cell Peak Traffic over 14 HS-PDSCHs.

em reliability DPA system reliability

Obje To ve Test

he HSDPA resource status indication and

code allocation of HS-d

ed

d in this test case, the average reported

UE initiates PS DL 2048K HSDPA background traffic, the traffic is setup

or HS-PDSCH and 4 codes for HS-SCCH are configured. The

UEs are used in this test case, the average

ata services, and the RNC sets up the services

D

T P context to release the link when data

Eac ata through FTP normally. Calculate

M. Iub s

1. Co power of all

ctive: rify the system reliability of holding traffic for long time.

Procedure: RNC initiates physical shared channel reconfiguration by t

capability indicated in the messagesAudit response, and finishes the power andPDSCH and HS-SCCH. Configure 5 HS-PDSCH channel codes an1 HS-SCCH channel codes, and downlink power is allocatdynamically.

1 HSDPA Catalog 12 UE is useCQI > 21.

Iub transmission configuration: no less than 6 Mbps.

on the HS-DSCH channel. 5 codes f

DL power is dynamically allocated. 6 HSDPA Catalog 12

reported CQI > 16. The six UEs initiate PS d

on the HS-DSCH. ownload large files with stable data source (larger than 20 MB) from the server through FTP by using the six UEs under test.

est UE deactivates the PDtransfer ends.

Expected Result: DUMETER or other tools can observe the speed of six UEs respectively.

h of the six UEs can transfer dand record the Cell Peak Traffic over 5 HS-PDSCHs.

tandard interface mmon measurement of HSDPA cell – transmitted carrier

co s not used for HS-SCCH transmissionde Objective:

follows the of protocol.

nfiguration by the HSDPA e status indication and

To verify HSDPA cell common measurement messagerequirement

Test Procedure: Setup cell successfully. RNC initiates physical shared channel reco

capability indicated in the messages resourc



Date 9/27/2006

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


es the power and code allocation of HS-

. asurement, Common

itted carrier power of all codes not used

Type is On Demand or Periodic or Event. Monitor Iub interface with protocol analyzer.

rocedure is successful, reports common measurement follow the Report

rement message follows the requirement

.21 by protocol analyzer.

2. Com ower

Audit response, and finishPDSCH and HS-SCCH.

Monitor Iub interface with protocol analyzer RNC initiates HSDPA cell common me

Measurement Type is transmfor HS-PDSCH or HS-SCCH transmission, Measurement Report Characteristics

Node B common measurement initialization pNode BCharacteristics Type.

Expected Result: Make sure the common measuof protocol 3GPP 25.433 V5.13.0 chapter 9.1 mon measurement of HSDPA cell – HS-DSCH required p

measurement O

Trequi tocol.

T

tatus indication and es the power and code allocation of HS-

col analyzer.

Measurement Report Characteristics Type is On Demand or Periodic

b interface with protocol analyzer.

easurement follow the Report

urement message follows the requirement y protocol analyzer.

3. Com ll – HS-DSCH provided bit rate

bjective: o verify HSDPA cell common measurement message follows the

rement of pro

est Procedure: Setup cell successfully. RNC initiates physical shared channel reconfiguration by the HSDPA

capability indicated in the messages resource sAudit response, and finishPDSCH and HS-SCCH.

Monitor Iub interface with proto RNC initiates HSDPA cell common measurement, Common

Measurement Type is HS-DSCH required power measurement,

or Event. Monitor Iu Node B common measurement initialization procedure is successful,

Node B reports common mCharacteristics Type.

Expected Result: Make sure the common measof protocol 3GPP 25.433 V5.13.0 chapter 9.1.21 b mon measurement of HSDPA ce

measurement Objective:

To verify HSDPA cell common measurement message follows the

ure:

d channel reconfiguration by the HSDPA essages resource status indication and

de allocation of HS-

mmon measurement, Common

vent.

requirement of protocol. Test Proced

Setup cell successfully. RNC initiates physical share

capability indicated in the mAudit response, and finishes the power and coPDSCH and HS-SCCH.

Monitor Iub interface with protocol analyzer. RNC initiates HSDPA cell co

Measurement Type is HS-DSCH provided bit rate measurement, Measurement Report Characteristics Type is On Demand or Periodic or E

Monitor Iub interface with protocol analyzer.



Date 9/27/2006

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


ent initialization procedure is successful, surement follow the Report

measurement message follows the requirement f protocol 3GPP 25.433 V5.13.0 chapter 9.1.21 by protocol analyzer.

Node B common measuremNode B reports common meaCharacteristics Type.

Expected Result: Make sure the commono

4. HSDPA cell configuration over Iub interface Objective:

Setup cell successfully.

PA d

f HS-PDSCH and HS-SCCH.

Monitor Iub interface with protocol analyzer. t by the

ssages resource status indication and Audit response, and finishes the power and code

SCCH. Node B responds with message physical shared channel

or Iub interface with protocol analyzer.

de B reports common measurement follow the Report

f protocol

5. H figured on RL over Iub interface

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

Test Procedure:

RNC initiates physical shared channel reconfiguration by the HSDcapability indicated in the messages resource status indication anAudit response, and finishes the power and code allocation o

RNC initiates physical shared channel reconfiguration requesHSDPA capability indicated in the me

allocation of HS-PDSCH and HS-

reconfiguration response. Monit Node B common measurement initialization procedure is successful,

NoCharacteristics Type.

Expected Result: Make sure the interface message follows the requirement o3GPP 25.433 V5.13.0 chapter 8.2.18 by protocol analyzer.

SDPA service recon

e reconfigured on RL over Iub interface follows the

l shared channel reconfiguration by the HSDPA ication and tion of HS-

Iub interface with protocol analyzer. S data traffic in the HSDPA cell.

e RL reconfiguration ready.

of protocol

N. 1. A

Objective: To verify HSDPA servic

requirement of protocol. Test Procedure:

Setup cell successfully. RNC initiates physica

capability indicated in the messages resource status indaAudit response, and finishes the power and code alloc

d HS-SCCH. PDSCH an Monitor UE initiates P RNC setups a HS-DSCH channel through sending RL reconfiguration

prepare message to Node B. Node B responds with messag

Expected Result: Make sure the interface message follows the requirement 3GPP 25.433 V5.13.0 chapter 8.3 by protocol analyzer.

Configuration ctivate/Deactivate HSDPA functionality in a Node B

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.

Objective:



Date 9/27/2006

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


Deactivate the HSDPA functionality of a cell. the HSDPA functionality of a cell.

s HSDPA service will be stopped and will be recovered. The service is normal.

2. C t

Log in to the O&M system.

Activate Initiate a HSDPA service.

Expected Result: The cell’

rea e a new node B with the HSDPA functionality

Ob

wit Te

ion.

gure the Iub interface data.

Activate the cell’s HSDPA functionality. ode B, and activate the configuration.

Result: Node B startup normally. The state of Iub ports and AAL2 adjacent is

ble. The state of the cell is available. The service is normal.

3. Change of HSDPA Configuration Parameters

jective: The purpose of this test is to check the procedure to create a new NodeB

h the HSDPA function. st Procedure: RNC and Node B are in normal operat 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. Confi Configure a cell data.

Upload configuration file to N Query the state of Iub ports and AAL2 adjacent. Query the state of the cell. Initiate a HSDPA service.

Expected

availa

Objective: rpose of this test is to change of HSDPA Configuration Parameters. ure:

de 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

The pu

Test Proced RNC and No

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.



Date 9/27/2006

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


Expected Result:

The service is normal.

6.2 Pilot/KPI Tests and Stress Tests

t/KPI tests will measure the quality and performance of the network and services te subscriber experience and possible problem while using The measu ommended by different st mance will be measured subjectively and objectively. For accuracy, the performance will be measured

ctively.

rform uged according to t de ndrecomme Performance Indicators (KPIs). 6.2.1 Gen lines:

Initiate a HSDPA service.

The operation doesn’t impact on service in UTRAN. The operation will interrupt the HSDPA service.

The pilo. The stress tests will valida

the mentioned 3G services.

rements will be compared to the acceptable values recandard bodies. For user experience, the perfor

obje The pe ance will be ga

nded 3G Keyhroughput, lay, clarity, a

eral Test Procedures and Guide

the vendor for gathering statistics must be up and

Documents on the procedure and the results table will be provided to the testers.

ll assist the engineer of the vendor at each node B sites. h a USIM each.

red before the test.

• MMS Settings • SThe st with the tion ubm

on how to configure the s.ceed to the test points in the specified location be the start equence.

ter is in a 3G coverage area. , the followin rvices will be tested:

g, Internet Browsing, Multimedia Streaming, Downloading, and MMS)

ng the laptop with an HSDPA card, the PS services will also be tested. wnlink speed

d in downloading file. n the table, according to site and test scenarios.

f the results will be verified by both DMPI and the vendor. The

The monitoring tool ofrunning.

A DMPI engineer wiEach tester is given 1 test phone witHandsets/test phones need to be configuThere are four basic things to be configured on the test phone • Enable 3G mode on the phone. • GPRS Settings

treaming Settings vendor needs to assi configura

st phone and must s it the

procedure Tester to p

te ro

of each test sfore

A 3G icon will be seen if the tes Using the 3G handset g se

Voice call SMS Video Call PS Services (Web Browsin

Usi Tester to download large file at high speed do Tester to conduct a voice calls while engage The results will be written i The validity o

signatures of the tester and vendor will be affixed to the results.



Date 9/27/2006

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

Title 3G and HSDPA Trial Test Cases and Procedures of 177 6.2.2 IN DOOR COVERAGE ASSESSMENTS (PILOT TEST)

T al level strength and ndoor Test Procedure:

Teste d in different buildings an n which may i Hospitals, and Offices.

sign d si in t For in oor assessments and outdoor

essments, test points are based on the Criteria and Guidelines as dio 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.

here the PI will use a

ird-party drive test tool while the vendor can use their own drive test

PI and supplier will compare the plot of each drive test.

Expected Result: accurate and acceptable to DMPI.

l, C/I or its 3G equivalence. roughput. The results should also be

R C/I

DOOR / OUT

Objective: his assessment is conducted to identify the sign

signal quality in the areas to be verified, be it an outdoor or i location.

r/s are deployenclude Malls, Hotels,

d institutio

Tester will be checking theareas or streets or floor.ass

al level an gnal quality the differend

provided by Ra

DMPI and the supplier shall conduct different drive test wtesters situated in each point will plot the RSSI and SIR. DMthtool. DM

The coverage plots areThe plots for voice should include quality, leveThe plots for data should include thtabulated: VOICE X Quality RX Level

DATA

Throughput (kbps)



Date 9/27/2006

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


6.2.3 Stres

6.2.3.1 Vo ______

Scenario: Sun Cellular 3G to Sun Cellular 3G

Test Execution:

Aber minutes

thrice at each of the test point a sults

s Test (Subjective Measurements)

ice Call: Site A ______________ Site B _______________ Phone Type _________ Phone Type ____

. For Continuous Mode Tester A to dial Tester B num Call will be terminated after 5 This will be repeated Record observation/comments nd re

Results Test Location Expected Results

1st Test 2nd Test 3rd Test Clear Voice Choppy Voice Disconnected before completion

all of 5 minutes Voice C Unable to Connect

B. For Call Gen Mode dial Tester B Number

Call will be terminated after 2 minutes

s will be repeated thrice at each of the test point. Record observation/comments and results

Tester A to

A 15-seconds pause is required before the next test sequence Thi

Results Test

Location Expected Results 1st Test 2nd Test 3rd Test

Cl ear Voice Ch oppy Voice Disconof 2 minutes Voice Call

nected before completion

Establis ice call in 3 ts.

hed connection of vo consecutive attemp

Unable to Connect

6.2.3.2 S

Scenario: Sun Cellular 3G to Sun Cellular 3G

T

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

MS:

est Execution:



Date 9/27/2006

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


Tester A to create text message icon, indicate the cell phone number or access number to

which the message will be sent during the test

s will be repeated thrice at each of the test point Record observation/comments and results

A. For SMS

In the “To:”

Monitor if the text message created was successfully sent Thi

Results Test


TesteTeste

r A able to send SMS to r B

Unab le to send SMS 6.2.3.3 Vid ______

_____

Scenario 1: Sun Cellular 3G to

Test Exec

A. For Continuous Mode ct number of Tester B

on ll” tion

be co ected d after 5 minutes

rice at each of the test point tion/comments a sults

eo Call: Site A ______________ Site B _______ Phone Type _________ Phone Type _____

Sun Cellular 3G

ution:

Tester A to dial conta Tester A to click on “Call” opti Tester A to choose “Video Ca Wait until the video call will

opnn

Video Call will be terminate This will be repeated th Record observa

nd re

Results Test Loc ion at 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

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



Date 9/27/2006

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


Call will be connected Video Call will be terminated after 2 minutes

l be repeated thrice at each of the test point. Record observation/comments and result

Wait until the Video

A 15-seconds pause is required before the next test sequence This wil


1st Test 2nd Test 3rd Test Clear Video and Voice Clear Video but Choppy Voice Dof 2 minutes Video call

isconnected before completion

Distorte d Video and Choppy VoiceNo 3G Icon e ral

n ven after seve

manual network selectio Poor Video and Choppy Voice

Poor Video but Good Voice Established connection of Video

ive attempts. call in 3 consecut

Unable to Connect

6.2.4.4 W

Test Execution:

ication with ve

A.

page via WAP for 5 minutes.

Web address to be typed would be: http://www ar.com.ph

AP Browsing:

Settings of 3G test handset for WAP browsing are subject for verif

ndor.

For WAP Browsing Tester A to connect and browse the WAP

.suncellul

P er ca wsice at e tes

on/comments and results

age will connect and test n begin broach of the

ng t point. This will be repeated thri

Record observati


1st Test 2nd Test 3rd Test

Continuous Connection

Disconnected before completionof 5 minutes WAP browsing

No 3G Icon even aftmanual network sele

er several ction

Unable to Connect



Date 9/27/2006

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


6.2.4.5 Internet Browsing:

Test Exec

S et for Interne rowsing ar ubject for verification with v

A sing

nect and browse the internet via phone internet browser for 5

rent l

ution:

ettings of 3G test hands t b e sendor.

. For Internet Brow Tester to conminutes.

Each Tester will use a diffe• http://www.yahoo.c

inkom

• http://www.google.com • http://www.friendster.com

nq7.net• http://www.i • http://www.cnn.com • http://www.suncellular.com.ph

connect and tester can begin browsing This will be repeated thrice at each of the test point.

rvation/comments and results

Page will

Record obse


1st Test 2nd Test 3rd Test


Do

isconnected before completion f 5 minutes Internet browsing

Nmanual network selection

o 3G Icon even after several

t Unable to Connec



Date 9/27/2006

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


6.2.4.6 Mult

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

Te

A. ming Tester A to view multimedia live video via streaming URL to be accessed is still for verification with the vendor.

will connect and tester can begin to view the video stream This will be repeated thrice at each of the test point

servation/comments and results

imedia Streaming:

r. st Execution: For Live Video Strea

Page

Record ob


1st Test 2nd Test 3rd Test Clear Video and Audio Frequent Buffering Disc efore completion

onnected b

of 6 min-streaming Distorted Image No 3G Icon even after several

a ual network selection m n Poor Video and Choppy Audio Poor Video but Clear Audi o

Unable to Co nnect

B. For Video Streaming On Demand Tester A to view multime emand) via streaming URL to b erification with the vendo Page will egin to view the video stream This will b int Record o

dia (video on de accessed is still for v r connect and tester can be repeated thrice at each of the test po

bservation/comments and results


1st Test 2nd Test 3rd Test Clear Video and Audio Frequent Buffering Disconnected before completion

f 6 min-streaming oDistorted Image No 3G Icon even after several

anual network selection mPoor Video and Choppy Audio Poor Video but Clear Audio

nable to Connect U C. For L e 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

iv



Date 9/27/2006

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


Results Test


Clear Video and Audio Frequent Buffering Disconnected before completion

of 6 min-streaming Distorted Image No 3G Icon even after several

anual network selection mPoor Video a nd Choppy Audio Po or Video but Clear Audio

Un leab to Connect

6.2.3.7 Downlo Test e

Set s with vendor.

A. Frnet via WAP for 2 minutes.

be:

ading

Ex cution:

ting of 3G test handset for WAP browsing are subject for verification

or Downloading Tester A to connect and browse the inte Web address to be typed wouldwww.suncellular.com.ph/sunwap/test/truewav.wav

Tester will be prompted to save lts

Record observation/comments and resu

Test Location Ex ults pected Res Results

Continuous Connection Disconnected before ompletion of 2

WAP brows c

minutes ing

Able to download file

Unable to download fileNo 3G Icon even after several manual

selection network to Connect Unable

6.2.3.8 MMS

Cellular 3G

T

Settings o t handset for MMS are subject for verification with vendor.

A. F

In the “To:” icon, indicate the cell phone number or access number to ic

Monitor if the multimedia created was successfully sent

Scenario: Sun Cellular 3G to Sun

est Execution:

f 3G tes

or MMS Tester A to create multimedia message

wh h the message will be sent during the test



Date 9/27/2006

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


Rec

This will be repeated thrice at each of the test point ord observation/comments and results


1st Test 2nd Test 3rd Test Te ster A able to send MMS

Unable to send MMS

6.2.2.3.9 HSDPA Test Execution: Setti 3G test laptop for HSDPA are s r verificati vendor. A. PA

card. er A will then cess http://www.microsoft.com

ngs of ubject fo on with

For HSD Tester A will use Laptop to be connec

datated to the internet using 3G HSDPA

Test ac he download page, click Home & Office XP Service 3 (SP3) file will be accessed.

er will be prom ted to save.

On tPack

Office and the

Test p

Test L ocation Expected Results Results

Continuo s Connection u Disconn ted before comple n of HSDPA downloading

ec tio


Unable to download file No 3G Icon even after several manual network selection

Unable to Connect



Date 9/27/2006

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


lity

twork point of view.

A. Per Site Ba

6.2.4.1 Voice Call Set-up Test Objective

This test is d sure the speed con ection from calling party (originatin the receiving party (terminating call). Test Procedure:

The te quipped w Agilent Dri Test tool (w pre-installed WAMS software) and two 3G phones.

Before sta the test, tester/s will note down the CID and the RSCP (in db serving N de B in the routes/areas to be tested. This will be rec the Call S t-up Test Form.

Time to be re s the numbers of seconds to estswitched voice call.

Teste ord the c l set-up time the call set-up Test form. For each route/area, it is recommended the testers conduct 10

s during the test.

Exp Test Lo Ph

6.2.4 Objective Measurements of Qua

The tests will be performed on a per site basis and also on a whole ne

sis

: one to mea

g call) ton

ithster is e ve ith

rtingm) of the oorded in e

corded i ablish the circuit

r/s will rec al in

repetitions to obtain more sample The specific test points will depend in the routes/area to be checked.

ected Result:

cation: ______________ Cell ID: ____________ one Type ________________

Trial Call Set-up Time (seconds)

RSSI (Rx LEV) (dbm)

Trial 1 rial 2 T

Trial 3 Trial 4 Trial 5 Trial 6 Trial 7 Trial 8

Trial 9 Trial 10

6.2.4.2 Voice Call Quality Test Objectiv

This one to ch k the call qu ty in the rou /areas to be test

Test Procedure:

The equipped with Agilent Drive Test tool and two 3G phon

One ill make the call and the other tester will receive the call.

e: test is d ec ali tes

ed.

tester ises.

tester w



Date 9/27/2006

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


During the call in each test point, the tester will record the RSCP (in m), Ec/Io in db, Tx Power in dB and CID. This will be recorded in

the Call Quality Test Form. rea, it is recommended the testers conduct 10

Expected Result: Test Loca ___ Phone Type: __

db

For each route/arepetitions to obtain more samples during the test.

tion: ______________ Cell ID: _________

__ ___________

Trial Ec/Io (db) RSCP Rx LEV (dbm)

Tx Power (dbm)

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

Tr ial 10

SMS Tes

Objective:

re the availability and performance of the SMS

as where the SMS will originate d will be received.

o itself. l

6.2.4.3

t

SMS test is used to measuervice. s

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/arean

The tester will send a SMS t The tester will record the Send Time, Receive Time, and Tota

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.



Date 9/27/2006

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


____

Expected Result:

Test Location: ______________ Cell ID: ________

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

est Procedure: other phone connected to the same

PC Before starting the test, the tester/s will record the CID of the

ere the SMS will originate

r will send a SMS to another phone connected to the

eive Time, and Total

recommended the testers conduct 10 re samples during the test.

cation: ______________ Cell ID: ____________ Phone Type: _______________

T• One phone sends SMS to an

serving Node B in the routes/areas whand will be received.

The testesame PC.

The tester will record the Send Time, RecTime. This will be recorded in the SMS Test form.

For each route/area, it is repetitions to obtain mo

Expected Result: Test Lo

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



Date 9/27/2006

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


6.2.4.4 MMS OThe MMS test is used to measure the availability and performance of a MMS servic AP.

Test Procedure: MMS test m criteria.

apable should able

Before starting the test, the tester/s will record the D of the serving Node B in the routes/areas where the MMS will originate an ceived. The tester w send a MMS to another phone conn ted 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

E

T P n

Test

bjective:

e. The test currently supports MMS transactions over the W

ust meet the followings shouPhone SIM

Test SIMsld be MMS cbe GPRS en

CI

d will be reill ec

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.

xpected Result:

est Location: ______________ Cell ID: ____________ ho e Type: _______________

Trial Tx Upload Time (s)

Tx Upload Rate (s)

Rx Upload Time (s)

Rx Upload Rate (s)

Total Test Time(s)

Trial 1 Trial 2 Trial 3

6.2.4.5 WAP TeObjectiv

nt test in the mobile environment due to widespread use o Ain a m ar to a WAP browser. However, the WAP test differs from a b p d

Test Procedure:

• Test SIMs should Before starting the test, the tester/ the CID of the serving

Node B in the routes/ where t t 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

st e:

WAP test is an importa

f W P-based technology. The WAP test downloads a web page from a server anner simil

rowser because the test takes measurements that are indicators of QoSrovi ed by a WAP service.

be GPRS enable s will record he WAP tesareas

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.



Date 9/27/2006

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


Expected Result: Test Location: ______________ Cell ID: ____________ Phone Type: _______________

Trial Total

Response Time (s)

Gateway Connect Time (s)

Data Transfer Time (s)

Gateway Disconnect

Time (s)


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) Trial Average Maximum

Download 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



Date 9/27/2006

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


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: _______________


Download Time


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.


Download Time


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) Trial Average Maximum

Accepted Value

32 Bytes 70 ms 256 Bytes 70 ms 1024 Bytes 70 ms



Date 9/27/2006

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

Title 3G and HSDPA Trial Test Cases and Procedures 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

Handover 3G to 3G Handover Success Rate




Date 9/27/2006

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


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.



Date 9/27/2006

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


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



Date 9/27/2006

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


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.



Date 9/27/2006

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


MSC/VLR HLRRNC

SEND_ROUTING_INFORMATION_REQPROVIDE_ROAMIN

G_NUMBER_IND


ALERTING



PAGING

PAGING_RESPONSE

COMMON_ID





CALL_CONFIRMED


CONNECT

CONNECT_ACKNOWLEDGE

IAM

ACM

ANM

DISCONNECT

RELEASE

RELEASE_COMPLETE

REL

RLC

IU_RELEASE_COMMAND

IU_RELEASE_COMPLETE

UE 2G MSC

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.



Date 9/27/2006

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


UE1 MSC/VLR 2G HLR

CM_SERVICE_REQUEST


RNC


SECURITY_MODE_COMPLETESEND_ROUTING_INFORMATION_RE

Q

PROVIDE_ROAMING_NUMBER_IND


CALL_PROCEEDING

SETUP

COMMON_ID




ALERTING

CONNECT

CONNECT_ACKNOWLEDGE

2G MSC

IAM

ACM

ANM

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.



Date 9/27/2006

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


UEa MSC/VLR SMC

CM_SERVICE_REQUEST



RNC



MAP_MO_FORWARD_SMFORWARD_SHORT_MESSAGE_REQ

SMS_CP_ACK

SMS_CP_DATA

SMS_CP_DATA

SMS_CP_ACK

COMMON_ID

IU_RELEASE_COMMAND

IU_RELEASE_COMPLETE

MAP_MO_FORWARD_SMFORWARD_SHORT_MESSAGE_CNF

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.



Date 9/27/2006

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


UE A MSC/VLR HLR

MAP_MT_FORWARD_SMFORWARD_SHORT_MESSAGE_IND

MAP_SEND_ROUTING_INFO_FOR_SM_ACK


RNC



SMS_CP_ACK

SMS_CP_DATA

SMS_CP_DATA

SMS_CP_ACK

IU_RELEASE_COMMAND

IU_RELEASE_COMPLETE

SMC

PAGING

PAGING_RESPONSE

COMMON_ID

MAP_MT_FORWARD_SMFORWARD_SHORT_MESSAGE_RSP

MAP_SEND_ROUTING_INFO_FOR_SM


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.



Date 9/27/2006

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


3G HLR 2G MSC/VLR3G MSC/VLR

Send_authentication_info_req

Send_authentication_info_respone

Update_Location

Insert_Subscriber_data

Insert_Subscriber_data ack

Update_Location ack

Cancel_Location

Cancel_Location ack

BSC/MS

Location_Update req.

Authentication_req.

Authentication_resp.

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.


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.



Date 9/27/2006

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





Update_Location



Update_Location ack

Cancel_Location

Cancel_Location ack

RNC/UE


Authentication_req.





Identity_req

Identity_resp.

3. CS HPLMN selection from GSM to WCDMA Objective:

Check whether UE can perform HPLMN selection from GSM to WCDMA which has different PLMN.


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


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.



Date 9/27/2006

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





Update_Location



Update_Location ack

Cancel_Location

Cancel_Location ack

RNC/UE


Authentication_req.





Identity_req

Identity_resp.

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.



Date 9/27/2006

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


MS 2G SGSN HLR

Attach Request

Update Location

Attach Accept

Cancel Location

Update Location Ack

Attach Complete



Identity Request

3G SGSN

Identif ication Request

Identif ication Response

Identity Response



(Note 3)

(Note 1)

(Note 2)

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.

Cancel Location Ack



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.




Date 9/27/2006

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


MS 3G SGSN HLR

Attach Request

Update Location

Attach Accept

Cancel Location

Update Location Ack

Attach Complete

RNC





Identity Request

2G SGSN

Identification Request

Identification Response

Identity Response





(Note 3)

(Note 3)

(Note 1)

(Note 2)

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.

Cancel Location Ack



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.




Date 9/27/2006

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


MS BSS SRNS New3G-SGSN

Old2G-SGSN GGSN HLR

Routeing Area Update Request

SGSN Context Request

SGSN Context Response





SGSN Context Acknowledge

Update GPRS Location

Cancel Location

Cancel Location Ack



Update GPRS Location Ack



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.

(Note 1)

(Note 2)

Common ID





C. Cell Reselection 1. CS Cell Reselection from WCDMA to GSM Objective:

Check whether UE can perform cell reselection from WCDMA to GSM.


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


number. Expected Result:

The Location Area Updating request is accepted by the GSM network and the UE is registered to GSM network.



Date 9/27/2006

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





Update_Location



Update_Location ack

Cancel_Location

Cancel_Location ack

BSC/MS


Authentication_req.





2. CS Cell Reselection from GSM to WCDMA Objective:

Check whether UE can perform cell reselection from GSM to WCDMA.


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


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.



Date 9/27/2006

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





Update_Location



Update_Location ack

Cancel_Location

Cancel_Location ack

RNC/UE


Authentication_req.





Identity_req

Identity_resp.

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.



Date 9/27/2006

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



Old3G-SGSN GGSN HLR










Cancel Location

Cancel Location Ack






Iu Release Command

Iu Release Complete

(Note 1)

(Note 2)

(Note 3)


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


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.



Date 9/27/2006

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



Old2G-SGSN GGSN HLR










Cancel Location

Cancel Location Ack







(Note 1)

(Note 2)

Common ID





D. Handover 1. CS handover from WCDMA to GSM Objective:

Check whether UE can perform Inter-System service handover from WCDMA to GSM.


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.



Date 9/27/2006

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


3G MSC

RELOCATION COMMAND

RELOCATION REQUIRED

RNC UE

HANDOVER FROMUTRAN COMMAND

IU RELEASE COMPLETE

IU RELEASE COMMAND

2G MSCBSC

PREPARE HANDOVERREQUEST

PREPARE HANDOVERRESPONSE

HANDOVER REQUEST

HANDOVER RESPONSEack.

IAM

ACM

PROCESS SIGNALLINGHANDOVER DETECT

ANM

SEND END SIGNALHANDOVER COMPLETE

2. CS handover from GSM to WCDMA Objective:

Check whether UE can perform Inter-System service handover from GSM to WCDMA.


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


The voice call has not been affected during the handover procedure.



Date 9/27/2006

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


2G MSC

HANDOVER COMMAND

HANDOVER REQUIRED

BSC UE

HANDOVER COMMAND

RELEASE COMPLETE

RELEASE

3G MSCRNC



RELOCATION REQUEST

RELOCATIONRESPONSE ack.

IAM

ACM

PROCESS SIGNALLINGRELOCATION DETECT

ANM

SEND END SIGNALRELOCATIONCOMPLETE

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.



Date 9/27/2006

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



Old3G-SGSN GGSN HLR









SRNS Data Forward Command

SRNS Context Request

SRNS Context Response

Forward Packets

Forward Packets

Update PDP Context Request

Update PDP Context Response


Cancel Location

Cancel Location Ack






Iu Release Command

Iu Release Complete

Cell Change Order From UTRAN

(Note 1)

(Note 2)


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.


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



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


from traces. Verify the MS information in the 2G SGSN that the PDP Context

is Active and the data transfer is normal.



Date 9/27/2006

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


Expected Result: The data session has not been affected during the handover procedure.


Old3G-SGSN GGSN HLR









SRNS Data Forward Command

SRNS Context Request

SRNS Context Response

Forward Packets

Forward Packets




Cancel Location

Cancel Location Ack






Iu Release Command

Iu Release Complete

(Note 1)

(Note 2)


5. PS handover from GPRS to WCDMA Objective:

Check whether UE can perform Inter-System PS handover/reselection from GPRS to WCDMA.



3G to SGSN. Power on UE and verify that the MS is attached to the GPRS



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


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.



Date 9/27/2006

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


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

MS BSS SRNS New

3G-SGSNOld

2G-SGSN GGSN HLR









Forward Packets




Cancel Location

Cancel Location Ack






(Note 1)

(Note 2)

Common ID

Service Request


RB Setup

RB Setup Complete







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.



Date 9/27/2006

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


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.

3G MSC

RELOCATION COMMAND

RELOCATION REQUIRED

RNC UE

HANDOVER FROMUTRAN COMMAND

IU RELEASE COMPLETE

IU RELEASE COMMAND

2G MSCBSC



HANDOVER REQUEST

HANDOVER RESPONSEack.

IAM

ACM

PROCESS SIGNALLINGHANDOVER DETECT

ANM

SEND END SIGNALHANDOVER 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


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.



Date 9/27/2006

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



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.



Date 9/27/2006

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


APPENDIX A. NETWORK ELEMENTS INFORMATION

Network Element HW Version Software Version

Node B

RNC SGSN GGSN HLR SMSC MMSC BTS MSC MGW



Date 9/27/2006

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

Title 3G and HSDPA Trial Test Cases and Procedures of 177 B. TEST RESULTS

Test Category Test Item Expected Results IMSI attach in same service area (SA)

Test the function of IMSI attach in one SA.

□ Passed □ Failed □ Untested

CS TESTING A. Mobility Management IMSI Attach

IMSI attach in different service area (SA)

Test the function of IMSI attach in a different SA.


MS location updates with IMSI

Test the function of MS location updates with IMSI


Location Update

Periodic location update

Test the function of Periodic location update


MS location updates with IMSI

Test the function of IMSI Detach


IMSI Detach

Implicit IMSI detach

Test the function of Implicit IMSI Detach


Authentication

UE authentication in RNC serving area in updating location

Test the function of authentication process in updating location


Ciphering in location update

Test the function of ciphering process in updating location


Ciphering

Ciphering in subscriber’s MOC/MTC

Test the function of ciphering process in call processing


IMSI unknown in HLR

Test the function of location update but IMSI unknown in HLR


Location Update Fail

Roaming restrict

Test the function of roaming restrict




Date 9/27/2006

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


Mobile to Mobile Speech Call

Test the function mobile to mobile speech call


Voice calls with 8 AMR

Test the function of Voice Calls with 8 AMR Code


B. Basic Service Mobile to Mobile Speech Call

TrFO function in 3G End Office

Test the function of TrFO in 3G End Office


Mobile to PSTN Speech Call

Test the function of mobile to PSTN speech call


Mobile to PSTN Speech Call, UE sending DTMF

Test the function of DTMF


Mobile to PSTN, more than 15 digits

Test the function that the MSC can handle dialing a PSTN number with more than 15 digits


PSTN to Mobile speech call

Test the function of PSTN to Mobile speech call


Speech Call between Mobile and PSTN

PSTN to Mobile speech call with Echo Cancellation

Test the function of echo cancellation


Video Call

Mobile to Mobile Video Call

Test the function of Mobile to Mobile video call


Emergency call (no USIM inside UE)

Test the function of Emergency Call


Special Service Call

Emergency call (USIM inside UE)

Test the function of Emergency Call




Date 9/27/2006

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


Short Message Service (MO)

Test the function of Short Message Service (MO)


Short Message Service (MT)

Test the function of Short Message Service (MT)


Mobile can receive SMMT during speech call

Test the function of Mobile receive SMMT during speech call


Mobile can receive SMMT during video call

Test the function of Mobile receive SMMT during video call


SMMT to a UE, out of coverage

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


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

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


Short Message Service

SMMT to a memory full UE, UE can receive SMS memory not full

Test the function of that UE B can receive short messages when there is free memory again


Mobile Terminating Call, the UE is busy

Test the function of Call Failure Processing when the called UE is busy


Mobile Terminating Call, the UE does not answer

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


Call Failure Processing

Mobile Terminating Call, the UE is out of coverage

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




Date 9/27/2006

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


Mobile Terminating Call, the UE is switched off

Test the function of Call Failure Processing when the called UE is powered off


Mobile Terminating Call, the UE is NULL

Test the function of Call Failure Processing when the called UE number is NULL


Call Forwarding Unconditional

Test the function of Call Forwarding Unconditional


Call Forwarding on Mobile Subscriber Busy

Test the function of Call Forwarding on Busy


Call Forwarding on No Reply

Test the function of Call Forwarding on No Reply


Call Forwarding on Mobile Subscriber Not Reachable

Test the function of Call Forwarding on Mobile Subscriber Not Reachable


Call Forwarding notification to A-party and B-party

Test the function of Call Forwarding notification to party A and party B


C. Supplementary Service Call Forwarding

Call Forwarding activation/interrogation/ deactivation

Test the function of Call Forwarding activation/interrogation/ deactivation


Call Forwarding Unconditional for Video Call

Test the function of Call Forwarding for Video Call


Call Forwarding on Mobile Subscriber Busy for Video Call

Test the function of Call Forwarding for video call


Call Forwarding for Video Call

Call Forwarding on No Reply for Video Call

Test the function of Call Forwarding for Video Call on No Reply




Date 9/27/2006

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


Call Forwarding on Mobile Subscriber Not Reachable for Video Call

Test the function of Call Forwarding on Mobile Subscriber Not Reachable


Barring of All Outgoing Calls

Test the function of Barring of All Outgoing Calls


Barring of All Incoming Calls

Test the function of Barring of All Incoming Calls


Call Barring

Call Barring activation/interrogation/ deactivation

Test the function of call barring activation/interrogation/ deactivation


Barring of All Outgoing Calls for Video Call

Test the function of Barring of All Outgoing Calls for Video Call


Call Barring for Video Call

Barring of All Incoming Calls for Video Call

Test the function of Barring of All Incoming Calls for Video Call


Barring of All Outgoing Calls for SMS

Test the function of Barring of All Outgoing Calls for SMS


Call Barring for SMS

Barring of All Incoming Calls for SMS

Test the function of Barring of All Incoming Calls for SMS


MS subscribe CLIR

Test the function of MS subscribe CLIR


Number Identification

Only subscribe CLIP

Test the function of only subscribe CLIP


Call Completion

Call Hold

Test the function of Call Hold




Date 9/27/2006

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


Call Waiting

Test the function of Call Waiting


Multiple Call Hold Swapping

Test the function of multiple call hold swapping


SMMO can be initiated by MS who currently holds a call

Test the function of multiple call hold swapping


Multiparty Service

Six-Way Service

Test the function of six-way multiparty service


Bill of MOC

Test the function of Bill of MOC


Bill of MTC

Test the function of Bill of MTC


Bill of Call Forward

Test the function of Bill of Call Forward


Bill of Call Hold and Call Wait

Test the function of Bill of Call Forward


Bill of SMS (MO)

Test the function of Bill of SMS (MO)


D. CS Domain Charging (CDR) CDR Generating

Bill of SMS (MT)

Test the function of Bill of SMS (MT)


PS TESTING A. Mobility Management

GPRS attach with IMSI

Check if the network can successfully handle the GPRS attach originated by Normal Subscriber with IMSI




Date 9/27/2006

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


GPRS attach with P-TMSI

Check if the network can successfully handle the GPRS attach originated by Normal Subscriber with P-TMSI

□ Passed □ Fail □ Untested

Attach

GPRS attach, MS unknown in HLR

Check if the network can successfully handle the GPRS attach originated by Unknown Subscriber


MS initiated Detach

Check if the network can successfully handle detach originated by Normal Subscriber


Detach

SGSN initiated Detach-Implicit

Check if the network can successfully handle detach Normal Subscriber implicitly


Purge

Purge

Check if SGSN can successfully purge Normal Subscriber


Intra SGSN Routing Area Update

Check if the network can successfully handle the Routing Area Update originated by normal subscriber


Routing Area Update

Periodic RA update

Check if the network can successfully handle the periodic Routing Area Update


HLR modification of subscriber data

Check if SGSN can successfully handle modification of subscriber data from HLR


Subscriber Management

HLR deleting of subscriber data

Check if SGSN can successfully handle deleting of subscriber data from HLR


Security

Authentication

Check if the network can successfully implement authentication function




Date 9/27/2006

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


Ciphering

Check if the network can successfully implement ciphering function


PDP Context Activation, transparent mode, static IP address, GTP V1

Check if the network can successfully handle the PDP context activation procedure originated by normal subscriber with transparent mode and static IP address


Multiple PDP contexts

Check if the network can support multiple PDP contexts for subscriber


PDP activation reject due to unknown APN

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


B. Session Management PDP Context Activation

PDP activation reject due to service not subscribed

Check if the network can successfully handle the PDP context activation procedure originated by normal subscriber with service not subscribed


MS initiated PDP Context Deactivation

Check if the network can successfully handle the PDP context deactivation procedure originated by normal subscriber


GGSN initiated PDP Context Deactivation

Check if the operator can successfully deactivate PDP context from GGSN


PDP Context Deactivation

SGSN initiated PDP Context Deactivation

Check if the SGSN can successfully initiate PDP context deactivation


APN Selection Rule

APN selection rule, No APN in Activate PDP Context Request

Check if the network can successfully select APN of PDP context when there is no APN in Activate PDP Context Request




Date 9/27/2006

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


APN selection rule, Wild Card

Check if the network can successfully select APN of PDP context when MS subscribes a PDP context of wild card


APN selection rule, MS send APN, APN NI included

Check if the network can successfully select APN of PDP context when there is APN in Activate PDP Context Request, APN NI included


APN selection rule, MS send APN in Mixed Case

Check if the network can successfully select APN of PDP context when there is APN in Activate PDP Context Request, APN in mixed case


GGSN Address Resolution

GGSN address resolution by DNS

Check if the network can resolve GGSN address by DNS


SGSN Gn interface Network Link Redundacy

Check if the SGSN Gn interface network link redundancy function is right


SGSN Ga interface Network Link Redundancy

Check if the SGSN Ga interface network link redundancy function is right


GGSN Gi interface Network Link Redundancy

Check if the GGSN Gi interface network link redundancy function is right


C. Reliability and Stability Interface and Link Redundancy

E2E stability test

Check the stability of E2E performance


Transfer Rate

Uplink/Downlink transfer rate

Check if the network can successfully handle the PDP context activation procedure originated by Normal Subscriber with transparent mode and static IP address




Date 9/27/2006

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

Title 3G and HSDPA Trial Test Cases and Procedures of 177 D. PS Domain Charging M-CDR Generation

M-CDR Generation

Check if the SGSN can successfully generate M-CDR and send it to CG after MS GPRS detach


S-CDR Generation

S-CDR Generation

Check if the SGSN can successfully generate S-CDR and send it to CG after PDP deactivation


S-SMO-CDR and S-SMT-CDR Generation

S-SMO-CDR and S-SMT-CDR Generation

Check if the SGSN can successfully generate S-SMO-CDR and S-SMT-CDR and send it to CG


G-CDR Generation

G-CDR Generation

Check if the GGSN can successfully generate G-CDR and send it to CG after PDP deactivation


E. CG CDR Backup

CDR Backup

Check if the CG can back up the CDR files to the local disk


CG Client Function

CG Client Function – User Management

Check if the CG can add user, delete user, modify user’s attribute and check user’s right




Date 9/27/2006

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


AMR Speech Service (12.2k)

Test the function of bearing AMR Speech service


AMR Speech Service (10.2K)



AMR Speech Service (4.5K)



RAN TESTING A. Bearer Capability Test Service Bearing CS Domain

CS Transparent Data Service

Test the function of bearing CS transparent data service


PS Data Service (uplink 64K + downlink 64K)

Test the function of bearing PS data service (uplink 64K + downlink 64K)


Service Bearing PS Domain


Test the function of bearing PS data service (uplink 64K + downlink 384K)



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)


Combined Service Bearing

1 CS Transparent Data Service (uplink 64K + downlink 64K) + 1 PS Data Service (uplink 64K + downlink 144K)

Test the function of bearing 1 CS transparent data service (uplink 64 Kbps + downlink 64 Kbps) + 1 PS data service (uplink 64K + downlink 144K)


SMS Service on CS Bearing

Test the SMS Service on CS Bearing


SMS Service Bearing

SMS Service on PS Bearing

Test the SMS Service on PS Bearing


B. Mobility Management Paging

Page UE in Idle Mode

Test the function of page UE in idle mode




Date 9/27/2006

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


Page UE in CELL_DCH State

Test the function of paging UE in CELL_DCH state


AMR Speech Service Soft Handover

Test the function of soft handover for AMR speech service


Video Telephone Service Soft Handover

Test the function of soft handover for video telephone service


PS Service Soft Handover

Test the function of soft handover for PS service


Soft Handover

Combined Service Soft Handover

Test the function of soft handover for CS and PS combined service


Intra-Frequency Hard Handover

Test the function of intra-frequency hard handover


Speech Service Inter-Frequency Hard Handover

Test the function of inter-frequency hard handover for AMR speech service


Video Telephone Inter-Frequency Hard Handover

Test the function of inter-frequency hard handover for video telephone service


PS Service Inter-Frequency Hard Handover

Test the function of intra-frequency hard handover for PS service


Hard Handover

Combined Service Inter-Frequency Hard Handover

Test the function of intra-frequency hard handover for CS and PS service


Forward Handover

Cell Update Triggered by Cell Reselection

Test the function of cell update triggered by cell reselection




Date 9/27/2006

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


Cell Setup

Test the function of cell setup in Node B


Cell Reconfiguration

Test the function of cell reconfiguration in Node B


Cell Deletion

Test the function of cell deletion in Node B


Cell Block

Test the function of cell block


C. Logical O&M Logic Cell

Cell Unblock

Test the function of cell unblock


Common Transport Channel Setup

Test the function of common transport channel setup in Node B


Common Transport Channel Reconfiguration

Test the function of common transport channel reconfiguration in Node B


Common Transport Channel

Common Transport Channel Reconfiguration

Test the function of common transport channel deletion in Node B


System Information

System Information Update

Test the function of system information update


Resource Audit

Cell Resource Audit

Test the function of cell resource audit between RNC and Node B


Tracing

Uu Interface Tracing

Test the function of Uu interface tracing




Date 9/27/2006

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


Iub Interface Tracing

Test the function of Iub interface tracing


Iu Interface Tracing

Test the function of Iu interface tracing


Single User Tracing

Test the function single user tracing


CS Call Admission Control

Test the function of CS call admission control


D. Radio Resource Management and Control Admission Control

PS Call Admission Control

Test the function of PS call admission control


Congestion Control

Congestion Control

Test the function of cell congestion control


Load Balancing Control

Intra-frequency Load Balancing Control

Test the function of intra-frequency load balancing


AMRC

Test the function of AMRC


Dynamic Channel Configuration – Rate Adjustment

Test the function of AMRC


Dynamic Resource Control

Dynamic Channel Configuration – State Transition

Test the state transition function of dynamic channel configuration


Power Control

Uplink Outloop Power Control

Test the function of uplink outloop power control




Date 9/27/2006

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


Uplink Inner Loop Power Control

Test the function of uplink inner loop power control


Downlink Power Balancing

Test the function of power balancing among DL radio link in soft handover




Date 9/27/2006

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

Title 3G and HSDPA Trial Test Cases and Procedures of 177 SERVICES A. Short Message Services (SMS)

Authenticating Subscriber

Authenticating the calling party

Authenticating the calling party


Accessing SMC

MS-to-MS SMS

MS-to-MS SMS


Submitting and Storing SMs

Submitting and storing MS-to-MS SMs

Submitting and storing MS-to-MS short message


Forwarding after receiving SM prompt

Forwarding after receiving SM prompt


Forwarding SMs

Retrying forwarding SMs automatically

Retrying forwarding SMs automatically


Sending SMs of high priority first

Sending SMs of high priority first


Priority Processing

Forwarding SMs of high priority forcibly when MS is temporarily absent

Sending SMs of high priority high priority forcibly when MS is temporarily absent.


Status report-forwarding notification (successful forwarding).

Status report-forwarding notification (successful forwarding).


Requesting Status Report

Status report-unforwarding notification (permanent failure).

Status report-unforwarding notification (permanent failure).


Supporting SMs in English

Supporting SMs in English


Supporting SMs in English/Tagalog

Supporting SMs in Tagalog.

Supporting SMs in Tagalog.




Date 9/27/2006

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


Supporting SMs in both English and Tagalog.

Supporting SMs in both English and Tagalog.


Supporting Long SMs

Supporting long SMs of over 140 bytes

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


Setting system parameters-setting country code

Setting system parameters-OCOS and TCOS setting.


Setting system parameters-modifying the deleting mode

Setting system parameters-modifying the deleting mode


System resource monitor-number of SMs

System resource monitor-number of SMs


Querying SMs-querying SMs in the SME

Querying SMs-querying SMs in the SME


Querying SMs-querying SMs in the memory

Querying SMs-querying SMs in the memory


Querying SMs-querying SMs in the database

Querying SMs-querying SMs in the database


Account Management

Account Management


Maintenance and Test Function .

Interface Management

Interface Management


Database Module Functions

Database module function.

Database module function.




Date 9/27/2006

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

Title 3G and HSDPA Trial Test Cases and Procedures of 177 License Configuration

Reading legal license file

Reading legal license file


MMS UA to MMS UA in the Single MMSC (MM/DR/RR)

To test whether MMS can be retrieved immediately if they are sent from MMS terminal 1 to MMS terminal 2 via the same MMSC.


MMS UA to Email (MM/DR)

To test sending MMS from an MMS terminal to an Email address through the MMSC.


B .Multimedia Message Services (MMS) Basic Service Flows

Email to MMS UA (MM)

To test sending MMS from an MMS terminal to an Email address through the MMSC.


Multiple recipients

To test sending MMS from MMS terminal 1 to MMS terminal 2, an Email account, or an ICP application through the MMSC


Validity Period

To test the correctness of the validity period setting


Specify the Earliest deliver Time

To test sending MMS from MMS terminal 1 and Application to MMS terminal 2 through the MMSC at the specified time.


Maximum Number of Receptions

To test the function of checking the number of recipients


Auto provisioning and refreshing of subscriber

To test the functions of updating the subscriber information in database automatically and auto provisioning for new subscriber.


Basic Features

System-Level Blacklist

To test whether the MMSC can deny MMS to or from the subscribers in the system-level blacklist.




Date 9/27/2006

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


User-Level Blacklist

To test whether the system supports the user-level blacklist


Delivery Report, Terminal-to-Terminal

To test whether the MMSC supports the terminal-to-terminal delivery report.


Limit the MM message size at the MM1 interface.

To test the function of limiting MM message size at the MM1 interface.


Recipient number format

To test the recipient number formats supported by the MMSC


Traffic Control

To test the traffic control function of the MMSC


Terminal-to-Terminal Performance

To test the terminal-to-terminal performance


System Blacklist in MM3 interface

To test System Blacklist function at the MM3 interface


System Whitelist in MM3 interface

To test System Whitelist function at the MM3 interface


Limit the MM message size at the MM3 interface

To verify limiting the MM message size function at the MM3 interface


Service Deny for specified Number Segment.

To test the services deny function for specified Number segment.


Operation and Maintenance

Maintenance of user account privilege

To test the function of maintaining the user account privilege




Date 9/27/2006

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


Maintenance of customer management system operators

To test the function of maintaining the customer management system operators.


Maintenance of System-Level Blacklisted Subscriber

To test whether the system-level blacklisted subscriber can be managed and maintained through the customer management system.


Maintenance of UA Profile

To test whether the user agent profile can be managed and maintained through the customer management system.


System Parameter Maintenance

To test whether the system parameters can be maintained through the customer management system.


MMSC startup and shutdown

To test whether MMS system is working completely


Restart process when killed

The test whether the Module of the MMMSC will start automatically when it killed


Supporting the Flow of Media Streams Played on Demand

To verify that the video server supports the media streams played on demand


Supporting to Pause the Streams Being Played on Demand

To verify that the video server supports to pause the streams being played on demand


Supporting to Interrupt the Streams Media Being Played on Demand

To verify that the video server supports to interrupt the streaming service.


C. Streaming Services Media Stream on Demand Service

Supporting to Perform Forward Query and Backward Query Operations on the Media Stream Being Played on Demand

To verify that the video server supports the forward query and backward query operations on the streaming service




Date 9/27/2006

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


Supporting to Play Streams on Demand Continuously

To verify that the video server supports to play streams on demand continuously for a long time.


Supporting the Live Streaming Service Flow

To verify that the video server supports live streaming service.


Supporting to Pause/Stop and Continue the Live Streaming Service (Depends on the handset)

To verify that the video server supports to pause/stop the live streaming service being played.


Supporting to Receive Multiple Live Streams from the Encoder

To verify that the video server supports to receive multiple live streams from the encoder.


Live Streaming Service

Supporting to Play Live Streams Continuously

To verify that the video server supports to play live streams continuously.


Supporting File Format of 3gp/mp4

To verify that the video server supports play in 3gp/mp4 file format


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

To verify that the video server supports H.263/MPEG-4 video encoding format.


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

To verify that the video server supports AMR-NB/AAC-LC audio encoding format.


Supporting Conversion Between Multiple Media File Formats (avi, mpg, mp3) – Live Stream Encoding

To verify that the video server supports conversion of multiple media file formats.


Supporting Export Type in File Format of 3GP

To verify that the video server supports export type in 3GP file format


Supporting Encoding

Supporting Output of Audio Only/Video Only

To verify that the video server supports output of audio only/video only




Date 9/27/2006

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


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

To verify that the video server supports multiple video encoding formats


Supporting to Published On-Demand Media Files to Video servers

To verify the function of publishing on-demand media files to Video servers


Supporting to Published Live Contents

To verify the function of publishing on-demand media files to Video servers


Supporting to Censor Contents

To verify that the video server supports to censor the contents


Supporting to Delete Media File on the Streaming Server

To verify that the video server supports to delete the media file on the streaming server.


Content Management Function

Supporting to Delete Live Content Files

To verify that the video server supports deletion of live content files


Supporting Multiple Level Operators Function

To verify the video server supports multiple level operators


CP Management Function

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

To verify the video server supports management of the CP account


Security Management Function

Supporting User Management (Adding/Deleting/Modify)

To verify the video server supports User registration functions


Supporting Application Startup/Stop

To verify the video server supports startup/stop applications


Security Management Function

Supporting Database Startup/Stop

To verify the video server supports startup/stop Database




Date 9/27/2006

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


Supporting Configuration Backup and Restore

To verify the video server supports configuration backup and restore


Supporting Database Backup and Restore

To verify the video server supports Database backup and restore


Supporting Generating CDR

To verify that the CDR file can be generated


Supporting Billing Function

Supporting Generating CDR for Aborted Play

Supporting the billing function in case of aborted play.




Date 9/27/2006

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


HSDPA Cell R99 UE Call Establishment - DCH-PS

To verify that HSDPA CELL UE R99 PS CALL ESTABLISHMENT


HSDPA Cell R99 UE Call Establishment - DCH-CS

To verify that HSDPA Cell UE R99 CS Call Establishment


HSDPA Cell HSDPA UE Call Establishment-Emergency

To verify that HSDPA Cell UE Emergency Call Establishment


HSDPA Cell HSDPA UE Call Establishment-SMS

To verify that HSDPA Cell UE SMS service.


HSDPA Cell HSDPA UE Call Establishment-H-PS

To verify that HSDPA Cell UE HSDPA PS Call Establishment


HSDPA to Multiservice-Multiservice AMR+HSDPA-PS

To verify that the system support CS+HSDPA PS Service


HSDPA Testing A. RAB Mapping

HSDPA to Multiservice-Multiservice VP+HSDPA-PS

To verify that the system support VP+HSDPA PS Service


HSDPA flexible power allocation with fixed HS-SCCH power, OCNS 25% load

To verify that HSDPA flexible power allocation algorithm could use the remain power left by R99


B. Power Management

HSDPA flexible power allocation with fixed HS-SCCH power, OCNS 50% load

To verify that HSDPA flexible power allocation algorithm could use the remain power left by R99


C. Code Management

HSDPA RNC controlled code allocation, R99 takes more

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.




Date 9/27/2006

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


HSDPA RNC controlled code allocation, HSDPA takes more

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.


HSDPA to HSDPA Mobility, Intra-RNC, Intra-NodeB, Intra- frequency

To verify the HSDPA service to ensure continuity when intra-frequency HS-DSCH cell change in the same NodeB does not 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, Intra-RNC, Inter-frequency

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.



HSDPA to non HSDPA Mobility, intra RNC,intra frequency

To verify that the RB carried by the HSDPA switches the service from HSDSCH to DCH after the handover from HSDPA supportive cell to non HSDPA supportive cell.



HSDPA to non HSDPA Mobility, Intra-RNC, Inter-frequency

To verify that the RB carried by the HSDPA switches the service from HSDSCH to DCH after the handover from HSDPA supportive cell to non HSDPA supportive cell.



D. Mobility

Non HSDPA to HSDPA Mobility, Intra-RNC, Intra-frequency

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.

To verify that if the signaling




Date 9/27/2006

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


procedure is correct, check the signaling plane time delay and user plane time delay.

Non HSDPA to HSDPA Mobility, Intra-RNC, Inter-frequency

To verify that the RB carried by the HSDPA switches the service from DCH to HS-DSCH after the handover from non HSDPA supportive cell to HSDPA supportive cell.



E. Load Management

HSDPA CAC To verify HSDPA Admission Control function.


IUB Efficiency for HSDPA 1 E1

To verify Iub bandwidth utilization efficiency and user throughput vs. HSDPA users with extreme limited IUB configuration.


F. Iub Flow Control

IUB Efficiency for HSDPA and R99，1 E1

To verify Iub bandwidth utilization efficiency with limited IUB configuration; and bandwidth allocation between HSDPA and R99 users.


HSDPA to FACH and to Idle 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.


G. State Switch

FACH to HSDPA To verify that burst traffic is switched from FACH to HSDSCH.


H. RTT

Ping Packet Delay 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.


I. Hardware Capacity

3*1 with 15 HS-PDSCH/cell

To verify the capability of HSDPA 3X1 with 15 HS-PDSCH/cell.




Date 9/27/2006

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


The HSDPA and R99 mixed cell sharing one carrier

To verify that if the system could support the configuration of HSDPA and R99 mixed cell only occupy one carrier.


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

To get Cell Peak Traffic over 5 HS-PDSCHs, Category 12 UE, CDM4 CQI>16.





J. Throughput Capacity




K. System Reliability

HSDPA System Reliability To verify the system reliability of holding traffic for long time


Common measurement of HSDPA cell - transmitted carrier power of all codes not used for HS-PDSCH or HS-SCCH transmission



Common measurement of HSDPA Cell - HS-DSCH required power measurement



Common measurement of HSDPA Cell - HS-DSCH provided bit rate measurement



HSDPA cell configuration over Iub interface

To verify HSDPA cell configuration over Iub interface follows the requirement of protocol.


L. Iub Standard Interface

HSDPA service reconfigured on RL over Iub interface

To verify HSDPA service reconfigured on RL over Iub interface follows the requirement of protocol.


M. Configuration

Activate / Deactivate HSDPA funcionality in a nodeB

The purpose of this test is to Activate / Deactivate HSDPA function




Date 9/27/2006

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


Create a new nodeB with the HSDPA funcionlity

The purpose of this test is to check the procedure to create a new NodeB with the HSDPA function


Change of HSDPA Configuration Parameters

The purpose of this test is to change of HSDPA Configuration Parameters


Iub HSDPA capacity increase/decrease

The purpose of this test is to provide and execute the Iub capacity increase/decrease procedure


Coverage PLOTS VOICE

RX Quality RX Level C/I

DATA

Throughput (kbps)



Date 9/27/2006

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


Stress Test (Subjective Measurements) Voice Call A. For Continuous Mode:


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:


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 __________


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



Date 9/27/2006

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


Poor Video but Good Voice Unable to Connect

B. For Call Gen Mode

Site A ______________ Site B _____________ Phone Type _________ Phone Type __________


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



Disconnected before completion of 5 minutes WAP browsing

No 3G Icon even after several manual network selection

Unable to Connect Internet Browsing



Disconnected before completion of 5 minutes Internet browsing

No 3G Icon even after several manual network selection

Unable to Connect



Date 9/27/2006

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

Title 3G and HSDPA Trial Test Cases and Procedures of 177 Multimedia Streaming A. For Live Video Streaming


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



Unable to Connect C. For Live TV Streaming



Unable to Connect



Date 9/27/2006

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

Title 3G and HSDPA Trial Test Cases and Procedures of 177 Downloading

Test Location Expected Results Results Continuous Connection Disconnected before completion of 2 minutes WAP browsing


Unable to download file No 3G Icon even after several manual network selection

Unable to Connect MMS


Tester A able to send MMS Unable to send MMS HSDPA

Test Location Expected Results Results Continuous Connection

Disconnected before completion of HSDPA downloading


Unable to download file

No 3G Icon even after several manual network selection Unable to Connect



Date 9/27/2006

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


Voice Call Set-up Test

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


Voice Call Quality Test

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


SMS Test

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


MMS Test

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


Pilot/KPI Tests and Stress Tests

WAP Test

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.




Date 9/27/2006

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


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 10

Voice Call Quality Test Test Location: ______________ Cell ID: ____________ Phone Type ________________

Trial Signal-to-Interference Ratio (db) RSSI Rx LEV (dbm) Tx Power (dbm)


Trial 10



Date 9/27/2006

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


SMS Test A. One phone sends SMS to itself


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


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



Date 9/27/2006

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


MMS Test Test Location: ______________ Cell ID: ____________ Phone Type ________________

Trial Tx Upload Time (s)

Tx Upload Rate (s)

Rx Upload Time (s)

Rx Upload Rate (s)

Total Test Time(s)


WAP Test Test Location: ______________ Cell ID: ____________ Phone Type ________________

Trial Total Response Time (s)

Gateway Connect Time (s)

Data Transfer Time (s)

Gateway Disconnect Time

(s)




Date 9/27/2006

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


HSDPA

A. Stationary and Good Coverage Test Location: ______________ Cell ID: ____________ HSDPA Card Type ________________

B. Stationary and Bad Coverage

Test Location: ______________ Cell ID: ____________ HSDPA Card Type ________________

C. Mobile

D. Ping Tests


Download Time



Download Time



Download Time


Latency/Delay (seconds) Trial Average Maximum

Accepted Time

32 Bytes 70 ms 256 Bytes 70 ms 1024 Bytes 70 ms



Date 9/27/2006

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


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


2G to 3G Handover Success Rate



Date 9/27/2006

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


IOT

Voice call from GSM to WCDMA

Test the function of the GSM to WCDMA speech call


Voice call from WCDMA to GSM

Test the function of the WCDMA to GSM speech call


SMS from WCDMA to GSM

Test the function of Short Message Service from WCDMA to GSM.


IOT Test Scenarios 3G2G Interoperability/ Inter-working Tests A. Basic Function

SMS from GSM to WCDMA

Test the function of Short Message Service (MT).


CS Roaming from WCDMA to GSM

Check whether UE can perform Inter-System roaming from WCDMA to GSM.


CS Roaming from GSM to WCDMA

Check whether UE can perform Inter-System roaming from GSM to WCDMA.


CS HPLMN selection from GSM to WCDMA

Check whether UE can perform HPLMN selection from GSM to WCDMA which has different PLMN


PS Roaming from WCDMA to GPRS

Check whether UE can perform Inter-System roaming from WCDMA to GSM/GPRS.


PS Roaming from GPRS to WCDMA

Check whether UE can perform Inter-System roaming from GSM/GPRS to WCDMA.


B. Roaming

PS HPLMN selection from GPRS to WCDMA

Check whether UE can perform HPLMN selection from GSM/GPRS to WCDMA which has different PLMN.


C. Cell Reselection

CS Cell Reselection from WCDMA to GSM

Check whether UE can perform cell reselection from WCDMA to GSM.




Date 9/27/2006

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

Title 3G and HSDPA Trial Test Cases and Procedures

of 177


CS Cell Reselection from GSM to WCDMA

Check whether UE can perform cell reselection from GSM to WCDMA.


PS Cell Reselection from WCDMA to GPRS

Check whether UE can perform cell reselection from WCDMA to GPRS.


PS Cell Reselection from GPRS to WCDMA

Check whether UE can perform cell reselection from GPRS to WCDMA.


CS handover from WCDMA to GSM

Check whether UE can perform Inter-System service handover from WCDMA to GSM.


CS handover from GSM to WCDMA

Check whether UE can perform Inter-System service handover from GSM to WCDMA.


PS handover in Cell_DCH from WCDMA to GPRS

Check whether UE can perform Inter-System PS handover in Cell_DCH mode from WCDMA to GPRS


PS handover in Cell_FACH from WCDMA to GPRS

Check whether UE can perform Inter-System PS handover in Cell_FACH mode from WCDMA to GPRS.


PS handover from GPRS to WCDMA

Check whether UE can perform Inter-System PS handover/reselection from GPRS to WCDMA


CS+PS handover from WCDMA to GSM/GPRS

Check whether UE can perform Inter-System PS+CS handover from WCDMA to GSM/GPRS.


D. Handover

Video Call handover from WCDMA to GSM/GPRS

Check whether UE can perform Inter-System Video Call handover from WCDMA to GSM/GPRS


Reachability Test Check whether UE can receive SMS and voice calls after moving from 3G network to 2G network



Date 9/27/2006

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

Title 3G and HSDPA Trial Test Cases and Procedures

of 177


Signatories: _______________________ _________________________ DMPI Representative Vendor Representative

Suncell 3G and HSDPA Trial Test Procedures

Documents

Transcript of Suncell 3G and HSDPA Trial Test Procedures