IP Library Granted Patent US 8,924,412
Granted Patent B2
US 8,924,412 · App. 11/614,947 · Granted Dec 30, 2014

Rules driven pan ID metadata routing system and network

Inventors: Geoffrey B. Rhoads (West Linn, OR); Tony F. Rodriguez (Portland, OR); Kenneth L. Levy (Stevenson, WA)
Assignee: Digimarc Corporation
G06F17/30289G06Q10/10H04N21/25891H04N21/4722G06Q10/06H04N21/252H04N21/84H04N21/854H04L65/4084H04N21/23892H04L67/22G06F17/3002G06F17/30038H04N21/8586H04N21/435G06F21/10H04L67/327G06F17/30G06Q30/02H04N21/235G06Q30/00
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,924,412
App. No.
11/614,947
Granted
Dec 30, 2014
Kind
B2
Abstract

Content objects are associated with metadata via content identifiers. In response to a user's query for metadata for a piece of content, the content identifier is derived from the content object and used to determine metadata responses to the query. Rules are applied to govern the metadata responses returned in response to the query. Traffic monitoring is performed to track usage of metadata.

Claims (45)

1. A routing system for receiving a request for metadata for a content object and directing a metadata response, the system comprising:

one or more programmed computers including:

an ID resolver programmed to receive a content identifier extracted from the content object, and programmed to determine associated metadata responses and a rule governing the metadata responses;

a rules processor programmed to execute the rule to determine a subset of the metadata responses; the routing system programmed to initiate the subset of metadata responses in response to the request and execution of the rule.

2. The routing system of claim 1 wherein the rule is dependent on user preferences of a user making the request.

3. The routing system of claim 2 wherein user preferences are derived from a history of metadata requests tracked by the routing system.

4. The routing system of claim 1 including a traffic monitor programmed to track usage data about requests for metadata from users along with user information.

5. The routing system of claim 4 including a metadata repository, wherein the usage data is stored in the metadata repository and linked to content objects using content identifiers in the content objects.

6. The routing system of claim 4 wherein the traffic monitor is programmed to analyze the usage data and programmed to identify an affinity group for a first content object.

7. The routing system of claim 6 wherein the metadata repository includes information about the affinity group identified by the traffic monitor, and the information about the affinity groups is linked to the first content object.

8. The routing system of claim 7 wherein the metadata repository comprises one or more electronic storage devices in communication with one or more computers programmed to allow users in an affinity group to add metadata for the first content object collaboratively.

9. A routing system for receiving a request for metadata for a content object and directing a metadata response, the system comprising:

one or more programmed computers including:

an ID resolver programmed to receive a content identifier extracted from the content object, and programmed to determine associated metadata responses; and

a traffic monitor programmed to track usage data about requests for metadata from users along with user information.

10. The routing system of claim 9 including a metadata repository, wherein the usage data is stored in the metadata repository and linked to content objects using content identifiers in the content objects.

11. The routing system of claim 10 wherein the traffic monitor is programmed to analyze the usage data and programmed to identify an affinity group for a first content object.

12. The routing system of claim 11 wherein the metadata repository includes information about the affinity group identified by the traffic monitor, and the information about the affinity groups is linked to the first content object.

13. The routing system of claim 12 wherein the metadata repository comprises one or more electronic storage devices in communication with one or more computers programmed to allow users in an affinity group to add metadata for the first content object collaboratively.

14. A routing method for receiving a request for metadata for a content object and directing a metadata response, the method comprising:

executing program instructions on one or more computers to perform the acts of:

receiving a content identifier extracted from the content object;

determining associated metadata responses and a rule governing the metadata responses;

executing the rule to determine a subset of the metadata responses; and

initiating the subset of metadata responses in response to the request and execution of the rule.

15. The method of claim 14 wherein initiating includes returning one or more URLs to a metadata source that provides the metadata response to a device from which the request originated.

16. The method of claim 14 wherein initiating includes forwarding the request to one or more metadata sources that provide the metadata response, the metadata sources identified by corresponding URLs.

17. A routing method for receiving a request for metadata for a content object and directing a metadata response, the method comprising:

executing program instructions on one or more computers to perform the acts of:

receiving a content identifier extracted from the content object;

determining associated metadata responses; and

tracking usage data about requests for metadata from users along with user information.

18. The routing method of claim 17 including storing the usage data in a metadata repository and linking the usage data to content objects using content identifiers in the content objects.

19. The routing method of claim 18 including analyzing the usage data to identify an affinity group for a first content object.

20. The routing method of claim 19 wherein the metadata repository includes information about the affinity group identified by analyzing the usage data, and the information about the affinity groups is linked to the first content object.

21. The routing method of claim 20 including allowing users in an affinity group to add metadata for the first content object collaboratively to the metadata repository.

22. A method for providing metadata for a content object, the method comprising:

executing program instructions on one or more computers to perform the acts of:

receiving a metadata request from a user, the metadata request being derived in part from a content object from which a content identifier is extracted, and the metadata request including metadata preferences of the user;

using the content identifier to determine a set of metadata for the content object, including determining the set of metadata linked to the content object by the content identifier in a database, the database maintaining links between the content identifier and disparate sources of metadata; and

applying the metadata preferences of the user to the set of metadata to produce a metadata response for the user.

23. The method of claim 22 wherein the content identifier is derived from perceptible attributes of an electronic content signal representing the content object.

24. The method of claim 22 wherein one of the disparate sources of metadata includes user generated metadata from a group of users; and wherein the database manages links between the content identifier and the user generated metadata such that the user generated metadata remains linked to the content object as the object is distributed across devices in a network.

25. The method of claim 22 wherein the metadata request is dependent on metadata usage information, and including: tracking requests for metadata to identify metadata usage information; and tailoring a response to the metadata request based on the metadata usage information.

26. The method of claim 25 wherein the tracking requests for metadata includes tracking requests for user generated metadata, wherein the database manages links between the content identifier and the user generated metadata such that the user generated metadata remains linked to the content object as the object is distributed across devices in a network.

Assignments (5)
ARTICLES OF CONVERSION Recorded Jun 19, 2026
From: DIGIMARC CORPORATION
To: DIGIMARC LLC
Reel/Frame 075863/0211 →
ARTICLES OF AMENDMENT OFTHE ARTICLES OF ORGANIZATION OF DIGIMARC LLC Recorded Jun 19, 2026
From: DIGIMARC LLC
To: DMRC LLC
Reel/Frame 075863/0266 →
MERGER Recorded May 12, 2010
From: DIGIMARC CORPORATION (A DELAWARE CORPORATION)
To: DIGIMARC CORPORATION (AN OREGON CORPORATION)
Reel/Frame 024369/0582 →
CONFIRMATION OF TRANSFER OF UNITED STATES PATENT RIGHTS Recorded Nov 5, 2008
From: L-1 SECURE CREDENTIALING, INC. (FORMERLY KNOWN AS DIGIMARC CORPORATION)
To: DIGIMARC CORPORATION (FORMERLY DMRC CORPORATION)
Reel/Frame 021785/0796 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 21, 2007
From: RHOADS, GEOFFREY B.; RODRIGUEZ, TONY F.; LEVY, KENNETH L.
To: DIGIMARC CORPORATION
Reel/Frame 019044/0422 →
Continuity (3)
Provisional Application 60753257 · Dec 21, 2005
Provisional Application 60747408 · May 16, 2006
Related Publication 20070208711A1 · Sep 6, 2007