17885108. USER PAIRING AND TRIGGERING ACTIVITIES USING EVENT DATA simplified abstract (Capital One Services, LLC)
USER PAIRING AND TRIGGERING ACTIVITIES USING EVENT DATA
Organization Name
Inventor(s)
Leeyat Bracha Tessler of Arlington VA (US)
Tyler Maiman of Melville NY (US)
Phoebe Atkins of Rockville VA (US)
USER PAIRING AND TRIGGERING ACTIVITIES USING EVENT DATA - A simplified explanation of the abstract
This abstract first appeared for US patent application 17885108 titled 'USER PAIRING AND TRIGGERING ACTIVITIES USING EVENT DATA
Simplified Explanation
The abstract describes a system where a server receives sets of times from two users, determines their locations, identifies events based on the locations and times, selects events based on user data, and triggers API calls associated with the selected events.
- Server receives sets of times from two users
- Determines locations of the users
- Identifies events based on locations and times
- Selects events based on user data
- Triggers API calls associated with selected events
Potential Applications
- Event planning and coordination
- Location-based services
- Personalized event recommendations
Problems Solved
- Efficient event scheduling
- Personalized event suggestions
- Seamless API integration
Benefits
- Improved event coordination
- Personalized user experience
- Automated API interactions
Original Abstract Submitted
In some implementations, a server may receive, from a first user, an indication of a first set of times and receive, from the second user, an indication of a second set of times. The server may determine a first location associated with the first user and a second location associated with the second user. Accordingly, the server may identify a set of events based on the first location, the second location, the first set of times, and the second set of times. The server may further select a subset of events, from the set of events, based on first event data associated with the first user and second event data associated with the second user. Based on a selected event from the subset of events, the server may identify an API associated with the selected event and may trigger a call to the identified API.