TWI809593B - Electronic device and method of root cause analysis for voice over ip signaling loop - Google Patents

Abstract

An electronic device and a method of root cause analysis for a VoIP signaling loop. The method includes: capturing a plurality of signalings from a telecommunication core network; arranging the plurality of signalings in order according to time to obtain signaling information, wherein the signaling information includes a status code corresponding to session initiation protocol, a result code of location information answer, and number portability routing information (NRI); and determining the root cause of the VoIP signaling loop according to the status code, the result code, and the NRI and outputting the root cause.

Description

Electronic apparatus and method for root cause analysis of VoIP signaling loops

The present invention relates to an electronic device and method for root cause analysis of network telephony signaling loops.

Voice over Internet protocol (VoIP) technology is an important driving force behind the rapid development of telecommunication networks. During the IP-based process of the public switched telephone network (PSTN), the establishment of calls has changed from the traditional circuit switch mode to the packet switch mode, and is based on the session initial agreement (session initiation protocol, SIP) to complete.

How to make customers feel indifferent during the process of port number transfer is the goal that telecom operators must achieve in order to maintain user experience. When human negligence or equipment obstacles lead to inconsistent routing, the SIP signal at the calling end cannot reach the receiving end correctly. In addition to this phenomenon causing customers to be unable to communicate, if the signal repeatedly flows through multiple devices or components and continues to circulate in the network, it will cause a signaling loop phenomenon. Signaling loops consume network and voice service resources, thereby affecting service performance. Therefore, how to propose a method for effectively detecting or predicting the occurrence of signaling loops is one of the important topics in this field.

The present invention provides an electronic device and method for root cause analysis of VoIP signaling loops, which can detect VoIP signaling loops in a telecommunications core network and output the root cause of VoIP signaling loops.

An electronic device for analyzing the root cause of network telephony signaling loops according to the present invention includes a processor, a storage medium and a transceiver. The transceiver is communicatively connected to the telecommunications core network. The storage medium stores multiple modules. The processor is coupled to the storage medium and the transceiver, and accesses and executes multiple modules, wherein the multiple modules include a signaling capture module, a collection and sorting module, and an exception analysis module. The signaling retrieval module retrieves a plurality of signalings from the telecommunications core network through the transceiver. The converging and sorting module sorts a plurality of signalings in sequence according to time to obtain signaling information, wherein the signaling information includes call status codes corresponding to the initial protocol of the session, result codes of location information responses, and number portability routing information. The abnormal analysis module judges the root cause of the VoIP signaling loop according to the status code, result code and number portability routing information, and outputs the root cause through the transceiver.

In an embodiment of the present invention, the above-mentioned exception analysis module generates a root cause in response to a status code matching a preset status code, wherein the root cause includes a status code, wherein the root cause indicates that a VoIP signaling loop has occurred .

In an embodiment of the present invention, the above-mentioned exception analysis module determines whether the result code does not match the preset result code in response to the mismatch between the status code and the preset status code. Assume result code mismatch to generate root cause, where root cause indicates a data out-of-sync between the phone number mapping server and the home subscriber server in the telecom core network, where root cause indicates that a VoIP signaling loop is occurring .

In an embodiment of the present invention, the above abnormal analysis module obtains the second number portability routing information from the signaling information in response to the result code matching the preset result code, wherein the abnormal analysis module responds to the number portability The root cause is a mismatch between routing information and second number portability routing information, where the root cause indicates a data out-of-sync between multiple phone number mapping servers in the telecom core network, where the root cause indicates VoIP The loop is about to happen.

In an embodiment of the present invention, the above-mentioned multiple signalings respectively include multiple session identification codes, wherein the collection and sorting module generates signaling information according to the multiple signalings in response to the matching of the multiple session identification codes.

A method for root cause analysis of VoIP signaling loop of the present invention, comprising: extracting multiple signalings from the telecommunications core network; arranging the multiple signalings sequentially according to time to obtain signaling information, wherein The signaling information includes the status code of the call corresponding to the session initial agreement, the result code of the location information response, and the number portability routing information; Circle the root cause, and output the root cause.

Based on the above, the electronic device of the present invention can analyze the signaling information to quickly find the VoIP signaling loops that have "happened", "is happening" or "is about to happen" and the corresponding abnormal door numbers, and can output the VoIP signal Let the root cause of the loop be a reference for maintenance personnel of the telecom network. The root cause can help the maintenance personnel to eliminate loop obstacles or warn the maintenance personnel in advance to avoid wasting network and service resources in the future.

The version RFC (request for comments) 3261 of the SIP protocol has standardized the mechanism for detecting the loop phenomenon, including "via header (via header)" and "max-forwards". The former can mark the equipment through which the signaling flows, so as to determine whether to repeat the signaling. If a network element detects a signaling loop, the network loop can send a status code (status-code) "482" representing "loop detected"; the latter is through limiting the number of forwarding , to avoid excessive consumption of resources. Each time the signaling passes through a relay (hop), the value of the forwarding times will be reduced by 1. When the value is 0, the network element can send a status code "483" representing "too many hops". If the number of forwarding times is set too high, it will cause unnecessary resource consumption. If the number of forwarding times is set too small, the call may not even be successfully established. Neither of the above two methods can know the root cause, and may misjudge the resonance as a loop when the resonance (forking) occurs.

In view of this, the present invention provides an electronic device and method for root cause analysis of VoIP signaling loops, which can detect VoIP signaling loops in the telecommunications core network, and can analyze the causes of VoIP signaling loops. The root cause of the loop.

FIG. 1 is a schematic diagram of an electronic device 100 for root cause analysis of VoIP signaling loops according to an embodiment of the present invention. The electronic device 100 may include a processor 110 , a storage medium 120 and a transceiver 130 .

