Aspects of the present disclosure involve a system comprising a computer-readable storage medium storing at least one program, method, and user interface to facilitate reward-based real-time communication between multiple users over a network. receiving, from a first device of a first user, a request for a real-time communication session. A request for a real-time communication session is received from a first device of a first user. Based on the request, the real-time communication session is established between the first user and a second user. A reward associated with participation by the second user in the real-time communication session is determined and provided to the second user.

TECHNICAL FIELD

The present disclosure generally relates to mobile and wearable computing technology. In particular, example embodiments of the present disclosure address systems, methods, and user interfaces to facilitate reward-based real-time communication sessions between users.

BACKGROUND

Many wearable and mobile devices such as “smart” glasses include an embedded camera. Users of these devices often stream video produced by an embedded camera to other users' devices using mobile device software applications and online platforms.

DETAILED DESCRIPTION

Aspects of the present disclosure include systems, methods, techniques, instruction sequences, and computing machine program products for facilitating real-time communication sessions between users. In this context, a request for a real-time communication session is generated based on input from a first user that includes criteria for identifying a second user to be included in the real-time communication session. As an example, the request may specific a target location at or near which the second user is to be located. The request can further indicate a reward to be provided to the second user for participating in the real-time communication session. One or more candidate users are identified based on the request and the candidate users are provided with a notification of the request along with an invitation to join the real-time communication session.

A real-time communication session is established between the first user and a second user that accepts the invitation. For example, the request may specify a target location and the second user that accepts the invitation can be identified based on being proximate to the target location. When a real-time communication session is established between a first user and a second user, a live camera feed that depicts a real-world environment at the location of the second user is presented to the first user. As an example, the second user may be wearing a wearable device that includes a camera and optical elements that include a transparent display through which the real-world environment is visible to the second user. During an active real-time communication session with the second user, the first user can view the real-world environment of the second user via the live camera feed generated by the camera of the second user's wearable device and displayed by a device of the first use and the first and second user can communicate verbally using an audio communication link between devices and also using augmented reality-based communication methods.

Upon termination of the real-time communication session, a reward is determined based on the second user's participation in the real-time communication session and provided to the second user. The reward can be based any one or more of: a reward amount specified in the request, a reward rate specified in the request, a reward type specified in the request, a default or baseline amount set for participating in the real-time communication session, a task performed by the second user that is specified in the request, a distance between the second user and the target location at the time of the request, and a duration of the session.

FIG. 1is a block diagram showing an example communication system100for exchanging data (e.g., messages and associated content) over a network. The communication system100includes multiple instances of a client device102(102-1and102-2). Each instance of the client device102hosts a number of applications including a communication client application104. Each communication client application104is communicatively coupled to other instances of the communication client application104and a communication server system108via a network106(e.g., the Internet).

A communication client application104is able to communicate and exchange data with another communication client application104and with the communication server system108via the network106. The data exchanged between communication client application104, and between a communication client application104and the communication server system108, includes functions (e.g., commands to invoke functions) as well as payload data (e.g., text, audio, video or other multimedia data).

The communication server system108provides server-side functionality via the network106to a particular communication client application104. While certain functions of the communication system100are described herein as being performed by either a communication client application104or by the communication server system108, the location of certain functionality either within the communication client application104or the communication server system108is a design choice. For example, it may be technically preferable to initially deploy certain technology and functionality within the communication server system108, but to later migrate this technology and functionality to the communication client application104where a client device102has a sufficient processing capacity.

The Application Program Interface (API) server110receives and transmits message data (e.g., commands and message payloads) between the client device102and the application server112. Specifically, the Application Program Interface (API) server110provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the communication client application104in order to invoke functionality of the application server112. The Application Program Interface (API) server110exposes various functions supported by the application server112, including account registration, login functionality, the sending of messages, via the application server112, from a particular communication client application104to another communication client application104, the sending of media files (e.g., images or video) from a communication client application104to the communication server application114, and for possible access by another communication client application104, the setting of a collection of media data (e.g., story), the retrieval of a list of friends of a user of a Client device102, the retrieval of such collections, the retrieval of messages and content, the adding and deletion of friends to a social graph, the location of friends within a social graph, and opening an application event (e.g., relating to the communication client application104).

The application server112hosts a number of applications and subsystems, including a communication server application114, an image processing system116and a social network system122. The communication server application114implements a number of message processing technologies and functions, particularly related to the aggregation and other processing of content (e.g., textual and multimedia content) included in messages received from multiple instances of the communication client application104. As will be described in further detail, the text and media content from multiple sources may be aggregated into collections of content (e.g., called stories or galleries). These collections are then made available, by the communication server application114, to the communication client application104. Other processor and memory intensive processing of data may also be performed server-side by the communication server application114, in view of the hardware requirements for such processing.

The communication server application114also facilities real-time communication sessions between users. To establish a real-time communication session between user103-1of client device102-1and user103-2of client device102-2, the communication server application114causes client device102-1to display a live camera feed that depicts a real-world environment at the location of the user103-2. In an example, the client device102-2is a wearable device (e.g., smart glasses) worn by the user103-2that includes a camera and optical elements that include a transparent display through which the real-world environment is visible to the user103-2. While the real-time communication session between the users103-1and103-2is active, the user103-1can view the real-world environment of the user103-2via the live camera feed generated by the camera of the client device102-2and displayed by the client device102-1. The communication server application114also enables the users103-1and103-2verbally using an audio communication and augmented reality based communication modalities.

