Gatekeeper QoS Model Resource Reallocation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Quality of Service (QoS) models in packet switched networks face challenges in scaling and managing resource reservations, particularly in ensuring low-latency transmission for critical traffic types like voice and streaming media, as they become difficult to manage with increased network traffic volume.
Innovation Solution
The method involves intelligently reallocating resources reserved for QoS models based on client demand, performance of traffic flows, and desired traffic features, using a Gatekeeper to monitor and adjust bandwidth allocation among flows, withdrawing underperforming QoS models and reallocating resources to improve performance and desirability indicators.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If IntServ architecture is used to guarantee QoS for packet streams, then transmission quality is improved, but device complexity and management difficulty increase significantly
Solution Approach 1:
The patent introduces a gatekeeper as an intermediary component that centralizes QoS management functions. The gatekeeper receives QoS requirements from endpoints, performs resource availability checks, and establishes resource reservations across multiple routers. This intermediary approach transfers the management complexity from distributed router components to a centralized entity, reducing the burden on individual network devices while maintaining QoS guarantees.
2Reliability
If resource reservations are made in each router for IntServ, then transmission reliability is improved, but ease of operation deteriorates as network traffic volume increases
Solution Approach 1:
The patent merges multiple QoS management functions into a single gatekeeper entity. Instead of each router independently managing reservations, the gatekeeper consolidates resource availability checking, reservation establishment, and modification functions. This merging reduces operational complexity by providing a unified management interface and centralized control, making it easier to manage reservations even as network traffic volume increases.
3Ease of operation
If DiffServ architecture is used to classify traffic into predetermined classes, then ease of operation is improved, but adaptability to dynamic QoS requirements deteriorates
Solution Approach 1:
The patent enables dynamic QoS model selection and modification within the DiffServ framework. Instead of relying solely on predetermined static classes, the system allows QoS parameters and models to be dynamically adjusted based on current network conditions and traffic requirements. The gatekeeper can modify resource allocations and QoS parameters in real-time, providing adaptability while maintaining the operational simplicity of class-based routing.
4Device complexity
If static resource allocation is used for QoS models, then device complexity is reduced, but productivity and network efficiency deteriorate when traffic patterns change
Solution Approach 1:
The patent implements feedback mechanisms that monitor network traffic patterns and QoS performance metrics. The gatekeeper receives information about actual traffic flows, resource utilization, and QoS compliance, then uses this feedback to dynamically adjust resource allocations. This feedback loop enables the system to adapt to changing traffic patterns and optimize network efficiency without requiring complex manual reconfiguration, maintaining relatively simple device operation while improving productivity.
Data Source
AI summary
The present invention provides a computer implemented method for allocating resources to Quality of Service, QoS, models in a network, the method comprising: selecting a route in the network, wherein the route comprises a plurality of flows of network traffic; obtaining model-to-route mapping data identifying a plurality of QoS models, wherein each QoS model is used by at least one of the plurality of flows of network traffic; monitoring the plurality of flows of network traffic to determine a characteristic of each of the plurality of flows; and in the event that one of the QoS models is withdrawn, reallocating resources of the selected route to flows of network traffic along that route, wherein the reallocation is based on at least one of: the QoS model used by each of the flows of network traffic along that route; and the characteristic of each of the flows.