Address Space Allocation for Distributed Resource Location

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for locating resources in distributed systems often rely on one-to-one mappings between clients and servers, which can lead to inefficiencies and lack of scalability, as they require a central server for resource allocation and do not effectively manage resource availability across multiple servers.

Innovation Solution

A system utilizing an address space with multiple regions, where each region is mapped to a server, allowing clients to transmit requests to a specific address within the region, and determining the selected server using a distributed hash table (DHT) or similar algorithm to direct requests to available resources, eliminating the need for a central server and enabling efficient resource allocation based on available resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a one-to-one mapping between client and server is used, then resource allocation is simple and direct, but scalability is poor and resource availability cannot be effectively managed across multiple servers

Engineering Contradiction:
Improveresource allocation mechanismVSAvoidscalability
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The address space is divided into multiple regions, with each region mapped to a different server. This segmentation allows the system to scale by adding more regions and servers without changing the fundamental client-request structure, resolving the contradiction between simple allocation and scalability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a new dimension (address space regions) to the traditional one-to-one client-server mapping. By mapping multiple servers to different regions of the address space, the system achieves scalability while maintaining the simplicity of direct address-based requests.

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

2Reliability

If a central server is used for resource allocation, then resource management is centralized and controlled, but the load on the central server increases and availability decreases

Engineering Contradiction:
Improveresource management controlVSAvoidresource allocation efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts the resource allocation function from a single central server and distributes it across multiple servers through address space region mapping. Each server independently manages its assigned region, eliminating the bottleneck and single point of failure while maintaining controlled resource management.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The address space acts as an intermediary layer between clients and servers. Instead of clients directly querying a central server for resource allocation, requests are routed through the address space mapping mechanism, which distributes load across multiple servers while maintaining organized resource management.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If multiple servers are available to satisfy requests, then resource availability increases, but the mapping complexity between clients and servers increases

Engineering Contradiction:
Improveresource availabilityVSAvoidclient-server mapping
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The address space provides a universal interface for all clients to access multiple servers. Instead of implementing complex client-side logic for server selection, the address space universally handles routing requests to appropriate servers based on region mapping, simplifying the client-server interaction while supporting multiple servers.

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

Data Source

PatentUS7685312B1Resource location by address space allocation
Publication Date: 2010.03.23 ORACLE AMERICAN INC
  • US7685312B1 patent drawing
  • US7685312B1 patent drawing
  • US7685312B1 patent drawing

AI summary

A method for locating a free resource involves maintaining an address space containing a plurality of regions, wherein each of the plurality of regions is mapped with a server to obtain a mapping, transmitting a request for the free resource from a client to a request address that belongs to one of the plurality of regions, determining a selected server using the mapping, and directing the request for the free resource to the selected server.