IP Library Granted Patent US 9,172,593
Granted Patent B2
US 9,172,593 · App. 13/939,529 · Granted Oct 27, 2015

System and method for identifying problems on a network

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,172,593
App. No.
13/939,529
Granted
Oct 27, 2015
Kind
B2
Abstract

Aspects of the invention may involve systems, methods, and computer readable medium. In an embodiment, a telecommunications network may contain telecommunications probes capable of generating detailed records describing network events. The telecommunications probes may be coupled to computer processors and/or memory. The memory may store detailed records created by the probes and instructions executable by the processors. The instructions may be to: identify detailed records that indicate an event failure including error codes and associated subscriber identifiers; learn a distribution of error codes and associated subscriber identifiers; detect event failures that indicate an increase in the number of subscriber identifiers for an error code; analyze attributes of the detected event failures to identify common attributes between the detected event failures; prepare a report identifying a network issue based on the identified common attributes between the detected event failures; transmit the report; and receive feedback based on the report.

Claims (49)

1. A system for identifying communication problems comprising:

a telecommunications network;

one or more telecommunications probes coupled to the telecommunications network, the telecommunications probes capable of generating detailed records describing one or more network events;

one or more processors in communication with the telecommunications probes; and

memory coupled to the one or more processors, the memory storing the detailed records received by the telecommunications probes and the memory storing instructions executable by the one or more processors, the instructions operable to:

identify detailed records that indicate an event failure including error codes and associated subscriber identifiers;

learn a distribution of error codes and associated subscriber identifiers;

detect event failures that indicate an increase in the number of subscriber identifiers for an error code;

analyze attributes of the detected event failures to identify one or more common attributes between the detected event failures;

prepare a report identifying a network issue based on the identified one or more common attributes between the detected event failures;

transmit the report; and

receive feedback based on the report.

2. The system of claim 1 , wherein an event comprises at least one of: phone on, phone connecting to the network, acquiring new base station, SMS, a data session, a phone registering on the network, or Internet access.

3. The system of claim 1 , wherein the increase in the number of subscriber identifiers for an error code crosses a threshold condition.

4. The system of claim 1 , wherein the common attributes to identify are listed in a configuration file.

5. The system of claim 1 , wherein the attributes comprise at least one of:

telephone numbers of requesting and receiving devices, location of devices, communication paths used, base station, signal tower, time, GGSN, SGSN, handset, network element, APN, cell technology, radio technology, roaming type, country, carrier, source number, destination number, destination category, destination nature of address, destination numbering plan, OPC/DPC, release location, routing natr, routing numbering plan, source category, source natr, source numbering plan, teleservice information, transmission media requirement, trunk, quality attribute, or mean opinion score.

6. A method of identifying communication problems comprising:

loading, by a computer, a first plurality of detailed records, wherein the detailed records contain attributes for one or more network events;

identifying, by the computer, a second plurality of detailed records from the first plurality of detailed records, wherein the second plurality of detailed records indicate an event failure;

detecting, by the computer, a signature in the second plurality of detailed records, wherein the signature is a pattern indicating a known failure type and associated attributes;

learning, by the computer, a typical pattern of attributes associated with the signature;

identifying, by the computer, a deviation from the learned pattern;

detecting, by the computer, one or more common attributes in a plurality of event failures based on the deviation from the learned pattern;

determining, by the computer, a problem based on the one or more common attributes in a plurality of event failures;

reporting, by the computer, the problem; and

receiving, by the computer, input on the problem.

7. The method of claim 6 , wherein deviations may be a percentage deviation in an attribute or an increase in the number of users affected by the network event.

8. The method of claim 6 , wherein the one or more common attributes are listed in a configuration file.

9. The method of claim 6 , wherein the one or more common attributes in a plurality of event failures comprises at least one of:

telephone numbers of requesting and receiving devices, location of devices, communication paths used, base station, signal tower, time, GGSN, SGSN, handset, network element, APN, cell technology, radio technology, roaming type, country, carrier, source number, destination number, destination category, destination nature of address, destination numbering plan, OPC/DPC, release location, routing natr, routing numbering plan, source category, source natr, source numbering plan, teleservice information, transmission media requirement, trunk, quality attribute, or mean opinion score.

10. The method of claim 6 , wherein input on the problem comprises one of an indication that future reports with the same attributes will be suppressed or an indication that future reports with the same attributes will be encouraged.

11. The method of claim 6 , wherein the one or more network events comprise at least one of: phone on, phone connecting to the network, acquiring new base station, SMS, a data session, a phone registering on the network, or Internet access.

12. A non-transitory computer-readable medium comprising instructions executable by one or more processors to identify communication problems, the computer-readable medium comprising one or more instructions for:

loading a first plurality of detailed records, wherein the detailed records contain attributes for one or more network events;

identifying a second plurality of detailed records from the first plurality of detailed records, wherein the second plurality of detailed records indicate an event failure;

detecting a signature in the second plurality of detailed records, wherein the signature is a pattern indicating a known failure type and associated attributes;

learning a typical pattern of attributes associated with the signature;

identifying a deviation from the learned pattern;

detecting one or more common attributes in a plurality of event failures based on the deviation from the learned pattern;

determining a problem based on the one or more common attributes in a plurality of event failures;

reporting the problem; and

receiving input on the problem.

13. The computer-readable medium of claim 12 , wherein deviations may be a percentage deviation in an attribute or an increase in the number of users affected by the network event.

14. The computer-readable medium of claim 12 , wherein the one or more common attributes between a plurality of event failures comprises at least one of:

telephone numbers of requesting and receiving devices, location of devices, communication paths used, base station, signal tower, time, GGSN, SGSN, handset, network element, APN, cell technology, radio technology, roaming type, country, carrier, source number, destination number, destination category, destination nature of address, destination numbering plan, OPC/DPC, release location, routing natr, routing numbering plan, source category, source natr, source numbering plan, teleservice information, transmission media requirement, trunk, quality attribute, or mean opinion score.

15. The computer-readable medium of claim 12 , wherein input on the problem comprises one of an indication that future reports with the same attributes will be suppressed or an indication that future reports with the same attributes will be encouraged.

16. The computer-readable medium of claim 12 , wherein the one or more common attributes are listed in a configuration file.

17. The computer-readable medium of claim 12 , wherein the one or more network events comprise at least one of: phone on, phone connecting to the network, acquiring new base station, SMS, a data session, a phone registering on the network, or Internet access.

Assignments (10)
RELEASE OF SECURITY INTEREST Recorded Apr 21, 2021
From: GOLDMAN SACHS BDC, INC. (AS SUCCESSOR-IN-INTEREST TO GOLDMAN SACHS MIDDLE MARKET LENDING CORP.), AS COLLATERAL AGENT
To: EMPIRIX INC.
Reel/Frame 055988/0203 →
RELEASE OF SECURITY INTEREST Recorded Sep 26, 2018
From: ARES CAPITAL CORPORATION, AS SUCCESSOR AGENT TO PACIFIC WESTERN BANK (AS SUCCESSOR TO CAPITALSOURCE BANK)
To: EMPIRIX INC.
Reel/Frame 046982/0124 →
SECURITY INTEREST Recorded Sep 26, 2018
From: EMPIRIX INC.
To: GOLDMAN SACHS MIDDLE MARKET LENDING CORP.
Reel/Frame 046983/0508 →
CORRECTIVE ASSIGNMENT TO CORRECT THE APPLICATION NO. 13929529 IN THE PATENT SECURITY INTEREST RECORDED ON 11/5/2015 TO 13939529 PREVIOUSLY RECORDED ON REEL 031580 FRAME 0694. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST. Recorded May 23, 2016
From: EMPIRIX INC.
To: STELLUS CAPITAL INVESTMENT CORPORATION, AS AGENT
Reel/Frame 038773/0257 →
CORRECTIVE ASSIGNMENT TO CORRECT THE APPLICATION NUMBER PREVIOUSLY RECORDED AT REEL: 031532 FRAME: 0806. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded May 6, 2016
From: EMPIRIX INC.
To: CAPITALSOURCE BANK, AS ADMINISTRATIVE AGENT
Reel/Frame 038683/0376 →
SECURITY INTEREST Recorded May 6, 2016
From: EMPIRIX INC.
To: CAPITALSOURCE BANK, AS ADMINISTRATIVE AGENT
Reel/Frame 038486/0732 →
CORRECTIVE ASSIGNMENT TO CORRECT THE RECEIVING PARTY FROM EMPIRIX TO EMPIRIX INC. PREVIOUSLY RECORDED ON REEL 031343 FRAME 0434. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Feb 28, 2014
From: KANE, CAMERON
To: EMPIRIX INC.
Reel/Frame 032369/0007 →
PATENT SECURITY AGREEMENT Recorded Nov 5, 2013
From: EMPIRIX INC.
To: STELLUS CAPITAL INVESTMENT CORPORATION, AS AGENT
Reel/Frame 031580/0694 →
SECURITY AGREEMENT Recorded Nov 1, 2013
From: EMPIRIX INC.
To: CAPITALSOURCE BANK, AS ADMINISTRATIVE AGENT
Reel/Frame 031532/0806 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 4, 2013
From: KANE, CAMERON
To: EMPIRIX
Reel/Frame 031343/0434 →