Patent Description:
<CIT> relates to methods, systems, and media for presenting mobile content corresponding to media content.

The article "<NPL>, describes a novel semi-supervised learning strategy to address the problem of celebrity identification. The video context information is explored to facilitate the learning process based on the assumption that faces in the same video track share the same identity. Once a frame within a track is recognized confidently, the label can be propagated through the whole track, referred to as the confident track. More specifically, given a few static images and vast face videos, an initial weak classifier is trained and gradually evolves by iteratively promoting the confident tracks into the "labeled" set. The iterative selection process enriches the diversity of the "labeled" set such that the performance of the classifier is gradually improved. This learning theme may suffer from semantic drifting caused by errors in selecting the confident tracks. To address this issue, we propose to treat the selected frames as related samples-an intermediate state between labeled and unlabeled instead of labeled as in the traditional approach. To evaluate the performance, we construct a new dataset, which includes <NUM> static images and <NUM> face
tracks of <NUM> celebrities. Comprehensive evaluations on this dataset and a public video dataset indicate significant improvement of our approach over established baseline methods.

The following presents a simplified summary in order to provide a basic understanding of some novel implementations described herein. This summary is not an extensive overview, and it is not intended to identify key/critical elements or to delineate the scope thereof. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.

The disclosed architecture enables the identification of entities such as people and content (e.g., text, logos, etc.) in live broadcasts (e.g., streaming content (e.g., video) of live events) and non-live presentations (e.g., movies) in realtime using at least recognition processes (e.g., face recognition). The realtime identification can be achieved for television broadcasts of live events as well as television shows and movies, and is sufficiently lightweight (fewer instructions for simpler and faster execution) to be handled by a system with modest resources (e.g., local client devices, portable computing devices, cell phones, etc.).

The disclosed architecture scales to both the live broadcasts and non-live television and computer-based shows and movies to recognize entities in the video frames and supplement the video presentation with information/content from network sources such as restricted (login enabled) and non-restricted information sources (e.g., websites) of the Internet, as well as from personal storage of a user and enterprise information sources.

More specifically, this can be accomplished by extracting live data related to a live event (where live data comprises realtime information generated as the event is occurring and/or in close time proximity to when the event is occurring). With respect to people entities, filtering can be performed to identify the named entities (e.g., people) from the extracted live data, and trending topics discovered as relate to the named entities, as associated with the live event. Multiple images (e.g., photos) of the named entities captured under different conditions (e.g., lighting, one or more suitable poses to enable quality recognition, etc.) can be utilized. The images are then processed to extract and learn facial features (train one or more models), and facial recognition is then performed on faces in the video (e.g., live) using the trained model(s).

The architecture also finds applicability to recognition processing of family members, relatives, and/or friends captured in personal movies/photos during social events such as reunions, gatherings, etc. The identification of such people can be recognized based on personal models trained for such categories of people. For example, it is commonplace for families and the families of relatives to grow in size and be dispersed across geographical locations such that "keeping up" with children and grandchildren can be difficult. The capture of family images of cousins, relatives, etc., and access to such images then enables the recognition of faces and background content for such members while reviewing past events (e.g., reunions) via videos, photos, and so on. The information presented with the video/photo during review can include what the person is doing now, biographical information, etc., received from social networks and other suitable information sources.

For example, the architecture can be implemented as a system, comprising: an access component configured to access information related to an event captured in a video; a collection component configured to collect training data from the information and used for identification of entities in the video; a training component configured to train a model using the training data; a recognition component configured to perform facial recognition processing of the entities in the video to identify a specific entity, the facial recognition processing performed using the model; and, a content component configured to obtain content relevant to the specific entity for presentation with the specific entity.

The architecture can be implemented as a method, comprising: accessing information related to viewing of a video and as relates to an event; collecting training data from the information for identification of an entity in the video; training a model using the training data; performing recognition processing of entities in the video to identify the entity, the recognition processing performed using the model; and presenting content relevant to the entity.

To the accomplishment of the foregoing and related ends, certain illustrative aspects are described herein in connection with the following description and the annexed drawings. These aspects are indicative of the various ways in which the principles disclosed herein can be practiced and all aspects and equivalents thereof are intended to be within the scope of the claimed subject matter. Other advantages and novel features will become apparent from the following detailed description when considered in conjunction with the drawings.

Entity recognition (e.g., face, textual) in live broadcasts is a daunting challenge. With respect to the entities being people, one approach to guarantee precision for a realtime event is to manually tag people (images thereof) scene-by-scene; however, this technique is not scalable to the potential millions of faces of people routinely shown in broadcasts.

