Static Resource Identifiers for Scalable Footprint Data Centers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud service providers face challenges in scaling cloud services efficiently due to fixed and dedicated computing resources in service enclaves, leading to difficulties in resource allocation and expansion, especially in conventional data centers.

Innovation Solution

Implementing a scalable footprint data center architecture that integrates core CSP services into an overlay network, utilizing hyperconverged server racks with SmartNICs and TPMs, allowing for flexible resource allocation and expansion while maintaining network isolation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If dedicated hardware is used for service enclave, then core services can be reliably provided, but the service enclave cannot be scaled flexibly and resources cannot be made available to customers

Engineering Contradiction:
Improvecore service availabilityVSAvoidservice enclave scalability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent merges the service enclave functionality into the overlay network infrastructure, combining core CSP services with customer infrastructure resources. This allows service enclave functions to be provided on-demand using the same hardware resources as customer workloads, enabling flexible scaling while maintaining service reliability through software-defined networking and virtualization.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements universality by making the infrastructure resources serve multiple functions - both customer workloads and core CSP services share the same physical hardware resources. The overlay network infrastructure provides multi-functionality by supporting both customer-specific services and provider core services, eliminating the need for separate dedicated hardware for service enclave.

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

2Productivity

If additional racks and servers are added to expand data center resources, then customer resource availability increases, but the physical footprint and complexity of the data center increases

Engineering Contradiction:
Improvecustomer resource availabilityVSAvoiddata center footprint
Core Design Contradiction:
ProductivityVSArea of stationary object

Solution Approach 1:

The patent applies dynamics by implementing a scalable footprint architecture where the data center can dynamically expand its virtual resources without proportionally increasing physical footprint. The overlay network enables dynamic allocation of compute, storage, and networking resources from existing infrastructure, allowing resource expansion through software rather than physical addition of racks and servers.

Inventive Principle:
Principle #15Dynamics

3Reliability

If unused resources within service enclave are reserved, then core services maintain availability, but these resources cannot be made available to customers

Engineering Contradiction:
Improvecore service availabilityVSAvoidresource allocation flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent applies preliminary action by pre-provisioning infrastructure resources in the overlay network that can be dynamically allocated to either customer workloads or core CSP services as needed. This allows the system to prepare resources in advance and then flexibly assign them based on demand, ensuring both service availability and resource utilization efficiency.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250385887A1Static resource identifiers in pre-fabricated scalable footprint data centers
Publication Date: 2025.12.18 ORACLE INT CORP
  • US20250385887A1 patent drawing
  • US20250385887A1 patent drawing
  • US20250385887A1 patent drawing

AI summary

Techniques are disclosed for static identifiers for software resources within the scalable footprint data center at various stages during the prefab process. A computing node in a region network and during a region build process can receive a static identifier for a software resource within the region network. The static identifier can include a static string corresponding to a region identifier for the region network. A service executing in the region network and after the region network is configured in a scalable footprint data center can receive a request that includes the static identifier. The service can determine whether the static identifier includes the static string. Based at least in part on a determination that the static identifier includes the static string, the service can obtain the region identifier for the region network from a datastore in the scalable footprint data center.