Lookup Service Opaque Resource ID Sharing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Representational state transfer (REST) APIs face challenges in enabling independent systems to communicate about shared resources without direct presence, particularly due to privacy concerns, making it difficult for applications to obtain a unique device identifier for user devices, especially when executing in isolated execution environments.
Innovation Solution
A method and system for sharing resource identification, where a lookup service on data processing hardware receives a resource ID request from an application, determines authorization, and transmits an opaque resource ID to the application, which can then use this ID to access information from a remote service, ensuring user consent and privacy through authentication and authorization processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If REST APIs are used to enable independent systems to communicate about shared resources, then system interoperability is improved, but privacy protection deteriorates due to exposure of device identifiers
Solution Approach 1:
The patent introduces a lookup service as an intermediary between applications and device identifiers. Instead of applications directly accessing device identifiers, they query the lookup service which returns opaque resource IDs. This mediator layer enables system communication while protecting privacy by never exposing actual device identifiers.
Solution Approach 2:
The patent creates opaque copies of device identifiers through resource IDs. These resource IDs are surrogate identifiers that reference the actual device identifier through the lookup service without revealing it. Applications work with these copied identifiers, achieving interoperability without privacy exposure.
2Reliability
If applications execute in isolated execution environments, then security is improved, but information sharing between applications deteriorates
Solution Approach 1:
The lookup service provides a universal mechanism that works across all isolated execution environments. By implementing a standard lookup service interface, applications in different isolated environments can all access the same resource ID system, enabling information sharing while maintaining their isolation and security boundaries.
3Ease of operation
If direct device identifier access is allowed, then application functionality is improved, but user consent requirements deteriorate
Solution Approach 1:
The system performs preliminary authorization by obtaining user consent once when the lookup service is configured. This advance authorization is stored and reused for subsequent resource ID queries, eliminating the need for repeated consent requests while maintaining user control. Applications can freely query resource IDs without triggering additional authorization complexity.
Data Source
AI summary
A method for sharing resource identification includes receiving, at a lookup service, from a first application executing on a particular device associated with a user, a resource identifier (ID) request requesting the lookup service to provide the first application access to a resource ID that identifies the particular device. The method also includes determining, by the lookup service, whether the first application executing on the particular device is authorized to access the resource ID. When the first application is authorized to access the resource ID, the method includes obtaining, by the lookup service, the resource ID and transmitting, by the lookup service, to the first application executing on the particular device, the resource ID.