US10248803B2 - Internal folder sharing - Google Patents
Internal folder sharing Download PDFInfo
- Publication number
- US10248803B2 US10248803B2 US14/271,846 US201414271846A US10248803B2 US 10248803 B2 US10248803 B2 US 10248803B2 US 201414271846 A US201414271846 A US 201414271846A US 10248803 B2 US10248803 B2 US 10248803B2
- Authority
- US
- United States
- Prior art keywords
- folder
- grantee
- parent
- virtual
- share
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active, expires
Links
Images
Classifications
-
- 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/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
- G06F16/164—File meta data generation
- G06F16/166—File name conversion
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
-
- 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/1824—Distributed file systems implemented using Network-attached Storage [NAS] architecture
- G06F16/183—Provision of network file services by network file servers, e.g. by using NFS, CIFS
-
- G06F17/30123—
-
- G06F17/30174—
-
- G06F17/30203—
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
- G06F21/6227—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database where protection concerns the structure of data, e.g. records, types, queries
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
-
- H04L67/42—
Definitions
- This application relates generally to cloud-based file storage. More particularly, this application relates to the internal file sharing in a cloud-based file storage.
- FIG. 1 is a block diagram illustrating a system, in accordance with an example embodiment, of securely synchronizing files.
- FIG. 2 is a block diagram illustrating a client device, in accordance with an example embodiment, that may form part of the system of FIG. 1 .
- FIG. 3 is a block diagram illustrating another client device, in accordance with an example embodiment, that may form part of the system of FIG. 1 .
- FIG. 4 is a block diagram illustrating a backend, in accordance with an example embodiment, that may form part of the system of FIG. 1 .
- FIG. 5 is a diagram illustrating sub-folder sharing in accordance with an example embodiment.
- FIG. 6 is a flow diagram illustrating a method, in accordance with an example embodiment, for sharing a folder in a file system between an owner and a grantee.
- FIG. 7 is a block diagram illustrating a mobile device, in accordance with an example embodiment.
- FIG. 8 is a block diagram of machine in the example form of a computer system within which instructions, for causing the machine to perform any one or more of the methodologies discussed herein, can be executed.
- various techniques are utilized in order to allow for efficient, accurate, and secure synchronization of files across multiple devices even in cases where a large number of events are occurring concurrently. This may include using an events-based technique to improve reliability during periods of file modifications being performed concurrently.
- name conflicts between different files may be resolved automatically.
- FIG. 1 is a block diagram illustrating a system 100 , in accordance with an example embodiment, of securely synchronizing files.
- files may be synchronized between one or more servers 102 and one or more client devices 104 A- 104 D.
- the client devices 104 A- 104 D may include various types of devices running various types of platforms with various types of operating systems and applications.
- client device 104 A may be a mobile device running proprietary mobile applications 106 .
- Client device 104 B may be a personal computer running a MacintoshTM operating system from Apple Inc. of Cupertino, Calif. This may include a file system known as Finder 108 , which may include a specialized plug-in 110 to allow Finder 108 to be altered in order to better operate with a proprietary application 112 .
- Client device 104 C may be a personal computer running a WindowsTM operating system from Microsoft Corp. of Redmond, Wash. This may include a file system known as Windows Explorer 114 , which may include a specialized plug-in 116 to allow Windows Explorer 114 to be altered in order to better operate with a proprietary application 118 . Additionally, applications such as Microsoft OfficeTM 120 and Microsoft OutlookTM 122 may also include their own specialized plug-ins 124 , 126 , respectively, which allow them to better operate with the proprietary application 118 . Client device 104 D may be a web-based device that may operate a web browser 128 instead of a traditional operating system.
- Each of the client devices 104 A- 104 D may communicate with a back-end 130 hosted by the one or more servers 102 . This communication may either take place directly between the back-end 130 and the proprietary applications 106 , 112 , 118 , or indirectly through a web application 132 .
- a provisioning service such as HostPilotTM 134 may also be present, and may coordinate with a directory service such as Active Directories 136 .
- FIG. 2 is a block diagram illustrating a client device, in accordance with an example embodiment, in more detail.
- the client device in this figure corresponds to client device 104 C of FIG. 1 , although in some example embodiments this diagram corresponds to a different client device.
- the various components in FIG. 2 are labeled as those components are labeled in FIG. 1 . In some embodiments, however, the components may not be identical.
- Proprietary application 116 may be a desktop application, and may store files in a local database 200 .
- the proprietary application 118 may also communicate with specialized plug-ins 116 , 124 , 126 in Windows Explorer 114 , Microsoft Office 120 and Microsoft OutlookTM 122 , respectively. This communication may take place, for example, using Thrift over TCP.
- the proprietary application 118 may communicate with a storage service 202 on the server 102 .
- FIG. 3 is a block diagram illustrating another client device, in accordance with an example embodiment, in more detail.
- the client device in this figure corresponds to client device 104 B of FIG. 1 , although in some example embodiments this diagram corresponds to a different client device.
- the various components in FIG. 3 are labeled as those components are labeled in FIG. 1 . In some embodiments, however, the components may not be identical.
- Proprietary application 112 may be a desktop application, and may store files in a local database 300 .
- the proprietary application 112 may also communicate with a specialized plugin 108 in Finder 110 . This communication may take place, for example, using Thrift over TCP.
- the proprietary application 118 may communicate with a storage device 302 on the server 102 .
- FIG. 4 is a block diagram illustrating a backend, in accordance with an example embodiment, in more detail.
- the backend in this figure corresponds to backend 130 of FIG. 1 , although in some example embodiments this diagram corresponds to a different backend.
- the various components in FIG. 4 are labeled as those components are labeled in FIG. 1 . In some embodiments, however, the components may not be identical.
- the backend 130 may include a front-end server 400 , which acts to perform much of the server-side storage functions described in this disclosure, as well as interfacing with the various devices. These functions will be discussed in more detail later in this document.
- the front-end server 400 may interface with client devices 104 A- 104 D through a firewall 402 .
- the front-end server 400 may also interface with a database server 404 , which may control access to a database 406 .
- the database 406 may be of many different types of formats.
- the database 406 is a relational database, such as one operated using Structured Query Language (SQL).
- SQL Structured Query Language
- Other formats of database are envisioned, however, as well, including flat-file and multidimensional databases.
- the database may store not just files and folders, but also metadata about the files and folders, including, but not limited to, information about which files and folders are shared, and with whom.
- a central server 408 performs internal tasks such as cleanup, provisioning, and other backend services.
- a key management server 410 provides access for keys created for each user. When a user is created on the central server 408 , a key may be issued by the key server 410 . These keys are also used by an encryption server 412 to encrypt and decrypt files and folders. This is accomplished through the use of the front end server 400 , which understands which organization the keys belong and submits file or folder content to the encryption server 412 for encryption. Active Directories 414 is used for integration with ExchangeTM.
- files to be synchronized between devices may be organized into folders. This allows a user to share an entire grouping of files with other users in an organization.
- the user initially sharing the folder can be referred to as the owner of the folder.
- the users with which the owner shares the folder can be referred to as grantees.
- the owner of a folder can share that folder with another user (grantee) from his/her organization using, for example, a web application.
- the grantee can receive a sharing invitation that can be either accepted or rejected using the web application.
- the desktop application can create the shared folder locally (on the device of the grantee) in specific folder (e.g. My SecuriSync ⁇ Shared Folder) and then synchronize this new local folder with the server folder.
- the owner and all the grantees could conceivably have multiple instances of the folder stored on a variety of different devices.
- an owner may have an instance of the folder on a desktop computer and a mobile phone, while one of the grantees may have an instance of the folder on a laptop computer and a tablet computer. All of these instances may be synchronized, not just for each user but among all the users having access to the folder.
- a folder can be shared by the owner at a number of different permission levels.
- the permission levels include View, Modify or Co-owner permission.
- the View permission allows viewing but not modification of the files in the folder.
- the grantee locally modifies one of the files in the folder, the local file will be overwritten with the server version.
- the modified version can be saved to a conflict file.
- the grantee locally deletes a file/folder that exists on the server, the file/folder will be restored locally. If the grantee having View permission locally creates a new file/folder, it will not be synchronized by the desktop application.
- the view permission only applies to the version of the files potentially shared with other users.
- the modified version can be shared with the user's other devices. In one example embodiment, this may be accomplished by synchronizing the conflict folder among the user's devices.
- a folder is shared with Modify or Co-owner permission
- the grantee locally modifies a file that exists on the server or creates a new file
- the local file version will be synchronized to the server (if there is no version conflict, which will be described in more detail below).
- the grantee locally creates a new folder, it will be created on the server by the desktop app. If the grantee locally deletes a file/folder that exists on the server, the file/folder will be deleted on server.
- a folder may be shared with a different user (grantee) regardless of its level in a folder hierarchy.
- the grantee may have one of a number of different permission levels (e.g., view, modify, co-owner).
- the subfolder can be shared regardless of whether or not the parent folder is shared. Permissions for folders and subfolders are each stored independently, allowing each folder or subfolder to be shared or not shared independently. If a subfolder is shared it may appear on grantee's devices as top-level folder while simultaneously appearing as a mid-level folder (subfolder) on the owner's devices.
- a parent folder is later shared with a grantee that already has permissions for a sub-folder of that parent folder, an issue may arise in that the grantee may get confused if suddenly the sub-folder disappears from a main directory and is placed in a new folder unbeknownst to the grantee.
- the new shared parent folder may appear on the user's device as a top-level folder, while the sub-folder also remains as a top-level folder, with the same permissions as it had before. Both the top-level folder and the subfolder may be synchronized with each other, despite both being stored in the same instance of the file system (e.g., on the same device).
- FIG. 5 is a diagram illustrating sub-folder sharing in accordance with an example embodiment.
- An owner 500 may wish to share various folders and subfolders 502 - 508 with a grantee 510 . This sharing may occur at various permission levels.
- the user may wish to grant viewing permission to Folder A 502 , which then means that all subfolders 504 , 506 , 508 are also shared with the grantee 510 at the view permission level. This results in the grantee 510 seeing all of the folders 502 - 508 when viewing folders in the view permission level. If the grantee 510 wishes to see only those folders that he has co-owner permissions to, however, he will only see Folder C 506 and Folder D 508 . Likewise, if the grantee 510 wishes to see only those folders that he has modify permissions to, then he will only see Folder D 508 .
- the various sharing permissions may be stored with the files/folders.
- a folder is shared with a grantee
- a virtual folder corresponding to the folder can be created on a device of the grantee. All objects within the folder can be copidd to the virtual folder to share and mapped to the existing objects.
- the shared folder may be stored at a level equal to parent folders of a file hierarchy on the device of the user.
- FIG. 6 is a flow diagram illustrating a method 600 , in accordance with an example embodiment, for sharing a folder in a file system between an owner and a grantee.
- an indication of a folder to share with a grantee may be received from the owner.
- the folder to share may be a subfolder within a parent folder.
- the parent folder in this instance, is not shared with the grantee.
- sharing permissions indicating a level of access the grantee has to the folder are stored with the folder.
- a virtual folder corresponding to the folder is created on a device of the grantee, the virtual folder mapping to all objects within the folder to share and being stored at a level equal to parent folders of a file hierarchy on the device of the grantee.
- a file version conflict may occur in the following situations:
- the local file is copied to the conflict file and then the local file is overwritten with the server version.
- the conflict file is created in the same folder as the original file and has the name ⁇ original file name>(Conflicted copy ⁇ YYYY-MM-DD>-for ⁇ user name>).
- ⁇ original file extension> e.g. “document(Conflicted copy 2013-04-04-for Nikita Uraltsev).docx”)
- FIG. 7 is a block diagram illustrating a mobile device 700 , according to an example embodiment.
- the mobile device 700 can include a processor 702 .
- the processor 702 can be any of a variety of different types of commercially available processors suitable for mobile devices 700 (for example, an XScale architecture microprocessor, a Microprocessor without Interlocked Pipeline Stages (MIPS) architecture processor, or another type of processor).
- a memory 704 such as a random access memory (RAM), a Flash memory, or other type of memory, is typically accessible to the processor 702 .
- the memory 704 can be adapted to store an operating system (OS) 706 , as well as application programs 708 , such as a mobile location enabled application that can provide LBSs to a user.
- OS operating system
- application programs 708 such as a mobile location enabled application that can provide LBSs to a user.
- the processor 702 can be coupled, either directly or via appropriate intermediary hardware, to a display 710 and to one or more input/output (I/O) devices 712 , such as a keypad, a touch panel sensor, a microphone, and the like.
- the processor 702 can be coupled to a transceiver 714 that interfaces with an antenna 716 .
- the transceiver 714 can be configured to both transmit and receive cellular network signals, wireless data signals, or other types of signals via the antenna 716 , depending on the nature of the mobile device 700 .
- a GPS receiver 718 can also make use of the antenna 716 to receive GPS signals.
- Modules can constitute either software modules (e.g., code embodied (1) on a non-transitory machine-readable medium or (2) in a transmission signal) or hardware-implemented modules.
- a hardware-implemented module is tangible unit capable of performing certain operations and can be configured or arranged in a certain manner.
- one or more computer systems e.g., a standalone, client or server computer system
- one or more processors can be configured by software (e.g., an application or application portion) as a hardware-implemented module that operates to perform certain operations as described herein.
- a hardware-implemented module can be implemented mechanically or electronically.
- a hardware-implemented module can comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC)) to perform certain operations.
- a hardware-implemented module can also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. It will be appreciated that the decision to implement a hardware-implemented module mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) can be driven by cost and time considerations.
- the term “hardware-implemented module” should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired) or temporarily or transitorily configured (e.g., programmed) to operate in a certain manner and/or to perform certain operations described herein.
- hardware-implemented modules are temporarily configured (e.g., programmed)
- each of the hardware-implemented modules need not be configured or instantiated at any one instance in time.
- the hardware-implemented modules comprise a general-purpose processor configured using software
- the general-purpose processor can be configured as respective different hardware-implemented modules at different times.
- Software can accordingly configure a processor, for example, to constitute a particular hardware-implemented module at one instance of time and to constitute a different hardware-implemented module at a different instance of time.
- Hardware-implemented modules can provide information to, and receive information from, other hardware-implemented modules. Accordingly, the described hardware-implemented modules can be regarded as being communicatively coupled. Where multiple such hardware-implemented modules exist contemporaneously, communications can be achieved through signal transmission (e.g., over appropriate circuits and buses) that connect the hardware-implemented modules. In embodiments in which multiple hardware-implemented modules are configured or instantiated at different times, communications between such hardware-implemented modules can be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware-implemented modules have access. For example, one hardware-implemented module can perform an operation and store the output of that operation in a memory device to which it is communicatively coupled.
- a further hardware-implemented module can then, at a later time, access the memory device to retrieve and process the stored output.
- Hardware-implemented modules can also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information).
- processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations.
- processors can constitute processor-implemented modules that operate to perform one or more operations or functions.
- the modules referred to herein can, in some example embodiments, comprise processor-implemented modules.
- the methods described herein can be at least partially processor-implemented. For example, at least some of the operations of a method can be performed by one of processors or processor-implemented modules. The performance of certain of the operations can be distributed among the one or more processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processor or processors can be located in a single location (e.g., within a home environment, an office environment or as a server farm), while in other embodiments the processors can be distributed across a number of locations.
- the one or more processors can also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations can be performed by a group of computers (as examples of machines including processors), these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., application program interfaces (APIs).)
- SaaS software as a service
- Example embodiments can be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them.
- Example embodiments can be implemented using a computer program product, e.g., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable medium for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers.
- a computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, subroutine, or other unit suitable for use in a computing environment.
- a computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
- operations can be performed by one or more programmable processors executing a computer program to perform functions by operating on input data and generating output.
- Method operations can also be performed by, and apparatus of example embodiments can be implemented as, special purpose logic circuitry, e.g., a FPGA or an ASIC.
- the computing system can include clients and servers.
- a client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
- both hardware and software architectures require consideration.
- the choice of whether to implement certain functionality in permanently configured hardware e.g., an ASIC
- temporarily configured hardware e.g., a combination of software and a programmable processor
- a combination of permanently and temporarily configured hardware can be a design choice.
- hardware e.g., machine
- software architectures that can be deployed, in various example embodiments.
- FIG. 15 is a block diagram of machine in the example form of a computer system 1500 within which instructions, for causing the machine to perform any one or more of the methodologies discussed herein, can be executed.
- the machine operates as a standalone device or can be connected (e.g., networked) to other machines.
- the machine can operate in the capacity of a server or a client machine in server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.
- the machine can be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine.
- PC personal computer
- PDA personal digital assistant
- STB set-top box
- web appliance web appliance
- network router switch or bridge
- machine any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine.
- machine shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.
- the example computer system 1500 includes a processor 1502 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both), a main memory 1504 and a static memory 1506 , which communicate with each other via a bus 1508 .
- the computer system 1500 can further include a video display unit 1510 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)).
- the computer system 1500 also includes an alpha-numeric input device 1512 (e.g., a keyboard or a touch-sensitive display screen), a user interface (UI) navigation device 1514 (e.g., a mouse), a disk drive unit 1516 , a signal generation device 1518 (e.g., a speaker), and a network interface device 1520 .
- an alpha-numeric input device 1512 e.g., a keyboard or a touch-sensitive display screen
- UI user interface
- disk drive unit 1516 e.g., a disk drive unit 1516
- signal generation device 1518 e.g., a speaker
- network interface device 1520 e.g., a network interface device
- the disk drive unit 1516 includes a machine-readable medium 1522 on which is stored one or more sets of instructions and data structures (e.g., software) 1524 embodying or utilized by any one or more of the methodologies or functions described herein.
- the instructions 1524 can also reside, completely or at least partially, within the main memory 1504 and/or within the processor 1502 during execution thereof by the computer system 1500 , with the main memory 1504 and the processor 1502 also constituting machine-readable media 1522 .
- machine-readable medium 1522 is shown in an example embodiment to be a single medium, the term “machine-readable medium” can 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 instructions or data structures 1524 .
- the term “machine-readable medium” shall also be taken to include any tangible medium that is capable of storing, encoding or carrying instructions 1524 for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present disclosure, or that is capable of storing, encoding or carrying data structures utilized by or associated with such instructions 1524 .
- the term “machine-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media.
- machine-readable media 1522 include non-volatile memory, including by way of example semiconductor memory devices, e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
- semiconductor memory devices e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and flash memory devices
- EPROM erasable programmable read-only memory
- EEPROM electrically erasable programmable read-only memory
- flash memory devices e.g., electrically erasable programmable read-only memory (EEPROM), and flash memory devices
- magnetic disks such as internal hard disks and removable disks
- magneto-optical disks e.g., magneto-optical disks
- the instructions 1524 can further be transmitted or received over a communications network 1526 using a transmission medium.
- the instructions 1524 can be transmitted using the network interface device 1520 and any one of a number of well-known transfer protocols (e.g., HTTP).
- Examples of communication networks include a local area network (LAN), a wide area network (WAN), the Internet, mobile telephone networks, plain old telephone (POTS) networks, and wireless data networks (e.g., WiFi and WiMax networks).
- POTS plain old telephone
- wireless data networks e.g., WiFi and WiMax networks.
- transmission medium shall be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions 1524 for execution by the machine, and includes digital or analog communications signals or other intangible media to facilitate communication of such software.
- inventive subject matter can be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed.
- inventive concept merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Computer Security & Cryptography (AREA)
- Data Mining & Analysis (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Human Computer Interaction (AREA)
- Computing Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
Claims (17)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/271,846 US10248803B2 (en) | 2013-05-08 | 2014-05-07 | Internal folder sharing |
US16/278,321 US20190180044A1 (en) | 2013-05-08 | 2019-02-18 | Internal folder sharing |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201361820793P | 2013-05-08 | 2013-05-08 | |
US14/271,846 US10248803B2 (en) | 2013-05-08 | 2014-05-07 | Internal folder sharing |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/278,321 Continuation US20190180044A1 (en) | 2013-05-08 | 2019-02-18 | Internal folder sharing |
Publications (2)
Publication Number | Publication Date |
---|---|
US20140337386A1 US20140337386A1 (en) | 2014-11-13 |
US10248803B2 true US10248803B2 (en) | 2019-04-02 |
Family
ID=51865582
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/271,846 Active 2037-04-06 US10248803B2 (en) | 2013-05-08 | 2014-05-07 | Internal folder sharing |
US14/271,918 Abandoned US20140372750A1 (en) | 2013-05-08 | 2014-05-07 | Client-side encryption |
US14/271,798 Abandoned US20140337290A1 (en) | 2013-05-08 | 2014-05-07 | Secure synchronization of files |
US16/278,321 Pending US20190180044A1 (en) | 2013-05-08 | 2019-02-18 | Internal folder sharing |
Family Applications After (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/271,918 Abandoned US20140372750A1 (en) | 2013-05-08 | 2014-05-07 | Client-side encryption |
US14/271,798 Abandoned US20140337290A1 (en) | 2013-05-08 | 2014-05-07 | Secure synchronization of files |
US16/278,321 Pending US20190180044A1 (en) | 2013-05-08 | 2019-02-18 | Internal folder sharing |
Country Status (2)
Country | Link |
---|---|
US (4) | US10248803B2 (en) |
WO (1) | WO2015171846A1 (en) |
Families Citing this family (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10248803B2 (en) | 2013-05-08 | 2019-04-02 | Intermedia.Net, Inc. | Internal folder sharing |
US20160140139A1 (en) * | 2014-11-17 | 2016-05-19 | Microsoft Technology Licensing, Llc | Local representation of shared files in disparate locations |
CN104579690B (en) * | 2015-01-23 | 2018-07-10 | 济南同智伟业软件股份有限公司 | High in the clouds KEY systems and application method |
US10277601B1 (en) | 2015-05-11 | 2019-04-30 | Google Llc | System and method for recursive propagating application access control |
US11470131B2 (en) * | 2017-07-07 | 2022-10-11 | Box, Inc. | User device processing of information from a network-accessible collaboration system |
CN107395612A (en) * | 2017-08-08 | 2017-11-24 | 四川长虹电器股份有限公司 | Realize the System and method for of network disk data safety |
US11055261B2 (en) | 2018-02-28 | 2021-07-06 | Microsoft Technology Licensing, Llc | In-application support for topological changes to files during remote synchronization |
US11088829B2 (en) * | 2018-09-04 | 2021-08-10 | International Business Machines Corporation | Securing a path at a node |
US11991273B2 (en) | 2018-09-04 | 2024-05-21 | International Business Machines Corporation | Storage device key management for encrypted host data |
US11038698B2 (en) | 2018-09-04 | 2021-06-15 | International Business Machines Corporation | Securing a path at a selected node |
US11640475B1 (en) * | 2019-11-26 | 2023-05-02 | Gobeep, Inc. | Systems and processes for providing secure client controlled and managed exchange of data between parties |
US11444754B1 (en) * | 2021-12-30 | 2022-09-13 | Monday.com Ltd. | Tenant level encryption |
Citations (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6324587B1 (en) * | 1997-12-23 | 2001-11-27 | Microsoft Corporation | Method, computer program product, and data structure for publishing a data object over a store and forward transport |
US6401079B1 (en) * | 1999-10-01 | 2002-06-04 | Inleague, Inc. | System for web-based payroll and benefits administration |
US6564369B1 (en) * | 1998-08-20 | 2003-05-13 | Pearson Technical Software, Inc. | Conflict checking using configuration images |
US20050144195A1 (en) * | 1999-12-02 | 2005-06-30 | Lambertus Hesselink | Managed peer-to-peer applications, systems and methods for distributed data access and storage |
US20070130143A1 (en) * | 2005-12-05 | 2007-06-07 | Wenbing Zhang | System and Method for File Sharing and Collaboration on the Internet |
US20090077262A1 (en) * | 2007-09-14 | 2009-03-19 | International Business Machines Corporation | System and method for synchronization between servers |
US20100306314A1 (en) | 2001-07-13 | 2010-12-02 | O'connell Jr Conleth S | Storage medium having a manageable file directory structure |
US20120166818A1 (en) | 2010-08-11 | 2012-06-28 | Orsini Rick L | Systems and methods for secure multi-tenant data storage |
US20120265976A1 (en) | 2011-04-18 | 2012-10-18 | Bank Of America Corporation | Secure Network Cloud Architecture |
US20130013560A1 (en) * | 2011-07-08 | 2013-01-10 | Arnold Goldberg | Desktop application for access and interaction with workspaces in a cloud-based content management system and synchronization mechanisms thereof |
US20130275509A1 (en) | 2012-04-11 | 2013-10-17 | Salesforce.Com Inc. | System and method for synchronizing data objects in a cloud based social networking environment |
US20130283232A1 (en) * | 2010-11-24 | 2013-10-24 | Van Megchelen & Tilanus B.V. | User-Friendly Method and System for Compiling a Unique Sample Code for a Digital Sample with the Help of a User Interface |
US20130282830A1 (en) | 2012-04-23 | 2013-10-24 | Google, Inc. | Sharing and synchronizing electronically stored files |
US20140337290A1 (en) | 2013-05-08 | 2014-11-13 | Intermedia.Net, Inc. | Secure synchronization of files |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2005078612A (en) * | 2003-09-04 | 2005-03-24 | Hitachi Ltd | File sharing system, and file transfer method between file sharing systems |
US7860825B2 (en) * | 2006-05-08 | 2010-12-28 | Palm, Inc. | Method for synchronizing software application and user data for asynchronous client-server and peer to peer computer networks |
US8099605B1 (en) * | 2006-06-05 | 2012-01-17 | InventSec AB | Intelligent storage device for backup system |
US20080005195A1 (en) * | 2006-06-30 | 2008-01-03 | Microsoft Corporation | Versioning synchronization for mass p2p file sharing |
US20080163743A1 (en) * | 2007-01-07 | 2008-07-10 | Freedman Gordon J | Synchronization methods and systems |
US8204856B2 (en) * | 2007-03-15 | 2012-06-19 | Google Inc. | Database replication |
US20120180073A1 (en) * | 2011-01-06 | 2012-07-12 | Hung Hin Leung | Mobile Device Application Framework |
US8862561B1 (en) * | 2012-08-30 | 2014-10-14 | Google Inc. | Detecting read/write conflicts |
US9400800B2 (en) * | 2012-11-19 | 2016-07-26 | Palo Alto Research Center Incorporated | Data transport by named content synchronization |
-
2014
- 2014-05-07 US US14/271,846 patent/US10248803B2/en active Active
- 2014-05-07 US US14/271,918 patent/US20140372750A1/en not_active Abandoned
- 2014-05-07 US US14/271,798 patent/US20140337290A1/en not_active Abandoned
-
2015
- 2015-05-07 WO PCT/US2015/029586 patent/WO2015171846A1/en active Application Filing
-
2019
- 2019-02-18 US US16/278,321 patent/US20190180044A1/en active Pending
Patent Citations (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6324587B1 (en) * | 1997-12-23 | 2001-11-27 | Microsoft Corporation | Method, computer program product, and data structure for publishing a data object over a store and forward transport |
US6564369B1 (en) * | 1998-08-20 | 2003-05-13 | Pearson Technical Software, Inc. | Conflict checking using configuration images |
US6401079B1 (en) * | 1999-10-01 | 2002-06-04 | Inleague, Inc. | System for web-based payroll and benefits administration |
US20050144195A1 (en) * | 1999-12-02 | 2005-06-30 | Lambertus Hesselink | Managed peer-to-peer applications, systems and methods for distributed data access and storage |
US20100306314A1 (en) | 2001-07-13 | 2010-12-02 | O'connell Jr Conleth S | Storage medium having a manageable file directory structure |
US20070130143A1 (en) * | 2005-12-05 | 2007-06-07 | Wenbing Zhang | System and Method for File Sharing and Collaboration on the Internet |
US20090077262A1 (en) * | 2007-09-14 | 2009-03-19 | International Business Machines Corporation | System and method for synchronization between servers |
US20120166818A1 (en) | 2010-08-11 | 2012-06-28 | Orsini Rick L | Systems and methods for secure multi-tenant data storage |
US20130283232A1 (en) * | 2010-11-24 | 2013-10-24 | Van Megchelen & Tilanus B.V. | User-Friendly Method and System for Compiling a Unique Sample Code for a Digital Sample with the Help of a User Interface |
US20120265976A1 (en) | 2011-04-18 | 2012-10-18 | Bank Of America Corporation | Secure Network Cloud Architecture |
US20130013560A1 (en) * | 2011-07-08 | 2013-01-10 | Arnold Goldberg | Desktop application for access and interaction with workspaces in a cloud-based content management system and synchronization mechanisms thereof |
US20130275509A1 (en) | 2012-04-11 | 2013-10-17 | Salesforce.Com Inc. | System and method for synchronizing data objects in a cloud based social networking environment |
US20130282830A1 (en) | 2012-04-23 | 2013-10-24 | Google, Inc. | Sharing and synchronizing electronically stored files |
US20140337290A1 (en) | 2013-05-08 | 2014-11-13 | Intermedia.Net, Inc. | Secure synchronization of files |
US20140372750A1 (en) | 2013-05-08 | 2014-12-18 | Intermedia.net. Inc. | Client-side encryption |
WO2015171846A1 (en) | 2013-05-08 | 2015-11-12 | Intermedia.Net, Inc. | Secure synchronization of files |
Non-Patent Citations (9)
Also Published As
Publication number | Publication date |
---|---|
US20140337290A1 (en) | 2014-11-13 |
US20190180044A1 (en) | 2019-06-13 |
US20140372750A1 (en) | 2014-12-18 |
US20140337386A1 (en) | 2014-11-13 |
WO2015171846A1 (en) | 2015-11-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20190180044A1 (en) | Internal folder sharing | |
US10951702B2 (en) | Synchronized content library | |
US10397319B2 (en) | Server-side selective synchronization | |
JP6419319B2 (en) | Synchronize shared folders and files | |
US9866508B2 (en) | Aggregating and presenting recent activities for synchronized online content management systems | |
US9461949B2 (en) | Managing links and invitations to shared content | |
US10168927B2 (en) | Data mirroring for network attached storage | |
US20150012861A1 (en) | Syncing content clipboard | |
US9996549B2 (en) | Method to construct a file system based on aggregated metadata from disparate sources | |
US20150006482A1 (en) | Naïve, client-side sharding with online addition of shards | |
EP2951734B1 (en) | Providing a content preview | |
US10057273B1 (en) | System and method for ensuring per tenant mutual exclusion of data and administrative entities with low latency and high scale | |
WO2019047976A1 (en) | Network file management method, terminal and computer readable storage medium | |
US20160179789A1 (en) | Content localization using fallback translations | |
US20140304384A1 (en) | Uploading large content items | |
US20140229457A1 (en) | Automatic content item upload | |
US9930063B2 (en) | Random identifier generation for offline database | |
US11595207B2 (en) | Utilizing encryption key exchange and rotation to share passwords via a shared folder | |
US20200356528A1 (en) | System and method for archive file check-in/out in an enterprise content management system | |
US20150163326A1 (en) | Approaches for remotely unzipping content | |
US11442892B2 (en) | File and data migration to storage system | |
US10917468B2 (en) | Systems and methods of re-associating content items | |
US11250527B2 (en) | Providing near real-time and effective litigation management for multiple remote content systems using asynchronous bi-directional replication pipelines |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTERMEDIA.NET, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:DUSEVIC, BOJAN;GACHECHILADZE, ANDREW;URALTSEV, NIKITA;AND OTHERS;SIGNING DATES FROM 20140502 TO 20140505;REEL/FRAME:032841/0232 |
|
AS | Assignment |
Owner name: SUNTRUST BANK, AS ADMINISTRATIVE AGENT, GEORGIA Free format text: FIRST LIEN PATENT SECURITY AGREEMENT;ASSIGNOR:INTERMEDIA.NET, INC.;REEL/FRAME:041590/0122 Effective date: 20170201 Owner name: SUNTRUST BANK, AS ADMINISTRATIVE AGENT, GEORGIA Free format text: SECOND LIEN PATENT SECURITY AGREEMENT;ASSIGNOR:INTERMEDIA.NET, INC.;REEL/FRAME:041590/0158 Effective date: 20170201 |
|
AS | Assignment |
Owner name: INTERMEDIA.NET, INC., CALIFORNIA Free format text: TERMINATION AND RELEASE OF SECOND LIEN SECURITY INTEREST IN PATENTS, RECORDED AT REEL 014590, FRAME 0192;ASSIGNOR:SUNTRUST BANK;REEL/FRAME:046610/0041 Effective date: 20180719 Owner name: INTERMEDIA.NET, INC., CALIFORNIA Free format text: TERMINATION AND RELEASE OF SECOND LIEN SECURITY INTEREST IN PATENTS;ASSIGNOR:SUNTRUST BANK;REEL/FRAME:046619/0417 Effective date: 20180723 Owner name: ACCESSLINE COMMUNICATIONS CORPORATION, CALIFORNIA Free format text: TERMINATION AND RELEASE OF SECOND LIEN SECURITY INTEREST IN PATENTS;ASSIGNOR:SUNTRUST BANK;REEL/FRAME:046619/0417 Effective date: 20180723 |
|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: INTERMEDIA.NET, INC., CALIFORNIA Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE LEGAL SIGNATURE OF INVENTOR BOJAN DUSEVIC PREVIOUSLY RECORDED ON REEL 032841 FRAME 0232. ASSIGNOR(S) HEREBY CONFIRMS THE THE ASSIGNMENT;ASSIGNORS:DUSEVIC, BOJAN;GACHECHILADZE, ANDREW;URALTSEV, NIKITA;AND OTHERS;SIGNING DATES FROM 20140502 TO 20140505;REEL/FRAME:049938/0458 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |