Service-Registered Link Responses Without Server-Side Preview Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing instant messaging systems require maintainers to interface with multiple service parties to manage link preview data, leading to high access and maintenance costs and difficulty in meeting user requirements due to the need for pre-storing data on servers, which complicates modifications and personalization.

Innovation Solution

An information processing method that saves registration information of service parties and determines target service parties based on interaction protocols, allowing data flow from a server to the service party, enabling personalized processing without server-side modifications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If service parties pre-store link preview data on the server, then link preview can be displayed quickly, but the server requires complex data management and maintenance operations

Engineering Contradiction:
Improvelink preview display speedVSAvoidserver data management complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent extracts the data storage responsibility from the server and transfers it to the service parties. Service parties store their own link preview data locally, and the server only manages registration information and forwards requests. This eliminates complex server-side data management while maintaining fast preview display through local data access at service parties.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If the server stores and manages link preview data, then data can be centrally controlled, but modifications require server-side operations increasing communication cost

Engineering Contradiction:
Improvedata control reliabilityVSAvoiddata modification time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent inverts the traditional data flow direction. Instead of the server pushing data to clients or receiving updates from service parties, service parties push their data to the server for storage and management. This inversion allows service parties to modify their own data independently without requiring server-side operations, reducing communication overhead and modification time while maintaining reliable data control through the registration mechanism.

Inventive Principle:
Principle #13The other way round (Inversion)

3Reliability

If each service party interfaces with the server for data management, then centralized control is achieved, but access and maintenance costs increase

Engineering Contradiction:
Improvecentralized data controlVSAvoidsystem development cost
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent creates a universal registration information storage mechanism that serves multiple functions: storing service party identification data, managing link-preview relationships, and enabling request forwarding. This single multi-functional registration system replaces the need for multiple separate interface mechanisms, reducing development complexity and maintenance costs while maintaining centralized control through the unified registration information structure.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS20250258884A1Information processing method and apparatus, electronic device, and storage medium
Publication Date: 2025.08.14 BEIJING ZITIAO NETWORK TECH CO LTD
  • US20250258884A1 patent drawing
  • US20250258884A1 patent drawing
  • US20250258884A1 patent drawing

AI summary

The present disclosure provides an information processing method and apparatus, an electronic device, and a storage medium. The information processing method comprises: in response to a registration operation of a service party, saving the registration information of the service party, the registration information comprising a link registered by the service party; and in response to request information transmitted by a target terminal and related to a target link, determining a target service party of the target link according to the registration information, and transmitting a notification to the target service party, so that the target service party responds to the target link according to the request information and a pre-agreed interaction protocol, wherein the interaction protocol is used for specifying a response mode of the service party to link-related different information.