Patent Grant
11809450
Computing devices (e.g., computers, tablets, smart phones) provide numerous ways for people to capture, store, create, share, view, and manage digital content. For example, conventional remote storage systems enable client devices to utilize resources of one or more remote servers to store, share, and otherwise manage any number of digital content items while preserving local storage space of individual client devices. Indeed, rather than storing all photos, videos, documents, programs, and other files on a local hard drive of a client device, users can remotely store and access any number of files using remote storage space provided by conventional remote storage systems.
Storing and managing digital content via remote storage, however, suffers from a number of limitations and drawbacks. For example, where a client device has an unreliable or poor connection with a remote storage system, a user of the client device is often unable to download or access a copy of one or more important files. In addition, where a file is accessible to multiple users and one or more users have made changes to the file, other users experiencing connectivity issues may mistakenly access outdated versions of the file, causing miscommunications and frustration between the users attempting to view or access the most updated version of the file.
Many individuals overcome or anticipate intermittent or poor network conditions by selectively storing local copies of remote files and periodically synchronizing the local copies with corresponding remote files maintained via the remote storage space. However, where remote storage accounts include tens and hundreds of thousands of files and folders, storage limitations of client devices limit the number of local copies that can be readily accessible without a reliable connection to the remote storage space. In addition, in selecting which files to store locally, users often select too many local files, depleting storage space of the client device, thereby negatively impacting performance of the client device and largely negating any benefit provided by the remote storage system. Alternatively, users often select too few files to locally store, resulting in one or more important files being inaccessible under poor network conditions.
Accordingly, there are a number of considerations to be made in managing access to remote content items.
Embodiments of the present disclosure provide benefits and/or solve one or more of the foregoing or other problems in the art with systems, methods, and computer-readable media for synchronizing local copies of digital content items with corresponding digital content items on a digital content management system. In particular, the disclosed systems provide local access to important digital content items by selectively identifying digital content items of interest to a user to maintain locally on the local storage of a client device without depleting unnecessary storage space of the client device. For example, in one or more embodiments, the disclosed systems generate synchronization scores for digital content items from a collection of digital content items accessible to the user and selectively synchronize and/or provide a recommendation to synchronize digital content items of interest to the user based on the associated synchronization scores. In one or more embodiments, the disclosed systems utilize one or multiple models for selectively identifying digital content items of particular interest to the user from the collection.
To elaborate, the systems disclosed herein can collect and analyze recall data including interactions by a user and a team of co-users with respect to digital content items from a collection of digital content items. The disclosed systems can analyze profiles of recalled digital content items as well as compare recall data of the user and a team of co-users using one or more analytical models. Based on the analysis of the digital content item profiles and recall data, the disclosed systems can identify digital content items of particular interest to the user. By selectively identifying digital content items of interest to a user, the disclosed systems can provide local access to important digital content items from a large collection of digital content items without depleting storage space of a client device having limited storage capabilities.
Moreover, the disclosed systems facilitate greater collaboration and communication between a team of users including the user and co-users without requiring a user to manually go through and select individual digital content items to synchronize to a local storage of the client device. For instance, by comparing user features, content features, and recall histories (e.g., a history of interactions with a collection of digital content items) of a user and associated co-users, the disclosed systems can identify digital content items to synchronize (or recommend synchronizing) for the user that will enable the user to more effectively collaborate and communicate with other co-users of the digital content management system.
Additional features and advantages of the present disclosure will be set forth in the description that follows, and in part will be obvious from the description, or may be learned by the practice of such exemplary embodiments. The features and advantages of such embodiments may be realized and obtained by means of the instruments and combinations particularly pointed out in the appended claims. These and other features will become more fully apparent from the following description and appended claims, or may be learned by the practice of such exemplary embodiments as set forth hereinafter.
In order to describe the manner in which the above-recited and other advantages and features of the disclosure can be obtained, a more particular description of the disclosure briefly described above will be rendered by reference to specific embodiments thereof that are illustrated in the appended drawings. It should be noted that the figures are not drawn to scale, and that elements of similar structure or function are generally represented by like reference numerals for illustrative purposes throughout the figures. Understanding that these drawings depict only typical embodiments of the present disclosure and are not therefore to be considered to be limiting of its scope, the present disclosure will be described and explained with additional specificity and detail through the use of the accompanying drawings.
The present disclosure provides one or more embodiments of a synchronization system that facilitates selectively synchronizing digital content items from a collection of digital content items to a local storage of a client device. In particular, the synchronization system collects and analyzes recall data for a user and associated co-users including a history of interactions with respect to the digital content items and corresponding file data. The synchronization system further determines a synchronization score for the digital content items of the collection of digital content items associated with a probability that the user will synchronize the digital content items to a local storage of the client device (or multiple client devices). Further, the synchronization system selectively synchronizes or provides a recommendation to synchronize one or more digital content items from the collection based on associated synchronization scores.
As mentioned above, the synchronization system collects recall data including information associated with recall of digital content items by a user of a digital content management system. For example, the synchronization system tracks which digital content items from a collection of digital content items recalled (e.g., accesses, downloads) by the user and identifies interactions by the user with respect to the recalled digital content items. In one or more embodiments, the synchronization system constructs a user profile including recall data associated with the user.
In addition to collecting information about the user, the synchronization system can similarly collect information about a team of users including co-users of the digital content management system. For example, the synchronization system can track which digital content items from the collection of digital content items each of the co-users recall in addition to identifying which of the digital content items the co-users have synchronized to local storage spaces. Similar to the user, the synchronization system can construct co-user profiles including recall data and synchronization data for the respective co-users.
The synchronization system can further analyze the collected recall data about the user and co-users to identify digital content items of interest to the user of the digital content management system. In particular, in one or more embodiments, the synchronization system analyzes the recall data including information about the user and co-users as well as information about the respective digital content items to determine a synchronization score indicative of whether the user will synchronize the digital content items to a local storage space of a client device. For example, in one or more embodiments, the synchronization system analyzes each of the digital content items from a collection of digital content items to identify digital content items having a similar profile or recall history as digital content items that have been synchronized by the user and/or co-users of the digital content management system.
As will be described in further detail below, the synchronization system can implement a variety of analysis models to determine synchronization scores for the respective digital content items. For example, in one or more embodiments, the synchronization system implements a content-based model that compares digital content item profiles to identify digital content items similar to those that have been synchronized by the user and/or co-users. As another example, in one or more embodiments, the synchronization system implements a correlation model that compares user profiles to determine synchronization patterns of co-users having a similar pattern of recall behavior as the user. Further, in one or more embodiments, the synchronization system utilizes a latent factor model that extrapolates data about any number of digital content items based on factors and features associated with the digital content items and co-users of the digital content management system who have recalled the digital content items.
In addition, as will be described in further detail below, the synchronization system can utilize a combination of different analysis models based on collected recall data about the user and/or team of users. For example, where a user has a limited recall history (e.g., a new user), the synchronization system can apply greater weight to a latent factor model or content-based model while applying less weight to a collaboration model. Alternatively, where a user has a more extensive recall history, the synchronization system can apply a greater weight to the collaboration model, where a user profile includes more information to compare with user profiles of co-users. Additional detail with regard to utilizing different models and combining analysis from respective models will be provided below.
Furthermore, upon determining synchronization scores for digital content items of the collection of digital content items, the synchronization system can synchronize and/or provide one or more recommendations to a user to synchronize one or more digital content items to a local storage space of a client device. For example, in one or more embodiments, the synchronization system identifies the digital content items having the highest synchronization scores and provides a recommendation to synchronize the identified digital content items. In addition, or as an alternative, in one or more embodiments, the synchronization system automatically synchronizes one or more digital content items to a local storage space of the client device based on the determined synchronization scores for the associated digital content items.
The synchronization system provides a number of advantages over conventional remote storage systems. For example, by selectively identifying those digital content items of particular interest to a user for synchronization, the synchronization system prevents downloading too many digital content items from a remotely stored collection and over-utilizing the local storage of individual client devices. Indeed, rather than automatically downloading all remotely stored files or any number of remotely stored files up to a storage capacity of the client device (largely negating many benefits provided by a remote storage), the synchronization system intelligently identifies digital content items of particular interest to locally store on the client device, while relying on the remote storage for other files. Accordingly, in contrast to conventional systems that over-utilize local storage space by downloading files that a specific user is unlikely to recall, the synchronization system improves functionality of client devices by selectively identifying digital content items for synchronization, resulting in efficient utilization of bandwidth and increasing available local storage space on the client devices.
In addition, by applying analysis models to determine a synchronization score that considers recall data from both the user and a team of co-users, the synchronization system facilitates effective collaboration and communication between the user and co-users of the synchronization system. For example, by considering a recall history including recall data of the user and recall data of co-users, the synchronization system considers a more extensive history of recall data to more accurately predict which of the digital content items would be of interest to the user. Further, by utilizing the recall history of any number of co-users, the synchronization system can effectively identify digital content items of interest even where a user has little or no recall history with respect to the collection of digital content items.
Furthermore, by utilizing multiple analysis models, the synchronization system customizes analysis of recall data based on features associated with the user, co-users, and individual digital content items. For example, where a user is a new user of the digital content management system, the synchronization system can place a greater emphasis on results of an analysis model structured to identify digital content items of interest for a user without an extensive recall history. Alternatively, where a user has an extensive recall history, the synchronization system can further consider or place a greater emphasis on one or more additional analysis models that consider the recall history of the user in identifying digital content items of interest for the user.
In addition, by determining synchronization scores and selectively identifying digital content items for synchronization in accordance with one or more embodiments described herein, the synchronization system facilitates intelligent selection of digital content items for synchronization without requiring intervention by a user of the client device. Indeed, by utilizing the analysis models described herein to determine digital content items for synchronization, the synchronization system can autonomously identify digital content items for synchronization without requiring a user to navigate a massive collection of digital content items to manually identify digital content items to synchronize. As a result, the synchronization system decreases user frustration as a result of large and disorganized collections of digital content items and/or miscommunications between a team of co-users.
As illustrated by the foregoing discussion, the present disclosure utilizes a variety of terms to describe features and advantages of a synchronization system. Additional detail is now provided regarding the meaning of some of these terms. For instance, as used herein, a “digital content item” or “digital content” can be any digital data such as documents, collaboration content items, text files, audio files, image files, video files, webpages, executable files, binaries, etc. A digital content item can include collections or other mechanisms for grouping digital content items together with different behaviors, such as folders, zip files, playlists, albums, etc. A collection of digital content items can refer to a folder or a plurality of digital content items that are related or grouped by a common attribute. For example, a collection of digital content items can refer to any number of digital content items accessible to a user of a digital content management system (e.g., via a user account of the digital content management system associated with the user).
As used herein, a “user” refers to an individual or other entity associated with a user account of the digital content management system that enables the user or co-users to access a collection of digital content items associated with the user account. For example, a user associated with a user account can store, view, download, or otherwise interact with digital content items via a remote storage space managed by the digital content management system. In addition, a user can provide access to one or more digital content items to co-users of the digital content management system. For example, a user can provide access to one or more digital content items associated with a user account to one or more co-users including individuals associated with respective co-user accounts and/or non-users of the digital content management system not otherwise associated with respective user-accounts.
As used herein, a “synchronization score” refers to a score determined for a user with respect to a digital content item from a collection of digital content items. In particular, a synchronization score associated with a digital content item refers to a likelihood or probability that a given user associated with a recall history with respect to digital content items from the collection of digital content items will request synchronization of the digital content item (e.g., provide a request to a digital content management system to synchronize the digital content item). Accordingly, a synchronization score refers to a prediction generated by a synchronization system that a user will eventually request synchronization of a digital content item to a local storage of a client device based on a recall history of the user and one or more co-users of the digital content management system with the digital content item and/or with other digital content items having similar features and/or characteristics. As will be described in further detail below, the synchronization system can utilize a number of different models and techniques to determine the synchronization score for a digital content item. In particular, in one or more embodiments, the synchronization system determines a synchronization score based on recall data associated with respective users and/or digital content items.
As used herein, “recall data” refers to information associated with digital content items from a collection of digital content items that a user and/or co-users of a digital content management system have accessed, synchronized, or otherwise interacted with using respective client devices and co-user client devices. In addition, recall data can refer to a number of actions (e.g., a history of actions) taken with respect to a digital content item. In one or more embodiments, a digital content item is “recalled” in a number of ways. For example, a recalled digital content item can refer to a digital content item that has been viewed, downloaded, interacted with, modified, synchronized, or otherwise been accessed by a user or co-users of the digital content management system.
In one or more embodiments described herein, recall data refers to recall data by one or more individuals. For example, “user-recall data” refers to information about one or more actions taken by a user of a client device with respect to a given digital content item. For instance, user-recall data can refer to a history of interactions with respect to any number of digital content items from a collection of digital content items. Similarly, “co-user recall data” refers to information about one or more co-users of the digital content management system with respect to any number of digital content items.
Additional detail will now be provided regarding the synchronization system in relation to illustrative figures portraying exemplary embodiments. For example,
As illustrated in
Although
In addition, the devices of environment 100 may refer to various types of computing devices. For example, one or more of the devices (e.g., server device(s) 102, co-user client devices 108a-n, client device 112) may include a mobile device such as a mobile telephone, a smartphone, a PDA, a tablet, or a laptop. Additionally, or alternatively, one or more of the devices may include a non-mobile device such as a desktop computer, a server, or another type of computing device. Additional detail with regard to different types of computing devices is described in reference to
In addition, in one or more embodiments, content management application 116 refers to a software application associated with digital content management system 104. In one or more embodiments, content management application 116 provides and controls various features and functionality on client device 112 and enables user 114 to share and receive digital content items stored on digital content management system 104 (e.g., stored on a remote storage space hosted by digital content management system 104). In one or more embodiments, the content management application 116 refers to a native or hybrid application installed on a respective computing device. Alternatively, in one or more embodiments, content management application 116 refers to a web browser used to access digital content management system 104. In addition, while not shown in
As an overview, digital content management system 104 enables client device 112 and co-user client devices 108a-n associated with respective user 114 and co-users 110a-n to store digital content items on digital content management system 104. For example, client device 112 can upload a digital content item from client device 112 to digital content management system 104 over network 118. Client device 112 can further remotely access the uploaded digital content item over network 118 by downloading or remotely accessing the digital content item on digital content management system 104.
In addition, in one or more embodiments, user 114 can facilitate providing access to co-user client devices 108a-n of digital content management system 104 by requesting to share one or more digital content items on digital content management system 104 with one or more identified co-users 110a-n associated with user 114. For example, digital content management system 104 can share access to one or more digital content items with a team of users including co-users 110a-n and user 114. In one or more embodiments, digital content management system 104 shares access to one or more co-users 110a-n by providing access to the digital content items from a user account of user 114 via co-users accounts of the respective co-users 110a-n. Alternatively, in one or more embodiments, digital content management system 104 shares access to one or more co-users 110a-n including non-users of digital content management system 104 by providing one or more shared links that facilitate access to digital content items stored on digital content management system 104. Accordingly, digital content management system 104 can provide access to any user of digital content management system 104 with whom user 114 has shared access.
In one or more embodiments, digital content management system 104 provides selective access to digital content items on a user account. For instance, digital content management system 104 can provide access to a single file, folder of files, or multiple selected files and folders from a larger collection of digital content items on a user account associated with user 114. In addition, digital content management system 104 can share access to single files, folders, or multiple selected files and folders from collections of digital content items between co-users 110a-n and user 114.
In addition to generally storing, sharing, and otherwise facilitating access to digital content items maintained on digital content management system 104, in one or more embodiments, synchronization system 106 facilitates synchronization of digital content items of digital content items associated with user 114. In particular, as described here, synchronization system 106 can synchronize a digital content item on digital content management system 104 to a local storage space of client device 112. As used herein, “synchronizing” a digital content item refers to downloading a local copy of a digital content item to a client device corresponding to a copy of the digital content item on digital content management system 104. In addition, synchronizing a digital content item can refer to updating the local copy of the digital content item to correspond to a current copy of the digital content item on digital content management system 104. For example, synchronization system 106 can periodically update the local copy of the digital content item by replacing the local copy with an updated copy including any edits or modifications made by user 114 and/or one or more co-users 108a-n of digital content management system 104.
In addition, as will be described in further detail below, in one or more embodiments, synchronization system 106 identifies one or more digital content items (e.g., associated with a user account) of digital content items to synchronize for a respective user. For example, in one or more embodiments, synchronization system 106 selectively identifies digital content items of digital content items associated with user 114 to automatically synchronize or, alternatively, to recommend synchronizing to a local storage of client device 112. In particular, synchronization system 106 selectively identifies digital content items of interest to synchronize to the local storage of client device 112 based on a determined likelihood that user 114 would synchronize or later request access to the identified digital content items.
In one or more embodiments, synchronization system 106 determines a coefficient between user 114 and digital content items of a collection of digital content items based on an analysis of the recall data associated with user 114 and co-users 110a-n of digital content management system 104. In particular, in one or more embodiments, synchronization system 106 determines a synchronization score indicative of whether user 114 will synchronize or otherwise request access to a given digital content item based on recall data associated with the given digital content item. In particular, synchronization system 106 determines a synchronization score with respect to a digital content item indicating a likelihood that a given user having a similar recall history with respect digital content items of the collection of digital content items will synchronize the digital content item. Synchronization system 106 can determine the synchronization score based on a combination of user-recall data and co-user recall data.
In addition, synchronization system 106 can determine the synchronization score using a variety of methods and techniques. For instance, as will be described in further detail in connection with
Upon identifying synchronizations scores for each of the digital content items of a collection of digital content items, synchronization system 106 can further provide a notification or recommendation associated with synchronizing one or more digital content items of interest to user 114. For example, in one or more embodiments, synchronization system 106 automatically synchronizes one or more digital content items of interest to user 114. In addition, or as an alternative, in one or more embodiments, synchronization system 106 provides a recommendation to synchronize one or more digital content items of interest to user 114. In one or more embodiments, synchronization system 106 provides an indication of one or more digital content items for synchronization to client device 112 causing content management application 116 to provide notifications and/or recommendations associated with synchronizing digital content items to the local storage of client device 112 via a graphical user interface of client device 112.
Additional detail will now be given with respect to identifying digital content items of interest for synchronization in accordance with one or more embodiments. In particular,
In particular, as shown in
In one or more embodiments, synchronization system 106 constructs a user profile for user 114 including recall data 212 associated with user 114. In particular, synchronization system 106 can build a user profile including interaction data with respect to any number of digital content items recalled by user 114. For example, the user profile can include an identification of recalled digital content items, a number of times that corresponding digital content items have been recalled by user 114, types of interactions (e.g., viewing, editing, downloading, synchronizing, etc.) performed with respect to digital content items, and other data associated with interactions by user 114 in connection with respective digital content items.
As further shown in
As shown in
As shown in
As an overview, and as will be described in further detail in connection with
In addition, and as will be described in further detail in connection with
Moreover, as will be described in further detail in connection with
For example, as will be described in further detail below in connection with
In one or more embodiments, synchronization prediction model 202 further includes combiner function 210 to combine outputs from the analysis models 204-208 for the collection of digital content items to determine synchronization scores 218 for respective digital content items. For example, synchronization system 106 can determine a content score, collaboration score, and/or latent factor score for each digital content items from the collection of digital content items, combine the scores using the combiner function 210 and generate synchronization scores for respective digital content items from the collection of digital content items.
While one or more embodiments involve determining outputs for each of the analysis models 204-208 for each digital content item, in one or more embodiments, synchronization system 106 determines a subset of the three outputs based on available information with respect to the digital content items. For example, where a digital content item has been recently added to the collection and has no recall history, synchronization system 106 may determine a synchronization score based on an output of content-based model 204 and another output of latent factor model 208 without considering an output of collaboration model 206. As another example, where a user has recently registered an account with digital content management system 104 and has a limited recall history, synchronization system 106 can similarly consider a subset of relevant outputs to determine a corresponding synchronization score.
In one or more embodiments, synchronization system 106 applies weights to respective outputs of models 204-208 of synchronized prediction model 202. As an example, where a user has a limited recall history, synchronization system 106 (e.g., combiner function 210) can apply a greater weight to an output of content-based model 204 than an output of collaboration model 206. In addition, as the user interacts with the collection of digital content item creating a more extensive recall history, synchronization system 106 (e.g., combiner function 210) can apply a greater weight to an output of collaboration model 206 while decreasing the weight applied to the output of content-based model 204. In one or more embodiments, synchronization system 106 applies a linear model for decreasing the weight of the content-based model 204 while increasing the weight of the correlation based model 206 over time.
In one or more embodiments, synchronization prediction model 202 includes a machine learning model trained to output synchronization scores based on identified patterns of interactions with respect to sample digital content items and whether users associated with the interactions eventually synchronized the sample digital content items. For example, synchronization system 106 can analyze sample data including a history of sample user recall data, sample content collection data, and an indication of whether users associated with the sample recall data eventually synchronize corresponding digital content items.
For example, synchronization system 106 can train content-based model 204 by fine-tuning one or more algorithms for comparing features of digital content item and associated synchronization histories. In addition, synchronization system 106 can train collaboration model 206 by fine-tuning one or more algorithms for comparing user profiles and associated synchronization histories. Further, synchronization system 106 can utilize machine learning optimization to capture global and local correlations between user factors and digital content factors to train latent factor model 208 to determine synchronization probabilities for users and corresponding digital content items having corresponding recall data and content collection data. In addition, in one or more embodiments, synchronization system 106 can train combiner function 210 to fine-tune how to combine outputs from the respective analysis models 204-208 in determining synchronization scores 218 for respective digital content items.
As further shown, synchronization system 106 generates content profile 304 for digital content item 302 including features associated with digital content item 302. In particular, as shown in
As further shown by
Based on the identified similarities and associated recall data, synchronization system 106 can determine score 316 based on the content-to-content comparison of content profile 304 and digital content item profiles 314a-d and associated recall data. For example, where content profile 304 and a corresponding digital content item profile have similar profiles and where the digital content item corresponding to a digital content item profile has been recalled frequently, synchronization system 106 can boost score 316 based on the identified similarities and recall frequency. Alternatively, where content profile 304 has a similar profile to a digital content item profile where the corresponding digital content item has been recalled infrequently (or has not been synchronized), synchronization system 106 can decrease score 316 for digital content item 302. As another example, where content profile 304 and a digital content item profile share few (e.g., zero) similarities, synchronization system 106 can disregard the digital content item profile when determining score 316. In one or more embodiments, synchronization system 106 combines comparisons between content profile 304 and digital content item profiles 314a-d to determine score 316, as shown in
Synchronization system 106 can determine content score by comparing features of digital content items using a variety of algorithms. For example, as mentioned above, in one or more embodiments, synchronization system 106 trains a machine learning model that compares features of digital content item profiles. As another example, in one or more embodiments, synchronization system 106 applies an algorithm that compares features of digital content items from the collection of digital content items. For instance, in one or more embodiments, synchronization system 106 applies the following formula:
where x refers to a user profile, i refers to a digital content item profile and u(x, i) refers to an estimated content score corresponding to digital content item profile i.
Determining the synchronization score for a digital content item using the content-based model as described in connection with
Moving onto
As shown in
In determining correlation scores, synchronization system 106 compares user profile 402 to co-user profiles 404a-c associated with respective co-users (e.g., co-users 110a-n) of digital content management system 104. In particular, as shown in
For example, with respect to
Synchronization system 106 can use various algorithms and analysis techniques to compare features and characteristics of user profiles. In one or more embodiments, synchronization system 106 trains a machine learning model to fine-tune one or more algorithms that compare features of user profiles. As another example, in one or more embodiments, synchronization system 106 applies an algorithm that compares features of user profiles with respect to digital content items recalled by users associated with the respective user profiles.
As mentioned above, in one or more embodiments, synchronization system 106 identifies co-users having similar co-user profiles as a user profile of user 114. In particular, in one or more embodiments, synchronization system 106 determines recall vectors representative of respective user profiles and compares the recall vectors using one or more different algorithms. As a first example, synchronization system 106 identifies similar users by comparing recall vectors using the following Jaccard algorithm:
where rx refers to a recall vector of user x and ry refers to a recall vector of user y. As another example, synchronization system 106 can identify similar users using the following Cosine similarity algorithm:
where rx refers to a recall vector of user x and ry refers to a recall vector of user y. In another example, synchronization system 106 can identify similar users using the following Pearson correlation coefficient algorithm:
where Sxy refers to digital content items recalled by both users x and y.
Upon identifying similar user profiles associated with a user profile of user 114, synchronization system 106 can further utilize the similar profiles to determine collaboration scores (e.g., recall predictions) using a variety of different algorithms. For example, in one or more embodiments, synchronization system 106 determines a collaboration score based on an average of similar users using the following algorithm for N similar co-users:
As an alternative to a straight or unweighted average, synchronization system 106 can determine a weighted average based on N similar users using the following algorithm:
While the above algorithms relate specifically to comparing user profiles, in one or more embodiments, synchronization system 106 utilizes similar algorithms to determine collaboration scores based on a comparison between digital content profiles. For example, as an alternative to the content-based model described above in connection with
In addition, in one or more embodiments, synchronization system 106 combines the result of the correlation equations described herein to determine a correlation score for a given digital content item.
In one or more embodiments, synchronization system 106 further implements one or more optimizations to the collaborative model for determining collaboration scores for digital content items. For example, as mentioned above, synchronization system can use the following basic collaborative filtering algorithm to determine a collaboration score for a given user with respect to a digital content item:
In addition, in one or more embodiments, synchronization system 106 extracts a bias value to account for one or more pairwise similarities that neglect interdependency among users using a convex optimization algorithm. In particular, synchronization system 106 can account for bias using the following algorithm:
where bxi=μ+bx+bi with μ referring to an overall mean score, bx referring to a score deviation of user x and bi referring to score deviation of file i. In addition, as an alternative to arbitrarily computing sim(i, j), synchronization system 106 can estimate wij from the data, which models interaction between pairs of files and not depend on user x. In particular, in one or more embodiments, synchronization system 106 the following algorithm to solve a stochastic gradient descent based on a transformed standard convex optimization problem:
rxi=bxi+Σj∈N(i;x)wij(rxj−bxj)
Determining correlation scores based on a comparison of user profiles (and digital content item profiles) as described herein has a number of advantages and benefits. For example, the above described correlation algorithms facilitate effective identification of digital content items of interest for user 114 by analyzing co-user recall data associated with co-users associated with user 114. In particular, where user 114 joins a team of co-users 110a-n for a particular project, synchronization system 106 can effectively predict digital content items that will be of interest to user 114 without an extensive recall history of user 114 with respect to a number of digital content items.
Proceeding onto
In one or more embodiments, synchronization system 106 generates a score for each digital content item based on identified recall data. In addition, as shown in
Synchronization system 106 can determine scores for respective fields of score matrix 502 in a variety of ways. For example, in one or more embodiments, synchronization system 106 utilizes the content-based model and/or correlation model to determine respective scores within score matrix 502. As another example, synchronization system 106 can assign a score based on a number of times a user of digital content management system 104 has recalled a digital content item. In one or more embodiments, synchronization system 106 receives global recall data for one or more digital content items and populates the fields of score matrix 502 based on global recall data (e.g., recall data from any number of users having access to digital content item).
As further shown, score matrix 502 includes blank or null scores within respective fields of score matrix 502 for digital content items for which recall data is limited (e.g., unavailable or does not exist because the digital content item has not been recalled). In one or more embodiments, synchronization system 106 utilizes known values of score matrix 502 to extrapolate scores for pairings of users and corresponding digital content items. For example, synchronization system 106 extrapolates scores for pairings having limited recall data (e.g., no recall data) based on scores for pairings that have more extensive recall data. In particular, as shown in
In one or more embodiments, synchronization system 106 factorizes score matrix 502 based on the known values of score matrix 502. In particular, synchronization system 106 can factorize score matrix 502 into Q-Matrix 504 and P-Matrix 506 (e.g., PT-Matrix) for the known values of score matrix 502. As shown in
As shown in
rxi=Σfqif·pxf
where rxi refers to a missing value of score matrix 502 corresponding to user x for digital content item i, qi refers to row i of matrix-Q 504, and px refers to column x of matrix-P 506. In particular, as shown in
In one or more embodiments, synchronization system 106 performs one or more additional optimizations to fine-tune or otherwise refine determined values of score matrix 502. For example, in one or more embodiments, in addition to the above algorithm for estimating respective fields of score matrix 502, synchronization system 106 determines unknown values of score matrix 502 by minimizing the following optimization algorithm:
minP,QΣ(i,x)∈R(rxi−qi·px)2+[λ1Σx∥px∥2+λ1Σi∥qi∥2]
where Q and P need not be orthogonal, in contrast to a single value decomposition, and the last two terms provide regulation to prevent overfitting when determining the unknown values of score matrix 502.
Accordingly, in one or more embodiments, synchronization system 106 utilizes scores from score matrix 502 to determine latent factor scores for each of the digital content items from the collection of digital content items. Indeed, predicting scores based on the latent factor model described in
As mentioned above, synchronization system 106 can utilize each of the above described analysis models alone or in combination. For example, in one or more embodiments, synchronization system 106 utilizes content-based model 204 including features and functionality described in connection with
Utilizing the synchronization prediction model 202 including individual or a combination of the above-described analysis models provides a substantial improvement over conventional methods for determining one or more digital content items to synchronize to a local storage of a client device. In particular, each of the above-described analysis models provide an improvement over random predictions for a sample set of recalls by users of digital content items 104. For example, using the following algorithm:
An accuracy of the above-described models can be demonstrated, where “Hits” refers to instances of recall of a given digital content item by a given user of digital content management system 104. Further, when used in combination, synchronization system 106 achieves improved accuracy over random prediction methods.
As mentioned above, synchronization system 106 can provide one or more synchronization recommendations to user 114 via a graphical user interface of client device 112 based on determined synchronization scores in accordance with one or more embodiments described herein. For example,
As shown in
As another example, synchronization system 106 can provide recommended files 608 for synchronization including digital content items B and C based on a determination that digital content items B and C have high synchronization scores. In particular, synchronization system 106 can provide recommended files 608 for synchronization including digital content items B and C based on a determination that synchronization scores for digital content items B and C exceed a second threshold score (e.g., a medium threshold score) without exceeding the first threshold score associated with a threshold probability that a user of client device 602 would synchronize digital content items B and C. Synchronization system 106 can utilize one or more additional threshold scores in identifying synchronization recommendations. For example, synchronization system 106 can utilize one or more user set thresholds (e.g., a threshold manually set or selected by a user) for automatically synchronizing and/or recommending digital content items for synchronization. Alternatively, synchronization system 106 can utilize one or more system set (e.g., a default threshold) for automatically synchronizing and/or recommending digital content items for synchronization.
Moreover, while automatically synchronized files 606 and recommended files 608 may refer to files uniquely suited to a user of client device 602, in one or more embodiments, synchronization system 106 may provide a list of popular files 610 including one or more digital content items generally popular to users of digital content management system 104 (while not necessarily including digital content items having synchronization scores that exceed one or more predetermined threshold scores). Popular files 610 can include default files, template files, setup files, or other files that are popular, but not frequently or recently recalled by users of digital content management system 104.
As further shown, synchronization system 106 can provide one or more synchronization options that enable a user of client device 602 to select one more digital content items to synchronize based on the recommendations. For example, as shown in
In addition, synchronization system 106 provides selectable options to enable a user of client device 602 to synchronize multiple files at once. For example, synchronization system 106 provides sync all options 614 for respective categories (e.g., recommended files 608, popular files 610) that enable a user of client device 602 to select multiple digital content items within a single category for synchronization. In addition, synchronization system 106 provides a sync files option 616 that enables a user of client device 602 to select all displayed options for synchronization to a local storage of client device 602. Alternatively, in one or more embodiments, synchronization system 106 provides one or more options to unsynchronize (e.g., delete from local storage) individual files and/or categories of files.
Turning now to
As shown in
In one or more embodiments, components of synchronization system 106 may, for example, be implemented as one or more stand-alone applications, as one or more modules of an application, as one or more plug-ins, as one or more library functions or functions that may be called by other applications (e.g., a web application), and/or as a cloud-computing model.
In addition, while
As shown in
In one or more embodiments, recall data manager 702 generates profiles for users and digital content items. For example, recall data manager 702 can generate a user profile including recall data for a respective user (e.g., user 114, co-users 110a-n) of digital content management system 104. In addition, recall data manager 702 can generate content profiles for each of the digital content items including recall data associated with the digital content items in addition to file information (e.g., file owner, namespace, file extension, etc.).
As further shown in
As further shown in
As mentioned above, in one or more embodiments, synchronization score manager 706 determines a synchronization score by combining results of multiple analysis models. For example, in one or more embodiments, synchronization score manager 706 utilizes a combiner function (e.g., combiner function 210) to combine outputs of respective analysis models. In one or more embodiments, synchronization score manager 706 determines a synchronization score by summing the outputs of the analysis models. Alternatively, in one or more embodiments, synchronization score manager 706 determines a synchronization score by applying different weights to the outputs of the analysis models.
For example, in one or more embodiments, synchronization score manager 706 applies different weights to respective outputs of analysis models 204-208 based on one or more factors associated with user 114 and/or respective digital content items. For instance, where user 114 is a new user of digital content management system 104 and has a limited recall history, synchronization score manager 706 may apply a higher weight to an output of content-based model 204 while applying a lower weight to an output of collaboration model 206 in combining the outputs to determine the synchronization score. Alternatively, where user 114 has an extensive recall history, synchronization score manager 706 can apply a higher weight to an output of collaboration model 206. Moreover, because latent factor model 208 often yields more accurate results individually than content-based model 204 and/or collaboration model 206, in one or more embodiments, synchronization score manager 706 applies the highest weight to the output of latent factor-based model 208.
As further shown in
In one or more embodiments, sync recommendation manager 708 provides different types of synchronization recommendations based on determined synchronization scores. For example, in one or more embodiments, sync recommendation manager 708 compares a synchronization score for a given digital content item to multiple thresholds corresponding with different recommendation-types. For instance, in one or more embodiments, sync recommendation manager 708 determines whether a synchronization score exceeds a high threshold corresponding to a near certainty that user 114 will synchronize a digital content item to a local storage of client device 112. If the synchronization score exceeds the high threshold, sync recommendation manager 708 automatically synchronizes the digital content item for user 114. As another example, sync recommendation manager 708 can provide a recommendation to synchronize (e.g., without automatically synchronizing) including a selectable option to synchronize based on determining that a synchronization score for a digital content item exceeds a recommendation threshold without exceeding the high threshold associated with automatic synchronization. Sync recommendation manager 708 can similarly compare synchronization scores with other thresholds associated with different types of recommendations.
In one or more embodiments, synchronization system 106 includes a collaboration service that provides an interactive content item collaboration platform whereby users (e.g., user 114 and co-users 110a-n) can simultaneously create collaboration content items, comment in the collaboration content items, and manage tasks within the collaboration content items. Collaboration content items can be files that users can create and edit using a collaboration content item editor and can contain collaboration content item elements. Collaboration content item elements may include a collaboration content item identifier, one or more author identifiers, collaboration content item text, collaboration content item attributes, interaction information, comments, sharing users, etc. Collaboration content item elements can be stored as database entities, which allows for searching and retrieving the collaboration content items. Multiple users may access, view, edit, and collaborate on collaboration content items at the same time or at different times. In some embodiments, this can be managed by requiring two users access a content item through a web interface and there they can work on the same copy of the content item at the same time.
As further shown in
In addition, data storage 710 includes user data 714. User data 714 can include any information associated with a given user of digital content management system 104. For example, user data 714 can include a recall history including identified digital content items that an associated user has recalled. In one or more embodiments, user data 714 includes user profiles for any number of users of digital content management system 104 including recall histories, identifiers of digital content items to which users have access, and other information associated with respective users.
As further shown, data storage 710 includes recall data 716. Recall data 716 can include any recall data by user 114 and co-users 110a-n of digital content management system 104 with respect to digital content items recalled by user 114 and/or co-users 110a-n of digital content management system 104. For example, recall data 716 can include identified digital content items that users have recalled in addition to information about interactions by the user with respect to the recalled digital content items. In addition, recall data 716 can include information about frequency of recall by users (e.g., collectively or individually) of digital content management system 104.
Each of the components 702-716 can comprise software, hardware, or both. For example, components 702-716 can comprise one or more instructions stored on a computer-readable storage medium and executable by processors of one or more computing devices. When executed by the one or more processors, the computer-executable instructions of synchronization system 106 can cause a server device and/or client device to perform the methods described herein. Alternatively, components 702-716 and their corresponding elements can comprise hardware, such as a special purpose processing device to perform a certain function or group of functions. Additionally, components 702-716 can comprise a combination of computer-executable instructions and hardware.
Furthermore, components 702-716 may, for example, be implemented as one or more operating systems, as one or more stand-alone applications, as one or more modules of an application, as one or more plug-ins, as one or more library functions or functions that may be called by other applications, and/or as a cloud-computing model. Thus, components 702-716 may be implemented as a stand-alone application, such as a desktop or mobile application. Furthermore, components 702-716 may be implemented as one or more web-based applications hosted on a remote server. Components 702-716 may also be implemented in a suite of mobile device applications or “apps.”
Turning now to
As further shown in
As further shown in
In one or more embodiments, method 800 includes determining the synchronization score for each digital content item from the collection of digital content items using a content-based analysis model (e.g., content-based model 204). For example, in one or more embodiments, method 800 includes constructing (e.g., from the user recall and team recall data) a content profile for the digital content item including file data for the digital content item and a history of interactions by the user account and the co-user accounts with respect to the digital content item. In addition, in one or more embodiments, method 800 includes generating the synchronization score based on a comparison between the content profile for the digital content item and content profiles for the recalled digital content items by the user account (from the user recall data) and the recalled digital content items by the co-user accounts (from the team recall data).
In one or more embodiments, method 800 includes determining the synchronization score for each digital content item using a collaboration analysis model (e.g., collaboration model 206). For example, in one or more embodiments, method 800 includes comparing identifiers of recalled digital content items from the user recall data with identifiers of recalled digital content items from the team recall data to identify a subset of co-users (e.g., a subset of co-user accounts) from the co-users (e.g., the co-user accounts) of the digital content management system having a similar recall history as the user account associated with the client device with respect to the collection of digital content items. In addition, in one or more embodiments, method 800 includes generating the synchronization score based on a comparison of the user recall data and team recall data associated with the subset of co-users (e.g., without considering team recall data from co-user accounts not included within the subset of co-user accounts).
In one or more embodiments, method 800 includes determining the synchronization score for each digital content item using a latent factor analysis model (e.g., latent factor model 208). For example, in one or more embodiments, method 800 includes generating a matrix (e.g., score matrix 502) representative of a recall history of users (e.g., user accounts) of the digital content management system with respect to the collection of digital content items. In one or more embodiments, the matrix includes a first plurality of fields including known scores between pairs of users (e.g., user accounts) of the digital content management system and digital content items that have been recalled by respective users of the digital content management system and a second plurality of fields including unknown scores between pairs of users and digital content items that have not been recalled by respective users of the digital content management system. In addition, in one or more embodiments, method 800 includes extrapolating scores for the second plurality of fields based on the known scores of the first plurality of fields.
In one or more embodiments, extrapolating the scores for the second plurality of fields includes factorizing the matrix to generate a Q-Matrix and a P-Matrix based on the known scores of the first plurality of fields. Extrapolating the scores can further include determining, for each field of the second plurality of fields of the matrix, a dot product of corresponding rows and columns of the Q-Matrix and the P-Matrix. In one or more embodiments, method 800 further includes determining the synchronization score based on the known values of the first plurality of fields of the matrix and the extrapolated scores for the second plurality of fields of the matrix.
As further shown in
In one or more embodiments, method 800 further includes detecting a selection (e.g., a user input) of the synchronization recommendation. For example, in one or more embodiments, providing the synchronization recommendation includes providing a selectable option corresponding to one or more identified digital content items (e.g., digital content items having a synchronization score that exceeds a threshold synchronization score). In addition, in one or more embodiments, method 800 includes synchronizing (e.g., automatically or in response to detecting a user selection of the selectable option) the one or more digital content items by downloading one or more copies of the one or more digital content items to a local storage of the client device where the one or more copies of the one or more digital content items (e.g., corresponding to one or more high resolution or original copies of the one or more digital content items maintained on the digital content management system). In one or more embodiments, synchronizing the one or more digital content items includes periodically updating the one or more copies of the one or more digital content items to correspond to one or more current versions of the one or more digital content items maintained on the digital content management system.
In one or more embodiments, method 800 includes identifying a first plurality of content items having synchronization scores that exceed a first threshold. In addition, in one or more embodiments, method 800 includes based on the first plurality of content items exceeding the first threshold, automatically synchronizing the first plurality of content items to a local storage of the client device of the user (e.g., based on the synchronization scores exceeding the first threshold and without receiving additional user input or requiring additional user action prior to synchronizing the first plurality of digital content items). In one or more embodiments, method 800 includes identifying a second plurality of content items having synchronization scores that exceed a second threshold without exceeding the first threshold. Further, in one or more embodiments, method 800 includes, based on the second plurality of content items exceeding the second threshold without exceeding the first threshold, providing the recommendation to synchronize the second plurality of content items to the client device without automatically synchronizing the second plurality of content items to the local storage of the client device.
Embodiments of the present disclosure may comprise or utilize a special purpose or general-purpose computer including computer hardware, such as, for example, one or more processors and system memory, as discussed in greater detail below. Embodiments within the scope of the present disclosure also include physical and other computer-readable media for carrying or storing computer-executable instructions and/or data structures. In particular, one or more of the processes described herein may be implemented at least in part as instructions embodied in a non-transitory computer-readable medium and executable by one or more computing devices (e.g., any of the media content access devices described herein). In general, a processor (e.g., a microprocessor) receives instructions, from a non-transitory computer-readable medium, (e.g., a memory, etc.), and executes those instructions, thereby performing one or more processes, including one or more of the processes described herein.
Computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer system. Computer-readable media that store computer-executable instructions are non-transitory computer-readable storage media (devices). Computer-readable media that carry computer-executable instructions are transmission media. Thus, by way of example, and not limitation, embodiments of the disclosure can comprise at least two distinctly different kinds of computer-readable media: non-transitory computer-readable storage media (devices) and transmission media.
Non-transitory computer-readable storage media (devices) includes RAM, ROM, EEPROM, CD-ROM, solid state drives (“SSDs”) (e.g., based on RAM), Flash memory, phase-change memory (“PCM”), other types of memory, other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer.
A “network” is defined as one or more data links that enable the transport of electronic data between computer systems and/or modules and/or other electronic devices. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a computer, the computer properly views the connection as a transmission medium. Transmissions media can include a network and/or data links which can be used to carry desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer. Combinations of the above should also be included within the scope of computer-readable media.
Further, upon reaching various computer system components, program code means in the form of computer-executable instructions or data structures can be transferred automatically from transmission media to non-transitory computer-readable storage media (devices) (or vice versa). For example, computer-executable instructions or data structures received over a network or data link can be buffered in RAM within a network interface module (e.g., a “NIC”), and then eventually transferred to computer system RANI and/or to less volatile computer storage media (devices) at a computer system. Thus, it should be understood that non-transitory computer-readable storage media (devices) can be included in computer system components that also (or even primarily) utilize transmission media.
Computer-executable instructions comprise, for example, instructions and data which, when executed at a processor, cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. In some embodiments, computer-executable instructions are executed on a general purpose computer to turn the general purpose computer into a special purpose computer implementing elements of the disclosure. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, or even source code. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the described features or acts described above. Rather, the described features and acts are disclosed as example forms of implementing the claims.
Those skilled in the art will appreciate that the disclosure may be practiced in network computing environments with many types of computer system configurations, including, personal computers, desktop computers, laptop computers, message processors, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile telephones, PDAs, tablets, pagers, routers, switches, and the like. The disclosure may also be practiced in distributed system environments where local and remote computer systems, which are linked (either by hardwired data links, wireless data links, or by a combination of hardwired and wireless data links) through a network, both perform tasks. In a distributed system environment, program modules may be located in both local and remote memory storage devices.
Embodiments of the present disclosure can also be implemented in cloud computing environments. In this description, “cloud computing” is defined as a model for enabling on-demand network access to a shared pool of configurable computing resources. For example, cloud computing can be employed in the marketplace to offer ubiquitous and convenient on-demand access to the shared pool of configurable computing resources. The shared pool of configurable computing resources can be rapidly provisioned via virtualization and released with low management effort or service provider interaction, and then scaled accordingly.
A cloud-computing model can be composed of various characteristics such as, for example, on-demand self-service, broad network access, resource pooling, rapid elasticity, measured service, and so forth. A cloud-computing model can also expose various service models, such as, for example, Software as a Service (“SaaS”), Platform as a Service (“PaaS”), and Infrastructure as a Service (“IaaS”). A cloud-computing model can also be deployed using different deployment models such as private cloud, community cloud, public cloud, hybrid cloud, and so forth. In this description and in the claims, a “cloud-computing environment” is an environment in which cloud computing is employed.
In particular embodiments, processor 902 includes hardware for executing instructions, such as those making up a computer program. As an example and not by way of limitation, to execute instructions, processor 902 may retrieve (or fetch) the instructions from an internal register, an internal cache, memory 904, or storage device 906 and decode and execute them. In particular embodiments, processor 902 may include one or more internal caches for data, instructions, or addresses. As an example and not by way of limitation, processor 902 may include one or more instruction caches, one or more data caches, and one or more translation lookaside buffers (TLBs). Instructions in the instruction caches may be copies of instructions in memory 904 or storage 906.
Memory 904 may be used for storing data, metadata, and programs for execution by the processor(s). Memory 904 may include one or more of volatile and non-volatile memories, such as Random Access Memory (“RAM”), Read Only Memory (“ROM”), a solid state disk (“SSD”), Flash, Phase Change Memory (“PCM”), or other types of data storage. Memory 904 may be internal or distributed memory.
Storage device 906 includes storage for storing data or instructions. As an example and not by way of limitation, storage device 906 can comprise a non-transitory storage medium described above. Storage device 906 may include a hard disk drive (HDD), a floppy disk drive, flash memory, an optical disc, a magneto-optical disc, magnetic tape, or a Universal Serial Bus (USB) drive or a combination of two or more of these. Storage device 906 may include removable or non-removable (or fixed) media, where appropriate. Storage device 906 may be internal or external to computing device 900. In particular embodiments, storage device 906 is non-volatile, solid-state memory. In other embodiments, Storage device 906 includes read-only memory (ROM). Where appropriate, this ROM may be mask programmed ROM, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), electrically alterable ROM (EAROM), or flash memory or a combination of two or more of these.
I/O interface 908 allows a user to provide input to, receive output from, and otherwise transfer data to and receive data from computing device 900. I/O interface 908 may include a mouse, a keypad or a keyboard, a touch screen, a camera, an optical scanner, network interface, modem, other known I/O devices or a combination of such I/O interfaces. I/O interface 908 may include one or more devices for presenting output to a user, including, but not limited to, a graphics engine, a display (e.g., a display screen), one or more output drivers (e.g., display drivers), one or more audio speakers, and one or more audio drivers. In certain embodiments, I/O interface 908 is configured to provide graphical data to a display for presentation to a user. The graphical data may be representative of one or more graphical user interfaces and/or any other graphical content as may serve a particular implementation.
Communication interface 910 can include hardware, software, or both. In any event, communication interface 910 can provide one or more interfaces for communication (such as, for example, packet-based communication) between computing device 900 and one or more other computing devices or networks. As an example and not by way of limitation, communication interface 910 may include a network interface controller (NIC) or network adapter for communicating with an Ethernet or other wire-based network or a wireless NIC (WNIC) or wireless adapter for communicating with a wireless network, such as a WI-FI.
Additionally or alternatively, communication interface 910 may facilitate communications with an ad hoc network, a personal area network (PAN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), or one or more portions of the Internet or a combination of two or more of these. One or more portions of one or more of these networks may be wired or wireless. As an example, communication interface 910 may facilitate communications with a wireless PAN (WPAN) (such as, for example, a BLUETOOTH WPAN), a WI-FI network, a WI-MAX network, a cellular telephone network (such as, for example, a Global System for Mobile Communications (GSM) network), or other suitable wireless network or a combination thereof.
Additionally, communication interface 910 may facilitate communications various communication protocols. Examples of communication protocols that may be used include, but are not limited to, data transmission media, communications devices, Transmission Control Protocol (“TCP”), Internet Protocol (“IP”), File Transfer Protocol (“FTP”), Telnet, Hypertext Transfer Protocol (“HTTP”), Hypertext Transfer Protocol Secure (“HTTPS”), Session Initiation Protocol (“SIP”), Simple Object Access Protocol (“SOAP”), Extensible Mark-up Language (“XML”) and variations thereof, Simple Mail Transfer Protocol (“SMTP”), Real-Time Transport Protocol (“RTP”), User Datagram Protocol (“UDP”), Global System for Mobile Communications (“GSM”) technologies, Code Division Multiple Access (“CDMA”) technologies, Time Division Multiple Access (“TDMA”) technologies, Short Message Service (“SMS”), Multimedia Message Service (“MMS”), radio frequency (“RF”) signaling technologies, Long Term Evolution (“LTE”) technologies, wireless communication technologies, in-band and out-of-band signaling technologies, and other suitable communications networks and technologies.
Communication infrastructure 912 may include hardware, software, or both that couples components of computing device 900 to each other. As an example and not by way of limitation, communication infrastructure 912 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a front-side bus (FSB), a HYPERTRANSPORT (HT) interconnect, an Industry Standard Architecture (ISA) bus, an INFINIBAND interconnect, a low-pin-count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCIe) bus, a serial advanced technology attachment (SATA) bus, a Video Electronics Standards Association local (VLB) bus, or another suitable bus or a combination thereof.
In particular, online content management system 1002 can manage synchronizing digital content across multiple client devices 1006 associated with one or more users. For example, a user may edit digital content using client device 1006. The online content management system 1002 can cause client device 1006 to send the edited digital content to online content management system 1002. Online content management system 1002 then synchronizes the edited digital content on one or more additional computing devices.
In addition to synchronizing digital content across multiple devices, one or more embodiments of online content management system 1002 can provide an efficient storage option for users that have large collections of digital content. For example, online content management system 1002 can store a collection of digital content on online content management system 1002, while the client device 1006 only stores reduced-sized versions of the digital content. A user can navigate and browse the reduced-sized versions (e.g., a thumbnail of a digital image) of the digital content on client device 1006. In particular, one way in which a user can experience digital content is to browse the reduced-sized versions of the digital content on client device 1006.
Another way in which a user can experience digital content is to select a reduced-size version of digital content to request the full- or high-resolution version of digital content from online content management system 1002. In particular, upon a user selecting a reduced-sized version of digital content, client device 1006 sends a request to online content management system 1002 requesting the digital content associated with the reduced-sized version of the digital content. Online content management system 1002 can respond to the request by sending the digital content to client device 1006. Client device 1002, upon receiving the digital content, can then present the digital content to the user. In this way, a user can have access to large collections of digital content while minimizing the amount of resources used on client device 1006.
Client device 1006 may be a desktop computer, a laptop computer, a tablet computer, a personal digital assistant (PDA), an in- or out-of-car navigation system, a handheld device, a smart phone or other cellular or mobile phone, or a mobile gaming device, other mobile device, or other suitable computing devices. Client device 1006 may execute one or more client applications, such as a web browser (e.g., Microsoft Windows Internet Explorer, Mozilla Firefox, Apple Safari, Google Chrome, Opera, etc.) or a native or special-purpose client application (e.g., Facebook for iPhone or iPad, Facebook for Android, etc.), to access and view content over network 1004.
Network 1004 may represent a network or collection of networks (such as the Internet, a corporate intranet, a virtual private network (VPN), a local area network (LAN), a wireless local area network (WLAN), a cellular network, a wide area network (WAN), a metropolitan area network (MAN), or a combination of two or more such networks) over which client devices 1006 may access online content management system 1002.
In the foregoing specification, the present disclosure has been described with reference to specific exemplary embodiments thereof. Various embodiments and aspects of the present disclosure(s) are described with reference to details discussed herein, and the accompanying drawings illustrate the various embodiments. The description above and drawings are illustrative of the disclosure and are not to be construed as limiting the disclosure. Numerous specific details are described to provide a thorough understanding of various embodiments of the present disclosure.
The present disclosure may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. For example, the methods described herein may be performed with less or more steps/acts or the steps/acts may be performed in differing orders. Additionally, the steps/acts described herein may be repeated or performed in parallel with one another or in parallel with different instances of the same or similar steps/acts. The scope of the present application is, therefore, indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope.
The present application is a continuation of U.S. application Ser. No. 15/964,267, filed on Apr. 27, 2018. The aforementioned application is hereby incorporated by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5165031 | Pruul et al. | Nov 1992 | A |
| 5452448 | Sakuraba et al. | Sep 1995 | A |
| 5862346 | Kley et al. | Jan 1999 | A |
| 6052735 | Ulrich et al. | Apr 2000 | A |
| 6125369 | Wu et al. | Sep 2000 | A |
| 6256634 | Moshaiov et al. | Jul 2001 | B1 |
| 6260040 | Kauffman et al. | Jul 2001 | B1 |
| 6272545 | Flanagin et al. | Aug 2001 | B1 |
| 6348932 | Nishikawa et al. | Feb 2002 | B1 |
| 6407750 | Gioscia et al. | Jun 2002 | B1 |
| 6467034 | Yanaka | Oct 2002 | B1 |
| 6496979 | Chen et al. | Dec 2002 | B1 |
| 6636873 | Carini et al. | Oct 2003 | B1 |
| 6636888 | Bookspan et al. | Oct 2003 | B1 |
| 6654746 | Wong et al. | Nov 2003 | B1 |
| 6725281 | Zintel et al. | Apr 2004 | B1 |
| 6757696 | Multer et al. | Jun 2004 | B2 |
| 6795688 | Plasson et al. | Sep 2004 | B1 |
| 6904185 | Wilkins et al. | Jun 2005 | B1 |
| 6938076 | Meyer et al. | Aug 2005 | B2 |
| 7039723 | Hu et al. | May 2006 | B2 |
| 7103357 | Kirani et al. | Sep 2006 | B2 |
| 7139555 | Apfel | Nov 2006 | B2 |
| 7143194 | Curley et al. | Nov 2006 | B1 |
| 7162454 | Donner et al. | Jan 2007 | B1 |
| 7228352 | Yaguchi et al. | Jun 2007 | B1 |
| 7263712 | Spencer | Aug 2007 | B2 |
| 7317699 | Godfrey et al. | Jan 2008 | B2 |
| 7319536 | Wilkins et al. | Jan 2008 | B1 |
| 7321919 | Jacobs et al. | Jan 2008 | B2 |
| 7369161 | Easwar et al. | May 2008 | B2 |
| 7372485 | Bodnar et al. | May 2008 | B1 |
| 7421458 | Taylor et al. | Sep 2008 | B1 |
| 7441180 | Kaczmarek et al. | Oct 2008 | B1 |
| 7502795 | Svendsen et al. | Mar 2009 | B1 |
| 7523191 | Thomas et al. | Apr 2009 | B1 |
| 7576752 | Benson et al. | Aug 2009 | B1 |
| 7644124 | Porter | Jan 2010 | B1 |
| 7680067 | Prasad et al. | Mar 2010 | B2 |
| 7707500 | Martinez | Apr 2010 | B2 |
| 7747596 | Bigioi et al. | Jun 2010 | B2 |
| 7773106 | Serdy, Jr. et al. | Aug 2010 | B2 |
| 7774326 | Arrouye et al. | Aug 2010 | B2 |
| 7809682 | Paterson et al. | Oct 2010 | B2 |
| 7873353 | Kloba et al. | Jan 2011 | B2 |
| 7885925 | Strong et al. | Feb 2011 | B1 |
| 7917628 | Hesselink et al. | Mar 2011 | B2 |
| 7930270 | Tsang | Apr 2011 | B2 |
| 7962137 | Coppinger et al. | Jun 2011 | B2 |
| 7962622 | Friend et al. | Jun 2011 | B2 |
| 8001088 | Tawa, Jr. | Aug 2011 | B2 |
| 8019900 | Sekar et al. | Sep 2011 | B1 |
| 8230026 | Gilhuly et al. | Jul 2012 | B2 |
| 8321374 | Holt et al. | Nov 2012 | B2 |
| 8341345 | Tulskie et al. | Dec 2012 | B2 |
| 8370298 | Strong et al. | Feb 2013 | B2 |
| 8392472 | Gupta et al. | Mar 2013 | B1 |
| 8600934 | Strong et al. | Dec 2013 | B2 |
| 8612439 | Prahlad et al. | Dec 2013 | B2 |
| 8620861 | Uhrhane et al. | Dec 2013 | B1 |
| 8650498 | Mihovilovic | Feb 2014 | B1 |
| 8965847 | Chang | Feb 2015 | B1 |
| 9037540 | Strong et al. | May 2015 | B2 |
| 9131054 | Vendrow et al. | Sep 2015 | B2 |
| 9501762 | Babenko et al. | Nov 2016 | B2 |
| 9817878 | Newhouse | Nov 2017 | B2 |
| 10057318 | Rashid et al. | Aug 2018 | B1 |
| 10158708 | Strong et al. | Dec 2018 | B2 |
| 10204338 | Lee | Feb 2019 | B2 |
| 10320904 | Strong et al. | Jun 2019 | B2 |
| 20020013852 | Janik | Jan 2002 | A1 |
| 20020032722 | Baynes et al. | Mar 2002 | A1 |
| 20020044159 | Kuroiwa et al. | Apr 2002 | A1 |
| 20020059604 | Papagan et al. | May 2002 | A1 |
| 20020065848 | Walker et al. | May 2002 | A1 |
| 20020066050 | Lerman et al. | May 2002 | A1 |
| 20020099772 | Deshpande et al. | Jul 2002 | A1 |
| 20020129096 | Mansour et al. | Sep 2002 | A1 |
| 20020161860 | Godlin et al. | Oct 2002 | A1 |
| 20020184264 | Berg et al. | Dec 2002 | A1 |
| 20020198858 | Stanley et al. | Dec 2002 | A1 |
| 20030004952 | Nixon et al. | Jan 2003 | A1 |
| 20030014478 | Noble | Jan 2003 | A1 |
| 20030018725 | Turner et al. | Jan 2003 | A1 |
| 20030028610 | Pearson | Feb 2003 | A1 |
| 20030037114 | Nishio et al. | Feb 2003 | A1 |
| 20030041094 | Lara et al. | Feb 2003 | A1 |
| 20030055825 | Chen et al. | Mar 2003 | A1 |
| 20030058277 | Bowman-Amuah | Mar 2003 | A1 |
| 20030065721 | Roskind | Apr 2003 | A1 |
| 20030074418 | Coker | Apr 2003 | A1 |
| 20030097361 | Huang et al. | May 2003 | A1 |
| 20030120680 | Agrawal et al. | Jun 2003 | A1 |
| 20030131098 | Huntington et al. | Jul 2003 | A1 |
| 20030154187 | Hayakawa et al. | Aug 2003 | A1 |
| 20030159136 | Huang et al. | Aug 2003 | A1 |
| 20030172127 | Northrup et al. | Sep 2003 | A1 |
| 20030182329 | Sato | Sep 2003 | A1 |
| 20030217181 | Kiiskinen | Nov 2003 | A1 |
| 20030218633 | Mikhail et al. | Nov 2003 | A1 |
| 20040015401 | Lee et al. | Jan 2004 | A1 |
| 20040024979 | Kaminsky et al. | Feb 2004 | A1 |
| 20040044732 | Fushiki et al. | Mar 2004 | A1 |
| 20040044799 | Sivaraman et al. | Mar 2004 | A1 |
| 20040054736 | Daniell et al. | Mar 2004 | A1 |
| 20040059711 | Jandel et al. | Mar 2004 | A1 |
| 20040068524 | Aboulhosn et al. | Apr 2004 | A1 |
| 20040070678 | Toyama et al. | Apr 2004 | A1 |
| 20040088420 | Allen et al. | May 2004 | A1 |
| 20040107236 | Nakagawa et al. | Jun 2004 | A1 |
| 20040123048 | Mullins et al. | Jun 2004 | A1 |
| 20040126750 | Theilmann et al. | Jul 2004 | A1 |
| 20040143598 | Drucker et al. | Jul 2004 | A1 |
| 20040148207 | Smith et al. | Jul 2004 | A1 |
| 20040148375 | Levett et al. | Jul 2004 | A1 |
| 20040172423 | Kaasten et al. | Sep 2004 | A1 |
| 20040177319 | Horn et al. | Sep 2004 | A1 |
| 20040267905 | McDonough et al. | Dec 2004 | A1 |
| 20040268364 | Faraj | Dec 2004 | A1 |
| 20050015441 | Attwood et al. | Jan 2005 | A1 |
| 20050038863 | Onyon et al. | Feb 2005 | A1 |
| 20050044164 | O'Farrell et al. | Feb 2005 | A1 |
| 20050044165 | O'Farrell et al. | Feb 2005 | A1 |
| 20050050479 | Bogdan et al. | Mar 2005 | A1 |
| 20050060281 | Bucher et al. | Mar 2005 | A1 |
| 20050091289 | Shappell et al. | Apr 2005 | A1 |
| 20050091595 | Shappell et al. | Apr 2005 | A1 |
| 20050149481 | Hesselink et al. | Jul 2005 | A1 |
| 20050149508 | Deshpande et al. | Jul 2005 | A1 |
| 20050165869 | Huang et al. | Jul 2005 | A1 |
| 20050192008 | Desai et al. | Sep 2005 | A1 |
| 20050193361 | Vitanov et al. | Sep 2005 | A1 |
| 20050198015 | Sezan et al. | Sep 2005 | A1 |
| 20050208803 | Rohatgi et al. | Sep 2005 | A1 |
| 20050223061 | Auerbach et al. | Oct 2005 | A1 |
| 20050246373 | Faulkner et al. | Nov 2005 | A1 |
| 20050246374 | Blinn et al. | Nov 2005 | A1 |
| 20050248374 | Kushnick | Nov 2005 | A1 |
| 20050262166 | Rajeev et al. | Nov 2005 | A1 |
| 20050278458 | Berger et al. | Dec 2005 | A1 |
| 20060018444 | Pantana et al. | Jan 2006 | A1 |
| 20060052091 | Onyon et al. | Mar 2006 | A1 |
| 20060053380 | Spataro et al. | Mar 2006 | A1 |
| 20060069809 | Serlet | Mar 2006 | A1 |
| 20060085429 | Wener et al. | Apr 2006 | A1 |
| 20060101053 | Proctor et al. | May 2006 | A1 |
| 20060101064 | Strong et al. | May 2006 | A1 |
| 20060123010 | Landry et al. | Jun 2006 | A1 |
| 20060156239 | Jobs et al. | Jul 2006 | A1 |
| 20060168000 | Bodlaender et al. | Jul 2006 | A1 |
| 20060170669 | Walker et al. | Aug 2006 | A1 |
| 20060184673 | Liebman | Aug 2006 | A1 |
| 20060198015 | Engler et al. | Sep 2006 | A1 |
| 20060242206 | Brezak et al. | Oct 2006 | A1 |
| 20060259957 | Tam et al. | Nov 2006 | A1 |
| 20060286536 | Mohler et al. | Dec 2006 | A1 |
| 20070005581 | Arrouye et al. | Jan 2007 | A1 |
| 20070005707 | Teodosiu et al. | Jan 2007 | A1 |
| 20070016586 | Samji et al. | Jan 2007 | A1 |
| 20070016695 | Rabbers et al. | Jan 2007 | A1 |
| 20070043830 | Housenbold et al. | Feb 2007 | A1 |
| 20070078938 | Hu et al. | Apr 2007 | A1 |
| 20070156434 | Martin et al. | Jul 2007 | A1 |
| 20070179989 | Maes | Aug 2007 | A1 |
| 20070180075 | Chasman et al. | Aug 2007 | A1 |
| 20070180084 | Mohanty et al. | Aug 2007 | A1 |
| 20070198473 | Carrier et al. | Aug 2007 | A1 |
| 20070209005 | Shaver et al. | Sep 2007 | A1 |
| 20070239898 | Friend et al. | Oct 2007 | A1 |
| 20070250645 | Meadows et al. | Oct 2007 | A1 |
| 20070276836 | Chatterjee et al. | Nov 2007 | A1 |
| 20070288614 | May et al. | Dec 2007 | A1 |
| 20070294366 | Ozzie et al. | Dec 2007 | A1 |
| 20080109448 | Aboel-Nil et al. | May 2008 | A1 |
| 20080126936 | Williams | May 2008 | A1 |
| 20080140732 | Wilson et al. | Jun 2008 | A1 |
| 20080168185 | Robbin et al. | Jul 2008 | A1 |
| 20080184125 | Suleiman et al. | Jul 2008 | A1 |
| 20080189627 | Nikitin et al. | Aug 2008 | A1 |
| 20080195729 | Chand et al. | Aug 2008 | A1 |
| 20080195739 | Ozzie et al. | Aug 2008 | A1 |
| 20080208870 | Tsang | Aug 2008 | A1 |
| 20080208998 | Warren et al. | Aug 2008 | A1 |
| 20080222212 | Prasad | Sep 2008 | A1 |
| 20080250083 | Kovacs et al. | Oct 2008 | A1 |
| 20080307504 | Cisler et al. | Dec 2008 | A1 |
| 20090024931 | Bae | Jan 2009 | A1 |
| 20090064284 | Poston et al. | Mar 2009 | A1 |
| 20090094252 | Wong et al. | Apr 2009 | A1 |
| 20090183060 | Heller et al. | Jul 2009 | A1 |
| 20090187609 | Barton et al. | Jul 2009 | A1 |
| 20090192976 | Spivack et al. | Jul 2009 | A1 |
| 20090300020 | Chen et al. | Dec 2009 | A1 |
| 20090327900 | Noll et al. | Dec 2009 | A1 |
| 20090328135 | Szabo et al. | Dec 2009 | A1 |
| 20100063670 | Brzezinski et al. | Mar 2010 | A1 |
| 20100115037 | Hull et al. | May 2010 | A1 |
| 20100115614 | Barile et al. | May 2010 | A1 |
| 20100153513 | Zahran | Jun 2010 | A1 |
| 20100198871 | Stiegler et al. | Aug 2010 | A1 |
| 20100205196 | Schreiber et al. | Aug 2010 | A1 |
| 20100241980 | Sosnosky et al. | Sep 2010 | A1 |
| 20100332682 | Sharp et al. | Dec 2010 | A1 |
| 20110010332 | Vasudevan et al. | Jan 2011 | A1 |
| 20110106880 | Strong et al. | May 2011 | A1 |
| 20120016915 | Choi et al. | Jan 2012 | A1 |
| 20120030378 | Kaila | Feb 2012 | A1 |
| 20120084355 | Locker et al. | Apr 2012 | A1 |
| 20120096389 | Flam et al. | Apr 2012 | A1 |
| 20120102410 | Gewecke et al. | Apr 2012 | A1 |
| 20120127156 | Goossens et al. | May 2012 | A1 |
| 20120197862 | Woytowitz et al. | Aug 2012 | A1 |
| 20120330887 | Young et al. | Dec 2012 | A1 |
| 20130007207 | Dietrich et al. | Jan 2013 | A1 |
| 20130066975 | Kantor et al. | Mar 2013 | A1 |
| 20130067594 | Kantor et al. | Mar 2013 | A1 |
| 20130091550 | Joyce et al. | Apr 2013 | A1 |
| 20130110903 | Myerscough et al. | May 2013 | A1 |
| 20130117423 | Gupta et al. | May 2013 | A1 |
| 20130191451 | Tse et al. | Jul 2013 | A1 |
| 20130198868 | Georgiev | Aug 2013 | A1 |
| 20130205251 | Cisler et al. | Aug 2013 | A1 |
| 20130212486 | Joshi et al. | Aug 2013 | A1 |
| 20130232187 | Workman et al. | Sep 2013 | A1 |
| 20130239014 | Patil | Sep 2013 | A1 |
| 20130246610 | Hirano | Sep 2013 | A1 |
| 20130275509 | Micucci et al. | Oct 2013 | A1 |
| 20130282830 | Besen et al. | Oct 2013 | A1 |
| 20130305039 | Gauda et al. | Nov 2013 | A1 |
| 20130311598 | Arrouye et al. | Nov 2013 | A1 |
| 20130311986 | Arrouye et al. | Nov 2013 | A1 |
| 20130318582 | McCann et al. | Nov 2013 | A1 |
| 20140095457 | Quan et al. | Apr 2014 | A1 |
| 20140181016 | Whitehead et al. | Jun 2014 | A1 |
| 20140188868 | Hunter et al. | Jul 2014 | A1 |
| 20140317031 | Babenko | Oct 2014 | A1 |
| 20140330857 | Hunter | Nov 2014 | A1 |
| 20150193347 | Kluesing | Jul 2015 | A1 |
| 20150213101 | Strong et al. | Jul 2015 | A1 |
| 20150222580 | Grue | Aug 2015 | A1 |
| 20150264115 | Reilly et al. | Sep 2015 | A1 |
| 20150358406 | Scheer | Dec 2015 | A1 |
| 20160026704 | Strong et al. | Jan 2016 | A1 |
| 20160028809 | Strong et al. | Jan 2016 | A1 |
| 20160028810 | Strong et al. | Jan 2016 | A1 |
| 20160028811 | Rashid et al. | Jan 2016 | A1 |
| 20160028812 | Strong et al. | Jan 2016 | A1 |
| 20160028813 | Strong et al. | Jan 2016 | A1 |
| 20160028814 | Strong et al. | Jan 2016 | A1 |
| 20160028815 | Strong et al. | Jan 2016 | A1 |
| 20160028852 | Strong et al. | Jan 2016 | A1 |
| 20160055171 | Araki et al. | Feb 2016 | A1 |
| 20170017352 | Kanter | Jan 2017 | A1 |
| 20170093780 | Lieb | Mar 2017 | A1 |
| 20170104648 | Meier | Apr 2017 | A1 |
| 20180278684 | Rashid et al. | Sep 2018 | A1 |
| 20180304434 | Sakugawa et al. | Oct 2018 | A1 |
| 20230004529 | Berman et al. | Jan 2023 | A1 |
| Entry |
|---|
| Advisory Action from U.S. Appl. No. 15/964,267, dated Feb. 18, 2021, 3 pages. |
| Advisory Action from U.S. Appl. No. 14/873,004, dated May 19, 2020, 3 pages. |
| Advisory Action from U.S. Appl. No. 15/992,342, dated May 19, 2020, 3 pages. |
| Deshpande M., et al., “Item-Based Top-N Recommendation Algorithms,” ACM Transactions on Information Systems, vol. 22, No. 1, Jan. 2004, pp. 143-177. |
| Final Office Action from U.S. Appl. No. 14/873,004, dated Feb. 12, 2020, 18 pages. |
| Final Office Action from U.S. Appl. No. 15/964,267, dated Nov. 19, 2021, 25 pages. |
| Final Office Action from U.S. Appl. No. 15/964,267, dated Nov. 30, 2020, 27 pages. |
| Final Office Action from U.S. Appl. No. 15/992,342, dated Feb. 25, 2020, 19 pages. |
| Final Office Action from U.S. Appl. No. 16/397,945, dated Sep. 29, 2020, 20 pages. |
| Jmans25, “Map/Mount Dropbox as a Network Drive,” Oct. 14, 2011, Youtube, 1 page. |
| Non-Final Office Action from U.S. Appl. No. 14/873,187, dated Jan. 10, 2020, 17 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/964,267, dated Aug. 6, 2021, 26 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/964,267, dated Jul. 27, 2020, 21 pages. |
| Non-Final Office Action from U.S. Appl. No. 16/397,945, dated Jul. 23, 2020, 18 pages. |
| Non-Final Office Action from U.S. Appl. No. 16/508,059, dated Apr. 2, 2021, 14 pages. |
| Non-Final Office Action from U.S. Appl. No. 16/991,446, dated Jul. 8, 2021, 18 pages. |
| Notice of Allowance for U.S. Appl. No. 14/873,186 dated May 15, 2019, 32 pages. |
| Notice of Allowance from U.S. Appl. No. 14/872,004, dated Nov. 10, 2021, 11 pages. |
| Notice of Allowance from U.S. Appl. No. 14/872,004, dated Apr. 19, 2022, 4 pages. |
| Notice of Allowance from U.S. Appl. No. 14/872,004, dated Feb. 22, 2022, 9 pages. |
| Notice of Allowance from U.S. Appl. No. 14/872,019, dated Feb. 15, 2022, 9 pages. |
| Notice of Allowance from U.S. Appl. No. 14/872,019, dated Jan. 21, 2022, 15 pages. |
| Notice of Allowance from U.S. Appl. No. 14/873,004, dated Aug. 12, 2020, 6 pages. |
| Notice of Allowance from U.S. Appl. No. 14/873,004, dated Jun. 12, 2020, 11 pages. |
| Notice of Allowance from U.S. Appl. No. 14/873,187, dated Jul. 30, 2020, 8 pages. |
| Notice of Allowance from U.S. Appl. No. 14/873,187, dated Jun. 24, 2020, 13 pages. |
| Notice of Allowance from U.S. Appl. No. 15/964,267, dated Feb. 14, 2022, 7 pages. |
| Notice of Allowance from U.S. Appl. No. 15/992,342, dated Aug. 27, 2020, 5 pages. |
| Notice of Allowance from U.S. Appl. No. 15/992,342, dated Jun. 15, 2020, 10 pages. |
| Notice of Allowance from U.S. Appl. No. 16/397,945, dated Feb. 25, 2021, 2 pages. |
| Notice of Allowance from U.S. Appl. No. 16/397,945, dated Jan. 6, 2021, 11 pages. |
| Notice of Allowance from U.S. Appl. No. 16/508,059, dated Nov. 5, 2021, 17 pages. |
| Notice of Allowance from U.S. Appl. No. 16/991,446, dated Oct. 4, 2021, 10 pages. |
| Notice of Allowance for U.S. Appl. No. 12/157,772 dated Oct. 6, 2010, 15 pages. |
| Notice of Allowance for U.S. Appl. No. 12/928,998 dated Oct. 9, 2012, 13 pages. |
| Notice of Allowance for U.S. Appl. No. 13/571,512 dated Apr. 6, 2018, 17 pages. |
| Notice of Allowance for U.S. Appl. No. 13/757,024 dated Jul. 25, 2013, 11 pages. |
| Notice of Allowance for U.S. Appl. No. 13/757,024 dated Oct. 30, 2013, 7 pages. |
| Notice of Allowance for U.S. Appl. No. 14/075,598 dated Jan. 14, 2015, 10 pages. |
| Notice of Allowance for U.S. Appl. No. 14/683,341 dated Jun. 25, 2018, 10 pages. |
| Notice of Allowance for U.S. Appl. No. 14/873,195 dated Apr. 2, 2019, 15 pages. |
| Notice of Allowance for U.S. Appl. No. 14/873,199 dated Jan. 25, 2019, 16 pages. |
| Notice of Allowance for U.S. Appl. No. 14/873,197 dated Aug. 29, 2019, 14 pages. |
| Office Action for U.S. Appl. No. 14/873,187 dated Apr. 24, 2019, 21 pages. |
| Office Action for U.S. Appl. No. 11/269,498 dated Aug. 22, 2007, 18 pages. |
| Office Action for U.S. Appl. No. 11/269,498 dated Mar. 25, 2008, 17 pages. |
| Office Action for U.S. Appl. No. 11/269,498 dated Mar. 7, 2007, 14 pages. |
| Office Action for U.S. Appl. No. 12/928,998 dated Apr. 22, 2011, 26 pages. |
| Office Action for U.S. Appl. No. 12/928,998 dated Nov. 23, 2011, 24 pages. |
| Office Action for U.S. Appl. No. 13/571,512 dated Apr. 23, 2015, 23 pages. |
| Office Action for U.S. Appl. No. 13/571,512 dated Feb. 24, 2014, 17 pages. |
| Office Action for U.S. Appl. No. 13/571,512 dated Jun. 13, 2014, 22 pages. |
| Office Action for U.S. Appl. No. 13/571,512 dated May 19, 2016, 21 pages. |
| Office Action for U.S. Appl. No. 13/571,512 dated Oct. 20, 2016, 27 pages. |
| Office Action for U.S. Appl. No. 13/571,512 dated Oct. 26, 2017, 28 pages. |
| Office Action for U.S. Appl. No. 13/571,512 dated Sep. 23, 2014, 25 pages. |
| Office Action for U.S. Appl. No. 14/683,341 dated Nov. 16, 2017, 14 pages. |
| Office Action for U.S. Appl. No. 14/872,004 dated Jan. 18, 2018, 8 pages. |
| Office Action for U.S. Appl. No. 14/872,004 dated Mar. 28, 2019, 19 pages. |
| Office Action for U.S. Appl. No. 14/872,004 dated Sep. 6, 2018, 11 pages. |
| Office Action for U.S. Appl. No. 14/872,019 dated Aug. 14, 2019, 14 pages. |
| Office Action for U.S. Appl. No. 14/872,019 dated Aug. 29, 2018, 13 pages. |
| Office Action for U.S. Appl. No. 14/872,019 dated Feb. 26, 2019, 15 pages. |
| Office Action for U.S. Appl. No. 14/872,019 dated Nov. 16, 2017, 14 pages. |
| Office Action for U.S. Appl. No. 14/872,943 dated Jul. 11, 2018, 12 pages. |
| Office Action for U.S. Appl. No. 14/872,943 dated Oct. 4, 2017, 13 pages. |
| Office Action for U.S. Appl. No. 14/872,943 dated Dec. 19, 2018, 19 pages. |
| Office Action for U.S. Appl. No. 14/873,004 dated Aug. 10, 2018, 19 pages. |
| Office Action for U.S. Appl. No. 14/873,004 dated Feb. 9, 2018, 28 pages. |
| Office Action for U.S. Appl. No. 14/873,004 dated Jul. 17, 2019, 17 pages. |
| Office Action for U.S. Appl. No. 14/873,004 dated Nov. 23, 2018, 34 pages. |
| Office Action for U.S. Appl. No. 14/873,004 dated Oct. 26, 2017, 26 pages. |
| Office Action for U.S. Appl. No. 14/873,186 dated Mar. 22, 2018, 24 pages. |
| Office Action for U.S. Appl. No. 14/873,186 dated Dec. 13, 2018, 33 pages. |
| Office Action for U.S. Appl. No. 14/873,187 dated Apr. 17, 2018, 15 pages. |
| Office Action for U.S. Appl. No. 14/873,187 dated Dec. 10, 2018, 18 pages. |
| Office Action for U.S. Appl. No. 14/873,195 dated Apr. 19, 2018, 14 pages. |
| Office Action for U.S. Appl. No. 14/873,195 dated Oct. 26, 2018, 14 pages. |
| Office Action for U.S. Appl. No. 14/873,197 dated Jul. 11, 2018, 13 pages. |
| Office Action for U.S. Appl. No. 14/873,197 dated Jun. 3, 2019, 20 pages. |
| Office Action for U.S. Appl. No. 14/873,197 dated Oct. 5, 2017, 13 pages. |
| Office Action for U.S. Appl. No. 14/873,197 dated Dec. 14, 2018, 16 pages. |
| Office Action for U.S. Appl. No. 14/873,199 dated Jun. 1, 2018, 16 pages. |
| Office Action for U.S. Appl. No. 15/992,342 dated Jul. 31, 2019, 29 pages. |
| Office Action for U.S. Appl. No. 14/872,943 dated Jun. 17, 2019, 19 pages. |
| Rhee E., “How to Map a Drive Letter to Google Drive in Windows,” May 3, 2012, Retrieved from https://www.cnet.com/how-to/how-to-Map-a-Drive-Letter-to-Google-Drive-in-Windows/ on Oct. 7, 2016, pp. 1-2. |
| Srinet K., et al., “10-605—HW 5—Distributed SGD for Matrix Factorization on Spark,” Carnegie Mellon University, Pittsburgh, PA, Nov. 12, 2015, pp. 1-11. |
| Non-Final Office Action from U.S. Appl. No. 17/652,259, dated Dec. 1, 2022, 18 pages. |
| Notice of Allowance from U.S. Appl. No. 17/652,259, dated Jun. 28, 2023, 4 pages. |
| Non-Final Office Action from U.S. Appl. No. 17/580,519 , dated May 16, 2023, 17 pages. |
| Notice of Allowance from U.S. Appl. No. 17/652,259, dated Jun. 13, 2023, 10 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20220277020 A1 | Sep 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15964267 | Apr 2018 | US |
| Child | 17663628 | US |
