Attach Procedure (4G)

Service Model

The UE initiates an attach procedure.

Signaling Procedure

Figure 1 shows the UE-initiated attach procedure.

Figure 1 UE-initiated attach procedure

Description of the Signaling Procedure

The detailed UE-initiated attach procedure (GTP-C-based S5/S8) is as follows:

1. The UE sends the Attach Request message to the eNodeB. The message contains IMSI or
old GUTI, last visited TAI (if available), UE Core Network Capability, Attach Type, and
ESM message container (Request Type, PDN Type, Protocol Configuration Options, and
Ciphered Options Transfer Flag).
2. The eNodeB finds the MME based on the RRC parameter carrying the old GUMMEI and
Selected Network. If the MME does not connect to the eNodeB or the old GUMMEI is
unavailable, the eNodeB selects an MME by using the MME selection function. The
eNodeB forwards the Attach Request message to the new MME.
3. Optional: If the UE identifies itself by using the GUTI and attaches to a different MME
after detach, the new MME obtains the old MME/SGSN address by using the GUTI and
sends the Identification Request message to the old MME/SGSN to request for the
subscriber IMSI. The message contains old GUTI and complete Attach Request message.

The old SGSN/MME sends the Identification Response message to the new MME.

4. Optional: If UE information does not exists on the old SGSN/MME or new MME, the
new MME sends a Identity Request message to the UE to request for the IMSI.
5. Optional: The authentication policy determines whether authentication is required.

5a. If integrity of the Attach Request message in 1 is not protected or the integrity check
fails, an authentication procedure is required.

5b. The MME obtains the IMEI from the UE by using the Identity Request message. The
IMEI must be encrypted for transmission. The MME can send the ME Identity Check
Request message to the EIR. The message contains ME Identity and IMSI. The EIR
returns the result by using the ME Identity Check Ack message. Based on the returned
result, the MME determines whether to continue the attach procedure or reject the attach
request initiated by the UE.
6. Optional: If the UE configures the Ciphered Options Transfer Flag in the Attach Request
message, the MME can send the Ciphered Options Request message to the UE to request
for Ciphered Options such as PCO and APN.

When the UE subscribes to services of multiple PDNs, if the PCO contains subscriber
identification (such as subscriber name and password in the PAP/CHAP parameter), the
UE must return the APN in the Ciphered Options Response message.

7. Optional: If active bearer contexts of the UE exist on the new MME (for example, the
UE reattaches to the same MME when the detach is not completed), the new MME sends
the Delete Session Request message to the related GW to delete the bearer contexts. The
message contains LBI. The GW replies with the Delete Session Response message. The
message contains Cause.

If the PCRF is deployed, the P-GW initiates the IP-CAN session termination procedure to
notify the PCRF that resources have been released.

8. Optional: After the detach, if the UE attaches to a different MME on which no valid
subscription context of the UE exists or the IMEI is changed (for example, the subscriber
changes the mobile phone), the MME sends the Update Location Request message to the
HSS. The message contains MME Identity, IMSI, ME Identity, and MME Capabilities.
9. Optional: The HSS sends the Cancel Location Request message to the old MME. The
message contains IMSI and Cancellation Type.

The old MME returns the Cancel Location Answer message to the HSS (including the
IMSI) and deletes the MME context and bearer context.

10. Optional: If active bearer contexts of the UE exist on the old MME/SGSN, the old
MME/SGSN sends the Delete Session Request message to the related GW to delete the
bearer contexts. The message contains LBI. The GW replies with the Delete Session
Response message. The message contains Cause.

If the PCRF is deployed, the P-GW initiates the IP-CAN session termination procedure to
notify the PCRF that resources have been released.

11. Optional: The HSS sends the Update Location Answer message to the new MME. The
message contains IMSI and Subscription Data. The subscription data contains one or
multiple PDN subscription contexts. Each PDN subscription context contains an EPS
subscribed QoS profile and the subscribed APN-AMBR. If the UE accesses the network
by using an unsubscribed APN or the HSS rejects the Update Location request, the new
MME rejects the attach request of the UE.

NOTE:
 The Insert Subscriber Data procedure is deleted in the MME mobility management. The
MME constructs contexts for the UE by using the subscription data in the Update
Location Ack message.

