Event Coverage Invitation Messaging System

Abstract

A system and method are provided for: receiving a transient message; generating an event overlay interface; overlaying the event overlay interface on the transient message; and receiving a selection of an event overlay component via the event overlay interface. The system and method are also provided for: generating a modified event overlay component based on a plurality of added event overlay contents; overlaying the modified event overlay component on the transient message; and sending a transient message including the overlaid modified event overlay component.

Description

[0001] Priority declaration

[0002] This application claims priority to U.S. patent application Ser. No. 16 / 856,811, filed on Apr. 23, 2020, which is incorporated herein by reference in its entirety. Background Art

[0003] Social media sharing platforms allow users to share millions of messages between mobile devices within a social networking environment. Users of social networks can share media content, such as audio, images, and videos, between their perspective user devices (e.g., mobile devices, personal computers). Social media sharing platforms can also allow users to set up events and send messages to other users by exchanging text messages.

[0004] As the popularity of mobile-based social networking systems continues to grow, users increasingly share media content items, such as electronic images, animations, or videos, with each other. These media content items are often uniquely personalized and therefore reflect the need to encourage electronic visual communication on a global scale. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] To easily identify the discussion of any particular element or act, one or more of the most significant digits in a reference number refers to the figure number that first introduces the element.

[0006] Figure 1 is a pictorial representation of a networked environment in which the present disclosure may be deployed, according to some example implementations.

[0007] Figure 2 is a graphical representation of a messaging client application according to some example embodiments.

[0008] Figure 3 is a graphical representation of a data structure as maintained in a database according to some example implementations.

[0009] Figure 4 is a graphical representation of a message according to some example embodiments.

[0010] Figure 5 is a flowchart for an access restriction process according to some example implementations.

[0011] Figure 6 A flow chart for generating an event overlay component according to one embodiment is shown.

[0012] Figure 7 An example of a user interface for an event overlay component is shown according to one embodiment.

[0013] Fig. 8A and Figure 8B An example user interface of an event editor interface is shown according to one implementation.

[0014] Fig. 9A , Fig. 9B and Fig. 9C An example user interface of a client device is shown according to one embodiment.

[0015] Fig.10 An example user interface depicting an event overlay is shown according to one embodiment.

[0016] Fig.11A and Fig. 11B An example user interface 1100 depicting a modified event overlay component 906 having an extended event profile interface 1106 is shown according to one embodiment.

[0017] Fig. 12A and Fig. 12B An example user interface 1200 depicting an event modifier interface 1204 is shown according to one implementation.

[0018] Fig.13A and Fig. 13B An example user interface 1300 depicting an event chat interface 1304 is shown according to one implementation.

[0019] Fig.14 is a diagrammatic representation of a machine in the form of a computer system within which a set of instructions may be executed, for causing the machine to perform any one or more of the methodologies discussed herein, according to some example embodiments.

[0020] Fig.15 is a block diagram illustrating a software architecture in which the present disclosure may be implemented according to an example implementation. DETAILED DESCRIPTION

[0021] As mentioned above, users within a social networking system send media content to each other for a variety of reasons. Most of the media content sent includes images and videos. There is an increasing need for users to attach or overlay customizable media overlay data objects to media content that invites recipients to join a group or event, whether virtual or in the real world.

[0022] When sending media content between users, it is of utmost importance that the social networking system provides the ability to customize, edit and modify invitations during the media content generation stage or after the media content has been saved in the memory of the user's device. Having these capabilities can significantly increase the interconnectivity and interactivity of end users.

[0023] In at least one embodiment of the present disclosure, a system is provided that improves functionality by allowing users in a social networking system to create, configure, and edit a user group invite event media overlay that is overlaid on a content collection or ephemeral message when sent to another user within the social networking system. The system allows a recipient of the event media overlay to interactively join an event group upon receiving a content collection, ephemeral message, private ephemeral message, or ephemeral content collection.

[0024] Embodiments of the present disclosure improve the functionality of an event media overlay generation system in an electronic messaging and imaging software system by: generating novel interface components during creation of the event overlay system and overlaying an event media overlay on top of a transient message or content collection associated with a media overlay icon; and using event overlay icons to minimize delays in executing an interactive group event session, thereby simplifying and technically enhancing the animation and content collection generation process.

[0025] The following description includes systems, methods, techniques, instruction sequences and computer program products that embody the illustrative embodiments of the present disclosure. In the following description, for the purpose of explanation, many specific details are set forth in order to provide an understanding of the various embodiments of the subject of the present invention. However, it will be apparent to those skilled in the art that the embodiments of the subject of the present invention can be practiced without these specific details. In general, known instruction instances, protocols, structures and techniques are not necessarily shown in detail.

[0026] Figure 1 1 is a block diagram illustrating an example messaging system 100 for exchanging data (e.g., messages and associated content) over a network. The messaging system 100 includes multiple instances of client devices 102, each of which hosts multiple applications including a messaging client application 104. Each messaging client application 104 is communicatively coupled to other instances of the messaging client application 104 and a messaging server system 108 via a network 106 (e.g., the Internet).

[0027] The messaging client application 104 is able to communicate and exchange data with another messaging client application 104 and with a messaging server system 108 via a network 106. The data exchanged between messaging client applications 104 and between messaging client applications 104 and messaging server system 108 includes functions (e.g., commands to call functions) and payload data (e.g., text, audio, video, or other multimedia data).

[0028] The messaging server system 108 provides server-side functionality to specific messaging client applications 104 via the network 106. Although certain functions of the messaging system 100 are described herein as being performed by the messaging client applications 104 or by the messaging server system 108, it is a design choice to locate certain functions within the messaging client applications 104 or within the messaging server system 108. For example, it may be technically preferable to initially deploy certain technologies and functions within the messaging server system 108, but later migrate these technologies and functions to the messaging client applications 104 where the client devices 102 have sufficient processing power.

[0029] The messaging server system 108 supports various services and operations provided to the messaging client applications 104. Such operations include sending data to the messaging client applications 104, receiving data from the messaging client applications 104, and processing data generated by the messaging client applications 104. As examples, the data may include message content, client device information, geo-location information, media annotations and overlays, message content persistence conditions, social network information, and live event information. The data exchange within the messaging system 100 is invoked and controlled through functions available via the user interface (UI) of the messaging client applications 104.

[0030] Turning now specifically to messaging server system 108, application program interface (API) server 110 is coupled to and provides a programming interface to application server 112. Application server 112 is communicatively coupled to database server 118, which facilitates access to database 120 in which data associated with messages processed by application server 112 is stored.

[0031] The application program interface (API) server 110 receives and sends message data (e.g., commands and message payloads) between the client device 102 and the application server 112. Specifically, the application program interface (API) server 110 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client application 104 in order to invoke the functions of the application server 112. Application program interface (API) server 110 exposes various functions supported by application server 112, including account registration, login functionality, sending messages from a particular messaging client application 104 to another messaging client application 104 via application server 112, sending media files (e.g., images or videos) from messaging client application 104 to messaging server application 114 and setting up a collection of media data (e.g., a content collection) for possible access by another messaging client application 104, retrieval of a friend list of a user of client device 102, retrieval of such a collection, retrieval of messages and content, adding and removing friends from a social graph, location of friends within a social graph, and opening application events (e.g., involving messaging client application 104).

[0032] The application server 112 hosts multiple applications and subsystems, including a messaging server application 114, an image processing system 116, a social networking system 122, and an event overlay system 124. The messaging server application 114 implements many message processing techniques and functions, particularly relating to the aggregation and other processing of content (e.g., text and multimedia content) included in messages received from multiple instances of the messaging client application 104. As will be described in more detail, text and media content from multiple sources can be aggregated into collections of content (e.g., referred to as content collections or libraries). The messaging server application 114 then makes these collections available to the messaging client application 104. In view of the hardware requirements for such processing, the messaging server application 114 can also perform other processor- and memory-intensive data processing on the server side.

[0033] The application server 112 also includes an image processing system 116 dedicated to performing various image processing operations, typically on images or videos received within the payload of messages at the messaging server application 114 .

[0034] The social networking system 122 supports various social networking functional services and makes these functionalities and services available to the messaging server application 114. To this end, the social networking system 122 maintains and accesses the entity graph 304 (e.g., Figure 3). Examples of functionality and services supported by the social networking system 122 include identifying other users of the messaging system 100 with whom a particular user has a relationship or "follows," as well as identifying other entities and identifying interests of a particular user.

