Inter-Layer QoS Mapping for Network Link Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network systems fail to consistently apply quality of service (QoS) treatments across different layers of the OSI model, particularly from the network layer to the link layer, leading to inconsistent and unpredictable end-to-end traffic management.

Innovation Solution

An Inter-Layer QoS engine that correlates network layer QoS markings with link layer QoS treatments, enabling routers and packet gateways to enforce appropriate QoS levels through bearer establishment and MPLS traffic class markings, allowing for consistent and predictable end-to-end QoS treatment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If network layer QoS markings are applied, then network layer QoS is enforced, but link layer QoS treatment does not appropriately correspond to the requested network layer QoS

Engineering Contradiction:
ImproveQoS treatment consistencyVSAvoidinter-layer QoS mapping mechanism
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary mapping mechanism that correlates network layer QoS markings with link layer QoS treatments. This intermediary layer translates between different QoS domains, ensuring that network layer QoS requests are appropriately reflected at the link layer without requiring direct integration between layers.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the QoS enforcement function into distinct layers: network layer QoS marking, intermediate QoS mapping, and link layer QoS treatment. This segmentation allows each layer to operate independently while maintaining coordinated QoS enforcement through the mapping relationships between layers.

Inventive Principle:
Principle #1Segmentation

2Reliability

If application-layer interworking is used to achieve QoS correlation, then QoS consistency can be achieved, but system complexity and processing overhead increase

Engineering Contradiction:
Improveend-to-end QoS treatmentVSAvoidapplication-layer interworking
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Instead of using application-layer interworking to achieve QoS correlation (top-down approach), the patent inverts the approach by implementing QoS mapping at the network and link layers (bottom-up approach). This eliminates the need for application-layer involvement in QoS enforcement while achieving the same end-to-end QoS consistency.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The patent extracts the QoS mapping function from the application layer and places it at the network and link layers. This extraction removes the complexity of application-layer interworking while preserving the essential QoS correlation functionality through dedicated mapping mechanisms at lower layers.

Inventive Principle:
Principle #2Taking out (Extraction)

3Ease of operation

If traditional layer-specific QoS enforcement is used, then each layer operates independently, but end-to-end QoS treatment becomes inconsistent and unpredictable

Engineering Contradiction:
Improveindependent layer operationVSAvoidQoS treatment predictability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces dynamic QoS mapping relationships between network and link layers. The mapping can be adjusted based on traffic conditions, service types, and network state, allowing layers to maintain operational independence while achieving predictable end-to-end QoS through coordinated mapping policies.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9647935B2Inter-layer quality of service preservation
Publication Date: 2017.05.09 VERIZON PATENT & LICENSING INC
  • US9647935B2 patent drawing
  • US9647935B2 patent drawing
  • US9647935B2 patent drawing

AI summary

A server device may store inter-layer quality of service (“QoS”) information, indicating a set of link layer QoS levels that are associated with a particular device, a set of network layer QoS levels that are associated with the set of link layer QoS levels, and a set of MPLS QoS levels that are associated with the set of link layer QoS levels. A network device may establish a set of bearers, that correspond to the set of link layer QoS levels, with a particular device; output information regarding the set of network layer QoS levels that are associated with the set of link layer QoS levels, to allow the particular device to select a bearer, of the set of bearers, via which to output traffic to the network device; receive, from the particular device, traffic via the bearer; and determine a particular MPLS QoS level associated with the received traffic.