Functionalities, features, and user interface of a synchronization client to a cloud-based environment

Information

  • Patent Grant
  • 9507795
  • Patent Number
    9,507,795
  • Date Filed
    Monday, January 13, 2014
    10 years ago
  • Date Issued
    Tuesday, November 29, 2016
    8 years ago
Abstract
Embodiments in the present disclosure include systems and methods related to a synchronization client of a cloud-based collaboration platform that runs on a user device for synchronizing folders and files between a location on the cloud-based collaboration platform and a location on the user device. The synchronization client informs a user of the status of synchronization processes and allows a user to choose various options depending on the informed status.
Description
COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the United States Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever. The following notice applies to the software and data as described below and in the drawings that form a part of this document: Copyright 2013, Box, Inc., All Rights Reserved.


BACKGROUND

Today, in addition to working with documents on a local device, such as a desktop computer or a tablet, people keep copies of documents in a cloud-computing environment. They may do so for backup, collaboration and other purposes. It is important to keep different versions of documents synchronized between the local device and the cloud-computing environment, and it would be useful to make the synchronization process efficient and user-friendly.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a diagram illustrating an example environment in which users communicate with a cloud-based concurrent-access collaboration platform.



FIG. 2 is a diagram illustrating the collaboration platform deployed in an enterprise or other organizational setting for organizing workspaces and work items.



FIG. 3 is a diagram illustrating example components of a synchronization client.



FIGS. 4A-C are diagrams illustrating an example user interface for performing sign-up, login-in, log-out and tutorial tasks.



FIG. 5 is a diagram illustrating an example user interface for accepting a user's selection of folders.



FIG. 6 is a diagram illustrating an example user interface for showing the progress of synchronization.



FIGS. 7A-C are diagrams illustrating an example user interface with three areas for showing summary information in terms issues, conflicts and updates.



FIGS. 8A-E are diagrams illustrating an example user interface displaying state-specific options.



FIG. 9 is a diagram illustrating an example user interface displaying a user's account information.



FIG. 10 is a diagram illustrating an example user interface for managing a user's synchronization settings.



FIG. 11 is a diagram illustrating an example user interface for displaying help and administration information.



FIG. 12 is a flowchart illustrating example transitions of a synchronization process.



FIG. 13 shows a diagrammatic representation of a machine in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.





DETAILED DESCRIPTION

The following description and drawings are illustrative and are not to be construed as limiting. Numerous specific details are described to provide a thorough understanding of the disclosure. However, in certain instances, well-known or conventional details are not described in order to avoid obscuring the description. References to one or an embodiment in the present disclosure can be, but not necessarily are, references to the same embodiment; and, such references mean at least one of the embodiments.


Reference in this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others. Similarly, various requirements are described which may be requirements for some embodiments but no other embodiments.


The terms used in this specification generally have their ordinary meanings in the art, within the context of the disclosure, and in the specific context where each term is used. Certain terms that are used to describe the disclosure are discussed below, or elsewhere in the specification, to provide additional guidance to the practitioner regarding the description of the disclosure. For convenience, certain terms may be highlighted, for example using italics and/or quotation marks. The use of highlighting has no influence on the scope and meaning of a term; the scope and meaning of a term is the same, in the same context, whether or not it is highlighted. It will be appreciated that same thing can be said in more than one way.


Consequently, alternative language and synonyms may be used for any one or more of the terms discussed herein, nor is any special significance to be placed upon whether or not a term is elaborated or discussed herein. Synonyms for certain terms are provided. A recital of one or more synonyms does not exclude the use of other synonyms. The use of examples anywhere in this specification including examples of any terms discussed herein is illustrative only, and is not intended to further limit the scope and meaning of the disclosure or of any exemplified term. Likewise, the disclosure is not limited to various embodiments given in this specification.


Without intent to limit the scope of the disclosure, examples of instruments, apparatus, methods and their related results according to the embodiments of the present disclosure are given below. Note that titles or subtitles may be used in the examples for convenience of a reader, which in no way should limit the scope of the disclosure. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. In the case of conflict, the present document, including definitions will control.


Embodiments of the present disclosure include systems and methods for a synchronization client that is connected with a collaboration environment including a cloud-based platform (e.g., cloud-based file sharing, collaboration, and/or storage platform/service) and runs on a client device to synchronize folders and files between the collaboration environment and the user device.



FIG. 1 is a diagram illustrating an example environment 100 in which users or collaborators communicate with a cloud-based concurrent-access collaboration platform (cloud-based service/platform, collaboration workspace and/or cloud storage service). A host system 110 hosts the collaboration platform which enables users to simultaneously create, view, edit, annotate, store, share and otherwise manage content in real time or near real time. The host system 110 has a high-availability architecture suited for handling the large volume of user requests.


The client devices 102 can be any system and/or device, and/or any combination of devices/systems that is able to establish a communication or a connection, including wired, wireless, cellular connections with another device, a server and/or other systems such as the host server 110. The client devices 102 typically include a display and/or other output functionalities to present information and data exchanged between among the client devices 102 and/or the host server 110.


For example, the client devices 102 can include mobile, handheld or portable devices or non-portable devices and can be any of, but not limited to, a server desktop, a desktop computer, a computer cluster, or portable devices including, a notebook, a laptop computer, a handheld computer, a palmtop computer, a mobile phone, a cell phone, a PDA, a smart phone (e.g., a BlackBerry device such as BlackBerry Z10/Q10, an iPhone, Nexus 4, etc.), a Treo, a handheld tablet (e.g. an iPad, iPad Mini, a Galaxy Note, Galaxy Note II, Xoom Tablet, Microsoft Surface, Blackberry PlayBook, Nexus 7, 10 etc.), a phablet (e.g., HTC Droid DNS, etc.), a tablet PC, a thin-client, a hand held console, a hand held gaming device or console (e.g., XBOX live, Nintendo DS, Sony PlayStation Portable, etc.), mobile-enabled powered watch (e.g., iOS, Android or other platform based), Google Glass, a Chromebook and/or any other portable, mobile, hand held devices, etc. running on any platform or any operating system (e.g., Mac-based OS (OS X, iOS, etc.), Windows-based OS (Windows Mobile, Windows 7, Windows 8, etc.), Android, Blackberry OS, Embedded Linux platforms, Palm OS, Symbian platform, Google Chrome OS, and the like. In one embodiment, the client devices 102 and host server 110 are coupled via a network 106. In some embodiments and the client devices 102 and host server 100 may be directly connected to one another.


The input mechanism on client devices 102 can include touch screen keypad (including single touch, multi-touch, gesture sensing in 2D or 3D, etc.), a physical keypad, a mouse, a pointer, a track pad, motion detector (e.g., including 1-axis, 2-axis, 3-axis accelerometer, etc.), a light sensor, capacitance sensor, resistance sensor, temperature sensor, proximity sensor, a piezoelectric device, device orientation detector (e.g., electronic compass, tilt sensor, rotation sensor, gyroscope, accelerometer), or a combination of the above.


Signals received or detected indicating user activity at client devices 102 through one or more of the above input mechanism, or others, can be used by various users or collaborators (e.g., collaborators 108) for accessing, through the network 106, a web-based collaboration environment or online collaboration platform (e.g., hosted by the host server 110). The collaboration environment or platform can have one or more collective settings 105 for an enterprise or an organization where the users belong, and can provide a user interface 104 for the users to access such platform under the settings 105.


In general, the network 106, over which the client devices 102 and the host server 110 communicate may be a cellular network, a telephonic network, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet, or any combination or variation thereof. For example, the Internet can provide file transfer, remote log in, email, news, RSS, cloud-based services, instant messaging, visual voicemail, push mail, VoIP, and other services through any known or convenient protocol, such as, but is not limited to the TCP/IP protocol, Open System Interconnections (OSI), FTP, UPnP, iSCSI, NSF, ISDN, PDH, RS-232, SDH, SONET, etc.


The network 106 can be any collection of distinct networks operating wholly or partially in conjunction to provide connectivity to the client devices 102 and the host server 110 and may appear as one or more networks to the serviced systems and devices. In one embodiment, communications to and from the client devices 102 can be achieved by, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet. In one embodiment, communications can be achieved by a secure communications protocol, such as secure sockets layer (SSL), or transport layer security (TLS).


In addition, communications can be achieved via one or more networks, such as, but are not limited to, one or more of WiMax, a Local Area Network (LAN), Wireless Local Area Network (WLAN), a Personal area network (PAN), a Campus area network (CAN), a Metropolitan area network (MAN), a Wide area network (WAN), a Wireless wide area network (WWAN), or any broadband network, and further enabled with technologies such as, by way of example, Global System for Mobile Communications (GSM), Personal Communications Service (PCS), Bluetooth, WiFi, Fixed Wireless Data, 2G, 2.5G, 3G (e.g., WCDMA/UMTS based 3G networks), 4G, IMT-Advanced, pre-4G, LTE Advanced, mobile WiMax, WiMax 2, WirelessMAN-Advanced networks, enhanced data rates for GSM evolution (EDGE), General packet radio service (GPRS), enhanced GPRS, iBurst, UMTS, HSPDA, HSUPA, HSPA, HSPA+, UMTS-TDD, 1xRTT, EV-DO, messaging protocols such as, TCP/IP, SMS, MMS, extensible messaging and presence protocol (XMPP), real time messaging protocol (RTMP), instant messaging and presence protocol (IMPP), instant messaging, USSD, IRC, or any other wireless data networks, broadband networks, or messaging protocols.



FIG. 2 is a diagram illustrating the collaboration platform deployed in an enterprise or other organizational setting 250 for organizing workspaces 205, 225 and 245 and work items 215, 235 and 255. The collaboration platform or environment hosts workspaces with work items that one or more users can access (e.g., view, edit, update, revise, comment, download, preview, tag, or otherwise manipulate, etc.). A work item can generally include any type of digital or electronic content that can be viewed or accessed via an electronic device (e.g., client devices 202). For example, the work items 215 and 235 include general digital content, such as .pdf files, .doc, slides (e.g., Powerpoint slides), images, audio files, multimedia content, web pages, blogs, etc. On the other hand, the work items 255 comprise “notes” or documents of a proprietary format, which support advanced and unique capabilities of data management and promote collaboration. A workspace can generally refer to any grouping of a set of digital content managed by the collaboration platform. For example, the workspaces A 205 and B 225 include general digital content while the workspace 245, referred to as a “notebook”, includes notes only. The grouping can be created, identified, or specified by a user or through other means. This user may be a creator user or administrative user, for example.


In general, a workspace can be associated with a set of users or collaborators (e.g., collaborators 108) who have access to the content included therein. The levels of access (e.g., based on permissions or rules) of each user or collaborator to access the content in a given workspace may be the same or may vary among the users. Each user may have their own set of access rights to every piece of content in the workspace, or each user may have different access rights to different pieces of content. Access rights may be specified by a user associated with a workspace and/or a user who created/uploaded a particular piece of content to the workspace, or any other designated user or collaborator.


In general, the collaboration platform allows multiple users or collaborators to access or collaborate on work items such that each user can remotely see edits, revisions, comments, or annotations being made to specific work items through their own user devices. For example, a user can upload a document to a workspace for other users to access (e.g., for viewing, editing, commenting, signing-off or otherwise manipulating). The user can login to the online platform and upload the document (or any other type of work item) to an existing workspace or to a new workspace. The document can be shared with existing users or collaborators in a workspace.


The web-based platform for collaborating on projects or jointly working on documents can be used by individual users and shared among collaborators. In addition, the collaboration platform can be deployed in an organized setting including but not limited to, a company (e.g., an enterprise setting), a department in a company, an academic institution, a department in an academic institution, a class or course setting, or any other types of organizations or organized setting.


When deployed in an organizational setting, multiple workspaces (e.g., workspace A, B C) can be created to support different projects or a variety of work flows. Each workspace can have its own associate work items. For example, workspace A 205 can be associated with work items 215, workspace B 225 can be associated with work items 235, and workspace 245 can be associated with work items 255. The work items 215, 235, and 255 can be unique to each workspace but need not be. For example, a particular work item or a note can be associated with only one workspace or it can be associated with multiple workspaces.


In general, each workspace has a set of users or collaborators associated with it. For example, workspace A 205 is associated with multiple users or collaborators 206. In some instances, workspaces deployed in an enterprise can be department specific. For example, workspace B can be associated with department 210 and some users shown as example user A 208, and workspace N 245 can be associated with departments 212 and 216 and users shown as example user B 214.


In the case of a notebook, collaborators of the notebook can have simultaneous read/write access to a note in the notebook. Specifically, in a concurrent fashion, each of the collaborators is able to make changes to the note or even edit the changes made by other collaborators. In addition, a separate list of collaborators can be specified at the note level to override the list of collaborators at the notebook level, so that different notes within the same notebook can be associated with different sets of collaborators.


In each workspace A, B . . . N, when an action is performed on a work item by a given user or any other activity is detected in the workspace, other users in the same workspace can be notified (e.g., in real time or in near real time, or not in real time). Activities which trigger real time notifications can include, by way of example but not limitation, adding, deleting, or modifying collaborators in the workspace, uploading, downloading, adding, deleting a work item in the workspace, creating a discussion topic in the workspace.


In some embodiments, items or content downloaded or edited can cause notifications to be generated. Such notifications can be sent to relevant users to notify them of actions surrounding a download, an edit, a change, a modification, a new file, a conflicting version, an upload of an edited or modified file.


In one embodiment, in a user interface to the web-based collaboration platform where notifications are presented, users can, via the same interface, create action items (e.g., tasks) and delegate the action items to other users including collaborators pertaining to a work item 215, for example. The collaborators 206 can be in the same workspace A 205 and can invite a new collaborator to join the workspace, for example. Similarly, in the same user interface where discussion topics can be created in a workspace (e.g., workspace A, B or N, etc.), actionable events on work items can be created and/or delegated/assigned to other users such as collaborators of a given workspace 206 or other users. Through the same user interface, task status and updates from multiple users or collaborators can be indicated and reflected. In some instances, the users can perform the tasks (e.g., review or approve or reject, etc.) via the same user interface.


Synchronization Client


The collaboration platform offers a synchronization client that runs on a client device to perform synchronization of folders and files between a location on the collaboration platform and a location on the client device. The synchronization client offers user interfaces that may be accessed directly from the client device or through the web. It informs a user of the status of synchronization processes and allows a user to choose various options depending on the informed status, thus making the synchronization process efficient and user-friendly.



FIG. 3 is a diagram illustrating example components of the synchronization client. In some embodiments, the synchronization client comprises an entry module 302, a synchronization module 304, a configuration module 306, and a network module 308.


As used herein, a “module” or the like includes a general purpose, dedicated or shared processor and, typically, firmware or software modules that are executed by the processor. Depending upon implementation-specific or other considerations, the module can be centralized or its functionality distributed. The module or the like can include general or special purpose hardware, firmware, or software embodied in a computer-readable (storage) medium for execution by the processor.


As used herein, a computer-readable medium or computer-readable storage medium is intended to include all mediums that are statutory (e.g., in the United States, under 35 U.S.C. 101), and to specifically exclude all mediums that are non-statutory in nature to the extent that the exclusion is necessary for a claim that includes the computer-readable (storage) medium to be valid. Known statutory computer-readable mediums include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware.


The network interface 308 can be a networking module that enables the host server to mediate data in a network with an entity that is external to the host server, through any known and/or convenient communications protocol supported by the host server and the external entity. The network interface 308 can communicate with one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, Wi-Fi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G, LTE, etc.), Bluetooth, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, a bridge router, a hub, a digital media receiver, and/or a repeater.


