Application-Based Data Labeling for Network Traffic Prioritization

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Network devices struggle to identify the application that generated a data packet, as traditional packet headers do not provide this information, leading to challenges in prioritizing and managing network traffic effectively.

Innovation Solution

The implementation of application-based labeling techniques, where a virtual socket generates a label based on the application, allowing the kernel to associate this label with non-packetized data before packetization, enabling informed decisions about data packet prioritization, routing, and security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If network devices inspect data packets to infer application type, then traffic prioritization capability is improved, but processing complexity and resource consumption increase

Engineering Contradiction:

Improvetraffic prioritization capabilityVSAvoidprocessing complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The application layer performs preliminary classification of data packets by application type before packetization. This early classification allows network devices to simply read the application type field in the packet header without performing complex inspection, thus improving traffic prioritization capability while reducing processing complexity at network devices

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

An application type identification mechanism acts as an intermediary between the application layer and network layer. This intermediary adds application type information to packet headers during packetization, enabling network devices to easily identify and prioritize traffic without needing to perform resource-intensive deep packet inspection

Inventive Principle:

Principle #24Intermediary (Mediator)

2Device complexity

If traditional packet headers are used without application identification, then packet structure simplicity is maintained, but network management and analytics capability deteriorate

Engineering Contradiction:

Improvepacket structure simplicityVSAvoidapplication identification information

Core Design Contradiction:

Device complexityVSLoss of information

Solution Approach 1:

The packet structure is segmented into traditional header fields and an additional application type field. This segmentation allows the packet to maintain compatibility with existing network protocols while adding specific application identification information, thus preserving packet structure simplicity while preventing information loss

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Application type information is added locally in the packet header at the source device where applications are known. This local quality enhancement allows network devices throughout the network to access application identification information without changing the overall packet structure or requiring complex processing at each network node

Inventive Principle:

Principle #3Local quality

Data Source

PatentUS12284119B2Application-based data labeling

Publication Date: 2025.04.22 CISCO TECHNOLOGY INC

AI summary

This disclosure describes techniques for performing application-based tagging. An example method includes receiving, at a virtual socket, non-packetized data from an application and generating, by the virtual socket, a label based on the application. One or more data packets are generated by packetizing at least a portion of the non-packetized data. A header field of the one or more data packets includes a tag based on the label.