Вы находитесь на странице: 1из 24

How to deploy MOCN for T

Project

HUAWEI TECHNOLOGIES CO., LTD.

Content
 Performance Risk in RAN SharingSharing->MOCN Process





Intra-frequency interference issue of 99,00 boundary


Load balance of 00 commercial strategy
Risk in Swap Process
KPI Monitor in MOCN

HUAWEI
CO., LTD.
HISILICONTECHNOLOGIES
SEMICONDUCTOR

Page 22
Page

MOCN Architecture
Common PLMN XXXX
TMV CN
52099

MSC

SGSN

RMV CN
52000
MSC

MSC

SGSN

SGSN

Iu interface

RNC

The shared RAN is connected to multi-operators


core network;

In MOCN, frequency and baseband resources are


shared;

Each operator can deploy Iu-flex independently;

Iub interface
NodeB

f1
f2

99+00
00
HUAWEI
CO., LTD.
HISILICONTECHNOLOGIES
SEMICONDUCTOR

Shared RAN

00
00

MOCN cell
Dedicated cell

Page 3

Configuration Discussion
BMA

LAC

3G F1

99+00

00

3G F2

00

00

00

00
00

F2

GSM 99

There

are not roaming relationship


between 3G of 99 and 00;
1, F1/F2 configure in the same LAC; different LAC with GSM
2, Neihboring configuration between F1/F2/GSM
3, ePLMN configure for 52000 user only. Configure in GSM 99/ 3G 00 core network.

HUAWEI
CO., LTD.
HISILICONTECHNOLOGIES
SEMICONDUCTOR

Page 4

Mobility of 99s
99s user
Handover

BMA
3G F1

99+00

Cell Reselection
A

00

00

00

X
3G F2

00

00

00

F2

GSM 99

3G<->3G

99
From F1 to F2, not allowed;F2 reject 99 user by PLMN(PLMN not allowed)
From Cell A to B, not allowed, 99 user drop to GSM;Cell B reject 99 user by PLMN(PLMN
not allowed)

3G ->2G

Coverage based inter PLMN inter-RAT handover;

2G<->3G

Cell reselect back to F1(No ePLMN, will not select F2);


HPLMN reselect;

HUAWEI
CO., LTD.
HISILICONTECHNOLOGIES
SEMICONDUCTOR

Page 5

Issue

When 99 user in BMA boundary move outside BMA


area, it can only hand over to GSM 99, due to BMA
outside F1/00 can not support the handover.

intraintra-frequency interference
00user

The RTWP of outside F1/00 cell may rise, the RTWP


of F1/99+00 cell may rise little.

99 user
F1
F2
F1
F2

F1
F2

99+00
00
99+
99+00
00
99+00
00

BMA

99+00
00
99+
99+00
00
99+00
00

BMA
boundary

00
00
00
00

Impact
Object

Impact

Reason

boundary
F1/99 user

Accessibility Ratio
maybe worse

1)When UE access the side to outside


can not do soft handover , Accessibility
Ratio decrease
2)Due to RTWP rise of F1/99+00

Call Drop Rate


maybe worse

1)More Inter-RAT handover may cause


CDR worse
2)Due to RTWP rise of F1/99+00

Inter-RAT
handover time
increase

If the GSM capacity is not


enough ,more use rs handover to GSM
may cause GSM congestion will cause
handover success ratio decrease

Accessibility Ratio
maybe worse

Due to RTWP rise of F1/00

Call Drop Rate


maybe worse

Due to RTWP rise of F1/00

00
00

outside

GSM 99
outside
F1/00 user

HUAWEI
CO., LTD.
HISILICONTECHNOLOGIES
SEMICONDUCTOR

Page 66
Page

intraintra-frequency interference analysis(1)


Outside

Boundary
99+
99+00

To simply the model , Couple Loss is defined as the loss


between the Base TX and UE, including the antenna
gain and path loss

00 B
Couple Loss2

Couple Loss1
99

GSM 99