The disclosed architecture scales to videos that include both live broadcasts and non-live television shows and movies to recognize entities in realtime in the video frames and supplement the video presentation with content network sources such as restricted and non-restricted information sources of the Internet, as well as from personal storage of a user and enterprise information sources. This can be accomplished by extracting live data related to an event, filtering named entities from the extracted live data, finding the trending topic based on named entity, fetching multiple images under different conditions for each person, extracting and learning facial features from multiple photos fetched, and recognizing faces in the live video on the basis of the trained data.

The architecture enables realtime entity recognition (e.g., faces of people) on-screen during live broadcasted events as well in TV shows and movies in realtime by attaching context obtained from different sources about the event, and retrieving training content (e.g., images for person faces) from a search engine. The different sources can be online, offline, structured, and/or unstructured.

The architecture is now described with respect to the live broadcast of an event. An event is defined as including activities occurring just before and just after the event as well as performance of the event. For example, a sporting event includes activities captured (covered) before the game begins and follow-up ("re-cap" as to post-game interview of players, coaches, playback of specific plays during the event, etc.) after the game is over. Description of a non-live implementation is described hereinafter. With respect to non-live events such as movie re-runs, the event includes activities captured (covered) before the movie begins such as a host person talking briefly about actors in the movie, and awards presented, and follow-up ("re-cap" as to post-movie commentary, etc.) after the movie is over.

The live broadcast process begins with live data (information) extraction from various data sources such as websites, online television program guides, online user messaging traffic, and so on. Data sources that typically accommodate a sufficient amount of user messaging traffic about different topics, such as social media websites, are particularly useful. Accordingly, user messages related to the live event are extracted from the one or more data sources in realtime with the event (while the activities of the event are actually occurring), and within a previously determined time window. The time window computed for any given event can be determined based on the kind of event and duration of the event, for example. Additionally, structured and unstructured search engine results information can also be extracted to determine the people-of-interest likely to be at the event.

After obtaining user messaging content (e.g., text) about the event, the user messaging content is processed through a named entity recognition system that generates a list of named entities and associated popularity, as the names occur in the content, and entity type (e.g., person, organization, location, etc.). When looking for people, named entities that do not refer to people names can be filtered out.

Using the above set of named entities, the architecture then finds the named entities that are trending (e.g., in social media networks) at the moment the event is occurring. The trending information provides context surrounding the live content of the video and further enables the generation of a ranked list of the people entities. The trending and ranked list generation process can be performed at regular time intervals to identify changes in trending topics related to the live event.

Model training comprises the use of a search engine to query for images of each person in the ranked list of named people entities. Fetching the multiple images is part of gathering the training data, and includes images of the people in different lighting conditions and from different angles, as well as other poses that could enhance the quality of the training data. Quality enhancement can also comprise removing images that include more than one face (e.g., group photos) and images with no people faces, leaving the labeled set of final images as the training data. The labeled set of photographs for each person (e.g., celebrity, public figure, etc.) is then processed as training data through a face recognition system to create a model of extracted and learned facial features from the images.

The individual frames of the live broadcasted event (e.g., on television) are input to the face recognition system. When the face recognizer produces an output from the list of people with which the recognizer was trained, and with a confidence level higher than a predetermined threshold, the frame that includes the image is tagged with the person's name.

The architecture is lightweight in that a small number (e.g., twenty) of images per named entity are sufficient to train the face recognition system and identify the corresponding entity with high precision. Since this process utilizes only a few images to be stored in memory, the system can learn and recognize faces quickly without high processor or memory requirements. Additionally, rather than processing every frame, the architecture can process every nth frame (e.g., every 25th frame), since items on screen do not change that frequently (e.g., every few seconds).

For non-live events such as pre-recorded television shows, the architecture operates slightly differently in that the list of people can be gathered from an online knowledge source that lists the on-screen and off-screen names of actors/celebrities. The image search is then performed for both the actor as well as the actor's on-screen name, using query refinements to get images of the actor in the same general makeup as on the show. These images, labeled with indicia such as the actor's name, are then input to the face recognition system for training, as in the live event description described herein. Additionally, user messages previously communicated on social media websites during the premiere of the movie or show episodes can be obtained to find mentioned entities.

As indicated herein, the architecture can be extended to process entities other than human faces. For example, image recognition can be implemented to identify textual information, logo designs, scenery, points of interest, etc., using image recognition algorithms in place of face recognition.

The disclosed architecture exhibits technical effects related to program execution, reduced memory requirements, and improved usability. For example, given the lightweight nature of the architecture, less memory is needed and thus, caching becomes more resource affordable thereby enabling an improved user experience. Additionally, less code to be executed translates into faster code execution and the improved user experience.

Reference is now made to the drawings, wherein like reference numerals are used to refer to like elements throughout. It may be evident, however, that the novel implementations can be practiced without these specific details. In other instances, well known structures and devices are shown in block diagram form in order to facilitate a description thereof. The intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the claimed subject matter.

