US11800011B1ActiveUtility

Call content management for mobile devices

92
Assignee: FIRST ORION CORPPriority: Aug 7, 2018Filed: May 25, 2021Granted: Oct 24, 2023
Est. expiryAug 7, 2038(~12.1 yrs left)· nominal 20-yr term from priority
H04M 3/4365H04W 12/062H04L 63/083H04L 63/0861H04M 3/42042H04M 2207/185H04W 12/06
92
PatentIndex Score
3
Cited by
38
References
20
Claims

Abstract

One example method of operation may include initiating a call via a calling device to a mobile device via a mobile device telephone number, responsive to initiating the call, retrieving call content data associated with a calling device profile, forwarding the call content data, via a content provider device, to the mobile device prior to establishing the call, hashing the mobile device telephone number to create a hashed value, storing the hashed value in the content provider device, authorizing the mobile device to receive the call content data, receiving a token representing the hashed value from the mobile device via the content delivery device, and connecting the call to the mobile device responsive to the token being authenticated.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
       1. A method comprising:
 initiating a call via a calling device to a mobile device via a mobile device telephone number; 
 hashing the mobile device telephone number to create a hashed value; 
 storing the hashed value in a content provider device; 
 forwarding an authorization request from the mobile device to a content delivery network; 
 installing an authorization application on the mobile device; 
 receiving an application programming interface (API) key at the mobile device; 
 responsive to receiving the API key, forwarding a token to the content delivery network which determines whether the token matches the hashed value; 
 authorizing the mobile device to receive call content; and 
 connecting the call to the mobile device responsive to the token being authenticated. 
 
     
     
       2. The method of  claim 1 , further comprising:
 comparing the token to the hash value stored in the content delivery device. 
 
     
     
       3. The method of  claim 1 , wherein the token comprises the hashed telephone number and one or more hardware identifiers of the mobile device. 
     
     
       4. The method of  claim 1 , further comprising:
 transmitting a notification to an application interface, the notification comprising a link to the call content. 
 
     
     
       5. The method of  claim 4 , further comprising:
 responsive to initiating the call, retrieving the call content associated with a calling device profile; and 
 responsive to receiving a confirmation of the notification being received, uploading the call content from the content provider device to the mobile device prior to establishing the call. 
 
     
     
       6. The method of  claim 1 , further comprising:
 responsive to connecting the call to the mobile device, loading the call content on a display of the mobile device. 
 
     
     
       7. The method of  claim 1 , wherein prior to completing the call, performing an authorization of the mobile device, wherein the authorization comprises one or more of a biometric data input, a passphrase input, and a mobile device location determination. 
     
     
       8. A system comprising:
 a calling device configured to call one or more mobile devices; 
 a content provider device configured to forward the call content data to the one or more mobile devices;
 wherein the calling device is configured to
 initiate a call to a mobile device among the one or more mobile devices via a mobile device telephone number; 
 wherein the content provider device is configured to 
 hash the mobile device telephone number to create a hashed value; and 
 store the hashed value in the content provider device; 
 wherein the mobile device is configured to 
 forward an authorization to a content delivery network; 
 install an authorization application; 
 receive an application programming interface (API) key; and 
 responsive to the API key being received, forward a token to the content delivery network which determines whether the token matches the hashed value; 
 wherein the call content device 
 authorizes the mobile device to receive the call content; 
 connects the call to the mobile device responsive to the token being authenticated. 
 
 
 
     
     
       9. The system of  claim 8 , wherein the token is compared to the hash value stored in the content delivery device. 
     
     
       10. The system of  claim 8 , wherein the token comprises the hashed telephone number and one or more hardware identifiers of the mobile device. 
     
     
       11. The system of  claim 8 , wherein a notification is transmitted to an application interface, the notification comprising a link to the call content. 
     
     
       12. The system of  claim 11 , wherein responsive to the call being initiated, the content delivery device retrieves the call content associated with a calling device profile and, responsive to a confirmation of the notification being received, upload the content from the content provider device to the mobile device prior to establishing the call. 
     
     
       13. The system of  claim 8 , wherein responsive to the call being connected to the mobile device, the mobile device loads the call content on a display of the mobile device. 
     
     
       14. The system of  claim 8 , wherein prior to the call being completed, perform an authorization of the mobile device via the content provider device, and wherein the authorization comprises one or more of a biometric data input, a passphrase input, and a mobile device location determination. 
     
     
       15. A non-transitory computer readable storage medium configured to store instructions that when executed cause a processor to perform:
 initiating a call via a calling device to a mobile device via a mobile device telephone number; 
 hashing the mobile device telephone number to create a hashed value; 
 storing the hashed value in a content provider device; 
 forwarding an authorization request from the mobile device to a content delivery network; 
 installing an authorization application on the mobile device; 
 receiving an application programming interface (API) key at the mobile device; 
 responsive to receiving the API key, forwarding a token to the content delivery network which determines whether the token matches the hashed value; 
 authorizing the mobile device to receive the call content; and 
 connecting the call to the mobile device responsive to the token being authenticated. 
 
     
     
       16. The non-transitory computer readable storage medium of  claim 15 , wherein the processor is further configured to perform:
 comparing the token to the hash value stored in the content delivery device. 
 
     
     
       17. The non-transitory computer readable storage medium of  claim 15 , wherein the token comprises the hashed telephone number and one or more hardware identifiers of the mobile device. 
     
     
       18. The non-transitory computer readable storage medium of  claim 15 , wherein the processor is further configured to perform:
 transmitting a notification to an application interface, the notification comprising a link to the call content. 
 
     
     
       19. The non-transitory computer readable storage medium of  claim 18 , wherein the processor is further configured to perform:
 responsive to initiating the call, retrieving the call content associated with a calling device profile; and 
 responsive to receiving a confirmation of the notification being received, uploading the call content from the content provider device to the mobile device prior to establishing the call. 
 
     
     
       20. The non-transitory computer readable storage medium of  claim 15 , wherein the processor is further configured to perform
 responsive to connecting the call to the mobile device, loading the call content on a display of the mobile device, wherein prior to completing the call, performing an authorization of the mobile device, wherein the authorization comprises one or more of a biometric data input, a passphrase input, and a mobile device location determination.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.