Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 24.501  Word version:  17.5.0

Top   Top   Up   Prev   Next
1…   3…   4…   4.4…   4.4.3…   4.5…   4.5.3…   4.6…   4.7…   4.9…   4.15…   5…   5.2…   5.3…   5.3.2…   5.3.7…   5.3.19…   5.4…   5.4.1.3…   5.4.2…   5.4.4…   5.4.5…   5.4.6…   5.5…   5.5.1.2.4   5.5.1.2.5…   5.5.1.3…   5.5.1.3.4   5.5.1.3.5…   5.5.2…   5.6…   5.6.2…   6…   6.1.4…   6.2…   6.3…   6.3.2…   6.3.3…   6.4…   6.4.1.4…   6.4.2…   6.5…   7…   8…   8.2.9…   8.3…   9…   9.11.2…   9.11.2.10…   9.11.3…   9.11.3.4…   9.11.3.8…   9.11.3.14…   9.11.3.18C…   9.11.3.29…   9.11.3.33…   9.11.3.39…   9.11.3.45…   9.11.3.50…   9.11.3.53A…   9.11.3.68…   9.11.3.75…   9.11.4…   9.11.4.10…   9.11.4.13…   9.11.4.16…   9.11.4.30…   9.12   10…   A…   B…   C…   D…   D.6…   D.6.3…

 

A  Cause values for 5GS mobility managementWord‑p. 832

A.1  Causes related to UE identificationWord‑p. 832

Cause #3 - Illegal UE
This 5GMM cause is sent to the UE when the network refuses service to the UE either because an identity of the UE is not acceptable to the network or because the UE does not pass the authentication check.
Cause #6 - Illegal ME
This 5GMM cause is sent to the UE if the ME used is not acceptable to the network, e.g. on the prohibited list.
Cause #9 - UE identity cannot be derived by the network.
This 5GMM cause is sent to the UE when the network cannot derive the UE's identity from the 5G-GUTI or 5G-S-TMSI because of e.g. no matching identity/context in the network, failure to validate the UE's identity due to integrity check failure of the received message.
Cause #10 - Implicitly de-registered
This 5GMM cause is sent to the UE either if the network has implicitly de-registered the UE, e.g. after the implicit de-registration timer has expired, or if the 5GMM context data related to the subscription does not exist in the AMF e.g. because of a AMF restart, or because of a registration request for mobility or registration update is routed to a new AMF.
Up

A.2  Cause related to subscription optionsWord‑p. 832

Cause #5 - PEI not accepted
This cause is sent to the UE if the network does not accept an initial registration procedure for emergency services using a PEI.
Cause #7 - 5GS services not allowed
This 5GMM cause is sent to the UE when it is not allowed to operate 5GS services.
Cause #11 - PLMN not allowed
This 5GMM cause is sent to the UE if it requests service, or if the network initiates a de-registration request, in a PLMN where the UE, by subscription or due to operator determined barring, is not allowed to operate.
Cause #12 - Tracking area not allowed
This 5GMM cause is sent to the UE if it requests service, or if the network initiates a de-registration request, in a tracking area where the HPLMN or SNPN determines that the UE, by subscription, is not allowed to operate.
Cause #13 - Roaming not allowed in this tracking area
This 5GMM cause is sent to a UE which requests service, or if the network initiates a de-registration request, in a tracking area of a PLMN or SNPN which by subscription offers roaming to that UE but not in that tracking area.
Cause #15 - No suitable cells in tracking area
This 5GMM cause is sent to the UE if it requests service, or if the network initiates a de-registration request, in a tracking area where the UE, by subscription, is not allowed to operate, but when it should find another allowed tracking area in the same PLMN or an equivalent PLMN or the same SNPN.
Cause #27 - N1 mode not allowed
This 5GMM cause is sent to the UE if it requests service, or if the network initiates a de-registration request, in a PLMN or SNPN where the UE by subscription or operator policy, is not allowed to operate in N1 mode.
Cause #31 - Redirection to EPC required
This 5GMM cause is sent to the UE if it requests service in a PLMN where the UE by operator policy, is not allowed in 5GCN and redirection to EPC is required.
Cause #72 - Non-3GPP access to 5GCN not allowed
This 5GMM cause is sent to the UE if it requests accessing 5GCN over non-3GPP access in a PLMN or SNPN, where the UE by subscription, is not allowed to access 5GCN over non-3GPP access.
Cause #74 - Temporarily not authorized for this SNPN
This 5GMM cause is sent to the UE if it requests access, or if the network initiates a de-registration procedure, in a cell belonging to an SNPN for which the UE has no subscription to operate or for which the UE is not allowed to operate onboarding services.
Cause #75 - Permanently not authorized for this SNPN
This 5GMM cause is sent to the UE if it requests access, or if the network initiates a de-registration procedure, in a cell belonging to an SNPN with a globally-unique SNPN identity for which the UE either has no subscription to operate, the UE's subscription has expired or the UE is not allowed to operate onboarding services.
Cause #76 - Not authorized for this CAG or authorized for CAG cells only
This 5GMM cause is sent to the UE if the UE requests access or de-registration:
  1. in a CAG cell with a CAG-ID which is not included in the UE's "allowed CAG list" for the PLMN; or
  2. in a non-CAG cell, wherein the UE is only allowed to access 5GS via CAG cells
