Token-Based PII Transmission With Ephemeral Runtime Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Striking a balance between effectively using Personal Identifiable Information (PII) data for personalized services while ensuring strict privacy protection and minimizing the risk of data breaches and unauthorized access is a significant challenge in modern digital environments.
Innovation Solution
A method and system for processing PII data in a runtime environment, where tokens are used to retrieve and process user data without persistent storage, utilizing Application Programming Interfaces (APIs) for secure data retrieval and deletion, and employing unique message IDs for tracking delivery data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If PII data is stored persistently for personalized services, then service personalization capability is improved, but data breach risk and privacy vulnerability increase
Solution Approach 1:
The patent extracts PII data from persistent storage by using tokens as substitutes. Instead of storing actual PII data in databases, the system stores only non-personal tokens that can be exchanged for PII data only when needed for a specific service interaction. This extraction of PII from persistent storage eliminates the breach risk while maintaining personalization capability through token-based access.
Solution Approach 2:
The patent introduces tokens as intermediary objects between the system and PII data. Tokens serve as mediators that represent PII data without being the data itself. The system stores and transmits only these intermediary tokens, which can be exchanged for actual PII data temporarily during service execution, then discarded. This intermediary mechanism enables personalization without persistent PII storage.
2Adaptability or versatility
If PII data is retrieved and processed for engagement campaigns, then service personalization is improved, but data retention time increases vulnerability window
Solution Approach 1:
The patent transforms the static PII storage model into a dynamic token-based system. Tokens are created dynamically when needed, used temporarily during the engagement campaign execution, and then discarded. This dynamic approach reduces the data retention window from potentially permanent storage to only the necessary duration for service execution, minimizing the vulnerability window while maintaining personalization.
Solution Approach 2:
The patent employs disposable tokens that are created, used, and then discarded. These tokens are inexpensive and short-lived compared to persistent PII storage. After serving their purpose in enabling personalization during the engagement campaign, the tokens are deleted, eliminating the need for long-term data retention and reducing ongoing vulnerability.
3Productivity
If third-party service providers are used for data broadcasting, then service delivery capability is improved, but PII data exposure risk increases
Solution Approach 1:
The patent extracts PII data from the data broadcasting process by using tokens instead. Third-party service providers receive and process only non-personal tokens, not actual PII data. This extraction of PII from the transmission process enables the system to leverage third-party delivery capabilities while preventing PII exposure to external providers.
Solution Approach 2:
The patent introduces tokens as intermediary data structures that facilitate communication with third-party service providers. These tokens act as mediators that enable service delivery functionality while preventing direct transmission of PII data to external providers. The tokens can be exchanged for PII data only when needed for the specific service interaction, then discarded.
Data Source
AI summary
A method for secure transmission of data is described. The method includes receiving a token corresponding to user data stored in a data storage device. Further, the PII data corresponding to the token is retrieved via an Application Programming Interface (API). The retrieved PII data is processed at a runtime environment for sending information to the users over one or more messages. The PII data is deleted from the runtime environment. Further, delivery data corresponding to delivered one or more messages is mapped with the token using a unique message ID.


