Unlockable content creation portal

Abstract

Embodiments herein describe a portal system for maintaining a user portal for managing and generating scannable images. The scannable image may be linked to different content types, such as website URLs, social media platform user profiles, and augmented reality experiences. The user portal is accessible from the social media platform via the user login credentials. Upon entering their user login credentials, the portal system authenticates the user login credentials and displays a list of existing scannable images stored in association with the user portal. A user may modify one or more aspects of an existing scannable image, or a new scannable image may be generated from the user interface.

Description

[0001] Priority claim

[0002] This application claims the benefit of priority to U.S. patent application serial number 18 / 165,747, filed on February 7, 2023, which is incorporated herein by reference in its entirety. Technical Field

[0003] Embodiments herein generally relate to scannable images. More specifically, but not by way of limitation, embodiments herein describe a content creation portal for generating and modifying scannable images. Background Art

[0004] Quick Response (QR) codes are often limited to having predefined functions and cannot be fully customized. This can be an unappealing experience for both users who want to share content and users who want to access it.

[0005] BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

[0006] In the drawings, which are not necessarily drawn to scale, like reference numerals may describe similar components in different views. To easily identify the discussion of any particular element or action, the highest-order digit or digits in a reference numeral refer to the figure in which the element is first introduced. Some non-limiting examples are shown in the figures of the accompanying drawings, in which:

[0007] Figure 1 is a diagrammatic representation of a networked environment in which the present disclosure may be deployed, according to some examples.

[0008] Figure 2 is a diagrammatic representation of a messaging system having both client-side and server-side functionality, according to some examples.

[0009] Figure 3 is a diagrammatic representation of data structures maintained in a database according to some examples.

[0010] Figure 4 is a diagrammatic representation of messages according to some examples.

[0011] Figure 5 A process for modifying unlockable data elements from a user portal of a social media application is shown, according to some examples.

[0012] Figure 6 is an illustration of a login screen for a portal system according to some examples.

[0013] Figure 7 is an illustration of a user portal interface generated by a portal system according to some examples.

[0014] Figure 8 is an illustration of an unlockable data element generation interface generated by a portal system according to some examples.

[0015] Figure 9 A system is shown in which a head wearable device is included according to some examples.

[0016] Figure 10 is a diagrammatic representation of a machine in the form of a computer system, according to some examples, within which a set of instructions may be executed, causing the machine to perform any one or more of the methodologies discussed herein.

[0017] Figure 11 is a block diagram illustrating a software architecture in which examples may be implemented. DETAILED DESCRIPTION

[0018] Current system users must navigate a different user interface for each type of functionality associated with a scannable image (e.g., a QR code). This process is inefficient and requires users to spend a significant amount of their time. Providing a comprehensive list of scannable images that a user has created in a single interface allows users to view all scannable images they have generated, helping to prevent duplicate scannable images from being generated. This unified interface collects all scannable images associated with a user into a user portal so that the user can modify, delete, or deactivate any individual scannable image without having to navigate multiple interfaces, thereby allowing for a more efficient computer system.

[0019] The following paragraphs describe a portal system for maintaining a user portal that is used to manage and generate scannable images. The scannable images can be linked to different content types, such as website URLs, social media platform user profiles, and augmented reality experiences. The user portal can be accessed from a mobile app or website of a social media platform via user login credentials. The user portal can be accessed via multiple user login credentials. For example, multiple members of a band may each have unique login credentials and unique user accounts, but can all access their band's band user portal. Each member of the band may also have a private user portal that is separate from their band user portal. For example, if a band member enters their login credentials, they can decide to select and thereby access either their band user portal or their private user portal.

[0020] Upon entering their user login credentials into the webpage or mobile application, the portal system will authenticate the user login credentials. The user is then directed to a user interface on the webpage or mobile application that displays a list of any existing scannable images stored in association with the user portal. The user can modify one or more aspects of an existing scannable image, or can generate a new scannable image from the webpage or user interface. For example, the user can modify the image, content type, and data associated with the scannable image. From within the user portal, the user can also view analytical insights associated with the scannable image. Further details of the portal system are described below.

[0021] Networked computing environment

[0022] Figure 1 1 is a block diagram illustrating an example interactive system 100 for facilitating interactions over a network (e.g., exchanging text messages, conducting text, audio, and video calls, or playing games). The interactive system 100 includes a plurality of client systems 102, each of which hosts a plurality of applications including an interactive client 104 and other applications 106. Each interactive client 104 is communicatively coupled to other instances of the interactive client 104 (e.g., hosted on respective other user systems 102), an interactive server system 110, and third-party servers 112 via one or more communication networks including a network 108 (e.g., the Internet). The interactive client 104 can also communicate with the locally hosted applications 106 using an application programming interface (API).

[0023] Each user system 102 may include multiple user devices, such as a mobile device 114 , a head wearable device 116 , and a computer client device 118 , which are communicatively connected to exchange data and messages.

[0024] The interactive clients 104 interact with other interactive clients 104 and with the interactive server system 110 via the network 108. The data exchanged between the interactive clients 104 (e.g., interaction 120) and between the interactive clients 104 and the interactive server system 110 includes functions (e.g., commands for activating functions) and payload data (e.g., text, audio, video, or other multimedia data).

[0025] The interactive server system 110 provides server-side functionality to the interactive clients 104 via the network 108. Although certain functions of the interactive system 100 are described herein as being performed by either the interactive clients 104 or the interactive server system 110, whether certain functions are located within the interactive clients 104 or within the interactive server system 110 may be a design choice. For example, it may be technically preferable to initially deploy certain technologies and functions within the interactive server system 110, but later migrate the technologies and functions to the interactive clients 104 where the user system 102 has sufficient processing power.

[0026] The interactive server system 110 supports various services and operations provided to the interactive clients 104. Such operations include sending data to the interactive clients 104, receiving data from the interactive clients 104, and processing data generated by the interactive clients 104. The data may include message content, client device information, geolocation information, media enhancements and overlays, message content persistence conditions, social network information, and live event information. The data exchange within the interactive system 100 is activated and controlled by functions available through the user interface (UI) of the interactive client 104.

[0027] Turning now specifically to the interaction server system 110, an application program interface (API) server 122 is coupled to the interaction server 124 and provides a programming interface thereto, making the functionality of the interaction server 124 accessible to the interaction clients 104, other applications 106, and third-party servers 112. The interaction server 124 is communicatively coupled to a database server 126, thereby facilitating access to a database 128 that stores data associated with interactions processed by the interaction server 124. Similarly, a web server 130 is coupled to the interaction server 124 and provides a web-based interface to the interaction server 124. To this end, the web server 130 processes incoming network requests via the Hypertext Transfer Protocol (HTTP) and several other related protocols.

[0028] The application program interface (API) server 122 receives and sends interaction data (e.g., commands and message payloads) between the interaction server 124 and the client system 102 (and, for example, the interaction client 104 and other applications 106), as well as the third-party server 112. Specifically, the application program interface (API) server 122 provides a set of interfaces (e.g., routines and protocols) that the interaction client 104 and other applications 106 can call or query to activate the functionality of the interaction server 124. The application program interface (API) server 122 exposes various functions supported by the interaction server 124, including account registration; login functionality; sending interaction data from a particular interaction client 104 to another interaction client 104 via the interaction server 124; transferring media files (e.g., images or videos) from the interaction client 104 to the interaction server 124; setting up a collection of media data (e.g., a story); retrieving a friend list of a user of the user system 102; retrieving messages and content; adding and removing entities (e.g., friends) from an entity graph (e.g., a social graph); locating friends within a social graph; and opening application events (e.g., related to the interaction client 104).

[0029] Interactive server 124 hosts multiple systems and subsystems, see below Figure 2 Provide a description.

[0030] Linked Applications

[0031] Returning to the interactive client 104, the features and functionality of external resources (e.g., linked applications 106 or mini-programs) are made available to the user via the interface of the interactive client 104. In this context, "external" refers to the fact that the application 106 or mini-program is external to the interactive client 104. External resources are typically provided by a third party, but may also be provided by the creator or provider of the interactive client 104. The interactive client 104 receives a user's selection of an option to launch or access features of such external resources. The external resource may be an application 106 installed on the user system 102 (e.g., a "local application"), or a small-scale version of an application (e.g., a "mini-program") hosted on the user system 102 or remote from the user system 102 (e.g., on a third-party server 112). The small-scale version of an application includes a subset of the features and functionality of the application (e.g., the full-scale, local version of the application) and is implemented using a markup language document. In some examples, the small-scale version of an application (e.g., a "mini-program") is a web-based markup language version of the application and is embedded in the interactive client 104. In addition to using markup language documents (eg, .*ml files), applets may incorporate scripting languages ​​(eg, .*js files or .json files) and style sheets (eg, .*ss files).

