MSOFTX3000

Function Acceptance MSOFTX3000

Test

Specification

for

Table of Contents

Table of Contents

Table of Contents.........................................................................................................................i Operation Guide......................................................................................................................... 1 T01 Port Maintenance Test.......................................................................................................1 T01-01Port Maintenance Test..........................................................................................1 T01-0101 Query Ethernet Port Status .....................................................................................1

T02 User Authority Management..............................................................................................2 T02-01 User Authority Management.................................................................................2 T02-0101 Command Group Management ...............................................................................2 T02-0102 Operator Authority Management...............................................................................4 T02-0103 Operator Login/Logout..............................................................................................5 T02-0104 Listing operator information.......................................................................................5 T02-0105 Listing the frame information.....................................................................................6 T02-0106 Display the FAN information......................................................................................6 T02-0107 Display the PDB information.....................................................................................6

T03 Alarm Management............................................................................................................7 T03-01 Alarm Management..............................................................................................7 T03-0101 Browse Current Alarm...............................................................................................7 T03-0102 Query Alarm Log.......................................................................................................8 T03-0103 Query Alarm Details..................................................................................................8

T03-02 Manually Forced Recover....................................................................................8 T03-0201 Manually Forced Recover.........................................................................................8

T03-03 Alarm Collection...................................................................................................9 T03-0301 Alarm Collection........................................................................................................9

T03-04 Typical Alarm Items............................................................................................10 T03-0401 BOARD FAULT.......................................................................................................10

i


Test

Specification

for

Table of Contents

T03-0403 ISUP/TUP ALARM TK NO7 MT BLOCK.................................................................11 T03-0404 SWAP STANDBY TO ACTIVE................................................................................11

T04 Performance Measurement Task Management...............................................................12 T04-01 Performance Measurement Task Management.................................................12 T04-0101Creating traffic measurement task...........................................................................12 T04-0102Deleting traffic measurement task............................................................................13 T04-0103Modifying traffic measurement task..........................................................................13 T04-0104Activating/Deactivating traffic measurement task.....................................................14 T04-0105Querying traffic measurement task..........................................................................15 T04-0106Querying traffic measurement result........................................................................15

T05 Tracing Management.......................................................................................................16 T05-01 Tracing Management.........................................................................................16 T05-0101 Per interface............................................................................................................16 T05-0102 Per subscriber.........................................................................................................17

T06 Maintanmance Functions.................................................................................................17 T06-01Log Management................................................................................................17 T06-0201Listing operation log information..............................................................................17

T06-02Version listing......................................................................................................18 T06-0301Query the version of MSOFTX3000.........................................................................18

T06-03Shelf Management..............................................................................................18 T06-0401Listing the shelf information......................................................................................18

T06-04 Board Management............................................................................................19 T06-0401 List the configuration of an existing board...............................................................19 T06-0402 Switching over board...............................................................................................19 T06-0403 Reset board.............................................................................................................20

T06-05Module Management...........................................................................................21 T06-0501Querying version number of module........................................................................21 T06-0502Displaying CPU seizure rate....................................................................................21

T06-06CPU Threshold....................................................................................................22 T06-0601List CPU Threshold..................................................................................................22

ii


Test

Specification

for

Table of Contents

T06-0602Set CPU Threshold..................................................................................................22

T07 Data Backup and restoration............................................................................................24 T07-01 Data Backup and restoration..............................................................................24 T07-0101 Data Backup (MSC Server).....................................................................................24 T07-0102 Data Restore (MSC Server)....................................................................................24 T07-0103 Restart System (MSC Server).................................................................................24

T08 Mobility Management ......................................................................................................25 T08-01 Location Update.................................................................................................25 T08-0101 MS location updates with IMSI................................................................................25 T08-0102 IMSI Detach.............................................................................................................27 T08-0103 IMSI attach..............................................................................................................28 T08-0104 2G-2G Roaming of CS Subscriber..........................................................................28

T08-02 Authentication.....................................................................................................29 T08-0201 GSM MS authentication in BSC serving area in updating location.........................29

T08-03VLR Management...............................................................................................29 T08-0301Display of subscriber by IMSI...................................................................................29 T08-0302 Display of subscriber by MSISDN...........................................................................29 T08-0303 Display MSRN information......................................................................................30

T09Basic Services..................................................................................................................30 T09-01 Basic Calls.........................................................................................................30 T09-0101GSM subscriber calls GSM subscriber....................................................................30 T09-0102 Mobile to PSTN speech call....................................................................................35 T09-0103PSTN to Mobile speech call.....................................................................................36

T09-02 Special Service Call...........................................................................................37 T09-0201 Emergency call........................................................................................................37

T09-03 Short Message Service......................................................................................38 T09-0301Short Message Service (MO)...................................................................................38 T09-0302 Short Message Service (MT)...................................................................................43

T10 Supplementary Service....................................................................................................43 T10-01 Call Forwarding..................................................................................................43

iii


Test

Specification

for

Table of Contents

T10-0101 Call Forwarding Unconditional (CFU)......................................................................43 T10-0102 Call Forwarding on Mobile Subscriber Busy (CFB).................................................43 T10-0103 Call Forwarding on No Reply (CFNRY)...................................................................44 T10-0104 Call Forwarding on Mobile Subscriber Not Reachable (CFNRC)............................44 T10-0105 Support the control of forwarding announcement...................................................45

T10-02 Call Barring........................................................................................................46 T10-0201 Barring of All Outgoing Calls (BAOC)......................................................................46 T10-0202 Barring of Outgoing International Calls (BOIC).......................................................46 T10-0203 Barring of All Incoming Calls (BAIC).......................................................................46

T10-03 Operator Determined Barring.............................................................................47 T10-0301 ODB-BAOC, no outgoing call can be made............................................................47 T10-0302 ODB-BOIC, no outgoing international call can be made ........................................47 T10-0303 ODB-BAIC, no incoming call can be made ............................................................47 T10-0304 ODB of supplementary service activations .............................................................48

T10-04 Number Identification.........................................................................................48 T10-0401 MS (/MS) provision CLIR Permanent, CLI display always suppressed ..................48 T10-0402 MS (/MS) provision CLIP Permanent, CLI can always be shown...........................49

T10-05 Call Completion..................................................................................................50 T10-0501 Call Hold..................................................................................................................50 T10-0502 Call Waiting.............................................................................................................50

T10-06Multiparty Service................................................................................................51 T10-0601 Multiparty Service....................................................................................................51

T10-07 USSD.................................................................................................................52 T10-0701Unstructured Supplementary Service Data (MO).....................................................52

T11Handover..........................................................................................................................53 T11-01Intra-office 2G Handover.....................................................................................53 T11-0101Intra-office 2G voice call hard handover...................................................................53

T12 CAMEL Service................................................................................................................54 T12-01 PPS calls PPS....................................................................................................54

iv


Test

Specification

for

Table of Contents

T12-0101 PPS calls PPS.........................................................................................................54

T12-02 PPS calls PPS

but the callee is busy...............................................................55

，



but the callee is busy....................................................................55

，

but the callee does not answer................................................55

，


but the callee does not answer....................................................55

，

T12-04 PPS calls the PPS service number to recharge.................................................57 T12-0401 PPS calls the PPS service number to recharge......................................................57

T12-05 PPS calls the PPS service number to query the balance...................................58 T12-0501 PPS calls the PPS service number to query the balance........................................58

T12-06 PPS calls the PPS service number for operator assistance...............................59 T12-0601 PPS calls the PPS service number for operator assistance....................................59

T13 Other MSC/VLR Functions...............................................................................................60 T13-01 Announcement...................................................................................................60 T13-0101 Announcements on Calling to Unregistered Subscriber..........................................60 T13-0102 The call is failed for the called subscriber is powered off........................................60 T13-0103 The call is failed when the called subscriber is not in the service area...................61 T13-0104 The call is failed for the called subscriber is busy...................................................61

T13-02 Long Call Notification and Auto/Manual Teardown.............................................62 T13-0201Long Call Notification and Auto Teardown...............................................................62

T14 Additional dialing table.....................................................................................................62 T15 Other Test........................................................................................................................69

v


Test

Specification

for

Operation Guide

Operation Guide T01 Port Maintenance Test T01-01Port Maintenance Test T01-0101 Query Ethernet Port Status

Objective Test networking diagram

To check whether the FE port status can be queried normally. None

Preset condition

1.The hardware configuration and cable connections are correct. BAM works normally. 2.Data is configured according to actual network conditions. 3.The communication between the BAM and the client is normal, and the client has the authority to execute relevant commands.

Test procedure

Enter command DSP PORT together with the frame number and slot number, and select “FE” for the “Port Type”.

Expected result

The status of FE port is returned.

Test Description

None

1


Test

Specification

for

Operation Guide

T02 User Authority Management T02-01 User Authority Management T02-0101 Command Group Management

Objective

To verify the function of adding and deleting command contained in command group

Serial Number of Test Networking Diagram

None

Preset Conditions

You have logged in to the BAM from the client successfully.

Test Procedures

1.

You have the right for carrying out the corresponding command.

1.

Open Menu “Authority->Command Group->Set Command Group Name”, on the POP_MENU “Set Command Group Name”, input the Command Group Name, and click OK.

2.

Open Menu “A uthority->Command Group->Modify Command Item”, on the POP_MENU, select correct Command Group, and click the command that will open to the user group, and then click OK.

3.

Open Menu “Authority->Accounts->ADD”, on the POP_MENU, input the right parameter for this user, especially specify “custom” parameter for Operator Definition, and in the right window select the command group which has setup, and then click OK.

4.

Open Menu “Authority->Accounts->Delete”, on the POP_MENU, select the right account you want to delete and click Delete. On the confirm window click

Expected Results

5.

YES.

1.

In step 3: the prompt information “Added successfully. Do you want to continue to add?” will be displayed.

