JP6335145B2 - Method and apparatus for correlating media metadata - Google Patents

Description

  Embodiments of the present invention generally relate to a digital video recorder (DVR). Embodiments of the present invention more specifically relate to techniques for correlating media metadata collected from various sources.

  Although the techniques described in this section can be pursued, they are not necessarily approaches that have been previously conceived or pursued. Accordingly, unless otherwise indicated herein, the techniques described in this section are not necessarily prior art to the claims of this application and are not admitted to be prior art by inclusion in this section.

  Sophisticated modern DVRs can schedule the recording of programs that will be broadcast on television sometime in the future. If a DVR user is interested in recording all episodes of a television series, the DVR user can instruct his DVR to obtain a “season pass” for that series. In response to such an instruction, the DVR automatically determines from the electronic program guide (EPG) data the time at which episodes of that series are scheduled to be broadcast in the future. Normally, whenever an episode of a selected series is about to be broadcast, the DVR automatically tunes the channel to the channel on which the episode will be broadcast and records the episode on the DVR's hard disk drive. As long as the recorded episode remains on the DVR hard disk drive, the DVR user can instruct the DVR to play the episode on the user's television. Conveniently, this allows DVR users to watch programs that the user is interested in at times other than the broadcast time of the program. A DVR user does not even need to know in advance the exact time that the program is scheduled to be broadcast.

  As used herein, a “program” is any visible and / or audible content presented via a television display and / or speakers. For example, a program may be an episode in a series of episodes, a movie, a sporting event, or news, but this is not an exclusive list of “programs”. When a digital video recorder (DVR) schedules a program for future recording, the DVR attempts to add the program to a “to do” list that the DVR maintains in its own storage. Whenever a program on the DVR “to do” list is broadcast, the DVR automatically records the program.

  Some DVRs allow DVR users to search for specific programs that the DVR user may be interested in. For example, in response to a search request from a DVR user, the DVR may indicate to the DVR user a user interface that allows the DVR user to enter criteria that a program that the DVR user is interested in should satisfy. The user interface may include different fields that the user can enter for different types of criteria that the program should be satisfied with. For example, the user interface may include a “title” field, one or more “actors” fields, a “category” and / or “genre” field, a “year” field, a “ratings” field, and so on. After receiving the criteria specified by the user via such a user interface, the DVR retrieves the program metadata obtained from the EPG data provider. Typically, the program metadata specified by the EPG indicates, for each program, the type of information (for example, title, actor, category, genre, year, rating, etc.) regarding the criteria entered by the user. Based on the program metadata provided by the EPG, the DVR determines a set of programs scheduled to be broadcast that are associated with the program metadata that meets the criteria specified by the user. DVR indicates a list of programs scheduled to be broadcast included in the set to the DVR user.

  For example, if a DVR user enters the phrase “Christopher” in the “Actor” field of the user interface, but leaves the “Title” field in the user interface blank, the DVR will be named “Christopher” as the actor (first The metadata provided by the EPG may be searched for all programs with any one of them (name, last name, middle name). In the metadata provided by the EPG, different types of information are found in different metadata fields. The metadata provided by the EPG for a particular program may have multiple fields tagged with an “actor” identifier. A field tagged with an “actor” identifier is considered an “actor” field. Each such actor field can include the names of actors appearing in the program. The DVR may retrieve EPG data for upcoming broadcast programs associated with metadata that includes an actor field that includes the phrase “Christopher”. After compiling such a list of programs and removing duplicate entries from the list, the DVR presents the list of programs to the DVR user. The DVR user can instruct the DVR to schedule recording of programs selected from the list as preferred by the DVR user.

  Significantly, if a DVR user specifies “Christopher” as an actor rather than as a title, the DVR will not attempt to search for “Christopher” in the title field. This is because doing so will likely lead to search results that DVR users are not interested in (in many programs that include “Christopher” in the title, any actor named “Christopher” May not star.) Therefore, in order to perform an accurate search that is likely to lead to the results that the DVR user is most interested in, the metadata provided by the EPG and searched by the DVR can be of different types (eg, “actor” metadata, “title” metadata). It is useful for DVR to include information classified as data).

  Metadata obtained from EPG data providers typically includes information about programs that are scheduled to be broadcast on various channels in the near future. However, a DVR can also obtain and show programs that are not scheduled to be broadcast on any particular channel at any particular time (eg, by radio waves or cable). Even if the program content is not scheduled to be broadcast on any channel in the near future (or to date), a DVR will give the DVR user the program content at any time preferred by the DVR user. It can be downloaded and shown (eg, via a data network such as the Internet). Program content that DVR users can request and view at any time, regardless of whether the content is scheduled to be broadcast on the channel, is referred to as “video on demand” (VOD) content. Unlike normally broadcast content, VOD content is typically presented to or provided to a DVR user only when the DVR user or DVR actually requests the VOD content. Using the same tuner hardware that DVR uses to get or receive content that is broadcast over channels in an older way, DVR may get or receive VOD content over a cable (but You don't have to.) Thus, DVR may obtain or receive VOD and non-VOD content, either through the same interface or through different interfaces, even though VOD content and non-VOD content may be available through different delivery mechanisms. Can do.

  Typically, VOD content is stored in digital form on a server accessible to the Internet maintained by a VOD service provider. There may be many different VOD service providers, each having its own set of servers, each having a different set of VOD content stored on its own set of servers. A particular DVR may be able to obtain VOD content from multiple different VOD service providers. In order to inform DVRs and DVR users what VOD content a particular VOD service provider will provide, the particular VOD service provider will download VOD metadata that can be downloaded onto the server of the particular VOD service provider. May be stored. The VOD metadata may indicate various types of information regarding VOD content that is accessible from a particular VOD service provider's server.

  A given DVR typically only obtains program metadata from a single well-known and widely used EPG data provider. Thus, the program metadata that the DVR obtains from the EPG data provider usually follows the format expected by the DVR, regardless of the specific program to which the program metadata belongs. Typically, the metadata provided by an EPG for a program includes a specific set of fields (eg, title, actor, category, genre, year, rating, etc.) and thus the EPG for each other program. The metadata provided by will also include a particular set of the fields (although the contents of those fields will naturally vary from program to program). In other words, the “structure” of the metadata provided by the EPG for each program will typically be uniform from program to program. Due to this structural uniformity of the metadata provided by the EPG, the DVR can more accurately perform user-initiated program content searches. Search results may be more inaccurate if the metadata provided by the EPG was not structurally uniform. Referring to the above example, if the metadata associated with the various programs does not include individual “title” and “actor” fields, the DVR will search for a program that matches the criteria specified by the user. It would be impossible to distinguish between a program that includes “Christopher” as an actor and a program that includes “Christopher” in the title.

As mentioned above, the DVR may be able to obtain VOD content from various VOD content providers. Often the program metadata provided by these VOD content providers will not have the same structure as the metadata provided by the EPG. That is, VOD content providers often feel little or no willingness to adapt their program metadata structure to someone else's program metadata structure. Often, program metadata provided by one VOD content provider will not have the same structure as program metadata provided by other VOD content providers. In addition, the VOD metadata includes information such as titles, actors, and genres (for naming several types of information), eg information is specifically tagged as titles, actors or genres in VOD metadata There may often be no guarantees attached—the “type” of the information item in the VOD metadata (eg, whether the information item is a title or an actor) can be determined solely from the VOD metadata. Often difficult or impossible. In the same way that a DVR can search for content that is normally broadcast, the DVR users should be able to search for VOD content, but the structural in the metadata provided by the VOD Such discrepancies often exist as obstacles in DVR methods,
Without this obstacle, DVR users should be able to search for VOD content in this way.
For example, the present invention provides the following items.
(Item 1)
A method for correlating media metadata from various sources,
The first metadata obtained from the sender and the second metadata obtained from another sender are
At least a part of the first metadata is similar to at least a part of the second metadata.
By determining that they are similar or identical,
Determining whether to link, wherein the structure of the first metadata is the second metadata.
Steps that are different from the structure of the data,
Determines that information is included in both the first metadata and the second metadata
The first metadata indicates that the information item is of a particular type.
And the second metadata does not indicate that the information item is of the specific type
, Steps and
Updating the second metadata based at least in part on the first metadata
And indicating that the information item of the second metadata is the specific type;
Based on at least in part the updated second metadata, the displayed multi
A set of multimedia content to be identified in the list of media content information
Determining at least one of the set of multimedia content
Pieces of multimedia content are available from the source and the set of malware
At least one other multimedia content of the multimedia content
Available from the source of the steps and
A method comprising:
(Item 2)
The source is an electronic program guide, and the second metadata is video on demand.
Billing related to content available from VOD content providers
Item 2. The method according to Item 1.
(Item 3)
The first metadata is a first video on demand (VOD) content provider
And the second metadata is associated with content available from
Available from a second VOD content provider different from other VOD content providers
Item 2. The method according to Item 1, wherein the method is related to content that is a function.
(Item 4)
The method is performed by an apparatus that is a digital video recorder (DVR).
Item 2. The method according to Item 1.
(Item 5)
The specific type is at least one of title, actor, and genre
Item 2. The method according to Item 1.
(Item 6)
Receiving user input defining one or more criteria, the one or more criteria;
A step wherein a particular criterion of the quasi indicates one or more types;
Determining a result of a set of programs satisfying the criteria, the result of the set of programs
Is determined by searching for candidate items of information, and the candidate items of information are the one or more items.
The result of the program set is shown to be one of the above types.
Included in the set of programs as specified in a list of program information; and
The method according to item 1, further comprising:
(Item 7)
The candidate item of information that is indicated to be a type of the one or more types is
7. The method of item 6, comprising the item of information in the second metadata.
(Item 8)
Determining a related program, the metadata relating to the related program.
Is an item of information that is also included in the metadata associated with the program in the result of the program set.
Including steps,
The method according to item 6, further comprising:
(Item 9)
In place of the digital video recorder (DVR), the method is (a) external to the DVR
(B) Executed by a server that communicates with the DVR over a network, item 1
The method described in 1.
(Item 10)
The second metadata relates to content that is available from a particular source;
The method comprises
The first metadata and the second metadata are related to the same content.
(A) related to the same content, and (b) the first metadata.
(C) one or more that is not specified in the second metadata.
Determining the above details;
In response to determining the one or more details, the one or more in a third metadata
Memorizing the details of
Store the association between the third metadata and the specific source on a persistent storage
And steps to
The method according to item 1, further comprising:
(Item 11)
The content of the second metadata scheduled to be broadcast on a specific channel at a specific time.
Content that can be obtained by the DVR at any time.
Item 2. The method according to Item 1, which is related to
(Item 12)
(A) Non-VO based at least in part on past user behavior regarding VOD programs
Schedule recordings of D programs, or (b) past users of non-VOD programs
Creating bookmarks for VOD programs based at least in part on behavior,
The method of item 1, further comprising at least one.
(Item 13)
The first metadata that is similar to or identical to at least a portion of the second metadata;
At least a part of the metadata is different from at least a part of the second metadata
The method according to item 1, wherein the method is tagged or labeled.
(Item 14)
Causing one or more processors to perform the steps of any one of items 1-13.
A volatile or non-volatile computer that stores coded instructions that can be stored
A data-readable storage medium.
(Item 15)
A processor and means for executing the steps according to any one of items 1 to 13 are provided.
Device.

  The invention is illustrated by way of example, but not by way of limitation, in the accompanying drawings, in which like reference numerals refer to like elements.

1 is a block diagram illustrating a system in which one embodiment of the present invention is implemented. FIG. 2 illustrates an exemplary system in which an embodiment of the invention is implemented. FIG. 2 is a block diagram showing an overall overview of the components of a digital video recorder (DVR), according to one embodiment of the present invention. FIG. 5 is a flow diagram illustrating a technique for correlating media metadata from various sources, according to one embodiment of the invention. It is a block diagram which shows the example of the computer system with which one Embodiment is implemented.

  A method and apparatus for correlating media metadata from various sources is described. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be apparent to those skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known structures or devices are shown in block diagram form in order to avoid unnecessarily obscuring the present invention.

Embodiments are described herein according to the following overview.
1.0 Overall Overview 2.0 Overview of DVR 3.0 Correlation of Media Metadata from Various Sources 4.0 Implementation Mechanism-Hardware Overview 5.0 Extensions and Alternatives

1.0 Overall Overview The demands identified in the background art above and other demands and objectives that will become apparent in the following description are achieved in the present invention. It includes, in one aspect, techniques for correlating program metadata from various sources.

  According to one embodiment of the invention, the DVR obtains separate sets of program metadata from different sources. For example, the DVR obtains a first set of program metadata from an EPG data provider, a second set of program metadata from a first VOD service provider, and a program metadata from a second VOD service provider. You might get a third set. Under such circumstances, the first set of program metadata identifies information about programs that are scheduled to be broadcast on various channels in the near future, and the second set of program metadata is the first VOD. Information about the program stored on the service provider's server is specified, and the third set of program metadata specifies information about the program stored on the server of the second VOD service provider. The structure of the set of program metadata that DVR obtains from these various sources is different. For example, certain types of information in one set of metadata (eg, title, actor, category, genre, age, rating, etc.) are different (or not at all) from the same type of information in another set of metadata. May be tagged or labeled (without different). In other embodiments, even if the program metadata from each source is actually related to the same specific program, the program metadata from one source is from another one of the sources. May include the type of information (eg, title, actor, category, genre, age, rating, etc.) for a particular program that does not include the program metadata.

  According to one embodiment of the invention, before obtaining separate sets of metadata from different sources, the DVR automatically identifies the same program to which two or more sets of metadata are associated. Compare the set of metadata to try. According to one embodiment of the present invention, when making this comparison, even if those sets of metadata are tagged or labeled differently, and one set of metadata is Even if it contains at least some information that the set does not contain, the DVR looks for similarities between the information contained in one set of metadata and the information contained in the other set of metadata. Determining that the program metadata as represented in the set of metadata from the first source is sufficiently similar to the program metadata as represented in a different set of metadata from the second source In response, the DVR concludes that the set of program metadata from the first source and the set of program metadata from the second source actually refer to the same program.

  In accordance with one embodiment of the present invention, in response to determining that two separate sets of program metadata are in fact related to the same program, the DVR can generate program metadata from at least one set of program metadata. Select information about programs that are missing from other sets. The DVR creates an instance of a “canonical” data structure for the program and inserts into this instance information that is missing from at least one of the metadata sources. In an instance of a standard data structure, each information item from the metadata source is labeled and / or stored with a specific overview, and thus each “type” (eg title, Actor, category, genre, age, rating, etc.). For example, an instance of a standard data structure may be stored as an XML document (including XML tags that indicate the type of information) that follows a particular XML overview. The DVR then associates the DVR's persistent storage (eg, one or more hard disks) with the unique program identifier of the program with which the metadata set is actually (but perhaps not explicitly) related. An instance of this standard data structure is stored on the drive or solid state drive).

  In accordance with one embodiment of the present invention, for each source from which this program is available, in connection with an instance of the standard data structure for this program, the DVR sends this transmission on the DVR's persistent storage. Remember the original similarity. For example, if the same program is available from both the first VOD service provider and the second VOD service provider, the DVR will send both the first VOD service provider and the second VOD service provider to this program. Instances of standard data structures may be associated. Similarly, if a program that is scheduled to be broadcast on a specific channel at a specific time is also available from the VOD service provider, the DVR will inform both the channel / time and the VOD service provider of the standard data structure for this program. Instances may be associated.

  In accordance with one embodiment of the present invention, in response to the DVR user's request to find a program that satisfies the criteria specified by the DVR user, the DVR receives the criteria from the DVR user and determines the criteria. Find an instance of a stored standard data structure for a satisfactory program. The DVR creates a list of programs that meet the criteria and presents the list to the DVR user. Significantly, the list includes both (a) programs that are to be broadcast on specific channels at specific times in the future, and (b) VOD programs that are available from VOD service providers at the user's discretion. May be included. Under such circumstances, DVR users benefit from the possibility of searching for programs coming from various sources with only one search created through only one user interface. DVR creates and completes an instance of a standard data structure based on metadata comparisons so that program metadata obtained from any of those sources is sparse, incomplete, or specific DVR users can benefit in this way.

  In other aspects, embodiments of the invention include a computer device and a computer-readable storage medium configured to perform the techniques described above.

2.0 DVR Overview FIG. 2A illustrates an exemplary system that may be implemented in one embodiment of the present invention. The system includes at least one client device, such as a DVR 202 that is communicatively connected to the network 205 via any communication interface, such as an Ethernet interface or a wireless communication port. The function of DVR is typically shown in US Pat. No. 6,233,389, which is owned by the assignee and incorporated herein by reference. The system also includes a service provider 204, a content provider 206, a personal computer 208, and a portable device 210.

  The personal computer 208 may be a personal computing device such as a desktop computer or a laptop computer, for example, and is also connected to the network 205 via any communication interface including wireless. The portable device 210 may be any handheld computing device capable of displaying multimedia content, a cellular phone, a portable media player, or any other portable device, and any communication including wireless. It may be connected to the network 205 via an interface. DVR 202, personal computer 208 and portable device 210 each communicate with service provider 204 via network 205. In other embodiments, DVR 202, personal computer 208, and portable device 210 each communicate with content provider 210 via network 205.

  Network 205 may be implemented by any medium or mechanism that provides for the exchange of data between devices in a communication system. Examples of network 205 include, but are not limited to, a local area network (LAN), a wide area network (WAN), the Internet, one or more terrestrial, satellite, or wireless links. Alternatively or additionally, any number of devices connected to the network 205 may be directly connected to each other via a communication link.

  In one embodiment, content provider 206 provides broadcast program content to DVR 202 via cable, satellite, terrestrial communication, or other communication methods. Broadcast program content may include any multimedia content such as audio, video, or video content. In another embodiment, content provider 206 provides multimedia content, such as any downloadable content, to DVR 202, personal computer 208, or portable device 210 via network 205.

  In one embodiment, the DVR 202 communicates with a service provider 204 that satisfies program guide data, graphical resources (eg, fonts, photos, etc.), service information, software, advertisements, event identification data, and user interests. Provides other types of data that allow the DVR 202 to operate the service provider 204 independently. In other embodiments, the DVR 202, personal computer 208, and portable device 210 communicate with each other and transfer content, metadata, or any other data over the network 205, communication connection, or any local network. can do.

  In other embodiments, the content provider 206 may provide the service provider 204 with content data or any metadata comprised of promotional data, icons, web data, and other information. The service provider 204 may then interpret the metadata and provide the content data metadata to the DVR 202, personal computer 208, or portable device 210.

  Referring to FIG. 2B, in one embodiment, the DVR 202 generally comprises a plurality of components indicated by a signal converter 254 that digitizes an analog television signal to convert to or accept a digital data stream. It is necessary to do. An example of the internal structure and operation of a DVR is further described in US Pat. No. 6,233,389.

  The DVR 202 receives a broadcast signal from an antenna, a cable television system, a satellite receiver, or the like via the input 252A. Input 252A may have a plurality of channel alignment modules that allow multiple signals to be received and recorded simultaneously. For example, the TV input stream received by input 252A may take the form of a National Television System Committee (NTSC) compliant signal or a PAL compliant broadcast signal. According to another example, the TV input stream received by input 252A may be a digital satellite system (DSS) compliant signal, a digital broadcast service (DBS) compliant signal, or an advanced television system committee (ATSC) compliant signal. A digital format such as DBS, DSS, and ATSC are based on standards called Video Expert Group 2 (MPEG-2) and MPEG-2 transport. The MPEG-2 transport is a digital data stream from a TV source transmitter that allows a TV receiver to disassemble the input stream and find a program within the multiplexed signal. Is a standard for formatting.

  MPEG-2 transport multiplexing supports multiple programs including multiple video and audio broadcasts and personal data within the same broadcast channel. Input 252A tunes the channel to a particular program, extracts a particular MPEG stream from the channel, and provides the MPEG stream to the rest of the system. Analog TV signals are encoded in the same MPEG format using separate video and audio encoders, so the rest of the system does not know how the signal was obtained. Information may be modulated into the vertical blanking interval (VBI) of an analog TV signal in many standard ways. For example, the North American Broadcasting Teletext Standard (NABTS) may be used to modulate information onto a line with NTSC signals, and the FCC (US Federal Communications Commission) will be used for subtitles (CC) and extended data services (EDS). Command the use of some other line. Such a signal is decoded by input 252A and sent to the other modules as if the signal were delivered via an MPEG-2 private data channel.

  The recording module 260 records the incoming data stream by storing the digital data stream in at least one storage device. The storage device is indicated by storage devices 264A / 264B designed to hold segments of the digital data stream. Storage device 264A / 264B is one or more non-volatile storage devices (eg, hard disk, solid state drive, USB external hard drive, USB external memory stick, USB external solid state drive, internal 264A and / or external 264B) Or a storage device that can access the network. Signal converter 254 retrieves segments of the data stream, converts the data stream to an analog signal, modulates the signal to an RF carrier, and passes output 252B through which the signal is delivered to a standard TV set. . Output 252B may alternatively deliver digital signals to a TV set or video monitor. For example, DVR 202 may utilize DVI to send digital signals to the TV via a digital visual interface port (DVI) cable.

  The DVR 202 also includes a communication interface 262 through which the DVR 202 communicates with the network 205 through an Ethernet, wireless network, modem, or other communication standard. Further, the DVR 202 may be integrated into the TV system, and thus the above components are housed in a TV set that can perform the functions of the components of the DVR 202.

  In other embodiments, the DVR 202 is typically required to receive, record, store, forward, and play digital data signals from multiple sources, such as a PC, DVR, service provider, or content server, for example. Consists of multiple components. The DVR 202 can transfer digital data signals to other DVRs or PCs. DVR 202 may encode or decode digital signals into multiple formats for playback, storage, or transfer via encoder 256A and decoder 256B. According to one embodiment of the present invention, encoder 256A generates an MPEG stream. According to another embodiment of the present invention, encoder 256A generates a stream that is encoded using a different codec. Decoder 256B decodes the stream encoded by encoder 256A, or the stream stored in the format if the stream was received using an appropriate decoder. The DVR 202 can also encrypt or decrypt the digital data signal using an encryptor / decryptor 258 that stores, transfers or reproduces the digital data signal.

  In one embodiment, DVR 202 communicates with service provider 204. The service provider 204 is programmatic guide data, graphical resources such as brand icons and images, service information, software programs, advertisements, and DVRs 202 operate independently of the service provider 204 to perform autonomous recording functions. Provide other forms of data that make it possible. Communication between DVR 202 and service provider 204 uses a secure delivery architecture to transfer data between DVR 202 and service provider 204 such that both service data and user privacy are protected.

3.0 Correlating Media Metadata from Various Sources FIG. 1 is a block diagram illustrating a system 100 in which one embodiment of the invention can be implemented. Embodiments of the present invention may additionally or alternatively be implemented in a system that includes more, fewer, or different components than those shown in FIG.

  The system 100 includes a DVR 102, the Internet 104, an EPG data provider 106, and VOD service providers 108A-N. The DVR 102, the EPG data provider 106, and the VOD service providers 108A-N are communicatively connected to the Internet 104. DVR 102 transmits data to and receives data from EPG data provider 106 and VOD service providers 108A-N via Internet 104. In addition, DVR 102 receives broadcast television signals representing scheduled programs, typically via media other than the Internet. For example, the DVR 102 may receive a broadcast television signal via a cable and / or wirelessly.

  In one embodiment of the invention, the DVR 102 periodically receives EPG metadata from an EPG data provider. The EPG metadata identifies programs that are scheduled to be broadcast on different channels (eg, via cable and / or wirelessly) at different times. In one embodiment of the invention, each unique program identified in the EPG data has a unique identifier that does not have any other program. Further, in one embodiment of the present invention, each unique episode of a multi-episode series has a unique identifier that does not have any other episode of that series (no other series). In one embodiment of the present invention, the EPG data provider 106 transmits such an identifier in the EPG data to the DVR 102 via the Internet 104. The EPG data provider 106 may be implemented as one or more servers. In one embodiment of the present invention, EPG data is formatted as an XML document according to an XML overview that is configured to be interpreted by the DVR 102.

  Each of the VOD service providers 108A-N may be implemented as a separate set of one or more servers. Each VOD service provider 108A-N is owned and operated by an individual person or organization. The VOD service providers 108A-N typically store programs that the DVR 102 can download via the Internet 104 in response to a user request for the DVR 102. Typically, the DVR 102 plays programs received by the DVR 102 from any VOD service provider 108A-N when the DVR 102 receives those programs (eg, via a television screen connected to the DVR 102). That is, in one embodiment of the present invention, the DVR 102 plays programs that the VOD service provider “streams” to the DVR 102 via the Internet 104 (eg, using transmission control protocols and Internet protocols). Additionally or alternatively, in one embodiment of the invention, the DVR 102 can record such downloaded programs on a permanent storage device for later viewing by the DVR 102 user. In one embodiment of the invention, each of the VOD service providers 108A-N is associated with a different uniform resource locator that the DVR 102 uses to access that VOD service provider.

  Even if each of the VOD service providers 108A-N stores programs that the DVR 102 can download via the Internet 104, in one embodiment of the present invention, the set of programs stored by each of the VOD service providers 108A-N is At least slightly different. Thus, VOD service provider 108A may store certain programs that VOD service provider 108B does not store, and vice versa. In one embodiment of the present invention, each of the VOD service providers 108A-N further stores program metadata indicating information (among other potential information) about the programs stored by the VOD service provider. In one embodiment of the invention, the DVR 102 requests this program metadata from the VOD service providers 108A-N, receives from the VOD service providers 108A-N, and uses this program metadata to determine which VOD program is a VOD service. A menu indicating whether download and browsing from the providers 108A-N are possible is generated and displayed to the user 102 of the DVR.

  Program metadata stored by one of the VOD service providers 108A-N may be different in format (and typically different) from program metadata stored by any other one of the VOD service providers 108A-N. Even if all of the VOD service providers 108A-N store program metadata in the form of XML documents (and one or more of the VOD service providers 108A-N may store program metadata in some other format. ), The XML summary followed by those XML documents is different for each XML document (if any). Typically, none of the program metadata stored by any VOD service provider 108A-N follows the same XML overview that EPG metadata provided by the EPG data provider 106 follows. Typically, none of the program metadata stored by any VOD service provider 108A-N identifies the program by a unique identifier that identifies the program in the EPG metadata provided by the EPG data provider 106. . Often, operators of VOD service providers 108A-N are unaware of such identifiers.

  The EPG metadata that the EPG metadata provider 106 provides to the DVR 102 typically includes detailed information about the programs that are to be broadcast, but the VOD service providers 108A-N often store less program metadata. , Less details to include. For example, EPG metadata may include at least (a) a unique identifier for the episode, (b) the title of the episode, (c) the title of the series to which the episode belongs, (d) Genre to which the episode belongs (for example, drama, comedy, horror, adventure, documentary, etc.), (e) rating of the episode (if any) (for example, TV-Y, TV-Y7, TV-G, TV-) PG, TV-14, TV-MA), (f) the year that the episode was originally broadcast, and (g) the name of one or more actors who appeared in the episode. In EPG metadata, each of these information items is defined by an XML tag, which identifies the “type” of each of these information items that can be defined by the XML tag. As a result, the DVR 102 can relatively easily determine which part of the EPG metadata indicates the title of the episode of the program and which part of the EPG metadata indicates, for example, the genre of the episode of the program. In contrast to EPG metadata, program metadata provided by VOD service providers 108A-N may exclude many of the details contained in EPG metadata. Program metadata provided by the VOD service providers 108A-N may not clearly indicate the “type” of the information item specified in the program metadata.

  According to one embodiment of the present invention, the DVR 102 (or any other agent or automated mechanism that operates on behalf of the DVR 102) is identified in program metadata that (a) actually identifies the type of information item. EPG data provider 106 and VOD service provider to identify the type, and (b) “fill in” program details that may have been excluded from one or more program metadata sources Correlate program metadata received from 108A-N. In one embodiment of the present invention, DVR 102 (or any other agent or automated mechanism that operates on behalf of DVR 102) allows each metadata to determine similarities between programs with which the program metadata is related. Compare program metadata received from the source. Based on this comparison, DVR 102 (or some other agent or automated mechanism that operates on behalf of DVR 102) is described above even if the metadata associated with the program does not explicitly identify the program. Attempt to label each program with a unique program identifier.

  For example, the DVR 102 may determine that the phrase in the program metadata received from the VOD service provider 108A is very similar or identical to the title of the particular program identified in the EPG metadata. . In addition, DVR 102 indicates that the phrase in the program metadata received from VOD service provider 108A is very similar or identical to the name of the actor appearing in the particular program, as indicated in the EPG metadata. May decide. As a result, due to this similarity, the DVR 102 reasonably concludes that the program metadata received from the VOD service provider 108 is actually related to the same specific program to which the same EPG metadata is related. In response to this conclusion, the DVR 102 can enhance the program metadata from the VOD service provider 108A so that the program metadata includes a unique program identifier and other details shown in the corresponding EPG data. The DVR 102 may label information items that are recognized but not labeled in the VOD program metadata, respectively, by type.

  FIG. 3 is a flow diagram illustrating a technique for correlating media metadata from various sources according to one embodiment of the invention. In alternative embodiments of the invention, techniques for correlating media metadata from various sources may include more, fewer, or different steps than those shown in FIG.

  Referring now to FIG. 3, at block 302, the DVR receives EPG metadata from the EPG data provider. EPG metadata is broadcast or available for scheduled programs (eg, DVR can be received as a broadcast television signal or multimedia signal) (eg, over the air, satellite, internet, or cable). And the scheduled date and time when those scheduled programs will be broadcast or available. As described above, in one embodiment of the present invention, for each program (which may be one episode of a series of episodes), the EPG metadata indicates a program identifier that identifies only that program. Each program has a unique identifier. This identifier may originate from an EPG data provider, but in one embodiment of the invention, this identifier originates from a source other than the EPG data provider. For example, the intermediate server may intercept the EPG metadata and add the program identifier to improve the EPG metadata, and then transfer the metadata with the improved identifier to the DVR.

  In block 304, the DVR stores the EPG metadata in the DVR's persistent storage. In doing so, the DVR may analyze tags and / or labels in the EPG metadata to determine the types of various information items in the metadata. For example, the DVR may determine that the information included in the “series” tag indicates the title of a series of a plurality of episodes to which the program belongs. In another example, the DVR may determine that the information contained within the “episode” tag indicates the title of the episode represented by the program. In another example, the DVR may determine that the information contained within the “ID” tag indicates a unique identifier for the program.

  EPG metadata typically includes information about multiple programs. For each such program, the DVR adds an instance of a “standard” data structure for that program, along with the metadata information item with which the program is associated. For example, an instance of a standard data structure may include a “series title” field into which the DVR inserts a series title as derived from EPG metadata. In another example, an instance of a standard data structure may include a “genre” field into which the DVR inserts a genre that fits the program as derived from EPG metadata. In one embodiment of the invention, the structure of an instance of a standard data structure does not change from program to program, but the values inserted into the fields of the standard data structure instance vary. Thus, in one embodiment of the invention, all examples of standard data structures have the same fields.

  The DVR may periodically obtain EPG metadata from the EPG data provider. From time to time, the storage of instances of standard data structures stored in the DVR may grow. As described below, the DVR may use instances of these standard data structures so that the DVR identifies and enhances the program metadata received from the VOD service provider.

  At block 306, the DVR receives program metadata from the VOD service provider. Typically, content provided by a VOD service provider—in response to a DVR user requesting a list of content stored by the VOD service provider, the DVR receives such program metadata. Program metadata received from the VOD service provider may not be clearly labeled and may have as much detailed information about the program as the EPG metadata.

  In block 308, the DVR compares the program information in the VOD program metadata having an instance of the standard data structure. VOD program metadata may include program information regarding a plurality of different programs. Based on the similarity between the information in the VOD program metadata and the information in the instance of the standard data structure, the DVR attempts to identify the program to which the VOD program metadata relates (VOD metadata is explicitly May not identify programs). For example, in both a title and an actor, based on the similarity between VOD program metadata for a particular program and an instance of a particular standard data structure, the particular program to which the VOD program metadata is associated is The DVR may determine that the structure instance is actually the same as the associated program. DVR may use various heuristics and comparison techniques to attempt to identify similarities between programs. In one embodiment of the present invention, a DVR is an instance of a standard data structure when the quantified similarity between the information in the standard data structure instance and the information in the VOD program metadata exceeds a certain threshold. And VOD program metadata are related to the same program.

  In block 310, in response to determining that the VOD program metadata is associated with the same program that the instance of the particular standard data structure is already associated with, the DVR is responsible for the program with which the VOD program metadata is associated. Create and add a new standard data structure instance. Based on the similarities between information items in instances of the old standard data structure and VOD program metadata, the DVR determines the type of information item in the VOD program metadata. For example, if an instance of the old standard data structure indicates the title of a particular episode in the “Episode Title” field, and if the VOD program metadata contains an information item that matches the value of the “Episode Title” field, DVR May add the information item to the “episode title” field of the new standard data structure.

  In addition, in one embodiment of the present invention, if an instance of the old standard data structure contains a value for some field that does not contain a value in the VOD program metadata, the DVR will correspond to the corresponding field of the new standard data structure instance. To add values from instances of old standard data structures. Thus, the DVR can use the EPG metadata to “complete” the partially complete metadata received from the VOD service provider. One of the values that the DVR can “carry over” to an instance of a new standard data structure is a unique program identifier that is in some cases not specified in the VOD program metadata.

  A value in an instance of the old standard data structure (including the value of EPG metadata) and a value in the instance of the new standard data structure (including the value of VOD program metadata) Even if an instance and the instance of the new standard data structure are associated with the same program, they may be different. For example, one field of the standard data structure may be a field that indicates the transmission source of the program. In one example, the value of this field may indicate a cable media provider or a wireless broadcast media provider, while in another example, the value of this field may indicate the URL of a VOD service provider's server. Information that is not related to VOD program content may be excluded from instances of standard data structures that contain values for VOD program content. For example, in some situations, if a VOD program is always available from a VOD service provider, an instance of a standard data structure for the VOD program is the channel on which the program is scheduled to be broadcast, or the program is broadcast. May not contain values related to the date and time of the appointment.

  At block 312, the DVR stores the new standard data instance (created and added at block 310) in the DVR's persistent storage. Thus, an instance of a new standard data structure is one of the DVR's stored instances of standard data structures that the DVR may use in the future to identify programs associated with VOD program metadata from other VOD service providers. Part. Thus, in one embodiment of the present invention, DVR uses EPG metadata to identify and complete partially complete VOD program metadata, but in one embodiment of the present invention, DVR Or alternatively, details from one VOD service provider's metadata are used to identify and complete some partially complete metadata from another VOD service provider.

  If the DVR user instructs the DVR to show a list of program content available via the DVR, the DVR will generate such a list based on an instance of the standard data structure stored by the DVR. Can do. The list may include references to both (a) programs that are scheduled to be broadcast on specific channels at specific dates and (b) programs that the DVR can download and / or stream from the VOD service provider. Thus, programs from various media sources can be presented to DVR users as a concise and comprehensive list in the user interface. To simplify the list of available programs, the DVR may selectively exclude multiple references to the same program if the same program is available from multiple different sources. The DVR can determine that the two programs are identical based on the unique program identifier stored in the standard data structure instance for the two programs.

  In addition, the DVR user requests a search for programs that satisfy the criteria specified by the DVR user (eg, all programs that have a particular word in the title, or all programs in which a particular actor appears). In response, the DVR determines those programs by determining a set of instances of a standard data structure whose relevant field (eg, title, actor, etc.) values meet the criteria specified by the DVR user. You can search. The DVR can indicate a list of programs that meet the criteria, including programs from various media sources (eg, cable television signals, wireless television signals, and multiple different VOD service providers, etc.). Further, to simplify the list of programs that meet the criteria, DVR may selectively exclude multiple references to the same program if the same program is available from multiple different sources. .

  Although certain steps of the above technique are described as being performed by a DVR, in alternative embodiments of the present invention, one or more of the steps may be performed by some mechanism external to the DVR instead of the DVR. Good. For example, a server outside the DVR and a server with which the DVR communicates via the Internet may mediate communication between the DVR, the EPG data provider, and the VOD service provider. The server may intercept metadata from EPG data providers and VOD service providers. The server can create, add and store instances of standard data structures as described above, thereby preventing the DVR from performing those tasks. In one embodiment of the present invention, when a DVR user instructs the DVR to perform a search for programs that meet certain criteria, the DVR instructs the server to perform this search instead of the DVR. The DVR can thus indicate to the DVR user the search results that the DVR received from the server.

  As noted above, in one embodiment of the present invention, the DVR (or server, or mechanism that operates on behalf of the DVR) is a program that is at least partially identified in the VOD program metadata from the VOD service provider. Create an instance of a general data structure for. As noted above, in one embodiment of the present invention, EPG metadata from an EPG data provider and / or other VOD program metadata (from other VOD service providers) is received from a VOD service provider. Used to “fill in” and complete details that may be excluded from the generated partial metadata. In addition or alternatively, in one embodiment of the present invention, additional media correlation information present in an instance of an existing standard data structure is generated for the program with which the VOD program metadata is associated. Will be added to the instance as well.

  Before or after an instance of the standard data structure is stored on the DVR (or another server), a human agent can send an instance of the standard data structure between that instance's program and one or more other instances of the program. By adding information indicating the correlation between the two, the information in the standard data structure instance can be improved. For example, if a particular program is starring “dark hero”, a human agent will add the particular program to the standard data structure for the instance. May add information to indicate that “Dark Hero” will be the main character. If the same program becomes available from the VOD service provider, information indicating that the particular program will be the “Dark Hero” will also be made available from the VOD service provider using the techniques described above. Will be copied to an instance of the standard data structure for the program. Thus, even if the VOD metadata for a program does not include attributes added by a human agent such as “Dark Hero”, in one embodiment of the present invention, an instance of an existing standard data structure for the same program As long as indicates the attributes already, an instance of the new standard data structure for the program will automatically include those attributes. Such attributes may match individual fields or multiple fields within a standard data structure.

  In one embodiment of the present invention, the DVR provides search features that result in programs having similar attributes (eg, “Dark Hero”) added by the human agent having those attributes. As a related program, it is shown to the DVR user. For example, a DVR user may instruct the DVR to search for a program having a particular title. In response to a search request from a DVR user, the DVR can return a list of programs (both traditionally broadcast and those provided by VOD) that have that particular title. In addition, the DVR is a program with attributes added by a human agent that are the same or similar to the attributes specified in the standard data structure instance of the program with the particular title (programs without a particular title). List). Such attributes added by a human agent may be added to any metadata-specific attributes received from any EPG data provider.

