Discontinuous Access Management Using Waiting Tickets

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Network systems face performance degradation and increased costs when handling a large number of user accesses due to limited resources, leading to delayed access processes or system downtime, as existing solutions like adding more servers are costly and inefficient.

Innovation Solution

Implementing a discontinuous access management method using waiting tickets to allocate resources, where user terminals are issued waiting tickets with sequence numbers and waiting times, allowing them to reconnect after a specified period, thereby managing resource allocation and preventing continuous access overload.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the number of servers is increased to handle more user requests, then the processing capability is improved, but the cost increases

Engineering Contradiction:
Improveprocessing capabilityVSAvoidcost
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The patent implements periodic action by controlling user access to the network system in discrete time intervals. The server allocates resources to a limited number of users simultaneously, then releases access to allow other users to connect. This periodic granting and releasing of access rights enables the single server to handle more total user requests over time without requiring additional hardware, thus improving productivity while avoiding increased costs.

Inventive Principle:
Principle #19Periodic action

2Reliability

If all users are maintained with continuous access to the network system, then user service quality is improved, but resource exhaustion occurs

Engineering Contradiction:
Improveuser service qualityVSAvoidresource availability
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent applies dynamics by making the access control system flexible and adaptive rather than static. The server dynamically adjusts which users have access at any given moment based on current resource availability and system conditions. Users can be granted access, then later released and re-granted access at different times, allowing the system to maintain good service quality for all users over time while preventing resource exhaustion through continuous adaptation of access patterns.

Inventive Principle:
Principle #15Dynamics

3Speed

If excessive requests are processed simultaneously, then user access speed is improved, but system stability deteriorates

Engineering Contradiction:
Improveaccess speedVSAvoidsystem stability
Core Design Contradiction:
SpeedVSStability of the object's composition

Solution Approach 1:

The patent implements preliminary action by pre-establishing access control rules and resource allocation limits before excessive requests can overwhelm the system. The server is configured with predetermined criteria for granting and releasing user access, allowing it to proactively manage request flow. When resource thresholds are approached, the system preemptively releases access to certain users before complete resource exhaustion occurs, maintaining system stability while still allowing high access speeds for users within the allocated capacity.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8775627B2Discontinuous access management method using waiting ticket for resource allocation control, waiting ticket management method, and resource allocation control method
Publication Date: 2014.07.08 STCLAB CO LTD
  • US8775627B2 patent drawing
  • US8775627B2 patent drawing
  • US8775627B2 patent drawing

AI summary

According to the present invention, it is determined whether to allocate a resource to a user having accessed without having a waiting ticket that indicates an access sequence number of the user terminal, and re-access of the user terminal after a waiting time is instructed by providing a waiting ticket and the waiting time to the user terminal if the user terminal cannot be allocated with the resource, and it is determined whether to allocate a resource to the user terminal having accessed with the waiting ticket and the resource is allocated to the user terminal if it is possible. If the resource cannot be allocated to the re-accessed user terminal, a waiting ticket and a waiting time are provided to the user terminal to instruct to access again after the waiting time has passed.