Patent Description:
Users of client devices increasingly capture video data via image capture devices included in various client devices and share the captured video with other users. For example, through an application associated with an online system executing on a client device, a user of the client device distributes video data captured via the client device, or otherwise obtained via the client device, to other users of the online system. To encourage user engagement, many applications allow a user of the client device to modify video data obtained by the client device and subsequently present the modified video data.

For example, various applications allow users to apply filters to video data obtained by a client device or to overlay text or images onto portions of video data obtained by the client device. However, conventional applications for modifying video data receive modifications to the video data and extract information from the video data to perform the modifications when the video data is rendered. For example, to overlay images on a face detected in the video data, a conventional application applies one or more detection methods to the video data while the video data is rendered and modifies the video data by overlaying the images on regions of the video data from which faces are detected. As methods for extracting information from video data are computationally intensive, extracting the information while rendering the video data and performing the modifications may more rapidly drain resources of a client device, such as power stored in a battery or other power supply of the client device. Patent publications <CIT> and <CIT> discuss information that is useful for understanding the background of the invention.

The present invention is directed to methods and computer programs according to the appended claims. A client device, such as a smartphone or a tablet computer, includes an image capture device configured to capture video data. A video effects application executing on the client device receives the captured video data and augments the captured data or modifies the video data when the captured video data is presented by a display device of the client device. For example, the video effects application overlays additional images or text on the captured video data when presenting the captured video data. The video effects application may augment or otherwise modify the video data when is the video data captured, or may modify the video data at a time subsequent to a time when the video data was captured.

To perform various modifications to the video data, the video effects application often extracts information from the captured video data and uses the extracted information to modify the captured video data. For example, the video effects application detected one or more faces in the captured video data and applies text or images to the video data based on locations of the detected faces in various frames of the captured video data. To more efficiently use a battery of the client device, the video effects application extracts information from the captured video data and stores the extracted information as metadata associated with the captured video data. In various embodiments, the video effects application provides the captured video data and metadata associated with the captured video data to an online system, allowing the online system to subsequently provide the captured video data and associated metadata to other client devices for rendering. For example, a user of the client device captures video via the client device and provides instructions to the video effects application to communicate the captured video and associated metadata to the online system; the user may also specify one or more other users of the online system to receive the captured video data and associated metadata to the online system, and the online system communicates the captured video data and associated metadata to client devices associated with the other users. The video effects application also stores information identifying modifications to the captured video data to be performed when rendering the captured video data. For example, information identifying one or more modifications to the captured video data is stored in association with times of the captured video data when the modifications are to be performed. The information describing the one or more modifications may also be provided to the online system, which may subsequently provide the information describing the one or more modifications to client devices associated with other users along with the captured video data and metadata associated with the captured video data.

When the captured video data is subsequently rendered for presentation, the video effects application provides the captured video data, the metadata associated with the captured video data, and the information identifying the one or more modifications to the captured video data to the renderer. Based on the metadata associated with the captured video data and the identified one or more modifications to the captured video data, the renderer performs the one or more modifications to the captured video data when the captured video data is rendered for display. For example, the renderer overlays text or graphics on one or more frames of the captured video data corresponding to one or more identified times of the video data based on locations within the one or more frames of detected faces or other objects included in the metadata associated with the captured video data.

If the captured video data and associated metadata is communicated to the online system, the online system may communicate the captured video data and associated metadata to an additional client device associated with another user of the online system. The other user of the online system may provide information describing one or more modifications to a video effects application or to a renderer of the additional client device, causing the renderer or video effects application of the additional client device to perform the described modifications to the captured video data using the metadata associated with the captured video data and present the modified captured video data to the other user of the client device. Using the metadata associated with the captured video data to perform the modifications to the captured video data without the renderer or the video effects application of the additional client device also extracting information from the captured video data, conserving computing and power resources of the additional client device.

Separately extracting information from the captured video data and performing the modifications to the video data allows the client device to more efficiently use its battery. As methods for extracting information from the captured video data are computationally intensive, extracting information from the captured video data and storing the extracted information as metadata associated with the captured video data allows the metadata associated with the captured video data to be provided to another client device along with the captured video data, allowing the other client device to leverage the metadata associated with the captured video data when modifying the video data during presentation rather than again extracting the information from the captured video data to modify the captured video data during presentation. Additionally, storing information extracted from the captured video data and using the stored information to modify the captured video data during presentation allows presentation of higher-quality modified captured video data. For example, using stored information extracted from the captured video data to modify the captured video data allows the modifications to the captured video data to be free of compression artifacts from compressing the captured video data. Further, modifying the captured video data based on stored information extracted from the captured video data may allow the video effects application to perform more complex modifications to the captured video data than if information were extracted from the captured video data while the captured video data is modified.

Embodiments according to the invention are in particular disclosed in the attached claims. All the above-mentioned objects can be achieved by the features as defined by the independent claims. Further enhancements are characterized by the dependent claims. At least one of the above embodiments provides one or more solutions to the problems and disadvantages with the background art. Other technical advantages of the present disclosure will be readily apparent to one skilled in the art from the following description and claims. Various embodiments of the present application obtain only a subset of the advantages set forth. Any claimed embodiment may be technically combined with any other claimed embodiment or embodiments.

In an embodiment according to independent claim <NUM> of the invention, a method, in particular a computer-implemented method, comprises:.

In an embodiment according to independent claim <NUM> of the invention, a method comprises:.

In an embodiment according to independent claim <NUM> of the invention, a computer program product, comprising a non-transitory computer readable storage medium having instructions encoded thereon that, when executed by a processor, cause the processor to:.

Further embodiments are set out in the dependent claims.

The figures depict various exemplary implementations for purposes of illustration only. One skilled in the art will readily recognize from the following discussion that alternative implementations of the structures and methods illustrated herein may be employed without departing from the principles described herein, wherein the scope of the invention is only defined by the appended claims.

