Introduction of UMTS RAN15.0_V1.3

8/10/2019 Introduction of UMTS RAN15.0_V1.3

http://slidepdf.com/reader/full/introduction-of-umts-ran150v13 1/125

www.huawei.com

Security Level:

HUAWEI TECHNOLOGIES CO., LTD.

Introduction of UMTS

RAN15.0

Author: xiqinghua 00160410

Email: [email protected]

Version: V1.3(20130128)





HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 3

Capacity Network Synergy

Hardware & Platform

•New RNC Platform

•New NodeB Hardware-WRFU

•New Micro NodeB -BTS3803E•RNC in Pool

•Turbo IC

•TDM

•DPCH PO•CPICH

HSPA+ Evolution

•DB-HSDPA

•Flexible DC/DB-HSDPA•4C-HSDPA

•UMTS-LTE Inter-RAT Cooperation

•HetNet Macro & Micro Co-carrier Uplink

Interference Control

•U900-U2100 Multiband Direct Retry

Based on UE Location

•MOCN Enhancement

Summary of RAN15.0

OAMExperience

•Platinum user prioritizing

•Differentiated Service Based on

Resource Reservation

•Fast customized QoE optimization

•Capacity Visualization Platform

•EBC (Event Based Counter)

•Turbo IC

•HSUPA Time Division Scheduling

•Load Based Dynamic Adjustment of

PCPICH Power

•DPCH Maximum Power Restriction

•DPCH Pilot Power Adjustment

•Layered Paging in Idle Mode




HSPA

Network KPI

•Accessibility Improvement

•Retainability Improvement

•Mobility Improvement

Experience

•SMS Paging Enhancement

•Cell HSPA Capability Indicator

Enhancement

Summary of RAN15.0 (system capability)

Note：System Capability Info only for Huawei internal training

OAM

•Sector level Counter for Multi-RRU

Co-cell•HSUPA Scheduler base on UE

location•Uplink Enhanced CELL_FACH




ID特称

Feature Name Owner

WRFD-150201 宏微同频上行干扰控制 Macro & Micro Co-carrier Uplink Interference Control qichunmei 00159872,

WRFD-150204 白金用户优先 Platinum User Prioritizing wangxiaomei 54131/huawei,

WRFD-150205 Idle态分级寻呼 Layered Paging in Idle Mode mijunwen 00151496/huawei,

WRFD-150206 Turbo IC Turbo IC qihuali 00168890/huawei,

WRFD-150207 4C-HSDPA 4C-HSDPA liuqi 51062/huawei,WRFD-150208 灵活DC/DB-HSDPA Flexible DC/DB-HSDPA liuqi 51062/huawei,

WRFD-150209 DB-HSDPA DB-HSDPA wangxiaoxia 00151683/huawei,

WRFD-150211 RNC in Pool负荷分担 RNC in Pool Load Sharing gaolonglong 00151769/huawei,

WRFD-150212 RNC in Pool节点备份 RNC in Pool Node Redundancy gaolonglong 00151769/huawei,

WRFD-150240 RNC in Pool多逻辑RNC RNC in Pool Multiple Logical RNCs gaolonglong 00151769/huawei,

WRFD-150213 MOCN Iub传输资源独立分配

MOCN Independent Iub Transmission Resource

Allocation xubing 00141968/huawei,

WRFD-150214 MOCN CE资源独立分配 MOCN Independent CE Resource Allocation xubing 00141968/huawei,

WRFD-150222 HSUPA时分调度 HSUPA Time Division Scheduling wanghaidan 00136487/huawei,

WRFD-150215 LTE到UMTS的SRVCC伴随PS切换 SRVCC from LTE to UMTS with PS Handover liyi 00133305/huawei,

WRFD-150216 基于负载的UMTS到LTE的PS重定向 Load Based PS Redirection from UMTS to LTE juzhiqiang 51663/huawei,

WRFD-150217 基于负载的UMTS到LTE的PS切换 Load Based PS Handover from UMTS to LTE juzhiqiang 51663/huawei,

WRFD-150219 基于覆盖的UMTS到LTE的PS重定向 Coverage Based PS Redirection from UMTS to LTE juzhiqiang 51663/huawei,

WRFD-150220 基于覆盖的UMTS到LTE的PS切换 Coverage Based PS Handover from UMTS to LTE juzhiqiang 51663/huawei,

WRFD-150231 基于RIM的UMTS辅助小区选择 RIM Based UMTS Target Cell Selection for LTE xukai 00136474,

WRFD-150230 DPCH Pilot功率调整 DPCH Pilot Power Adjustment lijian 00138284/huawei,

WRFD-150232 基于用户位置的多频段直接重试 Multiband Direct Retry Based on UE Location wuxianbin 00126768/huawei,

WRFD-150233 基于资源预留的差异化服务 Differentiated Service Based on Resource

Reservation liujianjun 58884/huawei,

WRFD-150236 基于负载的导频功率动态调整 Load Based Dynamic Adjustment of PCPICH guanlijun 00184006/huawei,

WRFD-150235 DPCH最大功率限制 DPCH Maximum Power Restriction weibo 00168749/huawei,

Feature Owner List




Content

1 Summary of RAN15.0

2 RAN15.0 Features in Details

d l f k




OAMExperience

Hardware & Platform

New RNC Platform

New NodeB Hardware-WRFU

New Micro NodeB -BTS3803E

RNC in Pool

CapacityHardware& Platform Network SynergyHSPA+




New RNC Platform: BSC6910

Before

•24 Gbps

• 3720K BHCA

• Service awareness

• 40 Gbps• 5300K BHCA

• Interface board

pooling

•Control plane

load sharing

•120 Gbps

• 64M BHCA

• EGPU, 1 for allprocessing board

• CP/UP dynamic

sharing

• Tbps level capacity

with

software upgrade

• Cloud Architecture,

sharing resourcesanywhere

G&U

GSM

UMTS

BSC 6900

Single platform for GU

BSC6900

Board pooling

optimization

2012Q2

BSC6910

New platform for MBB

2013Q2 (R15.0)

Cloud and Convergence

Future



HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

BSC6910: Unified Hardware and Maximize Resource Utilization

Page 9

Unified Hardware

Benefits:

• Unified hardware, greatly simplify HW

management

• Unified CP/UP processing enable dynamic

resource reconfiguration

Benefits:

• Automatic CP/UP reconfiguration based on historical

statistics

• Maximum resource utilization, adaptation to the

network evolution

One for All

DPUb

DPUe

SPUa

SPUb

DPUd

DPUg

XPUa

XPUb

EGPUa

UMTS GSM

Automatic CP / UP reconfiguration

UP Capacity

MBB Traffic model

CP CapacitySmartphone

Traffic model

CP Resource

UP Resource




WRFUa (100W) Radio Unitmodule

WRFUa (100W)

Frequency Band RX: 1920~1980; TX:

2110~2170

Multi Mode Support UMTS Mode

Tx/Rx 1T2R

Working Bandwidth 25M

Output Power

@RF module

Antenna Port

(W)

4C/80 W

1 Carrier: per carrier 80W




Weight (Kg) 11Kg

Input Power -48VDC (-38.4 ~ -57VDC)

New NodeB Hardware - WRFUa (100W)




