RNC
RNC
RNC
Manage the Radio Access Bearers for user data transport Manage and optimize the Radio Network resources The 3 RNC Roles
-------------------------------------------------------------------------------[16:48:23.772]0117 (bindID=0x11C0570E) <<---------<< (RANAP) RAB-AssignmentRequest (UE:5668) (RAB-ID=0x01) (maxBitRate=12200) (guaranteedBitRate=4750) (addr=461103200000000)
Video Call [10:20:56.660]0015 <<---<< (RANAP) RAB-AssignmentRequest (UE:220) (RAB-ID=0x01) (maxBitRate=64000) (guaranteedBitRate=64000) (addr=240010200000000) (bindID=0x3A01EAD2) trafficClass background Packet NB HS [10:44:24.184]0015 <<---<< (RANAP) RAB-AssignmentRequest (UE:927) (RAB-ID=0x05) (maxBitRate=7232000) (addr=217.214.245.89) (AltRAB-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-RABParameters) Packet 3 R99 [08:38:29.132]0014 <<---<< (RANAP) RAB-AssignmentRequest (UE:5116) (RAB-ID=0x05) (maxBitRate=384000) (addr=10.64.102.1) (Alt-RABParameters) 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. 2. 3. 4. 5.
ASE Monitor
The 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
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.
Node B Node B
Node B Node B
Node B Node B
Node B Node B
Node B Node B
Node B Node B
C C h a4
a4
a q
s a q s a q
s w
a s w a s w
a q l e k d
d d d d
d f r
j f r j f r
j r
f r f r
k l e l e k
f t
l t l t
s a q
s w
s w a s w a
a l e
e k l e k l
k d
d d d
d f r
j f r j f r
j r
f r f r
f t
t l t l
l a i
a i a i
l a i
a i a i
d u
d u d l l o
s a
u
d u d u l
l o
a
d o
l o
l
a
a l d
d l d d l d
a l d
d l d d l d k l
d k k
k k k k k
d k k
k k k k k k
k d l
s d l s d l
k d l
s d l s d
s c
f c f c
s c
f c f c
UE
u o a
j
j .
j .
UE
o a
j
j .
j .
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
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 Bs and their cells The CRNC controls the radio resources of its cells
Modular RNC
A B C
Type 50 Type 175 Type 300
F
Type 675
- -
Scalable capacity
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
SCB3 ETB
ETB ETB ETB SPB21 SPB21 SPB21 SPB21 SPB21 GPB53 - RNC SCCP2 MP - Standby GPB53 - RNC SCCP2 MP - Active GPB53 - RNC Module MP - Active GPB53 - RNC Module MP - Standby GPB53 - RNC Module MP - Active GPB53 - RNC O&M MP - Active GPB53 - RNC O&M MP - Active GPB53 - RNC Central MP - Standby GPB53 - RNC Central MP - Active GPB53 - RNC SCCP1 MP - Standby GPB53 - RNC SCCP1 MP - Active ETB ETB TUB2 TUB2 SXB3 SXB3 SCB3
18 19 8 1 2 3 4 5 6 7 9 10 11 12 13 14 15 16 17 20 21 22 23 24
Fan Unit
25 26
27
28
Main Subrack HW R5
SCB3 DB or ET-MC41
ETB Basic pos 2 ETB Extended pos. 2B ETB Extended pos. 2 A SPB21 SPB21 SPB21 SPB21 SPB21 DB GPB53 - RNC Module MP - Active GPB53 - RNC Module MP Standby GPB53 - RNC Module MP - Active GPB53 - RNC Module MP - Active GPB53 - RNC Module MP Active3 GPB53 - RNC Module MP - Active DB SPB21 SPB21 SPB21 SPB21 SPB21 DB or ET-MC41 ETB Extended pos. 1 DB or ET-MC41 ETB Basic pos. 1 SCB3
18 19 20 10 11 12 13 14 15 16 17 21 22 23 24 25
Fan Unit
26
27
28
Extension Subrack HW R5
1 2 3 4 5 6 7 8 9
Subrack Interconnection
Hub structure
One main subrack 0 - 5 extension subracks
ET
Main subrack
SCB SXB SXB MP DEV SCB
ISL
Extension
SCB subrack n
Extension SCB MP subrack n Extension SCB SCB MP subrack n Extension SCB SCB MP subrack n
SCB MP SCB
ET
ET DEV
ET DEV
ET DEV
DEV
1 + 1 redundancy on ISL
Extension
SCB subrack n MP SCB DEV ET
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
Front connection
Four Inter Subrack Links (ISLs)
Capacity
310 Mbps of ISL (510 Mbps max aggregated)
Subrack configuration
2 boards in the main subrack
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
Front connection
None.
Capacity
PowerPC
Subrack configuration
5 boards in the main and 10 in the extension subrack
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
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
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
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
Fetching statistics
1. 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 statistics
2.
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. From EMAS, launch Element Manager for the appropriate node from ONE. Choose Alarm Alarm List From Moshell type al or ala to see details lga to see historic alarms, exapmple lga 1 for last day.
2. 3. 4.