Section: 6.4.3.5 Abnormal cases in the UE
Content: Apart from the case described in clause 6.3.3, the following abnormal cases can be identified: a) Collision of UE requested bearer resource modification procedure and EPS bearer context modification procedure: If the UE receives a MODIFY EPS BEARER CONTEXT REQUEST message during the UE requested bearer resource modification procedure, the Procedure transaction identity IE of the MODIFY EPS BEARER CONTEXT REQUEST message is set to "No procedure transaction identity assigned" and the EPS bearer indicated in the MODIFY EPS BEARER CONTEXT REQUEST message is the EPS bearer that the UE had requested to modify, the UE shall abort internally the UE requested bearer resource modification procedure, and: - if the UE had initiated resource release for all the traffic flows for the bearer and the UE still needs to release the bearer (e.g. the TFT is empty due to error cases described in subclause 6.4.2.4 or subclause 6.4.3.4), the UE may proceed with the EPS bearer context modification procedure (i.e. respond with a MODIFY EPS BEARER CONTEXT ACCEPT message or a MODIFY EPS BEARER CONTEXT REJECT message) and deactivate the EPS bearer context locally without peer-to-peer signalling between the UE and the MME. In order to synchronize the EPS bearer context status with the MME, the UE may send a TRACKING AREA UPDATE REQUEST message that includes the EPS bearer context status IE to the MME; or - otherwise, the UE shall enter the state BEARER CONTEXT ACTIVE and proceed with the EPS bearer context modification procedure.