huawei kpn project test specification for charge audit function _v0_9

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 Charge Audit function Issue V0.9

Date 2007-08-02


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 Charge Audit function About This Document


i

About This Document

Author Prepared by Alex Su Date 2007-8-2

Reviewed by Date

Approved by Date

Purpose This manual is written based on 3GPP 23.018, 24.008 and 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.

& Special Comments:

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

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 release 2007-8-2 Alex Su

Project Document Test Specification for Handover in GSM System and UMTS System Table of Contents


Page i of 26

Table of Contents

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

1 Overview..............................................................................................................................1 1.1 Test Topology In Stage 1...........................................................................................1 1.2 Test Equipments........................................................................................................3

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

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

T45 Charge Audit function.......................................................................................................7 T45-01 O&M....................................................................................................................7 T45-02 Audit fuction testing ...........................................................................................12

Project Document Test Specification for Charge Audit function Part I Overview


Page 1 of 26

Part I Overview

1 Overview

In the Huawei-KPN project, the test of Charge Audit function aims for the validation of whether the Huawei MSC can support Charge Audit function.

1.1 Test Topology In Stage 1

Topology A




Page 2 of 26

Topology B


Topology C


Topology D




Page 3 of 26

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

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



Page 4 of 26

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

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



Page 5 of 26

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.


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.




Page 6 of 26

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 Charge Audit function Part II Operation Guide


Page 7 of 26

Part II Operation Guide

T45 Charge Audit function

T45-01 O&M

T45-0101 Create,modify and delete the measurement entity for Mobile Originating call

Objective

To verify the Huawei CN can handle the measurement of Charging Audit function.

Acceptance Criteria

l The specific measurement entity can be handle successfully.

Network diagram

Test Topology A

Precondition

l The operator log on MSOFTX3000 Performance Management System successfully.

Test procedure Expected results

1. Create the measurement entity for Mobile Originating call.

l The measurement entity is created successfully.

2. Modify the measurement entity for Mobile Originating call.

l The measurement entity is modified successfully.

3. Delete the measurement entity for Mobile Originating call.

l The measurement entity is deleted successfully.

Remarks

T45-0102 Create,modify and delete the measurement entity for CAMEL indicated call

Objective


Acceptance Criteria


Network diagram

Test Topology A

Precondition




Page 8 of 26


1. Create the measurement entity for CAMEL indicated call.


2. Modify the measurement entity for CAMEL indicated call.


3. Delete the measurement entity for CAMEL indicated call.


Remarks

T45-0103 Creat,modify and delete the measurement entity for CAMEL terminated call

Objective


Acceptance Criteria


Network diagram

Test Topology A

Precondition



1. Create the measurement entity for CAMEL terminated call.


2. Modify the measurement entity for CAMEL terminated call.


3. Delete the measurement entity for CAMEL terminated call.


Remarks

T45-0104 Creat,modify and delete the measurement entity for Terminating Service Call.

Objective


Acceptance Criteria


Network diagram



Page 9 of 26

Test Topology A

Precondition



1. Create the measurement entity for Terminating Service Call.


2. Modify the measurement entity for Terminating Service Call.


3. Delete the measurement entity for Terminating Service Call.


Remarks

T45-0105 Creat,modify and delete the measurement entity for GateWay outgoing call

Objective


Acceptance Criteria


Network diagram

Test Topology A

Precondition



1. Create the measurement entity for GateWay outgoing call.


2. Modify the measurement entity for GateWay outgoing call.


3. Delete the measurement entity for GateWay outgoing call.


Remarks

T45-0106 Creat,modify and delete the measurement entity for GateWay incoming call

Objective




Page 10 of 26

Acceptance Criteria


Network diagram

Test Topology A

Precondition



1. Create the measurement entity for GateWay incoming call.


2. Modify the measurement entity for GateWay incoming call.


3. Delete the measurement entity for GateWay incoming call.


Remarks

T45-0107 Creat,modify and delete the measurement entity for Early Call forwarding call

Objective


Acceptance Criteria


Network diagram

Test Topology A

Precondition



1. Create the measurement entity for Early Call forwarding call.


2. Modify the measurement entity for Early Call forwarding call.


3. Delete the measurement entity for Early Call forwarding call.


Remarks

T45-0108 Creat,modify and delete the measurement entity for Late Call forwarding Call



Page 11 of 26

Objective


Acceptance Criteria