Analysis
2D trigger at -100dBmCPICH is 33dBmthe couple loss is 133dB
From the link budget, in some scenarios, 99 user will cause the RTWP rise of outside F1/00 B cell. This is relevant with service and UE
position.
Solution
99 user should be able to handover to GSM asap.00 user should keep intra-frequency handover.
HUAWEI
CO., LTD.
HISILICONTECHNOLOGIES
SEMICONDUCTOR

Page 77
Page

intraintra-frequency interference analysis(2)


Outside

Boundary
99+00

00 B
Couple Loss2

Couple Loss1
00

GSM 99

1A threshold is 3dB
Assume RTWP of outside F1/00 is -98dBm,before 1A event triggered, the interference to F1/99+00 is calculated above.
This kind of interference is temporary for after 1A triggered, F1/99+00 can control the UE TX power.

HUAWEI
CO., LTD.
HISILICONTECHNOLOGIES
SEMICONDUCTOR

Page 88
Page

Solution1
00user

Impact Object

Impact

Effect

boundary
F1/99 user

Accessibility Ratio
maybe worse

N/A

Call Drop Rate


maybe worse

N/A

Inter-RAT handover
time increase

N/A

Accessibility Ratio
maybe worse

Improved

Call Drop Rate


maybe worse

Improved

99 user
F1
F2
F1
F2

F1
F2

99+00
00

99+00
00
99+00
00

99+00
00
99+00
00
BMA

99+00
00
BMA
boundary
GSM 99

00
00

boundary
F1/99 user

00
00
00
00

Reason
BMA 99+00

99+00 capacity loss

Block boundary
F1/99+00 cell

Boundary 00

Bearing more
capacity

Block boundary
F1/99+00 cell

outside

Solution: Block boundary F1/99+00 cell as buffer zone

99+00

Impact
Buffer Zone is simple to deploy
but there is some capacity loss.

HUAWEI
CO., LTD.
HISILICONTECHNOLOGIES
SEMICONDUCTOR

Page 99
Page

Blocked for Buffer Zone

Solution 2
UE TX
(dBm)

00
Boundary

Cell A

Outside

Handover
area

Cell B

00 B

99+00
Couple Loss1

Couple Loss2

20

99

99
Handover area

GSM 99

00

-20
distance
When 00 user leave Cell A to Cell B, 00 user UE TX power is less after handover to Cell B
When 99 user leave Cell A to Cell B , the UE TX power increased until the RSCP or Ec/No
2D event trigger coverage handover to GSM
The UE TX power of two users is depicted in the figure.

HUAWEI
CO., LTD.
HISILICONTECHNOLOGIES
SEMICONDUCTOR

Page 10
10
Page

2D trigger

Solution 2
UE TX
(dBm)

Cell A

Handover
area

20

Cell B

99

00

-20

Solution:
Switch on the handover based on UE TX power to
make F1/99 user more early handover to GSM
Impact:
If the UE Tx power limited trigger threshold set too
high, the effect is not obvious.
If the UE Tx power limited trigger threshold set too
lower,F1/00 user may trigger handover to GSM
HUAWEI
CO., LTD.
HISILICONTECHNOLOGIES
SEMICONDUCTOR

2D trigger
UE Tx power
limited
trigger
threshold

distance

Impact Object

Impact

Effect

boundary
F1/99 user

Accessibility Ratio
maybe worse

some improved

Call Drop Rate


maybe worse

some improved

Inter-RAT handover
times may increase

Times increase

Accessibility Ratio
maybe worse

Improved

Call Drop Rate


maybe worse

Improved

boundary
F1/99 user

Reason
boundary
F1/00 user

Inter-RAT handover
times may increase
Call Drop Rate
maybe worse

Page 11
11
Page

UE Tx power limited
trigger threshold
too small

Solution 2(The Rule of setting threshold)

UE TX
(dBm)

Cell A

Handover
area

20

The rule of setting UE Tx Power


limited trigger threshold.

Cell B

99

00

-20

2D trigger
UE Tx power
limited
trigger
threshold

distance

When 00 user leave Cell A to


Cell B, we choose the maximal
00 UE Tx power as the threshold.
So 00 user will soft handover to
Cell B.
Otherwise 99 user will trigger
handover to 2G.

