Rules engine for connected devices

In one embodiment, a method includes receiving notifications of events associated with the connected devices, evaluating a plurality of event sequences that include two or more events occurring within a particular time period, and generating a plurality of rules based on the evaluated event sequences. The method further includes receiving a notification of a first event associated with a first connected device on the network, determining that a first rule of the plurality of rules is based on the first event, and sending one or more instructions to connected devices in accordance with the first rule.

TECHNICAL FIELD

This disclosure generally relates to a network of objects embedded with electronics and software to enable objects to exchange data with a system.

BACKGROUND

A mobile 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, gyroscope, or accelerometer. 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 wireless local area networks (WLANs) or cellular-telephone network. Such a device may also include one or more cameras, scanners, touchscreens, microphones, or speakers. Mobile 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

In particular embodiments, a system receives event notifications for connected devices on a network. The events may be occurrences associated with the connected devices. The system evaluates event sequences that include two or more events occurring within a particular time period, and generates rules based on the evaluated sequences. The particular time period for the event sequences may be pre-determined or may be determined using historical data. In certain embodiments, the event sequences may be scored and rules may be generated for the event sequences based on the scores. In some embodiments, rules may only be generated for those event sequences having a score greater than a threshold. Once rules are generated, new event notifications are compared with the rules to determine whether a particular rule has been triggered based on the new event. If so, instructions are sent to connected devices in accordance with the triggered rule.

DESCRIPTION OF EXAMPLE EMBODIMENTS

FIG. 1illustrates an example network environment100associated with a social-networking system. Network environment100includes a client system130, a social-networking system160, and a third-party system170connected to each other by a network110. AlthoughFIG. 1illustrates a particular arrangement of client system130, social-networking system160, third-party system170, and network110, this disclosure contemplates any suitable arrangement of client system130, social-networking system160, third-party system170, and network110. As an example limitation, two or more of client system130, social-networking system160, and third-party system170may be connected to each other directly, bypassing network110. As another example, two or more of client system130, social-networking system160, and third-party system170may be physically or logically co-located with each other in whole or in part. Moreover, althoughFIG. 1illustrates a particular number of client systems130, social-networking systems160, third-party systems170, and networks110, this disclosure contemplates any suitable number of client systems130, social-networking systems160, third-party systems170, and networks110. As an example, network environment100may include multiple client system130, social-networking systems160, third-party systems170, and networks110.

In particular embodiments, client system130may be an electronic device including hardware, software, or embedded logic components or a combination of two or more such components and capable of carrying out the appropriate functionalities implemented or supported by client system130. As an example, a client system130may include a computer system such as a desktop computer, notebook or laptop computer, netbook, a tablet computer, e-book reader, GPS device, camera, personal digital assistant (PDA), handheld electronic device, cellular telephone, smartphone, augmented/virtual reality device, other suitable electronic device, or any suitable combination thereof. This disclosure contemplates any suitable client systems130. A client system130may enable a network user at client system130to access network110. A client system130may enable its user to communicate with other users at other client systems130.

In particular embodiments, social-networking system160may be capable of linking a variety of entities. As an example, social-networking system160may enable users to interact with each other as well as receive content from third-party systems170or other entities, or to allow users to interact with these entities through an application programming interfaces (API) or other communication channels.

FIG. 2illustrates example social graph200. In particular embodiments, social-networking system160may store one or more social graphs200in one or more data stores. In particular embodiments, social graph200may include multiple nodes—which may include multiple user nodes202or multiple concept nodes204—and multiple edges206connecting the nodes. Example social graph200illustrated inFIG. 2is shown, for didactic purposes, in a two-dimensional visual map representation. In particular embodiments, a social-networking system160, client system130, or third-party system170may access social graph200and related social-graph information for suitable applications. The nodes and edges of social graph200may 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 graph200.

In particular embodiments, a pair of nodes in social graph200may be connected to each other by one or more edges206. An edge206connecting a pair of nodes may represent a relationship between the pair of nodes. In particular embodiments, an edge206may include or represent one or more data objects or attributes corresponding to the relationship between a pair of nodes. As an example, a first user may indicate that a second user is a “friend” of the first user. In response to this indication, social-networking system160may send a “friend request” to the second user. If the second user confirms the “friend request,” social-networking system160may create an edge206connecting the first user's user node202to the second user's user node202in social graph200and store edge206as social-graph information in one or more of data stores164. In the example ofFIG. 2, social graph200includes an edge206indicating a friend relation between user nodes202of user “A” and user “B” and an edge indicating a friend relation between user nodes202of user “C” and user “B.” Although this disclosure describes or illustrates particular edges206with particular attributes connecting particular user nodes202, this disclosure contemplates any suitable edges206with any suitable attributes connecting user nodes202. As an example, an edge206may represent a friendship, family relationship, business or employment relationship, fan relationship (including, e.g., liking, etc.), follower relationship, visitor relationship (including, e.g., accessing, viewing, checking-in, sharing, etc.), 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 graph200by one or more edges206.

In particular embodiments, social-networking system160may create an edge206between a user node202and a concept node204in social graph200. As an example, 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 system130) may indicate that he or she likes the concept represented by the concept node204by clicking or selecting a “Like” icon, which may cause the user's client system130to send to social-networking system160a message indicating the user's liking of the concept associated with the concept-profile page. In response to the message, social-networking system160may create an edge206between user node202associated with the user and concept node204, as illustrated by “like” edge206between the user and concept node204. In particular embodiments, social-networking system160may store an edge206in one or more data stores. In particular embodiments, an edge206may be automatically formed by social-networking system160in response to a particular user action. As an example, if a first user uploads a picture, watches a movie, or listens to a song, an edge206may be formed between user node202corresponding to the first user and concept nodes204corresponding to those concepts. Although this disclosure describes forming particular edges206in particular manners, this disclosure contemplates forming any suitable edges206in any suitable manner.

