Cause Code Handling

Feature Summary and Revision History

Summary Data

Table 1. Summary Data

Applicable Product(s) or Functional Area

SMF

Applicable Platform(s)

SMI

Feature Default Setting

Enabled - Always-on

Related Changes in this Release

Not Applicable

Related Documentation

Not Applicable

Revision History

Table 2. Revision History
Revision Details Release

Added support for:

  • GTP cause code handling

  • GTPv2 IE and cause codes

2021.02.0

Added support for 5GSM cause code handling.

2020.02.0

5GSM Cause Code Handling

Feature Description

The SMF supports 5GSM cause handling for the UE and Network initiated procedures.

The supported procedures are:

  • PDU-Session-Establishment

  • PDU-Session-Modification

  • PDU-Session-Release

PDU Session Establishment Reject

If the connectivity with the requested DN is rejected by the network, SMF sets the 5GSM cause IE of the PDU Session Establishment Reject message to indicate the reason for rejecting the PDU Session Establishment procedure.

The SMF supports the following causes in the PDU Session Establishment Reject message.

Table 3. Supported PDU Session Establishment Reject messages

Reject Cause / 5GSM Cause

SMF Behavior

Cause #26 – insufficient resources

The SMF includes this cause when it receives N2SmInfoType with "PDU_RES_SETUP_FAIL" along with any of the following N2 causes:

  • RadioNetwork/Radio_resources_not_available

  • RadioNetwork/Failure_in_the_radio_interface_procedure

  • Misc/Not_enough_user_plane_processing_resources

Cause #27 – missing or unknown DNN

The SMF includes this cause when DNN is not present in SmContextCreateData even though it is required and not configured in SMF.

Cause #28 – unknown PDU session type

The SMF includes this cause when the PDU Session Establishment Request message includes a PDU session type that is not supported by SMF.

Cause #29 – user authentication or authorization failed

The SMF includes this cause when DN authentication of the UE was performed and completed unsuccessfully (Radius Authentication Timeout).

Cause #32 – service option not supported

The SMF supports this cause when the validation of received S-NSSAI fails against the allowed list of S-NSSAI.

Cause #33 – requested service option not subscribed

The SMF supports this cause when the UE requests a service option for which it has no subscription.

Cause #38 – network failure

The SMF supports this cause when the requested service was rejected due to an error in the network. This includes any internal failures or no response from any external NF during the PDN-setup procedure.

Cause #54 – PDU session does not exist

The SMF supports this cause when it does not have any information about the PDU session which is requested by the UE to transfer between 3GPP access and non-3GPP access or from the EPS to the 5GS.

Cause #70 – missing or unknown DNN in a slice

The SMF supports this cause when the slice configuration is present but the requested DNN is not configured under the slice in the SMF.

Protocol errors

Cause #95 – Semantically incorrect message

This 5GSM cause reports receipt of a message with semantically incorrect content.

Important 

For mandatory parameters (PDU Session Identity and Procedure Transaction Identity) with non-semantical error also, the SMF sends this cause.

PDU Session Modification Reject

If the SMF does not accept the request to modify the PDU session, it sets the 5GSM cause IE of the PDU Session Modification Reject message to indicate the reason for rejecting the PDU session modification procedure.

The SMF supports the following causes in the PDU Session Modification Reject message.

Table 4. Supported PDU Session Modification Reject messages

Reject Cause / 5GSM Cause

SMF Behavior

Cause #43 – Invalid PDU session identity

The SMF sends this cause when SMF does not have the session.

Protocol errors

Cause #95 – Semantically incorrect message

This 5GSM cause reports receipt of a message with semantically incorrect content.

Important 
For mandatory parameters (PDU Session Identity and Procedure Transaction Identity) with non-semantical error also, the SMF sends this cause.

PDU Session Release Reject

If the SMF does not accept the request to release the PDU session, SMF sets the 5GSM Cause IE of the PDU Session Release Reject message to indicate the reason for rejecting the PDU session release.

The SMF supports the following causes in the PDU Session Release Reject message.

Table 5. Supported PDU Session Release Reject message

Reject Cause / 5GSM Cause

SMF Behavior

Cause #43 – Invalid PDU session identity

The SMF supports this cause when SMF does not have the session.

Protocol errors

Cause #95 – Semantically incorrect message

This 5GSM cause reports receipt of a message with semantically incorrect content.

Important 

For mandatory parameters (PDU Session Identity and Procedure Transaction Identity) with non-semantical error also, the SMF sends this cause.

