WO2013162837A1 - Partage et synchronisation de fichiers mémorisés électroniquement - Google Patents

Partage et synchronisation de fichiers mémorisés électroniquement Download PDF

Info

Publication number
WO2013162837A1
WO2013162837A1 PCT/US2013/034983 US2013034983W WO2013162837A1 WO 2013162837 A1 WO2013162837 A1 WO 2013162837A1 US 2013034983 W US2013034983 W US 2013034983W WO 2013162837 A1 WO2013162837 A1 WO 2013162837A1
Authority
WO
WIPO (PCT)
Prior art keywords
file
file system
cloud
computer
electronically stored
Prior art date
Application number
PCT/US2013/034983
Other languages
English (en)
Inventor
Adam BESEN
David CATMULL
Hwi CHEONG
Alexander Deneui
Hendrik Mueller
Frank Pape
Ronald Schneider
Rishi SHARMA
Himanshu Vasishth
David Wurtz
Andrei MIRESTEAN
Michael Jeffrey PROCOPIO
Michael SORVILLO
Original Assignee
Google Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US13/453,909 external-priority patent/US9529818B2/en
Priority claimed from US13/453,860 external-priority patent/US20130282830A1/en
Priority claimed from US13/453,748 external-priority patent/US9244934B2/en
Priority claimed from US13/453,678 external-priority patent/US9239846B2/en
Priority claimed from US13/453,799 external-priority patent/US8949179B2/en
Application filed by Google Inc. filed Critical Google Inc.
Priority to CN201810489389.9A priority Critical patent/CN108717454B/zh
Priority to EP13782583.2A priority patent/EP2842050A4/fr
Priority to CN201810489494.2A priority patent/CN108710533B/zh
Priority to CN201810490633.3A priority patent/CN108804213B/zh
Priority to CN201380029205.6A priority patent/CN104685485B/zh
Publication of WO2013162837A1 publication Critical patent/WO2013162837A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/176—Support for shared access to files; File sharing support
    • G06F16/1767—Concurrency control, e.g. optimistic or pessimistic approaches
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/178—Techniques for file synchronisation in file systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/18—File system types
    • G06F16/182—Distributed file systems
    • G06F16/184—Distributed file systems implemented as replicated file system

