IP Library Granted Patent US 7,921,224
Granted Patent B2
US 7,921,224 · App. 11/647,931 · Granted Apr 5, 2011

Method of maintaining traffic services through congestion caused by network failovers

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 7,921,224
App. No.
11/647,931
Granted
Apr 5, 2011
Kind
B2
Abstract

In a method for controlling data traffic in a wireless or other communication network, one or more hardware/software agents are deployed to interface with one or more network entities such as routers, switches, backhaul transmission lines, and wireless base stations. The agents monitor the L1 (physical) and L2 (data link) layers of the network for the presence of indicators associated with network failover operations, such as DS1 alarms and protocol errors, respectively. Based on detected indicators across all monitored network entities, the agents determine if a failover operation has occurred. If so, data congestion associated with the failover operation is controlled according to a failover congestion monitoring and recovery mode (e.g., a data source backoff model), to reduce instances of dropped calls that would otherwise occur if the failover congestion were handled according to a general purpose congestion monitoring and recovery mode of the network.

Claims (56)

1. A method of data traffic control in a communication network, said method comprising:

monitoring, using at least one network entity of the network, data traffic to determine if a failover operation has occurred in the network; and, if so,

controlling, using the at least one network entity of the network, the data traffic in the network based on a differentiation between data congestion associated with data traffic volume in the network and data congestion associated with the failover operation; wherein:

the data congestion associated with the data traffic volume in the network and the data congestion associated with the failover operation are controlled using first and second traffic control modes, respectively;

the first mode is a general purpose congestion monitoring and recovery mode for controlling data congestion in the network without regard to any particular source of the data congestion; and

the second mode is a failover congestion monitoring and recovery mode formulated to prevent instances of dropped communications on the network associated with the failover operation including instances that would be permitted by the first mode.

2. The method of claim 1 further comprising:

monitoring a physical layer of the network and a data link layer of the network for indications associated with failover operations in the network using the at least one network entity of the network, said physical and data link layers being associated with the at least one network entity for the transmission of data across the network.

3. The method of claim 2 further comprising:

correlating said failover indications to a designated time scale of data transfer over the network using the at least one network entity of the network; and

determining if a failover operation has occurred based on the failover indications correlated to the designated time scale using the at least one network entity of the network.

4. The method of claim 3 wherein:

a plurality of network entities are monitored for failover indications; and

the failover indications for said plurality of network entities are correlated to the time scale.

5. The method of claim 4 wherein:

the physical layer is monitored for occurrences of physical layer alarms generated by any of the plurality of network entities; and

the data link layer is monitored for occurrences of data link protocol errors and/or information exchanges associated with failover operations in the data link layer, said data link layer being associated with said plurality of network entities.

6. The method of claim 2 wherein:

the physical layer is monitored for occurrences of physical layer alarms generated by the at least one network entity; and

the data link layer is monitored for occurrences of data link protocol errors and/or information exchanges associated with failover operations in the data link layer.

7. The method of claim 1 wherein the second mode uses a data source backoff model for controlling delays in transmission and/or re-transmission of data packets associated with the data congestion associated with the failover operation.

8. The method of claim 7 further comprising:

monitoring a physical layer of the network and a data link layer of the network for indications associated with failover operations in the network using the at least one network entity of the network, said physical and data link layers being associated with the at least one network entity for the transmission of data across the network.

9. The method of claim 8 further comprising:

correlating said failover indications to a time scale of data transfer over the network using the at least one network entity of the network; and

determining if a failover operation has occurred based on the failover indications correlated to the time scale using the at least one network entity of the network.

10. The method of claim 9 wherein:

a plurality of network entities are monitored for failover indications; and

the failover indications for said plurality of network entities are correlated to the time scale.

11. The method of claim 10 wherein:

the physical layer is monitored for occurrences of physical layer alarms generated by the plurality of network entities; and

the data link layer is monitored for occurrences of data link protocol errors and/or information exchanges associated with failover operations in the data link layer, said data link layer being associated with said plurality of network entities.

12. The method of claim 8 wherein:

the physical layer is monitored for occurrences of physical layer alarms generated by the at least one network entity; and

the data link layer is monitored for occurrences of data link protocol errors and/or information exchanges associated with failover operations in the data link layer.

13. A method of data traffic control in a communication network including a plurality of network entities, said method comprising:

monitoring data traffic of the communication network for indications associated with failover operations in the network using at least one of the network entities;

determining that a failover operation has occurred in the network based on said indications using the at least one of the network entities; and

controlling data congestion associated with the failover operation according to a failover congestion monitoring and recovery mode using the at least one of the network entities;