[0032] In response to receiving a user selection of an option to launch or access a feature of an external resource, the interactive client 104 determines whether the selected external resource is a web-based external resource or a locally installed application 106. In some cases, an application 106 installed locally on the user system 102 can be launched independently of and separately from the interactive client 104, for example, by selecting an icon corresponding to the application 106 on a home screen of the user system 102. A small-scale version of such an application can be launched or accessed via the interactive client 104, and in some examples, no portion of the small-scale application can be accessed outside of the interactive client 104 or only a limited portion of the small-scale application can be accessed outside of the interactive client 104. The small-scale application can be launched by the interactive client 104 receiving, for example, a markup language document associated with the small-scale application from the third-party server 112 and processing such a document.

[0033] In response to determining that the external resource is a locally installed application 106, the interactive client 104 instructs the user system 102 to launch the external resource by executing locally stored code corresponding to the external resource. In response to determining that the external resource is a web-based resource, the interactive client 104 communicates with the third-party server 112 (for example) to obtain a markup language document corresponding to the selected external resource. The interactive client 104 then processes the obtained markup language document to present the web-based external resource within the user interface of the interactive client 104.

[0034] The interactive client 104 can notify the user of the user system 102 or other users associated with such user (e.g., "friends") of activities occurring in one or more external resources. For example, the interactive client 104 can provide participants in a conversation (e.g., a chat session) within the interactive client 104 with notifications related to the current or recent use of an external resource by one or more members of the user group. One or more users can be invited to join an active external resource, or a recently used but currently inactive external resource (in a friend group) can be launched. The external resource can provide participants in the conversation (each using their own interactive client 104) with the ability to share items, conditions, states, or locations within the external resource during a chat session with one or more members of the user group. Shared items can be interactive chat cards, with which chat members can interact, for example, to launch the corresponding external resource, view specific information within the external resource, or be taken to a specific location or state within the external resource. Within a given external resource, a response message can be sent to the user on the interactive client 104. Based on the current context of the external resource, the external resource can selectively include different media items in the response.

[0035] The interactive client 104 can present a list of available external resources (e.g., applications 106 or applets) to the user to launch or access a given external resource. The list can be presented in a context-sensitive menu. For example, the icons representing different applications in the applications 106 (or applets) can change based on how the user launches the menu (e.g., from a conversational interface or from a non-conversational interface).

[0036] System Architecture

[0037] Figure 2 1 is a block diagram illustrating additional details regarding the interactive system 100 according to some examples. Specifically, the interactive system 100 is shown to include an interactive client 104 and an interactive server 124. The interactive system 100 includes a plurality of subsystems that are supported on the client side by the interactive client 104 and on the server side by the interactive server 124. Example subsystems are discussed below.

[0038] Image processing system 202 provides various functions that enable a user to capture and enhance (eg, annotate or otherwise modify or edit) media content associated with a message.

[0039] The camera system 204 includes control software (e.g., in a camera application) that interacts with and controls the hardware camera hardware of the user system 102 (e.g., directly or via operating system control) to modify and enhance the real-time images captured and displayed via the interactive client 104.

[0040] The enhancement system 206 provides functionality related to the generation and publication of enhancements (e.g., media overlays) for images captured in real time by the camera of the user system 102 or retrieved from the memory of the user system 102. For example, the enhancement system 206 is operable to select, present, and display media overlays (e.g., image filters or image lenses) for the interactive client 104 for enhancing the real-time imagery received via the camera system 204 or the stored imagery retrieved from the memory 902 of the user system 102. These enhancements are selected by the enhancement system 206 and presented to the user of the interactive client 104 based on inputs and data, such as:

[0041] The geolocation of the user system 102; and

[0042] Social network information of users of the user system 102 .

[0043] Enhancement can 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 can be applied to media content items (e.g., photos or videos) at user system 102 for transmitting in a message, or applied to video content, such as a video content stream or feed sent from interactive client 104. Therefore, image processing system 202 can interact with and support the various subsystems of communication system 208, such as messaging system 210 and video communication system 212.

[0044] Media overlays can include text or image data that can be superimposed on a photo taken by user system 102 or a video stream produced by user system 102. In some examples, the media overlay can be a location overlay (e.g., Venice Beach), the name of a live event, or a business name overlay (e.g., Beach Cafe). In another example, image processing system 202 uses the geographic location of user system 102 to identify a media overlay that includes the name of a business at the geographic location of user system 102. Media overlays may include other tags associated with the business. Media overlays may be stored in database 128 and accessed through database server 126.

[0045] Image processing system 202 provides a user-based publishing platform that enables users to select a geographic location on a map and upload content associated with the selected geographic location. Users can also specify situations in which specific media overlays should be provided to other users. Image processing system 202 generates a media overlay that includes the uploaded content and associates it with the selected geographic location.

[0046] The augmented reality creation system 214 supports the augmented reality developer platform and includes applications for content creators (e.g., artists and developers) to create and publish augmentations (e.g., augmented reality experiences) for the interactive clients 104. The augmented reality creation system 214 provides content creators with a library of built-in features and tools, including, for example, custom shaders, tracking techniques, and templates.

[0047] In some examples, the enhancement creation system 214 provides a merchant-based publishing platform that enables merchants to select specific enhancements associated with a geolocation via a bidding process. For example, the enhancement creation system 214 associates the highest bidding merchant's media overlay with the corresponding geolocation for a predefined amount of time.

[0048] The communication system 208 is responsible for enabling and processing various forms of communication and interaction within the interactive system 100 and includes a messaging system 210, an audio communication system 216, and a video communication system 212. The messaging system 210 is responsible for implementing temporary or time-limited access to content by the interactive clients 104. The messaging system 210 includes a plurality of timers (e.g., in a transient timer system 218) that selectively enable access (e.g., for presentation and display) of messages and associated content via the interactive clients 104 based on duration and display parameters associated with a message or a collection of messages (e.g., a story). Additional details regarding the operation of the transient timer system 218 are provided below. The audio communication system 216 enables and supports audio communication (e.g., real-time audio chat) between multiple interactive clients 104. Similarly, the video communication system 212 enables and supports video communication (e.g., real-time video chat) between multiple interactive clients 104.

[0049] The user management system 220 is operationally responsible for managing user data and profiles, and includes a social networking system 222 that maintains information about relationships between users of the interactive system 100 .

[0050] The collection management system 224 is operationally responsible for managing collections or collections of media (e.g., collections of text, images, video, and audio data). Collections of content (e.g., messages, including images, video, text, and audio) can be organized into "event libraries" or "event stories." Such collections can be made available for a specified time period (e.g., the duration of the event to which the content relates). For example, content related to a concert can be made available as a "story" for the duration of the concert. The collection management system 224 is also responsible for publishing icons to the user interface of the interactive client 104 that provide notifications of specific collections. The collection management system 224 includes curation functionality that enables collection managers to manage and curate specific content collections. For example, a curation interface enables event organizers to curate collections of content related to a specific event (e.g., removing inappropriate content or redundant messages). In addition, the collection management system 224 employs machine vision (or image recognition technology) and content rules to automatically curate content collections. In some examples, users can be paid to include user-generated content in collections. In such cases, the collection management system 224 operates to automatically pay such users for use of their content.

[0051] The mapping system 226 provides various geolocation functions and supports the presentation of map-based media content and messages by the interactive client 104. For example, the mapping system 226 enables the display of a user icon or avatar (e.g., stored in the profile data 302) on a map to indicate the current or past locations of the user's "friends" and media content generated by these friends (e.g., a collection of messages including photos and videos) within the context of the map. For example, a message posted by a user to the interactive system 100 from a particular geolocation can be displayed to a particular user's "friends" on the map interface of the interactive client 104 within the context of that particular location on the map. A user can also share his or her location and status information with other users of the interactive system 100 via the interactive client 104 (e.g., using an appropriate status avatar), where the location and status information is similarly displayed to selected users within the context of the map interface of the interactive client 104.

