BSS17 GSM ATP V17.0 Generic BSC TCUe3 PDF

BSS17 GSM ATP V17.
0 Generic BSC/TCUe3
Document number:
Document status:
Document issue:
Date:
0000003-82-2744
Standard
4
September 25, 2009
External document
Copyright 2009 Nortel Networks, All Rights Reserved
NORTEL NETWORKS CONFIDENTIAL:
The information contained in this document is the property of Nortel Networks. Except as specifically authorized in
writing by Nortel Networks, the holder of this document shall keep the information contained herein confidential
and shall protect same in whole or in part from disclosure and dissemination to third parties and use same for
evaluation, operation and maintenance purposes only.
The content of this document is provided for information purposes only and is subject to modification. It does not
constitute any representation or warranty from Nortel Networks as to the content or accuracy of the information
contained herein, including but not limited to the suitability and performances of the product or its intended
application.
The following are trademarks of Nortel Networks: *NORTEL NETWORKS, the NORTEL NETWORKS corporate
logo, the NORTEL Globemark, UNIFIED NETWORKS. The information in this document is subject to change
without notice. Nortel Networks assumes no responsibility for errors that might appear in this document.
All other brand and product names are trademarks or registered trademarks of their respective holders.
BSS17 GSM ATP V17.0 Generic BSC/TCUe3
0000003-82-2744
PUBLICATION HISTORY
Version:
Status:
Date:
Reason:
V3.00
Standard
February 24, 2009
Initial release
Version:
Status:
Date:
Reason:
V4.00
Standard
September 25, 2009
Restored to Active. Title change.
Nortel Networks confidential
BSS17 GSM ATP V17. 0 Generic BSC/TCUe3
V4. Standard
September 25, 2009 Page 2/59
0000003-82-2744
APPROVALS
This document does not impact any past, present, or future contractual obligations on the part of NORTEL
NETWORKS or CUSTOMER.
The following individuals have reviewed the Acceptance Test Plan and agree in principle.
Signature
Date
Approved by:
Nortel Networks
Scott Cromwell,
Network Integration
---------------------------------------
---------------------
Nader Peyvandi
GMI
--------------------------------------
-----------------------
Jeff Wallgren,
Manager,
GTAC
-------------------------------------
----------------------
V4. Standard
0000003-82-2744
CONTENTS
1.
2.
INTRODUCTION ............................................................................................................................... 6
1.1.
OBJECT ....................................................................................................................................... 6
1.2.
SCOPE ......................................................................................................................................... 6
1.3.
AUDIENCE FOR THIS DOCUMENT ............................................................................................ 6
REQUIREMENTS.............................................................................................................................. 7
2.1.
NETWORK CONFIGURATION FOR ACCEPTANCE TESTING................................................... 7
2.2.
TEST EQUIPMENT ...................................................................................................................... 7
2.3.
PRE-REQUISITS.......................................................................................................................... 7
2.4.
ATP PACKAGE ............................................................................................................................ 8
3.
DEFINITION OF ACCEPTANCE TESTS .......................................................................................... 9
4.
AGREEMENT SHEET ....................................................................................................................... 10

4.1.
TEST SUITE BSC...................................................................................................................... 11
4.1.1
5.
6.
7.
ADDITIONAL WIRING TEST ................................................................................................................. 13
CARD SLOT & CLUSTER NUMBERS.............................................................................................. 14

5.1.
CLUSTER NUMBER CHART: ...................................................................................................... 15
5.2.
VERIFY THE CALL IS ESTABLISHED: ........................................................................................ 15
5.3.
CREATE A SECOND LOGIN ON THE MSC: ............................................................................... 15
5.4.
DELETE SECOND LOGIN ON MSC: ........................................................................................... 15
CIC ACTIVATION.............................................................................................................................. 16
6.1.
CIC TESTING ............................................................................................................................... 17
6.2.
ADDITIONAL CIC TESTS............................................................................................................. 19
GROUP A: TESTS TO BE EXECUTED ON EVERY BSC/TCUE3.................................................... 20

7.1.1
7.1.2
7.1.3
7.1.4
7.1.5
7.1.6
7.1.7
7.1.8
ETHERNET LINK TEST BETWEEN OMUS AND THE OMC-R .......................................................... 20

DUPLEX CAPABILITIES: CEM TCU ..................................................................................................... 21
DUPLEX CAPABILITIES: IEM TCU....................................................................................................... 21
DUPLEX CAPABILITIES: CEM INTERFACE NODE ............................................................................ 23
DUPLEX CAPABILITIES: IEM INTERFACE NODE .............................................................................. 24
DUPLEX CAPABILITIES: 8K ................................................................................................................. 25
DUPLEX CAPABILITIES: ATM .............................................................................................................. 26
DUPLEX CAPABILITIES: OMU ............................................................................................................. 27
V4. Standard

7.1.9
7.1.10
7.1.11
7.1.12
7.1.13
7.2.
CALL TRACE SET-UP.................................................................................................................. 42
8.1.1
8.1.2
8.1.3
8.1.4
8.2.
8.3.
MOBILE TO MOBILE CALL, THEN RELEASE ..................................................................................... 43

MOBILE TO LANDLINE CALL RELEASE BY THE LANDLINE ......................................................... 44
LANDLINE TO MOBILE CALL RELEASE BY THE LANDLINE ......................................................... 45
SUSPEND AND RESUME ..................................................................................................................... 46
E911 ............................................................................................................................................. 47
8.2.1
8.2.2
SINGLE E911 CALL WITH SIM CARD.................................................................................................. 47

SINGLE E911 CALL WITHOUT SIM CARD.......................................................................................... 48
CHECKING THE NSS PARAMETERS FOR AMR........................................................................ 49
PERFORMANCE MANAGMENT TESTING ...................................................................................... 50

9.1.1
10.
BSCE3 CLOCK DRIFT........................................................................................................................... 34

MMS RESET .......................................................................................................................................... 36
CC1 MODULE REPLACEMENT............................................................................................................ 37
PRIVATE MMS REPLACEMENT .......................................................................................................... 38
SHARED MMS REPLACEMENT........................................................................................................... 39
PASSIVE OMU MODULE REPLACEMENT.......................................................................................... 40
TMU MODULE REPLACEMENT ........................................................................................................... 41
V17 BSCE3 CRITICAL CALL TESTING & TRAFFIC MANAGEMENT............................................. 42

8.1.
9.
TMU DEFENSE...................................................................................................................................... 28
AGPRS INTERFACE PCM FAULT........................................................................................................ 29
ABIS INTERFACE PCM FAULT (2S, 10S,)........................................................................................... 31
DEFENSE ON ACTIVE CEM2............................................................................................................... 31
DEFENSE ON ACTIVE IOM .................................................................................................................. 33
GROUP B: TESTS THAT NEED TO BE EXECUTED ON ONE E3 BSC IN EACH MARKET ....... 34
7.2.1
7.2.2
7.2.3
7.2.4
7.2.5
7.2.6
7.2.7
8.
0000003-82-2744
SUCCESSFUL CREATION MDSCANNERS ON A BSCE3 OBJECT. ................................................. 50
T1 ABIS LINK ASSIGNMENTS......................................................................................................... 51

10.1. E1 ABIS LINK ASSIGNMENTS .................................................................................................... 52
10.2. T1 A-LINK ASSIGNMENTS .......................................................................................................... 53
10.3. E1 A-LINKS ASSIGNMENTS ....................................................................................................... 55
10.4. A-TER LINK ASSIGNMENTS ....................................................................................................... 57
V4. Standard
0000003-82-2744
1. INTRODUCTION
1.1.
OBJECT
This document defines the test cases that need to be executed on a BSC/TCUe3 as an acceptance to ensure
proper functionality of these products as it has been defined in Nortel Network specifications and verified by
Nortel VO teams prior to General Availability for deployment in live network.
1.2.
SCOPE
This document lists all test cases that need to be performed as a minimum to verify the functionality of a
BSCe3 and/or TCUe3. This Acceptance Test Plan (ATP) can be applied only on BSC/TCUe3 that has been
installed and commissioned by following the Nortel Networks IMs (Installation Methods).
1.3.
AUDIENCE FOR THIS DOCUMENT
This document is addressed to the Network Integration team and will be provided to Customer for their
approval.
V4. Standard
0000003-82-2744
2. REQUIREMENTS
2.1.
NETWORK CONFIGURATION FOR ACCEPTANCE TESTING

OMC-R
Ethernet Switch
BSce3
CN
TCUe3
TCUe3
TCUe3
BSCe3
IN
BSCe3
IN
MSC1
MSC2
BTS
2.2.
BSCe3
CN
BTS
TEST EQUIPMENT
Mobile phones
TEMS
2.3.
PRE-REQUISITS
Ensure that all links / trunks are built and in-service.

Verify that the Tellabs Titan 5500 timing is set for "Internal"
V4. Standard
2.4.
0000003-82-2744
ATP PACKAGE
The ATP package contains the ATP, two password generators, and checklists for an E1 and T1 network and a
.sh file to un-lock the cics.
The ATP Package can be found at the following LiveLink:
http://livelinkott.ca.nortel.com/livelink/livelink.exe/82%2D1564_Generic_BSC_TCUe3_Acceptance_Test_Plan.pdf?func=doc
.fetch&nodeId=24717916&viewType=1
The Checklists and Password Generator can be found at the following LiveLink:
http://livelinkott.ca.nortel.com/livelink/livelink.exe?func=ll&objId=23164748&objAction=browse&sort=name&viewType=1
1. Password Generators:
A).To use the cempass.xls, type in the date and hit enter, and then click on generar passw cem.
B). Rename the DMS PW decoder.txt to DMS PW decoder.exe, open the PW decoder and click on decode.
2. Shell command
A). FTP the ww_cic.sh to /OMC/cmdFile/root on the server; see section CIC Activation for usage.
3. Checklists
A). Use either the E1 or T1 checklist to keep track of the tests completed.
V4. Standard
0000003-82-2744
3. DEFINITION OF ACCEPTANCE TESTS