In particular embodiments, an advertisement may be text (which may be HTML-linked), one or more images (which may be HTML-linked), one or more videos, audio, other suitable digital object files, a suitable combination of these, or any other suitable advertisement in any suitable digital format presented on one or more web pages, in one or more e-mails, or in connection with search results requested by a user. In addition or as an alternative, an advertisement may be one or more sponsored stories (e.g., a news-feed or ticker item on social-networking system160). A sponsored story may be a social action by a user (such as “liking” a page, “liking” or commenting on a post on a page, RSVPing to an event associated with a page, voting on a question posted on a page, checking in to a place, using an application or playing a game, or “liking” or sharing a website) that an advertiser promotes, for example, by having the social action presented within a pre-determined area of a profile page of a user or other page, presented with additional information associated with the advertiser, bumped up or otherwise highlighted within news feeds or tickers of other users, or otherwise promoted. The advertiser may pay to have the social action promoted. The social action may be promoted within or on social-networking system160. In addition or as an alternative, the social action may be promoted outside or off of social-networking system160, where appropriate. In particular embodiments, a page may be an on-line presence (such as a webpage or website within or outside of social-networking system160) of a business, an organization, or a brand facilitating its sharing of stories and connecting with people. A page may be customized, for example, by adding applications, posting stories, or hosting events.

A sponsored story may be generated from stories in users' news feeds and promoted to specific areas within displays of users' web browsers when viewing a web page associated with social-networking system160. Sponsored stories are more likely to be viewed by users, at least in part because sponsored stories generally involve interactions or suggestions by the users' friends, fan pages, or other connections. In connection with sponsored stories, particular embodiments may utilize one or more systems, components, elements, functions, methods, operations, or steps disclosed in U.S. patent application Ser. No. 13/327,557, entitled “Sponsored Stories Unit Creation from Organic Activity Stream” and filed 15 Dec. 2011, U.S. Patent Application Publication No. 2012/0203831, entitled “Sponsored Stories Unit Creation from Organic Activity Stream” and filed 3 Feb. 2012 as U.S. patent application Ser. No. 13/020,745, or U.S. Patent Application Publication No. 2012/0233009, entitled “Endorsement Subscriptions for Sponsored Stories” and filed 9 Mar. 2011 as U.S. patent application Ser. No. 13/044,506, which are all incorporated herein by reference as an example. In particular embodiments, sponsored stories may utilize computer-vision algorithms to detect products in uploaded images or photos lacking an explicit connection to an advertiser as disclosed in U.S. patent application Ser. No. 13/212,356, entitled “Computer-Vision Content Detection for Sponsored Stories” and filed 18 Aug. 2011, which is incorporated herein by reference as an example.

As described above, an advertisement may be text (which may be HTML-linked), one or more images (which may be HTML-linked), one or more videos, audio, one or more ADOBE FLASH files, a suitable combination of these, or any other suitable advertisement in any suitable digital format. In particular embodiments, an advertisement may be requested for display within third-party webpages, social-networking-system webpages, or other pages. An advertisement may be displayed in a dedicated portion of a page, such as in a banner area at the top of the page, in a column at the side of the page, in a GUI of the page, in a pop-up window, over the top of content of the page, or elsewhere with respect to the page. In addition or as an alternative, an advertisement may be displayed within an application or within a game. An advertisement may be displayed within dedicated pages, requiring the user to interact with or watch the advertisement before the user may access a page, utilize an application, or play a game. The user may, for example view the advertisement through a web browser.

A user may interact with an advertisement in any suitable manner. The user may click or otherwise select the advertisement, and the advertisement may direct the user (or a browser or other application being used by the user) to a page associated with the advertisement. At the page associated with the advertisement, the user may take additional actions, such as purchasing a product or service associated with the advertisement, receiving information associated with the advertisement, or subscribing to a newsletter associated with the advertisement. An advertisement with audio or video may be played by selecting a component of the advertisement (like a “play button”). In particular embodiments, an advertisement may include one or more games, which a user or other application may play in connection with the advertisement. An advertisement may include functionality for responding to a poll or question in the advertisement.

An advertisement may include social-networking-system functionality that a user may interact with. For example, an advertisement may enable a user to “like” or otherwise endorse the advertisement by selecting an icon or link associated with endorsement. Similarly, a user may share the advertisement with another user (e.g., through social-networking system160) or RSVP (e.g., through social-networking system160) to an event associated with the advertisement. In addition or as an alternative, an advertisement may include social-networking-system content directed to the user. For example, an advertisement may display information about a friend of the user within social-networking system160who has taken an action associated with the subject matter of the advertisement.

Social-networking-system functionality or content may be associated with an advertisement in any suitable manner. For example, an advertising system (which may include hardware, software, or both for receiving bids for advertisements and selecting advertisements in response) may retrieve social-networking functionality or content from social-networking system160and incorporate the retrieved social-networking functionality or content into the advertisement before serving the advertisement to a user. Examples of selecting and providing social-networking-system functionality or content with an advertisement are disclosed in U.S. Patent Application Publication No. 2012/0084160, entitled “Providing Social Endorsements with Online Advertising” and filed 5 Oct. 2010 as U.S. patent application Ser. No. 12/898,662, and in U.S. Patent Application Publication No. 2012/0232998, entitled “Selecting Social Endorsement Information for an Advertisement for Display to a Viewing User” and filed 8 Mar. 2011 as U.S. patent application Ser. No. 13/043,424, which are both incorporated herein by reference as examples only. Interacting with an advertisement that is associated with social-networking-system functionality or content may cause information about the interaction to be displayed in a profile page of the user in social-networking-system160.

Particular embodiments may facilitate the delivery of advertisements to users that are more likely to find the advertisements more relevant or useful. For example, an advertiser may realize higher conversion rates (and therefore higher return on investment (ROI) from advertising) by identifying and targeting users that are more likely to find its advertisements more relevant or useful. The advertiser may use user-profile information in social-networking system160to identify those users. In addition or as an alternative, social-networking system160may use user-profile information in social-networking system160to identify those users for the advertiser. As examples, particular embodiments may target users with the following: invitations or suggestions of events; suggestions regarding coupons, deals, or wish-list items; suggestions regarding friends' life events; suggestions regarding groups; advertisements; or social advertisements. Such targeting may occur, where appropriate, on or within social-networking system160, off or outside of social-networking system160, or on mobile computing devices of users. When on or within social-networking system160, such targeting may be directed to users' news feeds, search results, e-mail or other in-boxes, or notifications channels or may appear in particular area of web pages of social-networking system160, such as a right-hand side of a web page in a concierge or grouper area (which may group along a right-hand rail advertisements associated with the same concept, node, or object) or a network-ego area (which may be based on what a user is viewing on the web page and a current news feed of the user). When off or outside of social-networking system160, such targeting may be provided through a third-party website, e.g., involving an ad exchange or a social plug-in. When on a mobile computing device of a user, such targeting may be provided through push notifications to the mobile computing device.