[0052] The gaming system 228 provides various gaming functions within the context of the interactive client 104. The interactive client 104 provides a gaming interface that provides a list of available games that can be launched by a user within the context of the interactive client 104 and played with other users of the interactive system 100. The interactive system 100 also enables a particular user to invite other users to play a particular game by sending an invitation to such other users from the interactive client 104. The interactive client 104 also supports voice, video, and text messaging (e.g., chat) within the context of game play, provides leaderboards for games, and also supports the provision of in-game rewards (e.g., game coins and items).

[0053] The external resource system 230 provides an interface for the interactive client 104 to communicate with a remote server (e.g., a third-party server 112) to launch or access external resources (i.e., applications or applets). Each third-party server 112 hosts, for example, an application or a small-scale version of an application (e.g., a game application, a utility application, a payment application, or a ride-sharing application) based on a markup language (e.g., HTML5). The interactive client 104 can launch a web-based resource (e.g., an application) by accessing an HTML5 file from a third-party server 112 associated with the web-based resource. The applications hosted by the third-party server 112 are programmed in JavaScript using a software development kit (SDK) provided by the interactive server 124. The SDK includes an application programming interface (API) with functions that can be called or activated by a web-based application. The interactive server 124 hosts a JavaScript library that provides access to a given external resource for specific user data of the interactive client 104. HTML5 is an example of a technology for programming games, but applications and resources programmed based on other technologies can be used.

[0054] To integrate the SDK's functionality into a web-based resource, the third-party server 112 downloads the SDK from the interaction server 124, or the third-party server 112 receives the SDK in some other manner. Once downloaded or received, the SDK is included as part of the application code of the external web-based resource. The code of the web-based resource can then call or activate certain functions of the SDK to integrate the features of the interaction client 104 into the web-based resource.

[0055] The SDK stored on the interactive server system 110 effectively provides a bridge between external resources (e.g., applications 106 or applets) and the interactive client 104. This gives users a seamless experience of communicating with other users on the interactive client 104 while also preserving the look and feel of the interactive client 104. In order to bridge the communication between the external resources and the interactive client 104, the SDK facilitates communication between the third-party server 112 and the interactive client 104. The WebViewJavaScriptBridge running on the user system 102 establishes two one-way communication channels between the external resources and the interactive client 104. Messages are sent asynchronously between the external resources and the interactive client 104 via these communication channels. Each SDK function activation is sent as a message and a callback. Each SDK function is implemented by constructing a unique callback identifier and sending a message with the callback identifier.

[0056] By using the SDK, not all information from the interactive client 104 is shared with the third-party server 112. The SDK limits which information is shared based on the needs of the external resource. Each third-party server 112 provides an HTML5 file corresponding to the web-based external resource to the interactive server 124. The interactive server 124 can add a visual representation (e.g., a block diagram or other graphic) of the web-based external resource in the interactive client 104. Once the user selects the visual representation or instructs the interactive client 104 to access a feature of the web-based external resource through the GUI of the interactive client 104, the interactive client 104 obtains the HTML5 file and instantiates the resource for accessing the feature of the web-based external resource.

[0057] The interactive client 104 presents a graphical user interface (e.g., a login page or title screen) for the external resource. During, before, or after presenting the login page or title screen, the interactive client 104 determines whether the launched external resource has been previously authorized to access the user data of the interactive client 104. In response to determining that the launched external resource has been previously authorized to access the user data of the interactive client 104, the interactive client 104 presents another graphical user interface of the external resource that includes the functions and features of the external resource. In response to determining that the launched external resource has not been previously authorized to access the user data of the interactive client 104, after displaying the login page or title screen of the external resource for a threshold period of time (e.g., 3 seconds), the interactive client 104 slides up a menu (e.g., animating the menu to emerge from the bottom of the screen to the middle or other portion of the screen) for authorizing the external resource to access the user data. The menu identifies the type of user data that the external resource is authorized to use. In response to receiving a user selection of the accept option, the interactive client 104 adds the external resource to the list of authorized external resources and allows the external resource to access the user data from the interactive client 104. The interactive client 104 authorizes external resources to access user data under the OAuth 2 framework.

[0058] The interaction client 104 controls the type of user data shared with the external resource based on the type of external resource that is authorized. For example, an external resource comprising a full-scale application (e.g., application 106) is provided with access to a first type of user data (e.g., a two-dimensional avatar of the user with or without different avatar characteristics). As another example, an external resource comprising a small-scale version of an application (e.g., a web-based version of the application) is provided with access to a second type of user data (e.g., payment information, a two-dimensional avatar of the user, a three-dimensional avatar of the user, and an avatar with various avatar characteristics). Avatar characteristics include different ways to customize the look and feel of an avatar (e.g., different poses, facial features, clothing, etc.).

[0059] The advertising system 232 operatively enables third parties to purchase advertisements for presentation to end users via the interactive clients 104 and also handles the delivery and presentation of these advertisements.

[0060] The portal system 234 enables maintenance and management of a user portal on a social media platform (e.g., application 106). The portal system 234 receives login credentials from the interactive client 104 and authenticates the login credentials based on login data stored in a database (e.g., database 128). Upon authentication, the portal system 234 causes a list of unlockable elements associated with the user portal to be displayed. Unlockable elements are scannable images that can be scanned by a camera device to view various content, including but not limited to websites, AR experiences (e.g., accessed from the augmented creation system 214), games (e.g., accessed from the gaming system 228), user profiles (e.g., accessed from the user management system 220), and the like. The portal system 234 also allows users to modify one or more aspects of existing unlockable elements and generate new unlockable elements.

[0061] Data Architecture

[0062] Figure 3 is a diagram illustrating a data structure 300 that may be stored in a database 304 of the interactive server system 110 according to certain examples. Although the contents of the database 304 are shown as including a plurality of tables, it should be understood that data may be stored in other types of data structures (e.g., an object-oriented database).

[0063] The database 304 includes message data stored in a message table 306. For any particular message, the message data includes at least message sender data, message recipient (or receiver) data, and payload. Figure 3 Additional details regarding information that may be included in a message and included within the message data stored in message table 306 are described.

[0064] The entity table 308 stores entity data and is linked (e.g., by reference) to the entity graph 310 and the profile data 302. Entities for which records are maintained within the entity table 308 may include individuals, corporate entities, organizations, objects, places, events, and the like. Regardless of the entity type, any entity for which the interactive server system 110 stores data may be an identified entity. Each entity is provided with a unique identifier and an entity type identifier (not shown).

[0065] The entity graph 310 stores information related to relationships and associations between entities. By way of example only, such relationships may be social, professional (e.g., working at a common company or organization), interest-based, or activity-based. Some relationships between entities may be unidirectional, such as a subscription by an individual user to digital content from a business or publication (e.g., a newspaper or other digital media channel or brand). Other relationships may be bidirectional, such as a "friend" relationship between various users of the interactive system 100.

[0066] Certain permissions and relationships can be attached to each relationship, and can also be attached to each direction of the relationship. For example, a two-way relationship (e.g., a friend relationship between individual users) can include authorization to publish digital content items between the individual users, but certain restrictions or filters (e.g., based on content characteristics, location data, or time of day data) can be placed on the publication of such digital content items. Similarly, a subscription relationship between an individual user and a business user can impose varying degrees of restrictions on the publication of digital content from the business user to the individual user, and can significantly limit or prevent the publication of digital content from the individual user to the business user. As an example of an entity, a particular user can record certain restrictions in the record for that entity within the entity table 308 (e.g., through privacy settings). Such privacy settings can apply to all types of relationships in the context of the interactive system 100, or can be selectively applied to certain types of relationships.

[0067] Profile data 302 stores various types of profile data about a particular entity. Based on the privacy settings specified by the particular entity, profile data 302 can be selectively used and presented to other users of the interactive system 100. In the case where the entity is a person, profile data 302 includes, for example, the user's name, phone number, address, settings (e.g., notification and privacy settings), and an avatar representation (or a collection of such avatar representations) selected by the user. The particular user can then selectively include one or more of these avatar representations within the content of messages transmitted via the interactive system 100 and on a map interface displayed to other users by the interactive client 104. The collection of avatar representations can include a "status avatar," which presents a graphical representation of the user's status or activity that they may choose to transmit at a particular time.

