HOSN-app/thesis/content/04-concept/solution-strategy-architecture.tex

Various models can be used to implement a secure data exchange between the users of an \ac{OSN} via an add-on. The solution strategies shown below differ primarily in the question of where data is stored and how it can be found.

\begin{figure}[h!]
	\centering
	\includegraphics[width=1.0\textwidth]{solution-strategy-architecture}
	\caption{Different architectures: a) Use of a central server to which all hybrid \ac{OSN} users connect to, b) Creation of a P2P network among the users for data exchange.}
	\label{fig:solution-strategy-architecture}
\end{figure}

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. Using additional servers has the advantage that the data is always available and there are no dependencies to other hybrid \ac{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 explicitly queried. However, the operation and maintenance of one or more such servers are problematic. 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.

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 typical 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 \ac{IP} address, but the \ac{IP} address changes frequently, solutions must be found for accessibility. Since there is no central, global index, finding data is even more difficult.

An interim solution is also conceivable, in which an existing infrastructure, e.g., an already existing \ac{P2P} network or the blockchain, is used for storing and exchanging data. Since no influence can be exerted on existing infrastructure, its use entails further restrictions and potential risks.

Table \ref{tab:solution-strategy-architecture-comparison} lists the advantages and disadvantages of the different strategies.

% Own infrastructure
\newcommand{\advantageoi}{\begin{minipage} [t] {0.3\textwidth} 
		\begin{itemize}
			\item Availability of data
			\item Finding the data
			\item Resources only have to be available centrally
			\item No dependencies among hybrid \ac{OSN} users
		\end{itemize}
		\hspace{1mm}
\end{minipage}}

\newcommand{\disadvantageoi}{\begin{minipage} [t] {0.3\textwidth} 
		\begin{itemize}
			\item Expenses
			\item Who operates the infrastructure?
			\item Compliance with legal requirements
		\end{itemize}
\end{minipage}}

% Own network
\newcommand{\advantageon}{\begin{minipage} [t] {0.3\textwidth} 
		\begin{itemize}
			\item Resources scale with increasing number of users
		\end{itemize}
\end{minipage}}

\newcommand{\disadvantageon}{\begin{minipage} [t] {0.3\textwidth} 
		\begin{itemize}
			\item Availability of data
			\item Finding the data
			\item Addressing the peers
			\item Local resources limited
		\end{itemize}
		\hspace{1mm}
\end{minipage}}

% External infrastructure
\newcommand{\advantageei}{\begin{minipage} [t] {0.3\textwidth} 
		\begin{itemize}
			\item Ideally no costs
			\item Resources are provided by the external infrastructure
		\end{itemize} 
\end{minipage}}

\newcommand{\disadvantageei}{\begin{minipage} [t] {0.3\textwidth} 
		\begin{itemize}
			\item No influence on future development
			\item Dependence on infrastructure entails risks
		\end{itemize}
		\hspace{1mm}
\end{minipage}}


\begin{table}[h!]
	\centering
	\begin{tabular}{l|l|l|}
		\cline{2-3}
		& \textbf{Advantages} & \textbf{Disadvantages} \\ \hline
		\multicolumn{1}{|l|}{\textbf{\begin{tabular}[c]{@{}l@{}}Own infrastructure\\ (centralized)\end{tabular}}}        & \advantageoi                    & \disadvantageoi                       \\ \hline
		\multicolumn{1}{|l|}{\textbf{\begin{tabular}[c]{@{}l@{}}Own network\\ (decentralized/distributed)\end{tabular}}} & \advantageon                    & \disadvantageon                       \\ \hline
		\multicolumn{1}{|l|}{\textbf{External infrastructure}}                                                           & \advantageei                    & \disadvantageei                       \\ \hline
	\end{tabular}
	\caption{Advantages and disadvantages of the different solution strategies for the hybrid \ac{OSN} architecture.}
	\label{tab:solution-strategy-architecture-comparison}
\end{table}