Targeting criteria used to identify and target users may include explicit, stated user interests on social-networking system160or explicit connections of a user to a node, object, entity, brand, or page on social-networking system160. In addition or as an alternative, such targeting criteria may include implicit or inferred user interests or connections (which may include analyzing a user's history, demographic, social or other activities, friends' social or other activities, subscriptions, or any of the preceding of other users similar to the user (based, e.g., on shared interests, connections, or events)). Particular embodiments may utilize platform targeting, which may involve platform and “like” impression data; contextual signals (e.g., “Who is viewing now or has viewed recently the page for COCA-COLA?”); light-weight connections (e.g., “check-ins”); connection lookalikes; fans; extracted keywords; EMU advertising; inferential advertising; coefficients, affinities, or other social-graph information; friends-of-friends connections; pinning or boosting; deals; polls; household income, social clusters or groups; products detected in images or other media; social- or open-graph edge types; geo-prediction; views of profile or pages; status updates or other user posts (analysis of which may involve natural-language processing or keyword extraction); events information; or collaborative filtering. Identifying and targeting users may also include privacy settings (such as user opt-outs), data hashing, or data anonymization, as appropriate.

To target users with advertisements, particular embodiments may utilize one or more systems, components, elements, functions, methods, operations, or steps disclosed in the following, which are all incorporated herein by reference as examples: U.S. Patent Application Publication No. 2009/0119167, entitled “Social Advertisements and Other Informational Messages on a Social Networking Website and Advertising Model for Same” and filed 18 Aug. 2008 as U.S. patent application Ser. No. 12/193,702; U.S. Patent Application Publication No. 2009/0070219, entitled “Targeting Advertisements in a Social Network” and filed 20 Aug. 2008 as U.S. patent application Ser. No. 12/195,321; U.S. Patent Application Publication No. 2012/0158501, entitled “Targeting Social Advertising to Friends of Users Who Have Interacted With an Object Associated with the Advertising” and filed 15 Dec. 2010 as U.S. patent application Ser. No. 12/968,786; or U.S. Patent Application Publication No. 2012/0166532, entitled “Contextually Relevant Affinity Prediction in a Social-Networking System” and filed 23 Dec. 2010 as U.S. patent application Ser. No. 12/978,265.

An advertisement may be presented or otherwise delivered using plug-ins for web browsers or other applications, iframe elements, news feeds, tickers, notifications (which may include, for example, e-mail, Short Message Service (SMS) messages, or notifications), or other means. An advertisement may be presented or otherwise delivered to a user on a mobile or other computing device of the user. In connection with delivering advertisements, particular embodiments may utilize one or more systems, components, elements, functions, methods, operations, or steps disclosed in the following, which are all incorporated herein by reference as examples: U.S. Patent Application Publication No. 2012/0159635, entitled “Comment Plug-In for Third-Party System” and filed 15 Dec. 2010 as U.S. patent application Ser. No. 12/969,368; U.S. Patent Application Publication No. 2012/0158753, entitled “Comment Ordering System” and filed 15 Dec. 2010 as U.S. patent application Ser. No. 12/969,408; U.S. Pat. No. 7,669,123, entitled “Dynamically Providing a News Feed About a User of a Social Network” and filed 11 Aug. 2006 as U.S. patent application Ser. No. 11/503,242; U.S. Pat. No. 8,402,094, entitled “Providing a Newsfeed Based on User Affinity for Entities and Monitored Actions in a Social Network Environment” and filed 11 Aug. 2006 as U.S. patent application Ser. No. 11/503,093; U.S. Patent Application Publication No. 2012/0072428, entitled “Action Clustering for News Feeds” and filed 16 Sep. 2010 as U.S. patent application Ser. No. 12/884,010; U.S. Patent Application Publication No. 2011/0004692, entitled “Gathering Information about Connections in a Social Networking Service” and filed 1 Jul. 2009 as U.S. patent application Ser. No. 12/496,606; U.S. Patent Application Publication No. 2008/0065701, entitled “Method and System for Tracking Changes to User Content in an Online Social Network” and filed 12 Sep. 2006 as U.S. patent application Ser. No. 11/531,154; U.S. Patent Application Publication No. 2008/0065604, entitled “Feeding Updates to Landing Pages of Users of an Online Social Network from External Sources” and filed 17 Jan. 2007 as U.S. patent application Ser. No. 11/624,088; U.S. Pat. No. 8,244,848, entitled “Integrated Social-Network Environment” and filed 19 Apr. 2010 as U.S. patent application Ser. No. 12/763,171; U.S. Patent Application Publication No. 2011/0083101, entitled “Sharing of Location-Based Content Item in Social-Networking Service” and filed 6 Oct. 2009 as U.S. patent application Ser. No. 12/574,614; U.S. Pat. No. 8,150,844, entitled “Location Ranking Using Social-Graph Information” and filed 18 Aug. 2010 as U.S. patent application Ser. No. 12/858,718; U.S. patent application Ser. No. 13/051,286, entitled “Sending Notifications to Users Based on Users' Notification Tolerance Levels” and filed 18 Mar. 2011; U.S. patent application Ser. No. 13/096,184, entitled “Managing Notifications Pushed to User Devices” and filed 28 Apr. 2011; U.S. patent application Ser. No. 13/276,248, entitled “Platform-Specific Notification Delivery Channel” and filed 18 Oct. 2011; or U.S. Patent Application Publication No. 2012/0197709, entitled “Mobile Advertisement with Social Component for Geo-Social Networking System” and filed 1 Feb. 2011 as U.S. patent application Ser. No. 13/019,061. Although this disclosure describes or illustrates particular advertisements being delivered in particular ways and in connection with particular content, this disclosure contemplates any suitable advertisements delivered in any suitable ways and in connection with any suitable content.