12. The MME activates the default bearer by using the APN carried in the Attach Request
message or the default APN for subscription. The MME selects a P-GW based on the
APN configuration, selects the S-GW based on the network topology, and allocates an
EPS bearer ID for the default bearer. Then the MME sends the Create Session Request
message to create the default bearer. The message contains IMSI, MSISDN, MME TEID
for control plane, PDN GW address, PDN Address, APN, radio access technology (RAT)
type, and Default EPS Bearer QoS.
13. The S-GW creates a new EPS bearer in the EPS bearer list and sends the Create Session
Request message to the P-GW based on PDN GW address carried in 12. The message
contains IMSI, MSISDN, APN, Serving GW Address for the user plane, Serving GW
TEID of the user plane, Serving GW TEID of the control plane, RAT type, and Default
EPS Bearer QoS. The S-GW then caches all downlink data packets sent from the P-GW
and forwards the data packets after obtaining the eNodeB TEID from the Modify Bearer
Request message in 23.
14. Optional: If dynamic PCC is enabled, the P-GW initiates the IP-CAN session
establishment procedure to obtain the default PCC rules for the UE. If dynamic PCC is
disabled, the P-GW uses the locally configured policies.

14a. The P-GW sends the CCR-I message to the PCRF to instruct the PCRF to create the
IP-CAN session.

14b. The PCRF performs authorization and policy decision-making.

14c. The PCRF returns the CCA-I message to the P-GW, carrying the selected IP-CAN
bearer establishment mode.

NOTE:

The PCRF may provide the default charging mode and the following information:

o PCC Rules: executable policies related to the IP-CAN sessions

o Event Triggers: events that the P-GW must report to the PCRF

15. The P-GW creates a new EPS bearer in the EPS bearer context list and generates a new
charging ID. The P-GW can forward the user-plane PDU between the S-GW and PDN,
and starts charging. The P-GW returns the Create Session Response message to the S-
GW. The message contains PDN GW Address for the user plane, PDN GW TEID of the
user plane, PDN GW TEID of the control plane, PDN Type, PDN Address, EPS Bearer
Identity, and EPS Bearer QoS.
16. The S-GW returns the Create Session Response message to the new MME. The message
contains the PDN Type, PDN Address, Serving GW address for User Plane, Serving GW
TEID for User Plane, Serving GW TEID for control plane, EPS Bearer Identity, EPS
Bearer QoS, and PDN GW addresses and TEIDs.
17. The new MME sends the Attach Accept message to the eNodeB to request the
establishment of radio resources. The Attach Accept message is contained in the SI-
MME control message Initial Context Setup Request. If a new GUTI is allocated for the
new MME, the new GUTI is sent by using the Attach Accept message.
18. The eNodeB sends the RRC Connection Reconfiguration to the UE to allocate the air
interface resources. The RRC Connection Reconfiguration message carries the EPS radio
bearer ID and carries the Attach Accept message for the UE.
19. The UE sends the RRC Connection Reconfiguration Complete message to the eNodeB.
20. The eNodeB sends the Initial Context Setup Response message to the new MME,
carrying the eNodeB TEID and the address used for S1-U downlink transmission.
21. The UE sends the Direct Transfer message to the eNodeB, carrying the Attach Complete
message.
22. The eNodeB forwards the Attach Complete message to the new MME. The message
contains EPS Bearer Identity, NAS sequence number, and NAS-MAC.

After sending the Attach Complete message and obtaining a PDN address, the UE sends
uplink data packets to the eNodeB connected to the S-GW and P-GW.

23. The new MME sends the Modify Bearer Request message to the S-GW. The message
contains EPS Bearer Identity, eNodeB address, eNodeB TEID, and Handover Indication.

23a. If the message carries Handover Indication, the S-GW sends the Modify Bearer
Request message to the P-GW. The message contains Handover Indication and instructs
the P-GW to send the data packets from the non-3GPP network to the 3GPP IP access
system through tunnels and forward the data packets of the created default or dedicated
bearers to the S-GW.

23b. The P-GW returns the Modify Bearer Response message to the S-GW.

24. The S-GW returns the Modify Bearer Response message to the new MME. The message
contains EPS Bearer Identity.

After receiving the eNodeB TEID, the S-GW sends the cached downlink data packets.

25. Optional: After receiving the Modify Bearer Response message, the MME needs to send
the Notify Request message to the HSS, carrying the APN, P-GW Identity, and PLMN
information of the P-GW if the following conditions are met: The request type is not
handover, the UE can be handed over to non-3GPP access in the subscription data, and
the MME does not select the P-GW in the PDN subscription context specified by the
HSS.
26. Optional: The HSS stores the flag pairs of the APN and P-GW and sends the Notify
Response message to the MME.