huawei kpn project test specification for digital telephony testing_v0_93

This document is for use solely within Huawei and KPN. It should not be discussed, shown or referred to outside the organisation, without prior approval of the owner.

KPN Dragon Project

Project Document

Test Specification for Digital Telephony testing Issue V0.93

Date 2008-1-3

PDF 文件使用 "pdfFactory" 试用版本创建 www.fineprint.cn

http://www.fineprint.cn


Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. Please feel free to contact our local office or company headquarters.

Huawei Technologies (Netherlands) B.V. Address: Karspeldreef 4, 1101 CJ, Amsterdam Z-O

Website: http://www.huawei.com

Email: [email protected]

Copyright © Huawei Technologies Co., Ltd. 2006. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice

The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.


http://www.huawei.com

mailto:[email protected]


Project Document Test Specification for Digital Telephony testing About This Document


i

About This Document

Author Prepared by Jason Li Date 2007-12-11

Reviewed by Alex Su Date 2008-1-3

Approved by Date

Purpose This manual is written based on KPN requirement, with modifications to reflect the characteristics of Huawei equipment.

On finishing equipment installation and debugging, a test group, which consists of the KPN and Huawei staff, shall carry out test cases to the equipment, ensuring that it has reached the required indexes of KPN.

Related Versions The following table lists the product versions related to this document.

Product Name Version

MSOFTX3000 V100R006

UMG8900 V200R006

Intended Audience The intended audiences of this document are:





ii

l Policy planning

l Installation and Commissioning engineer

l NM configuration engineer

l Technical support engineer

l Test team member

Conventions

Numbering Specifications for Test Items Six-digit numeration

TXX-XXXX

Meaning

TXX-XXXXTest sub-item

Test item

Test category

General Conventions Convention Description

Arial Normal paragraphs are in Arial.

Boldface Names of files, directories, folders, and users are in boldface. For example, log in as user root.

Italic Book titles are in italics.

Courier New Terminal display is in Courier New.

GUI Conventions Convention Description

Boldface Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK.

> Multi-level menus are in boldface and separated by the “>” signs. For example, choose File > Create > Folder.





iii

Notes Before test starts, please ensure that the system is properly installed, the software and hardware debugging is passed, and the system functions normally.

The test items should be validated by representatives of KPN and the Huawei.

In actual test as well as in the preliminary tests, representatives of both parties should observe relevant testing criteria. As some indices are already tested before delivery, if the testing conditions are limited, sampling, or even exemption from testing can be introduced.

The used protocol is CAMEL phase 2.

& Special Comments:

In witness test, please stick to the contract and stipulation agreed by both parties. This manual serves as a reference only.





iv

References [1] KPN Telfort High Level Design (HLD) 2G and 3G Core Network. Jos Adema, Rob Wijsman.31 Dec

2006

[2] <<KPN DTT SPECIFICATION V1.3.doc>>

Update History Updates between document versions are cumulative. Therefore, the latest document version contains all updates made to previous versions.

Issue Details Date Author Approved by

0.9 Initial version 2007-12-11 Jason LI

0.91 Review by Jason 2007-12-14 Jason Li

0.92 Review by Zhoukia Huangyubing

2007-12-18 Jason Li

0.93 Revise 2008-01-03 Alex Su



Project Document Test Specification for Digital Telephony Testing Table of Contents


Page i of 24

Table of Contents

References...................................................................................................................................iv

Part I Overview...........................................................................................................................1

1 Overview..............................................................................................................................1 1.1 Test Topology In Stage 1...........................................................................................1 1.2 Test Topology In Stage 2...........................................................................................1 1.3 Test Topology In Stage 3...........................................................................................2 1.4 Test Topology In Stage 4...........................................................................................2 1.5 Test Topology In Stage 5...........................................................................................3 1.6 Test Equipments........................................................................................................3

2 Test Preparations.................................................................................................................3 2.1 Operations on MSOFTX3000 before the test session.................................................4 2.2 Operations on UMG8900 before the test session.......................................................4 2.3 Operations on MSOFTX3000 after the test session....................................................5 2.4 Operations on UMG8900 after the test session..........................................................6

Part II Operation Guide................................................................................................................7

Digital Telephony Testing........................................................................................................7

T44 Digital Telephony Testing.................................................................................................7 T44-01 Specified Resource Test Function........................................................................7

T44-0101 Specificed Circuit Mode.........................................................................................7 T44-0102 Polled Circuit Mode.................................................................................................8 T44-0103 Busy Circuit Sampling Mode...................................................................................8

