Network Device Transaction Prioritization via Packet Metadata
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network devices cannot effectively prioritize individual transactions within web applications without altering the application itself, as they lack the capability to inspect data at the application layer and can only inspect packet headers at the network layer, limiting their ability to differentiate and manage transaction importance.
Innovation Solution
The system modifies packet headers to include metadata that can be interpreted by network devices, using the DSCP and ECN fields in the TOS field to signal the importance of transactions, allowing network devices to provide alternate levels of service without violating network standards, thereby enabling transaction awareness and prioritization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If network devices inspect packet headers at the network layer only, then device complexity is reduced and ease of operation is improved, but the ability to differentiate and prioritize individual transactions within web applications is lost
Solution Approach 1:
The patent extends network device capability from the traditional network layer (Layer 3) to the application layer (Layer 7) by introducing a new dimension of inspection. Network devices now examine HTTP headers and application-layer data within packets, enabling them to identify and prioritize specific transactions based on application context while maintaining their core network layer routing functions. This multi-layer inspection approach allows devices to operate effectively at both levels simultaneously.
Solution Approach 2:
The patent introduces an intermediary mechanism in the form of modified packet headers that carry transaction identification information from the application layer down to the network layer. By embedding application-layer transaction identifiers into packet header fields, the system enables network devices to prioritize transactions without requiring complex application-layer processing, thus maintaining operational simplicity while gaining transaction differentiation capability.
2Adaptability or versatility
If network devices are enhanced to inspect application layer data, then transaction prioritization capability is improved, but device complexity and processing requirements increase
Solution Approach 1:
The patent implements preliminary action by having application-layer components (such as web servers or load balancers) tag packets with transaction identification information before packets reach network devices. This pre-marking approach allows network devices to perform simple header-based prioritization without needing to perform complex application-layer analysis, thereby reducing device complexity while maintaining transaction prioritization capability.
Solution Approach 2:
The patent segments the transaction prioritization function into separate components: application-layer tagging (performed by servers) and network-layer prioritization (performed by network devices). This segmentation allows each component to perform its specialized function efficiently, reducing the complexity burden on network devices while preserving the overall transaction prioritization capability of the system.
3Adaptability or versatility
If packet headers are modified to include application layer metadata, then transaction awareness is improved, but loss of information in standard packet formats occurs
Solution Approach 1:
The patent applies universality by designing packet header fields that serve multiple functions: standard routing information and application-layer transaction identification. By making header fields multi-functional, the system embeds transaction metadata without requiring additional dedicated space, thus preserving standard packet formats while enabling transaction awareness through existing header structures that can carry dual purposes.
Data Source
AI summary
Methods and apparatuses for prioritizing transactions are disclosed. An example method of an application performance monitor (APM) comprises intercepting a first packet being transmitted in a network that is monitored by the APM; determining that the first packet is associated with a transaction of the web application that is to be provided with an alternate level of service; modifying a field in the first packet to include metadata interpretable by at least one network device in the network to cause the at least one network device to provide the alternate level of service; and injecting the first packet into the network. The APM may cause network devices to prioritize a specific transaction of an application based on importance.