“Request accepted” is returned when the GTPv2 entity has accepted a control plane request.
“Context Not Found” is used in the response message by a GTP entity when it receives a message for which it does not
have context, e.g. TEID-C or EBI is not known.
“Context Not Found” may also be used by the PGW during UE requested PDN connectivity procedure while non-3GPP
to 3GPP handover, if the request corresponds to the handover of the PDN connection which does not exist with the
PGW.
“Service not supported” is used by the GTP entity when it receives a message, which corresponds to a feature or a
service which is not supported by the node.
“Service denied” is used when the requested service cannot be granted.
“System failure” is used by the GTP entity to indicate a generic error condition.
“No resources available” is used by the GTP entity to indicate the temporary unavailability of the resource(s) to process
the received request.
“Semantic error in the TFT operation”, “Syntactic error in the TFT operation”, “Semantic errors in packet filter(s)”,
“Syntactic errors in packet filters(s)”, “UE context without TFT already activated”, “Semantic error in the TAD
operation” and “Syntactic error in the TAD operation” are indications of error cases involving TFT(s)/TAD(s) as
specified in subclause 7.7.11 in this specification.
“Missing or unknown APN” is used by the PGW when it does not support the Access Point Name, received in Create
Session Request message.
“Relocation failure” is used by the target MME/S4-SGSN to indicate the source MME/S4-SGSN that the relocation has
failed.
“Denied in RAT” is used by the GTP entity to indicate that the requested service is not accepted in the RAT.
“Preferred PDN type not supported” is used by the PGW to indicate that the PDN type received in the Create Session
Request message is not supported by the PGW for the PDN corresponding to the received Access Point Name.
“Protocol type not supported” is used by the SGW to indicate that the S5/S8 protocol type requested by the MME/S4-
SGSN is not supported by it.
“UE not responding” is used by the MME/S4-SGSN to indicate that the UE is not responding to the request initiated by
the network, e.g. Paging.
“UE refuses” is used by the GTP entity to indicate that the UE, without specifying further detail, rejected the request
from the network.
“Unable to page UE” is used by the MME/S4-SGSN to indicate its inability to page the UE, temporarily.
“User authentication failed” is used by the GTP entity to indicate that the request is rejected due to failure in
authentication/security procedure.
“APN access denied – no subscription” is used to indicate that the PGW has denied the user access to an APN because a
subscription is required, but the subscriber does not have the necessary subscription.
“Remote peer not responding” is used by the SGW for the messages spanning through two interfaces. This cause value
is returned by the SGW to the MME/S4-SGSN or PGW in a response message where no response message is received
from the PGW or MME/S4-SGSN.
“Collision with network initiated request” is used by the PGW to indicate that the UE-initiated bearer resource
allocation/modification request is rejected since the PGW has requested a bearer resource allocation/modification for
the same service using a network-initiated procedure.
“Unable to page UE due to Suspension” is used by the MME/S4-SGSN to indicate that the UE has not been paged
because the bearers of the UE are in a suspended state.
“APN Restriction type Incompatible with currently active PDN connection” is used by the PGW to indicate that the
newly requested PDN connection has APN restriction value that is not compatible with the currently active PDN
connection(s)’s APN restriction value(s).
“Context Not Found” is used in the response message by a GTP entity when it receives a message for which it does not
have context, e.g. TEID-C or EBI is not known.
“Context Not Found” may also be used by the PGW during UE requested PDN connectivity procedure while non-3GPP
to 3GPP handover, if the request corresponds to the handover of the PDN connection which does not exist with the
PGW.
“Service not supported” is used by the GTP entity when it receives a message, which corresponds to a feature or a
service which is not supported by the node.
“Service denied” is used when the requested service cannot be granted.
“System failure” is used by the GTP entity to indicate a generic error condition.
“No resources available” is used by the GTP entity to indicate the temporary unavailability of the resource(s) to process
the received request.
“Semantic error in the TFT operation”, “Syntactic error in the TFT operation”, “Semantic errors in packet filter(s)”,
“Syntactic errors in packet filters(s)”, “UE context without TFT already activated”, “Semantic error in the TAD
operation” and “Syntactic error in the TAD operation” are indications of error cases involving TFT(s)/TAD(s) as
specified in subclause 7.7.11 in this specification.
“Missing or unknown APN” is used by the PGW when it does not support the Access Point Name, received in Create
Session Request message.
“Relocation failure” is used by the target MME/S4-SGSN to indicate the source MME/S4-SGSN that the relocation has
failed.
“Denied in RAT” is used by the GTP entity to indicate that the requested service is not accepted in the RAT.
“Preferred PDN type not supported” is used by the PGW to indicate that the PDN type received in the Create Session
Request message is not supported by the PGW for the PDN corresponding to the received Access Point Name.
“Protocol type not supported” is used by the SGW to indicate that the S5/S8 protocol type requested by the MME/S4-
SGSN is not supported by it.
“UE not responding” is used by the MME/S4-SGSN to indicate that the UE is not responding to the request initiated by
the network, e.g. Paging.
“UE refuses” is used by the GTP entity to indicate that the UE, without specifying further detail, rejected the request
from the network.
“Unable to page UE” is used by the MME/S4-SGSN to indicate its inability to page the UE, temporarily.
“User authentication failed” is used by the GTP entity to indicate that the request is rejected due to failure in
authentication/security procedure.
“APN access denied – no subscription” is used to indicate that the PGW has denied the user access to an APN because a
subscription is required, but the subscriber does not have the necessary subscription.
“Remote peer not responding” is used by the SGW for the messages spanning through two interfaces. This cause value
is returned by the SGW to the MME/S4-SGSN or PGW in a response message where no response message is received
from the PGW or MME/S4-SGSN.
“Collision with network initiated request” is used by the PGW to indicate that the UE-initiated bearer resource
allocation/modification request is rejected since the PGW has requested a bearer resource allocation/modification for
the same service using a network-initiated procedure.
“Unable to page UE due to Suspension” is used by the MME/S4-SGSN to indicate that the UE has not been paged
because the bearers of the UE are in a suspended state.
“APN Restriction type Incompatible with currently active PDN connection” is used by the PGW to indicate that the
newly requested PDN connection has APN restriction value that is not compatible with the currently active PDN
connection(s)’s APN restriction value(s).
As specified in sub-clause 5.3.1.1 in 3GPP TS 23.401 [3] and sub-clause 9.2.1 in 3GPP TS 23.060 [35], the cause value
“New PDN type due to single address bearer only” indicates that the MS has requested PDN type IPv4v6 and both IPv4
and IPv6 addressing is possible in the PDN but the Dual Address Bearer Flag of the Indication IE is set to 0 or the
Indication IE is absent, or only single IP version addressing is possible in the PDN.
“PGW not responding” is used by the SGW in PGW Restart Notification to indicate that the peer PGW has failed and
not restarted as specified in subclause 7.9.5.
“UE context without TFT already activated” is used by the PGW in the Bearer Resource Failure Indication message to
indicate that the PGW has received the Bearer Resource Command message without TAD IE in the secondary PDP
Context Activation procedure.
“Target access restricted for the subscriber” is used by the MME/SGSN in the Context Response message to indicate
that the target access is prohibited for the subscriber, based on the subscription profile.
“P-TMSI Signature mismatch” is used by the SGSN or MME in the Identification Response and Context Response
message if the P-TMSI Signature stored in the old SGSN or MME does not match the value sent by the UE via the new
SGSN or MME.