T44-02 Specified Subscriber Test Function....................................................................9 T44-0201 Non-specified path mode........................................................................................9 T44-0202 Specified trunk group mode...................................................................................10 T44-0203 Specificed sub-route mode....................................................................................11 T44-0204 Specificed office direction mode............................................................................12

T44-03 Call Simulator Function......................................................................................13 T44-0301 Simulating a Call Originated by A Interface............................................................13 T44-0302 Simulating a Call Originated by Iu Interface...........................................................14 T44-0303 Simulating an incoming Call over a ISUP Trunk with Callee in the Local office through

the CSIS..............................................................................................................................15 T44-0304 Simulating an incoming Call over a BICC Trunk with Callee in the Local office through

the CSIS..............................................................................................................................16



Project Document Test Specification for Digital Telephony Testing Part I Overview


Page 1 of 24

Part I Overview

1 Overview

In the Huawei-KPN project, the test of Digital Telephony Testing for the validation of whether the Huawei MSC

can play support Digital Telephony Testing normally.

1.1 Test Topology In Stage 1

Topology A






Page 2 of 24

Topology B


Topology C






Page 3 of 24

Topology D


Topology E

1.6 Test Equipments

Throughout the test case, the following test equipments are used.

1. 2G SIM card and 2G MS (Mobile Station): For the 2G subscriber.

2. 3G USIM card and 3G UE (User equipment): For the 3G subscriber.

2 Test Preparations





Page 4 of 24

There are two types of test preparations that should be done before and after completion of a test case: General preparation and Specific preparation.

The general test preparation is recommended to do at the beginning of each test session. It is recommended to do at the beginning of each day before starting test execution.

The specific test preparations should be executed before each TC (Test Case) and after completion of each TC (Test Case). The specific pre-condition is described in each TC.

2.1 Operations on MSOFTX3000 before the test session

General preparation

Checks on MSOFTX3000 status is normal with default configuration including alarms, software version and board status at the beginning of each test session.

For the detailed operation, please refer to <Health check operation guide for MOSTX3000 and UMG>.

Specific test preparation

Set up the user interface signaling trace before the execution of each test case using the following steps. Specified signaling trace is described in the pre-condition for relevant test cases.

Set up “User Interface Trace” operation in MSOFTX3000.

Procedure Expected result

Select the “Maintenance” label in the left navigation tree;

The navigation tree for maintenance is displayed in the left frame of MSOFTX3000.

Double click the “ServiceàUser Message Trace àUser Message Trace”

The User message Trace window is popped up.

Input the called number in the incoming trunk with PSTN option to trace the user interface signaling.

Select all the interfaces and click OK button

The Real-time User message Trace Window is shown up.

Save the command and output log file for record before each of the test cases execution if there is MML command executed in test cases.


Select the menu item of “SystemàOutput Window Setting” in MSOFTX3000.

The “Output Window Setting” window is popped up.

Select the “Maintenance” label and then select the checkbox of “Export to File” and “Auto save”.

Enter your prefer trace file name and path.

Click the OK button.

Command and output log file is created successfully with recording the output in Maintenance window.

2.2 Operations on UMG8900 before the test session

General Preparation





Page 5 of 24

Check that UMG8900 status is normal with default configuration including alarms, software version, and board status and resource availability at the beginning of each test session.

For the detailed operation, please refer to <Health check operation guide for MOSTX3000 and UMG>.

Specific Preparation

Save the command and output log file for record before each of the test cases execution if there is MML command executed in test cases.


Select the menu item of “SystemàOutput Window Setting” in UMG.


2 Select the “Maintenance” label and then select the checkbox of “Export to File” and “Auto save”.

Enter your prefer trace file name and path.

Click the OK button.

Command and output log file is created successfully with recording the output in Maintenance window.

2.3 Operations on MSOFTX3000 after the test session

General procedure

Check whether all the resources are released and the system changes back to normal state.

For the detailed check operation, please refer to <Health check operation guide for MOSTX3000 and UMG>.

Close up all the signaling trace windows.


Single click the “X” button in right-top corner of the real-time signal trace window in MSOFTX3000.

All the real-time signal trace windows closed up.

Close up all the log trace options.


Select the menu item of “SystemàOutput Window Setting” in MSOFTX3000.


Select the “Maintenance” label and remove the checkbox of “Export to File” and “Auto save”.

Click the OK button

The log file function is disabled.

Specific procedure

Save the signal trace message in the User Message Trace for each test case in MSOFTX3000.






Page 6 of 24

Single right click mouse and select “Save All the message” in real-time User Message Trace window to save the user interface signaling trace into one file as record.

The all the user messages saved as *.tmf.

Single right click mouse and select “Save All the message” in real-time M3UA Link set window to save the ISUP signaling trace into one file as record.

The all ISUP messages saved as *.tmf.