<FIG> is a block diagram of a system environment <NUM> for an online system <NUM>. The system environment <NUM> shown by <FIG> comprises one or more client devices <NUM>, a network <NUM>, one or more third-party systems <NUM>, and the online system <NUM>. In alternative configurations, different and/or additional components may be included in the system environment <NUM>. For example, the online system <NUM> is a social networking system, a content sharing network, a messaging server, or another system providing content to users.

The client devices <NUM> are one or more computing devices capable of receiving user input as well as transmitting and/or receiving data via the network <NUM>. In one embodiment, a client device <NUM> is a conventional computer system, such as a desktop or a laptop computer. Alternatively, a client device <NUM> may be a device having computer functionality, such as a personal digital assistant (PDA), a mobile telephone, a smartphone, a smartwatch, or another suitable device. A client device <NUM> is configured to communicate via the network <NUM>. In one embodiment, a client device <NUM> executes an application allowing a user of the client device <NUM> to interact with the online system <NUM>. For example, a client device <NUM> executes a browser application to enable interaction between the client device <NUM> and the online system <NUM> via the network <NUM>. In another embodiment, a client device <NUM> interacts with the online system <NUM> through an application programming interface (API) running on a native operating system of the client device <NUM>, such as IOS® or ANDROID™.

As further described below in conjunction with <FIG>, in various embodiments a client device <NUM> includes an image capture device capable of capturing video data and an application for modifying the captured video data. For example, an application executing on the client device <NUM> allows a user of the client device <NUM> to overlay images or text onto portions of video data captured by an image capture device or otherwise obtained by the client device <NUM>. In some embodiments, the application for modifying the video data provides additional functionality. For example, the application also allows a user to exchange content (e.g., messages) with other users of the online system <NUM>. Alternatively, an additional application allows the user to communicate with users of the online system <NUM> and the additional application obtains the modified video data from the application that modified the video data. To modify obtained video data while conserving resources (e.g., power supply resources), the application extracts information from the video data when the video data is obtained and stores metadata describing the extracted information in association with the video data. After receiving information describing one or more modifications to the video data, the application (or another application) uses the metadata associated with the video data to perform the described one or more modifications. This allows the video data to be modified without extracting information from the video data when the video data is received and again when the video data is modified. An example client device <NUM> is further described below in conjunction with <FIG>, while extraction of information from video data and modification of the video data is further described below in conjunction with <FIG> and <FIG>.

The client devices <NUM> are configured to communicate via the network <NUM>, which may comprise any combination of local area and/or wide area networks, using both wired and/or wireless communication systems. In one embodiment, the network <NUM> uses standard communications technologies and/or protocols. For example, the network <NUM> includes communication links using technologies such as Ethernet, <NUM>, worldwide interoperability for microwave access (WiMAX), <NUM>, <NUM>, code division multiple access (CDMA), digital subscriber line (DSL), etc. Examples of networking protocols used for communicating via the network <NUM> include multiprotocol label switching (MPLS), transmission control protocol/Internet protocol (TCP/IP), hypertext transport protocol (HTTP), simple mail transfer protocol (SMTP), and file transfer protocol (FTP). Data exchanged over the network <NUM> may be represented using any suitable format, such as hypertext markup language (HTML) or extensible markup language (XML). In some embodiments, all or some of the communication links of the network <NUM> may be encrypted using any suitable technique or techniques.

One or more third party systems <NUM> may be coupled to the network <NUM> for communicating with the online system <NUM>, which is further described below in conjunction with <FIG>. In one embodiment, a third party system <NUM> is an application provider communicating information describing applications for execution by a client device <NUM> or communicating data to client devices <NUM> for use by an application executing on the client device. In other embodiments, a third party system <NUM> provides content or other information for presentation via a client device <NUM>. A third party system <NUM> may also communicate information to the online system <NUM>, such as advertisements, content, or information about an application provided by the third party system <NUM>.

Various third party systems <NUM> provide content to users of the online system <NUM>. For example, a third party system <NUM> maintains pages of content that users of the online system <NUM> may access through one or more applications executing on a client device <NUM>. The third party system <NUM> may provide content items to the online system <NUM> identifying content provided by the online system <NUM> to notify users of the online system <NUM> of the content provided by the third party system <NUM>. For example, a content item provided by the third party system <NUM> to the online system <NUM> identifies a page of content provided by the online system <NUM> that specifies a network address for obtaining the page of content.

<FIG> is a block diagram of an architecture of the online system <NUM>. The online system <NUM> shown in <FIG> includes a user profile store <NUM>, a content store <NUM>, an action logger <NUM>, an action log <NUM>, an edge store <NUM>, a content selection module <NUM>, and a web server <NUM>. In other embodiments, the online system <NUM> may include additional, fewer, or different components for various applications. Conventional components such as network interfaces, security functions, load balancers, failover servers, management and network operations consoles, and the like are not shown so as to not obscure the details of the system architecture.

Each user of the online system <NUM> is associated with a user profile, which is stored in the user profile store <NUM>. A user profile includes declarative information about the user that was explicitly shared by the user and may also include profile information inferred by the online system <NUM>. In one embodiment, a user profile includes multiple data fields, each describing one or more attributes of the corresponding social networking system user. Examples of information stored in a user profile include biographic, demographic, and other types of descriptive information, such as work experience, educational history, gender, hobbies or preferences, location and the like. A user profile may also store other information provided by the user, for example, images or videos. In certain embodiments, images of users may be tagged with information identifying the social networking system users displayed in an image, with information identifying the images in which a user is tagged stored in the user profile of the user. A user profile in the user profile store <NUM> may also maintain references to actions by the corresponding user performed on content items in the content store <NUM> and stored in the action log <NUM>.

Each user profile includes user identifying information allowing the online system <NUM> to uniquely identify users corresponding to different user profiles. For example, each user profile includes an electronic mail ("email") address, allowing the online system <NUM> to identify different users based on their email addresses. However, a user profile may include any suitable user identifying information associated with users by the online system <NUM> that allows the online system <NUM> to identify different users.

