IP Library Granted Patent US 9,577,895
Granted Patent B2
US 9,577,895 · App. 14/485,486 · Granted Feb 21, 2017

System, method and apparatus for troubleshooting an IP 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,577,895
App. No.
14/485,486
Granted
Feb 21, 2017
Kind
B2
Abstract

The present invention provides a system, method and apparatus for troubleshooting one or more communications between a first device and a second device. A monitoring device disposed between the first device and the second device receives a message associated with the communication(s), analyzes the received message and stores the analyzed message whenever the analyzed message satisfies one or more troubleshooting criteria. The one or more troubleshooting criteria may include one or more data element criteria, one or more event-based criteria, one or more time-based criteria, one or more logical operators or a combination thereof. The method can be implemented using a computer program embodied on a computer readable medium having one or more code segments to perform the method steps.

Claims (32)

1. A method for troubleshooting one or more communications between a first device and a second device, comprising the steps of:

receiving a message associated with the communication(s) at a monitoring device disposed between the first device and the second device;

decoding the received message;

analyzing the decoded message;

storing the analyzed message in a history buffer whenever the analyzed message does not satisfy one or more troubleshooting criteria;

storing the analyzed message in an existing log file whenever the analyzed message satisfies the troubleshooting criteria and the analyzed message is part of one or more active troubleshooting sessions;

creating a new log file and storing the analyzed message in the new log file whenever the analyzed message satisfies the troubleshooting criteria and the analyzed message is not part of the active troubleshooting sessions;

determining whether the existing log files exceed one or more capacity levels; and

performing one or more predetermined actions based on the exceeded capacity level.

2. The method as recited in claim 1 , further comprising the step of extracting one or more messages stored in the history buffer and storing the extracted messages in the new log file after the new log file is created.

3. The method as recited in claim 2 , wherein the extracted messages relate to a specified message or a specified communication session or a combination thereof.

4. The method as recited in claim 1 , further comprising the steps of:

establishing a secure communication channel between the monitoring device and a security device;

receiving the security key from the security device via the secure communication channel;

storing the security key;

decrypting the received message using a security key whenever the received message is encrypted; and

receiving a new security key and storing the new security key whenever the security key associated with the communication(s) between the first device and the second device is changed.

5. An apparatus for troubleshooting one or more communications between a first device and a second device comprising: a first network interface; a second network interface; a third network interface; a data storage; and a microprocessor communicably coupled to the first network interface, the second network interface, the third network interface, and the data storage wherein the microprocessor receives a message associated with the communication(s) via the first network interface, analyzes the received message and stores the analyzed message in the data storage whenever the analyzed message satisfies one or more troubleshooting criteria, wherein the microprocessor receives the one or more troubleshooting criteria from a control center via the second network interface communicably coupled to the microprocessor and wherein the microprocessor receives a security key via the third network interface, stores the security key in the data storage and decrypts the received message using the security key whenever the received message is encrypted.

6. The apparatus as recited in claim 5 , wherein the one or more troubleshooting criteria comprise one or more data element criteria, one or more event-based criteria, one or more time-based criteria, one or more logical operators or a combination thereof.

7. The apparatus as recited in claim 5 , wherein a new security key is received and stored whenever the security key associated with the communication(s) between the first device and the second device is changed.

8. An apparatus for troubleshooting one or more communications between a first device and a second device comprising: a first interface; a second interface; a data storage; and a microprocessor communicably coupled to the first interface, the second interface and the data storage wherein the microprocessor receives a message associated with the communication(s) at a monitoring device disposed between the first device and the second device, decodes the received message, analyzes the decoded message, stores the analyzed message in a history buffer whenever the analyzed message does not satisfy one or more troubleshooting criteria, stores the analyzed message in an existing log file whenever the analyzed message satisfies the troubleshooting criteria and the analyzed message is part of one or more active troubleshooting sessions, creates a new log file and stores the analyzed message in the new log file whenever the analyzed message satisfies the troubleshooting criteria and the analyzed message is not part of the active troubleshooting sessions, determines whether the existing log files exceed one or more capacity levels, and performs one or more predetermined actions based on the exceeded capacity level.

