RNC Role in network

Manage the Radio Access Bearers for user data transport

Manage and optimize the Radio Network resources

The 3 RNC Roles

Manage the Radio Access Bearers for user data transport:

trafficClass conversationalSpeech

Timestamp UE RBS RNC CN Prot Message --------------------------------------------------------------------------------

[16:48:23.772]0117 <<---------<< (RANAP) RAB-AssignmentRequest (UE:5668) (RAB-ID=0x01) (maxBitRate=12200) (guaranteedBitRate=4750) (addr=461103200000000) (bindID=0x11C0570E)

AMR12.2 (kbps)AMR7.95AMR5.9AMR4.75

[16:48:23.776]0117 <<---<< (NBAP) RadioLinkReconfigurationPrepareFDD (tID=2321L) (UE:5668) (RBS.CCID=18) (BearerReq:bearerNotRequested) (dCH-ID=31) (dCH-ID=8) (dCH-ID=9) (dCH-ID=10) (rL-ID=0)[16:48:23.784]0117 >>--->> (NBAP) RadioLinkReconfigurationReady (tID=2321L) (UE:5668) (RNC.CCID=331) (rL-ID=0) (dCH-ID=8) (bindID=0xDD7003B7) (addr=240050003226019)[16:48:23.804]0117 <<--------<< (RRC) radioBearerSetup (UE:5668) (rrcTID=0) (cell-DCH) (RAB-ID=0x01) (GSM-MAP) (cs-domain) (ULsf64)[16:48:23.804]0117 <<---<< (NBAP) RadioLinkReconfigurationCommit (tID=2388L) (UE:5668) (RBS.CCID=18) (CFN=208)[16:48:24.424]0117 >>-------->> (RRC) radioBearerSetupComplete (UE:5668) (rrcTID=0) (startVal=0x3A)[16:48:24.428]0117 >>--------->> (RANAP) RAB-AssignmentResponse (UE:5668) (RAB-SetupOrModifiedList) (RAB-ID=0x01)

Video Call[10:20:56.660]0015 <<---<< (RANAP) RAB-AssignmentRequest (UE:220) (RAB-ID=0x01) (maxBitRate=64000) (guaranteedBitRate=64000) (addr=240010200000000) (bindID=0x3A01EAD2)

trafficClass backgroundPacket NB HS[10:44:24.184]0015 <<---<< (RANAP) RAB-AssignmentRequest (UE:927) (RAB-ID=0x05) (maxBitRate=7232000) (addr=217.214.245.89) (Alt-RAB-Parameters)Packet 3 HS[08:37:55.520]0014 <<---<< (RANAP) RAB-AssignmentRequest (UE:4915) (RAB-ID=0x05) (maxBitRate=7296000) (addr=10.64.102.1) (Alt-RAB-Parameters)Packet 3 R99[08:38:29.132]0014 <<---<< (RANAP) RAB-AssignmentRequest (UE:5116) (RAB-ID=0x05) (maxBitRate=384000) (addr=10.64.102.1) (Alt-RAB-Parameters) Packet 3 21Mbps[21:31:14.360]0116 <<---<< (RANAP) RAB-AssignmentRequest (UE:5387) (RAB-ID=0x05) (maxBitRate=16000000) (addr=0A406601)

System Resource Handling: RNC is constantly monitoring a set of HW and SW resources. The result from monitoring will serve as an input for Admission and congestion, Refer to document 83/1553-HSD 101 02/6 Capacity Management

1. Downlink Channelization Codes Monitor (soft congestion)The Downlink Channelization Code Monitor provides a measure for code tree utilization in the downlink.

2. Downlink Transmitted Carrier Power MonitorFor each call setup, the cell is transmitting additional power ncessary to maintain the new call. That power is added up to the total downlink transmitted power.

3. ASE MonitorThe ASE intends to express to some extend the static load on the air-interface caused by radio bearers in a connection in a cell relative to the static load caused by a set of radio bearers carrying a regular conversational CS speech 12.2 kbps RABs

4. Received Total Wideband Power MonitorThe uplink Received Total Wideband Power (RTWP) is monitored in order to provide information to RN Congestion Control regarding the uplink interference

