Text Message Token Authentication for Anomalous Message Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional technologies lack a reliable and efficient solution to prevent anomalous messages from being sent by bad actors to gain unauthorized access to a user's sensitive information communicated in text messages.
Innovation Solution
A system and method for implementing token-based authentication of text messages, where an entity communicates with a token server to obtain a security token, which is embedded into the message and verified by the user's device using a token server to authenticate the message's authenticity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional text message communication is used, then ease of operation is maintained, but reliability deteriorates due to inability to verify message authenticity
Solution Approach 1:
The patent introduces a token server as an intermediary component that generates and verifies security tokens. The token server mediates between the message sending entity and the user device, providing authentication services without requiring complex verification logic in each endpoint. This resolves the contradiction by centralizing the complexity in a dedicated security component while keeping the overall system reliable.
Solution Approach 2:
The authentication system is segmented into distinct functional components: the entity server that sends messages, the token server that generates and verifies tokens, and the user device that receives and validates tokens. This segmentation allows each component to have a specific, simplified responsibility, improving reliability without requiring the entire system to be complex.
2Reliability
If token-based authentication is implemented, then reliability improves through message verification, but device complexity increases due to additional authentication components
Solution Approach 1:
The entity server automatically requests and embeds security tokens in messages without requiring manual intervention. The user device automatically verifies tokens upon receiving messages. This self-service automation maintains ease of operation while implementing reliable authentication, as the complex verification processes occur automatically in the background.
Solution Approach 2:
The security token is generated and embedded in the message before the message is sent to the user. This preliminary action ensures that authentication data is already prepared and attached, allowing for quick verification at the receiving end without adding operational complexity during the actual message exchange.
3Reliability
If security tokens are generated and verified, then reliability improves by preventing unauthorized access, but loss of time increases due to additional verification steps
Solution Approach 1:
The security token is generated and embedded in the message before transmission. This preliminary action ensures that when the message reaches the user device, verification can occur immediately by simply checking the pre-attached token against the token server, minimizing verification time while maintaining strong unauthorized access prevention.
Solution Approach 2:
The patent replaces complex manual verification processes with automated electronic token verification. The token server quickly validates tokens using cryptographic comparisons, substituting time-consuming manual security checks with rapid automated processes that maintain high reliability with minimal time loss.
Data Source
AI summary
A system for implementing token-based authentication of text messages comprises an entity server in communication with a token server. The entity server sends a first message to the token server to request for a security token. The first message includes entity and user information with a reason for generating the security token. The token server generates the security token and sends it to the entity server. The token server stores the security token and associated data in a memory of the token server. The entity server sends a second message and the security token to a user device. The token server receives the second message and the security token from the user device for verification, and determines that the security token associated with the second message matches the stored data in the memory. The token server sends a validation message to the user device that the second message is authenticated.