2.

In step 4: the prompt information “ Delete Operator**?” will be displayed.

2


Test Description

Test

Specification

for

None

3

Operation Guide


Test

Specification

for

Operation Guide

T02-0102 Operator Authority Management

Objective Serial Number of

To verify the function of adding and deleting an operator None

Test Networking Diagram Preset Conditions

1.

The BAM functions normally.

The client works normally. The communication between the client and the BAM is normal. Log in to the BAM with the user name “Admin”. Test Procedures

1.

Add an operator by clicking [Authority /Accounts/Add] in the client interface.

Click [Authority /Accounts/Modify] to list all the operators. Query the newly added operator. Click [Authority /Accounts/Delete] to remove this operator. Query this operator again. Expected Results

1.

A prompt indicating successful addition of the operator is displayed.

The newly added operator is listed. A prompt indicating successful deletion of the operator is displayed. There is no record for the removed operator. Test Description

4


Test

Specification

for

Operation Guide

T02-0103 Operator Login/Logout

Objective Serial Number of Test Networking Diagram Preset Conditions Test Procedures

Test login/logout function None

Msoftx3000 (or BAM) is in normal operation. Open the Msoftx3000 O&M system and a [Login] dialog box will pop up. Input the operator name, password and the corresponding office; click to log in. Select the menu item [System/Logout], and a prompt box will pop up. Click to logout.

Expected Results

Expected result after test procedure 2: If the operator name, password and office are all correct, the login will be successful. In this case, the information such as "Connection normal, IP: 192.168.115.114" will be displayed in the status bar, and the command with the corresponding authority can be executed through the command window. Otherwise, a dialog box with prompts will pop up. Expected result after test procedure 3: All Windows will be closed after logout except main window.

Test Description

The IP address might be di fferent according to different situations.

T02-0104 Listing operator information

Objective

To verify the function of listing operator information


None

Preset Conditions

1.

Both the BAM and the client function normally.

You have the right for carrying out the corresponding command. Test Procedures

Carry out the command LST OP. By adopting the default setting, you can view the brief information of all operators. To query the details of a certain operator, type the operator name.

Expected Results

If default setting is adopted, the brief information of all operators will be displayed, including operator name and status. If an operator name is inputted and it exists, the details of the operator will be displayed. If the inputted operator name does not exist, a

5


Test

Specification

for

Operation Guide

prompt information “Corresponding results not found” will be given. Test Description

The returned result for login as an administrator is different from that for login as an ordinary user.

T02-0105 Listing the frame information

Objective

To verify the function of listing the frame information

Serial Number of Test Networking Diagram Preset Conditions

None

1.


The client works normally. The communication between the client and the BAM is normal. You have the right for carrying out the corresponding command. Test Procedures

Carry out LST FRM on the client, specify the shelf number, then press to execute the command

Expected Results

The information of specified frame will be shown

Test Description T02-0106 Display the FAN information

Objective

To verify the function of displaying the FAN information.


None

1.


The client works normally. The communication between the client and the BAM is normal. You have the right for carrying out the corresponding command. Test Procedures

Carry out DSP FAN on the client, specify the shelf number, then press to execute the command

Expected Results

The fan information of specified frame will be shown

TestDescription

None

T02-0107 Display the PDB information.


To verify the function of displaying the PDB information. None

6


Test

Specification

for

Operation Guide


1.


2.

The client works normally.

3. The communication between the client and the BAM is normal. 4. The user has the right for carrying out the corresponding command. Test Procedures

Carry out DSP PDB on the client, specify the shelf number, then press to execute the command

Expected Results

The PDB information of specified frame will be shown

TestDescription

None

T03 Alarm Management T03-01 Alarm Management T03-0101 Browse Current Alarm

Objective Serial Number of Test Networking Diagram Preset Conditions

Test Procedures

Test the function to browse current alarms. None

Msoftx3000 Alarm Management System has been logged in properly. Select the menu [Browse/Fault Alarm]. Select the menu [Browse/Event Alarm].

Expected Results

Test procedure 1: The [Fault Browse] window pops up, displaying current fault alarms not cleared. Test procedure 2: The newly reported fault alarms can be displayed in the [Fault Browse] window in real time; also the newly reported event alarms can be displayed in the [event Browse] window in real time.

Test Description

Relevant MML command: LST ALMAF. This function is to browse the alarms not cleared.

7


Test

Specification

for

Operation Guide

T03-0102 Query Alarm Log


Test the function to query alarm logs. None


Msoftx3000 Alarm Management System has been logged in properly.

Test Procedures

Select [Query/Query Alarm Log]. Set the query condition in the pop-up [Query Alarm Log] dialog box, and then click .

Expected Results

The pop-up [Query Alarm Log] dialog box will display the alarm logs in accordance with the query condition.

Test Description

Relevant MML command: LST ALMLOG.

T03-0103 Query Alarm Details

Objective Serial Number of Test Networking Diagram

Test the function to query alarm details None

Preset Conditions


Test Procedures

Double click an alarm record in the [Fault Browse], [Event Browse] or [Query Alarm Log] window, an [Alarm Details] dialog box will pop up.

Expected Results

The [Alarm Details] window will display the details of the alarm such as the alarm ID, name and locating information.

Test Description

Relevant MML command: NONE.

T03-02 Manually Forced Recover T03-0201 Manually Forced Recover


Test the function of clearing alarm manually. None

Msoftx3000 Alarm Management System has been logged in to

8


Test

Specification

for

Operation Guide

properly. Test Procedure

Generate an alarm. For example, generate Alarm 2033 by pull out the UPWR Board from NO.0 FRAME. List fault alarms (using the command LST ALMAF) to get one or more alarms not cleared. Use the command RMV ALMFLT to clear an alarm just queried. Use the command LST ALMLOG to query the alarms just queried.

Expected Results

In step 4, the system returns the alarm is not found. The color of this alarm will change to green color via red color.

Test Description

None

T03-03 Alarm Collection T03-0301 Alarm Collection


Test Procedure

Test the function of Alarm collection. None

Msoftx3000 Alarm Management System has been logged in properly. Select [Query/Query Alarm Log]. Set the query condition in the pop-up [Query Alarm Log] dialog box, and click .

Expected Results

Test Description

The pop-up [Query Alarm Log] dialog box displays the history alarms in accordance with the query conditions. If there are no such alarms, the system will give a corresponding prompt. Relevant MML command: LST ALMLOG.

9


Test

Specification

for

Operation Guide

T03-04 Typical Alarm Items T03-0401 BOARD FAULT


Test the alarm of Board fault. None

Preset Conditions


Test Procedure

Pull out the UPWR Board from the slot. Check the Alarm Management System whether there is the ALARM: UPWR Board fault. 1.

Expected Results

Insert this board into the correct slot.

There is new raised alarm UPWR Board fault in Alarm Management System. 1.

Test Description

After insert this board, these alarms will recover.

None

10


Test

Specification

for

Operation Guide

T03-0403 ISUP/TUP ALARM TK NO7 MT BLOCK

Objective


Test the alarm of The local TUP/ISUP blocks the opposite single circuit for maintenance None

Preset Conditions

Msoftx3000 Alarm Management System has been logged in properly. Msoftx3000 Operation and Maintenance System has been logged in properly.

Test Procedure

1.

Enter BLK N7TKC the correct module number, circuit type, the direction, the start circuit number and the end circuit number, and press [F9].

2.

An alarm ISUP/TUP ALARM TK NO7 MT BLOCK will appear in event alarm window.

3.

Enter UBL N7TKC the correct module number, circuit type, the direction, the start circuit number and the end circuit number, and press [F9].

Expected Results

There is new raised alarm ISUP/TUP ALARM TK NO7 MT BLOCK in Alarm Management System. 1.

Test Description

After unblock these trunk circuits, these alarms will recover from alarm window.

None

T03-0404 SWAP STANDBY TO ACTIVE


Test the alarm of Swap Standby board to Active board None

Preset Conditions

Msoftx3000 Alarm Management System has been logged in properly. Msoftx3000 Operation and Maintenance System has been logged in properly.

Test Procedure

Expected Results

Enter SWP BRD with the correct frame number, slot number, and the position number, then press [F9]. 1.

An alarm Swap Standby to Active will appear in fault alarm window, and a

11


Test

Specification

for

Operation Guide

series of program load alarm will appear in the event alarm window.

Test Description

2.

This board cans normally startup.

3.

After startup, this board becomes the standby board.

4.

The standby Board will become the Primary Board.

None

T04 Performance Measurement Task Management T04-01 Performance Measurement Task Management T04-0101Creating traffic measurement task

Objective

To verify the function of creating traffic measurement task


1.

The system is in normal operation.

2.

The client software runs normally.

3.

You have the right for executing traffic measurement management commands.

Test Procedures

1.

Select [Task/Create Task] in the traffic measurement system interface on the client. In the [Create a New Task] dialog box that pops up, specify the name of the measurement task to be created, and then select measurement functional set, measurement unit, measurement entities, measurement objects, measurement time information (including measurement duration, measurement time segments and measurement period, among which some are optional). After the setting, click .

2.

Select [Task list] in the navigation tree to check whether the newly created task exists. If so, double click the task or right click on the task and then select [Detailed Task Info] on the shortcut menu. In the [Task Information] window that appears, check the basic information, entity information, object information to see whether they are the same as the previous settings.

12


Test

3.

Specification

for

Operation Guide

After a whole measurement period, select the task in the [ Task list] column, and then click the menu [Task/Query Task Result], or right click on the task and then select [Query Task Result] on the shortcut menu. Select the time range, and then click .

Expected Results

1.

A prompt indicating successful creation is displayed.

2.

The newly created task exists, and the basic information, entity information and object information of the task are consistent with the previous settings.

3.

The measurement result list is displayed.

Test Description T04-0102Deleting traffic measurement task

Objective