5. RBS Hardware Monitor (soft congestion)HW dl is the total hardware usage in downlink CE rls dl is the number of CE in downlink used by a radio link settotal CE dl is the total available CE in downlink (as reported by the RBS) HW ul is the total hardware usage in uplink CE rls ul is the number of CE in uplink used by a radio link set total CE ul is the current total available CE in uplink (as reported by the RBS)

RN Soft Congestion control is part of the RN Admission Control feature, and aims to increase the accessibility by admitting users in a cell in case of resource shortage, if a low priority user can lower its rate or be pre-empted.

The behavior of RN Soft Congestion control differs depending on the request class: Non-guaranteed requests:

Can reduce the rate of other lower priority, non-guaranteed connection parts in steps (for example from interactive PS 384/64 to interactive PS 128/64), down to their lowest retainable rate. Equal priority request and connection parts will equally balance their resource utilization (for example a request for interactive PS 64/64 can reduce the rate of an equal priority interactive PS 128/64 to interactive PS 64/64, but not to lower rates).

Guaranteed requests: Can reduce the rate of any priority, non-guaranteed connection parts in steps down to their lowest retainable rate. If that is not sufficient, RN Soft Congestion can pre-empt existing guaranteed RABs of lower priority, or non-guaranteed RABs at the lowest retainable rate if request is pre-emption capable and connection part targeted is pre-emption vulnerable.

Note that in the current release of the product, RN Soft Congestion control does not target radio connections originating over Iur. Also note that MBMS control channels MCCH and MICH are not targeted.

The 3 RNC Roles

RNC SRNC

Core Network

Node B Node B Node B Node B

Iu Iu

Iur

Iub IubIub Iub

C ha n n e

l

4s

ak

dj

fl

ö

la

dk

sf

j

as

ld

f

öa

d

öl

kd

qw

e

rr

ti

uo

d

kl

c

.

sa

kd

jf

lö

l

ad

ks

fj

as

ld

f

öa

d

öl

kd

qw

e

rr

ti

uo

d

kl

c

.

sa

kd

jf

lö

l

ad

ks

fj

as

ld

f

öa

d

öl

kd

qw

e

rr

ti

uo

d

kl

c

.UE

UTRANSRNSRNS

SRNC• Each connected mode UE is controlled by a Serving RNC (SRNC)• The SRNC terminates Iu towards the CN• The SRNC terminates Uu L2 UP & CP towards UE

DRNC SRNC

Core Network

Node B Node B Node B Node B

Iu Iu

Iur

Iub IubIub Iub

C ha n n e

l

4s

ak

dj

fl

ö

la

dk

sf

j

as

ld

f

öa

d

öl

kd

qw

e

rr

ti

uo

d

kl

c

.

sa

kd

jf

lö

l

ad

ks

fj

as

ld

f

öa

d

öl

kd

qw

e

rr

ti

uo

d

kl

c

.

sa

kd

jf

lö

l

ad

ks

fj

as

ld

f

öa

d

öl

kd

qw

e

rr

ti

uo

d

kl

c

.UE

UTRANSRNSDRNS

DRNC • Inter RNC soft handover requires a second RNC to be involved• Such an RNC lending resources to an SRNC for a specific UE acts as a Drift RNC (DRNC).

CRNC• Each RNC acts as Controlling RNC (CRNC) for the directly connected Node B’s and their cells• The CRNC controls the radio resources of its cells

CRNC CRNC

Core Network

Node B Node B Node B Node B

Iu Iu

Iur

Iub IubIub Iub

UTRANRNSRNS

Two Subrack Types

– Main & Extension

Scalable capacity

– 1-6 subracks in 1-2 cabinets

Only 6 basic board types

– Common platform (CPP also used in MGW,

RBS and CDMA2000 nodes)

HW designed for any mix of traffic (CS/PS)

Hot expansion & repair

High reliability: Redundant HW and Soft SW upgrade

+ +

+

Main Subrack

Extension Subrack

- -

Modular RNCA

Type 50

BType 175

CType 300

FType 675

Future proof architectureSW centric implementation

Main Subrack HW R5

SC

B3

SX

B3

TU

B2

Fan Unit

SC

B3

TU

B2

ET

B

ET

B

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28

GP

B5

3 - R

NC

SC

CP

1 M

P - A

cti v

e

GP

B5

3 - R

NC

SC

CP

1 M

P - S

tan

db

y

GP

B5

3 - R

NC

Ce

ntra

l MP

- Ac