In the context of a real-time communication session, a request is generated based on input from an initiating user (e.g., the user103-1) that specifies one or more parameters for the session such as a target location at which a participating user (e.g., the user103-2) is to be located. A notification that includes an invitation to join the real-time communication session is provided to one or more users, and the real-time communication session is established between the initiating user and a second user (e.g., the user103-2that accepts the invitation. At the conclusion of the real-time communication session, a reward for participating in the real-time communication session is determined and provided to the second user.

The application server112also includes an image processing system116that is dedicated to performing various image processing operations, typically with respect to images or video generated and displayed by instances of the client device102.

The social network system122supports various social networking functions services, and makes these functions and services available to the communication server application114. To this end, the social network system122maintains and accesses an entity graph within the database120. Examples of functions and services supported by the social network system122include the identification of other users of the communication system100with which a particular user has relationships or is “following”, and also the identification of other entities and interests of a particular user.

The application server112is communicatively coupled to a database server118, which facilitates access to a database120in which is stored data associated with messages processed by the communication server application114.

FIG. 2is block diagram illustrating further details regarding the communication system100, according to example embodiments. Specifically, the communication system100is shown to comprise the communication client application104and the application server112, which in turn embody a number of subsystems, namely an ephemeral timer system202, a collection management system204, and a virtual rendering system206.

The ephemeral timer system202is responsible for enforcing temporary access to content permitted by the client application104and the application server112. To this end, the ephemeral timer system202incorporates a number of timers that, based on duration and display parameters associated with a message, or collection of messages (e.g., a story), selectively display and enable access to messages and associated content via the client application104.

The collection management system204is responsible for managing collections of media (e.g., collections of text, image, video, and audio data). In some examples, a collection of content (e.g., messages, including images, video, text, and audio) may be organized into an “event gallery” or an “event story.” Such a collection may be made available for a specified time period, such as the duration of an event to which the content relates. For example, content relating to a music concert may be made available as a “story” for the duration of that music concert.

The collection management system204furthermore includes a curation interface208that allows a collection manager to manage and curate a particular collection of content. For example, the curation interface208enables an event organizer to curate a collection of content relating to a specific event (e.g., delete inappropriate content or redundant messages). Additionally, the collection management system204employs machine vision (or image recognition technology) and content rules to automatically curate a content collection.

The virtual rendering system206provides various functions that enable a user to augment or otherwise modify or edit media content (e.g., comprising image data and/or audio data). For example, the virtual rendering system206provides functions related to application of virtual content to real-world environments whether through display of media objects on transparent displays through which a real-world environment is visible or through augmenting image data to include media objects overlaid on real-world environments depicted therein. The virtual content may comprise one or more media objects. A media object may include audio and visual content and visual effects. Examples of audio and visual content include pictures, texts, logos, animations, and sound effects. The audio and visual content or the visual effects can be applied to a media data (e.g., a live image stream). The virtual content may be stored in the database(s)120.

FIG. 3is a diagram illustrating a wearable device in the example form of glasses331for use in an real-time communication session, according to some example embodiments. The glasses331can include a frame332made from any suitable material such as plastic or metal, including any suitable shape memory alloy. The frame332can have a front piece333that can include a first or left lens, display, or optical element holder336and a second or right lens, display, or optical element holder337connected by a bridge338. The front piece333additionally includes a left end portion341and a right end portion342. A first or left optical element344and a second or right optical element343can be provided within respective left and right optical element holders336,337. Each of the optical elements343,344can be a lens, a display (e.g., a transparent display), a display assembly, or a combination of the foregoing. In some embodiments, for example, the glasses331are provided with an integrated near-eye display mechanism that enables, for example, display to the user of preview images for visual media captured by cameras367of the glasses331. In some embodiments, integrated near-eye display mechanism allows for display of a media object such that the media object is overlaid on a real-world environment that is viewable through the optical elements343and344.

The frame332additionally includes a left arm or temple piece346and a right arm or temple piece347coupled to the respective left and right end portions341,342of the front piece333by any suitable means, such as a hinge (not shown), so as to be coupled to the front piece333, or rigidly or fixably secured to the front piece333so as to be integral with the front piece333. Each of the temple pieces346and347can include a first portion351that is coupled to the respective end portion341or342of the front piece333and any suitable second portion352, such as a curved or arcuate piece, for coupling to the ear of the user. In one embodiment, the front piece333can be formed from a single piece of material, so as to have a unitary or integral construction. In one embodiment, the entire frame332can be formed from a single piece of material so as to have a unitary or integral construction.

The glasses331can include a device, such as a computer361, which can be of any suitable type so as to be carried by the frame332and, in one embodiment, of a suitable size and shape so as to be at least partially disposed in one of the temple pieces346and347. In one embodiment, the computer361has a size and shape similar to the size and shape of one of the temple pieces346,347and is thus disposed almost entirely if not entirely within the structure and confines of such temple pieces346and347. In one embodiment, the computer361can be disposed in both of the temple pieces346,347. The computer361can include one or more processors with memory, wireless communication circuitry, and a power source. The computer361comprises low-power circuitry, high-speed circuitry, and a display processor. Various other embodiments may include these elements in different configurations or integrated together in different ways.

The computer361additionally includes a battery362or other suitable portable power supply. In one embodiment, the battery362is disposed in one of the temple pieces346or347. In the glasses331shown inFIG. 3, the battery362is shown as being disposed in the left temple piece346and electrically coupled using a connection374to the remainder of the computer361disposed in the right temple piece347. One or more I/O devices can include a connector or port (not shown) suitable for charging a battery362accessible from the outside of the frame332, a wireless receiver, transmitter, or transceiver (not shown), or a combination of such devices. Given the limited size of the glasses331and the computer361, resource-intensive operations such as video streaming can quickly drain the battery362and can be a strain on the one or more processors of the computer361that can lead to overheating.

The glasses331include digital cameras367. Although two cameras367are depicted, other embodiments contemplate the use of a single or additional (i.e., more than two) cameras. For ease of description, various features relating to the cameras367will further be described with reference to only a single camera367, but it will be appreciated that these features can apply, in suitable embodiments, to both cameras367.

Consistent with some embodiments, the glasses331are an example instance of the client device102and may be worn by the user103-1. Further, in these embodiments, the user103-2can view a live camera feed generated by the camera367and interact with the user103-2by causing virtual content to be added to a real-world environment that is visible to the user103-1via the glasses331. That is, one or more media objects corresponding to virtual content selected by the user103-2can be displayed by the integrated near-eye display mechanism that enables such that the media object is overlaid on a real-world environment that is viewable through the optical elements343and344.

In various embodiments, the glasses331may include any number of input sensors or peripheral devices in addition to the cameras367. The front piece333is provided with an outward-facing, forward-facing, front, or outer surface366that faces forward or away from the user when the glasses331are mounted on the face of the user, and an opposite inward-facing, rearward-facing, rear, or inner surface369that faces the face of the user (e.g., user103-1) when the glasses331are mounted on the face of the user. Such sensors can include inward-facing video sensors or digital imaging modules such as cameras that can be mounted on or provided within the inner surface369of the front piece333or elsewhere on the frame332so as to be facing the user, and outward-facing video sensors or digital imaging modules such as the cameras367that can be mounted on or provided with the outer surface366of the front piece333or elsewhere on the frame332so as to be facing away from the user. Such sensors, peripheral devices, or peripherals can additionally include biometric sensors, location sensors, accelerometers, or any other such sensors.

The glasses331further include an example embodiment of a camera control mechanism or user input mechanism comprising a camera control button mounted on the frame332for haptic or manual engagement by the user. The camera control button provides a bi-modal or single-action mechanism in that it is disposable by the user between only two conditions, namely an engaged condition and a disengaged condition. In this example embodiment, the camera control button is a pushbutton that is by default in the disengaged condition, being depressible by the user to dispose it to the engaged condition. Upon release of the depressed camera control button, it automatically returns to the disengaged condition.

In other embodiments, the single-action input mechanism can instead be provided by, for example, a touch-sensitive button comprising a capacitive sensor mounted on the frame332adjacent to its surface for detecting the presence of a user's finger to dispose the touch-sensitive button to the engaged condition when the user touches a finger to the corresponding spot on the outer surface of the frame332. It will be appreciated that the above-described camera control button and capacitive touch button are but two examples of a haptic input mechanism for single-action control of the camera367and that other embodiments may employ different single-action haptic control arrangements.

FIG. 4is a block diagram illustrating aspects of the wearable device in the example form of the glasses331, according to some example embodiments. The computer361of the glasses331includes a central processor421in communication with an onboard memory426. The central processor421may be a CPU and/or a graphics processing unit (GPU). The memory426in this example embodiment comprises a combination of flash memory and random-access memory.

The glasses331further include a camera controller414in communication with the central processor421and the camera367. The camera controller414comprises circuitry configured to control recording of either photographic content or video content based upon processing of control signals received from the single-action input mechanism that includes the camera control button, and to provide for automatic adjustment of one or more image-capture parameters pertaining to capturing of image data by the camera367and on-board processing of the image data prior to persistent storage thereof and/or to presentation thereof to the user for viewing or previewing.

In some embodiments, the camera controller414comprises permanently configured circuitry, such as firmware or an application-specific integrated circuit (ASIC) configured to perform the various functions described herein. In other embodiments, the camera controller414may comprise a dynamically reconfigurable processor executing instructions that temporarily configure the processor to execute the various functions described herein.

The camera controller414interacts with the memory426to store, organize, and present image content in the form of photo content and video content. To this end, the memory426in this example embodiment comprises a photo content memory428and a video content memory442. The camera controller414is thus, in cooperation with the central processor421, configured to receive from the camera367image data representative of digital images produced by the camera367in accordance with some of the image-capture parameters, to process the image data in accordance with some of the image-capture parameters, and to store the processed image data in an appropriate one of the photo content memory428and the video content memory442.

The camera controller414is further configured to cooperate with a display controller449to cause display on a display mechanism incorporated in the glasses331of selected photos and videos in the memory426and thus to provide previews of captured photos and videos. In some embodiments, the camera controller414will manage processing of images captured using automatic bracketing parameters for inclusion in a video file.

A single-action input mechanism435is communicatively coupled to the central processor421and the camera controller414to communicate signals representative of a current state of the camera control button and thereby to communicate to the camera controller414whether or not the camera control button is currently being pressed. The camera controller414further communicates with the central processor421regarding the input signals received from the single-action input mechanism435. In one embodiment, the camera controller414is configured to process input signals received via the single-action input mechanism435to determine whether a particular user engagement with the camera control button is to result in a recording of video content or photographic content and/or to dynamically adjust one or more image-capture parameters based on processing of the input signals. For example, pressing of the camera control button for longer than a predefined threshold duration causes the camera controller414automatically to apply relatively less rigorous video processing to captured video content prior to persistent storage and display thereof. Conversely, pressing of the camera control button for shorter than the threshold duration in such an embodiment causes the camera controller414automatically to apply relatively more rigorous photo stabilization processing to image data representative of one or more still images.

The glasses331may be a stand-alone client device that is capable of independent operation or may be a companion device that works with a primary device to offload intensive processing and/or exchange data over the network106with the communication server system108. The glasses331may further include various components common to mobile electronic devices such as smart glasses or smart phones (for example, including a display controller for controlling display of visual media (including photographic and video content captured by the camera367) on a display mechanism incorporated in the device). Note that the schematic diagram ofFIG. 4is not an exhaustive representation of all components forming part of the glasses331.

FIG. 5is an interaction diagrams illustrating example interactions between a first device (client device102-1), a second device (client device102-2), and a server (application server112) of the communication system in performing a method600for facilitating a reward-based real-time communication session between a first user associated with the first device and a second user associated with the second device, according to example embodiments.

As shown inFIG. 5, the method500begins at operation502where the client device102-1generates a request for a real-time communication session and transmits the request to the application server112. The request is generated based on input received from a first user. The input can be received from a request submission interface presented by the client device102-1. For example, the application server112can provide instructions to the client device102-1to display a request submission interface, and the client device102-1, in turn, displays the request submission interface, and receives input via the request submission interface. The input defines one or more parameters for a real-time communication session with the user103-1. The one or more parameters can include criteria for a second user that is to be included in the real-time communication session. For example, the request can specify a target location (e.g., a geographic location or feature, a landmark, or an event) at which the second user is to be located, an identifier of a second user, or another attribute of a second user that is to be included in the real-time communication session. The one or more parameters can further include: a session duration; a task to be performed by the second user during the communication session; and a reward amount (e.g., a number of points or a monetary value), rate (e.g., dollars or points per minute), or type (e.g., a currency type or other redeemable points) to be provided to the second user in return for participating in the real-time communication session or performing the task.

In response to receiving the request (at operation504), the application server112provides a notification of the request to the client device102-2(at operation506). The notification includes an invitation that allows the user103-2to join a real-time communication session with the user103-1and further notifies the user103-2of any parameters associated with the real-time communication session such as the target location, a task to be performed, and/or a reward to be provided to the user103-2for participating in the real-time communication session. The user103-2can be identified based on one or more criteria included in the request. The client device102-2can be one of multiple device for which the application server112provides the notification. That is, the application server112can identify multiple candidate users to fulfill the request, and provide the notification to a client device operation by each user. For example, the application server112can identify multiple users that are within a predefined distance of the target location and provide a notification to a device of each such user, and the user who responds first is enabled to fulfil the request. In some instances, the application server112only provides notifications of requests to users who have indicated that they are willing to accept requests.

Upon receiving input indicative of acceptance of the invitation by the103-2, the client device102-2provides an indication of the acceptance to the application sever112, at operation508. Based on receiving the indication of acceptance (at operation510), the application server112initiates the real-time communication session between the users103-1and103-2(at operation512). When a real-time communication session is established, the user102-1is able to view a live camera feed (e.g., comprising a real-time image data) generated by the device102-2of the user102-2while also interacting with the user102-2using verbal and augmented reality based communication modalities. Accordingly, in initiating the real-time communication session, the application server112triggers activation of a camera associated with the client device102-2and causes the client device102-2to transmit a live camera feed generated by the camera back to the application server112(operation514). The application server112causes the client device102-1to display the live camera feed provided by the client device102-2(at operation516) thereby allowing the user103-1to view the real-world environment at the location of the user103-1. The live camera feed may be displayed on the client device102-1as part of a user interface that includes a set of selectable virtual content items that can be applied to the real-world environment that is visible to the user103-2via the client device102-2. The application server112also enables a real-time audio communication link between the devices that allows the users103-1and103-2to verbally communicate in real-time.

At operation518, the application server112terminates the real-time communication session between the client device102-1and110-2. In terminating the real-time communication session, the application server112terminates the display of the live camera feed on the client device102-2and disables the audio communication link between the devices. The application server112can terminate the real-time communication session based on user input received from one of the two devices (e.g., input corresponding to a request to terminate the real-time communication link) or based on expiration of a session duration specified in the request.

At operation520, the application server112determines a reward associated with the participation of the user103-2in the real-time communication session. The reward may comprise an amount of value corresponding to currency or points, and can be determined based on any one or more of an amount of value specified in the request, a rate specified in the request, an award type specified by the request, a default or baseline amount of value associated with participating in real-time communication session, a duration of the real-time communication session, a task performed by the second user during the session (e.g., based on task type or complexity), or based on a distance between the user103-2and the target location at the time of receiving the invitation to join the session.

The application server112provides the reward to the user102-2, at operation522, and the client device102-2displays a notification of the award, at operation524. The application server112may provide the reward by updating a user account associated with the user103-2to indicate that the user103-2has been provided the reward. Depending on the reward type, the application server112may also update a user account associated with the user102-1to reflect a deduction of the amount of value corresponding to the reward.

FIGS. 6-9are flowcharts illustrating operations of the communication system in performing a method600for facilitating a reward-based real-time communication sessions between a first user and a second user, according to example embodiments. The method600may be embodied in computer-readable instructions for execution by one or more processors such that the operations of the method600may be performed in part or in whole by the functional components of the communication system100; accordingly, the method600is described below by way of example with reference thereto. However, it shall be appreciated that at least some of the operations of the method600may be deployed on various other hardware configurations than the communication system100.

At operation605, the application server112receives a request, from a first device (e.g., client device102-1) of a first user (e.g., user103-1) for a real-time communication session with a second user. In the context of a real-time communication session, the first user can establish a real-time communication link with the second user to view a real-world environment at the second user's location and interact with the second user using both verbal and augmented reality based communication modalities.

The one or more parameters can be specified by the first user via a request submission interface presented on the first device. The request submission interface comprises one or more elements for the parameters of the real-time communication session. Accordingly, the request submission interface may include a combination of input fields, toggles, and other user interface input elements that can be used to specify configuration parameter.

At operation610, the application server112provides a notification of the request to a second device (e.g., client device102-2). The notification includes an invitation for the second user to join the real-time communication session with the first user. The notification can include an interactive element that allows the second user to accept the invitation and join the real-time communication session. The notification further informs the second user of any parameters of the real-time communication session specified by the first user. For example, the notification can specify any one or more of: a specific location (e.g., address, landmark, intersection, etc.) to which the second user is to travel; a task the second user is to perform; a session duration; and a reward amount (e.g., a number of points or monetary value), rate (e.g., dollars or points per minute), or type (e.g., a currency type or other redeemable points) to be provided to the second user in return for participating in the real-time communication session or performing the task. The notification can provide additional information about the task including, for example, detailed descriptions for completing the task and an estimated time for completing the task. In addition, the notification can include information about the first user.

The notification is sent to the second device of the second user based the second user being identified as satisfying one or more criteria specified in the request. For example, the notification may be sent to the second device based on detecting the second device being within a predefined distance of the target location specified by the request. As another example, the application sever112can provide the notification to the second device based on the second user corresponding to an identifier specified by the response. In some examples, the notification is only sent to the second device in response to the second user indicating they are willing to accept requests.

The application server112may provide the notification, for example, as a push notification, a notification displayed within a GUI of an application (e.g., client application104) executing on the second device, a text message, or an email. Depending on the embodiment, the application server112may transmit the message to the second device or may transmit a set of instructions to the second device that cause the second device to display the message. As will be discussed in further detail below, the second device may be one of a set of devices to which the application server112provides the message.

At operation615, the application server112receives a response that includes an indication of acceptance of the invitation from the second device. Based on receiving the indication of acceptance, the application server112establishes the real-time communication session between the first user and the second user, at operation620. In establishing the real-time communication session, the application server112activates a camera coupled to the second device, causes the second device to transmit the live camera feed generated by the camera back to the application server112, and causes display of the live camera feed on a display of the first device. In some embodiments, the camera is an embedded camera of the second device. In some embodiments, the camera is an embedded camera of a companion device of the second device such as a wearable device (e.g., glasses331). In causing the live camera feed of the second user to be displayed by the first device, the application server112enables the first user to view a real-world environment at the location of the second user (e.g., a location specified in the request) that is visible within the field of view of the camera coupled to second device.

At operation625, the application server112terminates the real-time communication session. In some instances, the application server112terminates the real-time communication session based on user input received from one of the two devices (e.g., input corresponding to a request to terminate the real-time communication session). In some instances, the application server112may terminate the real-time communication session based on expiration of a session duration specified in the request.

At operation630, the application server112determines a reward associated with the second user's participation in the real-time communication session. As noted above, the reward may comprise a monetary value or redeemable points. The reward may be determined, for example, based on any one or more of an amount of value specified by the first user as part of the request (e.g., a monetary value), a rate specified in the request, an award type specified by the request, a default or baseline amount of value associated with participating in real-time communication session, a duration of the real-time communication session, a task performed by the second user during the session, or based on a distance between the second user and the target location at the time of receiving the invitation to join the session. Accordingly, consistent with some embodiments, the application server112can determine the reward by determining a location of the second user based on location data obtained from the second device, and determining a distance between the location of the second user and the target location.

At operation635, the application server112provides the reward to the second user based on the second user's participation in the real-time communication session. The application server112may provide the reward by updating a user account associated with the second user to indicate that the user has been provided the reward. For example, the application server112may maintain a user account for the second user that allows the second user to accumulate an amount of value (e.g., in actual currency or in points) and in providing the reward, the application server112may increase the amount of accumulated value by the amount of value corresponding to the reward. In some embodiments, the application server112may also update a user account associated with the first user to reflect a deduction of the amount of value corresponding to the reward from the accumulated value in the user account of the first user.

As shown inFIG. 7, the method600may, in some embodiments, include operations705,710,715, and720. Consistent with these embodiments, the operations705and710may be performed where the application server112establishes the real-time communication session between the first and second users. At operation705, the application server112causes display of the live camera feed generated by the first device on the second device. The display of the live camera feed can further include a presentation of information about either the first or second user, an estimate reward to be provided to the second user, an elapsed time or indicator of time remaining. At operation710, the application server112enables a real-time audio communication link between the first and second device. The audio communication link between the first and second device allow the first and second users to communicate verbally and discuss the task in real-time.

Consistent with some embodiments, the operations715and720may be performed as part of the operation625, where the application server112terminates the real-time communication session between the first and second user. At operation715, the application server112terminates the display of the live camera feed (generated by the second device) on the first device. Upon termination of the live camera feed, the first user is no longer able to view the real-world environment of the second user. An operation720, the application server112disables the audio communication link between the first and second device thereby eliminating the ability for the first and second user to communicate verbally in real-time. In some embodiments, the application server112may further cause display of an indicator on the first and/or second device that the real-time communication session has been terminated.

As shown inFIG. 8, the method600may, in some embodiments, include operations805and810. Consistent with these embodiments, the operations805may be performed prior to operation710where the application server112transmits the message to the second device associated with the second user.

At operation805, the application server112identifies a set of candidate users to satisfy the request. The application server112identifies the set of candidate users based on one or more criteria specified by the request. In an example, the request specifies a target location and the application server112identifies a set of users within a predefined distance of the target location. The predefined distance may be a default value or may be specified by the first user as part of the request. The application server112can identify the set of candidate users based profile data and/or data obtained from a set of devices associated with the set of users (e.g., GPS data obtained from a GPS component). Furthering the example from above, the application server112may identify a set of devices that are within the predefined distance of the target location based on location data received from the devices. The second user is included in the set of candidate users and the second device is included in the set of devices.

Consistent with these embodiments, the operation610can be performed as part of the operation810, where the application server112provides the notification to a set of devices associated with the identified set of candidate users. That is, at operation810, the application server112provides the notification to the set of devices and the set of devices included the second device associated with the second user.

As shown inFIG. 9, the method600may, in some embodiments, include operations905,910, and915. Consistent with these embodiments, the operations905,910, and915can be performed at the real-time communication session is active. That is, the operations905,910, and915can be performed subsequent to operation620and prior to operation625.

At operation905, the application server112causes display, on the first device, of a set of selectable virtual content items to apply to the real-world environment at a location of the second user that is depicted in the live camera feed provided by the second device. Each virtual content item comprises one or more media objects. Media objects may be two or three dimensional.

At operation910, the application server112receives, from the first device, user input indicative of a selection by the first user of virtual content item from the set of virtual content items to apply to the real-world environment depicted in the live camera feed.

At operation915, the application server112causes both the first and second device to present the one or more media objects overlaid on the real-world environment depicted in the live camera feed provided by the second device based on the selected virtual content item. While the one or more media objects are presented, either user can interact with and manipulate the objects in real-time. The application server112may maintain object definition data that defines the display of the virtual content item (i.e., the one or more media objects) and in causing display of the one or more media objects, the application server112may provide the first and second devices with the virtual content definition data along with a set of instructions that causes the first and second device to display the one or more media objects overlaid on the real-world environment in accordance with the virtual content definition data in real-time.

As an example of the forgoing, the first user can select an arrow and have the arrow be applied to the real-world environment depicted in the live camera of the second user to point out the target location or other area to the second user. Both the first and second users can interact with and manipulate the arrow in real-time as it displayed, for example, by moving a location of the arrow.

In some embodiments, the second device is a wearable device worn by the second user that includes optical elements that include a transparent display device. Consistent with these embodiments, the application server112causes the transparent display device to display the one or more media objects while allowing the second user to continue to view the real-world environment through the device. In this manner, the one or more media objects are presented by the transparent display device overlaid on the real-world environment. However, it shall be appreciated that such information may in the alternative or in addition be presented by a primary device that is coupled to a wearable device. That is, depending on the embodiment, the wearable device of the second user can be a stand-alone device that is capable of independent operation or may be a companion device that works with a primary device to offload intensive processing.

The instructions provided to the first device cause the first device to display an augmented live camera feed that includes the one or more media objects of the virtual content item overlaid on the real-world environment. In some embodiments, the application server112may work in conjunction with a client application executing on the first device to augment image data from the live camera feed to include the one or more media objects overlaid on the real-world environment.

Software Architecture

FIG. 10is a block diagram illustrating an example software architecture1006, which may be used in conjunction with various hardware architectures herein described.FIG. 10is a non-limiting example of a software architecture, and it will be appreciated that many other architectures may be implemented to facilitate the functionality described herein. The software architecture1006may execute on hardware such as a machine1100ofFIG. 11that includes, among other things, processors1104, memory/storage1106, and I/O components1118. A representative hardware layer1052is illustrated and can represent, for example, the machine1100ofFIG. 11. The representative hardware layer1052includes a processing unit1054having associated executable instructions1004. The executable instructions1004represent the executable instructions of the software architecture1006, including implementation of the methods, components, and so forth described herein. The hardware layer1052also includes memory and/or storage modules1056, which also have the executable instructions1004. The hardware layer1052may also comprise other hardware1058.

In the example architecture ofFIG. 10, the software architecture1006may be conceptualized as a stack of layers where each layer provides particular functionality. For example, the software architecture1006may include layers such as an operating system1002, libraries1020, frameworks/middleware1018, applications1016, and a presentation layer1014. Operationally, the applications1016and/or other components within the layers may invoke API calls1008through the software stack and receive a response to the API calls1008as messages1012. The layers illustrated are representative in nature and not all software architectures have all layers. For example, some mobile or special-purpose operating systems may not provide a frameworks/middleware1018, while others may provide such a layer. Other software architectures may include additional or different layers.

The operating system1002may manage hardware resources and provide common services. The operating system1002may include, for example, a kernel1022, services1024, and drivers1026. The kernel1022may act as an abstraction layer between the hardware and the other software layers. For example, the kernel1022may be responsible for memory management, processor management (e.g., scheduling), component management, networking, security settings, and so on. The services1024may provide other common services for the other software layers. The drivers1026are responsible for controlling or interfacing with the underlying hardware. For instance, the drivers1026include display drivers, camera drivers, Bluetooth® drivers, flash memory drivers, serial communication drivers (e.g., Universal Serial Bus (USB) drivers), Wi-Fi® drivers, audio drivers, power management drivers, and so forth depending on the hardware configuration.

The libraries1020provide a common infrastructure that is used by the applications1016and/or other components and/or layers. The libraries1020provide functionality that allows other software components to perform tasks in an easier fashion than by interfacing directly with the underlying operating system1002functionality (e.g., kernel1022, services1024, and/or drivers1026). The libraries1020may include system libraries1044(e.g., C standard library) that may provide functions such as memory allocation functions, string manipulation functions, mathematical functions, and the like. In addition, the libraries1020may include API libraries1046such as media libraries (e.g., libraries to support presentation and manipulation of various media formats such as MPEG4, H.294, MP3, AAC, AMR, JPG, and PNG), graphics libraries (e.g., an OpenGL framework that may be used to render 2D and 3D graphic content on a display), database libraries (e.g., SQLite that may provide various relational database functions), web libraries (e.g., WebKit that may provide web browsing functionality), and the like. The libraries1020may also include a wide variety of other libraries1048to provide many other APIs to the applications1016and other software components/modules.

The frameworks/middleware1018provide a higher-level common infrastructure that may be used by the applications1016and/or other software components/modules. For example, the frameworks/middleware1018may provide various GUI functions, high-level resource management, high-level location services, and so forth. The frameworks/middleware1018may provide a broad spectrum of other APIs that may be utilized by the applications1016and/or other software components/modules, some of which may be specific to a particular operating system1002or platform.

The applications1016include built-in applications1038and/or third-party applications1040. Examples of representative built-in applications1038may include, but are not limited to, a contacts application, a browser application, a book reader application, a location application, a media application, a messaging application, and/or a game application. The third-party applications1040may include an application developed using the ANDROID™ or IOS™ software development kit (SDK) by an entity other than the vendor of the particular platform and may be mobile software running on a mobile operating system such as IOS™, ANDROID™, WINDOWS® Phone, or other mobile operating systems. The third-party applications1040may invoke the API calls1008provided by the mobile operating system (such as the operating system1002) to facilitate functionality described herein.

The applications1016may use built-in operating system functions (e.g., kernel1022, services1024, and/or drivers1026), libraries1020, and frameworks/middleware1018to create user interfaces to interact with users of the system. Alternatively, or additionally, in some systems interactions with a user may occur through a presentation layer, such as the presentation layer1014. In these systems, the application/component “logic” can be separated from the aspects of the application/component that interact with a user.

FIG. 11is a block diagram illustrating components of a machine1100, according to some example embodiments, able to read instructions from a machine-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically,FIG. 11shows a diagrammatic representation of the machine1100in the example form of a computer system, within which instructions1110(e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine1100to perform any one or more of the methodologies discussed herein may be executed. As such, the instructions1110may be used to implement modules or components described herein. The instructions1110transform the general, non-programmed machine1100into a particular machine1100programmed to carry out the described and illustrated functions in the manner described. In alternative embodiments, the machine1100operates as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine1100may operate in the capacity of a server machine 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 machine1100may comprise, but not be limited to, a server computer, a client computer, a PC, a tablet computer, a laptop computer, a netbook, a set-top box (STB), a PDA, an entertainment media system, a cellular telephone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of executing the instructions1110, sequentially or otherwise, that specify actions to be taken by the machine1100. Further, while only a single machine1100is illustrated, the term “machine” shall also be taken to include a collection of machines that individually or jointly execute the instructions1110to perform any one or more of the methodologies discussed herein.

The machine1100may include processors1104, memory/storage1106, and I/O components1118, which may be configured to communicate with each other such as via a bus1102. In an example embodiment, the processors1104(e.g., a CPU, a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a (GPU, a digital signal processor (DSP), an ASIC, a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor1108and a processor1109that may execute the instructions1110. AlthoughFIG. 11shows multiple processors1104, the machine1100may 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.

The memory/storage1106may include a memory1112, such as a main memory, or other memory storage, and a storage unit1114, both accessible to the processors1104such as via the bus1102. The storage unit1114and memory1112store the instructions1110embodying any one or more of the methodologies or functions described herein. The instructions1110may also reside, completely or partially, within the memory1112, within the storage unit1114, within at least one of the processors1104(e.g., within the processor's cache memory), or any suitable combination thereof, during execution thereof by the machine1100. Accordingly, the memory1112, the storage unit1114, and the memory of the processors1104are examples of machine-readable media.

Communication may be implemented using a wide variety of technologies. The I/O components1118may include communication components1140operable to couple the machine1100to a network1132or devices1120via a coupling1124and a coupling1122, respectively. For example, the communication components1140may include a network interface component or other suitable device to interface with the network1132. In further examples, the communication components1140may include wired communication components, wireless communication components, cellular communication components, Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components to provide communication via other modalities. The devices1120may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a USB).

Glossary

“CLIENT DEVICE” in this context refers to any machine that interfaces to a communications network to obtain resources from one or more server systems or other client devices. A client device may be, but is not limited to, a mobile phone, desktop computer, laptop, PDA, smart phone, tablet, ultra book, netbook, laptop, multi-processor system, microprocessor-based or programmable consumer electronics system, game console, set-top box, or any other communication device that a user may use to access a network.

“COMPONENT” in this context refers to a device, a physical entity, or logic having boundaries defined by function or subroutine calls, branch points, APIs, or other technologies that provide for the partitioning or modularization of particular processing or control functions. Components may be combined via their interfaces with other components to carry out a machine process. A component may be a packaged functional hardware unit designed for use with other components and a part of a program that usually performs a particular function of related functions. Components may constitute either software components (e.g., code embodied on a machine-readable medium) or hardware components.

A “HARDWARE COMPONENT” is a tangible unit capable of performing certain operations and may be configured or arranged in a certain physical manner. In various example embodiments, one or more computer systems (e.g., a standalone computer system, a client computer system, or a server computer system) or one or more hardware components of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware component that operates to perform certain operations as described herein. A hardware component may also be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware component may include dedicated circuitry or logic that is permanently configured to perform certain operations. A hardware component may be a special-purpose processor, such as a field-programmable gate array (FPGA) or an ASIC. A hardware component may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, a hardware component may include software executed by a general-purpose processor or other programmable processor.

Once configured by such software, hardware components become specific machines (or specific components of a machine) uniquely tailored to perform the configured functions and are no longer general-purpose processors. It will be appreciated that the decision to implement a hardware component mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations. Accordingly, the phrase “hardware component” (or “hardware-implemented component”) should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein.

Considering embodiments in which hardware components are temporarily configured (e.g., programmed), each of the hardware components need not be configured or instantiated at any one instance in time. For example, where a hardware component comprises a general-purpose processor configured by software to become a special-purpose processor, the general-purpose processor may be configured as respectively different special-purpose processors (e.g., comprising different hardware components) at different times. Software accordingly configures a particular processor or processors, for example, to constitute a particular hardware component at one instance of time and to constitute a different hardware component at a different instance of time.

The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented components that operate to perform one or more operations or functions described herein. As used herein, “processor-implemented component” refers to a hardware component implemented using one or more processors. Similarly, the methods described herein may be at least partially processor-implemented, with a particular processor or processors being an example of hardware. For example, at least some of the operations of a method may be performed by one or more processors or processor-implemented components.

Moreover, the one or more processors may also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), with these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., an application programming interface (API)). The performance of certain of the operations may be distributed among the processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processors or processor-implemented components may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example embodiments, the processors or processor-implemented components may be distributed across a number of geographic locations.

“PROCESSOR” in this context refers to any circuit or virtual circuit (a physical circuit emulated by logic executing on an actual processor) that manipulates data values according to control signals (e.g., “commands,” “op codes,” “machine code,” etc.) and which produces corresponding output signals that are applied to operate a machine. A processor may, for example, be a CPU, a RISC processor, a CISC processor, a GPU, a DSP, an ASIC, a RFIC, or any combination thereof. A processor may further be a multi-core processor having two or more independent processors (sometimes referred to as “cores”) that may execute instructions contemporaneously.