[0068] Where the entity is a group, profile data 302 for the group may similarly include one or more avatar representations associated with the group, in addition to the group name, members, and various settings for the relevant group (eg, notifications).

[0069] Database 304 also stores enhancement data, such as overlays or filters, in enhancement table 312. Enhancement data is associated with and applied to videos (video data is stored in video table 314) and images (image data is stored in image table 316).

[0070] In some examples, filters are displayed as overlays on an image or video during presentation to a recipient user. Filters can be of various types, including filters selected by a user from a set of filters presented to a sending user by the interactive client 104 when the sending user is composing a message. Other types of filters include geolocation filters (also referred to as geofilters), which can be presented to a sending user based on geolocation. For example, a geolocation filter specific to a nearby or special location can be presented by the interactive client 104 within the user interface based on geolocation information determined by a global positioning system (GPS) unit of the user system 102.

[0071] Another type of filter is a data filter, which can be selectively presented to the sending user by the interaction client 104 based on other input or information collected during the message creation process by the user system 102. Examples of data filters include the current temperature at a particular location, the current speed the sending user is traveling, the battery life of the user system 102, or the current time.

[0072] Other augmented data that can be stored in the image table 316 include augmented reality content items (e.g., 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.

[0073] The story table 318 stores data about a collection of messages and associated images, video, or audio data that are compiled into a collection (e.g., a story or gallery). The creation of a particular collection can be initiated by a particular user (e.g., each user for whom a record is maintained in the entity table 308). A user can create a "personal story" in the form of a collection of content that has been created and sent / broadcasted by that user. To this end, the user interface of the interactive client 104 can include a user-selectable icon that enables the sending user to add specific content to his or her personal story.

[0074] The collection can also constitute a "live story", which is a collection of content from multiple users created manually, automatically, or using a combination of manual and automatic techniques. For example, a "live story" can 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 can be presented with the option to contribute content to a particular live story, for example, via the user interface of the interactive client 104. Live stories can be identified to the user by the interactive client 104 based on his or her location. The end result is a "live story" told from the perspective of the group.

[0075] Another type of content collection is called a "location story," which enables users whose user systems 102 are located in a particular geographic location (e.g., on a college or university campus) to contribute to a particular collection. In some examples, contributions to location stories may employ secondary authentication to verify that the end user belongs to a particular organization or other entity (e.g., is a student on a university campus).

[0076] As mentioned above, video table 314 stores video data that, in some examples, is associated with messages whose records are maintained within message table 306. Similarly, image table 316 stores image data associated with messages whose message data is stored in entity table 308. Entity table 308 can associate various enhancements from enhancement table 312 with the various images and videos stored in image table 316 and video table 314.

[0077] The database 304 also includes an unlockable data element table 320 that stores unlockable elements associated with various user portals within the portal system 234 .

[0078] Data communication architecture

[0079] Figure 4 is a schematic diagram illustrating the structure of a message 400 according to some examples, the message 400 being generated by an interaction client 104 for transmission to another interaction client 104 via an interaction server 124. The content of a particular message 400 is used to populate a message table 306 stored within a database 304 accessible by the interaction server 124. Similarly, the content of the message 400 is stored in memory as "in-transit" or "in-flight" data of the user system 102 or the interaction server 124. The message 400 is shown as including the following example components:

[0080] Message identifier 402 : A unique identifier that identifies the message 400 .

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

[0082] • Message image payload 406: Image data captured by the camera component of the user system 102 or retrieved from the memory component of the user system 102 and included in the message 400. The image data for a message 400 sent or received may be stored in the image table 316.

[0083] • Message video payload 408: Video data captured by the camera component or retrieved from the memory component of the user system 102 and included in the message 400. The video data for a message 400 sent or received may be stored in the image table 316.

[0084] • Message audio payload 410 : audio data captured by a microphone or retrieved from a memory component of the user system 102 and included in the message 400 .

[0085] Message enhancement data 412: Enhancement data (e.g., filters, stickers, or other annotations or enhancements) representing enhancements to be applied to the message image payload 406, message video payload 408, or message audio payload 410 of the message 400. Enhancement data for a sent or received message 400 may be stored in the enhancement table 312.

[0086] • Message duration parameter 414: A parameter value indicating the amount of time, in seconds, that the content of the message (e.g., message image payload 406, message video payload 408, message audio payload 410) is to be presented to or made accessible to the user via the interactive client 104.

[0087] Message geolocation parameters 416: Geolocation data (e.g., latitude and longitude coordinates) associated with the content payload of the message. Multiple message geolocation parameter 416 values ​​can 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 the message image payload 406 or a specific video within the message video payload 408).

[0088] Message story identifier 418: An identifier value that identifies one or more content collections (e.g., a "story" identified in stories table 318) associated with a particular content item in message image payload 406 of message 400. For example, the identifier value can be used to associate multiple images within message image payload 406 with multiple content collections.

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

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

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

[0092] The content (e.g., value) of each component of message 400 may be a pointer to a location in a table where the content data value is stored. For example, the image value in message image payload 406 may be a pointer to a location in image table 316 (or the address of a location in image table 316). Similarly, the value in message video payload 408 may point to data stored in image table 316, the value stored in message enhancement data 412 may point to data stored in enhancement table 312, the value stored in message story identifier 418 may point to data stored in story table 318, and the values ​​stored in message sender identifier 422 and message recipient identifier 424 may point to user records stored in entity table 308.

[0093] Figure 5 A process 500 of modifying unlockable data elements from a user portal of a social media application according to one example is shown. In one example, a processor in the portal system 234, a processor in the interactive client 104, a processor in the interactive server system 110, or any combination thereof can perform the operations in the process 500.

[0094] In operation 502, the portal system 234 receives, via a processor, user login credentials associated with a user portal. The user login credentials are associated with a user account of a social media application (eg, the social networking system 222).

[0095] In operation 504, the portal system 234 authenticates the received user login credentials through the processor. For example, the portal system 234 can use the database of profile data 302 to authenticate the user login credentials.

[0096] In operation 506, the portal system 234 accesses a set of unlockable data elements associated with the user portal. The set of unlockable data elements includes an image and media content associated with the image. The unlockable data element is a scannable image that, when scanned, presents the media content associated with the image. The media content can be a website, a user profile for a social media application, an augmented reality experience, a game, and the like.

[0097] In operation 508, the portal system 234 causes the accessed set of unlockable data elements to be displayed on the user interface of the webpage. The set of unlockable data elements can be displayed in order based on creation date, with the most recently created unlockable data elements displayed first. In some examples, the set of unlockable data elements is grouped according to content type. For example, unlockable data elements associated with a website are displayed in a first portion of the user interface, unlockable data elements associated with a user profile are displayed in a second portion of the user interface, and unlockable data elements associated with an augmented reality experience are displayed in a third portion of the user interface. It should be understood that any sorting scheme can be applied to the display of the set of unlockable data elements.

[0098] In operation 510, portal system 234 receives a selection of an unlockable data element from the set of unlockable data elements. In operation 512, in response to the selection, portal system 234 modifies one or more aspects of the selected unlockable data element. The modification may include modifying an image associated with the unlockable data element, modifying a content type associated with the unlockable data element, or modifying data associated with the unlockable data element. Modifying an image, content type, or data associated with an unlockable data element may include replacing the original media, content type, or data with new media, content type, or data.

[0099] In some examples, each unlockable data element in the set of unlockable data elements is associated with an analytics icon displayed adjacent to the display of the unlockable data element. Selection of the analytics icon causes the display of analytics information associated with the corresponding unlockable data element. For example, the analytics information may include the total number and unique number of scans, location data associated with the scans, user information associated with the scans, user device information associated with the scans, and the like.

[0100] In some examples, the portal system 234 receives a second user login credential associated with the user portal. The second user login credential is associated with a second user account that is different from the user login credential and user account described above. After authenticating the second user login credential, the portal system 234 causes the accessed set of unlockable data elements associated with the user portal to be displayed. Thus, multiple user login credentials (and associated user accounts) can access a single user portal. Each unlockable data element in a shared user portal can have additional access restrictions. For example, only a first user may be allowed to modify a first unlockable data element, but not a second unlockable data element. Thus, access restrictions can be set at the user portal level and for each unlockable data element within the portal. In addition, a single user can access multiple user portals. For example, a user can have a private user portal that can only be accessed by that user and a shared user portal that can be accessed by a predefined user group.