Definitions

  • This disclosure relates generally to the sharing and synchronization of
  • Cloud entities server computers, desktop computers, personal computers, portable computers, mobile computers, web-enabled computers and other computers including tablet computers, personal digital assistants (PDAs) and smartphones.
  • PDAs personal digital assistants
  • aspects of the present disclosure are directed to architectures, methods, systems and structures that facilitate the sharing and synchronization of electronically stored files among and between Cloud entities and a number of computers, systems, devices and/or users.
  • electronically stored files are initially generated within Cloud entities and are subsequently replicated and synchronized with one or more client computing systems.
  • electronically stored files that are generated within client computing systems are subsequently replicated and synchronized with Cloud entities and other client computing systems.
  • a client determination is made during a synchronization operation whether or not to download/copy a file electronically stored in the Cloud to the client. If the file is of a particular type of file, then it is not downloaded/copied to the client.
  • a file is created locally at the client comprising a link to the file electronically stored in the Cloud.
  • the local electronically stored file may be made a type indicative of its Cloud origination.
  • the local file may be used to invoke a browser to access the file electronically stored in the cloud which may further utilize cloud computing services to access the file.
  • such sharing and synchronization is user administrable thereby permitting the formation of sharing and synchronization groups and/or systems.
  • client computing systems include a Local WATCHER and a Cloud WATCHER which concurrently monitor and detect changes to watched Local File Systems and Cloud File Systems respectively. Detected changes are used to generate work items that are ordered and selectively sent to a number of WORKERS for concurrent processing.
  • electronically stored files placed into a shared folder are automatically shared and synchronized with any authorized users of that shared folder.
  • This SUMMARY is provided to briefly identify some aspects of the present disclosure that are further described below in the DESCRIPTION. This SUMMARY is not intended to identify key or essential features of the present disclosure nor is it intended to limit the scope of any claims.
  • FIG. 1 is schematic diagram depicting an exemplary arrangement for sharing and synchronizing electronically stored files according to an aspect of the present disclosure
  • FIG 2 is a schematic diagram depicting another exemplary arrangement for sharing and synchronizing electronically stored files according to another aspect of the present disclosure
  • FIG 3 is a schematic diagram depicting yet another exemplary architecture for sharing and synchronizing electronically stored files according to an aspect of the present disclosure
  • FIGs 3a - 3c are schematic diagrams depicting exemplary drag-and-drop operations and synchronization status of electronically stored files according to an aspect of the present disclosure
  • FIG 4a is a schematic diagram depicting exemplary functional operation of a SyncCLIENT according to an aspect of the present disclosure
  • FIG 4b is a schematic diagram depicting an exemplary sequence of events when a document is originated in the Cloud and then propagated to a SyncCLIENT according to an aspect of the present disclosure
  • FIG 4c is a schematic diagram depicting an exemplary sequence of events when a document is originated via third-party application and subsequently shared/synchronized with SyncCLIENT as a link to Cloud or Cloud Site;
  • FIG 4d is a schematic diagram depicting exemplary mappings between
  • FIG 4e is a schematic diagram depicting an exemplary synchronization between SyncCLIENT and the Cloud according to an aspect of the present disclosure
  • FIG 4f is a schematic diagram depicting an additional exemplary synchronization between SyncCLIENT and the Cloud according to an aspect of the present disclosure
  • FIG 4g is a schematic diagram depicting an exemplary synchronization of a single file associated with multiple folders in the Cloud with a SyncCLIENT;
  • FIG 5 is a schematic block diagram depicting an exemplary architecture of a SyncCLIENT according to an aspect of the present disclosure
  • FIG 5 a is a schematic block diagram depicting an exemplary overview operation of EVENT AGGREGATOR according to an aspect of the present disclosure
  • FIG 5b is a schematic block diagram depicting an exemplary operation of EVENT AGGREGATOR according to an aspect of the present disclosure
  • FIG 5 c is a flow diagram depicting an exemplary operational overview of the EVENT AGGREGATOR according to an aspect of the present disclosure
  • FIG 6 is a schematic block diagram depicting Cloud WATCHER and Local WATCHER (Type-2) detecting changes to Cloud FileSystem and Local FileSystem respectively through the use of graphs according to an aspect of the present disclosure
  • FIG 6a is a schematic block diagram depicting Cloud WATCHER determining a current Cloud state from a Change LOG received from Cloud by SyncCLIENT according to an aspect of the present disclosure
  • FIG 7 is a schematic block diagram depicting the processing of work items by FETCHER and subsequent operations by WORKERS according to an aspect of the present disclosure
  • FIG 8 is a schematic block diagram depicting the serialization of Regular Work Items within FETCHER
  • FIG 9 is a schematic diagram depicting a representative computer system for implementing exemplary methods and systems for sharing and synchronizing
  • any block diagrams herein represent conceptual views of illustrative circuitry embodying the principles of the disclosure.
  • any flow charts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in computer readable medium and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.
  • processors may be provided through the use of dedicated hardware as well as hardware capable of executing software in association with appropriate software.
  • the functions may be provided by a single dedicated processor, by a single shared processor, or by a plurality of individual processors, some of which may be shared.
  • processor or “controller” should not be construed to refer exclusively to hardware capable of executing software, and may implicitly include, without limitation, digital signal processor (DSP) hardware, network processor, application specific integrated circuit (ASIC), field programmable gate array (FPGA), read-only memory (ROM) for storing software, random access memory (RAM), and non-volatile storage. Other hardware, conventional and/or custom, may also be included.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • ROM read-only memory
  • RAM random access memory
  • non-volatile storage Other hardware, conventional and/or custom, may also be included.
  • Software modules, or simply modules which are implied to be software may be represented herein as any combination of flowchart elements or other elements indicating performance of process steps and/or textual description. Such modules may be executed by hardware that is expressly or implicitly shown.
  • an electronically stored file is a type of abstraction. It provides a convenient way of bundling a set of data into identifiable units that in turn can be managed, stored, retrieved and operated upon by computer systems.
  • FIG 1 With initial reference to FIG 1 , there is shown a schematic diagram depicting an exemplary arrangement 100 for sharing and synchronizing electronically stored files according to an aspect of the present disclosure. Depicted in FIG 1 are a personal computer 110 and a "Cloud" 120 with which the personal computer 110 interacts via one or more known networking technologies 125.
  • a Cloud 120 is a model of networked resources such as storage, computing and applications.
  • Cloud computing generally refers to the delivery of computing as a service whereby shared resources, applications, software, data and information are provided to computers and other devices as a service over a network such as the Internet.
  • Cloud storage generally refers to electronic storage resources (for example, electronic FileSystems) provided by the Cloud 120 via a network.
  • Advantageously Cloud computing and/or Cloud storage may provide individual users only those resources needed for a particular task thereby eliminating payment for idle or unused resources.
  • users may be provided access to any latest software and infrastructure offering(s), thereby fostering compatibility and productivity.
  • Cloud computing and/or Cloud storage generally provides users with access to Cloud resources from anywhere that Internet access mechanisms are available.
  • Networking technologies 125 depicted in FIG 1 may advantageously provide Internet access to Cloud 120 either directly or via an internet service provider.
  • Representative networking technologies for Cloud access include, but are not limited to, dial-up, leased line, ISDN, optical, broadband, broadband over power lines, fiber to the home, DSL/ ADSL/SDSL, WiFi, WiMax, Cable, Satellite, Mobile Phone, and T-carrier, among others.
  • Known internetworking protocols, i.e., TCP/IP may be used in
  • FIG 1 Depicted further in FIG 1, are a number of electronic folders 112, 114, 116 that are resident in a storage system of personal computer 110.
  • electronic folders such as those depicted in FIG 1 are a type of virtual container in which groups of electronically stored files may be kept and organized.
  • a contemporary computer operating system such as that which may execute on personal computer 110, i.e., Windows, OS X, LINUX, etc., will generally include support for electronic file systems that may contain many thousands of folders.
  • Electronically stored files may be conveniently organized by storing related files in a common folder.
  • a folder contained within another folder is called a subfolder.
  • folder presents an analogy to a file folder used in offices and is used in almost all contemporary operating systems' desktop environments.
  • Folders too are a type of abstraction which provide a convenient way of bundling a set of electronically stored files into identifiable units that in turn can be managed, stored, retrieved and operated upon by computer systems. Folders are often depicted by computing systems as icons that visually resemble physical file folders.
  • personal computer 110 executes client synchronization and sharing program or set of services 115 which, for our purposes herein, we generally call "SyncCLIENT".
  • a client program executes on a particular computer and accesses one or more services made available by a complementary server program.
  • the server program is oftentimes (but not always) on another computer system in which case the client program accesses the services by way of a network.
  • SyncCLIENT 115 executes on personal computer 110 and interacts with complementary server services provided by Cloud 120 via networking technologies 125.
  • one or more folders resident on personal computer 110 are
  • folder 112 is replicated and synchronized with Cloud storage services 130 which electronically store folder 112-a in a Cloud FileSystem.
  • Cloud storage services 130 which electronically store folder 112-a in a Cloud FileSystem.
  • any additions/deletions/changes made to folder 112 on personal computer 110 executing SyncCLIENT 115 are reflected in folder 112-a in Cloud storage 130.
  • such operations result in an automatic backup of any files or folders within folder 112 on personal computer 110 to the Cloud storage 120.
  • any additions/deletions/changes made to folder 112-a, or its contents in Cloud 120 will be reflected in folder 112 or its contents in personal computer 110.
  • exemplary Cloud 120 may advantageously provide computing services in addition to Cloud storage services 130.
  • any of a number of applications i.e., word processing, spreadsheet, presentation graphics, calendaring, personal management, etc, 135 may be provided by Cloud 120 and accessed via a World Wide Web interface, for example, by computing device 150 or the personal computer 110, i.e., using - for example - a Web Browser.
  • computing device 150 may be a "scaled down" or "thin client” device (or tablet device or Smartphone, etc.) to access to Cloud computing resources.
  • thin clients generally depend on other computers (i.e., Cloud computing) to fulfill their computational role.
  • computing device 150 provides, for example, the ability to utilize Cloud computing resources 135 to edit, for example, any editable documents which are stored within cloud storage 130 and folder 112-a. Such editing may advantageously be made from any geographic location that computing device 150 may access Cloud 120 and its resources via networking technologies 127. Consequently, a user may employ the computing device 150 to create or edit or otherwise utilize Cloud computing resources 135 to modify/create folders or files contained within folder 112-a. According to an aspect of the present disclosure, changes made to the folder 112-a, or changes made to any files or folders contained therein are automatically synchronized with folder 112 on personal computer 110.
  • contemporary computer systems such as the personal computer 110 or other computing device 150 depicted in FIG 1, may employ operating systems such as WINDOWS, OS/X, LINUX, or similar systems or derivatives thereof that provide one or more user interfaces that allow a user to conveniently perform file system operations. More particularly, such user interfaces may allow a user to operate on files using familiar drag-and-drop, clipboard, and command- line operations.
  • operating systems such as WINDOWS, OS/X, LINUX, or similar systems or derivatives thereof that provide one or more user interfaces that allow a user to conveniently perform file system operations. More particularly, such user interfaces may allow a user to operate on files using familiar drag-and-drop, clipboard, and command- line operations.
  • synchronization and sharing permits the automatic, bidirectional, generation, backup, synchronization and sharing of files and folders between a personal computers 110, 150, and a Cloud 120.
  • FIG 2 there is shown another exemplary arrangement 200 depicting electronic file sharing and synchronization according to an aspect of the present disclosure.
  • FIG 2 Depicted in FIG 2, are a number of computing systems namely, computers 210, 250, and 260 which are labeled in FIG 2 as “home”, “laptop” and “work” respectively.
  • Each of the computers 210, 250 and 260 employ known network access technologies 225, 226, and 227 such as those previously described to access Cloud 220 and in particular Cloud storage services 230 FileSystem.
  • each of the computers 210, 250 and 260 executes an instance of SyncCLIENT 215, 256, and 267.
  • one or more folders resident on home computer 210 are automatically replicated and synchronized with Cloud storage services 230 FileSystem through the effect of the executing SyncCLIENT 215.
  • folder 212 which is resident on home computer 210 is replicated and synchronized with Cloud storage services 230 FileSystem which electronically stores folder 212-a and its electronic contents.
  • laptop computer 250 and work computer 260 are depicted as executing instances of
  • each of the executing instances of SyncCLIENT 256 and 267 may replicate and synchronize folder 212a locally, on computers 250 and 260 as folders 212b, and 212c, respectively.
  • folder 212 which is resident on home computer 210 is replicated and synchronized with folder 212a electronically stored by Cloud storage services 230 FileSystem as well as folders 212b and 212c which are resident on laptop computer 250 and work computer 260, respectively.
  • sharing and synchronization of electronically stored files permits a user to make create/modify electronically stored files on one computer (i.e., files in folder 212c on work computer 260) and have those created/modified electronically stored files automatically
  • each of the computers depicted therein include a number of folders that are not replicated/synchronized/shared with the Cloud 220 or other computers. More particularly, home computer 210 is depicted as including folders 214 and 216 which are not shared and/or synchronized. Similarly, laptop computer 250 is depicted as including folders 251 and 252 which are not shared and/or synchronized. Finally, work computer 260 is depicted as including folder 261 which is not shared and/or synchronized.
  • the particular folders that are shared/synchronized through the operation of SyncCLIENT with the Cloud 220 and/or other computing devices and/or users is user administrable.
  • Cloud 220 may provide Cloud computing resources 235 in addition to any Cloud storage resources 230. Consequently, a user may also provide Cloud computing resources 235 in addition to any Cloud storage resources 230. Consequently, a user may also provide Cloud computing resources 235 in addition to any Cloud storage resources 230. Consequently, a user may also provide Cloud computing resources 235 in addition to any Cloud storage resources 230. Consequently, a user may also provide Cloud computing resources 235 in addition to any Cloud storage resources 230. Consequently, a user may also
  • client computing devices i.e., home computer 210, laptop computer 250, work computer 260, or other computing device 270, which may advantageously employ browser applications and technologies.
  • an electronically stored file may also be generated, or originated in the Cloud through the effect of Cloud computing services.
  • an electronically stored file may be converted or recognized by Cloud computing services as being operable upon by those Cloud computing services.
  • these electronically stored files may be viewed as originated or generated or created as well for our purposes herein as we shall show and describe in somewhat greater detail.
  • sharing and synchronization of electronically stored files among a number of computers used by, for example, a single person the disclosure is not so limited.
  • synchronization and sharing of electronically stored files is performed among and between a number of computers and users.
  • FIG 3 there is shown another exemplary arrangement 300 depicting electronic file sharing and synchronization according to an aspect of the present disclosure.
  • FIG 3 are a number of computing systems namely personal computers 310, 350, and 360 that are used by different individual users and labeled in FIG 3 as “User 1", “User 2", and “User 3" respectively.
  • Each of the computers depicted 310, 350 and 360 employ network access technologies 325, 326, and 327 such as those previously described to access Cloud 320 and in particular Cloud storage services 330 FileSystem.
  • each of the User computers 310, 350 and 360 executes an instance of SyncCLIENT software 315, 356, and 367.
  • one or more folders resident on any of the computers, for example computer 310 are automatically replicated and synchronized with Cloud storage services 330 FileSystem through the effect of the executing SyncCLIENT software 315.
  • folder 312 which is resident on User 1 computer 310 is replicated and synchronized with Cloud storage services 330 FileSystem which electronically stores folder 312-a.
  • each of the executing instances of SyncCLIENT software 356 and 367 may replicate and synchronize folder 312a locally, on User 2 and User 3 computers 350 and 360 as folders 312b, and 312c, respectively.
  • folder 312 which is resident on User 1 computer 310 is replicated and synchronized with folder 312a stored in Cloud storage services 330 FileSystem as well as folders 312b and 312c which are resident on User 2 computer 350 and User 3 computer 360, respectively. Accordingly, sharing and synchronization of electronically stored files according to yet another aspect of the present disclosure permits multiple users to make
  • these or additional authorized users may access any Cloud computing services via web browser, for example, to create/modify any electronically stored files contained within folder 312a stored in Cloud storage services 320 FileSystem.
  • users may belong to multiple groups that share and synchronize electronically stored files.
  • FIGs 3a - 3c depict a drag-and-drop operation and subsequent synchronization of electronically stored files according to an aspect of the present disclosure.
  • a drag-and-drop operation is an action whereby a virtual object (such as an electronically stored file) is "grabbed” by graphical user interface mechanisms (i.e. mouse or touch sensitive screen) and dragged to a different location on onto/into another virtual object (such as a folder).
  • graphical user interface mechanisms i.e. mouse or touch sensitive screen
  • FIG 3a depicts a pair of overlapping windows 390, 392 such as those common to contemporary graphical user interfaces. Shown in window 392 is iconic representation of electronically stored file 393 entitled "LIFE CYCLE OF THE ELEPHANT.”
  • window 390 includes iconic representation of a local SyncDRIVE folder 391.
  • electronically stored files placed into the local SyncDRIVE folder 391 will be automatically replicated and synchronized with the Cloud (not specifically shown) and optionally other SyncDRIVE clients (not specifically shown).
  • a basic drag-and-drop sequence is accomplished by: moving a pointer to the electronically stored file 393, "grabbing" the file 393 by pressing a mouse button or other selection mechanism, "dragging" the file 393 to the SyncDRIVE folder 391, and “dropping" the file 393 by releasing the button or other selection mechanism.
  • an examination of the contents of the SyncDRIVE folder 391 as depicted in FIG 3b shows that copy of electronically stored file being synchronized with Cloud as indicated by changed icon 394 which in this example is indicative of the electronically stored file undergoing synchronization.
  • the icon associated with the electronically stored file 395 is updated to further reflect that the electronically stored file is synchronized.
  • the depiction of a synchronization status such as that shown may be performed by a variety of iconic or other mechanisms available in contemporary graphical user interfaces or computing systems. Examples include animated and/or audible mechanisms.
  • FIGs 3a- 3 c depict the synchronization status associated with an exemplary SyncCLIENT and Cloud
  • this disclosure is not so limited and further enhancements may depict initial, intermediate, and subsequent downstream synchronizations as well, for example with additional SyncCLIENT(s) that are part of a group such as those previously described.
  • FIG 4a depicts a simplified functional block diagram of an exemplary SyncCLIENT 410 according to an aspect of the present disclosure.
  • SyncCLIENT 410 includes at least two functional elements namely a Cloud WATCHER 440 and a Local WATCHER 430 which result from the execution of SyncCLIENT software on a computing device.
  • the Local WATCHER 440 includes at least two functional elements namely a Cloud WATCHER 440 and a Local WATCHER 430 which result from the execution of SyncCLIENT software on a computing device.
  • the Local WATCHER 430 includes at least two functional elements namely a Cloud WATCHER 440 and a Local WATCHER 430 which result from the execution of SyncCLIENT software on a computing device.
  • the Local WATCHER 440 includes at least two functional elements namely a Cloud WATCHER 440 and a Local WATCHER 430 which result from the execution of SyncCLIENT software on a computing device.
  • the Local WATCHER 430 includes at least two functional elements namely a Cloud WATCHER 440 and a Local WATCHER 430 which result from the execution of SyncCLIENT software on
  • the Cloud WATCHER 440 monitors and detects any changes to a watched local FileSystem 420 while the Cloud WATCHER 440 monitors and detects any relevant changes within Cloud FileSystem 460 resident in Cloud 450. When any changes are detected in either watched Local FileSystem 420 or Cloud FileSystem 460, synchronization between the two systems results.
  • the Cloud WATCHER 440 and the Local WATCHER 430 may operate concurrently or in parallel depending upon the hardware environment in which they operate.
  • a document is originated in the cloud through the use of Cloud Computing resources, electronically stored therein through the use of Cloud Storage Services, and finally synchronized with one or more SyncCLIENT(s).
  • FIG 4b there is shown a schematic diagram depicting the exemplary origination/creation of a document within the Cloud by a user. As depicted therein, the document is originated/created via a mobile device.
  • any of a variety of known mobile devices may be suitable for interacting with Cloud Computing Services to originate a document which may be subsequently stored in the Cloud via Cloud Storage Services.
  • Familiar devices include mobile telephones, tablets and other portable computing devices.
  • this disclosure is not limited to mobile devices and such origination/creation of a document within the Cloud may employ desktop or other computing devices as well.
  • any device that supports browser functionality may suffice for interacting with the exemplary Cloud Computing Services.
  • a document is originated in the Cloud via Cloud Computing Services, it is electronically stored therein via Cloud Storage Services.
  • a document electronically stored via Cloud Storage Services will have associated with it a resourcelD which uniquely identifies the electronically stored file in the Cloud Storage.
  • the document is electronically stored in the Cloud, it is subsequently synchronized/replicated with the SyncCLIENT.
  • the electronically stored file which originated via Cloud Computing Services is not physically (electronically) replicated/copied to the SyncCLIENT(s).
  • electronically stored document files which are originated in the Cloud via Cloud Computing Services and are subsequently stored therein are subsequently synchronized with one or more SyncCLIENT(s) as LINK(s) to the electronically stored document file in the Cloud. In this manner the electronically stored document that originated in the Cloud is advantageously not physically moved to the SyncCLIENT(s).
  • a LINK to the document (file) is propagated to the SyncCLIENT(s), where it is stored in the SyncCLIENT(s) local file system as an electronically stored file that comprises a LINK to the file in the Cloud.
  • the electronically stored file that comprises the LINK to the file in the Cloud may locally exhibit a type that is indicative of its Cloud storage. More particularly, such a locally stored file may be of a type ".gdoc", or any other predetermined type designation so indicative.
  • an electronically stored file is created in the SyncCLIENT file system (in the watched file system) that may advantageously appear to a user as a regular document, or text or other file as appropriate.
  • the local electronic file contains a LINK to the Cloud file.
  • such a LINK may identify the resource (document), a means for locating the resource and any particular access mechanism(s).
  • the LINK may include components indicative of a Uniform Resource Locator (URL), protocol(s), i.e., HTTPS, Services (DOCS), resourcelD, and TYPE.
  • URL Uniform Resource Locator
  • DOCS Services
  • resourcelD resourcelD
  • TYPE TYPE
  • additional components may be included in the LINK as necessary.
  • an invocation of a web browser may advantageously provide access to the file electronically stored in the Cloud to a user of a SyncCLIENT - whether mobile or stationary and advantageously not consume bandwidth unnecessarily.
  • FIG 4a and FIG 4b While we have described the operations depicted in FIG 4a and FIG 4b as pertaining to those electronically stored files that originate in the Cloud, we note once again that the teachings of the present disclosure are not so limited. More particularly, the present disclosure may likewise pertain to those electronically stored files that originate on a SyncCLIENT and are subsequently synchronized/replicated to the Cloud as previously described.
  • a user may originate an electronically stored file on a
  • the electronically stored file may be converted and/or modified (if necessary) to a format that may be conveniently operated on by one or more of the Cloud Computing Resource(s) and/or Cloud applications. Thereafter, that converted, electronically stored file may be synchronized with one or more SyncCLIENT(s) as a LINK to the electronically stored file in the Cloud.
  • SyncCLIENT a LINK to the electronically stored file in the Cloud.
  • files exhibiting such formats are electronically stored in the Cloud, they may be advantageously synchronized with SyncCLIENTs via the LINK mechanism(s) described previously and subsequently accessed from the SyncCLIENTs as if they originated in the Cloud.
  • a document or other object need not be generated via cloud computing services according to an aspect of the present disclosure. More particularly, and with reference now to FIG 4c, there is shown a schematic sequence of events whereby a document is originated via a third-party application, stored in the Cloud via Cloud
  • the SyncCLIENT recognizes that the document object in the CLOUD need not be copied to the SyncCLIENT and instead a LINK is generated to that object and stored locally as a file in the local file system of the
  • the document object may be accessed from the SyncCLIENT (or other computing devices to which the document has been synchronized) via a web browser - for example.
  • additional / alternative cloud sites may be referenced in the LINK such that the document or other resources may be accessed via that referenced cloud site as well.
  • folders and files in the Cloud and folders and files in a local file system may exhibit somewhat different characteristics.
  • FIG 4d there is shown an exemplary Cloud file system and an exemplary SyncCLIENT file system including a number of folders and files which will be used to describe some of these characteristics.
  • the exemplary Cloud file system depicted in FIG 4d exhibits a "down-up" structure rather than a "top-down” structure of the client file system that those skilled in the art will readily recognize. More specifically, this "down-up" structure exhibited by the Cloud file system results in multiple folders belonging to a single file. As depicted in FIG 4d, it may be observed that a single file, File A, as belonging to (or contained within) folder BAZ, that in turn belongs to both folders FOO and BAR. Accordingly, files electronically stored in the Cloud may have multiple parent folders which in turn may have multiple parent folders. In this regard, folders are analogous to labels that are applied to files. Furthermore, as used in the Cloud, names of folders and/or files are generally not unique.
  • files and folders in the Cloud have unique identifiers, resource IDs (resourcelD) which uniquely identify the file or folder to which it is associated.
  • resource IDs resource IDs
  • a local name of a file and/or folder may be different from its name in the Cloud since there may be conflicts with other files/folders having the same name in the local file system. Such conflicts may occur both among children and among parents.
  • a mapping is made between a folder resourcelD and its name (in the Cloud) and its local name as electronically stored on the SyncCLIENT.
  • FIG 4d An exemplary mapping between Cloud folders/file and local folders/file is depicted in FIG 4d.
  • such mapping may be made through a FileMapping object which includes one or more LocalEntry objects and a CloudEntry object.
  • local folder FOO is mapped to Cloud folder FOO
  • local folder BAR is mapped to Cloud folder BAR
  • two local folders BAZ are mapped to single Cloud folder BAZ
  • both FILE A files are mapped to single Cloud file, FILE A.
  • FIG 4e depicts an additional example of differences between files/folders as they are stored in the Cloud storage system and how those differences affect
  • FIG 4e there is depicted in a Cloud file system a folder named FOO, having two child folders both named BAR. Consequently, and according to an aspect of the present disclosure, when duplicate folders BAR are replicated/synchronized on the local file system they are uniquely named using the creation date of the Cloud resource.
  • one folder is named BAR in the local file system while the other is named BAR [XX/XX/XX] where XX XX XX is the date on which the Cloud resource of that folder was created.
  • FIG 4f depicts an additional example of differences between files/folders as they are stored in the Cloud storage system and how those differences affect
  • FIG 4f there is again depicted in a Cloud file system a folder named FOO, having two child folders both named BAR. Consequently, and according to an aspect of the present disclosure, when duplicate folders BAR are replicated/synchronized on the local file system they are uniquely named using - in this example - an incremental counter. As depicted in this example in FIG 4f, one folder is named BAR[n] in the local file system while the other is named BAR [n+1]. Those skilled in the art will appreciate that a combination of this incremental counter method along with the creation date of the Cloud object described in the preceding paragraphs are contemplated by this disclosure.
  • FIG 4g there is shown a schematic diagram depicting the synchronization of a single particular file, File A, that is electronically stored in the Cloud file system and is associated with (contained in) three separate folders namely, FOO, BAR, and BAZ.
  • File A that is electronically stored in the Cloud file system and is associated with (contained in) three separate folders namely, FOO, BAR, and BAZ.
  • this File A is synchronized/replicated with a SyncCLIENT and electronically stored in a local file system on that client
  • three individual folders namely, FOO, BAR, and BAZ are created on the SyncCLIENT file system wherein each contain a separate copy of that replicated File A.
  • subsequent synchronization with the Cloud takes place with the corresponding single File A that is resident in the Cloud file system.
  • FIG 5 there is shown a schematic block diagram 500 of a SyncCLIENT 510 that may illustratively perform the operations described previously with respect to FIGs 1 - 4.
  • an illustrative SyncCLIENT includes Cloud WATCHER 540, Local WATCHER (i.e., Type-2 WATCHER 530 or Type-1 WATCHER 535), EVENT AGGREGATOR 561, FETCHER 580, WORKER(s) 590, SNAPSHOT 560, and BLACKLIST 570.
  • Cloud WATCHER 540 monitors and detects any relevant changes to Cloud FileSystem 520 while Local WATCHER (530 or 535) monitors and detects any changes to watched Local FileSystem 515. With respect to the Cloud WATCHER 540, if any relevant changes to Cloud FileSystem 520 are detected,
  • FSChange notification(s) of those detected change(s) are sent to FETCHER 580.
  • FETCHER 580 With respect to the Local WATCHER (530 or 535), if any Local FileSystem changes are detected, notification is sent to EVENT AGGREGATOR 561.
  • the EVENT AGGREGATOR 561 receives change notifications from the Local WATCHER (Type-1) 535 or from the Local WATCHER (Type-2) 530 as appropriate.
  • the Local WATCHER (Type-1) 535 provides raw event file-level change notifications to the EVENT AGGREGATOR 561 while the Local WATCHER (Type-2) provides FSChange notifications to the EVENT AGGREGATOR 561.
  • the EVENT AGGREGATOR 561 generally will receive change notifications from the Local WATCHER and "hold” onto those notifications for some period of time. If during the hold period multiple changes are made to any related item(s) the EVENT AGGREGATOR 561 will advantageously combine or otherwise modify those changes into higher-level, more coherent events which are then sent by the EVENT AGGREGATOR 561 to the FETCHER 580.
  • the BLACKLIST 570 is a structure that lists those changes which have been previously sent to WORKERS 590 but were not completed for one reason or another. Accordingly, BLACKLIST 570 serves as a list of changes that are not to be performed so long as those changes remain on the BLACKLIST 570. Conversely, changes received by the FETCHER 580 that are not included in the BLACKLIST 570 are sent by the FETCHER 550 to the WORKER(s) 590 as work items for subsequent processing.
  • work items are generally those operations that are performed by the WORKERS to effect FSChanges. More particularly, a particular work item will generally identify an object to which it applies (i.e., a filename), a direction (i.e., download/upload), and an operation such as create, rename, delete, move and modify.
  • object to which it applies i.e., a filename
  • direction i.e., download/upload
  • an operation such as create, rename, delete, move and modify.
  • the SNAPSHOT 560 is locked when any
  • FETCHER 550 generally serializes the flow of work items before subsequent parallel processing by WORKERS 590.
  • FETCHER acts as a manager/lock that ensures that no two workers operate on conflicting and/or overlapping changes.
  • exemplary SyncCLIENT 510 software may execute.
  • operating systems include, but not limited to, Microsoft WINDOWS, OS/X, and LINUX.
  • WORKER(s) 590 may be implemented as multiple threads. Consequently, multiple WORKERS may operate simultaneously on multiple-processor or multiple-core computing systems or operate concurrently on uniprocessor computing systems. As a result, multiple WORKERS may be operating on a given work item concurrently with one another thereby enhancing the performance of sharing and synching operations.
  • UNIX derivatives such as OS/X and LINUX provide folder level change notifications while Microsoft WINDOWS provides a more detailed, file level change notification. More specifically, OS/X provides information about changes made to folders, while Microsoft WINDOWS provides information about changes made to individual folders. Consequently at least two different Local WATCHER(s) are depicted in FIG 5, namely Local WATCHER (Type-2) 530 and Local WATCHER (Type-1) 531. As further depicted in FIG 5, Local WATCHER (Type-2) provides Folder-Level Change Notifications 531 while Local WATCHER (Type-1) 535 provides File-Level Change Notifications 536.
  • Microsoft WINDOWS provides a ReadDirectoryChangesW Application Programming Interface (API) that provides notice of, for example,
  • CHANGE FILE NAME Any file name change in the watched folder (directory) or subtree;
  • CHANGE DIR NAME Any directory-name change in the watched directory or subtree;
  • CHANGE ATTRIBUTES Any attribute change in the watched directory;
  • CHANGE SIZE Any file-size change in the watched directory or subtree when file is written;
  • CHANGE LAST ACCESS Any change to the last access time of file(s) in the watched directory or subtree;
  • CHANGE CREATION Any change to the creation time of files in the watched directory or subtree;
  • CHANGE SECURITY Any security- descriptor change in the watched directory or subtree; to SyncCLIENT software accessing that API. Since OS X does not provide this File -Level change notification, a local graph
  • FIG 532 is used by Local WATCHER (Type-2) 530 to track the state of the watched local FileSystem 515.
  • the Cloud WATCHER 540 uses a cloud graph 541 to track the state of the watched Cloud Filesystem 520.
  • FIG 5 depicts both a Local WATCHER (Type-2) 530 and Local WATCHER (Type-1) 535 as component parts of SyncCLIENT 510, a particular instantiation of a SyncCLIENT advantageously does not require both.
  • FIG 5 a there is shown a schematic block diagram depicting a sequence of events associated with the saving of an electronically stored file, "N", and the operation of the Local WATCHER 535 and the EVENT AGGREGATOR 561.
  • N an electronically stored file
  • the Local WATCHER 535 and the EVENT AGGREGATOR 561 As those skilled in the art will recognize, such a sequence may accompany the operation of any of a number of popular application programs or suites of programs.
  • N the general sequence of events associated with these popular application programs or suites of programs, while saving an electronically stored file
  • the watched local file system 515 will exhibit the above sequence of events which will be detected by the Local
  • an exemplary SyncCLIENT includes an EVENT AGGREGATOR 561.
  • the EVENT AGGREGATOR 561 generally will receive change notifications from the Local WATCHER and "hold” onto those notifications for some period of time. If during the hold period multiple changes are made to any related item(s) the EVENT AGGREGATOR 561 will advantageously combine or otherwise modify those changes into higher-level, more coherent events which are then sent by the EVENT AGGREGATOR 561 to the FETCHER.
  • the EVENT AGGREGATOR 561 is depicted as receiving the above sequence of events namely, 1) Create Temp File N+1; 2) Delete File N; and 3) Move Temp File N+1 to N. As depicted in FIG 5a, the EVENT
  • AGGREGATOR 561 holds and aggregates/combines that sequence into a single work item namely:
  • FIG 5b is a schematic diagram depicting an overview of EVENT
  • a received Change Event Prior to their insertion into the Change Event Queue, a received Change Event is checked to see whether or not it may be combined with a Change Event already in the Change Event Queue. If so, the received Change Event is combined with the Change Event in the Change Event Queue and the combined Change Event is reinserted into the Change Event Queue. If the received Change Event cannot be combined with a Change Event already in the Change Event Queue, then the received Change Event is inserted into the Change Event Queue, uncombined. Periodically, the Change Event Queue is examined and any Change Event that has been in the Change Event Queue for a predetermined period of time is dispatched to the FETCHER (not specifically shown) for processing.
  • FIG 5 c is a flow diagram depicting a general operational overview of the EVENT AGGREGATOR 561 according to an aspect of the present disclosure.
  • the EVENT AGGREGATOR 561 receives a change event from a Local WATCHER.
  • the EVENT AGGREGATOR will examine the received change event to determine whether it is combinable with another received change event already inserted into a Change Event Queue. If the received change event is combinable with a change event already in the Change Event Queue, it is combined with the queued change event at block 564 and the combined change event is enqueued in the Change Event Queue at block 565.
  • the received change event is not combinable with a queued change event at block 564, then the received change event is enqueued into the Change Event Queue at block 565, uncombined.
  • the Change Event Queue is examined to determine whether any queued change events have been in the Change Event Queue for a period of time greater than some predetermined period. If so, then that change event is dequeued and sent to the fetcher for processing at block 567.
  • the EVENT AGGREGATOR 561 may combine received events with events already in the Event Queue based on known/learned patterns that are recognizable. More particularly, the EVENT AGGREGATOR may recognize particular event combinations from known patterns of received change sequences, observed file types, detected executable programs, executing processes etc., and from these data determine the particular changes being observed and use this information to make combinations.
  • FIG 6 there is shown a schematic block diagram depicting the operation of a Cloud WATCHER 640 and Local WATCHER (Type-2) 630 on a representative SyncCLIENT 610 according to an aspect of the present disclosure.
  • Cloud WATCHER 640 generates a Cloud Graph 642 which is indicative of the current state of the watched Cloud FileSystem 680.
  • the Cloud WATCHER 640 periodically generates a Current Cloud State representation 644 and then determines any differences between the two.
  • the Cloud WATCHER 640 Upon detecting a difference between the Cloud Graph 642 and the Current Cloud State representation 644, the Cloud WATCHER 640 generates an FSChange (File System Change Notification) and sends that FSChange to the FETCHER (not specifically shown). As previously noted with respect to the discussion of FIG 5, the FSChange notifications are used by the FETCHER to generate Work Items to be sent to WORKERS (not specifically shown).
  • the Current Cloud State representation 644 may be represented by an ordered list of changes made to objects within Cloud FileSystem as reported to the SyncCLlENT.
  • the Cloud Graph 642 may be preferably represented as a dictionary structure that includes a ResourcelD key wherein dictionary entries include - in addition to the ResourcelD - any filename(s), checksum(s), and timestamp(s).
  • Local WATCHER (Type-2) 630 monitors Watched Local FileSystem 615 via - for example - and FSEvents API which provides folder-level change notifications. Upon receipt of any folder-level change notifications, Local WATCHER (Type-2) 630 generates a Current Local State representation 634 which is indicative of the current state of the Watched Local FileSystem 615. The Local WATCHER (Type-2) 630 compares the Current Local State representation 634 with a previously generated, Local Graph 632 and determines any differences between the two. Upon detecting a difference between the Current Local State representation 634 and the Local Graph 632, the Local WATCHER 630 generates an FSChange and sends that FSChange to the EVENT AGGREGATOR (not specifically shown).
  • the EVENT AGGREGATOR holds onto changes for a period of time and if multiple changes to related items or particular known patterns are detected, then the EVENT AGGREGATOR may combine or otherwise modify those received FSChange events into higher level, coherent events which are then sent to the FETCHER as Work Items to be performed.
  • FIG 6a is a schematic block diagram depicting the receipt and update of the current cloud state 644.
  • the current cloud state 644 may be determined from a Change LOG 646 which is received by the SyncCLlENT 610 from the Cloud.
  • a Change LOG 646 such as that depicted in FIG 6a includes an ordered list of changes made to the Cloud File System 680 that is relevant to the particular SyncCLlENT 610 and/or a particular account.
  • the ordered list of changes made to the Cloud File System 680 included in the Change LOG 646 is already aggregated upon receipt by the SyncCLlENT 610. Consequently, the ordered list of changes received from the Cloud File System via the Change LOG 646 does not require further aggregation as do the changes observed by the Local WATCHERs described previously.
  • the Change LOG 646 includes, for a particular account, a number of entries including an indication of the current state of an item; whether an item has been moved to trash; and whether an item has been deleted from the trash.
  • this exemplary listing of entries included in the Change LOG is meant to be representative, and not exhaustive. Consequently, additional entries indicative of an item's status may be provided via the Change LOG.
  • these entries in the Change LOG may be used by the Cloud WATCHER to generate FSChange events that will be forwarded to the FETCHER.
  • FIG 7 there is shown a schematic block diagram depicting the generation of Work Items and subsequent processing of those Work Items by
  • SyncCLIENT 710 is representative SyncCLIENT 710 according to an aspect of the present disclosure.
  • one or more FSChange events are sent from Cloud WATCHER 740 or EVENT AGGREGATOR 735 to the FETCHER 720 as Work Items where they are placed into an ordered Work Queue 726.
  • FETCHER 720 arranges the received Work Items 725 such that they are performed in a prescribed order. More specifically, Work Items 725[1] ... 725 [n] are entered into a Work Queue 726 ordered from Oldest to Newest. In this regard, the FETCHER 720, through the effect of the Work Queue 726, serializes the Work Items 725 [1] ... 725 [n] before distributing those Work Items to Workers 750[1] ... 750[n] for concurrent processing.
  • FIG 8 there is shown a schematic block diagram 800 depicting the serialization of Work Items 825 [ 1 ] ... 825 [n] by FETCHER 820.
  • incoming Work Items 825[1] ... 825 [n] are arranged in a Work Queue 826 in Oldest to Newest order.
  • FETCHER 820 examines each of the Work Items in Work Queue
  • the FETCHER 820 sequentially examines Work Items 825[1] ... 825 [n] in the Work Queue 826, starting at the oldest and proceeding to the newest, to determine what dependencies - if any - are exhibited by the particular Work Item under examination. If an examined Work Item 825 [1] ... 825 [n] in the Work Queue 826 is affected by any entries in the Dependency Map 890, then it is determined to be unprocessable at that time.
  • the Dependency Map 890 includes a list of structures that may be affected by operations being performed by any of the plurality of workers 850[1] ... 850[n] at a given time.
  • Dependency Map 890 entries of particular significance depicted in FIG 8 are: inodes 891, resource ID(s) 892, and Filenames, etc., 893.
  • Additional dependencies not specifically shown in FIG 8 include Filenames of parents, children and cousin objects.
  • an inode is a data structure used by contemporary operating systems to store information about a file(s), directory(ies), or other file system object(s).
  • Inodes store information about files and directories (folders) such as ownership, mode, and type.
  • Files are associated with a particular inode, which is identified by an integer number (inode number).
  • a resourcelD is an identifier that uniquely identifies Cloud objects, for example, files. Accordingly, such a resourcelD would uniquely identify a particular file stored within the Cloud filesystem.
  • filenames are generally metadata about a file. Frequently filenames are strings used to identify (preferably - uniquely) the file electronically stored in a filesystem. Oftentimes, filenames include additional components namely a path associated with the file, a name associated with the file, a type associated with the file, and a version associated with the file.
  • FETCHER 820 maintains the Dependancy Map 890 which identifies dependencies that are currently impacted by Work Items being acted on by any of the Workers 850[1] ... 850[n]. Accordingly, as the FETCHER 820 examines Work Items 825[1] ... 825[n] in the Work Queue 826 it compares dependencies affected by the Work Item being examined with any dependencies in the Dependency Map 890. If any such dependencies affected by the examined Work Item are in Dependency Map 890, then that Work Item is skipped and the FETCHER 820 examines the next Work Item in the Work Queue 826.
  • the ordering of Work Items 825[1] ... 825 [n] is preferably maintained even if a particular Work Item is skipped. Accordingly, the Work Queue 826 within FETCHER 820 will always be in Oldest to Newest Order. If a particular Work Item is determined to be processable, that is to say its affected dependencies are not in the Dependency Map 890, then that Work Item is passed on to a WORKER 850[1] ... 850[n] for processing.
  • FETCHER 820 Whenever a WORKER finishes with a particular Work Item, FETCHER 820 reexamines the Work Queue 820 starting from the Oldest Work Item 825[1] in the Work Queue 820, scanning to the Newest Work Item 825 [n] in the Work Queue 826. As those skilled in the art will readily appreciate, Work Items in Work Queue 826 that were previously skipped (due to dependency conflict for example) will be rescanned and processed if such a determination is made by FETCHER 820. Of further advantage, since FETCHER 820 ensures that no two Work Items sent to WORKERS have dependency conflicts, there is no need for locks and a high degree of concurrency and/or parallelism is achieved in the WORKER operations.
  • FIG 9 shows an illustrative computer system 900 suitable for implementing methods and systems according to an aspect of the present disclosure.
  • the computer system may comprise, for example a computer running any of a number of operating systems.
  • the above-described methods of the present disclosure may be implemented on the computer system 900 as stored program control instructions.
  • Computer system 900 includes processor 910, memory 920, storage device 930, and input/output structure 940.
  • One or more input/output devices may include a display 945.
  • One or more busses 950 typically interconnect the components, 910, 920, 930, and 940.
  • Processor 910 may be a single or multi core.
  • Processor 910 executes instructions in which embodiments of the present disclosure may comprise steps described in one or more of the Figures. Such instructions are described in one or more of the Figures.
  • Memory 920 may store data and may be a computer-readable medium, such as volatile or non- volatile memory.
  • Storage device 930 may provide storage for system 900 including for example, the previously described methods. In various aspects, storage device 930 may be a flash memory device, a disk drive, an optical disk device, or a tape device employing magnetic, optical, or other recording technologies.
  • Input/output structures 940 may provide input/output operations for system 900.
  • Input/output devices utilizing these structures may include, for example, keyboards, displays 945, pointing devices, and microphones - among others.
  • computer system 900 for use with the present disclosure may be implemented in a desktop computer package 960, a laptop computer 970, a hand-held computer, for example a tablet computer, personal digital assistant or Smartphone 980, or one or more server computers which may advantageously comprise a "cloud" computer 990.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Software Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

