Protocol-Level Filtering via Network Stack Handlers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current content filtering mechanisms are port and application specific, limiting their ability to effectively handle multiple protocols and providing incomplete solutions, as they assume protocols based on the type of application or port used, which may not account for all scenarios.
Innovation Solution
Implementing protocol-level filtering mechanisms that are agnostic to ports and applications, using protocol detection components like handlers to identify and modify data streams within the networking stack, allowing for the filtering of content at the protocol level, regardless of the application or port, through data stream buffers and policy services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If port and application specific filtering mechanisms are used, then the filtering mechanism is simpler to implement, but the protocol detection capability is limited and cannot handle multiple protocols effectively
Solution Approach 1:
The patent segments the filtering mechanism into protocol detection components (handlers) that are attached to data streams at the networking stack level. Each handler is responsible for detecting a specific protocol by examining protocol-specific data within the stream, allowing multiple protocols to be detected independently without requiring complex port or application identification logic.
Solution Approach 2:
The patent introduces protocol handlers as intermediary components between the data stream and the filtering policy. These handlers act as mediators that inspect data streams, identify protocols through pattern matching and state machine analysis, and then apply appropriate filtering actions based on detected protocols, thereby enabling versatile protocol detection without direct complexity in the main filtering mechanism.
2Adaptability or versatility
If protocol-level filtering is implemented, then comprehensive protocol detection and manipulation is achieved, but the complexity of handling multiple protocols increases
Solution Approach 1:
The patent implements a universal handler framework that can detect and filter multiple protocols through a common architecture. The handler interface provides standardized methods for protocol detection and data stream manipulation, allowing different protocol-specific handlers to be integrated uniformly. This universal framework handles the complexity of multiple protocols internally while presenting a simplified interface to the filtering policy.
Solution Approach 2:
The patent employs a nested structure where protocol handlers are attached to data streams within the networking stack. Handlers can be nested in sequences to handle different layers of protocol detection, with outer handlers performing initial protocol identification and inner handlers performing more specific protocol analysis. This nesting allows complex multi-protocol handling to be organized in a manageable hierarchical structure.
3Measurement precision
If assumptions are made about protocols based on application or port type, then the filtering mechanism is easier to operate, but the measurement precision of protocol identification deteriorates
Solution Approach 1:
The patent replaces the mechanical system of port and application-based protocol assumptions with an automated protocol detection system. Instead of manually configuring which port or application corresponds to which protocol, the system uses protocol handlers that automatically inspect data streams and identify protocols through pattern matching and state machine analysis, thereby achieving high identification accuracy without requiring complex manual configuration or operation.
Data Source
AI summary
Mechanisms are disclosed for detecting protocols independently of the ports used by streams associated with the protocols or applications that may send out such streams. The detecting may entail using a content filter that is hosted on a networking stack, where the content filter may be composed of a stream buffer and handlers for detecting the protocols. The handlers may be further used to modify streams incoming to a port or streams outgoing from an application. The handlers can modify the streams in a variety of ways, including reading, inserting, replacing, deleting, and completing data in the streams according to some policy criteria, such as those set by parental controls. Individual handlers may be selected from a plurality or set of handlers so that they can be matched up to the appropriate streams.