To verify the function of deleting traffic measurement task


1.


2.


3.


4. Test Procedures

A traffic measurement task has been created successfully.

In the [Task list] column of the navigation tree, select the task to be deleted, and then click the menu [Task/Delete Task] or right click on the task and then select [Delete Task] on the shortcut menu. Finally, click for confirmation.

Expected Results

Test Description

1.

A prompt indicating successful deletion is displayed.

2.

Check the [Task list] column to confirm that the task has been deleted.

1.

After the task is deleted, its result list will be deleted too.

2.

You can find the MML commands for all the traffic measurement operations under the [Traffic Statistics] node of the command navigation tree in the maintenance management system at the client.

T04-0103Modifying traffic measurement task

13


Objective

Test

Specification

for

Operation Guide

To verify the function of modifying traffic measurement task


1.


2.


3.


Test Procedures

4.


1.

In the [Task list] column of the navigation tree, select the task to be modified, and then click the operation item corresponding to the task property to be modified on the [Task] menu or on the shortcut menu. Finally, modify the task property in the dialog box that pops up.

2.

You can modify such properties as task name, output mode, output

1.

A prompt indicating successful modification is displayed.

2.

Check the c ontents in the [T ask Information] window to se e whether the

device, and measurement unit and time information. Expected Results

specified property has been modified. Test Description

1.

You can find the MML commands for all the traffic measurement operations under the [Traffic Statistics] node of the command navigation tree in the maintenance management system at the client.

T04-0104Activating/Deactivating traffic measurement task

Objective

To verify the function of changing the state of traffic measurement task


1.


2.


3.


Test Procedures

4.

An activated traffic measurement task has been created.

1.

In the [Task list] column of the navigation tree, select the task to be deactivated, and then click the menu [Task/Deactivate Task] or right

14


Test

Specification

for

Operation Guide

click on the task and select [Deactivate Task] to deactivate the task. 2.

In the [Task list] column of the navigation tree, select the task deactivated just now. Then select [Task/Activate Task] or right click on the task and select [Activate Task] to activate the task.

Expected Results

1.

A prompt indicating the task status change from “activated” to “deactivated” is displayed. And in the navigate tree the icon of the task also changed to deactivated.

2.

A prompt indicating the task status change from “deactivated” to “activated” is displayed. And in the navigate tree the icon of the task also changed to activated.

Test Description

You can find the MML commands for all the traffic measurement operations under the [Traffic Statistics] node of the command navigation tree in the maintenance management system at the c lient.

T04-0105Querying traffic measurement task

Objective

To verify the function of querying traffic measurement task


1.


2.


3.


Test Procedures

Expected Results Test Description

In the [Task list] column of the navigation tree, select [Task/Query Task] or right click to select [Query Task] on the shortcut menu, and then select a query condition in the [Query] dialog box that pops up. Finally, click . A list of the tasks complying with the specified condition will be displayed. You can find the MML commands for all the traffic measurement operations under the [Traffic Statistics] node of the command navigation tree in the maintenance management system at the c lient.

T04-0106Querying traffic measurement result

Objective

To verify the function of querying traffic measurement result


1.


15


Test

Specification

for

Operation Guide

2.


3.


4.


Test Procedures

In the [Task list] column, select the task to be queried, and then click the menu [Task/Query Task Result] or right click on the task and then select [Query Task Result] on the shortcut menu. Next, set s uch parameters as time range in the [Query Task Result] dialog box that pops up. After the setting, click .

Expected Results

If there are measurement results for the task, they will be listed in the “Task Result” window; otherwise, the prompt for no result data generated within the specified time segment will be given.

Test Description

You can find the MML commands for all the traffic measurement operations under the [Traffic Statistics] node of the command navigation tree in the maintenance management system at the c lient.

T05 Tracing Management T05-01 Tracing Management T05-0101 Per interface

Objective

To verify the function of tracing external interfaces of the system

Serial Number of Test Networking Diagram Preset Conditions Test Procedures

Expected Results

The system operates normally and supports mobile originated call 1.

Click [Maintenance Navigator / Trace Management /Interface T race Task] and register interface trace tasks including C interface, D interface, E interface, A interface and H.248 interface.

2.

Make a 2G mobile originated call.

The trace tasks are registered successfully. Respective trace windows display all messages transmitted and received through the interface in sequence.

16


Test

Specification

for

Operation Guide

The traced messages are interpreted correctly. Test Description T05-0102 Per subscriber

Objective

To verify the function of tracing interface messages based on subscriber


Test Procedures

Expected Results

1.

A subscriber successfully completes a location update at the local office and is idle now.

2.

The system operates normally and sup ports mobile srcinated call

1.

Click [Maintenance Navigator/Trace Management/User Trace Task/User Interface], type the MSISDN or IMSI of the subscriber to be traced, and select the interface to be traced.

2.

Make a mobile originated call

1.

The trace tasks are registered successfully.

2.

The trace window displays all me ssages transmitted and received through the interface in sequence.

3.

The traced messages are interpreted correctly.

Test Description

T06 Maintanmance Functions T06-01Log Management T06-0201Listing operation log information


To verify the function of listing operation log information None

1. You have logged in to the BAM from the client successfully.

You have the right for carrying out the corresponding command. Several commands have been carried out. Test Procedures

Carry out the command LST LOG. By adopting the default setting, you can view the log information of all commands carried out that

17


Test

Specification

for

Operation Guide

day. To query the command log information by a certain condition, type the corresponding parameter. Expected Results

If default setting is adopted, the log information of all the commands carried out that day will be displayed. If a certain condition is inputted, the log information of the commands complying with the condition will be displayed. The displayed result is consistent with the actual command execution.

Test Description

T06-02Version listing T06-0301Query the version of MSOFTX3000

Objective

Query the version of MSOFTX3000


None

Preset Conditions

The client works normally

Test Procedures

Click [Help/About…] to open about dialog.

Expected Results

The version of MSOFTX3000 will be displayed

TestDescription

None

T06-03Shelf Management T06-0401Listing the shelf information

Objective

To verify the function of Listing the shelf information


None

Preset Conditions

1.The BAM functions normally. 2. The client works normally. 3. The communication between the client and the BAM is normal. 4. You have the right for carrying out the correstponding command.

Test Procedures

Carry out LST SHF on the client, specify the shelf number, then press to execute the command

18


Expected Results

Test

Specification

for

Operation Guide

The information of specified shelf will be shown .if the default value of "SN" is used. The information of all available shelves will be shown.

Test Description

None

T06-04 Board Management T06-0401 List the configuration of an existing board.

Objective

To verify the function of listing the configuration of an existing board


None

Preset Conditions

1.


2.


3. The communication between the client and the BAM is normal. 4. The user have the right for carrying out the correstponding command. Test Procedures

Carry out LST BRD on the client, Input the frame number and the slot number, Specify the location and the board type, then press to execute the command.

Expected Results

The information of specified board will be shown

TestDescription

None

T06-0402 Switching over board

Objective

To verify the function of switching over board


None

Preset Conditions

1.


2.


3. The communication between the client and the BAM is normal. 4. The user have the right for carrying out the correstponding command. 5.

The board to be tested supports switchover function

19


Test Procedures

Expected Results

Test

Specification

for

Operation Guide

1. Select the [Maintenance] tab from the navigation tree at the client and then double click a subrack node under [Device Management]. Select a pair of active & standby boards. Right click on the active board and then click [Swap Board] on the menu. Finally, click . 2.

Check the board status during switchover.

3.

Check switchover alarms at the alarm console.

1.

The operations are done successfully.

2. The srcinal standby board serves as the active one. When the srcinal active board is being reset, its status becomes “Fault”. Finally, the srcinal active board switches over to the standby board. 3. A board fault alarm (fault alarm) and a board switchover alarm (event alarm) are generated at the alarm console. Test Description

None

T06-0403 Reset board

Objective

To verify multiple methods of restarting the system


None

Preset Conditions

1.


2.


3. The communication between the client and the BAM is normal. 4. The user have the right for carrying out the correstponding command. Test Procedures

1. Press the reset button on the board. 2. Alternatively, you can right-click on the board on the GUI maintenance interface, and select “Reset board” from the shortcut menu. 3. Carry out RST BRD on the client, and specify the board position. 4. Observe alarms at the alarm console.

Expected Results

1.The run indicator on the board stops the slow flashing (in normal state). In a few seconds, the indicator start flashing quickly, and the board starts loading. 2.Board color on the GUI maintenance is red.

20


Test

Specification

for

Operation Guide

3.The system prompts “Operation succeeded”. 4.On the alarm console, first a fault alarm of the resetted board is generated, then the board loading process alarm is generated, and finally, the board fault recovery alarm is generated. Test Description

None

T06-05Module Management T06-0501Querying version number of module

Objective

To verify the function of listing module version number


None

Preset Conditions

1.


2.


3. The communication between the client and the BAM is normal. 4. You have the right for carrying out the corresponding command. Test Procedures

Carry out the command DSP EXVER. To list the version numbers of all modules, adopt the default setting. To list the version number of a certain module, specify the module number.

Expected Results

The version number(s) of the specified module(s) will be displayed.

Test Description

After the BAM command timer times out, only the version numbers of the modules received will be displayed.

T06-0502Displaying CPU seizure rate

Objective

To verify the function of displaying CPU seizure rate


None

Preset Conditions

1. 2.

The BAM functions normally. The client works normally.

3. The communication between the client and the BAM is normal.

21


Test

Specification

for

Operation Guide

4. You have the right for carrying out the corresponding command. Test Procedures

Carry out the command DSP CPUR. You can query the CPU seizure rate either by module number or by position. For the former mode, to list the CPU seizure rates of all modules, adopt the default setting; to list the CPU seizure rate of a certain module, specify the module number. For the latter mode, you must specify the frame number and slot number.

Expected Results