While user profiles in the user profile store <NUM> are frequently associated with individuals, allowing individuals to interact with each other via the online system <NUM>, user profiles may also be stored for entities such as businesses or organizations. This allows an entity to establish a presence on the online system <NUM> for connecting and exchanging content with other social networking system users. The entity may post information about itself, about its products or provide other information to users of the online system <NUM> using a brand page associated with the entity's user profile. Other users of the online system <NUM> may connect to the brand page to receive information posted to the brand page or to receive information from the brand page. A user profile associated with the brand page may include information about the entity itself, providing users with background or informational data about the entity.

The content store <NUM> stores objects that each represents various types of content. Examples of content represented by an object include a page post, a status update, a photograph, a video, a link, a shared content item, a gaming application achievement, a check-in event at a local business, a brand page, or any other type of content. Online system users may create objects stored by the content store <NUM>, such as status updates, photos tagged by users to be associated with other objects in the online system <NUM>, events, groups or applications. In some embodiments, objects are received from third-party applications or third-party applications separate from the online system <NUM>. In one embodiment, objects in the content store <NUM> represent single pieces of content, or content "items. " Hence, online system users are encouraged to communicate with each other by posting text and content items of various types of media to the online system <NUM> through various communication channels. This increases the amount of interaction of users with each other and increases the frequency with which users interact within the online system <NUM>.

In various embodiments, the content store <NUM> includes video data captured by a client device <NUM> and metadata associated with the video data by the client device <NUM>. As further described below in conjunction with <FIG>, a client device <NUM> extracts information from the captured video data and stores the metadata in association with the captured video data. The client device <NUM> may communicate the video data and associated metadata to the online system <NUM>, which stores the video data and associated metadata in the content store <NUM>. In various embodiments, the online system <NUM> receives information identifying a user of the online system <NUM> along with the video data and associated metadata and stores the information identifying the user in association with the video data and with the metadata associated with the video data. As further described below in conjunction with <FIG>, the online system <NUM> may retrieve video data and metadata associated with the video data from the content store <NUM> and provide the video data and associated metadata to client devices <NUM> associated with other users of the online system <NUM> in response to receiving a request from the user who provided the video data to the online system <NUM> to provide the video data to other users.

One or more content items included in the content store <NUM> include content for presentation to a user and a bid amount. The content is text, image, audio, video, or any other suitable data presented to a user. In various embodiments, the content also specifies a page of content. For example, a content item includes a landing page specifying a network address of a page of content to which a user is directed when the content item is accessed. The bid amount is included in a content item by a user and is used to determine an expected value, such as monetary compensation, provided by an advertiser to the online system <NUM> if content in the content item is presented to a user, if the content in the content item receives a user interaction when presented, or if any suitable condition is satisfied when content in the content item is presented to a user. For example, the bid amount included in a content item specifies a monetary amount that the online system <NUM> receives from a user who provided the content item to the online system <NUM> if content in the content item is displayed. In some embodiments, the expected value to the online system <NUM> of presenting the content from the content item may be determined by multiplying the bid amount by a probability of the content of the content item being accessed by a user.

Various content items may include an objective identifying an interaction that a user associated with a content item desires other users to perform when presented with content included in the content item. Example objectives include: installing an application associated with a content item, indicating a preference for a content item, sharing a content item with other users, interacting with an object associated with a content item, or performing any other suitable interaction. As content from a content item is presented to online system users, the online system <NUM> logs interactions between users presented with the content item or with objects associated with the content item. Additionally, the online system <NUM> receives compensation from a user associated with content item as online system users perform interactions with a content item that satisfy the objective included in the content item.

Additionally, a content item may include one or more targeting criteria specified by the user who provided the content item to the online system <NUM>. Targeting criteria included in a content item request specify one or more characteristics of users eligible to be presented with the content item. For example, targeting criteria are used to identify users having user profile information, edges, or actions satisfying at least one of the targeting criteria. Hence, targeting criteria allow a user to identify users having specific characteristics, simplifying subsequent distribution of content to different users.

In one embodiment, targeting criteria may specify actions or types of connections between a user and another user or object of the online system <NUM>. Targeting criteria may also specify interactions between a user and objects performed external to the online system <NUM>, such as on a third party system <NUM>. For example, targeting criteria identifies users that have taken a particular action, such as sent a message to another user, used an application, joined a group, left a group, joined an event, generated an event description, purchased or reviewed a product or service using an online marketplace, requested information from a third party system <NUM>, installed an application, or performed any other suitable action. Including actions in targeting criteria allows users to further refine users eligible to be presented with content items. As another example, targeting criteria identifies users having a connection to another user or object or having a particular type of connection to another user or object.

The action logger <NUM> receives communications about user actions internal to and/or external to the online system <NUM>, populating the action log <NUM> with information about user actions. Examples of actions include adding a connection to another user, sending a message to another user, uploading an image, reading a message from another user, viewing content associated with another user, and attending an event posted by another user. In addition, a number of actions may involve an object and one or more particular users, so these actions are associated with the particular users as well and stored in the action log <NUM>.

The action log <NUM> may be used by the online system <NUM> to track user actions on the online system <NUM>, as well as actions on third party systems <NUM> that communicate information to the online system <NUM>. Users may interact with various objects on the online system <NUM>, and information describing these interactions is stored in the action log <NUM>. Examples of interactions with objects include: commenting on posts, sharing links, checking-in to physical locations via a client device <NUM>, accessing content items, and any other suitable interactions. Additional examples of interactions with objects on the online system <NUM> that are included in the action log <NUM> include: commenting on a photo album, communicating with a user, establishing a connection with an object, joining an event, joining a group, creating an event, authorizing an application, using an application, expressing a preference for an object ("liking" the object), and engaging in a transaction. Additionally, the action log <NUM> may record a user's interactions with advertisements on the online system <NUM> as well as with other applications operating on the online system <NUM>. In some embodiments, data from the action log <NUM> is used to infer interests or preferences of a user, augmenting the interests included in the user's user profile and allowing a more complete understanding of user preferences.

