METHOD AND SYSTEM FOR STORING, RETRIEVING, AND MANAGING DATA FOR TAGS

• US 20080224857A1
• Filed: 05/23/2008
• Published: 09/18/2008
• Est. Priority Date: 10/30/2003
• Status: Active Grant

• Current Assignee: Motedata Corporation
• Original Assignee: Motedata Incorporated
• Inventors: Lupoli, Peter, Kesan, Jay
• Granted Patent: US 8,558,668 B2
• Time in Patent Office: Days
• US Class Current: 340/539.23
• CPC Class Codes: G06F 16/90 Details of database functions independent of the retrieved data types
• CPC Class Codes: G06F 16/903 Querying for retrieval from the web G06F16/953
• CPC Class Codes: G06K 7/10257 arrangements for protecting the interrogation against piracy attacks computer security in general G06F21/00; jamming of communication, countermeasures H04K3/00; secret communication H04K1/00
• CPC Class Codes: G06K 7/10366 the interrogation device being adapted for miscellaneous applications
• CPC Class Codes: G06Q 10/08 Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
• CPC Class Codes: G08B 13/2462 Asset location systems combined with EAS inventory, tracking, logistic G06Q10/00; entrance control systems G07C9/00
• CPC Class Codes: G08B 21/22 responsive to presence or absence of persons

Abstract

This invention relates generally to a method and system for storing, retrieving, and managing data for tags that are associated in some manner to any type of object. More particularly, the present invention writes data to these tags, reads data from these tags, and manages data that is written to and/or read from these tags.

Claims

1. A method for checking the proximity of one or more tags comprising:

receiving a message of a first type;

reading an identifier of a tag that sent said messages from said message; and

incrementing a number of encounters for said read tag identifiers.

2. A method for checking the proximity of one or more tags as in claim 1 further comprising the step of storing said number of encounters in a data structure of a first type.

3. A method for checking the proximity of one or more tags as in claim 2 further comprising the step of creating an entry for said retrieved tag identifier in said data structure if said retrieved tag identifier is not already within said data structure of said first type.

4. A method for checking the proximity of one or more tags as in claim 2 wherein said storing step is performed only if a signature of said read tag identifier in said message of said first type verifies.

5. A method for checking the proximity of one or more tags as in claim 2 wherein said incrementing step is performed only if a time in said message of said first type is within a predetermined time period.

6. A method for checking the proximity of one or more tags as in claim 5 wherein said predetermined time period is not more than one minute from a current time.

7. A method for checking the proximity of one or more tags as in claim 2 further comprising the step of transmitting said data structure of said first type upon receiving a message of a second type.

8. A method for checking the proximity of one or more tags as in claim 7 wherein said transmitting step is performed only if a signature in said message of said second type verifies.

9. A method for checking the proximity of one or more tags as in claim 7 further comprising the step of encrypting said data structure of said first type.

10. A method for checking the proximity of one or more tags as in claim 1 further comprising:

receiving a timer interrupt;

creating a message of said first type; and

sending said message of said first type.

11. A method for checking the proximity of one or more tags as in claim 1 wherein said message of said first type comprises one or more of the following:

a signature of a tag that sent said message, an identifier of a tag that sent said message, and a current time.

12. A method for generating an alarm when one or more tags fall outside of a proximity comprising:

receiving a message of a first type;

reading an identifier of a tag that sent said message from said message; and

resetting an alarm counter for said read identifier.

13. A method for generating an alarm as in claim 12 wherein said resetting step is performed only if a signature of said read tag identifier in said message of said first type verifies.

14. A method for generating an alarm as in claim 12 wherein said resetting step is performed only if a time in said message of said first type is within a predetermined time period.

15. A method for generating an alarm as in claim 14 wherein said predetermined time period is not more than one minute from a current time.

16. A method for generating an alarm as in claim 12 further comprising:

receiving a timer interrupt;

incrementing an alarm counter; and

sounding an alarm if said alarm counter is greater than a predetermined limit.

17. A method for generating an alarm as in claim 16 wherein said incrementing step and said sounding step are performed only when said tag receiving said interrupt is enabled.

18. A method for generating an alarm when one or more tags fall within a proximity comprising:

receiving a message of a first type;

reading an identifier of a tag that sent said message of said first type; and

sounding an alarm if said read identifier is in a list of sensitive tags.

19. A method for generating an alarm as in claim 18 wherein said sounding an alarm step is performed only if a signature in said message of said first type verifies.

20. A method for generating an alarm as in claim 18 wherein said sounding an alarm step is performed only if a time in said message of said first type is within a predetermined period.

21. A method for generating an alarm as in claim 20 wherein said predetermined period is not more than one minute from a current time.

22. A method for generating an alarm as in claim 18 further comprising:

receiving a message of a second type;

reading a tag identifier from said message of said second type; and

adding said tag identifier to said list of sensitive tags.

23. A method for generating an alarm as in claim 22 wherein said adding step is performed only if a signature in said message of said second type verifies.

24. A method for generating an alarm as in claim 18 further comprising:

receiving a message of a third type;

reading a tag identifier from said message of said third type; and

removing said tag identifier from said list of sensitive tags.

25. A method for generating an alarm as in claim 24 wherein said removing step is performed only if a signature in said message of said third type verifies.