Call Setup

Signalling Connection Handling: Call Setup

UE

Node B

RNC
The UE sends RRC Connection Request message with an establishment code (Emergency call, Registration, Signalling, Originating Call, IRAT Cell Reselection...).

RRC: RRC Connection Request (CCCH)

The Admission Control algorithm checks if the new radio link can be allowed in the cell, power control algorithm sets the initial DL power, UL SIR target, code control algorithm allocates the UL-DL SC code and DL Channelization code. NBAP: Radio Link Setup Request NBAP: Radio Link Setup Response AAL2SIG: ERQ AAL2SIG: ECF

The RNC orders the RBS to reserve the necessary resources The transport bearer (AAL2 connection) needed for signaling is set up over Iub by the RNC

RRC: RRC Connection Setup (CCCH)

The RRC Connection Setup message is used to specify the (signalling) radio bearer, the transport channel and the physical channel characteristics both in the UL and downlink directions.

Call Setup RRC Part

UE

Node B
RRC: RRC Connection Setup (CCCH) L1 synchronization

RNC

NBAP: Radio Link Restore Indication

Once UE establish the radio link, the RBS notifies the achievement of the new uplink radio interface synchronization Integrity and Ciphering related parameters, together with the UE capabilities requested in RRC setup message are included. These information are used by the RAB establishment procedure, UE Security Handling, and the Channel Switching function.

RRC: RRC Connection Setup Complete (DCCH)

UE in CELL_DCH state

Iu Control Plane Connection: Call Setup

UE

Node B

RNC

SGSN

RRC: Initial Direct Transfer (CM Service Request)

The establishment is initiated by the reception of an RRC message containing the NAS message that originally triggered the Signaling Connection setup. The SRNC sets up a Iu control plane connection to the CN and sends the RANAP message to the CN. This RANAP message includes the UE NAS message, current location information of UE and the Iu control plane connection identifier. SGSN/MSC performs authentication to make sure that the UE is genuine.

RANAP: Initial UE Message (CM Service Request)

SCCP: CC

RANAP: Direct Transfer (Authentication Request) RRC:DL Direct Transfer (Authentication Request) RRC:UL Direct Transfer (Authentication Response) RANAP: Direct Transfer (Authentication Response)

RANAP: Common ID

After the establishment of the Signaling Connection, the CN sends RANAP Common ID message to inform the SRNC about the permanent NAS UE Identity (IMSI).

RAB Establishment Part

UE

Node B

RNC
RANAP:RAB Assignment Request

CN

The CN initiates establishment of the Radio Access Bearer using the RAB Assignment Request message. This message includes the QoS of the call being established. The SRNC determines the Radio Connection configuration and checks the UE capabilities if the configuration can be supported by the UE. SRNC requests Node B to prepare establishment of DCH to carry the RAB. Node B allocates the resources and responds with the Ready message. The data transport bearer over the Iu CS/PS and Iub is set up by the RNC SRNC sends the RB Setup message to add the new DCH

NBAP: Radio Link Reconfiguration Prepare NBAP:Radio Link Reconfiguration Ready ALCAP:ERQ ALCAP:ECF ALCAP:ERQ ALCAP:ECF RRC:Radio Bearer Setup RRC:Radio Bearer Setup Complete RANAP:RAB Assignment Response

Reasons for RRC+RAB failures If resources are not allocated in the NodeB (Admission control, Power usage per RL, DL channelization codes, DL/UL Channel element usage) If resources are not allocated in the RNC subracks related to MP load, any outages or software issues If Iub link is not established, Aal2 signalling issues Synchronization failures (link Imbalance) TMA, feeder, jumper, swapped sectors, faulty NodeB, RAX/Tx board) Radio link connection reset (happens in PS domain)

Incorrect NodeB script files, software issues

RNC module

Reasons for RAB failures Insufficient channel elements is related to faulty Tx and RAX boards. May need additional boards RAB is assigned by CN and it depends upon kind of service requested by UE (conversational, streaming, interactive and background). So, incorrect QOS requirements can lead to RAB failures. Different RABs will need different protection and hense different transport channels Check DL BLER for different services During call setup, handover to 2G happens duirng RAB setup. So, IRAT neighbors and priority should be properly defined. Multiple data should be correlated to isolate the problem

Importance of defining correct neighbors and Priority

2-Way SHO: SC 165 is the serving cell, in active set & SC221 qualifies to be added to the active set.

Result - BQU4659C (SC165) 1 2 3 4 5 6 7 8 9 10 11 12 13 149 157 52 68 323 331 221 229 124 133 141 268 395 17 18 19 20 21 22 23 24 25 26 27 28 29 403 Result - BQU4841A (SC221) 1 2 3 4 5 6 7 8 229 237 395 403 165 268 323 331 17 18 19 20 21 22 23 24 213 125 96

14 28 30

15 16 36 237 31 32

9 10 68 141 25 26

11 12 13 14 15 16 28 149 157 181 155 236 27 28 29 30 31 32

