1 RNC Commissioning

Main Step Step 1 Checking Hardware

Step 2. Monitoring Unit Start Up Step 3. Logging into MMI system for first time Step 4. Create telnet or HTTP to print alarms Step 5. Setting calendar date and time for RNC Step 6. Enabling CPLD upgrade Step 7. Changing system name of the network element Step 8. Inspecting SW Build and Safe Copying Step 9. Inspecting the hardware management system Step 10. Interrogating the equipment database Step 11. Interrogating Hardware data Step 12. Interrogating Software build information Step 13. Inspecting mass memory devices Step14. Inspecting unit diagnostics and working states Step 15. Inspecting the messaging system Step 16. Inspecting synchronisation system Step 17. Configuring the VDS device Step 18. Verifying system start-up Step 19. Configured IP backbone Step 20. Configuring OMS Step 21. Testing IP connections for OMS Step 22. SW Upgrade

2 RNC Integration
Main Step

Step 1. Configuration of ESA24/ESA30

Step 2. Creating IuCS (ATM, IP)

Step 2. Creating IuCS (ATM, IP)

Step 3. Creating IuPS (ATM, IP)

Step 4. Creating IuR (ATM, IP)

Step5. Creating IuB (ATM, IP)

Step6. Creating OAM (Netact, IP)

Step7. Creating OAM (FlexiWBTS, ATM or IP)

3 Pre-Service handover Checks

Main Step

Pre-Checks (NSN)

4 FAC
Main Step

CSV file - Part and S/N verification

Sign-off of FAC document

Note: The Day count has been based on a Best Case scenario, were there are no HW, SW or any

RNC 2600 (RU20)

Responsibility

NSN - RNC Engineer, Field Manager, NSN Installation Contractor Vodacom - Vodacom Representative NSN - RNC Engineer NSN - RNC Engineer NSN - RNC Engineer NSN - BSC Engineer, RIC Team, NetAct resource if required NSN - RNC Engineer NSN - RNC Engineer NSN - RNC Engineer NSN - RNC Engineer NSN - RNC Engineer NSN - RNC Engineer NSN - RNC Engineer NSN - RNC Engineer NSN - RNC Engineer NSN - RNC Engineer NSN - RNC Engineer NSN - RNC Engineer NSN - RNC Engineer NSN - RNC Engineer, IP Planner if required for discrepancies NSN - RNC Engineer NSN - RNC Engineer NSN - RNC Engineer

Detail Activity Physical Cabling Configure Interface of ESA Route Configuration

Physical Cabling Logical Signalling Configuration

SCCP Parameter Modification IUCS Object Creation Physical Cabling Logical Signalling Configuration SCCP Parameter Modification IUPS Object Creation Physical Cabling Logical Signalling Configuration SCCP Parameter Modification IUR Object Creation Physical Cabling Tunnel Creation on the TX IPNB / COCO Creation (depend on the final TX) Configuration on the OMS & OMU Configuration on the NetAct Side Route Configuration / ATM Link IP Address / ATM Info (depend on the final TX)

Responsibility

NSN - RNC Engineer Vodacom Representative for Acceptance Signoff

Responsibility

NSN - Project Manager Vodacom - Logistics Manager

NSN - Project Manager Vodacom - Project Manager

Case scenario, were there are no HW, SW or any other issues found, and all transmission and other connect

Expected schedule

Day1

Day1 Day2 Day2 Day2 Day2 Day3 Day2 Day2 Day3 Day3 Day3 Day3 Day3 Day3 Day4 Day4 Day4 Day4 Day4 Day4 Day5

Requirements / Responsible Person Physical Port (VDC supply the available port to NSN - NPO) IP Address Space (VDC Supply the available subnet to NSN - NPO for the OAM Link) Subnet Information & GW (VDC supply the information about the router/hop to reach NetAct server from RNC to NSN - NPO. NSN - NPO prepare the datafill and Schematic diagram for the route) Physical Port (VDC supply the available port to NSN - NPO) SPC Information of the MSC/MGW (VDC supply the information about the MSC and/or MGW where RNC will be connected to to NSN - NPO)

