solution-strategy-architecture.tex 4.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081
  1. Various models can be used to implement secure data exchange between the users of an OSN via an add-on. The solution strategies shown below differ essentially in the question of where data is stored and how it can be found.
  2. \begin{figure}[h!]
  3. \centering
  4. \includegraphics[width=1.0\textwidth]{solution-strategy-architecture}
  5. \caption{Different architectures: a) Use of a central server to which all hybrid OSN users connect to, b) Creation of a P2P network among the users for data exchange.}
  6. \label{fig:solution-strategy-architecture}
  7. \end{figure}
  8. One possibility is to use an extra infrastructure to store the data, as shown in Figure \ref{fig:solution-strategy-architecture}.a. Additional servers are used to store and distribute the private data to be protected. This has the advantage that the data is always available and there are no dependencies to other hybrid OSN users. Furthermore, resources must only be available centrally and not locally for every user. At the central location the data can be indexed and specifically queried. However, it is problematic that one or more such servers must be operated and maintained. In principle, the question of the operators must be clarified, because the infrastructure must function reliably. An architecture based on this proposal was used by FaceCloak.
  9. In contrast, a decentralized or distributed solution strategy would create a network among users of the hybrid application. This strategy is depicted in Figure \ref{fig:solution-strategy-architecture}.b. No extra infrastructure would have to be operated. The users would then have a classic peer role. With this model, solutions must be found for how data is always available and can be found, even if a user is temporarily or permanently offline. Furthermore, the resources on the end devices are limited, so that effective, economical solutions are needed. Another challenge is the addressing of peers. Since they typically do not have a static IP address, but the IP address changes frequently, solutions must be found for accessibility. Since there is no central, global index, finding data is even more difficult.
  10. An interim solution is also conceivable, in which an existing infrastructure, e.g. an already existing P2P network or the block chain, is used for storing and exchanging data. Since no influence can be exerted on an existing infrastructure, its use entails further restrictions and potential risks.
  11. The advantages and disadvantages of the different strategies are listed in Table \ref{tab:solution-strategy-architecture-comparison} below.
  12. % Own infrastructure
  13. \newcommand{\advantageoi}{\begin{minipage} [t] {0.3\textwidth}
  14. \begin{itemize}
  15. \item Availability of data
  16. \item Finding the data
  17. \item Resources only have to be available centrally
  18. \item No dependencies among hybrid OSN users
  19. \end{itemize}
  20. \hspace{1mm}
  21. \end{minipage}}
  22. \newcommand{\disadvantageoi}{\begin{minipage} [t] {0.3\textwidth}
  23. \begin{itemize}
  24. \item expenses
  25. \item Who operates the infrastructure?
  26. \end{itemize}
  27. \end{minipage}}
  28. % Own network
  29. \newcommand{\advantageon}{\begin{minipage} [t] {0.3\textwidth}
  30. \begin{itemize}
  31. \item Resources scale with increasing number of users
  32. \end{itemize}
  33. \end{minipage}}
  34. \newcommand{\disadvantageon}{\begin{minipage} [t] {0.3\textwidth}
  35. \begin{itemize}
  36. \item Availability of data
  37. \item Finding the data
  38. \item Addressing the peers
  39. \item Local resources limited
  40. \end{itemize}
  41. \hspace{1mm}
  42. \end{minipage}}
  43. % External infrastructure
  44. \newcommand{\advantageei}{\begin{minipage} [t] {0.3\textwidth}
  45. \begin{itemize}
  46. \item Ideally no costs
  47. \item Resources are provided by the external infrastructure
  48. \end{itemize}
  49. \end{minipage}}
  50. \newcommand{\disadvantageei}{\begin{minipage} [t] {0.3\textwidth}
  51. \begin{itemize}
  52. \item No influence on future development
  53. \item Dependence on infrastructure entails risks
  54. \end{itemize}
  55. \hspace{1mm}
  56. \end{minipage}}
  57. \begin{table}[h!]
  58. \centering
  59. \begin{tabular}{l|l|l|}
  60. \cline{2-3}
  61. & \textbf{Advantages} & \textbf{Disadvantages} \\ \hline
  62. \multicolumn{1}{|l|}{\textbf{\begin{tabular}[c]{@{}l@{}}Own infrastructure\\ (centralized)\end{tabular}}} & \advantageoi & \disadvantageoi \\ \hline
  63. \multicolumn{1}{|l|}{\textbf{\begin{tabular}[c]{@{}l@{}}Own network\\ (decentralized/distributed)\end{tabular}}} & \advantageon & \disadvantageon \\ \hline
  64. \multicolumn{1}{|l|}{\textbf{External infrastructure}} & \advantageei & \disadvantageei \\ \hline
  65. \end{tabular}
  66. \caption{Advantages and disadvantages of the different solution strategies for the hybrid OSN architecture.}
  67. \label{tab:solution-strategy-architecture-comparison}
  68. \end{table}