中国联通CSFB测试的主要流程信令.docx
- 文档编号:22809815
- 上传时间:2023-04-28
- 格式:DOCX
- 页数:21
- 大小:1.09MB
中国联通CSFB测试的主要流程信令.docx
《中国联通CSFB测试的主要流程信令.docx》由会员分享,可在线阅读,更多相关《中国联通CSFB测试的主要流程信令.docx(21页珍藏版)》请在冰豆网上搜索。
中国联通CSFB测试的主要流程信令
中国联通FDD_LTE的CSFB测试和分析
一、前言
本文主要针对联通FDD-LTE网络,使用华星FLY6.0进行CSFB测试和分析;CSFB涉与4G侧(LTE)、3G侧(WCDMA)和MSC核心网侧三方的配合。
以下主要是针对测试和事件消息流程进行分析和说明。
二、CSFB测试流程
CSFB测试过程主要是主叫4G手机、被叫4G手机分别驻留LTE网络中,连接FLY6.0测试软件,进行主叫4G手机拨打被叫4G手机,主叫4G手机和被叫4G手机分别回落至WCDMA网络进行通话的过程。
CSFB测试流程主要分为测试准备、测试过程和测数据统计三个部分:
步骤
工作项目
备注
测试准备
1、测试手机是否支持FDD-LTE和3G双模;
使用中兴Q801U测试手机,支持FDDLTE和WCDMA
2、测试SIM卡是否具备4G和3G属性
测试卡4G/3G测试都具备;部分老3G卡需增加4G属性;删除4G属性的卡会出现“AU鉴权失败,无法驻留4G网络”现象
3、测试手机是否连接FLY6.0测试软件,并进行记录
每个小区都需要记录CSFB测试log
3、测试手机是否开启"LTE和WCDMA"双模模式,
手机“网络模式”中
4、手机选择双模后,是否稳定驻留4G;
5、无线环境是否稳定?
(RSRP>-100dBm,SINR>0dB)
6、从空口消息观察TAC配置,检查TAC和LAC的对应关系是否正常;
测试过程
1、主叫手机和被叫手机是否稳定驻留在4G网络;
2、主叫4G手机拨打被叫4G手机,是否拨通?
进行重复多次尝试;
1、若是未拨通,是否听见回铃音,判断主叫信令是否正常;2、若主叫信令正常,判断被叫寻呼消息和CSFB信令是否正常
3、从主被叫的KPI统计中观测CSFB是否统计正常?
4、从主被叫的CSFB信令流程来看,主被叫的CSFB信令流程是否正常?
一定要查看主被叫的CSFB的起呼、4G网络RRC释放、4G重选至3G、3G的RRC\RAB\Alerting的完整起呼流程。
验证完全完整后,才算合格。
数据统计
1、单站报告中CSFB成功率统计
2、CSFB的log记录备份
3、若存在测试不成功现象,可初步按照第4节指导进行初步分析原因,待调整后复测
分析原因一定要细分类,描述清晰,复测一定要确定故障消除
三、正常CSFB信令流程
3.1.主叫主要流程
当开机做主叫时,UE首先在FDD_LTE注册(attach),完成注册后进行拨号;
通过E_nodeB上发CSFB请求;其主要流程如下:
开机注册(attach)
注册请求消息AttachRequest(层三消息RRCConnectionRequest)由UE发出(消息属NAS层),请求中包括UE注册的小区,UE支持的加密算法和方式;联合注册的4G(TAC)和3G(LAC/RAC)与ClassMark;
Attachrequest
MORE:
0
LENGTH:
123
LENGTH:
123
LOG_CODE:
B0ED
timeStamp:
16:
20:
28.016
LTENASEMMplainOTAoutgoingmsg
LOG_VERSION:
1
STD_VERSION:
9
STD_VERSION_MAJOR:
5
STD_VERSION_MINOR:
0
NAS:
Attachrequest
SecurityHeaderType:
0
ProtocolDiscriminator:
7
Message_Types:
65
NASkeysetidentifier
TSC:
0-nativesecuritycontext
NASkeysetidentifier:
1
EPSattachtype
EPSattachtypevalue:
2-combinedEPS/IMSIattach
EPSmobileidentity
LengthofEPSmobileidentitycontents:
11
odd_evenindic:
0-evennumberofidentitydigitsandalsowhentheGUTIisused
Typeofidentity:
6-GUTI
MCC:
460
MNC:
01
MMEGroupID:
9A00
MMECode:
206
M_TMSI:
9A00CC345E25
UEnetworkcapability
EEA0:
1-supporte
128_EEA1:
1-supported
128_EEA2:
1-supported
EEA3:
0-notsupported
EEA4:
0-notsupported
EEA5:
0-notsupported
EEA6:
0-notsupported
EEA7:
0-notsupported
EIA0:
0-notsupported
128_EIA1:
1-supported
128_EIA2:
1-supported
EIA3:
0-notsupported
EIA4:
0-notsupported
EIA5:
0-notsupported
EIA6:
0-notsupported
EIA7:
0-notsupported
UEA0:
1-supported
UEA1:
1-supported
UEA2:
0-notsupported
UEA3:
0-notsupported
UEA4:
0-notsupported
UEA5:
0-notsupported
UEA6:
0-notsupported
UEA7:
0-notsupported
UCS2:
0-notsupported
UIA1:
1-supported
UIA2:
0-notsupported
UIA3:
0-notsupported
UIA4:
0-notsupported
UIA5:
0-notsupported
UIA6:
0-notsupported
UIA7:
0-notsupported
ACCCSFB:
1-supported
LPP:
0-notsupported
LCS:
0-notsupported
_1xSRVCC:
0-notsupported
NF:
1-supported
ESMmessagecontainer
Length:
38
ESMmessagecontainercontents:
02,03,D0,31,27,20,80,80,21,10,01,00,00,10,81,06,00,00,00,00,83,06,00,00,00,00,00,0D,00,00,03,00,00,0A,00,00,10,00
PDNconnectivityrequest
SecurityHeaderType:
0
ProtocolDiscriminator:
2
Message_Types:
208
PDNtype
PDNtypevalue:
3-IPv4v6
Requesttype
Requesttypevalue:
1-initialrequest
Protocolconfigurationoptions
Length:
32
ProtocolID0x:
8021
Lengthofprotocol:
16
code:
1-Configure-Request
Identifier:
0
length:
16
Type:
129-PrimaryDNSServerIPAddress
len:
6
Type:
131-Secondary-DNS-Address
len:
6
ProtocolID0x:
0D
Lengthofprotocol:
0
Trackingareaidentity
MCC:
460
MNC:
01TAC:
37135
DRXparameter
SPLITPGCYCLECODE:
10
CNSpecificDRXcyclelengthcoefficientandDRXvalueforS1mode:
0
SPLITonCCCH:
0-isnotsupported
non-DRXtimer:
0-nonon-DRXmodeaftertransferstate
MSnetworkcapability
LengthofMSnetworkcapabilitycontents:
3
MSnetworkcapabilityvalue:
E5,C0,3E
LocationareaidentificationMCC:
460MNC:
10
Lac:
47889
Mobilestationclassmark2
Revisionlevel:
2-UsedbymobilestationssupportingR99orlaterversionsoftheprotocol
ESIND:
0-
A5/1algorithmsupported:
1-notavailable
RFPowerCapability:
reserved
PScapability:
0-notpresent
SSScreeningIndicator:
1definedinGSM04.80SMcapability:
1-MobilestationsupportsmobileterminatedpointtopointSMS
VBSnotificationreception:
0-noVBScapabilityornonotificationswanted
VGCSnotificationreception:
0-noVGCScapabilityornonotificationswanted
FCFrequencyCapability:
0-TheMSdoesnotsupporttheextensionbandG1inadditiontotheprimaryGSMband
CM3:
1-TheMSsupportsoptionsthatareindicatedinclassmark3IE
LCSVAcapability:
1
UCS2:
0-theMEhasapreferenceforthedefaultalphabetoverUCS2
SoLSA:
0-TheMEdoesnotsupportSoLSA
CMSP:
1-NetworkinitiatedMOCMconnectionrequestsupportedforatleastoneCMprotocol
A5/3algorithmsupported:
1-notavailable
A5/2algorithmsupported:
0-available
Sparehalfoctet
LengthOfSupportedCodeclist:
8
SystemIdentification:
4
LengthOfBitmapforSysID:
2
LengthOfBitmapforSysID:
60
LengthOfBitmapforSysID:
04
SystemIdentification:
0
LengthOfBitmapforSysID:
2
LengthOfBitmapforSysID:
1F
LengthOfBitmapforSysID:
02VoicedomainpreferenceandUE'susagesetting
LengthofVoicedomainpreferenceandUE'susagesettingcontents:
6
UE'susagesetting:
0-Voicecentric
UE'susagesetting:
0-CSVoiceonly
VoicedomainpreferenceandUE'susagesetting
GUTItype:
0-NativeGUTI
MSnetworkfeaturesupport
Extendedperiodictimers:
1-MSsupport注册(attach)成功
UE收到RRCConnectionSetup消息,进行注册AttachAccepet(层三消息RRCConnectionSetupComplete),成功消息中包括注册的小区MCC,MNC,MMEGroupID,MMECode与UE的M_TMSI等信息.
3.1.3UE语音业务请求(CSFBMTSTART)
UE上发Extservicerequest(NAS到EMM)消息,内容为CSfallback业务请求;
Extendedservicerequest
MORE:
0
LENGTH:
35
LENGTH:
35
LOG_CODE:
B0ED
timeStamp:
16:
20:
44.796LTENASEMMplainOTAoutgoingmsg
LOG_VERSION:
1
STD_VERSION:
9
STD_VERSION_MAJOR:
5
STD_VERSION_MINOR:
0NAS:
Extendedservicerequest
SecurityHeaderType:
0
ProtocolDiscriminator:
7
Message_Types:
76
NASkeysetidentifier
TSC:
0-nativesecuritycontext
NASkeysetidentifier:
1
Servicetype
Servicetypevalue:
mobileoriginatingCSfallbackor1xCSfallbackMobileidentity
Odd/evenindication:
0-evennumberofidentitydigitsandalsowhentheTMSI/P-TMSIorTMGIandoptionalMBMSSessionIdentityisused
Typeofidentity:
4-TMSI/P-TMSI
Identitydigits(0x):
DC345E25
EPSbearercontextstatus
length:
32
EBI:
0
3.1.4E_nodeB指标UE回落
E_nodeB在下发给UE的RRCConnectionRelease中给出重定向的目标(utra_FDD=10713)
RRCConnectionRelease
MORE:
0
LENGTH:
1993
LENGTH:
1993
LOG_CODE:
B0C0
timeStamp:
16:
20:
44.928
RRCConnectionRelease
VERSION:
7
RRC_REL:
10
RRC_REL:
113
RRC_VER:
1PHYSICAL_CELL_ID:
368(4G服务小区)
FREQ:
1650
System_Frame_Number:
34
Subframe:
8
PDU_NUM:
6
ENCODED_MSG_LEN:
1964
RRC:
DL-DCCH-Message
message
c1
rrcConnectionRelease
rrc_TransactionIdentifier=0
criticalExtensions
c1
rrcConnectionRelease_r8
releaseCause=other
redirectedCarrierInfo(重定向方向)
utra_FDD=10713
nonCriticalExtension
nonCriticalExtension
cellInfoList_r9(以下是3G邻区扰码)
utra_FDD_r9[0]physCellId_r9=201
utra_FDD_r9[1]physCellId_r9=209
utra_FDD_r9[2]physCellId_r9=233
utra_FDD_r9[3]physCellId_r9=393
utra_FDD_r9[4]physCellId_r9=11
utra_FDD_r9[5]physCellId_r9=35
utra_FDD_r9[6]physCellId_r9=448
utra_FDD_r9[7]physCellId_r9=3
3.1.5.UE在3G网络进行呼叫
UE读取3G网络系统消息,发起业务请求(CMSerciveRequest);请求中包括业务类型,UE能力和支持的加密类型等等..
CMservicerequest
MORE:
0
LENGTH:
31
LENGTH:
31
LOG_CODE:
713A
timeStamp:
16:
20:
45.832
UMTSNASSignalingMessages
Direction:
FromUE
Length:
14
ChannelType:
5
MessageType:
36
UMTSNASSignalingMessages:
CMservicerequest
CMservicetype
ServiceType:
0
Cipheringkeysequencenumber
keysequence:
1
Mobilestationclassmark
Revisionlevel:
2-UsedbymobilestationssupportingR99orlaterversionsoftheprotocol
ESIND:
1-(
A5/1algorithmsupported:
0-(available)
RFPowerCapability:
7-reserved
PScapability:
1-(present)
SSScreeningIndicator:
1(definedinGSM04.80)
SMcapability:
1-MobilestationsupportsmobileterminatedpointtopointSMS
VBSnotificationreception:
0-noVBScapabilityornonotificationswanted
VGCSnotificationreception:
0-noVGCScapabilityornonotificationswanted
0-TheMSdoesnotsupporttheextensionbandG1inadditiontotheprimaryGSMbandClassmark3(CM3):
1-TheMSsupportsoptionsthatareindicatedinclassmark3IE
LCSVAcapability:
1
UCS2:
0-theMEhasapreferenceforthedefaultalphabetoverUCS2
SoLSA:
0-TheMEdoesnotsupportSoLSA
CMSP:
1-NetworkinitiatedMOCMconnectionrequestsupportedforatleastoneCMprotocol
A5/3algorithmsupported:
1-(notavailable)
A5/2algorithmsupported:
0-(available)
Mobileidentity
Typeofidentity:
4-TMSI/P-TMSI
Odd/evenindication:
0
Identitydigits:
0x03C3239B
3.1.6.RAU和RAB建立
在3G网络进行RAU(ROUTINGAREAUPDATEREQUEST),无线承载建立请求(RadioBearerSetupComplete),为UE分配无线资源.
RadioBearerSetupComplete
MORE:
0
LENGTH:
26
LENGTH:
26
LOG_CODE:
412FtimeStamp:
16:
20:
47.026
RRC:
UL_DCCH
integrityCheckInfo
messageAuthenticationCode=32,0xB60x110x690x93rrc_MessageSequenceNumber=2
message
radioBearerSetupComplete
rrc_TransactionIdentifier=0
start_Value=20,0x000x000110xxxxcount_C_ActivationTime=208
3.1.7.振铃(Alerting)
在3G网络无线资源分配完成后,网络发振铃消息给UE
3.1.8.接通(Connect)
被叫摘机,链路
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- 中国联通 CSFB 测试 主要 流程