Register Content Management via Independent API Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current point of sale devices require extensive data transfer and time-consuming system updates to change display content, such as background images, due to security restrictions, making it inefficient to provide timely and location-specific content updates.

Innovation Solution

A register content management system that generates and sends new content, including background images, text, videos, and audibles, independently from application updates, using a content API and a register content management module that considers the identity, geographic location, and time-specific requests of each register.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional system updates are used to change display content on point of sale devices, then security requirements are met, but data transfer volume and update time increase significantly

Engineering Contradiction:
ImprovesecurityVSAvoidupdate time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the system update into two independent parts: application updates and register content updates. By separating the display content (background images, videos, text) from the core application software, the system can update content without triggering a full system image refresh. This segmentation allows content to be updated independently through a content API, reducing update time while maintaining security controls on the core application layer.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts the register content (displayable content) from the tightly-controlled system image. By pulling content updates outside the traditional application update process and creating a separate content delivery mechanism via API, the system enables rapid content changes without compromising the security-integrated application layer. This extraction allows content to be modified independently while the core system remains under security control.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If traditional system updates are used to change display content, then security controls are maintained, but data transfer volume increases

Engineering Contradiction:
ImprovesecurityVSAvoiddata transfer
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent segments the data transfer into two streams: small control signals for content requests/responses via API, and separate large application updates only when necessary. By segmenting content delivery from application deployment, the system transfers only the necessary content data (images, videos, text) without redundant system image data, significantly reducing overall data transfer volume while maintaining security through controlled API access.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts content delivery from the bulky system image update process. By creating a dedicated content API that transfers only the specific content data needed (background images, videos, text content), the system eliminates the need to transfer entire system images or application packages for content changes, dramatically reducing data transfer requirements while maintaining security through API-based access control.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If code development and deployment is performed to change background images, then functionality is achieved, but development time and deployment complexity increase

Engineering Contradiction:
Improvecontent customizationVSAvoidcode deployment complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a self-service content update mechanism where the register system can request and receive content updates through an API without requiring external code development or deployment. The system autonomously manages content delivery, storing and displaying content based on API responses. This eliminates the need for developers to write deployment code for each content change, reducing complexity while maintaining full content customization capabilities through parameter-based control.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent introduces a content API as an intermediary between the content source and the register system. This API layer handles all content delivery logic, authentication, and data formatting, eliminating the need for direct code integration for each content update. The intermediary absorbs the complexity of content management, allowing simple content changes without code deployment while maintaining adaptability through configurable content parameters.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If full system images are updated to change content, then security is maintained, but update frequency and responsiveness decrease

Engineering Contradiction:
ImprovesecurityVSAvoidcontent update efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments content updates from application updates, allowing content to be refreshed independently and frequently without triggering security-intensive full system image deployments. By segmenting the update process into lightweight content changes via API and rare application updates, the system achieves high content update efficiency while maintaining security through the integrity-protected application layer that only updates when absolutely necessary.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary content preparation and delivery through the content API, which can stage and deliver content updates independently of application deployment cycles. This preliminary action allows content to be ready for immediate deployment without waiting for full system image updates, increasing productivity while security is maintained through pre-authenticated API access and controlled content delivery before application changes occur.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12223488B2Systems and methods for managing and updating register content
Publication Date: 2025.02.11 TARGET BRANDS INC
  • US12223488B2 patent drawing
  • US12223488B2 patent drawing
  • US12223488B2 patent drawing

AI summary

Methods and systems for managing register content is described. A register content management module receives an identity of the retail location register, identifies a geographic location associated with the retail location register, identifies a time for which the updated register content is requested, generates a new register content, and sends the new register content to the retail location register independently from sending an application update to the retail location register.