US 12,190,398 B2
Systems and methods for facilitating a reverse-entry process
Joseph Derek Morrison, Brooklyn, NY (US); and Richard Harvey Winslow, Jr., Glen Ridge, NJ (US)
Assigned to EAB Global, Inc., Washington, DC (US)
Filed by EAB Global, Inc., Washington, DC (US)
Filed on Nov. 21, 2022, as Appl. No. 18/057,718.
Application 18/057,718 is a continuation of application No. 17/032,086, filed on Sep. 25, 2020, abandoned.
Prior Publication US 2024/0171646 A1, May 23, 2024
Int. Cl. G06F 15/16 (2006.01); G06F 16/28 (2019.01); G06F 16/9535 (2019.01); G06F 21/62 (2013.01); G06Q 10/0631 (2023.01); G06Q 10/10 (2023.01); G06Q 30/018 (2023.01); G06Q 50/20 (2012.01); H04L 67/306 (2022.01)
CPC G06Q 50/2053 (2013.01) [G06F 16/288 (2019.01); G06F 16/9535 (2019.01); G06F 21/6254 (2013.01); G06Q 10/06311 (2013.01); G06Q 10/10 (2013.01); G06Q 30/0185 (2013.01); H04L 67/306 (2013.01)] 17 Claims
OG exemplary drawing
 
1. A computer-implemented method for facilitating a reverse-entry process, comprising:
obtaining a centralized first database of user profiles;
obtaining a second database of entity profiles corresponding to a plurality of distributed entities, each entity profile in the second database corresponding to a respective entity and including a respective entry criteria;
comparing the first database and the second database to identify one or more matches between a respective entity profile in the second database and a respective user profile in the first database that satisfies the entry criteria of the respective entity profile;
for each match of the one or more matches:
generating a respective anonymized universal user profile that excludes identifying information from the respective user profile; and
transmitting the respective anonymized universal user profile to a respective entity device associated with the matching entity profile;
receiving at least one reverse-entry request from the respective entity devices, each reverse-entry request comprising at least one admission request identifying at least one of the respective anonymized universal user profiles and the respective entity sending the reverse-entry request;
for each reverse-entry request:
de-anonymizing the reverse-entry request by linking the reverse-entry request to a further user profile in the first database that is associated with the respective anonymized universal user profile identified in the reverse-entry request;
generating a respective reverse-entry notification based on the respective entity identified in the reverse-entry request and the further user profile; and
transmitting the respective reverse-entry notification to a user device corresponding to the further user profile.