1 17

2 18

3 19

4 20

5 21

6 22

7 23

8 24

9 25

10 26

11 27

12 28

13 29

14 30

15 31

16 32

Temp Array 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

STEP 1 - Add both the active cells (A) and (B) to the listed set in the same position as they existed previously

Result - BQU4659C (SC165) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 165 149 157 52 68 323 331 221 229 124 133 141 268 395 17 18 19 20 21 22 23 24 25 26 27 28 29 30 237 403 Result - BQU4841A (SC221) 1 2 3 4 5 6 7 8 9 221 229 237 395 403 165 268 323 331 17 18 19 20 21 22 23 24 25 236 213 125 96

15 28 31

16 36 32

10 11 68 141 26 27

12 13 14 15 16 28 149 157 181 155 28 29 30 31 32

1 165 17

2 18

3 19

4 20

5 21

6 22

8 221 23 24

9 25

10 26

11 27

12 28

13 29

14 30

15 31

16 32

Temp Array 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

STEP 2 - Take the neighbor cell with the highest priority for the best active set cell, cell(A), and if it already exists in the old listed set add it to the new listed set in the same position. If it does not exist in the old listed set, then the position does not matter, therefore store it for addition later in a temporary array.

Result - BQU4659C (SC165) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 165 149 157 52 68 323 331 221 229 124 133 141 268 395 17 18 19 20 21 22 23 24 25 26 27 28 29 30 237 403 Result - BQU4841A (SC221) 1 2 3 4 5 6 7 8 9 221 229 237 395 403 165 268 323 331 17 18 19 20 21 22 23 24 25 236 213 125 96

15 28 31

16 36 32

10 11 68 141 26 27

12 13 14 15 16 28 149 157 181 155 28 29 30 31 32

1 2 165 149 17 18

3 19

4 20

5 21

6 22

8 221 23 24

9 25

10 26

11 27

12 28

13 29

14 30

15 31

16 32

Temp Array 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

STEP 3 - Take the neighbor cell with the highest priority for the second best active set cell(B), and if it already exists in th e old listed set add it to the new listed set in the same position. If it does not exist in the old listed set, then the position does not matter and it can be stored in a temporary array for later addition. Store the neighbo ring cell only if it does not already exist in the temporary array (avoid duplicate). If it is already stored in the temporary array, take the next neighboring cell in priority order from the next cell in the Active Set, cell(A) applying the same rules.

Result - BQU4659C (SC165) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 165 149 157 52 68 323 331 221 229 124 133 141 268 395 17 18 19 20 21 22 23 24 25 26 27 28 29 30 237 403 Result - BQU4841A (SC221) 1 2 3 4 5 6 7 8 9 221 229 237 395 403 165 268 323 331 17 18 19 20 21 22 23 24 25 236 213 125 96

15 28 31

16 36 32

10 11 68 141 26 27

12 13 14 15 16 28 149 157 181 155 28 29 30 31 32

1 2 165 149 17 18

3 19

4 20

5 21

6 22

8 9 221 229 23 24 25

10 26

11 27

12 28

13 29

14 30

15 31

16 32

Temp Array 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

STEP 4 - Repeat until all neighbor cells have been processed or until MaxIafMonSubsetIAF neighboring cells have been selected fo r the listed set.

Result - BQU4659C (SC165) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 165 149 157 52 68 323 331 221 229 124 133 141 268 395 17 18 19 20 21 22 23 24 25 26 27 28 29 30 237 403 Result - BQU4841A (SC221) 1 2 3 4 5 6 7 8 9 221 229 237 395 403 165 268 323 331 17 18 19 20 21 22 23 24 25 236 213 125 96

15 28 31

16 36 32

10 11 68 141 26 27

12 13 14 15 16 28 149 157 181 155 28 29 30 31 32

1 2 3 4 5 6 7 8 9 10 11 12 13 14 165 149 157 52 68 323 331 221 229 124 133 141 268 395 17 18 19 20 21 22 23 24 25 26 27 28 29 30 237 403 181 155 236 213 125 96

15 28 31

16 36 32

Temp Array 1 181 2 155 3 236 4 213 5 125 6 96 7 8 9 10 11 12 13 14 15 16

STEP 5 - Take the cells that have been selected to be included in the new listed set (stored in the temporary array) and add them to the listed set by filling the spaces that have not been filled in step (4), the neighboring cells are picked from the temporary array in the order they was stored (FIFO). (This makes sure that neighboring cells stored early in the temporary array will be the first to fill out the spaces in the listed set).

Future slides.

The following are some important KPIs to be monitored on a daily basis 1. Cell Availability 2. UL Synchronization failures 3. Voice Traffic Erlangs 4. Voice Access Failures

5. Voice Drops
6. Missing Neighbor 7. Inability to add neighbor

8. Voice 3G_2G IRAT Failure

9. Soft/Softer Overhead

If Cell Availability is 0, check the following Cell Reserved = 1 (not_reserved), all Accessclasses= FALSE. See next few slides for details Cell is locked If it has Critical or Major alarms, most likely there is a TT open. If not, open one and assign it to Switch/FOPS If you dont find any thing, it could be a sleepy. Restart NodeB as shown below

Go to WCDMA RAN Explorer as shown Scroll down and select the NodeB you want to troubleshoot as shown in the next slide

Go here to change Cell Reserved and Accessclass parameters

All 3G onair cells should be Not_Reserved. Click Apply after all changes

All of the following parameters [1 to 16] should be set to FALSE accessClassNBarred accessClassesBarredCS, accessClassesBarredPS

Note that Cell Status is automatically changed. Administrative State can be changed to Locked something to look out after a TT is closed

To check if the site is taking traffic, Right click on NodeB and go to Node Status Analyser

Click on each cell to check RRC counters below

If these counters are 0, cell is not taking any traffic. In case of Sleepy cell, you need to restart NodeB

Go to Element Manager to check Alarms, external TMA parameters, Restart RU, TxB, NodeB. Do a cold restart for NodeB in case of sleepy cell. Make sure you put reasons for restart including the TT number. Its better to call Switch if you want to restart

Go to SupervisionAlarm Log
Move the mouse over any alarm and click f1 to get description and troubleshooting options. You can populate TT or WO with these steps

Go to Terminal to troubleshoot T1, RU, FU and TMA

Step1

Step2

Step3

Enter 1 to get RSSI and x to exit. RSSI is read at RU. Normal RSSI (between -102 and -106) indicates good RU

This will give TMA current and FU voltage For RRU sites use 000900 instead of 001200 Optimum value for current is 100. 90 is the lower limit and would need FOPS to check TMA

Value should be 29xxx VSWR should be above 18

Use the following commands from NodeB to check the status of RU, FU and T1 st ru

st fu
st t1 pget t1 get radiolink al (alarms) Lga (alarm history for past year, to get most recent, type 24h for 24 hour period, 6h for 6 hour period, and so on). For T1 issues, assign TT to Switch. For hardware issues, assign TT or WO to FOPS

U1NC3658A> st tx 101119-11:55:25 11.166.154.67 8.0d RBS_NODE_MODEL_L_10_9 stopfile=/tmp/13776 ========================================================== ========================= Proxy Adm State Op. State MO ========================================================== ========================= 171 0 (DISABLED) Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1 199 1 (ENABLED) Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1

TO READ THE ERROR LOGS FOR HARDWARE:

U1NC3658A> lhsh 001000 te log read

10 slot number of HW. From above example it is the RAX board. Typically: Slot 4-9 are RAX boards, Slot 10-11 are TX boards Slot 2,4,6 are FU boards and so on. This allows you to further troubleshoot the HW on a board level.

Service Affecting Alarms AntennaBranch_AntennaSystemProblem AuxPlugInUnit_PiuConnectionLost Carrier_RejectSignalFromHardware Carrier_SignalNotReceivedWithinTime DbccDevice_GammaDownlinkFailure ExternalTma_LnaFailureBranchA ExternalTma_LnaFailureBranchB FuDeviceGroup_ExternalUnitFailure

Most likely there will be a TT open, if not, call Switch.

NbapCommon_Layer3SetupFailure
OpticalInterfaceLink_OpticalInterfaceLinkFailure RruDeviceGroup_GeneralHwError RuDeviceGroup_GammaUplinkFailure RuDeviceGroup_GeneralSwError

TpaDevice_AmplificationError
TrDeviceSet_GeneralHwError

Checking raw counter values from RNC RRC Attempts

From RNC, enter this command to check raw counters -m minushours 3 last 3 hours

-a aggregate for last 3 hrs

If you dont enter m 3 a, default is last 15 minutes

RAB Establishments and Success Check RAB Attempts and Success for 1 cell for last 15 minutes

Check RAB Attempts and Success for multiple sites using pipe (|) for last 1 hour aggregated (-a)

Voice and Packet Drops

Checking HS Stats

pmNoNormalRbReleaseHS Normal Release

pmNoSystemRbReleaseHS HS Drops

Check multiple sites and multiple counters pmx U1PH5293A|U1PH1009A pmTotNoRrcConnectReq|pmNoRabEstablish|pmNoNormalRa bReleaseSpeech|pmNoSystemRabReleaseSpeech -m 1 -a pmx U1PH5293A|U1PH1009A pmTotNoRrcConnectReq|pmNoRabEstablish|pmNoNormalRa bReleaseSpeech|pmNoSystemRabReleaseSpeech -s 20090708.0000 -e 20090708.1000 a -s start 20090708.0000 12 AM July 8 -e end 20090708.1000 10 AM July8 -a aggregate

PMR command options

pmr s 20090825.1000 e 20090825.1100 -a pmr s 20090825.1000 e 20090825.1100 pmr m 3 a Pmr m 2

Future slides.