The entry module 302 manages sign-up, login-in, log-out and tutorial tasks. FIGS. 4A-C are diagrams illustrating an example user interface for performing sign-up, login-in, log-out and tutorial tasks. The user interface allows a user to sign up for the synchronization client, log in to the synchronization client, and take a tour of the synchronization client by choosing the options 402, 404 and 406 and interacting with the screens 408, 410 and 412, respectively. The three options may continue to be displayed as the synchronization client is running.


For the sign-up and login-in tasks, the entry module 302 may accept a username and a password from a user. It may respond to unacceptable or incorrect user names or passwords and optionally apply the CAPTCHA technique. For the login-in task, the entry module 302 may also apply the OAuth technique or the Single Sign On (SSO) technique in addition to accepting the username and password for two-factor authentication. In applying these techniques, the entry module 302 may display a dialog requesting a user to grant permission to the synchronization client for accessing resources on a user's local computer, or send email requesting a user to confirm the log-in by following a URL.


Upon a successful login, the entry module 302 may store a token to indicate the success of the OAuth or SSO technique and keep the token alive for all future login-ins within a predetermined period of time, such as two weeks or a month. The entry module 302 may also perform different actions depending on whether the current user is the same as the last user. Specifically, it may work with a folder of a fixed name, such as “Box Sync”, in a fixed location on the collaboration platform. It may then reuse the folder if the current user is the same as the last user. It may also create the folder if that folder does not already exist or if the current user is different from the last user. In the latter case, if the folder already exists, it may rename that existing folder before creating a new one and show a warning message to that effect.


For the log-out task initiated by a user or caused by the expiration of a token, the entry module 302 may preserve all the data created since the log-in. It may also display a message indicating that a user is no longer connected to the synchronization client.


The synchronization module 304 manages file synchronization between the collaboration platform and other devices. Specifically, it enables the replication of folders and files in a location on the collaboration platform (“collaboration location” hereinafter) to a location on a device designated by a user (“local location” hereinafter), and synchronization of those folders and files between the two locations in real time. The synchronization module 304 may allow a user to select the collaboration location and the local location. FIG. 5 is a diagram illustrating an example user interface for accepting a user's selection of folders. The user interface displays the list of folders available in a predetermined collaboration location in 502 and allows a user to check off those folders to be replicated to a predetermined local location. It also allows a user to choose a different local location via 504.


During synchronization, the synchronization module 304 may keep a user informed through various status report mechanisms. In some embodiments, the synchronization module 304 may automatically present a user interface for real-time synchronization status update. FIG. 6 is a diagram illustrating an example user interface for showing the progress of synchronization. The user interface displays the time remaining until the end of synchronization in 602, the number of files left to synchronize in 604, and the number of files already synchronized in this synchronization process in 606.


In some embodiments, the synchronization module 304 may allow a user to invoke a user interface to view summary information regarding ongoing or recent synchronization and take further actions. FIGS. 7A-C are diagrams illustrating an example user interface with three areas for showing summary information in terms issues, conflicts and updates. In FIG. 7A, the user interface shows an “issues” tab listing the issues which have halted a synchronization process, such as an unsupported file format or filename. With respect to some of the issues, the user interface may allow a user to resume or restart the process after the issue is resolved, as in 702. In FIG. 7B, the user interface shows a “conflicts” tab listing the conflicts that were present between the folders and files in the collaboration location and those in the local location. As one example, the user interface may display a message stating that a conflict was resolved by renaming one of the conflicting files. As another example, it may separately show a list of conflicting files with details such as the file name, creation date, modification date, size, etc. The user interface may allow a user to review a conflicting file, as in 704. In FIG. 7C, the user interface shows a “recent updates” tab listing recent file updates requiring synchronization, such edits or creations. The user interface may allow a user to review an updated file, as in 706.


In some embodiments, the synchronization module 304 may automatically present a user interface for system-wide status update. As an example, the synchronization module 304 may display icons in an administrative area on a screen of a user's device, such as in the system tray for Windows and in the menu/status bar for Mac. Specifically, it may map the icons to predefined states, including “complete”, “in progress”, “paused”, “insecure”, and “offline”. The “complete” state indicates that that the synchronization client is running yet with no synchronization in progress for a user, the “in progress” state indicates that synchronization is in progress for a user, the “paused” state indicates that synchronization is on hold for a user, the “insecure” state indicates that synchronization is stopped for a user, at the user's instruction or due to an unforeseen security breach on the collaboration platform, for example, and the “offline” state indicates that that the synchronization is no longer running (although the user is still connected to the collaboration platform).


Further according to the example, the synchronization module 304 may allow a user to click on each of the icons to take further actions and present the list of further actions via a drop-down menu. FIGS. 8A-E are diagrams illustrating an example user interface displaying state-specific options. The user interface presents a drop-down menu offering common options across the states, such as exploring the collaboration location in 802, reviewing user preferences in 804 and quitting the synchronization client in 806. The drop-down menu also shows state-specific messages when available, such as a summary of an ongoing synchronization process including information on errors occurred so far for the “in progress” state in 808, and offers state-specific options. In FIG. 8A, the user interface shows the drop-down menu for the “complete” state. In FIG. 8B, the user interface shows the drop-down menu for the “in progress” state, which includes an option to pause an ongoing synchronization process in 810. In FIG. 8C, the user interface shows the drop-down menu for the “paused” state, which includes an option to resume a paused synchronization process in 812. In FIG. 8D, the user interface shows the drop-down menu for the “insecure” state, which includes an option to restart a stopped synchronization process. In FIG. 8E, the user interface shows the drop-down menu for the “offline” state, which includes an option to log in to the synchronization client.


In some embodiments, the synchronization module 304 may automatically display a status indicator together with a representation of a folder or a file, within a file explorer running on the collaboration platform or on the user's local device, to indicate a status of the folder or the file. For example, the synchronization module 304 may display an icon to indicate whether a folder or a file is shared (collaborative) or private, whether it is locked (checked out) or unlocked, and whether it is already synchronized, being synchronized, not synchronizable, or to be ignored. The icon could show one of these statuses at a time or more than one of them at the same time. Furthermore, the synchronization module 304 may follow a cascading rule in displaying the icons in that the icon for a folder should reflect an aggregate status over all the files in the folder. For example, it may display an “already synchronized” icon for a folder only when it is not displaying a “being synchronized” icon for any of the files in the folder.