[0035] The application server 112 also includes an event overlay system 124 dedicated to performing the functions described herein. In one example, the event overlay system 124 is configured to execute instructions including: generating an event overlay interface, overlaying the event overlay interface on a transient message, generating a modified event overlay component based on the added multiple event contents, and sending a transient message including the overlaid modified event overlay component to another computing device.

[0036] The application server 112 is communicatively coupled to a database server 118 , which facilitates access to a database 120 in which data associated with messages processed by the messaging server application 114 is stored.

[0037] Figure 2 1 is a block diagram showing additional details about the messaging system 100 according to an example implementation. Specifically, the messaging system 100 is shown to include a messaging client application 104 and an application server 112, which in turn contain a number of subsystems, namely, a transient timer system 202, a collection management system 204, and an annotation system 206.

[0038] The transient timer system 202 is responsible for implementing transient access to content permitted by the messaging client application 104 and the messaging server application 114. To this end, the transient timer system 202 incorporates a plurality of timers that selectively display messages and associated content and enable access to the messages and associated content via the messaging client application 104 based on durations and display parameters associated with the messages or collections of messages (e.g., collections of content). Additional details regarding the operation of the transient timer system 202 are provided below.

[0039] The collection management system 204 is responsible for managing collections of media (e.g., collections of text, image video, and audio data). In some examples, collections of content (e.g., messages, including images, videos, text, and audio) may be organized into "event libraries" or "event content collections." Such collections may be made available for a specified period of time (e.g., the duration of the event to which the content relates). For example, content related to a concert may be made available as a "content collection" for the duration of the concert. The collection management system 204 may also be responsible for publishing icons that provide notification of the existence of a particular collection to the user interface of the messaging client application 104.

[0040] The collection management system 204 also includes a curation interface 208 that allows a collection manager to manage and curate a particular collection of content. For example, the curation interface 208 enables an event organizer to curate a collection of content related to a particular event (e.g., to remove inappropriate content or redundant messages). In addition, the collection management system 204 employs machine vision (or image recognition technology) and content rules to automatically curate content collections. In some embodiments, compensation may be paid to users to include user-generated content in a collection. In such a case, the curation interface 208 operates to automatically pay such users for use of their content.

[0041] The annotation system 206 provides various functions that enable users to annotate or otherwise modify or edit media content associated with messages. For example, the annotation system 206 provides functions related to the generation and publication of media overlays for messages processed by the messaging system 100. The annotation system 206 is operable to supply a media overlay or supplementation (e.g., an image filter) to the messaging client application 104 based on the geographic location of the client device 102. In another example, the annotation system 206 is operable to supply a media overlay to the messaging client application 104 based on other information (e.g., social network information of the user of the client device 102).

[0042] A media overlay or, for example, an event overlay component may include audio and visual content and visual effects. Examples of audio and visual content include pictures, text, logos, animations, and sound effects. Examples of visual effects include color overlays. Audio and visual content or visual effects may be applied to media content items (e.g., photos) at client device 102. For example, a media overlay may include text that may be overlaid on a photo taken by client device 102. In another example, a media overlay includes an overlay of a location identifier (e.g., Venice Beach), a name of a live event, or a business name (e.g., Beach Cafe).

[0043] In another example, the annotation system 206 uses the geographic location of the client device 102 to identify a media overlay that includes the name of a business at the geographic location of the client device 102. The media overlay may include other tags associated with the business. The media overlay may be stored in the database 120 and accessed through the database server 118.

[0044] In one example implementation, the annotation system 206 provides a user-based publishing platform that enables a user to select a geographic location on a map and upload content associated with the selected geographic location. The user may also specify that a particular media overlay should be provided to the environments of other users. The annotation system 206 generates a media overlay including the uploaded content and associates the uploaded content with the selected geographic location.

[0045] In another example implementation, the annotation system 206 provides a merchant-based publishing platform that enables merchants to select specific media coverage associated with a geographic location via a bidding process. For example, the annotation system 206 associates the media coverage of the highest bidding merchant with the corresponding geographic location within a predefined amount of time.

[0046] Figure 3 is a schematic diagram illustrating a data structure 300 that may be stored in a database 120 of a messaging server system 108 according to certain example implementations. Although the contents of the database 120 are illustrated as including a plurality of tables, it should be understood that data may be stored in other types of data structures (e.g., as an object-oriented database).

[0047] The database 120 includes message data stored in a message table 314. The entity table 302 stores entity data, including an entity graph 304. The entities whose records are maintained in the entity table 302 may include individuals, corporate entities, organizations, objects, places, events, etc. Regardless of the type, any entity whose data is stored by the messaging server system 108 may be an identified entity. Each entity is provided with a unique identifier, as well as an entity type identifier (not shown).

[0048] The entity graph 304 also stores information about relationships and associations between entities. As examples only, such relationships may be social relationships, professional relationships (e.g., working in a common company or organization) based on interests or based on activities.

[0049] The database 120 also stores annotation data in the form of examples of filters in the annotation table 312. The filters whose data are stored in the annotation table 312 are associated with videos (whose data are stored in the video table 310) and / or images (whose data are stored in the image table 308) and are applied to the videos and / or images. In one example, the filter is displayed as an overlay over the image or video during presentation to the recipient user. The filter can be of various types, including a user-selected filter from a library of filters presented to the sending user by the messaging client application 104 when the sending user is composing a message.

[0050] Other types of filters include geolocation filters (also referred to as geofilters), which can be presented to the sending user based on the geographic location. For example, based on the geographic location information determined by the GPS unit of the client device 102, the messaging client application 104 can present a neighborhood or specific location-specific geolocation filter within the user interface. Another type of file manager is a data file manager, which can be selectively presented to the sending user by the messaging client application 104 based on other inputs or information collected by the client device 102 during the message creation process. Examples of data filters include the current temperature at a specific location, the current speed at which the sending user is traveling, the battery life of the client device 102, or the current time.

[0051] Other annotation data that can be stored in the image table 308 is augmented reality content items (eg, corresponding to application lenses or augmented reality experiences). Augmented reality content items can be real-time special effects and sounds that can be added to images or videos.

[0052] As described above, augmented reality content items, overlays, image transformations, AR images, and similar terms refer to modifications that can be made to a video or image. This includes real-time modifications, i.e., modifying an image as it is captured using a device sensor, and then displaying the image on the device's screen using the modifications. This also includes modifications to stored content such as video clips in a library that can be modified. For example, in a device with access to multiple augmented reality content items, a user can use a single video clip with multiple augmented reality content items to see how different augmented reality content items will modify the stored clip.

[0053] For example, by selecting different augmented reality content items for content, multiple augmented reality content items applying different pseudo-random motion models can be applied to the same content. Similarly, real-time video capture can be used with the modifications shown to show how the video image currently captured by the sensor of the device will modify the captured data. Such data can simply be displayed on the screen without being stored in the memory, or the content captured by the device sensor can be recorded and stored in the memory with or without modification (or both). In some systems, the preview function can show how different augmented reality content items will be viewed in different windows in the display at the same time. For example, this can enable multiple windows with different pseudo-random animations to be viewed on the display at the same time.

[0054] Data and various systems for using the data to modify content using augmented reality content items or other such transformation systems may therefore involve: detection of objects (e.g., faces, hands, bodies, cats, dogs, surfaces, objects, etc.); tracking of these objects as they leave, enter, and move around the field of view in a video frame; and modifying or transforming these objects as they are tracked. In various embodiments, different methods for implementing such transformations may be used. For example, some embodiments may involve generating a three-dimensional mesh model of one or more objects and implementing the transformation using transformations and animated textures of the models within the video.

[0055] In other embodiments, tracking of points on an object can be used to place an image or texture (which can be two-dimensional or three-dimensional) at the tracked location. In yet another embodiment, neural network analysis of a video frame can be used to place an image, model, or texture into content (e.g., an image or video frame). Thus, an augmented reality content item refers both to the images, models, and textures used to create transformations in the content, and to the additional modeling and analysis information required to achieve such transformations through object detection, tracking, and placement.

