CN116584083A - Co-location connectivity service - Google Patents

Abstract

Example co-location connectivity services are 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 a predetermined physical range. The messaging system monitors the physical proximity of the client devices based on sensor data obtained by the co-location connectivity service from respective messaging clients executing at respective client devices. In response to detecting that a client device is within a predetermined physical proximity, the messaging system generates a co-location experience by modifying a user interface in the corresponding messaging client.

Description

Co-location Connectivity Service

Cross References to Related Applications

This application claims the benefit of priority to U.S. Patent Application Serial No. 17/247,053, filed November 25, 2020, which is incorporated herein by reference in its entirety.

technical field

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

Background technique

Computer-implemented tools that allow users to access content and interact with other users online continue to grow in popularity. For example, various computer-implemented tools exist that allow users to share content with other users through messaging applications, or to play multiplayer video games online with other users. Some of such computer-implemented tools, known as applications or apps, may be designed to run on mobile devices such as phones, tablets, or watches.

Description of drawings

In the drawings (which are not necessarily drawn to scale), like reference numerals may depict similar parts in different views. To easily identify a discussion of any particular element or act, the highest digit or digits in a reference number refer to the figure number in which that element is first introduced. Some embodiments are shown by way of example and not limitation in the figures of the accompanying drawings, in which:

1 is a diagrammatic representation of a networked environment in which co-location connectivity services may be deployed, according to some examples.

2 is a block diagram of the architecture of a system for providing co-location experiences, according to some examples.

3 is a flowchart of a method for providing a co-location experience, according to some examples.

4 is a diagrammatic representation of an example co-location experience displayed on a corresponding display device of a co-location partner.

5 is a diagrammatic representation of a machine in the form of a computer system within which a set of instructions may be executed to cause the machine to perform any one or more of the methods discussed herein, according to some examples.

6 is a diagrammatic representation of a messaging system with both client-side and server-side functionality, according to some examples.

7 is a diagrammatic representation of data structures as maintained in a database, according to some examples.

Detailed ways

A messaging server system hosting a backend service for an associated messaging client is configured to: detect a co-location event indicating that two devices executing the respective messaging client are within a certain physical proximity, and unlock a previously designated The co-location event is responded to for one or more user experiences of the co-location experience.

Techniques for providing an online experience to users of a pair of users represented by respective user profiles in a messaging server system in such a way that the experience of serving the users varies based on the physical proximity of the users to each other The problem is addressed by an online co-location connectivity service configured to selectively pair user profiles associated with respective client devices equipped with sensors that communicate with each other within a predetermined physical proximity ; monitoring the physical proximity of the client device based on sensor data obtained by the co-location connectivity service from a respective messaging client executing at the respective client device; and in response to detecting that the client device is within a predetermined physical proximity range to modify the user interface in the corresponding messaging client. The predetermined range of physical proximity may be referred to as a co-location range. A user interface that is modified in response to detecting that a client device is within a predetermined physical proximity is an example of a co-location experience.

Pairing two user profiles associated with respective client devices includes designating the two user profiles as co-location partners in a database storing profiles representing users in the messaging server system. For example, paired profiles may each include an identification of the other profile and a flag indicating that the other profile is its co-location partner. In some implementations, the pairing process includes receiving a request from a user to pair 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 paired. configured to communicate with each other directly via near field communication technology (eg, wireless personal area network technology, radio frequency identification (RFID), etc.).

The profiles representing these two users are then designated as co-location partners in the database. Obtaining pairing permission from the user may require the transmission of a message or user interface from the messaging server system to the associated client device that includes selectable options to grant or deny pairing permission. If the option to grant permission is selected, the messaging server system enables pairing, if the option to deny permission is selected or if no response is received, the messaging server system does not effect pairing. For purposes of this description, a messaging client associated with a paired user profile is referred to as a paired messaging client, and an associated client device is referred to as a paired client device. When paired client devices come into co-location range of each other, a co-location event is sent from one client device to the other client device, and the co-location event is also sent to the messaging server system.

As noted above, an example of a co-location experience is a user interface that is modified in response to detecting that a client device is within a predetermined physical proximity, also referred to as a co-location user interface (UI). The co-location UI may include an indication of the device's co-location, as well as visual controls operable to activate features not otherwise available to the user, such as HTML5-based applications or games. In some implementations, the co-location UI may include an animation configured to play overlaid on the screen of the messaging client. Such an animation may be an animated image with a transparent background, for example, of a couple engaging in an activity that is only possible in a non-virtual realm when two people are in close proximity, such as hugging or dancing. Another example of such an animation is depicting a heart or balloon floating on the screen of the messaging client. The co-location UI may show corresponding customized avatars representing the paired user profiles, where the avatars are modified in a way that indicates that others are nearby. When the messaging server system detects that the paired device is no longer within a predetermined physical proximity, the co-location experience is disabled for the user of the paired messaging client.

While some less resource-intensive co-location experiences (shared simple animations) can be served directly to their users by paired messaging clients without a round trip to the messaging server system, others (more complex animations) or two-player game) may include interaction with a messaging server system. Furthermore, although the co-location connectivity service is described in the context of a messaging system, the co-location methods described herein can be advantageously used in any scenario where users interact via their client devices. For example, when a user participates in an interactive game via their client device, the co-location method may be used to unlock additional power in response to detecting the co-location of the client device. An online co-location connection service may be provided in an online messaging system comprising a messaging client and associated backend services, which is described below with reference to FIG. 1 .

networked computing environment