t ive

GP

B5

3 - R

NC

Ce

ntra

l MP

- Sta

nd

by

GP

B5

3 - R

NC

O&

M M

P - A

ctiv

e

GP

B5

3 - R

NC

O&

M M

P - A

ctiv

e

GP

B5

3 - R

NC

Mo

du

l e M

P - A

ct iv

e

GP

B5

3 - R

NC

Mo

du

l e M

P - S

tan

db

y

GP

B5

3 - R

NC

Mo

du

l e M

P - A

ct iv

e

ET

B

ET

B

ET

B

SP

B2

1

SP

B2

1

SP

B2

1

SP

B2

1

SP

B2

1

SX

B3

GP

B5

3 - R

NC

SC

CP

2 M

P - A

cti v

e

GP

B5

3 - R

NC

SC

CP

2 M

P - S

tan

db

y ET

B

Extension Subrack HW R5

Future proof architectureSW centric implementation

SC

B3

Fan Unit

SC

B3

1 2 3 4 5 6 7 8 9 10 11 17 18 19 20 21 22 23 24 25 26 27 2812 13 14 15 16

GP

B5

3 - R

NC

Mo

du

l e M

P –

Sta

nd

by

GP

B5

3 - R

NC

Mo

du

l e M

P - A

ctiv

e

GP

B5

3 - R

NC

Mo

du

l e M

P –

Ac

tive

3

GP

B5

3 - R

NC

Mo

du

l e M

P - A

ctiv

e

GP

B5

3 - R

NC

Mo

du

l e M

P - A

ctiv

e

GP

B5

3 - R

NC

Mo

du

l e M

P - A

ctiv

e SP

B2

1

SP

B2

1

SP

B2

1

DB

SP

B2

1

SP

B2

1

SP

B2

1

SP

B2

1

SP

B2

1

SP

B2

1

DB

SP

B2

1

DB

or E

T-M

C4

1

DB

or E

T-M

C4

1

ET

B B

as

ic p

os

. 1

ET

B E

xte

nd

ed

po

s. 1

ET

B E

xte

nd

ed

po

s. 2

A

ET

B B

as

ic p

os

2

ET

B E

xte

nd

ed

po

s. 2

B

DB

or E

T-M

C4

1

Extension subrack n

DEV

ET

SCB

SCB

MP

Main subrack

DEV

ET

MP

SCB

SCB

SXB

SXB

Extension subrack n

DEV

ET

SCB

SCB

MP

ISL

Subrack Interconnection

• Hub structure– One main subrack– 0 - 5 extension subracks

• Inter Subrack Links (ISLs) – Up to 15 m with electrical

twisted pair

• 1 + 1 redundancy on ISL

Extension subrack n

DEV

ET

SCB

SCB

MPExtension subrack n

DEV

ET

SCB

SCB

MPExtension subrack n

DEV

ET

SCB

SCB

MP

Switch Core Board, SCB

• Function

– Cell switching

– Basic connections to extension subrack

– Synchronization distribution

– Power filtering

– Supervise subrack temperature

• Front connection

– Four Inter Subrack Links (ISLs)

– Subrack power inlets

– Fan power and control

• Capacity– 28 × 622 Mbps switching

– 310 Mbps per ISL (510 Mbps max aggregated)

• Subrack configuration– 2 boards in the main and 2 boards in the extension subrack

Switch eXtension Board, SXB

• Function– Additional connections to extension subrack

• Front connection– Four Inter Subrack Links (ISLs)

• Capacity– 310 Mbps of ISL (510 Mbps max aggregated)

• Subrack configuration– 2 boards in the main subrack

General purpose Processor Board, GPB

• Function– Main Processor (MP)

– Basic CPP functions (IP-router connection handling, O&M etc..)

– AAL0 and AAL5 termination

• Front connection– 2 Ethernet 10baseT/100baseT

– 2 RS-232 (not used in RNC)

• Capacity– PowerPC

– Up to 1.5 Gbyte flash and 1 Gbyte RAM

– PowerQuick II for communication

• Subrack configuration– 11 boards in main and 6 in the extension subrack

Special purpose Processor Board, SPB

• Function– Application-dependent processing (SW)– AAL0, AAL2, and AAL5 termination

• Front connection– None.

• Capacity

– 5 × Special purpose Processor Modules (SPMs)