The processor 110 is, for example, a central processing unit (central processing unit, CPU), or other programmable general purpose or special purpose micro control unit (micro control unit, MCU), microprocessor (microprocessor), digital signal processing Digital Signal Processor (DSP), Programmable Controller, Application Specific Integrated Circuit (ASIC), Graphics Processing Unit (GPU), Image Signal Processor (ISP) ), image processing unit (image processing unit, IPU), arithmetic logic unit (arithmetic logic unit, ALU), complex programmable logic device (complex programmable logic device, CPLD), field programmable logic gate array (field programmable gate array , FPGA) or other similar components or combinations of the above components. The processor 110 can be coupled to the storage medium 120 and the transceiver 130 , and access and execute multiple modules and various application programs stored in the storage medium 120 .

The storage medium 120 is, for example, any type of fixed or removable random access memory (random access memory, RAM), read-only memory (read-only memory, ROM), flash memory (flash memory) , hard disk drive (hard disk drive, HDD), solid state drive (solid state drive, SSD) or similar components or a combination of the above components, and are used to store multiple modules or various application programs executable by the processor 110 . In this embodiment, the storage medium 120 can store multiple modules including one or more signaling capture modules 121 , collection and sorting modules 122 , and exception analysis modules 123 , and their functions will be described later.

The transceiver 130 transmits and receives signals in a wireless or wired manner.

In one embodiment, the functions of the electronic device 100 may be implemented by a plurality of different components. For example, multiple modules such as one or more signaling capture module 121 , collection and sorting module 122 , and exception analysis module 123 can be respectively implemented by different computers.

The electronic device 100 can detect whether a VoIP signaling loop occurs in the telecommunication network, and can analyze the root cause of the VoIP signaling loop. FIG. 2 shows a schematic diagram of a telecommunication network according to an embodiment of the invention. The telecommunication network may include an electronic device 100 , a user agent (user agent, UA) 200 , a user agent 300 and a telecommunication core network 500 . The user agent device 200 (or the user agent device 300 ) may include a phone device such as a mobile phone, a traditional phone or a smart watch, or may include a computing device such as a tablet computer, a desktop computer or a notebook computer with VoIP communication software. User agent device 200 (or user agent device 300 ) may have one or more sets of door numbers. In an embodiment, the user agent device 200 (or the user agent device 300 ) may also have information such as other client device identification codes, device serial numbers, or temporary identification codes. In this embodiment, it is assumed that the user agent device 200 is the calling end, and the user agent device 300 is the receiving end. The user agent device 200 and the user agent device 300 can establish a call through the telecommunications core network 500 . The UA device 200 (or UA device 300 ) can send signals or signaling to the telecommunications core network 500 for registration, update, subscription, or calling to another UA device for VoIP-based actions.

The telecom core network 500 may include various basic IP multimedia subsystem (IP multimedia subsystem, IMS) network elements, wherein the IMS network elements may include serving-call session control function (serving-call session control function, S-CSCF) elements , interrogation call session control function (interrogation-call session control function, I-CSCF) component, proxy call session control function (proxy-call session control function, P-CSCF) component, home subscriber server (home subscriber server, HSS) , user profile server function (UPSF) component, telephone number mapping (E.164 NUMber, ENUM) server, number portability database (NP database, NPDB) component, interconnection boundary control function ( interconnection border control function (IBCF) components, domain name system (domain name system, DNS) or application server (application server, AP), etc.

The electronic device 100 can be communicatively connected to the telecommunications core network 500 through the transceiver 130 . The signaling retrieval module 121 can retrieve one or more signalings from the telecom core network 500 or IMS network components through the transceiver 130 . The signaling captured by the signaling capture module 121 can be used to detect the occurrence and root cause of the VoIP signaling loop. In an embodiment, the telecommunications core network 500 may include multiple areas 50 governed by the same or different realms, and the electronic device 100 may include multiple signaling capture modules 121 . Area 50 is, for example, an IMS network. The electronic device 100 can respectively capture signaling in different areas 50 through a plurality of signaling capturing modules 121 , so that the signaling capturing range covers the entire telecom core network 500 . Multiple areas 50 governed by the same domain may be served by the same specific IMS element, while multiple areas 50 governed by different domains are served by different specific IMS elements. In one embodiment, the signaling capture module 121 can capture the signaling in the area 50 according to a preset period.

FIG. 3 shows a flowchart of a method for detecting VoIP signaling loops according to an embodiment of the present invention, wherein the method can be implemented by the electronic device 100 shown in FIG. 1 . In step S310 , the collection and sorting module 122 can obtain signaling information corresponding to the SIP call (SIP INVITE), and input the signaling information to the abnormal analysis module 123 .

Specifically, after the signaling retrieval module 121 retrieves a plurality of signalings from the telecommunications core network 500 through the transceiver 130, the collection and sorting module 122 can sort according to the time (for example: the time stamp in the signaling packet) Sequence a plurality of related signaling to obtain signaling information. The above signaling is, for example, VoIP signaling. In one embodiment, the collection and sorting module 122 can determine whether the signaling is related according to the call ID. Multiple call identification codes can be included in multiple signalings respectively. The collection and sorting module 122 can generate signaling information according to a plurality of signalings in response to a plurality of call ID matches. For example, if the call identification code in one signaling is the same as the call identification code in another signaling, the collection and sorting module 122 can determine that the two signalings are related signaling, and generate a signal according to the two signalings. order information. In one embodiment, the converging and sorting module 122 can determine whether the signaling is relevant according to the called number. For example, if the receiver number in one signaling is the same as the receiver number in another signaling, the collection and sorting module 122 can determine that the two signalings are related signaling, and generate signaling information according to the two signalings .

The signaling information is used to establish a session between the UA device 200 and the UA device 300 . The signaling information may include a call identification code, a status code corresponding to a SIP call (SIP status code), a location information answer (LIA) result code (diameter result code), and number portability routing information (number portability) routing information, NRI). The abnormal analysis module 123 can detect the VoIP signaling loop in the telecommunications core network 500 according to the status code, the result code and the number portability routing information, and determine the root cause of the VoIP signaling loop. In one embodiment, the signaling information may further include ENUM response code (reply code), ENUM DNS signaling, caller (caller) calling number (SIP-from-address), callee (callee) receiving number ( SIP-to-address), the originating IP address (source IP) of the caller, the receiving IP address (destination IP) of the receiver, and the time stamp of each signaling, wherein the calling number is the The phone number registered in the network 500 , and the called number is the phone number registered with the telecommunications core network 500 by the user agent device 300 . The number portability routing information may include a domain prefix (or routing number (RN)) and a called number. The domain prefix can be used to determine which domain the receiver's user agent device is under.

