您好,欢迎访问三七文档
当前位置:首页 > 商业/管理/HR > 项目/工程管理 > 释放流程及异常原因分析V2
R18G65B145R0G201B255R104G113B122R216G217B218R168G187B192Coreandbackgroundcolors:1©NokiaSolutionsandNetworks2014释放流程及异常释放原因分析2016-05张恒R18G65B145R0G201B255R104G113B122R216G217B218R168G187B192Coreandbackgroundcolors:2©NokiaSolutionsandNetworks2015Changeinformationclassificationinfooter概述主要内容说明本次主要讨论的内容:LTE业务释放类型及相应信令流程的详解;相关的counter触发定义,以及异常问题分析;通过对这些内容的梳理和讨论,能够了解LTE释放的理论知识,并且在日常KPI和Log分析方面,提供帮助。R18G65B145R0G201B255R104G113B122R216G217B218R168G187B192Coreandbackgroundcolors:3©NokiaSolutionsandNetworks2015释放流程及异常释放原因分析主要内容Changeinformationclassificationinfooter-业务承载类型及业务建立过程-业务释放类型及相应流程、原因•E-RABrelease•UEcontextrelease•RRCconnectionrelease-异常释放的触发情景详解•UEinitiateddrop•eNBinitiateddrop-异常释放relatedCounterTriggers-Network/FieldKPI及Drops分析-SummaryR18G65B145R0G201B255R104G113B122R216G217B218R168G187B192Coreandbackgroundcolors:4©NokiaSolutionsandNetworks2015Changeinformationclassificationinfooter业务承载类型LTE业务承载类型LTE的业务承载类型分为默认承载、专用承载两种:默认承载:UE开机时获得承载,一定是MME发起的业务,优先级特别低,NonGBR;专用承载:一定是由PGW触发建立的;一个UE可以有不同的专用承载;GTPvariant:EPSbearerterminationinPGWSRB与默认、专用承载关系R18G65B145R0G201B255R104G113B122R216G217B218R168G187B192Coreandbackgroundcolors:5©NokiaSolutionsandNetworks2015Changeinformationclassificationinfooter业务承载类型无线承载分类SRB–SignallingRadioBearers(SRBs)的定义是,仅用于传输RRC和NAS消息的RB(RadioBearer);DRB–DataRadioBearer,用于传输业务数据的无线承载;与S1-U承载共同组成E-RAB.分为UM、AM两种;R18G65B145R0G201B255R104G113B122R216G217B218R168G187B192Coreandbackgroundcolors:6©NokiaSolutionsandNetworks2015Changeinformationclassificationinfooter业务承载类型UEcontext及E-RABE-RAB–UE至SGW之间的承载,E-RAB是指用户平面的承载,由S1-U承载和DRB(DataRadioBearer,数据无线承载)串联而成,进入LTE系统的业务数据主要通过E-RAB进行传输。因此对于LTE,业务管理主要是在E-RAB层次上进行的。–一个UE可以有多个E-RAB,目前最多支持8个EPS承载(5个AMDRB,3个UMDRB).–在应用上,E-RAB常出现于性能指标的统计中,例如:E-RAB建立成功率。E-RAB建立成功指eNodeB成功为UE分配了通信通道的无线资源和用户面的无线承载,所以这个指标反映了eNodeB或小区接纳业务的能力,可以用来考虑系统负荷情况。R18G65B145R0G201B255R104G113B122R216G217B218R168G187B192Coreandbackgroundcolors:7©NokiaSolutionsandNetworks2015Changeinformationclassificationinfooter业务承载类型UEcontext及E-RABUEcontext–IncludingE-RABcontext,securitycontext,roamingrestriction,UES1signallingconnectionID(s),etc.intheeNB.在源eNB的UE上下文中还包含了与漫游和接入限制有关的信息;–InitialUEcontext只能由MME发起,一个UE只有一个UEcontext;–一个eNBUEcontext是eNB内和一个处于激活状态的UE相关联的一个信息块。这块信息是为了维持E-UTRAN提供给这个激活态UE的服务所必须的信息;–eNBUEcontext是在UE迁移到激活状态之后开始建立的;或者,eNBUEcontext是在切换目标eNB完成切换资源分配(切换准备阶段)之后开始建立的。RRCconnection层三信令连接,UE保持非IDLE的必须连接,一个UE只有一个RRCconnection,一旦连接释放,UE所有业务释放,并进入RRC_IDLE态;R18G65B145R0G201B255R104G113B122R216G217B218R168G187B192Coreandbackgroundcolors:8©NokiaSolutionsandNetworks2015ChangeinformationclassificationinfooterLTE完整业务流程默认承载建立信令流程(Attach)UEeNBMMES1AP:INITIALCONTEXTSETUPREQUEST+EMMATT_ACC+ESMACT_DEF_BEAR_REQS1AP:INITIALCONTEXTSETUPRESPONSERRC:RRCConnectionReconfiguration+EMMATT_ACC+ESMACT_DEF_BEAR_REQDRBandSRB2ConfigurationRRC:RRCConnectionReconfigurationCompleteNASSecurityEstablishment(Authentication+NASsecuritystart)RRC:UECapabilityEnquiryRRC:UECapabilityInformationUEradiocapabilitiesavailableàDRBcanbeestablishedS1AP:UECAPABILITYINFOINDICATIONPRACHRANDOMACCESSPRACHRANDOMACCESSRESPONSEPUSCH(Msg3)RRC:ConnectionRequestrandomaccessprocedureRRC:ConnectionSetupRRC:ConnectionSetupComplete+EMMATT_REQ+ESMPDNCONN_REQS1AP:INITIALUEMESSAGE+EMMATT_REQ+ESMPDNCONN_REQRRC:SecurityModeCommandRRC:SecurityCommandCompleteRRC:ULNASINFOTRANSFER(EMMATT_COMPLETE+ESMACT_DEF_BEAR_SUCCS1AP:ULNASTRANSPORT(EMMATT_COMPLETE+ESMACT_DEF_BEAR_SUCC)Steps:1.RandomAccess2.InitialNASmsg3.NASsecurity4.S1initsetup5.RRCsec+UEcap6.SRB2/DRBsetup7.NASreplyR18G65B145R0G201B255R104G113B122R216G217B218R168G187B192Coreandbackgroundcolors:9©NokiaSolutionsandNetworks2015ChangeinformationclassificationinfooterLTE完整业务流程RA及RRC连接建立流程SRB0:RRCconnectionrequest、RRCconnectionsetup(消息中包含SRB1建立的相关信息);SRB1:RRCconnectionsetupcomplete;R18G65B145R0G201B255R104G113B122R216G217B218R168G187B192Coreandbackgroundcolors:10©NokiaSolutionsandNetworks2015ChangeinformationclassificationinfooterLTE完整业务流程专用承载建立流程DedicatedBearerEstablishment:E-RAB建立UEeNBMMEAttachandDefaultBearerActivationTriggeringofDedicatedBeareractivationP-GWCreateBearerS1AP:E-RABSETUP+ESMACTIVATEDEDICATEDBEARERREQUESTtriggeringofDedicatedBeareractivationRRC:ULNASINFOTRANSFER+ESMBEARERRESOURCEALLOCATIONREQUESTS1AP:ULNASTRANSPORT(ESMBEARERRESOURCEALLOCATIONREQUEST)optionalprocedure,P-GWmayalsotriggerdedicatedbearercreationwithoutUErequestingitRRC:RRCConnectionReconfiguration+ESMACTIVATEDEDICATEDBEARERREQUESTDRBConfigurationRRC:RRCConnectionReconfigurationCompleteS1AP:ULNASTRANSPORT(ESMACTIVATEDEDICATEDBEARERREQUESTACCEPT)RRC:ULNASINFOTRANSFER+ESMACTIVATEDEDICATEDBEARERREQUESTACCEPTGTPv2:BearerResourceCommandR18G65B145R0G201B255R104G113B122R216G217B218R168G187B192Coreandbackgroundcolors:11©NokiaSolutionsandNetworks2015释放流程及异常释放原因分析主要内容Changeinformationclassificationinfooter-业务承载类型及业务建立过程-业务释放类型及相应流程、原因•E-RABrelease•UEcontextrelease•RRCconnectionrelease-Abnormalrelease的触发情景详解•UEinitiateddrop•eNBinitiateddrop-异常释放relatedCounterTriggers-Network/FieldKPI及Drops分析-SummaryR18G65B145R0G
本文标题:释放流程及异常原因分析V2
链接地址:https://www.777doc.com/doc-657348 .html