Network Node Priority Credit Database for Packet Reliability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In packet networks, the widespread marking of data packets as priority results in service providers ignoring these markings, leading to unreliable priority services, as 'best efforts' guarantees do not ensure that critical applications receive the necessary bandwidth.
Innovation Solution
Data packets are marked as priority based on their origin or destination network addresses stored in a database, with the priority field in the packet header being set accordingly, and priority credits can be purchased to guarantee quality of service, allowing true prioritization and ensuring that only designated packets receive priority treatment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data packets are marked as priority using diffserv or p-bit fields, then priority indication is provided, but service providers ignore these markings because most packets are marked as priority, making the priority marking ineffective
Solution Approach 1:
The system performs preliminary actions by pre-configuring priority rules, policies, and credit balances in the network database before data packets arrive. Network addresses, applications, and users are pre-identified as priority candidates based on predetermined criteria, so that when packets arrive, the priority determination can be made quickly and accurately without ad-hoc marking of all packets
Solution Approach 2:
The system implements feedback mechanisms by continuously monitoring packet flow, credit balances, and network conditions. The database is updated with packet transmission results and credit consumption, allowing the system to adjust priority markings dynamically. This feedback loop ensures that priority markings remain meaningful and actionable by service providers, as the system learns from actual network behavior and adjusts its marking strategy accordingly
2Reliability
If service providers offer best efforts guarantee, then service provision is simplified, but customers cannot receive guaranteed bandwidth for critical applications during high traffic
Solution Approach 1:
The patent introduces a database as an intermediary layer between customers and service providers. This database stores priority rules, policies, credit balances, and network address information, serving as a centralized mediator that automates priority determination. The database intermediary handles the complexity of priority management, allowing service providers to maintain simplified best-efforts infrastructure while still delivering guaranteed bandwidth for priority traffic through automated database-driven decision-making
Solution Approach 2:
The system dynamically changes parameters such as priority markings, credit balances, and policy rules based on network conditions, customer payments, and traffic patterns. By adjusting these parameters in real-time through database updates, the system can guarantee bandwidth for critical applications during high traffic without requiring complex manual service management, as the automated parameter changes enforce priority guarantees
3Reliability
If priority credits are introduced to guarantee quality of service, then service guarantees can be provided, but the system complexity increases with credit management and tracking
Solution Approach 1:
The patent merges multiple functions into the centralized database: priority rule storage, policy management, credit balance tracking, and packet priority determination all occur within the same database infrastructure. This consolidation reduces overall system complexity by eliminating the need for separate credit management systems, as the database serves as a unified platform that handles both quality of service guarantees and financial tracking in an integrated manner
Data Source
AI summary
A system and method for prioritizing data packets being communicated over a packet network may include receiving a data packet at a network node. The data packet may include an origination network address, a destination network address, and a data field. A determination may be made as to whether at least one of the origination and destination network addresses is a priority network address. The data field of the data packet may be set to a priority value if at least one of the origination and destination network addresses is determined to be a priority network address. The data field of the data packet may be set to a non-priority value if both the origination and destination network addresses are determined not to be a priority network address.