SYSTEM AND METHOD FOR GENERATING A LOCATION SPECIFIC TOKEN

• US 20170221059A1
• Filed: 05/29/2015
• Published: 08/03/2017
• Est. Priority Date: 05/29/2014
• Status: Abandoned Application

• Current Assignee: Ranvir Sethi
• Original Assignee: Ranvir Sethi
• Inventors: SETHI, RANVIR
• Application Number:
  US15/309,249
• Publication Number:
  US 20170221059A1
• Time in Patent Office: Days
• CPC Class Codes: G06F 21/44 Program or device authentication
• CPC Class Codes: G06F 2221/2111 Location-sensitive, e.g. geographical location, GPS
• CPC Class Codes: G06Q 20/3224 Transactions dependent on location of M-devices
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules
• 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 63/107 wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals

Abstract

A server (108) for authenticating an interaction between a first user device (104) and a second user device (110) is provided. The server (108) includes a memory unit, a set of modules, a database (232), and a processor. The set of modules comprise a token request processing module (202), a token associating module (204), a token comparison module (210), a distance obtaining module (212) and an interaction processing module (214). The token request processing module (202) receives an input from a first user (102) comprising a location specific token with a location. The token associating module (204) associates the location specific token with the location. The distance obtaining module (212) obtains a distance between a location associated with the first user (102) and the second user (112). The interaction processing module processes an interaction between the first user (102) and the second user (112).

Claims

1. A server for obtaining a location specific token for authenticating an interaction between a first user device and a second user device, said server comprising:

(i) a memory unit that stores (a) a set of modules, and (b) a database; and

(ii) a processor which executes said set of modules, wherein said set of modules comprise;

(a) a token processing module, executed by said processor, that receives an input from said first user device comprising a request to associate said location specific token with a location;

(b) a token associating module, executed by said processor, that associates said location specific token with said location, wherein said location specific token is specific to said location characterized by a threshold distance or a threshold area;

(c) a token communicating module, executed by said processor, that communicates said location specific token

(i) to said first user device associated with a first user, wherein said location specific token is first obtained by said server before it is obtained by said first user device;

or

(ii) from said first user device associated with said first user, wherein said location specific token is first obtained by said first user device before it is obtained by said server, wherein said location specific token is communicated from said first user device to said second user device associated with said second user, and

(d) a token receiving module, executed by said processor, that receives said location specific token from said second user device;

(e) a token comparison module, executed by said processor, that compares data based on said location specific token which is associated by said server with said location specific token which is received by said server from said second user device for a match;

(f) a distance obtaining module, executed by said processor, that obtains a distance between a location associated with said location specific token of said first user device and a location associated with said location specific token of said second user device, wherein said location associated with said location specific token is a physical location or an assumed location of a user of a user device; and

(g) an interaction processing module, executed by said processor, that processes an interaction between said first user and said second user when

(i) said match is found between said location specific token which is associated by said server and said location specific token which is received by said server from said second user device,

(ii) said distance between said location associated with first user and said location associated with second user is within said threshold area or said threshold distance, wherein said first user or said second user is inside or outside of said location characterized by said threshold area or said threshold distance, or

(iii) said distance between said location associated with said location specific token of said first user device and said location associated with said location specific token of said second user device is within said threshold area or said threshold distance.

2. The server of claim 1, wherein said set of modules further comprise a token obtaining module that obtains identical tokens, wherein said location specific token is associated with said first user and said location, wherein said location is a physical location or an assumed location of said first user.

3. The server of claim 1, wherein said location associated with said first user is characterized by a first threshold outer area or distance and a first threshold inner area or distance, wherein said first threshold inner area or distance is within said first threshold outer area or distance, wherein said location specific token (a) is obtained for said first threshold inner area or distance, (b) is valid only within said first threshold inner area or distance, and (c) is deactivated upon said location specific token moves out of said first threshold inner area or distance, or said location associated with said location specific token gets changed to a location that is not inside said first threshold inner area or distance.

5. The server of claim 1, wherein said location specific token is a reusable token that is identical for a plurality of users and simultaneously used by said plurality of users from said plurality of locations.

7. The server of claim 1, wherein said set of modules further comprise a token deactivation module, executed by said processor, that deactivates said location specific token when

(a) said first user moves out of said first threshold inner area or distance for which said location specific token is associated;

(b) said interaction between said first user and said second user is completed;

(c) upon said first user indicating to deactivate said location specific token;

or (d) said location associated with said location specific token is changed to a location that is outside of said first threshold inner area.

12. The server of claim 1, wherein said interaction is a transaction between said first user and said second user, wherein said first user is a payer or payee and said second user is a payer or payee.

24. The server of claim 1, wherein said set of modules further comprise a security check module that performs an additional security check for said payer upon detection of breach of a threshold amount by a cumulative total or a number based on said cumulative total of said transaction starting from a previous additional security check.

25. The server of claim 1, wherein said set of modules further comprise a token verification module that verifies whether said location specific token associated with said payer or said payee exists in a database of location specific tokens, wherein said database of said location specific tokens is associated with said threshold distance or said threshold area characterized by said location associated with said payee device or said location associated with said payer device.

26. The server of claim 1, wherein said location specific token is valid up to a predefined threshold time beyond which said location specific token is deactivated.

4. (canceled)

6. (canceled)

8. (canceled)

9. (canceled)

10. (canceled)

11. (canceled)

13. (canceled)

14. (canceled)

15. (canceled)

16. (canceled)

17. (canceled)

18. (canceled)

19. (canceled)

20. (canceled)

21. (canceled)

22. (canceled)

23. (canceled)

27. (canceled)

28. (canceled)

29. (canceled)