The CPU seizure rate(s) of the specified module(s) will be displayed.

Test Description

After the BAM command timer times out, only the CPU seizure rates of the modules received will be displayed.

T06-06CPU Threshold T06-0601List CPU Threshold

Objective

To verify the function of listing CPU overload threshold and resume threshold


None

Preset Conditions

1.


2.



Carry out LST CPUTHD on the client, specify the Module number,

Expected Results

and then press to execute the command. The information of CPU overload threshold and resume threshold will be displayed

TestDescription

None

T06-0602Set CPU Threshold

Objective

To verify the function of setting CPU overload threshold and resume threshold


None

Preset Conditions

1.


22


Test

2.

Specification

for

Operation Guide



Carry out SET CPUTHD on the client, specify the Module number and input the threshold value, then press to execute the command.

Expected Results

The threshold value will be changed

TestDescription

None

23


Test

Specification

for

Operation Guide

T07 Data Backup and restoration T07-01 Data Backup and restoration T07-0101 Data Backup (MSC Server)


To verify data backup function of MSC Server. None

Preset condition

You have logged in to the BAM from the client successfully. You have the right for carrying out the corresponding command.

Test procedure

Carry out BKP DB on the client of MSOFTX3000.

Expected result

The system returns a prompt “Dump Bam database and registry table successful”, indicating that the command is successfully carried out. There is a backup file in the format of “Bam.dat” generated in the backup folder of BAM. The date in the filename is the date on which the backup operation is carried out.

Test Description

The storage path of the database backup file is specified by BackupFilePath of [Dataman] in StxBam.ini in the BAM installation folder.

T07-0102 Data Restore (MSC Server)

Objective

To verify Data restore function of MSC server

Test networking diagram

None

Preset condition

Bam and SQL server are working normally.

Test procedure

1 Choose one clean Bam database; 2 Open the SQL Enterprise Management

Restore the clear BAM database

，

3 Choose the latest BAM database, and restore it again.

Expected result

Clean BAM and latest Bam database can be restored correctly.

Test Description

None

T07-0103 Restart System (MSC Server)

Objective

To verify system restart function of MSC server

24


Test

Specification

for


None

Preset condition

The latest BAM database has been restored correctly.

Test procedure

System restart based on power down/power up procedure.

Expected result

Operation Guide

The whole System is working normally. All boards are loaded correctly and working normally.

Test Description

None

T08 Mobility Management T08-01 Location Update T08-0101 MS location updates with IMSI

Objective Test networking diagram Preset condition

To demonstrate the successful completion of location update with IMSI. None

BTS, BSC, MSC and HLR are running normally. Use MOD MAPACCFG command to cancel TMSI Relocation in the MSC. The subscription data of the MS is subscribed in the HLR, and roaming is permitted. The MS data is not in the VLR. Start subscriber tracing in MSC, specify IMSI of the MS, and select to trace A interface and C/D/F interface.

Test procedure

Power on the test MS for a IMSI Attach. Check traced messages of the MS. The signaling process is as follows: 1. At A interface, MS sends LOCATION UPDATE REQUEST message, in which the parameter “Mobile Station Identity” is the IMSI or TMSI of the MS. 2.

At C/D/F interface, MSC/VLR srcinates location update to the HLR, and HLR inserts the MS data into the VLR.

3.

At A in terface, MSC/VLR sends LOCATION UPDATE ACCEPT message to the MS.

Use DSP USRINF command to check Subscriber information in the VLR. Expected result

After the location update (imsi attach), use DSP USRINF command to query Subscriber information. The vlr should stored the user-infomaion of the MS .The MS is in “IMSI Attach” state,

25


Test

Specification

for

Operation Guide

and “Location Area Identity” and “Cell Identity” are the cell parameters when the location update is performed.

Test description

After test,The tester should use the commands MOD MAPACCFG to restore TMSI reallocation, authentication, and ciphering configuration.

26


Test

Specification

for

Operation Guide

T08-0102 IMSI Detach

Objective

Test networking diagram Preset condition

To verify that MSC can modify MS state to “IMSI Detach” after receiving IMSI Detach request of the MS. None

BTS, BSC, MSC and HLR are running normally. The subscription data of the MS is subscribed in the HLR, and roaming is permitted. Start subscriber tracing in MSC, specify IMSI of the MS, and select to trace A interface and C/D/F interface. The MS is in power-on state in the local office.

Test procedure

Use DSP USRINF command to query Subscriber information in the VLR, and the status of MS is marked “IMSI Attach”. Power off the MS, and an IMSI Detach process is activated. Use DSP USRINF command to check the MS state in the VLR.

Expected result

When MS powers off, it transmits “IMSI Detach” message to inform the network. Use DSP USRINF command to query Subscriber information in the VLR, and the status of MS is marked “IMSI Detach”.

Test description

27


Test

Specification

for

Operation Guide

T08-0103 IMSI attach

Objective Test networking

To verify IMSI attach . None

diagram Preset condition

BTS, BSC, MSC and HLR are running normally. GSM subscriber A is subscribed in the HLR. Start subscriber tracing in MSC, specify IMSI of the MS, and select to trace A interface and C/D/F interface.

Test procedure

Location of GSM subscriber A is updated. GSM subscriber A powers off the mobile phone. Use DSP USRINF command to query the subscriber information in the VLR. Subscriber A powers on the mobile phone, and IMSI attach is initiated.

Expected result

IMSI attach is performed successfully for GSM subscriber A.

Test Description T08-0104 2G-2G Roaming of CS Subscriber

Objective

Check whether roaming process from 2G MSC to 2G MSC can be managed successfully.


1.


2.

Subscription data can be found in HLR and the MS has subscribed for

basic service. 3.

MS has been attached in 2G MSC/VLR first and no relative roaming

restriction has been set. Test Procedures

Expected Results

1.

Select 2G network manually from MS and try to roam to 2G MSC/VLR.

2.

Check & verify whether the roaming is successful.

The MS has attached 2G MSC successfully and the location update procedure is correct.

Test Description

28


Test

Specification

for

Operation Guide

T08-02 Authentication T08-0201 GSM MS authentication in BSC serving area in updating location

Objective

Check whether authentication process can be managed successfully in updating location


1.


2.

Subscription data can be found in HLR and the MS has subscribed for

basic service.

Test Procedures

Expected Results

3.

MS is power off.

4.

BSC support authentication in location update.

1. Execute the MML command MOD request authentication in location update.

AUTHCFG to

2.

Power on MS.

1.

MS is attached after successful location update.

set MSC always

Test Description

T08-03VLR Management T08-0301Display of subscriber by IMSI

Objective

Check whether it is correct to display Basic Information of a Subscriber by IMSI.


Test Procedures

1.


2.

There’re some subscribers on the local network.

1. Execute the command DSP USRINF from LMT. To select the parameter IMSI for User Number Type, input a corresponding us er number in the table User Number. 2.

Expected Results

Check & verify the outputting information.

The outputting information is c orrect.

Test Description T08-0302 Display of subscriber by MSISDN

29


Objective

Test

Specification

for

Operation Guide

Check whether it is correct to display Basic Information of a Subscriber by MSISDN.


Test Procedures

1.


2.


1. Execute the command DSP USRINF from LMT. To select the parameter MSISDN for User Number Type, input a corresponding user number in the table User Number. 2.

Expected Results

Check & verify the outputting information.

The outputting information is correct.

Test Description T08-0303 Display MSRN information

Objective

Check whether it is correct to display MSRN information.


Test Procedures

Expected Results

1.


2.


1.

MS A initiates a normal call to MS B.

2.

Execute the command DSP MSRNPRE to display MSRN information.

The outputting information is correct.

Test Description

T09Basic Services T09-01 Basic Calls T09-0101GSM subscriber calls GSM subscriber

T09-010101 MS calls MS in same MSC Test networking diagram

None

Objective

To verify whether GSM subscriber can call GSM subscriber normally.

30


Preset condition

Test procedure

Expected result

1

．

2

．

3

．

1

．

2

．

3

．

4

．

5

．

1

．

2

．

Test

Specification

for

The MS A and MS B have speech call service subscription. The MS A and MS B are idle. The MS A and MS B are in the same msc.

MS A and MS B power on. MS A initiates a normal call to MS B. MS B answers, the call connected. Observe the User Interface trace and keep the call for a while. Subsequently MS B hooks on. The call is correctly setup. High quality speech transmission after successful connection.

Test description T09-010102 MS in MSC20H calls MS in other MSC Test networking diagram

None

Objective


Preset condition

1

．

2

．

3

．

1

．

2

．

3

．

4

．

5

．

1

．

2

．

Test procedure

Expected result

The MS A and MS B have speech call service subscription. The MS A and MS B are idle. The MS A is in MSC2H,The MS B is in other MSC.


Test description T09-010103 MS in other MSC calls MS in MSC20H

31

Operation Guide


Test

Specification

for


None

Objective


Preset condition

1

．

2

．

3

．

1

．

2

．

3

．

4

．

5

．

1

．

2

．

Test procedure

Expected result

The MS A and MS B have speech call service subscription. The MS A and MS B are idle. The MS A is in other MSC,The MS B is in MSC2H.


Test description T09-010104 Call from MS1 to MS2, MS2-Busy Test networking diagram

None

Objective


Preset condition

1

．

2

．

1

．

2

．

3

．

4

．

Test procedure

The MS A and MS B have speech call service subscription. The MS A is idle,The MS B is busy. MS A and MS B power on. MS A initiates a normal call to MS B. The call is disconnected.

Observe the User Interface trace and keep the station a while.

5. The MS A hooks on.

Expected result

1

The call is incorrectly setup.

．

. Test description

32

Operation Guide


Test

Specification

for

T09-010105 Call from MS1 to MS2, No answer Test networking diagram

None

Objective


Preset condition

1

．

2

．

1

．

2

．

3

．

