Forked Communication Session Bandwidth Allocation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Forking a communication session across multiple endpoints can lead to bandwidth allocation issues, resulting in dropped calls due to exceeding available network bandwidth, as existing systems allocate bandwidth based on the sum of individual endpoints' requirements rather than the highest required bandwidth.
Innovation Solution
A system that determines the highest bandwidth requirement for a forked communication session based on the highest bandwidth requirement of one or more codecs involved, allocating that bandwidth to ensure the session can be established without unnecessary allocations for unanswerered forks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If bandwidth is allocated based on the sum of individual endpoints' requirements for forked sessions, then each endpoint can potentially use full bandwidth, but the total bandwidth allocation exceeds available network capacity causing dropped calls
Solution Approach 1:
The patent merges the bandwidth allocation for multiple forked communication endpoints into a single unified allocation based on the highest bandwidth requirement among all endpoints, rather than allocating separate bandwidth for each endpoint. This consolidation ensures that the total bandwidth allocation does not exceed available network capacity while still allowing any single endpoint to utilize the full allocated bandwidth when needed.
2Adaptability or versatility
If bandwidth is allocated for each forked endpoint individually, then each endpoint has sufficient bandwidth available, but the total allocation exceeds 100 Kbps causing network overload
Solution Approach 1:
The patent changes the bandwidth allocation parameter from a per-endpoint basis to a session-level basis. Instead of allocating bandwidth independently to each forked endpoint (which would result in multiple times the actual needed bandwidth), the system allocates bandwidth once at the session level based on the highest requirement, dynamically adjusting the allocation to match actual network needs and avoiding waste.
3Reliability
If the system allocates maximum bandwidth to all forked sessions, then communication quality is maintained, but network resources are exhausted and calls are dropped
Solution Approach 1:
The patent applies partial action by allocating bandwidth equal to the highest requirement among forked endpoints rather than the sum of all requirements. This partial allocation is sufficient to maintain communication quality for any single active endpoint while avoiding the excessive bandwidth consumption that would exhaust network resources and cause call drops.
Data Source
AI summary
A request for a communication session is received by a system. For example, a request to establish a voice communication session is received by the system. The system determines whether the request for the communication session is to be forked to a plurality of communication endpoints. If the communication session is to be forked, a highest bandwidth requirement for the forked communication session is determined. The determined highest bandwidth requirement for the forked communication session is based on a highest bandwidth requirement of one or more codecs that are defined in the received request for the communication session. The determined highest bandwidth requirement for the forked communication session is allocated so that the forked communication session can be established.