Co-location connection service

An example co-location connection service is described. The online co-location connection service is provided by a messaging system configured to selectively pair user profiles associated with respective client devices equipped with sensors that communicate with each other within the predetermined physical range. The messaging system monitors physical proximity of the client devices based on the sensor data obtained by the co-location connection service from the respective messaging clients executing at the respective client devices. In response to detecting that the client devices are within a predetermined physical proximity range the messaging system generates co-location experience by modifying the user interface in the respective messaging clients.

TECHNICAL FIELD

The present disclosure relates generally to facilitating interactions between devices hosting a messaging application.

BACKGROUND

The popularity of computer-implemented tools that permit users to access and interact with content and other users online continues to grow. For example, various computer-implemented tools exist that permit users to share content with other users through messaging applications or to play with other users online in multiplayer video games. Some of such computer-implemented tools, termed applications or apps, can be designed to run on a mobile device such as a phone, a tablet, or a watch.

DETAILED DESCRIPTION

A messaging server system, which hosts backend service for an associated messaging client, is configured to detect a co-location event indicating that two devices executing respective messaging clients are located within a certain physical proximity and respond to the co-location event by unlocking one or more user experiences previously designated as co-location experiences.

The technical problem of providing an online experience to a pair of users represented by respective user profiles in the messaging server system, in a way that the experience served to the respective associated messaging clients changes based on the users' physical proximity to each other, is addressed by an online co-location connection service configured to selectively pair user profiles associated with respective client devices equipped with sensors that communicate with each other within the predetermined physical proximity range, monitor physical proximity of the client devices based on the sensor data obtained by the co-location connection service from the respective messaging clients executing at the respective client devices and, in response to detecting that the client devices are within a predetermined physical proximity range, modifying the user interface in the respective messaging clients. A predetermined physical proximity range may be referred to as the co-location range. A user interface modified in response to detecting that the client devices are within a predetermined physical proximity range is an example of a co-location experience.

The operation of pairing two user profiles associated with respective client devices comprises designating these two user profiles, in a database that stores profiles representing users in the messaging server system, as co-location buddies. For example, each of the paired profiles may include an identification of the other profile and a flag indicating that the other profile is its co-location buddy. In some embodiments, the process of pairing includes receiving, from a user, a request to be paired with another user, obtaining a consent to be paired from the other user, and determining that the respective client devices of the two users are configured to communicate with each other directly over a near field communication technology, such as, e.g., a wireless personal area network technology, radio-frequency identification (RFID), etc.

The profiles representing the two users are then designated as co-location buddies in the database. Obtaining the consent to be paired from a user may entail communicating, from the messaging server system to the associated client device, a message or a user interface including a selectable option to grant or to deny consent to be paired. The messaging server system effectuates the pairing if the option to grant consent was selected and does not effectuate the pairing if the option to deny consent was selected of if not response was received. For the purposes of this description, the messaging clients associated with the paired user profiles are referred to as paired messaging clients, and the associated client devices are referred to as paired client devices. When the paired client devices come into the co-location range within each other, a co-location event is sent from one client device to the other, and, also, the co-location event is sent to the messaging server system.

As mentioned above, an example of a co-location experience is a user interface modified in response to detecting that the client devices are within a predetermined physical proximity range, also referred to as a co-location user interface (UI). The co-location UI may include an indication of co-location of the devices, as well as a visual control actionable to activate a feature that is not otherwise made available to the users, such as, e.g., an HTML5-based app or a game. The co-location UI may, in some embodiments, include animation configured to playback overlaid over a screen of the messaging client. Such animation may be an animated image with a transparent background, e.g., of a couple engaged in an activity that in non-virtual realm is only possible when two people are in close proximity, such as hugging or dancing. Another example of such animation is a depiction of hearts or balloons floating through the screen of the messaging client. The co-location UI may show respective custom avatars representing the paired user profiles, where the avatars are modified in a manner indicating that the other person is nearby. When the messaging server system detects that paired devices are no longer within a predetermined physical proximity range, the co-location experience is made unavailable to the users of the paired messaging clients.

While some less resource-intensive co-location experiences (sharing a simple animation) may be provided by the paired messaging clients to their users directly, without a roundtrip to the messaging server system, other co-location experiences (a more complex animation or a two player game) may include interaction with the messaging server system. Furthermore, while a co-location connection service is described in the context of a messaging system, the co-location methodology described herein may be utilized beneficially in any scenario where users interact via their client devices. For example, when users are engaged in an interactive game via their client devices, co-location methodology may be used to unlock additional power-ups in response to detecting co-location of the client devices. An online co-location connection service may be provided in an online messaging system comprising a messaging client and an associated backend service, which is described with reference toFIG. 1below.

