Beruflich Dokumente
Kultur Dokumente
Feb 2017
UL Info Transfer
Attach Complete
S1AP: UL Info Transfer :S1AP
Attach Complete
S10: Modify Bearer Request :S10
S10: Modify Bearer Complete :S10
Analysis:
1. RRC connection setup. As below, the RRC connection setup success rate is normal after 7th, Aug., but the
number of RRC connection setup increased after 7th, Aug.
Case Share 1 : TAC Not Mapping on CN Causes Attach Failure
2. E-RAB setup. The number of E-RAB setup is normal before 7th, Aug., and the E-RAB setup success rate was
normal before 7th, Aug. But the number of E-RAB setup dropped to zero suddenly from 7th, Aug.
Case Share 1 : TAC Not Mapping on CN Causes Attach Failure
3. Check the alarm log. There wasnt any new alarm report on 7th, Aug. (The IP Path Fault was caused by the X2
interface, rather than S1 interface, it wont affect the E-RAB setup.
Case Share 1 : TAC Not Mapping on CN Causes Attach Failure
4. Check the operation log. There wasnt any modification operation on 7th, Aug.
Case Share 1 : TAC Not Mapping on CN Causes Attach Failure
5. S1 interface trace. The MME dont send the initial UE context setup REQ message to eNB after eNB send the
initial_UE_MSG. On the opposite, the MME sends UE context release command to eNB to release the UE with cause
normal release. It needed the core network engineer to analyze it.
6. After the core network engineer check the MME. They confirmed that the core network engineer forgot to configure
the TAC of this eNodeB on the MME after they transferred the eNodeB to the other MME. When eNB send the
initial_UE_MSG Message to Core network, which includes the TAC of this eNodeB, but core network cant match this
site in TAC list. So it doesnt respond it, and do not trigger the e-RAB setup procedure.
Case Share 2 : Attach Failure due to missing User Plane Peer IP and MME IP
Phenomenon Description: UE cant make attach one new LTE site in SSA testing. And this site didnt
have any alarm impact service.
Analysis:
1. RRC connection setup. As below Graph 1 , the RRC connection setup success rate is normal after 24th Jan
when on air.
2. E-RAB connection setup. As below Graph 2, no any E-RAB Establish attempt happened.
Graph 1 Graph 2
Case Share 2 : Attach Failure due to missing User Plane Peer IP and MME IP
3. Check CN related parameter Local tracking area ID/CN Operator ID/Tracking area code, as Graph 3. These
parameters had been existing in live network. And another same parameter sites RRC/E-RAB setup SR was
normal, as Graph 4.
Graph 3 Graph 4
Case Share 2 : Attach Failure due to missing User Plane Peer IP and MME IP
4. DT test. Authentication and Security Mode can be made successfully. But Attach was rejected, cause was
unknown-or-missing-APN(27).
Case Share 2 : Attach Failure due to missing User Plane Peer IP and MME IP
4. Compare BSS parameter between issue site and normal site. Found issue site was lack of User Plane Peer IP.
5. BSS team assisted to check USERPLANEPEER and IPRT configuration. This site was not configured any SPWG IP
and MME IP. After add them at 1st Feb, LTE site access KPI recovered.
CSFB & Fast Return Analysis
CSFB & Fast Return KPI Analysis Root Cause checklist Workflow
Category Check List
Network available check
Start Operation Log Check
The whole Network KPI Degrade Transmission check
Alarm check
Local Event check
Phenomena analyse
Transmission check
Proposal Operation Log Check
Alarm check
TOP Cells Degrade Load balance strategy Parameter Check
Yes
Whole network KPI UL Interference Check
Degrade A License Check
Local Event check
Others TOP UE or TOP Subscriber
No
Yes
Formula
TOP Cell degradation
B CSFB SSR (%)=L.CSFB.E2W/L.CSFB.PrepSucc*100
No
Remark:
No
Network Level KPI Degradation judgment Reference
Problem Solved C If remove top 20% low CSFB and high Attempts failures but after the KPI
re-calculation still not reach the target
TOP Cell KPI Degradation judgment Reference
Yes
If remove top 20% low CSFB SR and high Attempts failures and after the
KPI re-calculation can reach the target
End TOP User or Subscriber
If after check everything but still can not solve problem, check top IMSI
from PCHR, and request for customer to add blacklist of top cell
For Optimization Proposal , Kindly see next slide
CSFB & Fast Return Feature and Parameters
Fast Return Parameter:
Related Switch :
LTE Parameter MML Command Recommend value Comments
Result:
This CSFB failure is contribute by weak coverage and UL interference, after RF optimization and improve the cell reselection threshold to 2G/3G,
CSFB failure issue solved.
Case Share: Fast Return Failure
Description:
Fast Return switch already open, Not trigger Fast Return function after the CSFB finished.
Founding:
Fast Return is controlled not only by Fast return switch but also controlled by idle U2L reselection parameter.
1: LTE Neighbor Frequent priority is low than 3G;
2: the IUPS signaling is after CSFB finished, need to open the enhanced fast return Reserved switch.
Solution:
Open the enhanced switch RESERVED_SWITCH_3_BIT12, modified the LTE Idle UCELLNFREQPRIOINFO higher than UMTS, after CSFB finished,
trigger fast return to LTE.
Inter-RAT HO KPI Analysis
IRAT HO KPI Analysis Root Cause Flow
Start
Proposal
External Neighbour
IRAT HO SR in Prepare Yes Yes
Phase inconsistency A
Issue
No No
Yes
IRAT HO SR in Execution Phase Parameter Unreasonable issue B
No
Yes
External Neighbour alarm issue c
Yes
Radio condition
D
No
Yes
Parameter
E
End
IRAT HO KPI Analyze Work Flow Proposal
A Solution For External Neighbour inconsistency Issue
1. Need to check 3G External Neighbors configuration much be correct.
( 3G Neighbor Parameter include: RncId, CellId, Mcc, Mnc, UtranDlArfcn, Rac, PScrambCode, Lac etc.)
2. Activate Inter RAT ANR Feature, open auto add and delete UMTS neighbor switch, and set delete UMTS neighbor HO time threshold.
(Switch include: UtranEventAnrSwitch-1&UtranAutoNrtDeleteSwitch-1, NCellRankingSwitch=UTRAN_SWITCH-1)
(Delete Threshold include: StatisticPeriodForNRTDel=1440, StatisticNumForNRTDel= 50, UtranNcellDelPunNum=50,
NcellHoStatNum=10, UtranNcellHoForNRTDelThd=10)
UTRAN_DELREDUNDANCENCELL 0 1
UTRAN_DELERRORNCELL 0 1
UtranEventAnrMode BASED_NCL NOT_BASED_NCL
StatisticPeriodForNRTDel 10080 1440
MOD ANR
StatisticNumForNRTDel 200 50
UtranNcellDelPunNum 1 50
NcellHoStatNum 200 10
LTE
UtranNcellHoForNRTDelThd 0 10
PS_HO@CsfbHoPolicyCfg 1 0
PS_HO@IdleModeCsfbHoPolicyCfg 1 0
CCO_HO@CsfbHoPolicyCfg 1 0
REDIRECTION@CsfbHoPolicyCfg 1 1
REDIRECTION@IdleModeCsfbHoPolicyCfg 1 1
Attachment 3 : Related Parameters for Reference
Recommend
Network Level LTE Parameter MML Command Default value
value
PERFENH_SYSHO_IN_FAIL_RETRY_SWI
Cell TCH@CellConnAlgoSwitch1 MOD UCELLCONNALGOPARA 0 1
UMTS
PERFENH_SYSHO_IN_BE_RATE_DOWN_
RNC SET UCORRMPARA 0 1
SWITCH@PerfEnhanceSwitch4
Attachment : Related Counters for Reference
Network Counter Comment
99 100
Degradation of IRAT HO after 7 200
Fail
97 Activated PS HO Switch
4 97 100
Finding : 96 3
96
Activated PS HO Switch
2 50
High number of IRAT Fail at worst 95
1 95
value -24, its mean IRAT HO can perform Sum of IRAT HO Fail Average of Inter-RAT Handover Execution Success Rate(L2W) Sum of LIRATHOE2WExecAttOut (None) Average of Inter-RAT Handover Execution Success Rate(L2W)