[0101] The portal system 234 can also be used to generate new unlockable data elements. The portal system 234 receives a selection from a web page and accesses an image. The portal system 234 then receives a subsequent selection by the user of a user interface element associated with a content type that the user wishes to associate with the new unlockable data element. The portal system 234 receives data including the selected content type and generates an unlockable data element using the image and the received data. The portal system 234 stores the unlockable data element in association with the user portal (e.g., in the unlockable data element table 320).

[0102] The unlockable data element described above is generated on a first computer device (eg, a client device). A second client device including an image capture unit can scan the unlockable data element to access media content associated with the unlockable data element.

[0103] In some examples, the portal system 234 includes an icon displayed near the display of the unlockable data element. The icon can be selected to view the analytical data associated with the unlockable data element. Additional information about the user interface is provided below.

[0104] Figure 6 6 is an example user interface 602 generated by the portal system 234. The user interface 602 is a login screen. Upon selecting button 604, the user is prompted by the portal system 234 to enter their login credentials.

[0105] Figure 7 708 is an example user interface generated by the portal system 234. The user interface 708 is a diagram of a user portal. The user portal includes various unlockable data elements (e.g., 702, 704, and 706). Each unlockable data element is associated with a name (e.g., (710, 712, and 714)). When selecting the unlockable data element itself or the name associated with the unlockable data element, each unlockable data element can be modified. When selecting an icon (e.g., 716), the unlockable data element can also be deleted. When selecting an icon (e.g., 720), the entire user portal can also be deleted. The analytical insights associated with a specific unlockable data element can be viewed by selecting an icon (e.g., 718). The aggregated analytical insights associated with all unlockable data elements in the user portal can be viewed by selecting an icon (e.g., 722). In addition, from within the user portal, the user can create a new unlockable data element by selecting a user interface element (e.g., 724).

[0106] After selecting the user interface 724, the portal system 234 enables Figure 8802 for generating a new unlockable data element. In field 818, the user can upload an image to be used with the new unlockable data element. The user must also select the type of content associated with the image (e.g., website URL 804, augmented reality experience 806 (or image overlay), or user profile 808). If the user is creating an unlockable data element of the website URL 804 type, they can enter the website address in field 810. If the user is creating an augmented reality experience 806 or user profile 808, the user may need to upload data from their computer client device 118 or from any suitable location where data is stored. The portal system 234 also allows the user to navigate back to the user interface 708 when selecting user interface element 814. When selecting user interface element 816, the user can view information and guidance that helps to correctly use the portal system 234. Once the unlockable data element is generated, it can be viewed from the user's user portal.

[0107] For example, if a user scans an unlockable data element associated with a website URL 804, the user will be navigated to the URL on their client device. If a user scans an unlockable data element associated with an AR experience 806, the AR experience 806 will appear on their client device. If the unlockable data element is associated with a user profile 808, then upon scanning the unlockable data element, the user will be navigated to the user profile within the social networking application.

[0108] System with head wearable device

[0109] Figure 9 A system 900 is shown that includes a head wearable device 116 with a selector input device according to some examples. Figure 9 is a high-level functional block diagram of an example head wearable device 116 communicatively coupled to a mobile device 114 and various server systems 904 (eg, interactive server system 110 ) via various networks 108 .

[0110] The head wearable device 116 includes one or more cameras, each of which may be, for example, a visible light camera 906 , an infrared emitter 908 , and an infrared camera 910 .

[0111] The mobile device 114 is connected to the head wearable device 116 using both a low power wireless connection 912 and a high speed wireless connection 914. The mobile device 114 is also connected to the server system 904 and the network 916.

[0112] The head wearable device 116 also includes two image displays of the optical assembly 918. The two image displays 918 of the optical assembly include one image display associated with the left lateral side of the head wearable device 116 and one image display associated with the right lateral side of the head wearable device 116. The head wearable device 116 also includes an image display driver 920, an image processor 922, low-power circuitry 924, and high-speed circuitry 926. The image displays 918 of the optical assembly are used to present images and videos to a user of the head wearable device 116, including images that may include a graphical user interface.

[0113] The image display driver 920 commands and controls the image display 918 of the optical assembly. The image display driver 920 can deliver image data directly to the image display 918 of the optical assembly for presentation, or can convert the image data into a signal or data format suitable for delivery to an image display device. For example, the image data can be video data formatted according to a compression format such as H.264 (MPEG-4 Part 10), HEVC, Theora, Dirac, RealVideo RV40, VP8, VP9, ​​etc., while the still image data can be formatted according to a compression format such as Portable Network Graphics (PNG), Joint Photographic Experts Group (JPEG), Tagged Image File Format (TIFF), or Exchangeable Image File Format (EXIF).

[0114] The head-wearable device 116 includes a frame and rods (or temples) extending from lateral sides of the frame. The head-wearable device 116 also includes a user input device 928 (e.g., a touch sensor or button), comprising an input surface on the head-wearable device 116. The user input device 928 (e.g., a touch sensor or button) is used to receive input selections from the user for manipulating the graphical user interface of the presented image.

[0115] Figure 9 The components for the head wearable device 116 shown in FIG are located on one or more circuit boards (e.g., PCBs or flexible PCBs) in the bezel or temples. Alternatively or additionally, the depicted components may be located in a block, frame, hinge, or nosepiece of the head wearable device 116. The left and right visible light cameras 906 may include digital camera elements, such as complementary metal oxide semiconductor (CMOS) image sensors, charge coupled devices, camera lenses, or any other corresponding visible light or light capturing elements that can be used to capture data, including images of a scene with an unknown object.

[0116] The head wearable device 116 includes a memory 902 that stores instructions for performing a subset or all of the functionality described herein. The memory 902 may also include a storage device.

[0117] like Figure 9 As shown, high-speed circuitry 926 includes a high-speed processor 930, memory 902, and high-speed wireless circuitry 932. In some examples, an image display driver 920 is coupled to high-speed circuitry 926 and operated by high-speed processor 930 to drive the left and right image displays of the optical assembly's image display 918. High-speed processor 930 can be any processor capable of managing high-speed communications and operations required by any general-purpose computing system for head-wearable device 116. High-speed processor 930 includes the processing resources required to manage high-speed data transmission over high-speed wireless connection 914 to a wireless local area network (WLAN) using high-speed wireless circuitry 932. In some examples, high-speed processor 930 executes an operating system (e.g., a Linux operating system) or other such operating system for head-wearable device 116, and the operating system is stored in memory 902 for execution. In addition to any other responsibilities, high-speed processor 930, which executes the software architecture of head-wearable device 116, manages data transmission with high-speed wireless circuitry 932. In some examples, high-speed wireless circuitry 932 is configured to implement the Institute of Electrical and Electronics Engineers (IEEE) 802.11 communication standard, also referred to herein as WiFi. In some examples, high-speed wireless circuitry 932 can implement other high-speed communication standards.

[0118] The low-power wireless circuitry 934 and high-speed wireless circuitry 932 of the head wearable device 116 may include a short-range transceiver (Bluetooth TM ) and a wireless wide area network transceiver, a wireless local area network transceiver, or a wide area network transceiver (e.g., cellular or WiFi). Mobile device 114—including a transceiver that communicates via low-power wireless connection 912 and a high-speed wireless connection 914—can be implemented using details of the architecture of head wearable device 116, as can other elements of network 916.

[0119] Memory 902 comprises any storage device capable of storing various data and applications, including camera data generated by left and right visible light cameras 906, infrared camera 910, and image processor 922, as well as images generated for display on an image display 918 of the optical assembly via image display driver 920. While memory 902 is shown as being integrated with high-speed circuitry 926, in some examples, memory 902 may be a separate, standalone component of head-worn device 116. In some such examples, electrical wiring may provide a connection from image processor 922 or low-power processor 936 to memory 902 via a chip including high-speed processor 930. In some examples, high-speed processor 930 may manage addressing of memory 902, such that low-power processor 936 will initiate high-speed processor 930 whenever a read or write operation involving memory 902 is required.

[0120] like Figure 9 As shown, the low-power processor 936 or the high-speed processor 930 of the head wearable device 116 can be coupled to a camera device (a visible light camera device 906, an infrared emitter 908 or an infrared camera device 910), an image display driver 920, a user input device 928 (for example, a touch sensor or button) and a memory 902.

