Dynamic QoS Policy Management via Remote Registry
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication systems have hard-coded quality of service (QoS) policies that cannot be easily modified once implemented, failing to adapt to changing requirements of dynamic document transport in real-time, particularly in environments where continuous high-bandwidth video and multimedia information transmission is challenging.
Innovation Solution
A system that retrieves QoS policies from a remote registry associated with document endpoints, allowing for dynamic enqueuing and transmission of documents based on offering-specific criteria, using XML documents to define and manage QoS policies, enabling flexible queue management and quota control.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If QoS policies are hard-coded into the communication system design, then the system structure is simple and stable, but the QoS parameters cannot be modified once implemented
Solution Approach 1:
The patent implements dynamic QoS policies by allowing message consumers to subscribe to offerings with specific QoS requirements and enabling real-time modification of these policies through message-based interactions. The system transitions from static hard-coded QoS to dynamic configurable QoS that can be adjusted during runtime based on changing requirements.
Solution Approach 2:
The patent introduces an intermediary layer consisting of message brokers, offerings, and subscriptions that mediate between the communication system and QoS policies. This intermediary structure allows QoS parameters to be defined and modified through messages without requiring changes to the core system architecture, thus maintaining stability while enabling flexibility.
2Adaptability or versatility
If soft-coding is used to specify QoS parameters, then the system becomes more flexible, but changes to QoS are not easily made once an information flow has commenced
Solution Approach 1:
The patent enables message consumers to self-define and self-manage their own QoS policies through subscriptions to offerings. Each consumer can independently specify their QoS requirements and modify them as needed without requiring system administrator intervention, making QoS changes easy to implement once the system is running.
Solution Approach 2:
The patent allows QoS policies to be pre-defined through offering definitions and subscription specifications before message flows commence. However, the system also enables runtime modification of these pre-defined policies through message-based updates, combining the benefits of preliminary configuration with flexible runtime adaptability.
3Adaptability or versatility
If QoS policies are dynamically changed, then the system adapts to changing application requirements, but the system complexity increases
Solution Approach 1:
The patent creates a universal QoS management framework where offerings, subscriptions, and message brokers serve multiple functions. The same infrastructure handles message routing, QoS policy definition, QoS modification, and monitoring, reducing overall system complexity despite the dynamic capabilities provided.
4Productivity
If queues are segregated by QoS policies, then delivery efficiency is improved, but queue management complexity increases
Solution Approach 1:
The patent segments queues by QoS policies and offerings, creating dedicated queues for different document types and delivery requirements. This segmentation improves delivery efficiency by allowing specialized handling of different document streams while the underlying message broker manages the complexity of multiple queues through unified routing rules.
Data Source
AI summary
A quality of service policy for one or more documents for transmission from the local storage to one or more end points for said documents through a communication system is retrieved from a remote registry associated with an offering, and said documents are enqueued according to said quality of service policy. In some cases, the registry may be co-hosted with at least one of the document end points. The quality of service policy may be derived from a transport policy for said one or more documents, and may even be such as to not specify a quality of service for delivery of some or all of the documents. In some cases, XML documents may be used to set forth the quality of service policies.