Data

Tools

Indexes

Applications

Experiments

Open Source Science

esha-nb-iot-v6

https://github.com/hafizkakar/esha-nb-iot-v6

Science Score: 44.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • ✓
    CITATION.cff file
    Found CITATION.cff file
  • ✓
    codemeta.json file
    Found codemeta.json file
  • ✓
    .zenodo.json file
    Found .zenodo.json file
  • ○
    DOI references
  • ○
    Academic publication links
  • ○
    Academic email domains
  • ○
    Institutional organization owner
  • ○
    JOSS paper metadata
  • ○
    Scientific vocabulary similarity
    Low similarity (7.8%) to scientific vocabulary
Last synced: 6 months ago · JSON representation ·

Repository

Basic Info
  • Host: GitHub
  • Owner: hafizkakar
  • Language: Python
  • Default Branch: main
  • Size: 2.1 MB
Statistics
  • Stars: 0
  • Watchers: 1
  • Forks: 0
  • Open Issues: 0
  • Releases: 0
Created over 1 year ago · Last pushed over 1 year ago
Metadata Files
Readme Citation

README.md

NB-IoT Hbyrid Blockchain using ECM-SHA256 Algorithm

Unique ID Generation • Device Join Procedure • Device Transactions

Motivation

The goal of this study is to further save energy consumption by NB-IoT Framework in "Enabling secure lightweight mobile Narrowband Internet of Things (NB-IoT) applications using blockchain" by using the ECM-SHA256 algorithm.

SHA-256

SHA-256 algorithm access message data from memory banks sequentially, as shown in the above figure.

ECM-SHA256

ECM-SHA256 algorithm reduces the computational power required for running the SHA-256 algorithm by access message data from memory banks in parallel rather than sequentially, as shown in the above figure.

ESHA-NB-IOT Framework

  • NB-IOT: devices are resource constrained with less computational power, low memory, storage and bandwidth. Therefore, devices only store hash of transactions initiated by them in an array as linear hash chain. By design, NB-IoT devices will have device address and reputation (default 4).
  • BASE STATIONS: Transactions initiated by NB-IoT devices can only be authorized by base station using non-interactive ZKP and then added to blockchain. The base station dynamically partitions its memory to store device transactions in a merkle tree and allocate the rest to store individual device transactions in a linear hash chain for faster access.
  • ETHEREUM BLOCKCHAIN: NB-IoT Devices and base stations are connected through ethereum blockchain using Remix IDE Smart Contracts. Non-interactive ZKP (HMAC) is used as consensus algorithm for block approval.
  • AUTHENTICATION SERVER: The only responsibility of the authentication server is to authenticate NB-IoT devices using unique ID allocated to the device.
  • DATA SERVER: is responsible for issuing Unique ID to NB-IoT devices.
  • IPFS (Inter Planetary File System): connects base stations to provide decentralised data storage and sharing.

bash Non-Interactive Zero-Knowledge Proof: The prover verifies that it knows secret information without revealing what that information is. In digital signatures, prover can demonstrate knowledge of private key associated with public key, without revealing the private key itself.

Unique ID Generation

  • For anonymity, when NB-IoT device joins a new cell, the data server issues a 'New Unique ID' and 'Encryption Secret' to the device after authentication.
  • The Unique ID is used as identifier in blockchain.
  • IoT Devices are assigned ‘Device Address’ as permanent ID by the Data Server when they join blockchain for the first time.
  • ECM-SHA256 implementation highlighted in blue.