<FIG> illustrates a system <NUM> for the automatic recognition of entities in media-captured events in accordance with the disclosed architecture. The system <NUM> includes an access component <NUM> configured to access information <NUM> (from various accessible sources <NUM>) as relates to an event <NUM> captured/presented in a video <NUM> and one or more entities <NUM> (e.g., people, logos, text, audio, other content and media types, etc.) shown in the video <NUM>.

The access component <NUM> can comprise one or more applications that interface to various accessible sources <NUM> (e.g., accessible by the public in general, sources that require login credentials, etc.) of information such as social media networks, enterprise networks, publicly-accessible websites, personal networks and storage devices, and so on. The access component <NUM> is capable of identifying the particular event <NUM> occurring in realtime or soon to occur, and then extracting the information <NUM> relevant to the event <NUM> (e.g., live broadcast event), movies, show re-runs, and/or other types of presentation media.

The access component <NUM> can further be configured to access event identifying data <NUM> from the various accessible sources <NUM> such as event program sources that include, but are not limited to, media communications sources (e.g., television, radio, web-based program sources, program guides, websites, etc.) that are readily available, and that typically provide such event identifying data <NUM>. The event identifying data <NUM> enables the access component <NUM> to obtain the relevant information <NUM> for the event <NUM> and any of the entities <NUM> associated with the event <NUM>.

For example, the event identifying data <NUM> of a sporting event can be obtained from the various accessible sources <NUM> that comprise television programming sources which indicate when the sporting event will take place, the location of the event, and possible entities such as sportscasters and team members of the teams participating in the sporting event. Thus, given this event identifying data <NUM>, it can be inferred that certain entities such as people, will be present in the video <NUM>, and it also can be inferred that specific pieces of content such as player statistics, biographies, etc., related to these people would be desirable for viewing in combination with the event <NUM>.

A collection component <NUM> is provided and configured to derive and output training data <NUM> from the information <NUM>, and use the training data <NUM> ultimately for identification of entities <NUM> in the video <NUM> via a trained model <NUM>. Accordingly, a training component <NUM> is provided and configured to train the model <NUM> using the training data <NUM>. The training component <NUM> is configured to train the model <NUM> using a set of tagged (labeled) images of the entities <NUM> to learn facial features of the entities <NUM>. In other words, where the event is known, it can also be known with high probability the identity of the people who will likely be part of the event. Thus, given this information, images of the people likely to be at or part of the event can be obtained and tagged for training the model <NUM>.

A recognition component <NUM> is provided and configured to perform recognition processing (e.g., facial) of the entities <NUM> in the video <NUM> to, for example, identify a specific entity (e.g., person) or multiple entities (e.g., sportscaster(s), players, coaches, etc.) where the recognition processing is performed using the trained model <NUM>.

A content component <NUM> is provided and configured to obtain content <NUM> relevant to the specific entity for presentation with the specific entity and/or video <NUM>. Once recognition processing is completed for given entities, the entities are then known, and the content component <NUM> then searches and retrieves content <NUM> relevant to the entity, event, etc., from the various accessible sources <NUM>, and facilitates presentation of the relevant content <NUM> on the device <NUM> presenting the video <NUM>, or other device(s) that may or may not be presenting (playing) the video <NUM>.

As previously indicated, the event <NUM> can be a live broadcast event captured via the video <NUM> and the video <NUM> is streamed (via the web to a computing device and/or television) for viewing on first device (e.g., the device <NUM>) while the event <NUM> is occurring. The relevant content <NUM> can then be presented on the first device (e.g., the device <NUM>) while the video <NUM> is being viewed on the first device (device <NUM>).

For example, when using a device such as a desktop computer, the content <NUM> can be presented in a content window next to the video window in which the video <NUM> is being presented. When using a smart television, similar side-by-side presentation of the video <NUM> and content <NUM> can be achieved.

In these scenarios, the content <NUM> can be configured to change dynamically based on the entity being viewed in the video <NUM>. For example, if the quarterback of a football team in a football event (being broadcast live) is the focus of the video, content relevant to the quarterback can be presented next to the video view in which the quarterback is shown as the predominant entity in the frames of the video. When the video then transitions from the quarterback back to the overall team play, the content <NUM> can be automatically changed to then show content relevant to the teams, such as division standing(s), game statistics, etc. Thus, the system <NUM> operates in realtime to provide content in realtime based on specific scenes and entities shown in the video <NUM>.

The disclosed architecture is suitably robust and capable to enable the video to be shown on a first device and the content on another device. Thus, where the event is a live event captured via the video and the video is streamed for viewing on a first device while the event is occurring, the relevant content can be presented on one or more other devices while the video is being viewed on the first device. In this scenario, a user can be watching the event on the television, while the relevant content is presented on a tablet computing device being held by the user.

