Patent Grant
11169699
The subject matter disclosed herein relates generally to control of an application through a display device and, more particularly, but not by way of limitation, to control of an application through a display device using gesture based triggers.
Users can interact with applications executing on mobile devices through touchscreen displays of the mobile devices. The touchscreen displays have limited screen size, and only a limited number of user interface objects, such as input and output elements (e.g., on-screen keyboard), menus, and other user interface objects (e.g., checkboxes, text entry fields), can be displayed on a given touchscreen display at any one time. These limitations make controlling applications through mobile devices difficult and can overall hamper user experience. Further, in some cases, some users may be limited to manipulating their respective mobile devices with only one available hand, which further worsens user experience.
Some example embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings.
In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide an understanding of various example embodiments of the present subject matter. It will be evident, however, to those skilled in the art, that the example embodiments of the present subject matter may be practiced without these specific details.
In various example embodiments, a computing device, such as a mobile computing device having a touchscreen display, can display an electronic document having a first portion and a second portion. The axis or direction of navigation of the electronic document corresponds to the orientation of the first and second portions; e.g., an electronic document having a first portion above a second portion defines a vertical axis of navigation (e.g., scroll direction), as according to an example embodiment. When the electronic document is initially displayed on the client device, the first portion may be displayed and the second portion may lie out of view, not displayed. As mentioned, a user may make a swipe gesture, e.g., swipe up, on the touchscreen along the axis of navigation, in a scroll direction, causing the second portion to be displayed (e.g., the first portion scrolls up and out of view, and the second portion scrolls into view from the bottom of the touchscreen display).
The second portion includes a gesture trigger, such as a modification trigger, that is configured to, upon execution of the trigger, minimize or otherwise remove the electronic document from the touchscreen display. The gesture trigger may further be configured to, upon execution of the trigger, perform further actions, such as subscribing to a series of electronic documents or submitting a transaction. In an example embodiment, the gesture trigger is triggered when a user swipes along a direction of navigation, on the second portion, through the touchscreen display.
With reference to
series can be all posts from an individual user that user 199 can receive and display on client device 106. The posts may be ephemeral and automatically be removed from display or deleted from client device 106 after a specified time. Similarly, electronic documents may also be part of a series in that they all come from the same source (e.g., same user, same publisher) or are otherwise identified as part of a specific series through a common identifier (e.g., a company name, post series name).
In various implementations, the client device 106 includes a computing device that includes at least a display and communication capabilities that provide access to the network-based publishing system 104 via the network 102. The client device 106 includes, but is not limited to, a remote device, work station, computer, general purpose computer, Internet appliance, hand-held device, wireless device, portable device, wearable computer, cellular or mobile phone, Personal Digital Assistant (PDA), smart phone, tablet, ultrabook, netbook, laptop, desktop, multi-processor system, microprocessor-based or programmable consumer electronic, game consoles, set-top box, network Personal Computer (PC), mini-computer, and so forth. In an example embodiment, the client device 106 includes one or more of a touch screen, accelerometer, gyroscope, biometric sensor, camera, microphone, Global Positioning System (GPS) device, and the like.
The client device 106 communicates with the network 102 via a wired or wireless connection. For example, one or more portions of the network 102 includes 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, a wireless network, a Wireless Fidelity (WI-FI®) network, a Worldwide Interoperability for Microwave Access (WiMax) network, another type of network, or any suitable combination thereof.
As discussed above, in some example embodiments, the client device 106 includes one or more of the applications such as post series client application 110. In some implementations, the post series client application 110 includes various components operable to present information to the user 199 and communicate with network-based publishing system 104 as discussed in further detail below.
The post series client application 110 may be implemented as a standalone application executed on top of the operating system of client device 106, as according to some example embodiments. In some example embodiments, the post series client application 110 runs within a web client (e.g., browser) on the client device 106 to access the various systems of the networked system 104 via the web interface supported by a web server 116. Similarly, according to some example embodiments, the post series client application 110 accesses the various services and functions provided by the network-based publishing system 104 via a programmatic interface provided by an Application Program Interface (API) server 114.
Users (e.g., the user 199) can include a person, a machine, or other means of interacting with the client device 106. In some example embodiments, the user is not part of the network architecture 100, but interacts with the network architecture 100 via the client device 106 or another means. For instance, the user provides input (e.g., touch screen input or alphanumeric input) to the client device 106 and the input is communicated to the network-based publishing system 104 via the network 102. In this instance, the network-based publishing system 104, in response to receiving the input from the user, communicates information to the client device 106 via the network 102 to be presented to the user. In this way, the user can interact with the network-based publishing system 104 using the client device 106.
The API server 114 and the web server 116 are coupled to, and provide programmatic and web interfaces respectively to, one or more application server 118. The application server 118 can host an electronic post publication system 124 that includes one or more modules or applications, each of which can be embodied as hardware, software, firmware, or any combination thereof. The application server 118 is, in turn, shown to be coupled to one or more database servers 120 that facilitate access to one or more information storage repositories or database(s) 122. In an example embodiment, the database(s) 122 are storage devices that store information to be posted (e.g., posts, electronic documents, series thereof) via the electronic post publication system 124. The database(s) 122 store subscription information, payment information, inventory information, order information, and user information (e.g., user profile data, username/password, preferences of user 199) to perform the operations discussed below.
Additionally, a post series generator app 128, executing on third party server 108, is shown as having programmatic access to the network-based publishing system 104 via the programmatic interface provided by the API server 114. The post series generator app 128 is, according to some example embodiments, an application configured to publish posts (e.g., ephemeral posts) and electronic documents to the electronic post publication system 124 for publication to one or more post series client applications 110 of subscribing users.
Further, while the client-server-based network architecture 100 shown in
The interface engine 200 is configured (e.g., by software) to interface the post series client application 110 with the client device 106. In some example embodiments, the client device 106 implements a native operating system having a library of interface objects and look-and-feel specifications. For example, the client device 106 may be a mobile phone or smartphone, and the native operating system may be a mobile native operating system that can download applications or “apps” from an app store for local execution.
Users, such as user 199, may interact with the downloaded apps through a touchscreen display of the client device 106. In some example embodiments, the operating system of the client device 106 includes native functionality to receive user input and interpret user interactions through the touchscreen display. The native operating system may forward the interpreted user interactions to interface engine 200, for example, when the user interaction involves selection or manipulation of objects in a user interface of the post series client application 110. The interface engine 200 may receive the interpreted user interactions and complete operations in concert with the other engines of the post series client application 110. Still, in some example embodiments, the interface engine 200 is configured to natively receive and interpret user interactions as gestures in place of the client device 106; such as, for example, in implementations where the client device 106 does not include such native functionality.
The display engine 205 is responsible for displaying the user interface elements in conjunction with the other engines in the post series client application 110. For example, in response to a user selecting (e.g., clicking, tapping, or tapping-and-holding) an icon for an electronic document, the display engine 205 may receive a gesture notification from the interface engine 200 that the electronic document icon has been selected and, in response, the display engine 205 may generate a display of the selected elements on the display of the client device 106.
The post series engine 210 is responsible for managing the posts, which may include electronic documents or other types of posts, such as ephemeral posts. In some example embodiments, ephemeral posts have a smaller file size than electronic documents, though both electronic documents and ephemeral posts may be only temporarily accessible through the client device 106, as discussed in further detail below. The electronic documents may have one or more portions (e.g., top portion, middle portion, bottom portion) that a user can scroll or navigate to along a direction of navigation; for example, where the electronic document has a total display size (e.g., pixel size) that is larger than the available screen size (e.g., pixel screen size) of the display screen of the client device 106. In those implementations, the display engine 205 may receive one or more navigation gestures from the interface engine 200. The navigation gestures may include one or more of the following: swipes, drag-and-hold in a direction, double tap on edge of document to navigate in the direction of the edge, and other navigation interactions. Responsive to the received navigation gestures, the display engine 205 may scroll or navigate to a portion of the electronic document that is not currently viewable or displayed on the display screen of the client device 106.
The trigger engine 215 is responsible for managing the trigger actions of the post series client application 110. In some example embodiments, the trigger engine 215 activates a trigger (e.g., a modification trigger), in response to portions of an electronic document being displayed. The trigger engine 215 is further configured to execute the trigger. The trigger specifies a function for handling by the action engine 220. The function specifies one or more actions to be performed.
The action engine 220 is configured to perform one or more actions in response to the trigger engine 215 executing the trigger. In particular, according to at least one example embodiment, in executing the trigger, the trigger engine 215 specifies a function configured to perform different actions, such as terminating, closing, or minimizing the displayed electronic documented, creating a subscription request, and transmitting the subscription request. In some example embodiments, the trigger is configured to direct or redirect the client device 106 to a website upon the trigger being executed. In some example embodiments, the trigger is configured to, upon the trigger being executed, retrieve content (e.g., electronic documents) that is similar to the current electronic document. The similar content may be retrieved from the e-post publication system 124. Further, in some example embodiments, the similar content is retrieved from third party servers, such as third party server 108. The similar content may then be stored by the post series client application 110 for later display, or may automatically be displayed upon being retrieved.
In some example embodiments, the trigger is configured to, upon the trigger being executed, start a communication with a chat-bot or human agent of the provider of the electronic document or the series. In some example embodiments, the trigger is configured via the executable code to, upon the trigger being executed, submit a search to a search engine and display results. In those example embodiments, the executable code may specify a search string and a search engine server to perform the search upon the trigger being executed. The search string may include or otherwise specify keywords that are in the electronic document. For example, the electronic document may discuss ideas for things to do in a given city, e.g., New York City, and the trigger may be configured to search for flights to New York City, upon the user 199 swiping up. Once the gesture is received, the action engine 220 causes the client device 110 to transmit the search string to a search engine or flight website, and the results are returned for display on client device 110, as according to some example embodiments. Accordingly, the trigger can be configured to perform other client device or network communication operations in a similar manner (e.g., configuring the executable code to perform the desired operation).
At operation 315, in response to receiving the first gesture on the first portion of the electronic document, the display engine 205 displays a second portion of the electronic document. In some example embodiments, the display engine 205 displays the second portion of the electronic document using a scrolling transition (e.g., sliding the first portion off display while sliding the second portion onto the display). Other transitions, such as panning, sliding, fading in/out, may be similarly implemented to display the second portion of the electronic document.
At operation 320, the interface engine 200 receives an indication that a second gesture was made on a second portion of the electronic document. In some example embodiments, the information is generated from the native operating system of the client device 106.
As illustrated, operations 330, 335, and 340 may be included as part of a trigger operation 325. In some example embodiments, the trigger operation 325 is executed when the second portion of the electronic document is displayed and a swipe up gesture is received on the second portion. The direction “up” may be relative to the orientation of the client device 106 or the orientation of the displayed application, where for example, the application display has been rotated 180 degrees responsive to the client device 106 being rotated.
Continuing at operation 330, in response to receiving the second gesture on the second portion, the display engine 205 collapses (e.g., minimizes) the interface of the electronic document. In some example embodiments, the collapse of the interface of the electronic document includes removing from display the first portion, the second portion, and any other portions included within the body of the electronic document. Further, in some example embodiments, the collapsing of the interface of the electronic document includes removing from display the one or more portions and minimizing the electronic document to an icon within a primary application display area of the post series client application 110.
At operation 335, the action engine 220 generates a subscription request. In some example embodiments, the subscription request includes information such as the time at which the second gesture was received (e.g., operating system time of client device 106, time of receipt of the gesture information by interface engine 200), user data (e.g., username/password), verification tokens, client ID, network ID, payment information that may be included along with the subscription request. At operation 340, the action engine 220 transmits the subscription request to the interface engine 200, which transmits the subscription request through network 102 to API server 114 to application server 118 and finally to the destination, the electronic post publication system 124. As described in further detail below, the electronic post publication system 124 may use the data in the subscription request to update information (e.g., subscription information) for user 199 in database 122 via database server 120.
At operation 345, the display engine 205 may automatically display future posts or electronic documents received from the electronic post publication system 124. In some example embodiments, the posts received at operation 345 are posts or electronic documents published after the point in time in which the second gesture was received at operation 320. The display operations of operation 345 may be automatically configured so that the client/server exchange patterns are reversed. For example, the one or more servers 118 may initiate communications with the post series client application 110 by pushing future posts or electronic documents to the client device 106 for automatic download and/or display.
As discussed, at operation 320, the interface engine 200 receives an indication that a gesture has been received through the display screen of the client device 106. The gesture may be in any direction, e.g., up/down, right/left with respect to the orientation of the client device 106 or displayed application.
At operation 410, the trigger engine 215 determines whether the second portion of the electronic document is currently being displayed on the client device 106. If the second portion of the electronic document is not displayed (e.g., the first portion of the electronic document is being displayed), then at operation 415, the trigger is not executed. Alternately, going back to operation 410, if it is determined that the second portion of the electronic is being displayed, then at operation 325, the trigger is executed by the trigger engine 215, thereby causing operations 330, 335, and 340 to be performed, as discussed above.
In some example embodiments, the operation of activating the trigger at operation 505 is performed by loading executable code into a memory portion of the client device 106 in response to displaying the second portion. For example, the second portion can include embedded trigger code that activates the trigger when the second portion is displayed or rendered on the post series client application 110. In some example embodiments, loading the second portion of the electronic document loads a control object into the memory of the client device 106. The control object is managed by the client device 110 operating system, and is included natively as a feature that applications built for the client device 110 operation system can invoke, as according to some example embodiments. In those example embodiments, the control object activates and awaits receipt of gestures in a specified direction to execute the trigger. For example, the specified direction may be along the direction of navigation, e.g., an upward swipe.
At operation 320, the interface engine 200 receives an indication from the client device 106 that the user of the client device 106 has made a gesture through the display screen. At operation 515, the trigger engine 215 determines whether the received gesture is in the specified direction of navigation. If the gesture is not made in the direction of navigation, then at operation 520, the trigger is not executed. If it is determined at operation 515 that the gesture received at operation 510 is in the direction specified, then the trigger engine 215 executes the trigger at operation 525, thereby causing operations 330, 335, and 340 to be performed, as discussed above. After the trigger is executed, at operation 345, the display engine 205 may automatically download and display future posts or electronic documents received from the electronic post publication system 124.
At operation 605, the action engine 220 identifies data for inclusion in the subscription request. The information may include a timestamp and client data. The timestamp is identified by looking up current client device 106 time or determining the time when the gesture was performed, or determining the time when an indication of the gesture being performed is received by interface engine 200. The client data includes information needed to submit a subscription request, including one or more of the following: user identification, verification information (e.g., username, password, or authentication token), identification of the series of posts to subscribe to, and type of subscription (e.g., levels of service, frequency of publication, etc.), payment information for paid subscription, or other data needed to subscribe.
At operation 610, the action engine 220 uses the information gathered at operation 605 and any network information (e.g., server address, requisite API data) needed to generate the subscription request. The generated subscription request is then transferred from the client device 106 to the application server 118.
At operation 615, the application server 118 receives the subscription request and uses the data in the subscription request to update a database, such as local database 122, with the timestamp data and the client data of operation 605. At operation 620, application server 118 receives other series posts, such as additional electronic documents or other ephemeral posts for publication. In some example embodiments, the additional electronic documents or ephemeral posts may be received from third party server 108 through a post series generator app 128. The electronic post publication system 124 receives the one or more additional series posts from third party server 108 and stores them in database 122 via database server 120. A post may be identified via the post series engine 210 as belonging to a particular series via a series identifier tag or data value. Series from different third party servers may be stored by their respective identifiers in database 122 by the electronic post publication system 124.
At operation 625, the application server 118 transmits posts having newer timestamps for automatic download by client device 106 in response to a request checking for new posts from client device 106 or as part of a push operation.
At operation 630, the client device 106 may automatically download the series posts. For example, the post series client application 110 may be configured to automatically download the newer posts without user interaction. In particular, when the post series client application 110 is initiated (e.g., starts-up) on client device 106, the post series engine 210 may send a request to electronic post publication system 124 to check for any new posts published since the post series client application 110 was last closed. Further, in some example embodiments, the automatic download of operation 630 may be implemented as a push operation, where the client device 106 is configured to automatically download the pushed publications while the client device 106 is running. Further, in some example embodiments, when the post series client application 110 is closed or not running, the native operating system of the client device 106 may still receive notification of the push operation from application server 118 and create a push notification on the display of the client device 106 and/or download the new posts as a background process so that when the post series client application 110 is initiated, the newer posts may be retrieved from local memory of the client device 106.
At operation 635, the client device 106 may automatically display the newer series posts upon receipt. In some example embodiments, the client device 106 may download the newer posts and not display the content of the posts (e.g., first portion, second portion), but instead show an icon for the post (e.g., thumbnail) that indicates new posts have been downloaded. Example indications may include a visible modification of the default icon (e.g., read posts may be grayed out, but newer unread posts may be lighter or more vibrantly colored), animations, or visible overlay tags.
As illustrated, the post series client application 110 includes a display of a plurality of electronic documents represented by icons 777A-C in a electronic document display area 707, as according to an example embodiment. The plurality of electronic documents may be populated within display area 707 according to usage data of user 199. The usage data may be collected and stored by client device 106 as user 199 uses post series client application 110. The usage data, for example, may include one or more of the following: most commonly accessed electronic documents, most commonly accessed ephemeral posts, the type of content in the accessed electronic documents or ephemeral posts, geographical location data collected from the GPS sensor of client device 106 (e.g., location data indicating that user 199 is near London, New York City, etc.), or past subscriptions to series posts. In some example embodiments, the user 199 may navigate an electronic document catalog from which the user 199 may browse through different electronic documents for selection and subscription.
It is appreciated that the actual content of the documents (e.g., first portion, second portion) may not be displayed in the electronic document display area but rather be linked to by a corresponding icon for each document or documents in the series. For example, “Cheshire Social” may correspond to a series of electronic documents that are represented by an icon 777A; “The Treacle Well” may correspond to a series of electronic documents that are represented by an icon 777B; and “Hatter & Hare” may correspond to a series of electronic documents represented by an icon 777C. Though only three series and corresponding icons 777A-C are depicted, it is appreciated that any number of series and icons may be displayed within display area 707, for example, in an alternating manner (e.g., carousel scroll). When the user 199 selects one of the icons 777A-C, the post series engine 210 retrieves the newest electronic document of the series from local memory of the client device 106 and loads it on the touchscreen display 700. In some example embodiments, if the newest electronic document has not been downloaded to local memory of the client device 106, the post series client application 110 may transmit a server request to electronic post publication system 124 requesting the latest electronic documents.
Further, according to some example embodiments, the post series client application 110 also displays a plurality of ephemeral posts in the ephemeral display area 715. When user 199 selects one of the posts, the post series engine 210 may retrieve the latest post from local memory or electronic post publication system 124 and display it. The ephemeral posts may display an image, a video, and/or a text for a preconfigured duration of time before automatically being deleted or removed from the display interface of the touchscreen display 700. The duration of time may be preconfigured by the creator of the post (e.g., another user), the post series client application 110 or the electronic post publication system 124. As with the electronic documents, each ephemeral post may belong to a series from other users. For example, all posts from the user “Dromio” may be considered as part of the same series.
Continuing, assuming user 199 selects icon 777A, the interface engine 200 will receive an indication from client device 106 that the user 199 has made a selection of the icon 777A, which will trigger the post series engine 210 to retrieve the electronic document corresponding to icon 777A and cause the display engine 205 to display the electronic document as illustrated in
In some example embodiments, each portion (e.g., 710A0, 710A1, and 710A2) of the electronic document 710A fills the entire the area of a primary application interface area 111 (e.g., an area of the touchscreen display 700 where the running application is displayed, excluding the status bar along the top). The top portion 710A0 of the interface includes a title, descriptive text, and an action element 720, according to an example embodiment. The action element 720, in some example embodiments, is a non-active element of the multi-portion electronic document. The action element 720 may not be linked or associated with a control object but rather includes instructions that the user 199 may use to navigate through the multi-portion electronic document.
The subscription operation is then sent out before, after, and/or during the transition from the second portion 710A2 to the home screen, as according to some example embodiments. As illustrated in
Further, responsive to the subscription request being received, the subscribed-to series may be placed in first (e.g., left most) among the plurality of electronic document icons 777A-C in display area 707. Further, responsive to the subscription request, the post series client application 110 may receive pushes from ephemeral posts of the series. For example, as illustrated, the “Cheshire Ephemeral Post” 750 is associated with the series posts and may be automatically displayed in the ephemeral display area 715.
The modification trigger may also be used to collapse an electronic document and perform other actions via the action engine 220, such as ordering a sample of an item discussed in an electronic document, as according to an example embodiment.
Continuing, at operation 830, the display engine 205 collapses the interface of the electronic document, for example by removing from the touchscreen display 700 a viewing of the first, second or any other portion of the displayed electronic document. At operation 835, the action engine 220 receives from the trigger engine 215 an indication that the trigger has been executed. For example, the trigger engine 215 references a specific function managed by the action engine 220. Accordingly, at operation 835, the action engine 220 executes the content of the function and generates a sample request for an item discussed in the electronic document. At operation 840, the action engine 220 transmits, via the interface engine 200, the sample request through the network 102 for fulfillment processing by the electronic post publication system 124 and/or the third party server 108.
At operation 910, the action engine 220 generates an order or sample request. At operation 915, the application server 118 receives the sample request for the item. At operation 920, the application server 118 may transmit a sample request to an order completion system that clears the payment using user payment information and submits an item order. In some example embodiments, the clearing of the payment transaction is performed by the third party server 108 using payment information provided by the application server 118. In some example embodiments, the application server 118 is configured to clear payments internally within the network-based publishing system 104 using payment information received from the client device 106. For example, the client device 106 may be part of an application marketplace or app store. The application server 118 may have pre-approved authority from the user 199 to complete transactions using the payment information of user 199. Once the order has been submitted by the application server 118, the application server 118 generates a display notification at operation 925. At operation 935, the client device 106 receives the display notification and displays the notification on the display device, e.g., touchscreen display 700, of the client device 106.
Though three example portions of an electronic document are disclosed here for purposes of explanation, it is appreciated that an electronic document may include any number of portions (e.g., two, three, ten, etc.). In those embodiments, the terms “top,” “first,” and “second portions” may be referenced per the number and location within the electronic document. For example, a seven-portioned electronic document may have its portions referenced as first portion (top), a plurality of middle portions, the second to last portion may be the sixth portion, and the last portion may be the seventh portion. In those embodiments, the operations involving the discussed second portion (e.g., determination operation 410 in
Certain embodiments are described herein as including logic or a number of components, modules, or mechanisms. Modules can constitute either software modules (e.g., code embodied on a machine-readable medium) or hardware modules. A “hardware module” is a tangible unit capable of performing certain operations and can be configured or arranged in a certain physical manner. In various example embodiments, one or more computer systems (e.g., a standalone computer system, a client computer system, or a server computer system) or one or more hardware modules of a computer system (e.g., a processor or a group of processors) can be configured by software (e.g., an application or application portion) as a hardware module that operates to perform certain operations as described herein.
In some example embodiments, a hardware module can be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware module can include dedicated circuitry or logic that is permanently configured to perform certain operations. For example, a hardware module can be a special-purpose processor, such as a Field-Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC). A hardware module may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, a hardware module can include software executed by a general-purpose processor or other programmable processor. Once configured by such software, hardware modules become specific machines (or specific components of a machine) uniquely tailored to perform the configured functions and are no longer general-purpose processors. It will be appreciated that the decision to implement a hardware module mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) can be driven by cost and time considerations.
Accordingly, the phrase “hardware module” should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. As used herein, “hardware-implemented module” refers to a hardware module. Considering embodiments in which hardware modules are temporarily configured (e.g., programmed), each of the hardware modules need not be configured or instantiated at any one instance in time. For example, where a hardware module includes a general-purpose processor configured by software to become a special-purpose processor, the general-purpose processor may be configured as respectively different special-purpose processors (e.g., including different hardware modules) at different times. Software accordingly configures a particular processor or processors, for example, to constitute a particular hardware module at one instance of time and to constitute a different hardware module at a different instance of time.
Hardware modules can provide information to, and receive information from, other hardware modules. Accordingly, the described hardware modules can be regarded as being communicatively coupled. Where multiple hardware modules exist contemporaneously, communications can be achieved through signal transmission (e.g., over appropriate circuits and buses) between or among two or more of the hardware modules. In embodiments in which multiple hardware modules are configured or instantiated at different times, communications between such hardware modules may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware modules have access. For example, one hardware module can perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware module can then, at a later time, access the memory device to retrieve and process the stored output. Hardware modules can also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information).
The various operations of example methods described herein can be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors constitute processor-implemented modules that operate to perform one or more operations or functions described herein. As used herein, “processor-implemented module” refers to a hardware module implemented using one or more processors.
Similarly, the methods described herein can be at least partially processor-implemented, with a particular processor or processors being an example of hardware. For example, at least some of the operations of a method can be performed by one or more processors or processor-implemented modules. Moreover, the one or more processors may also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), with these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., an Application Program Interface (API)).
The performance of certain of the operations may be distributed among the processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processors or processor-implemented modules can be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example embodiments, the processors or processor-implemented modules are distributed across a number of geographic locations.
The modules, methods, applications and so forth described in conjunction with
Software architectures are used in conjunction with hardware architectures to create devices and machines tailored to particular purposes. For example, a particular hardware architecture coupled with a particular software architecture will create a mobile device, such as a mobile phone, tablet device, and the like. A slightly different hardware and software architecture may yield a smart device for use in the “internet of things” while yet another combination produces a server computer for use within a cloud computing architecture. Not all combinations of such software and hardware architectures are presented here as those of skill in the art can readily understand how to implement the present subject matter in different contexts from the disclosure contained herein.
Additionally, or alternatively, the instruction 1116 can implement the interface engine 200, display engine 205, post series engine 210, trigger engine 215, and action engine 220 of
The machine 1100 can include processors 1110, memory/storage 1130, and I/O components 1150, which can be configured to communicate with each other such as via a bus 1102. In an example embodiment, the processors 1110 (e.g., a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) processor, a Complex Instruction Set Computing (CISC) processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Radio-Frequency Integrated Circuit (RFIC), another processor, or any suitable combination thereof) can include, for example, processor 1112 and processor 1114 that may execute instructions 1116. The term “processor” is intended to include multi-core processor that may include two or more independent processors (sometimes referred to as “cores”) that can execute instructions contemporaneously. Although
The memory/storage 1130 can include a memory 1132, such as a main memory, or other memory storage, and a storage unit 1136, both accessible to the processors 1110 such as via the bus 1102. The storage unit 1136 and memory 1132 store the instructions 1116 embodying any one or more of the methodologies or functions described herein. The instructions 1116 can also reside, completely or partially, within the memory 1132, within the storage unit 1136, within at least one of the processors 1110 (e.g., within the processor's cache memory), or any suitable combination thereof, during execution thereof by the machine 1100. Accordingly, the memory 1132, the storage unit 1136, and the memory of the processors 1110 are examples of machine-readable media.
As used herein, the term “machine-readable medium” means a device able to store instructions and data temporarily or permanently and may include, but is not be limited to, random-access memory (RAM), read-only memory (ROM), buffer memory, flash memory, optical media, magnetic media, cache memory, other types of storage (e.g., Erasable Programmable Read-Only Memory (EEPROM)) or any suitable combination thereof. The term “machine-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, or associated caches and servers) able to store instructions 1116. The term “machine-readable medium” shall also be taken to include any medium, or combination of multiple media, that is capable of storing instructions (e.g., instructions 1116) for execution by a machine (e.g., machine 1100), such that the instructions, when executed by one or more processors of the machine 1100 (e.g., processors 1110), cause the machine 1100 to perform any one or more of the methodologies described herein. Accordingly, a “machine-readable medium” refers to a single storage apparatus or device, as well as “cloud-based” storage systems or storage networks that include multiple storage apparatus or devices. The term “machine-readable medium” excludes signals per se.
The I/O components 1150 can include a wide variety of components to receive input, provide output, produce output, transmit information, exchange information, capture measurements, and so on. The specific I/O components 1150 that are included in a particular machine will depend on the type of machine. For example, portable machines such as mobile phones will likely include a touch input device or other such input mechanisms, while a headless server machine will likely not include such a touch input device. It will be appreciated that the I/O components 1150 can include many other components that are not shown in
In further example embodiments, the I/O components 1150 can include biometric components 1156, motion components 1158, environmental components 1160, or position components 1162 among a wide array of other components. For example, the biometric components 1156 can include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye tracking), measure biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram based identification), and the like. The motion components 1158 can include acceleration sensor components (e.g., an accelerometer), gravitation sensor components, rotation sensor components (e.g., a gyroscope), and so forth. The environmental components 1160 can include, for example, illumination sensor components (e.g., a photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., a barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., infrared sensors that detect nearby objects), gas sensor components (e.g., machine olfaction detection sensors, gas detection sensors to detect concentrations of hazardous gases for safety or to measure pollutants in the atmosphere), or other components that may provide indications, measurements, or signals corresponding to a surrounding physical environment. The position components 1162 can include location sensor components (e.g., a Global Positioning System (GPS) receiver component), altitude sensor components (e.g., altimeters or barometers that detect air pressure from which altitude may be derived), orientation sensor components (e.g., magnetometers), and the like.
Communication can be implemented using a wide variety of technologies. The I/O components 1150 may include communication components 1164 operable to couple the machine 1100 to a network 1180 or devices 1170 via a coupling 1182 and a coupling 1172, respectively. For example, the communication components 1164 include a network interface component or other suitable device to interface with the network 1180. In further examples, communication components 1164 include wired communication components, wireless communication components, cellular communication components, Near Field Communication (NFC) components, BLUETOOTH® components (e.g., BLUETOOTH® Low Energy), WI-FI® components, and other communication components to provide communication via other modalities. The devices 1170 may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a Universal Serial Bus (USB)).
Moreover, the communication components 1164 can detect identifiers or include components operable to detect identifiers. For example, the communication components 1164 can include Radio Frequency Identification (RFID) tag reader components, NFC smart tag detection components, optical reader components (e.g., an optical sensor to detect one-dimensional bar codes such as a Universal Product Code (UPC) bar code, multi-dimensional bar codes such as a Quick Response (QR) code, Aztec Code, Data Matrix, Dataglyph.RTM., MaxiCode, PDF417, Ultra Code, Uniform Commercial Code Reduced Space Symbology (UCC RSS)-2D bar codes, and other optical codes), acoustic detection components (e.g., microphones to identify tagged audio signals), or any suitable combination thereof. In addition, a variety of information can be derived via the communication components 106, such as location via Internet Protocol (IP) geo-location, location via WI-FI.RTM. signal triangulation, location via detecting a BLUETOOTH.RTM. or NFC beacon signal that may indicate a particular location, and so forth.
In various example embodiments, one or more portions of the network 1180 can be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, a WI-FI® network, another type of network, or a combination of two or more such networks. For example, the network 1180 or a portion of the network 1180 may include a wireless or cellular network, and the coupling 1182 may be a Code Division Multiple Access (CDMA) connection, a Global System for Mobile communications (GSM) connection, or other type of cellular or wireless coupling. In this example, the coupling 1182 can implement any of a variety of types of data transfer technology, such as Single Carrier Radio Transmission Technology (1×RTT), Evolution-Data Optimized (EVDO) technology, General Packet Radio Service (GPRS) technology, Enhanced Data rates for GSM Evolution (EDGE) technology, third Generation Partnership Project (3GPP) including 3G, fourth generation wireless (4G) networks, Universal Mobile Telecommunications System (UMTS), High Speed Packet Access (HSPA), Worldwide Interoperability for Microwave Access (WiMAX), Long Term Evolution (LTE) standard, others defined by various standard setting organizations, other long range protocols, or other data transfer technology.
The instructions 1116 can be transmitted or received over the network 1180 using a transmission medium via a network interface device (e.g., a network interface component included in the communication components 1164) and utilizing any one of a number of well-known transfer protocols (e.g., Hypertext Transfer Protocol (HTTP)). Similarly, the instructions 1116 can be transmitted or received using a transmission medium via the coupling 1172 (e.g., a peer-to-peer coupling) to devices 1170. The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding, or carrying the instructions 1116 for execution by the machine 1100, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.
Throughout this specification, plural instances may implement components, operations, or structures described as a single instance. Although individual operations of one or more methods are illustrated and described as separate operations, one or more of the individual operations may be performed concurrently, and nothing requires that the operations be performed in the order illustrated. Structures and functionality presented as separate components in example configurations may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components. These and other variations, modifications, additions, and improvements fall within the scope of the subject matter herein.
Although an overview of the present subject matter has been described with reference to specific example embodiments, various modifications and changes may be made to these embodiments without departing from the broader scope of embodiments of the present disclosure. The embodiments illustrated herein are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed. Other embodiments may be used and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. The Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.
As used herein, the term “or” is construed in the Boolean sense, e.g., “A or B” may include A, may include B, or may include A and B. Moreover, plural instances may be provided for resources, operations, or structures described herein as a single instance. Additionally, boundaries between various resources, operations, modules, engines, and data stores are somewhat arbitrary, and particular operations are illustrated in a context of specific illustrative configurations. Other allocations of functionality are envisioned and may fall within a scope of various embodiments of the present disclosure. In general, structures and functionality presented as separate resources in the example configurations may be implemented as a combined structure or resource. Similarly, structures and functionality presented as a single resource may be implemented as separate resources. These and other variations, modifications, additions, and improvements fall within a scope of embodiments of the present disclosure as represented by the appended claims. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.
This application is a continuation of and claims the benefit of priority of U.S. patent application Ser. No. 16/597,797, filed Oct. 9, 2019, now issued as U.S. Pat. No. 10,884,616, which is a continuation of and claims the benefit of priority of U.S. patent application Ser. No. 15/169,288, filed on May 31, 2016, now issued as U.S. Pat. No. 10,474,353, which is hereby incorporated by reference herein in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5754939 | Herz et al. | May 1998 | A |
| 6038295 | Mattes | Mar 2000 | A |
| 6158044 | Tibbetts | Dec 2000 | A |
| 6167435 | Druckenmiller et al. | Dec 2000 | A |
| 6205432 | Gabbard et al. | Mar 2001 | B1 |
| 6310694 | Okimoto et al. | Oct 2001 | B1 |
| 6484196 | Maurille | Nov 2002 | B1 |
| 6487586 | Ogilvie et al. | Nov 2002 | B2 |
| 6665531 | Soderbacka et al. | Dec 2003 | B1 |
| 6701347 | Ogilvie | Mar 2004 | B1 |
| 6711608 | Ogilvie | Mar 2004 | B1 |
| 6757713 | Ogilvie et al. | Jun 2004 | B1 |
| 6980909 | Root et al. | Dec 2005 | B2 |
| 7124164 | Chemtob | Oct 2006 | B1 |
| 7149893 | Leonard et al. | Dec 2006 | B1 |
| 7173651 | Knowles | Feb 2007 | B1 |
| 7243163 | Friend et al. | Jul 2007 | B1 |
| 7278168 | Chaudhury et al. | Oct 2007 | B1 |
| 7356564 | Hartselle et al. | Apr 2008 | B2 |
| 7376715 | Cunningham et al. | May 2008 | B2 |
| 7411493 | Smith | Aug 2008 | B2 |
| 7478402 | Christensen et al. | Jan 2009 | B2 |
| 7496347 | Puranik | Feb 2009 | B2 |
| 7519670 | Hagale et al. | Apr 2009 | B2 |
| 7535890 | Rojas | May 2009 | B2 |
| 7607096 | Oreizy et al. | Oct 2009 | B2 |
| 7703140 | Nath et al. | Apr 2010 | B2 |
| 7912896 | Wolovitz et al. | Mar 2011 | B2 |
| 8131597 | Hudetz | Mar 2012 | B2 |
| 8170957 | Richard | May 2012 | B2 |
| 8199747 | Rojas et al. | Jun 2012 | B2 |
| 8214443 | Hamburg | Jul 2012 | B2 |
| 8238947 | Lottin et al. | Aug 2012 | B2 |
| 8244593 | Klinger et al. | Aug 2012 | B2 |
| 8312097 | Siegel et al. | Nov 2012 | B1 |
| 8332475 | Rosen et al. | Dec 2012 | B2 |
| 8570907 | Garcia, Jr. et al. | Oct 2013 | B2 |
| 8718333 | Wolf et al. | May 2014 | B2 |
| 8724622 | Rojas | May 2014 | B2 |
| 8745132 | Obradovich | Jun 2014 | B2 |
| 8874677 | Rosen et al. | Oct 2014 | B2 |
| 8909679 | Root et al. | Dec 2014 | B2 |
| 8909714 | Agarwal et al. | Dec 2014 | B2 |
| 8909725 | Sehn | Dec 2014 | B1 |
| 8914752 | Spiegel | Dec 2014 | B1 |
| 8995433 | Rojas | Mar 2015 | B2 |
| 9040574 | Wang et al. | May 2015 | B2 |
| 9055416 | Rosen et al. | Jun 2015 | B2 |
| 9083770 | Drose et al. | Jul 2015 | B1 |
| 9094137 | Sehn et al. | Jul 2015 | B1 |
| 9100806 | Rosen et al. | Aug 2015 | B2 |
| 9100807 | Rosen et al. | Aug 2015 | B2 |
| 9113301 | Spiegel et al. | Aug 2015 | B1 |
| 9148424 | Yang | Sep 2015 | B1 |
| 9191776 | Root et al. | Nov 2015 | B2 |
| 9204252 | Root | Dec 2015 | B2 |
| 9224095 | Booth et al. | Dec 2015 | B2 |
| 9225805 | Kujawa et al. | Dec 2015 | B2 |
| 9225897 | Sehn et al. | Dec 2015 | B1 |
| 9237202 | Sehn | Jan 2016 | B1 |
| 9264463 | Rubinstein et al. | Feb 2016 | B2 |
| 9276886 | Samaranayake | Mar 2016 | B1 |
| 9294425 | Son | Mar 2016 | B1 |
| 9385983 | Sehn | Jul 2016 | B1 |
| 9396354 | Murphy et al. | Jul 2016 | B1 |
| 9407712 | Sehn | Aug 2016 | B1 |
| 9407816 | Sehn | Aug 2016 | B1 |
| 9430783 | Sehn | Aug 2016 | B1 |
| 9443227 | Evans et al. | Sep 2016 | B2 |
| 9482882 | Hanover et al. | Nov 2016 | B1 |
| 9482883 | Meisenholder | Nov 2016 | B1 |
| 9489661 | Evans et al. | Nov 2016 | B2 |
| 9491134 | Rosen et al. | Nov 2016 | B2 |
| 9532171 | Allen et al. | Dec 2016 | B2 |
| 9537811 | Allen et al. | Jan 2017 | B2 |
| 9560006 | Prado et al. | Jan 2017 | B2 |
| 9628950 | Noeth et al. | Apr 2017 | B1 |
| 9652896 | Jurgensen et al. | May 2017 | B1 |
| 9659244 | Anderton et al. | May 2017 | B2 |
| 9693191 | Sehn | Jun 2017 | B2 |
| 9705831 | Spiegel | Jul 2017 | B2 |
| 9742713 | Spiegel et al. | Aug 2017 | B2 |
| 9785796 | Murphy et al. | Oct 2017 | B1 |
| 9825898 | Sehn | Nov 2017 | B2 |
| 9854219 | Sehn | Dec 2017 | B2 |
| 9961520 | Brooks et al. | May 2018 | B2 |
| 10291573 | Ravishankar et al. | May 2019 | B2 |
| 10474353 | Burfitt | Nov 2019 | B2 |
| 10609036 | Allen et al. | Mar 2020 | B1 |
| 10884616 | Burfitt | Jan 2021 | B2 |
| 20020047868 | Miyazawa | Apr 2002 | A1 |
| 20020144154 | Tomkow | Oct 2002 | A1 |
| 20030052925 | Daimon et al. | Mar 2003 | A1 |
| 20030126215 | Udell | Jul 2003 | A1 |
| 20030217106 | Adar et al. | Nov 2003 | A1 |
| 20040100479 | Nakano et al. | May 2004 | A1 |
| 20040203959 | Coombes | Oct 2004 | A1 |
| 20050097176 | Schatz et al. | May 2005 | A1 |
| 20050198128 | Anderson | Sep 2005 | A1 |
| 20050223066 | Buchheit et al. | Oct 2005 | A1 |
| 20060242239 | Morishima et al. | Oct 2006 | A1 |
| 20060270419 | Crowley et al. | Nov 2006 | A1 |
| 20070038715 | Collins et al. | Feb 2007 | A1 |
| 20070064899 | Boss et al. | Mar 2007 | A1 |
| 20070073823 | Cohen et al. | Mar 2007 | A1 |
| 20070214216 | Carrer et al. | Sep 2007 | A1 |
| 20070233801 | Eren et al. | Oct 2007 | A1 |
| 20080055269 | Lemay et al. | Mar 2008 | A1 |
| 20080082941 | Goldberg et al. | Apr 2008 | A1 |
| 20080120409 | Sun et al. | May 2008 | A1 |
| 20080207176 | Brackbill et al. | Aug 2008 | A1 |
| 20080270938 | Carlson | Oct 2008 | A1 |
| 20080306826 | Kramer et al. | Dec 2008 | A1 |
| 20080313346 | Kujawa et al. | Dec 2008 | A1 |
| 20090013266 | Gandhi et al. | Jan 2009 | A1 |
| 20090042588 | Lottin et al. | Feb 2009 | A1 |
| 20090132453 | Hangartner et al. | May 2009 | A1 |
| 20100042948 | Kim et al. | Feb 2010 | A1 |
| 20100082427 | Burgener et al. | Apr 2010 | A1 |
| 20100131880 | Lee et al. | May 2010 | A1 |
| 20100185665 | Horn et al. | Jul 2010 | A1 |
| 20100306669 | Della Pasqua | Dec 2010 | A1 |
| 20110099507 | Nesladek et al. | Apr 2011 | A1 |
| 20110145564 | Moshir et al. | Jun 2011 | A1 |
| 20110202598 | Evans et al. | Aug 2011 | A1 |
| 20110213845 | Logan et al. | Sep 2011 | A1 |
| 20110286586 | Saylor et al. | Nov 2011 | A1 |
| 20110320373 | Lee et al. | Dec 2011 | A1 |
| 20120028659 | Whitney et al. | Feb 2012 | A1 |
| 20120117584 | Gordon | May 2012 | A1 |
| 20120184248 | Speede | Jul 2012 | A1 |
| 20120209921 | Adafin et al. | Aug 2012 | A1 |
| 20120209924 | Evans et al. | Aug 2012 | A1 |
| 20120254325 | Majeti et al. | Oct 2012 | A1 |
| 20120278692 | Shi | Nov 2012 | A1 |
| 20120304080 | Wormald et al. | Nov 2012 | A1 |
| 20130024808 | Rainisto | Jan 2013 | A1 |
| 20130071093 | Hanks et al. | Mar 2013 | A1 |
| 20130194301 | Robbins et al. | Aug 2013 | A1 |
| 20130290443 | Collins et al. | Oct 2013 | A1 |
| 20140032682 | Prado et al. | Jan 2014 | A1 |
| 20140122787 | Shalvi et al. | May 2014 | A1 |
| 20140201527 | Krivorot | Jul 2014 | A1 |
| 20140282096 | Rubinstein et al. | Sep 2014 | A1 |
| 20140325383 | Brown et al. | Oct 2014 | A1 |
| 20140359024 | Spiegel | Dec 2014 | A1 |
| 20140359032 | Spiegel et al. | Dec 2014 | A1 |
| 20140365349 | Kennon | Dec 2014 | A1 |
| 20150128014 | Monroe | May 2015 | A1 |
| 20150188873 | Halliday et al. | Jul 2015 | A1 |
| 20150193122 | Liu et al. | Jul 2015 | A1 |
| 20150199082 | Scholler et al. | Jul 2015 | A1 |
| 20150227602 | Ramu et al. | Aug 2015 | A1 |
| 20150269614 | Kramer | Sep 2015 | A1 |
| 20160085773 | Chang et al. | Mar 2016 | A1 |
| 20160085863 | Allen et al. | Mar 2016 | A1 |
| 20160086670 | Gross et al. | Mar 2016 | A1 |
| 20160099901 | Allen et al. | Apr 2016 | A1 |
| 20160170623 | Lewis et al. | Jun 2016 | A1 |
| 20160180887 | Sehn | Jun 2016 | A1 |
| 20160196584 | Franklin et al. | Jul 2016 | A1 |
| 20160277419 | Allen et al. | Sep 2016 | A1 |
| 20160321708 | Sehn | Nov 2016 | A1 |
| 20160359957 | Laliberte | Dec 2016 | A1 |
| 20160359987 | Laliberte | Dec 2016 | A1 |
| 20170161382 | Ouimet et al. | Jun 2017 | A1 |
| 20170263029 | Yan et al. | Sep 2017 | A1 |
| 20170287006 | Azmoodeh et al. | Oct 2017 | A1 |
| 20170295250 | Samaranayake et al. | Oct 2017 | A1 |
| 20170344246 | Burfitt | Nov 2017 | A1 |
| 20170374003 | Allen et al. | Dec 2017 | A1 |
| 20170374508 | Davis et al. | Dec 2017 | A1 |
| 20200249831 | Burfitt | Aug 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 2887596 | Jul 2015 | CA |
| 1093277 | Oct 2002 | CN |
| 109564500 | Apr 2019 | CN |
| 3465404 | Jun 2020 | EP |
| 20130024808 | Mar 2013 | KR |
| WO-2012000107 | Jan 2012 | WO |
| WO-2013008251 | Jan 2013 | WO |
| WO-2014194262 | Dec 2014 | WO |
| WO-2015192026 | Dec 2015 | WO |
| WO-2016054562 | Apr 2016 | WO |
| WO-2016065131 | Apr 2016 | WO |
| WO-2016112299 | Jul 2016 | WO |
| WO-2016179166 | Nov 2016 | WO |
| WO-2016179235 | Nov 2016 | WO |
| WO-2017176739 | Oct 2017 | WO |
| WO-2017176992 | Dec 2017 | WO |
| WO-2017210129 | Dec 2017 | WO |
| WO-2018005644 | Jan 2018 | WO |
| Entry |
|---|
| “1-Click—Wikipedia, the free encyclopedia”, [Online]. Retrieved from the Internet: <URL: https://en.wikipedia.org/wiki/1-Click>, (Accessed May 26, 2016), 3 pgs. |
| “U.S. Appl. No. 15/169,288, Non Final Office Action dated Oct. 18, 2018”, 13 pgs. |
| “U.S. Appl. No. 15/169,288, Notice of Allowance dated Jul. 2, 2019”, 9 pgs. |
| “U.S. Appl. No. 15/169,288, Response filed Mar. 18, 2019 to Non Final Office Action dated Oct. 18, 2018”, 16 pgs. |
| “U.S. Appl. No. 15/289,676, Final Office Action dated Jul. 15, 2019”, 20 pgs. |
| “U.S. Appl. No. 15/289,676, Non Final Office Action dated Oct. 25, 2018”, 16 pgs. |
| “U.S. Appl. No. 15/289,676, Notice of Allowance dated Nov. 18, 2019”, 18 pgs. |
| “U.S. Appl. No. 15/289,676, Response filed Apr. 24, 2019 to Non Final Office Action dated Oct. 25, 2018”, 21 pgs. |
| “U.S. Appl. No. 15/289,676, Response filed Oct. 15, 2019 to Final Office Action dated Jul. 15, 2019”, 24 pgs. |
| “U.S. Appl. No. 16/597,797, Corrected Notice of Allowability dated Oct. 19, 2020”, 2 pgs. |
| “U.S. Appl. No. 16/597,797, Notice of Allowance dated Sep. 2, 2020”, 16 pgs. |
| “U.S. Appl. No. 16/597,797, Preliminary Amendment filed Apr. 29, 2020”, 8 pgs. |
| “U.S. Appl. No. 16/800,868, Preliminary Amendment filed May 12, 2020”, 8 pgs. |
| “European Application Serial No. 17729970.9, Response filed Jul. 22, 2019 to Communication pursuant to Rules 161(1) and 162 EPC dated Jan. 10, 2019”, w/English Claims, 76 pgs. |
| “European Application Serial No. 20181733.5, Extended European Search Report dated Sep. 24, 2020”, 8 pgs. |
| “International Application Serial No. PCT/US2017/034782, International Preliminary Report on Patentability dated Dec. 13, 2018”, 9 pgs. |
| “International Application Serial No. PCT/US2017/034782, International Search Report dated Oct. 4, 2017”, 3 pgs. |
| “International Application Serial No. PCT/US2017/034782, Written Opinion dated Oct. 4, 2017”, 7 pgs. |
| “Korean Application Serial No. 10-2018-7038039, Notice of Preliminary Rejection dated Mar. 31, 2020”, w/ English translation, 9 pgs. |
| “Korean Application Serial No. 10-2018-7038039, Response filed Jun. 15, 2020 to Notice of Preliminary Rejection dated Mar. 31, 2020”, w/ English Claims, 26 pgs. |
| Bias, Lorena, et al., “Kim Kardashian Robbery Puts Spotlight on Celebrity Security”, USA Today, D.2. ProQuest., [Online] Retrieved from the Internet on Nov. 9, 2019: <URL: http://dialog.proquest.eom/professional/docview/1825640504?accountid=131444>, (Oct. 4, 2016), 4 pgs. |
| Castelluccia, Claude, et al., “EphPub: Toward robust Ephemeral Publishing”, 19th IEEE International Conference on Network Protocols (ICNP), (Oct. 17, 2011), 18 pgs. |
| Fajman, “An Extensible Message Format for Message Disposition Notifications”, Request for Comments: 2298, National Institutes of Health, (Mar. 1998), 28 pgs. |
| Leyden, John, “This SMS will self-destruct in 40 seconds”, [Online] Retrieved from the Internet: <URL: http://www.theregister.co.uk/2005/12/12/stealthtext/>, (Dec. 12, 2005), 1 pg. |
| Melanson, Mike, “This text message will self destruct in 60 seconds”, [Online] Retrieved from the Internet: <URL: http://readwrite.com/2011/02/11/this_text_message_will_self_destruct_in_60_seconds>, (Feb. 18, 2015), 4 pgs. |
| Sawers, Paul, “Snapchat for iOS Lets You Send Photos to Friends and Set How long They're Visible For”, [Online] Retrieved from the Internet: <URL: https://thenextweb.com/apps/2012/05/07/snapchat-for-ios-lets-you-send-photos-to-friends-and-set-how-long-theyre-visible-for/>, (May 7, 2012), 5 pgs. |
| Shein, Esther, “Ephemeral Data”, Communications of the ACM, vol. 56, No. 9, (Sep. 2013), 3 pgs. |
| Vaas, Lisa, “StealthText, Should You Choose to Accept It”, [Online] Retrieved from the Internet: <URL: http://www.eweek.eom/print/c/a/MessagingandCollaboration/StealthTextShouldYouChoosetoAcceptIt>, (Dec. 13, 2005), 2 pgs. |
| U.S. Appl. No. 15/169,288 U.S. Pat. No. 10,474,353, filed May 31, 2016, Application Control Using A Gesture Based Trigger. |
| U.S. Appl. No. 16/597,797, filed Oct. 9, 2019, Application Control Using a Gesture Based Trigger. |
| U.S. Appl. No. 15/289,676 U.S. Pat. No. 10,609,036, filed Oct. 10, 2016, Social Media Post Subscribe Requests for Buffer User Accounts. |
| U.S. Appl. No. 16/800,868, filed Feb. 25, 2020, Social Media Post Subscribe Requests for Buffer User Accounts. |
| “U.S. Appl. No. 16/597,797, Corrected Notice of Allowability dated Dec. 11, 2020”, 2 pgs. |
| “Chinese Application Serial No. 201780046815.5, Office Action dated Jul. 30, 2021”, w/ English translation, 10 pgs. |
| Number | Date | Country | |
|---|---|---|---|
| 20210089204 A1 | Mar 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16597797 | Oct 2019 | US |
| Child | 17115268 | US | |
| Parent | 15169288 | May 2016 | US |
| Child | 16597797 | US |