30. (canceled)

31. (canceled)

32. (canceled)

33. (canceled)

34. One or more non-transitory computer readable storage mediums storing one or more sequences of instructions, which when executed by one or more processors, causes

(a) receiving an input from said first user device comprising a request to associate a location specific token with a location;

(b) associating said location specific token with said location, wherein said location specific token is specific to a location characterized by a threshold distance or a threshold area;

(c) communicating said location specific token (i) to said first user device associated with a first user, wherein said location specific token is first obtained by said server before it is obtained by said first user device;

or (ii) from said first user device associated with said first user, wherein said location specific token is first obtained by said first user device before it is obtained by said server, wherein said location specific token is communicated from said first user device to a second user device associated with a second user;

(d) receiving said location specific token from said second user device;

(e) comparing data based on said location specific token which is associated by said server with said location specific token which is received by said server from said second user device for a match;

(f) obtaining a distance between a location associated with said location specific token of said first user device and a location associated with said location specific token of said second user device, wherein said location associated with said location specific token is a physical location or an assumed location of a user of a user device; and

(g) processing an interaction between said first user and said second user when

(i) said match is found between said location specific token which is associated by said server and said location specific token which is received by said server from said second user device,

(ii) said distance between said location associated with said first user and said location associated with said second user is within said threshold area or said threshold distance, wherein said first user or said second user is inside or outside of said location characterized by said threshold area or said threshold distance, or

(iii) said distance between said location associated with said location specific token of said first user device and said location associated with said location specific token of said second user device is within said threshold area or said threshold distance.

35. A server for simultaneously obtaining a plurality of identical tokens for authenticating an interaction between a first user device associated with a first user and a second user device associated with a second user, wherein said first user and said second user are located anywhere with respect to each other and keeping identical tokens separated by a threshold distance, wherein location associated with a token is any location of the world including a location that is remote to user'"'"'s physical location, said server comprising:

(i) a memory unit that stores (a) a set of modules, and (b) a database; and

(ii) a processor which executes said set of modules, wherein said set of modules comprise;

(a) a token processing module, executed by said processor, that receives an input from said first user comprising a request to associate a location specific token with a first location characterized by (i) a first threshold inner area and (ii) a first threshold outer area, wherein said first threshold inner area is subset of first threshold outer area;

(b) a token uniqueness validating module, executed by said processor, that (i) compares said location specific token generated at said first threshold inner area with active tokens in said first threshold outer area or said first threshold inner area; and

(ii) validates a uniqueness of said location specific token within said first location, wherein said location specific token is simultaneously used for a second location that is located proximal or elsewhere with respect to said first location, wherein said second location is characterized by (i) a second threshold inner area and (ii) a second threshold outer area, wherein said second threshold inner area is subset of second threshold outer area;

(c) a token associating module, executed by said processor, that associates said location specific token with said first location by validating said uniqueness of said location specific token within said first location; and

simultaneously associates said location specific token also with said second location.

36. The server of claim 35, wherein said set of modules further comprise a token communicating module, executed by said processor, that communicates said location specific token (i) to said first user device associated with said first user, wherein said location specific token is first obtained by said server before it is obtained by said first user device;

or (ii) from said first user device associated with said first user, wherein said location specific token is first obtained by said first user device before it is obtained by said server, wherein said location specific token is communicated from said first user device to said second user device associated with said second user.

37. The server of claim 35, further comprising a token receiving module, that receives said location specific token from said second user device with an associated location within said first inner threshold area or said first outer threshold area.

38. The server of claim 35, further comprising a token comparison module that matches data based on said location specific token associated with said first user device and said location specific token associated with said second user device by analysing if a location associated with both said location specific token is within said first inner threshold area or said first outer threshold area.

39. The server of claim 35, wherein said set of modules further comprise:

(i) a distance obtaining module, executed by said processor, that obtains a distance between a location associated with said location specific token of said first user device and a location associated with said location specific token of said second user device, wherein said location associated with said location specific token is a physical location or an assumed location of a user of a user device; and

(ii) an interaction processing module, executed by said processor, that processes an interaction between said first user and said second user when

(a) said match is found between said location specific token which is associated by said server and said location specific token which is received by said server, and

(b) said distance between said location associated with said location specific token of said first user device and said location associated with said location specific token of said second user device is within a predefined threshold area or a predefined threshold distance, wherein said first user or said second user is inside or outside of said location characterized by said predefined threshold area or said predefined threshold distance, and a location associated with said first user and said second user is a physical location of said user or an assumed location of said user, wherein a location associated with (i) said location specific token, (ii) said first user device, or (iii) said second user device is a user'"'"'s physical location or located remotely to said user'"'"'s physical location.

40. The server of claim of 35, wherein said location specific token is also used for an interaction between a third user and a fourth user in said second location by utilizing said second threshold inner area and said second threshold outer area.

42. The server of claim 35, wherein said set of modules further comprise an approval receiving module that receives an approval for said transaction from said payer device.

43. The server of claim 35, wherein said set of modules further comprise an approval receiving module that receives an approval for said transaction or interaction from said first user device or said second user device.

44. The server of claim 43, wherein said set of modules further comprise a transaction processing module that is configured to process said transaction between said payer and said payee upon

(i) successfully receiving said approval;

and

(ii) a match is found between said location specific token associated with said payer device and said location specific token associated with said payee device.

45. The server of claim 35, wherein said set of modules further comprise a token verification module that verifies whether said location specific token associated with said payer or said payee exists in a database of location specific tokens, wherein said database of said location specific tokens is associated with a threshold distance or a threshold area characterized by a location associated with a payer device or a location associated with a payee device.

41. (canceled)

46. (canceled)