《LTE典型信令过程资料》由会员分享，可在线阅读，更多相关《LTE典型信令过程资料（52页珍藏版）》请在金锄头文库上搜索。
1、LTE 典型信令过程,Software Architecture,3类NAS信令流程,1. 会话管理相关 2. 位置管理相关 3. 鉴权管理相关,UE,eNB,MME,SGW,PGW,RRC: RRC Connection setup complete,NAS: Attach Request NAS:PDN connectivity request,S1AP: Initial UE message,Authentication and NAS security procedure,HSS,S6a: Update Location request,S6a: Update Location ans
2、wer,S11: Create bearer request,S5: Create bearer request,S5: Create bearer response,S11: Create bearer response,S1AP: Initial Context setup request,NAS: Attach accept NAS: Activate Default EPS bearer request,NAS: Attach Request NAS:PDN connectivity request,RRC: RRCConnectionReconfiguration,NAS: Atta
3、ch accept NAS: Activate Default EPS bearer request,RRC: RRCConReconfigComplete,S1AP: Initial Context setup response,RRC: UL information Transfer,NAS: Attach complete NAS: Activate Default EPS bearer accept,S1AP: Uplink NAS Transport,NAS: Attach complete NAS: Activate Default EPS bearer accept,UE ini
4、tiated Detach Procedure,UE,eNB,MME,SGW,PGW,HSS,RRC: RRC Connection setup complete,NAS: Detach request,S1AP: Initial UE message,NAS: Detach request,Authentication and NAS security,S11: Delete session request,S5: Delete session request,S5: Delete session response,S11: Delete session response,S1AP: Dow
5、nlink NAS transport,NAS: Detach accept,RRC: DLInformation transfer,NAS: Detach accept,Radio and S1 Release,S6a: TDelay purge timer expires,S6a: Purge UE request,S6a: Purge UE answer,UE Triggered Service Request Procedure,Initial UE Message,Network Triggered Service Request,TAU procedure,Inter MME-TA
6、U-message flow,Handover,Handover Air Interface,TYPES OF HANDOVER X2 Based Handover : without SGW change and with SGW change S1 Based Handover : with eNB, MME and SGW change,X2 Handover,X2 is the interface between two eNBs and X2-AP is the protocols used for communication over it. The handover is dir
7、ectly performed between two eNodeBs. Handover takes place when the eNB detects that UE can no longer be served by it because of the power constraints. The MME is only informed at the end of the handover procedure once the handover is successful The release of resources at the source side is directly
8、 triggered from the target eNB.,RRC: Connection Reconfiguration Request,RRC: Connection Reconfiguration Complete,UE,S-eNB,T-eNB,MME,SGW,RRC: Measurement Control,X2AP: Handover Request,S11: Modify bearer request,S11: Modify bearer response,X2AP: SN Status Transfer,Sync,UL Allocation + TA for UE,UL Al
9、location,RRC: Measurement Report,Handover Decision,X2AP: Handover Response,UE Detach from old cell and sync to new cell,S1AP: Path Switch Request,S1AP: Path Switch Response,X2AP: UE Context Release,End Marker,Switch DL Path,Data Forwarding,Data Forwarding,End Marker,Flush DL Buffer,S1 Handover,This
10、type of handover takes place when there is no X2 connectivity between source eNB and target eNB. Both eNBs are served by different MMEs. SGWs can also be different. Source eNB is served by source MME and source SGW while target eNB is served by target MME and target SGW. Source and target MMEs can c
11、ommunicate over S10 interface. All the handover decisions are taking place on S1 interface, its called as S1 based handover.,UE,T-eNB,S-MME,T-MME,T-SGW,S10: Forward Relocation Request,S11: Create Session Request,S11: Create Session Response,S1AP: eNB Status Transfer,S1AP: Handover Required,S1AP: Han
12、dover Request,UE Detach from old cell and sync to new cell,S11: Modify Bearer Request,S1AP: UE Context Release Command,S-eNB,S-SGW,PGW,Handover Decision,S1AP: Handover Request Ack,S10: Forward Relocation Response,S1AP: Handover Command,RRC: Connection Reconfiguration,RRC: Connection Reconfiguration
13、Complete,S1AP: Handover Notify,S11: Modify Bearer Response,S5: Modify Bearer Request,S1AP: UE Context Release Complete,S11: Delete Session Request,S11: Delete Session Response,S1AP: MME Status Transfer,S10: Forward SRNS Context Notification,S10: Forward SRNS Context Ack,S10: Forward Relocation Compl
14、ete,S10: Forward Relocation Complete Ack,S5: Modify Bearer Response,开始,Before the UE can do anything, a Radio Resource Control connection must be established. The RRC is a logical connection between the UE and E-UTRAN. There are two different RRC states: RRC IDLE RRC CONNECTED,RRC IDLE,This state in
15、dicates that there is no signaling radio bearer is established i.e. no RRC connection is established. The UE is considered RRC_IDLE once it obtains the center frequency, reads the timing information, syncs to the eNodeB, and is ready to receive system broadcast information. UE monitors a paging chan
16、nel to detect incoming calls. UE can performs neighboring cell measurements and measurement reporting.,RRC CONNECTED,This state indicates that there is signaling radio bearer established i.e. RRC connection is established. Transfer of unicast data to/from an UE. The UE Monitors control channels associated with the shared data channel to determine if data is scheduled for it. The
