Endpoint Resource Pooling in Multi-Router Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing distributed router systems face inefficiencies in sharing infrastructure due to conflicting endpoint assignments, increased server latency, and difficulty in maintaining minimum session guarantees across multiple applications, making demand-based pooling of endpoint resources in multi-application environments challenging.

Innovation Solution

A system and method that divides endpoints into zones, where routers assign and manage endpoint resources dynamically, ensuring that session requests are routed efficiently while maintaining minimum port guarantees for each application, and preloaded resources are loaded as needed, using algorithms like hash and load-balancing to optimize resource allocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If dedicated hardware is allocated to match peak load for each client, then service guarantees (minimum sessions, latency, availability) are met, but resource utilization becomes inefficient and costs increase

Engineering Contradiction:
Improveservice guaranteeVSAvoidresource utilization efficiency
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system segments the endpoint pool into multiple zones, with each router managing a specific zone. This segmentation allows independent control of endpoint assignments within each zone while maintaining overall system coordination, enabling efficient resource sharing without compromising service guarantees

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements dynamic endpoint assignment where routers can allocate and reassign endpoints based on real-time demand rather than static dedicated allocation. This dynamic approach allows endpoints to be shared across multiple applications while maintaining service level agreements through demand-based pooling

Inventive Principle:
Principle #15Dynamics

2Loss of energy

If infrastructure is shared among multiple applications, then resource efficiency improves, but conflicting endpoint assignments occur among routers

Engineering Contradiction:
Improveresource efficiencyVSAvoidendpoint assignment coordination
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

By dividing the endpoint pool into distinct zones and assigning each router to manage a specific zone, the system eliminates conflicting assignments. Each router has authoritative control over its zone, preventing the conflicts that would arise from multiple routers attempting to assign the same endpoint

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The zone assignment acts as an intermediary mechanism that coordinates endpoint assignments across the distributed router system. This intermediary structure enables shared infrastructure while maintaining assignment consistency through hierarchical control

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If endpoints are constantly reassigned to handle multiple applications, then resource sharing improves, but server latency increases due to cache changes

Engineering Contradiction:
Improveendpoint sharing capabilityVSAvoidserver latency
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by preloading resources onto endpoints before they are needed. This allows endpoints to be assigned to applications without incurring latency, as the required resources are already in place and do not need to be loaded during runtime

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system applies local quality by maintaining different endpoint assignments for different zones based on their specific application requirements. Each zone's endpoints are optimized for their assigned applications, reducing cache changes and latency while still enabling overall resource sharing across the system

Inventive Principle:
Principle #3Local quality

4Adaptability or versatility

If endpoints are reassigned dynamically, then resource pooling improves, but preloaded resources required by applications become difficult to maintain

Engineering Contradiction:
Improveresource pooling flexibilityVSAvoidpreloaded resource maintenance
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The system performs preliminary resource loading onto endpoints before assignment to applications. This ensures that when endpoints are assigned, the required preloaded resources are already in place, eliminating the difficulty of maintaining preloaded resources in a dynamically reassigned environment

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements dynamic resource loading where resources are loaded onto endpoints based on real-time assignment needs. This dynamic approach maintains preloaded resources efficiently by loading them only when endpoints are assigned to specific applications, rather than maintaining them statically on all endpoints

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9203706B2System and method for enabling demand-based pooling of endpoint resources in a multi-application environment
Publication Date: 2015.12.01 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9203706B2 patent drawing
  • US9203706B2 patent drawing
  • US9203706B2 patent drawing

AI summary

A system and method is provided for enabling demand-based pooling of endpoint resources in a multi-router, multi-application hosting system. The method includes dividing a plurality of endpoints into zones. Each of a plurality of routers is assigned to one of the zones. Each router is enabled to control endpoint assignments within its zone. In the preferred embodiment, for each application hosted by the system, all requests for the application are concentrated on the minimum number of endpoints required to meet demand and fault tolerance requirements. When a request for an application comes into the system, a router will route the request to an endpoint assigned to the application, regardless of whether the endpoint is within the router's zone. If a new endpoint is needed for the application, the router will assign an endpoint within its zone to the application, and inform the other routers of the assignment.