Hybrid Intranet-Cloud Processing for Low-Latency Plant Data Exchange

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing information processing systems face challenges in efficiently integrating intranet and cloud-based models for data processing and communication, particularly in the context of a corporation's multiple plants, where seamless data exchange and control across different network environments is hindered.

Innovation Solution

An information processing system is implemented with a hybrid architecture that includes intranet and cloud-based systems, utilizing fog computing and cloud platforms to facilitate communication and processing between plant systems, cloud servers, and on-premises systems, enabling data exchange and control through a combination of machine learning and statistical analysis engines.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Power

If all data processing is performed on cloud servers, then computational power is sufficient, but network latency and communication overhead increase

Engineering Contradiction:
Improvecomputational powerVSAvoidnetwork latency
Core Design Contradiction:
PowerVSLoss of time

Solution Approach 1:

The system segments processing tasks between edge devices (local processing) and cloud servers (remote processing). Edge devices handle time-sensitive local operations while cloud servers handle computationally intensive tasks, resolving the contradiction between computational power and network latency by distributing workloads according to their respective strengths

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer (edge computing infrastructure) between end devices and cloud servers. This intermediary performs preliminary processing and filtering of data, reducing the amount of data that needs to be transmitted to the cloud while maintaining adequate computational capabilities locally

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If data is processed locally on intranet systems, then real-time responsiveness is improved, but processing capability is insufficient for complex tasks

Engineering Contradiction:
Improvereal-time responsivenessVSAvoidprocessing capability
Core Design Contradiction:
SpeedVSPower

Solution Approach 1:

The system divides processing responsibilities between local intranet systems (for real-time responses) and cloud servers (for complex computations). Local systems handle time-critical operations immediately while non-critical but computationally intensive tasks are offloaded to the cloud, achieving both responsiveness and processing capability

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Local intranet systems perform preliminary processing and filtering of data before transmitting to the cloud. This preliminary action enables immediate local responses to time-sensitive events while preparing optimized data sets for subsequent cloud-based complex analysis

Inventive Principle:
Principle #10Preliminary action

3Power

If cloud servers handle all processing, then processing capability is sufficient, but processing burden and costs increase

Engineering Contradiction:
Improveprocessing capabilityVSAvoidprocessing burden
Core Design Contradiction:
PowerVSLoss of energy

Solution Approach 1:

The system implements partial processing at the edge and partial processing in the cloud, rather than concentrating all processing in one location. This distributes the processing burden, reducing the load on cloud servers while maintaining adequate processing capability through the combined effort of edge and cloud resources

Inventive Principle:
Principle #16Partial or excessive action

4Reliability

If multiple separate systems are used for intranet and cloud, then system independence is maintained, but integration and seamless communication are hindered

Engineering Contradiction:
Improvesystem independenceVSAvoidintegration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges intranet and cloud systems into a unified hybrid architecture where both systems operate independently but are integrated through standardized communication protocols and data exchange mechanisms. This allows maintaining system independence while achieving seamless communication through the unified framework

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS12530019B2Information processing system
Publication Date: 2026.01.20 KYOCERA CORP
  • US12530019B2 patent drawing
  • US12530019B2 patent drawing
  • US12530019B2 patent drawing

AI summary

An information processing system includes a first system in an intranet of an organization, a second system of the organization being outside the intranet, and a server connected to the second system over an Internet outside the intranet. The second system communicates with the first system through the server located outside the intranet.