Contextual device locking/unlocking
Summary by NHIP
Contextual device locking
The method detects events via sensors to determine unique data and identify a second user through social-networking information linked to a first user. The system updates a lock status defining access levels to interfaces, functionality, or content based on the event, social-networking data, and device state.
Claim Score by NHIP
Abstract
Particular embodiments of a computing device associated with a user may detect an event using a sensor of the computing device. The event may be a lock-triggering event or an unlock-triggering event. The computing device may assess a state of the device. The computing device may also access further information associated with the user. The computing device may also monitor activity on the computing device to detect further events if such further monitoring is warranted. Based on the gathered information, the computing device may update a lock status of the device to lock or unlock access interfaces of the computing device, functionality of the computing device, or content accessible from the computing device. If the event comprised the computing device detecting an attempt by a third party to use the device, the device may attempt to identify the third party to determine if they are authorized to use the device.

Term
6.1 yearsleft in the term
Expires 26 October 2032.
- Priority and filed
- Granted
- Today
- Expires
20 claims: 3 independent, 17 dependent
- 1A method comprising:by a computing device associated with a first user, detecting an event using one or more sensors of the computing device;by the computing device, in response to detecting the event, determining unique data associated with a second user, wherein the event was triggered by the second user;by the computing device, assessing a state of the computing device;by the computing device, identifying the second user based on social-networking information associated with the first user and the second user, wherein the computing device looks up the social-networking information using the unique data;and by the computing device, updating a lock status of the computing device, wherein the lock status comprises a level of access to access interfaces of the computing device, functionality of the computing device, or content accessible from the computing device, the updating based on the event, the social-networking information, and the state, and wherein the level of access of the updated lock status is based on the social-networking information.
- 10One or more computer-readable non-transitory storage media embodying software operable when executed to:by a computing device associated with a first user, detect an event using one or more sensors of the computing device;by the computing device, in response to detecting the event, determining unique data associated with a second user, wherein the event was triggered by the second user;by the computing device, assess a state of the computing device;by the computing device, identify the second user based on social-networking information associated with the first user and the second user, wherein the computing device looks up the social-networking information using the unique data;and by the computing device, update a lock status of the computing device, wherein the lock status comprises a level of access to access interfaces of the computing device, functionality of the computing device, or content accessible from the computing device, the updating based on the event, the social-networking information, and the state, and wherein the level of access of the updated lock status is based on the social-networking information.
- 15Broadest claimClaim Score 57, broad(NHIP)A computing device comprising:one or more processors of a computing device associated with a first user;a sensor;and a memory coupled to the processors comprising instructions executable by the processors, the processors operable when executing the instructions to: detect an event using the sensor;in response to detecting the event, determine unique data associated with a second user, wherein the event was triggered by the second user;assess a state of the computing device;identify the second user based on social-networking information associated with the first user and the second user, wherein the processors look up the social-networking information using the unique data;and update a lock status of the computing device, wherein the lock status comprises a level of access to access interfaces of the computing device, functionality of the computing device, or content accessible from the computing device, the updating based on the event, the social-networking information, and the state, and wherein the level of access of the updated lock status is based on the social-networking information.
Independent claims3
60 paragraphs in 5 sections, as filed
TECHNICAL FIELD
0001This disclosure generally relates to computing devices, in particular, security measures for computing devices.
BACKGROUND
0002A computing device—such as a smartphone, tablet computer, or laptop computer—may include functionality for determining its location, direction, or orientation, such as a GPS receiver, compass, or gyroscope. Such a device may also include functionality for wireless communication, such as BLUETOOTH communication, near-field communication (NFC), or infrared (IR) communication or communication with a wireless local area networks (WLANs) or cellular-telephone network. Such a device may also include one or more cameras, scanners, touchscreens, microphones, or speakers. computing devices may also execute software applications, such as games, web browsers, or social-networking applications. With social-networking applications, users may connect, communicate, and share information with other users in their social networks.
SUMMARY OF PARTICULAR EMBODIMENTS
0003Particular embodiments of a computing device associated with a user may detect an event using a sensor of the computing device. The event may be a lock-triggering event or an unlock-triggering event. The computing device may assess a state of the device. The computing device may also access further information associated with the user. The computing device may also monitor activity on the computing device to detect further events if such further monitoring is warranted. Based on the gathered information, the computing device may update a lock status of the device to lock or unlock access interfaces of the computing device (e.g., screen, touchscreen, keyboard, other I/O devices), functionality of the computing device, or content accessible from the computing device. In particular embodiments, the access interfaces may be only partially unlocked, so as enable partial access to less sensitive applications or features (e.g., adjusting volume, viewing notification statistics, playing children's games). If the event comprised the computing device detecting an attempt by a third party to use the device, the device may attempt to identify the third party to determine if they are authorized to use the device.
BRIEF DESCRIPTION OF THE DRAWINGS
0004<figref idref="DRAWINGS">FIGS. 1A-B</figref> are example wireframes showing an example of contextual device locking/unlocking
0005<figref idref="DRAWINGS">FIG. 2</figref> is a flowchart of an example method according to particular embodiments.
0006<figref idref="DRAWINGS">FIG. 3</figref> is a block diagram of an example computing device.
0007<figref idref="DRAWINGS">FIG. 4</figref> is a block diagram of an example network environment.
0008<figref idref="DRAWINGS">FIG. 5</figref> is an example social graph.
DESCRIPTION OF PARTICULAR EMBODIMENTS
0009<figref idref="DRAWINGS">FIGS. 1A-B</figref> are example wireframes showing an example of contextual locking/unlocking of a user's computing device. In particular embodiments, mobile device <b>100</b> includes a touchscreen <b>105</b> and a camera <b>110</b>. Mobile device <b>100</b> may be able to connect to a social-networking system by way of a communications network, such as a cell network or Wi-Fi. Particular embodiments of a network environment associated with a social-networking system are described in further detail in <figref idref="DRAWINGS">FIG. 4</figref> and related text in the specification. Mobile device <b>100</b> may be able to detect its own location via GPS. Mobile device <b>100</b> may also include an accelerometer that can detect the motion of mobile device <b>100</b> within three dimensions. Mobile device <b>100</b> may also include a gyrometer that detects the orientation of mobile device <b>100</b> (e.g., whether mobile device <b>100</b> is tilted up or down, or turned horizontal). Mobile device <b>100</b> may further include sensors to perform biometric identification, such as by using camera <b>110</b> to capture an image in order to perform facial recognition, or by using sensors within touchscreen <b>105</b> to capture a fingerprint. Mobile device <b>100</b> may further include touch sensors and proximity sensors distributed over its exterior surface. As one of skill in the art would be aware, embodiments of the invention are not limited to receiving requests from or sending information to a mobile device and may be performed in association with other types of computing devices as described in <figref idref="DRAWINGS">FIG. 3</figref> and related text in the specification.
0010The user associated with mobile device <b>100</b> may be a member of a social-networking system, in which the computing device user's profile, connection information, and content associations are maintained. The user may be represented by a user node in the social graph. Embodiments of a social graph are described in further detail with respect to <figref idref="DRAWINGS">FIG. 5</figref>. Friends of the user may also be represented by user nodes in the social graph and connected to the user by edges in the social graph representing one or more degrees of separation. Content with which the user is associated may be represented by concept nodes in the social graph. Particular embodiments of the social graph are described in further detail in <figref idref="DRAWINGS">FIG. 5</figref> and related text in the specification.
0011As shown in <figref idref="DRAWINGS">FIG. 1A</figref>, the user has logged in to mobile device <b>100</b> and the user's personal information, such as their profile, newsfeed, contacts, messages, preferences, etc. is accessible. In an example scenario, after the user logs in to mobile device <b>100</b>, touch sensors on the back of mobile device <b>100</b> are able to detect that the user is holding mobile device <b>100</b>. In this example, even when the user props up mobile device <b>100</b> on a cushion so as to view screen <b>105</b> more comfortably, mobile device <b>100</b> is still able to detect the user is looking at the screen by performing periodic biometric identification by way of facial recognition using camera <b>110</b>. However, at one point, the user steps away from the device (e.g., to take a phone call or eat a meal), and mobile device <b>100</b> may detect that nobody is looking at the screen. After a minute or so, mobile device <b>100</b> may detect an event—that some unknown person (i.e., someone other than the user) is looking at the screen, such as, for example, by performing facial recognition. At this point, mobile device <b>100</b> may assess its state and determine that the information currently on display is of a personal nature. Mobile device <b>100</b> may determine that one or more functions and/or access interfaces of the mobile computing device should be locked. Mobile device <b>100</b> may then update its lock status and display a lock screen to the unknown person, as illustrated in <figref idref="DRAWINGS">FIG. 1B</figref>.
0012In particular embodiments, mobile device <b>100</b> may also attempt to use the facial recognition information to determine whether mobile device <b>100</b> is able to identify the unknown person. In the case where mobile device <b>100</b> is able to identify the unknown person (as, for example, the user's spouse, child, or friend), mobile device <b>100</b> may either choose not to lock its functions and/or access interfaces, or to only lock particular functions and/or access interfaces.
0013In particular embodiments, mobile device <b>100</b> may detect that an unknown person is looking at the screen, but upon assessing its state, mobile device <b>100</b> may determine that because no personal information is being displayed (e.g., only a browser window displaying the website for the New York Times newspaper), there is no immediate need to lock the screen. However, at this point, mobile device <b>100</b> may monitor activity on the device in order to detect whether the unknown person is attempting to use the device in an unauthorized manner (e.g., the person may be allowed to scroll the page up or down, but not to click on links within the website for the New York Times).
0014As shown in <figref idref="DRAWINGS">FIG. 1B</figref>, touchscreen <b>105</b> displays the lock status <b>115</b> of mobile device <b>100</b>, as well as an information/login area <b>120</b>. In particular embodiments, information/login area <b>120</b> may summarize updates received at mobile device <b>100</b>: “You have 3 notifications, 2 emails, and 1 friend request.” Information/login area <b>120</b> also displays a text input field <b>125</b> for entry of a username, text input field <b>130</b> for entry of a password, and “Unlock” button <b>135</b>, which submits the user-entered username and password for authentication. Information/login area <b>120</b> also displays a biometric identification area <b>140</b> where the user can provide a thumb scan and displays instructions: “To unlock, log in or press right thumb against designated area.”
0015In another example, mobile device <b>100</b> may automatically lock its access interfaces when placed into a bag, holster, or other enclosure (so as to avoid inadvertent user input), and then unlock its access interfaces when removed from the enclosure.
0016The steps involved in contextual locking/unlocking, as shown in <figref idref="DRAWINGS">FIG. 1</figref>, are described in further detail in <figref idref="DRAWINGS">FIG. 2</figref> and related text in the specification.
0017<figref idref="DRAWINGS">FIG. 2</figref> is a flowchart of an example method for displaying social-networking information in conjunction with an image of a real-world environment. In step <b>210</b>, particular embodiments maintain social-networking information for a user represented by a user node in a social graph.
0018In step <b>210</b>, particular embodiments of a computing device associated with a user may detect an event on the computing device. The event may comprise one of two types a lock-triggering event or an unlock-triggering event. A lock-triggering event may comprise any of a number of different events, such as, by way of example and not limitation: <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0019">closing a lid of the computing device;</li><li id="ul0002-0002" num="0020">placing the computing device on standby;</li><li id="ul0002-0003" num="0021">placing the computing device into an enclosure, such as a bag, sleeve, holster, or stand;</li><li id="ul0002-0004" num="0022">placing the computing device onto a surface with a screen of the computing device facing down;</li><li id="ul0002-0005" num="0023">detection that a third party is looking at a screen of the computing device by using biometric identification, such as looking at the computing device so as to allow the camera to capture an image of a face for performing facial recognition, or an image of a retina for performing a retina scan, or placing a finger on a sensor in order to capture a fingerprint;</li><li id="ul0002-0006" num="0024">disconnection of the computing device from a communications network designated as being familiar, e.g., a wifi network designated as one's home network;</li><li id="ul0002-0007" num="0025">detection that the computing device has been removed from being within proximity of a designated familiar device, e.g., a smartphone detecting that it has been moved from being next to one's spouse's phone or one's laptop;</li><li id="ul0002-0008" num="0026">receipt of a personal communication while the computing device is not within the user's control, e.g., the user is not holding the device and/or is not looking at the screen;</li><li id="ul0002-0009" num="0027">detection that the computing device has been removed from being in a designated familiar location, e.g., the user's home (which may be detected by, for example, GPS or cell tower triangulation), or on a desk with an embedded RFID tag; or</li><li id="ul0002-0010" num="0028">detection of an unauthorized attempt to download information to the computing device or retrieve information from the computing device, such as, for example, by way of a networking connection such as an infrared or other near-field communication (NFC)-type technology capable of pulling information from and/or pushing information to the computing device.</li></ul></li></ul>
0029An unlock-triggering event may comprise any of a number of different events, such as, by way of example and not limitation: <ul id="ul0003" list-style="none"><li id="ul0003-0001" num="0000"><ul id="ul0004" list-style="none"><li id="ul0004-0001" num="0030">opening a lid of the computing device;</li><li id="ul0004-0002" num="0031">removing the computing device from an enclosure;</li><li id="ul0004-0003" num="0032">detection based on biometric identification that the user is looking at a screen of the computing device;</li><li id="ul0004-0004" num="0033">detection, by one or more touch sensors, that the user is handling the computing device;</li><li id="ul0004-0005" num="0034">connection of the computing device to a communications network designated as being familiar;</li><li id="ul0004-0006" num="0035">detection that the computing device has been placed within proximity of a designated familiar device; or</li><li id="ul0004-0007" num="0036">detection that the computing device has been placed in a designated familiar location.</li></ul></li></ul>
0037In step <b>220</b>, the computing device may determine whether the user action was taken by the user of the computing device, or by another person. This determination may be based on biometric identification. If the user action was taken by another person, the computing device may determine whether the person is another user associated with the computing device, an identifiable person associated with the user, or a stranger who is not known to the user and/or not identifiable. In particular embodiments, the computing device may determine that a third party is unauthorized if the third party is not on a list of users authorized to use the computing device or if the third party is on a blacklist of users who are blocked from using the computing device.
0038In particular embodiments, the computing device may also attempt to determine the identity of the third party based on the facial recognition data. In particular embodiments, the computing device may store facial recognition data for previous users of the computing device in association with requested identifying information; for example, if a family member of the user has previously used the computing device, the computing device may have obtained a unique identifier, such as, for example, an email address or username, and stored the unique identifier in association with that person's facial recognition data for the purpose of recognizing that user in the future. In particular embodiments, the computing device may also attempt to determine a unique identifier for the person by accessing information in a database that may be able to provide identifying information for a person based on facial recognition data. In particular embodiments, the computing device may utilize such identifying information for the person to determine whether the person is connected to the user with respect to a social-networking system.
0039In particular embodiments, once the computing device has identified the unknown person, the computing device may attempt to retrieve further information associated with the now-identified third party to help determine whether to lock all access to the computing device, or whether it may be ok to leave some or all functions of the computing device unlocked. For example, if the computing device identifies the third party as being the spouse of the user, a trusted colleague of the user, or another registered user of the computing device, the computing device may not lock any of its functions, or it may lock access to only some sensitive information or personal applications, or, in the case of the other registered user of the computing device, it may simply place the user's computing state on standby and provide a login interface for the other registered user to log in and use the device. In particular embodiments, if the third party is identified as a social-networking connection of the user (“a friend”), the computing device may employ functionality to access a social graph associated with the social-networking system to determine how closely connected the friend is to the user. For example, the computing device may not lock all or any of its functions if it can be determined that the third party is a close friend (e.g., connected by one degree of separation with respect to the social graph). In particular embodiments, the user may be able to set preferences with respect to their social graph connections to assign different levels of locking the user's computing device. Such preferences may be based on any social-networking information available, e.g., threshold degree of separation, group affiliation, family/household indicators, etc.
0040In step <b>230</b>, particular embodiments of the computing device may assess a state of the device in order to help determine whether and/or how to update the lock status of the device. For example, and not by way of limitation, assessing the state of the device may include: <ul id="ul0005" list-style="none"><li id="ul0005-0001" num="0000"><ul id="ul0006" list-style="none"><li id="ul0006-0001" num="0041">determining the current lock status of the computing device—e.g., is the device currently locked, partially locked, or unlocked?</li><li id="ul0006-0002" num="0042">determining a location of the computing device—e.g., according to GPS information, is the device currently at a location that corresponds to the user's home or office?</li><li id="ul0006-0003" num="0043">determining a communications environment of the computing device—e.g., is the device currently connected to a wifi network associated with the user's home or office?</li><li id="ul0006-0004" num="0044">determining what other devices are in physical proximity to the computing device—e.g., is the device able to sense that the user's spouse's phone is near by?</li><li id="ul0006-0005" num="0045">determining whether a screen of the computing device is visible—e.g., would another person be able to see what is being displayed on the screen?</li><li id="ul0006-0006" num="0046">determining what is being displayed on the screen—e.g., is there personal information being displayed on the screen? Or publicly-accessible content?</li><li id="ul0006-0007" num="0047">determining a length of time that the computing device has been idle—e.g., has the device been untouched for the last three hours (such as, for example, may be the case if someone were watching a movie on it, but should be less likely if someone were in the middle of editing a document)?</li><li id="ul0006-0008" num="0048">determining a length of time since the computing device was last used by the user—e.g., has it been an unusually long period of time since the user last accessed the device?</li></ul></li></ul>
0049In step <b>240</b>, particular embodiments of the computing device may access further information related to the user associated with the computing device in order to help determine whether and/or how to update the lock status of the device. Additional information may include, by way of example and not limitation: <ul id="ul0007" list-style="none"><li id="ul0007-0001" num="0000"><ul id="ul0008" list-style="none"><li id="ul0008-0001" num="0050">calendar information for the user—e.g., in order to determine whether, on a particular day and at a particular time, the user is expected to be at home or at the office or somewhere else;</li><li id="ul0008-0002" num="0051">profile information of the user—e.g., in order to determine the user's home address and work address;</li><li id="ul0008-0003" num="0052">configuration settings of the computing device—e.g., in order to determine what networks, devices, and locations are designated as familiar;</li><li id="ul0008-0004" num="0053">a usage history associated with the computing device—e.g., in order to determine at what times the user typically uses the device.</li></ul></li></ul>
0054In step <b>250</b>, particular embodiments of the computing device may monitor further activity on the device by the detected third party in order to help determine whether and/or how to update the lock status of the device. In particular embodiments, once the computing device has identified that a third party is looking at the device, the computing device may monitor activity on the device while the third party is looking at the device, until the computing device detects that the user of the device has returned and has taken control of the device, in order to determine whether the third party is attempting to access any information or functions on the device. In particular scenarios, such as, for example, if the user was watching a video and paused the video while taking a restroom break, the computing device may determine that it is ok for the third party to view the screen but not for the third party to attempt to use the device to access any functions on the device—if this were to occur as the computing device is monitoring activity on the device, the computing device may then update its lock status to lock its access interfaces. In this case, when determining whether to lock all access to the computing device, or whether it may be ok to leave some or all functions of the computing device unlocked, the computing device may also consider what sort of activity was attempted by the third party.
0055In step <b>260</b>, particular embodiments of the computing device update the lock status of the device to lock or unlock one or more access interfaces of the device, lock or unlock one or more functions of the device, or block or allow access to particular content or all content accessible from the computing device. Updating the lock status may also include logging the event in association with the lock status and a timestamp. In particular embodiments, access may only be partially locked or blocked, so as enable partial access to less sensitive applications or features such as, for example, adjusting volume, viewing publicly-accessible content, or playing children's games.
0056In particular embodiments, the computing device may determine that the event indicates a security issue related to unauthorized attempted use of the computing device by a third-party—in such a scenario, the computing device may either generate a notification about the event to the user, to be displayed on the device and/or sent to the user (e.g., via email or text message). The computing device may also activate an alarm on the device.
0057<figref idref="DRAWINGS">FIG. 3</figref> is a block diagram of an example computing device <b>300</b>. In particular embodiments, one or more computer systems <b>300</b> perform one or more steps of one or more methods described or illustrated herein. In particular embodiments, one or more computer systems <b>300</b> provide functionality described or illustrated herein. In particular embodiments, software running on one or more computer systems <b>300</b> performs one or more steps of one or more methods described or illustrated herein or provides functionality described or illustrated herein. Particular embodiments include one or more portions of one or more computer systems <b>300</b>. Herein, reference to a computer system may encompass a computing device, where appropriate. Moreover, reference to a computer system may encompass one or more computer systems, where appropriate.
0058This disclosure contemplates any suitable number of computer systems <b>300</b>. This disclosure contemplates computer system <b>300</b> taking any suitable physical form. As example and not by way of limitation, computer system <b>300</b> may be an embedded computer system, a system-on-chip (SOC), a single-board computer system (SBC) (such as, for example, a computer-on-module (COM) or system-on-module (SOM)), a desktop computer system, a laptop or notebook computer system, an interactive kiosk, a mainframe, a mesh of computer systems, a mobile telephone, a personal digital assistant (PDA), a server, a tablet computer system, another mobile computing device, or a combination of two or more of these. Where appropriate, computer system <b>300</b> may include one or more computer systems <b>300</b>; be unitary or distributed; span multiple locations; span multiple machines; span multiple data centers; or reside in a cloud, which may include one or more cloud components in one or more networks. Where appropriate, one or more computer systems <b>300</b> may perform without substantial spatial or temporal limitation one or more steps of one or more methods described or illustrated herein. As an example and not by way of limitation, one or more computer systems <b>300</b> may perform in real time or in batch mode one or more steps of one or more methods described or illustrated herein. One or more computer systems <b>300</b> may perform at different times or at different locations one or more steps of one or more methods described or illustrated herein, where appropriate.
0059In particular embodiments, computer system <b>300</b> includes a processor <b>302</b>, memory <b>304</b>, storage <b>306</b>, an input/output (I/O) interface <b>308</b>, a communication interface <b>310</b>, and a bus <b>312</b>. Although this disclosure describes and illustrates a particular computer system having a particular number of particular components in a particular arrangement, this disclosure contemplates any suitable computer system having any suitable number of any suitable components in any suitable arrangement.
0060In particular embodiments, processor <b>302</b> includes hardware for executing instructions, such as those making up a computer program. As an example and not by way of limitation, to execute instructions, processor <b>302</b> may retrieve (or fetch) the instructions from an internal register, an internal cache, memory <b>304</b>, or storage <b>306</b>; decode and execute them; and then write one or more results to an internal register, an internal cache, memory <b>304</b>, or storage <b>306</b>. In particular embodiments, processor <b>302</b> may include one or more internal caches for data, instructions, or addresses. This disclosure contemplates processor <b>302</b> including any suitable number of any suitable internal caches, where appropriate. As an example and not by way of limitation, processor <b>302</b> may include one or more instruction caches, one or more data caches, and one or more translation lookaside buffers (TLBs). Instructions in the instruction caches may be copies of instructions in memory <b>304</b> or storage <b>306</b>, and the instruction caches may speed up retrieval of those instructions by processor <b>302</b>. Data in the data caches may be copies of data in memory <b>304</b> or storage <b>306</b> for instructions executing at processor <b>302</b> to operate on; the results of previous instructions executed at processor <b>302</b> for access by subsequent instructions executing at processor <b>302</b> or for writing to memory <b>304</b> or storage <b>306</b>; or other suitable data. The data caches may speed up read or write operations by processor <b>302</b>. The TLBs may speed up virtual-address translation for processor <b>302</b>. In particular embodiments, processor <b>302</b> may include one or more internal registers for data, instructions, or addresses. This disclosure contemplates processor <b>302</b> including any suitable number of any suitable internal registers, where appropriate. Where appropriate, processor <b>302</b> may include one or more arithmetic logic units (ALUs); be a multi-core processor; or include one or more processors <b>302</b>. Although this disclosure describes and illustrates a particular processor, this disclosure contemplates any suitable processor.
0061In particular embodiments, memory <b>304</b> includes main memory for storing instructions for processor <b>302</b> to execute or data for processor <b>302</b> to operate on. As an example and not by way of limitation, computer system <b>300</b> may load instructions from storage <b>306</b> or another source (such as, for example, another computer system <b>300</b>) to memory <b>304</b>. Processor <b>302</b> may then load the instructions from memory <b>304</b> to an internal register or internal cache. To execute the instructions, processor <b>302</b> may retrieve the instructions from the internal register or internal cache and decode them. During or after execution of the instructions, processor <b>302</b> may write one or more results (which may be intermediate or final results) to the internal register or internal cache. Processor <b>302</b> may then write one or more of those results to memory <b>304</b>. In particular embodiments, processor <b>302</b> executes only instructions in one or more internal registers or internal caches or in memory <b>304</b> (as opposed to storage <b>306</b> or elsewhere) and operates only on data in one or more internal registers or internal caches or in memory <b>304</b> (as opposed to storage <b>306</b> or elsewhere). One or more memory buses (which may each include an address bus and a data bus) may couple processor <b>302</b> to memory <b>304</b>. Bus <b>312</b> may include one or more memory buses, as described below. In particular embodiments, one or more memory management units (MMUs) reside between processor <b>302</b> and memory <b>304</b> and facilitate accesses to memory <b>304</b> requested by processor <b>302</b>. In particular embodiments, memory <b>304</b> includes random access memory (RAM). This RAM may be volatile memory, where appropriate Where appropriate, this RAM may be dynamic RAM (DRAM) or static RAM (SRAM). Moreover, where appropriate, this RAM may be single-ported or multi-ported RAM. This disclosure contemplates any suitable RAM. Memory <b>304</b> may include one or more memories <b>304</b>, where appropriate. Although this disclosure describes and illustrates particular memory, this disclosure contemplates any suitable memory.
0062In particular embodiments, storage <b>306</b> includes mass storage for data or instructions. As an example and not by way of limitation, storage <b>306</b> may include a hard disk drive (HDD), a floppy disk drive, flash memory, an optical disc, a magneto-optical disc, magnetic tape, or a Universal Serial Bus (USB) drive or a combination of two or more of these. Storage <b>306</b> may include removable or non-removable (or fixed) media, where appropriate. Storage <b>306</b> may be internal or external to computer system <b>300</b>, where appropriate. In particular embodiments, storage <b>306</b> is non-volatile, solid-state memory. In particular embodiments, storage <b>306</b> includes read-only memory (ROM). Where appropriate, this ROM may be mask-programmed ROM, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), electrically alterable ROM (EAROM), or flash memory or a combination of two or more of these. This disclosure contemplates mass storage <b>306</b> taking any suitable physical form. Storage <b>306</b> may include one or more storage control units facilitating communication between processor <b>302</b> and storage <b>306</b>, where appropriate. Where appropriate, storage <b>306</b> may include one or more storages <b>306</b>. Although this disclosure describes and illustrates particular storage, this disclosure contemplates any suitable storage.
0063In particular embodiments, I/O interface <b>308</b> includes hardware, software, or both providing one or more access interfaces for communication between computer system <b>300</b> and one or more I/O devices. Computer system <b>300</b> may include one or more of these I/O devices, where appropriate. One or more of these I/O devices may enable communication between a person and computer system <b>300</b>. As an example and not by way of limitation, an I/O device may include a keyboard, keypad, microphone, monitor, mouse, printer, scanner, speaker, still camera, stylus, tablet, touch screen, trackball, video camera, another suitable I/O device or a combination of two or more of these. An I/O device may include one or more sensors. This disclosure contemplates any suitable I/O devices and any suitable I/O interfaces <b>308</b> for them. Where appropriate, I/O interface <b>308</b> may include one or more device or software drivers enabling processor <b>302</b> to drive one or more of these I/O devices. I/O interface <b>308</b> may include one or more I/O interfaces <b>308</b>, where appropriate. Although this disclosure describes and illustrates a particular I/O interface, this disclosure contemplates any suitable I/O interface.
0064In particular embodiments, I/O interface <b>308</b> may include various types of sensors, such as, for example and without limitation: touch sensors (disposed, for example, on a display of the computing device, the back of the computing device and/or one or more lateral edges of the computing device) for detecting a user touching the surface of the computing device (e.g., using one or more fingers); accelerometer for detecting whether the computing device <b>300</b> is moving and the speed of the movement; thermometer for measuring the temperature change near the computing device <b>300</b>; proximity sensor for detecting the proximity of the computing device <b>300</b> to another object (e.g., a hand, desk, or other object); light sensor for measuring the ambient light around the computing device <b>300</b>; imaging sensor (e.g., camera) for capturing digital still images and/or video of objects near the computing device <b>300</b> (e.g., scenes, people, bar codes, QR codes, etc.); location sensors (e.g., Global Positioning System (GPS)) for determining the location (e.g., in terms of latitude and longitude) of the computing device; sensors for detecting communication networks within close proximity (e.g., near field communication (NFC), Bluetooth, RFID, infrared); chemical sensors; biometric sensors for biometrics-based (e.g., fingerprint, palm vein pattern, hand geometry, iris/retina, DNA, face, voice, olfactory, sweat) authentication of user of computing device <b>300</b>; etc. This disclosure contemplates that a computing device may include any applicable type of sensor. Sensors may provide various types of sensor data, which may be analyzed to determine the user's intention with respect to the computing device at a given time.
0065In particular embodiments, determining a location of the computing device is based on GPS information, triangulation information, proximity to one or more other designated safe devices, calendar information, or any combination thereof.
0066In particular embodiments, in addition to the front side, computing device <b>300</b> may have one or more sensors for performing biometric identification. Such sensors may be positioned on any surface of computing device <b>300</b>. In example embodiments, as the user's hand touches computing device <b>300</b> to grab hold of it, the touch sensors may capture the user's fingerprints or palm vein pattern. In example embodiments, while a user is viewing the screen of computing device <b>300</b>, a camera may capture an image of the user's face to perform facial recognition. In example embodiments, while a user is viewing the screen of computing device <b>300</b>, an infrared scanner may scan the user's iris and/or retina. In example embodiments, while a user is in contact or close proximity with computing device <b>300</b>, chemical and/or olfactory sensors may capture relevant data about a user. In particular embodiments, upon detecting that there is a change in state with respect to the identity of the user utilizing computing device <b>300</b>, either by itself or in combination with other types of sensor indications, computing device <b>300</b> may determine that it is being shared.
0067In particular embodiments, in addition to the front side, the computing device <b>300</b> may have touch sensors on the left and right sides. Optionally, the computing device <b>300</b> may also have touch sensors on the back, top, or bottom side. Thus, as the user's hand touches computing device <b>300</b> to grab hold of it, the touch sensors may detect the user's fingers or palm touching computing device <b>300</b>. In particular embodiments, upon detecting that there is a change in state with respect to a user touching computing device <b>300</b>, either by itself or in combination with other types of sensor indications, computing device <b>300</b> may determine that it is being shared.
0068In particular embodiments, computing device <b>300</b> may have an accelerometer in addition to or instead of the touch sensors on the left and right sides. Sensor data provided by the accelerometer may also be used to estimate whether a new user has picked up computing device <b>300</b> from a resting position, e.g., on a table or desk, display shelf, or from someone's hand or from within someone's bag. When the user picks up computing device <b>300</b> and brings it in front of the user's face, there may be a relatively sudden increase in the movement speed of computing device <b>300</b>. This change in the computing device's movement speed may be detected based on the sensor data supplied by the accelerometer. In particular embodiments, upon detecting that there is a significant increase in the speed of the computing device's movement, either by itself or in combination with other types of sensor indications, computing device <b>300</b> may determine that it is being shared.
0069In particular embodiments, computing device <b>300</b> may have a Gyrometer in addition or instead of the touch sensors on the left and right sides. A Gyrometer, also known as a gyroscope, is a device for measuring the orientation along one or more axis. In particular embodiments, a Gyrometer may be used to measure the orientation of computing device <b>300</b>. When computing device <b>300</b> is stored on a shelf or in the user's bag, it may stay mostly in one orientation. However, when the user grabs hold of computing device <b>300</b> and lifts it up and/or moves it closer to bring it in front of the user's face, there may be a relatively sudden change in the orientation of computing device <b>300</b>. The orientation of computing device <b>300</b> may be detected and measured by the gyrometer. If the orientation of computing device <b>300</b> has changed significantly, In particular embodiments, upon detecting that there is a significant change in the orientation of computing device <b>300</b>, either by itself or in combination with other types of sensor indications, computing device <b>300</b> may determine that it is being shared.
0070In particular embodiments, computing device <b>300</b> may have a light sensor. When computing device <b>300</b> is stored in a receptacle, e.g., the user's pocket or bag, or in a case or holster, it is relatively dark around computing device <b>300</b>. On the other hand, when the user brings computing device <b>300</b> out of his pocket, it may be relatively bright around computing device <b>300</b>, especially during day time or in well-lit areas. The sensor data supplied by the light sensor may be analyzed to detect when a significant change in the ambient light level around computing device <b>300</b> occurs. In particular embodiments, upon detecting that there is a significant increase in the ambient light level around computing device <b>300</b>, either by itself or in combination with other types of sensor indications, computing device <b>300</b> may determine that it is being shared.
0071In particular embodiments, computing device <b>300</b> may have a proximity sensor. The sensor data supplied by the proximity sensor may be analyzed to detect when computing device <b>300</b> is in close proximity to a specific object, such as the user's hand. For example, computing device <b>300</b> may have an infrared LED (light-emitting diode) (i.e., proximity sensor) placed on its back side. When the user holds such a computing device in his hand, the palm of the user's hand may cover the infrared LED. As a result, the infrared LED may detect when the user's hand is in close proximity to computing device <b>300</b>. In particular embodiments, upon detecting that computing device <b>300</b> is in close proximity to the user's hand, either by itself or in combination with other types of sensor indications, computing device <b>300</b> may determine that it is being shared.
0072A computing device <b>300</b> may have any number of sensors of various types, and these sensors may supply different types of sensor data. Different combinations of the individual types of sensor data may be used together to detect and estimate a user's current intention with respect to computing device <b>300</b> (e.g., whether the user really means to take computing device <b>300</b> out of his pocket and use it). Sometimes, using multiple types of sensor data in combination may yield a more accurate, and thus better, estimation of the user's intention with respect to computing device <b>300</b> at a given time than only using a single type of sensor data. Nevertheless, it is possible to estimate the user's intention using a single type of sensor data (e.g., touch-sensor data).
0073In particular embodiments, communication interface <b>310</b> includes hardware, software, or both providing one or more interfaces for communication (such as, for example, packet-based communication) between computer system <b>300</b> and one or more other computer systems <b>300</b> or one or more networks. As an example and not by way of limitation, communication interface <b>310</b> may include a network interface controller (NIC) or network adapter for communicating with an Ethernet or other wire-based network or a wireless NIC (WNIC) or wireless adapter for communicating with a wireless network, such as a WI-FI network. This disclosure contemplates any suitable network and any suitable communication interface <b>310</b> for it. As an example and not by way of limitation, computer system <b>300</b> may communicate with an ad hoc network, a personal area network (PAN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), or one or more portions of the Internet or a combination of two or more of these. One or more portions of one or more of these networks may be wired or wireless. As an example, computer system <b>300</b> may communicate with a wireless PAN (WPAN) (such as, for example, a BLUETOOTH WPAN), a WI-FI network, a WI-MAX network, a cellular telephone network (such as, for example, a Global System for Mobile Communications (GSM) network), or other suitable wireless network or a combination of two or more of these. Computer system <b>300</b> may include any suitable communication interface <b>310</b> for any of these networks, where appropriate. Communication interface <b>310</b> may include one or more communication interfaces <b>310</b>, where appropriate. Although this disclosure describes and illustrates a particular communication interface, this disclosure contemplates any suitable communication interface.
0074In particular embodiments, bus <b>312</b> includes hardware, software, or both coupling components of computer system <b>300</b> to each other. As an example and not by way of limitation, bus <b>312</b> may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a front-side bus (FSB), a HYPERTRANSPORT (HT) interconnect, an Industry Standard Architecture (ISA) bus, an INFINIBAND interconnect, a low-pin-count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCIe) bus, a serial advanced technology attachment (SATA) bus, a Video Electronics Standards Association local (VLB) bus, or another suitable bus or a combination of two or more of these. Bus <b>312</b> may include one or more buses <b>312</b>, where appropriate. Although this disclosure describes and illustrates a particular bus, this disclosure contemplates any suitable bus or interconnect.
0075Herein, a computer-readable non-transitory storage medium or media may include one or more semiconductor-based or other integrated circuits (ICs) (such, as for example, field-programmable gate arrays (FPGAs) or application-specific ICs (ASICs)), hard disk drives (HDDs), hybrid hard drives (HHDs), optical discs, optical disc drives (ODDs), magneto-optical discs, magneto-optical drives, floppy diskettes, floppy disk drives (FDDs), magnetic tapes, solid-state drives (SSDs), RAM-drives, SECURE DIGITAL cards or drives, any other suitable computer-readable non-transitory storage media, or any suitable combination of two or more of these, where appropriate. A computer-readable non-transitory storage medium may be volatile, non-volatile, or a combination of volatile and non-volatile, where appropriate.
0076<figref idref="DRAWINGS">FIG. 4</figref> illustrates an example network environment <b>400</b>. Network environment <b>400</b> includes a user <b>410</b>, a client system <b>300</b>, a social-networking system <b>430</b>, and a third-party system <b>440</b> connected to each other by a network <b>450</b>. Although <figref idref="DRAWINGS">FIG. 4</figref> illustrates a particular arrangement of user <b>410</b>, client system <b>300</b>, social-networking system <b>430</b>, third-party system <b>440</b>, and network <b>450</b>, this disclosure contemplates any suitable arrangement of user <b>410</b>, client system <b>300</b>, social-networking system <b>430</b>, third-party system <b>440</b>, and network <b>450</b>. As an example and not by way of limitation, two or more of client system <b>300</b>, social-networking system <b>430</b>, and third-party system <b>440</b> may be connected to each other directly, bypassing network <b>450</b>. As another example, two or more of client system <b>300</b>, social-networking system <b>430</b>, and third-party system <b>440</b> may be physically or logically co-located with each other in whole or in part. Moreover, although <figref idref="DRAWINGS">FIG. 4</figref> illustrates a particular number of users <b>410</b>, client systems <b>300</b>, social-networking systems <b>430</b>, third-party systems <b>440</b>, and networks <b>450</b>, this disclosure contemplates any suitable number of users <b>410</b>, client systems <b>300</b>, social-networking systems <b>430</b>, third-party systems <b>440</b>, and networks <b>450</b>. As an example and not by way of limitation, network environment <b>400</b> may include multiple users <b>410</b>, client system <b>300</b>, social-networking systems <b>430</b>, third-party systems <b>440</b>, and networks <b>450</b>.
0077In particular embodiments, user <b>410</b> may be an individual (human user), an entity (e.g., an enterprise, business, or third-party application), or a group (e.g., of individuals or entities) that interacts or communicates with or over social-networking system <b>430</b>. In particular embodiments, social-networking system <b>430</b> may be a network-addressable computing system hosting an online social network. Social-networking system <b>430</b> may generate, store, receive, and transmit social-networking data, such as, for example, user-profile data, concept-profile data, social-graph information, or other suitable data related to the online social network. Social-networking system <b>430</b> may be accessed by the other components of network environment <b>400</b> either directly or via network <b>450</b>. In particular embodiments, social-networking system <b>430</b> may include an authorization server that allows users <b>410</b> to opt in or opt out of having their actions logged by social-networking system <b>430</b> or shared with other systems (e.g., third-party systems <b>440</b>), such as, for example, by setting appropriate privacy settings. In particular embodiments, third-party system <b>440</b> may be a network-addressable computing system that can host third-party content objects and serve content, and/or provide a third-party advertisement serving engine. Third-party system <b>440</b> may generate, store, receive, and transmit third-party content and/or sponsored content, such as, for example, advertisements, incentive program notifications, coupons, etc. Third-party system <b>440</b> may be accessed by the other components of network environment <b>400</b> either directly or via network <b>450</b>. In particular embodiments, one or more users <b>410</b> may use one or more client systems <b>300</b> to access, send data to, and receive data from social-networking system <b>430</b> or third-party system <b>440</b>. Client system <b>300</b> may access social-networking system <b>430</b> or third-party system <b>440</b> directly, via network <b>450</b>, or via a third-party system. As an example and not by way of limitation, client system <b>300</b> may access third-party system <b>440</b> via social-networking system <b>430</b>. Client system <b>300</b> may be any suitable computing device, such as, for example, a personal computer, a laptop computer, a cellular telephone, a smartphone, or a tablet computer.
0078This disclosure contemplates any suitable network <b>450</b>. As an example and not by way of limitation, one or more portions of network <b>450</b> may include an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a cellular telephone network, or a combination of two or more of these. Network <b>450</b> may include one or more networks <b>450</b>.
0079Links <b>460</b> may connect client system <b>300</b>, social-networking system <b>430</b>, and third-party system <b>440</b> to communication network <b>450</b> or to each other. This disclosure contemplates any suitable links <b>460</b>. In particular embodiments, one or more links <b>460</b> include one or more wireline (such as for example Digital Subscriber Line (DSL) or Data Over Cable Service Interface Specification (DOCSIS)), wireless (such as for example Wi-Fi or Worldwide Interoperability for Microwave Access (WiMAX)), or optical (such as for example Synchronous Optical Network (SONET) or Synchronous Digital Hierarchy (SDH)) links. In particular embodiments, one or more links <b>460</b> each include an ad hoc network, an intranet, an extranet, a VPN, a LAN, a WLAN, a WAN, a WWAN, a MAN, a portion of the Internet, a portion of the PSTN, a cellular technology-based network, a satellite communications technology-based network, another link <b>460</b>, or a combination of two or more such links <b>460</b>. Links <b>460</b> need not necessarily be the same throughout network environment <b>400</b>. One or more first links <b>460</b> may differ in one or more respects from one or more second links <b>460</b>.
0080<figref idref="DRAWINGS">FIG. 5</figref> illustrates example social graph <b>500</b>. In particular embodiments, social-networking system <b>460</b> may store one or more social graphs <b>500</b> in one or more data stores. In particular embodiments, social graph <b>500</b> may include multiple nodes—which may include multiple user nodes <b>502</b> or multiple concept nodes <b>504</b>—and multiple edges <b>506</b> connecting the nodes. Example social graph <b>500</b> illustrated in <figref idref="DRAWINGS">FIG. 5</figref> is shown, for didactic purposes, in a two-dimensional visual map representation. In particular embodiments, a social-networking system <b>460</b>, client system <b>430</b>, or third-party system <b>470</b> may access social graph <b>500</b> and related social-graph information for suitable applications. The nodes and edges of social graph <b>500</b> may be stored as data objects, for example, in a data store (such as a social-graph database). Such a data store may include one or more searchable or queryable indexes of nodes or edges of social graph <b>500</b>.
0081In particular embodiments, a user node <b>502</b> may correspond to a user of social-networking system <b>460</b>. As an example and not by way of limitation, a user may be an individual (human user), an entity (e.g., an enterprise, business, or third-party application), or a group (e.g., of individuals or entities) that interacts or communicates with or over social-networking system <b>460</b>. In particular embodiments, when a user registers for an account with social-networking system <b>460</b>, social-networking system <b>460</b> may create a user node <b>502</b> corresponding to the user, and store the user node <b>502</b> in one or more data stores. Users and user nodes <b>502</b> described herein may, where appropriate, refer to registered users and user nodes <b>502</b> associated with registered users. In addition or as an alternative, users and user nodes <b>502</b> described herein may, where appropriate, refer to users that have not registered with social-networking system <b>460</b>. In particular embodiments, a user node <b>502</b> may be associated with information provided by a user or information gathered by various systems, including social-networking system <b>460</b>. As an example and not by way of limitation, a user may provide his or her name, profile picture, contact information, birth date, sex, marital status, family status, employment, education background, preferences, interests, or other demographic information. In particular embodiments, a user node <b>502</b> may be associated with one or more data objects corresponding to information associated with a user. In particular embodiments, a user node <b>502</b> may correspond to one or more webpages.
0082In particular embodiments, a concept node <b>504</b> may correspond to a concept. As an example and not by way of limitation, a concept may correspond to a place (such as, for example, a movie theater, restaurant, landmark, or city); a website (such as, for example, a website associated with social-network system <b>460</b> or a third-party website associated with a web-application server); an entity (such as, for example, a person, business, group, sports team, or celebrity); a resource (such as, for example, an audio file, video file, digital photo, text file, structured document, or application) which may be located within social-networking system <b>460</b> or on an external server, such as a web-application server; real or intellectual property (such as, for example, a sculpture, painting, movie, game, song, idea, photograph, or written work); a game; an activity; an idea or theory; another suitable concept; or two or more such concepts. A concept node <b>504</b> may be associated with information of a concept provided by a user or information gathered by various systems, including social-networking system <b>460</b>. As an example and not by way of limitation, information of a concept may include a name or a title; one or more images (e.g., an image of the cover page of a book); a location (e.g., an address or a geographical location); a website (which may be associated with a URL); contact information (e.g., a phone number or an email address); other suitable concept information; or any suitable combination of such information. In particular embodiments, a concept node <b>504</b> may be associated with one or more data objects corresponding to information associated with concept node <b>504</b>. In particular embodiments, a concept node <b>504</b> may correspond to one or more webpages.
0083In particular embodiments, a node in social graph <b>500</b> may represent or be represented by a webpage (which may be referred to as a “profile page”). Profile pages may be hosted by or accessible to social-networking system <b>460</b>. Profile pages may also be hosted on third-party websites associated with a third-party server <b>470</b>. As an example and not by way of limitation, a profile page corresponding to a particular external webpage may be the particular external webpage and the profile page may correspond to a particular concept node <b>504</b>. Profile pages may be viewable by all or a selected subset of other users. As an example and not by way of limitation, a user node <b>502</b> may have a corresponding user-profile page in which the corresponding user may add content, make declarations, or otherwise express himself or herself. As another example and not by way of limitation, a concept node <b>504</b> may have a corresponding concept-profile page in which one or more users may add content, make declarations, or express themselves, particularly in relation to the concept corresponding to concept node <b>504</b>.
0084In particular embodiments, a concept node <b>504</b> may represent a third-party webpage or resource hosted by a third-party system <b>470</b>. The third-party webpage or resource may include, among other elements, content, a selectable or other icon, or other inter-actable object (which may be implemented, for example, in JavaScript, AJAX, or PHP codes) representing an action or activity. As an example and not by way of limitation, a third-party webpage may include a selectable icon such as “like,” “check in,” “eat,” “recommend,” or another suitable action or activity. A user viewing the third-party webpage may perform an action by selecting one of the icons (e.g., “eat”), causing a client system <b>430</b> to send to social-networking system <b>460</b> a message indicating the user's action. In response to the message, social-networking system <b>460</b> may create an edge (e.g., an “eat” edge) between a user node <b>502</b> corresponding to the user and a concept node <b>504</b> corresponding to the third-party webpage or resource and store edge <b>506</b> in one or more data stores.
0085In particular embodiments, a pair of nodes in social graph <b>500</b> may be connected to each other by one or more edges <b>506</b>. An edge <b>506</b> connecting a pair of nodes may represent a relationship between the pair of nodes. In particular embodiments, an edge <b>506</b> may include or represent one or more data objects or attributes corresponding to the relationship between a pair of nodes. As an example and not by way of limitation, a first user may indicate that a second user is a “friend” of the first user. In response to this indication, social-networking system <b>460</b> may send a “friend request” to the second user. If the second user confirms the “friend request,” social-networking system <b>460</b> may create an edge <b>506</b> connecting the first user's user node <b>502</b> to the second user's user node <b>502</b> in social graph <b>500</b> and store edge <b>506</b> as social-graph information in one or more of data stores <b>24</b>. In the example of <figref idref="DRAWINGS">FIG. 5</figref>, social graph <b>500</b> includes an edge <b>506</b> indicating a friend relation between user nodes <b>502</b> of user “A” and user “B” and an edge indicating a friend relation between user nodes <b>502</b> of user “C” and user “B.” Although this disclosure describes or illustrates particular edges <b>506</b> with particular attributes connecting particular user nodes <b>502</b>, this disclosure contemplates any suitable edges <b>506</b> with any suitable attributes connecting user nodes <b>502</b>. As an example and not by way of limitation, an edge <b>506</b> may represent a friendship, family relationship, business or employment relationship, fan relationship, follower relationship, visitor relationship, subscriber relationship, superior/subordinate relationship, reciprocal relationship, non-reciprocal relationship, another suitable type of relationship, or two or more such relationships. Moreover, although this disclosure generally describes nodes as being connected, this disclosure also describes users or concepts as being connected. Herein, references to users or concepts being connected may, where appropriate, refer to the nodes corresponding to those users or concepts being connected in social graph <b>500</b> by one or more edges <b>506</b>.
0086In particular embodiments, an edge <b>506</b> between a user node <b>502</b> and a concept node <b>504</b> may represent a particular action or activity performed by a user associated with user node <b>502</b> toward a concept associated with a concept node <b>504</b>. As an example and not by way of limitation, as illustrated in <figref idref="DRAWINGS">FIG. 5</figref>, a user may “like,” “attended,” “played,” “listened,” “cooked,” “worked at,” or “watched” a concept, each of which may correspond to a edge type or subtype. A concept-profile page corresponding to a concept node <b>504</b> may include, for example, a selectable “check in” icon (such as, for example, a clickable “check in” icon) or a selectable “add to favorites” icon. Similarly, after a user clicks these icons, social-networking system <b>460</b> may create a “favorite” edge or a “check in” edge in response to a user's action corresponding to a respective action. As another example and not by way of limitation, a user (user “C”) may listen to a particular song (“Ramble On”) using a particular application (SPOTIFY, which is an online music application). In this case, social-networking system <b>460</b> may create a “listened” edge <b>506</b> and a “used” edge (as illustrated in <figref idref="DRAWINGS">FIG. 5</figref>) between user nodes <b>502</b> corresponding to the user and concept nodes <b>504</b> corresponding to the song and application to indicate that the user listened to the song and used the application. Moreover, social-networking system <b>460</b> may create a “played” edge <b>506</b> (as illustrated in <figref idref="DRAWINGS">FIG. 5</figref>) between concept nodes <b>504</b> corresponding to the song and the application to indicate that the particular song was played by the particular application. In this case, “played” edge <b>506</b> corresponds to an action performed by an external application (SPOTIFY) on an external audio file (the song “Imagine”). Although this disclosure describes particular edges <b>506</b> with particular attributes connecting user nodes <b>502</b> and concept nodes <b>504</b>, this disclosure contemplates any suitable edges <b>506</b> with any suitable attributes connecting user nodes <b>502</b> and concept nodes <b>504</b>. Moreover, although this disclosure describes edges between a user node <b>502</b> and a concept node <b>504</b> representing a single relationship, this disclosure contemplates edges between a user node <b>502</b> and a concept node <b>504</b> representing one or more relationships. As an example and not by way of limitation, an edge <b>506</b> may represent both that a user likes and has used at a particular concept. Alternatively, another edge <b>506</b> may represent each type of relationship (or multiples of a single relationship) between a user node <b>502</b> and a concept node <b>504</b> (as illustrated in <figref idref="DRAWINGS">FIG. 5</figref> between user node <b>502</b> for user “E” and concept node <b>504</b> for “SPOTIFY”).
0087In particular embodiments, social-networking system <b>460</b> may create an edge <b>506</b> between a user node <b>502</b> and a concept node <b>504</b> in social graph <b>500</b>. As an example and not by way of limitation, a user viewing a concept-profile page (such as, for example, by using a web browser or a special-purpose application hosted by the user's client system <b>430</b>) may indicate that he or she likes the concept represented by the concept node <b>504</b> by clicking or selecting a “Like” icon, which may cause the user's client system <b>430</b> to send to social-networking system <b>460</b> a message indicating the user's liking of the concept associated with the concept-profile page. In response to the message, social-networking system <b>460</b> may create an edge <b>506</b> between user node <b>502</b> associated with the user and concept node <b>504</b>, as illustrated by “like” edge <b>506</b> between the user and concept node <b>504</b>. In particular embodiments, social-networking system <b>460</b> may store an edge <b>506</b> in one or more data stores. In particular embodiments, an edge <b>506</b> may be automatically formed by social-networking system <b>460</b> in response to a particular user action. As an example and not by way of limitation, if a first user uploads a picture, watches a movie, or listens to a song, an edge <b>506</b> may be formed between user node <b>502</b> corresponding to the first user and concept nodes <b>504</b> corresponding to those concepts. Although this disclosure describes forming particular edges <b>506</b> in particular manners, this disclosure contemplates forming any suitable edges <b>506</b> in any suitable manner.
0088Herein, “or” is inclusive and not exclusive, unless expressly indicated otherwise or indicated otherwise by context. Therefore, herein, “A or B” means “A, B, or both,” unless expressly indicated otherwise or indicated otherwise by context. Moreover, “and” is both joint and several, unless expressly indicated otherwise or indicated otherwise by context. Therefore, herein, “A and B” means “A and B, jointly or severally,” unless expressly indicated otherwise or indicated otherwise by context.
0089The scope of this disclosure encompasses all changes, substitutions, variations, alterations, and modifications to the example embodiments described or illustrated herein that a person having ordinary skill in the art would comprehend. The scope of this disclosure is not limited to the example embodiments described or illustrated herein. Moreover, although this disclosure describes and illustrates respective embodiments herein as including particular components, elements, functions, operations, or steps, any of these embodiments may include any combination or permutation of any of the components, elements, functions, operations, or steps described or illustrated anywhere herein that a person having ordinary skill in the art would comprehend. Furthermore, reference in the appended claims to an apparatus or system or a component of an apparatus or system being adapted to, arranged to, capable of, configured to, enabled to, operable to, or operative to perform a particular function encompasses that apparatus, system, component, whether or not it or that particular function is activated, turned on, or unlocked, as long as that apparatus, system, or component is so adapted, arranged, capable, configured, enabled, operable, or operative.
Contents5
7 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US11710123B2 | Cited by | United States of America | Search report |
| US10567565B2 | Cited by | United States of America | Applicant |
| US9225677B2 | Cited by | United States of America | Search report |
| US10051567B2 | Cited by | United States of America | Applicant |
| US11470193B2 | Cited by | United States of America | Applicant |
| US10503885B2 | Cited by | United States of America | Search report |
| US11706329B2 | Cited by | United States of America | Applicant |
| US10433246B2 | Cited by | United States of America | Applicant |
| US10834246B2 | Cited by | United States of America | Applicant |
| US9419971B2 | Cited by | United States of America | Search report |
| US2024225225A9 | Cited by | United States of America | Search report |
| US9734787B2 | Cited by | United States of America | Search report |
| US9531709B2 | Cited by | United States of America | Applicant |
| US11003752B2 | Cited by | United States of America | Applicant |
| US11563739B2 | Cited by | United States of America | Applicant |
| US2014282084A1 | Cited by | United States of America | Pre-grant |
| US11120446B2 | Cited by | United States of America | Search report |
| US2024330925A1 | Cited by | United States of America | Search report |
| US2017344735A1 | Cited by | United States of America | Search report |
| US12321934B2 | Cited by | United States of America | Search report |
| US10019710B2 | Cited by | United States of America | Applicant |
| US2021406885A1 | Cited by | United States of America | Search report |
| US9736265B2 | Cited by | United States of America | Applicant |
| US10412080B1 | Cited by | United States of America | Search report |
| US10217103B2 | Cited by | United States of America | Applicant |
| US2021406884A1 | Cited by | United States of America | Search report |
| US10425892B2 | Cited by | United States of America | Applicant |
| US10338773B2 | Cited by | United States of America | Search report |
| US12132726B2 | Cited by | United States of America | Applicant |
| US10873576B2 | Cited by | United States of America | Applicant |
| US11695862B2 | Cited by | United States of America | Applicant |
| US2016188023A1 | Cited by | United States of America | Pre-grant |
| US10909535B2 | Cited by | United States of America | Applicant |
| US11461778B2 | Cited by | United States of America | Applicant |
| US10922676B2 | Cited by | United States of America | Applicant |
| US10924600B2 | Cited by | United States of America | Applicant |
| US12008565B2 | Cited by | United States of America | Search report |
| US11979514B2 | Cited by | United States of America | Applicant |
| US12002032B2 | Cited by | United States of America | Applicant |
| US12316799B2 | Cited by | United States of America | Applicant |
| US2002045457A1 | Cites | United States of America | Applicant |
| US2003139192A1 | Cites | United States of America | Applicant |
| KR20050013764A | Cites | Republic of Korea | Applicant |
| KR20050032816A | Cites | Republic of Korea | Applicant |
| US2005046580A1 | Cites | United States of America | Search report |
| US2005107114A1 | Cites | United States of America | Applicant |
| US2006090085A1 | Cites | United States of America | Search report |
| US2006288234A1 | Cites | United States of America | Search report |
| US2008120716A1 | Cites | United States of America | Search report |
| US2008255993A1 | Cites | United States of America | Applicant |
| US2010015976A1 | Cites | United States of America | Search report |
| US2010099394A1 | Cites | United States of America | Applicant |
| US2010144315A1 | Cites | United States of America | Search report |
| US2010323664A1 | Cites | United States of America | Applicant |
| KR20110041110A | Cites | Republic of Korea | Applicant |
| KR20110043012A | Cites | Republic of Korea | Applicant |
| KR20110043492A | Cites | Republic of Korea | Applicant |
| KR20110055137A | Cites | Republic of Korea | Applicant |
| US2011081889A1 | Cites | United States of America | Search report |
| US2011088086A1 | Cites | United States of America | Applicant |
| US2011105096A1 | Cites | United States of America | Search report |
| WO2012088974A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| US2012235790A1 | Cites | United States of America | Applicant |
| US2012262271A1 | Cites | United States of America | Applicant |
| US2013063611A1 | Cites | United States of America | Applicant |
| EP2364004A1 | Cites | European Patent Office (EPO) | Applicant |
| US20020045457A1 | Cites | United States of America | Applicant |
| US20030139192A1 | Cites | United States of America | Applicant |
| US20050046580A1 | Cites | United States of America | Search report |
| US20050107114A1 | Cites | United States of America | Applicant |
| US20060090085A1 | Cites | United States of America | Search report |
| US20060288234A1 | Cites | United States of America | Search report |
| US20080120716A1 | Cites | United States of America | Search report |
| US20080255993A1 | Cites | United States of America | Applicant |
| US20100015976A1 | Cites | United States of America | Search report |
| US20100099394A1 | Cites | United States of America | Applicant |
| US20100144315A1 | Cites | United States of America | Search report |
| US20100323664A1 | Cites | United States of America | Applicant |
| US20110081889A1 | Cites | United States of America | Search report |
| US20110088086A1 | Cites | United States of America | Applicant |
| US20110105096A1 | Cites | United States of America | Search report |
| US20120235790A1 | Cites | United States of America | Applicant |
| US20120262271A1 | Cites | United States of America | Applicant |
| US20130063611A1 | Cites | United States of America | Applicant |
| EP2364004 | Cites | European Patent Office (EPO) | Applicant |
| KR1020050013764A | Cites | Republic of Korea | Applicant |
| KR1020050032816A | Cites | Republic of Korea | Applicant |
| KR1020110041110 | Cites | Republic of Korea | Applicant |
| KR1020110043012 | Cites | Republic of Korea | Applicant |
| KR1020110043492 | Cites | Republic of Korea | Applicant |
| KR1020110055137 | Cites | Republic of Korea | Applicant |
| WO2012088974 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| U.S. Appl. No. 13/327,534, filed Dec. 15, 2011, Tseng. | Non-patent | – | Applicant |
| U.S. Appl. No. 13/571,160, filed Aug. 9, 2012, Matus. | Non-patent | – | Applicant |
| Non-Final Office Action for U.S. Appl. No. 13/327,534, May 7, 2013. | Non-patent | – | Applicant |
| International Search Report and Written Opinion for International Application PCT/US2012/069746, Apr. 5, 2013. | Non-patent | – | Applicant |
| European Patent Office Search Report for Application No. 13189504.7—1958, Feb. 5, 2014. | Non-patent | – | Applicant |
| International Search Report and Written Opinion for International Application PCT/US2013/066279, Feb. 7, 2014. | Non-patent | – | Applicant |
| U.S. Appl. No. 13/327,534, filed Dec. 15, 2011, Tseng. | Non-patent | – | Applicant |
| U.S. Appl. No. 13/571,160, filed Aug. 9, 2012, Matus. | Non-patent | – | Applicant |
43 members in 11 offices
Members43
| Document | Office | Kind | |
|---|---|---|---|
| EP2725532A1 | European Patent Office (EPO) | A1 | |
| CA2888089A1 | Canada | A1 | |
| CA2903795A1 | Canada | A1 | |
| CA2951782A1 | Canada | A1 | |
| CA3015104A1 | Canada | A1 | |
| US2014123273A1 | United States of America | A1 | |
| WO2014066451A1 | World Intellectual Property Organization (WIPO) | A1 | |
| US8914875B2This record | United States of America | B2 | |
| US2015067791A1 | United States of America | A1 | |
| AU2013334723A1 | Australia | A1 | |
| KR20150065906A | Republic of Korea | A | |
| IL238341A0 | Israel | A0 | |
| IL238341D0 | Israel | D0 | |
| CN104756122A | China | A | |
| AU2013334723B2 | Australia | B2 | |
| AU2015234292A1 | Australia | A1 | |
| MX2015005303A | Mexico | A | |
| MX2015005303A | Mexico | A | |
| CA2888089C | Canada | C | |
| JP5826983B1 | Japan | B1 | |
| US2015347730A1 | United States of America | A1 | |
| JP2016502176A | Japan | A | |
| KR101615610B1 | Republic of Korea | B1 | |
| KR20160058170A | Republic of Korea | A | |
| US9391994B2 | United States of America | B2 | |
| IL238341A | Israel | A | |
| CA2903795C | Canada | C | |
| AU2015234292B2 | Australia | B2 | |
| MX347013B | Mexico | B | |
| AU2017202637A1 | Australia | A1 | |
| BR112015009225A2 | Brazil | A2 | |
| AU2017202637B2 | Australia | B2 | |
| US9781119B2 | United States of America | B2 | |
| US2017366555A1 | United States of America | A1 | |
| CN104756122B | China | B | |
| US9973510B2 | United States of America | B2 | |
| KR20180067711A | Republic of Korea | A | |
| KR101867559B1 | Republic of Korea | B1 | |
| EP3361431A1 | European Patent Office (EPO) | A1 | |
| CA2951782C | Canada | C | |
| MX361476B | Mexico | B | |
| KR101951279B1 | Republic of Korea | B1 | |
| CA3015104C | Canada | C |
74 transactions on the USPTO file
Allowed after 1 non-final rejection and 1 final rejection.
- Non-final rejections
- 1
- Final rejections
- 1
- RCEs
- 0
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Maintenance Fee Reminder MailedREM. | REM. | |
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Payment of Maintenance Fee, 4th Year, Large EntityM1551 | M1551 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Response to Reasons for AllowanceREAS | REAS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Examiner's Amendment CommunicationEX.A | EX.A | |
| Interview Summary - Applicant Initiated - TelephonicEXAT | EXAT | |
| Interview Summary- Applicant InitiatedEXIA | EXIA | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| PILOT- Request for After Final Consideration ProgramRAFC | RAFC | |
| Response after Final ActionA.NE | A.NE | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Email NotificationEML_NTR | EML_NTR | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Mail Interview Summary - Applicant Initiated - TelephonicMEXAT | MEXAT | |
| Response after Non-Final ActionA... | A... | |
| Interview Summary- Applicant InitiatedEXIA | EXIA | |
| Interview Summary - Applicant Initiated - TelephonicEXAT | EXAT | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Application Is Now CompleteCOMP | COMP | |
| Email NotificationEML_NTR | EML_NTR | |
| Filing Receipt - UpdatedFLRCPT.U | FLRCPT.U | |
| Sent to Classification ContractorPGPC | PGPC | |
| A statement by one or more inventors satisfying the requirement under 35 USC 115, Oath of the ApplicOATHDECL | OATHDECL | |
| Additional Application Filing FeesADDFLFEE | ADDFLFEE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Email NotificationEML_NTR | EML_NTR | |
| Notice Mailed--Application Incomplete--Filing Date AssignedINCD | INCD | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
6 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Maintenance fee paymentMAFP | MAFP | |
| AssignmentAS | AS | |
| Maintenance fee paymentMAFP | MAFP | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication
- 8914875
- Application
- 13662187
Titles
- English
- Contextual device locking/unlocking
Patent term adjustment
- Applicant delay
- −63 days
- Net adjustment
- 0 days
Classification
- CPC, 14
- G06F21/30
- G06F21/31
- G06Q10/10
- G06F21/32
- G06F2221/032
- G06Q50/01
- G06F2221/2139
- H04M1/72454
- H04M1/66
- H04M1/72563
- H04L67/52
- G06Q10/48
- H04L63/101
- H04M1/72448
- IPC, 8
- G06F21 30
- G06F21 32
- G06Q10 10
- G06Q50 00
- H04M1 66
- H04M1 725
- H04M1 72448
- H04M1 72454