ETSI GS PDL 025 V1.1.1 (2025-05)

Permissioned Distributed Ledger (PDL); Wireless Consensus Network Composition and Organization

DGS/PDL-0025_wirelessCN_compo

General Information

• Status: Not Published
• Technical Committee: PDL - Permissioned Distributed Ledger
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Due Date: 02-Jun-2025
• Completion Date: 20-May-2025

Standards Content (Sample)

GROUP SPECIFICATION
Permissioned Distributed Ledger (PDL);
Wireless Consensus Network Composition and Organization
Disclaimer
The present document has been produced and approved by the Permissioned Distributed Ledger (PDL) ETSI Industry
Specification Group (ISG) and represents the views of those members who participated in this ISG.
It does not necessarily represent the views of the entire ETSI membership.

2 ETSI GS PDL 025 V1.1.1 (2025-05)

Reference
DGS/PDL-0025_wirelessCN_compo
Keywords
network, PDL, wireless
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2025.
All rights reserved.
ETSI
3 ETSI GS PDL 025 V1.1.1 (2025-05)
Contents
Intellectual Property Rights . 7
Foreword . 7
Modal verbs terminology . 7
Executive summary . 7
Introduction . 7
1 Scope . 9
2 References . 9
2.1 Normative references . 9
2.2 Informative references . 9
3 Definition of terms, symbols and abbreviations . 10
3.1 Terms . 10
3.2 Symbols . 11
3.3 Abbreviations . 11
4 Overview of Wireless Consensus Networks . 12
4.1 Introduction . 12
4.2 WCN Overall Framework . 12
4.2.1 Background . 12
4.2.2 Access network based WCN framework . 12
4.2.3 Self-organizing WCN framework . 13
4.3 WCN Applications . 13
4.3.1 Autonomous driving . 13
4.3.2 Sensor and IoT networks . 15
4.4 Relations between Composition and Organization . 15
4.4.1 Aspects . 15
4.4.2 Composition . 15
4.4.3 Organization . 16
4.4.4 Interdependence . 16
5 WCN Composition Specifications . 16
5.1 General Composition Requirements . 16
5.1.1 Introduction to Composition . 16
5.1.2 Access network based WCN components . 16
5.1.2.1 Consensus node (PDL node) . 16
5.1.2.1.1 The Primary function of a Consensus node . 16
5.1.2.1.2 Key Components of a Consensus node . 16
5.1.2.2 Access point . 16
5.1.2.3 Wireless communication infrastructure. 17
5.1.2.4 Membership service provider . 17
5.1.3 Self-organizing WCN . 17
5.1.3.1 Components of a Self-organizing WCN . 17
5.1.3.1.1 Computational resource . 17
5.1.3.1.2 Communication resource . 17
5.1.3.1.3 Storage . 17
5.1.3.1.4 Power supply . 17
5.2 Hardware Specifications . 17
5.2.1 Computational Hardware . 17
5.2.1.1 PDL node . 17
5.2.1.2 Communication node . 17
5.2.2 Communication Hardware . 17
5.2.2.1 PDL node . 17
5.2.2.2 Communication node . 18
5.2.3 Storage Hardware . 18
5.3 Functional Specifications . 18
ETSI
4 ETSI GS PDL 025 V1.1.1 (2025-05)
5.3.1 Consensus Mechanism . 18
5.3.1.1 Challenges in design of an effective consensus mechanism . 18
5.3.1.2 The Blockchain Trilemma . 18
5.3.1.3 Challenges and Trade-offs . 19
5.3.2 Security . 20
5.3.2.1 Software Security . 20
5.3.2.1.1 System and Application . 20
5.3.2.1.2 Run-time and Execution Environment . 20
5.3.2.1.3 Vulnerability Fixing . 20
5.3.2.2 Hardware Security . 20
5.4 Reliability . 20
5.4.1 Reliability of Individual Component . 20
5.4.1.1 Computation Working Conditions . 20
5.4.1.2 Communication Working Conditions . 21
5.4.1.3 Storage Working Condition . 21
5.4.2 Reliability of Systems . 22
5.4.2.1 Consensus Tolerance . 22
5.4.2.2 Crash Fault Tolerance vs. Byzantine Fault Tolerance . 22
5.4.2.3 Tolerance Analysis for Reliability . 23
6 WCN Organization Specifications . 23
6.1 General Organizational Requirement . 23
6.1.1 Introduction to organization . 23
6.1.2 Access network based WCN . 23
6.1.2.1 Group management . 23
6.1.2.2 Interface . 24
6.1.3 Self-organizing WCN . 24
6.1.3.1 Group management . 24
6.1.3.2 Interface . 24
6.2 Group Management Specifications . 24
6.2.1 State Description . 24
6.2.2 Discovering and Creating a Group . 25
6.2.2.1 For consensus nodes in access network based WCN . 25
6.2.2.2 For consensus nodes in self-organizing WCN . 25
6.2.3 Joining and Leaving a Group . 25
6.2.3.1 For consensus nodes in access network based WCN . 25
6.2.3.2 For consensus nodes in self-organizing WCN . 25
6.2.4 Modifying and Removing an Existing Group . 26
6.2.4.1 For leader nodes in access network based WCN . 26
6.2.4.2 For leader nodes in self-organizing WCN . 26
6.2.5 Contingency Group Management . 26
6.2.5.1 Access network based WCN . 26
6.2.5.2 Self-organizing WCN. 26
6.2.6 Organizational Security . 26
6.3 Interface Specifications . 27
6.3.1 Peering Interface . 27
6.3.1.1 Access network based WCN . 27
6.3.1.2 Self-organizing WCN. 27
6.3.2 Routing Interface . 27
6.3.2.1 Routing protocols . 27
6.3.2.2 Routing (RREQ) Initiation Process . 27
6.3.2.3 RREQ Handling by Intermediate Nodes . 28
6.3.2.4 Leader Node Response . 28
6.3.2.5 Direct Leader Communication . 28
6.3.2.6 Fault Tolerance Consideration . 28
6.3.3 State Synchronization Interface . 29
6.3.3.1 Leader node . 29
6.3.3.2 Follower node . 29
6.3.4 Communication Interface . 29
6.3.4.1 General . 29
6.3.4.2 Self-organizing . 29
6.3.4.3 Access Network based Organizing. 30
ETSI
5 ETSI GS PDL 025 V1.1.1 (2025-05)
6.3.5 Time Synchronization Interface . 30
6.3.5.1 General . 30
6.3.5.2 Self-organizing . 30
6.3.5.3 Access Network based Organizing. 30
7 Conclusion and Recommendation . 30
7.1 Conclusion . 30
7.2 Recommendations for the Next Step . 31
History . 32