[0056] Real-time video processing can be performed with any type of video data (e.g., video streams, video files, etc.) stored in the memory of any type of computerized system. For example, a user can load a video file and store it in the memory of the device, or a video stream can be generated using the device's sensors. In addition, any object such as a human face and body parts, an animal, or a non-living thing such as a chair, a car, or other objects can be processed using a computer animation model.

[0057] In some embodiments, when a specific modification is selected together with the content to be transformed, the elements to be transformed are identified by a computing device, and then detected and tracked whether they exist in the frame of the video. The elements of the object are modified according to the modification request, thereby transforming the frame of the video stream. For different types of transformations, the frames of the video stream can be transformed by different methods. For example, for the transformation of the frame mainly involving the variation of the elements of the object, the feature points of each element of the object are calculated (for example, using the Active Shape Model (ASM) or other known methods). Then, a grid based on the feature points is generated for each of at least one element of the object. The grid is used to track the next stage of the elements of the object in the video stream. During the tracking process, the grid mentioned for each element is aligned with the position of each element. Then, additional points are generated on the grid. A first set of first points is generated for each element based on the modification request, and a set of second points is generated for each element based on the set of the first points and the modification request. Then, the frame of the video stream can be transformed by modifying the elements of the object according to the set of the first point and the set of the second point and the grid. In such a method, the background of the modified object can also be changed or distorted by tracking and modifying the background.

[0058] In one or more embodiments, the transformation of some areas of an object using elements of the object can be performed by calculating feature points of each element of the object and generating a grid based on the calculated feature points. Points are generated on the grid, and then various areas based on these points are generated. The elements of the object are then tracked by aligning the area of ​​each element with the position of each element of at least one element, and the properties of the area can be modified according to the modification request, thereby transforming the frame of the video stream. Depending on the specific modification request, the properties of the mentioned area can be transformed in different ways. Such modifications may involve: changing the color of the area; removing at least some partial areas from the frame of the video stream; including one or more new objects in the area based on the modification request; and modifying or distorting the elements of the area or object. In various embodiments, any combination of such modifications or other similar modifications may be used. For some models to be animated, some feature points can be selected as control points to determine the entire state space of options for model animation.

[0059] In some embodiments of a computer animation model for transforming image data using face detection, faces are detected on an image using a specific face detection algorithm (e.g., Viola-Jones). An active shape model (ASM) algorithm is then applied to the face region of the image to detect facial feature reference points.

[0060] In other embodiments, other methods and algorithms suitable for face detection may be used. For example, in some embodiments, landmarks are used to locate features, which represent distinguishable points that are present in most of the images considered. For example, for facial landmarks, the location of the left pupil can be used. When the initial landmarks are not recognizable (for example, if a person has an eye patch), secondary landmarks can be used. Such a landmark recognition procedure can be used for any such object. In some embodiments, a set of landmarks forms a shape. The shape can be represented as a vector using the coordinates of the points in the shape. One shape is aligned with another shape using a similarity transformation (allowing translation, scaling, and rotation) that minimizes the average Euclidean distance between the shape points. The average shape is the average of the aligned training shapes.

[0061] In some embodiments, a landmark search begins with an average shape aligned with the position and size of the face determined by the global face detector. Such a search then repeats the steps of proposing tentative shapes by adjusting the positions of shape points via template matching of the image texture around each point, and then conforming the tentative shapes to the global shape model until convergence occurs. In some systems, individual template matches are unreliable, and the shape model brings together the results of weak template matchers to form a stronger overall classifier. The entire search is repeated at each level of the image pyramid, from coarse to fine resolution.

[0062] Embodiments of the transformation system can capture an image or video stream on a client device (e.g., client device 102) and perform complex image processing locally on the client device 102 while maintaining a suitable user experience, computation time, and power consumption. The complex image processing can include size and shape changes, emotion transfer (e.g., changing a face from a frown to a smile), state transfer (e.g., aging an object, reducing apparent age, changing gender), style transfer, application of graphical elements, and any other suitable image or video processing implemented by a convolutional neural network that has been configured to execute efficiently on the client device 102.

[0063] In some example embodiments, a computer animation model for transforming image data may be used by a system in which a user may capture an image or video stream of the user (e.g., a selfie) using a client device 102 having a neural network operating as part of a messaging client application 104 operating on the client device 102. A transformation system operating within the messaging client application 104 determines the presence of a face within the image or video stream and provides a modification icon associated with the computer animation model to transform the image data, or the computer animation model may be presented in association with an interface described herein. The modification icon includes changes that may be the basis for modifying the user's face within the image or video stream as part of the modification operation. Once the modification icon is selected, the transformation system initiates a process to transform the user's image to reflect the selected modification icon (e.g., generating a smiley face on the user). In some embodiments, the modified image or video stream may be presented in a graphical user interface displayed on the mobile client device as soon as the image or video stream is captured and the specified modification is selected. The transformation system may implement a complex convolutional neural network on a portion of the image or video stream to generate and apply the selected modification. That is, once the modification icon has been selected, the user can capture an image or video stream and present the modification results in real time or near real time. In addition, when the video stream is being captured and the selected modification icon remains switched, the modification can be persistent. A machine learning neural network can be used to implement such a modification.

[0064] In some embodiments, a graphical user interface presenting the modifications performed by the transformation system may provide additional interactive options for the user. Such options may be based on an interface for initiating content capture and selection of a particular computer animation model (e.g., initiated from a content creator user interface). In various embodiments, the modification may be persistent after the initial selection of the modification icon. The user may turn the modification on or off by tapping or otherwise selecting a face modified by the transformation system, and store the modification for later viewing or browsing to other areas of the imaging application. In the case where the transformation system modifies multiple faces, the user may globally turn the modification on or off by tapping or selecting a single face modified and displayed within the graphical user interface. In some embodiments, a single face in a set of multiple faces may be modified individually, or such modifications may be individually toggled by tapping or selecting a single face or a series of single faces displayed within the graphical user interface.

[0065] As mentioned above, the video table 310 stores video data, which in one embodiment is associated with messages whose records are maintained in the message table 314. Similarly, the image table 308 stores image data associated with messages whose message data is stored in the entity table 302. The entity table 302 may associate various annotations from the annotation table 312 with the various images and videos stored in the image table 308 and the video table 310.

[0066] The content collection table 306 stores data about a collection of messages and associated images, video or audio data that are compiled into a collection (e.g., a content collection or library). The creation of a particular collection can be initiated by a particular user (e.g., each user whose record is maintained in the entity table 302). A user can create a "personal content collection" in the form of a collection of content that has been created and sent / broadcasted by the user. To this end, the user interface of the messaging client application 104 may include an icon that the user can select to enable the sending user to add specific content to his or her personal content collection.

[0067] A collection may also constitute a "live content collection," 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 content collection" may constitute a curated stream of user-submitted content from different locations and events. Users whose client devices have location services enabled and who are at a common location event at a particular time may be presented with an option to contribute content to a particular live content collection, for example, via the user interface of the messaging client application 104. Live content collections may be identified to users by the messaging client application 104 based on the user's location. The end result is a "live content collection" told from a community perspective.

[0068] Another type of content collection is referred to as a "location content collection," which enables users whose client devices 102 are located in a particular geographic location (e.g., at a college or university campus) to contribute to a particular collection. In some implementations, contributions to a location content collection may require a second degree of authentication to verify that the end user belongs to a particular organization or other entity (e.g., is a student on a college campus).

[0069] The avatar table 318 may store personalized avatars associated with a user profile of the client device 102. In another example, a personalized avatar may be associated with a user profile that receives an event media overlay and interactively joins an event or group via the event media overlay. The avatar table 318 may provide associated avatars for inclusion in an avatar interface and ultimately sent or communicated to a second computing device when accessing and viewing a collection of content.

[0070] The event table 316 stores data related to the event. For example, the event table 316 stores details of the event, name, time, date, location, comments, images and pictures related to the event, and log events (e.g., actions) corresponding to the event (e.g., when a user joins the event, when a user invites another user, when the details of the event change), a chat session link for the event (e.g., a chat session link in the chat history table 316), a token for the event, and the like.