– PowerPC

• Subrack configuration– 5 boards in the main and 10 in the extension subrack

Timing Unit Board, TUB

• Function– Stabilized clock for network synchronization– Generation of UTRAN RNC specific frequencies

• Front connection– One input of 2 MHz reference– One input of 10 MHz reference

• Capacity– 50 ppb frequency accuracy– One hour holdover

• Subrack configuration– 2 boards in the main subrack

Exchange Terminal Level 4, ET-M4

• Function– ATM interface for 155 Mbps (SDH and SONET)– STM-1/OC3c/STS-3c ATM full rate (VC4)– AAL2 multiplexing and demultiplexing

• Front connection– Two optical MU connectors for 155 Mbps short haul single mode 1310 nm

(SC connectors on ICF for termination of external transmission)– One output for 2 MHz synchronization

• Capacity– 300 Mbps of ATM throughput

• Subrack configuration– Optional in any subrack

Exchange Terminal Level 4, ET-MF4

• Function– ATM interface for 155 Mbps (SDH and SONET)

– STM-1/OC3c/STS-3c ATM full rate (VC4)

– AAL2 multiplexing and demultiplexing

– HW support for MSP1+1 protection within board and between boards

• Front connection– Four optical MU connectors for 155 Mbps short haul single mode 1310 nm (SC

connectors on ICF for termination of external transmission)

– One output for 2 MHz synchronization

• Capacity– AAL5 throughput max 450Mbps/board, AAL2 throughput max 300Mbps/board

• Subrack configuration– Optional in any subrack

Exchange Terminal Level 4, ET-MC41

• Channelized STM-1 interface board, STM-1/VC12, OC-3/VT-1.5• Merge of SDH multiplexer and ET-MC1• Enables ATM/TDM over 1.5/2 over STM-1• One 155 Mb/s port with 63 × E1 or 84 × T1• MSP 1+1 Protecting line on other ET-MC41• Equipment protection in conjunction with MSP 1+1• Maximum IMA group size: 8 (As on ET-MC1)• IMA within fixed groups of E1/T1• Circuit emulation and Fractional support• 30 mm wide - 2 slots• Subrack configuration

– Optional in any subrack

ET-MFG

• Function– 1+1 Gigabit Ethernet ports, auto configuration 1000 Mbps– Protection switch is completed within 200 ms after a link failure

• Front connection– 1+1 ports per board– Each port has an Emily connector with four pairs of Category 5

balanced cabling

• Capacity– 700 Mbps throughput for an average payload size of 20 octets

• Subrack configuration– Optional in main subrack

Fetching statistics1. Pmr (default 1 hr. ’pmr –m 3’ ’pmr –s 20080613.1500 –e 20080613.1800’ ’pmr –m0.25’ last

period)• 1) RNC Node Traffic Performance • 2) RNC Node Traffic Performance, Hour by Hour• 3) RNC Node Traffic Performance, ROP by ROP• 4) RNC Module Traffic Performance• 5) RNC MP Load• 6) RNC MP Load, Hour by hour• 7) RNC UtranCell RRC Performance• 8) RNC UtranCell Speech Performance • 9) RNC UtranCell CS Data Performance• 10) RNC UtranCell PS Data Performance• 11) RNC UtranCell Throughput and NrUsers• 12) RNC UtranCell HSPA Performance• 13) RNC UtranCell IRAT Performance• 14) RNC UtranCell Soft HO Performance• 15) RNC UtranCell Uplink RTWP / RSSI • 16) RNC Worst 20 UtranCells for RRC Failure Rate Contribution• 17) RNC Worst 20 Utrancells for Speech RRC Failure Rate• 18) RNC Worst 20 Utrancells for PS Failure Rate• 19) RNC Worst 20 Utrancell for Speech RAB Setup• 20) RNC Worst 20 Utrancell for PS RAB Setup• 21) RNC Worst 20 UtranCells for Speech Drop Rate Contribution• 22) RNC Worst 20 UtranCells for Old HS Drop Rate Contribution• 23) RNC Worst 20 UtranCells for Soft HO Failure Contribution• 24) RNC Worst 20 UtranCells for High Uplink RTWP / RSSI• 25) RNC IubLink RRC Performance• 26) RNC IubLink Speech Performance • 27) RNC IubLink CS Data Performance• 28) RNC IubLink PS Data Performance• 29) RNC IubLink Soft HO Performance• 30) RNC IurLink Drop Rate• 31) RNC AtmPort RRC Performance• 32) RNC AtmPort Speech Performance • 33) RNC AtmPort CS Data Performance• 34) RNC AtmPort PS Data Performance• 35) RNC UtranCell Availability Report, Hour by Hour• 36) RNC UtranCell RAB failure breakdown• 37) RNC Q.Aal2 Setup Performance (Aal2Ap)• 38) RNC Q.Aal2 Setup Performance (Aal2Ap) per QoS Class• 39) UeRc BLER

