Architecture for general purpose trusted personal access system and methods therefor

• US 20060123092A1
• Filed: 11/15/2005
• Published: 06/08/2006
• Est. Priority Date: 12/03/2004
• Status: Active Grant

• Current Assignee: Fiserv Incorporated
• Original Assignee: Clairmail Incorporated (Fiserv Incorporated)
• Inventors: Madams, Peter H.C., Salesky, Joseph H.
• Granted Patent: US 7,844,674 B2
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04L 51/212 using filtering or selective blocking
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols

Abstract

A method for effecting the execution of an application function on an application server from a client device, the client device being coupled to a proxy server, the proxy server being further coupled to the application server that executes an application implementing the application function, is disclosed. The method includes receiving at the proxy server from the client device a first text message, the first text message including an text message destination address and an text message origination address, the first text message pertaining to a request to execute the application function. The method also includes authenticating a user associated with the first text message origination address by sending an authentication message to the user at an text message confirmation address that is different from the text message origination address and receiving confirmation from the user responsive to the authentication message. If the user is authenticated by the authenticating, the method further includes executing the application function at the application server as specified by the first text message, whereby the application function is ascertained based at least on the text message destination address.

Claims

1. A method for effecting the execution of an application function on an application server from a client device, said client device being coupled to a proxy server, said proxy server being further coupled to said application server that executes an application implementing said application function, comprising:

receiving at said proxy server from said client device a first text message, said first text message including a text message destination address and a text message origination address, said first text message pertaining to a request to execute said application function;

authenticating a user associated with said first text message origination address by sending an authentication message to said user at a text message confirmation address that is different from said text message origination address and receiving confirmation from said user responsive to said authentication message; and

if said user is authenticated by said authenticating, executing said application function at said application server as specified by said first text message, whereby said application function is ascertained based at least on said text message destination address.

2. The method of claim 1 wherein said client device is coupled to said proxy server via a first network, and said proxy server is coupled to said application server via a second network.

3. The method of claim 2, wherein said first network and said second network are the same.

4. The method of claim 2, wherein said first network and said second network are not the same.

5. The method of claim 2, wherein said first network is one of a wide area network, and a wireless network.

6. The method of claim 2, wherein said second network is one of a wide area network, a wireless network, and a local area network.

7. The method of claim 2 wherein said first text message further includes parameters in a body of said first text message, said parameters representing parameters relevant to said execution of said application function, said parameters being expressed as alphanumeric text.

8. The method of claim 7 wherein said authentication message is transmitted to said user using a first protocol that is different from a second protocol employed to transmit said first text message from said user.

9. The apparatus of claim 8, wherein said first protocol and said second protocol includes at least one of SMTP, SMS, MMS, IM, XMPP, web service, SOAP, XML, WAP, WML, HTTPS, and HTTP.

10. The method of claim 9 wherein said text message confirmation address represents a non-persistent text message address that is configured to be inactivated after said authenticating.

11. The method of claim 10 wherein said authenticating employs at least one of a time-sensitive authentication token, a personal identification number (PIN), and a password.

12. The method of claim 1, wherein said text message destination address is stored in a messaging address book on said client device.

13. The method of claim 1, wherein said first message on said client device with a form.

14. The method of claim 13, wherein said form is one of an XForm, a HTML form, and a WML form.

15. The method of claim 1, wherein said text message includes human readable text.

16. The method of claim 1, wherein said text message is a remote procedure call.

17. The method of claim 1, wherein said application server includes a graphical user interface, wherein said proxy server is coupled to said application server through said graphical user interface.

18. The method of claim 1, wherein said application server includes an API, wherein said proxy server is coupled to said application server through said API.

19. A method for effecting the execution of an application function on an application server from a client device, said client device being coupled to a proxy server, said proxy server being further coupled to said application server that executes an application implementing said application function, comprising:

receiving at said proxy server from said client device a first text message, said first text message including an text message destination address and an text message origination address, said first text message pertaining to a request to execute said application function;