Micro NodeB- BTS3803E

• Frequency : 2100 MHz, others developed as required

• BWM: 20MHz, 1/11/101/1001

• TX power : 2 x 2 W,2*2MIMO

• Throughput : 84Mbps (DL) /23Mbps (UL)

• CE: 128(DL) /128 (UL)

• Size: ~5.2 L

• Weight: ~6.5kg

• Power: POE (Power over Ethernet)

• WiFi: 2*100mw, 802.11n, 2.4Ghz (Optional）

• Wired backhaul : xPON/xDSL,GE/FE interface

• Wireless backhaul : eRelay, MW, WiFi

BTS3803E






Background

Two features is introduced at RAN15.0

RNC in Pool Load Sharing

RNC in Pool Node Redundancy

RNC in POOL Topology




Load Sharing Introduction

logical RNC 3GPP protocol defined logical entity, identified

by RNC ID.

Physical RNC

Physical RNC is physical equipment ,such as

BSC600 or BSC6910.

Master RNC

RNC network element hosting NodeB of a

logical RNC, Processing OM function for logical

RNC within POOL.

Overflow RNC

RNC network element processes overflowing

traffic from Master RNC for a logical RNC

CN

Iur-p

P_RNC2

Overflow

NodeB

CP

UP

RNC in Pool

IUB

IU

L_RNC1

P_RNC1

Master

Just CP

sharing is

supported

in RAN15.0.




NB3

BSC 6900

Iur

BSC 6900

Iur

NB2NB1

BSC 6900

Current

Load Sharing Application Scenario

RNC in Pool Load Sharing

• Smooth capacity expansionNew RNC CP capacity can be shared

with multiple existed BSC6900

NodeB Re-homing from existed

BSC6900 to new BSC6910 is No

needed

NB3

Iur Iur

NB1

6900

Iur-p

Iur-p

Iur-p

BSC 6910

RNC ID 1 RNC ID 2 RNC ID 3

NB2

6900 6900

RAN15.0

SGSNMSC Core

Network





Load Sharing Typical Configuration

Load Sharing Specification

Support 3*BSC6900(Master RNC) + 1*BSC6910(Backup RNC).

Support 1*BSC6910 + 1*BSC6910

Only Iur-p interface over IP is supported

RAN15.0 only supports CP sharing , and UP sharing will be supported in future

version.

the NodeB of the logical RNC can only be hosted in the master RNC.

Iur-p

L_RNC1

L_RNC2P_RNC1 P_RNC2

Overflow

RNC

Master

RNC

Master

RNCOverflow

RNC

Iur-p

P_RNC1

Logic RNCI

P_RNC4

Iur-p

P_RNC2

Logic RNC2

Iur-p

P_RNC3

Logic RNC3Master Overflow

Overflow

Overflow

Master

Master

69106900

6900

6900

6910 6910

Configuration Case A Configuration Case B






Load Sharing Benefit

Benefit

Provide a simpler path to capacity expansion (avoiding Iu/Iur/Iub

integration and NodeB re-homing)

Maximize the efficiency of the capacity purchased in BSC6910

hardware by allowing a single platform to augment multiple

existing RNCs

Two BSC6910 shares with each other to increase the hardware

utilization rate to the traffic break out scenario.

Impact User call establishment delay is increased about 150ms

(Maximum 400ms).




Load Sharing Dependence

License

RNC level license at Master RNC is needed.

Feature Dependence

None

Hardware

For BSC6900, the IP interface board GOUc or FG2c is neededfor Iur-p

For BSC6910, the IP interface board GOUc or FG2c or EXOua

is needed for Iur-p

Other

Transmission requirement for Iur-p interface: Time

delay<=10ms Jitter<=5ms Packet loss ratio<=0.01%

CME online is needed which support parameter configuration

synchronization.

CN

Iur-p

BSC6910

Overflow

NodeBCP

UP

Iu

b

Iu

RNCID1

BSC6900

Master

Act ive user num bers

are contro l led by

License




Node Redundancy Introduction

Backup RNC: Provide RNC service when Master

RNC outage for a logical RNC

All NodeBs of one logical RNC hosted to

one Master RNC, and secondary hosted

to one Backup RNC

Normally, Master RNC provide service

and Backup RNC in standby status.

when Master RNC breakdown and can’t

be recovered within a short term,

Backup RNC can take over Master RNC

to resume service.

CN

Iur-p

RNC1 RNC2

NodeB

Primary Homed

Secondary Homed

RNC in Pool

IUB

IU

P_RNC1

MasterP_RNC2

Backup




Node Redundancy Application Scenario

NB3

BSC 6900

Iur

BSC 6900

Iur

NB2NB1

BSC 6900

Current

NB3

Iur Iur

NB1

6900

Iur-p

Iur-p

Iur-p

BSC 6910


NB2

6900 6900

RAN15.0

SGSNMSC Core

Network

Iub

Iu

Active

Standby

RNC in Pool Node Redundancy

•Improved RAN system availabilityOne BSC6910 work as redundancy for

multi BSC6900 or BSC6910

Eliminates risk of single RNC outage





Node Redundancy Typical Configuration Node Redundancy Specification

Support N*BSC6900(Master RNC) + 1*BSC6910(Backup RNC). here,N<=3

Support 1*BSC6910 + 1*BSC6910

About 3 minutes needed for Node Redundancy activation procedure (Online user drops)

Redundancy Trigger

RAN15.0 only supports switch manually, automatic switch will be supported in future version.

Execute MML Command : REL UHOSTRNC at Master RNC Or Execute MML Command : FOC

UHOSTRNC at Backup RNC will trigger NodeB Redundancy procedure.

Iur-p

L_RNC1

L_RNC2P_RNC1 P_RNC2

Backup

RNC

Master

RNC

Master

RNCBackup

RNC

Iur-p

P_RNC1

Logic RNCI

P_RNC4

Iur-p

P_RNC2

Logic RNC2

Iur-p

P_RNC3

Logic RNC3Master Backup

Backup

Backup

Master

Master

69106900

6900

6900

6910 6910

Node Redundancy Scenario for BSC6900 Node Redundancy Scenario for BSC6910




Node Redundancy Benefit

Benefit

Improved RAN system availability. Eliminates risk of single RNC

outage.

Also, the feature could be used at RNC software upgrade

procedure. It will decrease service interrupt duration.

Network Impact

Backup RNC need add backup Iub/Iur/Iu interface configuration

Core Network need add backup Iu interface route

Neighbor RNC need add backup Iur interface route

NodeB need add dual-homing Iub interface configuration




Node Redundancy Dependence

License

Node Redundancy software license ( RNC level ) is

needed，the unit is NodeB number.

Feature Dependence

None

Hardware

For BSC6900, the IP interface board GOUc or FG2c

is needed for Iur-p

For BSC6910, the IP interface board GOUc or FG2c

or EXOua is needed for Iur-p

3900 series NodeB is required

Other

CME online is needed which support parameter

configuration synchronization. Only Iur-p interface over IP is supported

For the dual-homing NodeB the two transmission type

should be same for the two Iub interface.

CN

Iur-p

NodeB

Iu

BSC6900

Master

BSC6910

Backup

RNCID1

Iub

Number of Redundant

NodeBs are controlled

by License








DB-HSDPA Introduction

Description

DB-HSDPA allow that UE is able to setup HS-PDSCH connection on two

carriers of different bands and transmits data on two carriers simultaneously

At uplink, UE only transmit data at one carrier, i.e. Primer Carrier

pplication Scenario

Urban area or city hotspot where multi carrier available or dual-band

available, such as U900+U2100 co-sites area

Carrier on Band A

Carrier on Band B

Primary Carrier

Secondary Carrier




DB-HSDPA Introduction (cont.)

Compared with DC-HSDPA

The technology of DB-HSDPA is the same as DC-HSDPA except the

frequencies of the two cells. So, the function such as channel

configuration, mobility is same with DC-HSPDA.

The frequencies of DB-HSDPA cell group comes from different bands but

the frequencies of DC-HSDPA cell group should be the same band and

the neighbor frequencies.

Band combination supported

Band I+ Band VIII (2100+900)

Band II+ Band IV (1900+AWS)

Band I+ Band V (2100+850)

Band II+ Band V (1900+850)

Page28




DB-HSDPA Benefit

Peak throughput

DB-HSDPA 42Mbps

DB-HSDPA+MIMO 84Mbit/s

User experience

Maximum 80% UE average rate gain for burst

traffic compared with SC-HSDPA user.

Network Impact

Compared to the SC-HSDPA user, DB-HSDPA

should feedback CQIs of two frequencies

instead of one CQI of one frequency in uplink.

Therefore, the upload would be increased

slightly in case of high penetration of DB-HSDPA users. e.g. UL load is increased about

10% in case of 50 DB-HSDPA users in a cell.

Page29

D B-H SD PA Perform a nce G a in (2.1G H z+900M H z, Bu rst Tra ffic) ,PA 3

0

2

4

6

8

10

12

0 5 10 15 20

User N um b er/sector

A

v e

r a

g

e

B u

r s

t

R

a

t e

( M

b

p

s )

D B-H SD PA +64Q A M

2.1G H z-H SD PA +64Q A M

900M H z-H SD PA +64Q A M

80%




DB-HSDPA Dependence

Feature Dependence

WRFD-010610 HSDPA Introduction Package

WRFD-010685 Downlink Enhanced L2

WRFD-010629 DL 16QAM Modulation

Hardware

BTS3900/DBS3900,WBBPb,WBBPd or WBBPf board is needed

BTS3812E/BTS3812AE/BTS3812A is not supported

DBS3800, EBBC or EBBCd board is needed

UE

HSDPA Category is 21 or higher , and DB-HSDPA capability is

needed






Flexible DC/DB Introduction

Description

Multi carriers are combination as one carrier group, any carrier could be allocated dynamically to

establish DC-HSPA or DB-HSDPA service

Up to 4 carriers supported at one carrier pool, which belong to one NodeB

DC-HSDPA is used for any two carriers; DB-HSDPA is used for any two carrier in different band

One Carrier could belong multi DC-HSDPA or DB-HSDPA or DC-HSDPA+MIMO or DB-HSDPA+MIMO or

4C-HSDPA+MIMOcell group simultaneously

Application Scenario

Urban area or city hotspot where multi carrier available or dual-band available

F2(Band A)

F3(Band A)

F3(Band B)

DB

DB

DC

NodeB

Flexible HSDPA Dual-Band

F1(Band A)

F2(Band A)

F3(Band A)

DC

DC

NodeB

Flexible HSDPA Dual-Cell

DC

F1(Band A)

DC




Flexible DC/DB Introduction (cont.)

Difference with traditional DC-HSDPA/DB-HSDPA, flexible DC/DB allows that

carrier cells are dynamically allocate to user.

Flexible DC/DB enable easy configuration for DC-HSDPA/DB-HSDPA

It not need configure each cell pair for DC-HSDPA/DB-HSDPA.

All cells used by DC-HSDPA/DB-HSDPA are pushed to carrier pool(multi-cell group).

RNC will dynamically select carrier and HSPA+ technology for each multi carriercapability user.

With Flexible DC/DB，RNC will select secondary carrier for DC/DB-HSDPA

users from multi candidate carriers.

Scheduler

MAC-ehs HSDPA scheduler supports joint schedule DC-HSDPA/DB-HSDPA users

on multi carriers. Scheduler also supports mixed SC-HSDPA/DC-HSDPA/DB-HSDPA user scenario.




Flexible DC/DB Benefit

Benefit

Due to higher network radio resource utilization, UE average burst

rate will improve about 5%~20% than fixed DC/DB by simulation.

The gain will variation according to live network carriers load

status.

Network impact

Refer to DC-HSDPA and DB-HSDPA




Flexible DC/DB Dependence

Feature Dependence

WRFD-150209 DB-HSDPA (if one cell in the group operates at a different frequency band

from other cells, all cells in the group must support DB-HSDPA)

WRFD-010696 DC-HSDPA (is needed for all cells operated at the same frequency band)

Hardware

BTS3900/DBS3900 1) WBBPb,WBBPd or WBBPf board is needed