In particular embodiments, social-networking system160may perform particular actions with respect to a user based on coefficient information. Coefficients may be used to predict whether a user will perform a particular action based on the user's interest in the action. A coefficient may be used when generating or presenting any type of objects to a user, such as advertisements, search results, news stories, media, messages, notifications, or other suitable objects. The coefficient may also be utilized to rank and order such objects, as appropriate. In this way, social-networking system160may provide information that is relevant to user's interests and current circumstances, increasing the likelihood that they will find such information of interest. In particular embodiments, social-networking system160may generate content based on coefficient information. Content objects may be provided or selected based on coefficients specific to a user. As an example, the coefficient may be used to generate media for the user, where the user may be presented with media for which the user has a high overall coefficient with respect to the media object. As another example, the coefficient may be used to generate advertisements for the user, where the user may be presented with advertisements for which the user has a high overall coefficient with respect to the advertised object. In particular embodiments, social-networking system160may generate search results based on coefficient information. Search results for a particular user may be scored or ranked based on the coefficient associated with the search results with respect to the querying user. As an example, search results corresponding to objects with higher coefficients may be ranked higher on a search-results page than results corresponding to objects having lower coefficients.

In particular embodiments, one or more servers162may be authorization/privacy servers for enforcing privacy settings. In response to a request from a user (or other entity) for a particular object stored in a data store164, social-networking system160may send a request to the data store164for the object. The request may identify the user associated with the request and may only be sent to the user (or a client system130of the user) if the authorization server determines that the user is authorized to access the object based on the privacy settings associated with the object. If the requesting user is not authorized to access the object, the authorization server may prevent the requested object from being retrieved from the data store164, or may prevent the requested object from be sent to the user. In the search query context, an object may only be generated as a search result if the querying user is authorized to access the object. In other words, the object may have a visibility that is visible to the querying user. If the object has a visibility that is not visible to the user, the object may be excluded from the search results. Although this disclosure describes enforcing privacy settings in a particular manner, this disclosure contemplates enforcing privacy settings in any suitable manner.

FIG. 3illustrates an example system300comprising a set of connected devices305, gateway device310, control device315, and backend system320connected to social network160. Connected devices305, gateway device310, control device315, and backend system320may each comprise one or more computer systems, such as computer system500ofFIG. 5. Connected devices305, gateway device310, control device315, and backend system320may communicate with one another via any suitable network comprising any suitable connections (e.g., network110ofFIG. 1, with wireline connections, wireless connections, or a combination thereof). The architecture of system300may be used for the devices present within a defined physical space (e.g., a house, an office building, or a park), or with a set of devices related to a particular user or entity (e.g., connected devices associated with a user, where the devices are located in their home, their car, and/or their small retail business; or belonging to a property management business managing door locks and alarm security systems for a group of buildings). In embodiments involving a single physical location, only a single gateway device310may be needed to connect the connected devices305to control device315and/or backend system320. However, it will be understood that multiple gateway devices310may be used in certain embodiments (e.g., in large spaces where enhanced wireless coverage is needed). In embodiments involving multiple physical locations, each of the physical locations (e.g., house, car, and business) may each have its own respective gateway device310that connects the connected devices305of that location to control device315and/or backend system320. As in the single location example, it will be understood that multiple gateway devices310may be used in each physical location (e.g., in large spaces where enhanced wireless coverage is needed). In embodiments with multiple gateway devices310, each gateway device310may communicate with one another.

Connected devices305may include any suitable device for transmitting information associated with the device305(e.g., event notifications) to gateway device310and/or backend system320(by way of gateway device310). Connected devices305may include anything from complex embedded computing devices, to switches, to simple sensors. For example, the connected devices depicted inFIG. 3include a desktop computer, a laptop, a refrigerator, a home security system, a television, a vehicle, and a SLR camera. In particular embodiments, one or more of connected devices305may be operable to detect one or more environmental conditions, such as a time of day, day of the week, whether it is dark or light outside, an outside temperature, an ambient temperature, or any other suitable environmental condition. The environmental condition may be detected by the connected device305using a sensor located on or coupled to the device (e.g., a thermometer coupled to a thermostat), by accessing information stored at the connected device305(e.g., time, day, or date information stored locally on the device), by gathering information from another connected device305, gateway310, or backend system320(e.g., sensor information or time, day, or date information), by gathering information from other sources (e.g., the Internet), or by gathering information from any combination of the above (e.g., using the Internet to determine whether it was light or dark outside and/or what the weather was like at 5:47 pm on a particular day).

Gateway device310may include any suitable device for interfacing with connected devices305, control device315, and/or backend system320. In particular embodiments, gateway device310may be capable of supporting the required functionality to facilitate local network control of connected devices305and act as a local gateway for a service that may run in the cloud (e.g., on backend system320). In particular embodiments, the service may facilitate communication with the user (e.g., via control device315). In particular embodiments, the service and the user may communicate using natural language which may then be parsed by one or more components of system300(e.g., by control device315, gateway device310, backend system320, or a combination thereof). In particular embodiments, a user may use a messaging application on control device315to communicate with gateway device310and/or with any of the connected devices305(by way of the gateway device310). In particular embodiments, gateway device310may be based on a RASPBERRY PI platform running RASPIAN Linux and supporting WiFi, BLUETOOTH, ZWAVE and ZIGBEE dongles. Gateway device310may be used to host a gateway application that interfaces between the devices of system300.

Control device315may include any suitable device for presenting a user interface for interfacing with gateway device310and connected devices305(by way of gateway device310). For example, control device315present a user interface by way of an installed application, a browser, a SMS texting interface, or an interface provided by the device's operating system that allows a user of control device315to control, or send/receive information to, gateway device310and/or connected devices305. In particular embodiments, control device315may include one or more UI clients (e.g., a messaging service application), which acts as the main UX point; Social networking application or other mobile application—a helper application, used for initial provisioning, BLUETOOTH and location discovery, and generally anything permission related that the messaging application service application cannot do. In particular embodiments, a control application running on control device315may be used by the user to provision connected devices305. In further embodiments, the control application may provide a specific user experience for the user based on particular scenarios. In particular embodiments, the control application running on control device315may enable the viewing of information related to connected devices305, the setup and management of rules automatically generated by system300(such as rules generated using method400below), and pushing status updates from the connected devices305to a messaging application on the control device315.

