Section: Create Bearer Response
Content: The Create Bearer Response message shall be sent on the S5/S8 interface by the SGW to the PGW, and on the S11 interface by the MME to the SGW as part of the Dedicated Bearer Activation procedure. The message shall also be sent on the S5/S8 interface by the SGW to the PGW and on the S4 interface by the SGSN to the SGW as part of Secondary PDP Context Activation procedure or the Network Requested Secondary PDP Context Activation procedure. The message shall also be sent on the S2a interface by the TWAN to the PGW as part of the Dedicated bearer activation in WLAN on GTP S2a and on the S2b interface by the ePDG to the PGW as part of the Dedicated S2b bearer activation with GTP on S2b. The message shall also be sent on the S5/S8 or S2a/S2b interface by the SGW or the TWAN/ePDG to the PGW and on the S11/S4 interface by the MME/S4-SGSN to the SGW as part of the Network-initiated IP flow mobility procedure or UE-initiated IP flow mobility procedure, as specified by 3GPP TS 23.161[ Network-Based IP Flow Mobility (NBIFOM); Stage 2 ]  [71]. Possible Cause values are specified in Table 8.4-1. Message specific cause values are: - "Request accepted". - "Request accepted partially". - "Context not found". - "Semantic error in the TFT operation". - "Syntactic error in the TFT operation". - "Semantic errors in packet filter(s)". - "Syntactic errors in packet filter(s)". "Unable to page UE". "UE not responding". "Unable to page UE due to Suspension". "UE refuses". - "Denied in RAT". - "Temporarily rejected due to handover/TAU/RAU procedure in progress". - "MME/SGSN refuses due to VPLMN Policy". - "UE is temporarily not reachable due to power saving". - " Request rejected due to UE capability". Table -1: Information Elements in a Create Bearer Response Table -2: Bearer Context within Create Bearer Response Table 7.2.4-3: Overload Control Information within Create Bearer Response