The configuration module 306 manages the configuration of the synchronization client according to a user's preferences. In some embodiments, the configuration module 306 may display a user's account information. FIG. 9 is a diagram illustrating an example user interface displaying a user's account information. The user interface shows the account identification and type in 902, the amount of storage available and used on the collaboration platform in 904, and the amount of storage available and used on the user's local device in 906.


In some embodiments, the configuration module 306 may allow a user to customize synchronization settings. FIG. 10 is a diagram illustrating an example user interface for managing a user's synchronization settings. The user interface displays the current local location, and it allows a user to switch to a new local location from scratch via 1002 or move to a new local location with all the folders and files transferred via 1004. The user interface allows a user to specify the required download rate which applies to synchronization from the collaboration location to the local location and the required upload rate which applies to synchronization in the other direction in 1006. In addition, the user interface allows a user to indicate whether to receive real-time notifications that pop up on the user's desktop in 1008 and the default language to use in 1010.


In some embodiments, the configuration module 306 may display help and administration information to a user. FIG. 11 is a diagram illustrating an example user interface for displaying help and administration information. The user interface directs a user to help articles and allows a user to report problems in 1102. It allows a user to indicate whether to send diagnostics information to the collaboration platform in 1104. It also displays version and copyright information in 1106.



FIG. 12 is a flowchart illustrating example transitions of a synchronization process. The synchronization client is in the “complete” state at block 1202, with no synchronization in progress. Once a synchronization process is started, the synchronization client goes into the “in progress” state at block 1204. The process may then be paused, and the synchronization client goes into the “paused” state at block 1206. Subsequently, the process may be resumed, which then takes the synchronization client back to the “in progress” state at block 1204. When the process is in progress or paused, it may then be stopped, and the synchronization client goes into the “insecure” state at lock 1210, which would then require a user's attention to clear the error and possibly restart the process. When the process is completed without errors or other interruptions, the synchronization client goes back to the “complete” state.



FIG. 13 shows a diagrammatic representation of a machine in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.


In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.


The machine may be a server computer, a client computer, a personal computer (PC), a user device, a tablet PC, a laptop computer, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, an iPhone, an iPad, a Blackberry, a processor, a telephone, a web appliance, a network router, switch or bridge, a console, a hand-held console, a (hand-held) gaming device, a music player, any portable, mobile, hand-held device, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.


While the machine-readable medium or machine-readable storage medium is shown in an exemplary embodiment to be a single medium, the term “machine-readable medium” and “machine-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” and “machine-readable storage medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the presently disclosed technique and innovation.


In general, the routines executed to implement the embodiments of the disclosure, may be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as “computer programs”. The computer programs typically comprise one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processing units or processors in a computer, cause the computer to perform operations to execute elements involving the various aspects of the disclosure.


Moreover, while embodiments have been described in the context of fully functioning computers and computer systems, those skilled in the art will appreciate that the various embodiments are capable of being distributed as a program product in a variety of forms, and that the disclosure applies equally regardless of the particular type of machine or computer-readable media used to actually effect the distribution.


Further examples of machine-readable storage media, machine-readable media, or computer-readable (storage) media include, but are not limited to, recordable type media such as volatile and non-volatile memory devices, floppy and other removable disks, hard disk drives, optical disks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks, (DVDs), etc.), among others, and transmission type media such as digital and analog communication links.


The network interface device enables the machine to mediate data in a network with an entity that is external to the host server, through any known and/or convenient communications protocol supported by the host and the external entity. The network interface device can include one or more of a network adaptor card, a wireless network interface card, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater.


The network interface device can include a firewall which can, in some embodiments, govern and/or manage permission to access/proxy data in a computer network, and track varying levels of trust between different machines and/or applications. The firewall can be any number of modules having any combination of hardware and/or software components able to enforce a predetermined set of access rights between a particular set of machines and applications, machines and machines, and/or applications and applications, for example, to regulate the flow of traffic and resource sharing between these varying entities. The firewall may additionally manage and/or have access to an access control list which details permissions including for example, the access and operation rights of an object by an individual, a machine, and/or an application, and the circumstances under which the permission rights stand.


Other network security functions can be performed or included in the functions of the firewall, can be, for example, but are not limited to, intrusion-prevention, intrusion detection, next-generation firewall, personal firewall, etc. without deviating from the novel art of this disclosure.


Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to.” As used herein, the terms “connected,” “coupled,” or any variant thereof, means any connection or coupling, either direct or indirect, between two or more elements; the coupling of connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein”, “above”, “below”, and words of similar import, when used in this application, shall refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word “or”, in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.


The above detailed description of embodiments of the disclosure is not intended to be exhaustive or to limit the teachings to the precise form disclosed above. While specific embodiments of, and examples for, the disclosure are described above for illustrative purposes, various equivalent modifications are possible within the scope of the disclosure, as those skilled in the relevant art will recognize. For example, while processes or blocks are presented in a given order, alternative embodiments may perform routines having steps, or employ systems having blocks, in a different order, and some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or subcombinations. Each of these processes or blocks may be implemented in a variety of different ways. Also, while processes or blocks are at times shown as being performed in series, these processes or blocks may instead be performed in parallel, or may be performed at different times. Further, any specific numbers noted herein are only examples: alternative implementations may employ differing values or ranges.


The teachings of the disclosure provided herein can be applied to other systems, not necessarily the system described above. The elements and acts of the various embodiments described above can be combined to provide further embodiments.


Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the disclosure can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further embodiments of the disclosure.


These and other changes can be made to the disclosure in light of the above Detailed Description. While the above description describes certain embodiments of the disclosure, and describes the best mode contemplated, no matter how detailed the above appears in text, the teachings can be practiced in many ways. Details of the system may vary considerably in its implementation details, while still being encompassed by the subject matter disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the disclosure should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the disclosure with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the disclosure to the specific embodiments disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the disclosure encompasses not only the disclosed embodiments, but also all equivalent ways of practicing or implementing the disclosure under the claims.


While certain aspects of the disclosure are presented below in certain claim forms, the inventors contemplate the various aspects of the disclosure in any number of claim forms. For example, while only one aspect of the disclosure is recited as a means-plus-function claim under 35 U.S.C. §112, ¶6, other aspects may likewise be embodied as a means-plus-function claim, or in other forms, such as being embodied in a computer-readable medium. (Any claims intended to be treated under 35 U.S.C. §112, ¶6 will begin with the words “means for”.) Accordingly, the applicant reserves the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the disclosure.

Claims
  • 1. A client device comprising: a processor; anda memory storing instructions of a synchronization client that when executed by the processor causes the processor to communicate with a cloud-based computing platform for synchronizing folders and files between a collaboration location on the cloud-based computing platform and a local location on the synchronization client, wherein the cloud-based computing platform facilitates collaboration among multiple users via the cloud-based platform, the synchronization client including: an issue handling unit which aggregates for display on a user interface of the synchronization client one or more issues halting a synchronization process, wherein the one or more issues are selectable by a user to resume or restart the halted synchronization process,wherein the synchronization process comprises an in-progress state, a paused state, and an insecure state, and wherein the paused state and the in-progress state are configured to transition to the insecure state upon detection of a security breach,wherein the synchronization client is configured to: in response to determining that a folder in the folders involved in the synchronization process is identifiable by multiple synchronization states, assign an aggregate synchronization state to the folder in the folders involved in the synchronization process, the aggregate state representing a combined aggregation of one or more respective synchronization states of each file included in the folder;a conflict handling unit which aggregates for display on the user interface of the synchronization client at least one conflict of folders and files between the collaboration location and the local location for resolution during the synchronization process; andan update handling unit which aggregates for display on the user interface of the synchronization client summary information relating to one or more updates of folders and files triggering the synchronization process, wherein display of the summary information relating to each update is selectably expandable revealing additional options to the user to view an updated file or folder.
  • 2. The client device of claim 1, wherein an issue is exceeding a storage limit, an unsupported file type, or an unsupported filename.
  • 3. The client device of claim 1, wherein a description of a conflict for resolution includes information on renaming a conflicting folder or file.
  • 4. The client device of claim 1, wherein a description of a conflict for resolution includes information regarding each of conflicting files.
  • 5. The client device of claim 1, wherein each conflict is selectable by the user to view a conflicting folder or file.
  • 6. A method comprising: identifying by a synchronization client on a client device one or more issues halting a synchronization event, the synchronization client being configured to communicate with a cloud-based computing platform for synchronizing folders and files between a collaboration location on the cloud-based computing platform and a local location on the client device, wherein the cloud-based computing platform facilitates collaboration among multiple users via the cloud-based platform, wherein the synchronization event comprises an in-progress state, a paused state, and an insecure state, and wherein the paused state and the in-progress state are configured to transition into the insecure state upon detection of a security breach;identifying by the synchronization client at least one conflicts associated with folders and files between the collaboration location and the local location for resolution during the synchronization event, wherein the synchronization client is configured to:in response to determining that a folder in the folders involved in the synchronization process is identifiable by multiple synchronization states, assign an aggregate synchronization state to the folder in the folders involved in the synchronization process, the aggregate state representing a combined aggregation of one or more respective synchronization states of each file included in the folder;identifying by the synchronization client one or more updates of folders and files triggering the synchronization event; anddisplaying on one or more user interfaces provided by the synchronization client one or more messages corresponding to each of the one or more issues, the one or more conflicts, and the one or more updates of folders and files identified by the synchronization client, the one or more messages corresponding to the one or more updates of folders and files including summary information that is selectably expandable revealing additional options to facilitate sharing an updated folder or file.
  • 7. The method of claim 6, wherein the one or more issues includes exceeding a storage limit, an unsupported file type, or an unsupported filename.
  • 8. The method of claim 6, wherein a message from the one or more messages corresponding to the one or more issues is selectable by a user to resume or restart the halted synchronization event.
  • 9. The method of claim 6, wherein the one or more messages corresponding to the one or more conflicts include information about an action taken to resolve conflicting folders or files.
  • 10. The method of claim 6, wherein a message from the one or more messages corresponding to the one or more conflicts is selectable by a user to view or share a conflicting file or folder.
  • 11. A non-transitory computer-readable storage medium storing a set of instructions which when executed by a cloud-based computing system causes the cloud-based computing system to perform a method comprising: in response to a selection of a first tab of a user interface of a synchronization client, displaying in an issue handling area of the user interface, one or more issues halting a synchronization event, wherein an issue from the one or more issues is selectable by a user to resume or restart the halted synchronization event, wherein the synchronization event comprises an in-progress state, a paused state, and an insecure state, and wherein the paused state or the in-progress state are configured to transition into the insecure state upon detection of a security breach;in response to a selection of a second tab of the user interface, displaying in a conflict handling area of the user interface, one or more resolved conflicts that were present between folders or files between a collaboration location on the cloud-based platform and a local location on the synchronization client during the synchronization event, wherein a resolved conflict from the one or more resolved conflicts is selectable by the user to view a conflicting folder or a file, wherein the synchronization client is configured to: in response to determining that a folder in the folders involved in the synchronization event is identifiable by multiple synchronization states, assign an aggregate synchronization state to the folder in the folders involved in the synchronization event, the aggregate state representing a combined aggregation of one or more respective synchronization states of each file included in the folder; andin response to a selection of a third tab of the user interface, displaying in an update handling area summary information relating to one or more updates of folders or files that triggered the synchronization event, wherein display of the summary information relating to the one or more updates is selectably expandable revealing additional options to the user to view an updated folder or file.
  • 12. The computer-readable storage medium of claim 11, wherein the one or more issues that halted the synchronization event include exceeding a storage limit.
  • 13. The computer-readable storage medium of claim 11, wherein the one or more issues that halted the synchronization event include an unsupported file type.
  • 14. The computer-readable storage medium of claim 11, wherein the one or more issues that halted the synchronization event include an unsupported filename.
  • 15. The computer-readable storage medium of claim 11, wherein the one or more resolved conflicts include information about an action taken to resolve conflicting folders or files.
  • 16. The computer-readable storage medium of claim 11, wherein the resolved conflict from the one or more resolved conflicts is selectable by the user to share the conflicting folder or file.
  • 17. The client device of claim 1, wherein the security breach is unforeseen.
  • 18. The client device of claim 1, wherein the paused state is configured to transition into the insecure state in response to instructions from the user.
  • 19. The method of claim 6, wherein the security breach is unforeseen.
  • 20. The method of claim 6, wherein the paused state is configured to transition into the insecure state in response to instructions from the user.
  • 21. The computer-readable storage medium of claim 11, wherein the security breach is unforeseen.
  • 22. The computer-readable storage medium of claim 11, wherein the paused state is configured to transition into the insecure state in response to instructions from the user.