Network diagram

Test Topology A

Precondition



1. Create the measurement entity for Late Call forwarding Call.


2. Modify the measurement entity for Late Call forwarding Call.


3. Delete the measurement entity for Late Call forwarding Call.


Remarks

T45-0109 Creat,modify and delete the measurement entity for Roaming call

Objective


Acceptance Criteria


Network diagram

Test Topology A

Precondition



1. Create the measurement entity for Roaming call.


2. Modify the measurement entity for Roaming call.


3. Delete the measurement entity for Roaming call.


Remarks



Page 12 of 26

T45-0110 Creat,modify and delete the measurement entity for non-call service

Objective


Acceptance Criteria


Network diagram

Test Topology A

Precondition



1. Create the measurement entity for non-call service.


2. Modify the measurement entity for non-call service.


3. Delete the measurement entity for non-call service.


Remarks

T45-02 Audit fuction testing

T45-0201 Charge audit for Mobile Originating call of 2G subscriber

Objective

To verify the Charging Audit function of Huawei CN is normally.

Acceptance Criteria

l The specific measured data of Charging Audit function is correct.

Network diagram

Test Topology A

Precondition

l The operator log on MSOFTX3000 Performance Management System and the measurement entity for Mobile Originating call has been created successfully.

l A and B are all KPN 2G subscriber and registered in Huawei MSC.




Page 13 of 26

1. Executed command MOD GBILLCTRL to generate MOC bill .

2. Originate a call from A to B within a Measurement Time Period.

l The call is connected successfully.

l The result of measurement is: Answer Times is 1, Answer Charging Times is 1, Answer No Charging Times is 0, Tickets Count is 1, Abnormal No Charging Rate is 0.

3. Executed command MOD GBILLCTRL to not generate MOC bill.




Remarks

T45-0202 Charge audit for CAMEL indicated call of IN-MO and IN-MF

Objective


Acceptance Criteria


Network diagram

Test Topology A

Precondition

l The operator log on MSOFTX3000 Performance Management System and the measurement entity for Camel MOC Charging Audit Measurement has been created successfully.

l A、B and C are all KPN 2G IN subscriber and registered in Huawei MSC.and C Registered CFNRY in HLR




Page 14 of 26

1. Executed command MOD GBILLCTRL to generate AI_MOC bill .




3. Executed command MOD GBILLCTRL to not generate AI_MOC bill.




5. Executed command MOD GBILLCTRL to not generate AI_CFW bill.

6. Originate a call from A to B but B no answer forward to C



7. Executed command MOD GBILLCTRL to not generate AI_CFW bill.

8. Originate a call from A to B but B no answer forward to C



Remarks

T45-0203 Charge audit for CAMEL terminated call of IN-MT

Objective


Acceptance Criteria


Network diagram

Test Topology A

Precondition

l The operator log on MSOFTX3000 Performance Management System and the measurement entity for TCAMEL Charging Audit Measurement has been created successfully.

l A and B are all KPN 2G IN subscriber and registered in Huawei MSC.




Page 15 of 26

1. Executed command MOD GBILLCTRL to generate AI_MTC bill .




3. Executed command MOD GBILLCTRL to not generate AI_MTC bill.




Remarks

T45-0204 Charge audit for terminating service call.

Objective


Acceptance Criteria


Network diagram

Test Topology A

Precondition

l The operator log on MSOFTX3000 Performance Management System and the measurement entity for MTC Charging Audit Measurement has been created successfully.



1. Executed command MOD GBILLCTRL to generate MTC bill .




3. Executed command MOD GBILLCTRL to not generate MTC bill.




Remarks

T45-0205 Charge audit for GateWay outgoing call of the call from MSC Server to VMS



Page 16 of 26

Objective


Acceptance Criteria


Network diagram

Test Topology A

Precondition

l The operator log on MSOFTX3000 Performance Management System and the measurement entity for GWO Charging Audit Measurement has been created successfully.

l A is KPN 2G subscriber and registered in Huawei MSC,B is a PSTN subscriber


1. Executed command MOD GBILLCTRL to generate GWO bill.




3. Executed command MOD GBILLCTRL to not generate GWO bill.




Remarks

T45-0206 Charge audit for GateWay incoming call of the call from OLO and VMS to MSC Server

Objective


Acceptance Criteria


Network diagram

Test Topology A

Precondition