The maximal 00
UE Tx power

HUAWEI
CO., LTD.
HISILICONTECHNOLOGIES
SEMICONDUCTOR

Page 12
12
Page

Solution 3
3Modified in Product
Product

Impact Object

Impact

Effect

boundary
F1/99 user

Accessibility Ratio
maybe worse

Improved

Call Drop Rate


maybe worse

Some improved

Inter-RAT handover
time increase

Not improved

Accessibility Ratio
maybe worse

Improved

Call Drop Rate


maybe worse

Improved

Outside

Boundary
99+00

00 B
Couple Loss2

Couple Loss1

boundary
F1/99 user

99

GSM 99

Solution:
When 99 user move to F1/00 B cell, firstly active set is added, then trigger Inter-RAT handover
process. Due to this mechanism, the UE TX Power of 99 user can be controlled by F1/00 B cell. So
the Uplink interference can be eliminated some.
Impact:
Some Product code should be modified. Some resource of F1/00 B cell is used.

HUAWEI
CO., LTD.
HISILICONTECHNOLOGIES
SEMICONDUCTOR

Page 13
13
Page

00 Commercial dual carriers strategy


After 00 Commercial launched,
Two strategy can be used
1.Free camping / Load balancing strategy
2.Preferred camping/Service steering strategy

HUAWEI
CO., LTD.
HISILICONTECHNOLOGIES
SEMICONDUCTOR

Page 14
14
Page

Free camping / Load balancing strategy


Cell Reselection

BMA
3G F1

3G F2

99+00

00

00

00

00

Idle

00 can choose better Ec/Io cell to camp on

Access

00 user start services where the carrier camp on

00

00

F2

MOD UCELLSELRESEL: CellId=<CELLID>, QualMeas=CPICH_ECNO, QrxlevminExtSup=FALSE,


IdleSintrasearch=127, IdleSintersearch=127, NonhcsInd=NOT_CONFIGURED;

HUAWEI
CO., LTD.
HISILICONTECHNOLOGIES
SEMICONDUCTOR

Page 15

Real Network Application(Canada Bell free camping strategy analysis)

RRC request times

AMR Erlang

HSDPA user number

In the 24 hours, RRC request times and traffic of three carriers is almost the same.
So free camping strategy is fit for load balance.

HUAWEI
CO., LTD.
HISILICONTECHNOLOGIES
SEMICONDUCTOR

Page 16
16
Page

Preferred camping/Service steering strategy


Cell Reselection

BMA
99+00

3G F1

3G F2

00

00

00

00

00

00

Idle

00 prefer to camp on F1

Access

00 user start R99 services where the carrier camp on


00 user start H services DRD to F2/cell based on service steering

PriorityServiceFor
F1
F2

R99RT R99NRT
1
1
1
1

HUAWEI
CO., LTD.
HISILICONTECHNOLOGIES
SEMICONDUCTOR

HSDPA HSUPA
2
2
1
1

Page 17

Service Steering DRD

F2

Mobility of 00s user


Handover

BMA
3G F1

99+00

3G F2

00

Cell Reselection
A

00

00

00

00
00

F2

GSM 99

00
3G->2G

Coverage based inter PLMN inter-RAT handover; PS service reselect to GSM

2G<->3G

Cell reselect back to F1/F2; (PS


PS service cant reselect to 3G)
3G

3G<->3G

Handover between F1/F2 and Cell A/B

HUAWEI
CO., LTD.
HISILICONTECHNOLOGIES
SEMICONDUCTOR

Page 18

Strategy Comparison
F1/99+00
F2/00

Free camping / Load


balancing strategy
99 User R99+H
00 User R99+H

Preferred camping/Service
steering strategy
99 User R99+H
00 User R99

00 User R99+H

00 User H

Free camping / Load balancing strategy

Preferred camping/Service steering


strategy
If 00 user is too many,F2/00 can not
bear the R99 user of F2/00.The F1/99+00
may congestion.

99 User

If 00 user is too many,F2/00 can absorb


