Single Identifier Resource Access via Authentication Code

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing online platforms require users to register and login to access resources, limiting access to non-registered users and causing confusion when trying to grant access to different versions of resources, especially in development and testing scenarios where keeping the main resource unchanged is desired.

Innovation Solution

A computer-implemented method that allows accessing multiple resources via a single identifier by using an authentication code to determine access permissions and provide the appropriate resource, enabling access without requiring users to register with the hosting domain.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If users are required to register and login to access resources, then resource security and user accountability are improved, but user accessibility and ease of sharing resources are worsened

Engineering Contradiction:
Improveresource securityVSAvoiduser accessibility
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system segments the authentication process by introducing an intermediary authentication code that separates the resource owner's credentials from the user's access request. The resource owner generates and shares an authentication code without exposing their login credentials, while users can access resources using this code without registering. This segmentation resolves the contradiction by maintaining security through credential protection while improving accessibility through simplified user interaction.

Inventive Principle:
Principle #1Segmentation

2Manufacturing precision

If different versions of a resource are accessed via different identifiers, then resource version control is improved, but system complexity and potential for errors are worsened

Engineering Contradiction:
Improveresource version controlVSAvoidsystem complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The authentication code serves multiple functions: it identifies the resource, specifies the version, and provides access permissions. Instead of requiring separate identifiers for each resource version, the system uses a universal authentication code that can point to different versions of the same resource. This multi-functionality reduces system complexity while maintaining precise version control, as the same code structure can access multiple resource versions without requiring separate identifier management.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If the granter changes the resource identifier to grant access to different versions, then access control is improved, but the ability to keep the main resource unchanged is worsened

Engineering Contradiction:
Improveaccess controlVSAvoidresource integrity
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The authentication code acts as an intermediary between the resource identifier and the resource version. The granter can change which version the authentication code points to without modifying the main resource or its identifier. This intermediary mechanism allows flexible access control to different versions while keeping the main resource stable and unchanged, resolving the contradiction between adaptability and stability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11516279B2Systems and methods for accessing multiple resources via one identifier
Publication Date: 2022.11.29 GOOGLE LLC
  • US11516279B2 patent drawing
  • US11516279B2 patent drawing
  • US11516279B2 patent drawing

AI summary

A computer-implemented method includes receiving, by an application executing on a computing device, a first environment with a first identifier, in response to a first request comprising an authentication code. The method further includes associating, by the application, the first identifier with the authentication code, sending, by the application, a second request comprising the first identifier and the authentication code, and in response to sending the second request, receiving, by the application, a second environment with a second identifier. The second environment is a version snapshot of the first environment.