Service Aware Network Caching for Traffic Bottleneck Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional network caching devices lack service awareness, leading to bottlenecks in network environments as they fail to differentiate between varying requests and prioritize traffic effectively, especially during increased network congestion.

Innovation Solution

Implementing a service aware network caching device with a Quality of Service (QoS) processor that stores service level definitions to determine and manage service priorities for requests, allowing it to service requests based on defined priorities and forward or deny them accordingly, thereby reducing bottlenecks and improving network quality of service.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a network caching device is placed between clients and server to service requests, then server load is reduced and network traffic is managed, but the caching device itself becomes a bottleneck as network activity increases

Engineering Contradiction:
Improvenetwork traffic management capabilityVSAvoidcaching device bottleneck
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The caching device dynamically adjusts its behavior based on service priorities and network conditions. It services high-priority requests immediately while queuing or denying low-priority requests during congestion, allowing the device to adapt its processing characteristics to avoid becoming a fixed bottleneck.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

Different types of network traffic are treated differently based on their service priorities. The caching device applies local quality differentiation by servicing high-priority traffic with guaranteed performance while applying different handling to low-priority traffic, preventing uniform treatment that would create bottlenecks.

Inventive Principle:
Principle #3Local quality

2Ease of operation

If conventional caching devices service all requests equally, then implementation is simple, but network congestion cannot be effectively managed during high traffic periods

Engineering Contradiction:
Improvecaching device operation simplicityVSAvoidnetwork traffic prioritization capability
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

Service priorities and traffic classification rules are established in advance before congestion occurs. The caching device uses these pre-defined priorities to automatically differentiate traffic handling during congestion, eliminating the need for complex real-time decision-making while maintaining effective prioritization.

Inventive Principle:
Principle #10Preliminary action

3Device complexity

If the caching device services all requests without differentiation, then device complexity is low, but response time increases during network congestion

Engineering Contradiction:
Improverequest processing complexityVSAvoidrequest response time
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The device dynamically adjusts its servicing behavior based on request priorities and network conditions. High-priority requests receive immediate servicing while low-priority requests are queued or denied during congestion, reducing response time for critical traffic without requiring complex processing for each individual request.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS7747662B2Service aware network caching
Publication Date: 2010.06.29 NETAPP INC
  • US7747662B2 patent drawing
  • US7747662B2 patent drawing
  • US7747662B2 patent drawing

AI summary

Embodiments of this invention provide service aware network caching. A service aware network caching device determines a service priority for traffic received from a client targeted towards a storage server connected to the caching device. The caching device transmits a response to the client based on the service priority determined by the caching device. For a particular service priority, the caching device may be configured to retrieve and store other data related to the data requested in the traffic in anticipation of subsequent requests from a client for the related data. For a particular service priority, in order to service traffic associated with a higher service priority, the caching device may also be configured to disconnect the caching device's connections to other clients or servers when the connections are associated with lower service priorities and a particular congestion state is detected.