Networked Computing Environment

FIG. 1is a block diagram showing an example messaging system100for exchanging data (e.g., messages and associated content) over a network. The messaging system100includes multiple instances of a client device102, each of which hosts a number of applications, including a messaging client104. Each messaging client104is communicatively coupled to other instances of the messaging client104and a messaging server system108via a network106(e.g., the Internet).

A messaging client104is able to communicate and exchange data with another messaging client104and with the messaging server system108via the network106. The data exchanged between messaging client104, and between a messaging client104and the messaging server system108, includes functions (e.g., commands to invoke functions) as well as payload data (e.g., text, audio, video or other multimedia data). A client device hosting a messaging client104may be equipped with sensors permitting the messaging client104to communicate and exchange data (e.g., a Bluetooth UUID) with another messaging client104over a near field communication technology, such as, e.g., Bluetooth Low Energy technology.

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

Turning now specifically to the messaging server system108, an Application Program Interface (API) server110is coupled to, and provides a programmatic interface to, application servers112. The application servers112are communicatively coupled to a database server118, which facilitates access to a database120. A web server124is coupled to the application servers112and provides web-based interfaces to the application servers112. To this end, the web server124processes incoming network requests over the Hypertext Transfer Protocol (HTTP) and several other related protocols. The database120stores data associated with messages processed by the application servers112, such as, e.g., profile data about a particular entity. Where the entity is an individual, the profile data includes, for example, a user name, notification and privacy settings, as well as records related to changes made by the user to their profile data. Where a first user profile and a second user profile have been designated as co-location buddies for the purpose of accessing the co-location connection service, the first user profile includes a unique identification of the user's client device and an identification of the second user profile. The second user profile, in turn, includes a unique identification of their client device and an identification of the first user profile. An example of profile data that represents a profile paired with another user profile in the messaging system, where the paired profiles represent users of the co-location connection service is shown inFIG. 7, which is described further below.

The Application Program Interface (API) server110receives and transmits message data (e.g., commands and message payloads) between the client device102and the application servers112. Specifically, the Application Program Interface (API) server110provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client104in order to invoke functionality of the application servers112. The Application Program Interface (API) server110exposes various functions supported by the application servers112, including account registration, login functionality, the sending of messages, via the application servers112, from a particular messaging client104to another messaging client104, the sending of media files (e.g., images or video) from a messaging client104to a messaging server114, and for possible access by another messaging client104, opening an application event (e.g., relating to the messaging client104), as well as various functions supported by developer tools provided by the messaging server system108for use by third party computer systems.

The application servers112host a number of server applications and subsystems, including for example a messaging server114, an image processing server116, and a social network server122. The messaging server114implements 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 messaging client104. The image processing server116that is dedicated to performing various image processing operations, typically with respect to images or video within the payload of a message sent from or received at the messaging server114. The social network server122supports various social networking functions and services and makes these functions and services available to the messaging server114.

Also shown inFIG. 1is a co-location server117. The co-location server117provides an online co-location connection service configured to selectively pair user profiles associated with respective client devices equipped with sensors that communicate with each other within the predetermined physical range, monitor physical proximity of the client devices based on the sensor data obtained by the co-location connection service from the respective messaging clients executing at the respective client devices and, in response to detecting that the client devices are within a predetermined physical proximity range, generates co-location experience by modifying the user interface in the respective messaging clients. While, as shown inFIG. 1, an online co-location connection service is provided at the co-location server117, in some examples, an online co-location connection service may be provided at a messaging server, e.g., by the messaging server114.

The location of a co-location functionality may be either within the messaging client104or the messaging server system108or both. An example co-location system, which is supported on the client-side by the messaging client104and on the sever-side by the application servers112, is discussed below with reference toFIG. 6.

System Architecture

FIG. 6is a block diagram illustrating further details regarding the messaging system100, according to some examples. Specifically, the messaging system100is shown to comprise the messaging client104and the application servers112. The messaging system100embodies a number of subsystems, which are supported on the client-side by the messaging client104and on the sever-side by the application servers112. These subsystems include, for example, an augmentation system606, a map system608, a game system610, as well as a co-location connection system612.