The access component <NUM> can be configured to access the information <NUM> according to a predetermined time window, where the time window can be determined based on at least one of, kind of the event or duration of the event. In other words, the information <NUM> will likely be of the desired quality and quantity just prior (e.g., a few hours) to the event occurring rather than days or even weeks before the event. For example, where the various accessible sources <NUM> include social media, where user interest (user messages) in various events tends to trend with interest at certain times, usually of greater interest just prior to the event <NUM> occurring, and just after the occurrence of the event <NUM>, with less interest at a time (e.g., weeks, months) well before and well after the event occurrence.

<FIG> illustrates an alternative system <NUM> for the automatic recognition of entities in media-captured events in accordance with the disclosed architecture. The system <NUM> comprises the components and capabilities of the system <NUM> of <FIG>, as well as additional components, such as a named entity recognition component <NUM> and a trend component <NUM>. The named entity recognition component <NUM> is provided and configured to process social media messages, and output one or more of named entities, entity popularity parameters, and entity type information. The trend component <NUM> is provided and configured to access trend information that indicates entities that are trending in correlation to the event, and from which context of the event is inferred.

In operation, the access component <NUM> accesses the information <NUM> (from the various accessible sources <NUM>) as relates to the event <NUM> captured/presented in the video <NUM> and one or more entities <NUM> (e.g., people, logos, text, audio, other content and media types, etc.) shown in the video <NUM>.

The access component <NUM> can comprise one or more applications that interface to the various accessible sources <NUM>. The access component <NUM> identifies the particular event <NUM> occurring in realtime (e.g., broadcast live event, movie, etc.) or soon to occur, and then extracts the information <NUM> relevant to the event <NUM> (e.g., live broadcast event), movies, show re-runs, and/or other types of presentation media.

In the context of a broadcast live event, when the live event is being screened on television channels (e.g., the Oscars), live information related to the event is extracted. The sources for this information can be social media sites that provide a suitable amount of user message traffic (e.g., Twitter™). In operation, during the event, user messages related to the Oscars are extracted in realtime from the corresponding social media website, within a previously determined time window. The time window can be made to depend on the kind of event and the event duration. Additionally, structured and unstructured data can be extracted from knowledge graphs, websites that maintain updated data stores of movies, television, and celebrity content, etc., to determine the people who are expected for this event. In another example, if the event is a live sports event, websites that typically store and update sports-related information such as player and team statistics, player names, etc., can be accessed.

The access component <NUM> can further be configured to access the event identifying data <NUM> from the various accessible sources <NUM> such as event program sources that include, but are not limited to, media communications sources (e.g., television, radio, web-based program sources, program guides, websites, etc.) that are readily available, and that typically provide such event identifying data <NUM>. The event identifying data <NUM> enables the access component <NUM> to obtain the relevant information <NUM> for the event <NUM> and any of the entities <NUM> associated with the event <NUM>.

After obtaining all the content (e.g., text) from user messages about the event, this user content is processed by named entity recognition component <NUM>. The output of the named entity recognition component <NUM> is a list of named entities and attributes <NUM>, where the associated attributes can include, but are not limited to, entity popularity as the entity name occurs in the content (e.g., text) and entity type (e.g., Person name, Organization name, and/or Location name). Named entities that do not refer to people names can be filtered out. Put another way, the named entity recognition component <NUM> processes social media messages, and outputs one or more of named entities, entity popularity parameters, and entity type information.

For the above set of named entities (and attributes) <NUM>, the trend component <NUM> finds the named entities trending at the current time in social media networks. This provides information about the context for the live content of the video, and produces a ranked list <NUM> of entities. This step can be performed at regular intervals to keep up with changes in trending topics. Put another way, the trend component <NUM> is provided and configured to access trend information that indicates entities that are trending in correlation to the event, and from which context of the event is inferred.

From the top set of named people (the named entities and attributes <NUM>) obtained, a search engine (of the various accessible sources <NUM>) is queried by the collection component <NUM> to retrieve images for each person. Fetching multiple images (e.g., twenty, thirty, etc.) assists in gathering the training data <NUM> with the images (facial poses) in different lighting conditions and from different angles. Each image (e.g., photograph) can be processed through a face detection system to filter out images showing more than one face. This removes images such as group photos, which could eventually be problematic in computing specific faces from which to learn features and characteristics. Filtering can also be performed to remove images where no faces are detected.

The remaining processes are essentially the same as in the system <NUM> of <FIG> where, with respect to training the recognition component <NUM>, the collection component <NUM> derives and outputs the training data <NUM> from the information <NUM> to train the model <NUM> using the set of tagged (labeled) images of the entities <NUM> to learn facial features of the entities <NUM>. The recognition component <NUM> performs recognition processing (e.g., facial) of the entities <NUM> to identify a specific entity (e.g., person) or multiple entities (e.g., sportscaster(s), players, coaches, etc.), using the trained model <NUM>.

