IP Library Granted Patent US 12,657,250
Granted Patent B2
US 12,657,250 · App. 18/243,535 · Granted Jun 16, 2026

Systems and methods for interconnecting directories

Inventors: Abigail Lindsey Welsford (Sidcup, GB); Boy Anthony Kuhne (London, GB); Christopher Paul Kendall (Leighton Buzzard, GB); David Andrew Bray (Rickmansworth, GB); Manish Murarka (London, GB); Stephen Richard Wright (Uxbridge, GB)
Assignee: VOCALINK INTERNATIONAL LIMITED
G06F16/9538H04L9/30
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,657,250
App. No.
18/243,535
Granted
Jun 16, 2026
Kind
B2
Abstract

Systems and methods are provided for interconnecting proxy directories, through core proxy services. One example computer-implemented method includes receiving, by a first proxy service core computing device, from a participant, a proxy lookup request, where the proxy lookup request includes a proxy and based on one or more routing rules, submitting the proxy lookup request to a second proxy service core computing device. The method also includes receiving, by the first proxy service core computing device, from the second proxy service core computing device, a proxy lookup response, which includes account data linked to the proxy, and returning the proxy lookup response, to the participant, in response to the proxy lookup request.

Claims (38)

1 . A computer-implemented method for use in interconnecting proxy directories, the method comprising:

determining, by a proxy service client computing device, a proxy from a proxy lookup request is not included in a local proxy directory and/or local memory of the proxy service client computing device, the proxy service client computing device specific to a participant;

based on the proxy not being included in the local proxy directory and/or the local memory, submitting, by the proxy service client computing device, the proxy lookup request to a first proxy service core computing device;

receiving, by the first proxy service core computing device, from the participant, via the proxy service client computing device, the proxy lookup request;

determining, by the first proxy service core computing device, the proxy from the proxy lookup request is not included in a local registry of the first proxy service core computing device;

based on the proxy not being included in the local registry;

identifying a second proxy service core computing device based, in part, on content of and/or format of the proxy; and

submitting, by the proxy service core computing device, the proxy lookup request to the second proxy service core computing device;

receiving, by the first proxy service core computing device, from the second proxy service core computing device, a proxy lookup response, which includes account data linked to the proxy; and

returning, by the first proxy service core computing device, the proxy lookup response, to the participant, via the proxy service client computing device, in response to the proxy lookup request.

2 . The computer-implemented method of claim 1 , wherein identifying the second proxy service core computing device is further based on one or more routing rules.

3 . The computer-implemented method of claim 1 , further comprising appending, by the first proxy service core computing device, an entry to a trail stack included in the proxy lookup request, the entry indicative of the participant and/or the first proxy service core computing device.

4 . The computer-implemented method of claim 1 , further comprising appending a public key associated with the participant to the proxy lookup request, thereby permitting another participant to encrypt the account data using the public key, prior to directing the encrypted account data toward the first proxy service core computing device.

5 . The computer-implemented method of claim 1 , further comprising modifying the proxy lookup request consistent with a defined format, prior to submitting the proxy lookup request to the second proxy service core computing device.

6 . The computer-implemented method of claim 1 , wherein the first proxy service core computing device is located in a first region and wherein the second proxy service core computer device is located in a second, different region.

7 . The computer-implemented method of claim 1 , further comprising signing at least a portion of the proxy lookup request and/or at least a portion of the proxy lookup response.

8 . The computer-implemented method of claim 1 , wherein the proxy includes a phone number;

wherein the account data includes a primary account number, an expiration date, and/or a card verification code; and

wherein the account data is encrypted.

9 . A system for use in interconnecting proxy directories, the system comprising:

a proxy service client computing device of a participant; and

a first proxy service core computing device coupled in communication with the proxy service client computing device;

wherein the proxy service client computing device is configured, by first executable instructions, to:

determine whether a proxy from a proxy lookup request is included in a local proxy directory and/or local memory of the proxy service client computing device;

based on the proxy not being included in the local proxy directory and/or the local memory, submit the proxy lookup request to the first proxy service core computing device; and