BTS3812E/BTS3812AE/BTS3812A

1)For intra-band 3Carriers, EBBI,EDLP+EULP(d) board is needed

2)Inter-band 3Carriers and 4Carriers is not supported

DBS3800

1)For inter-band or intra-band 3Carriers, EBBC or EBBCd board is needed

2)4Carriers is not supported

UE

HSDPA Category is 21 or higher.

CapacityHardware& Platform HSPA+ Experience OAMNetwork Synergy




HSPA+ Evolution

DB-HSDPA

Flexible DC/DB-HSDPA

4C-HSDPA (3C-HSDPA included)




21M

(64QAM)

42M(DC)

84M

(4C/DC+MIMO)

168M

(4C+MIMO)

2012 2013 2014

HSPA+ 21M

HSPA+ 84M

HSPA+ 42M

HSPA+ 168M

2015 2016~

Smooth Evolution Proposal for

Commercial Network

21 28 4284

168

336

0

50

100

150

200

250

300

350

400

R6 R7 R8 R9 R10 R11

64QAM2X2MIMO

DC+64QAM

Or 64QAM+MIMO

DC+64QAM+

MIMO

4C+64QAM+

MIMO

4C+64QAM+4x

4MIMO

3Gpp Evolution

HSPA+ Evolution Roadmap

Mbps




4C-HSDPA Introduction

Description

4C-HSDPA Feature (and 4C-HSDPA+MIMO) allow Maximum 4 carriers transmit downlink data to one

UE simultaneously

4C-HSDPA Feature includes 4C-HSDPA and 3C-HSDPA

4C-HSDPA+MIMO Feature include 4C-HSDPA+MIMO and 3C-HSDPA+MIMO

At one Band, only 3C-HSDPA or 3C-HSDPA+MIMO is supported according to 3Gpp R10


Urban area or city hotspot where multi carrier available

NodeB

F 1

F 2

UE

BAND A

DL:DPCH/F-DPCH

UL:DCCH

HS-DSCH

F 3

F 4Secondary Carrier 3rd

HS-DSCH

HS-DSCH

HS-DSCH

Secondary Carrier 2nd

Secondary Carrier 1st

Primary Carrier

BAND B

UL:HS-DPCCH( CQI,HARQ ACK/NAKC for all carrier)




