Section: 6.5.3.4A Handling the maximum number of active EPS bearer contexts
Content: If the UE requests allocation of additional bearer resources, and the network has reached its maximum number of active EPS bearer contexts, then the network can: - reject the request if the network decides that it is necessary to allocate a dedicated EPS bearer context; or - accept the request by sending a MODIFY EPS BEARER CONTEXT REQUEST message. NOTE: An example of where the network will reject the request for allocation of additional bearer resources is when the request includes a GBR requirement while all existing bearers are non-GBR bearers, and the maximum number of active EPS bearer contexts has been reached at the network. If the maximum number of active EPS bearer contexts is reached at the UE (see clause 6.5.0) and the UE de-activates an active EPS bearer context prior to sending the request for additional bearer resources, then choosing which EPS bearer context to de-activate is a implementation specific, however the UE shall not deactivate a default EPS bearer context for emergency.