WO2014111781A1

WO2014111781A1 - System and methods of cloud based file sharing

Info

Publication number: WO2014111781A1
Application number: PCT/IB2013/061418
Authority: WO
Inventors: Dov Moran; Nadav MANSDORF; Ehud Weinstein
Original assignee: Albu Technologies Ltd.
Priority date: 2013-01-16
Filing date: 2013-12-30
Publication date: 2014-07-24

Abstract

The disclosure herein relates to file sharing of various file types between a plurality of accessors, using a cloud-based file sharing system. The cloud-based file sharing system comprising a file repository with at least one directory comprising a plurality of files and at least one accessor device associated with an accessor. Each accessor, connectable to the file repository through a cloud-based network, may be capable of accessing a different subset of files. The cloud-based file sharing system, may allow varying levels of access control, sharing rights and determination of additional content based on file and user metadata. It is noted that each accessor may contribute different files enabling automatic file sharing or configure the sharing mechanism. Further, different users may have different views of the files of the file repository.

Description

SYSTEM AND METHODS OF CLOUD BASED FILE SHARING

FIELD OF THE DISCLOSURE

The disclosure herein relates to file sharing of various file types. In particular, the disclosure relates to cloud based file sharing having varying levels of access control and determination of additional content based on file and user metadata.

BACKGROUND

The sharing of files, especially photos, is a popular use of the internet, and increasingly of cloud-based file storage. With the large number of files potentially accessible to anyone who can access any given cloud-based storage platform, there is an increased need for directed, as well as automated, ways to control the access of files. In addition, there is a need to facilitate the intelligent sharing of the large number of files with others. SUMMARY OF THE EMBODIMENTS

It is according to a first aspect of the disclosure to introduce a cloud-based file sharing system comprising: a file repository comprising at least one directory comprising at least one file; and at least one accessor device associated with an accessor connectable to the file repository through a cloud network. Optionally, the cloud-based file sharing system may have a plurality of accessor devices, the at least one directory comprising a plurality of files, wherein a first accessor device is capable of accessing a first subset of files and a second accessor device is capable of accessing a second subset of files. Variously, such accessor devices may be telephones, tablets, computers, media renders, televisions or the like. The cloud-based file sharing system may share files selected from the group consisting of graphics, picture, video, text and music files.

In another aspect of the disclosure a method is taught for populating a directory of a cloud-based file sharing system with at least one file comprising the steps of: assigning the at least one file located in a contributor host device to the directory; obtaining at least one contact detail regarding at least one contact; assigning an access right to the at least one contact with regard to the at least one file; uploading the directory and the at least one file from the contributor host device to a server database; and sending a notification to the at least one contact.

The method may further comprise the steps of: defining a set of associated metadata comprising profiling features for the at least one file; searching the contributor host device for one or more host additional files having at least one shared profiling feature; and suggesting host additional files to add to the directory.

Optionally, the method may further comprise the steps of: selecting at least one host additional file to assign to the directory; uploading the at least one host additional file from the contributor host device to the server database; and sending an additional notification to the at least one contact.

Additionally or alternatively, the method may still further comprise the steps of: a contact host device receiving the notification; searching the contact host device for one or more additional files having at least one shared profiling feature with the at least one file; suggesting contact additional files to add to the directory. Accordingly, the method may comprise the steps of: selecting at least one of the contact additional files to assign to the directory; uploading the at least one contact additional file from the contact host device to the server database; and sending an additional notification to the at least one contact.

Optionally, the step of defining a set of associated metadata comprising profiling features comprises the substeps of: identifying at least one profiling feature selected from the group consisting of: a timestamp; a location stamp; and at least one content within file; identifying access permission; identifying sharing permission; and associating to the file a metadata information block comprising the profiling features.

Where appropriate, the step of defining a set of associated metadata comprising profiling features comprises the substeps of: identifying the profiling features incorporated within metadata associated with a plurality of accessors having access to the directory; calculating a score for profiling features, with profiling features highly represented among the plurality of accessors having a high score; and including the high-scoring profiling features as the search parameters for additional files. Optionally, the step of assigning the access right comprises the substeps of: prompting the contributor to designate the file as private; and if the file is designated as not private, prompting the contributor to designate the file as exclusive; wherein: if the file is designated as private, then only the contributor is granted access rights to the file; if the file is designated as not private and as not exclusive, then all associates associated with the directory are granted access rights to the file; if the file is designated as not private and as exclusive, then the contributor is prompted to selected associates, and only the selected associates are granted access rights to the file.

Additionally or alternatively, the method of may comprise the step of assigning a sharing right to the at least one contact with regard to the at least one file, the step comprising the substeps of: prompting the contributor to designate the file as private; and if the file is designated as not private, prompting the contributor to designate the file as exclusive; wherein: if the file is designated as private, then only the contributor is granted sharing rights to the file; if the file is designated as not private and as not exclusive, then all associates with the directory is granted sharing rights to the file; and if the file is designated as not private and as exclusive, then the contributor is prompted to selected associates, and only the selected associates are granted sharing rights to the file. Still another method is taught of associating a directory to a plurality of accessors, comprising the steps of: populating the directory with a plurality of files; associating the plurality of accessors with the directory; granting access to at least one of the plurality of files populated in the directory to at least one of the plurality of accessors; presenting to at least one accessor one or more files for which the at least one accessor has been granted access. Optionally, the method may further comprise the step of: providing a personalized score for each of the plurality of files for which the at least one accessor has been granted access; prioritizing the presenting of each of the plurality of files to the at least one accessor based on the personalized score. Where appropriate, the presenting of the one or more files is produced in a plurality of content fields having different prominence levels, and wherein a file with a high personalized score is placed in a content field having a high prominence level.

