Reusable Component Framework for Dynamic Message Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network-based content hosting and delivery systems lack dynamic functionality and secure user authentication capabilities, limiting the implementation of dynamic content and secure transactions within messages, especially due to the complexity of technologies like Accelerated Mobile Pages (AMP) and the expertise required.

Innovation Solution

A novel framework that enables dynamic messages with common reusable components, allowing user interaction and authentication through access tokens or third-party tokens, which abstract user interactions, provide analytics, and enable secure transactions within messages, thereby simplifying the implementation and enhancing user experience.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If Accelerated Mobile Pages (AMP) technology is implemented to provide dynamic content functionality, then dynamic content capability is improved, but device complexity and implementation difficulty increase significantly

Engineering Contradiction:
Improvedynamic content capabilityVSAvoidtechnology complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the complex AMP functionality into a separate server-side component handler that processes reusable components. The client device receives simplified message templates with placeholder components, while the server handles the complex logic of rendering dynamic content, thereby reducing client-side complexity while maintaining adaptability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a server-side component handler as an intermediary between the message template system and the dynamic content generation. This intermediary processes the reusable components and generates the actual dynamic content, shielding clients from the complexity of AMP technology while enabling dynamic functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If expert programming knowledge is required to implement dynamic content solutions, then dynamic functionality is achieved, but ease of operation deteriorates as users must become expert programmers

Engineering Contradiction:
Improvedynamic content functionalityVSAvoidimplementation ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system enables self-service by providing pre-configured reusable components that automatically handle dynamic content generation. Users simply select from available templates and components without needing to write code, as the server-side handler automatically processes these components into dynamic content, making the system accessible to non-programmers.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent uses template copying where standardized message templates with embedded reusable components are replicated and distributed. These templates contain all necessary structural elements, and users can instantiate them without programming knowledge, as the server handles the complex rendering logic.

Inventive Principle:
Principle #26Copying

3Ease of manufacture

If static content is used in messages, then implementation simplicity is maintained, but functionality and user engagement are limited

Engineering Contradiction:
Improveimplementation simplicityVSAvoidmessage functionality
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent creates universal reusable components that can be embedded in message templates and serve multiple functions. These components can represent different types of dynamic content (products, services, actions) and are processed by a universal server-side handler, allowing simple template implementation while achieving versatile functionality across different message types.

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

Solution Approach 2:

The system transitions from static content to dynamic content by introducing reusable components that can be instantiated with different data. The server-side handler dynamically generates content based on these components and user context, allowing messages to adapt and change based on user interactions while maintaining simple template structures.

Inventive Principle:
Principle #15Dynamics

4Reliability

If user authentication capabilities are added to enable secure transactions, then security is improved, but device complexity increases

Engineering Contradiction:
Improveuser authentication capabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a server-side authentication intermediary that handles user verification and token management. The client device simply includes authentication tokens in requests to access reusable components, while the server validates these tokens and manages authentication state, thereby providing secure transactions without significantly increasing client device complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20230318831A1System and method of authentication of users of common reusable components
Publication Date: 2023.10.05 YAHOO ASSETS LLC
  • US20230318831A1 patent drawing
  • US20230318831A1 patent drawing
  • US20230318831A1 patent drawing

AI summary

Disclosed are systems and methods that provide a framework that allows for novel user interactions with dynamic messages using common reusable components and further allows for authentication of the user to the sender of the message. According to an embodiment, the framework functions by providing a message including a common reusable component with a corresponding content. The common reusable component allows the user to interact with the content. In some embodiments, in response to an interaction of the user with the common reusable component, a request is generated to the sender of the message to provide additional content or to perform an action. In some embodiments, the request includes an access token, a third-party token, or both. In some embodiments, the third-party token is created based on a credential of the user.