RCD URL Verification via Unique Identifier Feedback
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems lack effective verification mechanisms for delivering rich call data (RCD) graphical objects to wireless devices during voice calls, which hinders user identification and service payment validation.
Innovation Solution
A system that modifies the URL of RCD extensions with a unique identifier and verifies delivery by matching this identifier with a confirmation from the content delivery network (CDN), ensuring the graphical object is displayed on the device and enabling payment collection for the service.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If RCD graphical objects are delivered to wireless devices during voice calls, then user identification capability is improved, but delivery verification reliability deteriorates due to lack of verification mechanisms
Solution Approach 1:
The patent implements a feedback mechanism where the CDN sends a delivery confirmation message back to the RCD system containing the unique identifier. This feedback loop allows the system to verify whether the graphical object was successfully delivered to the wireless device, resolving the reliability issue while maintaining information delivery capability
Solution Approach 2:
The system performs preliminary action by modifying the URL with a unique identifier before delivering the graphical object to the CDN. This pre-prepared verification mechanism is embedded in the delivery process itself, enabling subsequent verification without adding complex post-delivery checks
2Measurement precision
If URL modification with unique identifier is implemented for verification, then delivery verification accuracy is improved, but system complexity increases due to additional processing steps
Solution Approach 1:
The unique identifier serves multiple functions simultaneously: it is embedded in the modified URL for tracking, included in the delivery confirmation message for verification, and stored in both the RCD system and CDN for matching. This multi-functionality reduces the need for separate verification mechanisms, offsetting the added processing complexity
3Reliability
If delivery verification mechanism is implemented, then service payment validation reliability is improved, but processing time increases due to additional verification steps
Solution Approach 1:
The delivery confirmation message is sent continuously as part of the normal CDN operation flow rather than as a separate verification step. The CDN automatically sends confirmation upon successful delivery, and the RCD system verifies by matching the unique identifier, allowing payment validation without interrupting the call setup process
Data Source
AI summary
A system for verifying delivery of a graphical object to a device receives a session initiation protocol (SIP) request including a rich call data (RCD) extension with a URL to a graphical object stored at a content delivery network (CDN). The graphical object indicates the originating source of the SIP request and is to be presented on a display of the device upon receiving the SIP request. The system modifies the URL to include a unique identifier and sends the SIP request message with the modified URL to the device. The system receives a delivery confirmation message including a copy of the unique identifier from the CDN indicating that the graphical object was delivered to the device. The system verifies delivery of the graphical object to the device based on the copy of the unique identifier in the delivery confirmation message.