[0121] The head-worn device 116 is connected to a host computer. For example, the head-worn device 116 is paired with the mobile device 114 via a high-speed wireless connection 914 or is connected to a server system 904 via a network 916. The server system 904 can be one or more computing devices that are part of a service or network computing system, for example, including a processor, memory, and a network communication interface to communicate with the mobile device 114 and the head-worn device 116 via the network 916.

[0122] The mobile device 114 includes a processor and a network communication interface coupled to the processor. The network communication interface allows communication via a network 916, a low-power wireless connection 912, or a high-speed wireless connection 914. The mobile device 114 may also store at least a portion of the instructions for generating binaural audio content in a memory of the mobile device 114 to implement the functionality described herein.

[0123] The output components of the head-worn device 116 include visual components such as a display, such as a liquid crystal display (LCD), a plasma display panel (PDP), a light-emitting diode (LED) display, a projector, or a waveguide. The image display of the optical assembly is driven by an image display driver 920. The output components of the head-worn device 116 also include acoustic components (e.g., speakers), tactile components (e.g., vibration motors), other signal generators, and the like. The input components of the head-worn device 116, the mobile device 114, and the server system 904 (e.g., user input devices 928) may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, an optical keyboard, or other alphanumeric input components), point-based input components (e.g., a mouse, touchpad, trackball, joystick, motion sensor, or other pointing instrument), tactile input components (e.g., physical buttons, a touch screen that provides location and force of touch or touch gestures, or other tactile input components), audio input components (e.g., a microphone), and the like.

[0124] The head wearable device 116 may also include additional peripheral elements. Such peripheral elements may include biometric sensors, additional sensors, or display elements integrated with the head wearable device 116. For example, the peripheral elements may include any I / O component including an output component, a motion component, a positioning component, or any other such component described herein.

[0125] For example, the biometric recognition component includes a component for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body postures, or eye tracking), measuring biological signals (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 electroencephalogram-based recognition), etc. The motion component includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, a rotation sensor component (e.g., a gyroscope), etc. The positioning component includes a position sensor component for generating position coordinates (e.g., a global positioning system (GPS) receiver component), a Wi-Fi or Bluetooth receiver for generating positioning system coordinates, etc. TM transceiver, altitude sensor components (e.g., an altimeter or barometer that detects air pressure, from which altitude can be derived), orientation sensor components (e.g., a magnetometer), etc. Such positioning system coordinates can also be received from the mobile device 114 via the low-power wireless connection 912 and the high-speed wireless connection 914 via the low-power wireless circuitry 934 or the high-speed wireless circuitry 932.

[0126] Machine Architecture

[0127] Figure 101 is a diagrammatic representation of a machine 1000 within which instructions 1002 (e.g., software, programs, applications, applet, apps, or other executable code) may be executed for causing the machine 1000 to perform any one or more of the methodologies discussed herein. For example, the instructions 1002 may cause the machine 1000 to perform any one or more of the methodologies described herein. The instructions 1002 transform a general-purpose, unprogrammed machine 1000 into a specific machine 1000 that is programmed to perform the functions described and illustrated in the manner described. The machine 1000 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 1000 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 1000 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 personal digital assistant (PDA), an entertainment media system, a cellular phone, a smartphone, 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 sequentially or otherwise executing instructions 1002 specifying actions to be taken by the machine 1000. Furthermore, while a single machine 1000 is shown, the term "machine" should also be construed to include a collection of machines that individually or jointly execute instructions 1002 to perform any one or more of the methodologies discussed herein. For example, the machine 1000 may include the user system 102 or any of a plurality of server devices forming part of the interactive server system 110. In some examples, the machine 1000 may also include both a client system and a server system, wherein certain operations of a particular method or algorithm are performed on the server side, and wherein certain operations of the particular method or algorithm are performed on the client side.

[0128] The machine 1000 may include a processor 1004, a memory 1006, and input / output I / O components 1008 that may be configured to communicate with each other via a bus 1010. In an example, the processor 1004 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 1012 that executes instructions 1002 and a processor 1014. The term "processor" is intended to include multi-core processors, which may include two or more independent processors (sometimes referred to as "cores") that may execute instructions concurrently. Although Figure 10 Multiple processors 1004 are shown, but the machine 1000 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.

[0129] The memory 1006 includes a main memory 1016, a static memory 1018, and a storage unit 1020, all of which are accessible by the processor 1004 via the bus 1010. The main memory 1006, the static memory 1018, and the storage unit 1020 store instructions 1002 that implement any one or more of the methodologies or functions described herein. The instructions 1002 may also reside, completely or partially, within the main memory 1016, within the static memory 1018, within the machine-readable medium 1022 within the storage unit 1020, within at least one of the processors 1004 (e.g., within a cache memory of the processor), or any suitable combination thereof during execution thereof by the machine 1000.

[0130] The I / O components 1008 may include various components for receiving input, providing output, generating output, sending information, exchanging information, capturing measurements, etc. The specific I / O components 1008 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 be less likely to include such a touch input device. It should be appreciated that the I / O components 1008 may include Figure 10Many other components are not shown in the drawings. In various examples, the I / O components 1008 may include user output components 1024 and user input components 1026. The user output components 1024 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)), acoustic components (e.g., speakers), tactile components (e.g., vibration motors, resistance mechanisms), other signal generators, etc. The user input components 1026 may include alphanumeric input components (e.g., keyboards, touch screens configured to receive alphanumeric input, optical keyboards, or other alphanumeric input components), point-based input components (e.g., mice, touch pads, trackballs, joysticks, motion sensors, or other pointing instruments), tactile input components (e.g., physical buttons, touch screens that provide location and force of touches or touch gestures, or other tactile input components), audio input components (e.g., microphones), etc.

[0131] In other examples, the I / O component 1008 may include a biometric component 1028, a motion component 1030, an environmental component 1032, or a positioning component 1034, as well as a wide range of other components. For example, the biometric component 1028 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, sweat, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or electroencephalogram-based recognition), etc. The motion component 1030 includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, and a rotation sensor component (e.g., a gyroscope).

[0132] Environmental components 1032 include, 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 purposes or for measuring pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment.

[0133] With respect to cameras, the user system 102 can have a camera system that includes, for example, a front-facing camera on the front surface of the user system 102 and a rear-facing camera on the rear surface of the user system 102. The front-facing camera can, for example, be used to capture still images and videos of the user of the user system 102 (e.g., “selfies”), which can then be enhanced with the enhancement data (e.g., filters) described above. For example, the rear-facing camera can be used to capture still images and videos in a more conventional camera mode, where the images are similarly enhanced with the enhancement data. In addition to the front-facing camera and the rear-facing camera, the user system 102 can also include a 360° camera for capturing 360° photos and videos.

[0134] Furthermore, the camera system of the user system 102 may include dual rear cameras (e.g., a main camera and a depth-sensing camera), or even triple, quad, or quintuple rear camera configurations on the front and back sides of the user system 102. For example, these multi-camera systems may include a wide-angle camera, an ultra-wide-angle camera, a telephoto camera, a macro camera, and a depth sensor.

[0135] The positioning component 1034 includes a position sensor component (for example, a GPS receiver component), an altitude sensor component (for example, an altimeter or barometer that detects air pressure, and the altitude can be obtained according to the air pressure), an orientation sensor component (for example, a magnetometer), etc.

[0136] Various technologies can be used to implement communications. The I / O components 1008 also include a communications component 1036 that is operable to couple the machine 1000 to a network 1038 or device 1040 via corresponding couplings or connections. For example, the communications component 1036 may include a network interface component or another suitable device that interfaces with the network 1038. In other examples, the communications component 1036 may include a wired communications component, a wireless communications component, a cellular communications component, a near field communications (NFC) component, a Components (e.g. Low energy consumption), Device 1040 may be another machine or any of a variety of peripheral devices (eg, a peripheral device coupled via USB).

[0137] Additionally, the communication component 1036 can detect an identifier, or include components operable to detect an identifier. For example, the communication component 1036 can include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., for detecting one-dimensional bar codes such as Universal Product Code (UPC) bar codes, multi-dimensional bar codes such as Quick Response (QR) codes, Aztec codes, Data Matrix, Dataglyph, etc.), or a combination of these components. TM , MaxiCode, PDF417, UltraCode, UCC RSS-2D barcode and other optical codes) or acoustic detection components (e.g., microphone for audio signal recognition of tags). In addition, various information can be obtained via the communication component 1036, such as location via Internet Protocol (IP) geolocation, location information via Signal triangulation to obtain location, location obtained by detecting NFC beacon signals that can indicate a specific location, etc.