La présente invention, selon certains aspects, concerne des architectures, des procédés et des systèmes ainsi que des structures qui facilitent le partage et la synchronisation de fichiers mémorisés électroniquement parmi et entre des entités de nuage et un certain nombre d'ordinateurs, de systèmes, de dispositifs et/ou d'utilisateurs. Un aspect particulier d'architecture fourni à titre d'exemple fait appel à la détermination concurrente de changements de système de fichiers à l'intérieur d'un système de fichiers en nuage et d'un système de fichiers clients, à l'ordonnancement sériel d'opérations de système de fichiers nécessaires en réponse aux changements de système de fichiers déterminés, et à l'exécution concurrente d'opérations de système de fichiers de sorte que le système de fichiers en nuage et le système de fichiers informatiques clients sont synchronisés.
PCT/US2013/034983 2012-04-23 2013-04-02 Partage et synchronisation de fichiers mémorisés électroniquement WO2013162837A1 (fr)

Priority Applications (5)

Application Number Priority Date Filing Date Title
CN201810489389.9A CN108717454B (zh) 2012-04-23 2013-04-02 共享和同步电子保存的文件
EP13782583.2A EP2842050A4 (fr) 2012-04-23 2013-04-02 Partage et synchronisation de fichiers mémorisés électroniquement
CN201810489494.2A CN108710533B (zh) 2012-04-23 2013-04-02 共享和同步电子保存的文件
CN201810490633.3A CN108804213B (zh) 2012-04-23 2013-04-02 共享和同步电子保存的文件
CN201380029205.6A CN104685485B (zh) 2012-04-23 2013-04-02 共享和同步电子保存的文件

