The cause code value in the GTPv2 message can indicate what happened between MME, SGW, and PGW so as to simplify the troubleshooting process.
The cause value must be included in the GTPv2 message response. In the message response, the Cause value indicates the acceptance or rejection of the corresponding message request. Cause value indicates an explicit reason for the refusal.
Cause values can also be included in message requests. In the request message, the Cause value indicates the reason for the request.
Cause code value 3GPP TS 29.274 V17.3.0 (2021-09)
| Cause value (decimal) | Meaning | Description |
|---|---|---|
| 0 | Reserved. Shall not be sent and if received the Cause shall be treated as an invalid IE | |
| ### | ### | Request / Initial message |
| 1 | Reserved | |
| 2 | Local Detach | ""Local Detach"" indicates that this detach is local to the MME/SGSN and so the associated SGSN/MME registration where the ISR is activated shall not be detached. The MME/SGSN that receives this message including this Cause value of ""Local Detach"" only deactivates the ISR. This Cause value shall be included in the procedures: - MME/SGSN-initiated Detach Procedure in case of implicit detach. |
| 3 | Complete Detach | ""Complete Detach"" indicates both the MME registration and the SGSN registration that the ISR is activated for, shall be detached. This ""Complete Detach"" Cause value shall be included in the procedures: - UE-initiated Detach Procedure. - MME/SGSN-initiated Detach Procedure in case of explicit detach. For the purpose of SGs handling, the SGSN shall include Detach Type in the Detach Notification message for ""Complete Detach"" when the UE is combined IMSI/EPS attached and the ISR is activated. |
| 4 | RAT changed from 3GPP to Non-3GPP | In the PGW initiated bearer deactivation procedure for the default bearer, the PGW may include the Cause IE in the Delete Bearer Request with values ""RAT changed from 3GPP to Non-3GPP"", ""Reactivation requested"" or ""Reactivation disallowed to APN"". This IE shall be sent on S5/S8 and S11/S4 interfaces if the message is caused by a handover with or without optimization from 3GPP to non-3GPP (see clause 9.3.2 in 3GPP TS 23.402 [45] and clause 5.4.4.1 in 3GPP TS 23.401 [3], respectively). In this case the Cause value shall be set to ""RAT changed from 3GPP to Non-3GPP"". |
| 5 | ISR deactivation | This IE shall also be sent on S11/S4 interfaces when the SGW requests to delete all bearer contexts for the given UE in an MME or S4-SGSN due to ISR deactivation, and the Cause value shall be set to "ISR deactivation". |
| 6 | Error Indication received from RNC/eNodeB/S4-SGSN/MME | If SGW receives an Error Indication from eNodeB/RNC/S4-SGSN/MME, the SGW shall send the Cause IE with value "Error Indication received from RNC/eNodeB/S4-SGSN/MME" to MME/S4-SGSN as specified in 3GPP TS 23.007 [17]. |
| 7 | IMSI Detach Only | ""IMSI Detach only"" indicates that combined IMSI/EPS attached UE initiates IMSI only GPRS detach from non-GPRS service as specified in clause 4.7.4.1, 3GPP TS 24.008 [5], and both the SGSN/MME registration shall be remained. The MME shall perform explicit IMSI detach from non-EPS service for the SGs handling purpose, which is specified in clause 5.5, 3GPP TS 29.118 [22]. This ""IMSI Detach only"" Cause value shall be included in the procedures: - UE-initiated Detach Procedure for GERAN/UTRAN for ""IMSI Detach only"". |
| 8 | Reactivation Requested | In the PGW initiated bearer deactivation procedure for the default bearer, the PGW may include the Cause IE in the Delete Bearer Request with values "RAT changed from 3GPP to Non-3GPP", "Reactivation requested" or "Reactivation disallowed to APN". |
| 9 | PDN reconnection to this APN disallowed | This IE may be sent by a PGW on S5/S8 during PGW initiated bearer deactivation procedures for the default bearer with values of "Reactivation requested" or " PDN reconnection to this APN disallowed" or "Multiple accesses to a PDN connection not allowed" (see clause 8.4 for details). |
| 10 | Access changed from Non-3GPP to 3GPP | This IE shall be sent on the S2a/S2b interface if the message is caused by handover from non-3GPP to 3GPP. In this case the Cause value shall be set to "Access changed from Non-3GPP to 3GPP". |
| 11 | PDN connection inactivity timer expires | "PDP connection inactivity timer expires" is used by the PGW in Delete Bearer Request(s) to indicate that all the bearer(s) for the emergency PDN connection are deleted upon the inactivity timer expiry as specified in 3GPP TS 23.203 [48]. |
| 12 | PGW not responding | "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 clause 7.9.5. |
| 13 | Network Failure | "Network failure" is used by the SGSN or MME in the Delete Session Request to indicate that the message is sent due to a network problem. |
| 14 | QoS parameter mismatch | "QoS parameter mismatch" is used by the SGSN or MME in the Delete Session Request to indicate that the PDN connection can not be established due to a QoS parameter mismatch. |
| 15 | EPS to 5GS Mobility | "EPS to 5GS Mobility" is used by the PGW, and it indicates that PGW initiated bearer deactivation procedure is due to EPS to 5GS mobility procedures. |
| ### | ### | Acceptance in a Response / triggered message. See NOTE 1. |
| 16 | Request accepted | "Request accepted" is returned when the GTPv2 entity has accepted a control plane request. |
| 17 | Request accepted partially | |
| 18 | New PDN type due to network preference. | As specified in clause 5.3.1.1 in 3GPP TS 23.401 [3] and clause 9.2.1 in 3GPP TS 23.060 [35], the cause value "New PDN type due to network preference" indicates that the UE has requested PDN type IPv4v6 and only IPv4 or IPv6 address is allowed for the PDN based on PGW operator policy. |
| 19 | New PDN type due to single address bearer only. | As specified in clause 5.3.1.1 in 3GPP TS 23.401 [3] and 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. |
| 20 to 63 | Spare. This value range shall be used by Cause values in an acceptance response/triggered message | |
| ### | ### | Rejection in a Response / triggered message. See NOTE 1. |
| 64 | Context Not Found | ""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. When ""Context Not Found"" is received at Bearer Context IE level, it means the bearer context is unknown in the peer. When ""Context Not Found"" is received at message level together with a known TEID-C in the GTPv2-C header in the response message, this indicates some bearer contexts are not known in the peer; the sender of the request message should further determine, based on the bearer context(s) included in the request message, that: - if the default bearer is unknown, this means the PDN connection is not known in the peer; - if one or more dedicated bearers are unknown, this means only those dedicated bearer contexts are not known in the peer. ""Context Not Found"" may be used by the PGW in the Create Session Response message during the non-3GPP to 3GPP access handover procedures, if the request corresponds to the handover of a PDN connection which does not exist in the PGW. ""Context Not Found"" may be used by the PGW in the Create Session Response message during the 3GPP to non-3GPP access handover procedures, if the request corresponds to the handover of a PDN connection which does not exist in the PGW. |
| 65 | Invalid Message Format | |
| 66 | Version not supported by next peer | |
| 67 | Invalid length | if a GTP entity receives a Request message within an IP/UDP packet of a length that is inconsistent with the value specified in the Length field of the GTP header, then the receiving GTP entity should log the error and shall send the Response message with Cause IE value set to "Invalid Length". |
| 68 | Service not supported | "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. |
| 69 | Mandatory IE incorrect | If a GTP entity receives an information element with a value which is shown as reserved, it shall treat that information element as invalid and should log the error. If the invalid IE is received in a Request, and it is a mandatory IE or a verifiable conditional IE, the GTP entity shall send a response with Cause set to "Mandatory IE incorrect " together with a type and instance of the offending IE. |
| 70 | Mandatory IE missing | A GTP entity shall check if all mandatory IEs are present in the received Request message. Apart from Echo Request message, if one or more mandatory information elements are missing in the received Request message, the GTP entity should log the error and shall send a Response message with Cause IE value set to ""Mandatory IE missing"" together with the type and instance of the missing mandatory IE. If a GTP entity receives a Response message with Cause IE value set to ""Mandatory IE missing"", it shall notify its upper layer. |
| 71 | Shall not be used. See NOTE 2 and NOTE 3. | |
| 72 | System failure | "System failure" is used by the GTP entity to indicate a generic error condition. |
| 73 | No resources available | "No resources available" is used by the GTP entity to indicate the temporary unavailability of the resource(s) to process the received request. |
| 74 | Semantic error in the TFT operation | "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 clause 7.7.11 in this specification.' |
| 75 | Syntactic error in the TFT operation | "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 clause 7.7.11 in this specification.' |
| 76 | Semantic errors in packet filter(s) | "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 clause 7.7.11 in this specification.' |
| 77 | Syntactic errors in packet filter(s) | "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 clause 7.7.11 in this specification.' |
| 78 | Missing or unknown APN | "Missing or unknown APN" is used by the PGW when it does not support the Access Point Name, received in Create Session Request message. |
| 79 | Shall not be used. See NOTE 2 and NOTE 3. | |
| 80 | GRE key not found | |
| 81 | Relocation failure | "Relocation failure" is used by the target MME/S4-SGSN to indicate the source MME/S4-SGSN that the relocation has failed. |
| 82 | Denied in RAT | "Denied in RAT" is used by the GTP entity to indicate that the requested service is not accepted in the RAT. |
| 83 | Preferred PDN type not supported | "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. |
| 84 | All dynamic addresses are occupied | |
| 85 | UE context without TFT already activated. See NOTE 6. | "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. |
| 86 | Protocol type not supported | "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. |
| 87 | UE not responding. See NOTE 7. | "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. |
| 88 | UE refuses | "UE refuses" is used by the GTP entity to indicate that the UE, without specifying further detail, rejected the request from the network. |
| 89 | Service denied. See NOTE 7. | "Service denied" is used when the requested service cannot be granted. |
| 90 | Unable to page UE | "Unable to page UE" is used by the MME/S4-SGSN to indicate its inability to page the UE, temporarily. |
| 91 | No memory available | |
| 92 | User authentication failed | "User authentication failed" is used by the GTP entity to indicate that the request is rejected due to failure in authentication/security procedure. |
| 93 | APN access denied – no subscription | "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. |
| 94 | Request rejected (reason not specified) | |
| 95 | P-TMSI Signature mismatch | "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. |
| 96 | IMSI/IMEI not known | ""IMSI/IMEI not known"", to be used when the UE is not registered in the MME If the MME/SGSN receives Change Notification Response containing a Cause value of ""IMSI/IMEI not known"" and CS bit set to 1, this indicates that the associated PDN connection does not exist within the PGW. The Change Reporting mechanism shall be stopped in the receiving SGSN/MME for all Bearers of the associated PDN connection. The SGSN/MME shall then initiate PDN disconnection for all of these PDN Connections. |
| 97 | Semantic error in the TAD operation | "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 clause 7.7.11 in this specification.' |
| 98 | Syntactic error in the TAD operation | "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 clause 7.7.11 in this specification.' |
| 99 | Shall not be used. See NOTE 2 and NOTE 3. | |
| 100 | Remote peer not responding | "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. |
| 101 | Collision with network initiated request | "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. |
| 102 | Unable to page UE due to Suspension | "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. |
| 103 | Conditional IE missing | A GTP entity shall check if conditional information elements are present in the received Request message, if possible (i.e. if the receiving entity has sufficient information available to check if the respective conditions were met). If one or more conditional information elements are missing, a GTP entity should log the error and shall send a Response message with Cause IE value set to "Conditional IE missing" together with the type and instance of the missing conditional IE. |
| 104 | APN Restriction type Incompatible with currently active PDN connection | "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). |
| 105 | Invalid overall length of the triggered response message and a piggybacked initial message | If a GTP entity receives two GTP messages (triggered response message and a piggybacked initial message) within an IP/UDP packet of a length that is inconsistent with the total length of the two concatenated messages as indicated by Length fields of the GTP headers, then the receiving GTP entity should log the error and return an appropriate Response message with Cause IE value set to ""Invalid overall length of the triggered response message and a piggybacked initial message"". That is: - for a Create Session Response message together with a piggybacked Create Bearer Request message, a Create Bearer Response message should be returned with the above Cause value. - for a Create Bearer Response message together with a piggybacked Modify Bearer Request message, a Modify Bearer Response message should be returned with the above Cause value. |
| 106 | Data forwarding not supported | |
| 107 | Invalid reply from remote peer | "Invalid Reply from remote peer" is used by the SGW for the messages spanning through two interfaces. This cause value is returned by the SGW to the MME/SGSN or PGW in a reply message where the corresponding reply message on S5/S8 or S11/S4 from the PGW or MME/SGSN is not decoded as valid. |
| 108 | Fallback to GTPv1 | The usage of "Fallback to GTPv1" is specified in clause 7.10 "Fallback to GTPv1 mechanism". |
| 109 | Invalid peer | "Invalid peer" is used by the SGW to indicate that currently the UE is being managed by the different node (e.g. MME/S4-SGSN) than the node (e.g. S4-SGSN/MME) which has sent the Delete Session Request message. |
| 110 | Temporarily rejected due to handover/TAU/RAU procedure in progress | "Temporarily rejected due to handover/TAU/RAU procedure in progress" is used by the MME/S4-SGSN for the bearer related procedure initiated by the PGW. When the handover/TAU/RAU with/without SGW change and/or MME/S4-SGSN change is in progress, the MME/S4-SGSN may receive Create / Update / Delete Bearer request message for the bearer creation, modification or deletion initiated by the PGW. If the handover/TAU/RAU procedure results in the SGW and/or MME/S4-SGSN change, then the bearer related procedure cannot be handled temporarily by the MME/S4-SGSN till the handover/TAU/RAU procedure is completed. In that case the MME/S4-SGSN shall reject the bearer related procedure with this rejection cause. This cause is also used to indicate that the Downlink Data Notification message is rejected temporarily due to the mobility procedures with MME or SGSN change in progress as specified in clause 5.3.4.3 in 3GPP TS 23.401 [3]. |
| 111 | Modifications not limited to S1-U bearers | The SGW shall send the cause value ""Modifications not limited to S1-U bearers"" if - it can not serve the MME Request without corresponding S5/S8 signalling other than to unpause charging in the PGW, or without corresponding Gxc signalling when PMIP is used over the S5/S8 interface, or - if there are suspended non-GBR bearers for that UE in the SGW (NOTE 3). Upon receipt of that cause value, the MME shall repeat its request using Modify Bearer Request message per PDN connection. |
| 112 | Request rejected for a PMIPv6 reason (see 3GPP TS 29.275 [26]). | |
| 113 | APN Congestion | "APN Congestion" is used by the PGW and it indicates that the PGW has detected congestion for the requested APN and performs overload control for that APN which does not allow the PDN connection to be established. |
| 114 | Bearer handling not supported | If a Bearer Resource Command message is related to an established PDN connection for LIPA or for SIPTO at the local network, the LGW shall reject the Bearer Resource Command with the cause value of "Bearer handling not supported". |
| 115 | UE already re-attached. See NOTE 7. | "UE already re-attached" is used by MME/S4-SGSN for the network triggered service restoration procedure as specified in 3GPP TS 23.007 [17]. The MME/S4-SGSN may send the Downlink Data Notification Acknowledge or Downlink Data Notification Failure Indication with this cause as part of the network triggered service restoration procedure. |
| 116 | Multiple PDN connections for a given APN not allowed | "Multiple PDN connections for a given APN not allowed" is used by SGW for reply message to the MME/S4-SGSN when PMIP-based S5/S8 is used. If either SGW or PGW does not support the multiple PDN connections to the same APN function, the SGW shall reject the PDN connectivity request procedure with this rejection cause when receiving Create Session Request for additional PDN connectivity to the given APN from the same UE. |
| 117 | Target access restricted for the subscriber | "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. |
| 118 | Shall not be used. See NOTE 2 and NOTE 3. | |
| 119 | MME/SGSN refuses due to VPLMN Policy | "MME/SGSN refuses due to VPLMN policy" is used by the MME/SGSN in the VPLMN to indicate to the PGW in the Create Bearer Response or Update Bearer Response that it does not allow the establishment or modification of the bearer due to VPLMN operator's policy. |
| 120 | GTP-C Entity Congestion | "GTP-C Entity Congestion" is used to indicate that the GTP-C entity has detected node level congestion and performs overload control at the node level, which does not allow the request to be processed. |
| 121 | Late Overlapping Request | "Late Overlapping Request" is used by the PGW in the Create Session Response to indicate that the incoming request collides with an existing session which has a more recent time stamp than the time stamp of the new request, as specified in clause 13.2. |
| 122 | Timed out Request | "Timed Out Request" is used by the SGW and PGW in the Create Session Response to indicate that the incoming request is known to have already timed out at the originating entity, as specified in clause 13.3. |
| 123 | UE is temporarily not reachable due to power saving | "UE is temporarily not reachable due to power saving" is used by the MME/SGSN in the Create/Update Bearer Response message to reject the corresponding network initiated procedures for a Delay Tolerant PDN connection and also request the PGW to hold the network initiated procedure until it receives the subsequent Modify Bearer Request message with the UASI flag indicating that the UE is available for end to end signalling. |
| 124 | Relocation failure due to NAS message redirection | "Relocation failure due to NAS message redirection" is used by the new MME/S4-SGSN to indicate to the old MME/S4-SGSN that the TAU/RAU procedure is not successful due to NAS message redirection as described in 3GPP TS 23.401 [3], or used by the initial AMF to indicate to the old MME that the context transfer procedure is not successful due to NAS message redirection as described in clause 4.11.1.3.4 of 3GPP TS 23.502 [83]. |
| 125 | UE not authorised by OCS or external AAA Server | "UE not authorised by OCS or external AAA Server" is used by the PGW in the Create Session Response to reject the corresponding UE initiated procedures when the OCS or an external AAA Server on SGi did not authorise it and the support of the Cause Code was indicated by the SGSN/MME within the Create Session Request. |
| 126 | Multiple accesses to a PDN connection not allowed | If a Create Session Request message requests the addition of an access to a PDN connection, and NBIFOM is not supported by the MME/SGSN, SGW or TWAN, the PGW should reject the request with the cause value of "Multiple accesses to a PDN connection not allowed". This cause is also used by the PGW in the Delete Bearer Request message to initiate the removal of 3GPP access from the PDN connection due to detection of the MME/SGSN or SGW not supporting NBIFOM at the inter-PLMN mobility procedure. |
| 127 | Request rejected due to UE capability | "Request rejected due to UE capability" is used by the MME in the Create Bearer Response to reject the request to add an EPS bearer that would exceed the UE capability (e.g. a NB-IoT UE can only support up to 2 EPS bearers). This cause value does not prevent the PGW from sending Create Bearer Request later. |
| 128 | S1-U Path Failure. See NOTE 8. | "S1-U Path Failure" is used by the SGW in the Create Session Response, or in the Modify Bearer Response message, or in the Modify Access Bearer Response message to report an S1-U path failure. The SGW may include this cause code in a Downlink Data Notification message and/or a Delete Bearer Request message to report the S1-U path failure. See clause 20.3 in 3GPP TS 23.007 [17]. |
| 129 | 5GC not allowed | "5GC not allowed" is used by the source MME in the Context Response message sent to the target AMF during an EPS to 5GS idle mode mobility procedure, to indicate that the UE is not allowed for 5GC, based on the subscription profile. |
| 130 | PGW mismatch with network slice subscribed by the UE | "PGW mismatch with network slice subscribed by the UE" is used by the PGW in the Create Session Response message during an EPS to 5GS mobility procedure, to indicate that the PGW is not serving the network slice subscribed by the UE for the APN/DNN. |
| 131 | Rejection due to paging restriction (NOTE 7) | "Rejection due to paging restriction" is used by the MME to indicate that the UE has not been paged because the MME holds stored Paging Restriction information for the UE that restricts the Downlink Data from causing paging as specified in clause 4.3.x.6 in 3GPP TS 23.401 [3] or the UE has rejected the page as specified in clause 4.3.x.4 in 3GPP TS 23.401 [3]. |
| 132 to 239 | Spare. For future use in a triggered/response message See NOTE 4. | |
| 240 to 255 | Spare. For future use in an initial/request message. See NOTE 5. |
| NOTE |
|---|
| NOTE 1: The listed cause values for rejection in a response/triggered message can be also used for request messages if the request message is triggered by a command message. |
| NOTE 2: Subclause 7.7.8 "Semantically incorrect Information Element" specifies quite strict handling of the reserved values and therefore this table shall not contain any reserved values. |
| NOTE 3: This value was used in earlier versions of the spec. If received, it shall be interpreted as unspecified rejection cause. Unspecified/unrecognized rejection cause shall be treated in the same ways as the cause value 94 "Request rejected (reason not specified)". |
| NOTE 4: This value is or may be used in the newer versions of the spec. If the receiver cannot comprehend the value, it shall be interpreted as unspecified rejection cause. Unspecified/unrecognized rejection cause shall be treated in the same ways as the cause value 94 "Request rejected (reason not specified)". |
| NOTE 5: This value is or may be used in the newer versions of the spec. If the receiver cannot comprehend the value, it shall be interpreted as an unspecified request/initial message cause. Unspecified/unrecognized cause handling in a request/initial message shall be implementation dependent (e.g. may be ignored). |
| NOTE 6: This Cause value is only used over the S4, S5 and S8 interface in the secondary PDP Context Activation procedure (see 9.2.2.1.1A in 3GPP TS 23.060 [4]). |
| NOTE 7: This cause value may also be used by a Downlink Data Notification Failure Indication, which is an initial message. |
| NOTE 8: This cause code may also be used in a Downlink Data Notification and a Delete Bearer Request message, which are initial messages. |
Reference:
3GPP TS 29.274 V17.3.0 (2021-09)
Technical Specification
3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
3GPP Evolved Packet System (EPS);
Evolved General Packet Radio Service (GPRS)
Tunnelling Protocol for Control plane (GTPv2-C);
Stage 3;
(Release 17)
No comments:
Post a Comment