Embedded Application Tags for Dynamic Web Content Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current web technologies face challenges in easily and cost-effectively integrating dynamic or real-time functionality into web pages and applications, particularly due to the complexity and varying infrastructure requirements of third-party APIs, which can be costly and time-consuming to implement and transition between.

Innovation Solution

The system allows developers to embed application tags in HTML, which are then populated by an actor app, providing a simple and declarative method to incorporate real-time features like presence, location, and communication functions without requiring extensive technical knowledge, leveraging existing web protocols like WebRTC and HTML5.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If third-party APIs are used to provide dynamic functionality, then real-time features can be integrated, but implementation complexity and transition costs increase

Engineering Contradiction:
Improvedynamic functionality integrationVSAvoidAPI implementation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (the tag system with actor apps) between the web content and third-party services. Instead of directly integrating complex APIs into web pages, the system uses simple embedded tags that interact with actor apps, which then communicate with external services. This mediator approach simplifies the integration process while maintaining access to dynamic functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the functionality into distinct components: embedded tags in web content, actor apps that process these tags, and external services. This segmentation allows each component to be developed and maintained independently, reducing overall system complexity and making transitions between services easier without affecting the entire system.

Inventive Principle:
Principle #1Segmentation

2Reliability

If in-house development is used to maintain control, then complete control over functionality is achieved, but development time and costs increase

Engineering Contradiction:
Improvecontrol over functionalityVSAvoiddevelopment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system enables self-service through the tag-actor app mechanism. Web developers can embed tags without needing to understand the underlying complex logic, while actor apps automatically handle the integration with external services. This allows organizations to maintain control over their web content while leveraging external services without investing significant time in custom development.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If multiple third-party APIs are used, then diverse functionality is achieved, but transition costs between APIs increase

Engineering Contradiction:
Improvefunctionality diversityVSAvoidtransition cost
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent creates a universal interface layer through the tag system that can work with multiple different actor apps and external services. The embedded tags use a standardized format that can interact with various services through different actor apps, providing multi-functionality while maintaining a consistent interface. This universality reduces transition costs when switching between services since the tag layer remains unchanged.

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

Data Source

PatentUS10108735B2System and method of embedded application tags
Publication Date: 2018.10.23 ARLINGTON TECHNOLOGIES LLC
  • US10108735B2 patent drawing
  • US10108735B2 patent drawing
  • US10108735B2 patent drawing

AI summary

A method is provided for receiving and rendering web content on a client device having an installed actor app. Web content containing an embedded application tag is requested from a server. The web content is received from the server on the client device. The actor app receives and injects a value in the embedded application tag from dynamic data received with the web content. The web content is displayed together with the value of the dynamic data on the client device.