In one embodiment, the collection and sorting module 122 can search the telecommunications core network 500 for the diameter CX interface signaling associated with the called number within a specific time period corresponding to the time stamp according to the called number and time stamp. , and then obtain the result code from the diameter CX interface signaling.

In one embodiment, the collection and sorting module 122 can search the telecommunications core network 500 for ENUM DNS signaling associated with the called number within a specific time period corresponding to the time stamp according to the called number and the time stamp. If the ENUM DNS signaling exists, the collection and sorting module 122 can obtain the routing prefix presented in regular expression (regex) from the ENUM DNS signaling.

In one embodiment, the collection and sorting module 122 can query the number portability database or one or more ENUM servers in the telecommunications core network 500 through a DNS application programming interface (API), so as to obtain the number Portability routing information, wherein the number portability routing information obtained from different ENUM servers may be the same or different.

In step S320, the abnormal analysis module 123 can determine whether the signaling information corresponds to a new VoIP signaling loop event. If the signaling information corresponds to a new VoIP signaling loop event, go to step S330. If the signaling information does not correspond to a new VoIP signaling loop event, go to step S390.

Specifically, when the abnormal analysis module 123 determines that the past signaling information corresponds to a VoIP signaling loop event, the abnormal analysis module 123 may store the past signaling information in the storage medium 120 . After receiving the new signaling information, if the new signaling information matches the past signaling information stored in the storage medium 120, the abnormal analysis module 123 can determine that the new signaling information does not correspond to a new VoIP signaling response. circle events. If the new signaling information does not match any previous signaling information in the storage medium 120, the abnormal analysis module 123 can determine that the new signaling information corresponds to a new VoIP signaling loop event.

The abnormal analysis module 123 can judge whether the two signaling information match according to parameters such as call identification code, calling number, calling IP address, receiving number, receiving IP address or time stamp. For example, if the time stamps in the two signaling messages correspond to the same time range and the receiver numbers in the two signaling messages are the same, the abnormal analysis module 123 can determine that the two signaling messages match. For another example, if the call identification codes in the two signaling information are the same, the abnormal analysis module 123 may determine that the two signaling information match.

In step S330, the abnormal analysis module 123 can determine whether the status code in the signaling information matches the default status code. If the status code matches the preset status code (that is, the status code is the same as the preset status code), go to step S360. If the status code does not match the default status code (that is, the status code is different from the default status code), go to step S340. The default status code is, for example, the status code "482" representing "loop detected" or the status code "483" representing "too many relay times". If the judgment result of step S330 is yes, it means that there is a VoIP signaling loop that has occurred in the telecommunications core network 500, and the VoIP signaling loop has been detected by the IMS network element in the telecommunications core network 500 . The IMS network element may send a signaling including status code "482" or status code "483" when VoIP signaling loop is detected.

In step S340, the abnormal analysis module 123 can determine whether the result code in the signaling information does not match the default result code. If the result code does not match the preset result code (ie: the result code is different from the preset result code), go to step S380. If the result code matches the preset result code (ie: the result code is the same as the preset result code), go to step S350. The default result code is, for example, "DIAMETER_SUCCESS (2001)". If the judgment result of step S340 is yes, it means that there is an ongoing VoIP signaling loop in the telecommunications core network 500, wherein the root cause of the VoIP signaling loop is, for example, the ENUM server in the telecommunications core network 500 and the home Data out of sync between user servers. It should be noted that if the abnormal analysis module 123 cannot obtain the result code, it will enter step S350.

In step S350, the abnormal analysis module 123 can determine whether there are different routing prefixes in the signaling information and determine whether the ENUM response code is equal to 0, wherein the ENUM response code equal to 0 means "no error". Routing prefixes or ENUM response codes can be obtained from ENUM DNS signaling. If the ENUM server has routing prefixes in different domains and the ENUM response code is equal to 0, go to step S380. If the ENUM server does not have routing prefix codes in different domains or the ENUM response code is not equal to 0, go to step S390. If the judgment result of step S350 is yes, it means that the data is not synchronized among the multiple ENUM servers in the telecommunications core network 500, and the data is not synchronized and may cause a VoIP signaling loop, wherein the multiple ENUM servers The ENUM servers include, for example, an ENUM server belonging to the domain of the user agent device 200 and an ENUM server belonging to the domain of the user agent device 300 .

In step S360, the abnormal analysis module 123 may store the signaling information in the storage medium 120, and create a new VoIP signaling loop event corresponding to the signaling information. The exception analysis module 123 can also number the VoIP signaling loop events. The VoIP signaling loop event may include information such as call identification code, called number, time stamp or status code.

In step S370, the abnormal analysis module 123 can send an alarm message through the transceiver 130, so as to notify the maintenance personnel of the telecom core network 500 that the VoIP signaling loop has occurred. The abnormal analysis module 123 can transmit the alarm message to the terminal device held by the maintenance personnel through email, mobile phone text message or IM software message.

