You are on page 1of 8

Dedicated bearer activation in combination with the default bearer activation at attach or UE requested PDN connectivity It is possible for

the PDN GW to initiate the activation of dedicated bearers as part of the attach procedure or as part of the UE requested PDN connectivity procedure over E UTRAN. However, the result of the dedicated bearer activation procedure is separate from the Attach procedure, meaning that the result of the Attach procedure is not dependent on whether the Dedicated bearer activation procedure succeeds or not. On the other hand, the dedicated bearer activation may only be regarded as successful if the Attach procedure completes successfully. The messages of the Dedicated bearer activation can be sent together with the messages of the Attach procedure or of the UE requested PDN connectivity procedure (i.e. Attach accept or PDN Connectivity Accept). If the MME has sent an Attach Accept message towards the eNodeB, and then the MME receives a Create Bearer Request before the MME receives the Attach Complete message, the MME shall wait for the Attach procedure to complete before the MME continues with Dedicated Bearer Activation procedure. It is possible that multiple dedicated bearers can simultaneously be activated in the signalling flow shown below.

Figure describes the activation of dedicated bearer(s) in combination with the default bearer activation either as part of the Attach procedure (with specific steps 1a, 7a, 10a) or as part of the UE requested PDN connectivity procedure (with specific steps 1b, 7b, 10b). 5. (On the P-GW-S-GW interface) Create Session Response message of the Attach procedure or UE-requested PDN connectivity procedure is combined with Create Bearer Request message of the Dedicated Bearer Activation Procedure

6.(On the S-GW-MME interface) Create Session Response message of the Attach procedure or UE-requested PDN connectivity procedure is combined with the Create Bearer Request message of the Dedicated Bearer Activation Procedure 7a. For Attach procedure: If the MME receives a Create Session Response message combined with a Create Bearer Request message, the MME shall send the S1-AP Initial Context Setup Request message to the eNodeB, including the NAS parts for both the Attach Accept message of the Attach procedure and the Bearer Setup Request of the Dedicated Bearer Activation Procedure. NOTE: The MME shall not send a Bearer Setup Request message of a new Dedicated Bearer Activation procedure to the eNodeB before sending the Attach Accept message of the Attach procedure to the eNodeB. If the MME has already sent the Attach Accept message of the Attach procedure to the eNodeB, the MME shall wait for the Attach Complete message to arrive before sending a separate Bearer Setup Request of a Dedicated Bearer Activation procedure. 7b. For UE requested PDN connectivity procedure: If the MME receives a Create Session Response message combined with a Create Bearer Request message, the MME shall send the S1AP Bearer Setup Request message to the eNodeB, including the NAS parts for both the PDN Connectivity Accept message and the Bearer Setup Request of the Dedicated Bearer Activation Procedure. 8-9. The radio bearer establishment of the default and dedicated bearer(s) is performed in the same RRC message. 10a. For Attach procedure: The eNodeB sends the S1-AP Initial Context Setup Response message to the MME. 10b. For UE requested PDN connectivity procedure: The eNodeB sends the S1-AP Bearer Setup Response message to the MME. 11. For the Attach procedure: The UE sends the eNodeB a Direct Transfer message containing the Attach Complete (Session Management Response for the Default Bearer) message as response of the attach procedure, and Direct Transfer messages containing the Session Management Responses of the dedicated bearer setup procedure. For the UE requested PDN connectivity procedure: The UE NAS layer builds a PDN Connectivity Complete (Session Management Response) for the Default Bearer Activation and Dedicated Bearer Activation Procedures. The UE then sends Direct Transfer (PDN Connectivity Complete) message to the eNodeB. The NAS messages to establish the EPS bearers shall be handled individually by the UE and be sent in separate RRC Direct Transfer messages.

12. The eNodeB sends an Uplink NAS Transport message to the MME, which contains the NAS messages from the RRC message in step 11. There may be multiple Uplink NAS Transport messages when the UE sends multiple RRC messages containing NAS messages in step 11. 13. Upon reception of the response messages in both step 10 and step 12, the Modify Bearer Request message of the Attach procedure or UE requested PDN connectivity procedure is combined with the Create Bearer Response message of the Dedicated Bearer Activation Procedure. After that, the Serving GW continues with sending a Create Bearer Response message to the PDN GW.

This document will explain about the new bearer allocation on top of default bearer. First we will cover the default bearer creation and then we will cover the allocation of dedicated bearer.

Default Bearer Creation:


1. 2. Here I will elaborate more on GTP perspective for creating default bearer. Please refer the following points when attach request initiated by UE, UE initiate a Attach Request towards eNB with the UE information such as IMSI, UE Core Network Capability, Attach Type, NAS information, RRC parameters etc. ENB derives MME from RRC parameter and forward the Attach Request i.e. S1-MME message (Initial UE Message) towards MME with the Selected Network, CSG ID (Common subscriber group), and TAI+ECGI information. MME will initiate a GTP-C signaling message towards S-GW to proceed with attach. This will help the EPS (Evolved Packet system) to create default bearer in the network. MME initiates Create Session Request with the following important information IMSI MMEs F-TEID for control plane (MME IP + TEID (Tunnel ID)). This will be used for future communication with MME. PGWs G-TEID for Control plane (P-GW IP + TEID (here it will be zero)). This will be used by S-GW to communicate with P-GW. Bearer Context to be created. This is the bearer information to be created at MME. This will include the default bearer ID with TFT, QOS. APN Recovery S-GW will process the Create Session Request initiated by MME and create the UE, eNB, and MME context and modify the Create session Request and send it to P-GW. Create session Request from S-GW will have the following important information IMSI S-GWs F-TEID for control plane (S-GW IP + TEID (Tunnel ID)). This will be used for future communication with S-GW. Bearer Context to be created. This is the bearer information to be created at S-GW. This will include the default bearer ID with TFT, QOS, S-GW user plane F-TEID APN Recovery

