资源描述
EPC介绍EPC介绍?EPC关键技术介绍?EPC业务流程介绍?EPC关键技术介绍?EPC业务流程介绍EPC的标准化进展1?可行性研究阶段?2004年12月正式立项至2006年6月完成。主要是网络结构优化的可行性研究，?输出的基准协议是 3GPP TR23.882:GPPsystemarchitecture evolution(SAE):Report on technical options and conclusions 2?Stage1（需求阶段）?定义SAE的需求，2006年12月完成?输出的基准协议是 3GPP TS 22.278:Service requirements for evolution of the system 牡档瑩捥畴敲尺3?Stage2（技术实现阶段）?定义SAE的网络结构、功能实体及其相互接口。2008年6月完成?输出的基准协议包括：3GPP TS 23.401:General Packet Radio Service(GPRS)enhancements for Long Term Evolution(LTE)access“3GPPTS23.402:GPPSystemArchitecture Evolution(SAE):Architecture enhancements for 潮?偐愠捣獥敳屳4?Stage3（协议实现阶段）?定义各接口上的具体协议。2009年3月完成?当前定义的协议有：3GPP TR24.801:GPPSystemArchitecture Evolution(SAE);CT?獡数瑣屳3GPPTR29.803:GPPSystemArchitecture Evolution(SAE):CT?獡数瑣屳3GPPTR29.804:GPPSystemArchitecture Evolution(SAE):CT?獡数瑣屳EPC的标准化进展1?可行性研究阶段?2004年12月正式立3GPP标准组织与制定阶段?阶段1：需求?SA1/NGMN?阶段2：结构?EPS by SA2?LTE by RAN3?阶段3：详细实现?EPC?CT1/3/4?SA3/5/5?LTE?RAN1/2/3/4/5?SA3/5?RAN1-物理层?RAN2-L2与L3无线协议?RAN3-结构与S1/X2接口?RAN4-RF与RRM性能要求?RAN5-终端测试3GPP标准组织与制定阶段?阶段1：需求?SA1/NGMN?EPC主要协议介绍TS 23.401GPRS enhancements for E-UTRAN accessTS 23.402Architecture enhancements for non-3GPP accessesTS 23.203Policy and charging control architectureTS 23.216Single Radio Voice Call Continuity(SRVCC)TS 23.272CS fallback in Evolved Packet System(EPS)Stage 2TS 33.4013GPP SAE Security architectureTS 33.4023GPP SAE Security aspects of non-3GPP accessesEPC主要协议介绍TS 23.401GPRS enhanceEPC Architecture(3GPP Standard)SGSNHSSMMESGWPGWBSCRNCBTSNodeBeNodeBOperators ServicesPCRFControl plane trafficUser plane trafficEPCS6dS6aS3S4S10S11S1-MMES1-US5(GTP)RxGxSGiSAE-GW:SGW+PGW?HSS,MME,SAE-GW realize LTE access and interworking with Non 3GPP network.?Based on GTP mobility,S4 SGSN support legacy UTRAN&GERAN access.?Based on MIP mobility,ePDG/AAA/PCRF increase network QoS and security.Flat Architecture,Access Agnostic,Separation of control plane from user plane,and all IPePDGS2bS2a/cNon 3GPPAccess NetworkS10 xS10 x3GPPCS CoreMobility based onMIPHandover Optimization6EPC Architecture(3GPP StandarEPC主要接口介绍接口协议协议号相关实体接口功能S1-MMES1AP36.413eNodeB-MME用于传送会话管理(SM)和移动性管理(MM)信息S1-UGTPv129.060eNodeB S-GW在GW与eNodeB设备间建立隧道，传送数据包S11GTPv229.274MME S-GW采用GTP协议，在MME和GW设备间建立隧道，传送信令S3GTPv229.274MME SGSN采用GTP协议，在MME和SGSN设备间建立隧道，传送信令S4GTPv229.274S-GW SGSN采用GTP协议，在S-GW和SGSN设备间建立隧道，传送数据和信令S6aDiameter29.272MME-HSS完成用户位置信息的交换和用户签约信息的管理S10GTPv229.274MME-MME采用GTP协议，在MME设备间建立隧道，传送信令S12GTPv129.060S-GW UTRAN在UTRAN与GW之间建立隧道，传送数据S2aPMIPv6/MIPv4RFC5213P-GW Trusted Non-3GPP IP Accesse用于传送非3GPP接入的业务接入信息S5/S8GTPv229.274S-GW P-GW采用GTP协议，在GW设备间建立隧道，传送数据包EPC主要接口介绍接口协议协议号相关实体接口功能S1-MME支持3GPP接入，EPC新增网元的主要功能点MMEServing GWPDN GW?NAS信令处理?NAS信令的安全保护?3GPP内不同节点之间的移动性管理?空闲移动终端的跟踪和可达?TA List管理?PDN GW和Serving GW选择?MME和SGSN 的选择?合法监听?漫游控制?安全认证?承载管理?eNodeB 之间的切换的本地锚点?E-UTRAN 空闲模式下数据缓存以及触发网络侧Service Request 流程?合法监听?数据包路由和转发?上下行传输层数据包标记?基于用户和QCI力度的统计（用于运营商间计费）?基于用户、PDN和QCI力度的上行和下行的计费?基于用户的包过滤?合法监听?IP地址分配?上下行传输层数据包标记?PCC?non-GBR的基于AMBR的下行速率控制?GBR的基于MBR的下行速率控制?DHCPv4和DHCPv6（client、server）?上行和下行的承载绑定?上行承载绑定校验类似SGSN的控制面功能类似SGSN的用户面功能类似GGSN的功能支持3GPP接入，EPC新增网元的主要功能点MMEServiTA(Tracking Area)List 移动管理优化TA List1TA List2Idea of TA List?All the tracking areas in a Tracking Area List to which a UE is registered are served by the same serving MME.?The MME may initiate the GUTI Reallocation procedure to reallocate TAI list at any time when a signaling association is established between UE and MME.?The TAI list may also be reallocated by the Attach or the Tracking Area Update procedures?The UE doesnt need trigger TA update procedure when the UE moves in the same TA List.The Tracking Area Identity is constructed from the MCC(Mobile Country Code),MNC(Mobile Network Code)and TAC(Tracking Area Code).TA 1TA 2TA 5TA 4TA 3MMETA(Tracking Area)List 移动管理优ISR(Idle Signaling Reduction)移动管理优化TA1TA3RA3TA2TA4TA5RA1RA2TA List1TA List2ISRCombinedArea=TAList+RA?TheUEdoesntneedtriggerTAupdateprocedurewhenitmovesinthecombinedarea.ISR is not recommended to deploy in commercial phase because of its complexity and less benefits.Combined areaRA4ISR(Idle Signaling Reduction)IPv4v6 双栈（Dual Stack）EPS承载处理IPv4v6 承载的优势承载类型LTE2/3G备注IPv4YYUE获取IPv4地址转发IPv4报文Ipv6YYUE获取IPv6地址转发IPv6报文IPv4v6YY/NUE获取IPv4和v6地址和转发IPv4和v6报文?解决在1个PDP上下文中传送IPv4和IPv6地址的用户数据，减少了需要的承载上下文数量终端SGSN/MMEPDN-GW?根据终端的能力在请求建立的承载类型具备IPv6和IPv4能力请求IPv4v6IPv4终端请求IPv4IPv6终端请求IPv6?终端能力不明，请求IPv4v6?MME/SGSN根据如下条件，向PGW请求标示DualStackFlagUE是否签约DualStack，否则拒绝，否则返回给UE“subscriptionlimitation”UE是否可能切换到不支持IPv4v6网络，是则返回给UE“singleaddressbearersonly”?PGW检查如下条件，判断是否接受DualStack请求若不允许该APN使用两个IP地址，则只分配一个IP地址，并返回给UE“networkpreference”如果允许该APN使用两个IP地址，则分配IPv4地址和IPv6地址，接受请求R8网络IPv4v6 双栈承载的处理方式LTE与2/3G承载之间要求一对一映射IPv4v6双栈（Dual Stack）EPS承载处理IPvEPC网络的安全优化UEeNBeNBXuXuMMES 1-CS 1-CX 2Evolved Packet Core(EPC)E-UTRANSAE GWS1-US1-USecurity layer 1Security layer 2Security layer 1?EPS Security and UMTS Security in Common?EPS access authentication:AKA?EPS Security and UMTS Security in Difference?EPS security layers?AS（Access Stratum）securitySecurity between UE and eNB（E-UTRAN）,including RRC signaling confidentiality,RRC signaling integrity and UP(User Plane)confidentiality?NAS（Non Access Stratum）securitySecurity between UE and MME,including NAS signaling confidentiality and NAS signaling integrity?Network Domain SecuritySecurity between layer 1 and layer 2,adopting NDS/IPsec?SNOW3G?AES?ZTEsupporttheabovealgorithmsaccordingto3GPP33series.AS and NAS algorithms EPC网络的安全优化UEeNBeNBXuXuMMES1-CSEPC网络中SGSN网元类型分析SGSN为GnGp SGSNSGSN为S4 SGSN优点?对原有GPRS网络改动少?原2/3G用户的业务流程和用户感受度没有太大改变?网络结构简单?在运营商网络中只有一张网络，即EPC网络；?运营商网络内只需要一套签约数据管理：HSS；?运营商网络内只需要一套DNS：R8 DNS（EPC DNS）；?与非3GPP网络的互通不存在问题；?本网内只有一套计费体系：EPC计费；?支持ISR?利于后续新功能的扩展缺点?GnGp SGSN无法获取用户属性，无法选择 GGSN还是PGW?两套不同的签约数据管理：HLR和HSS?需要支持Pre-R8 DNS（GPRS DNS）和R8 DNS（EPC DNS）?需要支持GPRS和EPC两套计费?不支持ISR功能，在S3/S4 SGSN和MME间实现?不利于后续新功能的扩展?与非3GPP网络的互通存在问题：与非 3GPP网络互通时一个基本的要求是非优化切换时PGW地址要锚定，而PGW地址的锚定是通过移动性管理网元将 PGW通知HSS保存而达到的。但由于 Gn/Gp SGSN使用HLR，即无法通知也无法将PGW地址保存在HSS。?对原有GPRS网络改动大，需要将原 Pre-R8 SGSN升级成S3/S4 SGSN。?网络复杂，S3/S4 SGSN的加入，特别是还要考虑与原有GPRS网络互通时，网络复杂。?原2/3G用户的业务流程和用户感受度有改变?2/3G接入时的业务流程与原有流程有变动，主要体现在以下两点：?从原来的UE触发流程为主变成了网络侧流程为主，需要手机支持网络侧流程；?取消了QoS协商，在无线无法满足下发的 QoS要求时，将直接删除承载。结论?从长期发展角度看，优选采用S4 SGSN。EPC网络中SGSN网元类型分析SGSN为GnGp SGSNChoice 1:Interworking With S4 SGSNHSSGSMUTRANService ContinuityGbIu-PSS4 SGSNS4S-GWMMEP-GWInternet&Sevice networkLTES1-MMES1-US10SGiS5/S8S12S6dS6aEPCS3GTPv2UDPIPL2L1GTPv2UDPIPL2L1S4 SGSNMME/SGWS3/S4DiameterSCTP/TCPIPL2L1DiameterSCTP/TCPIPL2L1S4 SGSNHSSS6dChoice 1:Interworking WithS4 Choice 2:Interworking With Gn/Gp SGSNHSSGSMUTRANService ContinuityGbIu-PSS-GWMMEP-GWInternet&Sevice networkLTES1-MMES1-US10SGiS5/S8Gn/Gp SGSNS12Gn/GpS6aGrEPCGn/Gp?To support GERAN/UTRAN handover from GERAN/UTRAN to LTE,the SGSN must be upgraded to R8?LTE to GERAN/UTRAN supported on pre R8 SGSN?Does not support of R8 feature ISR?Many protocols:GTPv0,V1 and V2,Diameter,MAPVia Gn/Gp SGSNVia S4 SGSN?Need upgrading on SGSN?Support of R8 feature as ISR?Fewer protocols in the network:GTPv2,DiameterChoice 2:Interworking WithGn/R8 QoS 与Pre R8 QoS 差异性GERAN/UTRANEUTRANSGSNGGSNMMESAE-GWPre R8 PCNR8 EPCMusicTVStockWEBPreR8MainQoSProfile?TrafficClass?ARP、GBR、MBR?TrafficHandlingPriority?SignallingIndication?SourceStatisticsDescriptor?PacketDelayBudget?PacketLossRateR8MainQoSProfile?QoSClassIdentifier,QCI?ARP、GBR、MBR?UEAMBR?APNAMBR?2G/3G网络支持网络和UE对QoS的协商，EPS中QoS不支持协商，控制全部在网络实现，如果部署PCC则由PCRF控制，否则在P-GW静态配置QoS策略；?EPS和2G/3G的QoSProfile中包含的参数不同。EPS的QoSProfile中的参数包括：UE的QoS参数UE-MABR和APN-AMBR，以及承载层的QoS参数QCI,ARP,GBRandMBR。2G/3G网络的QoSProfile中的参数都是基于承载级别的，包括Trafficclass,MBR,GBR,ARP等；?3GPP协议已经制定了标准的R8与PreR8QoS转换机制。R8 QoS与Pre R8 QoS差异性GERAN/UTRAStandardized QCI CharacteristicsThisQCIistypicallyassociatedwithanoperatorcontrolledservice,i.e.,aservicewheretheSDFaggregatesuplink/downlinkpacketfiltersareknownatthepointintimewhentheSDFaggregateisauthorized.QCIResource TypePriorityPacket Delay BudgetPacket Error LossRate Example Services1GBR2100 ms10-2Conversational Voice24150 ms10-3Conversational Video(Live Streaming)3350 ms10-3Real Time Gaming45300 ms10-6Non-Conversational Video(Buffered Streaming)5Non-GBR1100 ms10-6IMS Signalling66300 ms10-6Video(Buffered Streaming)TCP-based(e.g.,www,e-mail,chat,ftp,p2p file sharing,progressive video,etc.)77100 ms10-3Voice,Video(Live Streaming)Interactive Gaming88300 ms10-6Video(Buffered Streaming)TCP-based(e.g.,www,e-mail,chat,ftp,p2p file sharing,progressive video,etc.)99Standardized QCI CharacteristiMGCF/MGWSCC ASIMSCSCF多种LTE语音业务解决方案EPCPSTN/PLMNRAN/GERANMSCSMGWMMESAE-PGWCSINTRENETSGseNodeBEPCPSTN/PLMNRAN/GERANMSCSMGWMMESAE-PGWCSINTRENETSveNodeBEPCPSTN/PLMNRAN/GERANMSCMMESAE-PGWCSINTRENETeNodeBCSFB-UE speech fall back to 2/3G,No VoIP on LTE?UE发起MO和接收MT呼叫时，需首先切换回CS无线网络。?适用于 2/3G电路域与LTE无线网络重叠部署的场景。?需要升级所有与LTE有重叠无线覆盖区域的VMSC，以支持类似Gs接口的SGs接口联合位置更新、寻呼、短消息等功能。?网络结构简单，不需要部署IMS。SRVCC-LTE VoIP with IMS control?基于LTE实现语音和多媒体业务，LTE无线覆盖可以作为2G/3G无线的补充。?基于SCC AS和SRVCC增强MSC的控制，LTE 语音能够切换到CS网络。?需要部署IMS网络作为多媒体业务统一控制平台。?可以部署独立的 SRVCC 增强 MSC，支持Sv接口和SIP接口，避免所有MSC的升级。GANC-LTE VoIP with CS control?基于LTE实现语音和多媒体业务，LTE无线覆盖可以作为2G/3G无线的补充，支持向CS的平滑切换。?部署IWF模拟 BSC/RNC，向传统CS网络发起呼叫和切换，CS网络不需要升级。?需要UE支持基于LTE承载的CC/MM/SS协议栈能力。?不需要部署IMS网络。?方案尚未标准化，3GPP正在讨论。SGiA/IuhandoverhandoverMSCSMGWMGWMSCSSGsGANCMGCF/MGWSCC ASIMSCSCF多种LTE语音业务EMBMS技术(Rel9 Feature)UE E-UTRAN Uu E-UTRAN SGi-mb MBMS GW BM-SC M3 Content Provider SGmb M1 SGi MME SGSN Sn UTRAN UE Uu Iu PDN Gateway Sm The MBMS bearer service offers two modes:-Broadcast Mode;-Multicast Mode.Broadcast Mode is supported for EPS and GPRS,and Multicast Mode is supported for GPRS.MBMS for EPS supports E-UTRAN and UTRAN.MBMS for GPRS supports UTRAN and GERAN.EMBMS与MBMS差异性：主要在于EMSMS增加了IP multicast支持，但是只有广播模式。EMBMS技术(Rel9 Feature)UE E-UTR?EPC关键技术介绍?EPC业务流程介绍?EPC关键技术介绍?EPC业务流程介绍EPS域基本信令流程介绍?移动性管理?附着流程?TAU流程?业务请求流程?S1释放流程?GUTI重分配流程?Detach流程?会话管理?专有承载激活流程?带有QoS更新的承载修改?网络侧发起带QoS更新的承载修改?网络侧发起无QoS更新的承载修改?承载去活?UE请求的承载资源修改?切换管理?Intra-E-UTRAN切换?X2-based 切换?S1-based 切换?Inter RAT handover?E-UTRAN to UTRAN Iu mode Inter RAT切换?UTRAN Iu mode to E-UTRAN Inter RAT 切换?E-UTRAN to GERAN A/Gb mode Inter RAT切换?GERAN A/Gb mode to E-UTRAN Inter RAT切换?Inter RAT 切换取消EPS域基本信令流程介绍?移动性管理?附着流程?TAU流程?移动性管理EMM状态介绍 EMM-DEREGISTERED EMM-REGISTERED Attach accept Detach,Attach Reject,TAU reject,E-UTRAN interface switched off due to Non-3GPP handover,All bearers deactivated EMM-DEREGISTERED EMM-REGISTERED Attach accept TAU accept for a UE selecting E-UTRAN from GERAN/UTRAN Detach,Attach Reject,TAU reject,All bearers deactivated EMM state model in UE?MME中一般不保存MM上下文（除了避免每次附着时AKA流程情况下）?UE不可达，MME没有UE的任何位置或路由信息EMM Deregistered 状态EMM state model in MME?UE可达，MME知道UE的位置信息（位置精度至少在TAList基本）?UE至少有一个激活的PDN连接（最少一个默认承载上下文）?UE有安全上下文用于保存安全信息EMM Registered 状态移动性管理EMM状态介绍 EMM-DEREGISTERE移动性管理ECM状态介绍ECM state model in UE ECM state model in MME ECM-IDLE ECM-CONNECTED RRC connection established RRC connection released ECM-IDLE ECM-CONNECTED S1 connection established S1 connection released?UE和MME间没有NAS信令连接存在；?MME保存UE的TAList级别位置信息；?UE和MME间的上下文不同步。ECM-IDLE状态?UE与MME间存在信令连接，包括RRC连接和S1-MME连接；?MME保存UE的小区ID的级别位置信息；?UE和MME间的上下文信息互相同步。ECM-CONNECTED状态移动性管理ECM状态介绍ECM state model 移动性管理附着流程 3.Identification Request 1.Attach Request new MME Old MME/SGSN Serving GW PCRF HSS 3.Identification Response PDN GW 2.Attach Request eNodeB UE 4.Identity Request 4.Identity Response 5a.Authentication/Security 18.Attach Accept First Uplink Data 20.RRC Connection Reconfiguration Complete 19.RRC Connection Reconfiguration 21.Attach Complete 23.Update Bearer Response 22.Update Bearer Request First Downlink Data 24.Update Location Request 25.Update Location Response(B)(A)17.Create Default Bearer Response 13.Create Default Bearer Request 8.Update Location 9.Cancel Location 12.Update Location Ack 9.Cancel Location Ack 10.Delete Bearer Request 10.Delete Bearer Response 14.Create Default Bearer Request 16.Create Default Bearer Response 7.Delete Bearer Response 7.Delete Bearer Request 11.Insert Subscriber Data 11.Insert Subscriber Data Ack.First Downlink Data(C)EIR 5b.ME Identity Check 5b.Identity Request/Response 10.PCEF Initiated IP-CAN Session Termination 7.PCEF Initiated IP-CAN Session Termination 15.PCEF Initiated IP-CAN Session Establishment 6.PCO Request 6.PCO Response 在用户附着（接入）的同时建立默认承载，网络侧同时给UE分配IP地址移动性管理附着流程 3.Identification 移动性管理TAU流程(A)4.Context Request 2.TAU Request new MME old MME/old S4 SGSN new Serving GW PDN GW HSS 1.UE changes to a new Tracking Area 5.Context Response 6.Authentication 12.Update Location 13.Cancel Location 15.Insert Subscriber Data 14.Cancel Location Ack 17.Delete Bearer Request 18.Delete Bearer Response 19.TAU Accept 20.TAU Complete 7.Context Acknowledge old Serving GW 3.TAU Request eNodeB UE 11.Create Bearer Response 8.Create Bearer Request 9.Update Bearer Request 10.Update Bearer Response 16.Update Location Ack(B)15.Insert Subscriber Data Ack 移动性管理TAU流程(A)4.Context Re移动性管理Detach流程 (A)UE eNodeB MME Serving GW PDN GW PCRF 1.Detach Request 2.Delete Session Request 6.Delete Session Request 7.Delete Session Response 3.Delete Session Response 11.Detach Accept HSS SGSN 4.Detach Notification 5.Delete Session Request 9.Delete Session Response 10.Detach Ack 12.Signalling Connection Release 8.PCEF Initiated IP-CAN Session Termination 13.Notify Request 14.Notify Response 移动性管理Detach流程 (A)UE eNo会话管理承载概念介绍?默认承载类似一次激活?一个永久有效的承载，该承载在用户attach 时建立。?APN使用的是HSS中签约的默认APN，PCC规则使用PCRF下发的或P-GW 上配置的默认规则，地址由P-GW 分配。?一定是非GBR（GuaranteedBearerRate）承载?一般是低带宽、低时延、可用于访问DHCP服务器、IMS注册等。?专用承载类似二次激活?在默认承载建立后根据用户或应用层需要而建立，可以由网络侧或MS发起。?在默认承载基础上建立的到同一PDN的不同QoS 的承载。?可以是GBR或非GBR承载?多PDN激活类似激活第二个PDP当UE需要接入一个新PDN的时候，UE将新的APN带给MME，MME可能重新选择一个新的PDNGW。EPS系统支持一个PDNGW 接入多个PDN，也支持多个PDNGW 分别接入多个PDN。会话管理承载概念介绍?默认承载类似一次激活?一个永会话管理承载QoS控制?承载QoS控制控制?QoS控制粒度都是基于承载（Bearer）?对于QoS的动态控制，使用PCC机制。?将授权QoS参数分成了多个级别，用QCI（QoS class identifier）来标识。即一 个QCI就代表一套QoS参数?一个承载建立之后，QCI是不能改变的，如果QCI改变则必须重新发起新承载的建立过程。?LTE中的QoS参数分为UE级，APN级和承载级。其中per UE的参数包括UE-AMBR，per APN的参数包括APN-AMBR，per bearer 的参数包括：QCI,ARP,GBR and MBR。?per bearer QoS参数?QCI(QoS Class Identifier)：各个节点已经预配置包括eNodeB。基于GTP-u时，GTPU包的包头中带有QCI，区分QoS类别。在无线的PDU包头中也带有QCI。每个QCI对应一组无线调度参数?ARP(Allocation and Retention Priority)：建立或修改时的优先级，或出现异常时承载是否丢弃。建立后包的投递与此无关。?GBR(Guaranteed Bit Rate)?MBR(Maximum Bit Rate)?per APN的参数?APN-AMBR一个APN所对应的所有PDN Connection的所有Non-GBR Bearer的集合的最大速率，该集合中的任何一个Bearer的速率都可能达到该APN-AMBR所规定的上限APN-AMBR在HSS中签约PDN GW控制下行的APN-AMBR;UE和PDN GW负责上行APN-AMBR的控制。?per UE的参数?UE-AMBR：UE的所有Non-GBR Bearer的集合对应的最大速率，签约的UE-AMBR保存在HSS中，实际的UE-AMBR=Min(签约UE-AMBR，所有激活的APN-AMBR)，ENodeB负责上下行UE-AMBR的控制会话管理承载QoS控制?承载QoS控制?QoS控制粒度都3.Identification Request1.Attach Requestnew MMEOldM ME/SGSNServing GWPCRFHSS3.Identification ResponsePDN GW2.Attach RequesteNodeBUE4.Identity Request4.Identity Response5 a.Authentication/Security/ME Identity17.Attach AcceptF irst Uplink Data19.Radio Bearer establishment response18.Radio Bearer establishment request20.Attach Complete22.Update Bearer Response21.Update Bearer RequestFirst Downlink Data23.Update LocationRequest24.Update LocationResponse(B)(A)16.Create Default Bearer Response12.Create Default Bearer Request7.Update Location8.Cancel Location11.Update Location Ack8.Cancel Location Ack9.Delete Bearer Request9.Delete Bearer Response13.Create Default Bearer Request15.Create Default Bearer Response6.Delete Bearer Response6.Delete Bearer Request10.Insert Subscriber Data10.Insert Subscriber DataAck.14.PCRF InteractionFirstDownlinkData(C)EIR5 b.ME Identity Check6.PCRF interaction9.PCRF interaction会话管理承载建立流程在用户附着（接入）的同时建立默认承载，也可以同时建立默认承载和专有承载（依赖于PCC规则）3.IdentificationRequest1.Attac(B)(1.PCC Decision Provision)3.Update Bearer RequestMMEServingGWPDNGWPCR F4.Bearer Modify Request5.Radio Bearer Modify Request2.UpdateBearer request6.Radio Bearer Modify Response7.Bearer Modify Response8.Update Bearer Response9.UpdateBearer response(10.Provision Ack)UEeNodeB(A)会话管理网络侧发起的承载修改(B)(1.PCCDecisionProvision)3.U会话管理专有承载建立过程（GTP）?PCRF根据业务请求生成PCC Rule，包括QCI、ARP、GBR、MBR等信息；?PDN GW决定为该业务建立新承载，PDN GW根据PCC Rule生成EPS Bearer QoS，PDN GW向SGW发送创建专用承载请求消息，PDN GW将缺省承载的LBI也发送给SGW，PGW分配S5下行GTPU隧道ID；?SGW分配S1上行GTPU隧道ID和S5下行GTPU隧道ID；?MME为该新EPS Bearer分配Bearer ID，并向EUTRAN发送Radio Bearer建立请求，MME将S1上行GTUP隧道ID发送给EUTRAN；?EUTRAN与UE间建立Radio Bearer，并将Bearer对应的EPS Bearer ID发给UE；?EUTRAN将S1下行GTPU隧道ID发送给MME，MME转给SGW，在EUTRAN和SGW间建立S1 Bearer；?SGW将S5下行GTPU隧道ID发送给PGW，建立S5 Bearer。MMEPGWPCRFSGWCreate Dedicated Bearer RequestCreate Dedicated Bearer RequestBearer Setup Req/Session Management ReqRRC Conf complete/Session Management RespBearer Setup Resp/Session Management RespCreate Dedicated Bearer RespCreate Dedicated Bearer RespRRC Conf Req会话管理专有承载建立过程（GTP）?PCRF根据业务请求切换管理总体介绍?切换的基本要求：?用户处于连接状态（用户有上下行数据）?Intra-E-UTRAN切换?X2-based 切换?S1-based 切换?Inter RAT handover?E-UTRAN to UTRAN Iu mode Inter RAT切换?UTRAN Iu mode to E-UTRAN Inter RAT 切换?E-UTRAN to GERAN A/Gb mode Inter RAT切换?GERAN A/Gb mode to E-UTRAN Inter RAT切换?Inter RAT 切换取消切换管理总体介绍?切换的基本要求：?用户处于连接状态（用切换管理X2-based 切换 Handover completion UE Source eNodeB Source Serving GW PDN GW MME Target Serving GW Target eNodeB Handover execution 3a.Modify Bearer Request Downlink and uplink data Handover preparation Forwarding of data Downlink data Uplink data 1.Path Switch Request 3b.Modify Bearer Response 2.Create Session Request 4.Create Session Response 5.Path Switch Request Ack 6.Release Resource Downlink data Uplink data 7a.Delete Session Request 7b.Delete Session Response(A)(B)8.Tracking Area Update procedure 基于X2的切换要求：MME没有改变，且源eNodeB和目的eNodeB有X2接口。切换管理X2-based 切换 Handover com切换管理 S1-based 切换 UE Source eNodeB Source MME Source Serving GW PDN GW Target MME Target Serving GW Target eNodeB Detach from old cell and synchronize to new cell HSS 16.Modify Bearer Request 17.Modify Bearer Response 15.Modify Bearer Request Downlink User Plane data 2.Handover Required Downlink User Plane data 1.Decision to trigger a relocation via S1 3.Forward Relocation Request 5.Handover Request 5a.Handover Request Acknowledge 7.Forward Relocation Response 9.Handover Command 9a.Handover Command 11a.Only for Direct forwarding of data 12.Handover Confirm Downlink data 13.Handover Notify 14.Forward Relocation Complete Notification 14b.Forward Relocation Complete Acknowledge 16a.Modify Bearer Response.8a.Create Indirect Data Forwarding Tunnel Response(A)11b.Only for Indirect forwarding of data 18.Tracking Area Update procedure 19c.Delete Session Request(B)19a.UE Context Release Command Uplink User Plane data 8.Create Indirect Data Forwarding Tunnel Request 6a.Create Indirect Data Forwarding Tunnel Response 6.Create Indirect Data Forwarding Tunnel Request 4a.Create Session Response 4.Create Session Request 19b.UE Context Release Complete 19d.Delete Session Response 20a.Delete Indirect Data Forwarding Tunnel Request 20b.Delete Indirect Data Forwarding Tunnel Response 21a.Delete Indirect Data Forwarding Tunnel Request 21b.Delete Indirect Data Forwarding Tunnel Response 10.eNB Status Transfer 10c.eNB Status Transfer 10a.Forward Access Context Notification 10b.Forward Access Context Acknowledge 不能使用基于X2切换的流程才会采用基于S1接口的切换流程，该流程下MME、Serving GW可能会改变切换管理S1-based 切换 UE Source eN切换管理E-UTRAN to UTRAN Iu mode Inter RAT切换 UE Source eNodeB Target RNC Source MME Target SGSN Serving GW HSS PDN GW Uplink and Downlink User Plane PDUs 1.Handover Command 2.HO from E-UTRAN Command-Sending of uplink data possible 4.UTRAN Iu Access Procedures 5.Relocation Complete 6.Forward Relocation Complete Notification 6a.Forward Relocation Complete Acknowledge 7.Modify Bearer Request 8a.Modify Bearer Response 9.Modify Bearer Response Uplink and Downlink User Plane PDUs(Via Target SGSN if Direct Tunnel is not used)4a.Handover to UTRAN Complete Downlink User Plane PDUs If Direct Forwarding applies If Indirect Forwarding applies.Target Serving GW(A)8.Modify Bearer Request Via Target SGSN in case Direct Tunnel is not used 10.Routeing Area Update procedure 11.Delete Session Request(B)11a.Delete Session Response 11b.Release Resources For Serving GW relocation Steps 7,8 and 9,and the following User Plane path,will be handled by Target Serving GW 12.Delete Indirect Data Forwarding Tunnel Source 切换管理E-UTR
展开阅读全文