4C-HSDPA Introduction (cont.)

Support band combination

Two carriers in Band I (2.1GHz)+ one carrier in Band VIII (900MHz)

Three carriers in Band I (2.1GHz)+ one carrier in Band VIII (900MHz)

One carrier in Band II(1900MHz)+ two carriers Band IV (AWS)

Two carrier in Band II(1900MHz)+ one carriers Band IV (AWS)

Two carrier in Band II(1900MHz)+ two carriers Band IV (AWS)

One carrier in Band I(2.1GHz)+ two carriers in Band V (850MHz)

Two carrier in Band I(2.1GHz)+ one carriers in Band V (850MHz)

Two carrier in Band I(2.1GHz)+ two carriers in Band V (850MHz)




4C-HSDPA Benefit

Peak throughput 3C-HSDPA 63Mbps

4C-HSDPA 84Mbps

3C-HSDPA+MIMO 126Mbps

4C-HSDPA+MIMO 168Mbps

0

20

40

60

80

100

120

140

160

180

1c 2c 3c 4c

w/t MIMO

w/o MIMO

0%

20%

40%

60%

80%

100%

120%

2 UE per sector4 UE per sector8 UE per sector 16 UE per

sector

U s e r T h t

G a i n

4C-HSDPA vs DC-HSDPA

User Experience

In case of dense urban, small file download such asMP3 download, 4C-HSDPA user throughput will

improve 30%~80% compared with DC-HSDPA

Network Impact:

Cell uplink load (RTWP) will increased slightly in

case of high penetration of DB-HSDPA users due to 4C-

HSDPA uplink HS-DPCCH channel need more

power consumption




4C-HSDPA Dependence

Features Dependence

WRFD-010683 Downlink 64 QAM

WRFD-150209 DB-HSDPA ( is not needed while intra-band 3Carriers scenario)

WRFD-010696 DC-HSDPA (is needed for all cells operated at the same frequency band) ??

WRFD-150208 Flexible DC/DB-HSDPA

Hardware

BTS3900/DBS3900

1) For 3Carriers, WBBPb,WBBPd or WBBPf board is needed

2) For 4Carriers, WBBPd or WBBPf board is needed

BTS3812E/BTS3812AE/BTS3812A

1) For intra-band 3Carriers, EBBI,EDLP+EULP(d) board is needed

2) Inter-band 3Carriers and 4Carriers is not supported

DBS3800 1) For inter-band or intra-band 3Carriers, EBBC or EBBCd board is needed

2) 4Carriers is not supported

UE

HSDPA Category 29, 30, 31, or 32





Capacity

Turbo IC

HSUPA Time Division Scheduling

Load Based Dynamic Adjustment of PCPICH Power

DPCH Maximum Power Restriction DPCH Pilot Power Adjustment

Uplink Enhanced CELL_FACH

Layered Paging in Idle Mode




Background

UMTS Cell uplink capacity is limited by

the multi-access interference (MAI)

from UEs in and interference outside

the system.

Interference cancellation (IC) reduces

or eliminates interference between UEsto effectively improve UE receive

performance, which is an effective

method to improve uplink capacity.

The higher UE data rateresults in higher interference to

other UEs.








Turbo IC Dependence

Feature Dependence

WRFD-01061403 HSUPA 2ms TTI

WRFD-010691 HSUPA UL Interference Cancellation

Hardware

Only BTS3900/DBS3900 is supported, and WBBPf board is

needed

UE

HSUPA Category 6 or higher

License

Software license (cell level ) is needed


Experience OAM




Capacity

Turbo IC








Background

WCDMA is a self-interferingsystem. The higher uplink

data rate , the greater uplink

interference

At RAN15.0, HSUPA Time

Division Scheduling is

introduced which avoid and

decrease system interfering

User1

User2

User3

User4

User5

General scheduling mode: code division

Time Division Scheduling mode:

User transmitting data in different time, cell

interference be reduced

HSUPA User Scheduling




HSUPA Time Division Scheduling Introduction

Description

Timing alignment When HSUPA UEs set up the first radio link (RL), set the Default DPCH Offset Value for

time alignment to ensure no data transmission time overlap between different processes

TD User selection

Only 2ms HSUPA user will be scheduled with time division mode

SRB over HSUPA is required soft handover or softer handover user will not selected due to timing alignment issue

DPCH,4

DPCH,3

DPCH,2

Time2ms

P-CCPCH

E-DPDCH 1

E-DPDCH 2

E-DPDCH 3

E-DPDCH 4

DPCH,4

CD Scheduling Timi ng

DPCH,4

Time2ms

P-CCPCH

E-DPDCH 1

E-DPDCH 2

E-DPDCH 3

E-DPDCH 4

TD Scheduling Timi ng

UE1 Active Process

UE2 Active Process

UE3 Active Process

UE4 Active Process

Deactive Process

Figure 2: Time alignment of HSUPA user

HSUPA Ti Di i i S h d li





Introduction (cont.)

TD user HARQ allocation

Only one user is ensured to transmit high-speed data at one 2ms TTI and Up to 8

users supported simultaneously

If a UE gives up time division, the released process is allocated to the UE with the

lowest rate.

If a new UE requires scheduling, the UE with the highest rate satisfaction will release

partial HARQ to the new UE.

If there is no change on the time division UEs, periodically adjust the processes

between UEs to ensure fairness and differentiation between UEs.


Dense urban or hotspot area which have high percentage of HSUPA 2 ms users and

data transmission requirement

Single Antenna Scenario is recommended, such as indoor system

High mobility is NOT recommended, such as highway and high-speed train




Benefit

Benefit:

Uplink cell throughput increase about 10%~90% without

IC in case of single Rx Antenna and 2~8 Time Division

users by simulation

Uplink cell throughput increased about 5%~15% with

IC in case of 2 Rx Antenna and 2~8 Time Division users

by simulation

live network gain depended on penetration of 2ms

HSUPA UE and enough traffic volume.

Impact

Because that Time Division User should keep DL

DPCCH timing alignment , then PA PAR will increasedwhich impact cell downlink throughput

HSUPA Ti Di i i S h d li





Dependence

Feature Dependence

WRFD-01061403 HSUPA 2ms TTI

WRFD-010636 SRB Over HSUPA

Hardware

Only BTS3900/DBS3900 is supported (DBS3902E excluded), and

WBBPf board is needed

multiple RRUs share one cell scenario is NOT supported

UE

HSUPA Category 6 or higher

License

Software license (cell level) is needed


Experience OAM




Capacity

Turbo IC








Introduction

Description

If cell Non-HSPA consumption ratio is higher than configured active

threshold, degrade PCPCIH power step by step

On-line user max DL power not impacted during the adjustment procedure.

i.e. keep the default value

If cell Non-HSPA consumption ratio is less than configured restore

threshold, upgrade PCPCIH power step by step

The PCPICH adjustment range , period and step is configured.


Hotspot cells at Multi-Carrier network. The carrier which supplycontinuous coverage is not suggested to active this feature, the carrier

which supply traffic is suggested to active it.




Benefit

Benefit

Decrease CCH power consumption and shrink cell coverage range, then

decrease cell Non-HSPA power consumption

