Table Occupancy State Management for Concurrent Data Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In smart service scenarios, concurrent requests for the same service resource or table can lead to data processing errors, as existing methods fail to effectively manage the occupancy state and prevent simultaneous access.

Innovation Solution

A data processing method that involves obtaining the occupancy state of a service resource or table through a state identifier, locking the resource or table if idle, updating the state to 'in use' upon successful occupancy, and generating corresponding occupancy data to manage concurrent requests, thereby preventing errors from multiple simultaneous access attempts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If concurrent occupying-table requests are allowed to be processed simultaneously, then service response speed is improved, but data processing errors occur due to multiple simultaneous access attempts

Engineering Contradiction:
Improveservice response speedVSAvoiddata processing accuracy
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent applies preliminary action by checking the occupancy state of the target table before processing the occupying-table request. The server queries whether the table is currently occupied, and only processes the request if the table is idle. This preliminary check prevents concurrent access errors while maintaining efficient processing of valid requests.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary mechanism in the form of a state identifier that mediates between multiple concurrent requests. The state identifier indicates whether the table is occupied or idle, acting as a mediator that controls which request can successfully occupy the table. This intermediary prevents direct conflicts between concurrent requests while maintaining fast response times.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If table occupancy state is checked and updated without locking mechanism, then processing speed is maintained, but data integrity is compromised due to concurrent access

Engineering Contradiction:
Improveprocessing speedVSAvoiddata integrity
Core Design Contradiction:
ProductivityVSStability of the object's composition

Solution Approach 1:

The patent performs preliminary verification of the table's occupancy state before updating the state. By checking whether the table is idle before processing the occupying request, the system ensures data integrity without requiring complex locking mechanisms. This preliminary action maintains both processing speed and data stability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback by continuously monitoring and checking the occupancy state of the target table during the request processing. The server queries the current state before updating, ensuring that the state change is valid. This feedback mechanism maintains data integrity while avoiding the performance overhead of traditional locking mechanisms.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11893000B2Data processing methods, apparatuses and devices
Publication Date: 2024.02.06 RAJAX NETWORK &TECHNOLOGY (SHANGHAI) CO LTD
  • US11893000B2 patent drawing
  • US11893000B2 patent drawing
  • US11893000B2 patent drawing

AI summary

This specification provides data processing methods, apparatuses and devices. In embodiments of the specification, table data includes a state identifier for indicating whether a target table is in a use state or an idle state. Therefore, after an occupying-table request is received, the table data can be obtained, and the state of the target table can be determined from the state identifier in the table data. If the target table is in the idle state, the table data is locked; after the state identifier is updated to the use state, the table data is released; and occupying-table data of the target table is generated to respond to the occupying-table request.