In step S380 , the abnormal analysis module 123 can perform root cause analysis of the VoIP signaling loop.

In step S390, the exception analysis module 123 can determine whether the signaling information captured by the collection and sorting module 122 has been processed. If there is unprocessed signaling information, go to step S310, where the collection and sorting module 122 continues to input signaling information for analysis by the abnormal analysis module 123. If there is no unprocessed signaling information, the process of FIG. 3 ends.

FIG. 4 shows a flowchart of a method for root cause analysis (ie, step S380 ) according to an embodiment of the present invention, wherein the method can be implemented by the electronic device 100 shown in FIG. 1 . In step S381, the abnormal analysis module 123 can determine whether the result code in the signaling information does not match the preset result code. If the result code does not match the preset result code (that is, the result code is different from the preset result code), go to step S383. If the result code matches the preset result code (ie: the result code is the same as the preset result code), go to step S382. It should be noted that, if the abnormal analysis module 123 cannot obtain the result code, it will enter step S382.

If the judgment result of step S381 is yes, it means that the root cause of the VoIP signaling loop is data out-of-sync between the ENUM server and the HSS (or UPSF). If the judgment result of step S381 is negative, it means that the data in the HSS or UPSF component to which the called end belongs is normal. In other words, the VoIP signaling loop is caused by a routing anomaly in a domain different from the receiving end. Accordingly, in step S382, the abnormal analysis module 123 can determine whether there is an NRI mismatch in the signaling information. If the NRI does not match, go to step S384. If the NRI matches, the process in Figure 4 ends. If the determination result of step S382 is yes, it means that the root cause of the VoIP signaling loop is data out-of-sync between multiple ENUM servers. The NRI can come from the ENUM server or the NPDB component in the telecom core network 500 .

In step S383 , the abnormal analysis module 123 can collect information associated with the called number from various fields in the telecommunications core network 500 . For example, if the telecommunications core network 500 includes a plurality of HSS or UPSF components, the exception analysis module 123 can pass Diameter API or location information request (location information request, LIR) and other instructions to the HSS or UPSF components according to the received number. LIA signaling to poll for responses. The exception analysis module 123 can obtain information associated with the called number, such as origin-host, origin-realm, or result code, from the LIA signaling. For another example, the abnormal analysis module 123 can obtain the ENUM DNS signaling from the telecommunications core network 500 according to the called number, and obtain the ENUM response code or name authorization indicator (naming authority pointer) presented in Regex from the ENUM DNS signaling. , NAPTR) and other information associated with the called number. If the abnormal resolution module 123 cannot find the associated ENUM DNS signaling through the signaling information corresponding to the SIP call, the abnormal resolution module 123 can directly query the ENUM server with the receiving number in E.164 format through the DNS API , so as to obtain information such as the Regex field of the response code from the ENUM server.

In step S384, the abnormal analysis module 123 can determine whether the signaling information corresponds to a new VoIP signaling loop event. If the signaling information corresponds to a new VoIP signaling loop event, go to step S385. If the signaling information does not correspond to a new VoIP signaling loop event, go to step S387.

In step S385, the abnormal analysis module 123 may store the signaling information in the storage medium, and create a new VoIP signaling loop event corresponding to the signaling information. The exception analysis module 123 can also number the VoIP signaling loop events. The VoIP signaling loop event may include information such as call identification code, called number, time stamp or status code.

In step S386 , the abnormal analysis module 123 can send an alarm message through the transceiver 130 , so as to notify the maintenance personnel of the telecommunications core network 500 that a VoIP signaling loop may be about to occur or is currently occurring. The abnormal analysis module 123 can transmit the alarm message to the terminal device held by the maintenance personnel through email, mobile phone text message or IM software message.

In step S387, the abnormal analysis module 123 can determine the root cause of the VoIP signaling loop, and output the root cause for reference by maintenance personnel. The abnormal analysis module 123 can transmit the root cause to the terminal device held by the maintenance personnel through email, mobile phone short message or IM software message.