Datafill (NSN - NPO will compile the datafill based on the supplied information from VDC and Will provide the feature list need to activate based on the agreement with the customer) Datafill (NSN - NPO will compile the datafill based on the supplied information from VDC) Physical Port (VDC supply the available port to NSN - NPO) SPC Information of the SGSN/GGSN (VDC supply the information about the MSC and/or MGW where RNC will be connected to to NSN - NPO) Datafill (NSN - NPO will compile the datafill based on the supplied information from VDC and Will provide the feature list need to activate based on the agreement with the customer) Datafill (NSN - NPO will compile the datafill based on the supplied information from VDC) Physical Port (VDC supply the available port to NSN - NPO) SPC Information of the neighboring RNCs(VDC supply the information about the MSC and/or MGW where RNC will be connected to to NSN - NPO) Datafill (NSN - NPO will compile the datafill based on the supplied information from VDC and Will provide the feature list need to activate based on the agreement with the customer) Datafill (NSN - NPO will compile the datafill based on the supplied information from VDC) Physical Port (VDC supply the available port to NSN - NPO) TX Information (VDC Supply the available TX to NSN - NPO) Datafill (NSN - NPO will compile the datafill based on the supplied information from VDC)

Datafill (NSN - NPO will compile the datafill based on the supplied information from VDC) Datafill (NSN - NPO will compile the datafill based on the supplied information from VDC) Datafill (NSN - NPO will compile the datafill based on the supplied information from VDC) Datafill (NSN - NPO will compile the datafill based on the supplied information from VDC)

Expected schedule

Day 8

Expected schedule

Day 9

Day 10

, SW or any other issues found, and all transmission and other connections is in place and on time and in wor

Comments Confirm all CNIB and PCM cabling, and labelling, before NSN Installation Contractor leave site. CR to be requested at least 48hrs before power-up activity needs to be performed, Vodacom representative is required on site for the power-up activity, the activity is performed at night (22h00 till 04h00). Confirm that all units start up in normal WO state. Any faulty units need to be identified and send for repairs. Confirm any IP discrepancies with NPO and VC Planning. Confirm NTP Server IP address and set on OMS & OMU, and confirm time zone settings. Check with RIC if OK.

checked for both TBU-0 and TBU-1

Test on SFU-0 and SFU-1 All cables should be connected Requires an RNC Restart, confirm all units return to Working State - notice 0691 WORKING STATE CHANGE ACTIVATED.... All LAN cables must be installed for this (VC), Ips to be defined for OMU as per IP plan

RNC Restart required

Subtopics

See NED for RU10 or RU20. Access and IP plan provided by NPO planning. All the Intergation will be done by NSN - RNC Eng. If Something missed during the Integration the Engineer will coordinate with NSN - NPO & Customer.

NSN - RNC Engineer, NPO resource if required Vodacom - VC Representative, Tx RAN CORE if required

NSN - RNC Engineer, NPO resource if required Vodacom - VC Representative, Cisco Engineer if required

NSN - RNC Engineer, NPO resource if required, RIC Vodacom - VC Representative

NSN - RNC Engineer, NPO resource if required Vodacom - VC Representative, Tellabs Engineer, ATM & IP Resource

NSN - RNC Engineer, NetAct Resource, NPO resource if required Vodacom - VC Representative

NSN - RNC Engineer, NPO resource if required Vodacom - VC Representative

Comments

Final checks and on site BSC acceptance.

Comments

on time and in working order.

Expected schedule

Day 5

Day 5

Day 6

Day 7

Day 7

Day 7

Day 7

Comments

In case of issues, an VC CORE resource might be required for the connection to the MSS via the MGW.

In case of issues, an VC Cisco resource might be required for the connection to the 7609's

Confirm between which RNC Iur connections was created, also confirm that adjacencies for the Node-B and Flexi has been created for the correct RNC's for testing of handovers. NPO can provide XML for adjacencies,

Creation of links from the Node-B & Flexi, to the RNC, via Tellabs. This is done by 2 different sections from Vodacom.

Integration to NetAct