l The operator log on MSOFTX3000 Performance Management System and the measurement entity for GWI Charging Audit Measurement has been created successfully.

l B is KPN 2G subscriber and registered in Huawei MSC,A is a PSTN subscriber




Page 17 of 26

1. Executed command MOD GBILLCTRL to generate GWI bill .




3. Executed command MOD GBILLCTRL to not generate GWI bill.




Remarks

T45-0207 Charge audit for Early Call forwarding call of the call from PSTN and MS

Objective


Acceptance Criteria


Network diagram

Test Topology A

Precondition

l The operator log on MSOFTX3000 Performance Management System and the measurement entity for GMSC CFW Charging Audit Measurement has been created successfully.

l A 、B and C are all KPN 2G subscriber and registered in Huawei MSC,B Registered CFU in HLR.


1. Executed command MOD GBILLCTRL to generate CFW bill .

2. Originate a call from A to B forward to C within a Measurement Time Period.



3. Executed command MOD GBILLCTRL to not generate CFW bill.

4. Originate a call from A to B forward to C within a Measurement Time Period.



Remarks

T45-0208 Charge audit for Late Call forwarding Call



Page 18 of 26

Objective


Acceptance Criteria


Network diagram

Test Topology A

Precondition

l The operator log on MSOFTX3000 Performance Management System and the measurement entity for VMSC CFW Charging Audit Measurement has been created successfully successfully.

l A 、B and C are all KPN 2G subscriber and registered in Huawei MSC,B Registered CFNRY in HLR.


1. Executed command MOD GBILLCTRL to generate CFW bill .

2. Originate a call from A to B but B not answer and forward to C



3. Executed command MOD GBILLCTRL to not generate CFW bill.

4. Originate a call from A to B but B not answer and forward to C



Remarks

T45-0209 Charge audit for Roaming call

Objective


Acceptance Criteria


Network diagram

Test Topology A

Precondition

l The operator log on MSOFTX3000 Performance Management System and the measurement entity for Mobile Originating call has been created successfully.

l A and B are 2G inbound subscribers who are roaming to KPN and registered in Huawei MSC.




Page 19 of 26

1. Executed command MOD GBILLCTRL to generate ROAM bill.



l The result of measurement is: Answer Times is 1, Answer Charging Times is 1, Answer No Charging Times is 0, Tickets Count is 1, and Abnormal No Charging Rate is 0.

Remarks

T45-0210 Charge audit for non-call service,including SMS,SS action and USSD

Objective


Acceptance Criteria


Network diagram

Test Topology A

Precondition

l The operator log on MSOFTX3000 Performance Management System and the measurement entity for None Call Charging Audit Measurement has been created successfully.



1. Executed command MOD GBILLCTRL to generate SS_ACT bill .

2. Input *#21*11# from mobile telephone

to query the service of cfu.

l The result of measurement is: SS Action Charging Times is 1, SS Action No Charging Times is 0, SS Action Successful Times is 1,

3. Executed command MOD GBILLCTRL to generate SS_ACT bill .

4. A originate USSD successfully.

l The result of measurement is: SS Action Charging Times is 1, SS Action No Charging Times is 0, SS Action Successful Times is 1,

5. Executed command MOD GBILLCTRL to generate MO_SMS and MT_SMS bill .

6. A send a short message to B

l The result of measurement is: SMS MO Charging Times is 1, SMS MO No Charging Times is 0, SMS MO Successful Times is 1, SMS MT Charging Times is 1, SMS MT No Charging Times is 0, SMS MT Successful Times is 1.

Remarks

T45-0211 The number of B-number answer but no CDR exceed the designed threshold in a designed period

Objective



Page 20 of 26


Acceptance Criteria


Network diagram

Test Topology A

Precondition

l The operator log on MSOFTX3000 Performance Management System and the measurement entity for Mobile Originating call has been created successfully and it’s Upper threshold is set 2%

l A and B are KPN 2G subscribers and registered in Huawei MSC.


1. Executed command MOD GBILLCTRL to generate MOC bill.

2. Originate a call from A to B within a Measurement Time Period. MOC Abnormal No Charging Rate is 3%

l Have event alarm report, in alarm, Abnormal No Charging Rate is 3%.

Remarks

huawei kpn project test specification for charge audit function _v0_9

Documents

specific measured

generate aimtc

generate aimoc

generate ssact

generate gwi

generate aicfw

generate mtc

generate cfw