more 00 User.99 User will not affected.

00 User

If 99 User is too many, the load of


If 99 User is too many,00 user can not
F1/99+00 is heavier. The EcIo of F1/00+99
offload to F2/00 this may cause KPI
is worse, The 00 user can reselect to F2/00
worse.
to offload the traffic.

Free camping strategy is good for load balancing.


Preferred camping may cause traffic unbalanced which cause KPI degradation.

HUAWEI
CO., LTD.
HISILICONTECHNOLOGIES
SEMICONDUCTOR

Page 19
19
Page

How to get the target network


RMV(PLMN2)

RMV(PLMN2)

TMV(PLMN1)

Core
Living CN for TMV

New CN pool for RMV

Test bed CN for RMV

RNC
PBI RNC
RNC1

RNCn

RNC1

New RNC
Rehoming

RNCn

BMA

UPC

New

RAN Sharing

F1

PLMN1

PLMN2

F2

PLMN2

HUAWEI
CO., LTD.
HISILICONTECHNOLOGIES
SEMICONDUCTOR

MTG RNC

PLMN2

Page 20

NodeB

How to get the target network


RMV(PLMN2)

TMV(PLMN1)

RMV(PLMN2)

C o re
New CN pool for RMV

Test bed CN for RMV

Living CN for TMV

RNC
PBI RNC
RNC1

RNCn

RNC1

New CN pool
Rehoming RNC
Change to MOCN

RNCn

BMA

UPC

MOCN
RAN
Sharing

F1

PLMN2+PLMN1
PLMN1

PLMN2

F2

PLMN2

HUAWEI
CO., LTD.
HISILICONTECHNOLOGIES
SEMICONDUCTOR

MTG RNC

PLMN2

Page 21

Risk in Swap Process


1.Inter-PLMN 3G to 2G handover has been used in many other projects.

2.Except the intra-frequency interference issue, there is no special risk in swap process.

HUAWEI
CO., LTD.
HISILICONTECHNOLOGIES
SEMICONDUCTOR

Page 22
22
Page

KPI Monitor
Item
RTWP
TCP
CS CDR
PS CDR
RRC

KPI Reference
VS.MeanRTWP
VS.MeanTCP.NonHS
CS Service Drop Ratio (Cell)
PS Call Drop Ratio (Cell)
RRC Setup Success Ratio (Cell.Service)
RRC Setup Success Ratio (Cell.Other)

CS W2G Inter-RAT Handover Out Success Ratio (Cell)


Inter-RAT PS W2G Inter-RAT Handover Out Success Ratio (Cell)

Except regular KPI monitor, RTWP RRC CDR Inter-RAT success ratio should be monitored carefully.

HUAWEI
CO., LTD.
HISILICONTECHNOLOGIES
SEMICONDUCTOR

Page 23
23
Page

MOCN KPI monitor


Redirection

Retainability

Accessibility

Traffic

ID

Counter

Description

67193097

VS.IU.MOCN.CsPsCoordination

Number of Redirection Requests from CN (CS/PS Coordination Required)

67193098
67193099
67193100
67193101
67193102
67196193
67196195

VS.IU.MOCN.LocAreaNotAllowed
VS.IU.MOCN.PlmnNotAllowed
VS.IU.MOCN.RoamNotAllowed
VS.IU.MOCN.NoSuitableCell
VS.IU.MOCN.GprsServicesNotAllowed
VS.RAB.NormRel.AMR.PLMN.RNC
VS.RAB.NormRel.CS64.PLMN.RNC

67196197
67196192
67196194
67196196
67196186
67196188

VS.RAB.NormRel.PS.PLMN.RNC
VS.RAB.AbnormRel.AMR.PLMN.RNC
VS.RAB.AbnormRel.CS64.PLMN.RNC
VS.RAB.AbnormRel.PS.PLMN.RNC
VS.RAB.AttEstab.AMR.PLMN.RNC
VS.RAB.AttEstab.CS64.PLMN.RNC

Number of
Number of
Number of
Number of
Number of
Number of
Number of
Operator
Number
of