Following successful commissioning of BSC/TCUe3, Nortel Networks will perform Acceptance Test Plan (ATP).
The aim of this Acceptance testing is to ensure:
a) Proper operation of the hardware and software as a stand-alone test.
b) Proper functional interaction of the interfaces and message transfers between BSCe3 and TCUe3
each as a network element to the neighboring elements.
V4. Standard
0000003-82-2744
4. AGREEMENT SHEET
By signing this sheet, both parties, Customer and NORTEL NETWORKS agree that:
All test cases defined in this ATP (Acceptance Test Plan) have been executed properly except those
that have been identified as Not Applicable.
The testing had been scheduled by both parties in advance. If the Customer representative chose not
to witness the test, Nortel Networks Integration team would have performed the test as it was
scheduled.
All tests have passed the expected criteria. If a test case has failed, an SR (Service Request) has
been opened and routed to appropriate support organization to be resolved.
All issues have been identified and addressed to be resolved within agreed time frame.
Customer representative:
Name / Market
Signature
Date
--------------------------
-------------------------------
------------------
Nortel Networks representative:

Name
Signature
Date
----------------------------
-------------------------------
-------------------
V4. Standard
September 25, 2009Page 10/59
4.1.
0000003-82-2744
TEST SUITE BSC
WIRING TEST
No.
4.1.1
Test Title
Cabling Verification
6.1
CIC Testing
6.2
Additional CIC Testing
Date
Result
Comments
BSCE3 HARDWARE AND ROBUSTNESS TESTS

No.
Test Title
Date
7.1.1
Redundant Ethernet Link Test b/w E3 and OMCR
7.1.2
Duplex capabilities: CEM TCU
7.1.3
Duplex capabilities: IEM TCU
7.1.4
Duplex capabilities: CEM IN
7.1.5
Duplex capabilities: IEM IN
7.1.6
Duplex capabilities: 8K
7.1.7
Duplex capabilities: ATM
7.1.8
Duplex capabilities: OMU
7.1.9
TMU Defense
7.1.10
AGPRS Interface PCM Fault
7.1.11
A-Bis Interface PCM Fault
7.2.1
BSC E3 Clock Drift
7.2.2
MMS Reset
7.2.3
CC1 Module Replacement
7.2.4
Private MMS Replacement
7.2.5
Shared MMS Replacement
7.2.6
Passive OMU Module Replacement
7.2.7
TMU Module Replacement
Result
Comments
V4. Standard
0000003-82-2744
CRITICAL CALL TESTING & TRAFFIC MANAGEMENT

No.
Test Title
Mobile
Location
Verified
8.1.1
MS to MS then Release
8.1.2
MS to Landline, Release by Landline
8.1.3
Landline to MS, Release by Landline
8.1.4
Suspend and Resume MS Originate
8.2.1
E119 Call with SIM Card
8.2.2
E1191 Call without SIM Card
8.3
Check the AMR parameters on NSS side
9.1.1
Creation of different type of mdScanners
Date
Result
Comments
V4. Standard
4.1.1
0000003-82-2744
ADDITIONAL WIRING TEST
DESCRIPTION
The aim of this test is to ensure that all PCM cables between BSC/TCUe3 and DSX panels are installed
properly and there is no crossed wire or bad connections.
INITIAL CONDITIONS
1.
2.
3.
All PCM links are wired between BSC/TCUe3 and DSX panel.
The OMC-R is up and running
All un-used PCMs on both the BSC and TCU are created.
REQUIREMENTS
1.
2.
Patch cords and the latest BDIQ.

Access to OMC-R and MSC.
ACTION
1. For all LSAs newly-installed in the system, create un-referenced pcm objects for every real PCM link
at the OMC-R. The first six pairs of each LSA are created as A-ter and the rest are as A-bis on the
BSC object, on the TCU object create A-Interface links. Refer to section 10 for ABIS, A-Link, and
ATer assignments
2. Un-Lock all PCMS and at the DSX panel, patch a group of 4 PCM links from one LSA to 4 PCM links
on the MSC; observe that all links come in-service.
RESULT
No Tip/Ring reversals or bent pins on the LSA cables and all PCM links come in-service properly.
V4. Standard
0000003-82-2744
5. CARD SLOT & CLUSTER NUMBERS

dSH> idmdb/qidm
Current Date/Time: 2006/11/15 10:20:38.575
CEM 0 is Active
Slot: 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2
1 2 3 4 5 6 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8
--------------------------------------------------------------------------DevType:
I I
I I S S
I I
I I A A
I I
I I
E E
E E R R
E E
E E T T
E E
E E
M M
M M T T
M M
M M M M
M M
M M
0 0
0 0 0 1
1 1
1 1 1 2
2 2
2 2
2 3
5 6 9 0
3 4
7 8 9 0
3 4
6 7
--------------------------------------------------------------------------S
Control:
S S
S S S S
S S
S S S S
S S
S S
R T
CEM Target:
R R
R R R R
R R
R R R R
R R
R R
M A
Service State:
I I
I I I I
I I
I I I I
I I
I I
T
Fault:
- - - - - - - - - - E
Work Mode:
A I
I A I A
I A
I A I A
I A
I A
Alarm:
- - - - - - - - - - Action Pending:
- - - - - - - - - - --------------------------------------------------------------------------MIP raise:
. .
. . . .
. .
. . . .
. .
. .
MIP owner:
SW run mode:
T T
T T T T
T T
T T T T
T T
T T
dSH> slinkhal/scanrm
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
cluster
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
(slot
25) : RM_NOT_INSERT,
24) : RM_INSERT_ON, In-Frame
1) : RM_NOT_INSERT,
1) : RM_NOT_INSERT,
1) : RM_NOT_INSERT,
2) : RM_NOT_INSERT,
2) : RM_NOT_INSERT,
4) : RM_NOT_INSERT,
5) : RM_NOT_INSERT,
|
|
|
|
CLUST_FULL_ENABLED
CLUST_FULL_ENABLED
CLUST_FULL_ENABLED
CLUST_FULL_ENABLED
|
|
|
|
CLUST_FULL_ENABLED
CLUST_FULL_ENABLED
CLUST_FULL_ENABLED
CLUST_FULL_ENABLED
| CLUST_FULL_ENABLED
|
|
|
|
|
CLUST_FULL_ENABLED
CLUST_FULL_ENABLED
CLUST_FULL_ENABLED
CLUST_FULL_ENABLED
CLUST_FULL_ENABLED
V4. Standard
5.1.
0000003-82-2744
CLUSTER NUMBER CHART:
Card Type
Slot #
IEM #
Cluster #
Card Type
Slot #
IEM #
Cluster #
LsaRc 5
34
LsaRc 112
26
111
(LSA 0)
33
(LSA 3)
27
113
LsaRc 103
17
102
LsaRc 13
13
12
12
(LSA 1)
18
104
10
(LSA 4)
14
14
13
LsaRc 109
23
108
LsaRc 2
20
(LSA 2)
24
110
(LSA 5)
28
8K
Sw8kRm 9
32
ATM
19 (atmRm 105)
Sw8kRm 10
25
20 (atmRm 106)
5.2.
VERIFY THE CALL IS ESTABLISHED:
1. Connect to the serving MSC: telnet <MSC_ ip @>

GMSSRCH MSISDN 18684876754
5.3.
CREATE A SECOND LOGIN ON THE MSC:
permit nortelbss
111111
(Create Password)
111111
(Verify Password)
Hit enter twice for full privileges.
5.4.
(Create UserId)
DELETE SECOND LOGIN ON MSC:
> unpermit nortelbss
(Delete UserId created above)
V4. Standard
0000003-82-2744
6. CIC ACTIVATION
On TCU:
Unlock and bring into service all XTPs.
Connect to the OMC-R server: telnet <serv_ ip @>
Run ww_cic.sh, this will create a command file (cic_ulck.sh) and place it in /OMC/cmdFile/root.
/OMC/cmdFile/root
ww_cic.sh <BSC Number> <Start CIC> <End CIC> <Admin State>
Example: ww_cic.sh 36 1024 1992 unlocked
run command file cic_ulck.sh
On MSC:
Bring into service all concerned CICs
Connect to the serving MSC: telnet <MSC_ ip @>
Table TRKGRP
List all
(find trkgrp name associated with the BSC under test)
MAPCI;MTC;TRKS;TTP;POST G THOME3BSC25 <Start CIC> to <End CIC>
2
to 384
bsy all
rts all
RESULT
All CICs on the TCUs and MSC are in the idle state.
V4. Standard
6.1.
0000003-82-2744
CIC TESTING
DESCRIPTION
The purpose is to verify that the CICs on the MSC and TCU align by making test calls on one or more specific
CICs on each span.
STEPS
1.
2.
3.
4.
5.
Find the IMSI of the test phone

Add the IMSI of the test phone in Table CICTEST.
Find the name of the Routeset.
Access CICTEST tool, turn it on, and delete all isolated CICs and the isolate CIC to be tested.
Create a temporary login on the MSC if you only have one available.
ACTION
1.
gmssrch msisdn 19724148493

(obtain the IMSI number)
Table CICTEST
(If their is an different IMSI data-filled delete it first)
add 374129000231450
Table TRKGRP
List all
(find trkgrp name associated with the BSC under test)
MAPCI;MTC;TRKS;TTP;POST G THOME3BSC25 149
C7TTP
ROUTESET
(Displays routeset name e.g. THOME3BSC25RS)
CICTEST
The CICTEST CI tool is used to turn ON/OFF the CIC Isolation Tool. This tool is used to isolate A-interface CICs from the
Voice pool for testing.
help
Available CICTEST subcommands:

