Dynamic Content Generation via Server-Side Source Code Aggregation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data-encoded tags are limited in delivering dynamically-generated, interaction-specific content to network devices, as they can only pre-encode a small number of static data elements, failing to account for user-specific, device-specific, and environment-specific considerations.
Innovation Solution
A method and system that dynamically generate customized content by aggregating source code based on data elements such as tag identification, device metadata, user data, and environmental data, allowing for real-time content creation and delivery without preconfiguring static content types or interactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If static data elements are pre-encoded onto tags, then the tag technology is simple and easy to implement, but it cannot deliver dynamically-generated, interaction-specific content to network devices
Solution Approach 1:
A server computing device is introduced as an intermediary between the tag and the network device. The tag contains only a static URL pointer, while the server dynamically generates customized content by aggregating source code from a content repository based on received data elements (user identification, device identification, environmental data, etc.), then delivers the generated content to the network device. This intermediary approach enables dynamic content delivery without requiring complex logic in the simple tag structure.
2Productivity
If a content repository is preconfigured with separate sets of content for all possible interactions, then content delivery is fast and efficient, but the configuration becomes extremely complex and impractical
Solution Approach 1:
The content repository stores source code portions organized by data element types (user identification source code, device identification source code, environmental data source code, etc.) rather than pre-configuring complete content sets for every possible interaction scenario. The server dynamically aggregates these source code portions at runtime based on the specific combination of data elements received from each interaction, enabling flexible content generation without exhaustive preconfiguration.
Solution Approach 2:
The system changes the parameter organization from static content sets to dynamic source code aggregation. Instead of having fixed content for each interaction type, the server varies the aggregation of source code portions based on the specific parameters (data elements) received, such as user identification, device identification, and environmental conditions, thereby generating customized content on-demand.
3Loss of information
If tags only contain static URLs, then the tag structure is simple, but user-specific and device-specific personalization cannot be achieved
Solution Approach 1:
The tag pre-contains a static URL pointer that directs the network device to the server computing device. This preliminary action establishes the communication pathway without requiring the tag to store or process complex data. The actual personalization information (user identification, device identification, environmental data) is collected and processed by the server, which then generates the customized content payload incorporating all necessary information elements.
Data Source
AI summary
Methods and apparatuses are described for dynamically generating customized content for display on a network device. A server computing device receives a plurality of data elements from a network device upon initiation of an interaction between the network device and a tag in proximity to the network device. The server generates a content payload using at least a portion of the received data elements, where the content payload comprises source code defining content for display, a style of the content for display, and a layout of the content for display. The generating step includes querying a content repository based upon the received data elements to retrieve portions of the source code and aggregating the retrieved portions of the source code to form the content payload. The server computing device receives a request for the content payload, and transmits the content payload for generation of a graphical display.