1 is a block diagram illustrating an example messaging system 100 for exchanging data (eg, messages and associated content) over a network. Messaging system 100 includes multiple instances of client devices 102 each hosting multiple applications including messaging clients 104 . Each messaging client 104 is communicatively coupled to other instances of the messaging client 104 and to the messaging server system 108 via a network 106 (eg, the Internet).

A messaging client 104 is capable of communicating and exchanging data via a network 106 with another messaging client 104 and with a messaging server system 108 . Data exchanged between messaging clients 104 and between messaging clients 104 and messaging server system 108 includes functions (e.g., commands to activate functions) and payload data (e.g., text, audio, video, or other multimedia data). A client device hosting a messaging client 104 may be equipped with a sensor that allows a messaging client 104 to communicate and exchange data (eg, Bluetooth UUIDs) with another messaging client 104 via near field communication technology, such as Bluetooth low energy technology.

Messaging server system 108 provides server-side functionality to particular messaging clients 104 via network 106 . Although certain functions of messaging system 100 are described herein as being performed by messaging client 104 or by messaging server system 108, the location of certain functions within messaging client 104 or within messaging server system 108 Can be a design choice. For example, it may be technically preferable to initially deploy certain technologies and functionality within the messaging server system 108, but later migrate the technology and functionality to the messaging client 104 where the client device 102 has sufficient processing power.

Messaging server system 108 supports various services and operations provided to messaging clients 104 . Such operations include sending data to the messaging client 104 , receiving data from the messaging client 104 , and processing data generated by the messaging client 104 . As examples, this data may include message content, client device information, geolocation information, media enhancements and overlays, message content persistence conditions, social networking information, and live event information. Data exchange within the messaging system 100 is activated and controlled through functionality available via a user interface (UI) of the messaging client 104 .

Turning now specifically to the messaging server system 108 , an application programming interface (API) server 110 is coupled to and provides a programming interface to the application server 112 . Application server 112 is communicatively coupled to database server 118 that facilitates access to database 120 . Web server 124 is coupled to application server 112 and provides a web-based interface to application server 112 . To this end, web server 124 handles incoming network requests via Hypertext Transfer Protocol (HTTP) and several other related protocols. Database 120 stores data associated with messages processed by application server 112 , such as profile data about a particular entity. Where the entity is an individual, the profile data includes, for example, the user's name, notification and privacy settings, and records pertaining to changes made by the user to their profile data. Where the first user profile and the second user profile are designated as co-location partners for the purpose of accessing the co-location connectivity service, the first user profile includes the unique identification of its client device and the second user profile file ID. The second user profile in turn includes the unique identification of its client device and the identification of the first user profile. An example of profile data representing a profile paired with another user profile in the messaging system, where the paired profile represents a user of a co-location connectivity service, is shown in Figure 7, as will be described further below.