The content component <NUM> obtains the content <NUM> relevant to the specific entity for presentation with the specific entity and/or video <NUM>, the content <NUM> searched and retrieved from the various accessible sources <NUM>. The relevant content <NUM> can then be presented on the device <NUM> that presents the video <NUM>, or other device(s) that may or may not be presenting (playing) the video <NUM>.

As before, the content <NUM> can be changed dynamically based on the entity being viewed in the video <NUM>. Thus, the system <NUM> operates in realtime to provide content in realtime based on specific scenes and entities shown in the video <NUM>.

In accordance with the system <NUM> of <FIG>, the disclosed architecture is suitably robust and capable to enable the video to be shown on a first device and the content on another device. Thus, where the event is a live event captured via the video and the video is streamed for viewing on a first device while the event is occurring, the relevant content can be presented on one or more other devices while the video is being viewed on the first device. In this scenario, a user can be watching the event on the television, while the relevant content is presented on a tablet computing device being held by the user.

Additionally, the access component <NUM> can be configured to access the information <NUM> according to a predetermined time window, where the time window can be determined based on at least one of, kind of the event or duration of the event.

It is to be understood that in the disclosed architecture, certain components may be reoriented, combined, omitted, and additional components may be included. For example, due to the lightweight nature of the architecture, all components in the system <NUM> of <FIG>, except the sources <NUM>, can be implemented in a local device (e.g., a laptop). Similarly, all components in the system <NUM> of <FIG>, except the sources <NUM>, can be implemented in a local device (e.g., a laptop). Thus, caching in memory can be realized for fast execution of recognition processing and content presentation.

<FIG> illustrates a view <NUM> that shows presentation of the video <NUM> and relevant content <NUM> in a device display <NUM>. A video window <NUM> is shown in which the video <NUM> (e.g., movie, live broadcast, television program, etc.) is presented. The video window <NUM> can include various controls and indicators <NUM> such as forward, pause, fast forward, reverse, fast reverse, speaker volume control, and so on, commonly associated with user controls in viewing a movie.

Face recognition processing identifies the face <NUM> of a person <NUM> in the video <NUM> (as indicated in a recognition bounding box <NUM>, which may or may not be visible to the user while viewing the video <NUM>). Once the person <NUM> is identified, a query can be composed and processed by a search engine for the relevant content <NUM>. The relevant content <NUM> returned from the search can comprise any variety of media types, such as text (Text1 and Text2), images (Image <NUM> and Image2) of the person <NUM>, links (Links) that enable navigation by the user to websites or other content sources. The content <NUM> can be presented in a scrollable content window to enable review of content above or below the currently viewed content.

As indicated herein, image recognition on one or more frames of the video can be employed for logo identification, and which if used in combination with face recognition of a person in the same image, results in the content <NUM> comprising both content about the person <NUM> and content associated with the logo (not shown).

<FIG> illustrates a system <NUM> of entity recognition and content distribution among multiple client personal devices <NUM>. Here, three client personal devices (Device1, Device2, and Device3) such as tablet computers, laptop computers, desktop computers, smart phones, and the like, are being used by users in combination with watching the video <NUM> of a live broadcast on a television <NUM>. Any of the personal devices <NUM> and the television <NUM> can be implemented with system <NUM> or system <NUM>, and the associated methodologies as described herein.

Thus, in one illustrative operation, the television <NUM> performs face recognition in the video <NUM> of the live broadcast and content presentation of the relevant content <NUM>. The users of the person devices <NUM> can choose to view only the content <NUM> (as in Device1), only the video <NUM> (as in Device2), or both the video <NUM> and the content <NUM> (as in Device <NUM>).

In a second illustrative operation for devices without the capability of the disclosed architecture, Device1 operates to perform face recognition of the live broadcast video <NUM> presented by the television <NUM>, and then communicates (serves) the content <NUM> to the television <NUM> while also presenting the content <NUM> on the Device!. Device2 and Device3 can then receive the video <NUM>, the content <NUM>, or different items of the content <NUM>, as can be user selected, for example.

In yet another illustrative operation, the model created by Device1 can then be shared to the other devices, Device2 and Device3, rather than these devices being required to generate their own models or that lack the capability to generate models.

It can also be the case the one or more models can be generated before the event based on prior similar events and served (downloaded) to client devices. For example, while sporting events may change location for week to week, the faces associated with teams, sportscaster, etc., are relatively stable and remain essentially the same. Thus, models can be generated for specific teams, and then combined when the two teams compete for rapid live recognition on client devices.

Where the various accessible sources <NUM> may include personal storage devices and content and/or social media content the user wishes not to be used, the disclosed architecture can optionally include a privacy component that enables the user to opt in or opt out of exposing personal information. The privacy component enables the authorized and secure handling of user information, such as tracking information, as well as personal information that may have been obtained, is maintained, and/or is accessible. The user can be provided with notice of the collection of portions of the personal information and the opportunity to opt-in or opt-out of the collection process. Consent can take several forms. Opt-in consent can impose on the user to take an affirmative action before the data is collected. Alternatively, opt-out consent can impose on the user to take an affirmative action to prevent the collection of data before that data is collected.

