## 5 Technical Architecture of the Framework  
The IBBA framework is an amalgamation of disparate technologies, network protocols, connectivity, infrastructure, software, and deployment mechanisms. In general, the framework envisages a rollout of a food safety process aligned to five modules in the realm of food production (ex. harvesting, processing, and transportation) and distribution. Table 2 provides a summary of the five modules of IBBA. Figure 5 depicts the abstract representation of the IBBA framework in an implementation scenario--use case 1. The below section discusses a simple use case--use case 1--of the IBBA framework rollout to monitor food safety at a dairy farm:  
1. [label=(0)]
2. Suitable IoT sensors are designed or identified to gather information required to identify microbial contamination at the farm. Also, at the processing unit, IoT sensors that can detect microbial contamination either non-destructively (ex. E-nose) or through physical sampling (modules: IBBA IoT or IBBA Mobile) are identified. 3. The application logic that can process the IoT-sensed data is deployed and it is streamed to the EDGE server for further processing (modules: IBBA IoT/IBBA Mobile). 4. The EDGE server collects, collates, and aggregates the data from multiple IoT sensors and applies the AI/ML techniques to identify the \"patterns\" in the data to identify potential microbial contamination and send out alerts (module: IBBA Edge). 5. Before pushing the preprocessed/refined data to the IBBA Backbone, the EDGE server generates the hash string of the data files. The EDGE server then pushes the data file to the cloud provider along with its computed hash string to the blockchain. It \begin{table}
\begin{tabular}{p{42.7 pt} p{113.8 pt} p{113.8 pt}} \hline \hline \# & **Module** & **Description** & **Role** \\ \hline
1 & IBBA IoT & Custom hardware/software components collect and collate on-site real-time data to the edge server, ex. temperature, humidity, pH, IR spectrum data (absorption), etc. & Data Collection \\ \hline
2 & IBBA Mobile & This provides an ancillary data collection mechanism, mimics IoT device(s), and consumes information (alerts) provided by the IBBA Backbone. & Data Collection/Dissemination \\ \hline
3 & IBBA Edge & This is an on-site server used to process real-time data, apply AI/ML/DL to detect patterns, make local decisions, and aggregate data to the backbone server on the cloud. & Data Process-ing/Aggregation/Data Analysis \\ \hline
4 & IBBA Backbone & This aggregates data from all the edge locations of food processing/distribution channels, processes the data in near-real time, applies AI/ML/BL, predicts food recall scenarios, and disseminates the information to intended stakeholders. The analytics deployed on the backbone adds the value (5 th V) dimension, enabling the authorities to gain more insights and uncover the details. & Data Processing Data Dissemination \\ \hline
5 & IBBA API/ Portal & This provides extensions to external systems to access the IBBA Backbone for further local processing. & Data Processing Data Dissemination \\ \hline \hline \end{tabular}
\end{table} 
Table 2: IBBA modules. is practically impossible to alter a hash string stored on a blockchain, and thus, the data integrity of related data files on the cloud storage can be indirectly ensured. The hash string is also used for traceability of the food product source or trace forward to find where such products are in the distribution network (modules: IBBA Edge/IBBA Backbone). 5. The IBBA Backbone collates and aggregates the data from all farms/transportation channels/distribution centers/retail stores/labs and organizes them onto cloud-based HDFS. The variety of IoT sensors/systems that need to be implemented depends on the properties of food items to be transported or retained at the specific distribution centers.