Upload
keartichai-chomtaku
View
68
Download
13
Embed Size (px)
DESCRIPTION
How to Deploy MOCN
Citation preview
How to deploy MOCN for T How to deploy MOCN for T How to deploy MOCN for T How to deploy MOCN for T
ProjectProjectProjectProject
HUAWEI TECHNOLOGIES CO., LTD.
ProjectProjectProjectProject
ContentContentContentContent
� Performance Risk in RAN SharingPerformance Risk in RAN SharingPerformance Risk in RAN SharingPerformance Risk in RAN Sharing---->MOCN Process>MOCN Process>MOCN Process>MOCN Process
� Intra-frequency interference issue of 99,00 boundary
� Load balance of 00 commercial strategy
� Risk in Swap Process
� KPI Monitor in MOCN
HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 2
� KPI Monitor in MOCN
Page 2
MOCN ArchitectureMOCN ArchitectureMOCN ArchitectureMOCN Architecture
MSC SGSN
TMV CN
52099
Iu interface
。。。。。。。。。。。。MSC SGSN
RMV CN
52000SGSNMSC
Common PLMN XXXX
HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 3
99+0099+0099+0099+0099+0099+0099+0099+00
RNC
NodeB
Iub interface
。。。。。。。。。。。。Shared RAN
� 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;
00000000000000000000000000000000
0000000000000000f1
f2
MOCN cell
Dedicated cell
Configuration DiscussionConfiguration DiscussionConfiguration DiscussionConfiguration Discussion
GSM 99
3G F1
3G F2
99+0099+0099+0099+00 00
0000F2’
00 00
00
BMALAC
HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 4
1, F1/F2 configure in the same LAC; different LAC with GSM
2, Neihboring configuration between F1/F2/GSM3, ePLMN configure for 52000 user only. Configure in GSM 99/ 3G 00 core network.
�There are not roaming relationship
between 3G of 99 and 00;
Mobility of Mobility of Mobility of Mobility of 99999999’s user’s user’s user’s user
GSM 99
3G F1
3G F2
99+0099+0099+0099+00 00
0000F2’
00 00
00
BMA
X
X
Handover
Cell Reselection
A B
HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 5
99
3G<->3G 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;
00
intraintraintraintra----frequency interferencefrequency interferencefrequency interferencefrequency interference
99+0099+0099+0099+00
0099999999++++00000000
0000
0000
0099+0099+0099+0099+00
0099999999++++00000000
99 user
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.
The RTWP of outside F1/00 cell may rise, the RTWP
of F1/99+00 cell may rise little.
Impact Impact Impact Impact
ObjectObjectObjectObject
ImpactImpactImpactImpact ReasonReasonReasonReason
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
F1
F2
F1
F2
00user
HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 6Page 6
0099+0099+0099+0099+00
0000
0099+0099+0099+0099+00
BMABMA
boundary
GSM 99
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
outside
F1/00 user
Accessibility Ratio
maybe worse
Due to RTWP rise of F1/00
Call Drop Rate
maybe worse
Due to RTWP rise of F1/00
F1
F2
outside
intraintraintraintra----frequency interference analysis(1)frequency interference analysis(1)frequency interference analysis(1)frequency interference analysis(1)
99999999++++0000000000 B
OutsideBoundary
GSM 99
Couple Loss1 Couple Loss2
To simply the model , Couple Loss is defined as the loss
between the Base TX and UE, including the antenna
gain and path loss
99
HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 7Page 7
Analysis:2D trigger at -100dBm,CPICH is 33dBm,the couple loss is 133dBFrom 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.
intraintraintraintra----frequency interference analysis(2)frequency interference analysis(2)frequency interference analysis(2)frequency interference analysis(2)
99+0099+0099+0099+00 00 B
OutsideBoundary
GSM 99
Couple Loss1 Couple Loss2
00
HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 8Page 8
1A threshold is 3dBAssume 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.
Solution1Solution1Solution1Solution1Impact ObjectImpact ObjectImpact ObjectImpact Object ImpactImpactImpactImpact EffectEffectEffectEffect
boundary
F1/99 user
Accessibility Ratio
maybe worse
N/A
Call Drop Rate
maybe worse
N/A
Inter-RAT handover
time increase
N/A
boundary
F1/99 user
Accessibility Ratio
maybe worse
Improved
Call Drop Rate
maybe worse
Improved
Reason
BMA 99+00 99+00 capacity loss Block boundary
F1/99+00 cell
0099+0099+0099+0099+00
0099+0099+0099+0099+00
99+0099+0099+0099+00
0000
00
0099+0099+0099+0099+00
0099+0099+0099+0099+00
99+0099+0099+0099+00
99 user
F1
F2
F1
F2
F1
00user
0000
HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 9Page 9
GSM 99
Solution: Block boundary F1/99+00 cell as buffer zone
Impact::::Buffer Zone is simple to deploy,,,,but there is some capacity loss.
F1/99+00 cell
Boundary 00 Bearing more
capacity
Block boundary
F1/99+00 cell00
99+0099+0099+0099+000000
0099+0099+0099+0099+00
BMABMA
boundary
F1
F2
outside
99+0099+0099+0099+00 Blocked for Buffer Zone
Solution Solution Solution Solution 2222
99
UE TX(dBm)
20
Handover
areaCell A Cell B
2D trigger
99+0099+0099+0099+00 00 B
OutsideBoundary
Couple Loss1 Couple Loss2
Handover area
00
99
HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 10Page 10
00
distance
-20
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.
GSM 99
Solution 2Solution 2Solution 2Solution 2
99
UE TX(dBm)
UE Tx power limited
trigger
20
Handover
areaCell A Cell B
2D triggerImpact ObjectImpact ObjectImpact ObjectImpact Object ImpactImpactImpactImpact EffectEffectEffectEffect
boundary
F1/99 user
Accessibility Ratio
maybe worse
some improved
Call Drop Rate
maybe worse
some improved
HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 11Page 11
00
distance
trigger threshold
-20
Inter-RAT handover
times may increase
Times increase
boundary
F1/99 user
Accessibility Ratio
maybe worse
Improved
Call Drop Rate
maybe worse
Improved
Reason
boundary
F1/00 user
Inter-RAT handover
times may increase
UE Tx power limited
trigger threshold
too small
Call Drop Rate
maybe worse
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
Solution 2(The Rule of setting threshold)Solution 2(The Rule of setting threshold)Solution 2(The Rule of setting threshold)Solution 2(The Rule of setting threshold)
99
UE TX(dBm)
20
Handover
areaCell A Cell B
2D trigger
The rule of setting UE Tx Power
limited trigger threshold.
When 00 user leave Cell A to
Cell B, we choose the maximal 00 UE Tx power as the threshold.
HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 12Page 12
99
00
distance
UE Tx power limited
trigger threshold
-20
2D trigger
The maximal 00 UE Tx power
00 UE Tx power as the threshold.
So 00 user will soft handover to
Cell B.
Otherwise 99 user will trigger handover to 2G.
Solution 3Solution 3Solution 3Solution 3((((Modified in ProductModified in ProductModified in ProductModified in Product)))) Impact ObjectImpact ObjectImpact ObjectImpact Object ImpactImpactImpactImpact EffectEffectEffectEffect
boundary
F1/99 user
Accessibility Ratio
maybe worse
Improved
Call Drop Rate
maybe worse
Some improved
Inter-RAT handover
time increase
Not improved
boundary
F1/99 user
Accessibility Ratio
maybe worse
Improved
Call Drop Rate
maybe worse
Improved
99+0099+0099+0099+0000 B
OutsideBoundary
GSM 99
Couple Loss1 Couple Loss2
99
HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 13Page 13
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.
00 Commercial dual carriers strategy00 Commercial dual carriers strategy00 Commercial dual carriers strategy00 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
HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 14Page 14
Free camping / Load balancing strategyFree camping / Load balancing strategyFree camping / Load balancing strategyFree camping / Load balancing strategy
3G F1
3G F2
99+0099+0099+0099+00 00
0000 F2’
00 00
00
BMA Cell Reselection
A B
HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 15
0000
Idle 00 can choose better Ec/Io cell to camp on
Access 00 user start services where the carrier camp on
MOD UCELLSELRESEL: CellId=<CELLID>, QualMeas=CPICH_ECNO, QrxlevminExtSup=FALSE,
IdleSintrasearch=127, IdleSintersearch=127, NonhcsInd=NOT_CONFIGURED;
Real Network Application(Real Network Application(Real Network Application(Real Network Application(Canada Bell free camping strategy analysisCanada Bell free camping strategy analysisCanada Bell free camping strategy analysisCanada Bell free camping strategy analysis))))
HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 16Page 16
HSDPAHSDPAHSDPAHSDPA user numberuser numberuser numberuser numberRRC requestRRC requestRRC requestRRC request timestimestimestimes AMR AMR AMR AMR ErlangErlangErlangErlang
InInInIn the 24 hours, RRC request times and traffic of three carriers is almost the same.the 24 hours, RRC request times and traffic of three carriers is almost the same.the 24 hours, RRC request times and traffic of three carriers is almost the same.the 24 hours, RRC request times and traffic of three carriers is almost the same.
So free camping strategy is fit for load balance.So free camping strategy is fit for load balance.So free camping strategy is fit for load balance.So free camping strategy is fit for load balance.
Preferred camping/Service steering strategy Preferred camping/Service steering strategy Preferred camping/Service steering strategy Preferred camping/Service steering strategy
3G F1
3G F2
99+0099+0099+0099+00 00
0000 F2’
00 00
00
BMA Cell Reselection
A BService Steering DRD
HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 17
0000
PriorityServiceFor R99RT R99NRT HSDPA HSUPAF1 1 1 2 2F2 1 1 1 1
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
Mobility of 00’s user Mobility of 00’s user Mobility of 00’s user Mobility of 00’s user
GSM 99
3G F1
3G F2
99+0099+0099+0099+00 00
0000F2’
00 00
00
BMA
Handover
Cell Reselection
A B
HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 18
00
3G->2G Coverage based inter PLMN inter-RAT handover; (PS service reselect to GSM)2G<->3G Cell reselect back to F1/F2; (PS service can’tPS service can’tPS service can’tPS service can’t reselect to 3Greselect to 3Greselect to 3Greselect to 3G)
3G<->3G Handover between F1/F2 and Cell A/B
Strategy Comparison Strategy Comparison Strategy Comparison Strategy Comparison Free camping / Load balancing strategy
Preferred camping/Service steering strategy
F1/99+0099 User R99+H00 User R99+H
99 User R99+H00 User R99
F2/00 00 User R99+H 00 User H
Free camping / Load balancing strategyPreferred camping/Service steering strategy
If 00 user is too many,F2/00 can absorb If 00 user is too many,F2/00 can not
HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 19Page 19
99 UserIf 00 user is too many,F2/00 can absorb more 00 User.99 User will not affected.
If 00 user is too many,F2/00 can not bear the R99 user of F2/00.The F1/99+00 may congestion.
00 User
If 99 User is too many, the load of F1/99+00 is heavier. The EcIo of F1/00+99 is worse, The 00 user can reselect to F2/00to offload the traffic.
If 99 User is too many,00 user can not offload to F2/00 this may cause KPI worse.
Free camping strategy is good for load balancing.Free camping strategy is good for load balancing.Free camping strategy is good for load balancing.Free camping strategy is good for load balancing.
Preferred camping may cause traffic unbalanced which cause KPI degradation.Preferred camping may cause traffic unbalanced which cause KPI degradation.Preferred camping may cause traffic unbalanced which cause KPI degradation.Preferred camping may cause traffic unbalanced which cause KPI degradation.
How to get the target networkHow to get the target networkHow to get the target networkHow to get the target network
New CN pool for RMV
RMV(PLMN2) TMV(PLMN1)
RNC
PBI RNCPBI RNCPBI RNCPBI RNC
RMV(PLMN2)’
Test bed CN for RMVLiving CN for TMV
MTG RNCMTG RNCMTG RNCMTG RNC
Core
HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 20
RNC1 RNCn
PBI RNCPBI RNCPBI RNCPBI RNC MTG RNCMTG RNCMTG RNCMTG RNC
PLMN1
PLMN2
RNC1 RNCn
UPC
PLMN2
PLMN2
BMA
F1
F2
•New RNC•Rehoming
•New NodeB
RAN Sharing
How to get the target networkHow to get the target networkHow to get the target networkHow to get the target network
New CN pool for RMV
RMV(PLMN2) TMV(PLMN1)
RNC
PBI RNCPBI RNCPBI RNCPBI RNC
RMV(PLMN2)’
Living CN for TMV Test bed CN for RMV
MTG RNCMTG RNCMTG RNCMTG RNC
C o r eC o r eC o r eC o r e
HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 21
RNC1 RNCn
PBI RNCPBI RNCPBI RNCPBI RNC MTG RNCMTG RNCMTG RNCMTG RNC
PLMN1
PLMN2
RNC1 RNCn
BMAUPC
PLMN2
PLMN2
RAN Sharing
F1
F2
PLMN2+PLMN1
MOCN
• New CN pool• Rehoming RNC
• Change to MOCN
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.
Risk in Swap ProcessRisk in Swap ProcessRisk in Swap ProcessRisk in Swap Process
HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 22Page 22
KPI MonitorKPI MonitorKPI MonitorKPI Monitor
Item KPI Reference
RTWP VS.MeanRTWP
TCP VS.MeanTCP.NonHS
CS CDRCS Service Drop Ratio (Cell)
PS CDRPS Call Drop Ratio (Cell)
RRC Setup Success Ratio (Cell.Service)
HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 23Page 23
RRC RRC Setup Success Ratio (Cell.Service)RRC Setup Success Ratio (Cell.Other)
Inter-RATCS W2G Inter-RAT Handover Out Success Ratio (Cell)PS W2G Inter-RAT Handover Out Success Ratio (Cell)
Except regular KPI monitor, RTWP RRC CDR Inter-RAT success ratio should be monitored carefully.
MOCN KPI monitorMOCN KPI monitorMOCN KPI monitorMOCN KPI monitorID Counter Description
67193097 VS.IU.MOCN.CsPsCoordination Number of Redirection Requests from CN (CS/PS Coordination Required)
67193098 VS.IU.MOCN.LocAreaNotAllowed Number of Redirection Requests from CN (Location Area Not Allowed)67193099 VS.IU.MOCN.PlmnNotAllowed Number of Redirection Requests from CN (PLMN Not Allowed)67193100 VS.IU.MOCN.RoamNotAllowed Number of Redirection Requests from CN (Roaming Not Allowed in this Location Area)67193101 VS.IU.MOCN.NoSuitableCell Number of Redirection Requests from CN (No Suitable Cell in Location Area)67193102 VS.IU.MOCN.GprsServicesNotAllowed Number of Redirection Requests from CN (GPRS Services Not Allowed in this PLMN)67196193 VS.RAB.NormRel.AMR.PLMN.RNC Number of Normally Released AMR CS RABs for Operator67196195 VS.RAB.NormRel.CS64.PLMN.RNC Number of Normally Released 64kbit/s CS Conversational Service RABs for
Operator67196197 VS.RAB.NormRel.PS.PLMN.RNC Number of Normally Released PS RABs for Operator67196192 VS.RAB.AbnormRel.AMR.PLMN.RNC Number of Abnormally Released AMR CS RABs for Operator
67196194 VS.RAB.AbnormRel.CS64.PLMN.RNC Number of Abnormally Released 64kbit/s CS Conversational Service RABsfor Operator67196196 VS.RAB.AbnormRel.PS.PLMN.RNC Number of Abnormally Released PS RABs for Operator
67196186 VS.RAB.AttEstab.AMR.PLMN.RNC Number of AMR CS RABs Establishment Requests for Operator67196188 VS.RAB.AttEstab.CS64.PLMN.RNC Number of 64kbit/s CS Conversational Service RABs Establishment
Requests for Operator67196190 VS.RAB.AttEstab.PS.PLMN.RNC Number of PS RABs Establishment Requests for Operator
Redirection
Retainability
Accessibility
HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 24Page 24
67196190 VS.RAB.AttEstab.PS.PLMN.RNC Number of PS RABs Establishment Requests for Operator67196187 VS.RAB.SuccEstab.AMR.PLMN.RNC Number of AMR CS RABs Successfully Established for Operator(WB+NB)67196189 VS.RAB.SuccEstab.CS64.PLMN.RNC Number of 64kbit/s CS Conversational Service RABs Successfully67196191 VS.RAB.SuccEstab.PS.PLMN.RNC Number of PS RABs Successfully Established for Operator67193016 VS.HSDPAPSLoad.MaxDLThruput.PLMN.RN Maximum Downlink PS HSDPA Traffic for RNC per Operator67204836 VS.VP.Erlang.Equiv.PLMN.RNC Equivalent Erlang of 64kbit/s CS Service for RNC per Operator67193010 VS.R99PSLoad.MaxULThruput.PLMN.RNC Maximum Uplink PS R99 Traffic for RNC per Operator67193022 VS.MBMSPSLoad.MaxDLThruput.PLMN.RNC Maximum Downlink PS MBMS Traffic for RNC per Operator67204149 VS.MBMSPSLoad.DLThruput.PLMN.RNC Downlink PS MBMS Traffic for RNC per Operator67193019 VS.HSUPAPSLoad.MaxULThruput.PLMN.RN Maximum Uplink PS HSUPA Traffic for RNC per Operator67204835 VS.AMR.Erlang.Equiv.PLMN.RNC Equivalent Erlang of CS AMR Service for RNC per Operator67204146 VS.R99PSLoad.DLThruput.PLMN.RNC Downlink PS R99 Traffic for RNC per Operator67204147 VS.HSDPAPSLoad.DLThruput.PLMN.RNC Downlink PS HSDPA Traffic for RNC per Operator67203962 VS.CSLoad.Erlang.Equiv.PLMN.RNC Equivalent CS Erlang for RNC per Operator67193013 VS.R99PSLoad.MaxDLThruput.PLMN.RNC Maximum Downlink PS R99 Traffic for RNC per Operator67192511 VS.CSLoad.MaxErlang.Equiv.PLMN.RNC Maximum equivalent CS Erlang for RNC per Operator67204145 VS.R99PSLoad.ULThruput.PLMN.RNC Uplink PS R99 Traffic for RNC per Operator67204148 VS.HSUPAPSLoad.ULThruput.PLMN.RNC Uplink PS HSUPA Traffic for RNC per Operator73440109 VS.PS.CellFachUEs.PLMN Number of Cell_FACH UEs in PS Domain for RNC per Operator73410502 VS.PSLoad.Thruput.PLMN.RNC Average Total Throughput of UL and DL PS Services per Operator for RNC67204840 VS.PS.CellDchUEs.PLMN Number of Cell_DCH UEs in PS Domain for RNC per Operator73394023 VS.PSLoad.MaxThruput.PLMN.RNC Maximum Total Throughout of UL and DL PS Services per Operator for RNC
Accessibility
Traffic