TDLTE关键过程信令流程解析精.docx
- 文档编号:7257589
- 上传时间:2023-01-22
- 格式:DOCX
- 页数:44
- 大小:80.78KB
TDLTE关键过程信令流程解析精.docx
《TDLTE关键过程信令流程解析精.docx》由会员分享,可在线阅读,更多相关《TDLTE关键过程信令流程解析精.docx(44页珍藏版)》请在冰豆网上搜索。
TDLTE关键过程信令流程解析精
TD-LTE关键过程信令流程解析
1.目的
该文档通过对TD-LTE信令流程的说明和解析,向读者详细描述了TD-LTE信令流程和信令解码,有助于帮助读者在读懂信令的基础上,更好地分析信令,分析问题。
2.关键过程信令流程解析
E-UTRAN初始附着过程
1、流程概述——对于过程进行整体描述
附着过程就是UE向网络注册的过程。
注册成功,UE和MME从都会进入EMM注册状态。
网络根据用户UE当前状态和签约的信息为用户提供“一直在线”的IP服务连接。
附着过程结束,在MME里面为UE建立起一个上下文,在UE和PGW间为UE建立起一条默认EPS承载。
UE刚开机时,先进行物理下行同步,搜索测量进行小区选择,选择到一个suitable或者acceptable小区后,驻留并进行附着过程。
附着流程图如下:
Attach流程图
说明:
1步骤1~5会建立RRC连接,步骤6、9会建立S1连接,完成这些过程即标志着
NASsignallingconnection建立完成。
2消息7的说明:
UE刚开机第一次attach,使用的IMSI,无Identity过程;后续,
如果有有效的GUTI,使用GUTIattach,核心网才会发起Identity过程(为上下行直传消息。
3消息10~12的说明:
如果消息9带了UERadioCapabilityIE,则eNB不会发送
UECapabilityEnquiry消息给UE,即没有10~12过程;否则会发送,UE上报无线能力信息后,eNB再发UECapabilityInfoIndication,给核心网上报UE的无线能力信息。
为了减少空口开销,在IDLE下MME会保存UERadioCapability信息,在
INITIALCONTEXTSETUPREQUEST消息会带给eNB,除非UE在执行attach或
者"firstTAUfollowingGERAN/UTRANAttach"or"UEradiocapabilityupdate"TAU
过程(也就是这些过程MME不会带UERadioCapability信息给eNB,并会把本地
保存的UERadioCapability信息删除,eNB会问UE要能力信息,并报给MME。
注:
"UEradiocapabilityupdate"TAUisonlysupportedforchangesofGERANand
UTRANradiocapabilitiesinECM-IDLE.。
在CONNECTED下,eNB会一直保存UERadioCapability信息。
UE的E_UTRAN无线能力信息如果发生改变,需要先detach,再attach。
4发起UE上下文释放(即21~25的条件:
eNodeB-initiatedwithcausee.g.O&MIntervention,UnspecifiedFailure,UserInactivity,RepeatedRRCsignallingIntegrityCheckFailure,ReleaseduetoUEgeneratedsignallingconnectionrelease,etc.;orMME-initiatedwithcausee.g.authenticationfailure,detach,etc.
5eNB收到msg3以后,DCM给USM配置SRB1,配置完后发送msg4给UE;eNB
在发送RRCConnectionReconfiguration前,DCM先给USM配置DRB/SRB2等信息,配置完后发送RRCConnectionReconfiguration给UE,收到RRCConnectionReconfigurationComplete后,控制面再通知用户面资源可用。
6消息13~15的说明:
eNB发送完消息13,并不需要等收到消息14,就直接发送消
息15。
7如果发起IMSIattach时,UE的IMSI与另外一个UE的IMSI重复,并且其他UE
已经attach,则核心网会释放先前的UE。
如果IMSI中的MNC与核心网配置的不一致,则核心网会回复attachreject。
8消息9的说明:
该消息为MME向eNB发起的初始上下文建立请求,请求eNB建
立承载资源,同时带安全上下文,可能带用户无线能力、切换限制列表等参数。
UE的
安全能力参数是通过attachrequest消息带给核心网的,核心网再通过该消息送给eNB。
UE的网络能力(安全能力信息改变的话,需要发起TAU。
2、消息解析——对于关键参数进行解析
(1MasterInformationBlock(主信息块
RRC:
MasterInformationBlock
Messagetype:
BCCH_BCH
Direction:
Downlink
FrameNo:
1020
SubframeNo:
4
ComputerTimestamp:
17:
23:
26.843
BCCH-BCH-Message
message
dl-Bandwidth:
n100(下行带宽,目前配置为100PRB,20MHz带宽
phich-Config
phich-Duration:
normal(PHICH持续时间
phich-Resource:
half(PHICH资源大小,Ng配置为1/2即可保证PHICH资源够用,一般系统内的资源占用率不会到100%,上行单次传输平均占用的资源块数也可能比较大,此时一个PHICH组内实际占用的资源数会比较小,能够保证传输性能。
systemFrameNumber:
0xFF
spare:
0x0000
(2SysInfoType1(系统信息块1
RRC:
SysInfoType1
Messagetype:
BCCH_SCH
Direction:
Downlink
FrameNo:
1022
SubframeNo:
7
ComputerTimestamp:
17:
23:
26.843
BCCH-DL-SCH-Message
message
c1
systemInformationBlockType1
cellAccessRelatedInfo
plmn-IdentityList
PLMN-IdentityInfo
plmn-Identity
mcc
MCC-MNC-Digit:
4
MCC-MNC-Digit:
6
MCC-MNC-Digit:
0
mnc
MCC-MNC-Digit:
0
MCC-MNC-Digit:
0
cellReservedForOperatorUse:
notReserved
trackingAreaCode:
0x0200(小区所属跟踪区的ID
cellIdentity:
0x00099020
cellBarred:
notBarred
intraFreqReselection:
allowed
csg-Indication:
false
cellSelectionInfo
q-RxLevMin:
-60(小区重选最小信道要求,目前配置为-60dBmp-Max:
23(UE最大发射功率,目前配置为23dBm
freqBandIndicator:
38(E-UTRA工作频段,38指2570Mhz-2620Mhz
schedulingInfoList
SchedulingInfo
si-Periodicity:
rf32
sib-MappingInfo
sibType3
sibType4
tdd-Config
subframeAssignment:
sa1(上下行子帧配置,sa1指2U2D
specialSubframePatterns:
ssp7(特殊子帧配置,ssp7指10:
2:
2si-WindowLength:
ms10
systemInfoValueTag:
0
(3SysInfo(系统信息块
RRC:
SysInfo
Messagetype:
BCCH_SCH
Direction:
Downlink
FrameNo:
0
SubframeNo:
5
ComputerTimestamp:
17:
23:
26.843
BCCH-DL-SCH-Message
message
c1
systemInformation
criticalExtensions
systemInformation-r8
sib-TypeAndInfo
sib2
radioResourceConfigCommon
rach-ConfigCommon
preambleInfo
numberOfRA-Preambles:
n48(竞争前导码数量,预留48个Preamble码用于竞争随机接入
preamblesGroupAConfig
sizeOfRA-PreamblesGroupA:
n48
messageSizeGroupA:
b56
messagePowerOffsetGroupB:
dB8
powerRampingParameters
powerRampingStep:
dB2
preambleInitialReceivedTargetPower:
dBm-106
ra-SupervisionInfo
preambleTransMax:
n4
ra-ResponseWindowSize:
sf10
mac-ContentionResolutionTimer:
sf48
maxHARQ-Msg3Tx:
4
bcch-Config
modificationPeriodCoeff:
n4
pcch-Config
defaultPagingCycle:
rf64
nB:
halfT
prach-Config
rootSequenceIndex:
24(前导码根序列逻辑索引,当采用PreambleFormat0~3时,ZC根序列的选择与当前小区是否为高速小区有关,当采用PreambleFormat0~3且为高速小区时,RootSeqIndex的取值与Ncs有关,Preamble格式影响RootSeqIndex的取值范围以及选择原则
prach-ConfigInfo
prach-ConfigIndex:
3
highSpeedFlag:
false
zeroCorrelationZoneConfig:
3
prach-FreqOffset:
17
pdsch-ConfigCommon
referenceSignalPower:
15(小区参考信号功率,15对应全带宽等效总功率45.79dBm
p-b:
1(无CRS的OFDM符号上的数据RE与有CRS的OFDM符号上数据RE的能量之比,一般取1,即功率比为1:
1
pusch-ConfigCommon
pusch-ConfigBasic
n-SB:
4
hoppingMode:
interSubFrame
pusch-HoppingOffset:
33
enable64QAM:
true
ul-ReferenceSignalsPUSCH
groupHoppingEnabled:
false
groupAssignmentPUSCH:
0
sequenceHoppingEnabled:
false
cyclicShift:
0
pucch-ConfigCommon
deltaPUCCH-Shift:
ds2
nRB-CQI:
2
nCS-AN:
0
n1PUCCH-AN:
36
soundingRS-UL-ConfigCommon
setup
srs-BandwidthConfig:
bw0
srs-SubframeConfig:
sc0
ackNackSRS-SimultaneousTransmission:
true
srs-MaxUpPts:
true
uplinkPowerControlCommon
p0-NominalPUSCH:
-85(持续调度期望接收功率,根据需要随时修改
alpha:
al1
p0-NominalPUCCH:
-112(PUCCH期望功率,根据需要随时修改
deltaFList-PUCCH
deltaF-PUCCH-Format1:
deltaF0
deltaF-PUCCH-Format1b:
deltaF1
deltaF-PUCCH-Format2:
deltaF0
deltaF-PUCCH-Format2a:
deltaF2
deltaF-PUCCH-Format2b:
deltaF2
deltaPreambleMsg3:
4
ul-CyclicPrefixLength:
len1
ue-TimersAndConstants
t300:
ms2000(T300定时器时长,当UE发送RRCCONNECTIONREQUEST消息后启动T300定时器,当收到RRCCONNECTIONSETUP消息后停止T300定时器。
一旦超时,若RRCCONNECTIONREQUEST消息重发次数小于常量N300则重发RRCCONNECTIONREQUEST,否则进入空闲模式。
T300的设置应结合UE、UTRAN处理时延以及传播时延考虑,T300设置越大,UE等待时间越长。
N300设置越大,RRC连接成功建立的可能性越高,同时用于RRC建立的时间也可能越长,有可能出现某个UE反复尝试接入和发送连接建立请求,而对其它用户造成较强干扰的情况。
t301:
ms600(用户摘机定时器
t310:
ms2000
n310:
n20
t311:
ms1000
n311:
n1
freqInfo
additionalSpectrumEmission:
1
timeAlignmentTimerCommon:
infinity
sib3
cellReselectionInfoCommon
q-Hyst:
dB2
cellReselectionServingFreqInfo
s-NonIntraSearch:
2
threshServingLow:
0
cellReselectionPriority:
3
intraFreqCellReselectionInfo
q-RxLevMin:
-53
p-Max:
23(UE最大发射功率,目前配置为23dBm
s-IntraSearch:
3
allowedMeasBandwidth:
mbw6
presenceAntennaPort1:
true
neighCellConfig:
0x40
t-ReselectionEUTRA:
3
sib4
intraFreqNeighCellList
IntraFreqNeighCellInfo
physCellId:
0
q-OffsetCell:
dB0
IntraFreqNeighCellInfo
physCellId:
1
q-OffsetCell:
dB0
IntraFreqNeighCellInfo
physCellId:
4
q-OffsetCell:
dB0
IntraFreqNeighCellInfo
physCellId:
5
q-OffsetCell:
dB0
(4AttachRequest
Messagetype:
EPSMM
Direction:
Uplink
ComputerTimestamp:
17:
23:
02.843
FrameNo:
674
SubframeNo:
6
AttachRequest
Securityheadertype:
(0PlainNASmessage,notsecurityprotected
protocol_discriminator:
EPSMobilityManagement
NASEPSMobilityManagementMessageType:
(0x41Attachrequest
Typeofsecuritycontextflag(TSC:
(0Nativesecuritycontext
NASkeysetidentifier:
(0
Sparebit(s:
0
EPSattachtype:
(1EPSattach
EPSmobileidentity-OldGUTIorIMSI
Length:
11octets
odd/evenindic:
0
Typeofidentity:
(6GUTI
MobileCountryCode(MCC:
(460China(People'sRepublicof(移动国家码
MobileNetworkCode(MNC:
(00ChinaMobile(移动网络码
MMEGroupID:
32768
MMECode:
50
M-TMSI:
0x203f09(临时移动用户识别
UEnetworkcapability
Length:
4octets
EEA0:
(1Support
128-EEA1:
(1Support
128-EEA2:
(1Support
EEA3:
(0Notsupport
EEA4:
(0Notsupport
EEA5:
(0Notsupport
EEA6:
(0Notsupport
EEA7:
(0Notsupport
EIA0:
(1Support
128-EIA1:
(1Support
128-EIA2:
(1Support
EIA3:
(0Notsupport
EIA4:
(0Notsupport
EIA5:
(0Notsupport
EIA6:
(0Notsupport
EIA7:
(0Notsupport
UEA0:
(0Notsupport
UEA1:
(0Notsupport
UEA2:
(0Notsupport
UEA3:
(0Notsupport
UEA4:
(0Notsupport
UEA5:
(0Notsupport
UEA6:
(0Notsupport
UEA7:
(0Notsupport
UCS2support(UCS2:
(0Notsupport
UMTSintegrityalgorithmUIA1:
(0Notsupport
UMTSintegrityalgorithmUIA2:
(0Notsupport
UMTSintegrityalgorithmUIA3:
(0Notsupport
UMTSintegrityalgorithmUIA4:
(0Notsupport
UMTSintegrityalgorithmUIA5:
(0Notsupport
UMTSintegrityalgorithmUIA6:
(0Notsupport
UMTSintegrityalgorithmUIA7:
(0Notsupport
ESMmessagecontainer
Length:
29octets
ESMmessagecontainercontents:
21d01127178080211011010816000083600000a0
0000....=EPSbeareridentity:
0
....0010=protocol_discriminator:
(2EPSsessionmanagement
messages
Proceduretransactionidentity:
1
NASEPSsessionmanagementmessages:
(0xd0PDNconnectivityrequest
PDNtype:
(1IPv4
Requesttype:
(1Initialrequest
ProtocolConfigurationOptions
ElementID:
39
Length:
23octets
Ext:
1
Configurationprotocol:
(0PPP
Protocolinformation:
[0]:
ProtocolID:
IPCP(Hex8021
Contentslength:
16octets
Protocalcontents:
(Hex01010010810600000000830600000000
[1]:
ProtocolID:
(HexA
Contentslength:
0octets
Protocalcontents:
(Hex
Trackingareaidentity-LastvisitedregisteredTAI
ElementID:
82
MobileCountryCode(MCC:
(460China(People'sRepublicof
MobileNetworkCode(MNC:
(00ChinaMobile
Trackingareacode(TAC:
0x200
(5RRCConnectionRequest(建立一个RRC连接
RRC:
RRCConnectionRequest
Messagetype:
CCCH_UL
Direction:
Uplink
FrameNo:
675
SubframeNo:
9
ComputerTimestamp:
17:
23:
02.843
UL-CCCH-Message
message
c1
rrcConnectionRequest
criticalExtensions
rrcConnectionRequest-r8
ue-Identity(初始UE标识
randomValue:
0x397737492F
establishmentCause:
mo-Signalling(建立原因
spare:
0x00
(6RRCConnectionSetup(建立一个SRB1
RC:
RRCConnectionSetup
Messagetype:
CCCH_DL
Direction:
Downlink
FrameNo:
680
SubframeNo:
2
ComputerTimestamp:
17:
23:
02.953
DL-CCCH-Message
message
c1
rrcConnectionSetup
rrc-TransactionIdentifier:
0(RRC操作标识
criticalExtensions
c1
r
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- TDLTE 关键 过程 流程 解析