Mobile Service Status Monitoring via API Translation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In server and networked environments, especially in enterprise computing, scheduled maintenance checks are inadequate for detecting errors promptly, leading to significant financial losses due to unexpected downtime and accumulating errors in software and hardware.

Innovation Solution

A method and system that uses a mobile device to monitor and aggregate data from servers, providing visual indicators of service status through a mobile gateway and API, allowing for proactive identification and correction of issues, enabling continuous monitoring without the need for powerful computers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If scheduled maintenance checks are used to monitor servers, then device complexity is reduced, but reliability deteriorates due to delayed error detection

Engineering Contradiction:
Improveservice availabilityVSAvoiddetection time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary monitoring actions by continuously collecting service status data before errors manifest. The monitoring application proactively gathers information about service health, enabling early detection of potential issues before they cause downtime or require scheduled maintenance intervention.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where service status information is continuously collected, processed, and returned to users through the user interface. This real-time feedback loop allows users to monitor service health continuously and respond to issues as they develop, rather than waiting for scheduled maintenance windows.

Inventive Principle:
Principle #23Feedback

2Measurement precision

If powerful bulky machines are used to access and debug servers, then measurement precision improves for error detection, but device complexity and portability worsen

Engineering Contradiction:
Improveerror detection capabilityVSAvoidaccessibility
Core Design Contradiction:
Measurement precisionVSEase of operation

Solution Approach 1:

The system creates a simplified copy or representation of server status information that can be accessed on mobile devices. Instead of requiring direct access to powerful debugging machines, the monitoring application captures and transmits essential service status data to lightweight client devices, enabling remote monitoring without needing the full computational power of the original debugging systems.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system transitions monitoring capabilities from a single dimension (powerful stationary machines) to multiple dimensions by enabling access across different device types and locations. The service status information becomes accessible on various portable devices through the user interface, allowing users to monitor servers from any location rather than being constrained to specific powerful machines.

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

3Manufacturing precision

If servers remain offline for debugging, then manufacturing precision improves for error correction, but productivity deteriorates due to downtime

Engineering Contradiction:
Improveerror correction accuracyVSAvoidservice uptime
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The monitoring application performs preliminary error detection and notification before services go offline. By continuously monitoring service status and alerting users to potential issues, the system enables proactive error correction while services remain operational, eliminating the need to take systems offline for debugging.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service monitoring where users can independently check service status and receive notifications about issues without requiring system downtime. The monitoring application autonomously collects service status data and presents it through the user interface, allowing users to manage and debug services without interrupting their operation.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10445335B2Computing environment connectivity system
Publication Date: 2019.10.15 AETNA INC
  • US10445335B2 patent drawing
  • US10445335B2 patent drawing
  • US10445335B2 patent drawing

AI summary

Embodiments of the disclosure provide a system and a method of monitoring connectivity between a plurality of services in a computing environment. The server automatically periodically monitors and aggregates monitored data related to the at least one service through a monitoring application on the server. The monitoring involves collecting and logging status information of the services. The server then connects to the client device, via a mobile gateway, through an application interface (API) on the server. The API includes instructions for sending, receiving, and translating information between the server and the client device. The server then receives, from the client device, a status request. The server sends, from the monitoring application to the API, the monitored data related to the at least one service. Then the server translates, using the API, the monitored data related to the service to obtain the status of the service in the computing environment. Translating involves applying thresholding to the monitored data, utilizing current and historical monitored service status, to categorize the service status. The server sends the status category for the at least one service from the server to the client device via the API.