Application programming interface (API) server 110 receives and sends message data (eg, commands and message payloads) between client device 102 and application server 112 . Specifically, an application program interface (API) server 110 provides a set of interfaces (eg, routines and protocols) that can be called or queried by messaging clients 104 to activate the functionality of the application server 112 . An application programming interface (API) server 110 exposes various functions supported by the application server 112, including account registration, login functionality, sending a message from a particular messaging client 104 to another messaging client 104 via the application server 112, sending messages from a message A messaging client 104 sends a media file (e.g., an image or video) to a messaging server 114 and for possible access by another messaging client 104, opens an application event (e.g., Various functions supported by developer tools provided by the transceiver server system 108 for use by third-party computer systems.

Application server 112 hosts a number of server applications and subsystems including, for example, messaging server 114 , image processing server 116 , and social networking server 122 . Messaging server 114 implements a number of message processing techniques and functions, particularly related to aggregation and other processing of content (eg, text and multimedia content) included in messages received from multiple instances of messaging client 104 . Image processing server 116 is dedicated to performing various image processing operations, typically on images or video within the payload of messages sent from or received at messaging server 114 . The social networking server 122 supports and makes available various social networking functions and services to the messaging server 114 .

A co-location server 117 is also shown in FIG. 1 . The co-location server 117 provides an online co-location connectivity service configured to: selectively pair user profiles associated with respective client devices equipped with sensors that communicate with each other within a predetermined physical range, monitoring the physical proximity of the client device based on sensor data obtained by the co-location connectivity service from a respective messaging client executing at the respective client device, and in response to detecting that the client device is within a predetermined physical proximity range, The co-location experience is generated by modifying the user interface in the corresponding messaging client. While the online co-location connection service is provided at the co-location server 117 as shown in FIG. 1 , in some examples the online co-location connection service may be provided at the messaging server, eg, by the messaging server 114 .

The location of the co-location functionality may be within the messaging client 104 or within the messaging server system 108 or both. An example co-location system supported on the client side by the messaging client 104 and on the server side by the application server 112 is discussed below with reference to FIG. 6 .

system structure

FIG. 6 is a block diagram showing additional details about messaging system 100 according to some examples. In particular, messaging system 100 is shown including messaging client 104 and application server 112 . The messaging system 100 includes a number of subsystems supported on the client side by the messaging client 104 and on the server side by the application server 112 . These subsystems include, for example, augmentation system 606 , map system 608 , gaming system 610 , and co-location connection system 612 .

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

Enhancement system 606 provides various functions that enable a user to enhance (eg, annotate or otherwise modify or edit) media content associated with a message. For example, enhancement system 606 provides functionality related to generating and publishing media overlays for messages processed by messaging system 100 . The enhancement system 606 is operable to supply media overlays or enhancements (eg, image filters) to the messaging client 104 based on the geolocation of the client device 102 . In another example, the enhancement system 606 is operable to provide the media overlay to the messaging client 104 based on other information, such as in response to the co-location connection system 612 detecting that the client device is within a predetermined co-location range. Media overlays can include audio and visual content as well as visual effects. Examples of audio and visual content include pictures, text, logos, animations and sound effects. Examples of visual effects include color overlays. Audio and visual content or visual effects may be applied to media content items (eg, photos) at client device 102 . For example, media overlays may include text or images that can be superimposed on photos taken by client device 102 . In another example, the media overlay includes a location identification overlay (eg, Venice Beach), a name of a live event, or a business name overlay (eg, a beach cafe). In another example, the co-location connection system 612 and/or the augmentation system 606 cooperate with the map system 608 to provide various geographic location functions and support the presentation of map-based media content and messages by the messaging client 104 .

Another example of a co-location experience is an experience provided by a gaming system 610 in which a co-location connection system 612 generates a co-location UI including visual controls operable to activate a game. Gaming system 610 provides various gaming functions within the context of messaging client 104 . The messaging client 104 provides a gaming interface that includes a list of available games that can be launched by the user within the context of the messaging client 104 and played with other users of the messaging system 100 . The messaging system 100 also enables a particular user to invite other users to participate in playing a particular game by sending an invitation from the messaging client 104 to such other users. The messaging client 104 also supports both voice and text messaging (eg, chat) within the context of the game, provides leaderboards for the game, and also supports providing in-game rewards (eg, coins and items).

In some examples, the co-location experience provided by the co-location connectivity system 612 includes providing access to certain external resources, such as a corresponding messaging client associated with a paired client device, which can be accessed, for example, from the first An application or applet launched by a third-party server accessing an HTML5 file. HTML 5 is used as an example technology for programming games, but applications and resources programmed on other technologies can also be used.

As noted above, where two user profiles are paired for the purpose of accessing co-location connectivity services, the database storing the profile data (eg, database 120 of FIG. 1 ) reflects such pairing. An example data architecture is shown in Figure 7, which is discussed below.

data structure

7 is a schematic diagram illustrating a data structure 700 that may be stored in the database 120 of the messaging server system 108, according to some examples. While the contents of database 120 are shown as including multiple tables, it will be appreciated that data may be stored in other types of data structures (eg, as an object-oriented database).

Database 120 includes message data stored in message table 702 . For any particular message, the message data includes at least message sender data, message recipient (or receiver) data, and payload. Additional details regarding information that may be included in a message and included within message data stored in message table 702 are described below with reference to FIG. 4 .

Entity table 704 stores entity data and is (eg, referentially) linked to entity graph 706 and profile data 708 . Entities whose records are maintained in entity table 704 may include individuals, corporate entities, organizations, objects, places, events, and the like. Regardless of the entity type, any entity about which messaging server system 108 stores data may be an identified entity. Each entity is provided with a unique identifier as well as an entity type identifier (not shown).

The entity graph 706 stores information about relationships and associations between entities. By way of example only, such relationships may be interest-based or activity-based social relationships, professional relationships (eg, working in a common company or organization). The entity graph 706 may also store information reflecting pairings representing user profiles of users of the co-location connection system 612 of FIG. 6 .

Profile data 708 stores various types of profile data about a particular entity. Profile data 708 may be selectively used and presented to other users of messaging system 100 based on privacy settings specified by a particular entity. Where the entity is an individual, profile data 708 includes, for example, a user name, phone number, address, settings (eg, notification and privacy settings), and a user-selected avatar (or collection of such avatars). A particular user may then selectively include one or more of these avatar representations within the content of messages communicated via messaging system 100 and on map interfaces displayed by messaging client 104 to other users. A collection of avatar representations may include a "status avatar," which presents a graphical representation of a status or activity that a user may choose to communicate at a particular time. In addition to the user identification 718, the profile data 708 representing a profile paired with another user profile (where the paired profile represents a user of the co-location connectivity service 117) also includes a user device identification 720 and a paired user identification 722 . In one example, the location data exchange component of the power optimization system 206 shown in FIG. 2 obtains the location of the user equipment (represented by the user equipment identification) given the user profile including the user identification, the user equipment identification, and the paired user identification. positioning data, determining a paired profile based on the paired user identification, and transmitting the obtained positioning data of the user equipment to the paired device represented by the user equipment identification stored in the paired profile.

Database 120 also stores enhancement data, such as overlays or filters, in enhancement table 710 . Enhancement data is associated with and applied to video (data for video is stored in video table 714 ) and image (data for image is stored in image table 716 ). As mentioned above, video table 714 stores video data, which in one example is associated with messages whose records are stored within message table 702 . Similarly, image table 716 stores image data associated with messages whose message data is stored in entity table 704 . Entity table 704 may associate various enhancements from enhancement table 710 with various images and videos stored in image table 716 and video table 714 .

FIG. 2 is a block diagram illustrating an example system 200 for providing a co-location experience to users of the co-location connectivity system 612 of FIG. 6 . In some examples, system 200 corresponds to co-located connection system 612 shown in FIG. 6 . The system 200 includes a pairing component 210 , a co-location detector 220 and a co-location UI generator 230 . The pairing component 210 is configured to pair two user profiles. In some implementations, only paired user profiles can access the co-location services provided by the co-location connection system 612 . The pairing of the first user profile associated with the first client device and the second user profile associated with the second client device is performed online. Pairing includes determining that the first client device and the second client device include respective short-range communication sensors configured to communicate with each other within a predetermined physical range. The pairing operation may be performed without requiring the two client devices to be within communication range of their respective short-range communication sensors at the time of pairing, and without requiring a short-range communication between the first client device and the second client device. Wireless communication technology to communicate. Pairing includes: receiving a pairing request from the first client device to pair the first user profile with the second user profile; in response to the pairing request, obtaining a permission response from the second device, the permission being associated with the second user profile and after obtaining the permission response, pairing the first user profile with the second user profile.

The co-location detector 220 is configured to detect a co-location event indicating that the first client device executing the messaging client and the second client device executing the messaging client are within a predetermined physical range. Detecting a co-location event includes 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 technique. Co-location detector 220 is further configured to detect a distance event with respect to two client devices, and in response to detecting the distance event, transmit a visual indication of the distance event to the client devices. The distance event indicates that the first client device and the second client device are located outside a predetermined physical range. The distance event includes receiving from the first client device an indication that a connection previously established between the first client device and the second client device via the short-range wireless communication technique has terminated.

Co-location UI generator 230 is configured to generate a co-location user interface in response to detection of a co-location event by co-location detector 220 . The co-location user interface may include, for example, an indication of the co-location of the first client device and the second client device, a visual control operable to activate the HTML5-based application, and/or configured to be superimposed on the first client device An animation that plays on the screen of the messaging client at execution.

Each of the various components of system 200 may be provided at client device 102 and/or messaging server system 108 of FIG. 1 . Additional details regarding the operation of system 200 are described below.

FIG. 3 is a flowchart of a method 300 for providing a co-location experience. Method 300 may be performed by processing logic that may include hardware (eg, dedicated logic, programmable logic, microcode, etc.), software, or a combination thereof. In one example implementation, some or all of the processing logic resides at the client device 102 of FIG. 1 and/or at the messaging server system 108 of FIG. 1 . Although the depicted flowcharts may show operations as sequential processing, many of the operations may be performed in parallel or simultaneously. Also, the order of operations can be rearranged. A process terminates when its operations are complete. A process may correspond to a method, procedure, algorithm, or the like. The operations of a method may be performed in whole or in part, may be performed in conjunction with some or all operations of other methods, and may be implemented by any number of different systems (such as the systems described herein) or any part thereof (such as included in any system processor) to execute.

At operation 310, the co-location detector 220 of the co-location connection system 612 detects a co-location event indicating that the first client device executing the messaging client and the second client device executing the messaging client are within a predetermined physical range. At operation 320, in response to detecting the co-location event, the co-location UI generator 230 generates a co-location user interface including an indication that the first client device and the second client device are co-located. At operation 330, the co-location user interface is transmitted to the first client device and the second client device.

FIG. 4 is a diagrammatic representation 400 of an example co-location experience displayed on a corresponding display device of a co-location partner. As shown in FIG. 4, paired client devices 410 and 420 host respective messaging clients. Respective screens 412 and 422 of the messaging client display respective indications 414 and 424 that client devices 410 and 420 are within communication range of signal 430 and are therefore recognized as co-located by co-location connection service 442 hosted at messaging server 440. Paired client devices 410 and 420 communicate with messaging server 440 via a network, such as the Internet. The respective screens 412 and 422 of the messaging client also display respective animations 416 and 426 that are configured to play (e.g., float up) superimposed on the respective screens 412 and 422, and are operable to activate other applications (e.g., HTML5-based applications ) corresponding visual controls 418 and 428.

machine architecture

5 is a diagrammatic representation of a machine 600 within which instructions 608 (e.g., software, programs, applications, program, app, or other executable code). For example, instructions 508 may cause machine 500 to perform any one or more of the methods described herein. Instructions 508 transform a general-purpose unprogrammed machine 500 into a specific machine 500 programmed to perform the described and illustrated functions in the described manner. Machine 500 may operate as a standalone device, or may be coupled (eg, networked) to other machines. In a networked deployment, machine 500 may operate as 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. Machine 500 may include, but is not limited to: server computers, client computers, personal computers (PCs), tablet computers, laptop computers, netbooks, set-top boxes (STBs), personal digital assistants (PDAs), entertainment media systems, cellular phones, Smartphones, mobile devices, wearable devices (e.g., smart watches), smart home devices (e.g., smart appliances), other smart devices, web appliances, network routers, network switches, network bridges, or capable of sequentially or otherwise Any machine that executes instructions 508 specifying actions to be taken by machine 500 . Further, while a single machine 500 is shown, the term "machine" shall also be taken to include a collection of machines that individually or jointly execute instructions 508 to perform any one or more of the methodologies discussed herein. For example, machine 500 may include client device 102 or any of a number of server devices forming part of messaging server system 108 . In some examples, machine 500 may also include both client systems and server systems, where certain operations of a particular method or algorithm are performed on the server side and certain operations of the particular method or algorithm are performed on the client side.

Machine 500 may include a processor 502 , a memory 504 , and an input/output (I/O) component 538 that may be configured to communicate with one another via a bus 540 . In an example, processor 502 (e.g., central processing unit (CPU), reduced instruction set computing (RISC) processor, complex instruction set computing (CISC) processor, graphics processing unit (GPU), 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, processor 506 and processor 510 that execute instructions 508 . The term "processor" is intended to include a multi-core processor, which may include two or more separate processors (sometimes referred to as "cores") that can execute instructions concurrently. Although FIG. 5 shows multiple processors 502, machine 500 may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, Multiple processors with multiple cores or any combination thereof.

Memory 504 includes main memory 512 , static memory 514 , and storage unit 516 , all of which are accessible by processor 502 via bus 1410 . The main memory 504, the static memory 514, and the storage unit 516 store instructions 508 implementing any one or more of the methods or functions described herein. Instructions 508 may also reside wholly or partially within main memory 512, within static memory 514, within machine-readable medium 518 within storage unit 515, within at least Within a processor (eg, within a processor's cache memory) or any suitable combination thereof.

I/O components 538 may include various components for receiving input, providing output, making output, transmitting information, exchanging information, capturing measurements, and the like. The particular I/O components 538 included in a particular machine will depend on the type of machine. For example, a portable machine such as a mobile phone may include a touch input device or other such input mechanism, whereas a headless server machine would be less likely to include such a touch input device. It will be appreciated that I/O components 538 may include many other components not shown in FIG. 5 . In various examples, I/O components 538 can include user output components 524 and user input components 526 . User output components 524 may include visual components (e.g., a display such as a plasma display panel (PDP), light emitting diode (LED) display, liquid crystal display (LCD), projector, or cathode ray tube (CRT)), acoustic components (e.g., speakers), haptic components (eg, vibration motors, resistance mechanisms), other signal generators, etc. User input components 526 may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, an optical keyboard, or other alphanumeric input components), pointing-based input components (e.g., a mouse, a touchpad, a trackball). , joystick, motion sensor or other pointing instrument), tactile input components (e.g., physical buttons, touch screens or other tactile input components that provide the location and force of touch or touch gestures), audio input components (e.g., microphones), etc.

In other examples, I/O components 538 may include biometric components 528, motion components 530, environmental components 532, or location components 534, among various other components. For example, the biometric component 528 includes functions for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body gestures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweating, or brain waves), identifying Components for people (for example, voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition), etc. The moving part 530 includes an acceleration sensor part (for example, an accelerometer), a gravity sensor part, and a rotation sensor part (for example, a gyroscope).