The co-location connection system612is configured to selectively pair user profiles associated with respective client devices equipped with sensors that communicate with each other within the predetermined physical proximity range. The co-location connection system612monitors physical proximity of the client devices based on the sensor data obtained by the co-location connection service from the respective messaging clients executing at the respective client devices. In response to detecting that the client devices are within a predetermined co-location range, the co-location connection system612serves a co-location experience to the respective associated messaging clients executing at the respective client devices by modifying the user interface in the respective messaging clients. An example of a co-location experience is an augmented reality experience provided by the augmentation system606.

The augmentation system606provides various functions that enable a user to augment (e.g., annotate or otherwise modify or edit) media content associated with a message. For example, the augmentation system606provides functions related to the generation and publishing of media overlays for messages processed by the messaging system100. The augmentation system606operatively supplies a media overlay or augmentation (e.g., an image filter) to the messaging client104based on a geolocation of the client device102. In another example, the augmentation system606operatively supplies a media overlay to the messaging client104based on other information, such as in response to the co-location connection system612detecting that the client devices are within a predetermined co-location range. A media overlay may include audio and visual content and visual effects. Examples of audio and visual content include pictures, texts, logos, animations, and sound effects. An example of a visual effect includes color overlaying. The audio and visual content or the visual effects can be applied to a media content item (e.g., a photo) at the client device102. For example, the media overlay may include text or image that can be overlaid on top of a photograph taken by the client device102. In another example, the media overlay includes an identification of a location overlay (e.g., Venice beach), a name of a live event, or a name of a merchant overlay (e.g., Beach Coffee House). In another example, the co-location connection system612and/or the augmentation system606cooperate with the map system608, provides various geographic location functions, and supports the presentation of map-based media content and messages by the messaging client104.

Other examples of co-location experiences are experiences provided by the game system610, where the co-location connection system612generates a co-location UI that includes a visual control actionable to activate a game. The game system610provides various gaming functions within the context of the messaging client104. The messaging client104provides a game interface that includes a list of available games that can be launched by a user within the context of the messaging client104, and played with other users of the messaging system100. The messaging system100further enables a particular user to invite other users to participate in the play of a specific game, by issuing invitations to such other users from the messaging client104. The messaging client104also supports both the voice and text messaging (e.g., chats) within the context of gameplay, provides a leaderboard for the games, and, also, supports the provision of in-game rewards (e.g., coins and items).

In some examples, a co-location experience provided by the co-location connection system612includes providing access to certain external resources, e.g., applications or applets that the respective messaging clients associated with the paired client devices may launch, e.g., by accessing an HTML5 file from a third-party servers. HTML5 is used as an example technology for programming games, but applications and resources programmed based on other technologies can also be used.

As mentioned above, where two user profiles have been paired for the purpose of accessing the co-location connection service, the database that stores profile data (e.g., database120ofFIG. 1) reflects such pairing. Example data architecture is illustrated inFIG. 7, which is discussed below.

Data Architecture

FIG. 7is a schematic diagram illustrating data structures700, which may be stored in the database120of the messaging server system108, according to certain examples. While the content of the database120is shown to comprise a number of tables, it will be appreciated that the data could be stored in other types of data structures (e.g., as an object-oriented database).

The database120includes message data stored within a message table702. This message data includes, for any particular one message, at least message sender data, message recipient (or receiver) data, and a payload. Further details regarding information that may be included in a message, and included within the message data stored in the message table702is described below with reference toFIG. 4.

An entity table704stores entity data, and is linked (e.g., referentially) to an entity graph706and profile data708. Entities for which records are maintained within the entity table704may include individuals, corporate entities, organizations, objects, places, events, and so forth. Regardless of entity type, any entity regarding which the messaging server system108stores data may be a recognized entity. Each entity is provided with a unique identifier, as well as an entity type identifier (not shown).

The entity graph706stores information regarding relationships and associations between entities. Such relationships may be social, professional (e.g., work at a common corporation or organization) interested-based or activity-based, merely for example. The entity graph706may also store information reflecting the pairing of user profiles representing users of the co-location connection system612ofFIG. 6.

