Edge Cloud Verification System for Sensor Data Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In large-scale authentication and sensor-based systems, the increased load on networks and servers due to extensive data processing and storage requirements leads to high costs and inefficiencies, particularly when edge servers struggle to handle large registration datasets and require cloud server authentication.

Innovation Solution

A verification system is implemented where edge servers process detection data locally and verify it against a subset of registration data stored locally, while the cloud server handles failed verifications and maintains the main database, thereby reducing the load on both the cloud server and the communication between servers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all registration data is stored in the cloud server for verification, then verification accuracy is maintained, but network load and communication amount increase significantly

Engineering Contradiction:
Improveverification accuracyVSAvoidcommunication amount
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent segments the centralized database into multiple distributed databases across edge servers. Each edge server stores a portion of the registration data locally, allowing verification to be performed without constant cloud communication. This segmentation maintains verification accuracy while dramatically reducing network load.

Inventive Principle:
Principle #1Segmentation

2Productivity

If edge servers store large amounts of registration data locally, then verification can be performed independently, but storage capacity requirements increase

Engineering Contradiction:
Improvereal-time processing capabilityVSAvoidstorage capacity
Core Design Contradiction:
ProductivityVSVolume of stationary object

Solution Approach 1:

The patent applies local quality by having each edge server store only the specific portion of registration data relevant to its location or function. Instead of duplicating the entire database, each edge server maintains a customized subset of data, optimizing storage usage while enabling local verification capabilities.

Inventive Principle:
Principle #3Local quality

3Adaptability or versatility

If the system is scaled to handle more sensors and authentication terminals, then system capability increases, but server load and costs increase

Engineering Contradiction:
Improvesystem scaleVSAvoidserver configuration
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the system into hierarchical layers with edge servers handling local verification and a cloud server providing coordination. This segmentation allows the system to scale by simply adding more edge servers without increasing the complexity of individual server configurations.

Inventive Principle:
Principle #1Segmentation

4Reliability

If verification is performed centrally in the cloud server, then data consistency is maintained, but response time increases

Engineering Contradiction:
Improvedata consistencyVSAvoidresponse time
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The patent implements preliminary action by pre-distributing registration data to edge servers before verification is needed. This allows edge servers to perform immediate local verification without waiting for cloud server responses, dramatically reducing response time while maintaining data consistency through periodic synchronization.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3851971B1Verification system and verification server
Publication Date: 2025.05.14 HITACHI KOKUSAI ELECTRIC INC
  • EP3851971B1 patent drawingFigure 1
  • EP3851971B1 patent drawingFigure 2
  • EP3851971B1 patent drawingFigure 3

AI summary

The cloud server 100 holds the main database (102) for storing all the registration data that is handled in the present system, and the edge server 200 that is arranged close to the sensor 300 holds a sub-database (202) for storing part of the registration data. The sub-database (202) in the edge server 200 stores only the registration data having a high probability of being verified in the edge server 200. In the case where the edge server 200 verifies the detection data that has been acquired by the sensor 300 with the registration data within the sub-database and determines that the registration data that matches the detection data does not exist within the sub-database, the configuration allows the detection data to be transmitted to the cloud server 100 and requests the detection data to be verified with the registration data within the main database.