Assumed default PCPICH power ratio is 10% and PCPICH degrade threshold

is 3dB. The cell Non-HSPA power consumption will decrease 10%~15% at

busy hour of hotspot cells which has amount of HSPA users

Impact

Cell edge handover attempts and call drop maybe increased due to shrink

coverage

For multi-carriers network, the blind handover between different carriers due to

shrink coverage

Dependence Cell level license at RNC is needed

Page55






Background

Description:

As smart-phones penetrate quickly, more and more UEs will keep on line but

transmit nothing which wastes cell DL DPCH power for HSDPA users

This phenomena is shown as the figure. It means that most of cell power is

used by DL DPCH channel, and cell downlink throughput impacted due to

power limitation.

D L

T x P o w e r

User Num




Introduction Description

Only HSDPA user is selected

If cell Non-HSPA power higher than configured active threshold If No SRB transmission at DL DPCH of HSPA user , decrease DL DPCH max power value

If SRB transmission detected at DL DPCH of HSPA user ,restore DL DPCH max power value

The adjustment period is one TTI (i.e. 40ms)

No adjustment action at the TTI edge (i.e. last 10ms of TTI) to avoid DL RL failure

If cell Non-HSPA power less than configured restore threshold

Restore DL DPCH max power value

Application Scenario this feature is recommended when both Non-HSPA power consumption ratio and PS

user ratio are high.

Lab Test Result with 40 ftp download users distributed at cell edge




Benefit

Benefit

The average cell Non-HSPA power consumption is expected to decrease

by 5%~15% at busy hours of hotspot cell. The gain is variable accordingto cell HSDPA user number and location distribution of live network.

Impact

Cell HSDPA call drop ratio maybe increased due to cell edge user call

drop possibility increased

Dependence Cell level license at NodeB is needed

If WRFD-010652 SRB over HSDPA activated, this feature will not be used

if UE support SRB over HSDPA; this feature will still be used for UE which

not support SRB over HSDPA.

Lab Test Result with 40 ftp download users distributed at cell edge





Capacity

Turbo IC



DPCH Maximum Power Restriction

DPCH Pilot Power Adjustment





Introduction

Description

Decrease DPCCH Pilot PO and Pilot bit number when cell Non-HSDPA

power ratio is high than configured threshold


this feature is recommended when both Non-HSPA power consumption

ratio and PS user ratio are high.




Benefit Benefit

When this feature is activated and most UEs setup services over HSDPA,the average power consumed by every UE’s DL DPCH is expected to

decrease by 5%~20%

Impact

Cell drop ratio maybe increased due to Pilot info impact UE SIR

estimation.

Dependence

None


Experience OAM




Capacity

Turbo IC



DPCH Maximum Power Restriction

DPCH Pilot Power Adjustment





Background

The penetration of Smartphone is increasing continuously ,

more PS paging is happened at live network. It means that

PCH load is increasing rapidly, and high PCH load will cause

high discard!

Page64

0.00%

1.00%

2.00%

3.00%

4.00%

5.00%

6.00%

7.00%

8.00%

9.00%

0 .0 0 % 1 0 .0 0 % 2 0 .0 0 % 3 0 .0 0 % 4 0 .0 0 % 5 0 .0 0 % 6 0 .0 0 % 7 0 .0 0 % 8 0 .0 0 %

Discard ratio

PCH utilizationLive network PS paging stat.

PCH utilization vs Paging Discard Ratio

Layered Paging in Idle Mode Introduction




Layered Paging in Idle Mode Introduction

Description

Layer1: Paging is sent to the latest cell and all the intra and inter neighboring cells;

Layer2: if no response from UE before the timer (DRX cycle+360ms) expires, the

paging will be sent again in whole LA or RA area.


It is recommended if PCH congestion happened.

it is NOT recommended at high mobility scenario due to high Layer 1 paging failure

will happened. Such as highway, metro.

Page65

Step1: cell

levelpaging

If fail , then:

Step2: LA/RA level paging

Without “Layered

Paging”

With “Layered Paging”

No paging

response





Introduction(cont.)

Description

CS and PS switch independently

Control switches are designed separately for real time service

(Conversational and Streaming) and non real time service (Interactive,

Background and SMS);

Flexible cell configuration A black list of cells can be used to avoid this feature to be applied for these

cells (usually with high mobility).

UE ID info management

A UE list is maintained in RNC to record the UE ID(IMSI,TMSI)and the

latest cell ID where the UE turns into idle mode.

If there’s no interaction between UE and RNC before the timer

(UsrLocInfoAgingTmr, 30 minutes by default) expires since it turns into idle

mode, the UE will be removed from the UE list.




Layered Paging in Idle Mode Benefit

Benefit :

Reduce the amount of Paging messages for idle mode UEs, which will reduce the

PCH load.

Assumption

Total cell number in the LA/RA: 500

Average neighboring cell number: 64

Success ratio of layer 1 paging: 80% Success ratio of layer 2 paging : 100% (only one time Layer2 paging)

Reduced paging amount ratio

1 – (64 * 80% + (64 + 500) * 20%) / 500 = 67.2%

Network Impact

Call access delay is increased if layer 1 paging failure. The delay is ~1s if the DRX

cycle is 640ms.

License

RNC level license is required

Page67


Experience OAM




Network Synergy

UMTS-LTE Inter-RAT Cooperation

HetNet Co-Carrier Coordination Phase 1

U900-U2100 Multiband Direct Retry Based on UE Location

MOCN Enhancement



LTE to UMTS SRVCC with PS Handover




UL dual-mode UE

with both voice &

data

LTE

UMTS

VoIP & Data

UMTS

Voice & Data

Benefit: With PS handover, the

interruption of PS service

decreased and bring the end

user a better experience.

Dependence

UE should support SRVCC

SRVCC：Single Radio Voice Call Continuity


Experience OAM




Network Synergy


HetNet Macro & Micro Co-carrier Uplink Interference Control


MOCN Enhancement




• Co-Channel Challenges on Uplink• The gap on pilot power between Macro and Micro leads to imbalance on DL/UL at Microcell edge area. (Ie.

Macro Tx Pwr= 20 W, Micro Txpwr = 5W, the GAP on DL is ~6 dB)

At Non-SHO area:

Victim: Microcell

Impact: Substantial RTWP rise, UL blocking as the worse

case

Cause: UEs at Macro cell edge transmitting high power,

perceived by Microcell as huge noise

At SHO area:

Victim: Macro cell

Impact: Poor UL radio link quality perceived by Macro

cell, causing degraded HSPA T-Put

Cause: UE TxPwr is reduced as a result of Power control

dominated by the Microcell

UL boundary

DL boundary

- Because of pilot power difference, Micro’s DL

coverage is much less that of Macro’s

- However, UL coverage is basically the same

between Micro and Macro

Background




Introduction

Description

HetNet Macro & Micro Co-carrier Uplink Interference Control included 3 sub-

features

Micro Cell Dynamic Rx Sensitivity Control

Macro & Micro Joint Inter-frequency Redirection

Macro & Micro Joint Inter-frequency Handover.

Application Scenarios

Urban traffic hot-spot where Macro and Micro cell use the same frequency

Typical network topology

As following figure

Macro

Macro

Problematic area

MicroMicroF1

F2