The action log <NUM> may also store user actions taken on a third party system <NUM>, such as an external website, and communicated to the online system <NUM>. For example, an e-commerce website may recognize a user of an online system <NUM> through a social plug-in enabling the e-commerce website to identify the user of the online system <NUM>. Because users of the online system <NUM> are uniquely identifiable, e-commerce websites, such as in the preceding example, may communicate information about a user's actions outside of the online system <NUM> to the online system <NUM> for association with the user. Hence, the action log <NUM> may record information about actions users perform on a third party system <NUM>, including webpage viewing histories, advertisements that were engaged, purchases made, and other patterns from shopping and buying. Additionally, actions a user performs via an application associated with a third party system <NUM> and executing on a client device <NUM> may be communicated to the action logger <NUM> by the application for recordation and association with the user in the action log <NUM>.

In one embodiment, the edge store <NUM> stores information describing connections between users and other objects on the online system <NUM> as edges. Some edges may be defined by users, allowing users to specify their relationships with other users. For example, users may generate edges with other users that parallel the users' real-life relationships, such as friends, co-workers, partners, and so forth. Other edges are generated when users interact with objects in the online system <NUM>, such as expressing interest in a page on the online system <NUM>, sharing a link with other users of the online system <NUM>, and commenting on posts made by other users of the online system <NUM>.

An edge may include various features each representing characteristics of interactions between users, interactions between users and objects, or interactions between objects. For example, features included in an edge describe a rate of interaction between two users, how recently two users have interacted with each other, a rate or an amount of information retrieved by one user about an object, or numbers and types of comments posted by a user about an object. The features may also represent information describing a particular object or user. For example, a feature may represent the level of interest that a user has in a particular topic, the rate at which the user logs into the online system <NUM>, or information describing demographic information about the user. Each feature may be associated with a source object or user, a target object or user, and a feature value. A feature may be specified as an expression based on values describing the source object or user, the target object or user, or interactions between the source object or user and target object or user; hence, an edge may be represented as one or more feature expressions.

The edge store <NUM> also stores information about edges, such as affinity scores for objects, interests, and other users. Affinity scores, or "affinities," may be computed by the online system <NUM> over time to approximate a user's interest in an object or in another user in the online system <NUM> based on the actions performed by the user. A user's affinity may be computed by the online system <NUM> over time to approximate the user's interest in an object, in a topic, or in another user in the online system <NUM> based on actions performed by the user. Computation of affinity is further described in <CIT>, <CIT>, <CIT>, and <CIT>. Multiple interactions between a user and a specific object may be stored as a single edge in the edge store <NUM>, in one embodiment. Alternatively, each interaction between a user and a specific object is stored as a separate edge. In some embodiments, connections between users may be stored in the user profile store <NUM>, or the user profile store <NUM> may access the edge store <NUM> to determine connections between users.

The content selection module <NUM> selects one or more content items for communication to a client device <NUM> to be presented to a user. Content items eligible for presentation to the user are retrieved from the content store <NUM> or from another source by the content selection module <NUM>, which selects one or more of the content items for presentation to the viewing user. A content item eligible for presentation to the user is a content item associated with at least a threshold number of targeting criteria satisfied by characteristics of the user or is a content item that is not associated with targeting criteria. In various embodiments, the content selection module <NUM> includes content items eligible for presentation to the user in one or more selection processes, which identify a set of content items for presentation to the user. For example, the content selection module <NUM> determines measures of relevance of various content items to the user based on characteristics associated with the user by the online system <NUM> and based on the user's affinity for different content items. Based on the measures of relevance, the content selection module <NUM> selects content items for presentation to the user. As an additional example, the content selection module <NUM> selects content items having the highest measures of relevance or having at least a threshold measure of relevance for presentation to the user. Alternatively, the content selection module <NUM> ranks content items based on their associated measures of relevance and selects content items having the highest positions in the ranking or having at least a threshold position in the ranking for presentation to the user.

Content items eligible for presentation to the user may include content items associated with bid amounts. The content selection module <NUM> uses the bid amounts associated with ad requests when selecting content for presentation to the user. In various embodiments, the content selection module <NUM> determines an expected value associated with various content items based on their bid amounts and selects content items associated with a maximum expected value or associated with at least a threshold expected value for presentation. An expected value associated with a content item represents an expected amount of compensation to the online system <NUM> for presenting the content item. For example, the expected value associated with a content item is a product of the ad request's bid amount and a likelihood of the user interacting with the content item. The content selection module <NUM> may rank content items based on their associated bid amounts and select content items having at least a threshold position in the ranking for presentation to the user. In some embodiments, the content selection module <NUM> ranks both content items not associated with bid amounts and content items associated with bid amounts in a unified ranking based on bid amounts and measures of relevance associated with content items. Based on the unified ranking, the content selection module <NUM> selects content for presentation to the user. Selecting content items associated with bid amounts and content items not associated with bid amounts through a unified ranking is further described in <CIT>.

For example, the content selection module <NUM> receives a request to present a feed of content to a user of the online system <NUM>. The feed may include one or more content items associated with bid amounts and other content items, such as stories describing actions associated with other online system users connected to the user, which are not associated with bid amounts. The content selection module <NUM> accesses one or more of the user profile store <NUM>, the content store <NUM>, the action log <NUM>, and the edge store <NUM> to retrieve information about the user. For example, information describing actions associated with other users connected to the user or other data associated with users connected to the user are retrieved. Content items from the content store <NUM> are retrieved and analyzed by the content selection module <NUM> to identify candidate content items eligible for presentation to the user. For example, content items associated with users who not connected to the user or stories associated with users for whom the user has less than a threshold affinity are discarded as candidate content items. Based on various criteria, the content selection module <NUM> selects one or more of the content items identified as candidate content items for presentation to the identified user. The selected content items are included in a feed of content that is presented to the user. For example, the feed of content includes at least a threshold number of content items describing actions associated with users connected to the user via the online system <NUM>.

