Communication Token Identity Verification for Messaging Links
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing SMS marketing methods lack identity verification, leading to unauthorized access and misuse of promotional offers, potentially infringing consumer and merchant privacy rights, as forwarded messages can be received by non-targeted individuals and may contain personal information.
Innovation Solution
A method involving a communication server that transmits a link short message to a receiving terminal, generates a communication token, and performs identity verification by comparing it with a stored token, ensuring only authorized access to web data for opening a webpage, while sending a verification message if the token mismatch occurs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If short message is forwarded arbitrarily without verification, then consumers can access promotional offers and webpages, but non-targeted consumers may receive exclusive offers and privacy information may be infringed
Solution Approach 1:
The patent introduces a communication token as an intermediary between the short message and the webpage access. The token is generated by the server when the short message is sent and must be presented by the receiving terminal to access the webpage. This intermediary mechanism ensures that only the intended recipient (who has the token) can access the promotional content, preventing unauthorized access while maintaining ease of operation through automated verification.
Solution Approach 2:
The patent implements preliminary action by generating and attaching the communication token to the short message before it is sent to the recipient. The token is prepared in advance and embedded in the message, so that when the recipient clicks the link, the verification has already been set up. This preliminary preparation enables quick verification without adding significant steps for the user, resolving the contradiction between ease of access and reliability.
2Reliability
If identity verification is implemented through communication tokens, then unauthorized access is prevented, but the system complexity increases due to token generation and verification processes
Solution Approach 1:
The patent applies self-service by making the verification process automatic and self-executing. The receiving terminal automatically extracts the communication token from the short message and presents it to the server when accessing the webpage. The server automatically verifies the token without requiring manual intervention. This automation reduces the perceived complexity for users while maintaining high reliability through systematic verification.
Solution Approach 2:
The patent merges the verification process with the existing webpage access flow. Instead of creating a separate verification system, the communication token verification is integrated into the URL parameter passing mechanism. The token is embedded in the link itself, and the verification happens as part of the normal webpage loading process, reducing overall system complexity while maintaining security.
3Reliability
If web cookie with browsing token is used for verification, then access control is improved, but the system becomes more complex and may fail if cookie is not properly stored
Solution Approach 1:
The patent inverts the traditional approach by making the communication token the primary verification mechanism rather than relying solely on web cookies. The token is embedded directly in the short message and URL parameters, making it the fundamental basis for verification. The web cookie becomes a secondary storage mechanism rather than the primary verification method, reducing complexity while maintaining access control reliability.
Data Source
AI summary
A method implemented by a server includes: sending a link short message (LSM) to a terminal; generating a communication token (C token) based on a link request of the terminal, and determining whether the server has stored another identical C token; when negative, storing the C token, and sending web data and the C token to the terminal; when affirmative, further determining whether a web cookie in the link request contains a browsing token identical to the C token; when affirmative, sending the web data to the terminal; and when negative, sending a verification short message (VSM) to the terminal, and sending the web data to the terminal upon receiving a verification request within a predetermined duration since sending the VSM.