If the determination result of step S384 is negative, it means that a VoIP signaling loop has occurred. Accordingly, the abnormal analysis module 123 can generate a root cause indicating that a VoIP signaling loop has occurred, wherein the root cause can also include a status code (for example: status code "482" or status code "483". If step S381 With the judgment result of step S384 all being yes, representative VoIP signaling circle is taking place.Accordingly, abnormal parsing module 123 can produce the root cause that indicates that VoIP signaling circle is taking place, and wherein said root cause can also indicate signal Data out-of-sync occurs between the ENUM server in the core network 500 and the home user server. If the judgment result of step S382 and step S384 is all yes, it is possible to represent that the VoIP signaling loop will take place. According to this abnormal analysis model The group 123 can generate a root cause indicating that a VoIP signaling loop is about to occur, wherein the root cause can also indicate a data out-of-sync between ENUM servers in the telecommunications core network 500 .

The abnormal analysis module 123 generates a root cause and outputs the root cause through the transceiver 130 to alert the maintenance personnel of the telecom core network 500, wherein the root cause may include a status code, and the root cause may indicate VoIP signaling The loop has happened. The abnormal analysis module 123 can transmit the root cause to the terminal device held by the maintenance personnel through email, mobile phone short message or IM software message. In one embodiment, the root cause may also include information such as calling number, receiving number, time stamp, status code or VoIP signaling loop event number.

In one embodiment, the root cause may include related content of the information obtained in step S383. Specifically, the exception analysis module 123 can make the following judgments based on the information: if the domain of the receiving number queried by ENUM DNS is HSS A, but the querying of the receiving number from HSS A fails, it means that the receiving number stored in the ENUM server Inconsistent with the data of HSS A. The exception analysis module 123 can write the information into the root cause and report it to the maintenance personnel. If the query of the receiving phone number to HSS A is successful, the exception analysis module 123 can write the query result into the root cause and report it to the maintenance personnel.

FIG. 5 shows a signaling diagram for establishing a normal VoIP call (that is, no VoIP signaling loop event occurs) according to an embodiment of the present invention. The user agent device 200 can communicate with the user agent device 300 through the telecommunications core network 500 . The telecom core network 500 may include a P-CSCF component 510, a calling home network 520, an ENUM server 530, a called home network 540, and a P-CSCF component 550, wherein the calling The end home network 510 may include an S-CSCF element 521 , and the called end home network may include an I-CSCF element 541 , an HSS/UPSF element 542 and an S-CSCF element 543 . The UA device 200, the P-CSCF element 510, and the originator's home network 520 may belong to the same domain. The user agent device 300, the home network 540 of the receiving end, and the P-CSCF component 550 may belong to the same domain.

In step S501, the UA device 200 may send a SIP call to the S-CSCF element 521 through the P-CSCF element 510 to initiate a call. A SIP call can contain information such as the calling number and the receiving number.

In step S502 , the S-CSCF component 521 may send a DNS query (query) to the ENUM server 530 according to the SIP call, so as to query the domain to which the called number belongs.

In step S503 , the ENUM server 530 may send the domain to which the called number belongs to the S-CSCF component 521 in response to the DNS query. The S-CSCF component 521 and the ENUM server 530 can communicate with each other through ENUM DNS commands.

In step S504 , the S-CSCF component 521 may transmit the SIP call request to the I-CSCF component 541 according to the response from the ENUM server 530 , wherein the response indicates that the called number and the I-CSCF component 541 belong to the same domain. A SIP call request can contain information such as the calling number and the receiving number.

In step S505 , the I-CSCF component 541 may send a Diameter LIR command to the HSS/UPSF component 542 to query the S-CSCF component to which the called number belongs.

In step S506 , the HSS/UPSF component 542 may send a Diameter LIA command to the I-CSCF component 541 in response to the Diameter LIR command, wherein the Diameter LIA command may include information of the S-CSCF component 543 .

In step S507 , the I-CSCF component 541 may transmit the SIP call request to the UA device 300 through the S-CSCF component 543 and the P-CSCF component 550 .

In response to the SIP call request, in step S508, the user agent device 300 may pass the P-CSCF element 550, the S-CSCF element 543, the I-CSCF element 541, the S-CSCF element 521 and The P-CSCF component 510 transmits the SIP status (SIP status) to the UA device 200 , so as to establish a call between the UA device 200 and the UA device 300 .

FIG. 6 is a signaling diagram of a VoIP call in which an abnormal VoIP signaling loop occurs according to an embodiment of the present invention. In FIG. 6 , step S605 to step S610 are the first cycle in which an abnormal VoIP signaling loop occurs, and steps S611 to step S616 are a second cycle in which an abnormal VoIP signaling loop occurs. Although FIG. 6 only depicts two cycles in which the abnormal VoIP signaling loop occurs, in fact, the number of cycles in which the abnormal VoIP signaling loop occurs can be more than two, until the value of the forwarding times of the "maximum forwarding" is reduced. until 0.

In step S601, the UA device 200 may send a SIP call to the S-CSCF element 521 through the P-CSCF element 510 to initiate a call. A SIP call can contain information such as the calling number and the receiving number.

In step S602, the S-CSCF component 521 may send a DNS query to the ENUM server 530 according to the SIP call, so as to query the domain to which the called number belongs.

In step S603 , the ENUM server 530 may send the domain to which the called number belongs to the S-CSCF component 521 in response to the DNS query. The S-CSCF component 521 and the ENUM server 530 can communicate with each other through ENUM DNS commands.

In step S604 , the S-CSCF component 521 may send the SIP call request to the I-CSCF component 541 according to the response from the ENUM server 530 , wherein the response indicates that the called number and the I-CSCF component 541 belong to the same domain. A SIP call request can contain information such as the calling number and the receiving number.

In step S605 , the I-CSCF component 541 may send a Diameter LIR command to the HSS/UPSF component 542 to query the S-CSCF component to which the called number belongs.

Factors such as human error or equipment failure may cause data out-of-sync between the ENUM server 530 and the HSS/UPSF component 542 . If the data is not synchronized, in step S606, the HSS/UPSF component 542 can send a Diameter LIA command to the I-CSCF component 541, wherein the Diameter LIA command can include a result code indicating that the HSS/UPSF component 542 cannot query the called number, wherein The result code is, for example, DIAMETER ERROR USER UNKNOWN (5001).

In step S607, since the I-CSCF component 541 cannot know the domain to which the called number belongs, the I-CSCF component 541 may send a SIP call request to a preset S-CSCF component. The preset S-CSCF element may include the S-CSCF element 543 .

Since the S-CSCF component 543 cannot query the relevant information of the called number, in order to respond to the SIP call request, in step S608, the S-CSCF component 543 can send a DNS query to the ENUM server 530, so as to query the belonging of the called number field.

In step S609 , the ENUM server 530 can respond to the S-CSCF component 543 the domain (or home network) to which the called number belongs.

In step S610 , the S-CSCF component 543 transmits a SIP call request to the I-CSCF component 541 . A SIP call request can contain information such as the calling number and the receiving number.

The purpose of step S610 is the same as that of step S604. Therefore, in step S611, the I-CSCF component 541 may send the Diameter LIR command to the HSS/UPSF component 542 again, so as to query the S-CSCF component to which the called number belongs, as in step S605. Accordingly, the process in FIG. 6 will enter into the second loop (ie: step S611 to step S616 ) where the abnormal VoIP signaling loop occurs, until the value of the number of forwarding times in the "maximum forwarding" is reduced to 0. If the value of the forwarding times is reduced to 0 by an IMS network element, the IMS network element may send the status code "483" to the caller (ie, the user agent device 200 ).

In the embodiment of FIG. 6 , the VoIP signaling loop is rooted in data desynchronization between the ENUM server 530 and the HSS/UPSF component 542 . Although the ENUM server 530 thinks that the called number and the HSS/UPSF component 542 belong to the same domain, the HSS/UPSF component 542 cannot query the relevant information of the called number. The electronic device 100 can detect the VoIP signaling loop through the processes shown in FIG. 3 and FIG. 4 , and obtain the root cause of the VoIP signaling loop.

Referring to FIG. 3 and FIG. 6 , in step S310 , the collection and sorting module 122 can obtain signaling information corresponding to the SIP call (SIP INVITE), and input the signaling information to the abnormal analysis module 123 . Assume that the collection and sequencing module 122 has previously obtained the SIP call corresponding to step S607, and the collection and sequencing module 122 has currently obtained the SIP call corresponding to step S610. If there is no VoIP signaling loop event matching the above-mentioned SIP call in the storage medium 120, it can not be found in the specific time range, then in step S320, the abnormal analysis module 123 can judge that a new VoIP event has occurred according to the signaling information. Signaling loop event.

If the I-CSCF element 541 has the function of detecting VoIP signaling loops, in step S330, the abnormal analysis module 123 can obtain the status code "482" sent by the I-CSCF element 541 from the signaling information, and can Judging that the status code "482" matches the status code. If the I-CSCF component 541 does not have the function of detecting VoIP signaling loops, in step S330, the abnormal analysis module 123 can obtain from the signaling information the signal sent by the IMS network component whose forwarding times value is reduced to 0. The status code "483" can be judged to match the status code "483".

In step S360, the abnormal analysis module 123 may store the signaling information in the storage medium 120, and create a new VoIP signaling loop event corresponding to the signaling information. The exception analysis module 123 can also number the VoIP signaling loop events. The VoIP signaling loop event may include information such as call identification code, called number, time stamp or status code.

In step S370, the abnormal analysis module 123 can send an alarm message through the transceiver 130, so as to notify the maintenance personnel of the telecom core network 500 that the VoIP signaling loop has occurred. The abnormal analysis module 123 can transmit the alarm message to the terminal device held by the maintenance personnel through email, mobile phone text message or IM software message.

In step S380 , the abnormal analysis module 123 can perform root cause analysis of the VoIP signaling loop.

Referring to FIG. 4 and FIG. 6 , in step S381 , the abnormal analysis module 123 can determine whether the result code in the signaling information does not match the preset result code. Assuming that the result code in the signaling information is DIAMETER ERROR USER UNKNOWN (5001), the exception analysis module 123 may determine that the result code does not match the default result code.

In step S383 , the abnormal analysis module 123 can collect information associated with the called number from various fields in the telecommunications core network 500 . Since the VoIP signaling loop event corresponding to the signaling information has been created in step S360, therefore, in step S384, the abnormal analysis module 123 can determine that the signaling information does not correspond to a new VoIP signaling loop event.

In step S387, the abnormal analysis module 123 can determine the root cause of the VoIP signaling loop, and output the root cause for reference by maintenance personnel. The root cause may include relevant content of the information obtained in step S383. For example, the exception analysis module 123 can find out that the receiver number of the ENUM DNS query belongs to the same domain as the HSS/UPSF component 542 according to the information obtained in step S383, but the HSS/UPSF component 542 cannot query the receiver number. number, so a loop is generated. The exception analysis module 123 may also find that the receiving number should belong to the same domain as another HSS/UPSF component in the information. Accordingly, the abnormal analysis module 123 can determine that the information of the receiving number of the ENUM server 530 is incorrect. The exception analysis module 123 can add the judgment result to the root cause to notify the maintenance personnel.

FIG. 7 is a signaling diagram of a VoIP call in which an abnormal VoIP signaling loop occurs according to another embodiment of the present invention. The user agent device 200 can communicate with the user agent device 300 through the telecommunication core network 500 , wherein the user agent device 200 and the user agent device 300 are served by different telecommunication operators. The telecom core network 500 may include a P-CSCF element 710 , an operator 720 and an operator 730 . The attendant console 720 may include a S-CSCF component 721 , an ENUM server 722 and an IBCF component 723 . The attendant console 730 may include an IBCF component 731 , an S-CSCF component 732 and an ENUM server 733 . The user agent device 200 and the attendant console 720 may belong to the same field. The user agent device 300 and the attendant console 730 may belong to the same field.

In FIG. 7 , step S702 to step S707 are the first cycle in which an abnormal VoIP signaling loop occurs, and steps S708 to step S713 are a second cycle in which an abnormal VoIP signaling loop occurs. Although FIG. 7 only depicts two cycles in which abnormal VoIP signaling loops occur, in fact, the number of cycles in which abnormal VoIP signaling loops occur can be more than two, until the value of the forwarding times of "maximum forwarding" is reduced. until 0.

In step S701, the UA device 200 may send a SIP call to the S-CSCF element 721 through the P-CSCF element 710 to initiate a call. A SIP call can contain information such as the calling number and the receiving number.

In step S702, the S-CSCF component 721 may send a DNS query to the ENUM server 722 according to the SIP call, so as to query the domain to which the called number belongs.

In step S703 , the ENUM server 722 may send the domain to which the called number belongs to the S-CSCF component 721 in response to the DNS query. The ENUM server 722 may indicate to the S-CSCF element 721 that the called number corresponds to the attendant console 730 .

In step S704 , the S-CSCF component 721 may transmit the SIP call request to the S-CSCF component 732 through the IBCF component 723 and the IBCF component 731 according to the response of the ENUM server 722 .

In step S705 , the S-CSCF component 732 may query the ENUM server 733 for information about the called number through DNS query in response to the SIP call request.

In step S706 , the ENUM server 733 may send a DNS query response message to the S-CSCF component 732 , wherein the response message may indicate that the called number does not belong to the operator console 730 .

In step S707 , the S-CSCF component 732 may transmit the SIP call request to the S-CSCF component 721 through the IBCF component 723 and the IBCF component 731 .

The purpose of step S707 is the same as that of step S701. Therefore, in step S708, the S-CSCF component 721 will send the DNS query to the ENUM server 722 again, as shown in step S702. Accordingly, the process in FIG. 7 will enter into the second cycle (ie: step S708 to step S713 ) where the abnormal VoIP signaling loop occurs, until the value of the number of forwarding times in the "maximum forwarding" is reduced to 0.

In the embodiment of FIG. 7 , the root cause of the VoIP signaling loop is that data is not synchronized between ENUM servers of different telecommunication providers (ie: ENUM server 722 and ENUM server 733 ), or the ENUM server 722 and ENUM server 733 ENUM server 733 The information recorded by the upstream NPDB element is incorrect. If the session initiated by the user agent device 200 does not have a good call ID control mechanism, the VoIP signaling loop will loop endlessly. The electronic device 100 can detect the VoIP signaling loop through the processes shown in FIG. 3 and FIG. 4 , and obtain the root cause of the VoIP signaling loop.

Referring to FIG. 3 and FIG. 7 , in step S310 , the collection and sorting module 122 can obtain signaling information corresponding to the SIP call, and input the signaling information to the abnormal analysis module 123 . Assume that the collection and sequencing module 122 has previously obtained the SIP call corresponding to step S701, and the collection and sequencing module 122 has currently obtained the SIP call corresponding to step S707. If there is no VoIP signaling loop event matching the above-mentioned SIP call in the storage medium 120, it can not be found in the specific time range, then in step S320, the abnormal analysis module 123 can judge that a new VoIP event has occurred according to the signaling information. Signaling loop event.

Due to the communication period of different attendant consoles, the call identification code of signaling may change. Accordingly, the IMS network element will fail to detect the VoIP signaling loop and generate status code "482" or status code "483". Therefore, in step S330, the exception analysis module 123 may determine that the status code does not match the preset status code.

Since the called number does not belong to the attendant console 720, in step S340, the abnormal analysis module 123 cannot obtain the Diameter CX interface signaling related to the result code from the signaling information.

In step S350, the abnormal analysis module 123 can determine whether the signaling information includes routing prefixes respectively corresponding to different consoles. In this embodiment, it is assumed that the abnormal analysis module 123 obtains the routing prefix "RN1" corresponding to the operator console 720 and the routing prefix "RN2" corresponding to the operator console 730 from the signaling information. Therefore, the determination result of step S350 is yes.

In step S380 , the abnormal analysis module 123 can perform root cause analysis of the VoIP signaling loop.

Referring to FIG. 4 and FIG. 7 , since the exception analysis module 123 cannot obtain the result code, the flow in FIG. 7 enters step S382 . In step S382, the abnormal analysis module 123 can determine whether the NRIs provided by different ENUM servers in the signaling information do not match. In this embodiment, the NPDB component indicates that the called number corresponds to the routing prefix "RN2" (that is, the called number belongs to the attendant console 730), but the ENUM server 733 indicates that the called number corresponds to the routing prefix "RN1" ( That is: the called number belongs to the attendant console 720), therefore, the exception analysis module 123 can determine that the NRI does not match.

Since the VoIP signaling loop event corresponding to the signaling information has not been created in step S360, therefore, in step S384, the abnormal analysis module 123 can determine that the signaling information corresponds to a new VoIP signaling loop event.

In step S385, the abnormal analysis module 123 may store the signaling information in the storage medium, and create a new VoIP signaling loop event corresponding to the signaling information. The exception analysis module 123 can also number the VoIP signaling loop events. The VoIP signaling loop event may include information such as call identification code, called number, time stamp or status code.

In step S386 , the abnormal analysis module 123 can send an alarm message through the transceiver 130 to notify the maintenance personnel of the telecommunications core network 500 that the out-of-sync data between the ENUM servers may soon cause a VoIP signaling loop event. The abnormal analysis module 123 can transmit the alarm message to the terminal device held by the maintenance personnel through email, mobile phone text message or IM software message.

In step S387, the abnormal analysis module 123 can determine the root cause of the VoIP signaling loop, and output the root cause for reference by maintenance personnel. The exception analysis module 123 can attach the relevant information of the called number (for example: the attendant station to which the called number belongs or the routing prefix corresponding to the called number) from the NPDB component and the ENUM server 733 to the root cause to notify maintenance transport personnel.

FIG. 8 shows a flow chart of a method for root cause analysis of VoIP signaling loops according to an embodiment of the present invention, wherein the method can be implemented by the electronic device 100 shown in FIG. 1 . In step S801, a plurality of signalings are retrieved from the telecommunications core network. In step S802, a plurality of signalings are sequenced according to time to obtain signaling information, wherein the signaling information includes call status codes corresponding to the session initiation agreement, result codes of location information responses, and number portability routing information. In step S803, the root cause of the VoIP signaling loop is determined according to the status code, the result code and the number portability routing information, and the root cause is output.

To sum up, the electronic device of the present invention can capture the packets or signaling of the telecommunication network for analysis, apply the characteristics of the VoIP signaling loop, and correlate the corresponding information of the relevant ENUM server or HSS/UPSF components, etc., Assist the maintenance personnel to find out the root cause of the loop.

Compared with the conventional technology, the present invention has the following benefits and advantages: (1) In addition to reporting the loop status according to the SIP status code, the present invention also provides loop root cause analysis, which can greatly improve the maintenance personnel to perform loop Accurate diagnosis, and shorten the troubleshooting time, to avoid the resource consumption of the telecommunications core network. (2) The present invention can quickly generate the basic alarm content when the loop occurs, including information such as the start time of the loop event, the loop door number, etc., so as to achieve an instant alarm function, so that the maintenance personnel can be quickly notified to return Occurrence of circle events. (3) The present invention can generate a loop warning before a loop occurs or when a loop obstacle occurs but no relevant status code is generated. The present invention can also infer the root cause of the loop event through the door number information captured by associated devices (eg, ENUM server or HSS/UPSF components). Therefore, the present invention can greatly reduce the risk of enlargement of looping obstacles. (4) The method for capturing and analyzing signaling of the present invention can judge whether there is an abnormal event without embedding an agent device (agenet) in the IMS network element or equipment for monitoring. Therefore, the impact on the performance of each component or equipment can be minimized.

100: Electronic device 110: Processor 120: storage media 121:Signaling acquisition module 122:Collection and sorting module 123: Abnormal parsing module 130: Transceiver 200, 300: user agent device 50: area 500: Telecom core network 510, 550, 710: agent call talk control functional element 520: The calling end belongs to the network 521, 543, 721, 732: service call talk control function elements 530, 722, 733: Telephone number mapping server 540: The receiver belongs to the network 541: Query the call conference control function element 542: Belonging user server/user contract server functional element 720, 730: attendant console 723, 731: Interconnecting border control functional elements S310, S320, S330, S340, S350, S360, S370, S380, S381, S382, S383, S384, S385, S386, S387, S390, S501, S502, S503, S504, S505, S506, S507, S508, S6 01. S602, S603, S604, S605, S606, S607, S608, S609, S610, S611, S612, S613, S614, S615, S616, S701, S702, S703, S704, S705, S706, S707, S708, S709, S7 10. S711, S712, S713, S801, S802, S803: steps

FIG. 1 is a schematic diagram of an electronic device for root cause analysis of VoIP signaling loops according to an embodiment of the present invention. FIG. 2 shows a schematic diagram of a telecommunication network according to an embodiment of the invention. FIG. 3 shows a flowchart of a method for detecting VoIP signaling loops according to an embodiment of the present invention. FIG. 4 shows a flowchart of a method for root cause analysis according to an embodiment of the present invention. FIG. 5 shows a signaling diagram of establishing a normal VoIP call according to an embodiment of the present invention. FIG. 6 is a signaling diagram of a VoIP call in which an abnormal VoIP signaling loop occurs according to an embodiment of the present invention. FIG. 7 is a signaling diagram of a VoIP call in which an abnormal VoIP signaling loop occurs according to another embodiment of the present invention. FIG. 8 is a flowchart of a method for root cause analysis of VoIP signaling loops according to an embodiment of the present invention.

S801, S802, S803: steps

Claims (6)

An electronic device for root cause analysis of VoIP signaling loops, comprising: a transceiver, communicatively connected to a telecommunications core network; a storage medium, storing a plurality of modules; and a processor, coupled to the storage medium and the transceiver, and access and execute the plurality of modules, wherein the plurality of modules include: a signaling retrieval module, which retrieves a plurality of signals from the telecommunications core network through the transceiver Signaling; a collection and sorting module that arranges the plurality of signalings in sequence according to time to obtain signaling information, wherein the signaling information includes the status code of the call corresponding to the initial agreement of the negotiation, the result code of the location information response, and Number portability routing information; and an abnormal analysis module, according to the status code and default status code, the result code and default result code, and the number portability routing information and second number portability routing The matching result of the information judges the root cause of the VoIP signaling loop, and outputs the root cause through the transceiver, wherein the abnormal analysis module responds to the result code and the preset result code matching to obtain the second number portability routing information from the signaling information. The electronic device according to claim 1, wherein the abnormal resolution module generates the root cause in response to the status code matching a preset status code, wherein the A root cause includes the status code, wherein the root cause indicates that a VoIP signaling loop has occurred. The electronic device according to claim 2, wherein the abnormal analysis module determines whether the result code does not match the preset result code in response to the mismatch between the status code and the preset status code, wherein the The exception resolution module generates the root cause in response to the mismatch between the result code and the preset result code, wherein the root cause indicates that the telephone number mapping server and the home subscriber server in the telecommunications core network A data out-of-sync occurred between , wherein the root cause indicates that a VoIP signaling loop is occurring. The electronic device according to claim 3, wherein the anomaly resolution module generates the root cause in response to a mismatch between the number portability routing information and the second number portability routing information, wherein the The root cause indicates that data out-of-sync occurs among the plurality of phone number mapping servers in the telecommunications core network, wherein the root cause indicates that the VoIP signaling loop is about to occur. The electronic device as claimed in claim 1, wherein the plurality of signalings respectively include a plurality of call identification codes, wherein the collection and sorting module responds to the matching of the plurality of call identification codes according to the plurality of signaling command to generate the signaling information. A method for root cause analysis of VoIP signaling loops, comprising: extracting a plurality of signalings from a telecommunications core network; arranging the plurality of signalings in sequence according to time to obtain signaling information, wherein the The signaling information includes the status code of the call corresponding to the initial agreement of the session, the location information should be Answer result code and number portability routing information; and according to the status code and default status code, the result code and default result code, and the number portability routing information and second number portability routing The matching result of the information judges the root cause of the VoIP signaling loop, and outputs the root cause, wherein the abnormal analysis module responds to the result code matching the preset result code from the The signaling information obtains the second number portability routing information.

Images