Patent Application
20210272600
The present disclosure generally relates to the field of video editing, and more particularly to video editing on portable computing devices.
A popular feature of many portable computing devices, such as laptops, tablets, smartphones, media players, and wearable devices (e.g., watches, eyeglasses and other head-mounted displays, etc.), among others, is a camera for capturing photographs and video. With such devices at their immediate disposal, users can record more of their experiences than ever before. Users often like to edit these photos and videos to share with friends and family. However, conventional devices do not support video editing or only provide a rudimentary set of editing tools (e.g., trimming segments at the beginning or end of a video, splitting a large video into smaller clips, or joining several video clips into a larger video). Conventional video editing software typically requires users to overcome a steep learning curve. Even professional film editors need to spend a lot of time and effort to edit video, which may not be practical for users making personal videos of a generally non-commercial and ephemeral nature. In addition, form factors for portable computing devices may inhibit or preclude more complex video editing techniques. For example, conventional video editing software is usually only available for desktops, workstations, servers, and the like because of the large amounts of processing, memory, storage, network, power, and other resources the software needs for operation; portable computing devices may not have enough space to accommodate these amounts of computing resources because of the relatively small size of the portable devices. Portable computing devices also usually comprise relatively small touchscreens that can make fine-tuned edits difficult.
The present disclosure will describe various embodiments with reference to the drawings, in which:
Systems and methods in accordance with various embodiments of the present disclosure may overcome one or more of the aforementioned and other deficiencies experienced in conventional approaches for editing a video on computing devices (e.g., servers, workstations, desktops, laptops, tablets, smart phones, media players, wearable devices, etc.). In some embodiments, a computing device can receive a video, such as by a camera built into the computing device capturing the video or the computing device receiving the video from another electronic device (e.g., as an attachment to an electronic message, as a download from a remote storage source, as a transferred file from a USB device, etc.). The computing device can display a graphical user interface (GUI) for editing the video, such as to add, edit, and/or remove text, drawings, virtual objects (e.g., stickers, Bitmoji, emoticons, etc.), uniform resource locators (URLs), and/or other data to the video.
In some embodiments, the GUI can also allow the computing device to incorporate certain cuts, transitions, or other video effects, such as dissolves (e.g., fade-ins and fade-outs), wipes (e.g., a video frame or set of video frames replacing another frame or set of frames by traveling from one side of the frame to another or with a special shape), close-ups and long shots, L-cuts and J-cuts (e.g., an audio segment playing before the matching video and vice versa), and other types of edits into the video or a portion of the video. In one embodiment, the GUI can include user interface elements for selecting a clip of the video and re-sampling the clip using one or more sampling patterns to generate a new clip. For example, the GUI can include a video scrubber (sometimes also referred to as a video slider) comprising a selection bar and a selection slider (sometimes also referred to as a handle). The selection bar may represent the full length of the video, and the selection slider may represent the portion of the video (or video clip) which the computing device applies a specific cut, transition, or other video effect (e.g., a sampling pattern). The computing device can compute one or more histograms that define the number of frames of the original clip to sample over various time intervals to generate the new video clip. In addition or alternatively, the computing device can identify the function y=f(x) corresponding to the sampling pattern(s), where y can represent the number of frames to sample and x can represent time. The computing device can calculate the area between the line or curve of the function f(x) and the x-axis to determine the number of frames y of the original clip to sample to create the new video clip. The computing device can play the new clip as a preview of how another computing device may present the new clip. The computing device can also generate other previews by applying the cut, transition, or other video effect to a different segment of the video when the selection slider moves to a different location along the selection bar. In addition, the computing device can send the new clip to other computing devices. In this manner, the computing device can provide for advanced video editing techniques using a minimal number of gestures and other inputs. The present disclosure describes various other functions and advantages below in accordance with the various embodiments.
In this example, the camera application may present graphical user interface 100 in response to computing device 102 capturing a video or computing device 102 receiving the video from another electronic device and opening the video within the camera application, an electronic communication client application (e.g., email client, Short Message Service (SMS) text message client, instant messenger, etc.), a web browser/web application, a file manager or other operating system utility, a database, or other suitable application. Graphical user interface 100 includes video icon 106 which may indicate a state of the camera application, such as the camera application currently operating in a video editing mode. In some embodiments, video icon 106 may also be associated with an interface for sending the video, a portion of the video, an edited version of the video, or an edited clip of the video to local storage, remote storage, and/or other computing devices.
Graphical user interface 100 also includes various icons that may be associated with specific functions or features of the camera application, such as text tool icon 108, drawing tool icon 110, virtual object editor icon 112, scissors tool icon 114, paperclip tool icon 116, and timer icon 118, save tool icon 120, add tool icon 122, and exit icon 124. Selection of text tool icon 108, such as by computing device 102 receiving a touch or tap from a physical pointer or a click from a virtual pointer, can cause computing device 102 to display a text editing interface to add, remove, edit, format (e.g., bold, underline, italicize, etc.), color, and resize text and/or apply other text effects to the video. In response to receiving a selection of drawing tool icon 110, computing device 102 can present a drawing editor interface for selecting different colors and brush sizes for drawing in the video; adding, removing, and editing drawings in the video; and/or applying other image effects to the video.
Scissors tool icon 114 can be associated with a cut, copy, and paste interface for creating “stickers” or virtual objects that computing device 102 can incorporate into the video. In some embodiments, scissors tool icon 114 can also be associated with features such as “Magic Eraser” for deleting specified objects in the video, “Tint Brush” for painting specified objects in different colors, and “Backdrop” for adding, removing, and/or editing backgrounds in the video. Paperclip tool icon 116 can be associated an interface for attaching websites (e.g., URLs), search queries, and similar content in the video. Timer icon 118 can be associated with an interface for setting how long the video can be accessible to other users. Save tool icon 120 can be associated with an interface for saving the video to a personal or private repository of photos, images, and other content (referred to as “Memories” in the Snapchat application). Add tool icon 122 can be associated with an interface for adding the video to a shared repository of photos, images, and other content (referred to as “Stories” in the Snapchat application). Selection of exit icon 124 can cause computing device 102 to exit the video editing mode and to present the last user interface navigated to in the camera application.
Graphical user interface 100 also includes video presentation mode icon 126 for changing the manner of how the camera application presents the video. For instance, the camera application may support video presentation modes such as a “Play Once” mode in which the camera application may play the video one time, a “Loop” mode in which the camera application may continuously play the video in a loop, and an “Enhanced Clip” mode in which the camera application may edit a specified segment of the video (or video clip) to sample the segment according to one or more sampling patterns and play the segment. In an embodiment, the camera application may switch between these different presentation modes depending on the number of times computing device 102 detects selection of video presentation mode icon 126. For example, the camera application may initially present the video in “Play Once” mode and on every third selection of video presentation mode icon 126 thereafter, present the video in “Loop” mode after the first selection of video presentation mode icon 126 and every third selection thereafter, and present the video in “Enhanced Clip” mode after the second selection of video presentation mode icon 126 and every third selection thereafter.
Graphical user interface 150 also includes label 156 for representing the sampling pattern(s) the camera application will apply to the original clip to create the new video clip. In some embodiments, video presentation mode icon 126 may include graphic 158 to represent the sampling pattern(s). In other embodiments, label 156 may incorporate graphic 158 or the camera application may display graphic 158 elsewhere within graphical user interface 150. In this example, the “Enhanced Clip” mode involves applying the “Bounce” sampling pattern to the video clip corresponding to selection slider 154. Applying the Bounce effect to the video clip simulates the clip bouncing back and forth in a curve-eased, speed-ramped loop. In an embodiment, the camera application can sample the video clip at a rate that results in speeding up the first half of the new clip up to 65% of the length of the original clip and sampling the original clip in reverse at the same sped-up rate to form a loop such that the full length of the new clip is 130% of the length of the original clip.
In traditional speed ramping, a conventional video editor drops frames (to simulate speeding up a portion of a video) or adds frames (to simulate slowing down a portion of the video) and samples the video at a constant rate to achieve a linear increase or decrease in speed, respectively. In the example of
The units of time (e.g., tenths of seconds) used in the above example are illustrative and other embodiments may use smaller units of time (e.g., milliseconds, microseconds, etc.) or greater units of time (e.g., seconds, minutes, etc.). In addition, other embodiments may use videos having a smaller frame rate (e.g., 24 fps) while still other embodiments may use videos having greater frame rates (e.g., 48 fps, 60 fps, 120 fps, 240 fps, etc.). In some embodiments, the camera application may also enable customization of the frame rate for the new clip.
In the example of
with period 2L); and
with period 2L). In various embodiments, camera application may use any number of sampling patterns and any types of sampling patterns.
The camera application may use various approaches to apply a specified sampling pattern to the original clip to generate the new clip. In some embodiments, the camera application can determine the function y=f(x) where x represents time, and y represents the number of samples to extract from the original clip for creating the new clip. In other embodiments, the camera application can compute a histogram, such as shown in histograms 400, 430, and 460 of
Returning to
Process 500 can proceed to step 504 in which the computing device receives a selection of a clip of the video. In an embodiment, the computing device may display a video scrubber for selecting the clip, such as shown in
At step 506, the computing device may receive one or more adjustment factors k for determining the length of the new clip relative to the length of the original clip. The computing device may select a default adjustment factor (e.g., k=1) but support customization of the adjustment factor(s). For example, k=¾ may speed up the original clip such that the length of the new clip is 75% of the length of the original clip while k=4 may slow down the original clip such that the length of the new clip is 4 times the length of the original clip. The computing device may apply the same adjustment factor or different adjustment factors if the computing device applies a sampling pattern to the original clip more than once. For example, in an embodiment, the computing device may use a first adjustment factor k=0.65 for a first half of the new clip and a second adjustment factor k=0.35 for a second half of the new clip.
At step 508, the computing device can receive one or more sampling patterns to apply to the selected video clip. The computing device may select a default sampling pattern, such as the Bounce pattern illustrated in
Process 500 may continue to step 510 in which the computing device determines the number of frames to sample from the first clip for each interval of time over the length of the second clip. For example, if the first clip is 2 s in length with a frame rate of 30 fps, the computing device can divide the first clip into 60 1 s intervals and determine individual numbers (e.g., no number of frames for 0 to 1 s, n1 number of frames from is to 2 s, n2 number of frames from 2 s to 3 s, etc.) to sample from the first clip to determine the frames for the second clip.
An approach for determining the numbers of frames to extract from the original clip is for the computing device to determine the function y=f(x) corresponding to the sampling pattern, where x represents time and y represents the number of frames to sample. The computing device can determine the number of frames to sample by evaluating f(x) for each value of x (e.g., increments of 0.01 s, 0.05 s, 0.1 s, 1 s, etc.).
Another approach for determining the frames to retrieve from the original clip can involve the computing device generating a histogram corresponding to the sampling pattern and evaluating the histogram per unit of time. In some embodiments, the sum of every bin of the histogram is equal to a product of the frame rate of the new clip and a length of the new clip (and possibly an adjustment factor for lengthening or shortening the length of the new clip relative to the length of the original clip). For example, given histogram 400 of
At step 512, the computing device can extract frames of the original clip using the number of frames to sample determined in step 510. Then, at step 514, the computing device can assemble the new clip from the frames extracted from the original clip. This can include subsampling frames of the original clip during intervals in which the evaluation of f(x), the histogram, the definite integral of f(x), or other suitable approach indicates that the number of frames to sample for the new clip is less than the number of available frames at the corresponding interval of the original clip. This can also include interpolating frames of the original clip (e.g., repeating frames, merging frames, etc.) during intervals in which the evaluation of f(x), the histogram, the definite integral of f(x), or other suitable approach indicates that the number of frames to sample for the new clip is greater than the number of available frames at the corresponding interval of the original clip.
Process 500 may conclude at step 514 in which the computing device presents the new clip, such as to provide a preview of the new clip by displaying the new clip on a display screen of the computing device. In some embodiments, the computing device may also send the new clip to one or more other computing devices, such as devices associated with friends and other contacts of the user associated with the computing device. In some embodiments, the computing device may send the entire video to the other computing device(s) and metadata for recreating the new clip on the other device(s) (e.g., clip start time, clip end time and/or clip length, clip frame rate, one or more sampling patterns, sampling order for each sampling pattern (e.g., forward sampling or reverse sampling), the order to apply the sampling patterns, one or more adjustment factors for adjusting the length of a portion of the new clip corresponding to each sampling pattern relative to the length of the original clip, etc.). This can enable the other computing device to display the new clip as intended by the user associated with the first computing device but also allow the users of the other computing devices to generate their own clips from the original video.
In this example, network environment 600 includes content management system 602. Content management system 602 may based on a three-tiered architecture that includes interface layer 604, application logic layer 606, and data layer 608. Each module or component of network environment 600 may represent a set of executable software instructions and the corresponding hardware (e.g., memory and processor) for executing the instructions. To avoid obscuring the subject matter of the present disclosure with unnecessary detail, various functional modules and components that may not be germane to conveying an understanding of the subject matter have been omitted. Of course, additional functional modules and components may be used with content management system 602 to facilitate additional functionality that is not specifically described herein. Further, the various functional modules and components shown in network environment 600 may reside on a single server computer, or may be distributed across several server computers in various arrangements. Moreover, although content management system 602 has a three-tiered architecture, the subject matter of the present disclosure is by no means limited to such an architecture.
Interface layer 604 includes interface modules 610 (e.g., a web interface, a mobile application (app) interface, a restful state transfer (REST) application programming interface (API) or other API, etc.), which can receive requests from various client computing devices and servers, such as client devices 620 executing client applications (not shown) and third-party servers 622 executing third-party application(s) 624. In response to the received requests, interface modules 610 communicate appropriate responses to requesting devices via wide area network (WAN) 626 (e.g., the Internet). For example, interface modules 610 can receive requests such as HTTP requests, or other Application Programming Interface (API) requests.
Client devices 620 can execute web browsers or apps that have been developed for a specific platform to include any of a wide variety of mobile computing devices and mobile-specific operating systems (e.g., IOS™, ANDROID™, WINDOWS® PHONE). Client devices 620 can provide functionality to present information to a user and communicate via WAN 626 to exchange information with content management system 602.
In some embodiments, client devices 620 may include a camera app such as SNAPCHAT® that, consistent with some embodiments, allows users to exchange ephemeral messages that include media content, including video messages or text messages. In this example, the camera app can incorporate aspects of embodiments described herein. The ephemeral messages are deleted following a deletion trigger event such as a viewing time or viewing completion. In such embodiments, a device uses the various components described herein within the context of any of generating, sending, receiving, or displaying aspects of an ephemeral message.
Client devices 620 can each comprise at least a display and communication capabilities with WAN 626 to access content management system 602. Client devices 620 may include remote devices, workstations, computers, general purpose computers, Internet appliances, hand-held devices, wireless devices, portable devices, wearable computers, cellular or mobile phones, personal digital assistants (PDAs), smartphones, tablets, ultrabooks, netbooks, laptops, desktops, multi-processor systems, microprocessor-based or programmable consumer electronics, game consoles, set-top boxes, network PCs, mini-computers, and the like.
Data layer 608 includes database servers 616 that can facilitate access to information storage repositories or databases 618. Databases 618 are storage devices that store data such as member profile data, social graph data (e.g., relationships between members of content management system 602), and other user data and content data, such as videos, clips, sampling patterns, and the like.
Application logic layer 606 includes video modules 614, for supporting various video features discussed herein, and application logic modules 612, which, in conjunction with interface modules 610, can generate various user interfaces with data retrieved from various data sources or data services in data layer 608. Individual application logic modules 612 may be used to implement the functionality associated with various applications, services, and features of content management system 602. For instance, a camera application can be implemented using one or more application logic modules 612. The camera application can provide a messaging mechanism for users of client devices 620 to send and receive messages that include text and media content such as pictures and video. Client devices 620 may access and view the messages from the camera application for a specified period of time (e.g., limited or unlimited). In an embodiment, a particular message is accessible to a message recipient for a predefined duration (e.g., specified by a message sender) that begins when the particular message is first accessed. After the predefined duration elapses, the message is deleted and is no longer accessible to the message recipient. Of course, other applications and services may be separately embodied in their own application logic modules 612.
Ephemeral timer interface 706 is a subsystem of content management system 700 responsible for enforcing the temporary access to content permitted by client application 702 and server application 704. To this end, ephemeral timer interface 1014 can incorporate a number of timers that, based on duration and display parameters associated with content, or a collection of content (e.g., messages, videos, a SNAPCHAT® story, etc.), selectively display and enable access to the content via client application 702. Further details regarding the operation of ephemeral timer interface 706 are provided below.
Collection management interface 708 is a subsystem of content management system 700 responsible for managing collections of media (e.g., collections of text, images, video, and audio data). In some examples, a collection of content (e.g., messages, including images, video, text, and audio) may be organized into an “event gallery” or an “event story.” Such a collection may be made available for a specified time period, such as the duration of an event to which the content relates. For example, content relating to a music concert may be made available as a “story” for the duration of that music concert. Collection management interface 708 may also be responsible for publishing an icon that provides notification of the existence of a particular collection to the user interface of client application 702.
In this example, collection management interface 708 includes curation interface 712 to allow a collection manager to manage and curate a particular collection of content. For instance, curation interface 712 can enable an event organizer to curate a collection of content relating to a specific event (e.g., delete inappropriate content or redundant messages). Additionally, collection management interface 708 can employ machine vision (or image recognition technology) and content rules to automatically curate a content collection. In certain embodiments, compensation may be paid to a user for inclusion of user generated content into a collection. In such cases, curation interface 712 can automatically make payments to such users for the use of their content.
Annotation interface 710 is a subsystem of content management system 700 that provides various functions to enable a user to annotate or otherwise modify or edit content. For example, annotation interface 710 may provide functions related to the generation and publishing of media overlays for messages or other content processed by content management system 700. Annotation interface 710 can supply a media overlay (e.g., a SNAPCHAT® filter) to client application 702 based on a geolocation of a client device. As another example, annotation interface 710 may supply a media overlay to client application 702 based on other information, such as, social network information of the user of the client device. A media overlay may include audio and visual content and visual effects. Examples of audio and visual content include pictures, texts, logos, animations, and sound effects. An example of a visual effect includes color overlaying. The audio and visual content or the visual effects can be applied to a media content item (e.g., a photo) at the client device. For example, the media overlay including text that can be overlaid on top of a photograph generated taken by the client device. In yet another example, the media overlay may include an identification of a location overlay (e.g., Venice beach), a name of a live event, or a name of a merchant overlay (e.g., Beach Coffee House). In another example, annotation interface 710 can use the geolocation of the client device to identify a media overlay that includes the name of a merchant at the geolocation of the client device. The media overlay may include other indicia associated with the merchant. The media overlays may be stored in a database (e.g., database 618 of
In an embodiment, annotation interface 710 can provide a user-based publication platform that enables users to select a geolocation on a map, and upload content associated with the selected geolocation. The user may also specify circumstances under which a particular media overlay should be offered to other users. Annotation interface 710 can generate a media overlay that includes the uploaded content and associates the uploaded content with the selected geolocation.
In another embodiment, annotation interface 710 may provide a merchant-based publication platform that enables merchants to select a particular media overlay associated with a geolocation via a bidding process. For example, annotation interface 710 can associate the media overlay of a highest bidding merchant with a corresponding geolocation for a predefined amount of time
Data model 800 includes message data stored within message table 814. Entity table 802 stores entity data, including entity graphs 804. Entities for which records are maintained within entity table 802 may include individuals, corporate entities, organizations, objects, places, events, etc. Regardless of type, any entity regarding which the content management system 700 stores data may be a recognized entity. Each entity is provided with a unique identifier, as well as an entity type identifier (not shown).
Entity graphs 804 store information regarding relationships and associations between entities. Such relationships may be social, professional (e.g., work at a common corporation or organization), interested-based, activity-based, or based on other characteristics.
Data model 800 also stores annotation data, in the example form of filters, in annotation table 812. Filters for which data is stored within annotation table 812 are associated with and applied to videos (for which data is stored in video table 810) and/or images (for which data is stored in image table 808). Filters, in one example, are overlays that are displayed as overlaid on an image or video during presentation to a recipient user. Filters may be of various types, including user-selected filters from a gallery of filters presented to a sending user by client application 702 when the sending user is composing a message. Other types of filers include geolocation filters (also known as geo-filters) which may be presented to a sending user based on geographic location. For example, geolocation filters specific to a neighborhood or special location may be presented within a user interface by client application 702, based on geolocation information determined by a GPS unit of the client device. Another type of filer is a data filer, which may be selectively presented to a sending user by client application 702, based on other inputs or information gathered by the client device during the message creation process. Example of data filters include current temperature at a specific location, a current speed at which a sending user is traveling, battery life for a client device, the current time, or other data captured or received by the client device.
Other annotation data that may be stored within image table 808 can include “lens” data. A “lens” may be a real-time special effect and sound that may be added to an image or a video.
As discussed above, video table 810 stores video data which, in one embodiment, is associated with messages for which records are maintained within message table 814. Similarly, image table 808 stores image data associated with messages for which message data is stored in entity table 802. Entity table 802 may associate various annotations from annotation table 812 with various images and videos stored in image table 808 and video table 810.
Story table 806 stores data regarding collections of messages and associated image, video, or audio data, which are compiled into a collection (e.g., a SNAPCHAT® story or a gallery). The creation of a particular collection may be initiated by a particular user (e.g., each user for which a record is maintained in entity table 802) A user may create a “personal story” in the form of a collection of content that has been created and sent/broadcast by that user. To this end, the user interface of client application 702 may include an icon that is user selectable to enable a sending user to add specific content to his or her personal story.
A collection may also constitute a “live story,” which is a collection of content from multiple users that is created manually, automatically, or using a combination of manual and automatic techniques. For example, a “live story” may constitute a curated stream of user-submitted content from various locations and events. In some embodiments, users whose client devices have location services enabled and are at a common location event at a particular time may be presented with an option, via a user interface of client application 702, to contribute content to a particular live story. The live story may be identified to the user by client application 702 based on his or her location. The end result is a “live story” told from a community perspective.
A further type of content collection is known as a “location story”, which enables a user whose client device is located within a specific geographic location (e.g., on a college or university campus) to contribute to a particular collection. In some embodiments, a contribution to a location story may require a second degree of authentication to verify that the end user belongs to a specific organization or other entity (e.g., is a student on the university campus).
The values or data of the various components of message 900 may be pointers to locations in tables within which the values or data are stored. For example, an image value in message image payload 906 may be a pointer to (or address of) a location within image table 808 of
In this example, ephemeral message 1002 is shown to be associated with message duration parameter 1006, the value of which determines an amount of time that ephemeral message 1002 will be displayed to a receiving user of ephemeral message 1002 by a client application (e.g., client application 702). In one embodiment, where client application 702 is a SNAPCHAT® application client, ephemeral message 1002 is viewable by a receiving user for up to a maximum of 10 seconds that may be customizable by the sending user for a shorter duration.
Message duration parameter 1006 and message receiver identifier 1024 may be inputs to message timer 1012, which can be responsible for determining the amount of time that ephemeral message 1002 is shown to a particular receiving user identified by message receiver identifier 1024. For example, ephemeral message 1002 may only be shown to the relevant receiving user for a time period determined by the value of message duration parameter 1006. Message timer 1012 can provide output to ephemeral timer interface 1014 (e.g., an example of an implementation of ephemeral timer interface 706), which can be responsible for the overall timing of the display of content (e.g., ephemeral message 1002) to a receiving user.
Ephemeral message 1002 is shown in
In some embodiments, each ephemeral message 1002 within ephemeral story 1004 may be associated with story participation parameter 1010, a value of which can set forth the duration of time for which ephemeral message 1002 will be accessible within the context of ephemeral story 1004. For example, a particular ephemeral story may “expire” and become inaccessible within the context of ephemeral story 1004, prior to ephemeral story 1004 itself expiring in terms of story duration parameter 1008. Story duration parameter 1008, story participation parameter 1010, and message receiver identifier 924 each provide input to story timer 1016, which can control whether a particular ephemeral message of ephemeral story 1004 will be displayed to a particular receiving user and, if so, for how long. In some embodiments, ephemeral story 1004 may also be associated with the identity of a receiving user via message receiver identifier 1024.
In some embodiments, story timer 1016 can control the overall lifespan of ephemeral story 1004, as well as ephemeral message 1002 included in ephemeral story 1004. In an embodiment, each ephemeral message 1002 within ephemeral story 1004 may remain viewable and accessible for a time-period specified by story duration parameter 1008. In another embodiment, ephemeral message 1002 may expire, within the context of ephemeral story 1004, based on story participation parameter 1010. In some embodiments, message duration parameter 1006 can still determine the duration of time for which a particular ephemeral message is displayed to a receiving user, even within the context of ephemeral story 1004. For example, message duration parameter 1006 can set forth the duration of time that a particular ephemeral message is displayed to a receiving user, regardless of whether the receiving user is viewing that ephemeral message inside or outside the context of ephemeral story 1004.
Ephemeral timer interface 1014 may remove ephemeral message 1002 from ephemeral story 1004 based on a determination that ephemeral message 1002 has exceeded story participation parameter 1010. For example, when a sending user has established a story participation parameter of 24 hours from posting, ephemeral timer interface 1014 will remove the ephemeral message 1002 from ephemeral story 1004 after the specified 24 hours. Ephemeral timer interface 1014 can also remove ephemeral story 1004 either when story participation parameter 1010 for each ephemeral message 1002 within ephemeral story 1004 has expired, or when ephemeral story 1004 itself has expired in terms of story duration parameter 1008.
In an embodiment, a creator of ephemeral message story 1004 may specify an indefinite story duration parameter. In this case, the expiration of story participation parameter 1010 for the last remaining ephemeral message within ephemeral story 1004 will establish when ephemeral story 1004 itself expires. In an embodiment, a new ephemeral message may be added to the ephemeral story 1004, with a new story participation parameter to effectively extend the life of ephemeral story 1004 to equal the value of story participation parameter 1010.
In some embodiments, responsive to ephemeral timer interface 1014 determining that ephemeral story 1004 has expired (e.g., is no longer accessible), ephemeral timer interface 1014 can communicate with content management system 700 (and, for example, specifically client application 702 to cause an indicium (e.g., an icon) associated with the relevant ephemeral message story to no longer be displayed within a user interface of client application 702). Similarly, when ephemeral timer interface 706 determines that message duration parameter 1006 for ephemeral message 1002 has expired, ephemeral timer interface 1014 may cause client application 702 to no longer display an indicium (e.g., an icon or textual identification) associated with ephemeral message 1002.
In the example of
Operating system 1120 may manage hardware resources and provide common services. In this example, operating system 1120 includes kernel 1118, services 1122, and drivers 1124. Kernel 1118 may operate as an abstraction layer between the hardware and the other software layers. For example, kernel 1118 may be responsible for memory management, processor management (e.g., scheduling), component management, networking, security settings, and so on. Services 1122 may provide other common services for the other software layers. Drivers 1124 may be responsible for controlling or interfacing with the underlying hardware. For instance, drivers 1124 may include display drivers, camera drivers, Bluetooth® drivers, flash memory drivers, serial communication drivers (e.g., Universal Serial Bus (USB) drivers), Wi-Fi® drivers, audio drivers, power management drivers, and so forth depending on the hardware configuration.
Libraries 1116 may provide a common infrastructure that may be utilized by applications 1112 and/or other components and/or layers. Libraries 1116 typically provide functionality that allows other software modules to perform tasks in an easier fashion than to interface directly with the underlying operating system functionality (e.g., kernel 1118, services 1122, and/or drivers 1124). Libraries 1116 may include system libraries 1142 (e.g., C standard library) that may provide functions such as memory allocation functions, string manipulation functions, mathematic functions, and the like. In addition, libraries 1116 may include API libraries 1144 such as media libraries (e.g., libraries to support presentation and manipulation of various media format such as MPEG4, H.264, MP3, AAC, AMR, JPG, PNG), graphics libraries (e.g., an OpenGL framework that may be used to render 2D and 3D in a graphic content on a display), database libraries (e.g., SQLite that may provide various relational database functions), web libraries (e.g., WebKit that may provide web browsing functionality), and the like. Libraries 1116 may also include a wide variety of other libraries 1146 to provide many other APIs to applications 1112 and other software components/modules.
Frameworks 1114 (sometimes also referred to as middleware) may provide a higher-level common infrastructure that may be utilized by applications 1112 and/or other software components/modules. For example, frameworks 1114 may provide various graphic user interface (GUI) functions, high-level resource management, high-level location services, and so forth. Frameworks 1114 may provide a broad spectrum of other APIs that may be utilized by applications 1112 and/or other software components/modules, some of which may be specific to a particular operating system or platform.
Applications 1112 include camera application 1134, built-in applications 1136, and/or third-party applications 1138. Examples of representative built-in applications 1136 include a contacts application, a browser application, a book reader application, a location application, a media application, a messaging application, and/or a game application. Third-party applications 1138 may include any built-in applications 1136 as well as a broad assortment of other applications. In an embodiment, third-party application 1138 (e.g., an application developed using the ANDROID™ or IOS™ software development kit (SDK) by an entity other than the vendor of the particular platform) may be mobile software running on a mobile operating system such as IOS™, ANDROID™, WINDOWS® PHONE, or other mobile operating systems. In this example, third-party application 1138 may invoke API calls 1104 provided by operating system 1120 to facilitate functionality described herein.
Applications 1112 may utilize built-in operating system functions (e.g., kernel 1118, services 1122, and/or drivers 1124), libraries (e.g., system libraries 1142, API libraries 1144, and other libraries 1146), or frameworks/middleware 1114 to create user interfaces to interact with users of the system. Alternatively, or in addition, interactions with a user may occur through a presentation layer, such as presentation layer 1110. In these systems, the application/module “logic” can be separated from the aspects of the application/module that interact with a user.
Some software architectures utilize virtual machines. In the example of
In some embodiments, computing system 1200 can operate as a standalone device or may be coupled (e.g., networked) to other devices. In a networked deployment, computing system 1200 may operate in the capacity of a server or a client device in a server-client network environment, or as a peer device in a peer-to-peer (or distributed) network environment. Computing system 1200 may include a switch, a controller, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular telephone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any electronic device capable of executing instructions 1210, sequentially or otherwise, that specify actions to be taken by computing system 1200. Further, while a single device is illustrated in this example, the term “device” shall also be taken to include a collection of devices that individually or jointly execute instructions 1210 to perform any one or more of the methodologies discussed herein.
Computing system 1200 may include processors 1204, memory/storage 1206, and I/O components 1218, which may be configured to communicate with each other such as via bus 1202. In some embodiments, processors 1204 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include processor 1208 and processor 1212 for executing some or all of instructions 1210. The term “processor” is intended to include a multi-core processor that may comprise two or more independent processors (sometimes also referred to as “cores”) that may execute instructions contemporaneously. Although
Memory/storage 1206 may include memory 1214 (e.g., main memory or other memory storage) and storage 1216 (e.g., a hard-disk drive (HDD) or solid state device (SSD) may be accessible to processors 1204, such as via bus 1202. Storage 1216 and memory 1214 store instructions 1210, which may embody any one or more of the methodologies or functions described herein. Storage 1216 may also store video data 1250, including videos, clips, sampling patterns, and other data discussed in the present disclosure. Instructions 1210 may also reside, completely or partially, within memory 1214, within storage 1216, within processors 1204 (e.g., within the processor's cache memory), or any suitable combination thereof, during execution thereof by computing system 1200. Accordingly, memory 1214, storage 1216, and the memory of processors 1204 are examples of computer-readable media.
As used herein, “computer-readable medium” means an object able to store instructions and data temporarily or permanently and may include random-access memory (RAM), read-only memory (ROM), buffer memory, flash memory, optical media, magnetic media, cache memory, other types of storage (e.g., Erasable Programmable Read-Only Memory (EEPROM)) and/or any suitable combination thereof. The term “computer-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, or associated caches and servers) able to store instructions 1210. The term “computer-readable medium” can also include any medium, or combination of multiple media, that is capable of storing instructions (e.g., instructions 1210) for execution by a computer (e.g., computing system 1200), such that the instructions, when executed by one or more processors of the computer (e.g., processors 1204), cause the computer to perform any one or more of the methodologies described herein. Accordingly, a “computer-readable medium” refers to a single storage apparatus or device, as well as “cloud-based” storage systems or storage networks that include multiple storage apparatus or devices. The term “computer-readable medium” excludes signals per se.
I/O components 1218 may include a wide variety of components to receive input, provide output, produce output, transmit information, exchange information, capture measurements, and so on. The specific I/O components included in a particular device will depend on the type of device. For example, portable devices such as mobile phones will likely include a touchscreen or other such input mechanisms, while a headless server will likely not include a touch sensor. In some embodiments, I/O components 1218 may include output components 1226 and input components 1228. Output components 1226 may include visual components (e.g., a display such as a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), acoustic components (e.g., speakers), haptic components (e.g., a vibratory motor, resistance mechanisms), other signal generators, and so forth. Input components 1218 may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, a photo-optical keyboard, or other alphanumeric input components), point-based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or other pointing instruments), tactile input components (e.g., a physical button, a touch screen that provides location and/or force of touches or touch gestures, or other tactile input components), audio input components (e.g., a microphone), and the like.
In some embodiments, I/O components 1218 may also include biometric components 1230, motion components 1234, environmental components 1236, or position components 1238 among a wide array of other components. For example, biometric components 1230 may include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye tracking), measure bio-signals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram-based identification), and the like. Motion components 1234 may include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope), and so forth. Environmental components 1236 may include illumination sensor components (e.g., photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., infrared sensors that detect nearby objects), gas sensors (e.g., gas detection sensors to detect concentrations of hazardous gases for safety or to measure pollutants in the atmosphere), or other components that may provide indications, measurements, or signals corresponding to a surrounding physical environment. Position components 1236 may include location sensor components (e.g., a Global Position System (GPS) receiver component), altitude sensor components (e.g., altimeters or barometers that detect air pressure from which altitude may be derived), orientation sensor components (e.g., magnetometers), and the like.
Communication may be implemented using a wide variety of technologies. I/O components 1218 may include communication components 1240 operable to couple computing system 1200 to WAN 1232 or devices 1220 via coupling 1224 and coupling 1222 respectively. For example, communication components 1240 may include a network interface component or other suitable device to interface with WAN 1232. In some embodiments, communication components 1240 may include wired communication components, wireless communication components, cellular communication components, Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components to provide communication via other modalities. Devices 1220 may be another computing device or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via USB).
Moreover, communication components 1240 may detect identifiers or include components operable to detect identifiers. For example, communication components 1240 may include radio frequency identification (RFID) tag reader components, NFC smart tag detection components, optical reader components (e.g., an optical sensor to detect one-dimensional bar codes such as Universal Product Code (UPC) bar code, multi-dimensional bar codes such as Quick Response (QR) code, Aztec code, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar code, and other optical codes), or acoustic detection components (e.g., microphones to identify tagged audio signals). In addition, a variety of information may be derived via communication components 1240, such as location via Internet Protocol (IP) geolocation, location via Wi-Fi® signal triangulation, location via detecting an NFC beacon signal that may indicate a particular location, and so forth.
In various embodiments, one or more portions of WAN 1232 may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, a Wi-Fi® network, another type of network, or a combination of two or more such networks. For example, WAN 1232 or a portion of WAN 1232 may include a wireless or cellular network and coupling 1224 may be a Code Division Multiple Access (CDMA) connection, a Global System for Mobile communications (GSM) connection, or another type of cellular or wireless coupling. In this example, coupling 1224 may implement any of a variety of types of data transfer technology, such as Single Carrier Radio Transmission Technology (1×RTT), Evolution-Data Optimized (EVDO) technology, General Packet Radio Service (GPRS) technology, Enhanced Data rates for GSM Evolution (EDGE) technology, third Generation Partnership Project (3GPP) including 3G, fourth generation wireless (4G) networks, Universal Mobile Telecommunications System (UMTS), High-Speed Packet Access (HSPA), Worldwide Interoperability for Microwave Access (WiMAX), Long Term Evolution (LTE) standard, others defined by various standard-setting organizations, other long-range protocols, or other data transfer technology.
Instructions 1210 may be transmitted or received over WAN 1232 using a transmission medium via a network interface device (e.g., a network interface component included in communication components 1240) and utilizing any one of several well-known transfer protocols (e.g., HTTP). Similarly, instructions 1210 may be transmitted or received using a transmission medium via coupling 1222 (e.g., a peer-to-peer coupling) to devices 1220. The term “transmission medium” includes any intangible medium that is capable of storing, encoding, or carrying instructions 1210 for execution by computing system 1200, and includes digital or analog communications signals or other intangible media to facilitate communication of such software.
Throughout this specification, plural instances may implement components, operations, or structures described as a single instance. Although individual operations of one or more methods are illustrated and described as separate operations, one or more of the individual operations may be performed concurrently. Structures and functionality presented as separate components in example configurations may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components. These and other variations, modifications, additions, and improvements fall within the scope of the subject matter herein.
The embodiments illustrated herein are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed. Other embodiments may be used and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. The Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined by the appended claims, along with the full range of equivalents to which such claims are entitled.
As used herein, the term “or” may be construed in either an inclusive or exclusive sense. Moreover, plural instances may be provided for resources, operations, or structures described herein as a single instance. Additionally, boundaries between various resources, operations, modules, engines, and data stores are somewhat arbitrary, and particular operations are illustrated in a context of specific illustrative configurations. Other allocations of functionality are envisioned and may fall within a scope of various embodiments of the present disclosure. In general, structures and functionality presented as separate resources in the example configurations may be implemented as a combined structure or resource. Similarly, structures and functionality presented as a single resource may be implemented as separate resources. These and other variations, modifications, additions, and improvements fall within a scope of embodiments of the present disclosure as represented by the appended claims. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.
This application is a continuation of and claims the benefit of priority to U.S. patent application Ser. No. 16/893,694, filed on Jun. 5, 2020, which is a continuation of and claims the benefit of priority to U.S. patent application Ser. No. 15/691,393, filed on Aug. 30, 2017, which are incorporated herein by reference in their entireties.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16893694 | Jun 2020 | US |
| Child | 17323208 | US | |
| Parent | 15691393 | Aug 2017 | US |
| Child | 16893694 | US |