Cause #77 - Wireline access area not allowed
This 5GMM cause is sent to the 5G-RG or the W-AGF acting on behalf of the FN-CRG (or on behalf of the N5GC device) if the 5G-RG or the W-AGF acting on behalf of the FN-CRG (or on behalf of the N5GC device) request accessing 5GCN over a wireline access network belonging to a wireline access area, where the 5G-RG or the W-AGF acting on behalf of the FN-CRG (or on behalf of the N5GC device) are not allowed by subscription to access the 5GCN over the wireline access.
Cause #79 - UAS services not allowed
This 5GMM cause is sent to the UE if it requests accessing 5GCN with the Service-level device ID set to the CAA-level UAV ID in the Service-level-AA container IE for UAS services is not allowed according to the user's subscription data.
Up

A.3  Causes related to PLMN or SNPN specific network failures and congestion/authentication failuresWord‑p. 833

Cause #20 - MAC failure
This 5GMM cause is sent to the network if the USIM detects that the MAC in the AUTHENTICATION REQUEST message is not fresh.
Cause #21 - Synch failure
This 5GMM cause is sent to the network if the USIM detects that the SQN in the AUTHENTICATION REQUEST message is out of range.
Cause #22 - Congestion
This 5GMM cause is sent to the UE because of congestion in the network (e.g. no channel, facility busy/congested etc.).
Cause #23 - UE security capabilities mismatch
This 5GMM cause is sent to the network if the UE detects that the UE security capability does not match the one sent back by the network.
Cause #24 - Security mode rejected, unspecified
This 5GMM cause is sent to the network if the security mode command is rejected by the UE for unspecified reasons.
Cause #26 - Non-5G authentication unacceptable
This 5GMM cause is sent to the network in N1 mode if the "separation bit" in the AMF field of AUTN is set to 0 in the AUTHENTICATION REQUEST message (see TS 33.501).
Cause #28 - Restricted service area
This 5GMM cause is sent to the UE if it requests service in a tracking area of the 3GPP access or in an area of the wireline access, which is a part of the UE's non-allowed area or is not a part of the UE's allowed area.
Cause #43 - LADN not available
This 5GMM cause is sent to the UE if the user-plane resources of the PDU session are not established when the UE is located outside the LADN service area.
Cause #62 - No network slices available
This 5GMM cause is sent by the network if none of the requested network slice(s) in the registration request are allowed and there are no default network slice(s) configured in the network.
Cause #65 - Maximum number of PDU sessions reached
This 5GMM cause is used by the network to indicate that the procedure requested by the UE was rejected as the network has reached the maximum number of simultaneously active PDU sessions for the UE.
Cause #67 - Insufficient resources for specific slice and DNN
This 5GMM cause is sent by the network to indicate that the requested service cannot be provided due to insufficient resources for specific slice and DNN.
Cause #69 - Insufficient resources for specific slice
This 5GMM cause is sent by the network to indicate that the requested service cannot be provided due to insufficient resources for specific slice.
Cause #71 - ngKSI already in use
This 5GMM cause is sent to the network in N1 mode if the ngKSI value received in the AUTHENTICATION REQUEST message is already associated with one of the 5G security contexts stored in the UE.
Cause #73 - Serving network not authorized
This 5GMM cause is sent to the UE if the UE initiates registration towards a serving network and the serving network fails to be authorized by the UE's home network.
Cause #78 -PLMN not allowed to operate at the present UE location
This 5GMM cause is sent to the UE to indicate that the PLMN is not allowed to operate at the present UE location.
Cause #90 - Payload was not forwarded
This 5GMM cause is sent by the network to indicate that the requested service cannot be provided because payload could not be forwarded by AMF.
Cause #91 - DNN not supported or not subscribed in the slice
This 5GMM cause is sent by the network to indicate that the requested service cannot be provided because payload could not be forwarded by AMF because the DNN is not supported or not subscribed in the slice selected by the network if the UE did not indicate a slice, or the DNN is not supported or not subscribed in the slice indicated by the UE.
Cause #92 - Insufficient user-plane resources for the PDU session
This 5GMM cause is sent by the network to indicate that the requested service cannot be provided due to insufficient user-plane resources for the PDU session.
Up

A.4  Causes related to invalid messagesWord‑p. 835

Cause #95 - Semantically incorrect message
This 5GMM cause is used to report receipt of a message with semantically incorrect contents.
Cause #96 - Invalid mandatory information
This cause 5GMM indicates that the equipment sending this 5GMM cause has received a message with a non-semantical mandatory IE error.
Cause #97 - Message type non-existent or not implemented
This 5GMM cause indicates that the equipment sending this 5GMM cause has received a message with a message type it does not recognize either because this is a message not defined, or defined but not implemented by the equipment sending this 5GMM cause.
Cause #98 - Message type not compatible with protocol state
This 5GMM cause indicates that the equipment sending this 5GMM cause has received a message not compatible with the protocol state.
Cause #99 - Information element non-existent or not implemented
This 5GMM cause indicates that the equipment sending this 5GMM cause has received a message which includes information elements not recognized because the information element identifier is not defined or it is defined but not implemented by the equipment sending the 5GMM cause. However, the information element is not required to be present in the message in order for the equipment sending the 5GMM cause to process the message.
Cause #100 - Conditional IE error
This 5GMM cause indicates that the equipment sending this cause has received a message with conditional IE errors.
Cause #101 - Message not compatible with protocol state
This 5GMM cause indicates that a message has been received which is incompatible with the protocol state.
Cause #111 - Protocol error, unspecified
This 5GMM cause is used to report a protocol error event only when no other 5GMM cause in the protocol error class applies.
Up

Up   Top   ToC