[0071] Figure 4 is a schematic diagram illustrating the structure of a message 400 generated by a messaging client application 104 for transmission to another messaging client application 104 or a messaging server application 114 according to some embodiments. The content of a particular message 400 is used to populate a message table 314 stored in a database 120 and accessible by a messaging server application 114. Similarly, the content of the message 400 is stored in memory as "in-transit" or "in-flight" data for a client device 102 or application server 112. The message 400 is shown to include the following components:

[0072] Message identifier 402 : a unique identifier that identifies the message 400 .

[0073] Message text payload 404 : Text to be generated by a user via the user interface of the client device 102 and included in the message 400 .

[0074] Message image payload 406 : Image data captured by a camera component of the client device 102 or retrieved from a memory component of the client device 102 and included in the message 400 .

[0075] Message video payload 408 : Video data captured by the camera component or retrieved from the memory component of the client device 102 and included in the message 400 .

[0076] Message audio payload 410 : audio data captured by a microphone or retrieved from a memory component of the client device 102 and included in the message 400 .

[0077] Message annotation 412: Annotation data representing an annotation (eg, a filter, sticker, or other enhancement) to be applied to the message image payload 406, the message video payload 408, or the message audio payload 410 of the message 400.

[0078] Message duration parameter 414: A parameter value indicating the amount of time in seconds that the content of the message (eg, message image payload 406, message video payload 408, message audio payload 410) will be presented or made accessible to the user via the messaging client application 104.

[0079] Message geolocation parameter 416: Geolocation data (e.g., latitude and longitude coordinates) associated with the content payload of the message. Multiple message geolocation parameter 416 values ​​may be included in the payload, with each of these parameter values ​​being associated with a content item included in the content (e.g., a specific image within message image payload 406 or a specific video within message video payload 408).

[0080] Message story identifier 418: An identifier value that identifies one or more content collections (e.g., “content collections”) associated with a particular content item in message image payload 406 of message 400. For example, multiple images within message image payload 406 may each be associated with multiple content collections using an identifier value.

[0081] Message tags 420: Each message 400 may be tagged with a plurality of tags, each of which indicates a subject of content included in the message payload. For example, where a particular image included in the message image payload 406 depicts an animal (e.g., a lion), a tag value may be included within the message tags 420 indicating the relevant animal. The tag value may be manually generated based on user input, or may be automatically generated using, for example, image recognition.

[0082] • Message sender identifier 422: An identifier (eg, a messaging system identifier, an email address, or a device identifier) ​​that indicates the user of the client device 102 on which the message 400 was generated and from which the message 400 was sent.

[0083] • Message recipient identifier 424: Indicates an identifier (eg, a messaging system identifier, an email address, or a device identifier) ​​of the user of client device 102 to which message 400 is addressed.

[0084] The contents (e.g., values) of the various components of message 400 may be pointers to locations in a table in which content data values ​​are stored. For example, the image value in message image payload 406 may be a pointer to a location (or address) within image table 308. Similarly, the value within message video payload 408 may point to data stored within video table 310, the value stored within message annotation 412 may point to data stored in annotation table 312, the value stored within message story identifier 418 may point to data stored in content collection table 306, and the values ​​stored within message sender identifier 422 and message recipient identifier 424 may point to user records stored within entity table 302.

[0085] Figure 5 is a schematic diagram illustrating an access restriction process 500 according to which access to content (e.g., an ephemeral message 502 and an associated multimedia payload of data) or a collection of content (e.g., an ephemeral message group 504) can be time-limited (e.g., made ephemeral).

[0086] The ephemeral message 502 is shown to be associated with a message duration parameter 506, the value of which determines the amount of time that the ephemeral message 502 will be displayed by the messaging client application 104 to the receiving user of the ephemeral message 502. In one embodiment, the ephemeral message 502 may be viewed by the receiving user for up to 10 seconds, depending on the amount of time specified by the sending user using the message duration parameter 506.

[0087] The message duration parameter 506 and the message recipient identifier 424 are shown as inputs to a message timer 512, which is responsible for determining the amount of time that the ephemeral message 502 is displayed to a particular receiving user identified by the message recipient identifier 424. In particular, the ephemeral message 502 will only be displayed to the associated receiving user for a period of time determined by the value of the message duration parameter 506. The message timer 512 is shown as providing an output to a more general ephemeral timer system 202, which is responsible for the overall timing of displaying content (e.g., the ephemeral message 502) to the receiving user.

[0088] Short message 5022 Figure 5100 as being included in an ephemeral message group 504 (e.g., a message collection in a personal content collection, or an event content collection). The ephemeral message group 504 has an associated group duration parameter 508, the value of which determines the duration for which the ephemeral message group 504 is presented and accessible to users of the messaging system 100. The group duration parameter 508 can be, for example, the duration of a concert, where the ephemeral message group 504 is a collection of content related to the concert. Alternatively, a user (an owning user or an administrator user) can specify the value of the group duration parameter 508 when performing setup and creation of the ephemeral message group 504.

[0089] In addition, each ephemeral message 502 within the ephemeral message group 504 has an associated group participation parameter 510, the value of which determines the duration for which the ephemeral message 502 is accessible within the context of the ephemeral message group 504. Thus, a particular ephemeral message group 504 may "expire" and become inaccessible within the context of the ephemeral message group 504 before the ephemeral message group 504 itself expires according to the group duration parameter 508. The group duration parameter 508, the group participation parameter 510, and the message recipient identifier 424 each provide inputs to a group timer 514, which operatively first determines whether a particular ephemeral message 502 of the ephemeral message group 504 is to be displayed to a particular receiving user, and if so, for how long. Note that as a result of the message recipient identifier 424, the ephemeral message group 504 also knows the identity of the particular receiving user.

[0090] Thus, the group timer 514 operatively controls the overall lifespan of the associated ephemeral message group 504 and the individual ephemeral messages 502 included in the ephemeral message group 504. In one embodiment, each ephemeral message 502 within the ephemeral message group 504 remains viewable and accessible for a period of time specified by the group duration parameter 508. In other embodiments, within the context of the ephemeral message group 504, a particular ephemeral message 502 may expire based on the group participation parameter 510. Note that the message duration parameter 506 may still determine the duration that a particular ephemeral message 502 is displayed to a receiving user, even within the context of the ephemeral message group 504. Thus, the message duration parameter 506 determines the duration that a particular ephemeral message 502 is displayed to a receiving user, regardless of whether the receiving user is viewing the ephemeral message 502 within the context of the ephemeral message group 504 or outside the context of the ephemeral message group 504.

[0091] The transient timer system 202 may also be operable to remove a particular transient message 502 from a transient message group 504 based on determining that the particular transient message 502 has exceeded the associated group participation parameter 510. For example, when the sending user has established a group participation parameter 510 of 24 hours from posting, the transient timer system 202 will remove the associated transient message 502 from the transient message group 504 after the specified 24 hours. The transient timer system 202 is also operable to remove a transient message group 504 when the group participation parameter 510 of each transient message 502 within the transient message group 504 has expired or when the transient message group 504 itself has expired according to the group duration parameter 508.

[0092] In certain use cases, the creator of a particular ephemeral message group 504 may specify an indefinite group duration parameter 508. In this case, the expiration of the group participation parameter 510 of the last remaining ephemeral message 502 within the ephemeral message group 504 will determine when the ephemeral message group 504 itself expires. In this case, a new ephemeral message 502 with a new group participation parameter 510 added to the ephemeral message group 504 effectively extends the life of the ephemeral message group 504 to equal the value of the group participation parameter 510.

[0093] In response to the transient timer system 202 determining that the transient message group 504 has expired (e.g., is no longer accessible), the transient timer system 202 communicates with the messaging system 100 (and, for example, specifically with the messaging client application 104) to cause the indicia (e.g., icon) associated with the relevant transient message group 504 to no longer be displayed within the user interface of the messaging client application 104. Similarly, when the transient timer system 202 determines that the message duration parameter 506 of a particular transient message 502 has expired, the transient timer system 202 causes the messaging client application 104 to no longer display the indicia (e.g., icon or text identification) associated with the transient message 502.

