Providing customer information obtained from a carrier system to a client device

• US 10,154,082 B2
• Filed: 08/12/2014
• Issued: 12/11/2018
• Est. Priority Date: 08/12/2014
• Status: Active Grant

• Current Assignee: BOKU Identity Incorporated
• Original Assignee: Danal Incorporated (Twilio, Inc.)
• Inventors: Banerjee, Atreedev, Pardue, James
• Primary Examiner(s): Hirl, Jospeh P
• Assistant Examiner(s): Gundry, Stephen
• Application Number:
  US14/458,025
• Publication Number:
  US 20160050259A1
• Time in Patent Office: 1,582 Days
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/34 using cards, e.g. integrated circuit [IC] cards or magnetic cards
• CPC Class Codes: G06Q 30/00 Commerce
• CPC Class Codes: G06Q 30/0201 Market modelling; Market analysis; Collecting market data
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

Methods and systems are presented for accessing customer relationship management (CRM) information stored in a carrier system associated with a user of an identified client device. A client device is identified based on client device identification information received from a carrier system. CRM information associated with the identified client device is received from the carrier system, and data corresponding to at least a subset of the CRM information is output to the client device. The client device may be configured to pre-populate data fields of a transaction based on the data corresponding to at least a subset of the CRM information.

Claims

1. A system comprising:

an aggregator system comprising;

carrier input circuitry coupled to a carrier system and configured to receive customer relationship management (CRM) information and client device identification information from the carrier system;

client device output circuitry coupled to a client device and configured to provide data to the client device corresponding to at least a subset of the CRM information, wherein the client device is configured to;

receive a content page from a merchant system;

receive a selectable software import from the merchant system allowing the client device to directly communicate with the aggregator system;

pre-populate data fields on the content page based on the data corresponding to at least a subset of the CRM information received from the aggregation system; and

client device identification circuitry coupled to the carrier input circuitry and configured to identify the client device based on the client device identification information and to cause the data corresponding to at least a subset of the CRM information to be communicated to the client device based at least in part on the client device identification information.

2. The system of claim 1 further comprising authentication circuitry configured to authenticate a user in possession of the client device.

3. The system of claim 2, further comprising client device input circuitry configured to receive consent of the user, wherein the carrier input circuitry is configured to receive the CRM information based on the consent.

4. The system of claim 2, wherein the client device identification circuitry is further configured to cause the data corresponding to at least a subset of the CRM information to be communicated to the client device based at least in part on the user in possession of the client device being authenticated.

5. The system of claim 2, wherein the authentication circuitry is further configured to generate two authentication keys and merchant identification information, and to cause one of the two authentication keys and the merchant identification information to be communicated to a merchant system.

6. The system of claim 5, wherein the merchant system is configured to perform a hash operation on the merchant identification information using a hash function in order to generate hashed merchant identification information, and wherein the merchant system is further configured to communicate the hashed merchant identification information to the client device.

7. The system of claim 1, wherein the client device is coupled to the merchant system configured to generate a payload comprising at least one of correlation identification information, a timestamp value, a nonce value, and any combination thereof, wherein the merchant system is further configured to encrypt the payload to generate an encrypted payload, and wherein the merchant system is further configured to communicate the encrypted payload to the client device.

8. The system of claim 1, further comprising client device input circuitry coupled to the client device and configured to receive from the client device an identification call comprising a request object, a success handler, and an error handler, and wherein the execution of the identification call causes carrier identifying information and an authentication key to be communicated to the client device.

9. The system of claim 8, wherein the request object comprises at least one of hashed merchant identification information, an encrypted payload, a method name, one or more request-specific parameters, and any combination thereof.

10. The system of claim 8, wherein the client device input circuitry is further configured to receive from the client device a request for information call comprising a request object, a success handler, an error handler, and a pre-populating parameter, and wherein the execution of the request for information call causes the data corresponding to at least a subset of the CRM information to be communicated to the client device based at least in part on the authentication key.

11. The system of claim 10, wherein the request object comprises at least one of hashed merchant identification information, an encrypted payload, a method name, one or more request-specific parameters, and any combination thereof.

12. The system of claim 1, wherein the client device identification circuitry is configured to identify the client device based on a mobile originated message identification technique.

13. The system of claim 1, wherein the client device identification circuitry is configured to identify the client device based on a header enrichment identification technique.

14. The system of claim 1, wherein the CRM information is associated with a user in possession of the client device and comprises at least one of a name, an address, and billing information.

15. The system of claim 1, wherein the client device is configured to use the data corresponding to at least a subset of the CRM information as part of a transaction with the merchant system.

16. The system of claim 1, wherein the client device identification information comprises a mobile phone number corresponding to the client device.

17. A method comprising:

identifying, by an aggregator system, a client device based on client device identification information received from a carrier system;

receiving, by the aggregator system, customer relationship management (CRM) information from the carrier system; and

outputting, by the aggregator system, data corresponding to at least a subset of the CRM information to the client device based at least in part on the client device identification information, wherein the client device is configured to;

receive a content page from a merchant system;

receive a selectable software import from the merchant system allowing the client device to directly communicate with the aggregator system;

pre-populate data fields on the content page based on the data corresponding to at least a subset of the CRM information received from the aggregation system.

18. The method of claim 17, further comprising authenticating a user in possession of the client device.

19. The method of claim 18, further comprising receiving consent of the user from the client device, and wherein the CRM information is received based on the consent.

20. The method of claim 18, wherein outputting the data corresponding to at least a subset of the CRM information to the client device is based at least in part on the user in possession of the client device being authenticated.

21. The method of claim 17, wherein the merchant system is configured to provide software imports to the client device, and wherein the software imports allow the client device to interact with the aggregator system directly.

