Handle Resolution for Micro-blogging Message Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current micro-blogging systems face challenges in identifying and transmitting electronic messages to specific recipients without requiring the full domain name, as users often only type handles that partially identify the intended recipients, leading to difficulties in routing the messages to the correct user accounts.

Innovation Solution

The system employs a server-based mechanism to identify and resolve handles within messages by determining if they correspond to registered usernames for the author's domain or other domains, allowing for the automatic selection of the appropriate domain and transmission of the message to the intended recipient's account, even if the full domain name is not provided.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If users type only handles without full domain names to identify recipients, then user convenience and input speed are improved, but message routing accuracy and delivery reliability deteriorate

Engineering Contradiction:
Improveuser convenienceVSAvoidmessage routing accuracy
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The server system acts as an intermediary between the user's partial input (handle) and the complete routing information (full username with domain). The server receives the handle, queries the database to resolve it to a complete username, and uses that for accurate message routing. This intermediary resolution process maintains both user convenience and routing accuracy.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary resolution of handles to complete usernames on the server side before message delivery. By pre-resolving the handle to a full username through database lookup, the system ensures accurate routing information is available before the actual message transmission, eliminating the need for users to provide complete domain information.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the system requires full domain names for recipient identification, then message routing accuracy is improved, but user input complexity and time consumption increase

Engineering Contradiction:
Improvemessage routing accuracyVSAvoiduser input time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The server system automatically performs the domain resolution service without requiring user intervention. The system self-services the complete username generation by querying the database with the provided handle and retrieving the associated domain, eliminating the need for users to manually input or know the domain information.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The server acts as an intermediary that transforms the user's simple handle input into a complete routable username. The database serves as the intermediary data structure that maps handles to full usernames, enabling accurate routing without requiring users to provide complete information.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If the system performs domain resolution for handles, then message delivery accuracy to correct user accounts is improved, but server processing complexity increases

Engineering Contradiction:
Improvemessage delivery accuracyVSAvoidserver processing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary resolution of handles to complete usernames on the server side before message delivery. By pre-resolving the handle to a full username through database lookup, the system ensures accurate routing information is available before the actual message transmission, eliminating the need for users to provide complete domain information.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The server acts as an intermediary that transforms the user's partial input (handle) into a complete routable username. The database serves as the intermediary data structure that maps handles to full usernames, enabling accurate routing without requiring users to provide complete information.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9531649B2Identification of message recipients
Publication Date: 2016.12.27 GOOGLE LLC
  • US9531649B2 patent drawing
  • US9531649B2 patent drawing
  • US9531649B2 patent drawing

AI summary

In general, the subject matter described in this specification can be embodied in methods, systems, and program products for identifying a recipient for an electronic post. An electronic post that was authored by an authoring user is received. The post is detected to include text that partially, but not fully, identifies a target recipient for the post. The text that partially identifies the target recipient is determined to be associated with a valid first user account for a first domain or a valid second user account for a second domain. The first user account or the second user account is selected as a selected user account for the target recipient based on the determining. The electronic post is transmitted to a different remote computing device that is associated with the selected user account.