Environmental components 532 include, for example, one or more cameras (with still image/photo and video capabilities), lighting sensor components (e.g., photometers), temperature sensor components (e.g., one or more thermometers to detect ambient temperature) , humidity sensor components, pressure sensor components (e.g. barometer), acoustic sensor components (e.g. one or more microphones to detect background noise), proximity sensor components (e.g. infrared sensors to detect nearby objects), gas sensors (for example, gas detection sensors that detect concentrations of hazardous gases for safety or measure pollutants in the atmosphere), or other components that may provide indications, measurements, or signals corresponding to the surrounding physical environment.

Regarding cameras, the client device 102 may have a camera system including, for example, a front camera on the front surface of the client device 102 and a rear camera on the rear surface of the client device 102 . The front-facing camera may, for example, be used to capture still images and video (eg, "selfies") of the user of client device 102, which may then be enhanced with the aforementioned enhancement data (eg, filters). The rear camera may, for example, be used to capture still images and video in a more traditional camera mode, where these images are similarly enhanced with enhancement data. In addition to front and rear cameras, client device 102 may also include a 360° camera for capturing 360° photos and videos.

Additionally, the camera system of the client device 102 may include dual rear cameras (e.g., a main camera and a depth-aware camera), or even triple, quadruple, or quintuple rear cameras on the front and rear sides of the client device 102. Camera configuration. For example, these multi-camera systems may include wide-angle cameras, ultra-wide-angle cameras, telephoto cameras, macro cameras, and depth sensors.

