Call Identity Validation for Forwarded Calls
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing call authentication systems, such as STIR/SHAKEN, face challenges in maintaining end-to-end call identity validation when calls are forwarded, as they may not preserve the original attestation information and require additional processing resources for SHAKEN authentication.
Innovation Solution
A system and method that temporarily store identity information associated with an original call invite if the called device is likely to forward the call. This stored information is reused for end-to-end call identity validation of the forwarded call by matching it with the diverted call invite and attaching the original identity header, thereby preserving attestation information and reducing computational load.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the system performs full STIR/SHAKEN authentication for each forwarded call, then call identity validation reliability is improved, but computational resources and processing time are excessively consumed
Solution Approach 1:
The system performs STIR/SHAKEN authentication on the original call invite before forwarding, storing the validated identity header and attestation information in advance. When the call is forwarded, the pre-authenticated identity information is reused rather than performing authentication again, thus maintaining reliability while reducing computational resources for forwarded calls
Solution Approach 2:
The system creates a copy of the original validated identity header and attestation information and attaches it to the forwarded call invite. This copying approach allows the forwarded call to inherit the original authentication validity without requiring redundant computational verification, resolving the contradiction between validation reliability and resource consumption
2Reliability
If the system stores identity information for all called devices, then end-to-end call identity validation is improved, but device complexity and data management burden increase
Solution Approach 1:
The system applies selective storage by identifying called devices that are likely to forward calls based on specific criteria (such as forwarding history or device characteristics) and only storing identity information for those devices. This localized approach maintains end-to-end validation reliability for forwarded calls while avoiding the complexity of managing data for all called devices
3Loss of information
If the system attaches original identity header to diverted call invite, then attestation information preservation is improved, but processing complexity increases
Solution Approach 1:
The system extracts the validated identity header and attestation information from the original call invite and attaches them directly to the forwarded call invite. This extraction approach preserves attestation information effectively while using standardized protocol operations that minimize processing complexity compared to re-performing full authentication
Data Source
AI summary
The present disclosure describes providing end-to-end call identity validation of a forwarded call. Identity information associated with a received call invite may be temporarily stored and reused for the forwarded call when a determination is made that the called party is likely to forward the call. If the inbound call is diverted (forwarded) by the called device, a call invite comprising an indication that the invite has been diverted (forwarded) by the called device may be received. The system may match data associated with the diverted call invite with the stored identity information. In some examples, the SHAKEN identity header and SHAKEN token is stored and may be attached to the diverted call invite. DIV authentication may then be performed, and the diverted call invite comprising SHAKEN and DIV identity headers may be provided to the forward-to destination.