Back to results
US 11,232,393 B1Granted
Relationship based fulfillment systems and methods
AssigneeProject Noa, Inc.
InventorPaul Dohyung Kim
Life of this patent
Estimating the term…
Abstract
Described herein is a relationship based fulfillment system. Such a system may provide on-demand product fulfillment by personal and/or social contacts of a purchaser. The system may utilize the personal contacts and/or relationships of a user, as indicated through various contact databases or social groups of the user, to connect the user to various potential partners for providing relationship based fulfillment of products that are purchased by the user or performance of other relationship based services.
Claims20
A system comprising:
- a gateway, communicatively coupled to a network and configured to receive application data from user devices of user members;
- a location module, configured to receive location data from the user devices of the user members;
- a user database, configured to store user data associated with the user members, wherein the user data comprises daily ending locations of the user members;
- a group database, configured to store group data, the group data directed to one or more association groups, each of the association groups comprising a plurality of user members;
- an association database, configured to store association data, the association data indicating relationships between one or more association groups and one or more user members, wherein the association data is determined and periodically updated based on application data and/or location data;
- and
- a machine learning network, communicatively coupled to the location module and the user database, the machine learning network configured to perform a technique comprising:
- periodically receiving, with the location module and from a second user device associated with a second user, second user location data, generated by a global positioning system (GPS) device of the second user device;
- determining, with the machine learning network and based on the second user location data, a second user daily ending location;
- and
- providing, by the machine learning network to the user database, the second user daily ending location;
- a processor, communicatively coupled to the gateway, the user data, the group database, the association database, and the location module, the processor configured to perform operations comprising:
- receiving, with the gateway and from a first user device associated with a first user, a first pick-up request, wherein the first pick-up request is associated with a first pick-up location, a first drop-off location, and a first item category;
- receiving, with the location module and from the second user device, current second user location data, generated by the GPS device of the second user device, indicating a current second location of the second user device, and second user sensor data, generated by one or more of an accelerometer, a gyroscope, or a microphone of the second user device;
- determining, with the processor and from the current second user location data, the current second location;
- determining a shape and size of a merchant geofence around the first pick-up location, wherein the determining the shape and size of the merchant geofence comprises:
- determining, with the processor, an initial shape and size of the merchant geofence;
- determining, with the processor, that the merchant geofence does not meet a threshold candidate condition;
- and
- determining, with the processor, an updated shape and size of the merchant geofence;
- determining, with the processor, that the current second user location is within the updated merchant geofence;
- matching the second user to the first pick-up request, wherein the matching comprises:
- accessing, with the processor and in response to the first pick-up request, the association data stored within the association database to determine that the first user and the second user are both linked with a first association group;
- determining, with the processor and based on the association data and the first pick-up location, that the first association group is appropriate for the first pick-up request based on the first association group being related to the first item category;
- determining, with the processor and based on the second user sensor data, a mode of movement of the second user;
- determining, with the processor, a second user geofence around the current second location of the second user, wherein a size of the second user geofence is based on the determined mode of movement of the second user;
- determining, with the processor, that the first pick-up location is within the second user geofence;
- and
- accessing, with the processor, the second user daily ending location stored within the user database to determine that the first drop-off location is within a threshold distance of the second user daily ending location;
- and
- providing, with the gateway, first pick-up data comprising the first pick-up request to the second user device.
28 more elements
A method comprising:
- periodically receiving, with a location module and from a second user device associated with a second user, second user location data, generated by a global positioning system (GPS) device of the second user device;
- determining, with a machine learning network and based on the second user location data, a second user daily ending location;
- providing, by the machine learning network to a user database, the second user daily ending location;
- receiving, with a gateway and from a first user device associated with a first user, a first pick-up request, wherein the first pick-up request is associated with a first pick-up location, a first drop-off location, and a first item category;
- receiving, with a location module and from the second user device, current second user location data, generated by the GPS device of the second user device, indicating a current second location of the second user device, and second user sensor data, generated by one or more of an accelerometer, a gyroscope, or a microphone of the second user device;
- determining, with a processor and from the current second user location data, the current second location;
- determining a shape and size of a merchant geofence around the first pick-up location, wherein the determining the shape and size of the merchant geofence comprises:
- determining, with the processor, an initial shape and size of the merchant geofence;
- determining, with the processor, that the merchant geofence does not meet a threshold candidate condition;
- and
- determining, with the processor, an updated shape and size of the merchant geofence;
- determining, with the processor, that the current second user location is within the updated merchant geofence;
- matching the second user to the first pick-up request, wherein the matching comprises:
- accessing, with the processor and in response to the first pick-up request, association data stored within an association database to determine that the first user and the second user are both linked with a first association group;
- determining, with the processor and based on association data and the first pick-up location, that the first association group is appropriate for the first pick-up request based on the first association group being related to the first item category;
- determining, with the processor and based on the second user sensor data, a mode of movement of the second user;
- determining, with the processor, a second user geofence around the current second location of the second user, wherein a size of the second user geofence is based on the determined mode of movement of the second user;
- determining, with the processor, that the first pick-up location is within the second user geofence;
- and
- accessing, with the processor, the second user daily ending location stored within the user database to determine that the first drop-off location is within a threshold distance of the second user daily ending location;
- and
- providing, with the gateway, first pick-up data comprising the first pick-up request to the second user device.
19 more elements
Dependencies are inferred from the claim text.