3.

a. b. c. d. e. f. 4.

a. b. c. d. e.

Once P-GW receives Create Session Request , it will create UE, S-GW context and communicate with PCRF for QOS and APN resolve. If that succeed, P-GW will respond back with Create Session Response towards S-GW. The Create Session Response will have following information: a. Cause. This value will be used for Success/failure for the Create Session Request. b. P-GWs F-TEID for control plane (P-GWs IP + TEID ). This information will be used for future signaling message communication with P-GW. c. PAA (PDN Address Allocation). d. Bearer Contexts Created. This information element will have Default EPS bearer ID, P-GW user plane F-TEID, TFT, Bearer Qos, Charging ID. e. Charging GW f. Recovery 6. Once S-GW receives Create Session Response, it will create P-GW context and forward/process the Create Session Response with the following information. a. Cause. This value will be used for Success/failure for the Create Session Request. b. S-GWs F-TEID for control plane (S-GWs IP + TEID ). This information will be used for future signaling message communication with S-GW. c. PAA (PDN Address Allocation). d. Bearer Contexts Created. This information element will have Default EPS bearer ID, P-GW user plane F-TEID, TFT, Bearer Qos, Charging ID. e. Charging GW f. Recovery 7. Now if downlink data comes from PDN it will get buffered in S-GW as user plane eNB information shared with S-GW. 8. MME shares the eNB information as part of attach procedure with Modify Bearer request with the following information a. Bearer Contexts to be modified. This IE will have eNBs user plane F-TEID. 9. Once S-GW receives the Modify Bearer request with eNB information. It will respond back with Modify bearer Response. 10. Now downlink data can be sent to eNB because S-GW has the information of eNB. 11. But uplink data can possible after step 6. 5.

Dedicated Bearer Allocation:


Once the default bearer created the UE or network can opted for the dedicated bearer. To get more service from network, UE or NW may initiate the dedicated bearer allocation. 1. UE Initiated Dedicated Bearer Allocation: UE Request Bearer Resource Allocation message towards MME for allocating dedicated bearer. b. MME sends Bearer Resource Command with the default bearer ID to S-GW for a dedicated bearer allocation. That means MME commands to the P-GW to initiate a Create Bearer Request to start the dedicated bearer allocation. This command will provide the default bearer ID. This message will have the following information: I. EBI i.e. Default EPS bearer ID. II. PTI III. TAD (TFT rule + TFT ID) c. Once S-GW receives the Bearer Resource Command then the SGW or the PGW will determine if the UE is requesting an Allocation operation of bearer resources for a traffic flow aggregate based on the TFT operation code and the packet filter ID value in the Traffic Aggregate (TAD) IE and/or the presence of the EPS Bearer ID IE. d. PCRF entity has to check the APN and QoS details for bearer approval. a.

e. After P-GW received Bearer Resource Command, it will initiate Create Bearer Request towards S-GW for dedicated bearer allocation. This request will have the following information. I. EBI i.e. Default EPS bearer ID. II. Bearer Context. This IE will contain the dedicated bearer id with value 0 (as MME is going to allocate the bearer ID), TFT, P-GW user plane F-TEID etc. f. Once S-GW receives Create Bearer Request, it will propagate the message towards MME for dedicated bearer allocation. g. MME does a bearer setup request with eNB after receiving Create Bearer request from S-GW. h. Once the bearer setup request completes, MME sends back Create Bearer Response with the following information. I. Cause. This is for success or failure. II. Bearer Contexts. EBI. This ID will be assigned by MME with a value. eNB User plane F-TEID etc. i. Once S-GW receives Create Bearer Response then it update the UE,eNB and MME context for the dedicated bearer and sends the Create Bearer Response towards P-GW.

2. NW Initiated Dedicated Bearer Allocation: If the service provided by NW is not sufficient in a bearer then P-GW opted for dedicated bearer initiation. a. P-GW will initiate Create Bearer Request towards S-GW for dedicated bearer allocation. This request will have the following information. I. EBI i.e. Default EPS bearer ID. II. Bearer Context. This IE will contain the dedicated bearer id with value 0 (as MME is going to allocate the bearer ID), TFT, P-GW user plane F-TEID etc.

b. Once S-GW receives Create Bearer Request, it will propagate the message towards MME for dedicated bearer allocation. c. MME does a bearer setup request with eNB after receiving Create Bearer request from S-GW. d. Once the bearer setup request completes, MME sends back Create Bearer Response with the following information. I. Cause. This is for success or failure. II. Bearer Contexts. EBI. This ID will be assigned by MME with a value. eNB User plane F-TEID etc. e. Once S-GW receives Create Bearer Response then it update the UE,eNB and MME context for the dedicated bearer and sends the Create Bearer Response towards P-GW