ON
Turns ON the CIC Isolation Tool
OFF
Turns OFF the CIC Isolation tool
ADD <routeset><cic>
Isolates the given CIC
DELETE <routeset><cic>:
Deletes the isolated CIC
DISPLAY
Displays the test resources
HELP
display this help
QUIT
exits CICTEST
Test Resources reserved for CIC Isolation tool are:
CIC Isolation Tool is: ON
Test IMSIs data filled in Table CICTEST:
374129000231450
Isolated Test Routesets and Test CICs are given below:
1st Set of Test Resources
--------------------------Routeset
: THOME3BSC25RS
CIC
: 2473
CIC Availability: Y
To make it easier to perform the CIC testing, open two login windows on the MSC.
Create a second login on the MSC
In the first login window post the TTP that will be tested
V4. Standard
0000003-82-2744
MAPCI;MTC;TRKS;TTP;POST D MGW 152 129
In the second login window access the tool CICTEST and isolate the CIC to be tested.
CICTEST
add THOME3BSC25RS 129
on
Place a call and verify voice and that the TTP has gone into the CPB state.
Verify the call is on the right Cell.
GMSSRCH MSISDN 18684876754
Terminate the call and in CICTEST delete THOME3BSC25RS 129.
Repeat steps 2 to 5 for each CIC to be tested and record which CICs were tested on the
Checklist.
V4. Standard
BSC
6.2.
0000003-82-2744
ADDITIONAL CIC TESTS

2. Verify on the MSC for a T1 network that the following CICs are properly defined as SigLinks:
1, 25, 529, 553, 1057, 1081, 1585, 1609, 1921, 1945, 2451, 2473, 2977, 3001
e.g.
post d spm 1 553,
or
post d mgw 1 553
3. Verify on the MSC for a E1 network that the following CICs are properly defined as SigLinks:
1, 33, 513, 545, 1025, 1057, 1537, 1569, 1921, 1953, 2433, 2465, 2945, 2977
4. Additional CICs that should not be data-filled on the MSC for an E1 Network:
TCU 0:
32, 64,65, 96, 128, 160, 192, 224, 256, 288, 320, 352, 384, 416, 448, 480, 512, 544, 576, 577, 608, 640,
672, 704, 736, 768, 800, 832, 864, 896, 928, 960, 992, 1024, 1056, 1088, 1120, 1152, 1184, 1216, 1248,
1280, 1312, 1344, 1376, 1408, 1440, 1472, 1504, 1536, 1568, 1600, 1632, 1664, 1696, 1728, 1760, 1792,
1824, 1856, 1888, 1920,
TCU 1:
1952, 1984, 2016, 2048, 2080, 2112, 2144, 2176, 2208, 2240, 2272, 2304, 2336, 2368, 2400, 2432, 2464,
2496, 2528, 2560, 2592, 2624, 2656, 2688, 2720, 2752, 2784, 2816, 2848, 2880, 2912, 2944, 2976, 3008,
3040.
4. Using the BDIQ verify that each span has all their CICs in the idle state or CPB state.
querypm spm 2 15, or querypm mgw 2 15
V4. Standard
0000003-82-2744
7. GROUP A: TESTS TO BE EXECUTED ON EVERY

BSC/TCUE3
These tests are divided in two categories:
A) Tests that need to be executed on every BSC/TCUe3
B) Tests that need to be executed only once in each market
7.1.1
ETHERNET LINK TEST BETWEEN OMUS AND THE OMC-R
The OMU Module manages the Control, Interface and Transcoder Nodes. Supervises both the BSC and TCU
cabinets and manages the SCSI disks and the interfaces with the OMC-R and also provides system
maintenance.
DESCRIPTION
The purpose of this test case is to test the redundant Ethernet links between the OMC-R and OMUs on the
BSC e3.
INITIAL CONDITIONS
1. OMUs are in Duplex
ACTION 1
1. On the OMCR GUI, perform a display all on the BSC object to show real-time data
2. Disconnect the Ethernet cable from the Active OMU and do a display on the same parameter after the link
recovers.
NOTE: The required time to wait before cable is put back would be around 15 minutes.
RESULT 1
1. When the Ethernet connection is lost on the active OMU, it is reset causing the passive OMU to assume the
active role.
V4. Standard
7.1.2
0000003-82-2744
DUPLEX CAPABILITIES: CEM TCU
The CEM (Common Equipment Module) controls the LSA-RC, 8K-RM, ATM-RM modules and the traffic
switching functions. It also provides Clock synchronization and access to system maintenance via TML.
DESCRIPTION
Verify the ability for the system to keep the calls established during a swact (or multi-swact) on the active CEM,
and to report correctly the fault to the operator.
INITIAL CONDITIONS
1. The TCU is running in CEM duplex mode.
ACTION
1. Connect to the active CEM: telnet <CEM_ ip @>
2. If the CEMs are not on the network telnet to the active OMU: telnet <OMU_ ip @>
3. Use the following IPs to connect to the Active CEM on the TCU under test.
TCU 0: 172.252.1.100, TCU 1: 172.252.1.101
4. Check the state of the CEM, type: dSH> /inmci/dump data
a. If the state is INSV ACTIVE it means the board is active.
b. If the state is INSV INACTIVE it means the board is passive.
5. Set up a call and verify it is on test BTS.
NOTICE: When you login to a CEM first time, you cannot do certain commands, so you need to access the
root level: su root (password) to obtain the daily password run cempass.xls
1. On the active CEM Debug Shell perform the command in order to reset the active CEM
reset soft
2. Wait for the state change at the OMC-R to indicate that the CEM is enabled.
3. Stop the call.
RESULT
The active CEM is reset causing the passive CEM to assume the active role, during the swact the call will
remain up.
7.1.3
DUPLEX CAPABILITIES: IEM TCU
The IEM (Interface Electronic Module) transmits and converts the PCM (E1/T1) line coded signals to the CEM
module. It also provides clock and frame recovery, alarm recovery, alarm detection, line coding, mapping the
PCM information onto the S-Link and provides a diagnostic interface.
INITIAL CONDITIONS
DESCRIPTION
Verify the ability for the system to keep the calls established during a swact (and multi-swacts) on the active
IEM in a LSA-RC module, and to report correctly the fault to the operator.
INITIAL CONDITIONS
1. The TCU is running in CEM duplex mode.
2. The selected LSA module for testing is in duplex mode.
V4. Standard
0000003-82-2744
ACTION
2. If the CEMs are not on the network telnet to the active OMU: telnet <OMU_ ip @>
3. Use the following IPs to connect to the Active CEM on the TCU under test.
TCU 0: 172.252.1.100, TCU 1: 172.252.1.101
4. Check the state of the CEM, type: dSH> inmci/dump data
a) If the state is INSV ACTIVE it means the board is active.
b) If the state is INSV INACTIVE it means the board is passive.
NOTICE: When you login to a CEM the first time, you cannot do certain commands, so you need to access the
root level: su root (password) to obtain the daily password run cempass.xls
5. On the active CEM, check the state of the IEM, type:

dSH> idmdb/qidm
6. For each lsaRc group, the active IEM board (slots 5 & 6) is in SRI-A state which means: in service, without
any fault and active, and the passive are in SRI-I which means passive.
7. Knowing the slot number of the active IEM, obtain the cluster number with the following command:
dSH> slinkhal/scanrm
8. In order to force the call thru the IEM under test it is necessary to isolate one of the CICs. Refer to the ALink assignment charts and select one of the A-Links associated with that LSA.
9. On the OMC-R GUI, open the selected A-link and select a XTP to isolate.
10. Refer to section 6 to isolate CIC to be tested.
12. On the active CEM Debug Shell perform the command:
dSH> slinkhal/injclusterflt <cluster number> 0 to simulate a critical fault on the active IEM.
13.
14.
15.
16.
17.
Wait for the state change to indicate that the IEM has failed.
Check the call is still on-going.
Wait for the end of the new passive IEM board restart (approximately 7 minutes).
Hang-up the call.
Repeat test for each LSA on TCU 0 and TCU 1.
RESULT
1. The active IEM is reset causing the passive IEM to assume the active role, during the swact the call will
remain up.
V4. Standard
7.1.4
0000003-82-2744
DUPLEX CAPABILITIES: CEM INTERFACE NODE
The CEM (Common Equipment Module) controls the LSA-RC, 8K-RM, ATM-RM modules and the traffic
switching functions. It also provides Clock synchronization and access to system maintenance via TML.
DESCRIPTION
CEM, and to report correctly the fault to the operator.
INITIAL CONDITIONS
1. The CEMs are in duplex mode.
ACTION
Notice: When you login to a CEM first time, you cannot do certain commands, so you need to access the root
level: su root (password) to obtain the daily password run cempass.xls
4.
5.
6.
7.
8.
9.
Reset the active CEM: reset soft

