|
Work item:
|
Y.DPM-alm-fra
|
|
Subject/title:
|
Functional requirements and architecture of blockchain-based activity logs management for IoT data processing and management
|
|
Status:
|
Under study
|
|
Approval process:
|
TAP
|
|
Type of work item:
|
Recommendation
|
|
Version:
|
New
|
|
Equivalent number:
|
-
|
|
Timing:
|
2024-Q4 (Medium priority)
|
|
Liaison:
|
ITU-T SG16, SG17
|
|
Supporting members:
|
China Unicom; ZTE Corporation; CICT, BUPT, CAICT China; Renmin University of China
|
|
Summary:
|
There are many platforms to process and manage same IoT data in different stages and in different areas. In traditional solutions, each of the platforms usually stores its activity logs for processing and managing IoT data (IoT DPM) into its storage separately. Those activity logs are separated and managed by the platforms respectively. Therefore, the availability and trustworthiness of those activity logs are not guaranteed. In this case, it is uneasy to trace activity logs of IoT DPM in full lifecycle for the activity logs are stored and managed by different platforms.
In order to trace activity logs of IoT DPM, different platforms may use same activity log storage and related functionalities. Activity logs management (ALM) enabled by blockchain technologies provides functionalities to manage activity logs for IoT DPM in full lifecycle across platforms. Different platforms can save activity logs for IoT data into the shared storages via the ALM for IoT DPM individually. And then when they read activity logs of IoT DPM via the ALM, they can get all the relevant activity logs of the IoT DPM in full lifecycle from the shared storages via the ALM for IoT DPM, if authorized. The ALM and the shared storages are based on blockchain technologies and can keep the activity logs un-tamped. The ALM can facilitate the platforms to store and trace activity logs of IoT DPM in full lifecycle transparently and trustworthily.
This draft new Recommendation introduces blockchain-based activity logs management for IoT data processing and management, and specifies its characteristics, functional requirements and architecture.
|
|
Comment:
|
-
|
|
Reference(s):
|
|
|
Historic references:
|
|
Contact(s):
|
|
| ITU-T A.5 justification(s): |
|
|
|
|
First registration in the WP:
2022-07-29 16:50:19
|
|
Last update:
2023-09-27 18:14:12
|
