Rules Driven Pan ID Metadata Routing System and Network

• US 20070208711A1
• Filed: 12/21/2006
• Published: 09/06/2007
• Est. Priority Date: 12/21/2005
• Status: Active Grant

• Current Assignee: Digimarc Corporation
• Original Assignee: Digimarc Corporation
• Inventors: Rhoads, Geoffrey, Rodriguez, Tony, Levy, Kenneth
• Granted Patent: US 8,924,412 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06F 16/211 Schema design and management
• CPC Class Codes: G06F 16/40 of multimedia data, e.g. slideshows comprising image and additional audio data retrieval of still image data G06F16/50; retrieval of audio data G06F16/60; retrieval of video data G06F16/70
• CPC Class Codes: G06F 16/41 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/433 using audio data
• CPC Class Codes: G06F 16/434 using image data, e.g. images, photos, pictures taken by a user
• CPC Class Codes: G06F 16/48 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G06F 16/61 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/68 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G06F 16/683 using metadata automatically derived from the content
• CPC Class Codes: G06F 16/80 of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML content-based retrieval of web data G06F16/95
• CPC Class Codes: G06F 16/90335 Query processing
• CPC Class Codes: G06F 16/9038 Presentation of query results
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 16/9538 Presentation of query results
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 30/00 : Commerce
• CPC Class Codes: G06Q 30/02 : Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: H04L 65/612 : for unicast
• CPC Class Codes: H04L 67/10 : in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/535 : Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 67/63 : Routing a service request depending on the request content or context
• CPC Class Codes: H04N 1/32283 : Hashing
• CPC Class Codes: H04N 21/218 : Source of audio or video content , e.g. local disk arrays details of retrieval in video databases G06F16/739
• CPC Class Codes: H04N 21/2343 : involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements video transcoding H04N19/40; media packet handling at the source H04L65/762
• CPC Class Codes: H04N 21/235 : Processing of additional data, e.g. scrambling of additional data or processing content descriptors
• CPC Class Codes: H04N 21/2355 : involving reformatting operations of additional data, e.g. HTML pages optimising the visualization of content for information retrieval from the Internet G06F16/9577; tracking of instant messages H04L51/234; media packet handling at the source H04L65/762
• CPC Class Codes: H04N 21/23892 : involving embedding information at multiplex stream level, e.g. embedding a watermark at packet level
• CPC Class Codes: H04N 21/252 : Processing of multiple end-users' preferences to derive collaborative data
• CPC Class Codes: H04N 21/25891 : being end-user preferences retrieval of video data in a video database based on user preferences G06F16/739; arrangements for recognizing users' preferences H04H60/46; user profiles in network data switching protocols H04L67/306; processing of user preferences or user profiles in wireless networks H04W8/18
• CPC Class Codes: H04N 21/26258 : for generating a list of items to be played back in a given order, e.g. playlist, or scheduling item distribution according to such list retrieval of multimedia data based on playlists G06F16/40
• CPC Class Codes: H04N 21/41407 : embedded in a portable device, e.g. video client on a mobile phone, PDA, laptop constructional details of equipment or arrangements specially adapted for portable computer application G06F1/1626; arrangements specially adapted for mobile receivers in broadcast systems H04H20/57
• CPC Class Codes: H04N 21/42203 : sound input device, e.g. microphone
• CPC Class Codes: H04N 21/435 : Processing of additional data, e.g. decrypting of additional data, reconstructing software from modules extracted from the transport stream
• CPC Class Codes: H04N 21/4415 : using biometric characteristics of the user, e.g. by voice recognition or fingerprint scanning cryptography using biological data H04L9/3231; authentication in networks using biometric H04L63/0861
• CPC Class Codes: H04N 21/4722 : for requesting additional data associated with the content
• CPC Class Codes: H04N 21/84 : Generation or processing of descriptive data, e.g. content descriptors systems specially adapted for using meta-information in broadcast systems H04H60/73
• CPC Class Codes: H04N 21/854 : Content authoring
• CPC Class Codes: H04N 21/8586 : by using a URL processing chained hypermedia data for information retrieval G06F16/94; information retrieval from the Internet by using URLs G06F16/955; URL in broadcast information H04H20/93; Web-based protocols H04L67/02

Abstract

A method of associating a content object with metadata uses a combination of a content identifier and a bounding identifier to enable handling of disparate sets of content identifiers for content objects with potentially conflicting content identifiers. The method receives a content identifier for a content object from among a set of content identifiers. It provides a unique bounding identifier for the set of content identifiers. This unique bounding identifier is used in combination with the content identifier to form a globally unique identifier for the content object. This globally unique identifier is associated with a metadata source, which enables routing of a user to the metadata source. Another novel method addresses content objects with two or more content identifiers, potentially referencing different metadata sources. This method registers different globally unique identifiers for a content object. These globally unique identifiers each comprise a content identifier provided with the content object and a bounding identifier identifying a set of content identifiers of which the content identifier is a member. For each of the globally unique identifiers, information is maintained about a metadata source. The method receives a first content identifier for the content object, and uses a bounding identifier associated with the set of the first content identifier to determine the globally unique identifier for the first content identifier. The user is routed to the metadata source associated with globally unique identifier. This document describes a novel system that enables multiple identity providers (ID Providers) to register and use the system. The ID Provider registers with a metadata directory system, receives a unique bounding identifier, and uses this bounding ID (e.g., an ID provider ID) with subsequent interactions with the metadata directory system. Separately, metadata source providers register metadata sources with the metadata directory system. This enables many different participants to associate content objects with metadata sources using one or more identify providers. Examples of metadata source providers include content providers, like content owners or retailers that have the flexibility of working with different ID providers to associate content objects with metadata. Both content providers and ID providers can register and use the system. The metadata source is the system or device that provides the metadata, like a web site. The directory system uses an identifier for the metadata source, which enables it to maintain an association between a content object and its corresponding metadata source. For example, in some embodiments, a URL serves to identify the location of the source. The Content Metadata Directory Services (CMDS) is a global trusted directory service that connects consumers of identified content to content-provider authorized and managed metadata databases and other digital resources. It includes mostly links to metadata, forms globally unique IDs based upon overlapping content identifiers and unique bounding identifiers, enables multiple content identifiers within a content object, and enables multiple content identity technology providers, even when they are using different technology.

Claims

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

an ID resolver for receiving a content identifier extracted from the content object, and determining associated metadata responses and a rule governing the metadata responses;

a rules processor for executing the rule to determine a subset of the metadata responses;

the routing system operable 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 for tracking 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 operable to analyze the usage data and 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 is operable 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:

an ID resolver for receiving a content identifier extracted from the content object, and determining associated metadata responses; and

a traffic monitor for tracking 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 operable to analyze the usage data and 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 is operable 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:

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 system comprising:

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 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 and 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 the traffic monitor, 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:

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.