PDU Session Release Request

To initiate the UE-requested PDU Session Release procedure, UE sends the PDU Session Release Request message with the 5GSM Cause IE to indicate the reason for releasing the PDU session.

The SMF supports the following causes in the PDU Session Release Request message.

Reject Cause / 5GSM Cause

SMF Behavior

Cause #36 – regular deactivation

The SMF retains the statistics based on the cause and continues with the Release procedure.

Cause #41 – Semantic error in the TFT operation

The SMF retains the statistics based on the cause and continues with the Release procedure.

Cause #42 – Syntactical error in the TFT operation

The SMF retains the statistics based on the cause and continues with the Release procedure.

Cause #44 – Semantic errors in packet filter(s)

The SMF retains the statistics based on the cause and continues with the Release procedure.

Cause #45 – Syntactical errors in packet filter(s)

The SMF retains the statistics based on the cause and continues with the Release procedure.

PDU Session Modification Command Reject

If the UE rejects the PDU-Session-Modification-Command, it sets the 5GSM cause IE of the PDU Session Modification Reject message to indicate the reason for rejecting the PDU session modification.

The SMF supports the following 5GSM causes.

Table 6. Supported PDU Session Modification Reject messages

5GSM Cause

SMF Behavior

Cause #26 – insufficient resources

The SMF retains the statistics based on the cause.

Cause #43 – Invalid PDU session identity

The SMF retains the statistics based on the cause and releases the existing PDU session.

Cause #44 – Semantic error in packet filter(s)

The SMF retains the statistics based on the cause.

Cause #45 – Syntactical error in packet filter(s)

The SMF retains the statistics based on the cause.

Cause #83 – Semantic error in the QoS operation

The SMF retains the statistics based on the cause.

Cause #85 – Syntactical error in the QoS operation

The SMF retains the statistics based on the cause.

How it Works

The SMF supports 5GSM cause handling for the PDU-Session-Establishment, PDU-Session-Modification and PDU-Session-Release procedures. An appropriate SM cause will be sent over the N1 message to the UE.

Standards Compliance

The 5GSM Cause Handling feature complies with the 3GPP TS 24.501, version 15.4.0, Release 15 (Non-Access-Stratum (NAS) protocol for 5G System (5GS)).

Configuring the 5GSM Cause Handling Feature

5GSM Cause Handling OAM Support

This section describes operations, administration, and maintenance information for this feature.

Statistics

The 5GSM Cause Handling feature supports the following statistics to track the number of failures based on the 5GSM cause.

SMF N1 Message Stats

PDU-Session-Establishment-Reject:

  • NETWORK_FAILURE: The number of PDU-Session-Establishment-Reject messages sent from SMF with N1 Cause "NETWORK_FAILURE".

  • UNKNOWN_PDU_SESSION_TYPE: The number of PDU-Session-Establishment-Reject messages sent from SMF with N1 Cause "UNKNOWN_PDU_SESSION_TYPE".

  • USER_AUTHENTICATION_OR_AUTHORIZATION_FAILED: The number of PDU-Session-Establishment-Reject messages sent from SMF with N1 Cause "USER_AUTHENTICATION_OR_AUTHORIZATION_FAILED".

  • REQUESTED_SERVICE_OPTION_NOT_SUBSCRIBED: The number of PDU-Session-Establishment-Reject messages sent from SMF with N1 Cause "REQUESTED_SERVICE_OPTION_NOT_SUBSCRIBED".

  • MISSING_OR_UNKNOWN_DNN: The number of PDU-Session-Establishment-Reject messages sent from SMF with N1 Cause "MISSING_OR_UNKNOWN_DNN".

  • SERVICE_OPTION_NOT_SUPPORTED: The number of PDU-Session-Establishment-Reject messages sent from SMF with N1 Cause "SERVICE_OPTION_NOT_SUPPORTED".

  • INSUFFICIENT_RESOURCES: The number of PDU-Session-Establishment-Reject messages sent from SMF with N1 Cause "INSUFFICIENT_RESOURCES".

  • MISSING_OR_UNKNOWN_DNN_IN_A_SLICE: The number of PDU-Session-Establishment-Reject messages sent from SMF with N1 Cause "MISSING_OR_UNKNOWN_DNN_IN_A_SLICE".

  • PDU_SESSION_DOES_NOT_EXIST: The number of PDU-Session-Establishment-Reject messages sent from SMF with N1 Cause "PDU_SESSION_DOES_NOT_EXIST".