Problematic area

Macro

Macro

F2 can be configured

as F1's neighboring

cell for blind

handovers.

Introduction(cont.)




without desensitization

UL boundary DL boundary

Gap between the UL andDL boundaries:

Problematic areas

Step2： take RRC Re-direction and IFHO, make the users at the problematic

area move to other Macro frequenciesStep3：if there are still users in the problematic area after previous

step, perform full value Desensitization

Step1：Perform partially desensitization ( ie. half desensitisation value) first, to avoid the possible UL blocking by the serve UL interference. This step

can be disabled by parameter

If inter-frequency

handover fails

Cancel the totaldesensitization, and fall

back to the partial

desensitization after theUEs in the problematic

areas left.

When UE in the

problematic areas andtry to access or execute

handover, or modify

service, go to step 2

After the partial

desensitization: UL

boundary

DL boundary

Gap between the UL and DL boundaries:problematic areas

Partial desensitizationintensity

Before the partial

desensitization: ULboundary

Max. gap between the UL and DL boundaries

3-Step Approach to Mitigate Co-channel Impact

( )

I t d ti ( t )




• How to identify users at ON-SHO area？- when there is 1A’ event reporting

• Self defined 1A’ event: RNC sends Meas. Control with a new ID# for this self defined 1A’ event and waits for UE to report

• Only Macro with Co-channel Micro neighbor will send 1A’ Meas. Control

• 1A’ event can be considered as earlier trigger for entering SHO area (but no SHO as the consequence) , therefore 1A’ threshold is

typically higher than that of 1A• After 1A’ event triggered, there will be periodic 1A’ event reporting until a timer expiry

• How to identify users at SHO area?

• Based on the RL(s) in the active set: when there are Macro & Micro RLs in the active set and the best cell is Macro cell

• From Macro to Micro, 1A’ event is used as the sign of entering the problematic area, 1D event as exiting; From Micro to

Macro, 1D as the entering, stop 1A’ report as the exiting

Non-SHO area SHO area

How to identify users in problematic area?

Introduction(cont.)

I t d ti ( t )




RRC Redirection and Inter-frequency Handover

To reduce the UE numbers in

problematic area

RRC Redirection Macro & Micro Joint Inter-frequencyHandover

Is the UE in a

problematic area?

RRCRedirection Noaction

Yes NoIs the UE in a

problematic area?

BlindIFHO

No action

Yes No

The target cell for the inter-frequency blind

handover and redirection must meet allfollowing conditions:

1. The target cell is a macro cell.

2. The target cell is in neither the LDR state nor

the OLC state.

3. The target cell is an inter-frequency neighboring

cell for blind handover.

4. The target cell supports HSDPA or HSUPA.

5. The UE supports the frequency of the target

cell.

6. The target cell has no intra-frequency

neighboring micro cells (Indicated by MicroCellFlag)

For online H users without

CS RAB over DCH For Idle User accessrequest for PS service

Featrue1: Macro & Micro Joint Inter-frequency

Redirection

Featrue2: Macro & Micro Joint Inter-frequency

Handover

Introduction(cont.)

Introduction(cont.)




Triggering Desensitization Implementation

Update the reference background noise and maximum

target RTWP for HSUPA scheduling on the NodeBbased on the new desensitization value:

Maximum target RTWP = Reference background noise +TargetRoT

State 1: No UE in the

problematic areas: Partial

desensitization value

State 2: UEs are in the

problematic areas. Full

desensitization value

Event-triggered:

Inter-Freq HO failure or any UE is detected in theproblematic area

Periodic detection:The full desensitization timer expires and no UE is

detected in problematic area

Desensitization value configuration

The NodeB configures desensitization value on

RRUs according to the private information element

DesensPower .

Microcell Dynamic Rx Sensitivity Control

Partial desensitizationvalue

Full desensitization

value

MaxGAP Total2PartDesense

Diff

MaxGAP

MaxGAP = Difference in the pilot power -Difference in the

receiving capability + Difference in the background

noise

( )

Benefit & Impact




Benefit & Impact

Impact to be observed after Microcells implementation

The soft handover amount increases as a result of cells boundaries increase due to Microcell deployment

The Hard handover amount increase due to Feature enabled

When microcell is located as the weak coverage area of Macrocell, call drop rate, access successful rate

and other KPI will be improved due to coverage enhancement by Microcell

When Microcell is located at the hot spot for traffic offload, the overall KPI of the network basically keeps

unchanged or improves slightly due to traffic offload by Micarocell

Case #1: Microcell is implemented in RAN15 with Co-carrier, with 3 features of Co-carrier coordination enabled

F1(Macro) + F1(Micro) + F2 (Macro), 3 features work jointly - RAN15.0

Vs.

F1(Macro) + F2 (Macro)

Co-carrier Networking Case Analysis





B k d




3G lowband cell

3G highband cellMulti-bands network:

Background

Low band cell (U900/U850) has better coverage performance (stronger

penetration capabilities and lower path loss).

High band cell (U2100/U1800) can provide more capacity and improve the

user experience. Location Based Multi-band Direct Retry Feature is introduced at RAN15.0

to support U900/U850 & U2100/U1800 Synergy

I t d ti




Main ideas:

Low band cell serves mainly the users at cell edge.

High band cell serves mainly the users at cell centre.

Introduction

Note: This feature is only applied to HSDPA users.

I t d ti ( t )




Note: The RSCP measurement report period is 250ms.


Description

Pathloss and target cell load

status should be checked

when new RAB assignment

request received.

Pathloss is calculated form

cell RSCP measurement

RSCP measurement should

be triggered only the feature

switch ON



Dependence




Dependence

Feature Dependence

WRFD-020400 DRD Introduction Package

WRFD-020110 Multi Frequency Band Networking Management

WRFD-010610 HSDPA Introduction Package

Hardware: None

UE

The UEs must support both high- and low-frequency bands, such as

U2100 and U900.

License

Cell level license at RNC is needed

Network Synergy


Experience OAM




Network Synergy


HetNet Co-Carrier Coordination Phase 1


MOCN Enhancement

Background




Background MOCN (multiple operator Core

network) is defined at 3Gpp which allow

multi operator sharing radio equipment

and resource

MOCN should save operator’s

investigation and improve resource

utilization

Two new feature about MOCN

enhancement is introduced at RAN15.0

MOCN Independent Iub Transmission

Resource Allocation MOCN Independent CE Resource

Allocation

MSC

SGSN

RNC

NodeB

Cell

GGSN, HLR& apps

MOCN

Shared NEs



Benefit




Benefit

Benefit

This feature prevents one operator from occupying excess Iub

user-plane transmission resources in MOCN scenarios and

ensures that operators retain independent Iub user-plane

transmission resources. Impact

Each operator’s MAX available Iub bandwidth will reduced, and

total resource utilization efficiency maybe reduced

If one operator’s predefined Iub bandwidth less than the traffic

required, the KPI (RRC/RAB success rate ,HSPA throughput )will

be degraded.

Dependence




Dependence

Feature Dependency

WRFD-021311 MOCN Introduction Package is needed.

This feature cannot be used with WRFD-02130501 Dedicated Iub

Transmission Control or WRFD-140208 Iub Transmission

Resource Pool in RNC simultaneously. Hardware