In various embodiments, the content selection module <NUM> presents content to a user through a newsfeed including a plurality of content items selected for presentation to the user. One or more content items may also be included in the feed. The content selection module <NUM> may also determine the order in which selected content items are presented via the feed. For example, the content selection module <NUM> orders content items in the feed based on likelihoods of the user interacting with various content items.

The web server <NUM> links the online system <NUM> via the network <NUM> to the one or more client devices <NUM>, as well as to the one or more third party systems <NUM>. The web server <NUM> serves web pages, as well as other content, such as JAVA®, FLASH®, XML and so forth. The web server <NUM> may receive and route messages between the online system <NUM> and the client device <NUM>, for example, instant messages, queued messages (e.g., email), text messages, short message service (SMS) messages, or messages sent using any other suitable messaging technique. A user may send a request to the web server <NUM> to upload information (e.g., images or videos) that are stored in the content store <NUM>. Additionally, the web server <NUM> may provide application programming interface (API) functionality to send data directly to native client device operating systems, such as IOS®, ANDROID™, WEBOS® or BlackberryOS.

<FIG> is a block diagram of one embodiment of an architecture of a client device <NUM>. The client device <NUM> shown in <FIG> includes an image capture device <NUM>, a video effects application <NUM>, a renderer <NUM>, and a display device <NUM>. In other embodiments, the client device <NUM> may include additional, fewer, or different components for various applications. Further, various components of the client device <NUM> may provide various combinations of the functionality further described below in some embodiments.

The image capture device <NUM> is any device capable of capturing image or video data. Example image capture devices <NUM> include one or more cameras, one or more video cameras, or any other device capable of capturing image data. In some embodiments, the image capture device <NUM> includes one or more filters. Similarly, the image capture device <NUM> may include optics for altering light used to generate image or video data in various embodiments. Different client devices <NUM> may have image capture devices <NUM> having different characteristics (e.g., resolution of captured image data, shutter control, frame rates, focal lengths, diameter of an entrance pupil capturing light for generating video or image data). While <FIG> shows a client device <NUM> having a single image capture device <NUM>, in various embodiments, client devices <NUM> may include multiple image capture devices <NUM>.

The video effects application <NUM> comprises instructions that, when executed by a processor of the client device <NUM>, extracts information from video data received from the image capture device <NUM> or from any other suitable source. To extract information from video data, the video effects application <NUM> may apply one or more methods to the video data, with various methods extracting different information from the video data. For example, one or more methods applied by the video effects application <NUM> detect objects, such as faces, from various frames of the video data. As another example, one or more methods applied by the video effects application <NUM> determine optical flow vectors describing movement of objects or other components of the video data based on various frames of the video data. In various embodiments, the video effects application <NUM> may extract any suitable information from video data. In other examples, information extracted from video data tracks one or more objects across various frames of the video data (e.g., through application of one or more particle filters to the video data) or identifies changes in one or more objects detected in the video data (e.g., a change in expression of a face detected in the video data). Additionally, information extracted from video data by the video effects application <NUM> may be determined based on settings specified by a user of the client device <NUM>, based on information specified by the video effects application <NUM>, information specified by another application executing on the client device <NUM>, or based on information from any other suitable source. This allows customization of information extracted from video data by the video effects application in various implementations. As further described below in conjunction with <FIG>, the video effects application <NUM> stores information extracted from video data as metadata associated with the video data.

Additionally, the video effects application <NUM> receives information identifying modifications to video data. Information identifying modifications to video data may be received from a user, received from another application, received from an online system <NUM>, or received from a third party system <NUM>. Examples of modifications to video data identified to video effects application <NUM> include application of one or more filters to the video data, overlying text on one or more portions of the video data, overlaying images on one or more portions of the video data, altering a playback speed of the video data, modifying audio included in one or more portions of the video data, identifying movement of objects in the video data, modifying shading or coloring of one or more frames of the video data, tracking objects within the video data (e.g., application of particle filters), identifying changes in one or more objects in the video data (e.g., identifying a change) and any other suitable modification. One or more modifications to the video data may identify data obtained by the client device <NUM> when the video data is presentation that affects how the video data is modified; for example, a modification to the video data identifies one or more inputs received by the client device <NUM> when the video data is presented and instructions for altering image or text data overlaid on the video data based on the received one or more inputs. In other examples, data from an accelerometer of a client device <NUM>, from a position sensor of the client device <NUM>, from a microphone of the client device <NUM>, or from any other suitable component of the client device <NUM> may be identified and used to determine how the video data is modified when presented by the client device <NUM>. Additionally, information identifying modifications to video data may specify one or more characteristics of the metadata associated with the video data for performing a modification; for example, information describing a modification to the video data may specify a threshold measure of similarity to a particular object so an identified modification is performed if an object identified by the metadata has at least the threshold measure of similarity to the particular object, but the identified modification is not performed if the object identified by the metadata has less than the threshold measure of similarity to the particular object. Different modifications to video data may be identified to the video effects application <NUM> in various embodiments, so different implementations of the video effects application <NUM> may identify different modifications to video data. As further described below in conjunction with <FIG>, the video effects application <NUM> stores information identifying one or more modifications to the video data in association with the video data.

The renderer <NUM> receives video data, the metadata associated with the video data, and information describing modifications to the video data from the video effects application <NUM>. For purposes of illustration, <FIG> shows the renderer <NUM> as separate from the video effects application <NUM>; however, in various embodiments, the renderer <NUM> and the video effects application <NUM> may be combined into a single component. As further described below in conjunction with <FIG>, when rendering the video data, the renderer <NUM> modifies the video data by performing the modifications described by the information and renders the modified video data. To perform one or more of the modifications to the video data, the renderer <NUM> accesses the metadata and uses information extracted from the video data and described by the metadata. For example, if a modification to the video data identifies an image to overlay on an object in the video data (e.g., a face in the video data), the renderer <NUM> identifies frames of the video data including the object from the metadata and locations within the identified frames having the object and overlays the image on the locations within the identified frames that have the object. Hence, the renderer <NUM> leverages the metadata describing information extracted from the video data to subsequently modify the video data without again extracting information from the video data.

