Coordination Layer for Multi-Domain QoS Admission Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current quality of service (QoS) architectures in transport networks, such as Integrated Services and Differentiated Services, face challenges in coordinating admission control across multiple domains with different QoS architectures, leading to difficulties in providing end-to-end QoS guarantees.
Innovation Solution
A coordination layer is introduced that sits above the admission control interfaces of transport network domains, allowing for the distribution and combination of admission control requests and responses across multiple domains, independent of the QoS architectures used, through a hierarchy of coordinator entities that exchange coordination messages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple QoS architectures are used across different transport network domains, then each domain can operate with its own preferred QoS mechanism, but coordination of admission control across domains becomes difficult and complex
Solution Approach 1:
A coordination layer is introduced between the QoS signaller and the transport network domains. This coordination layer receives admission control requests, translates them into domain-specific QoS messages, and coordinates with multiple domains using different QoS architectures (such as RSVP for Integrated Services and DiffServ for Differentiated Services). The coordination layer acts as an intermediary that handles the complexity of multi-architecture coordination, allowing domains to operate independently with their own QoS mechanisms while still achieving end-to-end QoS coordination.
2Device complexity
If a single QoS architecture is enforced across all domains, then coordination becomes simpler, but adaptability to different network domain preferences and requirements is reduced
Solution Approach 1:
The coordination layer is designed with multi-functionality to handle multiple QoS architectures simultaneously. It can translate between different QoS message formats (such as RSVP messages for Integrated Services and DiffServ messages for Differentiated Services) and coordinate admission control across domains using different architectures. This universal approach allows the system to maintain simplicity in coordination while adapting to various domain preferences and requirements.
3Productivity
If domain-specific QoS messages are used directly without translation, then each domain operates efficiently with its native format, but the QoS signaller must understand multiple QoS architectures increasing its complexity
Solution Approach 1:
The QoS signaller extracts the essential QoS requirements from application layer requests without needing to understand domain-specific QoS architectures. The coordination layer then takes these extracted requirements and translates them into the appropriate domain-specific QoS messages (such as RSVP or DiffServ messages). This extraction approach allows domains to operate efficiently with their native formats while the QoS signaller remains simple and architecture-agnostic.
4Reliability
If admission control requests are translated to each domain's specific format, then end-to-end QoS can be guaranteed across domains, but the translation and coordination process increases processing time
Solution Approach 1:
The coordination layer performs preliminary translation of QoS requests into domain-specific formats before forwarding them to the respective domains. By preparing the appropriate QoS messages in advance (such as RSVP PATH messages or DiffServ admission requests), the coordination layer enables domains to process admission control requests more efficiently without requiring real-time translation during the admission control decision process, thus reducing overall processing time while maintaining end-to-end QoS guarantees.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The invention provides a coordination layer of coordinating entities provided intermediate the admission control interfaces of the transport network domains, and any QoS signaller which signals QoS requests on behalf of the application layer. The coordination layer acts to distribute an admission control request across the multiple transport network domains by the use of coordination request messages containing the admission control request being forwarded through the coordination layer of coordinating entities. At each coordinating entity the admission control request is passed on to the admission control interface of the transport network which the coordinating entity serves, and an admission control response obtained. This admission control response is then combined with admission control responses from the other domains which are propagated through the coordination layer via coordination messages. The result is that the coordination layer acts to combine the various admission control responses into a combined response, which can be provided back to the QoS signaller (or other requesting entity). Thus, coordination of admission control across multiple transport network domains is achieved, without a QoS signaller having to contact each individual domain.