The location component 534 includes a positioning sensor component (for example, a GPS receiver component), an altitude sensor component (for example, an altimeter or a barometer that detects air pressure from which the altitude can be obtained), an orientation sensor component (for example, a magnetometer), and the like.

Communications may be accomplished using various techniques. The I/O component 538 also includes a communication component 536 operable to couple the machine 500 to the network 520 or the device 522 via a corresponding coupling or connection. For example, communications component 536 may include a network interface component or other suitable device to interface with network 520 . In further examples, the communication component 536 can include a wired communication component, a wireless communication component, a cellular communication component, a near field communication (NFC) component, widget (eg, /> low energy consumption), /> components and other communication components that provide communication via other means. Device 522 may be another machine or any of a variety of peripherals (eg, a peripheral coupled via USB).

Additionally, communication component 636 can detect an identifier or include a component operable to detect an identifier. For example, communication components 636 may include radio frequency identification (RFID) tag reader components, NFC smart tag detection components, optical reader components (e.g., for detecting one-dimensional barcodes such as Universal Product Code (UPC) barcodes, such as fast Response (QR) Code, Aztec Code, Data Matrix, Data Symbol (Dataglyph), MaxiCode (MaxiCode), PDF417, Ultra Code (Ultra Code), UCC RSS-2D barcode multi-dimensional barcode, and other optical codes optical sensors) or acoustic detection components (e.g., microphones for recognizing marked audio signals). Additionally, various information can be derived via the communications component 536, such as a location via Internet Protocol (IP) geolocation, Signal triangulation yields a location, via detection of NFC beacon signals that may indicate a particular location, etc.

Various memories (e.g., main memory 512, static memory 514, and memory of processor 502) and storage unit 516 may store a set or more Sets of instructions and data structures (eg, software). These instructions (eg, instructions 508 ), when executed by processor 502 , cause various operations to implement the disclosed examples.

