# BDS: An Efficient Spark-Based Big Data Processing Scheme for Cloud Fog-IoT Orchestration
## 4 System Model and Methodology
### Components of the Fog-IoT Hierarchical Overlay Network and BDPS Architecture  
Our system architecture is divided into three conventional layers: the back-end, middleware, and front-end services. The three-layer architecture may be categorized as (1) the cloud layer or core (back-end), (2) the fog layer (middleware), and (3) the IoT layer (front-end). _The core or cloud layer:_ The central cloud or service tracks the active participation of BDPS process schedulers to deliver from the fog toward the cloud in a secure fashion through the SP (session password). According to the process loads at the fog-IoT network ends, the cloud sends verification and validation to the fog to start the BDPS to reduce (Algorithm 1) the extra delay overheads. The current fog sessions work to process the data allocations assigned for the allocated devices. The overall cloud-to-fog communication creates an initialization delay (e.g., session-based configured counter for packet scheduling). The fog sessions resume the work through re-scheduling (i.e., enabling BDPS) for the previous information (e.g., overloaded information at the network ends) for creates extra jamming loads. The cloud comprises a data center that acts as a reservoir and contains the logs or verified proofs for the generated BDPS scheme timings (e.g., a counter for the  
Figure 4: Overview of our developed BDPS scheme. affected processed packets). Later, the reservoir sends a code of conduct to the fog to cause a re-scheduling (i.e., in-memory-based Spark-RDD or BDPS) of synchronized processed packets within the fog-IoT orchestrations. Each renewed processed packet includes the information of the previous overloaded packets and the new super-seeded packets (i.e., BDPS-verified packets) as a hash table generation for the fog-IoT nodes. The hash table is a cloud-only mechanism or cloud-native function for assuring the process verification and validation. Thus, the developed scheme re-distributes the synchronized high-speed packets throughout the fog-IoT network ends with no loss of data with a delay efficient property. _The fog layer or middleware:_ The fog layer is equipped with a timer-based scheduled counter that acts as middleware for the cloud and IoT for super seeding (i.e., high-speed deliveries through in-memory) the extra overflow of processes or data jamming toward the IoT network ends. The fog layer establishes a Spark-RDD in-memory data accelerator (i.e., BDPS) mechanism to synchronize the processed data toward the IoT ends. The fog gathers direction from the cloud and verifies the needful (i.e., search for extra loaded data over packets using depth-first strategy) to generate the BDPS scheme for overcoming the extra user loads (i.e., data stress) across the fog-IoT ends. The BDPS scheme gathers the previous overloaded process stacks, aligns them with a counter track, and feeds them into the RAMA scheduler running or generated processes into the memory (i.e., RAM and cache for new and previous feeding sequentially) for the fast delivery of data distribution. The information-gathering procedure is performed regularly (Algorithm 1) after each process execution and verification from the cloud. The fog layer comprises a timestamp, SP (e.g., session password), which is generated if BDPS is needed to establish and track by the cloud reservoir. Furthermore, for the data load, the fog generates a counter-timer-based depth-first packet search strategy to encapsulate the loaded processes and check back for the cloud verification. After verification and validation, the fog layer starts the BDPS scheme, a mechanism for in-memory Spark-RDD data accelerator, to re-synchronize the packets (Algorithm 2) and deliver them to the respective device ends. Thus, the scheme synchronized past and newly created processes by supporting data loss avoidance by delivering it in a time-wise (i.e., high-speed process accelerators) function pattern. The fog layer also has a similar security pattern (i.e., SP) as the cloud to provide extra security for the packet schedulers.