[0138] Various memories (e.g., main memory 1016, static memory 1018, and memory of processor 1004) and storage unit 1020 may store one or more sets of instructions and data structures (e.g., software) implemented or used by any one or more of the methods or functions described herein. These instructions (e.g., instructions 1002) when executed by processor 1004 cause various operations to implement the disclosed examples.

[0139] Instructions 1002 may be sent or received over network 1038 using a transmission medium via a network interface device (e.g., a network interface component included in communications component 1036) and using any of several well-known transmission protocols (e.g., Hypertext Transfer Protocol (HTTP)). Similarly, instructions 1002 may be sent or received via a coupling (e.g., a peer-to-peer coupling) with device 1040 using a transmission medium.

[0140] Software Architecture

[0141] Figure 1111 is a block diagram 1100 illustrating a software architecture 1102 that can be installed on any one or more of the devices described herein. The software architecture 1102 is supported by hardware, such as a machine 1104 including a processor 1106, memory 1108, and I / O components 1110. In this example, the software architecture 1102 can be conceptualized as a stack of layers, where each layer provides specific functionality. The software architecture 1102 includes layers such as an operating system 1112, libraries 1114, frameworks 1116, and applications 1118. In operation, applications 1118 invoke API calls 1120 through the software stack and receive messages 1122 in response to API calls 1120.

[0142] The operating system 1112 manages hardware resources and provides common services. The operating system 1112 includes, for example, a kernel 1124, services 1126, and drivers 1128. The kernel 1124 serves as an abstraction layer between the hardware and other software layers. For example, the kernel 1124 provides functions such as memory management, processor management (e.g., scheduling), component management, networking, and security settings. Services 1126 can provide other common services to other software layers. Drivers 1128 are responsible for controlling or interfacing with the underlying hardware. For example, drivers 1128 may include display drivers, camera drivers, or Low-power drivers, Flash drivers, serial communication drivers (e.g., USB drivers), drivers, audio drivers, power management drivers, etc.

[0143] The libraries 1114 provide a common low-level infrastructure used by the applications 1118. The libraries 1114 may include a system library 1130 (e.g., a C standard library) that provides functions such as memory allocation functions, string manipulation functions, mathematical functions, etc. In addition, the libraries 1114 may include an API library 1132, 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 graphical content on a display in two dimensions (2D) and three dimensions (3D), a database library (e.g., SQLite providing various relational database functions), a web library (e.g., WebKit providing web browsing functions), etc. The library 1114 may also include a variety of other libraries 1134 to provide many other APIs to the application 1118 .

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

[0145] In an example, the applications 1118 may include a home application 1136, a contacts application 1138, a browser application 1140, a book reader application 1142, a location application 1144, a media application 1146, a messaging application 1148, a game application 1150, and a variety of other applications such as third-party applications 1152. The applications 1118 are programs that perform functions defined in the program. Various programming languages ​​may be used to create one or more of the applications 1118 structured in various ways, such as object-oriented programming languages ​​(e.g., Objective-C, Java, or C++) or procedural programming languages ​​(e.g., C or assembly language). In a specific example, the third-party applications 1152 (e.g., those written by entities other than the vendor of a particular platform using ANDROID) may be used to create a third-party application 1152. 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 system. In this example, the third party application 1152 can activate the API call 1120 provided by the operating system 1112 to facilitate the functions described in this article.

[0146] in conclusion

[0147] The portal system 234 allows for the efficient creation and distribution of unlockable data elements. Multiple users with different user accounts can access a single shared user portal through unique login credentials. Various levels of access restrictions allow users to control the entire user portal or individual unlockable data elements within the user portal.

[0148] Glossary

[0149] "Carrier signal" refers to any intangible medium, such as a digital or analog communication signal, that is capable of storing, encoding, or carrying instructions for execution by a machine, or other intangible medium that facilitates communication of such instructions. Instructions may be sent or received over a network using a transmission medium via a network interface device.

[0150] "Client device" refers to any machine that interfaces with a communications network to obtain resources from one or more server systems or other client devices, for example. A client device may be, but is not limited to, a mobile phone, a desktop computer, a laptop computer, a portable digital assistant (PDA), a smartphone, a tablet computer, an ultrabook, a netbook, a laptop computer, a multiprocessor system, a microprocessor-based or programmable consumer electronics product, a game console, a set-top box, or any other communications device that a user may use to access a network.

[0151] "Communications network" refers to, for example, one or more parts of a network, which may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a part of the Internet, a part of the Public Switched Telephone Network (PSTN), a Plain Old Telephone Service (POTS) network, a cellular telephone network, a wireless network, The network, other types of networks, or a combination of two or more such networks. For example, the network or a portion of the network may include a wireless network or a cellular network, and the coupling may be a code division multiple access (CDMA) connection, a global system for mobile communications (GSM) connection, or other types of cellular or wireless coupling. In this example, the coupling may implement any of various types of data transmission technologies, such as single carrier radio transmission technology (1xRTT), evolution data optimized (EVDO) technology, general packet radio service (GPRS) technology, enhanced data rates for GSM evolution (EDGE) technology, the third generation partnership project (3GPP) including 3G, fourth generation wireless (4G) networks, universal mobile telecommunications system (UMTS), high speed packet access (HSPA), world wide interoperability for microwave access (WiMAX), long term evolution (LTE) standards, other data transmission technologies defined by various standards setting organizations, other long distance protocols, or other data transmission technologies.

[0152] "Component" refers to a logic or device, a physical entity, for example, having the following boundaries, which are defined by function or subroutine calls, branch points, APIs, or other technologies that provide partitioning or modularization for specific processing or control functions. A component can be combined with other components via its interface to perform machine processing. A component can be a packaged functional hardware unit designed for use with other components and a part of a program that generally performs a specific function of a related function. A component can constitute a software component (for example, a code implemented on a machine-readable medium) or a hardware component. A "hardware component" is a tangible unit that can perform certain operations and can be configured or arranged in a certain physical manner. In various examples, one or more computer systems (for example, a stand-alone computer system, a client computer system, or a server computer system) or one or more hardware components (for example, a processor or a processor group) of a computer system can be configured by software (for example, an application or an application part) to operate as a hardware component that performs certain operations as described herein. Hardware components can also be implemented mechanically, electronically, or in any suitable combination thereof. For example, a hardware component can include a dedicated circuit system or logic that is permanently configured to perform certain operations. The hardware component can be a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC). The hardware component can also include a programmable logic or circuit system that is temporarily configured to perform certain operations by software. For example, the hardware component can include software executed by a general-purpose processor or other programmable processor. Once configured by such software, the hardware component becomes a specific machine (or a specific component of a machine), which is uniquely customized to perform the configured function and is no longer a general-purpose processor. It will be recognized that the decision to mechanically implement the hardware component in a dedicated and permanently configured circuit system or in a temporarily configured (e.g., configured by software) circuit system can be driven by cost and time considerations. Therefore, the phrase "hardware component" (or "hardware-implemented component") should be understood to include tangible entities, that is, entities that are physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) to operate in some way or perform certain operations described herein. Considering the example in which the hardware component is temporarily configured (e.g., programmed), it is not necessary to configure or instantiate each hardware component in the hardware component at any one time. For example, in the case where a hardware component includes a general-purpose processor that is configured by software to become a special-purpose processor, the general-purpose processor can be configured as a different special-purpose processor (e.g., including different hardware components) at different times. The software configures a specific one or more processors accordingly, such as to constitute a specific hardware component at one time and to constitute a different hardware component at a different time. A hardware component can provide information to other hardware components and receive information from other hardware components. Thus, the described hardware components can be considered to be communicatively coupled.In the case of multiple hardware components being present at the same time, communication can be achieved by signal transmission between or among two or more hardware components (for example, by appropriate circuits and buses). In the example in which multiple hardware components are configured or instantiated at different times, communication between such hardware components can be achieved, for example, by storing information in a memory structure accessible to multiple hardware components and retrieving information in the memory structure. For example, a hardware component can perform an operation, and the output of the operation is stored in a memory device coupled to its communication ground. Then, other hardware components can access the memory device at a subsequent time to retrieve the stored output and process it. The hardware component can also initiate communication with an input device or an output device, and can operate on resources (for example, a collection of information). The various operations of the example methods described herein can be performed at least in part by one or more processors that are temporarily configured (for example, by software) or permanently configured to perform related operations. Whether temporarily configured or permanently configured, such a processor can constitute a component that is operated to perform one or more operations or functions described herein. As used herein, a "processor-implemented component" refers to a hardware component implemented using one or more processors. Similarly, the method described in this article can be implemented at least in part by a processor, wherein specific one or more processors are examples of hardware. For example, at least some of the various operations of the method can be performed by one or more processors or the parts implemented by the processor. In addition, one or more processors can also be operated to support the execution of the related operations in a "cloud computing" environment or as "software as a service" (SaaS) operation. For example, at least some operations in the operation can be performed by a computer group (as an example of a machine including a processor), wherein these operations can be accessed via a network (for example, the Internet) and via one or more appropriate interfaces (for example, API). The execution of some operations can be distributed between processors, is not only resident in a single machine, but is deployed across multiple machines. In some examples, a processor or the parts implemented by the processor can be located in a single geographical location (for example, in a home environment, an office environment or a server farm). In other examples, a processor or the parts implemented by the processor can be distributed across multiple geographical locations.