A further method is taught of identifying one or more accessors of interest, comprising the steps of: identifying accessors with access to common files; identifying accessors with access to common directories; identifying accessors with access to files with similar file metadata; identifying accessors with similar accessor metadata; determining a link score for the identified accessors. Optionally, the step of determining a link score comprises obtaining a linkage function and applying said linkage function to said one or more identified accessors. A linkage function may comprise a formula for calculating a link score. The link calculation formula may, for example, comprise a combination of monomials, such as the products of a linkage indicator and associated weighting coefficient. Variously, the linkage indications may include the number of image albums or directories shared, number of shared items or images, number of items/images viewed by each user and the like. Accordingly, a linkage function may be defined to return a link score for a given set of users from a plurality of linkage variables, linkage factors, linkage parameters and the like.

Accordingly a computer readable medium is introduced having instructions thereon, which, when executed by a processor causes the processor to perform operations comprising the methods described herein.

In still another aspect of the disclosure, a system is introduced comprising: at least one processor, at least one display device, and at least one computer readable medium coupled to the processor, the computer readable medium comprising instructions, which, when executed by a processor causes the processor to perform operations of any of the methods described herein. Similarly, a computer readable medium may be presented having computer executable instructions for performing operations comprising any of these methods.

It is noted that in order to implement the methods or systems of the disclosure, various tasks may be performed or completed manually, automatically, or combinations thereof. Moreover, according to selected instrumentation and equipment of particular embodiments of the methods or systems of the disclosure, some tasks may be implemented by hardware, software, firmware or combinations thereof using an operating system. For example, hardware may be implemented as a chip or a circuit such as an ASIC, integrated circuit or the like. As software, selected tasks according to embodiments of the disclosure may be implemented as a plurality of software instructions being executed by a computing device using any suitable operating system.

In various embodiments of the disclosure, one or more tasks as described herein may be performed by a data processor, such as a computing platform or distributed computing system for executing a plurality of instructions. Optionally, the data processor includes or accesses a volatile memory for storing instructions, data or the like. Additionally or alternatively, the data processor may access a non-volatile storage, for example, a magnetic hard-disk, flash-drive, removable media or the like, for storing instructions and/or data. Optionally, a network connection may additionally or alternatively be provided. User interface devices may be provided such as visual displays, audio output devices, tactile outputs and the like. Furthermore, as required user input devices may be provided such as keyboards, cameras, microphones, accelero meters, motion detectors or pointing devices such as mice, roller balls, touch pads, touch sensitive screens or the like.

BRIEF DESCRIPTION OF THE FIGURES

For a better understanding of the embodiments and to show how it may be carried into effect, reference will now be made, purely by way of example, to the accompanying drawings. With specific reference now to the drawings in detail, it is stressed that the particulars shown are by way of example and for purposes of illustrative discussion of selected embodiments only, and are presented in the cause of providing what is believed to be the most useful and readily understood description of the principles and conceptual aspects. In this regard, no attempt is made to show structural details in more detail than is necessary for a fundamental understanding; the description taken with the drawings making apparent to those skilled in the art how the several selected embodiments may be put into practice. In the accompanying drawings:

Fig. 1 is a block diagram schematically representing selected components of a cloud based file sharing system; Figs. 2A-D show a set of schematic diagrams illustrating possible functionality within the file sharing system of creating a file, accessing or adding a file;

Figs. 3A-B are flowcharts representing selected actions of methods for creating a file, submission to the server and interacting with a contact;

Figs. 4A-D are flowcharts representing selected actions of methods for profiling a file and determining its associated link score level with reference to another profiling file;

Figs. 5A-D are flowcharts representing selected actions of methods for populating a shared directory, assigning access rights and sharing;

Fig. 6 is a flow chart representing selected actions of a method for selectively presenting content to various accessors; Figs. 7A-B are flowcharts representing selected actions of a method for providing a personalized presentation for each accessor; and Fig. 7C shows a possible user presentation template for use in presenting a personalized presentation of content.

DETAILED DESCRIPTION

Aspects of the present disclosure relate to file sharing between a plurality of accessors, using a cloud-based file sharing system. The cloud-based file sharing system comprising a file repository with at least one directory comprising a plurality of files and at least one accessor device associated with an accessor. Each accessor, connectable to the file repository through a cloud-based network, may be capable of accessing a different subset of files.

It is noted that the cloud-based file sharing system, may allow varying levels of access control, sharing rights and determination of additional content based on file and user metadata. In particular, it is further noted, that each accessor may contribute different files enabling automatic file sharing or configure the sharing mechanism. Optionally, users may be able to connect with contacts and share files stored in a file repository with those contacts by a simple procedure requiring little user input, perhaps only one instructive action such as a click, touch, gesture as appropriate and as described in more detail hereinafter. The system may automatically populate a file repository or suggest to the users files to upload to the file repository. Furthermore, each accessor may access a personalized presentation of the files stored in the shared repository to suit their own preferences and requirements.

Optionally, users may be able to use various gestures to select whole events. For example, a long-touch gesture may select all files characterized by being associated with a particular event such as a conference, a wedding, a lecture, a holiday or the like. Accordingly, various parameters may be used to characterize groups of files to selected in this manner. For example a time range and location combination may allow selection of files created around that time range, say a range of 4 hours of an event. Additionally or alternatively further parameters may be used to effect such a selection, accordingly content data may be used to characterize a file enabling, for example, selection of images including a particular person, place, event-type or the like. Still further parameter combinations will occur to those skilled in the art. Optionally, organization of albums may use 'Drag and Drop' fucntionality to merge an album into another within a category. Additionally or alteratively, 'Drag and Drop' functionality may be used to select and move individual files, images, content or categories of content as required. Optionally, the file sharing mechanism may allow toggling between two different views of an image, presenting the image only or presenting the image with properties associated with the image. For example a graphical representation of the reverse of a photograph may present metadata such as image properties or other characteristics of the file. Optionally, visualization of participants may use different color for each character chosen according to a color scheme.

Cloud-based System Architecture:

Some embodiments representing the current file sharing system, may use client/server technology, but are not limited to such architecture and may use other network architectures such as a peer-to-peer, where each node has equivalent responsibilities or the like.

It is noted that in software engineering, such a client/server network architecture in which presentation, application processing, and data management functions are logically separated are referred to as a multi-tier / multi-node architecture. The most widespread use of multi-node architecture is the three-node architecture, where the client may be considered the first node (presentation layer), the server may be the second node (application logic processing) and the database server may be the third node or tier (data management).

