Message Push Verification System Preventing Crosstalk
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current signature authentication methods for message push requests in the OAUTH protocol cannot ensure that messages are sent to the correct message receiver, leading to potential security risks and message crosstalk.
Innovation Solution
A message push method that includes a verification system within the message pusher to verify the message provider's identity and ensure that messages are pushed to the correct message receiver by using a JWT format with additional digest information to identify the intended application and its corresponding key, preventing unauthorized message delivery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If signature authentication is used for message push requests, then authentication between servers is provided, but message crosstalk occurs when messages are sent to incorrect receivers
Solution Approach 1:
The patent applies preliminary action by pre-establishing a mapping relationship between application identifiers and preset keys before message pushing. The verification system queries this mapping relationship in advance to obtain the correct preset key corresponding to the application identifier in the message push request, ensuring that the message is sent to the correct receiver from the outset rather than attempting to correct errors afterward.
Solution Approach 2:
The patent introduces an intermediary verification system that acts as a mediator between the message provider and message receiver. This verification system contains a mapping relationship module that stores and manages the mapping between application identifiers and preset keys, and a verification module that uses this mapping to ensure messages are delivered to the correct destination, thereby preventing message crosstalk.
2Manufacturing precision
If JWT format with digest information is used, then message delivery accuracy is improved, but protocol complexity increases
Solution Approach 1:
The patent applies segmentation by dividing the message push request into distinct components: the JWT format carries application identifier information, while separate digest information carries verification data. The verification system separately processes these components by querying the mapping relationship for the application identifier and then verifying the digest using the retrieved preset key, making the complex verification process more manageable and structured.
Solution Approach 2:
The patent implements partial action by focusing verification efforts on critical elements only. Rather than verifying every aspect of the message, the system specifically verifies the digest information using the preset key obtained from the application identifier mapping. This targeted approach ensures message delivery accuracy without requiring complete re-verification of the entire message structure.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
Embodiments of this application provide a message push method, an electronic device, and a storage medium, and relate to the field of communications technologies. The method includes: creating a mapping relationship between an application identifier and a preset key; sending the mapping relationship to a message provider; receiving a to-be-pushed message and a message push request that are sent by the message provider, where the message push request includes first information and a first digest; performing digest extraction on the first information in the message push request by using the preset key, to obtain a second digest; and comparing the second digest with the first digest, and pushing the to-be-pushed message to a message receiver corresponding to the application identifier if the second digest is consistent with the first digest. According to the method provided in embodiments of this application, message crosstalk can be avoided, and message push security can be improved.