Communication over a network may be via a network interface device (e.g., a network interface component included in communication component 536), using a transmission medium and using any of several well-known transmission protocols (e.g., Hypertext Transfer Protocol (HTTP)). 520 to send or receive instructions 508 . Similarly, instructions 608 may be sent or received via a coupling (eg, a peer-to-peer coupling) with device 522 using a transmission medium.

Glossary

"Carrier signal" means any intangible medium capable of storing, encoding, or carrying instructions for execution by a machine and includes digital or analog communication signals or other intangible medium to facilitate communication of such instructions. Instructions may be sent or received over a network via a network interface device using a transmission medium.

"Client Device" means any machine that interfaces with a communications network to obtain resources from one or more server systems or other client devices. Client devices can be, but are not limited to, mobile phones, desktop computers, laptop computers, portable digital assistants (PDAs), smart phones, tablet computers, ultrabooks, netbooks, laptop computers, multiprocessor systems, based A microprocessor-based or programmable consumer electronics product, game console, set-top box, or any other communication device that a user can use to access a network.

Communications network" means one or more parts of a network, which may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN) , Wireless WAN (WWAN), Metropolitan Area Network (MAN), Internet, Part of Internet, Part of Public Switched Telephone Network (PSTN), Plain Old Telephone Service (POTS) Network, Cellular Telephone Network, Wireless Network, network, other types of networks, or a combination of two or more such networks. For example, a network or portion of a network may comprise a wireless network or a cellular network, and the coupling may be a Code Division Multiple Access (CDMA) connection, a Global System for Mobile Communications (GSM) connection, or other type of cellular or wireless coupling. In this example, the coupling can implement any of various types of data transmission technologies, such as Single Carrier Radio Transmission Technology (1xRTT), Evolution Data Optimized (EVDO) technology, General Packet Radio Service (GPRS) technology, Enhanced Data Rates for GSM Evolution (EDGE) technology, Third Generation Partnership Project (3GPP) including 3G, Fourth Generation Wireless (4G) networks, Universal Mobile Telecommunications System (UMTS), High Speed Packet Access (HSPA), Global Interoperability for Microwave Access (WiMAX), Long Term Evolution (LTE) standards, other data transmission technologies defined by various standard setting organizations, other long range protocols or other data transmission technologies.

"Component" means a device, physical entity, or logic having boundaries defined by function or subroutine calls, branch points, APIs, or other techniques that provide partitioning or modularization of particular processing or control functions. Components may be combined with other components via their interfaces to perform machine processes. A component may be a packaged functional hardware unit designed for use with other components, and may be a part of a program that generally performs specific ones of the related functions. A component may constitute a software component (eg, code embodied on a machine-readable medium) or a hardware component. A "hardware component" is a tangible unit capable of performing certain operations and that may be configured or arranged in a certain physical manner. In various example embodiments, one or more computer systems (e.g., stand-alone computer systems, client computer systems, or server computer systems) or one or more A number of hardware components (eg, a processor or group of processors) are configured as hardware components operative to perform certain operations described herein. Hardware components 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 Application Specific Integrated Circuit (ASIC). Hardware components may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, hardware components may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, the hardware component becomes a specific machine (or specific part of a machine) uniquely tailored to perform the configured function, rather than a general-purpose processor. It will be appreciated that cost and time considerations may dictate whether to implement hardware components mechanically, in dedicated and permanently configured circuitry, or in temporarily configured (eg, by software) circuitry. Accordingly, the phrase "hardware component" (or "hardware-implemented component") should be understood to encompass a tangible entity that is physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) into a An entity that operates in a certain way or performs some of the actions described herein. Considering the example where hardware components are temporarily configured (eg, programmed), each of the hardware components need not be configured or instantiated at any one time. For example, in the case where hardware components include a general-purpose processor that becomes a special-purpose processor through software configuration, the general-purpose processor may be respectively configured as different special-purpose processors (for example, including different hardware components) at different times. . The software accordingly configures one or more particular processors to constitute, for example, a particular hardware component at one moment in time, and to constitute a different hardware component at a different moment in time. Hardware components can provide information to, and receive information from, other hardware components. Accordingly, the described hardware components may be considered to be communicatively coupled. Where multiple hardware components are present at the same time, communications may be achieved by the transmission of signals between or among two or more hardware components (eg, through appropriate circuits and buses). In embodiments where multiple hardware components are configured or instantiated at different times, this may be achieved, for example, by storing information in a memory structure to which the multiple hardware components have access and retrieving information from that memory structure communication between such hardware components. For example, a hardware component may perform an operation and store the output of the operation in its communicatively coupled memory device. Other hardware components can then access the memory device at a later time to retrieve and process the stored output. A hardware component can also initiate communications with input or output devices, and can operate on a resource (eg, a collection of information). The various operations of the example methods described herein may be performed, at least in part, by one or more processors that are temporarily configured (eg, by software) or permanently configured to perform the relevant operations. Whether temporarily configured or permanently configured, such a processor may constitute a processor-implemented component operative to perform one or more operations or functions described herein. As used herein, a "processor-implemented component" refers to a hardware component implemented using one or more processors. Similarly, the methods described herein may be implemented at least in part by a processor, the particular processor or processors being an example of hardware. For example, at least some operations of a method may be performed by one or more processors 1004 or processor-implemented components. Additionally, the one or more processors may also be operable to support the performance of related 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 an example of a machine including a processor), where these operations can be performed via a network (e.g., the Internet) and via one or more suitable interfaces (e.g., an API). ) to access. Execution of certain operations can be distributed across processors, not residing only within a single machine, but deployed across multiple machines. In some example embodiments, a processor or processor-implemented components may be located in a single geographic location (eg, within a home environment, office environment, or server farm). In other example implementations, a processor or processor-implemented component may be distributed across several geographic locations.

