Message Push via Intermediary Triplet Decoupling Device ID
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In message push technologies, service provider servers need to acquire device IDs to send messages to clients, which can expose private user information, and existing methods do not effectively prevent this exposure.
Innovation Solution
A method and apparatus that allow message pushing without requiring the service provider server to acquire a device ID by using a preconfigured information triplet that includes the service provider server identifier, user identity, and client identifier, where the client identifier is locally acquired or obtained through network interaction, enabling the PUSH server to push messages to the client without exposing private information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the service provider server uses deviceID to identify the client for message push, then the message can be delivered to the correct client, but the user's private information may be exposed
Solution Approach 1:
The patent introduces an intermediary mechanism (the information triplet structure and push server) that decouples the service provider server from direct access to the deviceID. The push server acts as a mediator that receives the triplet, resolves the deviceID internally, and delivers the message without exposing the deviceID to the service provider server, thus maintaining delivery accuracy while protecting privacy
2Ease of operation
If the service provider server directly obtains deviceID for message push, then the implementation process is simple, but the system security is compromised
Solution Approach 1:
The patent segments the message push process into distinct functional modules: the service provider server generates only the spID and userID, the push server handles the triplet storage and resolution, and the deviceID is kept separate and protected. This segmentation allows each component to perform its function while maintaining overall system security without significantly complicating the implementation
Data Source
AI summary
A message push method and apparatus comprise: receiving a push request sent by a service provider server, where the push request carries pushed message content, a service provider server identifier, and a user identity user identity stored by the service provider server; querying a preconfigured information triplet according to the service provider server identifier and the user identity, and acquiring a client identifier of a client that will receive the pushed message content, where a correspondence among the service provider server identifier, the user identity, and the client identifier is recorded in the information triplet; and pushing the pushed message content to the client according to the client identifier. A message push can be implemented in a case in which a service provider server does not need to acquire a client identifier of a target terminal, thereby preventing private data from being exposed.