This feature does not support BSC6910 IP transmission.

UE

None

License

NodeB level license is needed

MOCN Independent CE Resource Allocation




MOCN Independent CE Resource Allocation Description

M2000 allocate UL/DL CE license group for each operator;

Configure UL/DL CE license private group and common group for NodeB in M2000

Private group CE only can be used by the operator;

Common group CE can be shared between operators, it can be set to zero.

RNC indicate the user’s serving operator to NodeB

NodeB consume different group CE according the user’s serving operator.

private group CE will be first consumed;

common group can be used when the private group is used up;

first come first serve in common group.

RNC execute the action to release from congestion for each operator independently.

If one operator’s CE can be used is insufficiency, RNC will choose the operator’s users to do

BE rate reduction or TTI adjustment from 2ms to 10ms.Operator

B Operator

COperator

D

Operator

A

Common

Group

BBU Resource Allocation:

Private Group + Shared Group

Benefit




Benefit

Benefit

This feature prevents one operator from occupying excess CE

resources in MOCN scenarios. This ensures that each operator

retains independent CE resources.

Guarantee each Operator’s CE proportion by Private Group,

Optimize CE resource utilization efficiency by Shared Group

Impact

If one operator’s predefined CE license less than the traffic

required, the KPI (RRC/RAB success rate ,HSPA throughput )will

be worse.

Dependence




Dependence

Feature

WRFD-021311 MOCN Introduction Package is needed.

This feature cannot be used with WRFD-021304 RAN Sharing

Introduction Package simultaneously.

Hardware

DBS3900/BTS3900 with WBBPb,WBBPd or WBBPf board

UE

None

License

Software license (cell level) is needed

Experience


Experience OAM




Experience

Platinum user prioritizing

Differentiated Service Based on Resource Reservation

Fast customized QoE optimization

Background




Background

During Sport Game (e.g ATP match) or important festival (e.g Hajj), the traffic

will increase sharply and serious network’s congestion will happen, and all user

experience will deteriorate severely.

Platinum user prioritizing feature will improve valuable customer’s (such as VIP

group) experience in such congestion scenarios.

Page95

Introduction




Introduction

Platinum User identification

③Platinum User access

prioritizing both at RRC and RAB

phase

④Platinum User quality

Prioritizing at service holding

phase both for CS and PS service

Application Scenario: Hot Event

Scenario. Such as Sport Game or

festival

Introduction (cont )





Platinum User Configuration Platinum user IMSI list (at most 1000 users per RNC) should be configured by operator with administrator right , without

CN configuration changed.

Platinum User Identification

RNC will save and maintain Platinum Users’ IMSI-TMSI mapping list

If Initial UE identity IE in RRC connection request is TMSI or IMSI, RNC will distinguish Platinum User by TMSI-IMSI

table.

Whatever CS or PS service is initiated, TMSI will be used preferentially according 25.331.

RNC will get new TMSI from NAS message and refresh IMSI-TMSI mapping list.

Platinum user Access Prioritizing

Platinum user will preempt other user’s resource both at RRC and RAB establishment phase

In flow control , RRC Connection Request of platinum user is with same priority as conversational service .

Platinum User Voice Quality

Platinum user with AMR service will get more downlink power at weak coverage

Platinum User preferential Scheduling

Platinum user with PS service will get highest scheduling weight. it is independent of the Gold/Sliver/Copper user

configuration.

Gold/Sliver/Copper differentiation is only applied at scheduling phase, but Platinum user prioritizing is applied both ataccess and scheduling phase

Benefit & Impact




Benefit & Impact

Benefit

Platinum user will get higher access success rate than other users

at cell congestion scenario.

Platinum user CS voice quality is improved especially at weak

coverage condition.

Higher PS throughput will be supplied for Platinum user.

Impact

Cell Call drop rate in busy hours will increase due to Platinum

user’s resource preemption.

Dependence

RNC level License is required

Page98

Experience


Experience OAM




Experience













Description Cell HSDPA Power Quota is means that the percentage of cell total

Tx Power

Cell HSDPA Power Quota of each group only take effect in case of

cell power congestion

For example The HSDPA Power Quota is Group Gold 100%, Group Silver 70%, Group

Copper 10%

When cell power is NOT congested, the Group Copper users could use

more power as required. I.e. Quota will not limit the power allocation.

Only Cell power congestion happened, the Group Copper user could use

10% Quota maximally. i.e. Quota is effect.

Benefit




Benefit

Benefit Limit low valuable HSDPA user power consumption and supply more

power resource to high valuable HSDPA users at cell power

congestion scenario.

Impact

The GBR throughput of users at low valuable group is maybe not beguaranteed due to multi users sharing the limited Quota at cell power

congestion scenario. Even, call drop risk is increased for users at low

valuable group.

Dependence

RNC level license is needed This feature could not activated simultaneously with WRFD-030005

ICR downlink resource allocation or WRFD-140223 MOCN cell

resource allocation.

Experience


Experience OAM




Experience




Background




Background

As the investigation of 3rd party, Different application distribution at different

area. So single QoS strategy can’t fit multiplex custom requirement. At RAN15.0, customized QoS management platform is introduced to support

colorful and finer QoS management capability for different operator.

Top Applications list - North America, Mobile Access Top Applications list - Asia-Pacific, Mobile Access

Introduction

SmartCare Professional Serviceis required



HUAWEI TECHNOLOGIES CO., LTD.Huawei Confidential 106

NodeB RNC

M2000

NIU

1

Optimization Request

2

3

SGSN/GGSN

1

2

3

NIU board equipped(Hardware)

APP charact. Database

(software)

SmartCare Professional

Service

Fast optimization solution

w/o RAN release upgrade

Target Applicationexperience improved

quickly

Dependence



OAM


Experience OAM




OAM

Capacity Visualization Platform

EBC (Event Based Counter)

Capacity Visualization Platform

SmartView Professional

Service is required




Cell3:Hot spot

Cell2:

Dual-band

load

unbalance

Cell1:

Neighbor Cells outage

Cell Capacity Map

Capacity

Overview

BottleneckIdentification

In-depth

Analysis

PRS

License

Utility

Iu

Utility

Board

CPU Load

RNC1

RNC Capacity Alarm Map

Visualization by GISVisualization by table

NodeB

RNC

RNC

LicenseUtility

IuUtility

IurUtility

BoardCPU Load

RNC1

RNC2

…

Comprehensive and clear capacity

dashboard by multiple dimensions

DependencePRS server

SmartView Prof. Service

EBC (Event Based Counter)

One Feature of M2000




Service DimensionUser A

Event

Counter 1

EventCounter 2

…….

…….

Event

Counter 3

EventCounter 4

…….

Event

Counter 6

EventCounter 7

Benefit

Customized counter definition tomeet different customer’s need

Flexible counter amount, not

dependant on software upgrade

Simplifies service evaluation and

trouble shooting in the radio

network

User B

User C

SAU Board RNC

Feature Dimension

Cause Dimension

M2000

Dependence

SAU Board

System Capability Improvement




y p y p

Network KPI

Experience

HSPA

OAM

Accessibility Enhancement



HUAWEI TECHNOLOGIES CO., LTD.Huawei Confidential

112

Description