"Computer-readable storage medium" refers to both machine storage media and transmission media. Accordingly, these terms include both storage devices/media and carrier/modulated data signals. The terms "machine-readable medium", "computer-readable medium" and "device-readable medium" mean the same thing and may be used interchangeably in this disclosure.

"Machine storage medium" means a single or multiple storage devices and media (eg, centralized or distributed databases, and associated caches and servers) that store executable instructions, routines, and data. Accordingly, the term should be read to include, but not be limited to, solid-state memory, as well as optical and magnetic media, including memory internal or external to the processor. Specific examples of machine storage media, computer storage media, and device storage media include: non-volatile memory, including, for example, semiconductor memory devices such as Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), FPGA, and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The terms "machine storage medium", "device storage medium", "computer storage medium" mean the same thing and may be used interchangeably in this disclosure. The terms "machine storage medium", "computer storage medium" and "device storage medium" expressly exclude carrier waves, modulated data signals and other such media at least some of which are covered by the term "signal medium".

A "non-transitory computer-readable storage medium" refers to a tangible medium capable of storing, encoding, or carrying instructions for execution by a machine.

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

Claims (as amended under Article 19 of the Treaty)

1. A method comprising:

In an online messaging system comprising a messaging client and an associated backend service, providing a co-location connected service accessible from a client device via the messaging client:

detecting a co-location event indicating that a first client device executing the messaging client and a second client device executing the messaging client are within a predetermined physical range;

in response to detecting the co-location event, generating a co-location user interface including an indication that the first client device and the second client device are co-located; and

causing the co-location user interface to be presented to the first client device and the second client device,

Wherein the database of the messaging system includes an entity map to store information reflecting pairs representing user profiles of users of the co-location connectivity service.

2. The method of claim 1, wherein the detecting a co-location event comprises receiving from the first client device a communication between the first client device and the second client device via a short-range wireless communication technique. An indication of the connection established between.

3. The method of claim 1, wherein said generating a co-location user interface comprises including in said co-location user interface a visual control operable to activate an additional application.

4. The method of claim 1 , wherein the generating a co-location user interface comprises including in the co-location user interface a message configured to overlay a messaging client executing at the first client device. An animation played on the screen.

5. The method of claim 1 , wherein the messaging maintains a profile representing a corresponding user of the co-location connectivity service, the first client device communicating with the first user profile from the profile. profile, the second client device is associated with a second user profile from the profile.

6. The method of claim 5, further comprising pairing the first user profile and the second user profile online, the pairing comprising:

receiving a pairing request from the first client device to pair the first user profile with the second user profile;

obtaining a permission response from the second device in response to the pairing request, the permission being associated with the second user profile; and

After obtaining the permission response, pairing the first user profile with the second user profile.

7. The method of claim 6, wherein the pairing comprises determining that the first client device and the second client device include corresponding sensors configured to communicate with each other within the predetermined physical range .

8. The method of claim 7, wherein the pairing is achieved without communication between the first client device and the second client device via a short-range wireless communication technique.

9. The method of claim 1, further comprising:

detecting a distance event indicating that the first client device and the second client device are located outside the predetermined physical range; and

In response to detecting the distance event, a visual indication of the distance event is communicated to the first client device and the second client device.

10. The method of claim 9, wherein the detecting a distance event comprises receiving from the first client device a previous communication between the first client device and the second client device via short-range wireless communication technology. An indication that the established connection has been terminated.

11. A system comprising:

one or more processors; and

A non-transitory computer-readable storage medium comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform operations including:

In an online messaging system comprising a messaging client and an associated backend service, providing a co-location connected service accessible from a client device via the messaging client:

detecting a co-location event indicating that a first client device executing the messaging client and a second client device executing the messaging client are within a predetermined physical range;

in response to detecting the co-location event, generating a co-location user interface including an indication that the first client device and the second client device are co-located; and

causing the co-location user interface to be presented to the first client device and the second client device,

Wherein the database of the messaging system includes an entity map to store information reflecting pairs representing user profiles of users of the co-location connectivity service.

12. The system of claim 11, wherein the detecting a co-location event comprises receiving from the first client device a communication between the first client device and the second client device via a short-range wireless communication technique. An indication of the connection established between.

13. The system of claim 11, wherein said generating a co-location user interface comprises including in said co-location user interface a visual control operable to activate an additional application.

14. The system of claim 11 , wherein the generating a co-location user interface comprises including in the co-location user interface a message configured to overlay a messaging client executing at the first client device. An animation played on the screen.

15. The system of claim 11 , wherein the messaging maintains a profile representing a respective user of the co-location connectivity service, the first client device communicating with the first user profile from the profile. profile, the second client device is associated with a second user profile from the profile.

16. The system of claim 15 , wherein operations caused by instructions executed by the one or more processors include:

pairing the first user profile and the second user profile online, the pairing comprising:

receiving a pairing request from the first client device to pair the first user profile with the second user profile;

obtaining a permission response from the second device in response to the pairing request, the permission being associated with the second user profile; and

After obtaining the permission response, pairing the first user profile with the second user profile.

17. The system of claim 16, wherein the pairing includes determining that the first client device and the second client device include corresponding sensors configured to communicate with each other within the predetermined physical range. .

18. The system of claim 17, wherein the pairing is achieved without communication between the first client device and the second client device via a short-range wireless communication technique.

19. The system of claim 11 , wherein operations caused by instructions executed by the one or more processors include:

detecting a distance event indicating that the first client device and the second client device are located outside the predetermined physical range; and

In response to detecting the distance event, a visual indication of the distance event is communicated to the first client device and the second client device.

20. A machine-readable non-transitory storage medium having instruction data executable by a machine to cause the machine to perform operations, the operations comprising:

In an online messaging system comprising a messaging client and an associated backend service, providing a co-location connected service accessible from a client device via the messaging client:

detecting a co-location event indicating that a first client device executing the messaging client and a second client device executing the messaging client are within a predetermined physical range;

in response to detecting the co-location event, generating a co-location user interface including an indication that the first client device and the second client device are co-located; and

causing the co-location user interface to be presented to the first client device and the second client device,

Wherein the database of the messaging system includes an entity map to store information reflecting pairs representing user profiles of users of the co-location connectivity service.

Claims (20)

1. A method comprising: In an online messaging system comprising a messaging client and an associated backend service, providing a co-location connected service accessible from a client device via the messaging client: detecting a co-location event indicating that a first client device executing a messaging client and a second client device executing the messaging client are within a predetermined physical range; in response to detecting the co-location event, generating a co-location user interface including an indication that the first client device and the second client device are co-located; and The co-location user interface is caused to be presented to the first client device and the second client device. 2. The method of claim 1, wherein the detecting a co-location event comprises receiving from the first client device a communication between the first client device and the second client device via a short-range wireless communication technique. An indication of the connection established between. 3. The method of claim 1, wherein said generating a co-location user interface comprises including in said co-location user interface a visual control operable to activate an additional application. 4. The method of claim 1 , wherein the generating a co-location user interface comprises including in the co-location user interface a message configured to overlay a messaging client executing at the first client device. An animation played on the screen. 5. The method of claim 1 , wherein the messaging maintains a profile representing a corresponding user of the co-location connectivity service, the first client device communicating with the first user profile from the profile. profile, the second client device is associated with a second user profile from the profile. 6. The method of claim 5, further comprising pairing the first user profile and the second user profile online, the pairing comprising: receiving a pairing request from the first client device to pair the first user profile with the second user profile; obtaining a permission response from the second device in response to the pairing request, the permission being associated with the second user profile; and After obtaining the permission response, pairing the first user profile with the second user profile. 7. The method of claim 6, wherein the pairing comprises determining that the first client device and the second client device include corresponding sensors configured to communicate with each other within the predetermined physical range . 8. The method of claim 7, wherein the pairing is achieved without communication between the first client device and the second client device via a short-range wireless communication technique. 9. The method of claim 1, further comprising: detecting a distance event indicating that the first client device and the second client device are located outside the predetermined physical range; and In response to detecting the distance event, a visual indication of the distance event is communicated to the first client device and the second client device. 10. The method of claim 9, wherein the detecting a distance event comprises receiving from the first client device a previous communication between the first client device and the second client device via short-range wireless communication technology. An indication that the established connection has been terminated. 11. A system comprising: one or more processors; and A non-transitory computer-readable storage medium comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform operations including: In an online messaging system comprising a messaging client and an associated backend service, providing a co-location connected service accessible from a client device via the messaging client: detecting a co-location event indicating that a first client device executing a messaging client and a second client device executing the messaging client are within a predetermined physical range; in response to detecting the co-location event, generating a co-location user interface including an indication that the first client device and the second client device are co-located; and The co-location user interface is caused to be presented to the first client device and the second client device. 12. The system of claim 11, wherein the detecting a co-location event comprises receiving from the first client device a communication between the first client device and the second client device via a short-range wireless communication technique. An indication of the connection established between. 13. The system of claim 11, wherein said generating a co-location user interface comprises including in said co-location user interface a visual control operable to activate an additional application. 14. The system of claim 11 , wherein the generating a co-location user interface comprises including in the co-location user interface a message configured to overlay a messaging client executing at the first client device. An animation played on the screen. 15. The system of claim 11 , wherein the messaging maintains a profile representing a respective user of the co-location connectivity service, the first client device communicating with the first user profile from the profile. profile, the second client device is associated with a second user profile from the profile. 16. The system of claim 15 , wherein operations caused by instructions executed by the one or more processors include: pairing the first user profile and the second user profile online, the pairing comprising: receiving a pairing request from the first client device to pair the first user profile with the second user profile; obtaining a permission response from the second device in response to the pairing request, the permission being associated with the second user profile; and After obtaining the permission response, pairing the first user profile with the second user profile. 17. The system of claim 16, wherein the pairing includes determining that the first client device and the second client device include corresponding sensors configured to communicate with each other within the predetermined physical range. . 18. The system of claim 17, wherein the pairing is achieved without communication between the first client device and the second client device via a short-range wireless communication technique. 19. The system of claim 11 , wherein operations caused by instructions executed by the one or more processors include: detecting a distance event indicating that the first client device and the second client device are located outside the predetermined physical range; and In response to detecting the distance event, a visual indication of the distance event is communicated to the first client device and the second client device. 20. A machine-readable non-transitory storage medium having instruction data executable by a machine to cause the machine to perform operations, the operations comprising: In an online messaging system comprising a messaging client and an associated backend service, providing a co-location connected service accessible from a client device via the messaging client: detecting a co-location event indicating that a first client device executing a messaging client and a second client device executing the messaging client are within a predetermined physical range; in response to detecting the co-location event, generating a co-location user interface including an indication that the first client device and the second client device are co-located; and The co-location user interface is caused to be presented to the first client device and the second client device.