Dynamic Data Flow Enforcement via Destination Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Networks face challenges in managing and enforcing data flow rules due to unpredictable destination device identifiers, leading to inaccuracies in billing, traffic management, and Quality of Service (QoS) adherence, especially when end devices switch between permitted and unpermitted servers during data sessions.
Innovation Solution
A data flow management service is implemented, where end devices transmit destination device identifiers to network devices for validation, allowing the network to apply appropriate rules and traffic shaping parameters based on the validation outcome, ensuring compliance with data service subscriptions and usage policies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the network applies fixed data flow rules based on pre-configured destination device identifiers, then rule enforcement is simplified, but accuracy in billing and QoS management deteriorates when end devices switch between permitted and unpermitted servers
Solution Approach 1:
The patent implements dynamic data flow enforcement where the network device receives updated destination device identifiers from the end device during the PDU session and adjusts rule application accordingly. This transforms the static, pre-configured rule enforcement into a dynamic system that adapts to real-time destination changes, resolving the contradiction between operational simplicity and billing accuracy.
Solution Approach 2:
The system establishes a feedback loop where the end device provides destination device identifier information back to the network device, which then validates and applies appropriate rules. This feedback mechanism ensures that the network maintains accurate knowledge of current data flow destinations, enabling precise billing and QoS management while preserving ease of operation through automated rule selection.
2Measurement precision
If the network validates all destination device identifiers in real-time during data sessions, then billing accuracy improves, but network latency and processing overhead increase
Solution Approach 1:
The patent performs validation of destination device identifiers proactively during PDU session establishment and when destinations change, rather than continuously during data transmission. This preliminary validation approach ensures billing accuracy is maintained while minimizing latency by avoiding repeated real-time validation during active data flows.
Solution Approach 2:
The system applies validation selectively rather than uniformly to all data flows. The network device validates destination device identifiers based on specific triggers (session establishment, destination changes) rather than continuously monitoring all traffic, thereby achieving sufficient billing accuracy without excessive processing overhead and latency.
3Manufacturing precision
If the network dynamically adjusts traffic shaping parameters based on validated destination device identifiers, then resource allocation accuracy improves, but system complexity increases
Solution Approach 1:
The patent implements dynamic adjustment of traffic shaping parameters (such as bit rates, priority levels, and QoS thresholds) based on the validated destination device identifier. When a destination is identified and validated, the network device automatically modifies relevant traffic parameters to match the appropriate service level, achieving precise resource allocation without requiring complex manual configuration.
Solution Approach 2:
The system employs a universal rule management framework where a single validation mechanism serves multiple purposes: billing determination, QoS enforcement, and resource allocation. This multi-functional approach reduces overall system complexity by consolidating what could otherwise be separate complex subsystems into one integrated validation and rule application process.
Data Source
AI summary
A method, a device, and a non-transitory storage medium are described in which destination device identifiers associated with network devices are subject to a validation process before an end device attempts to establish a communication session with a network device. Based on an outcome of the validation process, a data flow subsequently established by the end device may be subject to a rule provided under a data usage plan subscribed to by the end device or another rule.