Fetching statistics• RNC Node Traffic Performance• Start Time: 2008-06-24 07:45:00 End Time: 2008-06-24 08:30:00• Object Counter • CS57Drop N/A• CS57RabSuc N/A• CS64Access 98.1• CS64CCSR 98.1• CS64Drop 0• CS64NoRabEstAtt 69• CellFACHDrop 0.6• DCHMinperDrop 0.0• EULMinperDrop N/A• EULRabSuc 98.9• EUL_NumRabEstAtt 181• FACHMinperDrop 0.1• HSMinperDrop 0.0• HsAccess 99.9• HsAvergNoUsers 0.9• HsRetransmissionRate 1.0• HsTputAverg 952.2• HsTputGt100KbAverg 1181.8• NoAbnormalHsRel 354• NoHsRel 1393• NoRrcConnReq 108092• NoRrcConnSuc 106917• OldHsDrop 25.4• PSAccess 99.9• PSCCSR 97.8• PSDCHRetransRate 1.0• PSDrop 2.1• PSIuSigSuc 100• PSRabSucc 99.9• PSRrcSucc 99.9• PsDCHFACHDropRate 1.0• PsDCHFACHRabSucc 99.9• RrcSuc 98.9• SpchAccess 99.3• SpchCCSR 98.7• SpchDrop 0.6• SpchIuSigSuc 100• SpchNoRabEstAtt 15678• SpchRabSuc 99.8• SpchRrcSuc 99.5

Fetching statistics2. Pmx (default 15 min. )

– pmx utrancell pmTotNoRrcConnectReq –m 3

– pmx utrancell pmTotNoRrcConnect –m 3• pmTotNoRrcConnectAttIratCcOrder • pmTotNoRrcConnectAttIratCellResel • pmTotNoRrcConnectFailCongIratCcOrder

• pmTotNoRrcConnectFailCongIratCellResel• pmTotNoRrcConnectReq • pmTotNoRrcConnectReqCs

• pmTotNoRrcConnectReqCsSucc • pmTotNoRrcConnectReqPs • pmTotNoRrcConnectReqPsSucc

• pmTotNoRrcConnectReqSms • pmTotNoRrcConnectReqSuccess

• pmTotNoRrcConnectSuccessIratCcOrder

• pmTotNoRrcConnectSuccessIratCellResel

– pmx utrancell rrc –s 20080613.1500 –e 20080613.1800

– Type ’h pmx’ or ’h pmr’ to find out more usage

Fetching Alarms

Alarms on UTRAN node can be fetched in three differnt ways:

1. From OSS, right click on desktop Alarm View Alarms Alarm List Viewer. Choose View and on left windows all available nodes will be visible. To choose one RNC, expand the RNC cluster and doubble click on that RNC node.

2. From EMAS, launch Element Manager for the appropriate node from ONE. Choose Alarm Alarm List

3. From Moshell type ’al’ or ’ala’ to see details4. ’lga’ to see historic alarms, exapmple ’lga 1’ for last day.

Fetching ’Iub’ availability

’str’ command’Iub’ availability shows the status of :

– Cell (C)– FACH (F)– RACH (R)– PCH (P)– HS (H)– EUL (E)– MBMS (M)– IUBLINK (I)– NBAP-C (C)– NBAP-D (D)– NODESYNCHTP1 (1)– NODESYNCHTP2 (2)

MOD IUBLINK CELLNAMES CFRPHEM1 CFRPHEM2 CFRPHEM3 CFRPHEM4 CFRPHEM5 CFRPHEM6 ICD12 ATMPORTS

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 0028 SC0028-A/B/C 111111 111111 111111 11111

1 0029 SC0029-A/B/C 111111 111111 111111 11111