The profile data708stores multiple types of profile data about a particular entity. The profile data708may be selectively used and presented to other users of the messaging system100, based on privacy settings specified by a particular entity. Where the entity is an individual, the profile data708includes, for example, a user name, telephone number, address, settings (e.g., notification and privacy settings), as well as a user-selected avatar representation (or collection of such avatar representations). A particular user may then selectively include one or more of these avatar representations within the content of messages communicated via the messaging system100, and on map interfaces displayed by messaging clients104to other users. The collection of avatar representations may include “status avatars,” which present a graphical representation of a status or activity that the user may select to communicate at a particular time. The profile data708that represents a profile paired with another user profile, where the paired profiles represent users of the co-location connection service117, include, in addition to a user identification718, a user device identification720and a paired user identification722. In one example, given a user profile that includes a user identification, a user device identification and a paired user identification, the location data exchange component of the power optimization system206shown inFIG. 2obtains location data of a user device (represented by the user device identification), determines the paired profile based on the paired user identification, and communicates the obtained location data of the user device to the paired device represented by a user device identification stored in the paired profile.

The database120also stores augmentation data, such as overlays or filters, in an augmentation table710. The augmentation data is associated with and applied to videos (for which data is stored in a video table714) and images (for which data is stored in an image table716). As mentioned above, the video table714stores video data that, in one example, is associated with messages for which records are maintained within the message table702. Similarly, the image table716stores image data associated with messages for which message data is stored in the entity table704. The entity table704may associate various augmentations from the augmentation table710with various images and videos stored in the image table716and the video table714.

FIG. 2is a block diagram illustrating an example system200for providing co-location experience to users of the of the co-location connection system612ofFIG. 6. In some examples, the system200corresponds to the co-location connection system612shown inFIG. 6. The system200includes a pairing component210, a co-location detector220, and a co-location UI generator230. The pairing component210is configured to pair two user profiles. In some embodiments, only paired user profiles can access the co-location service provided by the co-location connection system612. The pairing of a first user profile associated with a first client device and a second user profile associated with a second client device is performed online. The pairing comprises determining that the first client device and the second client device include respective short range communication sensors configured to communicate with each other within the predetermined physical range. The pairing operation may be performed without requiring that the two client devices are, at the time of pairing, are within a communication range permitted by their respective short range communication sensors and without requiring a communication between the first client device and the second client device via a short-range wireless communication technology. The pairing comprises receiving, from the first client device, a pairing request to pair the first user profile with the second user profile; in response to the pairing request, obtaining a consent response from the second device, the consent associated with the second user profile; and subsequent to the obtaining of the consent response, pairing the first user profile and the second user profile.

The co-location detector220is configured to detect a co-location event indicating that a first client device executing a messaging client and a second client device executing the messaging client are located within a predetermined physical range. The detecting of the co-location event comprises receiving, from the first client device an indication of a connection established between the first client device and the second client device via a short-range wireless communication technology. The co-location detector220is further configured to detect a distancing event with respect to two client devices and, in response to the detecting of the distancing event, communicate, to the client devices, a visual indication of the distancing event. A distancing event indicates that the first client device and the second client device are located outside of the predetermined physical range. The distancing event comprises receiving, from the first client device, an indication that a previously established connection between the first client device and the second client device via a short-range wireless communication technology has been terminated.

The co-location UI generator230is configured to generate, in response to the co-location detector220detecting of the co-location event, a co-location user interface. The co-location user interface may include, e.g., an indication of co-location of the first client device and the second client device, a visual control actionable to activate an HTML5-based application, and/or animation configured to playback overlaid over a screen of the messaging client executing at the first client device.

Each of the various components of the system200may be provided at the client device102and/or at the messaging server system108ofFIG. 1. Further details regarding the operation of the system200are described below.

FIG. 3is a flowchart of a method300for providing co-location experience. The method300may be performed by processing logic that may comprise hardware (e.g., dedicated logic, programmable logic, microcode, etc.), software, or a combination of both. In one example embodiment, some or all processing logic resides at the client device102ofFIG. 1and/or at the messaging server system108ofFIG. 1. Although the described flowchart can show operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed. A process may correspond to a method, a procedure, an algorithm, etc. The operations of methods may be performed in whole or in part, may be performed in conjunction with some or all of the operations in other methods, and may be performed by any number of different systems, such as the systems described herein, or any portion thereof, such as a processor included in any of the systems.

At operation310, the co-location detector220of the co-location connection system612detects a co-location event indicating that a first client device executing a messaging client and a second client device executing the messaging client are located within a predetermined physical range. At operation320, the co-location UI generator230, in response to the detecting of the co-location event, generates a co-location user interface including an indication of co-location of the first client device and the second client device. The co-location user interface is communicated to the first client device and to the second client device at operation330.