wherein the first proxy service core computing device is configured, by second executable instructions, to:

receive, from a participant, a proxy lookup request, the proxy lookup request including a proxy;

determine whether the proxy from the proxy lookup request is included in a local registry of the first proxy service core computing device;

based on the proxy not being included in the local registry;

identify a second proxy service core computing device based, in part, on content of and/or format of the proxy; and

submit the proxy lookup request to the second proxy service core computing device;

receive, from the second proxy service core computing device, a proxy lookup response, which includes account data linked to the proxy; and

return the proxy lookup response, to the participant, in response to the proxy lookup request.

10 . The system of claim 9 , wherein the first proxy service core computing device is further configured, by the second executable instructions, prior to submitting the proxy lookup request, to identify the second proxy service core computing device further based on one or more routing rules.

11 . The system of claim 9 , wherein the first proxy service core computing device is further configured, by the second executable instructions, to:

append an entry to a trail stack included in the proxy lookup request, the entry indicative of the participant and/or the first proxy service core computing device; and

append a public key associated with the participant to the proxy lookup request, thereby permitting another participant to encrypt the account data using the public key, prior to directing the encrypted account data toward the first proxy service core computing device.

12 . The system of claim 9 , wherein the first proxy service core computing device is further configured, by the second executable instructions, to modify the proxy lookup request consistent with a defined format, prior to submitting the proxy lookup request to the second proxy service core computing device.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 8, 2023
From: BRAY, DAVID ANDREW; KUHNE, BOY ANTHONY; WELSFORD, ABIGAIL LINDSEY; WRIGHT, STEPHEN RICHARD; KENDALL, CHRISTOPHER PAUL; MURARKA, MANISH
To: VOCALINK INTERNATIONAL LIMITED
Reel/Frame 064837/0955 →
Continuity (2)
Provisional Application 63406542 · Sep 14, 2022
Related Publication 20240086483A1 · Mar 14, 2024
References Cited (28)
US 10454690B1 · Popoveniuc et al. · 2019 [cited by applicant]
US 10728044B1 · Melo et al. · 2020 [cited by applicant]
US 12224991B1 · Joglekar et al. · 2025 [cited by applicant]
US 20030070070A1 · Yeager et al. · 2003 [cited by applicant]
US 20070073621A1 · Dulin et al. · 2007 [cited by applicant]
US 20090193443A1 · Lakshmanan · 2009 [cited by examiner]
US 20110289508A1 · Fell · 2011 [cited by examiner]
US 20120216035A1 · Leggette et al. · 2012 [cited by applicant]
US 20130117560A1 · Resch et al. · 2013 [cited by applicant]
US 20140040415A1 · Mathew · 2014 [cited by examiner]
US 20150262160A1 · Hursta · 2015 [cited by examiner]
US 20150278808A1 · Dulin et al. · 2015 [cited by applicant]
US 20160125370A1 · Grassadonia · 2016 [cited by examiner]
US 20160180299A1 · Sandraz · 2016 [cited by examiner]
US 20170093587A1 · Glisson · 2017 [cited by applicant]
US 20170302755A1 · Mathew · 2017 [cited by examiner]
US 20190036711A1 · Qiu · 2019 [cited by applicant]
US 20190363896A1 · Finlow-Bates · 2019 [cited by applicant]
US 20200028842A1 · Leiserson et al. · 2020 [cited by applicant]
US 20200076807A1 · Driever et al. · 2020 [cited by applicant]
US 20200275272A1 · Montemurro et al. · 2020 [cited by applicant]
US 20200311722A1 · Ginger · 2020 [cited by examiner]
US 20200322332A1 · Haque et al. · 2020 [cited by applicant]
US 20210083882A1 · Venable, Sr. · 2021 [cited by applicant]
US 20210135884A1 · Theodorou et al. · 2021 [cited by applicant]
US 20210247731A1 · Poluri et al. · 2021 [cited by applicant]
US 20210288822A1 · Sorensen et al. · 2021 [cited by applicant]
US 20220393884A1 · Panchamia et al. · 2022 [cited by applicant]