The display device <NUM> included in the client device <NUM> presents image data or video data to a user of the client device <NUM>. Examples of the display device <NUM> include a liquid crystal display (LCD), an organic light emitting diode (OLED) display, an active matrix liquid crystal display (AMLCD), or any other suitable device. Different client devices <NUM> may have display devices <NUM> with different characteristics. For example, different client devices <NUM> have display devices <NUM> with different display areas, different resolutions, or differences in other characteristics.

<FIG> is a flowchart of one embodiment of a method for modifying video data obtained by a client device <NUM>. In other embodiments, the method may include different and/or additional steps than those shown in <FIG>. Additionally, steps of the method may be performed in different orders than the order described in conjunction with <FIG> in various embodiments.

An image capture device <NUM> included in a client device <NUM> captures <NUM> video data. For example, a camera included in the client device <NUM> captures <NUM> video data. In various embodiments, the video data captured <NUM> by the image capture device <NUM> has any suitable resolution or any other suitable characteristics. In other embodiments, the client device <NUM> may capture <NUM> video data from any suitable source. For example, video data captured by the client device <NUM> is video data that the client device <NUM> receives from an online system <NUM>, from a third party system <NUM>, from another client device <NUM>, or from any other suitable source.

A video effects application <NUM> executing on the client device <NUM> receives the video data captured <NUM> by the image capture device <NUM> of the client device <NUM> and extracts <NUM> information from the captured video data. The video effects application <NUM> extracts <NUM> any suitable information from the captured video data in various embodiments. To extract <NUM> information from the captured video data and using the extracted information to modify the captured video data. For example, the video effects application <NUM> applies one or more processes to the captured video data to detect objects, such as faces, included in the captured video data; the video effects application <NUM> may identify locations within one or more frames of the video data of the detected objects. As another example, the video effects application <NUM> applies one or more processes to the captured video data to determine optical flow vectors describing motion of objects, or any other suitable component, in the captured video data. In various embodiments, the video effects application <NUM> may extract <NUM> any suitable characteristics of or information about the captured video data.

The video effects application <NUM> stores <NUM> the information extracted <NUM> from the captured video data as metadata associated with the captured video data. In various embodiments, the extracted information may be stored <NUM> in any suitable format in association with the captured video data. For example, if the extracted information includes objects detected in the captured video data, metadata stored <NUM> in association with the captured video data includes times within the video data where various objects, or identifiers of frames of the video data where the various objects, were detected along with identifiers of the detected objects; locations within various frames where objects were detected may also be included in the stored metadata. As another example, optical flow vectors determined from various frames are stored <NUM> in association with identifiers of frames of the captured video data from which the optical flow vectors were determined.

The video effects application <NUM> communicates the captured video data and the metadata associated with the captured video data to an online system <NUM> in some embodiments. The online system <NUM> stores the captured video data from the client device <NUM> and the metadata associated with the captured video data in some embodiments. For example, the video effects application <NUM> executing on the client device <NUM> communicates information identifying a user of the online system <NUM> associated with the client device <NUM> in association with the captured video data and the metadata associated with the captured video data to the online system <NUM>, which stores the captured video data and associated metadata in association with the user. As another example, the client device <NUM> communicates identifiers of additional users of the online system <NUM>, the captured video data, and the metadata associated with the captured video data to the online system <NUM>, which communicates the captured video data and metadata associated with the captured video data to additional client devices <NUM> associated with the additional users corresponding to the identifiers.

Additionally, the video effects application <NUM> receives <NUM> information identifying one or more modifications to the captured video data and stores <NUM> the received information identifying modifications to the captured video data in association with the captured video data. For example, the video effects application <NUM> receives <NUM> an identifier of a filter to apply to the captured video data from a user along with identifiers of one or more portions (e.g., identifiers of frames, time intervals) of the captured video data to which the filter is applied and stores <NUM> the identifier of the filter and identifiers of the one or more portions of the captured video data to which the filter is applied in association with the captured video data. As another example, the video effects application <NUM> receives <NUM> text or image data to overlay on one or more portions of the captured data and stores <NUM> the text or image data in association with identifiers of the one or more portions (e.g., identifiers of frames, time intervals) of the captured video data to where the text or image data is overlaid. The received <NUM> information may identify objects detected from the captured video data over which text or image data is overlaid in some embodiments. In some embodiments, the information identifying modifications to the captured video data is communicated from the client device <NUM> to the online system <NUM>. For example, the online system <NUM> receives information identifying a user of the online system <NUM> along with the information identifying modifications to the captured video data, and the online system <NUM> stores the information identifying the modifications in association with the user and with the captured video data and metadata associated with the captured video data. As another example, the online system <NUM> receives identifiers of additional users from the client device <NUM> along with the information identifying modifications to the captured video data, and the online system <NUM> communicates the captured video data, the metadata associated with the captured video data, and the information identifying modifications to the captured video data to additional client devices <NUM> associated with the additional users.

To modify the captured data based on the stored <NUM> information identifying the one or more modifications, when the captured video data is subsequently presented, the video effects application <NUM> provides the captured video data, the metadata associated with the captured video data, and the information identifying one or more modifications to the captured video data to a renderer <NUM>. In some embodiments, the renderer <NUM> is a component of the video effects application <NUM>. Alternatively, the renderer <NUM> is a separate component of the client device <NUM>; for example, the renderer <NUM> is a separate application executing on the client device <NUM> or is a hardware or firmware component of the client device <NUM>. When the captured video data is presented or stored, the renderer <NUM> modifies <NUM> the captured video data based on the identified one or more modifications and the metadata associated with the captured video data. For example, information associated with the captured video data identifies a portion of the captured video data where text or an image is overlaid, so the renderer <NUM> overlays the text or the image on the identified portion of the captured video data when the identified portion of the captured video data is rendered for presentation by a display device <NUM> of the client device <NUM> or is rendered for storage by the client device <NUM> or by an online system <NUM> or a third party system <NUM>. If an identified modification to the captured video data identifies an object within the video data that is to be modified, the renderer <NUM> identifies portions of the video data including the identified object from the metadata associated with the captured video data and modifies the object as specified by the information when the portions of the video data including the identified object are presented. Hence, the renderer <NUM> uses the metadata associated with the captured video data to identify portions of the captured video data that are modified based on the stored information and to modify the identified portions of the captured video data when rendering the captured video data for presentation.

