IP Library Granted Patent US 12,468,528
Granted Patent B2
US 12,468,528 · App. 18/623,708 · Granted Nov 11, 2025

Methods and a system for interface extensions

Inventors: Kip Oliver Morgan (Atlanta, GA); Alexander Arrabis Bronola (Lawrenceville, GA); Meenakshi Sreeraman (Waxhaw, NC)
Assignee: NCR Voyix Corporation
G06F8/656G06F3/04812G06F8/20G06F8/38G06F9/466G06Q30/0641
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,468,528
App. No.
18/623,708
Granted
Nov 11, 2025
Kind
B2
Abstract

A base transaction User Interface (UI) is provided that provides transaction processing for transactions at transaction terminals. The base UI can be customized through independent and decoupled customization/extension files, which provide specific UI customizations for UI screen content, UI screen styles, UI screen views, UI screen workflows, and UI screen resource functionality. Customizations or extensions are achieved without modifying the base UI. The customizations or extensions are dynamically obtained during execution of the base UI from the corresponding files and processed by the base UI as user-defined custom overrides.

Claims (52)

1 . A method, comprising:

obtaining a customization to a base interface associated with a transaction interface for a transaction being processed on a terminal;

processing the base interface with a portion of the base interface overridden by the customization within the transaction interface on the terminal during the transaction without modifying a base interface source code associated with the base interface; and

providing the customization within the transaction interface during the transaction at the terminal based on the processing.

2 . The method of claim 1 , wherein obtaining further includes obtaining the customization as a branding file for the base interface, the branding file comprises instructions for one or more of overriding images, overriding fonts, overriding colors, and overriding layouts for text information rendered by the base interface during the transaction.

3 . The method of claim 1 , wherein obtaining further includes obtaining the customization as instructions for screen sequences and screen views for screens rendered by the base interface during the transaction.

4 . The method of claim 1 , wherein obtaining further includes obtaining the customization as instructions for user interface options and user interface functions for screens rendered by the base interface during the transaction.

5 . The method of claim 1 , wherein obtaining further includes obtaining the customization as instructions dynamically processed for the portion of the base interface and overrides comprising one or more of:

native rendered text with replacement text;

native styles for visual features with replacement styles for visual features;

native processing sequences for screens with replacement processing sequences for the screens;

native views for the screens rendered with replacement views for the screens; and

native features and native functions for the screens rendered with replacement features and replacement functions for the screens.

6 . The method of claim 1 , wherein obtaining further includes obtaining resource objects and resource attributes processed by the customization and integrating the resource objects and the resource attributes with the customization.

7 . The method of claim 6 , wherein obtaining further includes obtaining the resource attributes based on a written and spoken language used at a location associated with the terminal.

8 . The method of claim 1 , wherein obtaining further includes one or more of:

mapping a context or state defined in the portion to a replacement context for the customization;

mapping a view defined in the portion to a replacement view for the customization; and

mapping a parameter defined in the portion to a replacement parameter for the customization.

9 . The method of claim 8 , wherein processing further includes providing the replacement context, the replacement view, and the replacement parameter dynamically to the base interface when the portion is invoked by the base interface during the transaction.

10 . The method of claim 1 , wherein obtaining the customization further includes identifying the customization based on a geographical location associated with the terminal.

11 . The method of claim 1 , wherein obtaining the customization further includes identifying the customization based on a retailer identifier associated with a retailer that provides the terminal.

12 . A method comprising:

initiating a transaction interface on a terminal;

obtaining a customization file associated with the transaction interface, wherein the customization file comprises override data for a portion of the transaction interface; and

dynamically implementing the override data during a transaction to change one or more of:

default content;

default screen sequences;

default screen styles;

default screen layouts; and

default screen option functionality;

wherein the override data is dynamically implemented by the transaction interface without modifying a source code associated with the transaction interface.

13 . The method of claim 12 , wherein obtaining further includes identifying the customization file based on a terminal identifier for the terminal.

14 . The method of claim 12 , wherein obtaining further includes dynamically obtaining, by the transaction interface, the customization file based on a file path defined in a configuration file for the transaction interface.

15 . The method of claim 12 , wherein dynamically implementing further includes identifying the override data as an override to base content provided in a transaction interface screen of the transaction interface.

16 . The method of claim 12 , wherein dynamically implementing further includes identifying the override data as an override to base sequences of transaction interface screens of the transaction interface.

17 . The method of claim 12 , wherein dynamically implementing further includes identifying the override data as an override to a base style presented for transaction screen interfaces of the transaction interface.

18 . The method of claim 12 , wherein dynamically implementing further includes dynamically altering a base-provided feature or attribute of the transaction interface with the override data.

19 . A system comprising:

a terminal comprising a processor and a non-transitory computer-readable storage medium;

the non-transitory computer-readable storage medium comprising customization filed and executable instructions for a transaction user interface (UI);

each customization file comprising text and instructions for custom overrides to the transaction UI; and

the transaction UI executed by the processor causing the processor to perform operations comprising:

dynamically obtaining the customization filed upon initiation on the terminal during a transaction being processed on the terminal; and

dynamically implement at least one custom override during the transaction to change one or more of:

default content;

default screen sequences for screens rendered on a display of the terminal;

default screen styles;

default screen layouts; and

default screen option functionality provided by the transaction UI

wherein the at least one customer override is implemented without modifying a source code associated with the transaction UI.