ETSI
6 ETSI GS PDL 025 V1.1.1 (2025-05)
List of Tables
Table 1 - Performance comparison of commonly used CMs .22

List of Figures
Figure 1 - WCN framework based on access network .12
Figure 2 - WCN framework based on self-organizing networks .12
Figure 3 - Wireless distributed consensus for traffic decision.13
Figure 4 - Consensus trilemma: decentralization, scalability and security .18
Figure 5 - Routing protocol .27

ETSI
7 ETSI GS PDL 025 V1.1.1 (2025-05)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI IPR online database.
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™, LTE™ and 5G™ logo are trademarks of ETSI registered for the benefit of its Members and of the
3GPP Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of ®
the oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This Group Specification (GS) has been produced by ETSI Industry Specification Group (ISG) Permissioned
Distributed Ledger (PDL).
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
Executive summary
The present document presents the architectures and fundamentals of nodes and networks in Wireless Consensus
Network (WCN) that can benefit various public and private services. Further the present document also discusses a set
of recommendations that can together enable a PDL-based Wireless Consensus Network framework.
Introduction
Wireless Consensus Networks (WCNs) containing numerous PDL nodes can be organized to achieve consensus for
various tasks of autonomous systems in wireless environments. While some potential use cases have been discussed in
previous group reports, components such as hardware, consensus mechanisms, functions, and interfaces needed to
construct each node and an integral WCN require further investigation and discussion.
ETSI
8 ETSI GS PDL 025 V1.1.1 (2025-05)
The present document demonstrates fundamental specifications for node composition and network organization in
WCN. Such specifications serve as a general guidance for different stakeholders assisting them to better understand the
key elements required to build effective WCNs.