PDU-Session-Modification-Reject:

  • INVALID_PDU_SESSION_IDENTITY: The number of PDU-Session-Modification-Reject messages sent from SMF with N1 Cause "INVALID_PDU_SESSION_IDENTITY".

PDU-Session-Release-Reject:

  • INVALID_PDU_SESSION_IDENTITY: The number of PDU-Session-Release-Reject messages sent from SMF with N1 Cause "INVALID_PDU_SESSION_IDENTITY".

PDU-Session-Release-Request:

  • REGULAR_DEACTIVATION: The number of PDU-Session-Release-Request messages received in SMF with N1 Cause "REGULAR_DEACTIVATION".

  • SEMANTIC_ERRORS_IN_PACKET_FILTER: The number of PDU-Session-Release-Request messages received in SMF with N1 Cause "SEMANTIC_ERRORS_IN_PACKET_FILTER".

  • SYNTACTICAL_ERROR_IN_PACKET_FILTER: The number of PDU-Session-Release-Request messages received in SMF with N1 Cause "SYNTACTICAL_ERROR_IN_PACKET_FILTER".

  • SEMANTIC_ERROR_IN_THE_TFT_OPERATION: The number of PDU-Session-Release-Request messages received in SMF with N1 Cause "SEMANTIC_ERROR_IN_THE_TFT_OPERATION".

  • SYNTACTICAL_ERROR_IN_THE_TFT_OPERATION: The number of PDU-Session-Release-Request messages received in SMF with N1 Cause "SYNTACTICAL_ERROR_IN_THE_TFT_OPERATION".

PDU-Session-Modification-Command-Reject:

  • INSUFFICIENT_RESOURCES: The number of PDU-Session-Modification-Command-Reject messages received in SMF with N1 Cause "INSUFFICIENT_RESOURCES".

  • INVALID_PDU_SESSION_IDENTITY: The number of PDU-Session-Modification-Command-Reject messages received in SMF with N1 Cause "INVALID_PDU_SESSION_IDENTITY".

  • SEMANTIC_ERRORS_IN_PACKET_FILTER: The number of PDU-Session-Modification-Command-Reject messages received in SMF with N1 Cause "SEMANTIC_ERRORS_IN_PACKET_FILTER".

  • SYNTACTICAL_ERROR_IN_PACKET_FILTER: The number of PDU-Session-Modification-Command-Reject messages received in SMF with N1 Cause "SYNTACTICAL_ERROR_IN_PACKET_FILTER".

  • SEMANTIC_ERROR_IN_THE_QOS_OPERATION: The number of PDU-Session-Modification-Command-Reject messages received in SMF with N1 Cause "SEMANTIC_ERROR_IN_THE_QOS_OPERATION".

  • SYNTACTICAL_ERROR_IN_THE_TFT_OPERATION: The number of PDU-Session-Modification-Command-Reject messages received in SMF with N1 Cause "SYNTACTICAL_ERROR_IN_THE_TFT_OPERATION".

GTP Cause Code Handling

Feature Description

The SMF supports GTP cause code handling for 4G procedures when it detects any failure with the IEs.

Create Session Request

The SMF supports the following causes in the Create Session Request message.

Table 7. Supported Create Session Request message

Cause

SMF Behavior

Missing or unknown APN

If the configured DNN does not match the DNN received in Create Session Request, then SMF rejects the message with this cause value in Create Session Response and sets the appropriate disconnect reason.

User authentication failed

If SMF receives failure AAA secondary authentication response from RADIUS, then SMF rejects the message with this cause value in Create Session Response. This cause indicates that the request is rejected due to failure in authentication or security procedure, and sets the appropriate disconnect reason.

APN access denied – no subscription

If SMF receives the subscription fetch failure response from UDM, then SMF rejects the message with this cause value in Create Session Response. This cause indicates that the SMF has denied user access to an APN because the subscriber does not have the necessary subscription. SMF also sets the appropriate disconnect reason.

New PDN type due to single address bearer only

If the Dual Address Bearer Flag (DAF) indication is not set and the requested PDN-type is IPV4V6 in Create Session Request message, then SMF rejects the message with this cause value in Create Session Response. SMF also sets the appropriate disconnect reason.

Late Overlapping Request

The Create Session Request message includes the Origination Time Stamp indicating the absolute time at which the request is initiated (as specified in clause 13.2.2, TS29.274).

