Method and system for storing, retrieving, and managing data for tags

• US 8,558,668 B2
• Filed: 05/23/2008
• Issued: 10/15/2013
• Est. Priority Date: 10/30/2003
• Status: Active Grant

• Current Assignee: Motedata Corporation
• Original Assignee: Motedata Incorporated
• Inventors: Lupoli, Peter, Kesan, Jay
• Primary Examiner(s): SYED, NABIL H
• Application Number:
  US12/125,998
• Publication Number:
  US 20080224857A1
• Time in Patent Office: 1,971 Days
• Field of Search: 340/10.1, 340/10.3, 340/539.23, 340/539.15, 340/516, 340/572.1, 340/10.2, 340/10.4, 340/10.5, 340/539.13, 340/5.61, 340/686.6, 340/539.11, 340/539.1, 340/571, 340/568.1
• US Class Current: 340/10.1
• 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 first message on a tag that is of a first type, that is broadcast at a regular time interval from a partner tag using a partner timer interrupt on the partner tag, and that includes a partner identifier of the partner tag that is used to distinguish the partner tag from other tags;

reading the partner identifier of the partner tag from said first message on the tag;

incrementing a number of tag encounters on the tag for said read partner identifier;

sounding an alarm on the tag if said read partner identifier is in a list of sensitive tags on the tag; and

broadcasting from the tag a second message that includes an identifier of the tag at the same regular time interval using a timer interrupt on the tag that the partner tag receives, uses to increment a number of partner tag encounters on the partner tag, and uses to sound an alarm on the partner tag if the identifier is in a partner list of sensitive tags on the partner tag, wherein the identifier is used to distinguish the tag from other tags.

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

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 read partner identifier in said data structure if said read partner identifier is not already within said tag 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 of storing said number of tag encounters on the tag in a tag data structure of a first type is performed only if a signature of said read partner identifier in said first 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 first 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 tag 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 tag 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 the second message on the partner tag;

reading the identifier of the tag from said second message on the partner tag; and

incrementing a number of partner tag encounters on the partner tag for said read identifier.

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

a signature of ft the partner tag that sent said first message, an partner identifier of the partner tag that sent said first message, and a current time.

12. A method for checking the proximity of one or more tags as in claim 1 wherein said sounding an alarm step is performed only if a signature in said first message of said first type verifies.

13. A method for checking the proximity of one or more tags as in claim 1 wherein said sounding an alarm step is performed only if a time in said first message of said first type is within a predetermined period.

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

15. A method for checking the proximity of one or more tags as in claim 1 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.

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

17. A method for checking the proximity of one or more tags as in claim 1 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.

18. A method for checking the proximity of one or more tags as in claim 17 wherein said removing step is performed only if a signature in said message of said third type verifies.