22. A non-transitory computer readable medium having stored instructions that when executed directs:

carrier input circuitry, in an aggregator system, to receive client device identification information from a carrier system;

client device identification circuitry, in the aggregator system, to identify a client device based on the client device identification information;

the carrier input circuitry to receive customer relationship management (CRM) information from the carrier system; and

communication circuitry, in the aggregator system, to output data corresponding to at least a subset of the CRM information to the client device based at least in part on the client device identification information, wherein the client device is configured to;

receive a content page from a merchant system;

receive a selectable software import from the merchant system allowing the client device to directly communicate with the aggregator system;

pre-populate data fields on the content page based on the data corresponding to at least a subset of the CRM information received from the aggregation system.

23. A system comprising:

an aggregator system comprising;

carrier input circuitry coupled to a carrier system and configured to receive customer relationship management (CRM) information from the carrier system;

merchant input circuitry coupled to a merchant system, wherein the merchant system stores client device identification information comprising a unique identifier associated with the client device, and wherein the merchant input circuitry is configured to receive the client device identification information from the merchant system;

client device output circuitry coupled to a client device and configured to provide data to the client device corresponding to at least a subset of the CRM information, wherein the client device is configured to pre-populate data fields based on the data corresponding to at least a subset of the CRM information; and

client device identification circuitry coupled to the merchant input circuitry and configured to identify the client device based on the client device identification information and to cause the data corresponding to at least a subset of the CRM information to be communicated to the client device based at least in part on the client device identification information.

24. The system of claim 23 further comprising authentication circuitry configured to authenticate a user in possession of the client device.

25. The system of claim 24, further comprising client device input circuitry configured to receive consent of the user, wherein the carrier input circuitry is configured to receive the CRM information based on the consent.

26. The system of claim 24, wherein the client device identification circuitry is further configured to cause the data corresponding to at least a subset of the CRM information to be communicated to the client device based at least in part on the user in possession of the client device being authenticated.

27. The system of claim 24, wherein the authentication circuitry is further configured to generate two authentication keys and merchant identification information, and to cause one of the two authentication keys and the merchant identification information to be communicated to a merchant system.

28. The system of claim 27, wherein the merchant system is configured to perform a hash operation on the merchant identification information using a hash function in order to generate hashed merchant identification information, and wherein the merchant system is further configured to communicate the hashed merchant identification information to the client device.

29. The system of claim 23, wherein the client device is coupled to the merchant system configured to generate a payload comprising at least one of correlation identification information, a timestamp value, a nonce value, and any combination thereof, wherein the merchant system is further configured to encrypt the payload to generate an encrypted payload, and wherein the merchant system is further configured to communicate the encrypted payload to the client device.

30. The system of claim 23, wherein a merchant system is configured to provide software imports to the client device, and wherein the software imports allow the client device to interact with the aggregator system directly.

31. The system of claim 30, further comprising client device input circuitry coupled to the client device and configured to receive from the client device an identification call comprising a request object, a success handler, and an error handler, and wherein the execution of the identification call causes carrier identifying information and an authentication key to be communicated to the client device.

32. The system of claim 31, wherein the request object comprises at least one of hashed merchant identification information, an encrypted payload, a method name, one or more request-specific parameters, and any combination thereof.

33. The system of claim 31, wherein the client device input circuitry is further configured to receive from the client device a request for information call comprising a request object, a success handler, an error handler, and a pre-populating parameter, and wherein the execution of the request for information call causes the data corresponding to at least a subset of the CRM information to be communicated to the client device based at least in part on the authentication key.

34. The system of claim 33, wherein the request object comprises at least one of hashed merchant identification information, an encrypted payload, a method name, one or more request-specific parameters, and any combination thereof.

35. The system of claim 23, wherein the client device identification circuitry is configured to identify the client device based on a mobile originated message identification technique.

36. The system of claim 23, wherein the client device identification circuitry is configured to identify the client device based on a header enrichment identification technique.

37. The system of claim 23, wherein the CRM information is associated with a user in possession of the client device and comprises at least one of a name, an address, and billing information.

38. The system of claim 23, wherein the client device is configured to use the data corresponding to at least a subset of the CRM information as part of a transaction with the merchant system.

39. The system of claim 23, wherein the client device identification information comprises a mobile phone number corresponding to the client device.

40. A system comprising:

a carrier system comprising;

client device input circuitry coupled to a client device and configured to receive client device identification information from the client device; and

aggregator output circuitry coupled to an aggregator system and configured to provide customer relationship management (CRM) information and the client device identification information to the aggregator system, wherein the aggregator system is configured to;

identify the client device based on the client device identification information; and

output data corresponding to at least a subset of the CRM information to the client device based on the client device identification information;

wherein the client device is configured to;

receive a content page from a merchant system;

receive a selectable software import from the merchant system allowing the client device to directly communicate with the aggregator system;

pre-populate data fields on the content page based on the data corresponding to at least a subset of the CRM information received from the aggregation system.

41. A system comprising:

a merchant system comprising;

client device input circuitry coupled to a client device and configured to receive client device identification information from the client device; and

aggregator output circuitry coupled to an aggregator system and configured to provide the client device identification information to the aggregator system, wherein the aggregator system is configured to;

identify the client device based on the client device identification information;

receive customer relationship management (CRM) information from a carrier system; and

output data corresponding to at least a subset of the CRM information to the client device based at least in part on the client device identification information;

wherein the client device is configured to;

receive a content page from a merchant system;

receive a selectable software import from the merchant system allowing the client device to directly communicate with the aggregator system;

pre-populate data fields on the content page based on the data corresponding to at least a subset of the CRM information received from the aggregation system.