Traffic Identification via Interface Binding Entries
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data identification capabilities in UEs for managing network resources are limited, particularly in identifying traffic types during web-browsing processes, which are often considered cumbersome and impractical due to the assumption of single continuous communication sessions.
Innovation Solution
Implementing a method that identifies traffic content types by monitoring HTTP sessions, parsing links within HTML content, and creating interface-binding entries to associate links with their respective content types, allowing for efficient interface selection and policy-based data routing during multiple sessions within a web-browsing process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If traffic identification is based on single continuous communication session assumption, then implementation is simpler, but traffic type identification accuracy deteriorates for web-browsing processes
Solution Approach 1:
The patent segments the web-browsing process into multiple independent communication sessions (HTTP session for HTML, separate sessions for images, videos, etc.) rather than treating it as a single continuous session. Each session is identified and routed independently based on its traffic content type, enabling accurate traffic identification while maintaining implementation feasibility through modular session handling.
2Measurement precision
If multiple communication sessions are monitored and managed separately, then traffic type identification accuracy improves, but device complexity increases
Solution Approach 1:
The patent introduces an intermediary component (traffic identification function/module) that sits between the network stack and application layer. This intermediary monitors HTTP sessions, identifies traffic content types by analyzing HTML content and links, and creates interface-binding entries. By centralizing this functionality in a dedicated intermediary module, the system achieves accurate multi-session traffic identification without distributing complexity across the entire system.
Solution Approach 2:
The patent performs preliminary actions by pre-identifying traffic content types during the HTTP session and creating interface-binding entries before actual data transmission occurs. The system monitors incoming HTML content, identifies links and their associated content types, and establishes binding entries in advance. This preliminary identification and binding setup simplifies subsequent session management and routing decisions.
3Speed
If interface selection is based on predefined rules only, then routing speed is faster, but adaptability to different traffic patterns deteriorates
Solution Approach 1:
The patent creates interface-binding entries in advance during HTTP sessions, pre-determining the appropriate interface for specific traffic content types and links. This preliminary binding establishment enables fast routing lookup without requiring complex real-time analysis, achieving both high routing speed and adaptability to different traffic patterns through pre-computed binding rules.
Solution Approach 2:
The patent changes the routing parameter from simple predefined rules to dynamic interface-binding entries that are created based on actual traffic content type identification. The system transforms static routing tables into dynamic bindings that adapt to different traffic patterns by creating specific interface associations based on monitored HTML content, links, and traffic types, thereby achieving both speed and adaptability.
Data Source
AI summary
Embodiments for enabling traffic content identification by a wireless transmit/receive unit are provided. The WTRU may store interface binding entries in a database associating links in a web page to various traffic content types, such as video, audio, and text. Upon a request to access one of the links, a socket may be created based on a data mobility policy associated with the traffic content type. Alternately, the database may associate the links directly to interface types based on the data mobility policies. The Access Network Discovery and Selection Function (ANDSF) may provide the data mobility policies to the WTRU.