Traditional programs：Message of

RRC Connection Setup is sent over the

FACH with fixed power during the RRC

setup Stage

New programs: Message of RRC

Connection Setup is sent over theFACH with Dynamic power according

to the coverage

This algorithm could be active by cell

Benefit

Improve RRC connect setup successrate in case of downlink weak coverageNote: only one fixed power addition step

is supported for Power Up procedure.

i.e. all RRC Connect Setup message at “Power Up” status will

user same FACH power.

Improve RRC connect success ratio

Accessibility Enhancement (cont.)Improve CS/PS RAB establishment success ratio




Description

Current Algorithm: CE is hardware resource in NodeB, RNC do the CE admission and

preemption, NodeB only do the CE dynamic scheduling between admitted UE. UE is rejected in RNC by CE resource, preemption is triggered in RNC;

UE is admitted in RNC, and reject in NodeB by CE resource (because of CE fragment, etc), preemption

can not be triggered.

Enhancement at RAN15.0：CE Preemption triggered in NodeB, increase the all the feature of

preemption

Benefit Decrease CS/PS RAB Failure due to CE congestion by Enhancement of RAB Preemption

Algorithm

Impact

Low priority service call drop due preempt will increased

UE request Admitted in RNC

Rejected by CE

•Preemption failure

•UE is rejected

UE request Admitted in RNC

Rejected by CE

Preemption triggered in NodeBUE admit success

Original Enhancement

p /

Retainability Enhancement




y

Description

Current Algorithm: RNC detected TRB reset of

Single PS user in state of Cell_DCH，Radio link

will be deleted and user drop in R14 and earlier

versions.

Enhancement at RAN15.0：Deactivate Radio link

instead of delete，user detect downlink Radio

link failure will trigger cell update procedure. If the

Cell update procedure establish successfully, the

user traffic is resume.

Benefit

Reduce the call drop trigged by TRB Reset,improve PS call drop rate(PS R99 and PS

HSDPA）

Decrease PS Call Drop

Retainability Enhancement(cont.)




y ( )

Description

Current algorithm: RNC release RL

when RNC detect SRB Reset after

Inter-RAT handover command

message sent. One call drop iscounted

Enhancement at RAN15.0: RNC

cancel the relocation procedure and

trigger call re-establishment by cell

update.

Benefit

Decrease call drop during Inter-RAT

handover procedureCS IRATHO procedure

Decrease CS/PS Call Drop

Mobility Enhancement(CS+PS with Iur Relocation) Description

C




Description

Current

If CS Relocation switch and PS

DSCR switch is ON, Execute CS+PScombined service handover over Iur,

no relocation executed

RAN15.0

If CS Relocation switch and PS

DSCR switch is ON, Execute CS+PS

combined service handover firstly,then release PS, execute CS

relocation lastly.

Benefit

Decrease CS call drop because that CS

Relocation due to HHO will trigger higher

call drop compared with CS staticrelocation (UE Not involved)

Dependence

None

Only CS+PS SHO over

Iur executed

Current

Step1: CS+PS SHO over

Iur executed

Step2:Release PS , then

execute CS relocation (UE

Not involved)

RAN15.0

IurSRNC DRNC DRNC

Release PS , then execute

CS Relocation due to Hard

Handover

Iur

Iur

SRNC DRNC DRNC

Iur

Step1: CS+PS SHO over Iur

executed

Step2:Release PS , then

execute CS relocation (UE

Not involved)

No Iur





y p y p

Network KPI

Experience

HSPA

OAM

SMS Paging Enhancement




Description

Current Algorithm:

SMS Paging priority is equal to PS Paging priority. So

when PCH is congested, SMS Paging may be

discarded, leading to SMS Experience get worse

Enhancement at RAN15.0:

Upgrade SMS Paging priority higher than PS Paging

priority as following: Conversational Call > SMS

(Low_Priority_Signalling) > Interactive /Background

/High_Priority_Signalling.

when PCH channel congestion happened ,discard

lowest priority to prioritize higher priority service

Benefit

To improve the success ratio of SMS paging

Page 118

CS

CS

PS

PS

PS

CS

CS

SMS

PS

PS

SMS

Paging Queue Paging Queue

DiscardSMS Paging

SMS Discard PSPaging

Cell HSPA Capability Indicator Enhancement




Description Most of UE, Android especially will display network status as

In idle status. Display “H” logo if SIB5 “HSDPA cell Indicator” is true; else, display “3G” logo.

In Connection status. Display “H” logo if HS-PDSCH is allocated; else, display “3G” logo .

Normally, System will broadcast cell HSPA capability according to cell configuration.

So, some UE will display “H” logo at HSPA cell even at idle status. In this case, the

user maybe have misunderstanding that the phone is online always, the battery

consumption and traffic consumption is increased.

At RAN15.0, one Cell HSPA Capability Display Switch is added to control if broadcast

cell HSPA capability at SIB5

Benefit

Eliminating user misunderstandings





Network KPI

Experience

HSPA

OAM



Uplink Enhanced CELL_FACH




DPCCH

F-DPCH

E-DPDCH/E-DPCCH

HS-SCCH

HS-PDSCH (1…N)

……

E-HICH/E-AGCH/E-RGCH

HS-DPCCH

Physical channels for E-FACH/E-RACH users

Description

Current Algorithm HS-DPCCH is Not supported.

NodeB executes blind retransmission

(fixed retransmission times) since there

is no ACK/NACK.

Enhancement at RAN15.0

HS-DPCCH feedback for E-RACH/E-

FACH user supported

NodeB executes the retransmission

based on the ACK/NACK feedback from

UE.

Benefit

Improve eFACH/eRach user downlink

throughput





Network KPI

Experience

HSPA

OAM

Sector level Counter for Multi-RRU Co-cell




Description New Counter Measurement Object is design to evaluate sector

accessibility and retainability

New Counter is useful in case of Multi-RRU co-cell scenario, such as

IDS, highway coverage。

Benefits Improve KPI issue troubleshooting efficiency

No Item Description

1 VS.RL.NormRel.Locell.Sector Cell-Sector level RL normal release number

2 VS.RL.AbnormRel.Locell.Sector Cell-Sector level RL abnormal release number3 VS.PositiveNum.AICH.Locell.Sector Cell-Sector level AI positive response number

4 VS.NegativeNum.AICH.Locell.Sector Cell-Sector level AI positive response number

5 VS.TBNum.Succ.RACH.Locell.SectorCell-Sector level RACH Channel received TB successfully

number

6 VS.TBNum.Total.RACH.Locell.Sector Cell-Sector level RACH Channel received TB total number



Copyright©2011 Huawei Technologies Co., Ltd. All Rights Reserved.

The information in this document may contain predictive statements including, without limitation,

statements regarding the future financial and operating results, future product portfolio, new technology,etc. There are a number of factors that could cause actual results and developments to differ materially

from those expressed or implied in the predictive statements. Therefore, such information is provided for

reference purpose only and constitutes neither an offer nor an acceptance. Huawei may change the

information at any time without notice

Thank youwww.huawei.com

Date post:	02-Jun-2018
Category:	Documents
Upload:	ariel-mendoza
View:	221 times
Download:	0 times

Introduction of UMTS RAN15.0_V1.3

Documents