FIG. 4is a diagrammatic representation400of an example co-location experience manifested on respective display devices of co-location buddies. As shown inFIG. 4, paired client devices410and420host respective messaging clients. Respective screens412and422of the messaging clients display respective indications414and424of the client devices410and420being located within the communication range of a signal430and thus identified by a co-location connection service442hosted at a messaging server440as co-located. The paired client devices410and420communicate with the messaging server440via a network, such as, e.g., the Internet. Respective screens412and422of the messaging clients also display respective animations416and426configured to playback (e.g., float upwards) overlaid over the respective screens412and422and respective visual controls418and428actionable to activate a further application, e.g., an HTML5-based app.

Machine Architecture

FIG. 5is a diagrammatic representation of the machine600within which instructions608(e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine500to perform any one or more of the methodologies discussed herein may be executed. For example, the instructions508may cause the machine500to execute any one or more of the methods described herein. The instructions508transform the general, non-programmed machine500into a particular machine500programmed to carry out the described and illustrated functions in the manner described. The machine500may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine500may 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 machine500may comprise, but not be 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 telephone, a smartphone, a mobile device, a wearable device (e.g., a smartwatch), 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 instructions508, sequentially or otherwise, that specify actions to be taken by the machine500. Further, while only a single machine500is illustrated, the term “machine” shall also be taken to include a collection of machines that individually or jointly execute the instructions508to perform any one or more of the methodologies discussed herein. The machine500, for example, may comprise the client device102or any one of a number of server devices forming part of the messaging server system108. In some examples, the machine500may also comprise both client and server systems, with certain operations of a particular method or algorithm being performed on the server-side and with certain operations of the particular method or algorithm being performed on the client-side.

The machine500may include processors502, memory504, and input/output I/O components538, which may be configured to communicate with each other via a bus540. In an example, the processors502(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 processor506and a processor510that execute the instructions508. The term “processor” is intended to include multi-core processors that may comprise two or more independent processors (sometimes referred to as “cores”) that may execute instructions contemporaneously. AlthoughFIG. 5shows multiple processors502, the machine500may 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 multiples cores, or any combination thereof.

The memory504includes a main memory512, a static memory514, and a storage unit516, both accessible to the processors502via the bus540. The main memory504, the static memory514, and storage unit516store the instructions508embodying any one or more of the methodologies or functions described herein. The instructions508may also reside, completely or partially, within the main memory512, within the static memory514, within machine-readable medium518within the storage unit515, within at least one of the processors502(e.g., within the Processor's cache memory), or any suitable combination thereof, during execution thereof by the machine500.

In further examples, the I/O components538may include biometric components528, motion components530, environmental components532, or position components534, among a wide array of other components. For example, the biometric components528include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye-tracking), measure biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram-based identification), and the like. The motion components530include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope).

With respect to cameras, the client device102may have a camera system comprising, for example, front cameras on a front surface of the client device102and rear cameras on a rear surface of the client device102. The front cameras may, for example, be used to capture still images and video of a user of the client device102(e.g., “selfies”), which may then be augmented with augmentation data (e.g., filters) described above. The rear cameras may, for example, be used to capture still images and videos in a more traditional camera mode, with these images similarly being augmented with augmentation data. In addition to front and rear cameras, the client device102may also include a 360° camera for capturing 360° photographs and videos.

Communication may be implemented using a wide variety of technologies. The I/O components538further include communication components536operable to couple the machine500to a network520or devices522via respective coupling or connections. For example, the communication components536may include a network interface Component or another suitable device to interface with the network520. In further examples, the communication components536may 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 devices522may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a USB).

The various memories (e.g., main memory512, static memory514, and memory of the processors502) and storage unit516may store one or more sets of instructions and data structures (e.g., software) embodying or used by any one or more of the methodologies or functions described herein. These instructions (e.g., the instructions508), when executed by processors502, cause various operations to implement the disclosed examples.

The instructions508may be transmitted or received over the network520, using a transmission medium, via a network interface device (e.g., a network interface component included in the communication components536) and using any one of several well-known transfer protocols (e.g., hypertext transfer protocol (HTTP)). Similarly, the instructions608may be transmitted or received using a transmission medium via a coupling (e.g., a peer-to-peer coupling) to the devices522.

Glossary