IP Library › Granted Patent US 8,558,668
Granted Patent B2
US 8,558,668 · App. 12/125,998 · Granted Oct 15, 2013

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

Inventors: Peter Lupoli (Santa Barbara, CA); Jay Kesan (Champaign, IL)
Assignee: Motedata Inc.
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,558,668
App. No.
12/125,998
Granted
Oct 15, 2013
Kind
B2
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 (32)

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.

Assignments (8)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 25, 2023
From: MOTEDATA LLC
To: MOTEDATA INC.
Reel/Frame 064705/0911 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 25, 2023
From: MOTEDATA INC.
To: MOTEDATA CORPORATION
Reel/Frame 064706/0623 →
CORRECTIVE ASSIGNMENT TO CORRECT THE TYPOGRAPHIC ERROR IN THE PROVISIONAL APPLICATION NUMBER ON THE ASSIGNMENT PREVIOUSLY RECORDED ON REEL 032907 FRAME 0412. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Jun 29, 2023
From: LUPOLI, PETER; KESAN, JAY
To: MOTEDATA INC.
Reel/Frame 064162/0001 →
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE'S NAME PREVIOUSLY RECORDED ON REEL 051562 FRAME 0612. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Feb 24, 2020
From: MOTEDATA INC.
To: MOTEDATA LLC
Reel/Frame 052351/0070 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 21, 2020
From: MOTEDATA INC.
To: EMPIRE IP LLC
Reel/Frame 051562/0612 →
CHANGE OF ADDRESS Recorded Nov 17, 2019
From: MOTEDATA INC.
To: MOTEDATA INC.
Reel/Frame 051041/0706 →
CHANGE OF ADDRESS Recorded Nov 3, 2019
From: MOTEDATA INC.
To: MOTEDATA INC.
Reel/Frame 050916/0406 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 15, 2014
From: LUPOLI, PETER; KESAN, JAY
To: MOTEDATA INC.
Reel/Frame 032907/0412 →
Continuity (3)
Division 10952789 · Sep 30, 2004
Provisional Application 60515449 · Oct 30, 2003
Related Publication 20080224857A1 · Sep 18, 2008