Test procedure

The MS A and MS B have speech call service subscription. The MS A and MS B are in idle..

MS A and MS B power on. MS A initiates a normal call to MS B. MS B does not answer, the call is disconnected.

4.

Observe the User interface trace and keep the station a while.

5. MS A hooks on.

Expected result

1


．

. Test description T09-010106Call to MS2 from MS1, Detached, Announcement Test networking diagram

None

Objective


Preset condition

1

．

2

．

The MS A and MS B have speech call service subscription. The MS A is in idle.

3 . The MS B is in detached.

Test procedure

1

．

MS A power on and MS B power off.

2

．

3

．


4.

Can not connect, observe the user interface trace and keep a while. MS A hooks on.

33

Operation Guide


Expected result

1

Test

Specification

for


．

. Test description T09-010107 Call to MS2 from MS1, No Page Response Test networking diagram

None

Objective


Preset condition

1

．

2

．

1

．

2

．

3

．

Test procedure

The MS A and MS B have speech call service subscription. The MS A and MS B are in idle..

MS A and MS B power on. MS A initiates a normal call to MS B. MS B does not response page.

4. Observe the user interface trace and keep a while.

Expected result

1


．

. Test description T09-010108 MS in MSC20H calls International MS Test networking diagram

None

Objective


Preset condition

1

．

2

．

3

．

1

．

2

．

3

．

Testprocedure

The MS A and MS B have speech call service subscription. The MS A and MS B are idle. The MS B is international ms.

MS A and MS B power on. MS A initiates a normal call to MS B. MS B answers, the call connected.

34

Operation Guide


Expected result

4

．

5

．

1

．

2

．

Test

Specification

for

Operation Guide

Observe the User Interface trace and keep the call for a while. Subsequently MS B hooks on. The call is correctly setup. High quality speech transmission after successful connection.

Test description

T09-0102 Mobile to PSTN speech call

T09-010201 Call from MS to PSTN, Successful Objective

To test the Mobile to PSTN speech call


None

Preset condition

1.The MS(/MS) has speech call service subscription. 2.The called party is idle.

Test procedure

1.MS(/MS) initiates a normal call to a local PSTN subscriber. 2.PSTN subscriber answers the call, holds it on for a while, and hangs up the call.

Expected result

1.The call can be established correctly. 2.Speech transmission of high quality is achieved after successful connection.

Test description

For the Test procedure, and message process, see the test item “Mobile Originating Call (MOC) with subsequent disconnection by the called party”.

T09-010202 Call from MS to PSTN, B-sub Busy Objective



None

Preset condition

1.The MS(/MS) has speech call service subscription. 2.The called party is busy.

Test procedure

1.MS(/MS) initiates a normal call to a local PSTN subscriber. 2.PSTN subscriber response busy, holds it on for a while, and hangs up the call.

Expected result

The call can not be established correctly.

35


Test

Specification

for

Operation Guide

Test description

T09-010203 Call from MS to PSTN, No answer Objective



None

Preset condition

1.The MS(/MS) has speech call service subscription. 2.The called party is idle.

Test procedure

1.MS(/MS) initiates a normal call to a local PSTN subscriber. 2.PSTN subscriber does not answer, holds it on for a while, and hangs up the call.

Expected result

The call can not be established correctly.

Testdescription

.

T09-0103PSTN to Mobile speech call

T09-010301 Call from PSTN to MS, Successful Objective

To test the PSTN to Mobile speech call


None

Preset condition

1.MS(/MS) has registered speech call service in networks. 2.MS(/MS) is idle.

Test procedure

1.PSTN subscriber initiates a normal call to MS(/MS) B. 2.MS(/MS) B answers, and the call is connected. 3.MS(/MS) B hangs up.

4.Observe MUA3LNK signaling. Expected result

1.The call is correctly setup. 2.Speech transmission of high quality is achieved after successful connection. 3.Observe MUA3LNK signaling, the IAM message carries “called party number” and “calling party number” correctly.

Test description

For test procedure, refer to the test case “Mobile Terminating Call (MTC) with subsequent disconnection by the called party”.

T09-010302 Call from PSTN to MS, B-sub Busy Objective


36


Test

Specification

for


None

Preset condition

1.MS(/MS) has registered speech call service in networks.

Operation Guide

2.MS(/MS) is busy. Test procedure

1.PSTN subscriber initiates a normal call to MS(/MS) B. 2.MS(/MS) B response busy.. 3.MS(/MS) B hangs up. 4.Observe MUA3LNK signaling.

Expected result

The call is incorrectly setup..

Test description

T09-010303 Call from PSTN to MS, No answer Objective



None

Preset condition

1.MS(/MS) has registered speech call service in networks. 2.MS(/MS) is idle.

Test procedure

1.PSTN subscriber initiates a normal call to MS(/MS) B. 2.MS(/MS) B does not answer. 3.MS(/MS) B hangs up. 4.Observe MTP3 signaling.

Expected result

The call is incorrectly setup..

Test description

T09-02 Special Service Call T09-0201 Emergency call

Objective

This test intends to demonstrate the Emergency call (without priority handling).


None

Preset condition

The MS(/MS) should propose the possibility of establishing an SOS call

37


Test procedure

Test

Specification

for

Operation Guide

Take out the SIM from the MS(/MS), and power on the MS(/MS). Initiate an emergency call from the MS(/MS).

Expected result

Test description

1.

The emergency call can be established successfully.

2.

Observe the A-interface signaling: The Setup message indicates that it is an emergency call.

3.

Voice transmission of high quality is achieved after successful connection.

Refer to the following case “Mobile emergency call (SIM inside MS(/MS)/no SIM inside MS(/MS)) (112 and 999)”.

T09-03 Short Message Service T09-0301Short Message Service (MO)

T09-030101Originating SMS, MS idle Objective

1.This test intends to demonstrate the successful completion of MO SMS.


2.SMC is included for the networking.

Preset condition

1.MS(/MS) A and MS(/MS) B have registered the SMS service in networks. 2.MS(/MS) A and MS(/MS) B have their locations updated successfully. 3.MSB is idle.

Test procedure

1.Set the correct short message center (SMC) address in MS(/MS) A. 2.MS(/MS) A sends a short message “12345” to MS(/MS) B.

Expected result

MS(/MS) A can send the short message successfully.

Test description

T09-030102 Originating SMS, MS busy Objective




Preset condition

1.MS(/MS) A and MS(/MS) B have registered the SMS service in networks. 2.MS(/MS) A and MS(/MS) B have their locations updated successfully. 3.Ms B is busy.

Test procedure


38


Expected result

Test

Specification

for

Operation Guide

3.MS(/MS) A can send the short message successfully.

Test description

T09-030103 Originating SMS, MS detached Objective




Preset condition

1.MS(/MS) A and MS(/MS) B have registered the SMS service in networks. 2.MS(/MS) A and MS(/MS) B have their locations updated successfully. 3.MS B is detached.

Test procedure


Expected result


Test description

T09-030104Originating SMS, MS not reachable Objective




Preset condition

1.MS(/MS) A and MS(/MS) B have registered the SMS service in networks. 2.MS(/MS) A and MS(/MS) B have their locations updated successfully. 3.Ms B not reachable.

Test procedure


Expected result


Test description

T09-030105 Terminating Long (more than 160 characters) SMS Objective


Testnetworking diagram


Preset condition

1.MS(/MS) A and MS(/MS) B have registered the SMS service in networks. 2.MS(/MS) A and MS(/MS) B have their locations updated successfully.

Test procedure

1.Set the correct short message center (SMC) address in MS(/MS) A.

39


Test

Specification

for

Operation Guide

2.MS(/MS) A sends a short message “12345” to MS(/MS) B. Expected result


Test description

T09-030106 Originating SMS – Pre-Paid, MS idle Objective




Preset condition

1.MS(/MS) A and MS(/MS) B have registered the SMS service in networks. 2.MS(/MS) A and MS(/MS) B have their locations updated successfully. 3.MS A is prepaid subscriber. 4.MS B is idle.

Test procedure


Expected result


Test description

T09-030107 Originating SMS – Pre-Paid, MS busy Objective




Preset condition

1.MS(/MS) A and MS(/MS) B have registered the SMS service in networks. 2.MS(/MS) A and MS(/MS) B have their locations updated successfully. 3.MS A is prepaid subscriber. 4.MS B is busy.

Test procedure


Expected result


Test description

T09-030108 Originating SMS – Pre-Paid, MS detached Objective




40


Preset condition

Test

Specification

for

Operation Guide

1.MS(/MS) A and MS(/MS) B have registered the SMS service in networks. 2.MS(/MS) A and MS(/MS) B have their locations updated successfully. 3.MS A is prepaid subscriber. 4.MS B is detached.

Test procedure


Expected result


Test description

T09-030109 Originating SMS – Pre-Paid, MS not reachable Objective




Preset condition

1.MS(/MS) A and MS(/MS) B have registered the SMS service in networks. 2.MS(/MS) A and MS(/MS) B have their locations updated successfully. 3.MS A is prepaid subscriber. 4.MS B is reachable.

Test procedure


Expected result


Test description

T09-030110 Terminating Long (more than 160 characters) SMS – Pre-Paid Objective




Preset condition

1.MS(/MS) A and MS(/MS) B have registered the SMS service in networks. 2.MS(/MS) A and MS(/MS) B have their locations updated successfully. 3.MS A is prepaid subscriber. 4.MS B is prepaid subscriber.

Test procedure


41


Expected result

Test

Specification

for


Test description

42

Operation Guide


Test

Specification

for

Operation Guide

T09-0302 Short Message Service (MT)


This test intends to demonstrate the successful completion of MT SMS. SMC is included for the networking.

Preset condition

MS(/MS) A has registered the SMS service in networks. MS(/MS) A has its location updated successfully.

Test procedure