4.0 Implementation Mechanism—Hardware Overview FIG. 4 is a block diagram that illustrates a computer system 400 upon which an embodiment of the invention may be implemented. Computer system 400 includes a bus 402 or other communication mechanism for communicating information, and a processor 404 coupled with bus 402 for processing information. Computer system 400 also includes a main memory 406 coupled to bus 402 for storing information and instructions executed by processor 404, such as random access memory (RAM) or other dynamic storage devices. Main memory 406 may also be used to store temporary variables or other intermediate information during execution of instructions executed by processor 404. Computer system 400 further includes a read only memory (ROM) 408 or other static storage device coupled to bus 402 for storing static information and instructions for processor 404. A storage device 410 such as a magnetic disk or optical disk for storing information and instructions is provided and coupled to the bus 402.

  Computer system 400 may be coupled via bus 402 to a display 412 for displaying information to a computer user, such as a cathode ray tube (CRT). Coupled to the bus 402 is an input device 414, including alphanumeric characters and other keys, for communicating information and command selections to the processor 404. Another type of user input device communicates direction information and command selections to the processor 404 and controls cursor movement 416, such as a mouse, trackball, stylus, or cursor direction key, to control cursor movement on the display 412. It is. The input device typically has two degrees of freedom in two axes, a first axis (eg, x-axis) and a second axis (eg, y-axis), which means that the device is positioned on a plane. It is possible to specify.

  The invention is related to the use of computer system 400 for selecting frames of a multi-frame video program for display in response to a selected trick play mode of a DVR. According to one embodiment of the present invention, selecting a frame of a multi-frame video program for display in accordance with the selected trick play mode of the DVR is one of one or more instructions included in the main memory 406. Provided by computer system 400 in response to processor 404 executing one or more arrays. Such instructions may be read into main memory 406 from other computer readable media, such as storage device 410. Execution of the array of instructions contained in main memory 406 causes processor 404 to execute the steps of the processing described herein. In alternative embodiments, hardwired circuitry may be used instead of or in combination with software instructions to implement the present invention. Thus, embodiments of the invention are not limited to any specific combination of hardware circuitry and software.

  The term “computer-readable medium” as used herein refers to any medium that participates in providing instructions to processor 404 for execution. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 410. Volatile media includes dynamic memory, such as main memory 406. Transmission media include coaxial cables, copper wire, and optical fibers including wires having a bus 402. Transmission media can also take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications.

  Common forms of computer readable media include, for example, floppy disk, flexible disk, hard disk, magnetic tape, or any other magnetic medium, CD-ROM, any other optical medium, punch card, Paper tape, any other physical medium with a hole pattern, RAM, PROM, EPROM, flash EPROM, any other memory chip or cartridge.

  Various forms of computer readable media may be involved in executing one or more sequences of one or more instructions to processor 404 for implementation. For example, the instructions may be first executed on a remote computer magnetic disk. The remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to computer system 400 can receive the data on the telephone line and use an infra-red transmitter to convert the data to an infra-red signal. An infrared detector receives the data carried in the infrared signal and a suitable circuit can stream the data on the bus 402. Bus 402 carries data to main memory 406, from which processor 404 retrieves and executes instructions. The instructions received by main memory 406 may optionally be stored on storage device 410 either before or after implementation by processor 404.

  Computer system 400 also includes a communication interface 418 coupled to bus 402. Communication interface 418 provides a two-way data communication coupling to network link 420 connected to local network 422. For example, communication interface 418 may be an integrated digital network (ISDN) card or modem that provides a data communication connection to a corresponding type of telephone line. As another example, communication interface 418 may be a LAN card that provides a data communication connection to a compatible local area network (LAN). A radio link may be implemented. In any such implementation, communication interface 418 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

  Network link 420 typically provides data communication through one or more networks to other data devices. For example, the network link 420 may provide a connection via the local network 422 to a data device operated by a host computer 424 or an Internet service provider (ISP) 426. Similarly, ISP 426 provides data communication services through a global packet data communication network commonly referred to as the “Internet” 428. Local network 422 and Internet 428 both use electrical, electromagnetic or optical signals that carry digital data streams. Signals over various networks and signals over network link 420 that carry digital data to or from computer system 400 and via communication interface 418 are exemplary forms of carrier waves that carry information. Take.

  Computer system 400 can send messages and receive data, including program code, via the network, network link 420, and communication interface 418. In the Internet example, the server 430 may send the requested code for the application program over the Internet 428, ISP 426, local network 422 and communication interface 418.

  The received code may be executed by processor 404 when received, and / or stored in storage device 410, or other non-volatile storage for later execution. In this way, computer system 400 can obtain application code in the form of a carrier wave.