Client software (may be referred to as the user agent) may allow interaction between the client machine (an electrical mobile device, tablet, handheld device, user terminal and the like) and the application layer. When web-based applications are used, the client node (usually a mobile App, a browser) renders the user interface, which may be generated by a presentation layer (the user application) on the client side or received from the server, for example.

The current disclosure of a cloud-based file sharing system, implementing client/server technology, may be used to facilitate sharing of multimedia files (pictures, video and the like), for example. The client node may be an electrical mobile device (the accessor device) operable, for example, on a iOS operating system of Apple, Android operating system of Google or a Web-Site implementing technologies such as HTML, JavaScript, Java, C#, ActiveX and the like. The client device may be used to capture pictures and videos, which may be transmitted to the second node, the server which may be used for storing the captured images into a third node, the shared files repository. Accordingly, the server node may provide various aspects of management functionality to allow the sharing. For example management functionality may include creating the file repository, creating one or more directories within the file repository, adding files to the file directories, adding new accessors, associating accessors to the files in the directories and the like.

Sharing mechanism:

Users (accessors) of the system may interact with one another to share files.

Optionally, sharing may be operable with non-system users.

Sharing of files between accessors may use various techniques and unique parameters in order to achieve the desired level of sharing, for the individual contributor.

For example, for the scenario of digital image file sharing of pictures and videos, in order to present a user with the most appropriate set of images, analyzing parameters may include: the popularity of an image measured optionally by the number of viewers, duration of image viewing as a personal parameter, optionally may be used as an aggregate parameter. Further, the relationship between the various viewers of an image may be optionally based on social network interfacing and the like.

Where appropriate, analyzing the image itself may produce additional information, if considering people associated with the image, facial expressions and the like.

Where appropriate, social references related to an image, measured according to various parameters, such as number of 'likes' as interpreted in a social space and social networks.

Where appropriate, the level of interaction made with the image such as adding titles, usage as a profiling image, adding various editing functionality and the like.

It is noted that an accessor of the cloud-based file sharing system may interact with other accessors having a user account, and where appropriate, interact with other non- system users.

As appropriate, for any two accessors, a link score, such as a level of sharing

