Cisco ASR 5000 series Product Overview page 882

▀ How MME Works
Figure 208. Subscriber Registration Setup Message Flow
Random Access
procedure
Attach Request
2
(user identity)
Authentication AKA procedure
RB_Est-Request
14
(Attach Accept)
RB_Est-Resp
(Attach Completet)
17
1. UE and eNodeB performs Random Access procedure.
2. After Random Access procedure completion, UE sends Attach Request with user identity to eNodeB.
3. The eNodeB forwards the Attach Request to MME
4. MME starts Authentication procedure with eNodeB and UE.
5. Once UE get authenticated MS sends Update Location Request to HSS with user IMSI derived during
Authentication procedure.
6. Once user get validated at HSS with IMSI, HSS sends Insert Subscriber Data Request to MME providing
subscriber profile and service subscription information to MME.
7. MME sends Create Bearer Request to Serving Gateway.
8. The S-GW forwards the request to P-GW.
9. P-GW reserves the EPS bearer and sends Create Bearer Response to the S-GW and establishes the EPS bearer
with S-GW for this user.
10. Once S-GW receives the Create Bearer Response from P-GW it reserves the EPS bearer and sends Create Bearer
Response to the MME and establishes the EPS bearer with MME for this user.
▄ Cisco ASR 5000 Series Product Overview
MME
eNodeB
1
Attach Request
3
(user identity)
Update location
4
Insert subscriber data
6
Insert subscriber
data Ack
Update location
8
9
Attach Accept
13
(new S-TMSI)
15
Attach Complete
16
(Ini Context Setup)
HSS
Serving GW
5
(IMSI)
7
Ack
Create Bearer Request
Create Bearer Response
12
17
Mobility Management Entity Overview
PDN GW
Create Bearer Request
10
Create Bearer Response
11
17
Enterprise
Internet
17
OL-22938-02