Transparent Back-to-Back Proxy Gatekeeper for H.323 QoS
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The H.323 standard limits the inclusion of H.323 stack layer functionality to only one gatekeeper per zone, preventing its integration in devices like media aggregation managers, which hinders end-to-end service quality management and QoS delivery in H.323 systems.
Innovation Solution
A transparent back-to-back proxy gatekeeper is introduced between the third-party gatekeeper and endpoints, enabling the H.323 stack layer functionality within media aggregators to perform quality of service delivery, dynamic bandwidth reservation, and QoS path admission control, while maintaining transparency to the existing gatekeeper.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the H.323 standard limits gatekeeper functionality to one gatekeeper per zone, then the system maintains simplicity and compliance with the standard, but it prevents integration of H.323 stack layer functionality in devices like media aggregation managers, hindering end-to-end service quality management
Solution Approach 1:
The patent introduces a proxy gatekeeper as an intermediary component that sits between the media aggregation manager and the existing gatekeeper. This proxy gatekeeper implements the H.323 stack layer functionality, allowing media aggregators to perform QoS management while maintaining compatibility with the standard's one-gatekeeper-per-zone constraint. The proxy gatekeeper translates and forwards messages between the media aggregator and the existing gatekeeper, enabling functionality integration without violating standard compliance.
2Reliability
If a transparent proxy gatekeeper is introduced between the gatekeeper and endpoints, then H.323 stack layer functionality can be included in media aggregators for QoS delivery, but it increases the overall system complexity and requires additional components
Solution Approach 1:
The proxy gatekeeper serves as a transparent intermediary that enables reliable end-to-end service quality management by implementing H.323 stack layer functionality in media aggregators. It maintains message format compatibility with the existing gatekeeper while enabling enhanced QoS capabilities, thus improving reliability without requiring fundamental changes to the existing gatekeeper architecture.
Solution Approach 2:
The proxy gatekeeper creates a simplified copy or representation of the gatekeeper interface at the media aggregator level. It handles H.323 message formatting and translation, allowing the media aggregator to function with gatekeeper capabilities without duplicating the entire gatekeeper system, thereby managing complexity while enabling enhanced functionality.
3Adaptability or versatility
If the proxy gatekeeper translates H.323 messages between different formats, then compatibility is maintained with existing gatekeepers, but it increases processing complexity and message translation overhead
Solution Approach 1:
The proxy gatekeeper uses message copying and template-based translation to convert H.323 messages between different formats. It maintains standard-compliant message structures while adapting content for media aggregator-specific QoS handling, enabling format compatibility with minimal processing overhead through efficient message transformation techniques.
Data Source
AI summary
Disclosed herein is a method of executing the RAS stage up to the set-up stage in a H.323 system. The H. 323 system comprises one or more third party gatekeepers and one or more end points. A transparent back-to-back proxy gatekeeper is introduced between a third party gatekeeper and end-points. Two sets of ports are created on the transparent back-to-back proxy gatekeeper. One set of ports represent themselves as end-points to the third party gatekeeper and the other set of ports represent themselves as known ports of the third party gatekeeper to the end point. A H.323 RAS request is intercepted transparently from an end-point to a third party gatekeeper. The H.323 RAS request is addressed to a well-known port number on the third party gatekeeper. The information of the H.323 RAS registration request is stored in a local persistent copy within the back-to-back proxy gatekeeper. The H.323 RAS registration request is passed to the well-known port number on the third party gatekeeper.