Identification of call flow failures in a telecommunications network

At least one non-transitory, computer-readable storage medium comprising instructions recorded thereon, wherein the instructions, when executed by at least one data processor of a system for identifying call flow failures in a telecommunications network, cause the system to:

• receive, from one or more 5G core network functions associated with the telecommunications network, by a call flow detection algorithm module of the system, a call flow trace,
• wherein the call flow trace includes a record of a call connected through at least one segment of the telecommunications network;
• identify, by the call flow detection algorithm module, a set of parameters associated each respective segment of the at least one segment of the call associated with the call flow trace,
• wherein the set of parameters comprises values for a first set of information elements (IEs) selected from:
• a call flow identification (ID), call flow type, a service Uniform Resource Identifier (URI), a message type, service URI specifics, a packet identifier, a request and response identifier, or an information element (IE) validation information;
• validate, by a call flow validation module of the system, the call flow trace by matching the set of parameters for the respective segments with existing validation parameters from a call flow validation input database,
• wherein the existing validation parameters include values for a second set of IEs and service procedures associated with historical successful call flows,
• wherein the second set of IEs includes one or more IEs from the first set of IEs,
• wherein the service procedures identify call flow protocols used for management of the historical successful call flows, and
• wherein the matching comprises comparing the set of parameters for the respective segments with the existing validation parameters to identify whether the set of parameters for the respective segments and the existing validation parameters are within a threshold range of each other;
• responsive to successfully validating the call flow trace,
• extract, by a call flow validation repository, information from the validated call flow trace,
• wherein the information extracted from the validated call flow trace comprises values of the existing validation parameters and service procedures matched against the set of parameters;
• store, by the call flow validation repository, information extracted from the validated call flow trace;
• and
• responsive to not successfully validating the call flow trace,
• identify, by a call flow trace comparator module of the system, a particular segment of the multiple segments of the call associated with the trace that failed the validation,
• determine, by a call flow failure signature check module of the system, that parameters associated with the particular segment match with existing failure parameters stored in a call flow failure signature database, and
• in response to a determination that the parameters associated with the particular segment match the existing failure parameters, remove, by the call flow failure signature check module of the system, information associated with the particular segment from the call flow validation repository.

A method for identifying call flow failures in a telecommunications network, the method comprising:

• receiving, from one or more 5G core network functions associated with the telecommunications network, by a call flow detection algorithm module, a call flow trace,
• wherein the call flow trace includes a record of a call connected through at least one segment of the telecommunications network;
• identifying, by the call flow detection algorithm module, a set of parameters associated each respective segment of the at least one segment of the call associated with the call flow trace,
• wherein the set of parameters comprises values for a first set of information elements (IEs) selected from:
• a call flow identification (ID), call flow type, a service Uniform Resource Identifier (URI), a message type, service URI specifics, a packet identifier, a request and response identifier, or an information element (IE) validation information;
• validating, by a call flow validation module, the call flow trace by matching the set of parameters for the respective segments with existing validation parameters from a call flow validation input database,
• wherein the existing validation parameters include values for a second set of IEs and service procedures associated with historical successful call flows,
• wherein the second set of IEs includes one or more IEs from the first set of IEs,
• wherein the service procedures identify call flow protocols used for management of the historical successful call flows, and
• wherein the matching comprises comparing the set of parameters for the respective segments with the existing validation parameters to identify whether the set of parameters for the respective segments and the existing validation parameters are within a threshold range of each other;
• responsive to successfully validating the call flow trace,
• extract, by a call flow validation repository, information from the validated call flow trace,
• wherein the information extracted from the validated call flow trace comprises values of the existing validation parameters and service procedures matched against the set of parameters;
• storing, by the call flow validation repository, the information extracted from the validated call flow trace;
• and
• responsive to not successfully validating the call flow trace,
• identifying, by a call flow trace comparator module of the system, a particular segment of the at least one segment of the call associated with the trace that failed the validation,
• determining, by a call flow failure signature check module of the system, that parameters associated with the particular segment match with existing failure parameters stored in a call flow failure signature storage location, and
• in response to a determination that the parameters associated with the particular segment match the existing failure parameters, removing, by the call flow failure signature check module of the system, information associated with the particular segment from the call flow validation repository.