[0094] Figure 6The flow chart for generating event coverage parts according to one embodiment is shown.In operation 602, computing device (for example, client device 102) receives transient message.In one example, transient message comprises media content item, for example picture, video, photo or image, and is associated with predetermined message duration parameter 506.In one example, computing device can receive transient message from another computing device such as smart phone, notebook computer, mobile device etc.In an example embodiment, user captures media content item via the camera device device of computing device and uses the captured media content to generate transient message.Computing device can display the captured image or video on the display area of ​​computing device, and provides option (for example, interface element) to add media coverage (for example, event coverage or other media coverage) to the captured media content item.In one embodiment, transient message 502 can be viewed by receiving user for up to 10 seconds, which depends on the amount of time specified by sending user using message duration parameter 506.

[0095] In another embodiment, instead of receiving a transient message, the computing device receives a content collection, transient content collection, video, image, photo, or media content item shared between computing devices (e.g., mobile devices, smart phones, personal computers, etc.). In an example embodiment, a user captures a media content item via a camera device of a computing device. For example, a user captures an image (e.g., a photo) or a video. The computing device can display the captured image or video on a display area of ​​the computing device and provide an option (e.g., an interface element) to add a media overlay to the captured media content item.

[0096] In operation 604, computing device generates event overlay interface and the event overlay interface is covered on transient message.In one example, event overlay interface comprises the database of event overlay parts, and the user of computing device can select from this database.In another example, the user can select one or more event overlay parts from the interactive menu of event overlay interface.One or more event overlay parts selected are added to transient message or media content item (for example, by event overlay parts are covered on media content item to strengthen media content item).Computing device automatically generates event overlay interface in response to user selection of event overlay parts, in response to capturing media content or in response to generating transient message, content set or transient content set.In operation 606, computing device receives the selection of event overlay parts via event overlay interface.

[0097] In operation 608, the computing device receives a plurality of event overlay contents added to the event overlay component. For example, the event overlay component includes an event editor interface. A user of the computing system, also referred to as a creator, inputs event overlay contents (e.g., event details, event information, or event knowledge) into the event editor interface of the event overlay component. The event overlay contents include, but are not limited to, the title of the event, location information associated with the event, a location based on a predetermined location criterion such as a location suggested by previously stored location information, location information received from another computing device or captured by the computing device via a camera device, time and date information associated with the event, and a description associated with the event. The user may input any alphanumeric string as the event overlay content via a keyboard, user gesture, voice, or other means.

[0098] In operation 610, a modified event overlay component is generated based on the added multiple event overlay contents. The user can also edit or modify the event details or event overlay contents according to the user response. The event overlay component also includes a user profile associated with the user device. Information from the user profile can be accessed and imported into the event overlay component or event editor interface. Once the event overlay contents are input into the event editor interface of the event overlay component, the computing device receives the event overlay contents.

[0099] In operation 612, the computing device covers the modified event cover component on the transient message. In an example implementation, the modified event cover component can be covered in any area of ​​the transient message or media content, and can be moved to different positions on the media content item. The modified event cover component can also be rotated (for example, so that it is in different orthogonal angles), amplified or compressed. In one example, the modified event cover component can have the color of change, the font of change, etc. In some example implementations, the modified event cover component is automatically resized based on the content provided for the event. In operation 614, the computing device sends the transient message of the modified event cover component comprising coverage to the second computing device. The transient message is received by the second computing device and is displayed on the user interface of the second computing device.

[0100] Figure 7 An example user interface 700 is shown displayed on a computing device (eg, client device 102) according to one embodiment. User interface 700 depicts an event overlay 704 displayed by a computing device according to one embodiment. Event overlay 704 is shown overlaid on a media content item 708.

[0101] Media content item 708 is an image of the American flag, however, media content item 708 may be any image, video, animation, content collection, ephemeral message, or ephemeral content collection. For illustration purposes, media content item 708 is an ephemeral message.

[0102] User interface 700 also includes a back button 702. The back button can be selected to display a previous page or a different page previously viewed on the computing device.

[0103] The event overlay component 704 also includes an event editor interface 706 in which a user of the computing device enters event overlay content. For example, the user can enter a title for the event, location information associated with the event, time and date information associated with the event, and a note or description associated with the event. The event overlay component 704 also includes a user profile (not shown) associated with the user device.

[0104] In one example, the event editor interface 706 is a combination of data fields that are designed to receive user input in the form of alphanumeric strings. The alphanumeric strings may also be referred to as subtitle data, content data, or event overlay content. The computing device receives content added from a user of the client device 102 via the event editor 706 via the keyboard interface 710, user gestures, voice input, external input devices, etc.

[0105] In another example, once the user selects the event overlay component 704, the title field is highlighted by default and entry of any other applicable event content is optional. Once the user has entered at least the title of the event, the user can click the back button 702, for example, to save changes or additions to the content within the event editor 706.

[0106] As mentioned earlier, Fig. 8A and Figure 8B 8 and 801 according to one embodiment. The user interfaces 800 and 801 each depict an event overlay component 704 containing added event overlay content 806 displayed by a client device. Fig. 8A As shown, information related to an event (referred to as event overlay in one example) may include location information, time and date information, and annotation or description information.

[0107] In one example, location information 802 is generated and displayed in a separate section of event overlay component 704. In one example, the computing device automatically populates the mapping location and coordinates and also provides suggestions based on the device's current location or the location of the event destination when the user enters content related to the event. For example, if the user device is located at 123 Main Street and the event information entered is related to a bowling alley, the computing device will access a third-party mapping server to determine bowling alleys near the user device.

[0108] exist Figure 8B , example event overlay content 802, 804, and 806 are displayed within fields of event overlay editor 706. For example, the user inputs a title of "Design Drinks!", which is displayed in event overlay part 704. In this example, location information 802 is an auto-populated suggestion corresponding to the location of the user device and the event information entered by the user.

[0109] exist Figure 8B In the example shown, the location information 802 and the date and time information 804 are "Location kitchen + Wine Bar Thursday 11:00 PM 9 / 13 / 19". The user also enters description information 806 in the event overlay editor 706 stating "Matt said he doesn't want a birthday party, but we all know he does, come to my house at 6:30 and he'll be there at 7:00!" In this example, the user enters the location information 802, the date and time information 804, and the description information 806 into the event overlay editor 706 of the event overlay component 704. The user can also edit or modify any field within the event editor interface 706, including the location information 802, the date and time information 804, or the description information 806.

[0110] Fig. 9A , Fig. 9B and Fig. 9C An example user interface according to one embodiment is shown. Fig. 9A As shown, event overlay 704 is overlaid on ephemeral message 708. In this example, ephemeral message 708 contains media content related to an image of the American flag. Ephemeral message 708 corresponds to the generated ephemeral message 708 sent to the second computing device. Event overlay 704 contains the title "Design Drinks!", as previously described. Fig. 8A and Figure 8B A messaging icon 902 and an event details button 904 are also shown at the bottom of the transient message 708 .

[0111] The messaging icon 902 reminds the user whether a message, email, ephemeral message, content collection, or ephemeral content collection is received, viewed, unviewed, expired, sent, etc. The event details button 904 activates the event content and associated details of the event overlay 704 .

[0112] exist Fig. 9B , the event overlay component 704 is overlaid on top of the transient message 708, and in one example, upon accessing the event overlay component 704, a modified event overlay component 906 is generated that includes event overlay content information 806, such as location information 802, time and date information 804, and description information 806 previously entered by a user using the event overlay editor 706. In one example, an event overlay messaging interface 908 is generated at the bottom of the modified event overlay component 906.

[0113] The event overlay messaging interface 908 displays one or more avatars 910 associated with each user who has received the event overlay component 704 via the transient message 708 and has interactively joined the event via accessing the interactive join option 912 (described in more detail below). Each generated avatar 910 is displayed in a separate portion 914 of the event overlay messaging interface 908. In one example, the generated modified event overlay component includes information input to the event overlay component's event editor interface, the event overlay messaging interface, and at least one or more avatars 910 associated with each user who has received the event overlay component via the transient message and has interactively joined the event via accessing the interactive join option 912 (described in more detail below). Each generated avatar 910 is displayed in a separate portion of the event overlay messaging interface. The modified event overlay component also includes an extended event profile interface, a status notification icon, an interactive map portion, a message portion, and a message attachment portion (described below).

