Website Server Data Update via Conditional User ID Monitoring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing Internet service platforms face inefficiencies in updating user data, leading to prolonged wait times for users and excessive resource consumption, particularly when handling complex logic processing or introducing new services.

Innovation Solution

A method where a website server instructs clients to obtain and return user identification information based on preset conditions, allowing for efficient updating of service-related data only when necessary, using techniques like inserting IMG tags with HTML code to monitor user behavior and update data dynamically, thereby reducing resource consumption and improving user experience.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If stop-and-wait technique is used to update user data, then data accuracy is improved, but user waiting time increases

Engineering Contradiction:
Improvedata accuracyVSAvoiduser waiting time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-constructing data in advance before users access it. The system performs complex logic processing and data construction ahead of time, storing results in a buffer so that when users access the service, the data is already prepared and can be delivered immediately without requiring users to wait for processing.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If periodic pre-construction of data is used, then user experience is improved, but system resource consumption increases

Engineering Contradiction:
Improveuser experienceVSAvoidsystem resource consumption
Core Design Contradiction:
Ease of operationVSUse of energy by moving object

Solution Approach 1:

The patent applies dynamics by making the data pre-construction process adaptive rather than static. The system dynamically adjusts what data to pre-construct based on user behavior patterns, service types, and access frequencies. Frequently accessed data is pre-constructed, while less important data is constructed on-demand, optimizing the balance between user experience and resource consumption.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent applies local quality by differentiating data construction strategies for different users and services. Instead of uniformly pre-constructing all data for all users, the system identifies specific user groups and service types that benefit from pre-construction, applying this optimization locally where it provides the most value while avoiding unnecessary resource consumption for other cases.

Inventive Principle:
Principle #3Local quality

3Speed

If buffering of data is used, then data delivery speed is improved, but resource consumption increases when new services are introduced

Engineering Contradiction:
Improvedata delivery speedVSAvoidresource consumption
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The patent applies partial action by buffering only the critical path data that directly impacts user experience, rather than buffering all possible data. The system identifies which data must be pre-buffered to achieve fast delivery and buffers only that subset, leaving other data to be constructed on-demand, thus reducing overall resource consumption while maintaining acceptable delivery speeds.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentEP2488938B1Data update for website users based on preset conditions
Publication Date: 2019.04.17 ALIBABA GROUP HOLDING LTD
  • EP2488938B1 patent drawingFigure 1
  • EP2488938B1 patent drawingFigure 2
  • EP2488938B1 patent drawingFigure 3

AI summary

Updating user data on a website includes: authenticating a user who is accessing the website via a client; determining whether an operation behavior of the user satisfies a first preset condition; in the event that the first preset condition is satisfied, obtaining user identification information, including a user identifier (ID); determining whether a stored user property that corresponds to the user ID satisfies a second preset condition; and in the event that the second preset condition is satisfied, updating designated service related data of the user.