Systems and methods for integrated third-party callbacks
Aspects described herein may allow for deploying third-party callback to be performed on a mobile device. For example, the mobile device may configure a third-party callback to be performed after a triggering event is detected by a remote device. The triggering event may relate to a remote device associated with the mobile device. A determination may be made as to whether the mobile device is within a pre-determined proximity of the remote device. If the two devices are in proximity and if the mobile device receives a message that indicates the triggering event has been detected, the mobile device may perform the third-party callback. In this way, a user's need to request services conveniently and accurately is facilitated.
1. A method comprising:
configuring, by a mobile device, a third-party callback to be performed by the mobile device based on a first location of a remote device associated with the mobile device, wherein the third-party callback comprises a request for transportation from a transportation service provider;
receiving, by the mobile device and from the remote device, a message comprising:
an indication of authentication, at the remote device, of biometric information of a user associated with the remote device or the mobile device; and
data indicating that the remote device has received an input command associated with the mobile device;
determining, by the mobile device and based on the indication of authentication of the biometric information of the user, that the first location of the remote device is within a pre-determined proximity of the mobile device;
determining, based on the first location of the remote device being within the pre-determined proximity, a second location of the mobile device; and
sending, by the mobile device, the third-party callback comprising the second location of the mobile device.
2. The method of claim 1 , wherein the message comprises data indicating a determination that the remote device has entered a geographical location.
3. The method of claim 1 , further comprising:
prior to the receiving the message, establishing, by the mobile device, a connection with the remote device by:
receiving, by the mobile device and from the remote device, a ping packet; and
sending, by the mobile device and to the remote device, a reply to the ping packet.
4. The method of claim 1 , wherein the determining that the first location of the remote device is within the pre-determined proximity of the mobile device further comprises:
broadcasting, by the mobile device and with a low transmission power, a connection request; and
receiving, by the mobile device and from the remote device, a reply to the connection request.
5. The method of claim 1 , wherein the determining that the first location of the remote device is within the pre-determined proximity of the mobile device further comprises:
determining, by the mobile device, that the mobile device and the remote device are connected to a same local network.
6. The method of claim 1 , wherein the sending the third-party callback comprises:
opening an application on the mobile device; and
sending, via the application and to a server associated with the transportation service provider, the third-party callback.
7. The method of claim 1 , wherein the sending the third-party callback further comprises:
sending, by the mobile device, an authentication request to authenticate the message;
receiving, by the mobile device, a response indicating that the message has been authenticated; and
sending the third-party callback further based on the response.
8. The method of claim 7 , wherein the message comprises a token, and wherein the sending the authentication request further comprises:
sending the token to a remote platform to authenticate the message.
9. A mobile device comprising:
one or more processors; and
memory configured to store computer instructions, when executed by the one or more processors, cause the mobile device to:
configure a third-party callback to be performed by the mobile device based on a first location of a remote device associated with the mobile device, wherein the third-party callback comprises a request for transportation from a transportation service provider;
receive, from the remote device, a message comprising:
an indication of authentication, at the remote device, of biometric information of a user associated with the remote device or the mobile device; and
data indicating that the remote device has received an input command associated with the mobile device;
determine, based on the indication of authentication of the biometric information of the user, whether the first location of the remote device is within a pre-determined proximity of the mobile device;
determine, based on the first location of the remote device being within the pre-determined proximity of the mobile device, a second location of the mobile device; and send the third-party callback comprising the second location of the mobile device.
10. The mobile device of claim 9 , wherein the computer instructions, when executed by the one or more processors, cause the mobile device to determine that the first location of the remote device is within the pre-determined proximity of the mobile device further based on:
determining that the mobile device and the remote device are connected to a same local network.
11. The mobile device of claim 9 , wherein the computer instructions, when executed by the one or more processors, cause the mobile device to send the third-party callback by causing the mobile device to:
Open an application on the mobile device; and
send, via the application and to a server associated with the transportation service provider, the third-party callback.
12. The mobile device of claim 9 , wherein the computer instructions, when executed by the one or more processors, cause the mobile device to send the third-party callback by further causing the mobile device to:
send an authentication request to authenticate the message;
receive a response indicating that the message has been authenticated; and
send the third-party callback further based on the response.
13. The mobile device of claim 9 , wherein the message comprises data indicating a determination that the remote device has entered a geographical location.
14. A non-transitory computer-readable medium storing computer instruction, when executed by one or more processors, cause a mobile device to:
configure a third-party callback to be performed by the mobile device based on a first location of a remote device associated with the mobile device, wherein the third-party callback comprises a request for transportation from a transportation service provider;
receive, from the remote device, a message comprising:
an indication of authentication, at the remote device, of biometric information of a user associated with the remote device or the mobile device; and
data indicating that the remote device has received an input command associated with the mobile device;
determining, based on the indication of authentication of the biometric information of the user, that the first location of the remote device is within a pre-determined proximity of the mobile device;
determine, based on the message, a second location of the mobile device; and send the third-party callback comprising the second location of the mobile device.
15. The non-transitory computer-readable medium of claim 14 , wherein
the mobile device and the remote device are connected to a same local network.
16. The non-transitory computer-readable medium of claim 14 , wherein the instructions, when executed by the one or more processors, cause the performing the third-party callback by causing:
opening an application on the mobile device; and
sending, via the application and to a server associated with the transportation service provider, the third-party callback.
17. The non-transitory computer-readable medium of claim 14 , wherein the instructions, when executed by the one or more processors, cause the sending the third-party callback by further causing:
sending an authentication request to authenticate the message;
receiving a response indicating that the message has been authenticated; and sending the third-party callback further based on the response.