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.
BSNL ACCEPTANCE TEST PLAN – BSC
PUBLICATION HISTORY
Version Date Author Amendment
1.0 December 29, 2004 Pramod Sasidharan First Draft
1.1 December 29, 2004 Fernand Mendes Doc review: section 1 added, affected sub sections 2.6.5,
2.6.7, 2.6.8, 2.6.11, and 2.6.12.
1.2 January 28, 2005 Master Iraban Modified to incorporate the changed of BSNL ATP review
comments.
1.3 February 4, 2005
Master Iraban, Fernand Mendes
Review comments incorporated.LOGO changed.
1.4 February 23, 2005
Ramesh Krishnamurthy Changes made after review with T&D Circle, Jabalpur
1.5 March 14, 2005 Master Iraban New test case added.
01.5 / EN 14/MAR/2004 Page 2/20
BSNL ACCEPTANCE TEST PLAN – BSC
APPROVALS
This document does not impact any past, present, or future contractual obligations on the part of NORTEL or BSNL customer. Signature indicates that the individual has reviewed the Mobility Acceptance Test Plan and agrees in principle.
Signature Date
Approved by:
Bob Young, _______________________ ______________Nortel Project Lead
Tony Morcos, _______________________ ______________Nortel Validation Lead
Approved by:
* _______________________ ______________BSNL T&D Circle
PLEASE NOTE:
Approvals will only be required on 1.0 or higher revisions and major program changes i.e. date changes, feature addition, deletion, or etc. The approvers can also use electronic signature in the form of email, as it is required by ISO9000.
All names with an “*” denote mandatory approval.
01.5 / EN 14/MAR/2004 Page 3/20
BSNL ACCEPTANCE TEST PLAN – BSC
CONTENTS
1. INFRASTRUCTURE TEST FOR BSC................................................................6
2.1 HARDWARE CHECKS (AS PER PO AND BOM)..............................................72.1.1 INTERFACE................................................................................................................................. 7
2.4.2.5 INTRA BSC HANDOVER....................................................................................................10
2.4.2.6 GPRS AND EDGE FUNCTIONALITY TEST.......................................................................11
2.5 NETWORK ELEMENTS MANAGEMENT TEST..............................................112.5.1 BTS AND TCU MANAGEMENT...................................................................................................11
1 Raised floor and Antistatic flooring As per EI-AT-70102 Layout and floor plan with Trunking and
Dimensioning approved diagram 3 Lighting and Power outlets4 Check of earthing system and its distribution Earth resistance value should be 0.5 ohm5 Fire detection system check EI protection – Fire AT-70006 Air-Condition EI Building AC T0002, T 00037 Engine Alternator As per T & D Test schedule8 A) Power Plant (As per T&D Test Schedule)
B) Battery (As per T&D Test Schedule) C) UPS/Inverter (As per T&D Test Schedule)
9 A) Layout approvalB) Number of RacksC) Rack Serial NumbersD) Verification of ironwork
10 As per layout drawing for1. Cabling2. Wiring
11 Voltage Drop Test ( Voltage drop should be < 1 volt )Battery Supply PSU Output DC Input to CabinetVolts Volts Volts
12 DDF Visual Checka) Positioning of equipmentsb) Leveling of racksc) Crimping of cables
13 QA Report provided for BSC Name 14 Documentation Provided15 General inspection (visual check)16 Media A/T between BSC & MSC As per T & D Test schedule
01.5 / EN 14/MAR/2004 Page 6/20
BSNL ACCEPTANCE TEST PLAN – BSC
2. BSC Acceptance Test
2.1 Hardware Checks (As per PO and BOM)
2.1.1 InterfaceType of interface between BSC & TCUType of interface between BSC & BTS Type of interface between BSC & OMC-R
2.1.2 PCIU
LED Status OFF ONStatus of Amber Lamp
2.1.3 CONTROL NODE
Status SIM Module1 SIM Module 2Green LEDRed LED
2.1.4 INTERFACE NODE
Status SIM Module1 SIM Module 2Green LEDRed LED
01.5 / EN 14/MAR/2004 Page 7/20
BSNL ACCEPTANCE TEST PLAN – BSC
2.1.5 BSC Card Checks Using the "STATE" command at the OMC-R, verify the operational state of the cards in the BSC.
Cards Status in OMC-R (OK / NOK)OMUTMUMMSCC-1CEMATM-SWATM-RMLSA-RC8K-RM
2.2 Software Checks
2.2.1 BSC RESTART TEST Power OFF/ON Test
Initial Condition:BSC is up and operational.
Test Procedure:1. Power ‘OFF’ the BSC, and power it ‘ON’
Expected Results: The BSC comes up and comes back to stable operational state.
Software Reset test
Initial Condition:BSC is up and operational.BSC is unlocked.TML connected to BSC, and GUI is open.
Test Procedure:1. Do a ‘Reset CN’ action from TML GUI.
Expected Results: The BSC comes up and comes back to stable operational state.
01.5 / EN 14/MAR/2004 Page 8/20
BSNL ACCEPTANCE TEST PLAN – BSC
2.2.2 SOFTWARE CONFORMITYInitial Condition:BSC is up and operational, and can be accessible from OMC-R
Test Procedure:1. Open GUI in OMC-R, and select the BSC.2. Write click and select ‘Display/Set’ option.3. Select ‘bsc software’ from the drop down list.
Expected Results: The BSC software used is displayed in the session log.
2.3 Synchronization Test In OMC-R, select BSC Right Click and select Display Set Option Select Display Dynamic Data This will show which PCM is synchronized with MSC
2.4 Functionality Tests
2.4.1 Location Update TestInitial Conditions:BSS network is up and running.Power off MS. Test Procedure:
1. Ensure that a new SIM is provided for the mobile.2. Turn on the MS handset and wait until the network information is shown on the visual information.
Expected Results: 1. MS is camped to the network.
2.4.2 Telephonic Services
2.4.2.1 Mobile to Mobile CallInitial Conditions:BSS Network is up, and running.Two MS are available (Use TEMS) with a valid SIM. Test Procedure:
1. Power on MSa and MSb
01.5 / EN 14/MAR/2004 Page 9/20
BSNL ACCEPTANCE TEST PLAN – BSC
2. MSa calls MSb.3. Call is established. 4. Verify the speech path. 5. Disconnect the call.
Expected Results:
1. Call is successful.2. Call disconnection is successful.
2.4.2.2 SMS CallInitial Conditions:BSS Network is up, and running.Two MS are available with a valid SIM. Test Procedure:
1. Power on MSa MSb2. MSa sends a SMS to the MSb3. SMS is successfully sent from MSa.4. SMS is successfullt delivered to MSb.
Expected Results:
1. Sending SMS is successful.
2.4.2.3 Data CallInitial Conditions:Two 9.6 kbps Asynchronous Non Transparent UDI capable mobilesEnsure table GHLRBCA of the HLR has been correctly data-filled. Ensure the Mobiles have been provisioned with data service in the HLR table GHLRBSVC. Set the modem’s baud rate on the mobile data equipment to 9.6 kbpsLocation update for the two mobiles in the same VLR is proper.
Test Procedure:1. From MSa, originate a data call to MSb2. Transfer files from MSa to MSb. 3. MSb clears the call.
Expected Results: 1. A data call is successfully established between the two mobiles. 2. Data is successfully transferred. 3. Verify the call is cleared.
2.4.2.4 FAX CallInitial Conditions:9.6 kbps Asynchronous G3 Fax capable mobile and PSTNEnsure table GHLRBCA of the HLR has been correctly data filled. Ensure the Mobile has been provisioned with fax service in the HLR table GHLRBSVC. Set the fax’ baud rate on the mobile data equipment to 9600 bps.
Test Procedure:1. From the Mobile, originate a fax call to the PSTN2. The fax document is sent from the Mobile. 3. The call is released from Mobile side.
01.5 / EN 14/MAR/2004 Page 10/20
BSNL ACCEPTANCE TEST PLAN – BSC
Expected Results: 1. The fax call is successfully established. 2. Fax is successfully sent. 3. The call is cleared
2.4.2.5 INTRA BSC HANDOVERInitial Condition:1 BSC and 2 BTS are available in BSS network.Both BTS are on the same BSC. 2 GSM handset with activated test SIM.
Test Procedure:1. Make mobile to mobile call.2. Perform a Intra BTS Handover.3. Verify the speech path. 4. The call does not drop and the new Cell ID is visible on TEMS
Expected Results: The Intra BSC handover should take place.
2.4.2.6 GPRS AND EDGE FUNCTIONALITY TEST GPRS Test
Initial Conditions:1 BTS, 1 BSC, 1 PCU, 1 SGSN, 1 HLR, 1 GGSN, 1 GPRS Phone + laptop+1 Linux or windows FTP servers are available on network.GSM and GPRS / EDGE Network operational.
Test Procedure:
1. Configure the MS in HLR with GPRS Services.2. Perform GPRS attach and PDP context activation.3. Use command window to download a 100k file from the FTP server. 4. Check the throughput and convert it into kbps by multiplying it with 8.43.
Expected Results:1. The file is successfully downloaded and the speed is as expected.
EDGE Test
Initial Conditions:1 BTS, 1 BSC, 1 PCU, 1 SGSN, 1 HLR, 1 GGSN, 1 EDGE Phone, and 1 Server are available on network.GSM and GPRS / EDGE Network operational.Enable EDGE in the Cell.
Test Procedure:
1. Initiate one uplink FTP connection using EDGE mobile.2. Begin a “Small Uplink Data transfer”.
Expected Results:1. Transfer is ended correctly
01.5 / EN 14/MAR/2004 Page 11/20
BSNL ACCEPTANCE TEST PLAN – BSC
2.5 Network Elements Management Test
2.5.1 BTS and TCU Management
Initial Conditions:BSS network is up, and operational with TCU, and BTS.BSS network is accessible from OMC-R. Test Procedure:
1. Open a GUI session in OMC-R2. Perform a ‘lock and unlock’ operation for BTS object.3. Perform a ‘lock and unlock’ operation for TCU object.
Expected Results:
1. The procedures should work fine withour any error message.
01.5 / EN 14/MAR/2004 Page 12/20
BSNL ACCEPTANCE TEST PLAN – BSC
2.6 BSC Diagnostics TestInitial Conditions:OMC-R is up and BSC is accessible from OMC-R Test Procedure:
1. Display dynamic data of BSC from OMC-R
Expected Results: 1. It should display the operational conditions of BSC.
2.7 Redundancy Test
2.7.1 POWER SUPPLY REDUNDANCY TEST Initial Condition:The BSC has 2 SIM modules for the dual shelfs (Control Node and Interface Node).
Control NodeIn the Control Node1. SIM module 1 is switch OFF.2. SIM module 2 is ON.3. Check that Control Node functions properly.
In the Control Node1. SIM module 2 is switch OFF.2. SIM module 1 is ON.3. Check that Control Node functions properly.
Interface NodeIn the Interface Node1. SIM module 1 is switch OFF.2. SIM module 2 is ON.3. Check that Interface Node functions properly.
In the Interface Node1. SIM module 2 is switch OFF.2. SIM module 1 is ON.3. Check that Interface Node functions properly.
Expected Results: 1. It should display the operational conditions of BSC.
01.5 / EN 14/MAR/2004 Page 13/20
BSNL ACCEPTANCE TEST PLAN – BSC
2.7.2 BSC – OMC-R LINK REDUNDANCYInitial Condition:Each BSC is equipped with two OMU (Operation and Maintenance Unit) cards.One of them will be in Active state and other card will be in Passive state.
Test Procedure:To check redundancy, follow the steps given below:
1. Configure the Active and Passive OMU cards IP address in OMC-R.2. Check and note the Active OMU card from OMC-R.3. Disconnect the Ethernet cable from the front of the Active OMU. 4. Check the md-interface link is up.
Expected Results: 1. The BSC OMC-R link should be stable
2.7.3 PROCESSOR REDUNDANCYInitial Condition:Each BSC is equipped with two OMU cards for processing in Control Node.Each BSC is equipped with two CEM for processing in Interface node. These OMU and CEM cards will be Active state and other card will be in Passive state.
Test Procedure:To check processor redundancy in Control Node, follow the steps given below:
1. Check at the OMCR, which OMU is active.2. Disconnect from the front of the active OMU the Ethernet (100baseT) cable.3. After a few minutes the active OMU restart and the switchover occur.
To check processor redundancy in Interface Node, follow the steps given below:
1. Using the TML software, a PC, and a cross connect 100baseT cable, Connect to the active CEM.2. Using the TML reset the active CEM3. The CEM swact, and the IN is operational
Expected Results: 1. The BSC processor in control and interface node should be stable
01.5 / EN 14/MAR/2004 Page 14/20
BSNL ACCEPTANCE TEST PLAN – BSC
2.8 To check External/Internal AlarmsAlarm Handling Test:The internal alarm can be extended to OMC-R. The Alarms can be handled, and once the alarm is attended to, it can be cleared.
Test Procedure 1:1. Start the MMI and Login in the OMC-R.2. Simulate power suppply alarm by switching off the power supply module.3. This alarm condition should be extended to OMC-R.4. Check for alarm at OMC-R.
Expected Results 1: The BSC processor in control and interface node should be stable.
Test Procedure 2:Removing cards from Control and Interface nodes. Check the alarms and note in the following table.
Note: Only CC-1, TMU, passive CEM, ATM-RM, LSA-RC, 8K-RM cards can be removed from the cabinet. OMU and MMS cards cannot be removed from the cabinet directly. It is not hot swap cards.
2.9 BACKUP AND RESTORE TESTInitial Conditions:BSS Network is up, and running.OMC-R is up and BSC is accessible from OMC-R. Test Procedure:
1. Take backup of BDE. 2. Restore the BDE3. Reset the BDA4. Build the BDA.
Expected Results:
1. After Restore BSC is up and operational.
01.5 / EN 14/MAR/2004 Page 16/20
BSNL ACCEPTANCE TEST PLAN – BSC
2.10 BSC PCM LOOPBACK Checks To check listed below pcm links loop back, using loop back push button in the CTMP board on the SAI (Service Area Interface). A sample check has to be performed from the following table.
2.11 Testing for Connecting BTSInitial Conditions:BTS and BSC is up and running.DDF is ready.Objects are created in OMC-R.OMC-R is up and BSC is accessible from OMC-R. Test Procedure:
1. Conect the BTS and BSC through DDF.2. Lock the BTS, and unlock.3. Verify that BTS is accessible from OMC-R.
Expected Results:
1. Lock and Unlock is possible.
2.12 Switchover and Diagnosis of SS7 controller
Initial Condition:Each BSC is equipped with two TMU cards for processing in Control Node.One TMU card will be Active state and other card will be in Passive state.
Test Procedure:To check processor redundancy in SS7, follow the steps given below:
1. Reset the active TMU card, which carries the SS7 link.2. The Passive TMU card should take the SS7 3. Open a telnet session to BSC, and open the following files for diagnosis report.
Expected Results: 1. Display dynamic data in Signaling Link Set will display the TMU card caring SS7 processing.
01.5 / EN 14/MAR/2004 Page 18/20
BSNL ACCEPTANCE TEST PLAN – BSC
2.13 Fixed coding scheme sector wise Initial Conditions:BSS Network is up, and running.OMC-R is up and BSC is accessible from OMC-R.The following hardware is available in network
1 BTS, 1 BSC, 1 PCU, 1 SGSN, 1 GGSN, 1 HLR, 1 Main Server, 1 GPRS phonesGSM and GPRS Network operational.Enable only one TDMA, TDMA 0 with main BCCH.Configure 4 PDTCH from TS 4 to TS 7 for GPRS calls.
Test Procedure:1. From the OMC-R set the coding scheme parameter to CS 1(in the TDMA object)2. Initiate a GPRS session, do a FTP transfer and check throughput.3. Change the coding scheme to CS – 2.4. Initiate a GPRS session, do a FTP transfer and check throughput.5. Change the coding scheme to CS – 3.6. Initiate a GPRS session, do a FTP transfer and check throughput.7. Change the coding scheme to CS – 4.8. Initiate a GPRS session, do a FTP transfer and check throughput.9. Verify that the throughput keeps increasing coding scheme changes from CS 1 to CS 4.
Expected Results
1. Coding scheme from 1 to 4 is supported in the GPRS network.
01.5 / EN 14/MAR/2004 Page 19/20
BSNL ACCEPTANCE TEST PLAN – BSC
Acceptance Testing has been conducted for ………………………. (Name and ID of Node) at…………………………………………………….. on ………… (Address of the Node) (Date)
and has been found satisfactory as per AT T&D circle.
