Smart Storage Service Wiki
This is the home page for 'clostore' project wiki.
The SSS service definition
SSS (Smart Storage Service) is some kind of middleware service that allows saving information from any user device on any type of remote storages in automatic mode. List of storages, storage parameters, rewriting policy and other information is determined by user (device) profile. All user profiles are stored in a database that is a part of the service. The user profile is filled in during users registration and may be changed later. As soon as some registered device becomes available in the network it connects to the service to save all required information in some remote storage that is determined by the user (device) profile. Remote storage here is any type of storages that may be found in the network (from home computers to cloud storages like Amazon S3).
The aim of the project
The aim of the project is to develop a prototype with basic functionality that shows power, flexibility and usability of the service that should show potential opportunity of the final product that will be created based on the prototype.
Architecture Assumptions
1) Storage is a network object that may permanently store information. Stored information may be accessible in the future by different users for analysis, processing and other purposes.
2) SSS may store information in different type of storages: HW servers, home PC, virtual storages, etc. Any storage that has an IP address and is available through the network may be potentially used by SSS.
3) Any network object (device) that may generate (produce) information and translate it into the IP network may use SSS to store information.
4) Information is translated from a producer to storage in secure mode.
5) Information may be encoded before to be stored. So such information is available for users that have appropriate keys.
6) Information that is stored in storage should be accessible for authorized users only.
7) Any user may register many data producer devices to use SSS. Each such device may use one or more storage to store data (based on device order, space available, rotation policy, etc.)
Architecture Scenarios
For the prototype it is planned to have several "perfect case" scenarios. The aim of these scenarios is to show basic possibilities of the product that may be interesting for potential investors. Full range of architecture’s scenarios (including error case scenarios) is planned to be developed later (based on the prototype analysis and new requirements).
1) Unlimited storage for PC (NB) or even servers.
- the user install client terminal service (CTS) on the PC (NB)
- a user register a device (PC or NB) in SSS
- SSS assign a storage (with size and rules (policy) according to the user’s request)
- CTS creates special folder (let it be “SSS” folder) on the PC’s HD.
- the user copy several files into the SSS folder
- as soon as copying is finished CTS check connection to the storage (through SSS)
- as soon as connection is available SSS move these files into the storage
- CTS create special links for each of these files inside the SSS folder.
- the user click on a link to have access to one of these file (open the file or just copy it)
The latest two steps are optional. Access to the files inside the storage may be done some other way.
2) Unlimited storage for a stream video (audio) device (video-camera).
- the user install client terminal service (CTS) on the Mobile Phone
- a user register a device (Mobile Phone) in SSS
- SSS assign a storage (with size and rules (policy) according to the user’s request)
- CTS catch video stream as soon as it appears and sent this stream to the storage (through SSS)
- if connection is not available the CTS store the stream in local buffer (HD) to sent it to the storage later (as soon as connection will be available
The latest two steps may be replaced by the first scenario to translate just video files instead of video stream (to simplify the prototype)
3) Stored information handling by users.
- a user goes to the storage (through SSS or directly)
- SSS (or storage) authenticate and authorize the user.
- user do something with the stored information (view, edit, remove, …)
The service architecture (Reference model)