Included herein is a set of flow charts representative of exemplary methodologies for performing novel aspects of the disclosed architecture. While, for purposes of simplicity of explanation, the one or more methodologies shown herein, for example, in the form of a flow chart or flow diagram, are shown and described as a series of acts, it is to be understood and appreciated that the methodologies are not limited by the order of acts, as some acts may, in accordance therewith, occur in a different order and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all acts illustrated in a methodology may be required for a novel implementation.

<FIG> illustrates a method in accordance with the disclosed architecture. At <NUM>, information related to an event for viewing in a video is accessed. At <NUM>, training data is collected from the information for identification of an entity in the video. At <NUM>, recognition processing of entities in the video is performed to identify the entity. The recognition processing is performed using a trained model. At <NUM>, content relevant to the entity is presented.

The method can further comprise presenting the relevant content while the video is being viewed. The method can further comprise presenting the relevant content on a device from which the video is being viewed or on a device different than the device from which the video is being viewed. The method can further comprise accessing the information, collecting the training data, performing the recognition processing, and presenting the content while the video is being viewed. The method can further comprise accessing the information, collecting the training data, performing the recognition processing, and presenting the content while the video captures a live event.

The method can further comprise accessing the information from social media networks and according to a predetermined time window relative to the event. The method can further comprise performing name recognition processing to identify names in the information as obtained from social media. The method can further comprise accessing trending information as to named entities to infer context of the event. The method can further comprise presenting relevant content in association with recognized faces of the entities.

<FIG> illustrates an alternative method in accordance with the disclosed architecture. At <NUM>, information about a live event and about people associated with the live event is accessed. The live event and people are captured and broadcast in a video. At <NUM>, named entity recognition is performed on the information to obtain a list of named entities and associated attributes a related to the live event. At <NUM>, trends in social media messages associated with the live event are identified to compute a ranked list of the named entities. At <NUM>, images of the named entities in the ranked list are obtained and processed to output training data that comprises features of faces of people associated with the live event. At <NUM>, a model is trained using the training data. At <NUM>, face recognition processing of people in the video is performed based on the training model, to identify the named entities and return content relevant to the named entities.

The method can further comprise accessing of the information, performing the named entity recognition, identifying the trends, obtaining and processing the images, training of the model, performing the face recognition processing, and presenting the relevant content while the live event is occurring. The method can further comprise presenting the relevant content on a device from which the video is being viewed or on a device different than the device from which the video is being viewed. The method can further comprise presenting the relevant content in association with a named entity when the named entity is shown in the video.

As used in this application, the term "component" is intended to refer to a computer-related entity, either hardware, a combination of software and tangible hardware, software, or software in execution. For example, a component can be, but is not limited to, tangible components such as one or more microprocessors, chip memory, mass storage devices (e.g., optical drives, solid state drives, magnetic storage media drives, etc.), computers, and portable computing and computing-capable devices (e.g., cell phones, tablets, smart phones, etc.). Software components include processes running on a microprocessor, an object (a software entity that maintains state in variables and behavior using methods), an executable, a data structure (stored in a volatile or a non-volatile storage medium), a module (a part of a program), a thread of execution (the smallest sequence of instructions that can be managed independently), and/or a program.

By way of illustration, both an application running on a server and the server can be a component. One or more components can reside within a process and/or thread of execution, and a component can be localized on one computer and/or distributed between two or more computers. The word "exemplary" may be used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects or designs.

Referring now to <FIG>, there is illustrated a block diagram of a computing system <NUM> that executes the automatic recognition of entities in media-captured events in accordance with the disclosed architecture. Alternatively, or in addition, the functionally described herein can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application-Specific Standard Products (ASSPs), System-on-a-Chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), etc., where analog, digital, and/or mixed signals and other functionality can be implemented in a substrate.

In order to provide additional context for various aspects thereof, <FIG> and the following description are intended to provide a brief, general description of the suitable computing system <NUM> in which the various aspects can be implemented. While the description above is in the general context of computer-executable instructions that can run on one or more computers, those skilled in the art will recognize that a novel implementation also can be realized in combination with other program modules and/or as a combination of hardware and software.