Backend system320may include any suitable server or group of servers for interfacing with, and aggregating data from, connected devices305, gateway device310, and control device315in system300, as well as connected devices, gateway devices, and control devices in other systems that communicate with backend system320. Backend system320may comprise a messaging infrastructure325(e.g., to communicate with control device315), an integration layer330(e.g., a platform and/or API to interface with a diverse array of connected devices, such as PARSE) to interface between elements of backend system320and gateway device310(and/or control device315and/or directly with connected devices305). Backend system320may maintain a data store332of device events, comprising data received from gateway device310and each of the connected devices305, as well as data derived therefrom. Backend system320may also maintain a data store334for one or more device graphs, in which gateway device310and each of the connected devices305may each be represented by a device node with edges connecting the device nodes. Backend system320may include a device graph intelligence infrastructure335for processing and analyzing the device events, updating the device graph, and providing feedback and/or instructions to connected devices305and/or control device315. In particular embodiments, certain functionality (e.g., evaluating event sequences and generating rules therefor in accordance with the present disclosure) may be provided by gateway device310, by backend system320, or by a combination thereof.

Backend system320may also communicate with social-networking system160. In particular embodiments, backend system320may leverage social-networking system160, a social graph associated with social-networking system160, particular identities in such a social graph, notifications provided to users of social-networking system160, or any combination thereof. For example, backend system320may utilize identifying information for a user of one or more connected devices305based on information from the social-networking system160to determine the user that performed an action with a particular connected device305(e.g., identifying the user performing user input related to a connected device305) or that was associated with an event occurring at connected device305(e.g., identifying the user that opened or unlocked a door).

In particular embodiments, gateway device310may have an application running thereon, wherein its responsibilities consist of understanding and dealing at “physical” level with the various connected devices305in system300. This may include, for example: discovery and provisioning of new connected devices305over BLUETOOTH, ZIBGEE, ZWAVE, WiFi (via a wireless access point or direct connection); mapping of connected devices305to a device type and/or device ID; mapping of the device type to available capabilities and/or functionalities; grouping or association of connected devices305in vertical (such as those with the same or similar capabilities, e.g., “lights” or “door locks”); support for understanding various industry protocols (e.g., for example ALLJOYN, THREAD, WEAVE, ZIGBEE, and the like); translating specific intents (e.g., associated with specific device IDs) passed from backend system320into direct control and query messages (e.g., “device ID(s) XXX on” passed on from gateway device→“Phillips Hue device ID XXX turn on”); translating specific device notifications into logical notifications that can be interpreted by backend system320(e.g., “August SmartLock device id XXX unlocked”→“device ID XXX unlocked”) or communicated to control device315. In particular embodiments, while gateway device301may perform some mapping between physical and logical devices, it may convert these into machine-readable structured formats.

In particular embodiments, the gateway application running on gateway device310may support a number of various vendors' or manufacturers' connected devices305. For example, the gateway application may support discovery and provisioning of two or more connected lights from multiple vendors (e.g., PHILLIPS HUE, BELKIN WEMO WiFi switch, ZIGBEE or ZWAVE smart switch); control of one or more pre-provisioned smart locks from different vendors (e.g., LOCKITRON, AUGUST); control and streaming of music and/or video to multiple targets over WiFi-connected speakers and/or smart TVs and the gateway device itself (e.g., via an HDMI port).

In particular embodiments, backend system320may include an application or service running thereon (or in the cloud) that communicates with gateway device310. It may handle integration with messaging applications and natural language processing systems (NLP), translation of the user's intent to specific logical device control intents (e.g., using NLP and context awareness), and machine learning (ML) to infer complex behavior rules involving multiple devices. In particular embodiments, backend system320may only interface with individual ones of connected devices305by way of gateway device310. In particular embodiments, backend system320may deal with logical devices (e.g., “lights” vs “PHILLIPS HUE”), aliases assigned by a user (e.g., “front porch light”) and device groups (e.g., “all lights”). As such, backend system320may provide one or more of the following interfaces and capabilities:1. Association of human naming of devices with logical ID provided by Home Gateway (e.g., user chooses name “Front Door Light” for a device id); Grouping/association of devices along a horizontal (same location, e.g., “living room” or “front door);2. Mapping of device capabilities to human input/output commands;3. Translating specific intents passed from the user associated with the specific names they have assigned devices into a device ID based actions. (e.g., “Turn on Front Porch Light”→“device id(s) XXX on”);4. Translating specific device notifications passed forward by the home gateway into human readable format (e.g., “device ID XXX unlocked”→“Front Door Unlocked”).

In particular embodiments, additional features provided by system300may include: NLP control and notifications of one or more connected devices305through a messaging application, explicit grouping of devices by the user, and creating and executing multi-device instructions (e.g., “when front door is unlocked, turn the lights on”).

In particular embodiments, to be able to interpret commands in a context aware fashion, the logic relies on a view of the device graph based on a userID (the user who wants to take action) and/or location information (e.g., based on signals like cell IDs of mobile networks around, WiFi geolocation, visible SSIDs etc. in addition to strong localization via GPS coordinates). For example, a user might be associated with multiple gateway devices310(e.g., a primary family home, a weekend condo, and a secondary home), in which case location information may determine to which devices a particular command should apply. In particular embodiments, the system300(by way of backend system320and/or gateway device(s)310) may provide for configuration of user role settings (user, command and location-based) in the device graph (e.g., permission models may allow for configuration of an admin role for full control and a limited user role with limited permissions). For example, a user may not want their kids (who are playing in the living room where the stereo system is located) to change the music the user is currently enjoying while working in his home office.

In particular embodiments, system300(e.g., using backend system320and/or gateway device310) may learn the habits and behaviors of a user and may generate automatic rules in accordance with those habits and behaviors. For example, upon a user coming home after work, the user may typically turn on their stereo shortly thereafter. One or more components of system300may detect this habit, and generate a rule that turns on the stereo when the user unlocks or opens the door after a particular time in the evening.

In particular embodiments, system300may learn the user's behaviors, trends, and habits by analyzing event sequences that occur within a particular time period (e.g., within a maximum amount of time) and may determine a score for event sequences. Upon the score reaching a certain threshold, a rule may be generated for the event sequence and may be employed by the system. In particular embodiments, system300may take into account environmental conditions (e.g., what time it is, what day of the week (e.g., weekend vs. weekday), whether it is light or dark outside, what the temperature inside or outside the building (or both) is, etc.) when evaluating the event sequences and/or generating rules therefor. In further embodiments, rules may be specific to each event sequence and there will be exceptions to each sequence. For instance, using the above example of the user coming home and the stereo turning on automatically, the rule may have a time-based exception to not turn on the stereo until after 5 pm, or may not turn on the stereo upon the user coming home on the weekend.