Storing metadata describing information extracted <NUM> from captured video data in association with the captured video data and subsequently leveraging the metadata associated with the captured video data to modify <NUM> the captured video data when it is presented or stored allows the client device <NUM> to more efficiently consume power, allowing the client device <NUM> to reduce draw from a battery or other power supply when modifying the captured video data. As methods for extracting <NUM> information from the captured video data are computationally intensive, extracting <NUM> information from the captured video data and storing <NUM> the extracted information as metadata associated with the captured video data allows subsequent modification of the captured video data by another client device <NUM> that receives the captured video data to leverage the metadata associated with the captured video data to modify the captured video data when rendering modified captured video data rather than again extracting the information from the captured video data after receiving the captured video data from the client device <NUM> or from the online system <NUM>. Additionally, storing <NUM> information extracted from the captured video data and using the stored information to modify <NUM> the captured video data during presentation or storage increases a quality of the modifications to the captured video data. For example, modifying <NUM> captured video data using stored metadata associated with the captured video data allows modifications to the captured video data to be free of artifacts from compressing the captured video data.

Further, modifying <NUM> the captured video data based on stored metadata describing information extracted from the captured video data may allow more complex modifications of the captured video data than if information were extracted from the captured video data while the captured video data is modified. For example, modifying <NUM> the captured video data based on metadata associated with the captured video data allows one or more modifications to the captured video data to account for data obtained by a client device <NUM> when the modified captured video data is presented. As an example, a client device <NUM> modifying <NUM> the captured video data differently modifies the video data based on different inputs from a user of the client device <NUM> (e.g., interactions with an input device of the client device <NUM> when the captured video data is presented) or based on different information captured by one or more components of the client device <NUM> (e.g., accelerometers, position sensors, etc.) while the client device <NUM> presents the captured video data. Hence, if the captured video data, metadata associated with the captured video data, and information identifying modifications to the captured video data are provided to additional client devices <NUM>, different additional client devices <NUM> may differently perform one or more modifications to the captured video data during presentation based on differences in data obtained by different additional client devices <NUM> during presentation of the captured video data. Additionally, modifying <NUM> the captured video data using metadata associated with the captured video data allows multiple modifications to portions of the captured video data based on metadata associated with portions of the captured video data. For example, if metadata associated with the captured video data identifies portions of the video data including a particular object or changes to the particular object, one or more images are overlaid onto the identified portions of the captured video data and audio of the captured video data is modified during the identified portions. Using the metadata associated with the captured video data simplifies performance of multiple modifications to various portions of the captured video data based on characteristics or content of the various portions of the captured video data.

While <FIG> describes extraction of information from video data captured <NUM> by an image capture device <NUM> of a client device, the method described above in conjunction with <FIG> may be applied to video data obtained by the client device <NUM> from any suitable source. For example, the client device <NUM> receives video data from another client device <NUM>, from an online system <NUM>, or from a third party system <NUM>, and the video effects application <NUM> extracts <NUM> information from the video data and stores <NUM> the extracted information as metadata associated with the video data, as further described above. The video effects application <NUM> receives <NUM> information describing one or more modifications to the video data and stores <NUM> the received information in association with the video data. When the video data is subsequently presented or stored, the renderer modifies the video data as specified by the received information based on the metadata associated with the video data, as further described above. Hence, video data obtained by the client device <NUM> from the image capture device <NUM> or obtained from any suitable source may be modified as described above in conjunction with <FIG>.

<FIG> is a process flow diagram of one embodiment of an architecture for modifying video data obtained by a client device <NUM>. In the example of <FIG>, an image capture device <NUM> of a client device <NUM> captures video data and provides <NUM> the captured video data to a video effects application <NUM> executing on the client device <NUM>. As further described above in conjunction with <FIG>, the video effects application <NUM> extracts information from the captured video data and stores the extracted information as metadata associated with the captured video data. Additionally, the video effects application <NUM> receives information identifying one or more modifications to the captured video data and stores the received information identifying modifications to the captured video data in association with the captured video data, as further described above in conjunction with <FIG>. The video effects application <NUM> provides the captured video data, the metadata associated with the captured video data, and the information identifying modifications to the captured video data to a renderer <NUM>.

The renderer <NUM> modifies the captured video data by performing the modifications specified by the received information to portions of the captured video data identified by the received information. When modifying the captured video data, the renderer <NUM> accesses the metadata associated with the captured video data and uses the information extracted from the captured video data and described by the metadata to perform one or more of the modifications. The renderer <NUM> provides the modified captured video data to a display device <NUM> of the client device <NUM> for presentation or to a storage device included in the client device <NUM> for storage. Hence, the architecture described in conjunction with <FIG> separates extraction of information from the captured video data from modification of the captured video data based on the extracted information, allowing modification of the captured video data to reduce power consumption by the client device <NUM>.

<FIG> is an interaction diagram of one embodiment of a method for providing video data obtained by a client device <NUM> and modifications to the video data to another client device <NUM> that performs the modifications and presents the modified video data. In other embodiments, the method may include different and/or additional steps than those shown in <FIG>. Additionally, steps of the method may be performed in different orders than the order described in conjunction with <FIG> in various embodiments.