9. The apparatus as recited in claim 8 , further comprising wherein the microprocessor extracts one or more messages stored in the history buffer and stores the extracted messages in the new log file after the new log file is created.

10. The apparatus as recited in claim 8 , wherein the extracted messages relate to a specified message or a specified communication session or a combination thereof.

11. The apparatus as recited in claim 8 , wherein the microprocessor: establishes a secure communication channel between the monitoring device and a security device; receives the security key from the security device via the secure communication channel; stores the security key; decrypts the received message using a security key whenever the received message is encrypted; and receives a new security key and stores the new security key whenever the security key associated with the communication(s) between the first device and the second device is changed.

12. A method for troubleshooting one or more communications between a first device and a second device comprising:

receiving, by a microprocessor, a message associated with the communication(s) via a first hardware network interface;

analyzing, by the microprocessor, the received message;

storing, by the microprocessor, the analyzed message in a data storage whenever the analyzed message satisfies one or more troubleshooting criteria, wherein the microprocessor receives the one or more troubleshooting criteria from a control center via a second hardware network interface and wherein the microprocessor receives a security key via a third hardware network interface;

storing, by the microprocessor, the security key in the data storage; and

decrypting the received message using the security key whenever the received message is encrypted.

13. The method of claim 12 , wherein the one or more troubleshooting criteria comprise one or more data element criteria, one or more event-based criteria, one or more time-based criteria, one or more logical operators, or a combination thereof.

14. The method of claim 12 , wherein a new security key is received and stored whenever the security key associated with the communication(s) between the first device and the second device is changed.

Assignments (15)
(SECURITY INTEREST) GRANTOR'S NAME CHANGE Recorded Sep 21, 2023
From: AVAYA INC.
To: AVAYA LLC
Reel/Frame 065019/0231 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 61087/0386) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063690/0359 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 53955/0436) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063705/0023 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001) Recorded May 18, 2023
From: GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT
To: ZANG, INC. (FORMER NAME OF AVAYA CLOUD INC.); AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; HYPERQUALITY, INC.; HYPERQUALITY II, LLC; CAAS TECHNOLOGIES, LLC; AVAYA MANAGEMENT L.P.
Reel/Frame 063779/0622 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 4, 2023
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 063542/0662 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 3, 2023
From: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; KNOAHSOFT INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB [COLLATERAL AGENT]
Reel/Frame 063742/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026 Recorded Apr 26, 2023
From: CITIBANK, N.A., AS COLLATERAL AGENT
To: AVAYA HOLDINGS CORP.; AVAYA INC.; AVAYA MANAGEMENT L.P.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063457/0001 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Aug 5, 2022
From: AVAYA INC.; INTELLISIST, INC.; AVAYA MANAGEMENT L.P.; AVAYA CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 061087/0386 →
SECURITY INTEREST Recorded Sep 25, 2020
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 053955/0436 →
SECURITY INTEREST Recorded Jan 23, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 045124/0026 →
SECURITY INTEREST Recorded Jan 10, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 045034/0001 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001 Recorded Dec 15, 2017
From: CITIBANK, N.A.
To: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL COMMUNICATIONS CORPORATION); VPNET TECHNOLOGIES, INC.
Reel/Frame 044893/0531 →
SECURITY INTEREST Recorded Jan 27, 2017
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS CORPORATION; VPNET TECHNOLOGIES, INC.
To: CITIBANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 041576/0001 →
MERGER AND CHANGE OF NAME Recorded May 15, 2015
From: SIPERA SYSTEMS, INC.; AVAYA INC.
To: AVAYA INC.
Reel/Frame 035648/0955 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 15, 2015
From: NAIM, GHASSAN; KURAPATI, SRIKRISHNA
To: SIPERA SYSTEMS, INC.
Reel/Frame 035648/0821 →