CROSS-REFERENCE TO RELATED APPLICATION AND EFFECTIVE FILING DATE ENTITLEMENT

The present application claims priority to and benefit from U.S. Provisional Patent Application Ser. No. 61/751,578, titled “Functionalities, Features, and User Interface of A Synchronization Client to A Cloud-Based Environment”, filed on Jan. 11, 2013, the content of which is incorporated by reference herein. This application is therefore entitled to an effective filing date of Jan. 11, 2013.

US Referenced Citations (636)
Number Name Date Kind
858619 O'Farrell Jul 1907 A
5043876 Terry Aug 1991 A
5748735 Ganesan May 1998 A
5774717 Porcaro Jun 1998 A
5787175 Carter Jul 1998 A
5799320 Klug Aug 1998 A
5848415 Guck Dec 1998 A
5864870 Guck Jan 1999 A
5926816 Bauer et al. Jul 1999 A
5999908 Abelow Dec 1999 A
6016467 Newsted et al. Jan 2000 A
6034621 Kaufman Mar 2000 A
6055543 Christensen et al. Apr 2000 A
6073161 DeBoskey et al. Jun 2000 A
6098078 Gehani et al. Aug 2000 A
6226618 Downs et al. May 2001 B1
6233600 Salas et al. May 2001 B1
6260040 Kauffman et al. Jul 2001 B1
6279109 Brundridge Aug 2001 B1
6289345 Yasue Sep 2001 B1
6292803 Richardson et al. Sep 2001 B1
6336124 Alam et al. Jan 2002 B1
6342906 Kumar et al. Jan 2002 B1
6345386 Delo et al. Feb 2002 B1
6370543 Hoffert et al. Apr 2002 B2
6374260 Hoffert et al. Apr 2002 B1
6385606 Inohara et al. May 2002 B2
6396593 Laverty et al. May 2002 B1
6441641 Pang et al. Aug 2002 B1
6446091 Noren et al. Sep 2002 B1
6449622 LaRue et al. Sep 2002 B1
6515681 Knight Feb 2003 B1
6539381 Prasad et al. Mar 2003 B1
6584466 Serbinis et al. Jun 2003 B1
6636872 Heath et al. Oct 2003 B1
6636897 Sherman et al. Oct 2003 B1
6654737 Nunez Nov 2003 B1
6662186 Esquibel et al. Dec 2003 B1
6687878 Eintracht et al. Feb 2004 B1
6714968 Prust Mar 2004 B1
6735623 Prust May 2004 B1
6742181 Koike et al. May 2004 B1
6760721 Chasen et al. Jul 2004 B1
6947162 Rosenberg et al. Sep 2005 B2
6952724 Prust Oct 2005 B2
6996768 Elo et al. Feb 2006 B1
7003667 Slick et al. Feb 2006 B1
7010752 Ly Mar 2006 B2
7020697 Goodman et al. Mar 2006 B1
7039806 Friedman et al. May 2006 B1
7069393 Miyata et al. Jun 2006 B2
7080104 Ring et al. Jul 2006 B2
7130831 Howard et al. Oct 2006 B2
7133834 Abelow Nov 2006 B1
7143136 Drenan et al. Nov 2006 B1
7149787 Mutalik et al. Dec 2006 B1
7152182 Ji et al. Dec 2006 B2
7155483 Friend et al. Dec 2006 B1
7165107 Pouyoul et al. Jan 2007 B2
7171468 Yeung et al. Jan 2007 B2
7178021 Hanna et al. Feb 2007 B1
7222078 Abelow May 2007 B2
7275244 Bell et al. Sep 2007 B1
7296025 Kung et al. Nov 2007 B2
7346778 Guiter et al. Mar 2008 B1
7353252 Yang et al. Apr 2008 B1
7362868 Madoukh et al. Apr 2008 B2
7363330 Ellman et al. Apr 2008 B1
7370269 Prabhu et al. May 2008 B1
7380120 Garcia May 2008 B1
7386535 Kalucha et al. Jun 2008 B1
7401117 Dan et al. Jul 2008 B2
7543000 Castro et al. Jun 2009 B2
7581221 Lai et al. Aug 2009 B2
7620565 Abelow Nov 2009 B2
7647559 Yozell-Epstein et al. Jan 2010 B2
7650367 Arruza Jan 2010 B2
7653668 Shelat et al. Jan 2010 B1
7661088 Burke Feb 2010 B2
7665093 Maybee et al. Feb 2010 B2
7676542 Moser et al. Mar 2010 B2
7698363 Dan et al. Apr 2010 B2
7734600 Wise et al. Jun 2010 B1
7739411 Messer et al. Jun 2010 B2
7756843 Palmer Jul 2010 B1
7774412 Schnepel Aug 2010 B1
7814426 Huesken et al. Oct 2010 B2
7886287 Davda Feb 2011 B1
7886295 Burger et al. Feb 2011 B2
7890964 Vogler-Ivashchanka et al. Feb 2011 B2
7937663 Parker et al. May 2011 B2
7958353 Matsuzaki et al. Jun 2011 B2
7958453 Taing Jun 2011 B1
7979296 Kruse et al. Jul 2011 B2
7996374 Jones et al. Aug 2011 B1
8027976 Ding et al. Sep 2011 B1
RE42904 Stephens, Jr. Nov 2011 E
8065739 Bruening et al. Nov 2011 B1
8090361 Hagan Jan 2012 B2
8103662 Eagan et al. Jan 2012 B2
8117261 Briere et al. Feb 2012 B2
8140513 Ghods et al. Mar 2012 B2
8151183 Chen et al. Apr 2012 B2
8185830 Saha et al. May 2012 B2
8200582 Zhu Jun 2012 B1
8201230 Day et al. Jun 2012 B2
8214747 Yankovich et al. Jul 2012 B1
8230348 Peters et al. Jul 2012 B2
8239918 Cohen Aug 2012 B1
8326814 Ghods et al. Dec 2012 B2
8347276 Schadow Jan 2013 B2
8358701 Chou et al. Jan 2013 B2
8370803 Holler et al. Feb 2013 B1
8429540 Yankovich et al. Apr 2013 B1
8447820 Gay May 2013 B1
8464161 Giles et al. Jun 2013 B2
8473775 Helmick et al. Jun 2013 B1
8515902 Savage Aug 2013 B2
8527549 Cidon Sep 2013 B2
8549066 Donahue et al. Oct 2013 B1
8549511 Seki et al. Oct 2013 B2
8582777 Urivskiy et al. Nov 2013 B2
8583619 Ghods et al. Nov 2013 B2
8607306 Bridge et al. Dec 2013 B1
8650498 Mihovilovic Feb 2014 B1
8719445 Ko May 2014 B2
8719810 Oh May 2014 B2
8745267 Luecke et al. Jun 2014 B2
8782637 Khalid Jul 2014 B2
8825597 Houston et al. Sep 2014 B1
8849955 Prahlad et al. Sep 2014 B2
8868574 Kiang et al. Oct 2014 B2
8892679 Destagnol et al. Nov 2014 B1
8914856 Velummylum et al. Dec 2014 B1
8914900 Smith et al. Dec 2014 B2
8918387 Sokolov Dec 2014 B1
8949179 Besen et al. Feb 2015 B2
8949939 Peddada Feb 2015 B2
8955103 Kline, III et al. Feb 2015 B2
8959579 Barton et al. Feb 2015 B2
8966062 Giese et al. Feb 2015 B1
8990307 Barreto et al. Mar 2015 B2
8990955 Hymel et al. Mar 2015 B2
9015248 Barreto et al. Apr 2015 B2
9054919 Kiang et al. Jun 2015 B2
9239846 Besen et al. Jan 2016 B2
9244934 Besen et al. Jan 2016 B2
9396216 Barreto et al. Jul 2016 B2
9396245 Mackenzie et al. Jul 2016 B2
20010027492 Gupta Oct 2001 A1
20020029218 Bentley et al. Mar 2002 A1
20020091738 Rohrabaugh et al. Jul 2002 A1
20020099772 Deshpande et al. Jul 2002 A1
20020116544 Barnard et al. Aug 2002 A1
20020133509 Johnston et al. Sep 2002 A1
20020147770 Tang Oct 2002 A1
20020194177 Sherman et al. Dec 2002 A1
20030041095 Konda et al. Feb 2003 A1
20030084306 Abburi et al. May 2003 A1
20030093404 Bader et al. May 2003 A1
20030108052 Inoue et al. Jun 2003 A1
20030110264 Whidby et al. Jun 2003 A1
20030115326 Verma et al. Jun 2003 A1
20030135536 Lyons Jul 2003 A1
20030135565 Estrada Jul 2003 A1
20030154306 Perry Aug 2003 A1
20030204490 Kasriel Oct 2003 A1
20030217171 Von Stuermer et al. Nov 2003 A1
20030228015 Futa et al. Dec 2003 A1
20040003104 Boskovic et al. Jan 2004 A1
20040021686 Barberis Feb 2004 A1
20040076187 Peled Apr 2004 A1
20040088647 Miller et al. May 2004 A1
20040098361 Peng May 2004 A1
20040103147 Flesher et al. May 2004 A1
20040111415 Scardino et al. Jun 2004 A1
20040117438 Considine et al. Jun 2004 A1
20040122949 Zmudzinski et al. Jun 2004 A1
20040128359 Horvitz et al. Jul 2004 A1
20040162836 Aronoff et al. Aug 2004 A1
20040177138 Salle et al. Sep 2004 A1
20040181579 Huck et al. Sep 2004 A1
20040196307 Zak et al. Oct 2004 A1
20040201604 Kraenzel et al. Oct 2004 A1
20040218214 Kihara et al. Nov 2004 A1
20040230624 Frolund et al. Nov 2004 A1
20040230652 Estrada et al. Nov 2004 A1
20040246532 Inada Dec 2004 A1
20040260977 Ji et al. Dec 2004 A1
20040267836 Armangau et al. Dec 2004 A1
20050005276 Morgan Jan 2005 A1
20050010860 Weiss et al. Jan 2005 A1
20050022175 Sliger et al. Jan 2005 A1
20050022229 Gabriel et al. Jan 2005 A1
20050028006 Leser et al. Feb 2005 A1
20050033777 Moraes et al. Feb 2005 A1
20050038831 Souder et al. Feb 2005 A1
20050038997 Kojima et al. Feb 2005 A1
20050050228 Perham et al. Mar 2005 A1
20050055306 Miller et al. Mar 2005 A1
20050063083 Dart et al. Mar 2005 A1
20050097061 Shapiro et al. May 2005 A1
20050097225 Glatt et al. May 2005 A1
20050097434 Storisteanu May 2005 A1
20050102328 Ring et al. May 2005 A1
20050108406 Lee et al. May 2005 A1
20050114305 Haynes et al. May 2005 A1
20050114378 Elien et al. May 2005 A1
20050138118 Banatwala et al. Jun 2005 A1
20050172284 Dandekar et al. Aug 2005 A1
20050182966 Pham et al. Aug 2005 A1
20050198299 Beck et al. Sep 2005 A1
20050198452 Watanabe Sep 2005 A1
20050234864 Shapiro Oct 2005 A1
20050234943 Clarke Oct 2005 A1
20050261933 Magnuson Nov 2005 A1
20060005163 Huesken et al. Jan 2006 A1
20060026502 Dutta Feb 2006 A1
20060026535 Hotelling et al. Feb 2006 A1
20060036568 Moore et al. Feb 2006 A1
20060041603 Paterson et al. Feb 2006 A1
20060041752 Tuvell et al. Feb 2006 A1
20060047804 Fredricksen et al. Mar 2006 A1
20060053088 Ali et al. Mar 2006 A1
20060053380 Spataro et al. Mar 2006 A1
20060070083 Brunswig et al. Mar 2006 A1
20060075071 Gillette Apr 2006 A1
20060117247 Fite et al. Jun 2006 A1
20060123062 Bobbitt et al. Jun 2006 A1
20060133340 Rybak et al. Jun 2006 A1
20060168550 Muller et al. Jul 2006 A1
20060173952 Coyle Aug 2006 A1
20060174051 Lordi et al. Aug 2006 A1
20060174054 Matsuki Aug 2006 A1
20060179070 George et al. Aug 2006 A1
20060179309 Cross et al. Aug 2006 A1
20060242204 Karas et al. Oct 2006 A1
20060242206 Brezak et al. Oct 2006 A1
20060259524 Horton Nov 2006 A1
20060265719 Astl et al. Nov 2006 A1
20060271510 Harward et al. Nov 2006 A1
20060288043 Novak et al. Dec 2006 A1
20070016680 Burd et al. Jan 2007 A1
20070028291 Brennan et al. Feb 2007 A1
20070038934 Fellman Feb 2007 A1
20070067349 Jhaveri et al. Mar 2007 A1
20070079242 Jolley et al. Apr 2007 A1
20070100830 Beedubail et al. May 2007 A1
20070115845 Hochwarth et al. May 2007 A1
20070118598 Bedi et al. May 2007 A1
20070124460 McMullen et al. May 2007 A1
20070124737 Wensley et al. May 2007 A1
20070124781 Casey et al. May 2007 A1
20070126635 Houri Jun 2007 A1
20070130143 Zhang et al. Jun 2007 A1
20070130163 Perez et al. Jun 2007 A1
20070162610 Un et al. Jul 2007 A1
20070179993 Arruza Aug 2007 A1
20070198609 Black et al. Aug 2007 A1
20070208878 Barnes-Leon et al. Sep 2007 A1
20070214180 Crawford Sep 2007 A1
20070220016 Estrada et al. Sep 2007 A1
20070220590 Rasmussen et al. Sep 2007 A1
20070240057 Satterfield et al. Oct 2007 A1
20070250762 Mansfield Oct 2007 A1
20070256065 Heishi et al. Nov 2007 A1
20070266304 Fletcher et al. Nov 2007 A1
20070282848 Kiilerich et al. Dec 2007 A1
20070283443 McPherson et al. Dec 2007 A1
20070288290 Motoyama et al. Dec 2007 A1
20080005135 Muthukrishnan et al. Jan 2008 A1
20080005195 Li Jan 2008 A1
20080016146 Gan et al. Jan 2008 A1
20080021959 Naghi et al. Jan 2008 A1
20080028323 Rosen et al. Jan 2008 A1
20080040173 Aleong et al. Feb 2008 A1
20080040503 Kleks et al. Feb 2008 A1
20080040560 Hall et al. Feb 2008 A1
20080046828 Bibliowicz et al. Feb 2008 A1
20080059656 Saliba et al. Mar 2008 A1
20080063210 Goodman et al. Mar 2008 A1
20080065881 Dawson et al. Mar 2008 A1
20080077631 Petri Mar 2008 A1
20080091763 Devonshire et al. Apr 2008 A1
20080091790 Beck Apr 2008 A1
20080104277 Tian May 2008 A1
20080114720 Smith et al. May 2008 A1
20080133674 Knauerhase et al. Jun 2008 A1
20080140732 Wilson et al. Jun 2008 A1
20080147790 Malaney et al. Jun 2008 A1
20080151817 Fitchett et al. Jun 2008 A1
20080154873 Redlich et al. Jun 2008 A1
20080182628 Lee et al. Jul 2008 A1
20080183467 Yuan et al. Jul 2008 A1
20080184130 Tien et al. Jul 2008 A1
20080194239 Hagan Aug 2008 A1
20080195673 Hamel et al. Aug 2008 A1
20080215883 Fok et al. Sep 2008 A1
20080222654 Xu et al. Sep 2008 A1
20080243855 Prahlad et al. Oct 2008 A1
20080250333 Reeves et al. Oct 2008 A1
20080250348 Alimpich et al. Oct 2008 A1
20080263099 Brady-Kalnay et al. Oct 2008 A1
20080271095 Shafton Oct 2008 A1
20080276158 Lim et al. Nov 2008 A1
20080281972 Gupta et al. Nov 2008 A1
20080294899 Gazzetta et al. Nov 2008 A1
20090015864 Hasegawa Jan 2009 A1
20090019093 Brodersen et al. Jan 2009 A1
20090019426 Baeumer et al. Jan 2009 A1
20090030710 Levine Jan 2009 A1
20090043848 Kordun Feb 2009 A1
20090044128 Baumgarten et al. Feb 2009 A1
20090049131 Lyle et al. Feb 2009 A1
20090119322 Mills et al. May 2009 A1
20090125469 McDonald et al. May 2009 A1
20090132651 Roger et al. May 2009 A1
20090138808 Moromisato et al. May 2009 A1
20090150417 Ghods et al. Jun 2009 A1
20090150627 Benhase et al. Jun 2009 A1
20090158142 Arthursson et al. Jun 2009 A1
20090164438 Delacruz Jun 2009 A1
20090171983 Samji et al. Jul 2009 A1
20090172201 Carmel Jul 2009 A1
20090177754 Brezina et al. Jul 2009 A1
20090193107 Srinivasan et al. Jul 2009 A1
20090193345 Wensley et al. Jul 2009 A1
20090198772 Kim et al. Aug 2009 A1
20090210459 Nair et al. Aug 2009 A1
20090214115 Kimura et al. Aug 2009 A1
20090235167 Boyer et al. Sep 2009 A1
20090235181 Saliba et al. Sep 2009 A1
20090235189 Aybes et al. Sep 2009 A1
20090249224 Davis et al. Oct 2009 A1
20090254589 Nair et al. Oct 2009 A1
20090260060 Smith et al. Oct 2009 A1
20090265430 Bechtel et al. Oct 2009 A1
20090271708 Peters et al. Oct 2009 A1
20090276771 Nickolov et al. Nov 2009 A1
20090282212 Peterson Nov 2009 A1
20090282483 Bennett Nov 2009 A1
20090300356 Crandell Dec 2009 A1
20090300527 Malcolm et al. Dec 2009 A1
20090327358 Lukiyanov et al. Dec 2009 A1
20090327405 FitzGerald et al. Dec 2009 A1
20090327961 De Vorchik et al. Dec 2009 A1
20100011292 Marinkovich et al. Jan 2010 A1
20100011447 Jothimani Jan 2010 A1
20100017262 Iyer et al. Jan 2010 A1
20100017619 Errico Jan 2010 A1
20100036929 Scherpa et al. Feb 2010 A1
20100042720 Stienhans et al. Feb 2010 A1
20100057560 Skudlark et al. Mar 2010 A1
20100057785 Khosravy et al. Mar 2010 A1
20100076946 Barker et al. Mar 2010 A1
20100082534 Sagar et al. Apr 2010 A1
20100082634 Leban Apr 2010 A1
20100083136 Komine et al. Apr 2010 A1
20100088150 Mazhar et al. Apr 2010 A1
20100092126 Kaliszek et al. Apr 2010 A1
20100093310 Gbadegesin et al. Apr 2010 A1
20100107225 Spencer et al. Apr 2010 A1
20100122184 Vonog et al. May 2010 A1
20100131868 Chawla et al. May 2010 A1
20100151431 Miller Jun 2010 A1
20100153835 Xiong et al. Jun 2010 A1
20100162365 Del Real Jun 2010 A1
20100162374 Nair Jun 2010 A1
20100179940 Gilder et al. Jul 2010 A1
20100185463 Noland et al. Jul 2010 A1
20100185932 Coffman et al. Jul 2010 A1
20100191689 Cortes et al. Jul 2010 A1
20100198783 Wang et al. Aug 2010 A1
20100198871 Stiegler et al. Aug 2010 A1
20100198944 Ho et al. Aug 2010 A1
20100205392 Schnapp et al. Aug 2010 A1
20100205537 Knighton et al. Aug 2010 A1
20100212010 Stringer et al. Aug 2010 A1
20100218237 Ferris et al. Aug 2010 A1
20100223378 Wei Sep 2010 A1
20100229085 Nelson et al. Sep 2010 A1
20100235526 Carter et al. Sep 2010 A1
20100235539 Carter et al. Sep 2010 A1
20100241611 Zuber Sep 2010 A1
20100241972 Spataro et al. Sep 2010 A1
20100242028 Weigert Sep 2010 A1
20100250120 Waupotitsch et al. Sep 2010 A1
20100251340 Martin et al. Sep 2010 A1
20100257457 De Goes Oct 2010 A1
20100262582 Garcia-Ascanio et al. Oct 2010 A1
20100267588 Nelson et al. Oct 2010 A1
20100274765 Murphy et al. Oct 2010 A1
20100274772 Samuels Oct 2010 A1
20100281118 Donahue et al. Nov 2010 A1
20100290623 Banks et al. Nov 2010 A1
20100306379 Ferris Dec 2010 A1
20100312615 Murphy et al. Dec 2010 A1
20100318893 Matthews et al. Dec 2010 A1
20100322252 Suganthi et al. Dec 2010 A1
20100325155 Skinner et al. Dec 2010 A1
20100325527 Estrada et al. Dec 2010 A1
20100325559 Westerinen et al. Dec 2010 A1
20100325655 Perez Dec 2010 A1
20100332401 Prahlad et al. Dec 2010 A1
20100332962 Hammer et al. Dec 2010 A1
20100333116 Prahlad et al. Dec 2010 A1
20110001763 Murakami Jan 2011 A1
20110016409 Grosz et al. Jan 2011 A1
20110022559 Andersen et al. Jan 2011 A1
20110022812 van der Linden et al. Jan 2011 A1
20110029883 Lussier et al. Feb 2011 A1
20110040812 Phillips Feb 2011 A1
20110041083 Gabai et al. Feb 2011 A1
20110047413 McGill et al. Feb 2011 A1
20110047484 Mount et al. Feb 2011 A1
20110052155 Desmarais et al. Mar 2011 A1
20110054968 Galaviz Mar 2011 A1
20110055299 Phillips Mar 2011 A1
20110055721 Jain et al. Mar 2011 A1
20110061045 Phillips Mar 2011 A1
20110061046 Phillips Mar 2011 A1
20110065082 Gal et al. Mar 2011 A1
20110066951 Ward-Karet et al. Mar 2011 A1
20110078243 Carpenter et al. Mar 2011 A1
20110083167 Carpenter et al. Apr 2011 A1
20110093567 Jeon et al. Apr 2011 A1
20110099006 Sundararaman et al. Apr 2011 A1
20110107088 Eng et al. May 2011 A1
20110107205 Chow et al. May 2011 A1
20110113320 Neff et al. May 2011 A1
20110119313 Sung et al. May 2011 A1
20110125847 Cocheu et al. May 2011 A1
20110131299 Sardary Jun 2011 A1
20110137991 Russell Jun 2011 A1
20110142410 Ishii Jun 2011 A1
20110145187 Himmelsbach et al. Jun 2011 A1
20110145282 Moore et al. Jun 2011 A1
20110145589 Camenisch et al. Jun 2011 A1
20110154180 Evanitsky et al. Jun 2011 A1
20110161289 Pei et al. Jun 2011 A1
20110167125 Achlioptas Jul 2011 A1
20110167353 Grosz et al. Jul 2011 A1
20110167435 Fang Jul 2011 A1
20110185292 Chawla et al. Jul 2011 A1
20110202424 Chun et al. Aug 2011 A1
20110202599 Yuan et al. Aug 2011 A1
20110208958 Stuedi et al. Aug 2011 A1
20110209064 Jorgensen et al. Aug 2011 A1
20110213765 Cui et al. Sep 2011 A1
20110219419 Reisman Sep 2011 A1
20110225417 Maharajh et al. Sep 2011 A1
20110238458 Purcell et al. Sep 2011 A1
20110238621 Agrawal Sep 2011 A1
20110238759 Spataro et al. Sep 2011 A1
20110239135 Spataro et al. Sep 2011 A1
20110246294 Robb et al. Oct 2011 A1
20110246950 Luna et al. Oct 2011 A1
20110252071 Cidon Oct 2011 A1
20110252312 Lemonik et al. Oct 2011 A1
20110252320 Arrasvuori et al. Oct 2011 A1
20110252339 Lemonik et al. Oct 2011 A1
20110258461 Bates Oct 2011 A1
20110258561 Ladouceur et al. Oct 2011 A1
20110277027 Hayton et al. Nov 2011 A1
20110282710 Akkiraju et al. Nov 2011 A1
20110289433 Whalin et al. Nov 2011 A1
20110296022 Ferris et al. Dec 2011 A1
20110313803 Friend et al. Dec 2011 A1
20110314145 Raleigh et al. Dec 2011 A1
20110320197 Conejero et al. Dec 2011 A1
20110320936 Mohan et al. Dec 2011 A1
20120036370 Lim et al. Feb 2012 A1
20120057696 Chew Mar 2012 A1
20120064879 Panei Mar 2012 A1
20120072436 Pierre et al. Mar 2012 A1
20120079095 Evans et al. Mar 2012 A1
20120089610 Agrawal et al. Apr 2012 A1
20120089659 Halevi et al. Apr 2012 A1
20120089710 Rakowski et al. Apr 2012 A1
20120096521 Peddada Apr 2012 A1
20120101995 Agetsuma et al. Apr 2012 A1
20120110005 Kuo et al. May 2012 A1
20120110436 Adler, III et al. May 2012 A1
20120110443 Lemonik et al. May 2012 A1
20120117626 Yates et al. May 2012 A1
20120124306 Abercrombie et al. May 2012 A1
20120124547 Halbedel May 2012 A1
20120130900 Tang et al. May 2012 A1
20120134491 Liu May 2012 A1
20120136936 Quintuna May 2012 A1
20120143825 Boehm et al. Jun 2012 A1
20120144283 Hill et al. Jun 2012 A1
20120150888 Hyatt et al. Jun 2012 A1
20120151265 Bender et al. Jun 2012 A1
20120151551 Readshaw et al. Jun 2012 A1
20120158908 Luna et al. Jun 2012 A1
20120159178 Lin et al. Jun 2012 A1
20120159310 Chang et al. Jun 2012 A1
20120166516 Simmons et al. Jun 2012 A1
20120173612 Vegesna-Venkata et al. Jul 2012 A1
20120173625 Berger Jul 2012 A1
20120179802 Narasimhan et al. Jul 2012 A1
20120179981 Whalin et al. Jul 2012 A1
20120185355 Kilroy Jul 2012 A1
20120185913 Martinez et al. Jul 2012 A1
20120192055 Antebi et al. Jul 2012 A1
20120192086 Ghods et al. Jul 2012 A1
20120203670 Piersol Aug 2012 A1
20120203908 Beaty et al. Aug 2012 A1
20120204032 Wilkins et al. Aug 2012 A1
20120206653 Graves et al. Aug 2012 A1
20120207449 Angquist et al. Aug 2012 A1
20120209815 Carson et al. Aug 2012 A1
20120209889 Agnoli et al. Aug 2012 A1
20120214444 McBride et al. Aug 2012 A1
20120218885 Abel et al. Aug 2012 A1
20120221789 Felter Aug 2012 A1
20120224691 Purohit Sep 2012 A1
20120226767 Luna et al. Sep 2012 A1
20120233155 Gallmeier et al. Sep 2012 A1
20120233205 McDermott Sep 2012 A1
20120233543 Vagell et al. Sep 2012 A1
20120240061 Hillenius et al. Sep 2012 A1
20120240183 Sinha Sep 2012 A1
20120257249 Natarajan Oct 2012 A1
20120259964 Lin et al. Oct 2012 A1
20120263166 Cho et al. Oct 2012 A1
20120266203 Elhadad et al. Oct 2012 A1
20120284290 Keebler et al. Nov 2012 A1
20120284638 Cutler et al. Nov 2012 A1
20120284664 Zhao Nov 2012 A1
20120291011 Quine Nov 2012 A1
20120296790 Robb Nov 2012 A1
20120309540 Holme et al. Dec 2012 A1
20120311157 Erickson et al. Dec 2012 A1
20120317239 Mulder et al. Dec 2012 A1
20120317487 Lieb et al. Dec 2012 A1
20120328259 Seibert, Jr. et al. Dec 2012 A1
20120331177 Jensen Dec 2012 A1
20120331441 Adamson Dec 2012 A1
20130007245 Malik et al. Jan 2013 A1
20130007471 Grab et al. Jan 2013 A1
20130007894 Dang et al. Jan 2013 A1
20130013560 Goldberg et al. Jan 2013 A1
20130014023 Lee et al. Jan 2013 A1
20130042106 Persaud et al. Feb 2013 A1
20130054634 Chakraborty et al. Feb 2013 A1
20130055127 Saito et al. Feb 2013 A1
20130067232 Cheung et al. Mar 2013 A1
20130073403 Tuchman et al. Mar 2013 A1
20130073621 Waddoups et al. Mar 2013 A1
20130080765 Mohanty et al. Mar 2013 A1
20130080919 Kiang et al. Mar 2013 A1
20130110565 Means, Jr. et al. May 2013 A1
20130110961 Jadhav May 2013 A1
20130117337 Dunham May 2013 A1
20130117376 Filman et al. May 2013 A1
20130124458 Barreto et al. May 2013 A1
20130124638 Barreto et al. May 2013 A1
20130124984 Kuspa May 2013 A1
20130138608 Smith May 2013 A1
20130138615 Gupta et al. May 2013 A1
20130151690 Shah et al. Jun 2013 A1
20130159411 Bowen Jun 2013 A1
20130163289 Kim et al. Jun 2013 A1
20130167253 Seleznev et al. Jun 2013 A1
20130179947 Kline, III et al. Jul 2013 A1
20130185347 Romano Jul 2013 A1
20130185558 Seibert et al. Jul 2013 A1
20130191339 Haden et al. Jul 2013 A1
20130198600 Lockhart et al. Aug 2013 A1
20130212067 Piasecki et al. Aug 2013 A1
20130212486 Joshi et al. Aug 2013 A1
20130218978 Weinstein et al. Aug 2013 A1
20130226876 Gati et al. Aug 2013 A1
20130227522 Lerum et al. Aug 2013 A1
20130239049 Perrodin et al. Sep 2013 A1
20130246901 Massand Sep 2013 A1
20130246932 Zaveri et al. Sep 2013 A1
20130254699 Bashir et al. Sep 2013 A1
20130262210 Savage et al. Oct 2013 A1
20130262862 Hartley Oct 2013 A1
20130268480 Dorman Oct 2013 A1
20130268491 Chung et al. Oct 2013 A1
20130268999 Kiang et al. Oct 2013 A1
20130275398 Dorman et al. Oct 2013 A1
20130275429 York et al. Oct 2013 A1
20130275509 Micucci et al. Oct 2013 A1
20130282830 Besen et al. Oct 2013 A1
20130304694 Barreto et al. Nov 2013 A1
20130304697 Movida Nov 2013 A1
20130305039 Gauda Nov 2013 A1
20130325803 Akirav et al. Dec 2013 A1
20130326344 Masselle et al. Dec 2013 A1
20140006357 Davis et al. Jan 2014 A1
20140006465 Davis et al. Jan 2014 A1
20140007205 Oikonomou Jan 2014 A1
20140013112 Cidon et al. Jan 2014 A1
20140019497 Cidon et al. Jan 2014 A1
20140019498 Cidon et al. Jan 2014 A1
20140032489 Hebbar et al. Jan 2014 A1
20140032616 Nack Jan 2014 A1
20140033277 Xiao et al. Jan 2014 A1
20140033291 Liu Jan 2014 A1
20140033324 Kiang et al. Jan 2014 A1
20140040182 Gilder et al. Feb 2014 A1
20140040206 Ramakrishnan et al. Feb 2014 A1
20140047509 Bhogal et al. Feb 2014 A1
20140052939 Tseng et al. Feb 2014 A1
20140059002 Lockhart et al. Feb 2014 A1
20140059217 Pizurica Feb 2014 A1
20140068589 Barak Mar 2014 A1
20140074629 Rathod Mar 2014 A1
20140082071 Rexer Mar 2014 A1
20140150023 Gudorf et al. May 2014 A1
20140156373 Roberts et al. Jun 2014 A1
20140172595 Beddow et al. Jun 2014 A1
20140172783 Suzuki et al. Jun 2014 A1
20140172799 Dorman Jun 2014 A1
20140188798 Mackenzie et al. Jul 2014 A1
20140195485 Dorman Jul 2014 A1
20140201145 Dorman et al. Jul 2014 A1
20140244600 Schmidt et al. Aug 2014 A1
20140280605 Zhang Sep 2014 A1
20140337291 Dorman et al. Nov 2014 A1
20140337491 Barreto et al. Nov 2014 A1
20140344456 Buzbee et al. Nov 2014 A1
20140359286 Wen et al. Dec 2014 A1
20140372376 Smith et al. Dec 2014 A1
20140379647 Smith et al. Dec 2014 A1
20150019723 Kweon et al. Jan 2015 A1
20150039556 Mackenzie et al. Feb 2015 A1
20150186668 Whaley et al. Jul 2015 A1
20150237406 Ochoa et al. Aug 2015 A1
20150339113 Dorman et al. Nov 2015 A1
20160065672 Savage et al. Mar 2016 A1
Foreign Referenced Citations (43)
Number Date Country
2724521 Nov 2009 CA
101997924 Mar 2011 CN
102264063 Nov 2011 CN
0348614 Jan 1990 EP
0921661 Jun 1999 EP
1349088 Oct 2003 EP
1528746 May 2005 EP
1933242 Jun 2008 EP
2372574 Oct 2011 EP
2610776 Jul 2013 EP
2453924 Apr 2009 GB
2471282 Dec 2010 GB
09-101937 Apr 1997 JP
11-025059 Jan 1999 JP
2003273912 Sep 2003 JP
2004310272 Nov 2004 JP
09-269925 Oct 2007 JP
2008250944 Oct 2008 JP
20020017444 Mar 2002 KR
20040028036 Apr 2004 KR
20050017674 Feb 2005 KR
20060070306 Jun 2006 KR
20060114871 Nov 2006 KR
20070043353 Apr 2007 KR
20070100477 Oct 2007 KR
20100118836 Nov 2010 KR
20110074096 Jun 2011 KR
20110076831 Jul 2011 KR
WO-0007104 Feb 2000 WO
WO-0219128 Mar 2002 WO
WO-2004097681 Nov 2004 WO
WO-2006028850 Mar 2006 WO
WO-2007024438 Mar 2007 WO
WO-2007035637 Mar 2007 WO
WO-2007113573 Oct 2007 WO
WO-2008011142 Jan 2008 WO
WO-2008076520 Jun 2008 WO
WO-2011109416 Sep 2011 WO
WO-2012167272 Dec 2012 WO
WO-2013009328 Jan 2013 WO
WO-2013013217 Jan 2013 WO
WO-2013041763 Mar 2013 WO
WO-2013166520 Nov 2013 WO
Non-Patent Literature Citations (126)
Entry
“Conceptboard”, One-Step Solution for Online Collaboration, retrieved from websites http://conceptboard.com and https://www.youtube.com/user/ConceptboardApp?feature=watch, printed on Jun. 13, 2013, 9 pages.
“How-to Geek, How to Sync Specific Folders With Dropbox,” downloaded from the internet http://www.howtogeek.com, Apr. 23, 2013, 5 pages.
“Microsoft Office SharePoint 2007 User Guide,” Feb. 16, 2010, pp. 1-48.
“PaperPort Professional 14,” PC Mag. Com review, published Feb. 2012, Ziff Davis, Inc., 8 pages.
“PaperPort,” Wikipedia article (old revision), published May 19, 2012, Wikipedia Foundation, 2 pages.
“Quickoffice Enhances Android Mobile office Application for Improved Productivity on latest Smartphone and Table Devices,” QuickOffice Press Release, Nov. 21, 2011, QuickOffice Inc., 2 pages.
“QuickOffice,” Wikipedia Article (old revision), published May 9, 2012, Wikipedia Foundation, 2 pages.
“Understanding Metadata,” National Information Standards Organization, NISO Press, 2004, 20 pages.
Cisco, “FTP Load Balancing on ACE in Routed Mode Configuration Example,” DocWiki, Jun. 2011, 7 pages.
Conner, “Google Apps: The Missing Manual,” published by O'Reilly Media, May 27, 2008, 24 pages.
Exam Report for EP13158415.3, Applicant: Box, Inc. Mailed Jun. 4, 2013, 8 pages.
Exam Report for EP13168784.0, Applicant: Box, Inc. Mailed Nov. 21, 2013, 7 pages.
Exam Report for GB1300188.8, Applicant: Box, Inc. Mailed May 31, 2013, 8 pages
Exam Report for GB1306011.6, Applicant: Box, Inc. Mailed Apr. 18, 2013, 8 pages.
Exam Report for GB1309209.3, Applicant: Box, Inc. Mailed Oct. 30, 2013, 11 pages.
Exam Report for GB1310666.1, Applicant: Box, Inc. Mailed Aug. 30, 2013, 10 pages.
Exam Report for GB1311417.8, Applicant: Box, Inc. Mailed Dec. 20, 2013, 5 pages.
Exam Report for GB1312095.1, Applicant: Box, Inc. Mailed Dec. 12, 2013, 7 pages.
Exam Report for GB1312874.9, Applicant: Box, Inc. Mailed Dec. 20, 2013, 11 pages.
Exam Report for GB1313559.5, Applicant: Box, Inc., Mailed Aug. 22, 2013, 19 pages.
Exam Report for GB1316532.9, Applicant: Box, Inc. Mailed Oct. 31, 2013, 10 pages.
Exam Report for GB1316533.7, Applicant: Box, Inc. Mailed Oct. 8, 2013, 9 pages.
Exam Report for GB1316971.9, Applicant: Box, Inc. Mailed Nov. 26, 2013, 10 pages.
Exam Report for GB1317600.3, Applicant: Box, Inc. Mailed Nov. 21, 2013, 8 pages.
Exam Report for GB1318373.6, Applicant: Box, Inc. Mailed Dec. 17, 2013, 4 pages.
Exam Report for GB1320902.8, Applicant: Box, Inc. Mailed Dec. 20, 2013, 4 pages.
Gedymin, “Cloud computing with an emphasis on Google App Engine,” Master Final Project, Sep. 2011, 146 pages.
Google Docs, http://web. Archive.org/web/20100413105758/http://en.wikipedia.org/wiki/Google—docs, Apr. 13, 2010, 6 pages.
International Search Report and Written Opinion for PCT/US2008/012973 dated Apr. 30, 2009, pp. 1-11.
International Search Report and Written Opinion for PCT/US2011/039126 mailed on Oct. 6, 2011, pp. 1-13.
International Search Report and Written Opinion for PCT/US2011/041308 Mailed Jul. 2, 2012, pp. 1-16.
International Search Report and Written Opinion for PCT/US2011/056472 mailed on Jun. 22, 2012, pp. 1-12.
International Search Report and Written Opinion for PCT/US2011/057938, Applicant: Box, Inc., Mailed Mar. 29, 2013, 10 pages.
International Search Report and Written Opinion for PCT/US2011/060875 Mailed Oct. 30, 2012, pp. 1-10.
International Search Report and Written Opinion for PCT/US2012/056955, Applicant: Box, Inc., Mailed Mar. 27, 2013, pp. 1-11.
International Search Report and Written Opinion for PCT/US2012/063041, Applicant: Box, Inc., Mailed Mar. 29, 2013, 12 pages.
International Search Report and Written Opinion for PCT/US2012/065617, Applicant: Box, Inc., Mailed Mar. 29, 2013, 9 pages.
International Search Report and Written Opinion for PCT/US2012/067126, Applicant: Box, Inc., Mailed Mar. 29, 2013, 10 pages.
International Search Report and Written Opinion for PCT/US2012/070366, Applicant: Box, Inc., Mailed Apr. 24, 2013, 10 pages.
International Search Report and Written Opinion for PCT/US2013/020267, Applicant: Box, Inc., Mailed May 7, 2013, 10 pages.
International Search Report and Written Opinion for PCT/US2013/023889, Applicant: Box, Inc., Mailed Jun. 24, 2013, 13 pages.
International Search Report and Written Opinion for PCT/US2013/029520, Applicant: Box, Inc., Mailed Jun. 26, 2013, 10 pages.
International Search Report and Written Opinion for PCT/US2013/034662, Applicant: Box, Inc., Mailed May 31, 2013, 10 pages.
International Search Report and Written Opinion for PCT/US2013/035404, Applicant: Box, Inc., Mailed Jun. 26, 2013, 13 pages.
International Search Report and Written Opinion for PCT/US2013/039782, Applicant: Box, Inc., Mailed Aug. 28, 2013, 15 pages.
Internet Forums, http://web.archive.org/web/20100528195550/http://en.wikipedia.org/wiki/Internet—forums, Wikipedia, May 30, 2010, pp. 1-20.
Langfeld L. et al., “Microsoft SharePoint 2003 Unleashed,” Chapters 11 and 15, Jun. 2004, pp. 403-404, 557-561, 578-581.
Lars, “35 Very Useful Online Tools for Improving your project Management and Team Collaboration,” Apr. 31, 2010, tripwiremagazine.com, pp. 1-32.
Palmer, “Load Balancing FTP Servers,” BlogNav, Oct. 2008, 2 pages.
Parr, “Google Docs Improves Commenting, Adds E-mail Notifications,” Apr. 16, 2011, mashable.com, pp. 1-6.
Partial International Search Report for PCT/US2011/041308 dated Feb. 27, 2012, pp. 1-2.
Patent Court Document of Approved Judgment for GB0602349.3 and GB0623571.7; Mar. 3, 2009, 17 pages.
Supplementary European Search Report European Application No. EP 08 85 8563 dated Jun. 20, 2011 pp. 1-5.
Wayback, “Wayback machine,” Wayback, Jun. 1, 2011, 1 page.
Wiki, http://web.archive.org/web/20100213004936/http://en.wikipedia.org/wiki/Wiki, Feb. 13, 2010, pp. 1-16.
Yahoo! Groups, http://web.archive.org/web/20090320101529/http://en.wikipedia.org/wiki/Yahoo!—Groups, Wikipedia, Mar. 20, 2009, pp. 1-6.
“Average Conversion Time for a D60 RAW file?” http://www.dpreview.com, Jul. 22, 2002, 4 pages.
“Revolving sync conflicts; frequently asked questions,” Microsoft Tech Support, Jul. 16, 2012, retrieved from the Internet: http://web.archive.org/web, 2 pages.
“Troubleshoot sync problems,” Microsoft Tech Support: May 2, 2012, retrieved from the internet, http://web. Archive.org/web, 3 pages.
“Tulsa TechFest 2012—Agenda,” retrieved from the website, http://web.archive.org, Oct. 2, 2012, 2 pages.
Burns, “Developing Secure Mobile Applications for Android,” Oct. 2008, Version 1.0, 1-28 pages.
Cohen, “Debating the Definition of Cloud Computing Platforms,” retrieved from the internet, http://forbes.com, Feb. 3, 2014, 7 pages.
Comes, “MediaXchange User's Manual,” Version 1.15.15, Feb. 1, 2009, pp. 1-90.
Delendik, “Evolving with Web Standards—The Story of PDF.JS,” retrieved from the internet, http://people.mozilla.org, Oct. 12, 2012, 36 pages.
Delendik, “My PDF.js talk slides from Tulsa TechFest,” retrieved from the internet, http://twitter.com, Oct. 12, 2012, 2 pages.
Duffy, “The Best File-Syncing Services,” pcmag.com, retrieved from the internet: http://www.pcmag.com, Sep. 28, 2012, 7 pages.
Exam Report for EP13177108.1, Applicant: Box, Inc. Mailed May 26, 2014, 6 pages.
Exam Report for EP13185269.1, Applicant: Box, Inc. Mailed Jan. 28, 7 pages.
Exam Report for GB1308842.2, Applicant: Box, Inc. Mailed Mar. 10, 2014, 4 pages.
Exam Report for GB1312264.3, Applicant: Box, Inc. Mailed Mar. 24, 2014, 7 pages.
Exam Report for GB1314771.5, Applicant: Box, Inc. Mailed Feb. 17, 2014, 7 pages.
Exam Report for GB1318792.7, Applicant: Box, Inc. Mailed May 22, 2014, 2 pages.
International Search Report and Written Opinion for PCT/US2013/034765, Applicant: Box, Inc., Mailed Jan. 20, 2014, 15 pages.
John et al., “Always Sync Support Forums—View topic—Allway sync funny behavior,” Allway Sync Support Forum at http://sync-center.com, Mar. 28, 2011, XP055109680, 2 pages.
Partial Search Report for EP131832800, Applicant: Box, Inc. Mailed May 8, 2014, 5 pages.
Pyle et al., “How to enable Event logging for Offline Files (Client Side Caching) in Windows Vista,” Feb. 18, 2009, retrieved from the internet: http://blogs.technet.com, 3 pages.
Rao, “Box Acquires Crocodoc to Add HTML5 Document Converter and Sleek Content Viewing Experience to Cloud Storage Platform,” retrieved from the internet, http://techcrunch.com, May 9, 2013, 8 pages.
Search Report for EP 11729851.3, Applicant: Box, Inc. Mailed Feb. 7, 2014, 9 pages.
Search Report for EP13187217.8, Applicant: Box, Inc. Mailed Apr. 15, 2014, 12 pages.
Search Report for EP141509422, Applicant: Box, Inc. Mailed May 8, 2014, 7 pages.
Search Report for EP14151588.2, Applicant: Box, Inc. Mailed Apr. 15, 2014, 12 pages.
Sommerer, “Presentable Document Format: Improved On-demand PDF to HTML Conversion,” retrieved from the internet, http://research.microsoft.com, 8 pages.
Tulloch et al., “Windows Vista Resource Kit,” Apr. 8, 2007, Microsoft Press, XP055113067, 6 pages.
Walker, “PDF.js project meeting notes,” retrieved from the internet, http://groups.google.com, May 15, 2014, 1 page.
Exam Report for GB1410569.6 Applicant: Box, Inc. Mailed Jul. 11, 2014, 9 pages.
Extended Search Report for EP131832800, Applicant: Box, Inc. Mailed Aug. 25, 2014, 7 pages.
Extended Search Report for EP141509422, Applicant: Box, Inc. Mailed Aug. 26, 2014, 12pages.
Search Report for EP 13189144.2 Applicant: Box, Inc. Mailed Sep. 1, 2014, 9 pages.
Exam Report for GB1312874.9 Applicant: Box, Inc. Mailed Sep. 26, 2014, 2 pages.
Exam Report for GB1415126.0 Applicant: Box, Inc. Mailed Oct. 2, 2014, 8 pages.
Exam Report for GB1415314.2 Applicant: Box, Inc. Mailed Oct. 7, 2014, 6 pages.
Exam Report for GB1309209.3 Applicant: Box, Inc. Mailed Oct. 7, 2014, 3 pages.
Exam Report for GB1315232.7 Applicant: Box, Inc. Mailed Oct. 9, 2014, 5 pages.
Exam Report for GB1318789.3 Applicant: Box, Inc. Mailed Oct. 30, 2014, 6 pages.
Microsoft Windows XP Professional Product Documentation: How Inheritance Affects File and Folder Permissions, Apr. 11, 2014, 2 pages.
Exam Report for GB1317393.5 Applicant: Box, Inc. Mailed Nov. 7, 2014, 6 pages.
Exam Report for GB1311417.8 Applicant: Box, Inc. Mailed Nov. 7, 2014, 2 pages.
Exam Report for GB1311421.0 Applicant: Box, Inc. Mailed Nov. 7, 2014, 4 pages.
Exam Report for GB1316682.2 Applicant: Box, Inc. Mailed Nov. 19, 2014, 6 pages.
Exam Report for GB1312095.1 Applicant: Box, Inc. Mailed Nov. 19, 2014, 5 pages.
Exam Report for GB1313559.5 Applicant: Box, Inc. Mailed Nov. 4, 2014, 2 pages.
User's Guide for SMART Board Software for Windows, published Dec. 2004, 90 pages.
Zambonini et al., “Automated Measuring of Interaction with User Interfaces,” Published as WO2007113573 Oct. 2007, 19 pages.
Exam Report for GB1309209.3 Applicant: Box, Inc. Mailed Jan. 19, 2015, 6 pages.
“Agilewords—How to Request Approval,” YouTube, http://www.youtube.com/watch?v=3-Ov3DYNN3Q, Jan. 31, 2011, 2 pages.
“Agilewords—Features, Powerful Features Yet Simple,” Jun. 1, 2011, http://web.archive.org/web/20110601223756/http://agilewords.com/product/features, 3 pages.
Conner, “Google Apps: The Missing Manual,” published by O'Reilly Media, May 27, 2008, 42 pages.
Exam Report for EP 13177108.1, Applicant: Box, Inc. Mailed Feb. 17, 2015, 6 pages.
Exam Report for GB1312264.3 Applicant: Box, Inc. Mailed Jan. 30, 2015, 5 pages.
Exam Report for GB1312874.9 Applicant: Box, Inc. Mailed Feb. 10, 2015, 7 pages.
Exam Report for GB1316685.5 Applicant: Box, Inc. Mailed Feb. 17, 2015, 5 pages.
Exam Report for EP 13185269.1, Applicant: Box, Inc. Mailed Feb. 13, 2015, 8 pages.
Exam Report for GB1311459.0 Applicant: Box, Inc. Mailed Aug. 19, 2013, 6 pages.
“Dropbox: Sync only specific folders,” posted on Feb. 9, 2012, available online at http://www.tech-recipes.com/rx/20865/dropbox-sync-only-specific-folders/, 4 pages.
Exam Report for GB1220644.7 Applicant: Box, Inc. Mailed May 1, 2015, 4 pages.
Invens, “Using and Troubleshooting Offline Files,” Jun. 23, 2002, Windows IT Pro, pp. 1-5.
Invens, “Using and Troubleshooting Offline Files,” Jun. 23, 2002, Windows IT Pro, Figures 1 and 2, 2 pages.
“How-to Geek, How to Sync Specific Folders With Dropbox,” originally written on Jun. 20, 2010 and archived version retrieved from WaybackMachine as published online on Jun. 4, 2010 at http://www.howtogeek.com/howto/18285/sync-specific-folders-with-dropbox, 7 pages.
Exam Report for GB1316532.9 Applicant: Box, Inc. Mailed Mar. 27, 2015, 6 pages.
Burney, “How to Move Document from Your Computer to Your iPad and Back Again,” May 31, 2011, 3 pages.
Exam Report for GB1413461.3; Applicant: Box, Inc. Mailed Aug. 21, 2015, 6 pages.
Fu et al., Efficient and Fine-Grained Sharing of Encrypted Files, Quality of Service (IWQos), 2010 18th International Workshop on year 2010, pp. 1-2.
Sommerer, “Presentable Document Format: Improved On-demand PDF to HTML Conversion,” retrieved from the internet, http://research.microsoft.com, Nov. 2004, 8 pages.
Ivens, “Using and Troubleshooting Offline Files,” Jun. 23, 2002, Windows IT Pro, Figure 1.
Ivens, “Configuring Offline Files,” Apr. 21, 2002, Windows IT Pro, pp. 1-5.
Exam Report for GB1316532.9; Applicant: Box, Inc., Mailed Mar. 8, 2016, 3 pages.
Related Publications (1)
Number Date Country
20140201138 A1 Jul 2014 US
Provisional Applications (1)
Number Date Country
61751578 Jan 2013 US