Worksheet in VDC SRAN WR Pilot Info 31.5.12.xls

7/30/2019 Worksheet in VDC SRAN WR Pilot Info 31.5.12.xls

1/17

1 RNC Commissioning

Main Step

Step 1 Checking Hardware

Step 2. Monitoring Unit Start Up

Step 3. Logging in to MMI system for f i rs t t im e

Step 4. Create telnet or HTTP to print alarms

Step 5. Sett ing c alendar date and time fo r RNC

Step 6. Enabl ing CPLD up grade

Step 7. Changing s ystem n ame of the network element

Step 8. Inspecting SW Bui ld and Safe Copyin g

Step 9. Inspecting the hardware management system

Step 10. Interrogating th e equipm ent database

Step 11. Interrogating Hardware data

Step 12. Interrogating Softw are bui ld info rmation

Step 13. Inspecting m ass memory devices

Step14. Inspecting un it diagnostics and wo rking states

Step 15. Inspecting th e messaging sy stem

Step 16. Inspecting sy nchr onisation sy stem

Step 17. Configu ring th e VDS device

Step 18. Veri fying sy stem s tart-up

Step 19. Configu red IP backbone

Step 20. Configu ring OMS

Step 21. Testing IP conn ections for OMS

Step 22. SW Upg rade

2 RNC Integration

Main Step

Step 1. Configuration of ESA24/ESA30

Step 2. Creating IuCS (ATM, IP)


2/17

3 Pre-Service handover Checks

Main Step

Pre-Checks (NSN)

4 FAC

Main Step

CSV file - Part and S/N verification

Step7. Creating OAM (FlexiWBTS, ATM or IP)

Step 3. Creating IuPS (ATM, IP)

Step 4. Creating IuR (ATM, IP)

Step5. Creating IuB (ATM, IP)

Step6. Creating OAM (Netact, IP)


3/17

Sign-off of FAC document

Note: The Day count has been based on a Best Case sce


4/17

RNC 2600 (RU20)

Responsibility

NSN - RNC Engineer, Field Manager, NSN

Installation ContractorVodacom - Vodacom Representative

NSN - RNC Engineer

NSN - RNC Engineer

NSN - RNC Engineer

NSN - BSC Engineer, RIC Team, NetAct resource

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

discrepanciesNSN - RNC Engineer

NSN - RNC Engineer

NSN - RNC Engineer

Detail Activity

Physical Cabl ing

Configu re Interface of ESA

Route Configu ration

Physical Cabl ing

Log ical Signal l ing Config uration


5/17

SCCP Parameter Mod if ication

IUCS Object Creation

Physical Cabl ing



IUPS Objec t Creation

Physical Cabl ing



IUR Object Creation

Physical Cabl ing

Tunnel Creation on the TX

IPNB / COCO Creation (depend o n th e final

TX)

Configu ration on the OMS & OMU

Conf igurat ion o n the NetAct Side

Route Configu ration / ATM Link

IP Add ress / ATM Info (depend o n the final

TX)

Responsibility

NSN - RNC Engineer

Vodacom Representative for Acceptance Sign-

off

Responsibility

NSN - Project Manager

Vodacom - Logistics Manager


6/17

NSN - Project Manager

Vodacom - Project Manager

nario, were there are no HW, SW or a


7/17

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 supp ly the avai lable port to NSN - NPO)

IP Address Space (VDC Supp ly the avai lable subnet to NSN - NPO for the OAM Lin k)

Subnet Informat ion & GW (VDC supply the in format ion about the router /hop to reach NetAct server from

RNC to NSN - NPO. NSN - NPO prepare the datafi l l and Sch ematic diagram for th e route)


SPC Inform ation of th e MSC/MGW (VDC sup ply the info rmation about th e MSC and/or MGW where RNC

wil l be conn ected to to NSN - NPO)


8/17

Datafi ll (NSN - NPO wil l compi le the datafi l l based on th e suppl ied info rmation from VDC and Wil l pro vide

the feature l ist need to activate based on th e agreement w ith the cus tom er)

Datafi ll (NSN - NPO wil l compi le the datafi l l based on th e suppl ied info rmation from VDC)


SPC Inform ation of th e SGSN/GGSN (VDC supp ly the inform ation about t he MSC and/or MGW where RNC

wil l be conn ected to to NSN - NPO)





SPC Inform ation of the neighbo ring RNCs(VDC sup ply the inform ation about the MSC and/or MGW where

RNC wil l be conn ected to to NSN - NPO)





TX Information (VDC Supply the avai lable TX to NSN - NPO)






Expected schedule

Day 8

Expected schedule

Day 9


9/17

Day 10

y other issues found, and all transmission and other connections is in place and on time a


10/17

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 requiredon 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


11/17


Vodacom - VC Representative, Cisco Engineer if required

NSN - RNC Engineer, NPO resource if required, RIC

Vodacom - VC Representative


Vodacom - VC Representative, Tellabs Engineer, ATM & IP Resource

NSN - RNC Engineer, NetAct Resource, NPO resource if required




Comments

Final checks and on site BSC acceptance.

Comments


12/17

nd in working order.


13/17

Expected

schedule

Day 5

Day 5


14/17

Day 6

Day 7

Day 7

Day 7

Day 7


15/17


16/17

Comments

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


17/17

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

Worksheet in VDC SRAN WR Pilot Info 31.5.12.xls

Documents

Transcript of Worksheet in VDC SRAN WR Pilot Info 31.5.12.xls