05_cn31535en30gla0_mobility And Bearer Management In Flexi Ns 3.0 Mme.pdf
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View 05_cn31535en30gla0_mobility And Bearer Management In Flexi Ns 3.0 Mme.pdf as PDF for free.
More details
- Words: 4,011
- Pages: 166
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
1
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
2
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
4
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
5
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
6
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
7
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
8
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
9
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
10
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
11
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
12
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
13
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
14
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
15
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
16
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
17
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
18
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
19
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
20
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
21
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
22
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
23
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
24
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
25
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
26
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
27
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
28
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
29
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
30
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
31
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
32
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
33
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
34
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
35
Mobility Management & Bearer Management in Flexi Network Server 3.0
The attach procedure in LTE/EPS is quite similar to the GPRS attach in 2G/3G. It brings the UE from EMM_DEREGISTERED state to EMM_REGISTERED. In addition to that the procedure also establishes the default SAE bearer for the UE and thus allocates the required IP addresses for the subscriber in the external packet data network. 1. The UE connects to the serving cell and the associated eNB. The UE sends the ATTACH REQUEST message (NAS) including IMSI/ old GUTI, old TAI, old GUMMEI and old ECGI. The eNB selects an available MME and forwards the message to it. 2. The first task of the MME is to identify and authenticate the subscriber. Thus it contacts the HSS (in case IMSI is used for identification) or the old MME (in case the UE is identified via old GUTI) with IDENTIFICATION REQUEST (GTP-C). The response should contain the IMSI (when contacting old MME) and some authentication vectors for the subscriber. (Flowchart shows direct contact with HSS). 3. Using the authentication vectors from the old MME/HSS the new MME can start an authentication procedure (NAS). The authentication mechanism is the same as in 3G. 4. After a successful authentication the new MME can begin to update the HSS and download the subscription data from there. This is achieved via Diameter procedures UPDATE LOCATION and INSERT SUBSCRIBER DATA. During this process the HSS will also force the old MME to clear the stored data about the subscriber using the Diameter operation CANCEL LOCATION. The Figure shows the Attach procedure without Gateway Selection by DNS Server.
CN31535EN30GLA0
36
Mobility Management & Bearer Management in Flexi Network Server 3.0
5. Based on the subscription data the new MME must decide whether a default bearer has to be created or not. The default access point name (default APN) assists the MME in selection of an appropriate SAE GW. To this serving gateway the CREATE DEFAULT BEARER REQUEST message (GTP-C) is sent to. The SAE GW will now create the S5/S8 tunnel. This is done with the same message, but sent to the PDN GW. 6. When the EPC resources for the default bearer are prepared, the new MME can give the ATTACH ACCEPT message to eNB. The S1-AP message which will contain it is the Initial Context Setup request and it will also hold the tunnel endpoint identifier allocated by the Serving GW for S1-U interface. The eNB creates the radio bearer for the default SAE bearer and returns ATTACH COMPLETE to the MME. The S1-AP message this one is in will hold the TEID allocated by the eNB for S1-U interface. Via an UPDATE BEARER procedure the MME will give this parameter to the Serving GW. 7. Now the default SAE bearer is complete and the UE is in state EMM_REGISTERED and ECM_CONNECTED. The Figure shows the Attach procedure without Gateway Selection by DNS Server.
CN31535EN30GLA0
37
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
38
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
39
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
40
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
41
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
42
Mobility Management & Bearer Management in Flexi Network Server 3.0
The UE sends a Detach Request message to the MME as shown in figure above. This message triggers the establishment of the S1 connection if the UE is in ECMIDLE mode. 1. The eNB forwards the Detach Request NAS message to the MME along with the Tracking Area Identity (TAI) and E-UTRAN Cell Global Identifier (ECGI) of the cell which the UE is using. 2. The active Evolved Packet System (EPS) bearer in the S-GW is deactivated by the MME. The MME sends the Delete Bearer Request message to the S-GW. 3. The S-GW releases the related EPS Bearer context information and responds with the Delete Bearer Response message. 4. The MME sends a Detach Accept message to the UE. 5. The MME releases the S1-MME signaling connection for the UE by sending S1 Release Command to the eNB with cause set to detach. 6. If the subscription data indicates that the user is allowed to perform handover to non-3GPP access and the MME is configured to notify the HSS at detach, the MME sends Notify Request to indicate that HSS must remove the APN and PGW identity for this UE. 7. The HSS removes the APN and P-GW identity pairs and sends a Notify Response to the MME. (Note that Notify Request / Notify Response is not supported yet.)
CN31535EN30GLA0
43
Mobility Management & Bearer Management in Flexi Network Server 3.0
1.
The MME initiated detach procedure is either explicit (e.g. by O&M intervention) or implicit. The MME may implicitly detach a UE, if it has not had communication with UE for a long period of time. The MME does not send the Detach Request (Detach Type) message to the UE for implicit detach. The implicit detach is local to the MME, i.e. an SGSN registration will not be detached. If the UE is in ECM-CONNNECTED state the MME may explicitly detach the UE by sending a Detach Request message to the UE. The Detach Type may be set to re-attach in which case the UE should re-attach at the end of the detach process. If the UE is in ECM-IDLE state the MME pages the UE.
2.
Any EPS Bearer Context information in the Serving GW regarding this particular UE and related to the MME are deactivated by the MME sending Delete Session Request (TEID) message to the Serving GW. If the PDN GW requested UE's location info, the MME also includes the User Location Information IE in this message.
3.
When the S-GW receives the Delete Session Request message from the MME, the Serving GW releases the related EPS Bearer context information. The Serving GW sends a Delete Session Request (TEID) message to the PDN GW. This message includes an indication that all bearers belonging to that PDN connection shall be released.
4.
The PDN GW acknowledges with Delete Bearer Response (TEID) message. The PDN GW employs an IP-CAN Session Termination procedure as defined in TS 23.203 [6] with the PCRF to indicate to the PCRF that the EPS Bearer(s) are released if a PCRF is configured.
5.
The Serving GW acknowledges with Delete Session Response (TEID) message.
6.
The SGSN sends Detach Acknowledge message to the MME.
7.
If the UE receives the Detach Request message from the MME in the step 1, the UE sends a Detach Accept message to the MME any time after step 1. The eNodeB forwards this NAS message to the MME along with the TAI+ECGI of the cell which the UE is using.
8.
After receiving the Detach Accept message, Delete Session Response and, if appropriate, Detach Acknowledge message, the MME releases the S1-MME signaling connection for the UE by sending an S1 Release Command (Cause) message to the eNodeB. The details of this step are covered in the "S1 Release Procedure". If the Detach Type requests the UE to make a new attach, the UE reattaches after the RRC Connection Release is completed.
9.
After the MME receives the Delete Session Response from Serving GW, if the subscription data indicates that the user is allowed to perform handover to non-3GPP access and the MME is configured to notify the HSS at detach, the MME shall send a Notify Request to indicate that the HSS shall remove the APN and PDN GW identity pairs for this UE.
10. The HSS removes all APN and PDN GW identity pairs that were dynamically stored and sends a Notify Response to the MME.
CN31535EN30GLA0
44
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
45
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
46
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
47
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
48
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
49
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
50
Mobility Management & Bearer Management in Flexi Network Server 3.0
1. The UE sends TRACKING AREA UPDATE REQUEST with its current GUTI or IMSI, old TAI and EPS Bearer Status information to the eNB. This one has to forward the message to a MME. If the old MME cannot be selected, then a new MME must be chosen by the eNB. 2. The new MME must first of all get the identity (IMSI) of the subscriber and authenticate him/her. Therefore the new MME contacts the old one via GTP-C CONTEXT REQUEST. The CONTEXT RESPONSE contains IMSI, authentication vectors, but also all information about the currently active SAE bearers of this user. 3. With one of the authentication vectors the new MME can start authentication. 4. After a successful authentication the new MME analyzes if a Serving GW change is needed 5. New MME informs the old one that it is ready to take control over the UE (Context Acknowledge message). The old MME will now start a timer and wait for the cancellation of the subscriber record. 6. In parallel to the previous step the new MME sends GTP-C CREATE BEARER REQUEST to the Serving GW it has selected. The message will trigger the setup of new S1 tunnels and trigger an update towards PDN GW. This will change the traffic path from PDN GW to new Serving GW to new eNB.
CN31535EN30GLA0
51
Mobility Management & Bearer Management in Flexi Network Server 3.0
7. Also simultaneously with the previous steps the MME will update the HSS. During this the HSS will cancel the subscriber record in the old MME. The old MME will of course also delete the old tunnels in the old Serving GW. 8. At the end the UE gets a NAS message TRACKING AREA UPDATE ACCEPT. In it a new GUTI and new tracking area (or tracking area list) will be contained. The UE has to acknowledge with TRACKING AREA UPDATE COMPLETE.
CN31535EN30GLA0
52
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
53
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
54
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
55
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
56
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
57
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
58
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
59
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
60
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
61
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
62
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
63
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
64
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
65
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
66
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
67
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
68
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
69
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
70
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
73
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
74
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
75
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
76
Mobility Management & Bearer Management in Flexi Network Server 3.0
For further information about the EPS Bearer, please refer to 3GPP TS 23.401, section 4.7.2
CN31535EN30GLA0
77
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
78
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
79
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
80
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
81
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
82
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
83
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
84
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
85
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
86
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
87
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
88
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
89
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
90
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
91
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
92
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
93
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
94
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
95
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
96
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
97
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
98
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
99
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
100
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
101
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
102
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
103
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
104
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
105
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
106
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
107
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
108
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
109
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
110
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
111
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
112
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
113
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
114
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
115
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
116
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
117
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
118
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
119
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
120
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
121
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
122
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
123
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
124
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
125
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
126
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
127
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
128
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
129
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
130
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
131
Mobility Management & Bearer Management in Flexi Network Server 3.0
UE in idle mode When UE is in idle mode, it sends the Extended Service Request message to the MME and the UE moves to the ECM-CONNECTED state. The MME sends the S1-AP Initial Context Setup Request (with CS fallback indicator, LAI) to the eNB. This message indicates to the eNB that the UE should be moved to 2G/3G (GERAN/UTRAN) network. The eNB responds with the S1-AP Initial Context Setup Response message. The eNB sends the S1-AP UE Context Release Request message to the MME. As a result, the MME initiates the S1 release procedure which releases the UE context in the eNB as well as all eNB-related information in the S-GW. The rest of the steps in CSFB mobile-originating call in 2G/3G (GERAN/UTRAN) idle mode are the same as in the CSFB mobile-originating call in 2G/3G (GERAN/UTRAN) active mode. Mobile-originating CS emergency call An MO emergency CSFB call can take place when the UE is in active or idle mode. In both cases, the MO emergency call procedure is the same as that of MO CSFB call except for the following: • The Extended Service Request message sent by UE to the MME has service type IE set as mobile originating CS fallback emergency call. • In UE active state, the S1-AP UE Context Modification Request message sent by the MME to the eNB has the CS fallback indicator IE set as CS fallback high priority. • In UE idle state, the S1-AP Initial Context Setup Request message sent by the MME to the eNB has the CS fallback indicator IE set as CS fallback high priority.
CN31535EN30GLA0
132
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
133
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
134
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
135
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
136
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
137
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
138
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
139
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
140
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
141
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
142
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
143
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
144
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
145
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
146
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
147
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
148
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
149
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
150
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
151
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
152
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
153
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
154
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
155
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
156
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
157
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
158
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
159
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
160
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
161
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
162
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
163
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
164
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
165
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
166
Mobility Management & Bearer Management in Flexi Network Server 3.0
The UE sends measurement reports to the E-UTRAN. Based on the UE measurement reports the source E-UTRAN triggers an SRVCC handover to the UTRAN/GERAN. The eNB sends the Handover Required message, indicating that the target is UTRAN/GERAN with only CS HO support, to the source MME. • The source MME performs the EPS bearer splitting function by separating the voice EPS bearer from the non-voice EPS bearers. • The source MME sends the SRVCC PS to CS Request message to the target MSC through the Sv interface to initiate the PS to CS handover procedure, and the MSC replies with the SRVCC PS to CS Response message. • The source MME sends the Handover Command message to the eNB. • The source MME receives the SRVCC PS to CS Complete Notification message from the target MSC and replies with the SRVCC PS to CS Complete Acknowledge message. • The source MME deactivates the voice bearer towards the S-GW/P-GW and sets the Voice Bearer indicator to the Delete Bearer Command message. • The remaining PS resources are re-established when the UE performs inter-system RAU. With RAU, the UE selects UTRAN/GERAN cell served by the target SGSN. • The source MME sends the UE Context Release Command message to the source eNB. Since there is no longer any need for the source eNB to forward data, the eNB releases its resources. • The MME deletes the session from the S-GW.
CN31535EN30GLA0
167
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
168
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
169
CN31535EN30GLA0
1
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
2
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
4
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
5
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
6
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
7
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
8
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
9
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
10
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
11
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
12
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
13
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
14
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
15
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
16
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
17
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
18
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
19
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
20
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
21
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
22
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
23
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
24
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
25
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
26
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
27
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
28
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
29
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
30
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
31
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
32
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
33
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
34
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
35
Mobility Management & Bearer Management in Flexi Network Server 3.0
The attach procedure in LTE/EPS is quite similar to the GPRS attach in 2G/3G. It brings the UE from EMM_DEREGISTERED state to EMM_REGISTERED. In addition to that the procedure also establishes the default SAE bearer for the UE and thus allocates the required IP addresses for the subscriber in the external packet data network. 1. The UE connects to the serving cell and the associated eNB. The UE sends the ATTACH REQUEST message (NAS) including IMSI/ old GUTI, old TAI, old GUMMEI and old ECGI. The eNB selects an available MME and forwards the message to it. 2. The first task of the MME is to identify and authenticate the subscriber. Thus it contacts the HSS (in case IMSI is used for identification) or the old MME (in case the UE is identified via old GUTI) with IDENTIFICATION REQUEST (GTP-C). The response should contain the IMSI (when contacting old MME) and some authentication vectors for the subscriber. (Flowchart shows direct contact with HSS). 3. Using the authentication vectors from the old MME/HSS the new MME can start an authentication procedure (NAS). The authentication mechanism is the same as in 3G. 4. After a successful authentication the new MME can begin to update the HSS and download the subscription data from there. This is achieved via Diameter procedures UPDATE LOCATION and INSERT SUBSCRIBER DATA. During this process the HSS will also force the old MME to clear the stored data about the subscriber using the Diameter operation CANCEL LOCATION. The Figure shows the Attach procedure without Gateway Selection by DNS Server.
CN31535EN30GLA0
36
Mobility Management & Bearer Management in Flexi Network Server 3.0
5. Based on the subscription data the new MME must decide whether a default bearer has to be created or not. The default access point name (default APN) assists the MME in selection of an appropriate SAE GW. To this serving gateway the CREATE DEFAULT BEARER REQUEST message (GTP-C) is sent to. The SAE GW will now create the S5/S8 tunnel. This is done with the same message, but sent to the PDN GW. 6. When the EPC resources for the default bearer are prepared, the new MME can give the ATTACH ACCEPT message to eNB. The S1-AP message which will contain it is the Initial Context Setup request and it will also hold the tunnel endpoint identifier allocated by the Serving GW for S1-U interface. The eNB creates the radio bearer for the default SAE bearer and returns ATTACH COMPLETE to the MME. The S1-AP message this one is in will hold the TEID allocated by the eNB for S1-U interface. Via an UPDATE BEARER procedure the MME will give this parameter to the Serving GW. 7. Now the default SAE bearer is complete and the UE is in state EMM_REGISTERED and ECM_CONNECTED. The Figure shows the Attach procedure without Gateway Selection by DNS Server.
CN31535EN30GLA0
37
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
38
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
39
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
40
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
41
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
42
Mobility Management & Bearer Management in Flexi Network Server 3.0
The UE sends a Detach Request message to the MME as shown in figure above. This message triggers the establishment of the S1 connection if the UE is in ECMIDLE mode. 1. The eNB forwards the Detach Request NAS message to the MME along with the Tracking Area Identity (TAI) and E-UTRAN Cell Global Identifier (ECGI) of the cell which the UE is using. 2. The active Evolved Packet System (EPS) bearer in the S-GW is deactivated by the MME. The MME sends the Delete Bearer Request message to the S-GW. 3. The S-GW releases the related EPS Bearer context information and responds with the Delete Bearer Response message. 4. The MME sends a Detach Accept message to the UE. 5. The MME releases the S1-MME signaling connection for the UE by sending S1 Release Command to the eNB with cause set to detach. 6. If the subscription data indicates that the user is allowed to perform handover to non-3GPP access and the MME is configured to notify the HSS at detach, the MME sends Notify Request to indicate that HSS must remove the APN and PGW identity for this UE. 7. The HSS removes the APN and P-GW identity pairs and sends a Notify Response to the MME. (Note that Notify Request / Notify Response is not supported yet.)
CN31535EN30GLA0
43
Mobility Management & Bearer Management in Flexi Network Server 3.0
1.
The MME initiated detach procedure is either explicit (e.g. by O&M intervention) or implicit. The MME may implicitly detach a UE, if it has not had communication with UE for a long period of time. The MME does not send the Detach Request (Detach Type) message to the UE for implicit detach. The implicit detach is local to the MME, i.e. an SGSN registration will not be detached. If the UE is in ECM-CONNNECTED state the MME may explicitly detach the UE by sending a Detach Request message to the UE. The Detach Type may be set to re-attach in which case the UE should re-attach at the end of the detach process. If the UE is in ECM-IDLE state the MME pages the UE.
2.
Any EPS Bearer Context information in the Serving GW regarding this particular UE and related to the MME are deactivated by the MME sending Delete Session Request (TEID) message to the Serving GW. If the PDN GW requested UE's location info, the MME also includes the User Location Information IE in this message.
3.
When the S-GW receives the Delete Session Request message from the MME, the Serving GW releases the related EPS Bearer context information. The Serving GW sends a Delete Session Request (TEID) message to the PDN GW. This message includes an indication that all bearers belonging to that PDN connection shall be released.
4.
The PDN GW acknowledges with Delete Bearer Response (TEID) message. The PDN GW employs an IP-CAN Session Termination procedure as defined in TS 23.203 [6] with the PCRF to indicate to the PCRF that the EPS Bearer(s) are released if a PCRF is configured.
5.
The Serving GW acknowledges with Delete Session Response (TEID) message.
6.
The SGSN sends Detach Acknowledge message to the MME.
7.
If the UE receives the Detach Request message from the MME in the step 1, the UE sends a Detach Accept message to the MME any time after step 1. The eNodeB forwards this NAS message to the MME along with the TAI+ECGI of the cell which the UE is using.
8.
After receiving the Detach Accept message, Delete Session Response and, if appropriate, Detach Acknowledge message, the MME releases the S1-MME signaling connection for the UE by sending an S1 Release Command (Cause) message to the eNodeB. The details of this step are covered in the "S1 Release Procedure". If the Detach Type requests the UE to make a new attach, the UE reattaches after the RRC Connection Release is completed.
9.
After the MME receives the Delete Session Response from Serving GW, if the subscription data indicates that the user is allowed to perform handover to non-3GPP access and the MME is configured to notify the HSS at detach, the MME shall send a Notify Request to indicate that the HSS shall remove the APN and PDN GW identity pairs for this UE.
10. The HSS removes all APN and PDN GW identity pairs that were dynamically stored and sends a Notify Response to the MME.
CN31535EN30GLA0
44
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
45
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
46
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
47
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
48
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
49
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
50
Mobility Management & Bearer Management in Flexi Network Server 3.0
1. The UE sends TRACKING AREA UPDATE REQUEST with its current GUTI or IMSI, old TAI and EPS Bearer Status information to the eNB. This one has to forward the message to a MME. If the old MME cannot be selected, then a new MME must be chosen by the eNB. 2. The new MME must first of all get the identity (IMSI) of the subscriber and authenticate him/her. Therefore the new MME contacts the old one via GTP-C CONTEXT REQUEST. The CONTEXT RESPONSE contains IMSI, authentication vectors, but also all information about the currently active SAE bearers of this user. 3. With one of the authentication vectors the new MME can start authentication. 4. After a successful authentication the new MME analyzes if a Serving GW change is needed 5. New MME informs the old one that it is ready to take control over the UE (Context Acknowledge message). The old MME will now start a timer and wait for the cancellation of the subscriber record. 6. In parallel to the previous step the new MME sends GTP-C CREATE BEARER REQUEST to the Serving GW it has selected. The message will trigger the setup of new S1 tunnels and trigger an update towards PDN GW. This will change the traffic path from PDN GW to new Serving GW to new eNB.
CN31535EN30GLA0
51
Mobility Management & Bearer Management in Flexi Network Server 3.0
7. Also simultaneously with the previous steps the MME will update the HSS. During this the HSS will cancel the subscriber record in the old MME. The old MME will of course also delete the old tunnels in the old Serving GW. 8. At the end the UE gets a NAS message TRACKING AREA UPDATE ACCEPT. In it a new GUTI and new tracking area (or tracking area list) will be contained. The UE has to acknowledge with TRACKING AREA UPDATE COMPLETE.
CN31535EN30GLA0
52
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
53
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
54
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
55
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
56
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
57
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
58
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
59
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
60
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
61
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
62
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
63
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
64
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
65
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
66
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
67
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
68
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
69
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
70
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
73
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
74
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
75
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
76
Mobility Management & Bearer Management in Flexi Network Server 3.0
For further information about the EPS Bearer, please refer to 3GPP TS 23.401, section 4.7.2
CN31535EN30GLA0
77
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
78
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
79
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
80
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
81
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
82
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
83
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
84
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
85
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
86
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
87
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
88
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
89
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
90
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
91
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
92
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
93
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
94
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
95
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
96
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
97
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
98
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
99
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
100
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
101
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
102
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
103
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
104
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
105
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
106
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
107
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
108
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
109
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
110
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
111
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
112
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
113
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
114
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
115
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
116
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
117
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
118
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
119
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
120
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
121
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
122
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
123
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
124
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
125
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
126
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
127
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
128
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
129
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
130
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
131
Mobility Management & Bearer Management in Flexi Network Server 3.0
UE in idle mode When UE is in idle mode, it sends the Extended Service Request message to the MME and the UE moves to the ECM-CONNECTED state. The MME sends the S1-AP Initial Context Setup Request (with CS fallback indicator, LAI) to the eNB. This message indicates to the eNB that the UE should be moved to 2G/3G (GERAN/UTRAN) network. The eNB responds with the S1-AP Initial Context Setup Response message. The eNB sends the S1-AP UE Context Release Request message to the MME. As a result, the MME initiates the S1 release procedure which releases the UE context in the eNB as well as all eNB-related information in the S-GW. The rest of the steps in CSFB mobile-originating call in 2G/3G (GERAN/UTRAN) idle mode are the same as in the CSFB mobile-originating call in 2G/3G (GERAN/UTRAN) active mode. Mobile-originating CS emergency call An MO emergency CSFB call can take place when the UE is in active or idle mode. In both cases, the MO emergency call procedure is the same as that of MO CSFB call except for the following: • The Extended Service Request message sent by UE to the MME has service type IE set as mobile originating CS fallback emergency call. • In UE active state, the S1-AP UE Context Modification Request message sent by the MME to the eNB has the CS fallback indicator IE set as CS fallback high priority. • In UE idle state, the S1-AP Initial Context Setup Request message sent by the MME to the eNB has the CS fallback indicator IE set as CS fallback high priority.
CN31535EN30GLA0
132
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
133
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
134
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
135
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
136
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
137
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
138
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
139
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
140
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
141
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
142
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
143
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
144
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
145
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
146
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
147
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
148
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
149
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
150
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
151
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
152
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
153
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
154
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
155
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
156
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
157
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
158
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
159
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
160
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
161
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
162
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
163
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
164
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
165
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
166
Mobility Management & Bearer Management in Flexi Network Server 3.0
The UE sends measurement reports to the E-UTRAN. Based on the UE measurement reports the source E-UTRAN triggers an SRVCC handover to the UTRAN/GERAN. The eNB sends the Handover Required message, indicating that the target is UTRAN/GERAN with only CS HO support, to the source MME. • The source MME performs the EPS bearer splitting function by separating the voice EPS bearer from the non-voice EPS bearers. • The source MME sends the SRVCC PS to CS Request message to the target MSC through the Sv interface to initiate the PS to CS handover procedure, and the MSC replies with the SRVCC PS to CS Response message. • The source MME sends the Handover Command message to the eNB. • The source MME receives the SRVCC PS to CS Complete Notification message from the target MSC and replies with the SRVCC PS to CS Complete Acknowledge message. • The source MME deactivates the voice bearer towards the S-GW/P-GW and sets the Voice Bearer indicator to the Delete Bearer Command message. • The remaining PS resources are re-established when the UE performs inter-system RAU. With RAU, the UE selects UTRAN/GERAN cell served by the target SGSN. • The source MME sends the UE Context Release Command message to the source eNB. Since there is no longer any need for the source eNB to forward data, the eNB releases its resources. • The MME deletes the session from the S-GW.
CN31535EN30GLA0
167
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
168
Mobility Management & Bearer Management in Flexi Network Server 3.0
CN31535EN30GLA0
169
Related Documents
Ned - Flexi Ns - Mme Hardware Description.pdf
April 2020 1
Ns
May 2020 42
Ns
June 2020 31
Ns
July 2020 30More Documents from ""
Ned - Flexi Ns - Mme Hardware Description.pdf
April 2020 1
04_02_cn31534en30gla0_flexins3.0 Mme Integration.pdf
April 2020 7
I_o System Administration - Mss15.pdf
April 2020 2
Omgw_hardware Description.pdf
April 2020 22