Intermediary System for Client-Side Service Anomaly Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The integration of client-side services into web applications poses challenges in monitoring and controlling operations, particularly when anomalies occur, leading to issues with service level agreements, compliance, and performance degradation due to the lack of control over third-party service code executing outside the server's control.

Innovation Solution

An intermediary system is introduced between client devices and servers to collect metadata, detect anomalies, and control service operations by delaying, removing, or modifying operations associated with detected issues, ensuring consistent performance and compliance across multiple client devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If client-side services are integrated into web applications, then functionality and user experience are improved, but control and monitoring capability deteriorate

Engineering Contradiction:
ImprovefunctionalityVSAvoidcontrol capability
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces a server as an intermediary between the web application and third-party client-side services. This server establishes proxies for service instances, intercepts communications, and enables monitoring and control of service operations without requiring changes to the third-party service code. The intermediary resolves the contradiction by maintaining service functionality while providing the necessary control and monitoring capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If third-party service code executes outside server control, then service independence and flexibility are improved, but reliability and compliance deteriorate

Engineering Contradiction:
Improveservice independenceVSAvoidcompliance
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where the intermediary server monitors service instance operations, detects anomalies, and responds by modifying or terminating service execution. The system collects metadata about service operations, compares it against expected behavior, and provides feedback control to ensure compliance with service level agreements and organizational policies, thereby maintaining reliability while preserving service independence.

Inventive Principle:
Principle #23Feedback

3Ease of manufacture

If service instances operate autonomously on client devices, then deployment flexibility is improved, but anomaly detection and control capability deteriorate

Engineering Contradiction:
Improvedeployment flexibilityVSAvoidanomaly detection
Core Design Contradiction:
Ease of manufactureVSDifficulty of detecting and measuring

Solution Approach 1:

The patent shifts the monitoring and control dimension from the client device level to the server level. Instead of attempting to monitor services directly on diverse client devices, the intermediary server creates proxies and intercepts communications at the network layer, enabling anomaly detection and control from a centralized dimension. This approach maintains deployment flexibility while providing comprehensive monitoring capabilities.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentEP3785119B1System and method for governing client-side services
Publication Date: 2023.08.16 YOTTAA INC
  • EP3785119B1 patent drawingFigure 1A
  • EP3785119B1 patent drawingFigure 1B
  • EP3785119B1 patent drawingFigure 1C

AI summary

Described embodiments include methods and systems for managing client-side services. An intermediary may receive metadata from a first client device of the plurality of client devices. The metadata can include runtime characteristics of a first instance of a service that is incorporated into a client-side application or a web application. The first instance may execute on the first client device and request service data from the at least one server. The intermediary can detect an anomaly in the operation of the first instance of the service. The intermediary can identify an operation of the first instance of the service causing the detected anomaly. The intermediary can, responsive to the detected anomaly, cause delay, removal or modification of operations corresponding to the identified operation, in other instances of the service executing on the plurality of client devices.