# Insights into the Issue of Deploying a Private LoRaWAN
## 4 Experimental and Analytical Results
### Deployment Ease Evaluation
#### 4.3.2 Methodology of Deployment  
The public and the private network should follow a certain methodology for deployment. However, our experiences show that these methodologies slightly differ from each other. This chapter introduces a summary of deployment methodology for both private and public networks based on our best practice. \(\bullet\)**Decision- making**  
1. Estimate the size of the network (geographic area, number of gateways for a private case, number of nodes, density of nodes), desired service parameters (availability, throughput, type of communication, latency, communication frequency), and desired additional services (such as localization service presence). 2. Determine the possible future growth of the network or the network requirements. In addition, determine the possible future growth of the environment (i.e., new shopping areas, industrial complexes, and other noise-generating elements). 3. Analyze the feasibility of handling these requirements and future needs by LoRaWAN accounting for frequency regulations and technology limitations (check the availability of desired devices for the selected application). Decide whether the LoRaWAN technology is suitable for the selected use case. If possible, make a cost-efficiency analysis for LoRaWAN and other technologies (include the cost of development if end-devices are not available). 4. Use tester device(s) to characterize the signal quality of the public service from the most remote and difficult points (ask for an exact frequency plan of the network service provider). Discuss the possibilities of service-level agreement (SLA) with the public operator. Based on the results, selected parameters, and cost-efficiency, decide whether to go for either the private or the public network. \begin{table}
\begin{tabular}{p{142.3 pt} p{284.5 pt}} \hline \hline
**Parameter** & **Description** \\ \hline \multirow{6}{*}{\(C_{\text{fee}}\)} & In the public network, there will be regular fees based on the number of devices and the number of messages. Though the private network has no device or message fees, the fee for the back-end (LoRaWAN server) needs to be considered. Moreover, the gateways need to be connected via a transport technology such as cellular or Ethernet. For this reason, there might be additional costs for transport services (connecting the gateways). Further, this item also includes regular fees such as software licenses, software updates, and paid support. \\ \hline \multirow{6}{*}{\(C_{\text{enr}}\)} & The price for energy consumption. The public network mostly contains only end-devices which are often powered by batteries (devices powered by power network should be included here). However, the private network’s energy consumption costs must include the cooling system energy costs as well as main servers, gateways, and other devices used for the LoRaWAN infrastructure. Moreover, this part should also include battery exchange, which occurs in the use cases with a higher frequency of messages, where batteries last only several years. \\ \hline \multirow{2}{*}{\(C_{\text{rent1}}\)} & These are the rents for roofs or pillars for antennas, which are necessary in the private networks (large-scale private applications only). \\ \hline \multirow{2}{*}{\(C_{\text{rent2}}\)} & Second renting part, where rented parts of the infrastructure might be included (again, mostly in the large-scale private applications only). \\ \hline \multirow{2}{*}{\(C_{\text{ope-oth}}\)} & Other operational costs such as material costs, insurance, surveillance, training, taxes, salaries, depreciation, and others. \\ \hline \hline \end{tabular} Note: All the costs must be computed for one whole year.  
\end{table} 
Table 6: The list of items constituting OPEX. \(\bullet\)**Private Network**  
1. Estimation of the network coverage should be computed via simulation tools, i.e., Radio Mobile.