Client Router IPv6 Extended Headers for Multi-Flow Billing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network billing systems face challenges in accurately and efficiently billing multiple packet flows from different client devices to various accounts, particularly in segmented models, due to limitations in deep packet inspection and high implementation costs.
Innovation Solution
The implementation of a system and method that uses a client router to communicate billing information and groom traffic flows by assigning identifiers and applying billing categories, utilizing extended headers with vendor-specific attributes to manage and prioritize data flows, allowing for precise billing and traffic management across multiple devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If deep packet inspection is used to identify and bill multiple packet flows, then billing accuracy is improved, but implementation cost and scaling cost increase significantly
Solution Approach 1:
The patent segments the billing function by introducing flow identifiers that divide packet flows into distinct billable units. Each flow is tagged with a unique identifier at the network edge, allowing the billing system to process segmented flow information rather than performing complex deep packet inspection on entire data streams. This segmentation enables accurate flow identification while reducing the computational complexity and cost of the billing infrastructure.
Solution Approach 2:
The patent applies preliminary action by tagging packet flows with identifiers at the network edge before they reach the billing system. This pre-processing step embeds billing-relevant information directly into the packet flow metadata, so that when packets arrive at the billing system, the identification and classification work has already been done. This eliminates the need for expensive deep packet inspection at the billing point, as the necessary information is already prepared in advance.
2Adaptability or versatility
If multiple packet flows from the same client router are billed to different accounts, then billing versatility is improved, but system complexity increases
Solution Approach 1:
The patent implements universality by creating a multi-functional identifier system that serves multiple purposes: flow identification, account routing, and billing classification. The same flow identifier structure is used across different billing scenarios (single account, multiple accounts, segmented billing), making the system adaptable to various billing models without requiring separate complex mechanisms for each scenario. This universal identifier approach enables billing versatility while maintaining system simplicity.
3Productivity
If extended headers with vendor-specific attributes are used to convey billing information, then information transmission efficiency is improved, but protocol complexity increases
Solution Approach 1:
The patent uses extended headers as an intermediary mechanism to carry billing information between network elements. Rather than requiring direct complex communication protocols between billing systems and network elements, the extended headers serve as a standardized intermediary format that can convey flow identification and billing information efficiently. This intermediary approach simplifies the overall system by providing a common language for information exchange, reducing the need for complex point-to-point protocol implementations.
Data Source
AI summary
A method includes receiving at a network device, an identifier from a vehicle routing device. The vehicle routing device is configured to identify packet data flows based on an application running on a vehicle client device. The packet data flows are flowing over a communication link between the vehicle routing device and the vehicle client device. The method includes identifying each packet of each flow according to the application that sends or receives packets related to each of the packet data flows, determining an extended header for the one or more packet data flows based on an Internet protocol version 6 (IPv6) extension header and a RADIUS vendor specific attributes (VSA) structure, and transmitting, by the vehicle routing device, to the network device, the extended header and the one or more packet data flows.