MS (/MS) B sends a short message “12345” to MS (/MS) A. The short message “12345” is sent to MS (/MS) A from SMC.

Expected result

MS(/MS) A can receive the message successfully.

Test description

T10 Supplementary Service T10-01 Call Forwarding T10-0101 Call Forwarding Unconditional (CFU)

Objective

This test intends to demonstrate the successful completion of forwarding call


None

Preset condition

MS (/MS) A is available Call Forwarding Unconditional service. The forward- to party is PSTN user C.

Test procedure

MS (/MS) A registers unconditional forwarding to PSTN user C, and activates unconditional forwarding service. Be sure that the MS (/MS) A has been provided with CFU service. MS (/MS) B srcinates a call to MS (/MS) A. The call is forwarded to the PSTN user C, and PSTN user C answers, keep the call a minute. MS (/MS) B disconnects the call.

Expected result

The call to MS (/MS) A is forwarded correctly to the appointed PSTN user.

Test description T10-0102 Call Forwarding on Mobile Subscriber Busy (CFB)

Objective

This test intends to demonstrate the successful completion of forwarding call.

43


Test

Specification

for

Operation Guide


None

Preset condition

MS (/MS) A is available Call Forwarding on Mobile Subscriber Busy service. The forward-to party is PSTN user C that is idle.

Test procedure

MS (/MS) A registers CFB to local PSTN user C and activates CFB. Be sure that the MS (/MS) A has been provided with CFU service. MS (/MS) A calls MS (/MS) D, and keeps the call. MS (/MS) B calls MS (/MS) A. The call is forwarded to the PSTN user C, and PSTN user C answers, keep the call for a while. PSTN user C disconnects the call.

Expected result

The call to subscriber A is forwarded correctly to the appointed PSTN user C.

Test description T10-0103 Call Forwarding on No Reply (CFNRY)

Objective



None

Preset condition

MS (/MS) A registers CFNRY service. The forward-to party is PSTN user C.

Test procedure

MS (/MS) A registers CFNRY to PSTN user C and activates it. Be sure that the MS (/MS) A has been provided with CFU service. MS (/MS) B calls MS (/MS) A. MS (/MS) A does not answer the call. The call is forwarding to the PSTN user C. PSTN user C answers, C disconnects the call. and keeps the call for a while, then PSTN user

Expected result

The call to MS (/MS) A can be f orwarded to the appointed PSTN user correctly.

Test description T10-0104 Call Forwarding on Mobile Subscriber Not Reachable (CFNRC)

Objective



None

Preset condition

MS (/MS) A registers CFNRC service, the forward-to party is PSTN user C.

Test procedure

MS (/MS) A registers CFNRC service; the forwarding party is PSTN

44


Test

Specification

for

Operation Guide

user C. Be sure that the MS (/MS) A has been provided with CFU service. MS (/MS) A powers off. MS (/MS) B calls MS (/MS)A. The call is forwarding to the PSTN user C. PSTN user C answers and keeps the call for a while, and then disconnects the call. Expected result

1.

The call can be forwarding to the PSTN user C correctly.

Test description T10-0105 Support the control of forwarding announcement


To verify call forwarding notification to caller None

1. Set CFU for subscriber A in the HLR, and set the “Notification to calling Subscriber” as “true”, The forward- to party is MS (/MS) C. 2. Use MOD MSFP command to set BIT8 of the software parameter P149 to 0.

Test Procedures

1. The system is in normal operation. 2. MS (/MS) B srcinates a call to MS (/MS) A. 3. Observe the User Interface trace. 4. The call is forwarded to MS (/MS) C,and MS (/MS) C picks up the c all. 5. Subsequently MS (/MS) B hangs up after communication.

Expected Results

1. The call can be established correctly. 2. During call forwarding process, B hears notification announcement 3. High quality voice transmission after successful connection.

Test Description

45


Test

Specification

for

Operation Guide

T10-02 Call Barring T10-0201 Barring of All Outgoing Calls (BAOC)

Objective Testdiagram networking

This test intends to demonstrate the successful completion of BAOC None

Preset condition

MS (/MS) A’s BAOC service is available. Be sure that the MS (/MS) A has been provided with BAOC service.

Test procedure

Barring all the outgoing calls for MS (/MS) A. MS (/MS) A call local PSTN user C. MS (/MS) A hangs up.

Expected result

1.

MS (/MS) A can hear correct tone notices that all outgoing call is barred.

Test description T10-0202 Barring of Outgoing International Calls (BOIC)


This test intends to demonstrate the successful completion of BOIC None

Preset condition

MS (/MS) A‘s BOIC service is available.

Test procedure

Barring all the international outgoing calls for MS (/MS) A. MS (/MS) A calls an international PSTN user. MS (/MS) A can hear correct tone notices. MS (/MS) A hangs up.

Expected result

1.

MS (/MS) A can hear correct tone noticing user that all of outgoing international calls are barred.

Test description T10-0203 Barring of All Incoming Calls (BAIC)


This test intends to demonstrate the successful completion of BAIC None

Preset condition

MS (/MS) A’s BAIC service is available.

Test procedure

Barring all the incoming calls for MS (/MS) A. MS (/MS) B calls MS (/MS) A.

46


Test

Specification

for

Operation Guide

MS (/MS) B can hear the correct tone notices. MS (/MS) B hangs up. Expected result

1.

MS (/MS) B can hear correct tone noticing user that all of incoming calls of MS are barred.

Test description

T10-03 Operator Determined Barring T10-0301 ODB-BAOC, no outgoing call can be made


To verify ODB-BAOC function. None

Preset condition Test procedure

1.

Set ODB-BAOC fo r MS (/MS) in the HLR.

Expected result

2. 1.

The MS (/MS) initiates an outgoing call. No outgoing call can be made.

Test description T10-0302 ODB-BOIC, no outgoing international call can be made


To verify ODB-BOIC function. None


Expected result

1.

Set ODB-BOIC for MS (/MS) in the HLR.

2.

The MS (/MS) initiates outgoing international call.

1.

No outgoing international call can be made

Test description T10-0303 ODB-BAIC, no incoming call can be made


To verify ODB-BAIC call None

ODB-BAIC service is set for MS (/MS) in the HLR. Be sure that the MS (/MS) A has been provided with ODB-BAIC service.

47


Test

Specification

for

Operation Guide

Test Procedures

Using PSTN or another MS to initiates a call to this MS subscriber

Expected Results

Originating subscriber can hear “The subscriber you are dialing has been in arrearage “or similar voice.

Test Description

T10-0304 ODB of supplementary service activations


To verify the barring of supplementary service activation None


Set “ODB of supplementary service” for MS (/MS)in the HLR. On the HLR, execute the interrelated command to bar the activation of supplementary service. Register a supplementary service for MS (/MS)in the HLR. For example, on the HLR, execute the interrelated command to provide the CFU service. Operate the corresponding phone menu to activate the service. If the phone menus do not support such an operation, dial the following number: i.

Activation

:

*SC*SI#

Corresponding to the CFU service, the SC is 21 and the SI is the pre-defined forwarded-to number. Expected result

The MS (/MS)fails to activate the supplementary service.

Test description

T10-04 Number Identification T10-0401 MS (/MS) provision CLIR Permanent, CLI display always suppressed


To verify that mobile subscriber can restrict CLIP by CLIR Permanent None

BTS, BSC, MSC and HLR are running normally. HLR stores the subscription data of a GSM MS (/MS) A. MS (/MS) A has the CLIR service right with the attribute “temporary

48


Test

Specification

for

Operation Guide

restricted”. HLR stores the subscription data of a GSM MS (/MS) B. MS (/MS) B is a non-override subscriber and has the CLIP service right. On the MSC, open the subscriber trace. Specify the IMSI number of MS (/MS) A/B. Select to trace the A interface and C/D/F interface. Test procedure

MS (/MS) A and B successfully update their locations with MSC and are idle now. Query the configured supplementary service data of MS (/MS) A in VLR by executing the DSP USRSS command. MS (/MS) A srcinates a call to MS (/MS) B. From the subscriber trace of MS (/MS) A, observe the Setup message through the A interface. MSC successfully pages MS (/MS) B. From the subscriber trace of MS (/MS) B, observe the Setup message through the A interface. Observe the calling number displayed on MS B. The number of MS (/MS) A will not display on MS (/MS) B.

Expected result

Query the supplementary service data of MS (/MS) A on the VLR, and you can find the CLIR state: a)

Active Status

b)

Register Status : Registered

: Active

c)

Provision Status : Provisioned

d)

Quiescence Status : Not Quiescent

e)

CLI Restrict Options = Permanent

Test description T10-0402 MS (/MS) provision CLIP Permanent, CLI can always be shown


This test intends to demonstrate the successful completion of CLIP None

BTS, BSC, MSC and HLR are running normally. HLR stores the subscription data of MS (/MS) A and B. MS (/MS) A has the CLIP service right. MS does not have the CLIR service right. On the MSC, open the subscriber trace. Specify the IMSI number of MS (/MS) A. Select to trace the A interface and C/D/F interface.

Test procedure

MS (/MS) A and B successfully update their locations with MSC and are idle now. Query the configured supplementary service data of MS (/MS) A in VLR by executing the DSP USRSS command. MS (/MS) B srcinates a call to MS (/MS) A.

49


Test

Specification

for

Operation Guide

The number of MS (/MS) B is displayed on the screen of MS (/MS) A. Expected result

Query the supplementary service data of MS (/MS) A on the VLR, and you can find the CLIP state: a)

Active Status

: Active

b)

Register Status : Registered

c)

Provision Status : Provisioned

Quiescence Status : Not Quiescent. Test description

T10-05 Call Completion T10-0501 Call Hold

()1

Objective

()2

This test intends to demonstrate the successful completion of call hold.

()3


()4

None

()5

Preset condition