wherein the failover congestion monitoring and recovery mode is configured for preventing instances of dropped communications on the network associated with failover operations including instances that would be permitted by a general purpose traffic control mode of the network where the association of the failover congestion with the failover operation is not considered;

wherein the failover congestion monitoring and recovery mode utilizes a data source backoff model for controlling delays in transmission and/or re-transmission of data packets associated with said communications.

14. The method of claim 13 further comprising:

monitoring a physical layer of the network and a data link layer of the network for said indications associated with failover operations in the network using the at least one of the network entities, said physical and data link layers being associated with said network entities for the transmission of data across the network.

15. The method of claim 14 further comprising:

correlating said failover indications to a time scale of data transfer over the network using the at least one of the network entities; and

determining, using the at least one of the network entities, that the failover operation has occurred based on the failover indications correlated to the time scale.

16. The method of claim 15 wherein:

the physical layer is monitored for occurrences of physical layer alarms generated by any of the at least one of the network entities; and

the data link layer is monitored for occurrences of data link protocol errors and/or information exchanges associated with failover operations in the data link layer, said data link layer being associated with said at least one network entity.

17. A method of data traffic control in a communication network including a plurality of network elements, said method comprising:

monitoring a physical layer of the network and a data link layer of the network for indicators associated with failover operations in the network using a network entity of the network, said physical and data link layers being associated with at least the network entity;

determining whether a failover operation has occurred based on the indicators associated with failover operations using the network entity of the network; and, if so,

controlling data traffic associated with the failover operation using a data source backoff model using the network entity of the network;

wherein the failover congestion monitoring and recovery mode is configured for preventing instances of dropped communications on the network associated with failover operations including instances that would be permitted by a general purpose traffic control mode of the network where the association of the failover congestion with the failover operation is not considered;

wherein the failover congestion monitoring and recovery mode utilizes a data source backoff model for controlling delays in transmission and/or re-transmission of data packets associated with said communications.

18. The method of claim 17 wherein the data associated with the indicators includes (i) time data of when the indicators occurred and (ii) data relating to at least the network entity with which the indicators are respectively associated.

Assignments (11)
PATENT SECURITY AGREEMENT Recorded Apr 22, 2023
From: RPX CORPORATION
To: BARINGS FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 063429/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 28, 2021
From: PROVENANCE ASSET GROUP LLC
To: RPX CORPORATION
Reel/Frame 059352/0001 →
RELEASE OF SECURITY INTEREST Recorded Nov 30, 2021
From: NOKIA US HOLDINGS INC.
To: PROVENANCE ASSET GROUP HOLDINGS LLC; PROVENANCE ASSET GROUP LLC
Reel/Frame 058363/0723 →
RELEASE OF SECURITY INTEREST Recorded Nov 30, 2021
From: CORTLAND CAPITAL MARKETS SERVICES LLC
To: PROVENANCE ASSET GROUP HOLDINGS LLC; PROVENANCE ASSET GROUP LLC
Reel/Frame 058983/0104 →
ASSIGNMENT AND ASSUMPTION AGREEMENT Recorded Feb 14, 2019
From: NOKIA USA INC.
To: NOKIA US HOLDINGS INC.
Reel/Frame 048370/0682 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 13, 2017
From: NOKIA TECHNOLOGIES OY; NOKIA SOLUTIONS AND NETWORKS BV; ALCATEL LUCENT SAS
To: PROVENANCE ASSET GROUP LLC
Reel/Frame 043877/0001 →
SECURITY INTEREST Recorded Sep 13, 2017
From: PROVENANCE ASSET GROUP HOLDINGS, LLC; PROVENANCE ASSET GROUP LLC
To: NOKIA USA INC.
Reel/Frame 043879/0001 →
SECURITY INTEREST Recorded Sep 13, 2017
From: PROVENANCE ASSET GROUP HOLDINGS, LLC; PROVENANCE ASSET GROUP, LLC
To: CORTLAND CAPITAL MARKET SERVICES, LLC
Reel/Frame 043967/0001 →
RELEASE OF SECURITY INTEREST Recorded Oct 9, 2014
From: CREDIT SUISSE AG
To: ALCATEL-LUCENT USA INC.
Reel/Frame 033950/0001 →
SECURITY INTEREST Recorded Mar 7, 2013
From: ALCATEL-LUCENT USA INC.
To: CREDIT SUISSE AG
Reel/Frame 030510/0627 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 24, 2010
From: JAJOO, SANDESH R.; SODANKOOR, CHANDRASHEKAR
To: ALCATEL-LUCENT USA INC.
Reel/Frame 023980/0626 →