[0114] like Fig. 9CAs shown, the event overlay messaging interface 908 is expanded to depict a separate portion 914 of the event overlay messaging interface 908, which contains an avatar 910 associated with each user who has received and joined or accepted the invitation described in the event details shown in the event overlay component 704. In one example, when a user receives a transient message 708 (or any other media content, such as a collection of content, an image, a video, a message) containing an event media component 704. Upon activating the interactive join option 912, the computing device accesses the user profile of the user who has activated the interactive join option 912, and adds the user to the event overlay directory associated with the event as a member of the event depicted and described in the event overlay component 704. For example, the computing device sends the user profile information to a third computing device, such as a server, so that the user is included in the event overlay directory. In another example, upon activating the interactive join option 912, the computing device generates an event overlay status icon depicting that the user is attending the event, as shown in the expanded separate portion 914 of the event overlay messaging interface 908.

[0115] Fig.10 An example user interface 1000 depicting an event overlay 704 from a chat interface 1002 is shown according to one embodiment. In one example, a transient message with an event overlay is sent from the transient message chat interface 1002 to a second computing device. Figure 5 As described in , once a transient message has been received and viewed, the transient message having the event coverage component is deleted upon determining that a predetermined time period has passed.

[0116] Fig.11A and Fig. 11B An example user interface 1100 depicting a modified event overlay widget 906 with an extended event profile interface 1106 is shown according to one embodiment. In one example, once a user has created an event overlay widget 704 and invited other users, or once a user has received and interactively joined an event associated with an event overlay widget 704, the modified event overlay widget 906 as shown displays a generated status notification icon 1102 and one or more avatars 910 associated with each user who has received the event overlay widget 704 and interactively joined the event after accessing an interactive join option 912 displayed in an extended individual portion 914 of the event overlay message interface 908. In one example, the event overlay status icon 1104 is a two-layer interactive button 1104 depicting "Go" and "Don't Go" or an emoticon, graphic image, or avatar.

[0117] like Fig. 11BAs shown, the modified event overlay component 906 also includes an extended event profile interface 1106, which displays the generated interactive map portion 1108, the message portion 1110, and the message attachment portion 1112. In another example, the interactive map portion 1108 displays an indication (not shown) of the event on a map at a location corresponding to the event and within a time period corresponding to the time of day of the event. The indication is in the form of a flag, an avatar of a user attending the event, a 2D or 3D graphical object, other indications, or a combination of indications. In one example, when the interactive map portion 1108 is activated, driving, public transportation, or walking directions are activated and displayed on the user device. Driving, public transportation, or walking directions are also included in the message attachment portion 1112.

[0118] The message section 1110 contains the chat session between users who have joined the event, wherein the user who joined the event can view the messages in the chat session that occurred after the user joined the event. Any messages in the chat session before the user joined are visible to other users who have already joined, but not to the new user who just joined. Any messages in the chat session that occurred after the new user joined will be visible to the new user. In another example embodiment, when a user joins the event, the user can view all messages that occurred before joining.

[0119] In another example implementation, when a user joins an event, the user can view all messages that occurred prior to joining. The message attachment section 1112 retains and displays any computing components that were transmitted or saved during the message section 1110 chat session between users who have joined the event. For example, links to websites, addresses, user names, images, videos, and any other form of electronic media saved or sent during the chat session are depicted in the message attachment section 1112.

[0120] Fig. 12A and Fig. 12B Example user interfaces 1200 and 1201 are shown, each depicting an event modifier interface 1204, according to one embodiment. In one example, a user navigates to an event modifier interface 1204 as an option stored in the example Fig. 12A An event modifier interface 1204 is shown within a menu icon 1202 at the top of the modified event overlay 906. Although menu icon 1202 is depicted as accessing event modifier interface 1204, any graphical icon or object may be used. Event modifier interface 1204 is generated depicting four options: (1) Manage Event; (2) Cancel Event; (3) Add Members; and (4) Edit Event Details.

[0121] In one example, when the manage event option is activated, the user (also referred to as the creator) will have the option to edit the details previously entered into the event editor interface 706. In another example, the user can also activate the cancel event option depicted in the event modifier interface 1204, where the user (e.g., the user who created the event) can cancel the event. When an event is canceled, the event group remains activated.

[0122] In another example, when an event is canceled, the computing device sends a request to the computing system to cancel the event. The computing system receives the request, stores an indication that the event is canceled, sends a notification to each user who joined the event that the event has been canceled, and changes the state of the event to indicate that the event is canceled. Fig. 12B As shown, the computing device displays the status of event 1206 to indicate that the event is canceled.

[0123] In one example implementation, the event group remains activated so that users who joined the event can continue chatting in the chat session. In another example, when the event is canceled, the interactive map portion 1108 is updated to depict that the event location no longer exists. In another example, a leave event interface notification option is displayed as an indicator to the event creator or event user notifying them that they have left the event.

[0124] When Fig. 12A and Fig. 12B When the add member option 1208 is activated in the event modifier interface 1204 shown in , the user can add one or more users to the event unilaterally or based on user recommendations. In one example, the add member option 1208 is also an interactive graphical icon, emoticon, avatar, or some other media icon object, such as Fig. 12B As shown. The computing device sends a request to the computing system to add the specified new user, and the computing system adds the user to the event. The computing system sends a response message to the computing device indicating that the user has successfully joined the event.

[0125] The computing device can display an indication to the user that they have successfully joined the event. In one example, the computing device displays a message indicating that the user has joined the chat interface to allow the user to chat with other users who have joined the event. In another example, when the edit event details in the event modifier interface 1204 is activated, the computing system displays Figure 7 The event editor interface 706 is shown. Once the event editor interface 706 is displayed, the user has the option of editing the event details, such as Figure 7 discussed.

[0126] Fig.13A and Fig. 13BExample user interfaces 1300 and 1301 are shown, each depicting an event chat interface 1304, according to one embodiment. As described above, when a user joins an event, the user gains access to the event chat interface, e.g. Fig.13A 13. The event chat interface 1304 is shown in FIG. The event chat interface 1304 depicts the event overlay component 704 title, the event chat banner 1302, and the event chat section 1308 at the top.

[0127] In one example, the event chat banner 1302 displays a message that the user is attending an event and may be deleted after an initial viewing or after a viewing after a predetermined period of time, as described above with respect to Figure 6 In another example, the event chat banner 1302 also includes one or more avatars 910 associated with each user who has received and accepted the event corresponding to the event overlay component 704.

[0128] An event details button 904 is included in the event chat interface 1304 and activates the event content and associated details of the event overlay component 704 when selected. The user also has the option of activating a contact invitation button 1306 to access a contact database or contact directory associated with the user of the device. Upon activating the contact database via the contact invitation button 1306, the user has the option of inviting additional contacts by selecting each contact to whom an invitation is to be sent. The computing device sends the event overlay component 704 to the associated computing device of each selected contact.

[0129] The event chat section 1308 is a real-time active chat session between users who have joined the event. Fig. 13B As depicted, when one or more new users join the event, the new user avatars 1310 are displayed directly into the event chat portion 1308. In another example, the user avatars 1310 are added to the separate portion 914 and the event chat banner 1302 is updated to show the added “new group members.” In one example, any messages in the chat session that occur after the new user joins will be visible to the new user, and any messages in the chat session that occurred before the new user joins will not be visible to the new user.

[0130] Fig.141400 within which instructions 1408 (e.g., software, programs, applications, applet, app, or other executable code) may be executed for causing the machine 1400 to perform any one or more of the methods discussed herein. For example, the instructions 1408 may cause the machine 1400 to perform any one or more of the methods described herein. The instructions 1408 transform a general purpose, unprogrammed machine 1400 into a specific machine 1400 that is programmed to perform the functions described and illustrated in the manner described. The machine 1400 may operate as a standalone device or may be coupled (e.g., networked) to other machines.

[0131] In a networked deployment, the machine 1400 may operate as a server or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 1400 may include, but is not limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a PDA, an entertainment media system, a cellular phone, 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 machine capable of executing instructions 1408 that specify actions to be taken by the machine 1400, either sequentially or in other ways. In addition, while only a single machine 1400 is shown, the term "machine" shall also be construed to include a collection of machines that individually or jointly execute instructions 1408 to perform any one or more of the methodologies discussed herein.