ETSI
9 ETSI GS PDL 025 V1.1.1 (2025-05)
1 Scope
The present document defines the services of Permissioned Distributed Ledger (PDL) platform, which enable wireless
distributed consensus for reliable industrial connected autonomous systems. The present document also outlines the
composition of wireless consensus nodes and their organizations. Furthermore, it defines a series of consensus patterns
and steps to improve reliability and enable fault tolerance.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found in the
ETSI docbox.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
Not applicable.
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long-term validity.
The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's
understanding, but are not required for conformance to the present document.
[i.1] Kim, Jung Hoon, Byung Wan Jo, Jun Ho Jo, and Do Keun Kim. 2020: "Development of an IoT-
Based Construction Worker Physiological Data Monitoring Platform at High Temperatures"
Sensors 20, no. 19: 5682.
[i.2] Resnati, Davide, Akira Goda, Gianluca Nicosia, Carmine Miccoli, Alessandro S. Spinelli, and
Christian Monzio Compagnoni: "Temperature effects in NAND flash memories: A comparison
between 2-D and 3-D arrays". IEEE Electron Device Letters 38, no. 4 (2017): 461-464.
[i.3] Chen, Fei, Bo Chen, Hongzhe Lin, Yachen Kong, Xin Liu, Xuepeng Zhan, and Jiezhi Chen:
"Temperature impacts on endurance and read disturbs in charge-trap 3D NAND flash memories".
Micromachines 12, no. 10 (2021): 1152.
[i.4] Wang, Zih-Song, Te-Yuan Yin, Tzung-Hua Ying, Ya-Jui Lee, Chieh-Yi Lu, Hideki Arakawa, and
Chrong Jung Lin: "Impact of moisture from passivation on endurance and retention of NAND
flash memory". IEEE transactions on electron devices 60, no. 1 (2012): 254-259.
[i.5] Maruf, Adnan, Sashri Brahmakshatriya, Baolin Li, Devesh Tiwari, Gang Quan, and Janki
Bhimani: "Do temperature and humidity exposures hurt or benefit your SSDs?". In 2022 Design,
Automation & Test in Europe Conference & Exhibition (DATE), pp. 352-357. IEEE, 2022.
ETSI
10 ETSI GS PDL 025 V1.1.1 (2025-05)
[i.6] Yin, M., Malkhi, D., Reiter, M. K., Gueta, G. G., & Abraham, I. (2019): "HotStuff: BFT
Consensus with Linearity and Responsiveness". In Proceedings of the 2019 ACM Symposium on
Principles of Distributed Computing (PODC '19).
[i.7] Castro, M., & Liskov, B. (1999): "Practical Byzantine Fault Tolerance". In Proceedings of the
Third Symposium on Operating Systems Design and Implementation (OSDI '99).
[i.8] Ongaro, D., & Ousterhout, J. (2014): "In Search of an Understandable Consensus Algorithm". In
Proceedings of the 2014 USENIX Annual Technical Conference (USENIX ATC '14).
3 Definition of terms, symbols and abbreviations
3.1 Terms
access network based WCN: type of WCN where consensus nodes communicate with each other via wireless access
networks such as cellular networks (4G, 5G) or Wi-Fi
Advanced Driver Assistance System (ADAS): technologies that assist drivers in driving and parking functions, often
using automated technology like sensors and cameras
blockchain Trilemma: challenge of simultaneously achieving decentralization, security, and scalability in blockchain
systems
Byzantine Fault Tolerance (BFT): system's ability to continue operating correctly even when some nodes are
malfunctioning or acting maliciously. Distributed computing literature, originated from Leslie Lamport's Byzantine
Generals Problem
Consensus Mechanism (CM): protocols used to validate transactions and organize them in a distributed ledger system
Crash Fault Tolerance (CFT): system's ability to continue operating correctly when nodes fail by crashing but do not
behave maliciously
HotStuff: leader-based Byzantine fault-tolerant consensus algorithm with linear communication complexity
NOTE: As defined in Maofan Yin et al.'s 2019 paper [i.6].
Permissioned Distributed Ledger (PDL): decentralized network with restricted access where participants have to be
authorized, typically governed by a consortium
Practical Byzantine Fault Tolerance (PBFT): specific consensus algorithm that provides Byzantine fault tolerance
with high transaction throughput
NOTE: As defined in Miguel Castro and Barbara Liskov's 1999 paper [i.7].
Proof of Authority (PoA): consensus mechanism that relies on a set of approved validators to produce blocks and
secure the network
Proof of Stake (PoS): consensus mechanism where validators are selected based on the quantity of cryptocurrency they
hold and are willing to "stake"
Proof of Work (PoW): consensus mechanism that requires computational effort to validate transactions and create new
blocks. Bitcoin whitepaper by Satoshi Nakamoto
raft: consensus algorithm designed to be more understandable than Paxos, providing crash fault tolerance
NOTE: As defined in Diego Ongaro and John Ousterhout's 2014 paper [i.8].
Selective Edge Decision layer (SED layer): extension of ADAS's decision-making unit allowing WCN to process
committed data directly under certain auto-driving conditions
self-organizing WCN: type of WCN where consensus nodes establish direct peer-to-peer connections with other nodes
without relying on access points
ETSI
11 ETSI GS PDL 025 V1.1.1 (2025-05)
Trusted Execution Environment (TEE): secure area within a processor that ensures confidentiality and integrity of
code and data
Vehicle-to-Everything (V2X): communication technology enabling vehicles to interact with other vehicles,
infrastructure, pedestrians, and networks
Wireless Consensus Network (WCN): network where PDL nodes reach consensus via wireless networks rather than
traditional wired connections
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
rd
3GPP 3 Generation Partnership Project
4G The fourth generation of mobile phone mobile communication technology standards
5G The fifth generation of mobile phone mobile communication technology standards
ADAS Advanced Driver Assistance System
ARM Advanced RISC Machine
BFT Byzantine Fault Tolerance
CFT Crash Fault Tolerance
CM Consensus Mechanism
CPU Central Processing Unit
ID Identity
IoT Internet of Things
IP Internet Protocol Address
LiDAR Light Detection and Ranging
LoRa Long Range
LTE Long Term Evolution
NAND NOT AND (memory)
NBIoT Narrowband Internet of Things
OS Operational System
PBFT Practical Byzantine Fault Tolerance
PDL Permissioned Distributed Ledger
PoA Proof of Authority
PoS Proof of Stake
PoW Proof of Work
PoX Proof-based Algorithms
PSU Power Supply Unit
RAM Random Access Memory
RF Radio Frequency
RISC Reduced Instruction Set Computer
RREP Routing Response Message
RREQ Routing Request Message
TEE Trusted Execution Environment
TPS Transaction Per Second
UART Universal Asynchronous Receiver and Transmitter
UWB Ultra Wide Band
V2X Vehicle to Everything
WCN Wireless Consensus Network
ETSI
12 ETSI GS PDL 025 V1.1.1 (2025-05)
4 Overview of Wireless Consensus Networks
4.1 Introduction
Permissioned Distributed Ledgers (PDLs), also known as permissioned blockchains, are typical decentralized networks
with restricted access. A governing consortium oversees the PDL network, granting specific permissions to authorized
participants. These participants identify themselves through digital certificates or other means.
In a PDL network, transactions are validated and organized through consensus among the permitted participants. The
data is structured in blocks with each new block linked to the previous via a cryptographic hash. This structure ensures
data integrity by creating an immutable and tamper-proof record.
Each participating node in the PDL network maintains a copy of the ledger.
Nodes can act as either:
• Miners (committing nodes): These nodes maintain the ledger and provide essential network support. They
participate in the consensus process and commit new blocks of records.
• Clients: These nodes only requests transactions from miner nodes and do not participate in consensus or ledger
maintenance.
Traditionally, PDL systems have been designed for stable wired communication networks, assuming sufficient and
reliable communication resources. However, the emergence of Wireless Consensus Networks (WCN), where some PDL
nodes reach consensus via wireless networks, may pose new challenges for consensus such as unstable wireless
connections and the mobility of some PDL nodes.
While wireless networks are widely deployed using various protocols and standards, WCN introduces new challenges
that may require adjustments to both network architecture and hardware, as well as to Consensus Mechanisms (CMs)
deployed. The present document aims to analyse the WCN paradigm, identifying specifications for future applications.
The present document discusses potential specifications and applications of WCN for PDL, covering aspects such as
architecture, hardware requirements, consensus mechanisms, and protocols. It defines key components of WCN nodes
and outlines how WCNs should be constructed and operated.
4.2 WCN Overall Framework
4.2.1 Background
The organization of a WCN relies on two essential elements: consensus nodes (PDL nodes) and wireless
communication methods. Based on the communication methods, WCN frameworks can be categorized into two types:
1) Access network based WCN: Consensus nodes communicate with each other via access networks.
2) Self-organizing WCN: Each consensus node in this type of WCN has the ability to communicate directly with
other nodes.
4.2.2 Access network based WCN framework
The first type of WCN framework involves an access network as illustrated in Figure 1. It illustrates four consensus
nodes that communicate via wireless access networks such as cellular networks (4G, 5G, etc.) or Wi-Fi networks.
When a node initiates a consensus request, it sends it to other nodes through the access network. All nodes can begin
executing the consensus protocol, communicating with each other via that network. Consensus can be reached
according to the protocol. All nodes in this WCN can act as PDL nodes, storing the consensus results (transactions) and
maintaining the PDL's integrity.
ETSI
13 ETSI GS PDL 025 V1.1.1 (2025-05)

Figure 1: WCN framework based on access network
4.2.3 Self-organizing WCN framework
In a self-organizing WCN, all consensus nodes establish direct connections with other nodes to perform consensus
protocol communications. Unlike the access network based framework, there is no access point or wireless
communication infrastructure to support communications between consensus nodes, as illustrated in Figure 2.
In this framework, consensus nodes are expected to have peer-to-peer communication capabilities. These capabilities
enable them to self-organize into WCNs and perform consensus protocols to maintain the PDL.

Figure 2: WCN framework based on self-organizing networks
4.3 WCN Applications
4.3.1 Autonomous driving
Wireless Consensus Networks (WCNs) have significant potential in the field of autonomous driving. Figure 3 illustrates
an example scenario where WCNs can enhance road safety and vehicle coordination. In this scenario, a motorbike is
driving in the blind spot of a truck. If the truck attempts to merge into the right lane without assistance, a collision could
occur. However, if the truck, motorbike and three cars in Figure 3 form a WCN, they can reach a consensus regarding
the occupancy of the right lane. This consensus would result in declining the truck's request to move into the right lane.
Additionally, this lane occupancy information can be recorded in the PDL for nearby vehicles to access.
ETSI
14 ETSI GS PDL 025 V1.1.1 (2025-05)

Figure 3: Wireless distributed consensus for traffic decision
The application of WCNs in autonomous driving offers several benefits:
1) Extended Perception: Autonomous vehicles can perceive information from other vehicles hundreds of meters
away, improving safety and predictability.
2) Data Sharing: Vehicles can share various types of data, including:
• Road conditions obtained after visual image processing
• Environmental information perceived by LiDAR
• Alarm information from unstable systems
• Cooperative operation requests
3) Predictable Behaviour: When consensus is reached, the committed data can predictably influence the
behaviour of each vehicle in the cluster.
4) Advanced Driver Assistance System (ADAS) Integration: WCNs can contribute to ADAS by enhancing
environmental perception. ADAS consists of two core parts:
a) Perception: Utilizes a variety of sensors (e.g. millimetre-wave radar, lidar, cameras, and satellite
navigation) to sense the surrounding environment. It collects data, identifies objects, and track people
and vehicles passing by at any time.
b) Decision-making: Processes and analyses the perceived data.
5) Execution: Carries out instructions based on the decision-making process.V2X Services: In the ADAS
perception, the vehicle node in the WCN can interact with the in-vehicle ADAS via embedded communication
interfaces (e.g. UART or USB) to provide Vehicle-to-Everything (V2X) services under the Raft consensus
mechanism.
6) Data Flow Options: When consensus is complete, the committed data can flow in two ways:
a) Direct transfer of raw committed data to the ADAS decision-making layer.
ETSI
15 ETSI GS PDL 025 V1.1.1 (2025-05)
b) Use of WCN as a "selective edge decision layer" (SED layer) for ADAS: The SED layer is designed as an
extension of the ADAS's decision-making unit. It allows the WCN to have the privilege to process the
committed data directly under certain auto-driving conditions. Then, the processed data or control commands
are transferred to the ADAS. Such privilege can be activated in some high-order auto-driving scenarios.
By leveraging WCNs, autonomous driving systems can enhance their environmental awareness, decision-making
processes, and overall safety. The distributed nature of WCNs paves the way for more advanced and coordinated
autonomous driving systems.
4.3.2 Sensor and IoT networks
The application of WCNs in sensor or IoT networks offers several benefits:
1) Data Sharing: Sensors or IoT devices can share various types of data, including:
- Environmental information from sensors
- Working progress
- Cooperative operation requests
2) Anomaly detection:
- The leader node can confirm the live status of other nodes in the network using consensus, then record
and report the abnormal nodes to the system administrator. For instance, in an underwater sensor
network, the administrator can retrieve the live status of each sensor from the leader sensor node instead
of communicating with each sensor to confirm its working status.
- Abnormal variance of environmental elements in the network operating environment can be detected by
the WCN if some nodes achieve consensus on huge variance of certain environmental elements.
4.4 Relations between Composition and Organization
4.4.1 Aspects
The effectiveness and efficiency of Wireless Consensus Networks (WCNs) depend on two crucial aspects: the
composition of individual nodes and the organization of the network as a whole. These aspects are closely interrelated
and are addressed in detail in the following two clauses of the present document.
Understanding this relationship is crucial for designing and implementing effective WCNs. The following clauses
explore these aspects in detail, providing a comprehensive framework for WCN development and deployment.
4.4.2 Composition
The composition of WCN nodes is critical because nodes may transfer between different WCNs. To ensure seamless
integration and operation across various networks, the capabilities of each node to achieve consensus need to be
standard
...