1.BTS, BSC, MSC, and HLR run normally. 2.The subscription data of GSM subscribers A and B are stored in HLR. 3.GSM subscriber A has registered the Call Hold supplementary service.

()6

Test procedure

1.The locations of GSM subscribers A and B have been updated in MSC successfully. 2.GSM subscriber A initiates a call to GSM subscriber B. Subscriber B answers the call.

3.GSM subscriber A holds the call. Subscriber B hears the call hold announcement. 4.GSM subscriber A retrieves the call with subscriber B. 5.GSM suscriber A hangs up.

()7

Expected result

1.GSM subscribers can hold and retrieve a c all successfully. 2.Subscriber B in the call hold state can hear the call hold announcement.

Test description T10-0502 Call Waiting

Objective

This test intends to demonstrate the successful completion of call waiting.

50



Test

Specification

for

Operation Guide

None

Preset condition

BTS, BSC, MSC, and HLR run normally. The subscription data of GSM subscribers A, B and C are stored in HLR. GSM subscriber B has registered the Call Waiting supplementary service.

Test procedure

The locations of GSM subscribers A, B and C have been updated in MSC successfully. GSM subscriber A makes a call to subscriber B. Subscriber B answers the call. Subscribers A and B are talking with each other. MSC sends the “Alerting” message to subscriber C to notify subscriber C of entering the call waiting state. Before the call waiting timer expires, subscriber B releases the call with subscriber A, and accepts the call from subscriber C. Subscribers B and C are talking with each other. After subscriber B hangs up, the call is released.

Expected result

Subscriber C in the call waiting state can hear the call waiting announcement. Subscriber C in the call can be hold and active correctly.

Test description

T10-06Multiparty Service T10-0601 Multiparty Service

Objective

This test intends to demonstrate the successful completion of a three-party call.


None

Preset condition

MS (/MS) A has registered the Multiparty Call and Call Hold supplementary services.

Test procedure

MS (/MS) A calls another MS (/MS) B. MS (/MS) A holds the call with MS (/MS) B. MS (/MS) A calls MS (/MS) C. MS (/MS) A activates the multi-party Service. MS (/MS) A releases the call.

51


Expected result

Test

Specification

for

Operation Guide

The multiparty call can be invoked successfully, and the subscribers can hear the voice of each other.

Test description

T10-07 USSD T10-0701Unstructured Supplementary Service Data (MO)


To verify that MSC/VLR can correctly process the MO USSD single interaction triggered by mobile subscriber None

MS (/MS) supports USSD. MS (/MS) has its location updated successfully. The subscriber tracing function has been enabled in MSC. The IMSI of a subscriber is specified, and the A interface is selected to be traced.

Test procedure

Execute the command ADD USSDCTRL at the maintenance console: Enter service code “99”, select “QUERY MSISDN”, and add the USSD function. Enter the string “*#99#” in the mobile phone to query the subscriber’s MSISDN.

Expected result

The MSISDN is displayed on the subscriber’s mobile phone. By checking the tracing messages of the A interface, you can see the message “REGISTER/RELEASE COMPLETE”.

Test description

52


Test

Specification

for

Operation Guide

T11Handover T11-01Intra-office 2G Handover T11-0101Intra-office 2G voice call hard handover

Objective


To verify whether the handover between BSCs in the same MSC can be performed for the subscriber successfully during a conversation and the conversation is not affected. None

Preset Conditions

1.

There are two BSC systems in the MSC, BSC -A and BSC -B, and the two BSC systems have adjacent CELL.

2.

The MSC is configured with correct location area data and A interface

1.

Start A interface message tracing task.

2.

Start MS interface tracing task.

3.

A GSM subscriber calls another GSM subscriber.

4.

During the conversation, the called GSM subscriber enters the BSC -B

data. Test Procedures

serving CELL from BSC -A serving CELL and handover is performed. 5.

Observe whether the conversation is interrupted or the voice quality is lowered.

Expected Results

Test Description

1.

The handover is successful, the conversation is not interrupted and the voice quality is not greatly lowered during the handover.

2.

The subscriber interface tracing task is performed correctly.

3.

The message process of A interface is correct.

None

53


Test

Specification

for

Operation Guide

T12 CAMEL Service T12-01 PPS calls PPS T12-0101 PPS calls PPS


This test intends to demonstrate the successful completion of PPS call PPS. SCP support CAMEL Phase II or above. 1.

The mobile terminals and networks are normal.

2.

GSM subscriber A has subscription O-CSI information in the HLR,

3.

Before testing this example, customers need to provide the signaling interface specification between MSC and SCP.

4.

Location update for local GSM subscribers A and B is successful in the GSM network.

Test procedure

Expected result

5.

The MS A and B user is idle.

1.


2.

MS B answers, the call connected.

3.

Observe the User Interface trace and keep the call for a while.

4.

Subsequently MS A hangs up.

1.

The call is correctly setup.

2.

MO Trigger subscriber A’s intelligent service normally.

3.

High quality speech transmission after successful connection.

4.

The call release normally.

Test description

54


Test

Specification

for

Operation Guide

T12-02 PPS calls PPS but the callee is busy ，



but the callee is busy

，

This test intends to demonstrate the successful completion of PPS calls PPS but the callee is busy. ，

SCP support CAMEL Phase II or above.

Preset condition

1.


2.


3.

GSM subscriber A has subscription O-CSI information in the HLR.

4.


Test procedure

Expected result

5.


1.

GSM subscriber B is talking with another PSTN user.

2.

GSM subscriber A calls local GSM subscriber B,

3.

MSC release the call.

1.

Trigger subscriber A’s intelligent service normally, MSC send message when call release.

2.


Test description

T12-03 PPS calls PPS but the callee does not answer ，



but the callee does not answer

，

This test intends to demonstrate the successful completion of PPS calls PPS but the callee does not answer. ，

SCP support CAMEL Phase II or above. 1.


55


Test

2.

Specification

for

Operation Guide


3.

GSM subscriber A has subscription O-CSI DP2 information in the HLR.

4.


Test procedure

Expected result

5.


1.

GSM subscriber A calls local GSM subscriber B,

2.

the called subscriber not answer the call after the phone set rings.

3.

At timeout, MSC release the call.

1.

Trigger subscriber A’s intelligent service normally, MSC send message to SCP when call release.

2.


Test description

56


Test

Specification

for

Operation Guide

T12-04 PPS calls the PPS service number to recharge T12-0401 PPS calls the PPS service number to recharge

Objective

Test networking diagram Preset condition

This test intends to demonstrate the successful completion of recharge when GSM CAMEL subscribes call ordinary GSM subscribers SCP support CAMEL Phase II or above. 1.


2.


3.


4.

Location update for local GSM subscribers A is successful in the GSM network.

5.

The MS A ser is idle.

Test procedure

GSM subscriber A calls Customer Service Center. After A hear the prompt select the recharge flow.

Expected Result

The recharge is successful after the correct recharge password is input. The announcement prompts the balance and validity period after recharge.

Test Description

57


Test

Specification

for

Operation Guide

T12-05 PPS calls the PPS service number to query the balance T12-0501 PPS calls the PPS service number to query the balance

Objective

This test intends to demonstrate the successful completion of query the balance when GSM CAMEL (O-CSI )subscribes call ordinary GSM subscribers



Preset condition

1.


2.


3.


4.


5.

The MS A user is idle.

Test procedure

GSM subscriber A calls Customer Service Center. After A hear the prompt select the query the balance flow ..

Expected Result

A hear the announcement indicate that your available Credit and expired date.

Test Description

58


Test

Specification

for

Operation Guide

T12-06 PPS calls the PPS service number for operator assistance T12-0601 PPS calls the PPS service number for operator assistance

Objective

This test intends to demonstrate the successful completion of transferred to operator assistance when GSM CAMEL (O-CSI)subscribes call ordinary GSM subscribers



Preset condition

1.


2.


3.


4.


5.

The MS A use r is idle.

Test procedure

GSM subscriber A calls Customer Service Center. After A hear the prompt select the transfer to operator assistance flow.

Expected Result

1.

A hear the announcement like indicate that you are being transferred to customer care center.

2.

After that, the call is connect to operator assistance successfully.

Test Description

59


Test

Specification

for

Operation Guide

T13 Other MSC/VLR Functions T13-01 Announcement T13-0101 Announcements on Calling to Unregistered Subscriber

Objective

To verify that proper prompt tone can be played to caller when calling an unregistered Subscriber.


1.


2.

GSM subscribers A registers in MSC/VLR.

Test Procedures

Subscriber A calls an unregistered Subscriber.

Expected Results

Subscriber A can hear the prompt tone (according to announcementt files which provided by DMPI).

Test Description

T13-0102 The call is failed for the called subscriber is powered off

Objective

To verify whether announcement can be played normally when the called mobile subscriber powers off the MS.


None

Preset condition

1.

The data of mobile subscriber A is stored in the HDB/VDB.

2.

The data of called subscriber B is stored in the HDB, and B powers off his/her MS.

Test procedure

A calls B.

Expected result

1.

Mobile subscriber A can hears correct announcement.

2.

After the announcement ends, the call and related resources are released normally.

Test Description

1.

The operators can determine whether to play announcement for this case.

60


2.

Test

Specification

for

Operation Guide

The announcement contents are determined by the o perators.

T13-0103 The call is failed when the called subscriber is not in the service area

Objective

To verify whether announcement can be played normally when paging is not responded.


None

Preset condition

1.


2.

The data of called subscriber B is stored in the HDB/VDB.

Test procedure

A calls B, and paging to B is not responded.

Expected result

1.

Mobile subscriber A hears correct announcement

2.

After the announcement ends, the call and related resources are released normally.

Test Description

1.


2.


T13-0104 The call is failed for the called subscriber is busy

Objective Test networking

To verify whether announcement can be played normally when the called mobile subscriber is busy. None

diagram Preset condition

