## 3 Methodology  
Our proposed methodology consist of the design of the framework modules, working of the system model, and the proposed algorithm. These are explained in steps in the following section. Moreover, our system model consists of three layers, namely, the IoT-enabled industrial layer, the blockchain edge layer, and the user layer. These are discussed thoroughly in the subsections of the methodology. Moreover, the proposed framework consist of the following phases in order to process a user request:  
1. Registration Phase: In this phase, registration of data center full node is performed securely in offline mode by trusted registration authority. In addition, light node, i.e., sensor node, is registered using a zero knowledge proof protocol. This protocol authenticates two parties without revealing any secret identity or information. In this approach, one party becomes the challenger and the other party becomes the prover. 2. Verification Phase: In this phase, \(\square\)P is initiated for verification from the light node end. With the receiving information from inputs, all possible values are found correct using the \(\blacksquare\)P and \(\blacksquare\)\(\blackminus\)\(\blackminus\)\(\blackminus\)\(\blackminus\)\(\blackminus\)\(\blackminus\)\(\blackminus\)\(\blackminus\)\(\blacksquare\) is computed at the light node end to maintain the difficulty level by adding the value (z). The value z is computed using large prime value (I) and corresponding generator (\(\blacksquare\)). In this scenario, it becomes the prover and (\(\blackminus\)) becomes the verifier. 3. Validation and Block Creation Phase: If the data becomes registered, the joining of the blockchain process takes place. These are the steps involved in block creation and validation:
4. At first step, key value pair (P Bkj, P Rkj ) is created, where P Bkj is identified as a public key and P Rkj is identified as a private key of \(j\)th light node. 5. Furthermore, the work of registration is initiated. 6. The creates a signature and forward to respective nodes for its validation. \begin{table}
\begin{tabular}{l l l l l l l} \hline \hline
**Technique/Technology** & **Reference** & **Scope (Shape/Size)** & **Scale (Number of People)** & **Privacy Issues** & **Sampling Time** & **Accuracy** \\ \hline Access Control & [1] & NA & 18 & Yes & Yes & 80\% \\  & [26] & 60 & NA & Yes & Yes & 80\% \\  & [8] & 250 & NA & Yes & Yes & 80\% \\  & [10] & 100 & NA & Yes & NA & 92\% \\  & [28] & 100 & 8 & Yes & Yes & NA \\ Access Control Types & [23] & 50 & 1 & No & Yes & NA \\  & [3] & NA & 1 & No & NA & NA \\  & [28] & NA & 14 & No & yes & 86\% \\  & [9] & NA & 1 & No & Yes & 75\% \\ Framework & [32] & 100 & 2 & No & yes & NA \\  & [10] & NA & 150 & No & NA & 90\% \\ Security & [11] & 50 & 1 & Yes & yes & 93\% \\  & [18] & 200 & NA & Yes & yes & 79\% \\  & [15] & 100 & NA & Yes & No s & NA \\  & [17] & 50 & 6 & Yes & No s & 60\% \\  & [21] & 100 & 30 & Yes & NA & 91\% \\ Data Storage & [20] & NA & 45 & Yes & Yes & 70\% \\  & [14] & NA & 4 & No & Yes & 80\% \\  & [18] & 100 & 4 & No & Yes & NA \\  & [43] & 40 & 9 & No & Yes & 80\% \\  & [19] & 200 & 23 & No & NA & NA \\  & [26] & 100 & 1 & No & NA & 70\% \\  & [25] & 50 & 3 & No & Yes & 80\% \\  & [32] & 150 & 3 & No & Yes & 85\% \\  & [34] & NA & 3 The access control policies validates the signature. Once the signature matches successfully, then the client send request of the joining network uses the credential P Bkj. * The security smart contracts send the validation request to the peer nodes (N-p) for validation of location of user. * The peer nodes (N-p) validate the location of nodes using smart contracts with timestamp recorded by smart contracts in blockchain according to the latitude and longitude. * Once it is verified, then True/False acknowledgment is sent back to the corresponding node. * For True status, a new block (Bj) is generated and appended into the blockchain network with credential P B-k-j. * Data generation and block updating: This phase describes the process of data creation by (\(L_{N}\)).