Fault Information Server for In-Vehicle Terminals

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems that notify users of faults in in-vehicle devices connected via wireless networks do not provide information on the impact of these faults on the services they offer, leaving users unaware of the service disruptions.

Innovation Solution

A fault information providing server connected to a processing server group, which includes a fault occurrence/recovery management unit, log management unit, rule management unit, service impact calculation unit, and service impact notification unit, to manage and notify users of the service impact caused by faults, using log information and predefined rules to calculate and communicate the service impact.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If a relay device notifies users of fault occurrence in in-vehicle devices, then users can know the existence of faults, but users cannot know the impact on the provided service

Engineering Contradiction:
Improveservice impact informationVSAvoidsystem complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent introduces a fault information providing server as an intermediary component that receives fault notifications from the relay device, calculates service impact using log information and rules, and provides comprehensive fault information to users. This mediator handles the complex analysis work, keeping the original relay device and service systems simple while ensuring users receive complete information about both fault occurrence and service impact

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system is divided into distinct functional modules: the relay device that detects faults, the fault information providing server that analyzes impact, and the notification system that delivers information to users. This segmentation allows each component to focus on its specific function, reducing overall system complexity while providing comprehensive fault information

Inventive Principle:
Principle #1Segmentation

2Loss of information

If the system provides detailed fault information to users, then users can understand service impact, but the system requires complex log management and rule processing

Engineering Contradiction:
Improveservice status informationVSAvoidinformation processing complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system pre-establishes rule sets that define relationships between fault types and service impacts before faults occur. When a fault happens, the system simply applies these pre-defined rules to calculate impact, avoiding the need for complex real-time analysis. Log information is also pre-collected and organized, enabling rapid impact assessment when faults occur

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The fault information providing server automatically calculates service impact by itself using its own stored log information and rule sets, without requiring external intervention or complex coordination with other systems. This self-service capability simplifies the overall system architecture while providing comprehensive fault information

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10437695B2Fault information providing server and fault information providing method for users of in-vehicle terminals
Publication Date: 2019.10.08 FAURECIA CLARION ELECTRONICS CO LTD
  • US10437695B2 patent drawing
  • US10437695B2 patent drawing
  • US10437695B2 patent drawing

AI summary

A fault information providing server which is connected to a processing server group configured from a plurality of servers, and which provides information related to a fault that occurred in the processing server group to a user of a service provided by the processing server group, comprises: a fault occurrence/recovery management unit which manages fault occurrence of the processing server group; a log management unit which manages log information related to a history of service provided by each server of the processing server group; a rule management unit which manages rules related to a service impact representing an impact on the service caused by the fault; a service impact calculation unit which calculates the service impact based on the log information and the rules; and a service impact notification unit which notifies the service impact calculated by the service impact calculation unit to the user.