[0132] The machine 1400 may include a processor 1402, a memory 1404, and an I / O component 1438, which may be configured to communicate with each other via a bus 1440. In an example embodiment, the processor 1402 (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 ASIC, a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 1406 that executes instructions 1408 and a processor 1410.

[0133] The term "processor" is intended to include multi-core processors, which may include two or more independent processors (sometimes referred to as "cores") that can execute instructions simultaneously. Fig.14Multiple processors 1402 are shown, but the machine 1400 may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiple cores, or any combination thereof.

[0134] The memory 1404 includes a main memory 1412, a static memory 1414, and a storage unit 1416, which are all accessible by the processor 1402 via the bus 1410. The main memory 1404, the static memory 1414, and the storage unit 1416 store instructions 1408 that embody any one or more of the methods or functions described herein. The instructions 1408 may also reside, completely or partially, within the main memory 1412, within the static memory 1414, within the machine-readable medium 1418 within the storage unit 1416, within at least one of the processors 1402 (e.g., within a cache memory of a processor), or within any suitable combination thereof during execution thereof by the machine 1400.

[0135] I / O components 1438 may include various components that receive input, provide output, generate output, transmit information, exchange information, capture measurements, etc. The specific I / O components 1438 included in a particular machine will depend on the type of machine. For example, a portable machine such as a mobile phone may include a touch input device or other such input mechanism, while a headless server machine will likely not include such a touch input device. It will be appreciated that I / O components 1438 may include Fig.14 In various example implementations, the I / O components 1438 may include a user output component 1424 and a user input component 1426.

[0136] The user output components 1424 may include visual components (e.g., displays such as plasma display panels (PDPs), light emitting diode (LED) displays, liquid crystal displays (LCDs), projectors, or cathode ray tubes (CRTs)), auditory components (e.g., speakers), tactile components (e.g., vibration motors, resistance mechanisms), other signal generators, etc. The user input components 1426 may include alphanumeric input components (e.g., keyboards, touch screens configured to receive alphanumeric input, optical keyboards, or other alphanumeric input components), pointing-based input components (e.g., mice, touch pads, trackballs, joysticks, motion sensors, or another pointing instrument), tactile input components (e.g., physical buttons, touch screens or other tactile input components that provide location and / or force of touch or touch gestures), audio input components (e.g., microphones), etc.

[0137] In other example embodiments, the I / O component 1438 may include a biometric component 1428, a motion component 1430, an environmental component 1432, or a positioning component 1434, as well as various other components. For example, the biometric component 1428 includes components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body postures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweating, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition), etc. The motion component 1430 includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, and a rotation sensor component (e.g., a gyroscope).

[0138] The environment component 1432 includes, for example, one or more cameras (with still image / photo and video capabilities), an illumination sensor component (e.g., a photometer), a temperature sensor component (e.g., one or more thermometers that detect ambient temperature), a humidity sensor component, a pressure sensor component (e.g., a barometer), an acoustic sensor component (e.g., one or more microphones that detect background noise), a proximity sensor component (e.g., an infrared sensor that detects nearby objects), a gas sensor (e.g., a gas detection sensor for detecting concentrations of hazardous gases for safety reasons or for measuring pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment. The positioning component 1434 includes a position sensor component (e.g., a GPS receiver component), an altitude sensor component (e.g., an altimeter or barometer that detects air pressure from which altitude can be derived), an orientation sensor component (e.g., a magnetometer), etc.

[0139] Various technologies may be used to implement communications. I / O components 1438 also include communications components 1436 that are operable to couple machine 1400 to network 1420 or device 1422 via corresponding couplings or connections. For example, communications components 1436 may include a network interface component or another suitable device that interfaces with network 1420. In other examples, communications components 1436 may include wired communications components, wireless communications components, cellular communications components, near field communications (NFC) components, Components (e.g. Low power consumption), Device 1422 may be another machine or any of a variety of peripheral devices (eg, a peripheral device coupled via USB).

[0140] In addition, the communication component 1436 can detect an identifier or include a component operable to detect an identifier. For example, the communication component 1436 can include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting the following items: a one-dimensional barcode, such as a universal product code (UPC) barcode; a multi-dimensional barcode, such as a Quick Response (QR) code, Aztec code, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D barcode and other optical codes), or an auditory detection component (e.g., a microphone for identifying an audio signal of a tag). In addition, various information can be obtained via the communication component 1436, such as the location of a geographic location via an Internet Protocol (IP), the location of a location via a wireless network, and the location of a location via a wireless network. The location of signal triangulation, the location of an NFC beacon signal via detection that can indicate a specific location, etc.

[0141] Various memories (e.g., main memory 1412, static memory 1414, and / or memory of processor 1402) and / or storage unit 1416 may store one or more instruction sets and data structures (e.g., software) that embody or are used by any one or more of the methods or functions described herein. These instructions (e.g., instructions 1408) when executed by processor 1402 cause various operations to implement the disclosed embodiments.

[0142] The instructions 1408 may be sent or received over the network 1420 using a transmission medium, via a network interface device (e.g., a network interface component included in the communication component 1436), and using any of several well-known transmission protocols (e.g., the Hypertext Transfer Protocol (HTTP)). Similarly, the instructions 1408 may be sent or received via a coupling (e.g., a peer-to-peer coupling) to the device 1422 using a transmission medium.

[0143] Fig.151500 is a block diagram illustrating a software architecture 1504 that can be installed on any one or more of the devices described herein. The software architecture 1504 is supported by hardware, such as a machine 1502 including a processor 1520, a memory 1526, and an I / O component 1538. In this example, the software architecture 1504 can be conceptualized as a stack of layers, where each layer provides specific functionality. The software architecture 1504 includes layers such as an operating system 1512, a library 1515, a framework 1508, and an application 1506. In operation, the application 1506 calls an API call 1550 through the software stack and receives a message 1552 in response to the API call 1550.

[0144] The operating system 1512 manages hardware resources and provides public services. The operating system 1512 includes, for example, a kernel 1514, services 1516, and drivers 1522. The kernel 1514 acts as an abstraction layer between the hardware layer and other software layers. For example, the kernel 1514 provides functions such as memory management, processor management (such as scheduling), component management, network and security settings. Services 1516 can provide other public services for other software layers. Drivers 1522 are responsible for controlling or interfacing with the underlying hardware. For example, drivers 1522 may include display drivers, camera drivers, Driver or Low-power drivers, Flash memory drivers, serial communication drivers (for example, Universal Serial Bus (USB) drivers), Drivers, audio drivers, power management drivers, etc.

[0145] The library 1510 provides a low-level common infrastructure used by the application 1506. The library 1510 may include a system library 1518 (e.g., a C standard library) that provides functions such as memory allocation functions, string manipulation functions, mathematical functions, etc. In addition, the library 1510 may include an API library 1524, such as a media library (e.g., a library for supporting the presentation and manipulation of various media formats, such as Moving Picture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC), Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codec, Joint Photographic Experts Group (JPEG or JPG), or Portable Network Graphics (PNG)), a graphics library (e.g., an OpenGL framework for rendering in two dimensions (2D) and three dimensions (3D) in graphical content on a display), a database library (e.g., SQLite for providing various relational database functions), a web library (e.g., WebKit for providing web browsing functions), etc. The library 1510 may also include a variety of other libraries 1528 to provide many other APIs to the application 1506 .

[0146] The framework 1508 provides a high-level common infrastructure used by the applications 1506. For example, the framework 1508 provides various graphical user interface (GUI) functions, advanced resource management, and advanced positioning services. The framework 1508 can provide a wide range of other APIs that can be used by the applications 1506, some of which can be specific to a particular operating system or platform.

