Route Event Record Entry Processing for Policy-Change Correlation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity of network operation and maintenance is increased by the diversity of communication technologies, protocol types, and network device vendors, making it difficult to manage route changes and associated policies effectively.
Innovation Solution
A route event record entry processing method that associates route changes with the policies causing them, allowing for flexible recording and management by generating entries that include information about route prefixes, policies, and attribute changes, enabling efficient route management through network devices and control devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If route policies are recorded separately from route attributes, then the recording system is simpler, but route management efficiency deteriorates due to inability to associate policies with route changes
Solution Approach 1:
The patent merges route attribute information and route policy information into a single unified record entry. Each record contains both the route prefix/attributes and the associated policy details (policy name, policy type, match conditions, actions), eliminating the need for separate recording systems and enabling direct association between route changes and their causing policies.
Solution Approach 2:
The patent introduces an intermediary mapping relationship between route attributes and policy information. The route attribute acts as a key that links to detailed policy records, allowing efficient retrieval and association without directly embedding all policy data in every route record, thus balancing complexity and manageability.
2Productivity
If all route policy details are recorded in every route entry, then route management efficiency improves through complete information availability, but device complexity increases due to larger data storage requirements
Solution Approach 1:
The patent segments route policy information into modular components including policy identifier, policy type, match conditions, and actions. Each route record contains only the essential policy identifier and type, while detailed policy specifications are stored separately and referenced as needed, reducing redundancy and storage complexity.
Solution Approach 2:
The patent adds a new dimension to the recording structure by introducing policy-specific fields (policy_name, policy_type, match_condition, action) as separate dimensions alongside traditional route attributes. This dimensional expansion allows comprehensive policy tracking without requiring all policy details to be embedded in every route entry.
3Device complexity
If route changes are tracked without policy association, then the tracking system is simpler, but the ability to analyze and manage route changes deteriorates
Solution Approach 1:
The patent performs preliminary action by pre-associating policy information with route attributes at the time of policy application. When a route policy is applied or modified, the system proactively records the policy details alongside the route attributes, ensuring policy context is captured before route changes occur, eliminating the need for complex post-hoc analysis.
Solution Approach 2:
The patent implements feedback mechanisms where route policy records provide continuous information about policy application status and effects. The system monitors and records whether policies are matched, their execution results, and any route changes they cause, creating a feedback loop that maintains accurate policy-context information without requiring complex tracking systems.
Data Source
AI summary
This application provides a route event record entry processing method, a network device, and a control device. The method includes: obtaining, by a network device, first information and second information that correspond to a route prefix, where the first information is used to indicate information about a first route policy for the route prefix, and the second information is used to indicate attribute information obtained after processing the route prefix by using the first route policy; and generating, by the network device, a route event record entry for the route prefix based on the first information and the second information, where the route event record entry includes the route prefix, the first information, and the second information.