authenticating a user associated with said first text message origination address by sending an authentication message to said user at a text message confirmation address that is the same as said text message origination address and receiving confirmation from said user responsive to said authentication message; and

if said user is authenticated by said authenticating, executing said application function at said application server as specified by said first text message, whereby said application function is ascertained based at least on said text message destination address.

20. A method for effecting the execution of an application function on an application server from a client device, said client device being coupled to a proxy server, said proxy server being further coupled to said application server that executes an application implementing said application function, comprising:

receiving at said proxy server from said client device a first message, said first message including a message destination address and a message origination address, said first message pertaining to a request to execute said application function; and

executing said application function at said application server as specified by said first message, whereby said application function is ascertained based at least on said message destination address.

21. The method of claim 20 wherein said client device is coupled to said proxy server via a first network, and said proxy server is coupled to said application server via a second network.

22. The method of claim 21, wherein said first network and said second network are the same.

23. The method of claim 21, wherein said first network and said second network are not the same.

24. The method of claim 21, wherein said first network is one of a wide area network, and a wireless network.

25. The method of claim 21, wherein said second network is one of a wide area network, a wireless network, and a local area network.

26. The method of claim 21 wherein said first text message further includes parameters in a body of said first text message, said parameters representing parameters relevant to said execution of said application function, said parameters being expressed as alphanumeric text.

27. The method of claim 21, wherein said text message destination address is stored in a messaging address book on said client device.

28. The method of claim 20, wherein said application server includes a graphical user interface, wherein said proxy server is coupled to said application server through said graphical user interface.

29. The method of claim 20, wherein said application server includes an API, wherein said proxy server is coupled to said application server through said API.

30. An architecture for enabling a client device to remotely execute an application function on an application server, said client device being coupled to a proxy server, said proxy server being further coupled to said application server that executes an application implementing said application function, comprising:

means for receiving at said proxy server from said client device a first text message, said first text message including a text message destination address and an text message origination address, said first text message pertaining to a request to execute said application function;

means for authenticating a user associated with said first text message origination address by sending an authentication message to said user at an text message confirmation address that is different from said first text message origination address and receiving confirmation from said user responsive to said authentication message; and

if said user is authenticated by said authenticating, means for executing said application function at said application server as specified by said first text message, whereby said application function is ascertained based at least on said text message destination address.

31. The apparatus of claim 30 wherein said client device is coupled to said proxy server via a first network, and said proxy server is coupled to said application server via a second network.

32. The apparatus of claim 31, wherein said first network and said second network are the same.

33. The apparatus of claim 31, wherein said first network and said second network are not the same.

34. The apparatus of claim 30, wherein said first network is one of a wide area network, and a wireless network.

35. The apparatus of claim 31, wherein said second network is one of a wide area network, a wireless network, and a local area network.

36. The apparatus of claim 31 wherein said first text message further includes parameters in a body of said first text message, said parameters representing parameters relevant to said execution of said application function, said parameters being expressed as alphanumeric text.

37. The apparatus of claim 36 wherein said authentication message is transmitted to said user using a first protocol that is different from a second protocol employed to transmit said first text message from said user.

38. The apparatus of claim 37, wherein said first protocol and said second protocol includes at least one of SMTP, SMS, IM, web service, SOAP, XML, HTTPS, and HTTP.

40. The apparatus of claim 38 wherein said authenticating employs at least one of a time-sensitive authentication token, a personal identification number (PIN), and a password.

41. The apparatus of claim 30, wherein said text message destination address is stored in a messaging address book on said client device.

42. The apparatus of claim 30, wherein said application server includes a graphical user interface, wherein said proxy server is coupled to said application server through said graphical user interface.

43. The apparatus of claim 30, wherein said application server includes an API, wherein said proxy server is coupled to said application server through said API.

39. The apparatus of clam 38 wherein said confirmation text message address represents a non-persistent text message address that is configured to be inactivated after said authenticating.