Cloud Service Error Grouping for Bulk Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud computing platforms face challenges in efficiently mapping and managing network services, particularly in multi-tenant architectures, where failures can lead to outages affecting multiple customers, and require complex custom scripts for automated processes, complicating error resolution and service management.

Innovation Solution

The implementation of a multi-instance cloud architecture with dedicated server instances and load balancers for each customer, along with a service mapping system that identifies service entry points, collects network information, groups errors, and provides a user interface for bulk error resolution, enabling parallel processing and efficient service mapping and error handling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a shared cloud computing infrastructure is used to provide flexible access to computing resources, then resource utilization and accessibility are improved, but service reliability and fault isolation deteriorate because failures can affect multiple customers

Engineering Contradiction:
Improveaccessibility to computing resourcesVSAvoidservice availability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the cloud computing infrastructure into multiple isolated server instances, each dedicated to a specific customer or tenant. This segmentation isolates failures to individual instances while maintaining shared resource benefits, resolving the contradiction between resource sharing and failure isolation.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If custom scripts are implemented to perform automated processes in PaaS, then functional flexibility and customization are improved, but system complexity and error resolution difficulty increase

Engineering Contradiction:
Improvefunctional customizationVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary service layer that provides standardized automation capabilities between the user and underlying infrastructure. This intermediary abstracts complex scripting requirements while maintaining functional flexibility, reducing system complexity without sacrificing customization.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Difficulty of detecting and measuring

If comprehensive service mapping is performed across multiple services to identify failures, then error detection capability is improved, but processing time and computational resources increase

Engineering Contradiction:
Improveerror detection capabilityVSAvoidprocessing time
Core Design Contradiction:
Difficulty of detecting and measuringVSLoss of time

Solution Approach 1:

The patent performs preliminary service mapping and establishes baseline relationships between services before failures occur. This pre-established mapping enables rapid error detection and propagation tracking when failures happen, improving detection capability without incurring full mapping costs during incident response.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If multiple server instances are maintained for different customers to improve isolation and reliability, then service reliability is improved, but infrastructure complexity and management overhead increase

Engineering Contradiction:
Improveservice isolationVSAvoidinfrastructure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements universal server instances that can be dynamically assigned to different customers and services. These multi-functional instances provide the same isolation and reliability benefits as dedicated instances but reduce overall infrastructure complexity through resource consolidation and standardized management procedures.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentEP3468144B1Displaying errors of cloud service components
Publication Date: 2022.03.30 SERVICENOW INC
  • EP3468144B1 patent drawingFigure 1
  • EP3468144B1 patent drawingFigure 2
  • EP3468144B1 patent drawingFigure 3

AI summary

Techniques related to bulk mapping network services are disclosed. The techniques include a system, comprising non-transitory memory devices, and hardware processors configured to execute instructions from the non-transitory memory devices to cause the system to determine a set of service entry point candidates for an organization based, at least in part, on network information received from load balancing servers, receive user input including a selection of a set of service entry points selected from the set of service entry point candidates, collect network information related to two or more service entry points of the set of service entry point candidates in parallel, the network information including returned errors associated with a respective service entry point, group the returned errors into category groups based on characteristics of the returned errors, and display the category groups on a display device for bulk resolution.