5.0 Extensions and Alternatives In the foregoing specification, the invention has been described with reference to specific embodiments thereof. However, it will be apparent that various modifications and changes may be made without departing from the broader spirit and scope of the invention. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense.

  For example, while some of the above embodiments of the invention relate to using correlated metadata to indicate a list of programs that include both VOD and non-VOD programs, additional embodiments of the invention , Such correlated metadata to schedule the recording of non-VOD programs and / or bookmark VOD programs (in some cases for later retrieval by DVR and / or for viewing by DVR users) In addition, embodiments may be used that are also used. For example, based on DVR user behavior with respect to one or more VOD programs, the DVR may automatically schedule recording of one or more non-VOD programs, including the one or more VOD programs and the one. This is based on metadata correlated between one or more non-VOD programs. In another example, based on DVR user behavior for one or more non-VOD programs (eg, traditional, time-scheduled broadcasts), the DVR automatically selects one or more VOD programs. Bookmarks may be made (to direct the user's attention) based on metadata correlated between the one or more VOD programs and the one or more non-VOD programs. The metadata may be correlated using the techniques described herein.

Claims (15)

A method for correlating media metadata from various sources, the method comprising:
The first metadata obtained from the sender and the second metadata obtained from another sender are similar to at least a part of the second metadata. Determining whether to correspond to the same specific content by determining whether the first metadata structure is the same as the second metadata structure. Different from that,
Determining that an item of information related to the particular content is included in both the first metadata and the second metadata;
If the first metadata indicates that the item of information is of a particular type and the second metadata does not indicate that the item of information is of the particular type; Updating the second metadata to indicate that the item of information in the second metadata is of the specific type based only on the specific type indicated by the metadata of the first Updating the second metadata indicates only the specific type of details indicated by the first metadata and not indicated by the second metadata. Including filling in the metadata of
Determining a set of multimedia content to be identified in a displayed list of multimedia content information based at least in part on the updated second metadata, comprising: At least one of the multimedia content of the multimedia content is available from the source, and at least one other multimedia content in the list of multimedia content is obtained from the other source. A method comprising:   The method of claim 1, wherein the source is an electronic program guide and the second metadata relates to content that is available from a video on demand (VOD) content provider.   The first metadata relates to content that is available from a first video on demand (VOD) content provider, and the second metadata is a second different from the first VOD content provider. The method of claim 1, wherein the method relates to content that is available from a VOD content provider.   The method of claim 1, wherein the method is performed by a device that is a digital video recorder (DVR).   The method of claim 1, wherein the specific type is at least one of a title, an actor, and a genre. Receiving user input defining one or more criteria, wherein a particular criterion of the one or more criteria indicates one or more types;
Determining a result of a set of programs that satisfy the criteria, wherein the set of programs is determined by searching for candidate items of information, wherein the candidate items of information are of the one or more types; The result of the program set is included in the program set to be identified in the displayed list of program information;
The method of claim 1, further comprising:   The method of claim 6, wherein the candidate item of information indicated to be a type of the one or more types includes the item of information in the second metadata. Determining an associated program, wherein the metadata associated with the associated program includes an item of information that is also included in the metadata associated with the program within the result of the set of programs. The method of claim 6, further comprising: the related program does not meet the criteria.   The method is performed by a server instead of a digital video recorder (DVR), wherein the server is (a) external to the DVR and (b) communicates with the DVR over a network. 4. The method according to 4. The second metadata relates to content that is available from a particular source,
The method
In response to determining that the first metadata and the second metadata are related to the same content, determining one or more details, the one or more details being (A) related to the same content and (b) specified in the first metadata, but (c) not specified in the second metadata,
Responsive to determining the one or more details, storing the one or more details in a third metadata;
Storing an association between the third metadata and the particular source on a permanent storage device;
The method of claim 1, further comprising:   The second metadata is related to content scheduled to be broadcast on a specific channel at a specific time, and the first metadata is related to content that the DVR can obtain at any time. The method described.   (A) scheduling non-VOD program recordings based at least in part on past user actions on VOD programs; or (b) at least partly on past user actions on non-VOD programs. The method of claim 1, further comprising at least one of creating a bookmark for a VOD program based thereon.   At least a portion of the first metadata that is similar to or identical to at least a portion of the second metadata is tagged or labeled differently than at least a portion of the second metadata. The method of claim 1, wherein:   14. A volatile or non-volatile computer readable storage medium having encoded instructions stored thereon, wherein the instructions perform the steps included in the method of any one of claims 1-13. A computer-readable storage medium capable of causing one or more processors to do.   An apparatus comprising a processor and means for performing the steps involved in the method according to any one of claims 1-13.

Images