Network Abnormality Cause Specification via Session-Based Log Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for specifying the abnormality cause route in networks require extensive labor and time due to the need to search through large volumes of communication logs, increasing costs and reducing efficiency.
Innovation Solution
A system that includes a storage device for holding communication relation information, separating communication history by session presence or absence, and an arithmetic device to prioritize routes based on predefined conditions, efficiently identifying abnormality cause routes in networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If communication logs of all relay terminals are searched to specify the abnormal cause route, then the abnormality cause route can be specified, but the work requires a considerable amount of labor and time
Solution Approach 1:
The patent segments the communication logs by separating them according to session presence or absence. This segmentation allows the system to focus analysis on specific log categories rather than processing all logs uniformly, thereby reducing the time required for abnormality cause route specification while maintaining accuracy.
Solution Approach 2:
The patent changes the analysis parameter by introducing session presence/absence as a classification criterion. By evaluating communication logs based on this parameter and applying policies that prioritize certain session types, the system efficiently identifies abnormal cause routes without examining every log entry in detail.
2Measurement precision
If communication logs of all relay terminals are searched to specify the abnormal cause route, then the abnormality cause route can be specified, but labor and cost increase
Solution Approach 1:
The patent segments the communication logs by separating them according to session presence or absence. This segmentation allows the system to focus analysis on specific log categories rather than processing all logs uniformly, thereby reducing the time required for abnormality cause route specification while maintaining accuracy.
Solution Approach 2:
The patent changes the analysis parameter by introducing session presence/absence as a classification criterion. By evaluating communication logs based on this parameter and applying policies that prioritize certain session types, the system efficiently identifies abnormal cause routes without examining every log entry in detail.
3Measurement precision
If all communication logs are processed to ensure accurate abnormality cause route specification, then measurement precision is maintained, but device complexity increases
Solution Approach 1:
The patent segments the communication logs by separating them according to session presence or absence. This segmentation allows the system to focus analysis on specific log categories rather than processing all logs uniformly, thereby reducing the time required for abnormality cause route specification while maintaining accuracy.
Solution Approach 2:
The patent changes the analysis parameter by introducing session presence/absence as a classification criterion. By evaluating communication logs based on this parameter and applying policies that prioritize certain session types, the system efficiently identifies abnormal cause routes without examining every log entry in detail.
Data Source
AI summary
[Problem] An abnormality cause route in a network can be efficiently specified, and labor and a cost required for work can be reduced.[Solution] An abnormality cause specification support system 101 includes: a storage device 203 that holds communication relation information 401 in which a communication history between terminals 20 belonging to a predetermined network 10 is stored separately according to presence and absence of a session in the communication, and a policy 601 for specifying an abnormality cause route occurring in the network 10; and an arithmetic device 201 that specifies, among the communication history indicated by the communication relation information 401, a communication history indicating a condition defined in the policy 601 and a predetermined degree of conformity, and specifies a route between the terminals indicated by the specified communication history as an abnormal cause route to be considered with priority in the network 10.