1.


2.

The data of called subscribers B and C is stored in the HDB/VDB.

3.

B has established a call with C, and they are talking.

Test procedure

A calls B.

Expected result

1.

Mobile subscriber A hears correct announcement, for example, “Sorry! The subscriber you dialed is busy now, please redial later!”

2.

After the announcement ends, the call and related resources are released

61


Test

Specification

for

Operation Guide

normally. Test Description

1.


2.


T13-02 Long Call Notification and Auto/Manual Teardown T13-0201Long Call Notification and Auto Teardown

Objective

To verify Supervision and Disconnection of L ong Duration Calls


None

Preset condition

.1

The mobile terminals and networks work well.

.2

Use command MOD GBILLCTRL: MCT=5, TO=TRUE to set parameter for Long Duration Calls, which means that the call over 5 minutes shall be released.

Test procedure

Mobile subscriber A makes a call to mobile subscriber B successfully. Mobile subscriber A and B keep the call all the time.

Expected result

.1

The call shall be released after 5 minutes since the PSTN subscriber accepting the call.

.2

An alarm will be generated and sent to OMC terminal.

Test Description

T14 Additional dialing table NO

Te sC t as e s

T es t re su lt

MS to MS, Successful T14-1

MS calls MS in same MSC

T14-2

PP-MS calls MS in same MSC

T14-3

MS in MSC2H calls MS in other MSC

T14-4

PP-MS in MSC2H calls MS in other MSC

T14-5

MS in other MSC calls MS in MSC2H MS to MS, Unsuccessful

62

C o mm e n t


Test

Specification

for

T14-6

Call from MS1 to MS2, MS2-Busy

T14-7

Call from PP-MS1 to MS2-Busy

T14-8

Call from MS1 to MS2, No answer

T14-9

Call from PP-MS1 to MS2, No answer

T14-10

Call to MS2 from MS1, Detached, Announcement

T14-11

Call to MS2 from PP-MS1, Detached, Announcement

T14-12

Call to MS2 from MS1, No Page Response

T14-13

Call to MS2 from PP-MS1, No Page Response

Operation Guide

Handover Test T14-14

MS calls MS in same MSC and makes an intra MSC handover

T14-15

PP-MS calls MS in same MSC and makes

T14-16

an intra MSC handover MS in calls MS in same MSC and makes an inter MSC handover to other MSC

T14-17

PP-MS calls MS in same MSC and makes an inter MSC handover to other MSC

T14-18

PP-MS in MSC2H calls MS in MSC2H and makes an inter MSC handover to other MSC and then a subsequent handover back to MSC2H. MS to INT

T14-19

MS in MSC2H calls International MS

T14-20

PP-MS in MSC2H calls International MS MS to PSTN

T14-21

Call from MS to PSTN, Successful

T14-22

Call from PP-MS to PSTN, Successful

T14-23

Call from MS to PSTN, B-sub Busy

T14-24

Call from PP-MS to PSTN, B-sub Busy

T14-25

Call from MS to PSTN, No answer

T14-26

Call from PP-MS to PSTN, No answer

NO

Te sC t as e s

T es t re su lt

63

C o mm e n t


Test

Specification

for

PSTN to MS T14-27

Call from PSTN to MS, Successful

T14-28

Call from PSTN to MS, B-sub Busy

T14-29

Call from PSTN to MS, No answer

T14-30

MS From other operator calls MS in MSC2H, Successful

T14-31

MS From other operator calls Pre-Paid MS in MSC2H, Successful

T14-32

MS in MSC2H calls Globe MS, Successful

T14-33

PP-MS in MSC2H calls Globe MS, Successful

T14-34

MS in MSC2H calls Smart MS, Successful

T14-35

PP_MS in MSC2H calls Smart MS, Successful

T14-36

MS1 calls MS2 the call is forwarded to MS3 (CFU)

T14-37

MS1 calls MS2, MS2 is busy the call is forwarded to MS3

T14-38

MS1 calls MS2, call forwarded on No reply to MS3

T14-39

MS1 calls MS2, call forwarded on MS2 No Reachable to MS3

T14-40

MS1 calls MS2, Default call forwarded to MS3

Other Operators

Call Forwarding

T14-41 MS1 calls Pre-Paid MS2 the call is forwarded to MS3 (CFU) T14-42

MS1 calls Pre-Paid MS2, MS2 is busy the call is forwarded to MS3

T14-43

MS1 calls Pre-Paid MS2, call forwarded on No reply to MS3

T14-44

MS1 calls Pre-Paid MS2, call forwarded on MS2 No Reachable to MS3

T14-45

MS1 calls Pre-Paid MS2, Default call forwarded to MS3

T14-46

PP-MS1 calls Pre-Paid MS2 the call is

64

Operation Guide


Test

Specification

for

forwarded to MS3 (CFU) T14-47

PP-MS1 calls Pre-Paid MS2, MS2 is busy the call is forwarded to MS3

T14-48

PP-MS1 calls Pre-Paid MS2, call forwarded on No reply to MS3

T14-49

PP-MS1 calls Pre-Paid MS2, call forwarded on MS2 No Reachable to MS3

T14-50

PP-MS1 calls Pre-Paid MS2, Default call forwarded to MS3 Call Waiting/Hold

T14-51

MS1 calls MS2, MS3 calls MS2 (Call waiting and Call Hold) During Call Waiting/Hold ensure correct tones are heard

T14-52

PP-MS1 calls MS2, MS3 calls MS2 (Call waiting and Call Hold) During Call Waiting/Hold ensure correct tones are heard

T14-53

MS1 calls MS2, PP-MS3 calls MS2 (Call waiting and Call Hold) During Call Waiting/Hold ensure correct tones are heard MultiParty

T14-54

Multiparty MS1, MS2 and MS3

T14-55

Multiparty PP-MS1, MS2 and MS3 CLIP/CLIR

T14-56

Calling Line Identification Presentation

T14-57

Calling Line Identification Restriction

T14-58

Calling Line Identification Presentation PrePaid

T14-59

Calling Line Identification Restriction PrePaid DTMF

T14-60

MS1 initiates DTMF sending Tones

T14-61

MS2 receives DTMF tones

T14-62

PP-MS1 initiates DTMF sending Tones

T14-63

PP-MS2 receives DTMF tones Echo Canceller

T14-64

Make Call with Echo Canceller, ensure

65

Operation Guide


Test

Specification

for

device attached T14-65

Make Call with Echo Canceller, ensure device NOT attached Tones

T14-66

MS1 calls MS2, Check the Ring tone for correctness

T14-67

MS1 from other MSC calls MS2, Check the Ring tone for correctness

T14-68

PSTN calls MS1, Check the Ring tone for correctness

T14-69

MS1 from Other Operator calls MS1, Check the Ring tone for correctness

T14-70

MS1 calls Busy MS2, Check the Ring Back tone for correctness at MS1 when MS2 is free

T14-71

MS1 calls Busy MS2 with call waiting, Check the Ring Back tone for correctness at MS1 when MS2 is free

T14-72

Test any other Tones as required International Roaming

T14-73

International MS performs Location Update

T14-74

International MS1 calls MS, Successful

T14-75

International MS1 sends SMS to MS, Successful

T14-76

MS1 sends SMS to International MS, Successful

T14-77

PP-MS1 sends SMS to International MS, Successful Long Duration

T14-78

Long duration call, automatic disconnection after 1 hour Barring

T14-79

MS1 with Category OBO1 calls MS2, barring successful

T14-80

MS1 with Category OBO2 calls MS2, barring successful

66

Operation Guide


Test

Specification

for

T14-81

MS1 calls MS2 with Category OBI1, barring successful

T14-82

Pre-Paid MS1 with Category OBO1 calls MS2, barring successful

T14-83

Pre-Paid MS1 with Category OBO2 calls MS2, barring successful

T14-84

MS1 calls Pre-Paid MS2 with Category OBI1, barring successful

T14-85

Barring of all Incoming Calls Emergency calls

T14-86

MS make Emergency call with SIM

T14-87

PP-MS make Emergency call with SIM

T14-88

MS make Emergency Call without SIM

T14-89

PP-MS make Emergency call without SIM Other test

T14-90 T14-91

Originating SMS, MS idle

T14-92

Originating SMS, MS detached

T14-93

Originating SMS, MS not reachable

T14-94

Terminating Long (more than 160 characters) SMS

T14-95

Originating SMS – Pre-Paid, MS idle

T14-96

Originating SMS – Pre-Paid, MS busy

T14-97

Originating SMS – Pre-Paid, MS detached

T14-98

Originating SMS – Pre-Paid, MS not

Originating SMS, MS busy

reachable T14-99

Terminating Long (more than 160 characters) SMS – Pre-Paid

T14-100

MS Retrieve message from Voice-Mail

T14-101

PP-MS Retrieve message from Voice-Mail

T14-102

Pre paid MS call to - Recharge

T14-103

Pre paid MS call to – Balance enquiry

T14-104

Remote node connection via OSS RC

T14-105

Collection of counters and alarms via OSS

67

Operation Guide


Test

Specification

for

T14-106

Call Tracing of call through network possible (CTRAI)

T14-107

Test of Basic Charging

T14-108

Roaming partners Location Update Testing

T14-109

Revenue assurance Testing

T14-110

Announcement Testing

T14-111

CDR Validation

68

Operation Guide


Test

Specification

for

Operation Guide

T15 Other Test NO

Te sC t as e s

T15-001

CIC Testing (1 STM-1 to TMSC1)

T15-002

CIC Testing (1 STM-1 to TMSC2)

T15-003

E1 recovery testing

T15-004

Clock board synchronization

T15-005

Traffic control mechanism test

T15-006

Fault/Manual Switch-over

T15-007

Checklist verification (office data audit)

T es t re su lt

69

C o mm e n t

MSOFTX3000

Recommend Documents