Application Layer QoS Marking for Network Priority Handling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

There is no mechanism for an application layer to indicate requested quality of service (QoS) handling to a network layer, resulting in suboptimal priority considerations for application layer messages, leading to communication errors and inefficient use of network resources.

Innovation Solution

The application layer classifies and marks application layer protocol data units (PDUs) with a priority level, which is then mapped to a network layer priority class, allowing the network layer to handle traffic based on optimal priority considerations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If application layer messages are transmitted without QoS marking, then the network layer can handle traffic using default best-effort delivery, but application layer traffic is handled with suboptimal priority considerations leading to communication errors and packet drops

Engineering Contradiction:
Improvecommunication reliabilityVSAvoidprotocol complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent embeds QoS marking capabilities within existing application layer protocols by defining new header fields (Priority Code Point and Differentiated Services Code Point) that nest within the application layer protocol structure. This allows QoS information to be carried alongside application data without requiring separate signaling mechanisms or external QoS infrastructure, thereby improving reliability while minimizing added complexity.

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The patent applies QoS marking at the application layer before packets are transmitted to the network layer. By classifying and marking packets with appropriate priority levels and DSCP values in advance, the system ensures that QoS handling is predetermined and automated, eliminating the need for real-time priority decisions at network layer routers and improving communication reliability without requiring complex runtime processing.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If application layer QoS marking is implemented, then traffic can be handled with optimal priority considerations, but the application layer protocol structure becomes more complex

Engineering Contradiction:
Improvenetwork resource efficiencyVSAvoidprotocol structure complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent defines application layer header fields that serve multiple functions: the Priority Code Point field provides application-specific priority classification, while the Differentiated Services Code Point field enables interoperability with standard IP QoS infrastructure. This multi-functionality allows a single marking mechanism to improve network resource efficiency while maintaining compatibility with existing protocols, thereby reducing the net increase in complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent introduces standardized parameter fields (PCP and DSCP) with defined bit structures and value ranges that can be systematically applied across different application protocols. By establishing fixed parameter formats and mapping relationships, the patent enables automated QoS handling without requiring complex protocol-specific processing logic, thus improving productivity while controlling complexity through parameter standardization.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20240430205A1Systems and methods for application layer protocol quality of service marking
Publication Date: 2024.12.26 VERIZON PATENT & LICENSING INC
  • US20240430205A1 patent drawing
  • US20240430205A1 patent drawing
  • US20240430205A1 patent drawing

AI summary

In some implementations, an application device may generate a protocol data unit (PDU) associated with an application layer protocol, with the PDU including a header field. The application device may determine a priority level associated with the PDU. The application device may mark the header field with an indication of the priority level associated with the PDU. The application device may transmit, to a second network device, the PDU using the application layer protocol.