20 . The system of claim 19 , wherein the terminal is a point-of-sale terminal, a self-service terminal, an automated teller machine, a phone, or a tablet computer.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 25, 2025
From: MORGAN, KIP OLIVER; BRONOLA, ALEXANDER ARRABIS
To: NCR CORPORATION
Reel/Frame 070321/0282 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 25, 2025
From: SREERAMAN, MEENAKSHI
To: NCR CORPORATION
Reel/Frame 070321/0503 →
CHANGE OF NAME Recorded Feb 25, 2025
From: NCR CORPORATION
To: NCR VOYIX CORPORATION
Reel/Frame 070321/0717 →
Continuity (3)
Division 17690307 · Mar 9, 2022
Continuation 16947391 · Jul 30, 2020
Related Publication 20240354099A1 · Oct 24, 2024
References Cited (46)
US 6115711A · White · 2000 [cited by applicant]
US 7404177B1 · Greenfield et al. · 2008 [cited by applicant]
US 8327351B2 · Paladino et al. · 2012 [cited by applicant]
US 8438539B2 · Hertenstein · 2013 [cited by applicant]
US 8555273B1 · Chia et al. · 2013 [cited by applicant]
US 9002574B2 · Garrett et al. · 2015 [cited by applicant]
US 9600247B2 · Sutherland et al. · 2017 [cited by applicant]
US 9699610B1 · Chicoine · 2017 [cited by examiner]
US 10296450B2 · Vainer · 2019 [cited by applicant]
US 10891821B2 · Swaine · 2021 [cited by examiner]
US 11663199B1 · Kiselev et al. · 2023 [cited by applicant]
US 20030058277A1 · Bowman-Amuah · 2003 [cited by applicant]
US 20090132966A1 · Lahiri · 2009 [cited by applicant]
US 20090282423A1 · Smith · 2009 [cited by examiner]
US 20140258894A1 · Brown et al. · 2014 [cited by applicant]
US 20150205595A1 · Dudai · 2015 [cited by applicant]
US 20170269976A1 · Venkataraman et al. · 2017 [cited by applicant]
US 20180225209A1 · Mannava et al. · 2018 [cited by applicant]
US 20190197181A1 · Li et al. · 2019 [cited by applicant]
US 20190251063A1 · Colla et al. · 2019 [cited by applicant]
US 20190370780A1 · Monaghan · 2019 [cited by examiner]
US 20200264766A1 · Hameed · 2020 [cited by examiner]
US 20200394708A1 · Cella · 2020 [cited by applicant]
US 20200394709A1 · Cella · 2020 [cited by applicant]
US 20210226774A1 · Padmanabhan · 2021 [cited by applicant]
US 20210304146A1 · Helft et al. · 2021 [cited by applicant]
U.S. Appl. No. 16/947,391 U.S. Pat. No. 11,354,115, filed Jul. 30, 2020, Methods and a System for Interface Extensions. [cited by applicant]
U.S. Appl. No. 17/690,307 U.S. Pat. No. 11,947,955, filed Mar. 9, 2022, Methods and a System for Interface Extensions. [cited by applicant]
“U.S. Appl. No. 16/947,391, Advisory Action mailed Dec. 6, 2021”, 4 pgs. [cited by applicant]
“U.S. Appl. No. 16/947,391, Final Office Action mailed Sep. 24, 2021”, 16 pgs. [cited by applicant]
“U.S. Appl. No. 16/947,391, Non Final Office Action mailed Mar. 23, 2021”, 15 pgs. [cited by applicant]
“U.S. Appl. No. 16/947,391, Notice of Allowance mailed Feb. 7, 2022”, 11 pgs. [cited by applicant]
“U.S. Appl. No. 16/947,391, Response filed Jun. 23, 2021 to Non Final Office Action mailed Mar. 23, 2021”, 8 pgs. [cited by applicant]
“U.S. Appl. No. 16/947,391, Response filed Nov. 22, 2021 to Final Office Action mailed Sep. 24, 2021”, 8 pgs. [cited by applicant]
“U.S. Appl. No. 17/690,307, Non Final Office Action mailed Jun. 16, 2023”, 13 pgs. [cited by applicant]
“U.S. Appl. No. 17/690,307, Notice of Allowance mailed Dec. 6, 2023”, 9 pgs. [cited by applicant]
“U.S. Appl. No. 17/690,307, Preliminary Amendment filed Mar. 22, 2022”, 7 pgs. [cited by applicant]
“U.S. Appl. No. 17/690,307, Response filed May 15, 2023 to Restriction Requirement mailed Mar. 13, 2023”, 9 pgs. [cited by applicant]
“U.S. Appl. No. 17/690,307, Response filed Sep. 18, 2023 to Non Final Office Action mailed Jun. 16, 2023”, 6 pgs. [cited by applicant]
“U.S. Appl. No. 17/690,307, Restriction Requirement mailed Mar. 13, 2023”, 6 pgs. [cited by applicant]
Joseph, Vinod Cherian, et al., “Modeling UI agents for public environments to enhance the V2oIP embedded AMT access point services”, (2005). [cited by applicant]
Ledeczi, Akos, “Composing domain-specific design environments”, Computer 34(11), (2001), 44-51. [cited by applicant]
Martin, G, “Overview of the MPSoC design challenge”, (2006), 274-279. [cited by applicant]
Shim, Ssy, “Business-to-business e-commerce frameworks”, (2000). [cited by applicant]
Thomas, C G, et al., “An adaptive environment for the user interface of Excel”, Proceedings of the 1st international conference on Intelligent user interfaces, (1993), 123-130. [cited by applicant]
Yoo, R M, et al., “Performance evaluation of Intel transactional synchronization extensions for high-performance computing”, (2013). [cited by applicant]