2.4 Operations on UMG8900 after the test session

General procedure

Check whether all the resources are released and the system changes back to normal state.

For the detailed check operation, please refer to <Health check operation guide for MOSTX3000 and UMG>.

Close up all signaling trace window.


Single click the “X” button in right-top corner of the real-time signal trace window in UMG.

All the real-time signal trace windows are closed up.

Close up all the log trace options.


Select the menu item of “SystemàOutput Window Setting” in UMG.


Select the “Maintenance” label and remove the checkbox of “Export to File” and “Auto save”.

Click the OK button

The log file function is disabled.

Specific procedure

Check all the resources released.


Carry out MML command “DSP VMGWRSC” on UMG8900 LMT.

All the resources are released.



Project Document Test Specification for Digital Telephony Testing Part II Operation Guide


Page 7 of 24

Part II Operation Guide

Digital Telephony Testing

T44 Digital Telephony Testing

T44-01 Specified Resource Test Function

T44-0101 Specificed Circuit Mode

Objective

To verify that the specified resource test –Specificed Circuit Mode of the Call Simulation and Inspection System (CSIS) can be correctly implemented

Network diagram

Topology E

Precondition

l A is KPN subscriber.

l Login in LMT and open CSIS window. (Maintenance>Monitor > Call Simulation Inspection System)

Test procedure Expected result

1. Input A’s MSISDN number in Inspected No. and click Call to originate a test call to A.

A is alerting.

2. A answers the test call. The test call is connected.

The Setting form display in CSIS window.

3. Set Inspection Type to Detection of Designated Resources, Test Mode to Specified Circuit, and Inspecting Mode to Bi-directional, and input TG. Name, Start CIC and End CIC. Click Start to continue testing.

The CSIS window returns the output result in Result Output form indicating the current status of the specified circuit.

4. A releases the test call. The test call is released successfully.

Check Point

1. The output result is correct.

2. There is no CDR for the test phone call.

Remarks

You can continue the test by clicking Next, or start a new test by selecting another inspecting type. After the test, click Hang up or directly terminate the test call.





Page 8 of 24

T44-0102 Polled Circuit Mode

Objective

To verify that the specified resource test –Polled Circuit Mode of the Call Simulation and Inspection System (CSIS) can be correctly implemented

Network diagram

Topology E

Precondition





A is alerting.



3. Set Inspection Type to Detection of Designated Resources, Test Mode to Polled Circuit, and Inspecting Mode to Bi-directional, and specify values in TG. Name, Start CIC , End CIC, Step and Test Duration. Click Start to continue testing.

Huawei MSC perform the testing automatically on specified circuits according to the Step in a specified trunk group after the specified test duration times out



Check Point

1. The output result is correct.

2. There is no CDR for the test phone call.

Remarks


T44-0103 Busy Circuit Sampling Mode

Objective

To verify that the specified resource test –Specificed Circuit Mode of the Call Simulation and Inspection System (CSIS) can be correctly implemented

Network diagram

Topology E

Precondition


l Login in LMT and open CSIS window. (Maintenance>Monitor > Call Simulation Inspection





Page 9 of 24

System)



A is alerting.



3. Set Inspection Type to Detection of Designated Resources, Test Mode to Busy Circuit Sampling, and Inspecting Mode to Bi-directional, and specify values in TG. Name, Sampling Interval and Test Duration. Click Start to continue testing.

The system can automatically perform the sampling test on the busy circuits of a specified trunk group after the specified test duration times out.



Check Point

1.The voice on the busy circuits can be heard by A.

2.The output result is correct.

3. There is no CDR for the test phone call

Remarks


T44-02 Specified Subscriber Test Function

T44-0201 Non-specified path mode

Objective

To verify that the specified resource test and specified subscriber test of the CSIS can be correctly implemented

Network diagram

Topology E

Precondition

l A and B are both KPN subscriber.


Test Procedure Expected result





Page 10 of 24


A is alerting.



3. Set Inspection Type to Specified subscriber test and Path type to Do not Specify The Path, Input B’s number into the callee number, Click Start to continue testing.

The system automatically selects an accessible path to B, and also the message flows between NEs will be displayed.

The CSIS window depicts the general information flow of the connection. The connection displayed in the figure is the same as actual conditions.


Check Point

1.There is no CDR for the test phone call

2.MTC CDR is generated for B-subscriber ,

The Calling Party Number in MTC CDR is the MSC Server Address

The called party number in CDR will be B Party number.

The test telephone number will not appear in CDR.

Remarks


T44-0202 Specified trunk group mode

Objective


Network diagram

Topology E

Precondition

l A and B are both KPN subscriber.







Page 11 of 24


