Patent Application
20070143370
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.
Today'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'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'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.
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.
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.
The present invention will become more fully understood from the detailed description and the accompanying drawings, wherein:
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.
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'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.
Referring to
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.
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).
Turning now to
In some embodiments, monitoring service module 24 and providers 28A and 28B 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 30A to subscribe to receive an EPG update notification 30B 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.
It is envisioned that a service event update notification from a content provider can indicate that a series is now partitioned differently for consumer'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.
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 28A and 28B. In another example, a child's viewing activity can be recorded and tabulated to reflect the child's habits of viewing violent content for viewing by a parent user granted access to the child's user profile by virtue of the parent user's status as the home network administrator. In still another example, a user'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.
Turning now to
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.
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.
Turning now to
Turning now to
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 54A, user voice command at step 54B, and/or content directory service (CDS) interactions with some control point at step 54C. Generating the user metadata based on user activity at step 54A 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.
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 56A 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 56B, subtitle contents at step 56C, and any metadata included in the vertical blanking intervals at step 56D. 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 56E. Other translations between metadata formats can also be made. The generated metadata can be used in an update at step 62.
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.
Turning now to
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.