[0153] "Computer-readable storage media" refers to, for example, both machine storage media and transmission media. Thus, these terms encompass both storage devices / media and carrier waves / modulated data signals. The terms "machine-readable medium," "computer-readable medium," and "device-readable medium" mean the same thing and may be used interchangeably in this disclosure.

[0154] A "transient message" is a message that is accessible for a limited duration, for example. Transient messages can be text, images, videos, and the like. The access period for a transient message can be set by the message sender. Alternatively, the access period can be a default setting or a setting specified by the recipient. Regardless of the setting technique, the message is transient.

[0155] “Machine storage media” refers to, for example, a single or multiple storage devices and media (e.g., centralized or distributed databases, and associated caches and servers) that store executable instructions, routines, and data. Thus, the term should be taken to include, but is not limited to, solid-state memory and optical and magnetic media, including memory internal or external to the processor. Specific examples of machine storage media, computer storage media, and device storage media include: non-volatile memory, including, for example, semiconductor memory devices such as erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGAs, and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The terms “machine storage media,” “device storage media,” and “computer storage media” mean the same thing and may be used interchangeably in this disclosure. The terms “machine storage media,” “computer storage media,” and “device storage media” expressly exclude carrier waves, modulated data signals, and other such media, at least some of which are encompassed by the term “signal media.”

[0156] “Non-transitory computer-readable storage medium” refers to a tangible medium that is capable of storing, encoding, or carrying instructions for execution by a machine, for example.

[0157] "Signal medium" refers to any intangible medium that is capable of storing, encoding, or carrying instructions for execution by a machine and includes digital or analog communication signals, or other intangible media that facilitates the communication of software or data. The term "signal medium" should be taken to include any form of modulated data signals, carrier waves, etc. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. The terms "transmission medium" and "signal medium" mean the same thing and may be used interchangeably in this disclosure.

[0158] A "user device" refers to a device that is, for example, accessed, controlled, or owned by a user and with which the user interacts to perform actions or interact with other users or computer systems.

Claims

1. A method comprising: receiving, by a processor, user login credentials associated with a user portal; authenticating, by the processor, the received user login credentials; accessing a set of unlockable data elements associated with the user portal, the set of unlockable data elements comprising an image and media content associated with the image; causing the accessed set of unlockable data elements to be displayed on a user interface of the webpage; receiving a selection of an unlockable data element from the set of unlockable data elements; as well as In response to the selection, one or more aspects of the selected unlockable data element are modified.

2. The method according to claim 1, further comprising: receiving a second selection from the webpage; responsive to the second selection, accessing a second image; receiving a third selection of a user interface element from the webpage, the user interface element being associated with a content type; receiving data including the content type; generating a second unlockable data element using the second image, the second image being associated with the data; as well as The second unlockable data element is stored in association with the user portal.

3. The method according to claim 1, wherein The unlockable data element is configured to present the media content when scanned by a camera unit.

4. The method according to claim 2, wherein: The content type includes at least one of a website, an augmented reality experience, or a user profile.

5. The method according to claim 2, wherein: The image is an original image, and wherein modifying one or more aspects of the selected unlockable data element further comprises: Access new images; associating the new image with the data; and The original image is replaced with the new image.

6. The method according to claim 2, wherein: The data is original data, and the content type is a first content type, and wherein modifying one or more aspects of the selected unlockable data element further comprises: accessing new data comprising a second content type, the second content type being different from the first content type; associating the new data with the selected unlockable data element; and The original data is replaced with the new data.

7. The method according to claim 1, wherein The user login credential is a first user login credential, and the method further includes: receiving second user login credentials associated with the user portal; authenticating the second user login credentials; and The accessed set of unlockable data elements associated with the user portal is caused to be displayed.

8. The method according to claim 1, further comprising: receiving a selection of an icon displayed adjacent to the selected unlockable data element; as well as In response to the selection, analytical data associated with the selected unlockable data element is caused to be displayed.

9. A system comprising: processor; as well as a memory storing instructions that, when executed by the processor, configure the system to perform operations comprising: receiving user login credentials associated with a user portal; authenticating the received user login credentials; accessing a set of unlockable data elements associated with the user portal, the set of unlockable data elements comprising an image and media content associated with the image; causing the accessed set of unlockable data elements to be displayed on a user interface of the webpage; receiving a selection of an unlockable data element from the set of unlockable data elements; and In response to the selection, one or more aspects of the selected unlockable data element are modified.

10. The system according to claim 9, wherein: The instructions further configure the system to: receiving a second selection from the webpage; responsive to the second selection, accessing a second image; receiving a third selection of a user interface element from the webpage, the user interface element being associated with a content type; receiving data including the content type; generating a second unlockable data element using the second image, the second image being associated with the data; as well as The second unlockable data element is stored in association with the user portal.

11. The system according to claim 9, wherein: The unlockable data element is configured to present the media content when scanned by a camera unit.

12. The system according to claim 10, wherein: The content type includes at least one of a website, an augmented reality experience, or a user profile.

13. The system according to claim 10, wherein: The image is an original image, and wherein modifying one or more aspects of the selected unlockable data element further comprises: Access new images; associating the new image with the data; and The original image is replaced with the new image.

14. The system according to claim 10, wherein: The data is original data, and the content type is a first content type, and wherein modifying one or more aspects of the selected unlockable data element further comprises: accessing new data comprising a second content type, the second content type being different from the first content type; associating the new data with the selected unlockable data element; and The original data is replaced with the new data.

15. The system according to claim 9, wherein: The user login credential is a first user login credential, wherein the instruction further includes: receiving second user login credentials associated with the user portal; authenticating the second user login credentials; and The accessed set of unlockable data elements associated with the user portal is caused to be displayed.

16. The system according to claim 9, wherein: The instructions also include: receiving a selection of an icon displayed adjacent to the selected unlockable data element; and In response to the selection, analytical data associated with the selected unlockable data element is caused to be displayed.

17. A non-transitory computer-readable storage medium comprising instructions that, when executed by a computer, cause the computer to perform operations comprising: receiving user login credentials associated with a user portal; authenticating the received user login credentials; accessing a set of unlockable data elements associated with the user portal, the set of unlockable data elements comprising an image and media content associated with the image; causing the accessed set of unlockable data elements to be displayed on a user interface of the webpage; receiving a selection of an unlockable data element from the set of unlockable data elements; as well as In response to the selection, one or more aspects of the selected unlockable data element are modified.

18. The computer-readable storage medium of claim 17, wherein: The instructions also include: receiving a second selection from the webpage; responsive to the second selection, accessing a second image; receiving a third selection of a user interface element from the webpage, the user interface element being associated with a content type; receiving data including the content type; generating a second unlockable data element using the second image, the second image being associated with the data; and The second unlockable data element is stored in association with the user portal.

19. The computer-readable storage medium of claim 17, wherein: The unlockable data element is a scannable image.

20. The computer-readable storage medium of claim 19, wherein: The scannable image is created by a first user device, and the instructions further include: An indication is received that the scannable image was scanned by a second user device, the second user device being different from the first user device.

Images