In particular embodiments, an event is generated by a connected device305(e.g., a door is unlocked or opened/closed, a light in the bathroom is turned on, etc.). After the event occurs, events thereafter that occur within a particular time period (e.g., 1 minute, 5 minutes, or 10 minutes) may be evaluated. The evaluation may look at a delta, or time slice, between each of the events in the event sequence and/or conditional factors (e.g., environmental conditions or a status of the connected devices305at the time), and may determine whether the event sequence is habitual and/or intentional, or otherwise. For instance, system300may determine whether the event sequence has occurred previously and may determine or adjust a score associated with the event sequence accordingly.

For example, in particular embodiments, when an event occurs, the events within a particular time delta (referred to as Dmax in this paragraph, which may be 1 minute in some embodiments, or determined experimentally in other embodiments) are evaluated (e.g., Event1, Event2, . . . ). A score is then generated for the sequence based on the equation:
Score=1−Π(Dmax−min(deltaN,Dmax))/Dmax.

The score may be evaluated against previous event sequences and/or conditions surrounding the event sequence. If an event sequence with the same condition has previously occurred, then the score may be multiplied or otherwise modified. After the scoring or score adjustment, a later calculation may be employed to determine whether or not the score exceeds a certain threshold. If the score does exceed the threshold, a rule may be generated to automatically implement the event sequence upon seeing a particular event and/or condition occur in the future. Using the above example, when system300detects the user unlocking the door in the evening (e.g., after 5 pm), system300may send instructions to the stereo to turn on (e.g., using a push command as described below). An example method for generating rules based on detected event sequences is described below with respect toFIG. 4.

In particular embodiments, a rules runtime interpreter may run on backend system320, and comprise a JAVASCRIPT application that reads locally-stored rules, spawns the main process (e.g., pushes instructions to connected devices305) and monitors any output. Backend system may then (a) parse the pushed data received from integration layer330and (b) based on the parsed information, do one or more of: updating the rules; storing new rules locally; executing device control; executing queries; discovering devices; parsing the rules; waiting for triggers indicated by the rules (e.g., a time or a sensor measurement); executing events on the triggers; executing device control; running a local webserver which allows triggering of the rules via local networks.

Example Push Protocol

Field “command”, required, type “string”, values“query”|”discover”|”control”|”rule”|”user”“command” == “rule” operate on the rule:Field “rule_id” - required for “command” == “rule”, type:string, id of the ruleField “action” - optional, type:string, values:“update”|”delete”, default “update”“update” - updates or creates (if necessary) the rule“delete” - deletes the ruleField “rule_data” - required if “action”==“update”,type:json, rule to be added/updated to rules.data“command” == “discover” - discovers devices. No arguments.Updates PARSE devices table.“command”==”query” - queries the device state,“command”==”control” -controls the device:Field: “device_id”- required, type:string , id of thedeviceField: “settings” - required for “command” == “control”,device-specific control requests.query posts “device_state” message back to query posts“device_state” message back to integration layer 330“command” == “user” - backend sends an authorized user'sSYSTEMID to the gateway device. This is a tradeoff when devicelogin is not completed, otherwise the gateway device may notknow which user is controlling it. The gateway device may savethe user identification to a file and read it when saving a“DeviceMessage”.

Example Device Instructions

LightsPHILIPS HUEhue_get(device_id, light_id)Get the state (on/off status, hue, brightness,saturation, etc.) of all or a specific bulb.hue_set(device_id, light_id, power, bri, hue, sat)Set the state of a specific bulbhue_config(ip, user)Add a new user to a PHILIPS HUE bridge.May prompt a user to press the safety button onthe PHILIPS HUE bridgeReturns device idSpeakersMusic playermusic player_play(device_id)music player_pause(device_id)music player_next(device_id)music player_previous(device_id)music player_play_uri(device_id)music player_clear_queue(device_id)music player_add_toqueue(device_id)music player_play_mode(device_id)music player_get_volume(device_id)music player_config(ip)

In particular embodiments, a push from integration layer330may be in curl format as shown below:

In particular embodiments, the App ID (e.g., device ID) and REST key should be taken from the particular device being used. The current app's id/key is: “ro2sqHypZCVs4qe6dwvj31gOYLaux6hBFGd6J54g”, “dl5gBnYcsubgJtG91dGPYi0x40rFWu2 ZyNxJ6inZ”. In particular embodiments, the where clause may be used when directing a push to a single connected device305or particular connected devices305. In particular embodiments, the where clause may be omitted to send a push to all connected devices305. In particular embodiments, the gateway installation ID is a unique identifier generated for each connected device305. It may also be stored in integration layer330in certain embodiments. In particular embodiments, the command can be one of: rule, discover, query, control, or update. Each of these commands expects specific fields to follow the command key (which are outlined below).

In particular embodiments, the push data fields of a rule command may be in the format shown below:

In particular embodiments, the command is the same as above. In this case, it specifies that the current push deals with a rule. In particular embodiments, the action field specifies what will be happening with the rule—either “update” or “delete”. If not specified, it will default to update. Update should be used to create or update rules, and delete will delete a rule. In particular embodiments, the rule_id field specifies what rule will be acted upon. It must always be specified even if a new rule is being created (in which case it will be used as the new rule's id). It may also be unique. In particular embodiments, the rule_data field is used only for update actions and is not used for delete actions. It contains the data that will be used to update/save the rule with. The specific fields are below. In further embodiments, The name field specifies the name for the rule. This should typically be a more friendly name for the rule with which the user can use to reference it.

In further embodiments, the trigger field is used to specify the trigger for the rule. Two types of triggers are supported—a device based trigger, which is fired when a device enters a certain state, and a time-based trigger, which is used to set off cron jobs. In particular embodiments, the trigger field may look like the following example below. The event field may be structured identically to the “state” field on a condition, except it does not support “time”.

In particular embodiments, the cron field specifies a cron job for the rule which will cause the rule to be executed at specific times. It will only be referenced if the trigger's event field is the string “time”. In particular embodiments, the conditions field allows for further conditions to be specified before execution of the rule. It is formed as a JSON tree which supports AND, OR, and NOT logical operators. It can further be used to check the current time, and whether or not a device is in a specific state. An example of a conditions field is shown below.

In further embodiments, the type field specifies whether this is a state check or a logical operation. As mentioned above, the logical operations supported are AND, OR, and NOT. Three state checks are supported: value, range, and time.

In further embodiments, the check type field is used to specify the type of state check being defined. It is not needed for logical operations. Value checks are used to make sure a device is in a specific state. Range checks offer the same functionality as a value check, except they allow a range of values to be specified. Time checks are used to specify the time in which the rule should be executed. In particular embodiments, if a range or time check is define, the range_min and range_max fields must be specified. In particular embodiments, if a value check is define, value must be specified.

In further embodiments, the state_name field is used to specify the particular parameter being checked. For range and value checks, these are the values of the device being checked. For a time check, this can either be minutes, hours, date, day, or month. To specify an exact value for a time check (similar to a value check but for time), the same number should be used in the range_min and range_max fields.

In particular embodiments, the actions field tells the rule exactly what should happen if the rule is triggered and the conditions are met. An example is below. In further embodiments, the deviceId field specifies what device the actions will be performed on. In further embodiments, the actions field shows what parameters should be changed on the device, and what each parameter should be set to. Note: currently these should be in the same format that a Control command would use, except only one parameter should be specified in a single element in the array.

In particular embodiments, a complete rule may look like the following example:

In particular embodiments, a discover command does not require further arguments. Thus, a full discover command may appear similar to the following example:

In particular embodiments, a command requires the ID of the queried device, as well as what type of device it is. A query command may appear similar to the following example:

In particular embodiments, a command causes gateway device310to change the current state of a connected device305given the parameters that are passed in the command. The parameters correspond to the type of connected device305being controlled, so the command may be formatted according to the type of connected device305. An examples command is shown below:

In particular embodiments, a device cloud (e.g., system300in a home) may have a corresponding instance in the cloud. Each device action (user command, device event, etc.) may be logged and sent over a messaging queue of the device cloud instance. A recipe may contain one or multiple rules. A rule may have a device action, which can be executed with timing or triggered by another action. A particular device cloud instance may have a rule execution engine for digesting device action messaging queue and execute rules. In certain embodiments, there may be rules incorporating permissions, capabilities, events, and actions.

In particular embodiments, the base rule may be:

In particular embodiments, the schedule rule may be:

In particular embodiments, the trigger rule may be:

In particular embodiments, the execution engine may be:

FIG. 4illustrates an example method400for generating and executing behavior-based rules for connected devices on a network. For ease of reference, method400is described below with respect to certain devices in system300ofFIG. 3. However, it will be understood that the steps of method400may be performed by any suitable device in a device cloud in accordance with the present disclosure. Method400may be performed by executing software or other instructions embodied in a computer-readable medium using one or more processors embodied by a computing device or devices of the system (e.g., a computer system similar to computer system500ofFIG. 5).

Method400begins at step410, where backend system320receives notifications of events associated with the one or more connected devices305. The event notifications may be received from the one or more connected devices305either directly or via gateway device310. The event notifications may be sent in any suitable format, such as plain text or XML. In particular embodiments, the event notifications may include indications that a particular occurrence happened with respect to the connected device305that sent the notification. For example, when a door is unlocked, the lock (i.e., a connected device305of system300) may send a notification to gateway device310indicating the unlock event. Gateway device310may then forward the notification to backend system320, in the same format or in a different format from that sent by the lock device. In particular embodiments, an event may be a user input at a connected device305(or control device315). For example, the user may command a stereo to turn on after returning home from work in the evening. The command sent may thus be the event or the stereo turning on may be the event, or both.

At step420, backend system320evaluates event sequences for the connected devices305. The event sequences may include two or more events associated with one or more connected devices305that occur within a particular time period. The event sequences may include events for a single connected device305or a plurality of connected devices305. Thus, for every event notification received, backend system320may analyze that event and the next events that occur within the particular time period to determine whether the event sequence (if any occurs for the event) should become a rule for automatic execution in the future when the event occurs. In certain embodiments. the particular time period may be pre-determined, and may be, for example, 1 minute, 5 minutes, or 10 minutes. In other embodiments, the particular time period may be determined using historical data. This may include determining a maximum time difference for two events in an event sequence associated with a generated rule. For example, backend system320may look at the maximum time difference between a first and last event of event sequences in generated rules. Furthermore, a user may begin to reject or delete rules that they do not wish to be automatic. Based on these rejections, backend system320may determine a maximum amount of time for event sequences that are kept as rules and may use this amount of time as the maximum amount of time to evaluate event sequences.

In particular embodiments, evaluating the plurality of event sequences may include determining a score associated with each event sequence. In certain embodiments, the score for each event sequence may be determined based on time differences between the two or more events in the event sequence. For example, where events of an event sequence occur closely in time to one another, the event sequence may have a relatively high score. Conversely, where events of an event sequence occur many minutes from one another, the event sequence may have a relatively low score. In certain embodiments, the may be determined using the formula:
score=1−Π(Dmax−min(deltaN,Dmax))/Dmax,
where:Dmax refers to the particular time period; anddeltaN refers to an amount of time between an Nth event in the eventsequence and the chronologically-first event in the event sequence.

In particular embodiments, evaluating the event sequences may include determining that the event sequence is substantially similar to another event sequence and modifying the score associated with the event sequence accordingly. For example, where an event sequence has occurred previously, the score for such event sequences may be multiplied by a certain factor.

At step430, backend system320generates a plurality of rules based on the event sequences evaluated at step420. In particular embodiments, generating a rule may include determining that a score associated with the event sequence has exceeded a threshold. The threshold may be pre-determined in certain embodiments, or determined experimentally in other embodiments. For example, scores for rules kept or rejected by a user may be analyzed to determine a threshold for generating future rules.

In particular embodiments, whether a rule is generated or not may be based on one or more environmental conditions present during the evaluated event sequences. The one or more environmental conditions may include one or more of: a time of day, a day of week, an outside temperature (e.g., where a connected device is located inside), or an ambient temperature (i.e., around the connected device, outside or inside). For example, a user when returning home from work may turn on the stereo every night, but may not do so when arriving home for lunch or on the weekends. Thus, a rule for automatically turning on the stereo after a user has unlocked a door may only be triggered where the unlocking of the door occurs after 5 pm on a weekday.

In particular embodiments, a generated rule may be further based on a status of a connected device when the event sequence under evaluation begins. For example, an event sequence may include unlocking a door and then turning on the stereo (each device being a connected device305). Sometimes, one or more lights may be on and sometimes they may be off when this event sequence occurs, which may be because the user does not turn on the stereo if someone is already home (i.e., why the lights are already on). Thus, in this example, a rule for automatically turning on the stereo may be based on whether one or more lights in the home are already turned on.

In particular embodiments, an exception may be generated that is associated with at least one rule of the plurality of rules. The exception may be generated by backend system320in some embodiments. For example, in evaluating the event sequence of unlocking a door and turning on the stereo, backend system320may determine that the event sequence only or mostly occurs during the weekdays. As such, backend system320may generate an exception to the rule dictating that the stereo be turned on when the user unlocks the door, indicating an exception for weekends. In other embodiments, the exception may be generated by a user of the system. For example, after a rule has been generated dictating that the stereo be turned on when the user unlocks the door, the user (via control device315) may indicate an exception for weekends.

At step440, backend system320receives an event notification for a connected device305. The notification may be received after one or more rules have been generated by backend system320at step430. The event notification may indicate a first event has occurred at a first connected device305.

At step450, backend system320determines whether the event received at step440is associated with any rule generated at step430. In particular embodiments, this may include determining that a first rules of the plurality of rules is based on the first event for which the notification was received at step440. In some embodiments, this step may include backend system320analyzing the rules already generated to determine which rules have event sequences that start with the first event (i.e. those that are chronologically first in the event sequence). This step may further include determining which rules of those that have event sequences that start with the first event have one or more matching conditions (e.g., environmental conditions).

If the event is not associated with any rule, the method returns to step440where backend system320waits to receive additional event notifications from connected devices305. If the event received at step450is associated with a particular rule, then, at step460, backend system320sends instructions to connected devices305in accordance with the particular rule. The instructions may be sent as a part of a message to the connected devices305associated with the rule (i.e., those participating in the event sequence that is part of the rule). The instructions may be sent to connected devices305directly or via gateway device310. The instructions may be in any suitable format for performing the action on the particular connected device305. In some embodiments (e.g., those having devices from different vendors), the format of each respective message including instructions may be different for each connected device305. In certain embodiments, the instructions may be in a format similar to the pushed rule command formats discussed above with reference toFIG. 3. In the door lock and stereo example from above, this step may thus include sending instructions to the stereo to turn on (or perform one or more other actions) after detecting that the door has unlocked in the evening with no lights on.

Particular embodiments may repeat one or more steps of the method400ofFIG. 4, where appropriate. Although this disclosure describes and illustrates particular steps of the method ofFIG. 4as occurring in a particular order, this disclosure contemplates any suitable steps of the method ofFIG. 4occurring in any suitable order. Furthermore, although this disclosure describes particular components, devices, or systems carrying out particular steps of the method400ofFIG. 4, this disclosure contemplates any suitable combination of any suitable components, devices, or systems carrying out any suitable steps of the method400ofFIG. 4.

FIG. 5illustrates an example computer system500. In particular embodiments, one or more computer systems500perform one or more steps of one or more methods described or illustrated herein. In particular embodiments, one or more computer systems500provide functionality described or illustrated herein. In particular embodiments, software running on one or more computer systems500performs 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 systems500. Herein, reference to a computer system may encompass a computing device, and vice versa, where appropriate. Moreover, reference to a computer system may encompass one or more computer systems, where appropriate.

In particular embodiments, computer system500includes a processor502, memory504, storage506, an input/output (I/O) interface508, a communication interface510, and a bus512. 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.

In particular embodiments, processor502includes hardware for executing instructions, such as those making up a computer program. As an example, to execute instructions, processor502may retrieve (or fetch) the instructions from an internal register, an internal cache, memory504, or storage506; decode and execute them; and then write one or more results to an internal register, an internal cache, memory504, or storage506. In particular embodiments, processor502may include one or more internal caches for data, instructions, or addresses. This disclosure contemplates processor502including any suitable number of any suitable internal caches, where appropriate. As an example, processor502may 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 memory504or storage506, and the instruction caches may speed up retrieval of those instructions by processor502. Data in the data caches may be copies of data in memory504or storage506for instructions executing at processor502to operate on; the results of previous instructions executed at processor502for access by subsequent instructions executing at processor502or for writing to memory504or storage506; or other suitable data. The data caches may speed up read or write operations by processor502. The TLBs may speed up virtual-address translation for processor502. In particular embodiments, processor502may include one or more internal registers for data, instructions, or addresses. This disclosure contemplates processor502including any suitable number of any suitable internal registers, where appropriate. Where appropriate, processor502may include one or more arithmetic logic units (ALUs); be a multi-core processor; or include one or more processors502. Although this disclosure describes and illustrates a particular processor, this disclosure contemplates any suitable processor.

In particular embodiments, memory504includes main memory for storing instructions for processor502to execute or data for processor502to operate on. As an example, computer system500may load instructions from storage506or another source (such as, for example, another computer system500) to memory504. Processor502may then load the instructions from memory504to an internal register or internal cache. To execute the instructions, processor502may retrieve the instructions from the internal register or internal cache and decode them. During or after execution of the instructions, processor502may write one or more results (which may be intermediate or final results) to the internal register or internal cache. Processor502may then write one or more of those results to memory504. In particular embodiments, processor502executes only instructions in one or more internal registers or internal caches or in memory504(as opposed to storage506or elsewhere) and operates only on data in one or more internal registers or internal caches or in memory504(as opposed to storage506or elsewhere). One or more memory buses (which may each include an address bus and a data bus) may couple processor502to memory504. Bus512may include one or more memory buses, as described below. In particular embodiments, one or more memory management units (MMUs) reside between processor502and memory504and facilitate accesses to memory504requested by processor502. In particular embodiments, memory504includes 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. Memory504may include one or more memories504, where appropriate. Although this disclosure describes and illustrates particular memory, this disclosure contemplates any suitable memory.

In particular embodiments, storage506includes mass storage for data or instructions. As an example, storage506may 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. Storage506may include removable or non-removable (or fixed) media, where appropriate. Storage506may be internal or external to computer system500, where appropriate. In particular embodiments, storage506is non-volatile, solid-state memory. In particular embodiments, storage506includes 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 storage506taking any suitable physical form. Storage506may include one or more storage control units facilitating communication between processor502and storage506, where appropriate. Where appropriate, storage506may include one or more storages506. Although this disclosure describes and illustrates particular storage, this disclosure contemplates any suitable storage.