If SMF receives any subsequent CSR from different S-GW and different sequence number with older timestamp in "Origination Time Stamp" than the time stamp stored for the existing session, then SMF rejects the new CSR with this cause value in Create Session Response. This cause indicates the incoming request collides with an existing session that does not have a recent time stamp than the time stamp of the new request.

If the timestamp is newer, then SMF aborts the current procedure and handles the new CSR request with the recent time stamp.

Timed Out Request

If the incoming CSR received origination-time-stamp and maximum-wait-time IEs, SMF starts the SLA timer with maximum-wait-time value at the start of the Create procedure and aborts the Create procedure on expiry of the timer. Then SMF rejects with this cause value in CSR Response.

New PDN type due to network preference

If the session type configured under profile dnn is IPv4 or IPv6, and the requested PDN type coming in Create Session Request is IPv4v6, then SMF rejects the message with this cause value in Create Session Response.

Delete Bearer Request

The SMF supports the following causes in the Delete Bearer Request message.

Table 8. Supported Delete Bearer Request messages

Cause

Scenario

Reactivation required

SMF sends Delete Bearer Response for default bearer with this cause value in the following cases:

  • CHF reconciliation

  • PCF reconciliation

  • Internal DB conflict

  • Session Report with SRSR/GTER/SRIR/SPTER/ERIR

PDN connection inactivity timer expires

SMF sends Delete Bearer Response for default bearer with this cause value in the following cases:

  • CP-IDLE timer expiry

  • Session Report with UPIR

  • Absolute Timer Expiry

RAN/NAS Cause IE

SMF receives the RAN/NAS Cause IE from access network in the GTP messages due to QoS flow termination or PDU session termination. SMF provides the received cause in the ranNasRelCauses attribute of the RuleReport to PCF. See the TS 29.274 version 15.4.0 for more information about this cause.

The supported GTP messages are:

  • Create Bearer Response

  • Update Bearer Response

  • Delete Bearer Command

  • Delete Session Request

Spec Derived Cause Code Mapping

The SMF supports specification derived (TS 29.524) cause code mapping for 5G messages for UDM and PCF interfaces.

Table 9. Mapping from HTTP to 5GSM cause values – Request rejected by UDM due to N10 failures

HTTP Status Code on N10

Protocol or Application Error

5GSM Cause to UE

403 Forbidden

ROAMING_NOT_ALLOWED

Cause #29 "User authentication or authorization failed"

DNN_NOT_ALLOWED

Cause #27 "Missing or unknown DNN"

404 Not Found

USER NOT FOUND

Cause #29 "User authentication or authorization failed"
Table 10. Mapping from HTTP to 5GSM cause values – Request rejected by PCF

HTTP Status Code on N7

Protocol or Application Error

5GSM Cause to UE

400 Bad Request

USER_UNKNOWN

Cause #29 - User authentication or authorization failed

ERROR_INITIAL_PARAMETERS

Cause #31 - Request rejected, unspecified

ERROR_TRIGGER_EVENT

Cause #31 - Request rejected, unspecified

403 Forbidden

ERROR_TRAFFIC_MAPPING_ INFO_REJECTED

#29 "User authentication or authorization failed"

ERROR_CONFLICTING_REQUEST

Cause #67 - insufficient resources for specific slice and DNN

POLICY_CONTEXT_DENIED

#29 "User authentication or authorization failed"

VALIDATION_CONDITION_ NOT_MET

#29 "User authentication or authorization failed"

Standards Compliance

The supported GTP cause codes comply with the following standards:

  • 3GPP TS 29.274, Version 15.4.0

  • 3GPP TS 29.524

Configuring GTP Cause Codes

This section describes how to configure cause to class mapping and class to cause mapping.

For source interface failures, the cause-map-class profile determines which class-map-cause profile must be applied on the corresponding target interface, only if the latter is configured under access profile. The respective CLI configurations send the user-defined cause values to the target interface based on the source interface failures and cause values. If the CLI commands are not configured, the target interface sends spec driven cause values as default values.

Cause to Class Mapping Configuration

This section describes how to configure cause to class mapping in SMF.

Configuring Cause to Class Map under cause-map-class Profile

Use the following sample configuration to configure cause to class mapping under cause-map-class profile:

config 
   profile cause-map-class nf-type [ udm | pcf ] cmc_profile_name 
      source { status-code httpv2_code cause cause_value } fail-class failclass_string 
      exit