A client device 110A obtains <NUM> video data and extracts <NUM> information from the video data when the video data is obtained <NUM>. As further described above in conjunction with <FIG>, the video data may be captured by an image capture device <NUM> included in the client device 110A, received from another client device <NUM>, received from a third party system <NUM>, received from an online system <NUM>, retrieved from a storage device included in the client device 110A, or obtained <NUM> from any other suitable source. While the client device 110A obtains <NUM> the video data, the client device 110A extracts <NUM> information from the video data. As further described above in conjunction with <FIG>, the client device 110A applies one or more processes to the video data to extract any suitable information from the video data (e.g., objects, optical flow vectors, changes to one or more objects, locations within one or more frames of the video data of objects, etc.). The client device 110A stores <NUM> the extracted information as metadata associated with the video data. For example, if the extracted information includes objects detected in the captured video data, metadata stored <NUM> in association with the video data includes times within the video data where various objects, or identifiers of frames of the video data where the various objects, were detected along with identifiers of the detected objects; locations within various frames where objects were detected may also be included in the stored metadata.

Additionally, the client device 110A receives <NUM> information identifying one or more modifications to the video data and stores. For example, the client device 110A receives <NUM> an identifier of a filter to apply to the captured video data from a user along with identifiers of one or more portions (e.g., identifiers of frames, time intervals) of the captured video data to which the filter is applied. As another example, the client device 110A receives <NUM> text or image data to overlay on one or more portions of the captured data (e.g., identifiers of frames, time intervals) of the captured video data to where the text or image data is overlaid. The received information may identify objects detected from the captured video data over which text or image data is overlaid in some embodiments. As described above in conjunction with <FIG>, the received information may identify one or more objects or characteristics of one or more portions of the video data and one or more modifications to perform to portions of the video data including the one or more objects or having the one or more characteristics.

The client device 110A provides <NUM> the video data, the metadata associated with the captured video data, and the information identifying the one or more modifications to the video data to the online system <NUM>, which stores <NUM> the video data, the metadata associated with the video data, and the information identifying the one or more modifications to the video data. For example, the client device 110A provides <NUM> information identifying a user of the online system <NUM> associated with the client device 110A in association with the video data, with the metadata associated with the video data, and with the information identifying the one or more modifications the video data to the online system <NUM>, which stores <NUM> the video data, associated metadata, and information identifying the one or more modifications to the video data in association with the user.

The online system <NUM> provides <NUM> the video data, the metadata associated with the video data, and the information identifying the one or more modifications to the video data to an additional client device 110B. In various embodiments, the additional client device 110B is associated with a user of the online system <NUM> provided <NUM> to the online system <NUM> along with the video data, the metadata associated with the video data, and the information identifying the one or more modifications to the video data. Alternatively, the online system <NUM> receives information identifying an additional user of the online system <NUM> from a user associated with the client device 110A, identifies an additional client device 110B associated with the additional user from information the online system <NUM> maintains for the additional user, and provides <NUM> the video data, the metadata associated with the video data, and the information identifying one or more modifications to the video data to the additional client device 110B.

When the additional client device 110A receives the video data, the metadata associated with the video data, and the information identifying one or more modifications to the video data, the additional client data uses the metadata to perform <NUM> one or more of the identified modifications the video data while rendering the video data and presents <NUM> the modified video data via a display device <NUM>. Using the metadata associated with the video data to perform <NUM> one or more of the identified modifications while rendering the video data allows the additional client device 110B to reduce draw from a battery or other power supply when modifying the video data. As described above in conjunction with <FIG>, extracting information from video data is computationally intensive, and using the metadata to perform <NUM> one or more of the modifications to the video data allows the additional client device 110B to leverage the metadata associated with the video data to modify the video data during rendering without again extracting information for performing the modifications from the video data after receiving the captured video data.

The foregoing description of the embodiments has been presented for the purpose of illustration; it is not intended to be exhaustive or to limit the patent rights to the precise forms disclosed. Persons skilled in the relevant art can appreciate that many modifications and variations are possible in light of the above disclosure.

Some portions of this description describe the embodiments in terms of algorithms and symbolic representations of operations on information. These algorithmic descriptions and representations are commonly used by those skilled in the data processing arts to convey the substance of their work effectively to others skilled in the art. These operations, while described functionally, computationally, or logically, are understood to be implemented by computer programs or equivalent electrical circuits, microcode, or the like. Furthermore, it has also proven convenient at times, to refer to these arrangements of operations as modules, without loss of generality. The described operations and their associated modules may be embodied in software, firmware, hardware, or any combinations thereof.

Embodiments may also relate to an apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, and/or it may comprise a general-purpose computing device selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a non-transitory, tangible computer readable storage medium, or any type of media suitable for storing electronic instructions, which may be coupled to a computer system bus. Furthermore, any computing systems referred to in the specification may include a single processor or may be architectures employing multiple processor designs for increased computing capability.

Embodiments may also relate to a product that is produced by a computing process described herein. Such a product may comprise information resulting from a computing process, where the information is stored on a non-transitory, tangible computer readable storage medium and may include any embodiment of a computer program product or other data combination described herein.

Claim 1:
A method comprising:
obtaining (<NUM>, <NUM>) video data at a client device (110A);
extracting (<NUM>, <NUM>), at the client device (110A), information from the video data by the client device (110A) applying one or more processes to the video data when the video data is obtained at the client device (110A);
storing (<NUM>, <NUM>), at the client device (110A), the extracted information as metadata associated with the video data;
receiving (<NUM>, <NUM>), at the client device (110A), information identifying one or more modifications to the video data;
storing (<NUM>), at the client device, the received information identifying modifications to the video data in association with the video data;
providing (<NUM>), at the client device (110A), the video data, the metadata, and the identified modifications to an online system (<NUM>);
storing (<NUM>), at the online system (<NUM>), the video data, the metadata, and the identified modifications; and
providing (<NUM>), by the client device (110A), at the online system (<NUM>), the video data, the metadata, and the identified modifications to a plurality of additional client devices (110B) for display, each of the plurality of additional client devices (110B) configured to modify the video data differently during presentation of the video data based on differences in data captured by one or more components of each of the plurality of additional client devices (110B).