3GPP 24.501 v20.0.0 — the document's own text
5.5.1.3.6 Mobility and periodic registration update for initiating an emergency PDU session not accepted by the network
Taught in 4. Inside TS 24.501, the document at the centre (CT1 — the group that writes what your phone says, overview).
If the mobility and periodic registration update request for initiating an emergency PDU session cannot be accepted by the network, the UE shall perform the procedures as described in clause 5.5.1.3.5. If the mobility and periodic registration update request for initiating an emergency PDU session fails due to receiving the AUTHENTICATION REJECT message, the UE shall perform the procedures as described in clauses 5.4.1.2.2.11, 5.4.1.2.3.1, 5.4.1.2.3A.1 or 5.4.1.3.5. Then if the UE is in the same selected PLMN where the last mobility and periodic registration update request was attempted, the UE shall:
- inform the upper layers of the failure of the procedure; or
NOTE 1: This can result in the upper layers requesting implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229 [14] can result in the emergency call being attempted to another IP-CAN.
- perform de-registration locally, if not de-registered already, and attempt initial registration for emergency services.
If the mobility and periodic registration update request for initiating an emergency PDU session fails due to abnormal case b) in clause 5.5.1.3.7, the UE shall perform the actions as described in clause 5.5.1.3.7 and inform the upper layers of the failure to access the network.
NOTE 2: This can result in the upper layers requesting implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229 [14] can result in the emergency call being attempted to another IP-CAN.
If the mobility and periodic registration update request for initiating an emergency PDU session fails due to abnormal cases c), d), e) or g) in clause 5.5.1.3.7, the UE shall perform the procedures as described in clause 5.5.1.3.7. Then if the UE is in the same selected PLMN where the last mobility and periodic registration update request was attempted, the UE shall:
- inform the upper layers of the failure of the procedure; or
NOTE 3: This can result in the upper layers requesting implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229 [14] can result in the emergency call being attempted to another IP-CAN.
- perform de-registration locally, if not de-registered already, and attempt initial registration for emergency services.