A is alerting.



3. Set Inspection Type to Specified subscriber test and Path type to Trunk Group, and input TG. Name, Start CIC , End CIC and Step, Input B-number into the Callee Number, Click Start to continue testing.

When the specified CIC is in idle state, the CIC can be connected to the specified subscriber.


4. Click Continue to continue the testing. The system displays the execution result on the Result Output tab

The currect CIC value is calculated as follows:

Current CIC value = Previous test CIC value + Step value

Check Point






Remarks


T44-0203 Specificed sub-route mode

Objective


Network diagram

Topology E

Precondition

l A is a KPN subscriber.

l B is a PSTN subscriber.







Page 12 of 24


A is alerting.



3. Set Inspection Type to Specified subscriber test and Path type to Subroute,and input Subroute Name. Input B-number into the Callee Number, Click Start to continue testing.

The system automatically selects an accessible circuit to the callee on Specifed subroute, and also the message flows between NEs will be displayed



Check Point


2.GWO CDR is generated for B-subscriber ,

The Calling Party Number in GWO CDR is the MSC Server Address


The test telephone number will not appear in CDR. 3. The Calling Party Number in the IAM message is the test telephone number.

Remarks


T44-0204 Specificed office direction mode

Objective


Network diagram

Topology E

Precondition









Page 13 of 24


A is alerting.



3. Set Inspection Type to Specified subscriber test and Path type to office,and input Incoming Office Name,Start CIC,End CIC and Step. Input B-number into the Callee Number, Click Start to continue testing.

When the specified CIC is in idle state, the CIC can be connected to the specified subscriber.


4. Click Continue to continue the testing. The system displays the execution result on the Result Output tab

The currect CIC value is calculated as follows:

Current CIC value = Previous test CIC value + Step value

Check Point






3. The Calling Party Number in the IAM message is the test telephone number.

Remarks


T44-03 Call Simulator Function

T44-0301 Simulating a Call Originated by A Interface

Objective

To verify that the MO call originated by A interface is successful

Network diagram

Topology E

Precondition

l A and B are both 2G KPN subscriber.







Page 14 of 24


A is alerting.



3. Simulate an MO call originated by A interface and configure the following parameters: Set Inspection type to Call simulator, and Analog type to A Interface; input Calling LAI and Calling CI respectively; set Calling Number Type to MSISDN;

Input A number into Calling party number

Input B number into called party number

Click Start to originate the call.

The callee is normally connected. After the callee is alerted, the test call stops playing the hold tone and then starts to play the ring back tone. After the callee is connected, the conversion is normally set up.

The system will displays relevant information flow of the call

4. After the call is connected, the simulating callee hangs up.

The simulating callee can normally hang up. The test call resumes the hold tone.

Check Point


2. MOC CDR is genearated for A-subscriber

The Calling Party Number in MOC CDR is the MSC Server Address







Remarks


T44-0302 Simulating a Call Originated by Iu Interface

Objective

To verify that the MO call originated by Iu interface is successful

Network diagram

Topology E

Precondition

l A and B are both 3G KPN subscriber.






Page 15 of 24



A is alerting.



3. Simulate an MO call originated by A interface and configure the following parameters: Set Inspection type to Call simulator, and Analog type to Iu Interface; input Calling LAI and Calling CI respectively; set Calling Number Type to MSISDN;






4. After the call is connected, the simulating callee hangs up.

The simulating callee can normally hang up. The test call resumes the hold tone.

Check Point










Remarks


T44-0303 Simulating an incoming Call over a ISUP Trunk with Callee in the Local office through the CSIS

Objective

To verify that an incoming call over a ISUP trunk is successful through the CSIS

Network diagram

Topology E

Precondition






Page 16 of 24





A is alerting.



3. Simulate an incoming call over a ISUP trunk and configure the following parameters: Set Inspection type to Call simulator, and Analog type to ISUP Trunk; input Incoming TG.Name






4. After the call is connected, the callee hangs up.


Check Point










Remarks

None

T44-0304 Simulating an incoming Call over a BICC Trunk with Callee in the Local office through the CSIS

Objective

To verify that an incoming call over a ISUP trunk is successful through the CSIS

Network diagram

Topology E





Page 17 of 24

Precondition

l A is a KPN subscriber register in Huawei MSC 1.

l B is a KPN subscriber register in Huawei MSC 2.




A is alerting.



3. Simulate an incoming call over a BICC trunk and configure the following parameters: Set Inspection type to Call simulator, and Analog type to BICC Trunk; input Incoming TG.Name






4. After the call is connected, the callee hangs up.


Check Point










Remarks

None



huawei kpn project test specification for digital telephony testing_v0_93

Documents