NOTES:

  • profile cause-map-class nf-type [ udm | pcf ] cmc_profile_name : Specify the NF profile name to configure the cause-map-class profile.

  • source { status-code httpv2_code cause cause_value } fail-class failclass_string

    • status-code httpv2_code : Specify the HTTPv2 status code of the source interface.

    • cause cause_value : Specify the cause value as a string.

    • fail-class failclass_string : Specify the failure class as a string.

  • The profile cause-map-class is associated to the network-element profile.

  • The status-code and cause keywords are optional. If both are configured, then the corresponding fail-class is given higher priority followed by status-code and cause .

Example

The following is an example of the UDM interface configuration:

profile cause-map-class nf-type udm UDM-CMC
     source status-code 403 cause DNN_NOT ALLOWED fail-class congestion
Configuring Cause to Class Map under Network-element Profile

Use the following sample configuration to configure cause to class mapping under network-element profile: 

config 
   profile network-element [ udm | pcf ] nfprofile_name 
      cause-map-class-profile cmcp_name 
      exit

NOTES:

  • profile network-element [ udm | pcf ] nfprofile_name : Specify the NF profile name to configure the network-element profile.

  • cause-map-class-profile cmcp_name : Specify the cause to class map profile name.

Example

The following is an example of the UDM interface configuration:

profile network-element udm nfprf-udm
     cause-map-class UDM-CMC
Sample Configuration
[smf] smf# show running-config profile cause-map-class
profile cause-map-class nf-type udm CMC-UDM-1
 source status-code 500 cause CAUSE2 fail-class failClass2
 source status-code 500 cause CAUSE3 fail-class failClass3
 source status-code 501 cause CAUSE1 fail-class failClass1
 source status-code 502 cause CAUSE2 fail-class failClass1
 source status-code 504 cause CAUSE4 fail-class failClass4
 source status-code 505 cause CAUSE4 fail-class failClass5
exit
profile cause-map-class nf-type udm CMC-UDM-2
 source status-code 501 cause CAUSE1 fail-class failClass6
 source status-code 501 cause any fail-class failClass6
 source status-code 502 cause CAUSE1 fail-class failClass6
 source status-code 502 cause CAUSE2 fail-class failClass6
 source status-code 502 cause any fail-class failClass6
 source status-code any cause CAUSE1 fail-class failClass6
 source status-code any cause CAUSE2 fail-class failClass6
exit
profile cause-map-class nf-type udm CMC-UDM-3
 source status-code 504 cause CAUSE4 fail-class failClass4
 source status-code 505 cause CAUSE4 fail-class failClass5
exit
profile cause-map-class nf-type pcf PCF-CMC-1
 source status-code 500 cause CAUSE2 fail-class failClass2
 source status-code 500 cause CAUSE3 fail-class failClass3
 source status-code 501 cause CAUSE1 fail-class failClass1
 source status-code 502 cause CAUSE2 fail-class failClass1
 source status-code 504 cause CAUSE4 fail-class failClass4
 source status-code 505 cause CAUSE4 fail-class failClass5
exit
profile cause-map-class nf-type pcf PCF-CMC-2
 source status-code 500 cause any fail-class failClass2
 source status-code 501 cause any fail-class failClass3
 source status-code any cause CAUSE2 fail-class failClass2
 source status-code any cause CAUSE3 fail-class failClass3
exit
[smf] smf#

Class to Cause Mapping Configuration

This section describes how to configure class to cause mapping in SMF.

Configuring Class to Cause Map under class-map-cause Profile

Use the following sample configuration to configure class to cause mapping under class-map-cause profile: 

config 
   profile class-map-cause cmc_profile_name 
      fail-class failclass_string 
         target n11 { status-code  httpv2_code cause cause_value } | [ n1 | n2 | gtp ] { cause cause_value } 
         exit

NOTES:

  • profile class-map-cause cmc_profile_name : Specify the profile name to configure class-map-cause.

  • fail-class failclass_string : Specify the failure class as a string.

  • target n11 { status-code httpv2_code cause cause_value } | [ n1 | n2 | gtp ] { cause cause_value } :

    • target : Specify the target interface.

    • status-code httpv2_code : Specify the HTTPv2 status code for the target interface.

    • cause cause_value : Specify the cause value for the target interface.

  • The profile class-map-cause is associated to the access profile.

  • The status-code keyword is not applicable to the GTP, N1, and N2 interfaces.

Example

The following is an example of the CLI configuration:

profile class-map-cause cmc1
    fail-class congestion
         target gtp cause 72
Configuring Class to Cause Map under Access Profile

Use the following sample configuration to configure class-to-cause mapping under access profile: 

