Autonomous System Billing via Egress Path Tagging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current billing systems for data transmission out of an Autonomous System (AS) lack efficiency in determining accurate charges based on varying egress paths, communication protocols, encryption types, and intermediate nodes, leading to complexities in network topology changes and customer preferences.
Innovation Solution
Implementing a system that maps egress paths and overlay networks to billing classification tags using Border Gateway Protocol (BGP) community tags, allowing incremental billing counters based on transmitted data, and selecting egress paths based on packet characteristics such as destination, priority, and security, thereby associating each egress path with a specific billing counter.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If traditional traffic classification rules are used to determine billing, then billing can be calculated based on data transmission, but the system cannot accurately account for variations in egress paths, communication protocols, encryption types, and intermediate nodes
Solution Approach 1:
The patent segments the billing determination process by introducing billing classification tags that categorize data transmissions based on specific characteristics (egress path, communication protocol, encryption type, intermediate nodes). Each tag represents a distinct segmentation of the overall billing criteria, allowing precise measurement without requiring a monolithic complex system.
Solution Approach 2:
The patent adds multiple dimensions to the billing system by incorporating BGP community tags that encode various transmission characteristics. Instead of relying on a single classification rule, the system uses multi-dimensional tagging (egress path tags, protocol tags, encryption tags, node tags) that can be combined to achieve precise billing accuracy.
2Adaptability or versatility
If multiple egress paths are available for data transmission, then customer preferences and packet characteristics can be optimized, but determining accurate billing charges becomes more complex
Solution Approach 1:
The patent applies preliminary action by pre-tagging routing information with billing classification tags before data transmission occurs. The BGP community tags are established in advance for each egress path, communication protocol, and intermediate node, so that when data is transmitted, the billing determination simply involves reading the pre-established tags rather than analyzing complex path variations in real-time.
Solution Approach 2:
The patent introduces billing classification tags as intermediaries between the egress path selection mechanism and the billing calculation system. These tags mediate the complex relationship between multiple egress paths and billing charges by providing a simplified interface that captures all necessary characteristics without requiring the billing system to directly process complex path selection logic.
3Adaptability or versatility
If traffic classification rules are used to analyze data flow, then billing charges can be determined, but the system lacks adaptability to network topology changes and customer preferences
Solution Approach 1:
The patent implements dynamics by making the billing classification tags updateable and adaptable to changing network conditions. The BGP community tags can be dynamically modified to reflect network topology changes, new egress paths, or updated customer preferences without requiring a complete reconfiguration of the billing system. This allows the system to adapt efficiently while maintaining fast billing calculation through the continued use of tagged routing information.
Data Source
AI summary
Operations include determining billing for data being transmitted out of an Autonomous System (AS). An internal node in the AS determines billing for a packet transmitted out of the AS based at least on an egress path of the packet. The packet is received at the internal node in the AS The internal node selects an egress path of the packet based on one or more characteristics of the packet. The egress path is mapped directly or indirectly to a billing counter. The billing counter is incremented based on (a) the transmission of the packet on the overlay network to the egress gateway and (b) transmission of the packet out of the AS on the selected egress path.