End-to-end management of authenticated communications
Disclosed herein are systems and methods for providing mobile call authentication. For instance, a token indicative of a call request can be received from a calling party. The token can include a called party number and a time of the request. A subscriber database can be accessed to determine identifying information associated with the calling party based at least in part on the token. The token can be authenticated based at least in part on the identifying information and using one or more predefined authentication protocols. The token can be stored in a call session registry storing data indicative of a plurality of active telephone call events. A verification request for the call request can be received from the called party. The call request can be verified based at least in part on the token. The called party can be notified that the call request has been verified.
1. A computer-implemented method for providing end-to-end mobile call authentication, the method comprising:
receiving, by one or more computing devices, a token indicative of a call request from a calling party, the token comprising a called party telephone number and a time of the call request, wherein the called party telephone number is associated with a called party and a called party device;
accessing, by the one or more computing devices, a subscriber database to determine the identifying information associated with the calling party based at least in part on the token;
authenticating, by the one or more computing devices, the token based at least in part on the identifying information and using one or more predefined authentication protocols;
storing, by the one or more computing devices, the authenticated token in a call session registry, wherein the call session registry stores tokens indicative of a plurality of active telephone call events until the telephone call events are terminated;
receiving, by the one or more computing devices, a verification request for the call request from the called party;
in response to receiving the verification request, verifying, by the one or more computing devices, the call request by determining that the authenticated token is currently stored in the call session registry; and
in response to the verifying, notifying, by the one or more computing devices, the called party that the call request has been verified.
2. The computer-implemented method of claim 1 , further comprising, prior to receiving the token indicative of the call request:
receiving, by the one or more computing devices, first subscriber data specifying one or more attributes of the calling party, and second subscriber data specifying one or more attributes of the called party; and
registering, by the one or more computing devices, the calling party based at least in part on the first subscriber data, and the called party based at least in part on the second subscriber data;
wherein the first subscriber data and the second subscriber data comprise the identifying information, device information, and subscription or policy information respectively associated with the calling party and the called party; and
wherein accessing the subscriber database comprises accessing at least one of the first subscriber data and the second subscriber data.
3. The computer-implemented method of claim 1 , further comprising:
accessing, by the one or more computing devices, the subscriber database to determine device capabilities and specifications of the called party device;
identifying in the subscriber database, by the one or more computing devices, content associated with the calling party to be provided to the called party device; and
determining, by the one or more computing devices, whether the content can be accommodated by the called party device based at least in part on the capabilities and specifications of the called party device.
4. The computer-implemented method of claim 3 , further comprising, when the content can be accommodated by the called party device, providing, by the one or more computing devices, the content to the called party device.
5. The computer-implemented method of claim 3 , further comprising, when the content cannot be accommodated by the called party device:
modifying, by the one or more computing devices, the content or
generating new content based at least in part on the capabilities and specifications of the called party device.
6. The computer-implemented method of claim 1 , further comprising:
determining, by the one or more computing devices, when the call request or a telephone call resulting from the call request is no longer active; and
deleting, by the one or more computing devices, the token from the call session registry when the call request or the telephone call is no longer active.
7. The computer-implemented method of claim 1 , wherein the token further comprises at least one of a calling party telephone number, a direction of the call request, information associated with a telephone carrier, or information associated with a telephone network.
8. The computer-implemented method of claim 1 , wherein the identifying information associated with the called party comprises at least one of a user profile associated with a mobile application installed on a mobile phone of the called party, a unique identifier of the called party, or information specifying one or more services to which the called party subscribes.
9. The computer-implemented method of claim 1 , wherein the one or more predefined authentication protocols comprise a stir/shaken (S/S) protocol.
10. The computer-implemented method of claim 1 , wherein the calling party is an enterprise and the called party is a mobile telephone.
11. A call authentication system comprising:
a call session registry configured to store data indicative of a plurality of active telephone call events;
a subscriber database configured to store identifying information associated with a plurality of users; and
one or more processors coupled to the call session registry and the subscriber database, the one or more processors configured to:
receive a token indicative of a call request from a calling party, the token comprising a called party telephone number and a time of the call request, wherein the called party telephone number is associated with a called party and a called party device;
access the subscriber database to determine the identifying information associated with the called party based at least in part on the token;
authenticate the token based at least in part on the identifying information and using one or more predefined authentication protocols;
store the authenticated token in the call session registry, wherein the call session registry stores tokens indicative of a plurality of active telephone call events until the telephone call events are terminated;
receive a verification request for the call request from the called party;
in response to receiving the verification request, verify the call request by determining that the authenticated token is currently stored in the call session registry; and
in response to the verifying, notify the called party that the call request has been verified.
12. The call authentication system of claim 11 , the one or more processors further configured to, prior to receiving the token indicative of the call request:
receive first subscriber data specifying one or more attributes of the calling party, and second subscriber data specifying one or more attributes of the called party; and
register the calling party based at least in part on the first subscriber data, and the called party based at least in part on the second subscriber data;
wherein the first subscriber data and the second subscriber data comprise the identifying information, device information, and subscription or policy information respectively associated with the calling party and the called party; and
wherein accessing the subscriber database comprises accessing the first subscriber data and the second subscriber data.
13. The call authentication system of claim 11 , wherein the one or more processors are further configured to:
access the subscriber database to determine device capabilities and specifications of the called party device;
identify, in the subscriber database, content associated with the calling party to be provided to the called party device; and
determine whether the content can be accommodated by the called party device based at least in part on the capabilities and specifications of the called party device.
14. The call authentication system of claim 13 , wherein the one or more processors are further configured to, when the content can be accommodated by the called party device, provide the content to the called party device.
15. The call authentication system of claim 13 , wherein the one or more processors are further configured to, when the content cannot be accommodated by the called party device:
modify the content or
generating new content based at least in part on the capabilities and specifications of the called party device.
16. A non-transitory computer-readable media having instructions stored thereon that, when executed by one or more computing devices, causes the one or more computing devices to perform operations comprising:
receiving a token indicative of a call request from a calling party, the token comprising a called party telephone number and a time of the call request, wherein the called party telephone number is associated with a called party and a called party device;
accessing, by the one or more computing devices, a subscriber database to determine identifying information associated with the called party based at least in part on the token;
authenticating the token based at least in part on the identifying information and using one or more predefined authentication protocols;
storing the authenticated token in a call session registry, wherein the call session registry stores tokens indicative of a plurality of active telephone call events until the telephone call events are terminated;
receiving a verification request for the call request from the called party;
in response to receiving the verification request, verifying the call request by determining that the authenticated token is currently stored in the call session registry; and
in response to the verifying, notifying the called party that the call request has been verified.
17. The non-transitory computer-readable media of claim 16 , the operations further comprising, prior to receiving the token indicative of the call request:
receiving first subscriber data specifying one or more attributes of the calling party, and second subscriber data specifying one or more attributes of the called party; and
registering the calling party based at least in part on the first subscriber data, and the called party based at least in part on the second subscriber data;
wherein the first subscriber data and the second subscriber data comprise the identifying information, device information, and subscription or policy information respectively associated with the calling party and the called party; and
wherein accessing the subscriber database comprises accessing the first subscriber data and the second subscriber data.
18. The non-transitory computer-readable media of claim 16 , the operations further comprising:
accessing the subscriber database to determine device capabilities and specifications of the called party device;
identifying, in the subscriber database, content associated with the calling party to be provided to the called party device; and
determining whether the content can be accommodated by the called party device based at least in part on the capabilities and specifications of the called party device.
19. The non-transitory computer-readable media of claim 16 , the operations further comprising:
determining when the call request or a telephone call resulting from the call request is no longer active; and
deleting the token from the call session registry when the call request or the telephone call is no longer active.