config 
   profile access access_profile_name 
      [ gtpc | n1 | n2 | n11 ] class-map-cause-profile cmc_profile_name 
      exit

NOTES:

  • profile access access_profile_name : Specify the profile name to configure the access profile.

  • class-map-cause-profile cmc_profile_name : Specify the profile name to configure the class-to-cause map profile.

Example

The following is an example of the CLI configuration:

profile access access1
       n11 class-map-cause cmc1
Sample Configuration
[smf] smf# show running-config profile class-map-cause
profile class-map-cause CMC
 fail-class failClass1
  target n11 status-code 403 cause CA1
  target n1 cause CA_N1
  target n2 cause CA_n2
  target gtp cause 75
 exit
 fail-class failClass2
  target n11 status-code 402 cause CAUSE4
  target n1 cause CAUSE3
  target n2 cause CAUSE2
  target gtp cause 95
 exit
exit
[smf] smf#

GTP Cause Code Handling OAM Support

This section describes operations, administration, and maintenance information for this feature.

Statistics Support

The source interface failures support the following disconnect reasons:

  • disc_new_pdn_type_due_to_single_addr_bearer_only—The number of Create Session Request failures with cause value "New PDN type due to single address bearer only" in Create Session Response.

  • disc_new_pdn_type_due_to_network_preference—The number of Create Session Request failures with cause value "New PDN type due to network preference" in Create Session Response.

  • disc_pdnsetup_dnn_missing_or_unknown—The number of Create Session Request failures with cause value "Missing or unknown APN" in Create Session Response.

  • disc_request_timeout_at_originating_entry—The number of Create Session Request failures with cause value "Timed Out Request" in Create Session Response.

GTPv2 IE and Cause Codes

Feature Description

This chapter describes the GPRS Tunneling Protocol, Version 2 (GTPv2) IEs and cause codes for 4G and 5G procedures.

Cause Source Errors

The Cause Source (CS) bit supports the following cause values in Create Session Response, Modify Bearer Response, Modify Bearer Failure Indication (MBFI), or Delete Bearer Failure Indication (DBFI).

Cause Value

Scenario

Context Not Found

When the subscriber is not present in SMF and receives Create Session Response with handover indication, the SMF sends this cause.

Missing Or Unknown APN

When Create Session Response receives missing or unknown APN, the SMF sends this cause.

DBFI with cause Context Not Found (Session not found)

When subscriber is not present in SMF and receives Delete Bearer Command, the SMF sends this cause.

Delete Session Response with cause Context Not Found (Session not found)

When subscriber is not present in SMF and receives a Delete Session Request in old TEID, the SMF sends this cause.

Bearer Context IE Errors

The Bearer Context IE Error (BCE) bit supports the following cause values in Delete Session Response, Modify Bearer Response, Modify Bearer Failure Indication (MBFI), or Delete Bearer Failure Indication (DBFI).

Cause Value

SMF Behavior or Scenario

MBFI with cause Context Not Found (EBI not found)

When SMF receives Modify Bearer Request with a wrong EBI in bearer context, the SMF sends MBFI with Context Not Found.

DBFI with cause Context Not Found (EBI not found)

When SMF receives Delete Bearer Command with a wrong EBI in bearer context, the SMF sends DBFI with Context Not Found.

Remote Node Errors

SMF supports the following remote node errors:

  • Context not found

  • Missing or unknown APN

  • PduSessionType

  • Mandatory IE missing

  • Malformed message errors

Statistics Support

The following is an example query of the supported GTPC message statistics. 


smf_gtpc_msg_stats{app_name="smf",cluster="smf",data_center="smf",instance_id="1",
message_type="modify_bearer_request",qos_5qi="",rat_type="",
reason="EGTP_CAUSE_CONTEXT_NOT_FOUND",service_name="smf-service",smf_current_procedure="",status="failures"} 1 
smf_gtpc_msg_stats{app_name="smf",cluster="smf",data_center="smf",instance_id="1",
message_type="delete_bearer_request",qos_5qi="",rat_type="",
reason="EGTP_CAUSE_CONTEXT_NOT_FOUND",service_name="smf-service",smf_current_procedure="",status="failures"} 1
smf_gtpc_msg_stats{app_name="smf",cluster="smf",data_center="smf",instance_id="1",
message_type="delete_session_request",qos_5qi="",rat_type="",
reason="EGTP_CAUSE_CONTEXT_NOT_FOUND",service_name="smf-service",smf_current_procedure="",status="failures"} 1