The computing system <NUM> for implementing various aspects includes the computer <NUM> having microprocessing unit(s) <NUM> (also referred to as microprocessor(s) and processor(s)), a computer-readable storage medium (where the medium is any physical device or material on which data can be electronically and/or optically stored and retrieved) such as a system memory <NUM> (computer readable storage medium/media also include magnetic disks, optical disks, solid state drives, external memory systems, and flash memory drives), and a system bus <NUM>. The microprocessing unit(s) <NUM> can be any of various commercially available microprocessors such as single-processor, multiprocessor, single-core units and multi-core units of processing and/or storage circuits. Moreover, those skilled in the art will appreciate that the novel system and methods can be practiced with other computer system configurations, including minicomputers, mainframe computers, as well as personal computers (e.g., desktop, laptop, tablet PC, etc.), hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices.

The computer <NUM> can be one of several computers employed in a datacenter and/or computing resources (hardware and/or software) in support of cloud computing services for portable and/or mobile computing systems such as wireless communications devices, cellular telephones, and other mobile-capable devices. Cloud computing services, include, but are not limited to, infrastructure as a service, platform as a service, software as a service, storage as a service, desktop as a service, data as a service, security as a service, and APIs (application program interfaces) as a service, for example.

The system memory <NUM> can include computer-readable storage (physical storage) medium such as a volatile (VOL) memory <NUM> (e.g., random access memory (RAM)) and a non-volatile memory (NON-VOL) <NUM> (e.g., ROM, EPROM, EEPROM, etc.). A basic input/output system (BIOS) can be stored in the non-volatile memory <NUM>, and includes the basic routines that facilitate the communication of data and signals between components within the computer <NUM>, such as during startup. The volatile memory <NUM> can also include a high-speed RAM such as static RAM for caching data.

The system bus <NUM> provides an interface for system components including, but not limited to, the system memory <NUM> to the microprocessing unit(s) <NUM>. The system bus <NUM> can be any of several types of bus structure that can further interconnect to a memory bus (with or without a memory controller), and a peripheral bus (e.g., PCI, PCIe, AGP, LPC, etc.), using any of a variety of commercially available bus architectures.

The computer <NUM> further includes machine readable storage subsystem(s) <NUM> and storage interface(s) <NUM> for interfacing the storage subsystem(s) <NUM> to the system bus <NUM> and other desired computer components and circuits. The storage subsystem(s) <NUM> (physical storage media) can include one or more of a hard disk drive (HDD), a magnetic floppy disk drive (FDD), solid state drive (SSD), flash drives, and/or optical disk storage drive (e.g., a CD-ROM drive DVD drive), for example. The storage interface(s) <NUM> can include interface technologies such as EIDE, ATA, SATA, and IEEE <NUM>, for example.

One or more programs and data can be stored in the memory subsystem <NUM>, a machine readable and removable memory subsystem <NUM> (e.g., flash drive form factor technology), and/or the storage subsystem(s) <NUM> (e.g., optical, magnetic, solid state), including an operating system <NUM>, one or more application programs <NUM>, other program modules <NUM>, and program data <NUM>.

The operating system <NUM>, one or more application programs <NUM>, other program modules <NUM>, and/or program data <NUM> can include items and components of the system <NUM> of <FIG>, items and components of the system <NUM> of <FIG>, items and components of the view <NUM> of <FIG>, items and components of the system <NUM> of <FIG>, and the methods represented by the flowcharts of <FIG> and <FIG>, for example.

Generally, programs include routines, methods, data structures, other software components, etc., that perform particular tasks, functions, or implement particular abstract data types. All or portions of the operating system <NUM>, applications <NUM>, modules <NUM>, and/or data <NUM> can also be cached in memory such as the volatile memory <NUM> and/or non-volatile memory, for example. It is to be appreciated that the disclosed architecture can be implemented with various commercially available operating systems or combinations of operating systems (e.g., as virtual machines).

The storage subsystem(s) <NUM> and memory subsystems (<NUM> and <NUM>) serve as computer readable media for volatile and non-volatile storage of data, data structures, computer-executable instructions, and so on. Such instructions, when executed by a computer or other machine, can cause the computer or other machine to perform one or more acts of a method. Computer-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose microprocessor device(s) to perform a certain function or group of functions. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, or even source code. The instructions to perform the acts can be stored on one medium, or could be stored across multiple media, so that the instructions appear collectively on the one or more computer-readable storage medium/media, regardless of whether all of the instructions are on the same media.

Computer readable storage media (medium) exclude (excludes) propagated signals per se, can be accessed by the computer <NUM>, and include volatile and non-volatile internal and/or external media that is removable and/or non-removable. For the computer <NUM>, the various types of storage media accommodate the storage of data in any suitable digital format. It should be appreciated by those skilled in the art that other types of computer readable medium can be employed such as zip drives, solid state drives, magnetic tape, flash memory cards, flash drives, cartridges, and the like, for storing computer executable instructions for performing the novel methods (acts) of the disclosed architecture.

