Section: Bearer Resource Command
Content: A Bearer Resource Command message shall be sent from a MME to a SGW and forwarded to PGW as a part of the UE requested bearer resource allocation procedure or UE requested bearer resource modification procedure (which is used also for a dedicated bearer deactivation or dedicated bearer activation), as specified by 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ]  [23]. The message shall also be sent on the S4 interface by a SGSN to a SGW and on the S5/S8 interface by a SGW to a PGW as part of the MS initiated PDP Context modification procedure, or secondary PDP context activation procedure. The message shall also be sent on the S11/S4 interface by an MME/S4-SGSN to a SGW and on the S5/S8 or S2a/S2b interface by a SGW or a TWAN/ePDG to a PGW as part of the UE-initiated IP flow mobility procedure and the UE requested IP flow mapping procedure, as specified by 3GPP TS 23.161[ Network-Based IP Flow Mobility (NBIFOM); Stage 2 ]  [71]. Table 7.2.5-1 specifies the presence of the IEs in the message. Table -1: Information Elements in a Bearer Resource Command NOTE: Depending on the protocol type on the S5/S8 interface, the SGW or the PGW will determine if the UE is requesting an Allocation/Modification 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. Table 7.2.5-2: Overload Control Information within Bearer Resource Command