Tools

• Access to OSS server

• XShell to run Moshell

• EMAS or Moshell

• FTP client, e.g. Total Commander

Important IP Add.

• OSS: 10.10.4.199 used to launch EMAS

• OSS Server: 10.10.4.194 used to load the scripts

• OMNIF: 10.10.4.199 used to run Moshell

Node B Integration Procedure

Note: Assuming all E1 connections are ready and stable before integration.

Load files to OSS

• Use Total Commander to load scripts to OSS server (IP Add. 10.10.4.194)

• Scripts to be loaded– ARW– AAL2RC– SAC– CELL– UR

• Note: External HW & OAM scripts are loaded at RBS

Load to OSS Server

Load ARW

Ext.HW & OAM scripts loaded at

RBS

folder location

Load AAL2RC, SAC & CELL

folder location

Load UR

Neighbor scripts (utran relation)

folder location

Run & Import ARW Scripts

• To launch WCDMA RAN Explorer– Start OSSRight

clickConfigurationWCDMA radio access networkWCDMA RAN Explorer

• Basic procedure to load ARW1. New Planned Config.

2. Open Planned Config.

3. RBS Wizard (Import)

4. Activate Planned Config.

Launch WCDMA RAN Explorer

1.New, 2.Open, 3.RBS Wizard & 4.Activate

1.New, 2.Open, 3.RBS Wizard & 4.Activate

Load remaining scripts

• Similar procedure with ARW scripts except use Import Planned Config. instead of RBS Wizard

1. New Planned Config.

2. Open Planned Config.

3. Import Planned Config.

4. Activate Planned Config

Load remaining scripts

1. Load AAL2RC, SAC & Cell

2. Synchronize RBS with OSS3. Reload ARW script to activate

RBS 4. Load UR

1.New, 2.Open, 3.Import & 4.Activate

Synchronize

When synchronized, status will change to

connected & synchronize

Reload ARW

Load UR

UR Data Added

UR Data Added

Verify AtmPort connecting Node B to RXI

• Launch RANAG EM using ONE• Identify the AtmPort carrying the

related E1 links to Node B• Check status of E1 links (should be

enabled)• ASP engineer to disconnect 1st E1 at

site, verify E1 status at RXI• Carry out same process for 2nd E1• This process is to verify the E1

connectivity from far end to RXI

Launch ONE

Launch RANAG EM

Check E1 status

Test Calls

• Unlock and enable all cells at RNC

• Contractor to do test call sector by sector at site

• Test calls can be monitored using: get radio command in RBS using Moshell

• If test call successful, contractor can leave site, else, troubleshoot/lock the site

Unlock NBAP & Cells

Unlock Node Synch TP

Unlock Transport Channels

Final Step: Create CV and set startable

• Launch RBS EMSoftwareSwManagementRight Click Configuration VersionCreatetype new CV name & add commentRight Click on new CVSet Startable

• Format of new CV– Mu_<CV name>_<date>_<time>– Add comments, e.g. JAWABM integrated to RNHTA

• Absolute final step!-Send daily summary to colleagues and bosses in Managed Services, MiTV

Create CV & Set Startable

Discussion

• To discuss the contents of the scripts loaded

• To discuss where and the purpose the scripts are loaded

• To explain some terms in RAN

Purpose of Each Process• Loading scripts:

– To define the configurations planned in RNC, RXI and RBS into the OSS

• Synchronization– To ensure the RAN elements are in sync with OSS

• Unlock cells– To enable intended cells, NBAP & Node Sync. TP

after synchronization• Test calls

– To verify each sector is functioning properly• Create CV

– Only the latest CV is set for the RBS. Useful when software upgrade fails or RBS restarts, RBS will roll back to the latest CV

Info. in ARW script

• Add RBS Wizard script• Activated at RNC, RXI and RBS• Main Subrack num.• IMA group• ATM port• RXI name• RNC name• RBS name• DNS name• Node security state• Time zone• Iub link name

Info. in AAL2RC script

• ATM Adaptation Layer 2 Routing Case script

• Activated at RXI• Vendor name• RNC name• AAL2 data routing case• Route list• Route priority list

Info. in SAC script

• Service area code script

• Vendor name

• Service area num.

• Date and time

Info. in Cell script

• RNC name

• RBS name

• Scrambling code

• Max. Tx power

• Iub link name

• Data format version

• Tx timing

Info. in UR script

• Utran relation script• Activated at RNC• Cell neighbor details• Neighbour RNC name• Neighbor RBS name• Utran cell ID• Load sharing candidate• Data format version

Info. in OAM Access script

• Operation, Administration and Maintenance Access script

• Loaded at RBS• RBS Ethernet IP Add. & mask• Mub A & Mub B IP Add.• VC32 & VC33• Node IP Add. connecting to Mub A & Mub B• Domain name• DNS IP Add.

Info. in Ext. HW script

• External hardware script• Loaded at RBS• HW configuration of various equipment such as:

– External alarm– Power supply– Battery backup– Sector number, beam direction, lat. & long. – TMA config.– Antenna config.– Local cell config.– Alarms definition

Terms in RANNode B Application Part (NBAP) Signalling protocol responsible for the control of the Node-B by

the RNC. These signalling links are carried over Iub

NBAP Common Controls overall Node-B functionality

NBAP Dedicated Controls separate cells or sectors of the Node-B

Forward Access Channel (FACH) A point-to-multipoint downlink transport channel used to convey data to one or more UEs

Random Access Channel (RACH) Uplink Transport Channel used by the UE to initiate access to the WCDMA RAN access point. It can also be used to carry small data packets

Paging Channel (PCH) Downlink point-to-multipoint Transport Channel, used to page a group of UEs in the Coverage Area of the cell.

High Speed Downlink Shared Channel (HSDHCH)

Used in HSDPA to send packets on the downlink to the UEs.

Node Synchronization Termination Point (NodeSynchTp) 1 & 2

All links for Node Synchronization are terminated on the RNC and the new RBS

ATM Adaptaion Layer 2 (AAL2) Transport mechanism in WCDMA RAN

Inverse Multiplexing for ATM (IMA) Protocol that facilitates combining multiple low-speed ATM circuits into a single logical pipe

Conclusion

• All information needed in RAN are defined in the scripts loaded at– RNC– RXI– RBS

• Info. given by MiTV (in Excel) can be verified in the scripts

• Info. in the scripts help in troubleshooting, e.g. RBS uses TMA but scripts use ASC setting