Patent Grant
9614880
The disclosure relates generally to methods for generating real-time notifications in an activity stream.
Computer systems are known that allow for shared access to objects. As one example, shared storage systems or workspaces allow users to create or store objects such as files at a remote server, access the files via a network such as the internet, grant shared access to the files to other users, and in some examples, edit the files using a file creation and editing system that is associated with the shared storage system. Shared access to an object can include the ability to download the object, view the object, modify the object, share the object with additional users, make copies of the object, and delete the object. These types of systems are referred to here as shared workspaces.
In one example of a shared workspace, online document storage and editing systems are known that store files and allow multiple users who have been granted access to a particular file to take actions such as editing files or adding comments to files. In some shared workspaces, users can be provided with historical activity information regarding completed actions that were previously performed with respect to certain shared-access objects.
The disclosure relates to methods for generating real-time notifications in an activity stream.
One aspect of the disclosed embodiments is a method that includes providing, by a server computer, a shared workspace for facilitating collaborative work by a plurality of users with respect to a plurality of shared-access objects; obtaining real-time activity information describing ongoing actions currently being performed with respect to one or more of the shared-access objects; determining, based at least in part on the real-time activity information, whether a real-time notification rule is satisfied; outputting, for display in an activity stream and in response to determining that the real-time notification rule is satisfied, a real-time notification; and removing, from display in the activity stream, the real-time notification upon determining that the real-time notification rule is no longer satisfied.
Another aspect of the disclosed embodiments is a method that includes providing, by a server computer, a shared workspace for facilitating collaborative work by a plurality of users with respect to a plurality of shared-access objects; obtaining real-time activity information describing ongoing actions currently being performed with respect to the plurality of shared-access objects; applying a set of real-time notification rules to generate a set of real time notifications wherein each real-time notification rule is based at least in part on the real-time activity information and relates to one or more of the shared-access objects and wherein each real-time notification is associated with a ranking score; and outputting, for display in an activity stream, at least some of the real-time notifications based in part on the ranking score.
Another aspect of the disclosed embodiments is an apparatus that includes one or more processors and one or more memory devices for storing program instructions used by the one or more processors. The program instructions, when executed by the one or more processors, cause the one or more processors to provide a shared workspace for facilitating collaborative work by a plurality of users with respect to a plurality of shared-access objects; obtain real-time activity information describing ongoing actions currently being performed with respect to one or more of the shared-access objects; determine, based at least in part on the real-time activity information, whether a real-time notification rule is satisfied; output, for display in an activity stream and in response to determining that the real-time notification rule is satisfied, a real-time notification; and remove, from display in the activity stream, the real-time notification upon determining that the real-time notification rule is no longer satisfied.
The description makes reference to the accompanying drawings wherein like reference numerals refer to like parts throughout the several views, and wherein:
Methods for generating real-time notifications in an activity stream are described here. A shared workspace facilitates collaborative work on a plurality of shared-access objects by a plurality of users. The systems and methods described here can obtain real-time activity information describing ongoing actions currently being performed with respect to one or more of the shared-access objects within the shared workspace. Based at least in part on this real-time activity information, the system and methods described here can determine whether any ongoing actions satisfy one or more real-time notification rules. If a real-time notification rule is satisfied, a real-time notification can be output for display in an activity stream. If the systems and methods described here further determine that the real-time notification rule is no longer satisfied, the real-time notification can be removed from display in the activity stream. Real-time notifications can be distinguished from historical notifications that can also be displayed within the activity stream by the status of the actions which generate them: currently ongoing actions for real-time notifications and previously completed actions for historical notifications.
The systems, services, servers, and other computing devices described here are in communication via a network 150. The network 150 can be one or more communications networks of any suitable type in any combination, including wireless networks, wired networks, local area networks, wide area networks, cellular data networks, and the internet.
The application hosting service 130 can provide access to one or more hosted applications to a defined group of users including operators associated with the user system 110 and the additional user systems 120. As used here, a shared workspace is any manner of system, program, or interface that allows a defined group of users to utilize an access-restricted system in which information can be shared between users for the purpose of collaboratively working on a project. As will be discussed below, shared workspaces can implement document storage, creation, and editing functions. In some implementations, the application hosting service 130 allows a particular shared workspace to be accessed upon presentation of a credential, such as a username and password combination, that are associated with a registered user of that particular shared workspace. In some implementations, one or more users of each shared workspace are able to grant access to additional users or revoke access from existing users.
Each server computer 132 can include memory 220, such as a random access memory device (RAM). Any other suitable type of storage device can also be used as the memory 220. The memory 220 can include code and data 222 that can be accessed by the CPU 210 using a bus 230. The memory 220 can further include one or more application programs 224 and an operating system 226. The application programs 224 can include software components in the form of computer executable program instructions that cause the CPU 210 to perform the operations and methods described here.
A storage device 240 can be optionally provided in the form of any suitable computer readable medium, such as a hard disc drive, a memory device, a flash drive, or an optical drive. One or more input devices 250, such as a keyboard, a mouse, or a gesture sensitive input device, receive user inputs and can output signals or data indicative of the user inputs to the CPU 210. One or more output devices can be provided, such as a display device 260. The display device 260, such as a liquid crystal display (LCD) or a cathode-ray tube (CRT), allows output to be presented to a user, for example, in response to receiving a video signal.
Although
In the illustrated example, the shared workspace includes a storage system, or drive, for storing shared-access objects. The storage system and any different or additional applications or systems that could be used in the shared workspace can be provided in the form of software instructions that are executed by a processor or computer, such as the one or more server computers 132 of the application hosting service 130 shown in
In the illustrated example, the shared workspace includes a notification system for generating, storing, and displaying notifications 402a-e within the activity stream, for example, within a tab-style access window denoted by the tag 404, “Activity.” The notifications 402a-e can be used to provide insight to users of the shared workspace as to ongoing actions being taken and historical actions that have been taken by one or more users of the shared workspace with respect to the one or more folders 304a-c or one or more documents 306a-f that comprise the shared-access objects within the storage system. In this example, when the tab-style access window denoted by the tag 404, “Activity,” is selected by a user of the shared workspace, the interface 400 for the activity stream is displayed over the location of the tag 308, “Files,” as shown in
The notification system within the shared workspace can be configured to collect real-time activity information describing ongoing actions currently being performed with respect to one or more of the shared-access objects. This real-time activity information can include information describing, for example, the identification of a shared-access object, the type of ongoing action being taken with respect to a shared-access object, the identity of a user associated with an ongoing action in respect to a shared-access object, and information related to the time at which the ongoing action in respect to a shared-access object commenced. Similarly, historical activity information describing completed actions that were previously performed with respect to one or more of the shared-access objects can be collected and stored by the notification system, the storage system, or any other system associated with the shared workspace.
The notification system can also be configured to determine the content of real-time notifications based on whether a set of real-time notification rules is satisfied using real-time activity information. In one example, the notification system can be configured to display a real-time notification within the activity stream whenever a user is currently viewing, editing, or commenting upon the one of the folders 304a-c or one of the documents 306a-f within the shared workspace. As shown in
The notification system can also be configured to remove real-time notifications from display within the activity stream upon determining that the real-time notification rule which generated the real-time notification is no longer being satisfied. For example, once “Jane Smith” closes Document B 306b in the shared workspace, the notification system can remove this information from display within notification 402a. Similarly, once “John Doe” closes out the commenting function for Document A 306a, the notification system can remove this information from display within notification 402b.
The notification system can also be configured to determine the content of historical notifications based on whether a set of historical notification rules is satisfied using historical activity information. In one example, the notification system can be configured to display a historical notification within the activity stream based on previously completed user actions in the shared workspace, such as creation of documents 306a-f, comments made within documents 306a-f, edits made within documents 306a-f, etc. As shown in
Though the interface 400 to the activity stream in
In one example, the user menu 408 and the sort-by menu 410 can be used to filter the notifications 402a-e based on the level of activity of the user and the identity of the user taking the actions that satisfy one of the notification rules (e.g. the real-time notification rules or the historical notification rules) in the notification system. The identities of the users can be represented both by names, for example “Jane Smith,” “John Doe,” “Jane Doe,” and “John Smith,” and by pictures or icons associated with the users. The order in which the users are listed within the activity stream can be based on the level of activity of the user, for example, based on the number of actions taken by the user or based on how recently the actions occurred.
The order in which the users are listed within the activity stream can also be based on a ranking score associated with the user. The ranking score can be based, for example, on the identity of the user performing an action, the permission levels (e.g. owner, editor, commenter, viewer) associated with the user performing the action, the level of activity of the user performing an action, the identification of the shared-access object undergoing an action, the subject matter of the shared-access object undergoing the action, or the preferences of the user viewing the activity stream. In the example of
The icons for the most active or highest ranked users, e.g. current user “Jane Smith” and historical user “John Smith,” can be configured to appear darker than the icons for the less active or lower ranked users, in this example, current and historical user “John Doe.” Hence, opacity of a user icon is another means of sorting or filtering the notifications 402a-e based on the ranking score, activity level, and identity of the users within the activity stream. In the example shown in
As described above, various sorting and filtering of the notifications 402a-e are possible, such as grouping by the ownership of the shared-access object upon which actions are being taken, by the status of a given user within the shared workspace (e.g. viewing, editing, idle, offline), by the subject matter of the shared-access objects upon which the actions are taken, by the type of action being taken that satisfies either a real-time notification rule or historical notification rule, and as described below in respect to
The real-time notifications 402a-b can also be configured to be removed from display within the activity stream, for example, by the user dismissing one or more of the real-time notifications 402a-b from the activity stream by selecting, for example, a close icon represented by an “X” within a box, proximate to the respective real-time notification 402a, 402b. The real-time notifications 402a-b in the activity stream can also be distinguished from the historical notifications 402c-e within the activity stream as shown in
In the
The notifications 500a-f can also include information about the duration of a user's interaction with a shared-access object, the current status of the user within the shared workspace (e.g. idle, brainstorming, refining, commenting, offline, seeking collaborators, etc.), the number of users currently collaborating on a shared-access object, or any other information related to the ongoing or previous actions being taken within the shared workspace. The shared workspace, storage system, activity stream, and notification system can also be configured for integration into a calendar application. For example, a meeting within the calendar application can be configured to be a shared workspace and invitees to the meeting can be the users of the shared workspace. The activity stream tracking the actions within the meeting can indicate to each of the invitees participating in the meeting which shared-access objects are being viewed, edited, opened, closed, etc. by other meeting participants. This application of the activity stream can be particularly useful in the meeting context when invitees are in separate geographic locations but still want to work together at the same time on the same shared-access objects, such as the documents 306a-e, stored within a document storage system.
At operation 602, a shared workspace is provided for facilitating collaborative work by a plurality of users on a plurality of shared-access objects. The shared workspace can be provided, for example, by one of the server computers 132 of
At operation 604, real-time activity information describing ongoing actions currently being performed with respect to one or more of the shared-access objects is obtained, for example, using the notification system. As described above, real-time activity information can include information describing the identification of a shared-access object, the type of ongoing action being taken with respect to a shared-access object, the identity of a user associated with an ongoing action in respect to a shared-access object, and information related to the time at which the ongoing action in respect to a shared-access object commenced.
At operation 606, a determination is made as to whether a real-time notification rule is satisfied based at least in part on the real-time activity information obtained in operation 604. One or more real-time notification rules can be configured, as described above in reference to
If, at operation 606, it is determined that no ongoing actions within the shared workspace satisfy a real-time notification rule, the process 600 returns to operation 604. If, at operation 606, it is determined that an ongoing action satisfies at least one real-time notification rule, the process 600 advances to operation 608. At operation 608, a real-time notification is generated and output for display in the activity stream. For example, the real-time notifications 402a-b displayed within the interface 400 to the activity stream shown in
At operation 610, a determination is made as to whether one of the real-time notification rules is no longer being satisfied. If, at operation 610, it is determined that the real-time notification rule is still being satisfied, the process 600 returns to operation 608, and the real-time notification remains as displayed within the activity stream. If, at operation 610, it is determined that the real-time notification rule is no longer satisfied, the process 600 advances to operation 612, and the applicable notification can be removed from the activity stream. For example, the user “Jane Smith” who is currently viewing Document B 306b according to real-time notification 402a shown in
At operation 702, a shared workspace is provided for facilitating collaborative work by a plurality of users on a plurality of share-access objects. The shared workspace can be provided, for example, by one of the server computers 132 of
At operation 704, real-time activity information describing ongoing actions currently being performed with respect to one or more of the shared-access objects is obtained, for example, using the notification system. As described above, real-time activity information can include information describing the identification of a shared-access object, the type of ongoing action being taken with respect to a shared-access object, the identity of a user associated with an ongoing action in respect to a shared-access object, and information related to the time at which the ongoing action in respect to a shared-access object commenced.
At operation 706, a set of real-time notification rules can be applied to generate a set of real-time notifications, such as real-time notification 402a-b. The real-time notification rules can be based, at least in part, on the real-time activity information obtained at operation 704 and can be configured to relate to one or more of the shared-access objects within the shared workspace. The real-time notifications generated in response to satisfaction of one or more of the real-time notification rules can also be associated with a ranking score. As described above, the ranking score can be based, for example, on the identity of the user performing an action, the level of activity of the user performing an action, the identification of the shared-access object undergoing an action, the subject matter of the shared-access object undergoing the action, or the preferences of the user viewing the activity stream.
At operation 708, at least some of the real-time notifications generated at operation 706 can be output for display in the activity stream. The notification system can determine which subset of real-time notifications to display within the activity stream based in part on the ranking scores associated with each of the real-time notifications. For example, a user can select or the notification system can be configured to display real-time notifications for ongoing actions that are being performed by a selected group of highly-ranked users that are important to the user viewing the activity stream. After display of at least some of the real-time notifications, the process 700 ends.
The foregoing description describes only some exemplary implementations of the described techniques. Other implementations are available. For example, the particular naming of the components, capitalization of terms, the attributes, data structures, or any other programming or structural aspect is not mandatory or significant, and the mechanisms that implement the invention or its features may have different names, formats, or protocols. Further, the system may be implemented via a combination of hardware and software, as described, or entirely in hardware elements. Also, the particular division of functionality between the various system components described here is merely exemplary, and not mandatory; functions performed by a single system component may instead be performed by multiple components, and functions performed by multiple components may instead performed by a single component.
The words “example” or “exemplary” are used here to mean serving as an example, instance, or illustration. Any aspect or design described here as “example’ or “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects or designs. Rather, use of the words “example” or “exemplary” is intended to present concepts in a concrete fashion. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise, or clear from context, “X includes A or B” is intended to mean any of the natural inclusive permutations. That is, if X includes A; X includes B; or X includes both A and B, then “X includes A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form. Moreover, use of the term “an embodiment” or “one embodiment” or “an implementation” or “one implementation” throughout is not intended to mean the same embodiment or implementation unless described as such.
The implementations of the computer devices (e.g., clients and servers) described here can be realized in hardware, software, or any combination thereof. The hardware can include, for example, computers, intellectual property (IP) cores, application-specific integrated circuits (ASICs), programmable logic arrays, optical processors, programmable logic controllers, microcode, microcontrollers, servers, microprocessors, digital signal processors or any other suitable circuit. In the claims, the term “processor” should be understood as encompassing any of the foregoing hardware, either singly or in combination. The terms “signal” and “data” are used interchangeably. Further, portions of each of the clients and each of the servers described here do not necessarily have to be implemented in the same manner.
Operations that are described as being performed by a single processor, computer, or device can be distributed across a number of different processors, computers or devices. Similarly, operations that are described as being performed by different processors, computers, or devices can, in some cases, be performed by a single processor, computer or device.
Although features may be described above or claimed as acting in certain combinations, one or more features of a combination can in some cases be excised from the combination, and the combination may be directed to a sub-combination or variation of a sub-combination.
The systems described here, such as client computers and server computers, can be implemented using general purpose computers/processors with a computer program that, when executed, carries out any of the respective methods, algorithms and/or instructions described here. In addition or alternatively, for example, special purpose computers/processors can be utilized which can contain specialized hardware for carrying out any of the methods, algorithms, or instructions described here.
Some portions of above description include disclosure presented in terms of algorithms and symbolic representations of operations on information. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. These operations, while described functionally or logically, are understood to be implemented by computer programs. Furthermore, it has also proven convenient at times, to refer to these arrangements of operations as modules or by functional names, without loss of generality. It should be noted that the process steps and instructions of implementations of this disclosure could be embodied in software, firmware or hardware, and when embodied in software, could be downloaded to reside on and be operated from different platforms used by real time network operating systems.
Unless specifically stated otherwise as apparent from the above discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system memories or registers or other such information storage, transmission or display devices.
At least one implementation of this disclosure relates to an apparatus for performing the operations described. This apparatus may be specially constructed for the required purposes, or it may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored on a computer readable storage medium that can be accessed by the computer.
All or a portion of the embodiments of the disclosure can take the form of a computer program product accessible from, for example, a non-transitory computer-usable or computer-readable medium. The computer program, when executed, can carry out any of the respective techniques, algorithms and/or instructions described here. A non-transitory computer-usable or computer-readable medium can be any device that can, for example, tangibly contain, store, communicate, or transport the program for use by or in connection with any processor. The non-transitory medium can be, for example, any type of disk including floppy disks, optical disks, CD-ROMs, magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, application specific integrated circuits (ASICs), or any type of media suitable for tangibly containing, storing, communicating, or transporting electronic instructions.
It is to be understood that the disclosure is not to be limited to the disclosed embodiments but, on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5450593 | Howell et al. | Sep 1995 | A |
| 5579471 | Barber et al. | Nov 1996 | A |
| 6006239 | Bhansali et al. | Dec 1999 | A |
| 6009405 | Leymann et al. | Dec 1999 | A |
| 6119165 | Li et al. | Sep 2000 | A |
| 6314105 | Luong | Nov 2001 | B1 |
| 6449688 | Peters et al. | Sep 2002 | B1 |
| 6507845 | Cohen | Jan 2003 | B1 |
| 6590568 | Astala et al. | Jul 2003 | B1 |
| 6614804 | McFadden et al. | Sep 2003 | B1 |
| 6687735 | Logston et al. | Feb 2004 | B1 |
| 6711557 | Palaniappan | Mar 2004 | B1 |
| 6947396 | Salmi | Sep 2005 | B1 |
| 7030861 | Westerman et al. | Apr 2006 | B1 |
| 7113917 | Jacobi et al. | Sep 2006 | B2 |
| 7146377 | Nowicki et al. | Dec 2006 | B2 |
| 7386576 | Watanabe et al. | Jun 2008 | B2 |
| 7536386 | Samji et al. | May 2009 | B2 |
| 7620902 | Manion et al. | Nov 2009 | B2 |
| 7660902 | Graham et al. | Feb 2010 | B2 |
| 7711771 | Kirnos | May 2010 | B2 |
| 7756821 | Havens et al. | Jul 2010 | B2 |
| 7821405 | Heidloff et al. | Oct 2010 | B2 |
| 7827299 | Cadarette et al. | Nov 2010 | B2 |
| 7904303 | Chien et al. | Mar 2011 | B2 |
| 7908183 | Jacobi et al. | Mar 2011 | B2 |
| 7945600 | Thomas et al. | May 2011 | B1 |
| 8041672 | Ogawa et al. | Oct 2011 | B2 |
| 8132111 | Baron et al. | Mar 2012 | B2 |
| 8156059 | Dunning et al. | Apr 2012 | B2 |
| 8194986 | Conwell | Jun 2012 | B2 |
| 8196047 | Fisher et al. | Jun 2012 | B2 |
| 8285700 | Steelberg et al. | Oct 2012 | B2 |
| 8298087 | Smith | Oct 2012 | B1 |
| 8407613 | Hope | Mar 2013 | B2 |
| 8412731 | Aubert et al. | Apr 2013 | B2 |
| 8417000 | Mendis | Apr 2013 | B1 |
| 8429565 | Agarawala et al. | Apr 2013 | B2 |
| 8458174 | Duerig | Jun 2013 | B1 |
| 8464184 | Cook et al. | Jun 2013 | B1 |
| 8467955 | Jiang et al. | Jun 2013 | B2 |
| 8468164 | Paleja et al. | Jun 2013 | B1 |
| 8479122 | Hotelling et al. | Jul 2013 | B2 |
| 8504565 | Pitts | Aug 2013 | B2 |
| 8522230 | Nathan et al. | Aug 2013 | B2 |
| 8522258 | Shaw | Aug 2013 | B1 |
| 8532400 | Babenko et al. | Sep 2013 | B1 |
| 8547352 | Park et al. | Oct 2013 | B2 |
| 8548844 | Steelberg et al. | Oct 2013 | B2 |
| 8555173 | Kast | Oct 2013 | B2 |
| 8560975 | Beaver et al. | Oct 2013 | B2 |
| 8571331 | Cifarelli | Oct 2013 | B2 |
| 8584022 | O'Shaughnessy et al. | Nov 2013 | B1 |
| 8612439 | Prahlad et al. | Dec 2013 | B2 |
| 8612470 | Fushman et al. | Dec 2013 | B1 |
| 8624836 | Miller et al. | Jan 2014 | B1 |
| 8638312 | Lim | Jan 2014 | B2 |
| 8644688 | Fishman et al. | Feb 2014 | B2 |
| 8661053 | Flynn et al. | Feb 2014 | B2 |
| 8670597 | Petrou et al. | Mar 2014 | B2 |
| 20020054117 | van Dantzich | May 2002 | A1 |
| 20020099844 | Baumann et al. | Jul 2002 | A1 |
| 20020112116 | Nelson | Aug 2002 | A1 |
| 20020116399 | Camps et al. | Aug 2002 | A1 |
| 20020167538 | Bhetanabhotla | Nov 2002 | A1 |
| 20020178271 | Graham et al. | Nov 2002 | A1 |
| 20020184375 | Wagner et al. | Dec 2002 | A1 |
| 20030184653 | Ohkubo | Oct 2003 | A1 |
| 20030208490 | Larrea et al. | Nov 2003 | A1 |
| 20040135904 | Shiota et al. | Jul 2004 | A1 |
| 20040189707 | Moore et al. | Sep 2004 | A1 |
| 20050033777 | Moraes et al. | Feb 2005 | A1 |
| 20050131992 | Goldstein et al. | Jun 2005 | A1 |
| 20060059174 | Mese et al. | Mar 2006 | A1 |
| 20060159127 | Childress et al. | Jul 2006 | A1 |
| 20060229932 | Zollo et al. | Oct 2006 | A1 |
| 20060242581 | Manion et al. | Oct 2006 | A1 |
| 20070100937 | Burtner | May 2007 | A1 |
| 20070244969 | Knight | Oct 2007 | A1 |
| 20070250401 | Hearn et al. | Oct 2007 | A1 |
| 20080123904 | Sakamoto et al. | May 2008 | A1 |
| 20080126476 | Nicholas et al. | May 2008 | A1 |
| 20080165141 | Christie | Jul 2008 | A1 |
| 20080177623 | Fritsch et al. | Jul 2008 | A1 |
| 20080195956 | Baron et al. | Aug 2008 | A1 |
| 20080270398 | Landau et al. | Oct 2008 | A1 |
| 20090112868 | Rajamani et al. | Apr 2009 | A1 |
| 20090112985 | Quinn | Apr 2009 | A1 |
| 20090271356 | Jeong et al. | Oct 2009 | A1 |
| 20090327975 | Stedman | Dec 2009 | A1 |
| 20100017426 | Marston | Jan 2010 | A1 |
| 20100046392 | Childress et al. | Feb 2010 | A1 |
| 20100070707 | Nishimura | Mar 2010 | A1 |
| 20100161441 | Hounsell | Jun 2010 | A1 |
| 20100211575 | Collins et al. | Aug 2010 | A1 |
| 20100241971 | Zuber | Sep 2010 | A1 |
| 20100250337 | Kassaei | Sep 2010 | A1 |
| 20100251305 | Kimble et al. | Sep 2010 | A1 |
| 20100256981 | Nielsen et al. | Oct 2010 | A1 |
| 20100332846 | Bowden et al. | Dec 2010 | A1 |
| 20100332958 | Weinberger et al. | Dec 2010 | A1 |
| 20110010672 | Hope | Jan 2011 | A1 |
| 20110044512 | Bambha et al. | Feb 2011 | A1 |
| 20110208668 | Phillips | Aug 2011 | A1 |
| 20110289423 | Kim et al. | Nov 2011 | A1 |
| 20120032436 | Zantout et al. | Feb 2012 | A1 |
| 20120072449 | Patch et al. | Mar 2012 | A1 |
| 20120078845 | Kasbekar et al. | Mar 2012 | A1 |
| 20120084689 | Ledet et al. | Apr 2012 | A1 |
| 20120089610 | Agrawal et al. | Apr 2012 | A1 |
| 20120096046 | Kucera | Apr 2012 | A1 |
| 20120136936 | Quintuna | May 2012 | A1 |
| 20120192086 | Ghods | Jul 2012 | A1 |
| 20120197980 | Terleski et al. | Aug 2012 | A1 |
| 20120213404 | Steiner | Aug 2012 | A1 |
| 20120233227 | Alexander et al. | Sep 2012 | A1 |
| 20120246153 | Pehle | Sep 2012 | A1 |
| 20120254332 | Irvin | Oct 2012 | A1 |
| 20120290609 | Britt | Nov 2012 | A1 |
| 20120290926 | Kapadia et al. | Nov 2012 | A1 |
| 20120290947 | Baggett et al. | Nov 2012 | A1 |
| 20120303477 | Ben-Itzhak | Nov 2012 | A1 |
| 20120303684 | Sakurai et al. | Nov 2012 | A1 |
| 20120324368 | Putz et al. | Dec 2012 | A1 |
| 20130014023 | Lee et al. | Jan 2013 | A1 |
| 20130024464 | Berner et al. | Jan 2013 | A1 |
| 20130073976 | McDonald et al. | Mar 2013 | A1 |
| 20130080940 | Reeves et al. | Mar 2013 | A1 |
| 20130104080 | Bosworth et al. | Apr 2013 | A1 |
| 20130132896 | Lee et al. | May 2013 | A1 |
| 20130138674 | Jeong et al. | May 2013 | A1 |
| 20130138685 | Brucher et al. | May 2013 | A1 |
| 20130173637 | Kim et al. | Jul 2013 | A1 |
| 20130185638 | Tischer | Jul 2013 | A1 |
| 20130188886 | Petrou et al. | Jul 2013 | A1 |
| 20130202198 | Adam et al. | Aug 2013 | A1 |
| 20130218845 | Kleppner | Aug 2013 | A1 |
| 20130263289 | Vijayan et al. | Oct 2013 | A1 |
| 20130339435 | De Armas | Dec 2013 | A1 |
| 20140019317 | Casares et al. | Jan 2014 | A1 |
| 20140019910 | Kim et al. | Jan 2014 | A1 |
| 20140029798 | Flynn et al. | Jan 2014 | A1 |
| 20140067702 | Rathod | Mar 2014 | A1 |
| 20140068443 | Eng et al. | Mar 2014 | A1 |
| 20140129942 | Rathod | May 2014 | A1 |
| 20140164535 | Lynch et al. | Jun 2014 | A1 |
| 20140236722 | Rathus et al. | Aug 2014 | A1 |
| 20140317552 | Romatoski | Oct 2014 | A1 |
| 20150193521 | Schoeffler et al. | Jul 2015 | A1 |
| 20150363062 | Gunn | Dec 2015 | A1 |
| 20150363640 | Meyer | Dec 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 0371608 | Jun 1990 | EP |
| 1275222 | Jan 2003 | EP |
| 2187322 | May 2010 | EP |
| 2458512 | May 2012 | EP |
| WO0051021 | Aug 2000 | WO |
| WO03090096 | Oct 2003 | WO |
| WO2007085083 | Aug 2007 | WO |
| WO2009032712 | Mar 2009 | WO |
| WO2012092025 | Jul 2012 | WO |
| Entry |
|---|
| ISR & Written Opinion, Re: Application # PCT/US2015/020375; Jun. 12, 2015. |
| ISR and Written Opinion of the International Searching Authority for International Application No. PCT/US2015010618, Mar. 25, 2015. |
| ISR & Written Opinion, Re: Application #PCT/US2015/020378 citing new art; Aug. 18, 2015. |
| Automatic Album Maker Moment.me Arrives on Android, Adds A “Manual Mode” Mode to Boost Engagement, TechCrunch, Feb. 18, 2013, http://techcrunch.com/2013/02/18/automatic-album-maker-moment-me-arrives-on- android-adds-a-manual-mode-mode-to-boost-engagement/. |
| Flayvr, A. Mobile App That Automatically Creates Photo Albums, Raises $450K Seed Round, TechCrunch, Oct. 4, 2012, http://techcrunch.com/2012/10/04/flayvr-a-mobile-app-that-automatically-creates-photo-albums-raises-450k-seed-round/. |
| Larson, Michael, “Probing Network Characteristics: A Distributed Network Performance Framework”, Dr. Dobb's Journal, Jun. 2004, pp. 22-29. |
| Lowe, D. , “Object recognition from local scale-invariant features,” International Conference on Computer Vision Corfu, Greece (Sep. 1999) pp. 1150-1157. |