Applications Claiming Priority (10)

Application Number Priority Date Filing Date Title
US13/453,799 2012-04-23
US13/453,748 2012-04-23
US13/453,678 2012-04-23
US13/453,909 US9529818B2 (en) 2012-04-23 2012-04-23 Sharing and synchronizing electronically stored files
US13/453,860 US20130282830A1 (en) 2012-04-23 2012-04-23 Sharing and synchronizing electronically stored files
US13/453,860 2012-04-23
US13/453,748 US9244934B2 (en) 2012-04-23 2012-04-23 Sharing and synchronizing electronically stored files
US13/453,909 2012-04-23
US13/453,678 US9239846B2 (en) 2012-04-23 2012-04-23 Sharing and synchronizing electronically stored files
US13/453,799 US8949179B2 (en) 2012-04-23 2012-04-23 Sharing and synchronizing electronically stored files

Publications (1)

Publication Number Publication Date
WO2013162837A1 true WO2013162837A1 (fr) 2013-10-31

Family

ID=49483749

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2013/034983 WO2013162837A1 (fr) 2012-04-23 2013-04-02 Partage et synchronisation de fichiers mémorisés électroniquement

Country Status (3)

Country Link
EP (1) EP2842050A4 (fr)
CN (1) CN104685485B (fr)
WO (1) WO2013162837A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10762054B2 (en) 2016-07-22 2020-09-01 Microsoft Technology Licensing, Llc Cloud content states determination logic

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10599526B2 (en) * 2016-01-13 2020-03-24 Microsoft Technology Licensing, Llc Auto-save operation for collaborative editing of electronic documents
US10769113B2 (en) * 2016-03-25 2020-09-08 Microsoft Technology Licensing, Llc Attribute-based dependency identification for operation ordering
JP6869122B2 (ja) * 2017-06-20 2021-05-12 シャープ株式会社 コンテンツ連携システム、コンテンツ受信装置及びコンテンツ連携方法
CN109597537B (zh) * 2017-09-30 2022-04-15 腾讯科技（深圳）有限公司 文件同步方法、装置及设备
US10866963B2 (en) * 2017-12-28 2020-12-15 Dropbox, Inc. File system authentication
CN111596933A (zh) * 2020-07-09 2020-08-28 腾讯科技（深圳）有限公司 文件处理方法、装置、电子设备及计算机可读存储介质
CN111880737A (zh) * 2020-07-28 2020-11-03 苏州浪潮智能科技有限公司 一种数据读写方法、装置、设备及计算机可读存储介质
CN117149727A (zh) * 2023-09-18 2023-12-01 上海鸿翼软件技术股份有限公司 一种文件处理方法、装置、设备以及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100161759A1 (en) * 2008-12-22 2010-06-24 Ctera Networks Ltd. Storage device and method thereof for integrating network attached storage with cloud storage services
US20110078243A1 (en) * 2009-09-30 2011-03-31 Boopsie, Inc. Leveraging Collaborative Cloud Services to Build and Share Apps
US20110231386A1 (en) * 2010-03-19 2011-09-22 Microsoft Corporation Indexing and searching employing virtual documents
US20120005193A1 (en) * 2010-03-19 2012-01-05 Hitachi, Ltd. File-sharing system and method for processing files, and program
US20120005256A1 (en) * 2010-06-30 2012-01-05 Deskstream, Inc. Method and system of operating system independence

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090300169A1 (en) * 2008-06-03 2009-12-03 Microsoft Corporation Synchronization throttling based on user activity
US8219524B2 (en) * 2008-06-24 2012-07-10 Commvault Systems, Inc. Application-aware and remote single instance data management
CN102377827A (zh) * 2011-12-13 2012-03-14 方正国际软件有限公司 多级云存储系统及其存储方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100161759A1 (en) * 2008-12-22 2010-06-24 Ctera Networks Ltd. Storage device and method thereof for integrating network attached storage with cloud storage services
US20110078243A1 (en) * 2009-09-30 2011-03-31 Boopsie, Inc. Leveraging Collaborative Cloud Services to Build and Share Apps
US20110231386A1 (en) * 2010-03-19 2011-09-22 Microsoft Corporation Indexing and searching employing virtual documents
US20120005193A1 (en) * 2010-03-19 2012-01-05 Hitachi, Ltd. File-sharing system and method for processing files, and program
US20120005256A1 (en) * 2010-06-30 2012-01-05 Deskstream, Inc. Method and system of operating system independence

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2842050A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10762054B2 (en) 2016-07-22 2020-09-01 Microsoft Technology Licensing, Llc Cloud content states determination logic