Wait for the state change to indicate that the CEM has failed.
Check the call is still ongoing.
Wait for the state change to indicate that the board is restarted.
Terminate the call.
Repeat steps 1 to 5 for second CEM.
RESULT
The active CEM is reset causing the passive CEM to assume the active role, during the swact the call will
remain up.
V4. Standard
7.1.5
0000003-82-2744
DUPLEX CAPABILITIES: IEM INTERFACE NODE
The IEM (Interface Electronic Module) transmits and converts the PCM (E1/T1) line coded signals to the CEM
module. It also provides clock and frame recovery, alarm recovery, alarm detection, line coding, mapping the
PCM information onto the S-Link and provides a diagnostic interface
DESCRIPTION
IEM in an lsaRc, and to report correctly the fault to the operator.
INITIAL CONDITIONS
ACTION
Notice: When you login to a CEM first time, you cannot do certain commands, so you need access the root
3. On the active CEM, check the state of the IEM, type: dSH > idmdb/qidm
4. For each lsaRc group, the active IEM board is in SRI-A state which means: in service, without any fault and
active, and the passive are in SRI-I which means passive.
5. Knowing the slot number of the active IEM, obtain the cluster number with the following command: dSH>
slinkhal/scanrm
6. A list of clusters number corresponding to slot number appears in the Debug Shell.
7. In order to force the call thru the IEM under test it will be necessary to lock down all A-Ter links not
associated with that IEM, refer to the table LSA A-Ter Link assignments.
dSH> slinkhal/injclusterflt <cluster number> 0 to simulate a critical fault sent by the
active IEM.
10. Wait for the state change to indicate that the IEM has failed.
11. Check the call is still on-going.
10. Wait for the state change to indicate that the board is restarted.
11. Terminate the call.
12. Repeat steps 1 to 14 for the second IEM on the LSA under test.
13. Repeat test for each LSA provisioned on the Interface Node.
RESULT
1. The active IEM is reset causing the passive IEM to assume the active role, during the swact the call will
remain up.
V4. Standard
7.1.6
0000003-82-2744
DUPLEX CAPABILITIES: 8K
The 8K Module is an application-specific circuit module that performs a timeswitch function on sub-DSO rate
channels, allowing for the efficient switching of 8 and 16 k
DESCRIPTION
8K, and to report correctly the fault to the operator.
INITIAL CONDITIONS
ACTION
3. Check the state of the 8K, type: dSH> idmdb/qidm.
The active 8K board (slots 9 or 10) is in SRI-A state which means: in service, without any fault and active. The
passive is in SRI-I which means passive, note the 8K slot with a SRI-A status
4. Knowing the slot number of the active 8K, obtain the cluster number with the following command: dSH>
slinkhal/scanrm
5. A list of clusters number corresponding to slot number appears in the Debug Shell
6. Set up a call on the test BTS, and verify it is on test BTS.
dSH> slinkhal/injclusterflt <cluster number> 0 to simulate a critical fault on the active
8K.
8. Wait for the state change to indicate that the 8K has failed
9. Check the call is still on-going.
10. Wait for the end of the new passive 8K board restart.
11. Repeat steps 1 to 11 for second 8K under test,
RESULT
1. The active 8K is reset causing the passive 8K to assume the active role, during the swact the call will remain
up.
V4. Standard
7.1.7
0000003-82-2744
DUPLEX CAPABILITIES: ATM
The ATM-RM module provides OC-3 connectivity between the IN and CN modules. It also converts ATM/AL-1
and ATM/AL-5 cells into DSO rate channels and ATM/AL-5 packets into intra-node messaging.
DESCRIPTION
Validate the ability for the system to keep the calls established during a swact (and multi-swacts) on the active
ATM-RM and to report correctly the fault to the operator.
INITIAL CONDITIONS
1. Both ATM-RM are in operational state.
ACTION
3. Check the state of the ATM-RM, type dSH> idmdb/qidm
4. The active ATM-RM board is in SRI-A state, which means: in service, without any fault and active. The
passive is in SRI-I, which means passive.
5. Knowing the slot number of the active ATM, obtain the cluster number by using the following
command: dSH> slinkhal/scanrm
6. A list of clusters number corresponding to slot number appears in the Debug Shell.
dSH> slinkhal/injclusterflt <cluster number> 0 to simulate a critical fault on the
active ATM.
9. Wait for the state change to indicate that the ATM has failed.
10. Check the call is still ongoing.
11. Repeat steps 2 to 11 for the second ATM card.
RESULT
1. The active ATM is reset causing the passive ATM to assume the active role, during the swact the call will
remain up.
V4. Standard
7.1.8
0000003-82-2744
DUPLEX CAPABILITIES: OMU
The OMU (Operation and Maintenance Unit) manages the Control, Interface and Transcoder Nodes.
Supervises both the BSC and TCU cabinets and manages the SCSI disks and the interfaces with the OMC-R
and also provides system maintenance
DESCRIPTION
Verify the ability for the system to keep the calls established during a swact on the active OMU, and to report
correctly the fault to the operator.
INITIAL CONDITIONS
1. The BSC e3 is running in duplex OMU.
ACTION
1. Connect to the active OMU telnet<OMU_ip @>
user: omu or root
password: omu or root
2. Perform the command: msgViOmuState to check the state of the OMU.
4. Execute the following command on the active OMU, in order to perform a swact OMU :
bos_suicide
5. Wait at the OMC-R for the state change notification in notification monitor window about the BSC
MdInterface and the BSC object.
7. Wait for the recovery of the BSC MdInterface.
8. Wait for the state change to indicate the OMU has been enabled.
9. Then in case of multi-swact testing, repeat steps 1 to 5.
RESULT
1. When the Ethernet connection is lost on the active OMU, it is reset causing the passive OMU to assume the
active role.
V4. Standard
7.1.9
0000003-82-2744
TMU DEFENSE
The TMU (Traffic Management Unit) manages processing power for the GSM CallP, terminates the GSM
protocols for A, Abis, Ater and Agprs interfaces. It also terminates the low level of the GSM protocols Lapd and
SS7.
DESCRIPTION
The purpose is to monitor and verify LWP (Light Weight Processing) active/passive on the TMU does not lose
Call Processing from the result of a TMU shutdown.
INITIAL CONDITIONS
1. All TMU cards are in operational state.
ACTION
user: root
password: root
3. Perform a display Dynamic data on the BTS/SiteManager to find which TMU (TMU Shelf/TMU slot)
manages the co-located call Processing
4. On the TMU managing the co-located BTS, disable it with the software command:
a. If OMU 5 is active, example: rbckp 172.37.2.1 reset <shelf><slot>
rbckp 172.37.2.1 reset 1 12

b. If OMU 9 is active, example: rbckp 172.41.2.1 reset <shelf><slot>
rbckp 172.37.2.1 reset 1 12

5. Verify that the TMU has been stopped and the Cell is now being processed by another TMU.
6. The TMU card should come back into service in about 5 minutes.
7. Repeat step 2 through step 6 for another 2 TMUs that are actively supporting the test cell.
RESULT
1. The TMU is disabled, and the call is handed off to another TMU.
V4. Standard
7.1.10
0000003-82-2744
AGPRS INTERFACE PCM FAULT
DESCRIPTION
The aim is to verify the PCM supervision and defense functions in case of Agprs PCM disconnection.
INITIAL CONDITIONS
1. PCUSN is operational
2. To perform with the co-located BTS
ACTION
1. Lock the Agprs PCM carrying the Signaling link to the PCUSN.
2. Connect to the PCUSN telnet<PCUSN_ip @>
3. Check which DS1 has a SigLink
d -p ns
NS
primaryReference = Lp/5 DS3/0 DS1/1
secondaryReference = Lp/5 DS3/0 DS1/11
tertiaryReference = Lp/5 DS3/0 DS1/18
useableReferences = enabled
reversionDelay
= 0 minutes
ssmProtocol
= disabled
ok
2007-04-30 13:28:31.63
4. Check which PCM the DS1 is assigned to:
d p lp/* ds3/* ds1/* ch/0 applicationFramername
ok
Lp/* DS3/* DS1/* Chan/0

+==+===+===+--------------------+------------------------------------|Lp|DS3|DS1|applicationFramerNam|Response
| |
|
|
e
|
+==+===+===+--------------------+------------------------------------| 5| 0| 1|Pcusa/1 Conn/40
|
| |
|
| PcmLk/26
|
| 5| 0| 2|Pcusa/1 Conn/40
|
| |
|
| PcmLk/27
|
.
.
.
| 5| 0| 11|Pcusa/1 Conn/40
|
| |
|
| PcmLk/81
|
| 5| 0| 12|Pcusa/1 Conn/40
|
| |
|
| PcmLk/80
|
.
.
.
| 5| 0| 18|Pcusa/1 Conn/40
|
| |
|
| PcmLk/138
|
| 5| 0| 19|Pcusa/1 Conn/40
|
| |
|
| PcmLk/137
|
| 5| 0| 20|Pcusa/1 Conn/40
|
| |
|
| PcmLk/136
|
.
.
2007-04-30 13:29:42.18
V4. Standard
0000003-82-2744
5. Check which PCM has the siglink on the Cell under test:
d pcusa/* conn/* pcm/* cgicell/lac,cell
d pcusa/* conn/* pcm/* cgicell/440,33193
ok
6.
7.
8.
Pcusa/* Conn/* PcmLk/* CgiCell/440,33193

Use -noTabular to see the many hidden attributes.
+=====+====+=====+-----+------+---+---+------------------------------------|Pcusa|Conn|PcmLk|cellB|state |mCC|mNC|Response
|
|
|
| VCI |
|
|
|
+=====+====+=====+-----+------+---+---+------------------------------------|
1| 40|
81| 1216|inServ|374| 12|
2007-04-30 13:59:45.48
On the OMC-R GUI: lock the AGPRS PCM that is carrying the Signaling Link
Wait for the state change in the notification monitor windows, at the OMC-R.
Un-lock the Agprs PCM.
RESULTI
The Signaling Link will move to another AGPRS Link.
V4. Standard
7.1.11
0000003-82-2744
ABIS INTERFACE PCM FAULT (2S, 10S,)
DESCRIPTION
Check the defense action from BSCe3, when the disconnections on the Abis interface are executed. The times
for the disconnections are 2 sec and 10 sec.
INITIAL CONDITIONS
1. The BSCe3 is running in OMU duplex mode.
ACTION
Fault on Abis: 2 seconds
2. Disconnect the Abis PCM for 2 seconds.
3. After the reconnection, check the call is still on going.
Fault on Abis: 10 seconds
2. Disconnect the Abis PCM for 10 sec, and check the call is lost.
3. Wait for the recovery of the BTS.
RESULT
Fault on Abis: 2 sec
While there is no detection by the BSC, there is no defense action. The voice is lost during the disconnection.
Fault on Abis: 10 sec
1. When the Fault crosses the threshold (5 sec) the site will drop and recover after the PCM is reconnected.
7.1.12
DEFENSE ON ACTIVE CEM2
OVERVIEW
The aim of this test is to check the behavior of the Optical BSC3000 when removing the active CEM2 (hot remove or
swact action)
PREREQUISITES
The OMC-R is operational in V17
The Optical BSC3000 is running without issue
CONFIGURATIONS
1 Optical BSC3000 with its TCU3000 and PCUSN

At least 1 BTS linked to HSA 0
1 MS for GSM call
1 PC with TML software installed + associated cables
V4. Standard
0000003-82-2744
ACTIONS
1.
Perform a GSM call
2.
Unplug the active CEM2 board
3.
Connect the TML on the new active CEM2
4.
Check the boards states
6.
Plug the remaining CEM2
7.
Check the redundancy with the TML capabilities once the CEM2 are all up and running
8.
Reset the active CEM2 with the TML
9.
Connect the TML on the new active CEM2
10. Wait for the new passive to be up and running and check the board status with the TML
11. Check that for each unplug or board restart, the corresponding notifications are raised (see [R2] and [R3] for
details on notifications)
12. Check that the call is still present
EXPECTED RESULTS:
1. The call is established successfully
2. When the CEM2 is unplugged the call is still present
3. TML is connected to the active CEM2 without issue
4. The BSC is simplex from the IN point of view, only 1 CEM2 is available
5. CEM2 is plugged with no issue
6. Both CEM2 are up and running (BSC3000 is in duplex mode)
7. The old active CEM2 is reseted with the TML
8. TML is connected to the new active CEM2 without issue
9. New passive is up and running (BSC3000 is in duplex mode)
10. All notifications are send to the OMC-R
11. The call is not ended
EXIT CRITERIA
BSC is operational, all boards are up and running
All notifications are sent to the OMC-R
The call is performed successfully
V4. Standard
7.1.13
0000003-82-2744
DEFENSE ON ACTIVE IOM
OVERVIEW
The aim of this test is to check the behavior of the Optical BSC3000 when removing the active IOM (hot remove or
swact action)
PREREQUISITES
The OMC-R is operational in V17.
The Optical BSC3000 is available
The MUX is up and running and the synchronization is good and stable
CONFIGURATIONS
1 Optical BSC3000 with its TCU3000 and PCUSN

At least 1 BTS linked to HSA 0
1 MS for GSM call
1 PC with TML software installed + associated cables
ACTIONS
1.
Establish a GSM call
2.
Unplug the active IOM board
3.
Connect the TML on the active CEM2
4.
Check the boards states
5.
Plug the remaining IOM
6.
Check the redundancy with the TML capabilities once the IOM are all up andvrunning
7.
Reset the active IOM with the TML
8.
Wait for the new passive to be up and running and check the board status withvthe TML
9.
Check that for each unplug or board restart, the corresponding notifications arevraised (see [R2] and [R3] for
details on notifications)
10. Check that the call is still present
V4. Standard
0000003-82-2744
EXPECTED RESULTS:
1. The call is established
2. When the IOM is unplugged the call is still present
3. TML is connected to the active CEM2 without issue
4. The BSC has only one IOM running
5. IOM is plugged without issue
6. Both IOM are up and running
7. The active IOM is reseted with the TML without issue
8. New passive is up and running
9. All notifications are send to the OMC-R
10. The call is not ended
EXIT CRITERIA
BSC is operational, all boards are up and running
All notifications are sent to the OMC-R
The call is performed successfully
7.2.
GROUP B: TESTS THAT NEED TO BE EXECUTED ON ONE E3 BSC IN EACH

MARKET
7.2.1
BSCE3 CLOCK DRIFT
DESCRIPTION
The purpose of this test case is to check the correct detection and the alarm display in case of BSCe3 clock
drift.
INITIAL CONDITIONS
1. BSCe3 is up and operational.
V4. Standard
0000003-82-2744
ACTION
user: root
password: root
2. Check for active OMU by typing: msgViOmuState
3. Modify the BSCe3 time, using the date command example: date 10080045
(Equates to Oct 8th 12:45 AM]
4. Wait for the detection of this time inconsistency between the OMC and the BSCe3, may take considerable
time, be patient.
Note: Date is automatically reconfigured and only a notification is sent.
RESULT
1. Once the notification is received, verify the correct date is restored
V4. Standard
7.2.2
0000003-82-2744
MMS RESET
The MMS (Mass Memory Storage) module houses the data and software repositories.
DESCRIPTION
Verify the procedure for resetting a MMS board.
INITIAL CONDITIONS
1. System is up and operational with both OMUs and all MMSs are in-service.
ACTION
user: root
password: root
2. Enter the command: lsvg -l std_mirvg
(Check the state and configuration of the shared disks)
std_mirvg:
LV NAME
TYPE
std_mirvglvlog
jfslog
std_mirvg_LV0
jfs
/OMU_STORAGE/SHARE
std_mirvg_LV1
jfs
/OMU_STORAGE/log/share
std_mirvg_LV2
jfs
/OMU_STORAGE/fault/share
std_mirvg_LV3
jfs
/OMU_STORAGE/rw_data/share
LPs
1
167
119
PPs
PVs
1
167
119
1
1
LV STATE
MOUNT POINT
1
open/syncd
N/A
open/syncd
open/syncd
119
119
open/syncd
44
44
open/syncd
3. On one of the shared MMS, press the Removal Request Button.

4. Wait until the red LED starts to flash,
RESULT
1. The MMS red LED starts to flash.
2. The MMS red LED should flash for fifteen minutes signifying it is ready for removal and then returns to
normal condition.
V4. Standard
7.2.3
0000003-82-2744
CC1 MODULE REPLACEMENT
The CC1 is an ATM switch that implements the ATM network used as the Control Node backplane. It also
provides OC-3 connectivity towards to Interface node.
DESCRIPTION
Validate the ability of the system to keep calls established during the replacement of a CC1 module.
INITIAL CONDITIONS
1. Both CC1 modules are in operational state.
ACTION
user: omu
password: omu
3. Check the state of the OMU: msgViOmuState
4. Reset on the CC1 associated with the passive ATM:
rbckp omu_<slotNbrOfActiveOmu>_tm reset <CC1shelfNbr> <CC1slotNbr>

a. eg.
5.
6.
7.
8.
rbckp omu_5_tm reset <shelf><slot>

rbckp omu_5_tm reset 1 8
or
rbckp omu_9_tm reset <shelf><slot>
rbckp omu_9_tm reset 1 8
Wait for the state change to indicate that the CC1has failed.
Check the call is still on-going.
During the CC1 reset, unplug the CC1 and insert the replacement CC1.
Wait for the state change to indicate that the CC1 is came back in service.
RESULT
1. The call will remain up during the reset and replacement of the passive CC1.
V4. Standard
7.2.4
0000003-82-2744
PRIVATE MMS REPLACEMENT
DESCRIPTION
Validate the ability of the system to keep calls established during the replacement of a private MMS.
INITIAL CONDITIONS
1. System is up and operational with both OMUs and all MMSs in-service.
ACTION
2. The MMS to be replaced is in slot 5 or slot 10, pick the one corresponding to the passive OMU.
3. Remove the filler that is located in slot 7 for the Private MMS in slot 5 or slot 8 for the Private MMS in
slot 9 of shelf 0 of the Control Node.
4. Insert a new MMS module in slot 7 or 8 of shelf 0 of the Control Node.
5. Extract the updated spare MMS module.
6. Extract the private MMS module identified in step 3 following the steps below:
a. If the private MMS module is operational you must first isolate the hard disk by pressing with a
ballpoint pen the Removal request pushbutton located on the front panel of the module.
b. Wait until the red LED starts to flash,
c. Extract the MMS module.
8. Insert the filler module in slot 7 or 8 and then insert the updated MMS module into slot 5 or slot 10 of shelf 0
and observe the LED sequence.
RESULT
1. A call is up and should stay up during the procedure.
V4. Standard
7.2.5
0000003-82-2744
SHARED MMS REPLACEMENT
DESCRIPTION
Validate the ability of the system to keep calls established during the replacement of a shared MMS.
INITIAL CONDITIONS
1. System is up and operational with both OMUs and all MMSs in-service.
ACTION
1. Set up a call and verify it is on test BTS
2. Identify the shared MMS module you want to replace in slot 6 or 9 of shelf 0 of the Control Node.
3. Remove the shared MMS module identified in the previous step following the below procedure.
a. If the shared MMS you want to replace is operational you must first push the Removal request
button located on the front panel of the MMS to be replaced to isolate the hard disk.
b. Wait until the red LED starts to flash,
c. At this time you may extract the MMS module.
4. Insert the replacement MMS module and observe the LED sequence.
5. The operation is complete.
RESULT
1. A call is up and should stay up during the procedure.
V4. Standard
7.2.6
0000003-82-2744
PASSIVE OMU MODULE REPLACEMENT
The OMU (Operation and Maintenance Unit) manages the Control, Interface and Transcoder Nodes.
Supervises both the BSC and TCU cabinets and manages the SCSI disks and the interfaces with the OMC-R
and also provides system maintenance
DESCRIPTION
Validate the ability of the system to keep calls established during the replacement of the passive OMU module.
INITIAL CONDITIONS
1. A spare OMU module is available
ACTION
2. Connect to the passive OMU telnet<OMU_ip @>
user: root
password: root
3. Check the active state of the OMU: msgViOmuState
4. Shut down the OMU: bos_stop
5. Wait for the state change that the OMU has failed.
7. Unplug the passive OMU, and insert the replacement OMU.
8. Wait for the state that the OMU is operational.
10. Stop the call.
RESULT
The replacement of the passive OMU has been successful without any call drop.
V4. Standard
7.2.7
0000003-82-2744
TMU MODULE REPLACEMENT
The TMU (Traffic Management Unit) manages processing power for the GSM CallP, terminates the GSM
protocols for A, Abis, Ater and Agprs interfaces. It also terminates the low level of the GSM protocols Lapd and
SS7.
DESCRIPTION
Validate the ability of the system to stay operational (no impact) during the replacement of a faulty TMU
module.
INITIAL CONDITIONS
1. BSCe3 is duplex and operational.
2. A spare TMU module is available
ACTION
2. Perform a display Dynamic data on the BTS/SiteManager to find which TMU (TMU Shelf/TMU slot)
manages the co-located call Processing.
3. Extract the TMU module the call is on.
4. Verify that the Cell is now been processed by another TMU.
5. Re-seat the TMU module or replace with the spare one.
6. Wait for the state change that the TMU is operational.
8. Stop the call.
9. Repeat steps 1 to 9 on two more TMUs.
RESULT
The replacement of the TMU was successful with no impact on the system.
V4. Standard
0000003-82-2744
8. V17 BSCE3 CRITICAL CALL TESTING & TRAFFIC

MANAGEMENT
All test cases in this chapter are absolutely necessary to be performed on every BSC/TCUe3. Theses
test cases will need the toy cell (test BTS). These test cases may be repeated by drive team after
rehome.
8.1.
CALL TRACE SET-UP

> QGSMVLR MSISDN 18763184175
(Will display the IMSI number)
Mtrace Setup:
Toolsup
access on mtrace
enter password:
mtrace
status
desel IMSI <IMSI number>
sel IMSI 310490010001190
act event
status
clear
Originate a call from target mobile to mobile
verify two way speech
Terminate Call
status
print all
clear
Originate a call from target mobile to land line
Terminate Call
status
print all
clear
Originate a call from land line to target mobile
Terminate Call
status
print all
clear
(Using the DMS PW decoder.exe, obtain the daily password)
(if another subscriber is identified delete them from the subscriber list)
(IMSI number from above)
V4. Standard
8.1.1
0000003-82-2744
MOBILE TO MOBILE CALL, THEN RELEASE
DESCRIPTION
Check the different phases of a Mobile to Mobile call by monitoring the A-interface.
ACTION
1. Begin A-interface logging.
2. Set up a call from Mobile 1 (originator) to Mobile 2 (terminator) and verify speech path and hang-up.
Example Trace: IMSI number: 374129000231450
NSD TRID MSC BSS/ MS/SMLC LMU
BSSMAP:
<----CL3 - CM Srvc Request
gsm_rr_comp_l3_event (8) IND
gsm_mm_rr_establish_sap_event (12) IND
gsm_mm_cm_service_req_event (17) IND
gsm_mm_process_acc_req_event (21) IND
gsm_vlr_process_acc_req_event (0) IND
BSSMAP:
----->
Cipher Mode Command
gsm_vlr_process_acc_req_event (0)
gsm_mm_process_acc_req_event (21) RESP
BSSMAP:
<----Classmark Update
gsm_rr_classmark_update_event (12) IND
BSSMAP:
<----Cipher Mode Complete
gsm_rr_cipher_event (11) CONF
DTAP:
0
--------->
Identity Request
gsm_mm_cm_service_req_event (17) RESP
DTAP:
1
0
<--------Setup
gsm_mm_rr_data_sap_event (11) IND
gsm_cc_mmcc_establish_sap_event (3) IND
gsm_vlr_outgoing_call_event (7) IND
gsm_vlr_complete_call_event (8) REQ
DTAP:
0
8
--------->
Call Proceeding
gsm_cc_sync_sap_event (4) REQ
gsm_mm_sync_sap_event (3) REQ
gsm_rr_sync_sap_event (24) REQ
gsm_rr_assign_event (10) REQ
BSSMAP:
----->
Assignment Request
DTAP:
0
<--------Identity Response
gsm_rr_trans_data_sap_event (19) IND
gsm_mm_identification_event (23) CONF
BSSMAP:
<----Assignment Complete
gsm_rr_assign_event (10) CONF
gsm_rr_sync_sap_event (24) CONF
gsm_mm_sync_sap_event (3) CONF
gsm_cc_sync_sap_event (4) CONF
umts_rr_rls_held_dt_event (117) REQ
DTAP:
0
8
--------->
Alerting
sm_rr_pi_supervision_event (2) REQ
gsm_cc_mmcc_data_sap_event (1) REQ
DTAP:
0
8
--------->
Connect
gsm_rr_pi_supervision_event (2) REQ
DTAP:
1
0
<--------Connect Ack.
gsm_cc_mmcc_data_sap_event (1) IND
DTAP:
0
8
--------->
Disconnect
gsm_mm_cc_takedown_event (50) REQ
DTAP:
0
0
<--------Release
DTAP:
0
8
--------->
Release Complete
gsm_cc_mmcc_release_sap_event (2) REQ
gsm_mm_cc_release_sap_event (2) REQ
gsm_rr_release_sap_event (21) REQ
BSSMAP:
----->
Clear Command
BSSMAP:
<----Clear Complete
gsm_rr_clear_event (9) CONF
gsm_ho_takedown_or_retry_event (41) REQ
V4. Standard
8.1.2
0000003-82-2744
MOBILE TO LANDLINE CALL RELEASE BY THE LANDLINE
DESCRIPTION
Check the different phases of a mobile-to-land line call, by monitoring the A-interface.
ACTION
2. Set up a call from the Mobile to land line and verify speech path and hang-up.
BSSMAP:
<----CL3 - CM Srvc Request
sm_rr_comp_l3_event (8) IND
gsm_mm_rr_establish_sap_event (12) IND
gsm_mm_cm_service_req_event (17) IND
gsm_vlr_process_acc_req_event (0) IND
BSSMAP:
----->
Cipher Mode Command
gsm_vlr_process_acc_req_event (0) RESP
umts_rr_loc_rpt_event (116) REQ
BSSMAP:
<----Classmark Update
BSSMAP:
<----Cipher Mode Complete
gsm_mm_ciphering_event (16) CONF
gsm_mm_identification_event (23) REQ
gsm_rr_data_sap_event (22) REQ
DTAP:
0
--------->
Identity Request
DTAP:
1
0
<--------Setup
sm_mm_rr_data_sap_event (11) IND
gsm_cc_mmcc_establish_sap_event (3) IND
gsm_vlr_outgoing_call_event (7) IND
gsm_vlr_complete_call_event (8) REQ
DTAP:
0
<--------Identity Response
gsm_mm_identification_event (23) CONF
DTAP:
0
8
--------->
Call Proceeding
gsm_cc_sync_sap_event (4) REQ
gsm_mm_sync_sap_event (3) REQ
gsm_rr_sync_sap_event (24) REQ
BSSMAP:
----->
Assignment Request
BSSMAP:
<----Assignment Complete
gsm_mm_sync_sap_event (3) CONF
gsm_cc_sync_sap_event (4) CONF
DTAP:
0
8
--------->
Alerting
DTAP:
0
8
--------->
Connect
DTAP:
1
0
<--------Connect Ack.
DTAP:
0
0
<--------Disconnect
gsm_mm_cc_takedown_event (50) REQ
gsm_cc_mmcc_data_sap_event (1) REQ
DTAP:
0
8
--------->
Release
DTAP:
1
0
<--------Release Complete
BSSMAP:
----->
Clear Command
BSSMAP:
<----Clear Complete
V4. Standard
8.1.3
0000003-82-2744
LANDLINE TO MOBILE CALL RELEASE BY THE LANDLINE
DESCRIPTION
Check the different phases of a land line to mobile call by monitoring the A-interface.
ACTION
2. Set up a call from the land line to the Mobile and verify speech path and hang-up.

gsm_vlr_incoming_call_event
(11) IND
BSSMAP:
BSSMAP:
----->
<-----
BSSMAP:
----->
BSSMAP:
<-----
BSSMAP:
<-----
DTAP:
DTAP:
DTAP:
--------->
--------->
8
<---------
BSSMAP:
DTAP:
1
----->
<---------
BSSMAP:
<-----
DTAP:
--------->
DTAP:
<---------
DTAP:
<---------
DTAP:
--------->
DTAP:
<---------
DTAP:
--------->
DTAP:
<---------
BSSMAP:
BSSMAP:
----->
<-----
gsm_vlr_page_search_event (10) REQ

gsm_cc_mmcc_establish_sap_event (3) REQ
gsm_mm_cc_establish_sap_event (1) REQ
gsm_rr_establish_sap_event (20) REQ
Paging
CL3 - Page Response
gsm_rr_comp_l3_event (8) IND
gsm_mm_rr_establish_sap_event (12) CONF
Cipher Mode Command
gsm_vlr_process_acc_req_event (0) RESP
gsm_mm_cc_establish_sap_event (1) CONF
Classmark Update
Cipher Mode Complete
Setup
gsm_mm_ciphering_event (16) CONF
gsm_mm_identification_event (23) REQ
gsm_rr_data_sap_event (22) REQ
Identity Request
gsm_mm_cc_establish_sap_event (1) CONF
Call Confirmed
Assignment Request
Identity Response
gsm_rr_trans_data_sap_event (19) IND
Assignment Complete
Progress
Alerting
Connect
Connect Ack.
GSM_MM_CHECK_IMEI_EVENT (26) RESP
Disconnect
Release
Release Complete
Clear Command
Clear Complete
V4. Standard
8.1.4
0000003-82-2744
SUSPEND AND RESUME
DESCRIPTION
The goal of this test consists in verifying that the Suspend and Resume procedure is executed when the MS
enters in circuit-dedicated mode (when GSM call occurs during GPRS data transfer).
Right now, only class B and class C Mobiles are available. These MS cannot perform simultaneous voice and
packet data services. So, when in packet transfer mode they want to initiate a GSM voice call, they must
perform a Suspend and Resume procedure.
INITIAL CONDITIONS
A GPRS session is available.
ACTION 1
Perform a data transfer and initiate a call while the transfer is ongoing.
RESULT 1
The MS turns in Circuit-Switched mode.
ACTION 2
Hang up the voice call.
RESULT 2
The data transfer is resuming.
V4. Standard
8.2.
0000003-82-2744
E911
8.2.1
SINGLE E911 CALL WITH SIM CARD
DESCRIPTION
Verify that an e911 call can be successfully place across the e3BSC platform.
INITIAL CONDITIONS
1. E911 system has been installed, integrated and qualified for in-service operation.
2. Mobile is properly equipped with a valid SIM card.
ACTION 1
1. Place an E911 call from the mobile.
2. Identify the call as a test call to the operator.
3. If Lb Links are associated with the BSC/TCU the test call is passing through, verify the Mobile's Location is
received at the E911 center.
4. Release the call.
RESULT 1
1. E911 call is successful.
V4. Standard
8.2.2
0000003-82-2744
SINGLE E911 CALL WITHOUT SIM CARD
TITLE
Single E911 Call without SIM Card
DESCRIPTION
Verify that an E911 call can be successfully place across the e3BSC platform using a mobile that does not
have a SIM card.
INITIAL CONDITIONS
1. E911 system has been installed, integrated and qualified for in-service operation.
2. Mobile does not have a SIM card.
ACTION 1
1. Place an E911 call from the mobile.
2. Identify the call as a test call to the operator.
3. If Lb Links are associated with the BSC/TCU the test call is passing through, verify the Mobile's Location is
received at the E911 center.
4. Release the call.
RESULT 1
E911 call is successful.
V4. Standard
8.3.
0000003-82-2744
CHECKING THE NSS PARAMETERS FOR AMR
DESCRIPTION
The aim of this test is to ensure that all parameters are set properly on NSS to have AMR activated.
INITIAL CONDITIONS
1. MSC is working with NSS17 or later releases.

2. There is no call processing issue on BSS or NSS side.
ACTION
1.
2.
Login to MAP
Check the following tables to make sure that all settings are correct.
FR3 and HR3 codecs should be added in the circuit pool Truck tables (TRKGRP CICPool option)
TABLE OFCVAR
MULTIPLE_VOCODER_SUPPORT needs to be changed to: ON_WITH_CHANGES
RESULT
1. All parameters are set on the system as it is recommended in the table in this test procedure.
V4. Standard
0000003-82-2744
9. PERFORMANCE MANAGMENT TESTING

9.1.1
SUCCESSFUL CREATION MDSCANNERS ON A BSCE3 OBJECT.
TEST PURPOSE:
The purpose of this test is to verify that General Statistic, Fast Statistic & Real Time mdScanners can be
created for a BSCe3 object on a V17 OMC-R.
PROCEDURE:
1. Login to OMC-R GUI
2. On main menu of the network view browser, go under Objects, select MdScanner, and apply on
small window that is popped out.
3. On new window, click on Add Objects and select BSC, type the BSC number, and apply
4. For each mdScanner Type select the following for each field:
mdObjectList:
mdGranularityPeriod:
mdScannerType:
mdLog:
associatedLog:
mdArchive:
mdConfirm:
mdTransferMode:
operationalState:
mdStorageDuration:
bscNumber
1440
General Statistic
Logged
bscNumber
60
Fast Statistic
Logged
bscNumber
5
Real Time
Not Logged
Archived
Confirmed
FTAM
Archive
Confirmed
FTAM
Not Archived
Not Confirmed
CMIS
5. From MMI, select the BSC and perform a Display/set on the created MD-scanner and check that
attributes are identical to the parms above.
TEST RESULTS
The MdScanners are created.
V4. Standard
0000003-82-2744
10. T1 ABIS LINK ASSIGNMENTS
V4. Standard
0000003-82-2744
10.1. E1 ABIS LINK ASSIGNMENTS
V4. Standard
0000003-82-2744
10.2. T1 A-LINK ASSIGNMENTS

TCU 0
LSA 0 - lsaRc 5
MMI
Port
0
LSA
Port
0
1
2
LSA 1 - lsaRc 103

Allocation
LSA 2 - lsaRc 109
LSA
Port
0
Allocation
Ater
MMI
Port
28
Ater
29
Ater
30
Ater
LSA 3 - lsaRc 112
LSA
Port
0
Allocation
Ater
MMI
Port
56
LSA
Port
0
Allocation
Ater
MMI
Port
84
Ater
57
Ater
58
Ater
85
Ater
Ater
86
Ater
31
Ater
59
Ater
87
Ater
Ater
32
Ater
33
Ater
60
Ater
88
Ater
Ater
61
Ater
89
Ater
A21
34
A43
62
A65
90
A87
A20
35
A42
63
A63
91
A86
A19
36
A41
64
A63
92
A85
A18
37
A40
65
A62
93
A84
10
10
A17
38
10
A39
66
10
A61
94
10
A83
11
11
A16
39
11
A38
67
11
A60
95
11
A82
12
12
A15
40
12
A37
68
12
A59
96
12
A81
13
13
A14
41
13
A36
69
13
A58
97
13
A80
14
14
A13
42
14
A35
70
14
A57
98
14
A79
15
15
A12
43
15
A34
71
15
A56
99
15
A78
16
16
A11
44
16
A33
72
16
A55
100
16
A77
17
17
A10
45
17
A32
73
17
A54
101
17
A76
18
18
A9
46
18
A31
74
18
A53
102
18
A75
19
19
A8
47
19
A30
75
19
A52
103
19
A74
20
20
A7
48
20
A29
76
20
A51
104
20
A73
21
21
A6
49
21
A28
77
21
A50
105
21
A72
22
22
A5
50
22
A27
78
22
A49
106
22
A71
23
23
A4
51
23
A26
79
23
A48
107
23
A70
24
24
A3
52
24
A25
80
24
A47
108
24
A69
25
25
A2
53
25
A24
81
25
A46
109
25
A68
26
26
A1
54
26
A23
82
26
A45
110
26
A67
27
27
A0
55
27
A22
83
27
A44
111
27
A66
SigLks 0 & 4
SigLks 1 & 5
SigLks 2 & 6
Ater
SigLks 3
&7
V4. Standard
0000003-82-2744
TCU 1
LSA 0 - lsaRc 5
MMI
Port
0
LSA
Port
0
1
2
LSA 1 - lsaRc 103

Allocation
LSA 2 - lsaRc 109
LSA
Port
0
Allocation
Ater
MMI
Port
28
Ater
29
Ater
30
Ater
5
6
7
LSA 3 - lsaRc 112
LSA
Port
0
Allocation
Ater
MMI
Port
56
LSA
Port
0
Allocation
Ater
MMI
Port
84
Ater
57
Ater
58
Ater
85
Ater
Ater
86
Ater
31
Ater
59
Ater
87
Ater
Ater
32
Ater
60
Ater
88
Ater
Ater
33
A21
34
Ater
61
Ater
89
Ater
A43
62
A65
90
A87
A20
35
A42
63
A64
91
A86
A19
A18
36
A41
64
A63
92
A85
37
A40
65
A62
93
A84
10
10
A17
38
10
A39
66
10
A61
94
10
A83
11
12
11
A16
39
11
A38
67
11
A60
95
11
A82
12
A15
40
12
A37
68
12
A59
96
12
A81
13
13
A14
41
13
A36
69
13
A58
97
13
A80
14
14
A13
42
14
A35
70
14
A57
98
14
A79
15
15
A12
43
15
A34
71
15
A56
99
15
A78
16
16
A11
44
16
A33
72
16
A55
100
16
A77
17
17
A10
45
17
A32
73
17
A54
101
17
A76
18
18
A9
46
18
A31
74
18
A53
102
18
A75
19
19
A8
47
19
A30
75
19
A52
103
19
A74
20
20
A7
48
20
A29
76
20
A51
104
20
A73
21
21
A6
49
21
A28
77
21
A50
105
21
A72
22
22
A5
50
22
A27
78
22
A49
106
22
A71
23
23
A4
51
23
A26
79
23
A48
107
23
A70
24
24
A3
52
24
A25
80
24
A47
108
24
A69
25
25
A2
53
25
A24
81
25
A46
109
25
A68
26
26
A1
54
26
A23
82
26
A45
110
26
A67
27
27
A0
55
27
A22
83
27
A44
111
27
A66
SigLks 8 & 11
SigLks 9 & 12
Ater
SigLks 10 & 13
V4. Standard
0000003-82-2744
10.3. E1 A-LINKS ASSIGNMENTS

TCU 0
LSA 0 - lsaRc 5
MMI
Port
0
LSA
Port
0
1
2
3
LSA 1 - lsaRc 103

Allocation
LSA 2 - lsaRc 109
LSA
Port
0
Allocation
Ater
MMI
Port
21
Ater
22
Ater
23
Ater
24
Ater
A15
LSA 3 - lsaRc 112
LSA
Port
0
Allocation
Ater
MMI
Port
42
LSA
Port
0
Allocation
Ater
MMI
Port
63
Ater
43
Ater
44
Ater
64
Ater
Ater
65
Ater
Ater
45
Ater
66
Ater
25
Ater
26
A31
46
Ater
67
Ater
47
A47
68
A63
A14
27
A30
48
A46
69
A62
A13
28
A29
49
A45
70
A61
A12
A11
29
A28
50
A44
71
A60
30
A27
51
A43
72
A59
10
10
A10
31
10
A26
52
10
A42
73
10
A58
11
12
11
A9
32
11
A25
53
11
A41
74
11
A57
12
A8
33
12
A24
54
12
A40
75
12
A56
13
13
A7
34
13
A23
55
13
A39
76
13
A55
14
14
A6
35
14
A22
56
14
A38
77
14
A54
15
15
A5
36
15
A21
57
15
A37
78
15
A53
16
16
A4
37
16
A20
58
16
A36
79
16
A52
17
17
A3
38
17
A19
59
17
A35
80
17
A51
18
18
A2
39
18
A18
60
18
A34
81
18
A50
19
19
A1
40
19
A17
61
19
A33
82
19
A49
20
20
A0
41
20
A16
62
20
A32
83
20
A48
SigLks 0 & 4
SigLks 1 & 5
SigLks 2 & 6
Ater
SigLks 3
&7
V4. Standard
0000003-82-2744
TCU 1
LSA 0 - lsaRc 5
MMI
Port
0
LSA
Port
0
LSA 1 - lsaRc 103

Allocation
LSA 2 - lsaRc 109
LSA
Port
0
Allocation
Ater
MMI
Port
21
Ater
22
Ater
Ater
LSA 3 - lsaRc 112
LSA
Port
0
Allocation
Ater
MMI
Port
42
LSA
Port
0
Allocation
Ater
MMI
Port
63
Ater
43
Ater
64
Ater
23
Ater
24
Ater
44
Ater
65
Ater
45
Ater
66
Ater
Ater
25
Ater
46
Ater
67
Ater
A15
26
A31
47
A47
68
A63
A14
A13
27
A30
48
A46
69
A62
28
A29
49
A45
70
A61
A12
29
A28
50
A44
71
A60
Ater
A11
30
A27
51
A43
72
A59
10
10
A10
31
10
A26
52
10
A42
73
10
A58
11
11
A9
32
11
A25
53
11
A41
74
11
A57
12
12
A8
33
12
A24
54
12
A40
75
12
A56
13
13
A7
34
13
A23
55
13
A39
76
13
A55
14
14
A6
35
14
A22
56
14
A38
77
14
A54
15
15
A5
36
15
A21
57
15
A37
78
15
A53
16
16
A4
37
16
A20
58
16
A36
79
16
A52
17
17
A3
38
17
A19
59
17
A35
80
17
A51
18
18
A2
39
18
A18
60
18
A34
81
18
A50
19
19
A1
40
19
A17
61
19
A33
82
19
A49
20
20
A0
41
20
A16
62
20
A32
83
20
A48
SigLks 8 & 11
SigLks 9 & 12
SigLks 10 & 13
V4. Standard
0000003-82-2744
10.4. A-TER LINK ASSIGNMENTS

T1
LSA 0 - lsaRc 5
LSA 1 - lsaRc 103
LSA 2 - lsaRc 109
MMI Port
MMI Port
MMI Port
28
56
29
57
30
58
31
59
32
60
33
61
LSA 3 - lsaRc 112
LSA 4 - lsaRc 13
LSA 5 - lsaRc 5
MMI Port
MMI Port
MMI Port
84
112
140
85
113
141
86
114
142
87
115
143
88
116
144
89
117
145
E1
LSA 0 - lsaRc 5
LSA 1 - lsaRc 103
LSA 2 - lsaRc 109
MMI Port
MMI Port
MMI Port
21
42
22
43
23
44
24
45
25
46
LSA 3 - lsaRc 112
LSA 4 - lsaRc 13
LSA 5 - lsaRc 5
MMI Port
MMI Port
MMI Port
63
84
105
64
85
106
65
86
107
66
87
108
67
88
109
V4. Standard
0000003-82-2744
BSC e3 maximum configuration

Maximum configuration for a single frame BSCe3 is 3000 Erlang
3000 Erlang translates into 14 TMUs.
PEC
DESCRIPTION
NTQE09AA
BSCE3 FRAME ASSEMBLY
2400E
1
NTRU0218
HOISTING KIT
NTRU0101
JUNCTION KIT
NTRU0324
RAISED/CONCRETE FLOOR ANCHOR KIT (ZO
NTRU0220
CABLE COVER KIT (2200H)
NTLX9560
ETSI-SAI SIDE PANEL KIT
NTLX95DJ
NTLX73BB
ETSI-SAI FRAME ASSEMBLY

ASYNCHRONOUS TRANSFER MODE (ATM)
RESOURCE MODULE
NTLX82BA
COMMON EQUIP. CARD W/ETHERNET
NTQE07AA
MOD:SUB RATE TIMESWITCH 8K RES
NTLX61AA
SHELF INTERFACE MODULE (SIM)
NTQE06AB
CC1 COMMUNICATION CONTROLLER
NTQE05AA
MOD: MASS MEMORY STORAGE-MMS
NTQE03AB
MOD: OPERATION MAINT UNIT
NTLX60AA
FILLER MODULE ASSEMBLY
29
29
P0913548
LABEL: CSA BSC E-3
NTQE84CA
LSA-CTU T1 100
NTQE04AA
MOD: TRAFIC MNGT UNIT-TMU
12
14
NTQE98DA/B/C
DA1 8 PAIR STP CABLE
28
42
NTQE84CA
LSA-CTU T1 100
PEC
NTLX89DA
INTERFACE ELECTRONICE MODULE (IEM)
TERMINATION INTERFACE MODULE (TIM)
CTU ASSEMBLY
NTLX92AA
NTLX93DA
DESCRIPTION
3000E
V4. Standard
0000003-82-2744
TCU e3 maximum configuration

Maximum configuration for a single "shelf" TCUe3 is 1800 Erlang
One TCUe3 frame can accommodate two (2) shelves
1800 Erlang translates into 10 TRMs and 4 LSA
PEC
DESCRIPTION
NTQE89AA
TCUE3 FRAME ASSEMBLY
1200E
1
NTRU0218
HOISTING KIT
NTRU0101
JUNCTION KIT
NTRU0324
RAISED/CONCRETE FLOOR ANCHOR KIT (ZONE
NTRU0220
CABLE COVER KIT (2200H)
NTLX9560
ETSI-SAI SIDE PANEL KIT
NTLX95DJ
ETSI-SAI FRAME ASSEMBLY
NTLX82BA
COMMON EQUIP. CARD W/ETHERNET
NTLX61AA
SHELF INTERFACE MODULE (SIM)
NTLX60AA
FILLER MODULE ASSEMBLY
21
42
P0913550
LABEL: CSA TCU E-3
NTQE84CA
LSA-CTU T1 100
NTQE08AB
TRANSCODER RESS. MOD. TRM+
12
21
35
NTQE98DA/B/CDA1 8 PAIR STP CABLE
NTQE84CA
LSA-CTU T1 100
PEC
DESCRIPTION
NTLX89DA
INTERFACE ELECTRONICE MODULE (IEM)
NTLX92AA
TERMINATION INTERFACE MODULE (TIM)
NTLX93DA
CTU ASSEMBLY
***************END OF DOCUMENT***************
2000E
V4. Standard

BSS17 GSM ATP V17.0 Generic BSC TCUe3 PDF

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

BSS17 GSM ATP V17.0 Generic BSC TCUe3 PDF

Enviado por

Direitos autorais:

Formatos disponíveis

BSS17 GSM ATP V17.

BSS17 GSM ATP V17.0 Generic BSC/TCUe3

Nortel Networks confidential

BSS17 GSM ATP V17. 0 Generic BSC/TCUe3

September 25, 2009 Page 2/59

BSS17 GSM ATP V17.0 Generic BSC/TCUe3

Nortel Networks confidential

BSS17 GSM ATP V17. 0 Generic BSC/TCUe3

September 25, 2009 Page 3/59

BSS17 GSM ATP V17.0 Generic BSC/TCUe3

AUDIENCE FOR THIS DOCUMENT ............................................................................................ 6

NETWORK CONFIGURATION FOR ACCEPTANCE TESTING................................................... 7

TEST EQUIPMENT ...................................................................................................................... 7

ATP PACKAGE ............................................................................................................................ 8

DEFINITION OF ACCEPTANCE TESTS .......................................................................................... 9

AGREEMENT SHEET ....................................................................................................................... 10

TEST SUITE BSC...................................................................................................................... 11

ADDITIONAL WIRING TEST ................................................................................................................. 13

CARD SLOT & CLUSTER NUMBERS.............................................................................................. 14

CLUSTER NUMBER CHART: ...................................................................................................... 15

VERIFY THE CALL IS ESTABLISHED: ........................................................................................ 15

CREATE A SECOND LOGIN ON THE MSC: ............................................................................... 15

DELETE SECOND LOGIN ON MSC: ........................................................................................... 15

CIC TESTING ............................................................................................................................... 17

ADDITIONAL CIC TESTS............................................................................................................. 19

GROUP A: TESTS TO BE EXECUTED ON EVERY BSC/TCUE3.................................................... 20

ETHERNET LINK TEST BETWEEN OMUS AND THE OMC-R .......................................................... 20

BSS17 GSM ATP V17. 0 Generic BSC/TCUe3

September 25, 2009 Page 4/59

BSS17 GSM ATP V17.0 Generic BSC/TCUe3

CALL TRACE SET-UP.................................................................................................................. 42

MOBILE TO MOBILE CALL, THEN RELEASE ..................................................................................... 43

SINGLE E911 CALL WITH SIM CARD.................................................................................................. 47

CHECKING THE NSS PARAMETERS FOR AMR........................................................................ 49

PERFORMANCE MANAGMENT TESTING ...................................................................................... 50

BSCE3 CLOCK DRIFT........................................................................................................................... 34

V17 BSCE3 CRITICAL CALL TESTING & TRAFFIC MANAGEMENT............................................. 42

SUCCESSFUL CREATION MDSCANNERS ON A BSCE3 OBJECT. ................................................. 50

T1 ABIS LINK ASSIGNMENTS......................................................................................................... 51

Nortel Networks confidential

BSS17 GSM ATP V17. 0 Generic BSC/TCUe3

September 25, 2009 Page 5/59

BSS17 GSM ATP V17.0 Generic BSC/TCUe3

AUDIENCE FOR THIS DOCUMENT

Nortel Networks confidential

BSS17 GSM ATP V17. 0 Generic BSC/TCUe3

September 25, 2009 Page 6/59

BSS17 GSM ATP V17.0 Generic BSC/TCUe3

NETWORK CONFIGURATION FOR ACCEPTANCE TESTING

Ensure that all links / trunks are built and in-service.

Nortel Networks confidential

BSS17 GSM ATP V17. 0 Generic BSC/TCUe3

September 25, 2009 Page 7/59

BSS17 GSM ATP V17.0 Generic BSC/TCUe3

Nortel Networks confidential

BSS17 GSM ATP V17. 0 Generic BSC/TCUe3

September 25, 2009 Page 8/59

BSS17 GSM ATP V17.0 Generic BSC/TCUe3

3. DEFINITION OF ACCEPTANCE TESTS

Nortel Networks confidential

BSS17 GSM ATP V17. 0 Generic BSC/TCUe3

September 25, 2009 Page 9/59

BSS17 GSM ATP V17.0 Generic BSC/TCUe3