Section: 6.1.3.3.3 MS initiated PDP Context Modification not accepted by the network 6.1.3.3.3.1 General
Content: Upon receipt of a MODIFY PDP CONTEXT REQUEST message, the network may reject the MS initiated PDP context modification request by sending a MODIFY PDP CONTEXT REJECT message to the MS. The message shall contain a cause code that typically indicates one of the following: # 26: insufficient resources; # 30: activation rejected by GGSN, Serving GW or PDN GW; # 32: Service option not supported; # 37: QoS not accepted; # 41: semantic error in the TFT operation; # 42: syntactical error in the TFT operation; # 44: semantic errors in packet filter(s); # 45: syntactical errors in packet filter(s); # 48: request rejected, Bearer Control Mode violation; # 60: bearer handling not supported; or # 95 - 111: protocol errors. If upon the reception of a MODIFY PDP CONTEXT REQUEST message the network fails to re-establish the radio access bearer for a PDP context whose maximum bit rate in uplink and downlink is set to 0kbit/s, the network shall reply with a MODIFY PDP CONTEXT REJECT message with cause #26 "insufficient resources". If a TFT modification was requested and the requested TFT is not available, then the MODIFY PDP CONTEXT REJECT message shall be sent. The network shall reply with a MODIFY PDP CONTEXT REJECT message with cause #48 "request rejected, Bearer Control Mode violation", if - the selected Bearer Control Mode is 'MS/NW' and the MS requests to create a TFT for a PDP context that was established without TFT; - the selected Bearer Control Mode is 'MS/NW' and the MS requests to upgrade the QoS of a PDP context without downlink packet filters, unless uplink packet filters already exist for the PDP context and the MS requests with the same MODIFY PDP CONTEXT REQUEST message to create downlink packet filters ; - the selected Bearer Control Mode is 'MS/NW' and the MS requests to modify the QoS, but does not include a TFT with at least apacket filter identifiers to indicate which packet filters in the TFT that is associated with the QoS change; or - the selected Bearer Control Mode is 'MS/NW' and the MS requests to modify the QoS for a PDP context associated with a TFT containing packet filters established by both the MS and the network and the MS tries to modify other parameters than the bitrate parameters in the QoS profile of that PDP context. If a TFT modification was requested and the MS requests to modify or delete packet filters which were added by the network, then the MODIFY PDP CONTEXT REJECT message shall be sent. If the MS has requested to modify the QoS of a default PDP context, the network shall reply with a MODIFY PDP CONTEXT REJECT message with cause code "QoS not accepted". If the MS has requested to modify the PDP context of a LIPA PDN connection or SIPTO at the local network PDN connection, then the network shall reply with a MODIFY PDP CONTEXT REJECT message with cause code "bearer handling not supported". The TFT in the request message is checked by the network for different types of TFT IE errors as specified in subclause 6.1.3.3.4. The network may include a Back-off timer value IE in the MODIFY PDP CONTEXT REJECT message. The network shall not include the SM cause value #26 "insufficient resources" in the MODIFY PDP CONTEXT REJECT message due to APN based congestion control being active. If the Back-off timer value IE is included and the SM cause value is not #26 "insufficient resources", the network may include the Re-attempt indicator IE to indicate whether the MS is allowed to attempt a bearer resource modification procedure in the PLMN for the same in S1 mode, and whether another attempt in A/Gb and Iu mode or in S1 mode is allowed in an equivalent PLMN. Upon receipt of a MODIFY PDP CONTEXT REJECT message, the MS shall stop timer T3381 and enter the state PDP-ACTIVE.