US2013267200A1PendingUtilityA1

System and method for secure transaction process via mobile device

62
Assignee: ACCELLS TECHNOLOGIES 2009 LTDPriority: Apr 10, 2012Filed: Dec 30, 2012Published: Oct 10, 2013
Est. expiryApr 10, 2032(~5.7 yrs left)· nominal 20-yr term from priority
G06Q 20/3223G06Q 20/425G06Q 20/3278H04L 63/083G06Q 20/40H04W 12/068H04W 12/06
62
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A system providing enhanced security for device based transactions, constituted of: a server associated with a network address; a first device associated with a user, the first device in communication with the server over a first communication channel responsive to an obtained server network address; a second device associated with the user arranged to obtain the server network address from the first device; and a mobile device server in communication with the second device over a second communication channel, the mobile device server in communication with the server via a third communication channel, the mobile device server arranged to: obtain the server network address from the second device over the second communication channel; obtain the server network address from a trusted source; and authorize to the server over third communication channel a transaction only in the event that the server network addresses are consonant.

Claims

exact text as granted — not AI-modified
1 - 32 . (canceled) 
     
     
         33 . A system providing enhanced security for device based transactions, the system comprising:
 a first server, a second server and a mobile device server, said mobile device server comprising a processor and associated with a memory;   a first device associated with a user, said first device in communication with said first server over a first communication channel, said first device arranged to request a transaction via said first server;   a second device associated with the user,   said mobile device server in communication with said second device over a second communication channel, said mobile device server in communication with said first server over a third communication channel,
 said memory associated with said mobile device server storing instructions which when executed by said mobile device server processor causes said mobile device server to:
 input a transaction authorization request from said first server; 
 authenticate said second device over said second communication channel; 
 authorize a transaction between the first device and the first server responsive to said second device authentication; 
 input a transaction authorization request from said second server, said second server in communication with one of the first and second devices associated with the user; and 
 authorize the input transaction authorization request from said second server responsive to the authorization of the transaction between the first device and the first server. 
 
   
     
     
         34 . The system of  claim 33 , wherein each of said first server and said second server are provider servers. 
     
     
         35 . The system of  claim 33 , wherein said stored instructions when executed by said mobile device server processor further cause said mobile device server to:
 authorize the input transaction authorization request from said second server responsive to a transactions authorization history between said first device associated with the user and at least one of said first server and said second server.   
     
     
         36 . The system of  claim 35 , wherein said transactions authorization history is stored on said memory associated with said mobile device server. 
     
     
         37 . The system of  claim 33 , further comprising a third server, and wherein said stored instructions when executed by said mobile device server processor further cause said mobile device server to:
 authorize the input transaction authorization request from said second server responsive to a transactions authorization history between said first device associated with the user and at least one of said first server, said second server and said third server.   
     
     
         38 . The system of  claim 33 , wherein said transactions authorization history is stored on said memory associated with said mobile device server. 
     
     
         39 . The system of  claim 33 , further comprising a third server, and wherein said stored instructions when executed by said mobile device server processor further cause said mobile device server to:
 authorize the input transaction authorization request from said second server responsive to a transactions authorization history between said first device associated with the user and at least one of said first server, said second server and said third server.   
     
     
         40 . The system of  claim 39 , wherein said transactions authorization history is stored on said memory associated with said mobile device server. 
     
     
         41 . The system of  claim 33 , further comprising a third server, wherein said stored instructions when executed by said mobile device server processor further cause said mobile device server to:
 accumulate history details of validations between any of said first device associated with the user and said second device associated with the user, and each of said first server, second server and said third server, said accumulated history thereby increasing a security value associated with the user; and   authorize at least one further transaction authorization request to one of said first server, said second server and said third server responsive to said increased security value and predetermined rules.   
     
     
         42 . The system of  claim 33 , wherein said first device and said second device are a single device. 
     
     
         43 . A computer implemented method of providing single sign on, the method comprising:
 providing a first server;   providing a second server;   providing a mobile device server;   said provided first server:
 receiving a first transaction request over a first communication channel from a first device associated with a user; and 
 transmitting a first transaction authorization request to said mobile device server responsive to said received transaction request of the first communication channel, 
   said provided second server:
 receiving a second transaction request from one of the first device associated with the user and a second device associated with the user; and 
 transmitting a second transaction authorization request to said mobile device server responsive to said received second transaction request, 
   said provided mobile device server:
 authenticating the second device associated with the user over a second communication channel responsive to the transmitted first transaction authorization request; 
 authorizing the first transaction authorization request to said provided first server responsive to said second device authentication; 
 authorizing the second transaction authorization request to said provided second server responsive to the authorization of the first transaction authorization request. 
   
     
     
         44 . The method of  claim 43 , wherein each of said provided first server and said provided second servers are provider servers. 
     
     
         45 . The method of  claim 43 , wherein said provided mobile device server further authorizes the second transaction responsive to a transactions authorization history associated with the user. 
     
     
         46 . The method of  claim 45 , wherein said transactions authorization history is stored on said provided mobile device server. 
     
     
         47 . The method of  claim 43 , wherein said provided first device and said provided second device are a single device. 
     
     
         48 . The method of  claim 43 , further comprising providing a third server, the method further comprising:
 accumulating history details of validations between any of said first device associated with the user and said second device associated with the user, and each of said provided first server, provided second server and said provided third server, said accumulated history thereby increasing a security value associated with the user; and   authorizing at least one further transaction authorization request to one of said first server, said second server and said third server responsive to said increased security value and predetermined rules.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.