('friendship level'), may be determined based on cooperation between the two accessors and the degree of interaction between them. For example, the 'friendship level' , for any two users, may be based on linkage indications such as the number of image albums or directories shared, number of shared items or images, number of items/images viewed by each user and the like. Accordingly, a linkage function may be defined to return a link score for a given set of users from a plurality of linkage variables, linkage factors, linkage parameters and the like such as follows: Friendship level (x, y) =f (# of shared albums, # of shared items, # of items viewed,...) where x and y, each represent a user.

By way of illustration only, one example of such a linkage function may comprise a formula for calculating a link score. The link calculation formula may, for example, comprise a combination of monomials, such as the products of a linkage indicator and associated weighting coefficient.

Accordingly, the 'friendship level' may represent a low link score for any set of users with limited level of sharing, and high link score indicating a high level of sharing.

The function may use a linear expression. Additionally or alternatively, the function may use polynomial expressions.

It is noted, that although the linkage function may be used to grade the linkage level between only two users, such a function may be readily extended to return link scores for sets of three or more users allowing the grading of linkage groups or sets.

Such data interaction indication may represent important business related information and may further allow a better individual experience to be provided, creating stronger social network representing and quantifying social and business ties across business communities.

The quantified 'friendship level' may be targeted towards achieving a better representation of the social and business relationship between individual members of business community. This may provide indications of a community's strength, based on cooperation level while measuring the associated parameters of a number of shared albums, number of share items, level of interaction between the users based upon duration of viewing of elements of the other side, number of views and the like.

Description of the Embodiments:

It is noted that the systems and methods of the disclosure herein may not be limited in their application to the details of construction and the arrangement of the components or methods set forth in the description or illustrated in the drawings and examples. The systems and methods of the disclosure may be capable of other embodiments or of being practiced or carried out in various ways. Alternative methods and materials similar or equivalent to those described herein may be used in the practice or testing of embodiments of the disclosure. Nevertheless, particular methods and materials are described herein for illustrative purposes only. The materials, methods, and examples are not intended to be necessarily limiting.

In various embodiments of the disclosure, one or more tasks as described herein may be performed by a data processor, such as a computing platform or distributed computing system for executing a plurality of instructions. Optionally, the data processor includes or accesses a volatile memory for storing instructions, data or the like. Additionally or alternatively, the data processor may access a non-volatile storage, for example, a magnetic hard-disk, flash-drive, removable media or the like, for storing instructions and/or data. Optionally, a network connection may additionally or alternatively be provided. User interface devices may be provided such as visual displays, audio output devices, tactile outputs and the like. Furthermore, as required user input devices may be provided such as keyboards, cameras, microphones, accelerometers, motion detectors or pointing devices such as mice, roller balls, touch pads, touch sensitive screens or the like.

Reference is made to the system diagram of Fig. 1 showing a representation of a cloud-based file sharing system 100. The file sharing system 100 may be used to facilitate the sharing of files of various media such as pictures, video, music, text, multimedia files and the like as well as combinations thereof.

The file sharing system 100 includes a file repository 102, a cloud network 104. The file sharing system 100 may further include various accessor devices 106, 108 and 110, 112A-C connectable to the file repository 102 through the cloud network 104.

The file sharing system 100 provides computer-aided functionality for managing a repository of content accessible to a plurality of accessors. The file-sharing system 100 may provide various functionality such as the ability of creating one or more directories within the file repository 102, adding one or more files to the file directories, adding new accessors, associating said accessors to the files in the directories, assigning permissions such as access rights and sharing rights to various accessors and the like.

The accessor devices 106, 108, 110, 112A-C may be operable to access the files based on permissions. Further, the accessor devices 106, 108, 110, 112A-C may be operable to store new files into the file repository 102.

Various accessor devices 106, 108, 110, 112A-C may be used to access the files. For example, a mobile communication device, such as mobile telephones 106, 108, 110, tablet computers 112B, laptop computers 112C or the like, may be operable to execute a software application for capturing, uploading, accessing presenting files and the like.

It is particularly noted that accessor devices may include media Tenderers 112A such as televisions, media players, tablet computers, computers, digital picture frames and the like. Such a media player 112A may be configured to display a popup notification 113, an overlay screen or the like indicating that a particular shared file repository has been updated, perhaps in real time.

Further, the file sharing system 100 may enable the creating of profiles for content stored in directories based on content metadata as detailed herein. The profiling functionality may additionally or alternatively enable comparing between profiles, creating a link score to define the linkage level between two profiles and such like. An accessor device may run a program, which may be an application or an app, which associates the accessor device with an accessor, which may be a user or user account. The accessibility of directories, and individual files within each directory, to an accessor, may be controlled by a set of permissions. As such, an accessor may have permission to access only a subset of directories, giving each accessor a personalized level of access to a directory. An accessor may only have the permission to access a subset of files within a directory. The subset of the directory accessible to an accessor may be referred to as an album. Additionally, the file sharing system 100 may provide presentation functionality of at least a portion of the directory content to accessors in a personalized manner.

It is particularly noted that file sharing system 100 is operable for sharing of any file types supported by the accessor devices. Such files may include, for example, graphics, picture, video, text, music files supporting various file formats, multimedia files, combinations thereof or any other data type files, including data collection files and the like.

Optionally, the file directory may be part of a larger file repository. Such a file repository may be structured as a set of directories, where each directory may contain a set of files and possibly additional set of sub-directories.

Reference is now made to the schematic diagrams of Figs. 2A-D, illustrating possible functionality within the file sharing system 100 of creating a directory, accessing a file within a directory, displaying the accessed files or adding a file into the existing directory 102. The schematic diagrams of Figs 2A-D may be implemented by a data processing device, such as the accessor devices 106, 108 and 110 of Fig. 1, for example, interacting with a server of a remote machine (not shown).

A file may be created by a contributor and may be inserted into the file sharing system 100 with a possible specific attribute, such as 'private', 'exclusive' or 'none', for example. A 'private' file may, for example, be left with access rights for the contributor only, while an 'exclusive' file may be allowed access rights to others at the discretion of the contributor. Files with 'none' attribute, for example, may be allowed access by all accessors that are associated with the containing parent directory.

Fig. 2A shows a schematic diagram of possible illustration of creating activity by accessorsl06 and 108. The accessor may interact with a directory as a contributor that creates a new directory or a new file within an existing directory, or as an associate that accesses an existing file. The accessors 106 and 108 represent contributors, which are allowed to create new files, inserting them into the file repository 102 for storage and possibly allowing access rights or sharing rights to other accessors based upon the attribute that may be associated with the newly created file. It is noted that a first accessor 106 may serve as a creator of the shared directory

102. The creation of the file repository 102 may involve the creator 106 uploading a first content file FILE A and associating at least a second accessor 108. Additional content 101 may be uploaded, possibly automatically, from a memory associated with a device of the creator 106. Furthermore, when the second accessor 108 accesses the file repository 102 further additional content 103 may be uploaded from a memory associated with a device of the second accessor 108. As described in greater detail below, the process of creating and initially populating the shared directory may be streamlined and automated for efficiency. Fig. 2B shows an illustration representing how various accessors may have different access rights to various files stored in the file repository 102. Each one of accessor devices 106, 108 and 110 may have different access rights to a subset of the file repository 102, with the different subsets forming a personalized album. Accordingly, accessor device 106 may have permission access to FILE A, FILE B and FILE D, while accessor device 108 may have permission access to FILE A, FILE B and FILE C and accessor device 110 may have permission access to FILE B and FILE C only.

An accessor that creates a file within a directory may be associated with the file as a contributor. Further, other accesors may be associated with the file as an associate. The associate may be of various types, including: an associate with access rights, which may access the file but cannot share it with another accessor; or an associate with sharing rights, which may access the file and in addition share it with another accessor. When an associate with sharing rights shares a file with another accessor, that accessor becomes associated with that file as an associate. Typically, a contributor is also an associate with sharing rights.

Fig. 2C shows an illustration representing the personalized experience 100A of various accessors using the cloud-based file sharing system and retrieving their associated files only, partially private while others are shared, such that a stored picture file repository, for example, may be presented differently to various accessors. Further, an accessor may view images of personal interest, for example, based upon level of friendship parameters, determining the level of association with other accesors of the same file repository. The retrieval process of files from the file repository may use various filters coupled with navigation options. Such filters may be applied and selected from a group of time, location, people, type of information and combinations thereof. It is noted that the level of friendship may indicate the level of sharing between any two accessors, and may include parameters such as the number of image albums shared, number of shared items or images within an album, number of items/images viewed by each user and the like.

Each one of the accessor devices 103A and 103B, may optionally have different access rights to a subset of the file repository 102, with the different subsets forming a personalized album where the different subset may overlap. Accordingly, accessor device 103A may have access to files A, B, D, F and G, while accessor device 103B may have access to A, C, D, E and G, such that files A, D and G are mutually shared between accessors 103 A and 103B.

It is further noted that the sharing indications and various parameters resulting from various computation and filtering processes, may be stored as part of data describing the file repository, such that retrieving files from the repository is faster.

Optionally, users may be able to use various gestures to select whole events. For example, a long-touch gesture may select all files characterized by being associated with a particular event such as a conference, a wedding, a lecture, a holiday or the like. Accordingly, various parameters may be used to characterize groups of files to selected in this manner. For example a time range and location combination may allow selection of files created around that time range, say a range of 4 hours of an event. Additionally or alternatively further parameters may be used to effect such a selection, accordingly content data may be used to characterize a file enabling, for example, selection of images including a particular person, place, event-type or the like. Still further parameter combinations will occur to those skilled in the art.

Optionally, visualization of participants may use different color for each character chosen according to a color scheme.

Fig. 2D shows an illustration of a possible activity of adding a file for storage in the file repository 102 by a contributor 202, and providing access to the added file to other accessors. FILE E, added by a contributor 202, may be shared with another accessor, as an associate with access rights 204, which may access FILE E but cannot share it. Optionally, FILE E may be shared with another accessor, and further pass on the sharing privilege, such that the other accessor also becomes an associate with sharing rights.

Referring back to Fig. 2B, it is noted that although the first accessor 106 may have been the initial creator of the file repository 102, that accessor 106 may not necessarily have access rights to all files stored within the file repository 102. For example, the second accessor 108 may have contributed content FILE C, say, granting access rights to a third accessor 110 but not granting access rights to the first accessor 106. Accordingly, the creator 106 of the file repository 102 does not have access to certain content FILE C stored thereupon.

Optionally, organization of albums may use 'Drag and Drop' functionality to merge an album into another within a category. Additionally or alteratively, 'Drag and Drop' functionality may be used to select and move individual files, images, content or categories of content as required.

Optionally, the file sharing mechanism may allow toggling between two different views of an image, presenting the image only or presenting the image with properties associated with the image. For example a graphical representation of the reverse of a photograph may present metadata such as image properties or other characteristics of the file.

Reference is made now to the flow charts of Figs. 3A-B, which schematically represent selected actions, providing a possible illustration of an interaction cycle between a contributor and a contact, including the creation of a directory, adding content, assigning rights, uploading to a server and sending notification to a contact. The functionality presented in Figs 3A-B may be implemented by a data processing device, such as the accessor devices 106, 108 and 110 of figure 1, communicating with a server of a remote machine (not shown). The method of Fig. 3A chiefly indicates activities on the contributor side. The method may optionally include creating a content directory - step 302A. Once the directory is created, or if an existing directory is being used, the method includes adding content into the directory - step 304A and obtaining contact details possibly from a list of contacts or through user entry - step 306A for the purpose of assigning access rights - step 308A. Once the associated files are selected, they may be uploaded onto the remote server machine - step 310A, saving the files to the database - step 330A. When the files are saved on the server side, a notification, such as an email, text message, chat message or the like, is sent to the contact - step 332A, triggering contact interaction - step 340A as outlined in greater detail in Fig. 3B below. Additionally, the files may be profiled - step 312A, defining a set of profiling features associated with the file ("the associated metadata") and accordingly, the contributor's host device may be searched for additional files having a similar profile of the content stored (for example, having at least one profiling feature that is shared with the file)

- step 314A and suggest said host additional files to be added to the directory - step 316A. The desired host additional files may be selected - step 318A and uploaded onto the server

- step 320A. When the additional selected host files are saved on the server side, a notification may be sent to the contact - step 332A, triggering contact interaction - step 340A. The method of Fig. 3B refers to the interaction of the server side with the contact side - step 340A. The contact interaction - step 340A may include receiving change notification such as an email, text message, chat message or the like when database changes are applied - step 302B. In response to the change notification, an initial check is carried out to verify the existence of the application on the device on which the change notification was received - step 304B. If the application is not installed, it may be downloaded from a server automatically, or with little user input, and installed - step 306B. It is noted that where required, usernames, login details, passwords and the like may be set automatically by the system, perhaps requiring only a single click instruction from a user. After installing the application, or if the application is already installed, the host device may be searched for contact additional files of a similar profile of the content stored - step 308B, to enable further content suggestion - step 310B, selecting the desired contact additional files - step 312B and uploading selected contact additional files to the server - step 314B. If more content is desired - step 316B, a further cycle of suggesting additional files - step 310B may take place. Otherwise, the process waits for another notification - step 318B.

Reference is now made to the flow charts of Figs. 4A-B schematically representing selected actions of methods to associate profiling information with a repository stored file, and to determine the score level of the link between two profiling files. The methods of Figs 4A-B are implemented by a data processing device, such as the accessor devices 106, 108 and 110 of Fig. 1, interacting with a server of a remote machine (not shown).

Fig 4A provides a possible method of updating target file metadata information comprising profiling features in its associated file. The file may be associated with metadata information related to its target file, such as file timestamp (e.g. creation of file, changes and the like), physical location stamp, for example gathered from satellite positioning, cellular triangulation or the like, its type and relevant content as well as associated access and sharing permissions.

The method may include obtaining a target file of any of the hereinabove types specified - step 402A, which may include one or more steps of the following: identifying the timestamp - step 404A; identifying the location stamp- step 406A; identifying one or more target file contents- step 408A. Identification of file contents may variously include, inter alia, text recognition for identifying keywords and the like, image analysis for face recognition or the like, audio track fingerprinting, media recognition or the like. The method may include further steps of identifying target file access permissions - step 410A and identifying target file sharing permissions - step 412A. Thereafter, the collected file information may be transformed into a metadata information block stored together, or otherwise associated, with the target file data. Referring now to Figs. 4B and 4C, showing methods for suggesting additional content for uploading to the file repository. With particular reference to Fig. 4A, the existence of the metadata associated with each uploaded file - step 402B, describing various attributes of said uploaded file, enables the searching of linked files with similar metadata - step 404B. Such links between two files may control the searching and suggesting of additional files to upload - step 406B.

By way of example, and so as to better illustrate the utility of the system, a shared file repository may be associated with a particular event, occasion or period which may be defined by a time frame. For example a user may upload media files such as pictures, videos and the like to a shared directory relating to an event such as a particular party defined by a particular location and time frame. Accordingly, the system may search accessors' devices for media files having associated metadata including location stamps lying within a location range defining the party location and timestamps within a time range defining the duration of the party. Such media files may be uploaded or otherwise included in an album associated with the particular event. It is noted that other events may be defined by extended timeframes or extended location ranges. For example a holiday trip may be defined by a two week time period and may be determined for example by an extended location range, say, a city, country, region or the like. It is further noted that location ranges may be negatively defined, such as by defining a region as anywhere outside my defined home region. It is particularly noted that time ranges and location ranges may be automatically defined by a system according to data harvested from user units. For example, calendar appointments may be used to define events, location history may be used to define location ranges, and the like. Furthermore, where appropriate, permissions may be granted for contents of emails and the like to be analyzed so as to provide defined ranges. Referring now to Fig. 4C, once a file is uploaded and its metadata are associated therewith - step 402C, suggestion of additional files to upload may also be controlled by metadata associated with individual accessors associated with the directory - step 404C.

Each accessor may be characterized by the aggregate metadata of the files that said accessor has access and/or sharing rights to. For example, a high proportion of the files that a first accessor has access and/or sharing rights to may have a particular location stamp, or a file content, or the like (e.g., the first accessor may have access to many files with a "Colorado" location stamp and file content of "mountains". In addition, each accessor may be prompted to enter personal information such as age, location, sex, interests, and the like. The features of accessor metadata of the accessors associated in the directory to which the new file was assigned may influence the search for additional files to upload - step 406C.

Additionally, by mining the collection of file access and sharing rights metadata, accessors of interest may be identified. Referring now to Fig. 4D, such accessors of interest may be other accessors with: access and/or sharing rights to one or more of the same files - step 402D; access to one or more of the same directories - step 404D; access and or sharing rights to files having similar metadata - step 406D. Similarly, accessors with similar accessor metadata (e.g., age, location, sex, interests etc.) may be identified - step 408D. The above factor may be used to calculate an accessor link score - step 410D. Optionally, once accessors of interest with a high link-score are identified, a contributor may be prompted to share the file, or grant privileged access to the accessor(s) in interest, e.g., access to an exclusive file or invite said accessor of interest to the directory - step 412D.

The link score may indicate the strength of a link between two or more contacts. The link score may be calculated or determined from a link score function by considering the values of a variety of link score factors and link score parameters such as by counting the number of files shared between the two contacts, by counting the number of directories or file repositories commonly accessible between the two contacts or the like. Additionally or alternatively, a link score function may include consideration of the frequency of sharing between two or more contacts, the nature of files shared between the contacts, the number of shared files and the like. Furthermore, the link score calculation may draw other link score determinants such as the nature of data provided in contact lists such as knowledge of one another's nicknames, dates of birth, spouse's names and the like.

It is further noted that contacts maybe grouped into clusters. Each cluster of contacts may be assigned a cluster link score indicating the tightness of the links binding the whole cluster. The cluster link score may be determined at least in part from frequency of sharing between the contacts of the cluster, the nature of files shared between the contacts of the cluster, the number of shared files between contacts of the cluster, the link scores between individual members of the cluster and the like. Reference is now made to the flow charts of Figs. 5A-D, which schematically represent selected actions of methods providing a possible file population process including possible functionality of assigning access rights and defining sharing options. The methods of Figs 5A-D may be implemented by a data processing device, such as the accessor devices 106, 108 and 110 of Fig. 1, interacting with a server of a remote machine (not shown).

Fig 5A provides a possible method for the general mechanism of assigning access and sharing rights for populated files, starting with step 502A of uploading a file by a contributor for storing in a shared directory - step 504A. Once the file is stored, access rights may be assigned to the file - step 506A, defining the permissions and adding the functionality of defining sharing rights for the files - step 508A, defining the allowed / disallowed sharing functionality for those having the predefined access to the newly uploaded file.

Fig 5B provides a possible functional flow of a method of assigning access rights to a previously uploaded file into the file directory 102 as specified in step 506A of Fig. 5A. The process may prompt a possible contributor (possibly, the owner of the target file) to assign access rights - step 502B. If the desired target file is set as private, possibly defined in its associated profile attributes - step 504B, then only the contributor is granted with access rights to the target file - step 510B, otherwise (target file is not private), a further step is required to test for exclusivity of the target file - step 506B. If the target file is not exclusive, all accessors associated with the containing directory where target file resides, are granted access permission - step 514B, otherwise (target file is exclusive), contributor is prompted to select associates or accessors accordingly - step 508B, granting sharing rights to list of associates or accessors selected - step 512B. It is noted that similar functionality may be associated to multiple files, either by selecting a set of files or selecting a specific directory assigning access rights to the higher level which is automatically assigned to all files included in the selected directory.

It is further noted that reversing the access granting functionality may also be possible and may allow for removing access rights from a file, a set of files or a directory, and is similarly possible.

Fig 5C provides a possible functional flow of a method of assigning sharing rights to a previously uploaded file into the file directory 102 as specified in step 508A of figure

5A. The process prompts a possible contributor (possibly, the owner of the target file) to assign sharing rights - step 502C. If the desired target file is set as private, possibly defined in its associated profile attributes - step 504C, then only the contributor is granted with sharing rights to the target file - step 5 IOC, otherwise (target file is not private), a further step is required to test for exclusivity of the target file - step 506C. If the target file is not exclusive, all associated accessors with the containing directory where target file resides, are granted sharing permission - step 514C. Otherwise, if the target file is exclusive, the contributor may be prompted to select accessors, accordingly - step 508C, and to select the depth sharing rights to be assigned - step 511C, and then granting sharing rights to list of accessors selected - step 512C. The depth of sharing rights refers to the right to assign sharing rights. For example, if an associate is assigned sharing rights with a depth of one, they would be permitted to grant access rights to other associates but not to grant sharing rights. An associate with a sharing rights with a depth of two be permitted to grant sharing rights with a depth of one. In general, any associate granted sharing rights with a depth of n would be permitted to assign sharing rights to a depth of (n-1 ).

It is noted that a similar functionality of granting sharing rights may be associated to multiple files either by selecting a set of files or selecting a specific directory assigning sharing rights to directory higher level which is then automatically assigned to all files contained in the selected directory. It is further noted that reversing the hereinabove sharing rights functionality may also be possible and may allow for removing sharing rights from a file, a set of files or a directory, and is similarly possible.

Fig 5D provides a unified flowchart of the complete population process method as detailed in the description of figure 5A, the associated flow of providing access rights as detailed in the description of figure 5B and the associated flow of providing sharing rights as detailed in the description of figure 5C. Referring now to the flowchart of Fig. 6, various selected actions are illustrated of a method for performing a selective process of associating content to a group of accessors. The method of Fig. 6 is implemented by a data processing device, such as a remote server in communication with the accessor devices 106, 108 and 110 of Fig. 1. The method may include obtaining a reference to a directory containing content files - step 602.

It is noted that each of the files in the content directory may be of a particular file type, such as images, video, music, text, data files, multimedia or the like. Optionally, it is noted that the file directory may contain files collected from different sources and may contain a mixture of files of different types.

The shared directory may be associated with a plurality of accessors - step 604, with no specific access permissions to content files or may grant default access permission to all files in the shared directory, to all associated accessors. For each content file, in the shared directory, access permission may be granted to at least one associated accessor - step 606, or leave access uniquely to its contributor if content file is exclusive. Furthermore, for each associated accessor, with granted access permission to any content file in the shared directory, the content file may be presented for viewing - step 608. Referring now to the flowchart of Figs. 7A-B, showing various selected actions are illustrated of a method for providing general personalized presentation, followed with an example. The method of Figs 7A-B is implemented by a data processing device, such as the accessor devices 106, 108 and 110 of Fig. 1, interacting with a server of a remote machine (not shown). The method of Fig. 7A may include obtaining a selection of files, from a shared directory, with access permission to the associated accessor - step 702A. Each file of the selected set may be provided a personalized score manually or automatically - step 704A. The personalized score, may be assigned according to the metadata information stored in the associated profile of a selected file, or may fetch additional personalized information stored on the server. The prioritized content list, by personal score, may create a possible presentation - step 706 A. The personalized presentation may be used for immediate viewing, on the accessor device or stored remotely on the server for later viewing.

The personalized score may be dependent on personal factors such as age, sex, profession and the like as well as file-related factors such as frequency or duration of viewing the file or similar files or the like. Furthermore, the personalized score may additionally or alternatively depend upon factors relating to factors relating to the accessor' s characteristics of the access to other files, or to the strength of connection to other accessors.

It is noted that the personalized presentation may possibly be presented in different possible forms according to standards of graphical user interface or the like. Thus, even if they have access to the same set of files, different accessors may be provided with different presentations of the same content, each personalized to suit individual preferences. Optionally, the personalized presentation may be stored locally on the accessor device.

The example of Fig. 7B includes obtaining a template with content fields having a plurality of prominence level - step 702B. Accordingly, the population of content fields is such that high scoring content is assigned to field having high prominence level.

It is noted that prominence level may be determined by size, shape, position, color or the like. By way of example, reference is now made to Fig. 7C illustrating a possible user presentation template 720 for use in presenting a personalized presentation of content to an accessor on an accessor device such as a communication device 700. The template 720 includes a title field 722, a first prominence level field 724, a second prominence level field 726, a third prominence level field 728 and a fourth prominence level field 729. The fields may be populated differently for different accessors according to personal preferences. Accordingly, referring back to Fig. 1, a first accessor 106 may view a personalized album presentation in which FILE A, an image for example, may be presented in the first prominence level field 724, whereas for a second accessor 108 FILE A is presented in the second prominence level field 726.

Similarly, FILE C, a link to a video for example, is presented to the first accessor 106 in the third prominence level field 728, to the second accessor 108 in the first prominence level field 724 and to the third accessor 110 in the second prominence level field 726. It is particularly noted that media files may be presented as a thumbnails, moving images, text, audio prompts or otherwise as suit requirements.

Technical and scientific terms used herein should have the same meaning as commonly understood by one of ordinary skill in the art to which the disclosure pertains. Nevertheless, it is expected that during the life of a patent maturing from this application many relevant systems and methods will be developed. Accordingly, the scope of the terms such as computing unit, network, display, memory, server and the like are intended to include all such new technologies a priori.

As used herein the term "about" refers to at least ± 10 %.

The terms "comprises", "comprising", "includes", "including", "having" and their conjugates mean "including but not limited to" and indicate that the components listed are included, but not generally to the exclusion of other components. Such terms encompass the terms "consisting of and "consisting essentially of".

The phrase "consisting essentially of means that the composition or method may include additional ingredients and/or steps, but only if the additional ingredients and/or steps do not materially alter the basic and novel characteristics of the claimed composition or method.

As used herein, the singular form "a", "an" and "the" may include plural references unless the context clearly dictates otherwise. For example, the term "a compound" or "at least one compound" may include a plurality of compounds, including mixtures thereof.

The word "exemplary" is used herein to mean "serving as an example, instance or illustration". Any embodiment described as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments or to exclude the incorporation of features from other embodiments.

The word "optionally" is used herein to mean "is provided in some embodiments and not provided in other embodiments". Any particular embodiment of the disclosure may include a plurality of "optional" features unless such features conflict.

Whenever a numerical range is indicated herein, it is meant to include any cited numeral (fractional or integral) within the indicated range. The phrases "ranging/ranges between" a first indicate number and a second indicate number and "ranging/ranges from" a first indicate number "to" a second indicate number are used herein interchangeably and are meant to include the first and second indicated numbers and all the fractional and integral numerals therebetween. It should be understood, therefore, that the description in range format is merely for convenience and brevity and should not be construed as an inflexible limitation on the scope of the disclosure. Accordingly, the description of a range should be considered to have specifically disclosed all the possible subranges as well as individual numerical values within that range. For example, description of a range such as from 1 to 6 should be considered to have specifically disclosed subranges such as from 1 to 3, from 1 to 4, from 1 to 5, from 2 to 4, from 2 to 6, from 3 to 6 etc., as well as individual numbers within that range, for example, 1, 2, 3, 4, 5, and 6 as well as non-integral intermediate values. This applies regardless of the breadth of the range.

It is appreciated that certain features of the disclosure, which are, for clarity, described in the context of separate embodiments, may also be provided in combination in a single embodiment. Conversely, various features of the disclosure, which are, for brevity, described in the context of a single embodiment, may also be provided separately or in any suitable subcombination or as suitable in any other described embodiment of the disclosure. Certain features described in the context of various embodiments are not to be considered essential features of those embodiments, unless the embodiment is inoperative without those elements. Although the disclosure has been described in conjunction with specific embodiments thereof, it is evident that many alternatives, modifications and variations will be apparent to those skilled in the art. Accordingly, it is intended to embrace all such alternatives, modifications and variations that fall within the spirit and broad scope of the appended claims.

All publications, patents and patent applications mentioned in this specification are herein incorporated in their entirety by reference into the specification, to the same extent as if each individual publication, patent or patent application was specifically and individually indicated to be incorporated herein by reference. In addition, citation or identification of any reference in this application shall not be construed as an admission that such reference is available as prior art to the present disclosure. To the extent that section headings are used, they should not be construed as necessarily limiting.

The scope of the disclosed subject matter is defined by the appended claims and includes both combinations and sub combinations of the various features described hereinabove as well as variations and modifications thereof, which would occur to persons skilled in the art upon reading the foregoing description.

Claims

1. A cloud-based file sharing system comprising: a file repository comprising at least one directory comprising at least one file; and at least one accessor device associated with an accessor connectable to the file repository through a cloud network.

2. The cloud-based file sharing system of claim 1 having a plurality of accessor devices, said at least one directory comprising a plurality of files, wherein a first accessor device is capable of accessing a first subset of files and a second accessor device is capable of accessing a second subset of files.

3. The cloud-based file sharing system of claim 1 wherein the file may be selected from the group consisting of graphics, picture, video, text and music files.

4. A method for populating a directory of a cloud-based file sharing system with at least one file comprising the steps of:

- assigning said at least one file located in a contributor host device to said directory;

- obtaining at least one contact detail regarding at least one contact;

- assigning an access right to said at least one contact with regard to said at least one file;

- uploading said directory and said at least one file from said contributor host device to a server database; and

- sending a notification to said at least one contact.

5. The method of claim 4 further comprising the steps of:

- defining a set of associated metadata comprising profiling features for said at least one file;

- searching the contributor host device for one or more host additional files having at least one shared profiling feature; and

- suggesting host additional files to add to the directory.

6. The method of claim 5 further comprising the steps of:

- selecting at least one host additional file to assign to said directory; - uploading said at least one host additional file from said contributor host device to said server database; and

- sending an additional notification to said at least one contact.

7. The method of any one of claims 4-6 further comprising the steps of:

- a contact host device receiving said notification;

- searching the contact host device for one or more additional files having at least one shared profiling feature with said at least one file; and

-suggesting contact additional files to add to the directory.

8. The method of claim 7 further comprising the steps of:

- selecting at least one of said contact additional files to assign to said directory; and

- uploading said at least one contact additional file from said contact host device to said server database; and

- sending an additional notification to said at least one contact.

9. The method of claim 5 wherein the step of defining a set of associated metadata comprising profiling features comprises the substeps of:

- identifying at least one profiling feature selected from the group consisting of:

- a timestamp;

- a location stamp; and

- at least one content within file;

- identifying access permission;

- identifying sharing permission; and

-associating to said file a metadata information block comprising said profiling features.

10. The method of claim 5 wherein the step of defining a set of associated metadata comprising profiling features comprises the substeps of:

- identifying the profiling features incorporated within metadata associated with a plurality of accessors having access to the directory; - calculating a score for profiling features, with profiling features highly represented among said plurality of accessors having a high score; and

- including the high- scoring profiling features as the search parameters for additional files.

11. The method of claim 4 wherein the step of assigning said access right comprises the substeps of:

- prompting said contributor to designate the file as private; and

- if the file is designated as not private, prompting said contributor to designate the file as exclusive; wherein:

- if the file is designated as private, then only the contributor is granted access rights to the file;

- if the file is designated as not private and as not exclusive, then all associates with the directory is granted access rights to the file;

- if the file is designated as not private and as exclusive, then the contributor is prompted to selected associates, and only the selected associates are granted access rights to the file.

12. The method of claim 4 further comprising the step of assigning a sharing right to said at least one contact with regard to said at least one file, the step comprising the substeps of:

- prompting said contributor to designate the file as private; and

- if the file is designated as private, then only the contributor is granted sharing rights to the file;

- if the file is designated as not private and as not exclusive, then all associates associated with the directory are granted sharing rights to the file; and

- if the file is designated as not private and as exclusive, then the contributor is prompted to selected associates, and only the selected associates are granted sharing rights to the file.

13. A method of associating a directory to a plurality of accessors, comprising the steps of:

- populating said directory with a plurality of files; - associating said plurality of accessors with said directory;

- granting access to at least one of said plurality of files populated in said directory to at least one of said plurality of accessors;

- presenting to at least one accessor one or more files for which said at least one accessor has been granted access.

14. The method of claim 13 further comprising the step of:

- providing a personalized score for each of said plurality of files for which said at least one accessor has been granted access;

- prioritizing the presenting of each of said plurality of files to said at least one accessor based on said personalized score.

15. The method of claim 14 where the presenting of said one or more files is produced in a plurality of content fields having different prominence levels, and wherein a file with a high personalized score is placed in a content field having a high prominence level.

16. A method of identifying one or more accessors, comprising the steps of:

- identifying accessors with access to common files;

- identifying accessors with access to common directories;

- identifying accessors with access to files with similar file metadata;

- identifying accessors with similar accessor metadata;

- determining a link score for the identified accessors.

17. The method of claim 16 wherein said determining a link score comprises obtaining a linkage function and applying said linkage function to said one or more identified accessors.

18. A computer readable medium having instructions thereon, which, when executed by a processor causes the processor to perform operations comprising the methods of any one of claims 4-16.

19. A system comprising: at least one processor, at least one display device, and at least one computer readable medium coupled to the processor, said computer readable medium comprising instructions, which, when executed by a processor causes the processor to perform operations comprising the methods of any one of claims 4-16.

20. A computer readable medium having computer executable instructions for performing operations comprising the methods of any one of claims 4-17.