Quality-Aware URI Negotiation for Network Path Constraints
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current communication networks lack the ability for application clients and servers to effectively negotiate quality of service parameters, such as latency, jitter, and bandwidth, which are crucial for delivering high-quality resources like audio and video streams, as existing protocols primarily operate at lower layers and do not allow end-user requests for quality assurance.
Innovation Solution
A method where the application client and server use a quality-aware protocol, designated by a specific URI scheme (e.g., 'httpq'), to negotiate and enforce quality parameters like latency, jitter, and bandwidth constraints through an iterative message sequence, allowing network nodes to adjust their settings to meet these requirements, and optionally include headers like Q-Latency-constraint, Q-Jitter-constraint, and Q-Bandwidth-constraint in HTTP messages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If existing protocols (DiffServ, RSVP) are used at lower layers, then quality of service can be ensured along communication path, but end users cannot request quality of service and application level quality negotiation is not possible
Solution Approach 1:
The patent introduces a new dimension to the protocol stack by implementing quality of service negotiation at the application layer (HTTP level) rather than only at lower network layers. This is achieved through quality-aware HTTP headers (Q-headers) that carry quality parameters and constraints between application client and server, enabling application-specific quality negotiation without modifying the underlying transport or network layer protocols.
Solution Approach 2:
The patent uses quality-aware HTTP headers as an intermediary mechanism to translate application-level quality requirements into network-enforceable parameters. These headers act as a mediator between the application layer (where quality needs are defined) and the network layer (where quality enforcement occurs), allowing quality of service negotiation without direct modification of lower layer protocols.
2Adaptability or versatility
If quality parameters are negotiated at application level, then end users can request quality of service, but existing standards and practices must be maintained for compatibility
Solution Approach 1:
The patent makes HTTP headers multi-functional by extending them to carry both traditional HTTP metadata and quality of service parameters. The same HTTP request and response mechanisms that already exist for web communication are now also used for quality negotiation, allowing a single protocol to serve multiple purposes without requiring separate specialized protocols.
Solution Approach 2:
The patent changes the parameters of existing HTTP headers to include quality-related information. By modifying header fields to carry quality constraints and measurements, the system enables quality of service negotiation using the familiar HTTP framework, maintaining compatibility while adding new functionality through parameter extension.
3Reliability
If quality parameters are enforced by network nodes, then smooth rendering of multimedia resources is achieved, but additional quality negotiation messages are required
Solution Approach 1:
The patent performs quality negotiation in advance before actual resource delivery. Quality constraints are established during the initial HTTP request-response exchange, allowing network nodes to pre-configure quality enforcement mechanisms. This preliminary quality agreement prevents the need for continuous negotiation during resource delivery, reducing overall time loss.
Solution Approach 2:
The patent implements quality measurement and feedback mechanisms where application clients can measure actual quality parameters and initiate re-negotiation when quality degradation is detected. This feedback loop ensures quality compliance without requiring constant proactive negotiation, as the system only re-negotiates when actually needed based on measured quality conditions.
Data Source
AI summary
Method for an application client (C) and an application server (S) to negotiate quality parameters of a path (P) within a communication network (NAC, NMC, NB, NMS, NAS) connecting them. The method comprises the application client (C) sending to the application server (S) a request containing an identifier of a resource and said application server (S) sending at least an answer containing data associated to said resource to the application client (C). This request and this answer are transmitted through the path (P). The method is characterized in that the identifier specifies that the at least one answer should be compliant to a quality-aware protocol and contain quality parameters to be enforced by network nodes along the path (P).