The SMF maintains the following statistics to track the total number of attempted, successful, and failed node-level and session-level
requests.
-
SMF_SERVICE_STATS for the following procedure types:
-
upf_node_report_pdu_sess_rel
attempted: Total number of attempted PDU session release requests triggered due to the node report.
successful: Total number of successful PDU session release requests triggered due to the node report.
failure: Total number of failed PDU session release requests triggered due to the node report.
-
upf_sess_report_gter_pdu_sess_rel
attempted: Total number of attempted PDU session release requests triggered due to the session report “GTER”.
successful: Total number of successful PDU session release requests triggered due to the session report “GTER”.
failure: Total number of failed PDU session release requests triggered due to the session report “GTER”.
-
SMF_PROTOCOL_UDP_REQ_MSG_TOTAL for the following message types:
-
n4_node_report_req
attempted: Total number of attempted N4 requests triggered due to the node report.
successful: Total number of successful N4 requests triggered due to the node report.
failure: Total number of failed N4 requests triggered due to the node report.
-
n4_session_report_req
attempted: Total number of attempted N4 requests triggered due to the session report.
successful: Total number of successful N4 requests triggered due to the session report.
failure: Total number of failed N4 requests triggered due to the session report.
-
SMF_PROTOCOL_UDP_RES_MSG_TOTAL for the following message types:
-
n4_node_report_res
attempted: Total number of attempted N4 responses triggered due to the node report.
successful: Total number of successful N4 responses triggered due to the node report.
failure: Total number of failed N4 responses due to the node report.
-
n4_session_report_res
attempted: Total number of attempted N4 responses triggered due to the session report.
successful: Total number of successful N4 responses triggered due to the session report.
failure: Total number of failed N4 responses due to the session report.
-
SMF_DISCONNECT_STATS triggered for the following disconnect reasons:
gtpu_peer_path_failure : This statistic is triggered when the session is deleted due to the node report.
upf_sess_report_gter_pdu_sess_rel: This statistic is triggered when the session is deleted due to the session report.
The following is an example of the statistics:
Node Report SMF-service stats:
smf_service_stats{app_name="SMF",cluster="Local",data_center="DC",dnn="intershat",
emergency_call="false",instance_id="0",pdu_type="ipv4",
procedure_type="upf_node_report_pdu_sess_rel",qos_5qi="",rat_type="NR",
reason="",service_name="smf-service",status="attempted",up_state=""}
smf_service_stats{app_name="SMF",cluster="Local",data_center="DC",dnn="intershat",
emergency_call="false",instance_id="0",pdu_type="ipv4",
procedure_type="upf_node_report_pdu_sess_rel",qos_5qi="",rat_type="NR",
reason="",service_name="smf-service",status="success",up_state=""} 1
Session Report SMF-service stats:
smf_service_stats{always_on="",app_name="smf",cluster="smf",data_center="unknown",
dcnr="",dnn="intershat",emergency_call="false",instance_id="0",pdu_type="ipv4",
procedure_type="upf_sess_report_gter_pdu_sess_rel",qos_5qi="",rat_type="NR",
reason="",service_name="smf-service",status="attempted",up_state=""} 1
smf_service_stats{always_on="",app_name="smf",cluster="smf",data_center="unknown",
dcnr="",dnn="intershat",emergency_call="false",instance_id="0",pdu_type="ipv4",
procedure_type="upf_sess_report_gter_pdu_sess_rel",qos_5qi="",rat_type="NR",
reason="",service_name="smf-service",status="success",up_state=""} 1
Node Report SMF-protocol stats:
smf_proto_udp_req_msg_total{app_name="smf",cluster="smf",data_center="unknown",
instance_id="0",message_direction="inbound",message_name="n4_node_report_req",
msgpriority="",service_name="smf-protocol",status="accepted",
transport_type="origin"} 15
smf_proto_udp_res_msg_total{app_name="smf",cause="1",cluster="smf",
data_center="unknown",instance_id="0",message_direction="outbound",
message_name="n4_node_report_res",msgpriority="",service_name="smf-protocol",
status="accepted",transport_type="origin"} 15
Session Report SMF-protocol stats:
smf_proto_udp_req_msg_total{app_name="smf",cluster="smf",data_center="unknown",
instance_id="1",message_direction="inbound",message_name="n4_session_report_req",
msgpriority="",service_name="smf-protocol",status="accepted",
transport_type="origin"} 43
smf_proto_udp_res_msg_total{app_name="smf",cause="1",cluster="smf",
data_center="unknown",instance_id="1",message_direction="outbound",
message_name="n4_session_report_res",msgpriority="",service_name="smf-protocol",
status="accepted",transport_type="origin”}
The SMF also maintains labels to track the number of session deletions due to the node report and session report types – GTER,
SRIR, and SPTER.
For example, the label "LABEL_DISC_PDNREL_GTER_SESSION_REP" is added to track the session deletion due to the presence of
GTER.