Interface Machine Buffering Hot Topic Messages

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The current methods for handling hot topic messages in User Generated Content systems, such as microblogs, lead to increased costs and limited request capacity due to the need for multiple data backups, which can result in system overload when a large number of requests are generated rapidly.

Innovation Solution

A method and system where multiple interface machines buffer hot topic messages, sharing the requests and reducing the load on the storage system by determining whether a message is a hot topic message based on buffering duration and request frequency, and retrieving it from a storage machine if necessary, ensuring data consistency by invalidating buffered messages after a valid period.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multiple data backups are built at the bottom layer of the storage system to distribute requests, then the request distribution capability is improved, but the system cost increases due to extra machine expenses

Engineering Contradiction:
Improverequest distribution capabilityVSAvoidsystem cost
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The interface machine performs preliminary buffering of hot topic messages before they reach the storage system. By anticipating and caching frequently accessed messages at the interface layer, the system avoids the need for multiple backup storage points, thereby distributing requests effectively without incurring additional machine expenses.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The interface machine acts as an intermediary between the user and the storage system. It buffers hot topic messages and validates their duration, mediating request distribution at the interface layer rather than requiring multiple backup storage points, thus reducing system cost while maintaining request distribution capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If multiple data backups are built to achieve request distribution, then the request handling capacity is improved, but the data synchronization complexity increases between main point and backup points

Engineering Contradiction:
Improverequest handling capacityVSAvoiddata synchronization complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent extracts the buffering and validation functionality from the storage system and places it at the interface machine. This separation removes the need for complex data synchronization between multiple backup points, as the interface machine independently manages hot topic message buffering and validation without requiring coordination with backup storage points.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The interface machine serves as an intermediary that handles hot topic message buffering and validation, eliminating the need for a complex multi-point backup synchronization system. By managing requests at the interface layer, it simplifies the storage system architecture while maintaining request handling capacity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If the maximum request quantity supported by backup points is exceeded, then the system reliability is maintained within limits, but the system breaks down when the limit is exceeded

Engineering Contradiction:
Improvesystem stabilityVSAvoidrequest quantity scalability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The interface machine performs preliminary buffering of hot topic messages and validates their duration before processing requests. This preliminary action enables the system to handle unlimited hot topic requests without relying on backup point capacity limits, thereby improving both stability and scalability beyond the constraints of traditional backup systems.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The interface machine autonomously manages hot topic message buffering and validation without requiring backup points. This self-service capability at the interface layer allows the system to scale request handling capacity dynamically based on actual hot topic traffic, rather than being constrained by predetermined backup point limits.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9612771B2Method and system for processing hot topic message
Publication Date: 2017.04.04 TENCENT TECHNOLOGY (SHENZHEN) CO LTD
  • US9612771B2 patent drawing
  • US9612771B2 patent drawing
  • US9612771B2 patent drawing

AI summary

Embodiments of the present invention provide a method and system for processing hot topic message. The method includes: receiving, by an interface machine, a read request for a message, and determining whether the interface machine has buffered the message and whether buffering duration of the message does not exceed preset valid duration; feeding back, if the message has been buffered and the buffering duration of the message does not exceed the preset valid duration, the message that the interface machine has buffered; and determining, if the message has been buffered but the buffering duration of the message exceeds the preset valid duration or the message is not buffered, whether the message is a hot topic message, and retrieving, if the message is a hot topic message, the hot topic message from a storage machine, buffering the hot topic message, recording a buffering moment, and feeding back the hot topic message.