Seed = Old Unique ID | Encryption Secret | Nonce
Unique ID = UUID(random.getrandbits(Seed)



IoT Client bash $ python IoTClient.py Terminal Output ```bash Sent tuple to Authentication Server (A): ('192.168.1.71', 1001) - ('NReq', '0x000000000000000a', '6148bf32701b7ddd20a1e7c4b4c052f3', '1721519301')

Received tuple from Authentication Server (A): ('192.168.1.71', 1001) - ('c718faeefcd166b2c1e90f0e08888c6d', '1721519280', '68AFF4353B8317BE24CA6096F19EA95D80DD992BA5F1E0C3F60C296EEE304BB3', '0BD471F807062F5CDA968C3CE14A00368AFE6939B63C985ABDE8A20E5CC93114')

Sent tuple to Data Server (B): ('192.168.1.71', 2002) - ('IDReq', '6', '0x000000000000000a', 'D1CDFB53D3FBD31372A5708DB39B7525AA8D8E0277C1A0BBAEF4589AF237A3D6', '6148bf32701b7ddd20a1e7c4b4c052f3', '1721519280', 'c718faeefcd166b2c1e90f0e08888c6d', '0BD471F807062F5CDA968C3CE14A00368AFE6939B63C985ABDE8A20E5CC93114')

Received tuple from Data Server (B): ('192.168.1.71', 2002) - ('0x00000000000000aa', '7a8253502d40e501662c91eb6c7e162b', '1721519264')

New Unique ID received from Data Server = 0x00000000000000aa

```

Authentication Server bash $ python AuthenticationServer.py Terminal Output ```bash Received tuple from IoT (C): ('192.168.1.253', 54044): ('NReq', '0x000000000000000a', '6148bf32701b7ddd20a1e7c4b4c052f3', '1721519301')

Sent tuple to IoT (C): ('192.168.1.253', 54044) - ('c718faeefcd166b2c1e90f0e08888c6d', '1721519280', '68AFF4353B8317BE24CA6096F19EA95D80DD992BA5F1E0C3F60C296EEE304BB3', '0BD471F807062F5CDA968C3CE14A00368AFE6939B63C985ABDE8A20E5CC93114')

Sent tuple to Data Server (B): ('192.168.1.71', 2002) - ('0x000000000000000a', 'c718faeefcd166b2c1e90f0e08888c6d', '1721519301', '1721519280', '0BD471F807062F5CDA968C3CE14A00368AFE6939B63C985ABDE8A20E5CC93114')

```

Data Server bash $ python Dataserver.py Terminal Output ```bash Received tuple from Authentication Server (A): ('192.168.1.71', 1001): ('0x000000000000000a', 'c718faeefcd166b2c1e90f0e08888c6d', '1721519301', '1721519280', '0BD471F807062F5CDA968C3CE14A00368AFE6939B63C985ABDE8A20E5CC93114')

Received tuple from IoT (C): ('192.168.1.253', 54044): ('IDReq', '6', '0x000000000000000a', 'D1CDFB53D3FBD31372A5708DB39B7525AA8D8E0277C1A0BBAEF4589AF237A3D6', '6148bf32701b7ddd20a1e7c4b4c052f3', '1721519280', 'c718faeefcd166b2c1e90f0e08888c6d', '0BD471F807062F5CDA968C3CE14A00368AFE6939B63C985ABDE8A20E5CC93114')

Sent tuple to IoT (C): ('192.168.1.253', 54044) - ('0x00000000000000aa', '7a8253502d40e501662c91eb6c7e162b', '1721519264')

```

Unique ID Generation - Statistical Summary (SHA-256 Sequential vs Parallel)

This section provides the statistical summary of the energy measurements and duration using pyRAPL (Python Running Average Power Limit).

| SEQUENTIAL | CPU | DRAM | Duration | |-----------|----------|----------|-------------| | IoT Client | 774842 | 197058 | 584787 | | Authentication Server | 1506117 | 862443 | 585755| | Data Server | 1505859 | 862154 | 585535 |

| PARALLEL | CPU | DRAM | Duration | |-----------|----------|----------|-------------| | IoT Client | 750888 | 188364 | 556404 | | Authentication Server | 1436314 | 822456 | 557470 | | Data Server | 1436441 | 822411 | 557417 |

| PERCENTAGE % | CPU | DRAM | Duration | |--------------------|---------|---------|----------| | IoT Client | 3.1% | 4.4% | 4.9% | | Authentication Server | 4.6% | 4.6% | 4.8% | | Data Server | 4.6% | 4.6% | 4.8% |

Measurement Units - Energy Units (CPU, DRAM) = Microjoules - Duration = Microseconds


Device Join Procedure

  • (1-2) Authentication Server authenticates the NB-IoT device using its existing Unique ID.
  • (3) After authentication, NB-IoT device sends 'Leave Request' to Home Base Station along with address of Visiting Base Station.
  • (4-6) Home Base Station 'Approve' the request. Then, Base Station 'Saves' deployed Smart Contract along with transactions recorded in JSON format in Remix IDE. The file is then uploaded to Inter Planetary File System (IPFS) and resulting File Hash is shared with Visiting Base Station.
  • (7-10) NB-IoT sends 'Join Request' to Visiting Base Station. Visiting Base Station downloads JSON file from IPFS, verifies IoT device using Unique ID and then sends 'New Unique ID' and 'Encryption Secret' to NB-IoT device. The New Unique ID and Encryption Secret is then used by Non-Interactive ZKP for block approval.
  • ECM-SHA256 implementation highlighted in blue.

IoT Client bash $ python IoTClient.py Terminal Output ```bash Sent tuple to Authentication Server (A) ('192.168.1.71', 1001) - ('NReq', '0x000000000000000a', '8e6e0aa746ccc38b3016f5b61bc5d48e', '1721520743', 'F2A2C96B931407AD2E6CC2D0348D76B8F98B6811D6F34A28BF664A17A8B2EAF5')

Received tuple from Authentication Server (A) ('192.168.1.71', 1001) - ('be8064004b62b6310e55f85600e4787e', '1721520729', '36F738E997A320DD386EBB8641E837C9250754848B4A6498193DBCBB5F325CC7')

Sent tuple to Home Base Station (D) ('192.168.1.71', 3003) - ('LReq', '8e6e0aa746ccc38b3016f5b61bc5d48e', '1721520743', '0x000000000000000a', '0x00000000000000bb')

Received tuple from Home Base Station (D) ('192.168.1.71', 3003) - ('RApp', 'eead184328e6c99f48b5115dc6ec3d21', '122F3DADE9419B3779DFE10A58C822664BEAF50A34117BED138B8DA60AB4637B')

Sent tuple to Visiting Base Station (B) ('192.168.1.71', 2002) - ('JReq', '6', '0x000000000000000a', 'F2A2C96B931407AD2E6CC2D0348D76B8F98B6811D6F34A28BF664A17A8B2EAF5', '8e6e0aa746ccc38b3016f5b61bc5d48e', '1721520743', '1721520729', 'F3C3732DCAF39CE4D5324A6180976D644C9158885E44FE6B685918B9D2F430DF')

Received tuple from Visiting Base Station (B) ('192.168.1.71', 2002) - ('RApp', '0x00000000000000aa', '0x0000000000000011', 'f0f9df22c2ac17ccb62abfb4d82a039c', '1721520697')

New Unique ID received from Visiting Base Station (B) = 0x00000000000000aa

```

Authentication Server bash $ python Authentication.py Terminal Output ```bash Received tuple from IoT (C): ('192.168.1.253', 50335): ('NReq', '0x000000000000000a', '8e6e0aa746ccc38b3016f5b61bc5d48e', '1721520743', 'F2A2C96B931407AD2E6CC2D0348D76B8F98B6811D6F34A28BF664A17A8B2EAF5')

Sent tuple to IoT (C): ('192.168.1.71', 50335) - ('be8064004b62b6310e55f85600e4787e', '1721520729', '36F738E997A320DD386EBB8641E837C9250754848B4A6498193DBCBB5F325CC7')

Sent tuple to Visiting Base Station Server (B): ('192.168.1.71', 2002) - ('LReq', 'A0E872F7AAF4D52155AF4AA6715F04B5B74A810710DA8F21CF378DAB20EF62D2', '0x000000000000000a', 'be8064004b62b6310e55f85600e4787e', '8e6e0aa746ccc38b3016f5b61bc5d48e')

```

Home Base Station bash $ python HomeBS.py Terminal Output ```bash Received tuple from IoT (C): ('192.168.1.253', 50335): ('LReq', '8e6e0aa746ccc38b3016f5b61bc5d48e', '1721520743', '0x000000000000000a', '0x00000000000000bb')

Sent tuple to IoT (C): ('192.168.1.71', 50335) - ('RApp', 'eead184328e6c99f48b5115dc6ec3d21', '122F3DADE9419B3779DFE10A58C822664BEAF50A34117BED138B8DA60AB4637B')

```

Visiting Base Station bash $ python VisitingBS.py Terminal Output ```bash Received tuple from Authentication Server (A): ('192.168.1.71', 1001): ('LReq', 'A0E872F7AAF4D52155AF4AA6715F04B5B74A810710DA8F21CF378DAB20EF62D2', '0x000000000000000a', 'be8064004b62b6310e55f85600e4787e', '8e6e0aa746ccc38b3016f5b61bc5d48e')

Received tuple from IoT (C): ('192.168.1.253', 50335): ('JReq', '6', '0x000000000000000a', 'F2A2C96B931407AD2E6CC2D0348D76B8F98B6811D6F34A28BF664A17A8B2EAF5', '8e6e0aa746ccc38b3016f5b61bc5d48e', '1721520743', '1721520729', 'F3C3732DCAF39CE4D5324A6180976D644C9158885E44FE6B685918B9D2F430DF')

Sent tuple to IoT (C): ('192.168.1.253', 50335) - ('RApp', '0x00000000000000aa', '0x0000000000000011', 'f0f9df22c2ac17ccb62abfb4d82a039c', '1721520697')

```

Device Join Procedure - Statistical Summary (SHA-256 Sequential vs Parallel)

This section provides the statistical summary of the energy measurements and duration using pyRAPL (Python Running Average Power Limit).

| SEQUENTIAL | CPU | DRAM | Duration | |-----------|----------|----------|-------------| | IoT Client | 1316593 | 328564 | 995397 | | Authentication Server | 2442085 | 1442671 |998613 | | Home Base Station | 2438706 | 1441211 | 997650 | | Visiting Base Station | 2435663 | 1439906 | 996787|

| PARALLEL | CPU | DRAM | Duration | |-----------|----------|----------|-------------| | IoT Client | 1299641 | 326426 | 980816 | | Authentication Server | 2411952 | 1421583 |983750| | Home Base Station | 2408627 | 1420214 | 982851 | | Visiting Base Station | 2404560 | 1418571 | 981790 |

| PERCENTAGE % | CPU | DRAM | Duration | |--------------------|---------|---------|----------| | IoT Client | 1.3% | 0.7% | 1.5% | Authentication Server | 1.2% | 1.5% | 1.5% | | Home Base Station | 1.2% | 1.5% | 1.5% | | Visiting Base Station | 1.3% | 1.5% | 1.5% |

Measurement Units - Energy Units (CPU, DRAM) = Microjoules

- Duration = Microseconds


Device Transactions

  • Devices generate SHA256 hash using Timestamp, nonce, unique ID, reputation, message and Encryption Secret.
  • Resulting hash is sent to Base Station along with Timestamp, nonce, unique ID, reputation, message.
  • Base station will generate and compare its hash with received hash and on verification will append the transaction to its merkle tree and linear hash chain.
  • ECM-SHA256 implementation highlighted in blue.

IoT Client bash $ python IoTClient.py Terminal Output ```bash Sent tuple to Home Base Station (D) ('192.168.1.71', 3003) - ('AReq', '0x00000000000000aa', 4, 'IoT Data', 'FCC7B19574CD8A483CF4CB64705C6971530A3BE70CE8229469DE92AD08E92D0C', '063913a9bcd99ec0815b9434e99e7722', '1721523291')

Transaction 1 Approved, Device reputation incremented: 5, transaction hash from Base Station (D): ('192.168.1.71', 3003) - 0x60d14431721375ed7347df1c21f2fee9a3bbefbb39ea470b06a614b7e1d65419

Sent tuple to Home Base Station (D) ('192.168.1.71', 3003) - ('AReq', '0x00000000000000aa', 5, 'IoT Data', '37A9954F77FC7F026BDC1857A4B1B87F211274EFB6F2082EF5CDC60DC0B63E04', '063913a9bcd99ec0815b9434e99e7722', '1721523291')

Transaction 2 Approved, Device reputation incremented: 6, transaction hash from Base Station (D): ('192.168.1.71', 3003) - 0x60d14431721375ed7347df1c21f2fee9a3bbefbb39ea470b06a614b7e1d65419

Sent tuple to Home Base Station (D) ('192.168.1.71', 3003) - ('AReq', '0x00000000000000aa', 6, 'IoT Data', '12BEF72552682A93013650E5406D3D6A1E044424EB3FC9D38DDAFAC747870462', '063913a9bcd99ec0815b9434e99e7722', '1721523291')

Transaction 3 Approved, Device reputation incremented: 7, transaction hash from Base Station (D): ('192.168.1.71', 3003) - 0x60d14431721375ed7347df1c21f2fee9a3bbefbb39ea470b06a614b7e1d65419

Sent tuple to Home Base Station (D) ('192.168.1.71', 3003) - ('AReq', '0x00000000000000aa', 7, 'IoT Data', '449DED05D72BB5D9BDA013A7CB2433F6CB2E0BC1512DE696F0F781EAAF4BFD71', '063913a9bcd99ec0815b9434e99e7722', '1721523291')

Transaction 4 Approved, Device reputation incremented: 8, transaction hash from Base Station (D): ('192.168.1.71', 3003) - 0x60d14431721375ed7347df1c21f2fee9a3bbefbb39ea470b06a614b7e1d65419

Approved Transactions in Linear Hash Chain: ['0x60d14431721375ed7347df1c21f2fee9a3bbefbb39ea470b06a614b7e1d65419', '0x60d14431721375ed7347df1c21f2fee9a3bbefbb39ea470b06a614b7e1d65419', '0x60d14431721375ed7347df1c21f2fee9a3bbefbb39ea470b06a614b7e1d65419', '0x60d14431721375ed7347df1c21f2fee9a3bbefbb39ea470b06a614b7e1d65419']

```

Base Station bash $ python BS.py Terminal Output ```bash Received tuple from IoT (C): ('192.168.1.253', 59655): ('AReq', '0x00000000000000aa', 4, 'IoT Data', 'FCC7B19574CD8A483CF4CB64705C6971530A3BE70CE8229469DE92AD08E92D0C', '063913a9bcd99ec0815b9434e99e7722', '1721523291')

Sent tuple to IoT (C): ('192.168.1.253', 59655) - ('0x60d14431721375ed7347df1c21f2fee9a3bbefbb39ea470b06a614b7e1d65419', 5)

Received tuple from IoT (C): ('192.168.1.253', 59655): ('AReq', '0x00000000000000aa', 5, 'IoT Data', '37A9954F77FC7F026BDC1857A4B1B87F211274EFB6F2082EF5CDC60DC0B63E04', '063913a9bcd99ec0815b9434e99e7722', '1721523291')

Sent tuple to IoT (C): ('192.168.1.253', 59655) - ('0x60d14431721375ed7347df1c21f2fee9a3bbefbb39ea470b06a614b7e1d65419', 6)

Received tuple from IoT (C): ('192.168.1.253', 59655): ('AReq', '0x00000000000000aa', 6, 'IoT Data', '12BEF72552682A93013650E5406D3D6A1E044424EB3FC9D38DDAFAC747870462', '063913a9bcd99ec0815b9434e99e7722', '1721523291')

Sent tuple to IoT (C): ('192.168.1.253', 59655) - ('0x60d14431721375ed7347df1c21f2fee9a3bbefbb39ea470b06a614b7e1d65419', 7)

Received tuple from IoT (C): ('192.168.1.253', 59655): ('AReq', '0x00000000000000aa', 7, 'IoT Data', '449DED05D72BB5D9BDA013A7CB2433F6CB2E0BC1512DE696F0F781EAAF4BFD71', '063913a9bcd99ec0815b9434e99e7722', '1721523291')

Sent tuple to IoT (C): ('192.168.1.253', 59655) - ('0x60d14431721375ed7347df1c21f2fee9a3bbefbb39ea470b06a614b7e1d65419', 8)

```

Device Transactions - Statistical Summary (SHA-256 Sequential vs Parallel)

This section provides the statistical summary of the energy measurements and duration using pyRAPL (Python Running Average Power Limit).

** MESSAGE SIZE = 64 bytes **

| SEQUENTIAL | CPU | DRAM | Duration | |-----------|----------|----------|-------------| | IoT Client | 506382 | 126933 | 416183 | | Base Station | 938172 | 602190 | 416900 |

| PARALLEL | CPU | DRAM | Duration | |-----------|----------|----------|-------------| | IoT Client | 492220 | 125947 | 414481 | | Base Station | 934001 | 599060 | 414430 |

| PERCENTAGE % | CPU | DRAM | Duration | |--------------------|---------|---------|----------| | IoT Client | 2.8% | 0.8% | 0.4% | | Base Station | 0.4% | 0.5% | 0.6% |

** MESSAGE SIZE = 128 bytes **

| SEQUENTIAL | CPU | DRAM | Duration | |-----------|----------|----------|-------------| | IoT Client | 521395 | 129560 | 421181 | | Base Station | 655866 | 610531 | 421630 |

| PARALLEL | CPU | DRAM | Duration | |-----------|----------|----------|-------------| | IoT Client | 498073 | 126073 | 412044| | Base Station | 640476 | 597514 | 412348 |

| PERCENTAGE % | CPU | DRAM | Duration | |--------------------|---------|---------|----------| | IoT Client | 4.5% | 2.7% | 2.2% | | Base Station | 2.3% | 2.1% | 2.2% |

** MESSAGE SIZE = 256 bytes **

| SEQUENTIAL | CPU | DRAM | Duration | |-----------|----------|----------|-------------| | IoT Client | 497560 | 127524 | 417810 | | Base Station | 942181 | 604444 | 418672 |

| PARALLEL | CPU | DRAM | Duration | |-----------|----------|----------|-------------| | IoT Client | 486206 | 126135 | 412271 | | Base Station | 929539 | 595927 | 412186 |

| PERCENTAGE % | CPU | DRAM | Duration | |--------------------|---------|---------|----------| | IoT Client | 2.3% | 1.1% | 1.3% | | Base Station | 1.3% | 1.4% | 1.5% |

** MESSAGE SIZE = 512 bytes **

| SEQUENTIAL | CPU | DRAM | Duration | |-----------|----------|----------|-------------| | IoT Client | 496230 | 129090 | 414467 | | Base Station | 950389 | 599802 | 415126 |

| PARALLEL | CPU | DRAM | Duration | |-----------|----------|----------|-------------| | IoT Client | 493296 | 128212 | 412978 | | Base Station | 936617 | 597061 | 413358 |

| PERCENTAGE % | CPU | DRAM | Duration | |--------------------|---------|---------|----------| | IoT Client | 0.6% | 0.7% | 0.4% | | Base Station | 1.4% | 0.5% | 0.4% |

** MESSAGE SIZE = 1024 bytes **

| SEQUENTIAL | CPU | DRAM | Duration | |-----------|----------|----------|-------------| | IoT Client | 508843 | 131060 | 419403 | | Base Station | 967612 | 608418 | 421241 |

| PARALLEL | CPU | DRAM | Duration | |-----------|----------|----------|-------------| | IoT Client | 501655 | 127026 | 414143 | | Base Station | 955371 | 597659 | 414166 |

| PERCENTAGE % | CPU | DRAM | Duration | |--------------------|---------|---------|----------| | IoT Client | 1.4% | 3.1% | 1.3% | | Base Station | 1.3% | 1.8% | 1.7% |

Measurement Units - Energy Units (CPU, DRAM) = Microjoules - Duration = Microseconds

Average Relative Improvement of all Modules in NB-IoT Blockchain Framework

| AVERAGE | CPU | DRAM | Duration | |--------------------|---------|---------|----------| | | 2.1% | 2.0% | 1.9% |

** INITIAL EXPERIMENTS CONDUCTED ON SINGLE SYSTEM **

| | CPU | DRAM | Duration | |--------------------|---------|---------|----------| | Average % | 19.63 | 33.14 | 36.64 |

Check Repository

Disclaimer:

This project uses original code from Washinton University Bitcoin Project by Brad conte.

NB-IoT Hbyrid Blockchain using ECM-SHA256 Algorithm

Unique ID Generation • Device Join Procedure • Device Transactions

Owner

  • Login: hafizkakar
  • Kind: user

Citation (CITATION.cff) 

# This CITATION.cff file was generated with cffinit.
# Visit https://bit.ly/cffinit to generate yours today!

cff-version: 1.2.0
title: NB-IoT Hbyrid Blockchain using ESHA-256 Algorithm
message: >-
  If you use this software, please cite it using the
  metadata from this file.
type: software
authors:
  - given-names: Hafizullah
    family-names: Kakar
    email: n01543583@unf.edu
    affiliation: University of North Florida
  - given-names: Swapnoneel
    family-names: Roy
    email: s.roy@unf.edu
    affiliation: University of North Florida
    orcid: 'https://orcid.org/0000-0003-1164-2757'
repository-code: 'https://github.com/hafizkakar/ESHA-NB-IOT-V6'
abstract: >-
  The goal of this study is to further save energy
  consumption by NB-IoT Framework in "Enabling secure
  lightweight mobile Narrowband Internet of Things (NB-IoT)
  applications using blockchain" by using the Energy
  Efficient SHA-256 (ESHA-256) algorithm.
keywords:
  - 'NB-IoT, Blockchain, SHA256, Energy Optimization'
license: Python-2.0
version: '1.0'
date-released: '2024-09-27'

GitHub Events

Total
  • Push event: 2
Last Year
  • Push event: 2