67196190
67196187
67196189
67196191
67193016
67204836
67193010
67193022
67204149
67193019
67204835
67204146
67204147
67203962
67193013
67192511
67204145
67204148
73440109
73410502
67204840
73394023

VS.RAB.AttEstab.PS.PLMN.RNC
VS.RAB.SuccEstab.AMR.PLMN.RNC
VS.RAB.SuccEstab.CS64.PLMN.RNC
VS.RAB.SuccEstab.PS.PLMN.RNC
VS.HSDPAPSLoad.MaxDLThruput.PLMN.RN
VS.VP.Erlang.Equiv.PLMN.RNC
VS.R99PSLoad.MaxULThruput.PLMN.RNC
VS.MBMSPSLoad.MaxDLThruput.PLMN.RNC
VS.MBMSPSLoad.DLThruput.PLMN.RNC
VS.HSUPAPSLoad.MaxULThruput.PLMN.RN
VS.AMR.Erlang.Equiv.PLMN.RNC
VS.R99PSLoad.DLThruput.PLMN.RNC
VS.HSDPAPSLoad.DLThruput.PLMN.RNC
VS.CSLoad.Erlang.Equiv.PLMN.RNC
VS.R99PSLoad.MaxDLThruput.PLMN.RNC
VS.CSLoad.MaxErlang.Equiv.PLMN.RNC
VS.R99PSLoad.ULThruput.PLMN.RNC
VS.HSUPAPSLoad.ULThruput.PLMN.RNC
VS.PS.CellFachUEs.PLMN
VS.PSLoad.Thruput.PLMN.RNC
VS.PS.CellDchUEs.PLMN
VS.PSLoad.MaxThruput.PLMN.RNC

HUAWEI
CO., LTD.
HISILICONTECHNOLOGIES
SEMICONDUCTOR

Redirection Requests from CN (Location Area Not Allowed)


Redirection Requests from CN (PLMN Not Allowed)
Redirection Requests from CN (Roaming Not Allowed in this Location Area)
Redirection Requests from CN (No Suitable Cell in Location Area)
Redirection Requests from CN (GPRS Services Not Allowed in this PLMN)
Normally Released AMR CS RABs for Operator
Normally Released 64kbit/s CS Conversational Service RABs for

Normally Released PS RABs for Operator


Number of Abnormally Released AMR CS RABs for Operator
Number of Abnormally Released 64kbit/s CS Conversational Service RABs
for Operator
Number
of Abnormally Released PS RABs for Operator
Number of AMR CS RABs Establishment Requests for Operator
Number of 64kbit/s CS Conversational Service RABs Establishment
Requests
Number offor
PS Operator
RABs Establishment Requests for Operator

Number of AMR CS RABs Successfully Established for Operator(WB+NB)


Number of 64kbit/s CS Conversational Service RABs Successfully
Number of PS RABs Successfully Established for Operator
Maximum Downlink PS HSDPA Traffic for RNC per Operator
Equivalent Erlang of 64kbit/s CS Service for RNC per Operator
Maximum Uplink PS R99 Traffic for RNC per Operator
Maximum Downlink PS MBMS Traffic for RNC per Operator
Downlink PS MBMS Traffic for RNC per Operator
Maximum Uplink PS HSUPA Traffic for RNC per Operator
Equivalent Erlang of CS AMR Service for RNC per Operator
Downlink PS R99 Traffic for RNC per Operator
Downlink PS HSDPA Traffic for RNC per Operator
Equivalent CS Erlang for RNC per Operator
Maximum Downlink PS R99 Traffic for RNC per Operator
Maximum equivalent CS Erlang for RNC per Operator
Uplink PS R99 Traffic for RNC per Operator
Uplink PS HSUPA Traffic for RNC per Operator
Number of Cell_FACH UEs in PS Domain for RNC per Operator
Average Total Throughput of UL and DL PS Services per Operator for RNC
Number of Cell_DCH UEs in PS Domain for RNC per Operator
Maximum Total Throughout of UL and DL PS Services per Operator for RNC

Page 24
24
Page

Вам также может понравиться