Endpoint Table Reallocation for Server Availability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In enterprise systems, particularly in healthcare, the allocation of service endpoints to servers is challenging when one server becomes non-operational, leading to service endpoint unavailability and disruption in processing requests.

Innovation Solution

An endpoint table is maintained to specify the allocation of service endpoints to server systems, allowing for reallocation of endpoints from a non-operational server to operational ones, ensuring continuous processing of requests and high availability by updating the table to direct packets to the newly allocated server.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If service endpoints are allocated to multiple servers for scalability and higher throughput, then system productivity and reliability improve, but system complexity increases due to the need for dynamic reallocation and endpoint table management

Engineering Contradiction:
ImprovethroughputVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces an endpoint table as an intermediary data structure that decouples the complexity of service endpoint allocation from the server processing logic. The endpoint table serves as a centralized registry that maps service endpoints to their allocated servers, allowing the system to manage complex allocations without increasing the complexity of individual server operations. This intermediary layer enables scalable throughput while containing system complexity in a manageable central component.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If service endpoints are statically allocated to servers, then system complexity is reduced, but system reliability deteriorates when servers become non-operational

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

Solution Approach 1:

The patent implements dynamic service endpoint allocation where the endpoint table can be updated in real-time to reflect changes in server operational status. When a server becomes non-operational, the system dynamically reallocates its service endpoints to other available servers by updating the endpoint table entries. This dynamic approach maintains high service availability while managing reallocation complexity through systematic table updates rather than complex redistribution algorithms.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system performs preliminary actions by maintaining the endpoint table in advance, which pre-establishes the mapping between service endpoints and servers. This preliminary structure allows for rapid reallocation when failures occur, as the system only needs to update existing table entries rather than compute new allocations from scratch. The endpoint table serves as a pre-prepared allocation framework that enables quick reliability recovery without complex real-time computation.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If service endpoints are reallocated dynamically upon server failure, then system reliability is maintained, but loss of time occurs during the reallocation process

Engineering Contradiction:
Improveservice continuityVSAvoidreallocation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The endpoint table is maintained in advance as a pre-configured allocation structure, allowing the system to perform rapid updates when server failures occur. Rather than computing allocations in real-time during failures, the system leverages the pre-established endpoint table framework to quickly redirect service endpoints to alternative servers. This preliminary structuring minimizes reallocation time while maintaining service continuity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system updates only the specific endpoint table entries affected by server failures rather than performing a complete system-wide reallocation. This partial action approach focuses computational effort only on the necessary changes, significantly reducing reallocation time. By updating individual endpoint mappings rather than reconstructing the entire allocation system, the patent achieves rapid service continuity with minimal time loss.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10110670B2Allocation of service endpoints to servers
Publication Date: 2018.10.23 ORACLE INT CORP
  • US10110670B2 patent drawing
  • US10110670B2 patent drawing
  • US10110670B2 patent drawing

AI summary

An aspect of the present disclosure provides for allocation of service endpoints to servers. In an embodiment, an endpoint table is maintained to specify currently allocation of respective service endpoints to corresponding server systems. Upon occurrence of a condition requiring reallocation of a first set of service endpoints currently allocated to a first server system, the first set of service endpoints are reallocated among the operational server systems (typically the server systems other than the first server system). The endpoint table is accordingly updated in accordance with the reallocation. When a packet is thereafter received directed for delivery to a target service endpoint, the packet is delivered to one of the operational server systems, which is indicated as being allocated the target service endpoint in the updated endpoint table.