Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Test
Specification
for
Table of Contents
Table of Contents
Test
Specification
for
Table of Contents
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
T06-02Version listing......................................................................................................18
T06-0301Query the version of MSOFTX3000.........................................................................18
T06-03Shelf Management..............................................................................................18
T06-0401Listing the shelf information......................................................................................18
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
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-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
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-06Multiparty Service................................................................................................51
T10-0601 Multiparty Service....................................................................................................51
T10-07 USSD.................................................................................................................52
T10-0701Unstructured Supplementary Service Data (MO).....................................................52
iv
Test
Specification
for
Table of Contents
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
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 Preset condition To check whether the FE port status can be queried normally. None
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.
Enter command DSP PORT together with the frame number and slot number, and select FE for the Port Type. The status of FE port is returned. None
Test
Specification
for
Operation Guide
Test Procedures
1.
2.
Expected Results
1.
2.
Test
Specification
for
Operation Guide
None
Test
Specification
for
Operation Guide
T02-0102 Operator Authority Management Objective Serial Number of Test Networking Diagram Preset Conditions To verify the function of adding and deleting an operator None
1.
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
Function Acceptance MSOFTX3000 T02-0103 Operator Login/Logout Objective Serial Number of Test Networking Diagram Preset Conditions Test Procedures
Test
Specification
for
Operation Guide
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 <OK> to log in. Select the menu item [System/Logout], and a prompt box will pop up. Click <OK> 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
T02-0104 Listing operator information Objective Serial Number of Test Networking Diagram Preset Conditions To verify the function of listing operator information None
1.
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. 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
Expected Results
Test
Specification
for
Operation Guide
T02-0105 Listing the frame information Objective Serial Number of Test Networking Diagram Preset Conditions 1. To verify the function of listing the frame information None
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 Expected Results Test Description T02-0106 Display the FAN information Objective Serial Number of Test Networking Diagram Preset Conditions 1. To verify the function of displaying the FAN information. None
Carry out LST FRM on the client, specify the shelf number, then press <F9> to execute the command The information of specified frame will be shown
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 Expected Results Test Description
Carry out DSP FAN on the client, specify the shelf number, then press <F9> to execute the command The fan information of specified frame will be shown
None
T02-0107 Display the PDB information. Objective Serial Number of To verify the function of displaying the PDB information. None
Test
Specification
for
Operation Guide
2.
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 Expected Results Test Description
Carry out DSP PDB on the client, specify the shelf number, then press <F9> to execute the command The PDB information of specified frame will be shown
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.
Test
Specification
for
Operation Guide
T03-0102 Query Alarm Log Objective Serial Number of Test Networking Diagram Preset Conditions Test Procedures Test the function to query alarm logs. 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 then click <OK>.
The pop-up [Query Alarm Log] dialog box will display the alarm logs in accordance with the query condition. Relevant MML command: LST ALMLOG.
T03-0103 Query Alarm Details Objective Serial Number of Test Networking Diagram Preset Conditions Test Procedures Test the function to query alarm details None
Msoftx3000 Alarm Management System has been logged in properly. Double click an alarm record in the [Fault Browse], [Event Browse] or [Query Alarm Log] window, an [Alarm Details] dialog box will pop up. The [Alarm Details] window will display the details of the alarm such as the alarm ID, name and locating information.
Relevant MML command: NONE.
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
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 <OK>.
Expected Results
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.
Test Description
Test
Specification
for
Operation Guide
Msoftx3000 Alarm Management System has been logged in properly. Pull out the UPWR Board from the slot. Check the Alarm Management System whether there is the ALARM: UPWR Board fault.
1. Insert this board into the correct slot.
There is new raised alarm UPWR Board fault in Alarm Management System.
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 Serial Number of Test Networking Diagram Preset Conditions Test the alarm of The local TUP/ISUP blocks the opposite single circuit for maintenance None
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]. An alarm ISUP/TUP ALARM TK NO7 MT BLOCK will appear in event alarm window.
2.
3.
Enter UBL N7TKC the correct module number, circuit type, the direction, the start circuit number and the end circuit number, and press [F9].
There is new raised alarm ISUP/TUP ALARM TK NO7 MT BLOCK in Alarm Management System.
After unblock these trunk circuits, these alarms will recover from alarm window.
None
T03-0404 SWAP STANDBY TO ACTIVE Objective Serial Number of Test Networking Diagram Preset Conditions Test the alarm of Swap Standby board to Active board None
Msoftx3000 Alarm Management System has been logged in properly. Msoftx3000 Operation and Maintenance System has been logged in properly.
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. 2. 3. 4. Test Description This board cans normally startup. After startup, this board becomes the standby board. The standby Board will become the Primary Board.
None
2.
12
Test
Specification
for
Operation Guide
3.
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 <Query>.
Expected Results
1. 2.
A prompt indicating successful creation is displayed. The newly created task exists, and the basic information, entity information and object information of the task are consistent with the previous settings.
3. Test Description
T04-0102Deleting traffic measurement task Objective Serial Number of Test Networking Diagram Preset Conditions 1. 2. 3. The system is in normal operation. The client software runs normally. You have the right for executing traffic measurement management commands. 4. Test Procedures A traffic measurement task has been created successfully. To verify the function of deleting traffic measurement task
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 <Yes> for confirmation. 1. 2. A prompt indicating successful deletion is displayed. Check the [Task list] column to confirm that the task has been deleted. After the task is deleted, its result list will be deleted too. 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.
Expected Results
Test Description
1. 2.
13
Function Acceptance MSOFTX3000 Objective Serial Number of Test Networking Diagram Preset Conditions
Test
Specification
for
Operation Guide
1. 2. 3.
The system is in normal operation. The client software runs normally. You have the right for executing traffic measurement management commands.
4. Test Procedures 1.
A traffic measurement task has been created successfully. 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. You can modify such properties as task name, output mode, output device, and measurement unit and time information.
2.
Expected Results
1. 2.
A prompt indicating successful modification is displayed. Check the contents in the [Task Information] window to see whether the 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 Serial Number of Test Networking Diagram Preset Conditions 1. 2. 3. The system is in normal operation. The client software runs normally. You have the right for executing traffic measurement management commands. 4. Test Procedures 1. An activated traffic measurement task has been created. 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 To verify the function of changing the state of traffic measurement task
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. 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 client.
2.
T04-0105Querying traffic measurement task Objective Serial Number of Test Networking Diagram Preset Conditions 1. 2. 3. The system is in normal operation. The client software runs normally. You have the right for executing traffic measurement management commands. Test Procedures 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 <OK>. 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 client. To verify the function of querying traffic measurement task
T04-0106Querying traffic measurement result Objective Serial Number of Test Networking Diagram Preset Conditions 1. The system is in normal operation. To verify the function of querying traffic measurement result
15
Test
Specification
for
Operation Guide
2. 3.
The client software runs normally. You have the right for executing traffic measurement management commands.
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 such parameters as time range in the [Query Task Result] dialog box that pops up. After the setting, click <Query>. 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. 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.
Expected Results
Test Description
2. Expected Results
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 Serial Number of Test Networking Diagram Preset Conditions 1. A subscriber successfully completes a location update at the local office and is idle now. The system operates normally and supports mobile originated call 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. Make a mobile originated call The trace tasks are registered successfully. The trace window displays all messages transmitted and received through the interface in sequence. 3. Test Description The traced messages are interpreted correctly. To verify the function of tracing interface messages based on subscriber
2. Test Procedures 1.
2. Expected Results 1. 2.
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 Serial Number of Test Networking Diagram Preset Conditions Test Procedures Expected Results Test Description Query the version of MSOFTX3000 None
The client works normally Click [Help/About] to open about dialog. The version of MSOFTX3000 will be displayed
None
T06-03Shelf Management
T06-0401Listing the shelf information Objective Serial Number of Test Networking Diagram Preset Conditions To verify the function of Listing the shelf information None
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 <F9> to execute the command
18
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
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 <F9> to execute the command. The information of specified board will be shown
None
T06-0402 Switching over board Objective Serial Number of Test Networking Diagram Preset Conditions To verify the function of switching over board None
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
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 <Yes>. 2. 3. Check the board status during switchover. Check switchover alarms at the alarm console. The operations are done successfully.
Expected Results
1.
2. The original standby board serves as the active one. When the original active board is being reset, its status becomes Fault. Finally, the original 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 Serial Number of Test Networking Diagram Preset Conditions To verify multiple methods of restarting the system None
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 Serial Number of Test Networking Diagram Preset Conditions To verify the function of listing module version number None
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. The version number(s) of the specified module(s) will be displayed.
After the BAM command timer times out, only the version numbers of the modules received will be displayed.
T06-0502Displaying CPU seizure rate Objective Serial Number of Test Networking Diagram Preset Conditions To verify the function of displaying CPU seizure rate None
1. 2.
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. The CPU seizure rate(s) of the specified module(s) will be displayed.
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 Serial Number of Test Networking Diagram Preset Conditions To verify the function of listing CPU overload threshold and resume threshold None
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 Expected Results Test Description T06-0602Set CPU Threshold Objective Serial Number of Test Networking Diagram Preset Conditions To verify the function of setting CPU overload threshold and resume threshold None
Carry out LST CPUTHD on the client, specify the Module number, and then press <F9> to execute the command. The information of CPU overload threshold and resume threshold will be displayed
None
1.
Test
Specification
for
Operation Guide
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 SET CPUTHD on the client, specify the Module number and input the threshold value, then press <F9> to execute the command. The threshold value will be changed
None
23
Test
Specification
for
Operation Guide
You have logged in to the BAM from the client successfully. You have the right for carrying out the corresponding command.
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<Year><Month><Day>.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 Test networking diagram Preset condition Test procedure To verify Data restore function of MSC server None
Clean BAM and latest Bam database can be restored correctly. None
T07-0103 Restart System (MSC Server) Objective To verify system restart function of MSC server
24
Function Acceptance MSOFTX3000 Test networking diagram Preset condition Test procedure Expected result None
Test
Specification
for
Operation Guide
The latest BAM database has been restored correctly. System restart based on power down/power up procedure.
The whole System is working normally. All boards are loaded correctly and working normally.
Test Description
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. At C/D/F interface, MSC/VLR originates location update to the HLR, and HLR inserts the MS data into the VLR. At A in terface, MSC/VLR sends LOCATION UPDATE ACCEPT message to the MS.
2.
3.
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 diagram Preset condition To verify IMSI attach . None
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.
T08-0104 2G-2G Roaming of CS Subscriber Objective Serial Number of Test Networking Diagram Preset Conditions 1. 2. The system is in normal operation. Subscription data can be found in HLR and the MS has subscribed for Check whether roaming process from 2G MSC to 2G MSC can be managed successfully.
basic service. 3. MS has been attached in 2G MSC/VLR first and no relative roaming
restriction has been set. Test Procedures 1. 2. Expected Results Test Description Select 2G network manually from MS and try to roam to 2G MSC/VLR. Check & verify whether the roaming is successful.
The MS has attached 2G MSC successfully and the location update procedure is correct.
28
Test
Specification
for
Operation Guide
T08-02 Authentication
T08-0201 GSM MS authentication in BSC serving area in updating location Objective Serial Number of Test Networking Diagram Preset Conditions 1. 2. The system is in normal operation. Subscription data can be found in HLR and the MS has subscribed for Check whether authentication process can be managed successfully in updating location
basic service. 3. 4. Test Procedures MS is power off. BSC support authentication in location update.
1. Execute the MML command MOD AUTHCFG to set MSC always request authentication in location update. 2. Power on MS. MS is attached after successful location update.
1.
T08-03VLR Management
T08-0301Display of subscriber by IMSI Objective Serial Number of Test Networking Diagram Preset Conditions 1. 2. Test Procedures The system is in normal operation. Therere some subscribers on the local network. Check whether it is correct to display Basic Information of a Subscriber by IMSI.
1. Execute the command DSP USRINF from LMT. To select the parameter IMSI for User Number Type, input a corresponding user number in the table User Number. 2. Check & verify the outputting information.
29
Function Acceptance MSOFTX3000 Objective Serial Number of Test Networking Diagram Preset Conditions
Test
Specification
for
Operation Guide
1. 2.
The system is in normal operation. Therere some subscribers on the local network.
Test Procedures
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. Check & verify the outputting information.
T08-0303 Display MSRN information Objective Serial Number of Test Networking Diagram Preset Conditions 1. 2. Test Procedures 1. 2. Expected Results Test Description The system is in normal operation. Therere some subscribers on the local network. MS A initiates a normal call to MS B. Execute the command DSP MSRNPRE to display MSRN information. Check whether it is correct to display MSRN information.
T09Basic Services
T09-01 Basic Calls
T09-0101GSM subscriber calls GSM subscriber
30
Test
Specification
for
Operation Guide
1The MS A and MS B have speech call service subscription. 2The MS A and MS B are idle. 3 The MS A and MS B are in the same msc.
Test procedure
1MS A and MS B power on. 2MS A initiates a normal call to MS B. 3MS B answers, the call connected. 4Observe the User Interface trace and keep the call for a while. 5Subsequently MS B hooks on.
Expected result
1The call is correctly setup. 2High quality speech transmission after successful connection.
Test description T09-010102 MS in MSC20H calls MS in other MSC Test networking diagram Objective Preset condition None To verify whether GSM subscriber can call GSM subscriber normally. 1The MS A and MS B have speech call service subscription. 2The MS A and MS B are idle. 3 The MS A is in MSC2H,The MS B is in other MSC. Test procedure 1MS A and MS B power on. 2MS A initiates a normal call to MS B. 3MS B answers, the call connected. 4Observe the User Interface trace and keep the call for a while. 5Subsequently MS B hooks on. Expected result 1The call is correctly setup. 2High quality speech transmission after successful connection. Test description T09-010103 MS in other MSC calls MS in MSC20H
31
Function Acceptance MSOFTX3000 Test networking diagram Objective Preset condition None
Test
Specification
for
Operation Guide
To verify whether GSM subscriber can call GSM subscriber normally. 1The MS A and MS B have speech call service subscription. 2The MS A and MS B are idle. 3 The MS A is in other MSC,The MS B is in MSC2H.
Test procedure
1MS A and MS B power on. 2MS A initiates a normal call to MS B. 3MS B answers, the call connected. 4Observe the User Interface trace and keep the call for a while. 5Subsequently MS B hooks on.
Expected result
1The call is correctly setup. 2High quality speech transmission after successful connection.
Test description T09-010104 Call from MS1 to MS2, MS2-Busy Test networking diagram Objective Preset condition None To verify whether GSM subscriber can call GSM subscriber normally. 1The MS A and MS B have speech call service subscription. 2The MS A is idle,The MS B is busy. Test procedure 1MS A and MS B power on. 2MS A initiates a normal call to MS B. 3 The call is disconnected. 4Observe the User Interface trace and keep the station a while. 5. The MS A hooks on.
Expected result
Test description
32
Test
Specification
for
Operation Guide
T09-010105 Call from MS1 to MS2, No answer Test networking diagram Objective Preset condition None To verify whether GSM subscriber can call GSM subscriber normally. 1The MS A and MS B have speech call service subscription. 2The MS A and MS B are in idle..
Test procedure
1MS A and MS B power on. 2MS A initiates a normal call to MS B. 3MS 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
Test description T09-010106Call to MS2 from MS1, Detached, Announcement Test networking diagram Objective Preset condition None To verify whether GSM subscriber can call GSM subscriber normally. 1The MS A and MS B have speech call service subscription. 2The MS A is in idle. 3 . The MS B is in detached.
Test procedure
1MS A power on and MS B power off. 2MS A initiates a normal call to MS B. 3Can not connect, observe the user interface trace and keep a while. 4. MS A hooks on.
33
Test
Specification
for
Operation Guide
Expected result
Test description T09-010107 Call to MS2 from MS1, No Page Response Test networking diagram Objective Preset condition None To verify whether GSM subscriber can call GSM subscriber normally. 1The MS A and MS B have speech call service subscription. 2The MS A and MS B are in idle..
Test procedure
1MS A and MS B power on. 2MS A initiates a normal call to MS B. 3MS B does not response page. 4. Observe the user interface trace and keep a while.
Expected result
Test description T09-010108 MS in MSC20H calls International MS Test networking diagram Objective Preset condition None To verify whether GSM subscriber can call GSM subscriber normally. 1The MS A and MS B have speech call service subscription. 2The MS A and MS B are idle. 3 The MS B is international ms. Testprocedure 1MS A and MS B power on. 2MS A initiates a normal call to MS B. 3MS B answers, the call connected.
34
Test
Specification
for
Operation Guide
4Observe the User Interface trace and keep the call for a while. 5Subsequently MS B hooks on. Expected result 1The call is correctly setup. 2High quality speech transmission after successful connection. Test description
35
Test
Specification
for
Operation Guide
Testdescription
36
Test
Specification
for
Operation Guide
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
Test description
Test description
37
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
1. 2. 3.
The emergency call can be established successfully. Observe the A-interface signaling: The Setup message indicates that it is an emergency call. Voice transmission of high quality is achieved after successful connection.
Test description
Refer to the following case Mobile emergency call (SIM inside MS(/MS)/no SIM inside MS(/MS)) (112 and 999).
38
Test
Specification
for
Operation Guide
39
Test
Specification
for
Operation Guide
2.MS(/MS) A sends a short message 12345 to MS(/MS) B. Expected result Test description 3.MS(/MS) A can send the short message successfully.
40
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
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.
41
Test
Specification
for
Operation Guide
42
Test
Specification
for
Operation Guide
T09-0302 Short Message Service (MT) Objective Test networking diagram Preset condition This test intends to demonstrate the successful completion of MT SMS. SMC is included for the networking.
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.
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 originates 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.
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 MS (/MS) A is available Call Forwarding on Mobile Subscriber Busy service. The forward-to party is PSTN user C that is idle.
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.
T10-0103 Call Forwarding on No Reply (CFNRY) Objective Test networking diagram Preset condition Test procedure This test intends to demonstrate the successful completion of forwarding call None MS (/MS) A registers CFNRY service. The forward-to party is PSTN user C.
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, and keeps the call for a while, then PSTN user C disconnects the call.
The call to MS (/MS) A can be forwarded to the appointed PSTN user correctly.
T10-0104 Call Forwarding on Mobile Subscriber Not Reachable (CFNRC) Objective Test networking diagram Preset condition Test procedure This test intends to demonstrate the successful completion of forwarding call None MS (/MS) A registers CFNRC service, the forward-to party is PSTN user C.
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 Test description T10-0105 Support the control of forwarding announcement Objective Serial Number of Test Networking Diagram Preset Conditions 1. The call can be forwarding to the PSTN user C correctly.
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 originates 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 call. 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
MS (/MS) As 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.
1.
MS (/MS) A can hear correct tone notices that all outgoing call is barred.
T10-0202 Barring of Outgoing International Calls (BOIC) Objective Test networking diagram Preset condition Test procedure This test intends to demonstrate the successful completion of BOIC None
MS (/MS) As BOIC service is available. 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.
1.
MS (/MS) A can hear correct tone noticing user that all of outgoing international calls are barred.
T10-0203 Barring of All Incoming Calls (BAIC) Objective Test networking diagram Preset condition Test procedure This test intends to demonstrate the successful completion of BAIC None
MS (/MS) As BAIC service is available. 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 Test description 1. MS (/MS) B can hear correct tone noticing user that all of incoming calls of MS are barred.
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
Using PSTN or another MS to initiates a call to this MS subscriber Originating subscriber can hear The subscriber you are dialing has been in arrearage or similar voice.
T10-0304 ODB of supplementary service activations Objective Test networking diagram Preset condition Test procedure 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 Test description The MS (/MS)fails to activate the supplementary service.
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 originates 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) b) c) d) e) Active Status : Active Register Status : Registered Provision Status : Provisioned Quiescence Status : Not Quiescent CLI Restrict Options = Permanent
Test description T10-0402 MS (/MS) provision CLIP Permanent, CLI can always be shown Objective Test networking diagram Preset condition 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 originates a call to MS (/MS) A.
49
Test
Specification
for
Operation Guide
Query the supplementary service data of MS (/MS) A on the VLR, and you can find the CLIP state:
a) b) c) Active Status : Active Register Status : Registered Provision Status : Provisioned
()1 ()3
()2 ()4
This test intends to demonstrate the successful completion of call hold. None
()5
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 call 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
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 Test networking diagram Preset condition Test procedure This test intends to demonstrate the successful completion of a three-party call. None MS (/MS) A has registered the Multiparty Call and Call Hold supplementary services.
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
Test
Specification
for
Operation Guide
The multiparty call can be invoked successfully, and the subscribers can hear the voice of each other.
T10-07 USSD
T10-0701Unstructured Supplementary Service Data (MO) Objective Test networking diagram Preset condition 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 subscribers MSISDN.
Expected result
The MSISDN is displayed on the subscribers 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
1.
There are two BSC systems in the MSC, BSC -A and BSC -B, and the two BSC systems have adjacent CELL. The MSC is configured with correct location area data and A interface data.
2.
Test Procedures
1. 2. 3. 4.
Start A interface message tracing task. Start MS interface tracing task. A GSM subscriber calls another GSM subscriber. During the conversation, the called GSM subscriber enters the BSC -B serving CELL from BSC -A serving CELL and handover is performed.
5.
Expected Results
1.
The handover is successful, the conversation is not interrupted and the voice quality is not greatly lowered during the handover. The subscriber interface tracing task is performed correctly. The message process of A interface is correct.
53
Test
Specification
for
Operation Guide
54
Test
Specification
for
Operation Guide
2. Test description
55
Test
Specification
for
Operation Guide
2.
Before testing this example, customers need to provide the signaling interface specification between MSC and SCP.
3. 4.
GSM subscriber A has subscription O-CSI DP2 information in the HLR. Location update for local GSM subscribers A and B is successful in the GSM network.
The MS A and B user is idle. GSM subscriber A calls local GSM subscriber B, the called subscriber not answer the call after the phone set rings. At timeout, MSC release the call. Trigger subscriber As intelligent service normally, MSC send message to SCP when call release. The call release normally.
2. Test description
56
Test
Specification
for
Operation Guide
GSM subscriber A calls Customer Service Center. After A hear the prompt select the recharge flow. The recharge is successful after the correct recharge password is input. The announcement prompts the balance and validity period after recharge.
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 SCP support CAMEL Phase II or above. 1. 2. The mobile terminals and networks are normal. Before testing this example, customers need to provide the signaling interface specification between MSC and SCP. 3. 4. GSM subscriber A has subscription O-CSI information in the HLR. Location update for local GSM subscribers A is successful in the GSM network. 5. Test procedure Expected Result Test Description The MS A user is idle.
GSM subscriber A calls Customer Service Center. After A hear the prompt select the query the balance flow.. A hear the announcement indicate that your available Credit and expired date.
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 SCP support CAMEL Phase II or above. 1. 2. The mobile terminals and networks are normal. Before testing this example, customers need to provide the signaling interface specification between MSC and SCP. 3. 4. GSM subscriber A has subscription O-CSI information in the HLR. Location update for local GSM subscribers A is successful in the GSM network. 5. Test procedure Expected Result The MS A user is idle.
GSM subscriber A calls Customer Service Center. After A hear the prompt select the transfer to operator assistance flow. 1. A hear the announcement like indicate that you are being transferred to customer care center. After that, the call is connect to operator assistance successfully.
2. Test Description
59
Test
Specification
for
Operation Guide
Subscriber A calls an unregistered Subscriber. Subscriber A can hear the prompt tone (according to announcementt files which provided by DMPI).
T13-0102 The call is failed for the called subscriber is powered off Objective Test networking diagram Preset condition To verify whether announcement can be played normally when the called mobile subscriber powers off the MS. None 1. 2. The data of mobile subscriber A is stored in the HDB/VDB. The data of called subscriber B is stored in the HDB, and B powers off his/her MS. Test procedure Expected result A calls B. 1. 2. Mobile subscriber A can hears correct announcement. 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
Test
Specification
for
Operation Guide
2.
T13-0103 The call is failed when the called subscriber is not in the service area Objective Test networking diagram Preset condition To verify whether announcement can be played normally when paging is not responded. None 1. 2. Test procedure Expected result The data of mobile subscriber A is stored in the HDB/VDB. The data of called subscriber B is stored in the HDB/VDB.
A calls B, and paging to B is not responded. 1. 2. Mobile subscriber A hears correct announcement After the announcement ends, the call and related resources are released normally.
Test Description
1. 2.
The operators can determine whether to play announcement for this case. The announcement contents are determined by the operators.
T13-0104 The call is failed for the called subscriber is busy Objective Test networking diagram Preset condition To verify whether announcement can be played normally when the called mobile subscriber is busy. None 1. 2. 3. Test procedure Expected result The data of mobile subscriber A is stored in the HDB/VDB. The data of called subscribers B and C is stored in the HDB/VDB. B has established a call with C, and they are talking.
A calls B. 1. Mobile subscriber A hears correct announcement, for example, Sorry! The subscriber you dialed is busy now, please redial later! After the announcement ends, the call and related resources are released
2.
61
Test
Specification
for
Operation Guide
normally. Test Description 1. 2. The operators can determine whether to play announcement for this case. The announcement contents are determined by the operators.
.1 .2
The mobile terminals and networks work well. 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 .2
The call shall be released after 5 minutes since the PSTN subscriber accepting the call. An alarm will be generated and sent to OMC terminal.
Test Description
Test result
MS to MS, Successful
Comment
MS calls MS in same MSC PP-MS calls MS in same MSC MS in MSC2H calls MS in other MSC PP-MS in MSC2H calls MS in other MSC MS in other MSC calls MS in MSC2H MS to MS, Unsuccessful
62
Function Acceptance MSOFTX3000 T14-6 T14-7 T14-8 T14-9 T14-10 T14-11 T14-12 T14-13
Test
Specification
for
Operation Guide
Call from MS1 to MS2, MS2-Busy Call from PP-MS1 to MS2-Busy Call from MS1 to MS2, No answer Call from PP-MS1 to MS2, No answer Call to MS2 from MS1, Detached, Announcement Call to MS2 from PP-MS1, Detached, Announcement Call to MS2 from MS1, No Page Response Call to MS2 from PP-MS1, No Page Response Handover Test
MS calls MS in same MSC and makes an intra MSC handover PP-MS calls MS in same MSC and makes an intra MSC handover MS in calls MS in same MSC and makes an inter MSC handover to other MSC PP-MS calls MS in same MSC and makes an inter MSC handover to other MSC 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 T14-20
Call from MS to PSTN, Successful Call from PP-MS to PSTN, Successful Call from MS to PSTN, B-sub Busy Call from PP-MS to PSTN, B-sub Busy Call from MS to PSTN, No answer Call from PP-MS to PSTN, No answer Test Cases
Test result
Comment
63
Test
Specification
for
Operation Guide
PSTN to MS T14-27 T14-28 T14-29 Call from PSTN to MS, Successful Call from PSTN to MS, B-sub Busy Call from PSTN to MS, No answer Other Operators T14-30 T14-31 T14-32 T14-33 T14-34 T14-35 MS From other operator calls MS in MSC2H, Successful MS From other operator calls Pre-Paid MS in MSC2H, Successful MS in MSC2H calls Globe MS, Successful PP-MS in MSC2H calls Globe MS, Successful MS in MSC2H calls Smart MS, Successful PP_MS in MSC2H calls Smart MS, Successful Call Forwarding T14-36 T14-37 T14-38 T14-39 T14-40 T14-41 T14-42 T14-43 T14-44 T14-45 T14-46 MS1 calls MS2 the call is forwarded to MS3 (CFU) MS1 calls MS2, MS2 is busy the call is forwarded to MS3 MS1 calls MS2, call forwarded on No reply to MS3 MS1 calls MS2, call forwarded on MS2 No Reachable to MS3 MS1 calls MS2, Default call forwarded to MS3 MS1 calls Pre-Paid MS2 the call is forwarded to MS3 (CFU) MS1 calls Pre-Paid MS2, MS2 is busy the call is forwarded to MS3 MS1 calls Pre-Paid MS2, call forwarded on No reply to MS3 MS1 calls Pre-Paid MS2, call forwarded on MS2 No Reachable to MS3 MS1 calls Pre-Paid MS2, Default call forwarded to MS3 PP-MS1 calls Pre-Paid MS2 the call is
64
Test
Specification
for
Operation Guide
forwarded to MS3 (CFU) T14-47 T14-48 T14-49 T14-50 PP-MS1 calls Pre-Paid MS2, MS2 is busy the call is forwarded to MS3 PP-MS1 calls Pre-Paid MS2, call forwarded on No reply to MS3 PP-MS1 calls Pre-Paid MS2, call forwarded on MS2 No Reachable to MS3 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 PP-MS1 calls MS2, MS3 calls MS2 (Call waiting and Call Hold) During Call Waiting/Hold ensure correct tones are heard MS1 calls MS2, PP-MS3 calls MS2 (Call waiting and Call Hold) During Call Waiting/Hold ensure correct tones are heard MultiParty T14-54 T14-55 Multiparty MS1, MS2 and MS3 Multiparty PP-MS1, MS2 and MS3 CLIP/CLIR T14-56 T14-57 T14-58 T14-59 Calling Line Identification Presentation Calling Line Identification Restriction Calling Line Identification Presentation PrePaid Calling Line Identification Restriction PrePaid DTMF T14-60 T14-61 T14-62 T14-63 MS1 initiates DTMF sending Tones MS2 receives DTMF tones PP-MS1 initiates DTMF sending Tones PP-MS2 receives DTMF tones Echo Canceller T14-64 Make Call with Echo Canceller, ensure
T14-52
T14-53
65
Test
Specification
for
Operation Guide
Make Call with Echo Canceller, ensure device NOT attached Tones
MS1 calls MS2, Check the Ring tone for correctness MS1 from other MSC calls MS2, Check the Ring tone for correctness PSTN calls MS1, Check the Ring tone for correctness MS1 from Other Operator calls MS1, Check the Ring tone for correctness MS1 calls Busy MS2, Check the Ring Back tone for correctness at MS1 when MS2 is free MS1 calls Busy MS2 with call waiting, Check the Ring Back tone for correctness at MS1 when MS2 is free Test any other Tones as required International Roaming
T14-71
T14-72
International MS performs Location Update International MS1 calls MS, Successful International MS1 sends SMS to MS, Successful MS1 sends SMS to International MS, Successful PP-MS1 sends SMS to International MS, Successful Long Duration
T14-78
T14-79 T14-80
MS1 with Category OBO1 calls MS2, barring successful MS1 with Category OBO2 calls MS2, barring successful
66
Test
Specification
for
Operation Guide
MS1 calls MS2 with Category OBI1, barring successful Pre-Paid MS1 with Category OBO1 calls MS2, barring successful Pre-Paid MS1 with Category OBO2 calls MS2, barring successful MS1 calls Pre-Paid MS2 with Category OBI1, barring successful Barring of all Incoming Calls Emergency calls
MS make Emergency call with SIM PP-MS make Emergency call with SIM MS make Emergency Call without SIM PP-MS make Emergency call without SIM Other test
T14-90 T14-91 T14-92 T14-93 T14-94 T14-95 T14-96 T14-97 T14-98 T14-99 T14-100 T14-101 T14-102 T14-103 T14-104 T14-105
Originating SMS, MS idle Originating SMS, MS busy Originating SMS, MS detached Originating SMS, MS not reachable Terminating Long (more than 160 characters) SMS Originating SMS Pre-Paid, MS idle Originating SMS Pre-Paid, MS busy Originating SMS Pre-Paid, MS detached Originating SMS Pre-Paid, MS not reachable Terminating Long (more than 160 characters) SMS Pre-Paid MS Retrieve message from Voice-Mail PP-MS Retrieve message from Voice-Mail Pre paid MS call to - Recharge Pre paid MS call to Balance enquiry Remote node connection via OSS RC Collection of counters and alarms via OSS
67
Test
Specification
for
Operation Guide
Call Tracing of call through network possible (CTRAI) Test of Basic Charging
Roaming partners Location Update Testing Revenue assurance Testing Announcement Testing CDR Validation
68
Test
Specification
for
Operation Guide
Test result
Comment
CIC Testing (1 STM-1 to TMSC1) CIC Testing (1 STM-1 to TMSC2) E1 recovery testing Clock board synchronization Traffic control mechanism test Fault/Manual Switch-over Checklist verification (office data audit)
69