6.7 Reception of an ESM STATUS message by an ESM entity

24.3013GPPNon-Access-Stratum (NAS) protocol for Evolved Packet System (EPS)Release 18Stage 3TS

The purpose of the sending of the ESM STATUS message is to report at any time certain error conditions detected upon receipt of ESM protocol data. The ESM STATUS message can be sent by both the MME and the UE (see example in figure 6.7.1).

If the ESM entity of the UE receives an ESM STATUS message the UE shall take different actions depending on the received ESM cause value:

#43 (Invalid EPS bearer identity);

The UE shall abort any ongoing ESM procedure related to the received EPS bearer identity, stop any related timer, and deactivate the corresponding EPS bearer context locally (without peer to peer signalling between the UE and the MME).

#81 (Invalid PTI value);

The UE shall abort any ongoing ESM procedure related to the received PTI value and stop any related timer.

#97 (Message type non-existent or not implemented);

The UE shall abort any ongoing ESM procedure related to the PTI or EPS bearer identity and stop any related timer.

On receipt of an ESM STATUS message with any other ESM cause value no state transition and no specific action shall be taken as seen from the radio interface, i.e. local actions are possible.

If the ESM entity of the MME receives an ESM STATUS message the MME shall take different actions depending on the received ESM cause value:

#43 (Invalid EPS bearer identity);

The MME shall abort any ongoing ESM procedure related to the received EPS bearer identity, stop any related timer, and deactivate the corresponding EPS bearer context locally (without peer to peer signalling between the MME and the UE).

#81 (Invalid PTI value);

The MME shall abort any ongoing ESM procedure related to the received PTI value and stop any related timer.

#97 (Message type non-existent or not implemented);

The MME shall abort any ongoing ESM procedure related to the PTI or EPS bearer identity and stop any related timer.

The local actions to be taken by the MME on receipt of an ESM STATUS message with any other ESM cause value are implementation dependent.

Figure 6.7.1: ESM status procedure