Cloud Resource Discovery Using In-Use Datacenter Filtering

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Cloud-based discovery of computing resources across multiple datacenters is inefficient and time-consuming due to the large number of API calls required, which can overwhelm the service provider's capacity and result in outdated information by the time discovery is complete.

Innovation Solution

Implementing initial API calls to identify in-use datacenters and performing pattern-based discovery within these datacenters, reducing the number of API calls needed to complete the process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If cloud-based discovery queries all datacenters to ensure complete resource information, then measurement precision is improved, but loss of time worsens

Engineering Contradiction:

Improvecompleteness of resource informationVSAvoiddiscovery duration

Core Design Contradiction:

Measurement precisionVSLoss of time

Solution Approach 1:

The patent applies preliminary action by first querying a subset of datacenters to obtain initial resource information before performing the main discovery process. This preliminary query identifies which datacenters contain resources, allowing the system to focus subsequent detailed discovery only on those relevant datacenters rather than querying all datacenters, thus reducing total discovery time while maintaining information completeness.

Inventive Principle:

Principle #10Preliminary action

2Measurement precision

If the number of API calls is increased to discover all computing resources, then measurement precision is improved, but object-generated harmful factors worsen

Engineering Contradiction:

Improvecompleteness of resource informationVSAvoidservice provider capacity overload

Core Design Contradiction:

Measurement precisionVSObject-generated harmful factors

Solution Approach 1:

The patent extracts and removes unnecessary API calls by first identifying which datacenters actually contain resources through an initial subset query. This extraction eliminates the need to make API calls to datacenters that have no resources, reducing the total number of calls made to the service provider while still discovering all actual resources, thereby preventing capacity overload.

Inventive Principle:

Principle #2Taking out (Extraction)

3Loss of time

If discovery is limited to a subset of datacenters to reduce API calls, then loss of time is improved, but measurement precision worsens

Engineering Contradiction:

Improvediscovery durationVSAvoidcompleteness of resource information

Core Design Contradiction:

Loss of timeVSMeasurement precision

Solution Approach 1:

The patent uses preliminary action to first perform a quick subset query to identify which datacenters contain resources. This preliminary step enables the system to then focus the main discovery process only on those identified datacenters, ensuring complete resource information is obtained while minimizing the scope and time of the detailed discovery phase.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS20260104936A1Efficient Cloud-Based Discovery of Computing Resources

Publication Date: 2026.04.16 SERVICENOW INC

AI summary

An example embodiment may involve requesting and receiving, from a distributed computing platform, resource indicators that specify a set of resources provided by the distributed computing platform, wherein the set of resources is associated with a user identifier; parsing the resource indicators to locate datacenter indicators in the set of resources, wherein the datacenter indicators identify in-use datacenters of the distributed computing platform; and performing pattern-based discovery, within the in-use datacenters, of computing resources of the distributed computing platform that are associated with the user identifier.