Also Published As

Publication number Publication date
CN104685485A (zh) 2015-06-03
CN104685485B (zh) 2018-06-15
EP2842050A4 (fr) 2016-01-13
EP2842050A1 (fr) 2015-03-04

Similar Documents

Publication Publication Date Title
US20210081371A1 (en) Sharing and synchronizing electronically stored files
US9239846B2 (en) Sharing and synchronizing electronically stored files
US9244934B2 (en) Sharing and synchronizing electronically stored files
US9529818B2 (en) Sharing and synchronizing electronically stored files
US20130282830A1 (en) Sharing and synchronizing electronically stored files
WO2013162837A1 (fr) Partage et synchronisation de fichiers mémorisés électroniquement
KR102459800B1 (ko) 클라이언트 동기화 서비스에 대한 로컬 트리의 업데이트
US10848557B2 (en) Server-side selective synchronization
US10678649B2 (en) Interfacing with a virtual database system
US20170249330A1 (en) Identification of moved or renamed files in file synchronization
US11816128B2 (en) Managing content across discrete systems
US10747643B2 (en) System for debugging a client synchronization service
CN108804213B (zh) 共享和同步电子保存的文件
US9449004B2 (en) File repository abstraction layer
CA3083530C (fr) Mise a jour d'un arbre local pour un service de synchronisation de client
Leite Smart Briefcases Sincronizaçao de Ficheiros Replicados

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13782583

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2013782583

Country of ref document: EP