Abstract:
An automatic metadata generation service system for use in home networks includes a home network interface adapted to perceive user network activity on a home network. A metadata generation service module generates user metadata based on the user network activity. An update service module automatically updates one or more existing metadata sets on the home network with generated metadata. In other aspects, a metadata generation service system for use with a home network, includes a home network interface adapted to interact with one or more of content providers or service providers according to one or more service discovery protocols. A monitoring service module obtains an update of metadata from one or more of the providers. A metadata generation service module convert metadata of one format received via the update to metadata of another format required by the home network.

Description:
FIELD OF THE INVENTION  
       [0001]     The present invention generally relates to a middleware service architecture supporting metadata in a home networked device control framework, and relates in particular to a metadata automatic generation service system for use in home networks.  
       BACKGROUND OF THE INVENTION  
       [0002]     Today&#39;s home networks are places for complex interactions between users and equipment, and between users and content and service providers. Metadata services provide an important function in enabling system functionality for many of such interactions. Typically, metadata is generated by content and service providers, and is associated with some content to be processed by a user and/or user&#39;s equipment. In effect, the metadata describes the content in accordance with a predefined metadata schema that labels the content according to a settled methodology so that it can be readily organized or interpreted. Today&#39;s metadata schema include XML schemas (e.g., CDS, TVA, UPnP, Dublin Core, etc.). However, there is no automatic process of generating multiple content and user metadata based on complex interactions within a home network. The present invention fulfills this need.  
       SUMMARY OF THE INVENTION  
       [0003]     In accordance with the present invention, an automatic metadata generation service (AMDGS) system for use in home networks includes a home network interface adapted to perceive user home network content viewership and other activity. A metadata generation service module generates user metadata based on home network AV control traffic and other types of user network activity. An update service module automatically updates one or more existing metadata sets on the home network with generated metadata. In other aspects, a metadata generation service system for use with a home network includes a home network interface adapted to interact with one or more of content providers or service providers according to one or more service discovery and control protocols. A monitoring service module obtains an update of metadata from one or more of the providers via these protocols. A metadata generation service module converts metadata of one format/schema to metadata of another format/schema required by the home network.  
         [0004]     Further areas of applicability of the present invention will become apparent from the detailed description provided hereinafter. It should be understood that the detailed description and specific examples, while indicating the preferred embodiment of the invention, are intended for purposes of illustration only and are not intended to limit the scope of the invention.  
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0005]     The present invention will become more fully understood from the detailed description and the accompanying drawings, wherein:  
         [0006]      FIG. 1  is block diagram illustrating a metadata generation service module of the metadata service in accordance with the present invention;  
         [0007]      FIG. 2  is a block diagram illustrating monitoring and update service modules of the metadata service in accordance with the present invention;  
         [0008]      FIG. 3  is a block diagram illustrating a first embodiment of a metadata device in accordance with the present invention;  
         [0009]      FIG. 4  is a block diagram illustrating a second embodiment of a metadata device in accordance with the present invention;  
         [0010]      FIG. 5  is a flow diagram illustrating a method of operation for the metadata service in accordance with the present invention; and  
         [0011]      FIG. 6  is a flow diagram illustrating an example of user metadata generation in accordance with the present invention. 
     
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS  
       [0012]     The following description of the preferred embodiments is merely exemplary in nature and is in no way intended to limit the invention, its application, or uses.  
         [0013]     The middleware service architecture of the present invention provides for automatic generation of content-related and user-related metadata based on home network activity, and also based on content and service provider event notifications. This service can be discoverable and controllable from various types of consumer equipment (e.g., Audio/Video devices) devices of XML-based home control frameworks, such as UPnP. For example, user content segmentation preferences and metadata can be generated based on the user&#39;s media playback activity, with subsequent generation of related user metadata (e.g., TVA schema-based metadata). Additional service components also allow for content/user-related metadata (including content instance location metadata, content promotional metadata, and content segmentation metadata) generation and update as a result of content and service provider subscription-based services.  
         [0014]     Referring to  FIG. 1 , automatic metadata generation service (AMDGS)  11  includes a metadata generation service module  12  that generate user metadata  14  (e.g., for TV Anytime) based on copies of UPnP audio visual control actions  22  received from a control point  10  interacting with a media server (MS)  16  and media renderer (MR)  18 . User/consumer metadata relates to a user of control point  10 , and user preferences are just one example of user metadata. User behaviors and viewership habits are further examples of user metadata (e.g., frequency of viewing some portion of content or preference to a specific type of content, like drama). In contrast, content metadata is related to content in a description. As an example related to UPnP eventing, consider that a user subscribes to a content promotion service (a discoverable Metadata service). User interaction with such metadata service performed through a control point  10  can result in content-related metadata being generated. If user or content metadata is affected, it can be updated based on the subscription behavior of the user.  
         [0015]     Content could also be segmented in various ways. For example, a series can be partitioned in one hour-long segments, with commercial insertions following a pattern that is predefined by a content/service provider. This circumstance provides an example of how content can be segmented before it arrives at the home network. Content can also be segmented further by user playback activity that pauses in one place, loops, skips ahead in another, and loops back to repeat a given portion of content. It can therefore be useful to generate content segmentation metadata indicating how the content is segmented in multiple ways. For example, it can be useful to analyze streaming or stored content to determine the segments of shows and commercial insertions, and generate metadata based on the analysis. It can also be useful to record user commands relating to user consumption of the content (e.g., PLAY, PAUSE), and generate content segmentation metadata accordingly.  
         [0016]     Generated metadata  14  can describe content consumed, rejected, or otherwise responded to by a user employing control point  10  to interface with media content. Thus, user metadata  14  can be generated based on analysis of network user activity, which can include user initiated controls, UPnP Content Directory Service (CDS)-control point (CP) activity, and/or user activity relating to control of the media server  16  and/or media renderer  18  (e.g., play/stop/fast forward).  
         [0017]     Turning now to  FIG. 2 , some embodiments of the AMDGS  11  according to the present invention include a monitoring service module  24  interfacing with an update service module  26 . Monitoring service module  24  can monitor various forms of information  28  relating to one or more content streams and generate content and user metadata in response. For example, monitoring service module can receive streaming media content and/or related electronic programming guide (EPG) information including textual content descriptions and/or metadata from various content providers  28 A and service providers  28 B.  
         [0018]     In some embodiments, monitoring service module  24  and providers  28 A and  28 B can cross-advertise services, exchange service-level events, event and service subscriptions, and/or promotions  30  in relation to content and services. For example, monitoring service module  24  can use a subscription message  30 A to subscribe to receive an EPG update notification  30 B indicating that new EPG information is available. Thus, monitoring service module  24  can periodically receive and parse EPG-related metadata and/or analyze streaming media content  25 . As a result, monitoring service module  24  can generate content metadata  32  based on content stream segmentation, closed captions, subtitles, and/or vertical blanking interval contents and other types of stream analysis. In a related example, a movie can carry promotion metadata that should be utilized only after the movie is viewed. In this case, a promotional code can be delivered to the user upon watching the movie that gives the user a reference point (e.g., a new set of content location and content description metadata) to another program that is a reward to the user for purchasing and buying the original content.  
         [0019]     It is envisioned that a service event update notification from a content provider can indicate that a series is now partitioned differently for consumer&#39;s playback, such that a serial that was previously intended to be played back in one hour segments should now be packaged for viewing in thirty minute segments. Similarly, the content can indicate a change in a pattern of commercial insertions. The automatic metadata generation service can therefore generate some of the segmentation metadata which will describe how the content in question is now segmented and/or subsequent viewership and commercial insertions are to be performed.  
         [0020]     It should be readily understood that metadata  32  can be generated in accordance with different formats and XML schemas (e.g., CDS, TVA, UPnP, Dublin Core, etc.), and that the metadata can be used in various ways. For example, user profiles can be developed based on user network activity and follow CC/PP-based device/user profile schemas. In one example, a MD record can reflect that a particular user skipped one commercial, but watched another twice, and this MD record may be reported to content and/or service providers  28 A and  28 B. In another example, a child&#39;s viewing activity can be recorded and tabulated to reflect the child&#39;s habits of viewing violent content for viewing by a parent user granted access to the child&#39;s user profile by virtue of the parent user&#39;s status as the home network administrator. In still another example, a user&#39;s viewing preferences can be recorded and communicated to a device being employed by that user to view content, and the device can deliver the content according to the preferences (i.e., initial viewership format aspect, format change between normal and HDTV programs, initial volume, volume change during commercials, etc.). It is also envisioned that such metadata can be used to recommend and/or automatically record content for users using DVR type device, as an example.  
         [0021]     Turning now to  FIG. 3  some embodiments of the AMDGS  11  can be a metadata generation service  12  employed by an update service  26  to generate metadata based on contents of an update request  40 , generated by a control point as a result of subscription to a metadata publisher. For example, consider a control point  10  of a metadata device, such as a set top box or remote control, subscribing via subscribe message  34  to a media content stream-related metadata publisher that at least includes pre-authored metadata, such as “E-flyer” metadata in accordance with the TVA standard.  
         [0022]     Control point  10 , which is optional, can act as a monitoring module which may or may not generate metadata. In fact, control point  10  may, in generating request  40 , transparently pass through metadata in whatever form it is received from the metadata publisher  36 . Thus, metadata update request  40  can contain content metadata and/or pre-authored metadata that is not in a target metadata format (e.g., TVA format). Alternatively or additionally, control point  10  may generate user metadata based on its own A/V session control actions. Metadata generation service module and/or metadata update service module can translate the input metadata into the target metadata schema needed by the device. It should be readily understood that the control point is optional, as services can also interact with each other, by means of discovering each other, subscribing to each other, and invoking each other actions/interfaces.  
         [0023]     In any case, update service module  26  can evaluate the metadata set to determine the need for generation of metadata at evaluation component  42 , and form a metadata update message  44  of appropriate metadata. Any contents of update request  40  that are already in the proper form of metadata can be added to the action  44  directly. However, any AV action-generated metadata and/or pre-authored metadata not in the proper metadata format can be transmitted to metadata generation service  12 . Metadata generation service  12  can then generate the metadata and return them to the update service  26  for addition to the message  44  carrying target metadata. This message  44  can then be transmitted over the communications system to accomplish metadata system update.  
         [0024]     Turning now to  FIG. 4 , it should be readily understood that a metadata enabled device can have control point (CP) and services instances, and that the monitoring service module  24  of AMDGS  11  can translate interactions between other services (e.g., copies of AV actions) into instructions for the AMDGS  11 . For example, in UPnP, CPs are separate entities from the services. Monitoring service module  24  can interpret the AV actions, and instruct MD update module  26  and/or generation module  12  accordingly. Also, monitoring service module  24  can subscribe to content providers and metadata publishers  36 . For example, AMDGS  11  can subscribe to services of a metadata publisher  36  via messages  34  and  38 , and thereafter receive new metadata event messages  46  that pass pre-authored metadata not already in the required metadata format to control point  10 . In this manner, control point  10  can assist in connecting the AMDGS with other services so that metadata of the required format can be generated based on the pre-authored metadata, and passed to metadata update service  26 . Update service  26  can therefore perform update using metadata  48  received from control point  10 . However, it should be understood that the CP is optional, as services can subscribe to other services directly as described above. Also, UPnP events are just an example of service subscription events. Alternatives to UPnP event subscription can be metadata publisher service subscription. Further, any or all of monitoring service module  24 , generation service module  12 , or update service module  26  can receive the corresponding service events.  
         [0025]     Turning now to  FIG. 5 , a method of operation for a TVA metadata generation system includes, in some embodiments, participating in a service discovery protocol of an XML device control framework at step  50 . Information about user activity relating to user consumption of a media content stream can be received at step  52 .  
         [0026]     At step  54 , user metadata can be generated based on received AV control actions. For example, user metadata can be generated based on user activity at step  54 A, user voice command at step  54 B, and/or content directory service (CDS) interactions with some control point at step  54 C. Generating the user metadata based on user activity at step  54 A can include generating user metadata based on user selections, user playback activity, and/or user rendering preferences. For example, user rendering preferences can be generated based on user playback activity.  
         [0027]     At step  56 , a media content stream can be received and monitored, with content metadata being generated based on characteristics and/or content of the stream. For example, content metadata can be generated based on stream analysis at step  56 A that can include parsing contents of textual descriptions in an EPG, and/or noting stream segmentation by doing content stream picture analysys. Also, content metadata can be generated based on closed captions at step  56 B, subtitle contents at step  56 C, and any metadata included in the vertical blanking intervals at step  56 D. Alternatively or additionally, in step  54  and/or step  56 , any pre-authored metadata relating to user media consumption activity and/or media content that is not already in a required format can be used to generate equivalent metadata of the required format. For example, TVA metadata can be generated from non-TVA format metadata produced as user preferences and/or media consumption history. Also, non-TVA format metadata extracted from an EPG embedded in a media content stream can be converted to TV Anytime metadata as in step  56 E. Other translations between metadata formats can also be made. The generated metadata can be used in an update at step  62 .  
         [0028]     In a parallel process, a notification can be received at step  58  of a metadata change event from a content or service provider, and the new metadata obtained. Then, the newly obtained metadata can be translated as described above to a required format as needed at step  60 . Finally, an update can occur based on the metadata at step  62 .  
         [0029]     Turning now to  FIG. 6 , the process of generating user metadata based on user AV control commands/viewing activity is further explored with an example. For example, at step  64 , recordings are made regarding user viewings of different portions of categorized content. For example, the user may skip a sports commercial, but view a particular car commercial twice. In this case, it is possible to infer a degree of user interest in automobiles or in the particular advertised automobile based on the number of times the user viewed the commercial at step  66 A. Similarly, it is reasonable to infer that the user is not interested in sports in general, or perhaps not interested in the particular sport advertised at step  66 B. User activity and other types of metadata can therefore be generated at step  68  about the user&#39;s interests. The user&#39;s profile (including metadata) can then be updated, and/or the content or service providers can be notified of the user&#39;s interest. Other home network users may also find it useful to view the user&#39;s profile in making gift purchase decisions, especially if instances of expressed user interest are tabulated with respect to categories, and the categories in the user&#39;s profile dynamically updated with metadata as they are observed. Such a user profile can be of similar use to content and service providers.  
         [0030]     The description of the invention is merely exemplary in nature and, thus, variations that do not depart from the gist of the invention are intended to be within the scope of the invention. Such variations are not to be regarded as a departure from the spirit and scope of the invention.