Edge Application Compliance Aggregation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In edge computing networks, ensuring compliance across distributed application components across different layers is complex due to varying security policies and regulatory requirements, which existing technologies struggle to manage effectively.

Innovation Solution

A computer-implemented method and system that uses a compliance manager to perform compliance checks at each layer of the edge computing network, aggregating scores and determining an overall compliance score using a compliance profile, which identifies specific checks for each component and transmits results upward to a top layer for analysis.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If compliance checks are performed at each layer of the edge computing network, then compliance determination accuracy is improved, but system complexity increases

Engineering Contradiction:
Improvecompliance determination accuracyVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The compliance management system is segmented into multiple layers (edge device layer, edge server layer, cloud server layer), with each layer performing compliance checks on components appropriate to its level. This segmentation allows comprehensive compliance determination while distributing system complexity across manageable layers rather than concentrating all compliance functions in a single complex system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A compliance profile acts as an intermediary that identifies and manages the set of compliance checks for each component. The compliance profile translates complex regulatory requirements into specific, actionable checks that can be performed at different layers, thereby improving compliance determination accuracy while reducing the apparent complexity for individual components.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If compliance scores are transmitted from each layer upward, then overall compliance visibility is improved, but data transmission volume increases

Engineering Contradiction:
Improvecompliance visibilityVSAvoiddata transmission volume
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The system extracts only the essential compliance score information from each layer and transmits it upward to the next layer. Rather than transmitting all raw compliance data, the system extracts aggregated compliance scores that capture the essential compliance status while minimizing data transmission volume.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Compliance scores from multiple components within a layer are aggregated and combined into a single compliance score for that layer before transmission upward. This merging process maintains overall compliance visibility at the cloud server layer while significantly reducing the volume of data that needs to be transmitted across the network.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If compliance checks are performed on all distributed components, then compliance coverage is improved, but processing time increases

Engineering Contradiction:
Improvecompliance coverageVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Compliance checks are segmented and distributed across multiple layers, with each layer performing checks on components appropriate to its level. This segmentation enables comprehensive compliance coverage of all distributed components while parallelizing the processing across layers, thereby reducing overall processing time compared to sequential centralized checking.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Compliance checks are performed at the edge device layer and edge server layer before data reaches the cloud server layer. This preliminary action ensures that compliance issues are detected and addressed at the source, providing comprehensive compliance coverage while reducing the time required for final compliance determination at the cloud level.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20240320687A1Distributed Edge Application Compliance
Publication Date: 2024.09.26 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US20240320687A1 patent drawing
  • US20240320687A1 patent drawing
  • US20240320687A1 patent drawing

AI summary

A computer implemented method determines a compliance of an application. A number of processor units determines compliance scores resulting from compliance checks performed at each layer in layers in an edge computing network for components for the application running in the layers. The compliance checks performed at each layer are determined using a compliance profile identifying a set of the compliance checks for each component in the application. The number of processor units transmit the compliance scores determined in each layer in the layers upward to a top layer in the layers. The number of processor units aggregate compliance scores received from the components in a lower layer for transmission upward in the layers to the top layer as aggregated compliance scores. The number of processor units determine the compliance for the application using an overall aggregate score determined at the top layer.