Patent Grant
11019391
This disclosure generally relates to determining that mobile devices and content devices are connected to the same local networks, and to providing customized content to these devices.
Users of an online system view and interact with content presented on their mobile devices such as smartphones. Since smartphones are typically personal devices, the online system may customize the content provided to the smartphones. In other words, based on user-specific information received from a personal mobile device, the online system may determine content items likely to be interesting to a particular user. However, the number of electronic devices that users can use to access online content has been increasing. For instance, in addition to smartphone type mobile devices, users have smart TVs, set-top boxes, or other types of content devices that provide digital media. In contrast to smartphones, smart TVs and set-top boxes may not be personal devices, e.g., multiple users in a household may use the same smart TV, and the users may not need to log in to an account on a content device as they would for applications on a smartphone. Thus, conventional systems are unable to provide customized content to these non-personal content devices. It is challenging and desirable for an online system to determine which specific users are using a content device, so that the online system can personalize the content presented to the users.
An online system determines that mobile devices and content devices are connected to the same local network. In an embodiment, a user that interacts with the online system using a smartphone mobile device also uses other types of content devices to access online content. For example, the user watches TV shows and movies on a smart TV or via a set-top box, or listens to music or radio using a digital media streaming device. The online system can associate the smartphone to the user because the user logs in to a user profile via an application on the smartphone. However, the user may not necessarily log in using content devices. Thus, to determine whether a content device is associated with a certain user, the online system provides a token and network ports to the content device. A content device that is connected to the same local network (e.g., a WiFi network at the user's home or office) as the mobile device can establish a connection together using a selected network port, and send the token to the mobile device. Responsive to receiving the token from the mobile device, the online system determines that the mobile device and the content device are connected to the same local network. Thus, the online system may send content items to one or both of the devices, and the user may view or interact with content items simultaneously on multiple devices.
The figures depict embodiments of the present invention for purposes of illustration only. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the invention described herein.
I. System Overview
The online system 100 allows users of the online system 100 to communicate or otherwise interact with each other and access content. The online system 100 receives information about the users, for example, user profile information and information about actions performed by users on the online system 100 or a third party system 120. The online system 100 stores the information associated with user profiles, e.g., in a social graph data structure. In addition, the online system 100 provide content items (e.g., text, images, video, audio, or other types and combinations of media) for presentation to users via mobile devices 110 or content devices 140. The online system 100 may use a token to determine that a given mobile device 110 and a given content device 140 are simultaneously connected to a same local network 150. Thus, the online system can personalize content items sent to both mobile devices 110 and content devices 140 based on the known information about the users.
A third party system 120 may also provide content items for communication to users via mobile devices 110 and content devices 140. Such an entity may be a company or other type of organization offering a product or message. In some embodiments, the third party system 120 provides compensation to the online system 100 in return for the online system 100 presenting the third party system's 120 content items to users. Further, the third party system 120 may provide criteria indicating attributes of users to which to target certain types of content items.
A mobile device 110 is a computing device capable of receiving user input as well as transmitting or receiving data via the network 130. In one embodiment, a mobile device 110 is a conventional computer system, such as a desktop or laptop computer. Alternatively, a mobile device 110 may be a device having computer functionality, such as a personal digital assistant (PDA), a mobile telephone, a smartphone, or another suitable device. In one embodiment, a mobile device 110 executes an application allowing a user of the mobile device 110 to interact with the online system 100 or a third party system 120. For example, a mobile device 110 executes a browser application to enable interaction between the mobile device 110 and the online system 100 via the network 130.
Since users may log in or sign in to the user's account on the online system 100, the online system 100 can associate a mobile device 110 to the particular user who owns or uses that mobile device 110. For instance, the mobile device 110 stores a cookie (also referred to as a web cookie, Internet cookie, or browser cookie), which the online system 100 may use to identify the corresponding user of the mobile device 110. In some embodiment, a mobile device 110 interacts with the online system 100 through an application programming interface (API) running on a native operating system of the mobile device 110, such as IOS® or ANDROID™.
A content device 140, similar to a mobile device 110, is also a computing device capable of receiving user input as well as transmitting or receiving data from the online system 100 or a third party system 120 via the network 130. In some embodiments, the content device 140 is a smart TV, set-top box, digital media streaming device, Internet of things (IoT) device, or another type of device suitable for presenting content to users. In contrast to a mobile device 110, a user of a content device 140 may not necessarily log in to a user profile (or user account) using the content device 140. Moreover, in some embodiments, mobile devices 110 are normally associated with one user, while content devices 140 may be used by any number of users (e.g., simultaneously or at different times). In some embodiments, a content device 140 executes an application associated with a third party system 120.
A local network 150, also known as a local area network (LAN) connects devices within a given geographic area. Local networks 150 may use wired transmission technologies (e.g., Ethernet) or wireless transmission technologies (e.g., WiFi). For example, a local network 150 may be a WiFi network connecting devices within a house, apartment, commercial building, office building, or outdoors area.
The network 130 includes any combination of local area networks (e.g., local networks 150) or wide area networks, using wired or wireless communication systems. In one embodiment, the network 130 uses standard communications technologies and/or protocols. For example, the network 130 includes communication links using technologies such as Ethernet, 802.11, worldwide interoperability for microwave access (WiMAX), 3G, 4G, code division multiple access (CDMA), digital subscriber line (DSL), etc. Examples of networking protocols used for communicating via the network 130 include multiprotocol label switching (MPLS), transmission control protocol/Internet protocol (TCP/IP), hypertext transport protocol (HTTP), simple mail transfer protocol (SMTP), and file transfer protocol (FTP). Data exchanged over the network 130 may be represented using any suitable format, such as hypertext markup language (HTML) or extensible markup language (XML). In some embodiments, all or some of the communication links of the network 130 may be encrypted using any suitable technique or techniques.
By providing customized content items to both a content device 140 and mobile device 110 of the user, the online system 100 may provide a more engaging user experience that is personalized to the user. For example, the smart TV content device 140 has a larger display than the smartphone mobile device 110, but may not include as many user controls (e.g., a touch screen interface) as the mobile device 110. Thus, by providing complementary content items simultaneously to the two devices, the user can interact with the content item displayed on the smart TV using the smartphone, e.g., serving as a complementary “control device.” For instance, the smart TV shows an image of a car, and the user can explore different views outside and inside the car using the smartphone, resulting in a more immersive experience than would be possible with only one of the two devices. In some embodiments, the mobile device 110 or content device 140 may be a virtual or augmented reality (VR/AR) type device.
II. Example System Architecture of Online System
The user profile store 200 stores user profiles associated with users of the online system 100. A user profile includes declarative information about the user that was explicitly shared by the user and may also include profile information inferred by the online system 100. In one embodiment, a user profile includes multiple data fields, each describing one or more attributes of the corresponding user of the online system 100. Examples of information stored in a user profile include biographic, demographic, and other types of descriptive information, such as work experience, educational history, gender, hobbies or preferences, location and the like.
A user profile may also store other information provided by the user, for example, images or videos. In certain embodiments, images of users may be tagged with identification information of users of the online system 100 displayed in an image. A user profile in the user profile store 200 may also maintain references to actions by the corresponding user performed on the online system 100. The user profile store 200 further stores data describing one or more relationships between different users and allows users to specify their relationships with other users. For example, these user-defined relationships allow users to generate relationships with other users that parallel the user's real-life relationships, such as friends, co-workers, partners, and the like.
The user profile store 200 can store user profiles associated with individuals, as well as user profiles associated with entities such as businesses or organizations, e.g., associated with a third party system 120. This allows an entity to establish a presence on the online system 100 for connecting and exchanging content with other users of the online system 100. The entity may post information about itself, about items associated with the entity, for example, products offered by the entity, or provide other information to users of the online system 100 using a brand page associated with the entity's user profile. Users of the online system 100 may connect to the brand page to receive information posted to the brand page or to receive information from the brand page. A user profile associated with the brand page may include information about the entity itself, providing users with background or informational data about the entity.
The action logger 210 receives communications about user actions internal to and/or external to the online system 100, populating the action log 220 with information about user actions. Examples of actions include adding a connection to another user, sending a message to another user, uploading an image, reading a message from another user, viewing content associated with another user, attending an event posted by another user, among others. In addition, a number of actions may involve an object and one or more particular users, so these actions are associated with those users as well and stored in the action log 220.
The action log 220 may be used by the online system 100 to track user actions on the online system 100, as well as actions on third party systems 120 that communicate information to the online system 100. Users may interact with various objects on the online system 100, and the action logger 210 stores information describing these interactions in the action log 220. Examples of interactions with objects include: interacting with a content items displayed on a user interface of content device 140 or mobile device 110, viewing products on a brand page, commenting on posts, sharing links, and checking-in to physical locations via a mobile device 110, and any other interactions. Additional examples of interactions with objects on the online system 100 that are included in the action log 220 include: acquiring a product from a third party system 120, commenting on a photo album, communicating with a user, establishing a connection with an object, joining an event to a calendar, joining a group, creating an event, authorizing an application, using an application, and expressing a preference for an object (“liking” the object).
The issuing engine 230 and the network engine 240 determine whether content devices 140 and mobile devices 110 are connected to the same local networks 150. The issuing engine 230 communicates with content devices 140 to issue tokens, e.g., which function similarly to a web cookie. In particular, responsive to the issuing engine 230 identifying a content device 140 that is online (e.g., connected to the network 130 via a local network 150), the issuing engine 230 sends a range of ports and a token to the content device 140. Further, the issuing engine 230 requests the content device 140 to select one of the ports and listen for a connection on a local network 150 by opening the selected port. The issuing engine 230 may determine the token randomly and associate a specific token with the content device 140, e.g., to be saved in the network data store 235. In use cases where there are multiple content devices 140 in a certain geographic area, the issuing engine 230 may provide unique tokens to each of the content devices 140.
The network engine 240 communicates with mobile devices 110 to receive tokens from the mobile devices 110. In particular, when a mobile device 110 is online, the mobile device 110 sends network information to the network engine 240, for example, indicating an IP address (e.g., IPV6), a subnet, or other network identifying information. Responsive to the network engine 240 suspecting that the mobile device 110 is connected to the same local network 150 as a given content device 140 (previously issued a token) based on the network information, the network engine 240 provides the port selected by the given content device 140 to the mobile device 110. At this point, the network engine 240 may not necessarily know for certain that the mobile device 110 is connected to the same local network 150 because multiple devices could have the same IP address, but not be connected to the same local network.
If the mobile device 110 is able to connect to the given content device 140 using the selected port, the given content device 140 sends the token to the mobile device 110. In turn, the mobile device 110 sends the token to the network engine 240. Since the issuing engine 220 stored information about the token previously provided to the content device 140 in the network data store 235, the network engine 240 can compare the token received from the mobile device 110 with the stored token information. Responsive to determining a match of the tokens, the network engine 240 verifies that the devices are connected on the same local network 150. On the other hand, responsive to the network engine 240 not identifying a suspected shared local network connection, the network engine 240 may store the network information received from the mobile device 110 in the network data store 235, and may later access the stored information when other content devices 140 come online.
Once the online system 100 determines that a mobile device 110 and content device 140 are on the same local network 150, the online system 100 may not know whether the devices are physically located nearby each other, in some embodiments. If the content device 140 is not nearby the mobile device 110, the user will not be able to view (e.g., simultaneously or during the same session) content items displayed on both of the devices. For instance, the mobile device 110 and content device 140 are both connected to the same WiFi local network 150 at the user's house, but the user and the mobile device 110 are located in a different room of the house than the content device 140. Thus, to determine a physical proximity between a mobile device 110 and a content device, the signal processing engine 250 analyzes signals received from the mobile device 110 or the content device 140. In some embodiments, the signal processing engine 250 includes a signal strength detector 260 and an audio processing engine 270.
In one embodiment, the signal strength detector 260 determines the strengths of signals detected by the mobile device 110 or the content device 140. The devices may detect signals such as WiFi signals, BLUETOOTH® signals, or infrared (IR) signals, among others. The signal strength detector 260 may determine a received signal strength indicator (RSSI) of the detected signal or another type of signal strength measurement. Responsive to determining that the strength of a signal is greater than a threshold value, the signal strength detector 260 determines that a mobile device 110 is located in physical proximity to a content device 140. For example, if the mobile device 110 and content device 140 are both located nearby a WiFi router or BLUETOOTH® beacon, the detected signals from each device will have comparable signal strengths. In some embodiments, the signal strength detector 260 sends instructions to one of the mobile device 110 or the content device 140 to send a short-range transmission (WiFi or BLUETOOTH® signals), which may be detected by the other device if the two devices are located nearby each other. In other words, one of the devices functions as a beacon.
In one embodiment, the audio processing engine 270 analyzes audio signals detected by the mobile device 110 or the content device 140. In one example, responsive to determining that the volume of a detected audio signal is greater than a threshold value, the audio processing engine 270 determines that a mobile device 110 is located in physical proximity to a content device 140. The audio processing engine 270 may also analyze other parameters of audio signals such as frequency, variance, or patterns extracted from the signal, to determine physical proximity. Additionally, the audio processing engine 270 may implement audio processing techniques known to one skilled in the art, e.g., voice recognition or filtering algorithms. Similar to the signal strength detector 260, the audio processing engine 270 may send instructions to one of the mobile device 110 or content device 140 to function as an “audio beacon.” If the two devices are nearby each other, then an audio signal played by device designated as the beacon will be detected by the other device. In use cases where multiple devices detect the same signal, the signal processing engine 250 may determine which of the detecting devices is closest to the origin of the signal (e.g., a device functioning as the beacon).
The content engine 280 sends content items to mobile devices 110 and content devices 140 for presentation to users of the online system 100. The content engine 280 can analyze information from other components of the online system 100 (e.g., the user profile store 200 or action log 220) to generate content items. Additionally, the content engine 280 may store generated content items or content items received from a third party system 120 in the content database 205. In some embodiments, the content engine 280 sends content items that include sponsored content.
In some embodiments, the content engine 280 sends content items to devices responsive to the online system 100 determining that the devices are connected to the same local network 150 and/or located within physical proximity to each other. Additionally, the content engine 280 may send content items, which are associated with or complementary to each other, to nearby devices. For example, a first content item includes one view (e.g., a top, bottom, side, isometric, perspective, exploded, or cross-sectional view) of a graphic or object, and a second content item includes a different view of the same graphic or object. As another example, a first content item includes a first video and a second content item includes a second (e.g., different or the same) video that is synchronized with the first video. Moreover, the content engine 280 may send instructions to a device to update a content item displayed on the device, e.g., responsive to the action logger 210 determining that a user interacted with the content item or another content item. In one use case, the action logger 210 determines that the user acquired an item, e.g., a movie or a song, using a smartphone mobile device 110, and a smart TV content device 140 (nearby the user) updates its display to play the movie or the song. In some embodiments, the content engine 280 selects which content items to send based on previously provided content items. For example, the action logger 210 determines that a user viewed a content item associated with a third party system 120 on a smart TV content device 140 at the user's house. Thus, the content engine 280 sends another content item associated with the third party system 120 for display on a different content device 140, e.g., another smart TV at the apartment of the user's friend when the user visits the friend's apartment.
In some embodiments, the content engine 280 sends content items for presentation responsive to determining that a user has visited a certain geographic area at least a threshold number of times during a predetermined period (e.g., 3 times in 7 days). The content engine 280 may track the number of times the user visits the certain geographic area based on the issuing engine 230, network engine 240, and signal processing engine 250 determining instances in which a mobile device 110 of the user is physically located nearby a content device 140 and also connected to the same local network 150. For instance, the content engine 280 tracks how many times the user visits a living room of the user's house that includes a smart TV content device 140. In some embodiments, the content engine 280 does not send a sponsored content item to the devices during the first detected instance of a mobile device 110 being located nearby a content device 140.
III. Example Sequence Diagram for Providing Content Items
To confirm the suspected connection of the mobile device 110 and content device 140 to the local network 150, the online system 100 sends 312 information about the selected port to the mobile device 110. Using the selected port, the mobile device 110 requests 314 to connect to the content device 140. If the mobile device 110 and content device 140 are indeed connected to the same local network 150, the two devices establish 316 a connection with each other. In some embodiments, the devices periodically execute a background process (e.g., which can run even if a user is not actively interacting with a client application using the device) to perform these steps for trying to establish a connection. The content device 140 sends 318 the token to the mobile device 110 via the established connection. The mobile device 110 sends 320 the received token to the online system 100. Since the online system 100 originally sent the token (in step 302) to the content device 140, the online system 100 can determine 322 that the mobile device 110 and content device 140 are connected to the same local network 150 based on the token received from the mobile device 110. Responsive to confirming that the two devices are on the same local network 150, the online system 100 determines 324 a content item customized for a user of the devices and sends 326 the content item to the content device 140 for presentation to the user.
IV. Example Process Flows
In one embodiment, the issuing engine 230 sends 410 network ports and a token to a content device 140. The issuing engine 230 receives 420 a selection of one of the network ports from the content device 140. The issuing engine 230 stores 430 first network information associated with the content device 140 in the network data store 235, where the first network information includes an indication of the selected network port. The network engine 240 receives 440 second network information from a mobile device 110 connected to a local network 150. The network engine 240 determines 450 that the content device 140 and the mobile device 110 are potentially connected to the local network 150 based on the first network information and the second network information. The network engine 240 sends 460 information indicating the selected port to the mobile device 110 in response to determining that the content device 140 and the mobile device 110 are potentially connected to the local network 150. The content device 140 provides the token to the mobile device 110 through a connection established via the selected port. The network engine 240 receives 470 the token from the mobile device 110. The network engine 240 determines 480 that the content device 140 and the mobile device 110 are simultaneously connected to the local network 150 based on the received token. The content engine 280 sends 490 a content item for presentation to the content device 140 in response to determining that the content device 140 and the mobile device 110 are simultaneously connected to the local network 150.
In some embodiments, the tokens sent by the issuing engine 230 expire after a predetermined duration of time (e.g., 1, 5, or 10 minutes). Using periodically expiring tokens may be advantageous for security or quality control purposes, e.g., to prevent other systems or devices from circumventing the issuing engine 230 to produce tokens. Responsive to determining that a token issued to a content device 140 has expired, the issuing engine 230 may send a subsequent token to the content device 140, and update the corresponding information in the network data store 235. Furthermore, the issuing engine 230 may also send an updated range of ports, and in return, the content device 140 may send information indicating a selected of a subsequent port from the updated range of ports to the online system 100. The content device 140 may send the subsequent token to a mobile device 110 via a re-established (or a new) connection using the subsequent selected port. Responsive to the online system 100 receiving the subsequent token from the mobile device 110, the content engine 280 provides a subsequent content item for presentation to the content device 140.
In one embodiment, the network engine 240 determines 510 that a content device 140 and a mobile device 110 of a user are simultaneously connected to a local network 150 (for example, using the method shown in
In some embodiments, the action logger 210 determines that the user is not interested in the first content item based on the interaction. For example, the interaction indicates that the user closed or skipped the first content item, or viewed the first content item for only a short period of time. Responsive to this determination, the content engine 280 sends a third content item to replace the first content item for presentation of the display of the content device 140. For example, the first content item includes information describing a certain genre of TV shows, while the third content item includes information describing a different genre of TV shows or other online media. The content engine 280 may select the third content item from a set of candidate content items not including the first content item. In an embodiment, the first content item may include content from a third party system 120, and the set of candidate content items does not include other content from the same third party system 120, e.g., because the online system 100 determines that the user does not have an interest in the third party system 120.
V. Alternative Embodiments
The foregoing description of the embodiments of the invention has been presented for the purpose of illustration; it is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Persons skilled in the relevant art can appreciate that many modifications and variations are possible in light of the above disclosure.
Some portions of this description describe the embodiments of the invention in terms of algorithms and symbolic representations of operations on information. These algorithmic descriptions and representations are commonly used by those skilled in the data processing arts to convey the substance of their work effectively to others skilled in the art. These operations, while described functionally, computationally, or logically, are understood to be implemented by computer programs or equivalent electrical circuits, microcode, or the like. Furthermore, it has also proven convenient at times, to refer to these arrangements of operations as modules, without loss of generality. The described operations and their associated modules may be embodied in software, firmware, hardware, or any combinations thereof.
Any of the steps, operations, or processes described herein may be performed or implemented with one or more hardware or software modules, alone or in combination with other devices. In one embodiment, a software module is implemented with a computer program product including a computer-readable non-transitory medium containing computer program code, which can be executed by a computer processor for performing any or all of the steps, operations, or processes described.
Embodiments of the invention may also relate to a product that is produced by a computing process described herein. Such a product may include information resulting from a computing process, where the information is stored on a non-transitory, tangible computer readable storage medium and may include any embodiment of a computer program product or other data combination described herein.
Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the invention be limited not by this detailed description, but rather by any claims that issue on an application based hereon. Accordingly, the disclosure of the embodiments of the invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.
This application is a continuation of co-pending U.S. application Ser. No. 15/657,939, filed Jul. 24, 2017, which is incorporated by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 9084003 | Sanio et al. | Jul 2015 | B1 |
| 10439676 | Belk | Oct 2019 | B2 |
| 20050177861 | Ma et al. | Aug 2005 | A1 |
| 20060020960 | Relan et al. | Jan 2006 | A1 |
| 20110069940 | Shimy et al. | Mar 2011 | A1 |
| 20110071841 | Fomenko et al. | Mar 2011 | A1 |
| 20110141293 | Yoneyama et al. | Jun 2011 | A1 |
| 20120315848 | Smith et al. | Dec 2012 | A1 |
| 20130027613 | Kim et al. | Jan 2013 | A1 |
| 20130124309 | Traasdahl et al. | May 2013 | A1 |
| 20140157339 | Zhang et al. | Jun 2014 | A1 |
| 20140168071 | Ahmed et al. | Jun 2014 | A1 |
| 20150234820 | Aravamudan | Aug 2015 | A1 |
| 20150237394 | Haykinson et al. | Aug 2015 | A1 |
| 20150326692 | Kaneko et al. | Nov 2015 | A1 |
| 20160006864 | Park et al. | Jan 2016 | A1 |
| 20160105826 | Matsunaga | Apr 2016 | A1 |
| 20160149891 | Kuper et al. | May 2016 | A1 |
| 20160219319 | Servignat et al. | Jul 2016 | A1 |
| 20160262198 | Gardner, III et al. | Sep 2016 | A1 |
| 20160294842 | Ramalingam et al. | Oct 2016 | A1 |
| 20160359932 | Cho et al. | Dec 2016 | A1 |
| 20160371751 | Cohen | Dec 2016 | A1 |
| 20170048590 | Chen | Feb 2017 | A1 |
| 20170094345 | Zerr et al. | Mar 2017 | A1 |
| 20170134802 | D'Acunto et al. | May 2017 | A1 |
| 20170150305 | Chaudhri et al. | May 2017 | A1 |
| 20170228774 | Sallas et al. | Aug 2017 | A1 |
| 20170324790 | Li et al. | Nov 2017 | A1 |
| 20180095615 | Martier et al. | Apr 2018 | A1 |
| 20180348965 | Stekkelpak | Dec 2018 | A1 |
| Entry |
|---|
| United States Office Action, U.S. Appl. No. 15/657,965, dated Aug. 18, 2020, 23 pages. |
| United States Office Action, U.S. Appl. No. 15/657,965, dated Apr. 25, 2018, 19 pages. |
| United States Office Action, U.S. Appl. No. 15/657,965, dated Feb. 19, 2019, 20 pages. |
| United States Office Action, U.S. Appl. No. 15/657,965, dated Oct. 26, 2018, 20 pages. |
| United States Office Action, U.S. Appl. No. 15/657,965, dated Sep. 5, 2019, 20 pages. |
| United States Office Action, U.S. Appl. No. 15/657,965, dated May 13, 2020, 22 pages. |
| United States Office Action, U.S. Appl. No. 15/657,965, dated Feb. 3, 2020, 20 pages. |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15657939 | Jul 2017 | US |
| Child | 16590688 | US |