[0147] In an example implementation, applications 1506 may include home applications 1536, contacts applications 1530, browser applications 1532, book reader applications 1534, location applications 1542, media applications 1544, messaging applications 1546, game applications 1548, and a broad category of other applications such as third-party applications 1540. e applications 1506 are programs that perform functions defined in the program. Various programming languages ​​may be used to create one or more applications 1506 structured in various ways, such as object-oriented programming languages ​​(e.g., Objective-C, Java, or C++) or procedural programming languages ​​(e.g., C language or assembly language). In a specific example, third-party applications 1540 (e.g., those developed by entities other than the vendor of a particular platform using ANDROID TM or IOS TM Software Development Kit (SDK) can be used to develop applications on platforms such as IOS TM ANDROID TM , Mobile software running on the mobile operating system of the phone or other mobile operating systems. In this example, third-party applications 1540 can call API calls 1550 provided by the operating system 1512 to facilitate the functions described herein.

[0148] Throughout this specification, multiple instances can implement the parts, operations or structures described as single instances. Although the single operations of one or more methods are shown and described as separate operations, one or more single operations can be performed simultaneously, and there is no requirement to perform these operations in the order shown. The structure and function presented as a separate component in the example configuration can be implemented as a combined structure or component. Similarly, the structure and function presented as a single component can be implemented as a separate component. These and other variations, modifications, additions and improvements fall within the scope of the subject matter herein.

[0149] Although an overview of the inventive subject matter has been described with reference to specific example embodiments, various modifications and changes may be made to these embodiments without departing from the broader scope of the embodiments of the present disclosure.

[0150] The embodiments shown herein are described in sufficient detail to enable those skilled in the art to practice the disclosed teachings. Other embodiments may be used and derived therefrom, so that structural and logical substitutions and changes may be made without departing from the scope of the present disclosure. Therefore, the specific embodiments should not be understood in a limiting sense, and the scope of the various embodiments is limited only by the appended claims and the full scope of equivalents to which these claims are assigned.

[0151] As used herein, the term "or" may be interpreted in an inclusive or exclusive sense. In addition, multiple instances may be provided as a single instance for a resource, operation, or structure described herein. In addition, the boundaries between various resources, operations, modules, engines, and data stores are somewhat arbitrary, and specific operations are shown in the context of a specific illustrative configuration. Other functional allocations are contemplated and may fall within the scope of various embodiments of the present disclosure.

[0152] In general, structures and functions presented as separate resources in the example configurations may be implemented as combined structures or resources. Similarly, structures and functions presented as single resources may be implemented as separate resources. These and other variations, modifications, additions and improvements fall within the scope of the embodiments of the present disclosure as represented by the appended claims. Therefore, the description and drawings are to be regarded in an illustrative rather than a restrictive sense.

Claims

1. A method for generating an event coverage component, comprising: accessing a media content item by a first computing device associated with a first user; generating, by the first computing device, an event overlay interface for creating an event invitation for sending to a second computing device associated with a second user; displaying the event overlay interface as an overlay on the media content item on a user interface of the first computing device; receiving, by the first computing device via the event overlay interface, a user selection of an event overlay component; In response to receiving a user selection of an event overlay component, receiving event information provided by the first user; automatically determining a venue suggestion based on the location of the first computing device and the event information; updating the event coverage component based on the event information and the venue suggestion; causing the updated event overlay component to overlay the media content item; displaying the updated event overlay and the media content item on a user interface of the first computing device; as well as The media content item overlaid with the updated event overlay is sent to the second computing device for display on the second computing device.

2. The method for generating an event coverage component according to claim 1, wherein: The media content item is accessible for a predetermined time-limited duration, and The media content items include images, videos or texts.

3. The method for generating an event coverage component according to claim 1, further comprising: receiving a plurality of event coverage contents added to the event coverage component; The event coverage content includes time information, date information and description information.

4. The method for generating an event coverage component according to claim 3, further comprising: generating an event editor interface associated with the event overlay component; and Wherein, the event coverage content is added via the event editor interface.

5. The method for generating an event coverage component according to claim 1, further comprising: Receiving a content set of the event overlay component including an update, the content set including a set of messages and media content; providing an interactive join option to select said event overlay component associated with said updated event overlay component; receiving a selection of the interactive join option from the second computing device; as well as In response to receiving a selection of the interactive join option, an event overlay messaging interface is generated.

6. The method for generating an event coverage component according to claim 5, further comprising: Activate event coverage message delivery interface; adding a second user associated with the second computing device to an event coverage directory associated with the event coverage component; as well as An event coverage status icon is displayed in the event coverage message transmission interface, and the event coverage status icon includes a status notification that the second user has been added to the event coverage list.

7. The method for generating an event coverage component according to claim 6, wherein: The event overlay component also includes a user profile associated with the second computing device, a geographic map component, a message component, a description portion, and a media attachment component.

8. The method for generating an event coverage component according to claim 7, further comprising: generating an avatar based on a user profile associated with the second computing device; as well as An associated avatar is displayed in the event overlay messaging interface.

9. The method for generating an event coverage component according to claim 1, further comprising: Prior to receiving the selection, a messaging icon is displayed within a user interface of the first computing device, the messaging icon being used to indicate a status of a message separate from the media content item.

10. The method for generating an event coverage component according to claim 9, wherein: The messaging icon indicates whether a message separate from the media content item has been received, viewed, not yet viewed, expired, or sent with respect to the first computing device.

11. A server system, comprising: processor; as well as a memory storing instructions that, when executed by the processor, configure the server system to perform operations comprising: accessing a media content item by a first computing device associated with a first user; generating, by the first computing device, an event overlay interface for creating an event invitation for sending to a second computing device associated with a second user; displaying the event overlay interface as an overlay on the media content item on a user interface of the first computing device; receiving, by the first computing device via the event overlay interface, a user selection of an event overlay component; In response to receiving a user selection of an event overlay component, receiving event information provided by the first user; automatically determining a venue suggestion based on the location of the first computing device and the event information; updating the event coverage component based on the event information and the venue suggestion; causing the updated event overlay component to overlay the media content item; displaying the updated event overlay and the media content item on a user interface of the first computing device; as well as The media content item overlaid with the updated event overlay is sent to the second computing device for display on the second computing device.

12. The server system according to claim 11, wherein: The media content item is accessible for a predetermined time-limited duration, and The media content items include images, videos or texts.

13. The server system according to claim 11, wherein: The operations also include: receiving a plurality of event coverage contents added to the event coverage component; The event coverage content includes time information, date information and description information.

14. The server system according to claim 13, further comprising: generating an event editor interface associated with the event overlay component; and Wherein, the event coverage content is added via the event editor interface.

15. The server system according to claim 11, wherein: The instructions further configure the server system to perform operations including: Receiving a content set of the event overlay component including an update, the content set including a set of messages and media content; providing an interactive join option to select said event overlay component associated with said updated event overlay component; receiving a selection of the interactive join option from the second computing device; as well as In response to receiving a selection of the interactive join option, an event overlay messaging interface is generated.

16. The server system according to claim 15, further comprising: Activate event coverage message delivery interface; adding a second user associated with the second computing device to an event coverage directory associated with the event coverage component; as well as An event coverage status icon is displayed in the event coverage message transmission interface, and the event coverage status icon includes a status notification that the second user has been added to the event coverage list.

17. The server system according to claim 16, wherein: The event overlay component also includes a user profile associated with the second computing device, a geographic map component, a message component, a description portion, and a media attachment component.

18. The server system according to claim 17, wherein: The operations also include: generating an avatar based on a user profile associated with the second computing device; and An associated avatar is displayed in the event overlay messaging interface.

19. A non-transitory computer-readable storage medium comprising instructions that, when executed by a computer, cause the computer to perform operations comprising: accessing a media content item by a first computing device associated with a first user; generating, by the first computing device, an event overlay interface for creating an event invitation for sending to a second computing device associated with a second user; displaying the event overlay interface as an overlay on the media content item on a user interface of the first computing device; receiving, by the first computing device via the event overlay interface, a user selection of an event overlay component; In response to receiving a user selection of an event overlay component, receiving event information provided by the first user; automatically determining a venue suggestion based on the location of the first computing device and the event information; updating the event coverage component based on the event information and the venue suggestion; causing the updated event overlay component to overlay the media content item; displaying the updated event overlay and the media content item on a user interface of the first computing device; as well as The media content item overlaid with the updated event overlay is sent to the second computing device for display on the second computing device.

20. The non-transitory computer readable storage medium of claim 19, wherein: The instructions further configure the computer to perform operations including: Receiving a content set of the event overlay component including an update, the content set including a set of messages and media content; providing an interactive opt-in option to select an event overlay component profile associated with the updated event overlay component; receiving a selection of the interactive join option; responsive to receiving a selection of the interactive join option, activating an event overlay messaging interface; adding a user associated with the first computing device to an event coverage directory associated with the event coverage component configuration file; as well as An event coverage status icon is displayed in the event coverage component configuration file, the event coverage icon including a status notification that the user has been added to the event coverage directory.

Images