Apparatus for executing an application function using a smart card and methods therefor

• US 7,870,202 B2
• Filed: 06/05/2006
• Issued: 01/11/2011
• Est. Priority Date: 12/03/2004
• Status: Expired due to Fees

• Current Assignee: Fiserv Incorporated
• Original Assignee: Clairmail Incorporated (Fiserv Incorporated)
• Inventors: Madams, Peter H. C., Zadek, Ayelet, Salesky, Joseph H.
• Primary Examiner(s): Serrao; Ranodhi N
• Application Number:
  US11/422,318
• Publication Number:
  US 20060282528A1
• Time in Patent Office: 1,681 Days
• Field of Search: 709/206, 709/238, 709/219, 726/9, 726/12, 726/20, 455/418
• US Class Current: 709/206
• CPC Class Codes: G06F 15/173 using an interconnection network, e.g. matrix, shuffle, pyramid, star, snowflake
• 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 with a smart card. The method includes transmitting a first text message pertaining to a request to execute the application function to the proxy server. The method also includes sending a token request message to the user at a text message confirmation address that is different from the text message origination address, generating a token in the smart card, and transmitting the token to the proxy server. If the token is valid, the method includes executing the application function at the application server as specified by the first text message, whereby the first 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 mobile client device with a smart card, said mobile client device being coupled to a proxy server, said proxy server being further coupled to said application server that executes said application function, said method comprising:

receiving at said proxy server from said mobile client device a first message, wherein said first message includes a first message destination address and a first message origination address, and wherein said proxy server is a final destination of said first message, and wherein said first message pertains to a request to execute said application function, and wherein said first message includes a human-readable input parameter; and

wherein said first message conforms to a text-based user-to-user messaging protocol;

authenticating in said proxy server a user associated with said first message origination address by sending a token request message to said user at a message confirmation address and receiving a token generated by said smart card, wherein said token is received in said proxy server at a non-persistent message address that is configured to be inactivated after said authenticating;

selecting in said proxy server said application server based at least on said human-readable input parameter of said first message;

generating in said proxy server a second message utilizing said first message, wherein said second message is for use by said application server; and

transmitting to said application server from said proxy server said second message, to cause said application server to execute said application function based on said second message.

2. The method of claim 1 wherein said mobile 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 message further includes additional parameters in a body of said first message, and wherein said additional parameters are relevant to said execution of said application function, and wherein said additional parameters are expressed as alphanumeric text.

8. The method of claim 2 wherein said token request message is transmitted to said user using a first protocol that is different from a second protocol employed to transmit said first message from said user.

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

10. The method of claim 1, wherein said message confirmation address is different from said first message origination address.

11. The method of claim 1, wherein said message confirmation address is the same as said first message origination address.

12. The method of claim 1, wherein said first message is created on said mobile client device with a form selected from the group consisting of an XForm, a HTML form, and a WML form.

13. The method of claim 1, wherein said token is encrypted.

14. The method of claim 1, wherein said smart card includes a Subscriber Identity Module (SIM).

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

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