Intercluster Call Admission Control Bandwidth Deduction Prevention

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Inconsistent network management and bandwidth allocation lead to disruptions and poor call quality, especially during congestion, as existing protocols like RSVP struggle to accurately manage data sessions and prevent duplicate bandwidth deductions in shared network environments.

Innovation Solution

Implementing a method within an intercluster Call Admission Control (CAC) arrangement that uses Unified Communications Manager (UCM) and Location Bandwidth Manager (LBM) to model complex networks, track bandwidth across clusters, and prevent duplicate bandwidth deductions by employing fate-share IDs and session identifiers, ensuring efficient bandwidth allocation and maintaining call quality.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If RSVP is used to reserve bandwidth along data paths, then resource reservation capability is improved, but duplicate bandwidth deductions and inconsistent network management occur in shared network environments

Engineering Contradiction:
Improvebandwidth reservation reliabilityVSAvoidbandwidth accounting accuracy
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent segments the bandwidth management function by introducing separate Location Bandwidth Managers (LBMs) at each network location, which independently track and account for bandwidth deductions. This segmentation prevents duplicate deductions by ensuring each LBM maintains its own local account of reserved bandwidth, resolving the inconsistency problem in shared network environments while maintaining reliable RSVP-based reservations.

Inventive Principle:
Principle #1Segmentation

2Productivity

If bandwidth is shared across multiple clusters and call agents, then network resource utilization is improved, but duplicate bandwidth deductions occur leading to call disruptions

Engineering Contradiction:
Improvenetwork resource utilizationVSAvoidcall session stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where Location Bandwidth Managers continuously monitor and report bandwidth reservation status back to the network. When a bandwidth deduction occurs at any location, the LBM provides feedback to prevent duplicate deductions at other locations, ensuring call session stability while maintaining efficient shared bandwidth utilization across clusters.

Inventive Principle:
Principle #23Feedback

3Power

If routers handle increased bandwidth demands during congestion, then network capacity is improved, but packets are indiscriminately discarded compromising call quality

Engineering Contradiction:
Improvenetwork bandwidth capacityVSAvoidpacket loss during congestion
Core Design Contradiction:
PowerVSObject-affected harmful factors

Solution Approach 1:

The patent applies preliminary action by reserving bandwidth before congestion occurs through RSVP signaling. Location Bandwidth Managers pre-account for bandwidth deductions and establish reserved bandwidth buckets in advance, ensuring that when congestion occurs, packets with reserved bandwidth are protected from indiscriminate discarding, maintaining call quality during high-demand periods.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9450882B2Method and apparatus for supporting call admission control using graph assembly and fate-share identifiers
Publication Date: 2016.09.20 CISCO TECHNOLOGY INC
  • US9450882B2 patent drawing
  • US9450882B2 patent drawing
  • US9450882B2 patent drawing

AI summary

In one embodiment, a method includes obtaining a potential bandwidth deduction at a call agent, the call agent being associated with an intercluster call admission control (CAC) arrangement in which bandwidth is shared, the potential bandwidth deduction being associated with a session. The method also includes determining whether the potential bandwidth deduction is a duplicate bandwidth deduction, deducting the potential bandwidth deduction from a bandwidth bucket when it is determined that the potential bandwidth deduction is not the duplicate bandwidth deduction, and ignoring the potential bandwidth deduction when it is determined that the potential bandwidth deduction is the duplicate bandwidth deduction.