A user can interact with the computer <NUM>, programs, and data using external user input devices <NUM> such as a keyboard and a mouse, as well as by voice commands facilitated by speech recognition. Other external user input devices <NUM> can include a microphone, an IR (infrared) remote control, a joystick, a game pad, camera recognition systems, a stylus pen, touch screen, gesture systems (e.g., eye movement, body poses such as relate to hand(s), finger(s), arm(s), head, etc.), and the like. The user can interact with the computer <NUM>, programs, and data using onboard user input devices <NUM> such a touchpad, microphone, keyboard, etc., where the computer <NUM> is a portable computer, for example.

These and other input devices are connected to the microprocessing unit(s) <NUM> through input/output (I/O) device interface(s) <NUM> via the system bus <NUM>, but can be connected by other interfaces such as a parallel port, IEEE <NUM> serial port, a game port, a USB port, an IR interface, short-range wireless (e.g., Bluetooth) and other personal area network (PAN) technologies, etc. The I/O device interface(s) <NUM> also facilitate the use of output peripherals <NUM> such as printers, audio devices, camera devices, and so on, such as a sound card and/or onboard audio processing capability.

One or more graphics interface(s) <NUM> (also commonly referred to as a graphics processing unit (GPU)) provide graphics and video signals between the computer <NUM> and external display(s) <NUM> (e.g., LCD, plasma) and/or onboard displays <NUM> (e.g., for portable computer). The graphics interface(s) <NUM> can also be manufactured as part of the computer system board.

The computer <NUM> can operate in a networked environment (e.g., IP-based) using logical connections via a wired/wireless communications subsystem <NUM> to one or more networks and/or other computers. The other computers can include workstations, servers, routers, personal computers, microprocessor-based entertainment appliances, peer devices or other common network nodes, and typically include many or all of the elements described relative to the computer <NUM>. The logical connections can include wired/wireless connectivity to a local area network (LAN), a wide area network (WAN), hotspot, and so on. LAN and WAN networking environments are commonplace in offices and companies and facilitate enterprise-wide computer networks, such as intranets, all of which may connect to a global communications network such as the Internet.

When used in a networking environment the computer <NUM> connects to the network via a wired/wireless communication subsystem <NUM> (e.g., a network interface adapter, onboard transceiver subsystem, etc.) to communicate with wired/wireless networks, wired/wireless printers, wired/wireless input devices <NUM>, and so on. The computer <NUM> can include a modem or other means for establishing communications over the network. In a networked environment, programs and data relative to the computer <NUM> can be stored in the remote memory/storage device, as is associated with a distributed system. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers can be used.

The computer <NUM> is operable to communicate with wired/wireless devices or entities using the radio technologies such as the IEEE <NUM>. xx family of standards, such as wireless devices operatively disposed in wireless communication (e.g., IEEE <NUM> over-the-air modulation techniques) with, for example, a printer, scanner, desktop and/or portable computer, personal digital assistant (PDA), communications satellite, any piece of equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, news stand, restroom), and telephone. This includes at least Wi-Fi™ (used to certify the interoperability of wireless computer networking devices) for hotspots, WiMax, and Bluetooth™ wireless technologies. Thus, the communications can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices. Wi-Fi networks use radio technologies called IEEE <NUM>. 11x (a, b, g, etc.) to provide secure, reliable, fast wireless connectivity. A Wi-Fi network can be used to connect computers to each other, to the Internet, and to wire networks (which use IEEE <NUM>-related technology and functions).

The architecture can be implemented as a system, comprising: means for accessing information related to viewing of a video and as relates to an event; means for collecting training data from the information for identification of an entity in the video; means for training a model using the training data; means for performing recognition processing of entities in the video to identify the entity, the recognition processing performed using the model; and means for presenting content relevant to the entity.

Claim 1:
A system (<NUM>) for the automatic recognition of entities in media-captured events, comprising:
a hardware processor, and a memory device configured to store computer-executable instructions that when executed by the processor cause the processor to enable computer-executable components, the components comprising:
an access component (<NUM>) configured to access information related to entities including people in an event captured in a video;
an entity recognition component (<NUM>) configured to process social media messages, and output a set of named entities and attributes, wherein the attributes include entity popularity parameters, and entity type information;
a trend component (<NUM>) configured to access trend information that indicates entities that are trending in correlation to the event in social media networks, and from which information about the live content of the video is inferred, and to produce a ranked list of entities, for the set of named entities and attributes;
a collection component (<NUM>) configured to collect training data for the set of named entities and attributes by querying a search engine to retrieve images for each entity in the ranked list of entities, the training data used for identification of the entities in the video;
a training component (<NUM>) configured to train a model using the training data that comprises a set of tagged images of the entities to learn facial features of the entities;
a recognition component (<NUM>) configured to receive video frames of the event and to perform facial recognition processing of the entities in the video frames to identify a specific entity, the facial recognition processing performed using the model; and
a content component (<NUM>) configured to obtain content relevant to the specific entity for presentation with the video of the specific entity.