ETSI GS PDL 012 V1.1.1 (2022-05)

Permissioned Distributed ledger (PDL); Reference Architecture

DGS/PDL-0012_Ref_Arc_Framwk

General Information

• Status: Not Published
• Technical Committee: PDL - Permissioned Distributed Ledger
• Current Stage: 12 - Completion
• Due Date: 09-May-2022
• Completion Date: 05-May-2022

Standards Content (Sample)

GROUP SPECIFICATION
Permissioned Distributed Ledger (PDL);
Reference Architecture
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 012 V1.1.1 (2022-05)

Reference
DGS/PDL-012_Ref_Arc_Framwk
Keywords
architecture, PDL
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:
http://www.etsi.org/standards-search
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 at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
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
rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
and/or governmental
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 2022.
All rights reserved.
ETSI
3 ETSI GS PDL 012 V1.1.1 (2022-05)
Contents
Intellectual Property Rights . 8
Foreword . 8
Modal verbs terminology . 8
Executive summary . 8
Preface . 9
1 Scope . 10
2 References . 10
2.1 Normative references . 10
2.2 Informative references . 11
3 Definition of terms, symbols and abbreviations . 11
3.1 Terms . 11
3.2 Symbols . 15
3.3 Abbreviations . 15
4 Introduction . 16
5 ETSI-ISG-PDL Reference Architecture . 17
5.1 Definition of a Functional Block . 17
5.2 Reference Architecture Overview . 17
5.3 Development Guiding Principles . 21
5.3.1 Platform development guiding principles . 21
5.3.1.1 Platform Categories . 21
5.3.1.2 Category Alpha Platform . 21
5.3.1.2.1 Introduction . 21
5.3.1.2.2 Category Alpha-1 Platform . 22
5.3.1.2.3 Category Alpha-2 Platform . 22
5.3.1.3 Category Bravo Platform . 22
5.3.1.3.1 Introduction . 22
5.3.1.3.2 Category Bravo-1 Platform . 22
5.3.1.3.3 Category Bravo-2 Platform . 22
5.3.1.4 Category "Charlie" Platform . 23
5.3.1.4.1 Introduction . 23
5.3.1.4.2 Category Charlie-1 Platform . 23
5.3.1.4.3 Category Charlie-2 Platform . 23
5.3.1.4.4 Category Charlie-3 Platform . 24
5.3.1.4.5 Category Charlie-4 Platform . 24
5.3.1.5 Category Delta Platform . 24
5.3.1.5.1 Introduction . 24
5.3.1.5.2 Category Delta-1 Platform. 24
5.3.1.5.3 Category Delta-2 Platform. 24
5.3.1.5.4 Category Delta-3 Platform. 25
5.3.1.5.5 Category Delta-4 Platform. 25
5.3.2 Application development guiding principles . 25
5.3.3 Platform Services Dependency . 25
5.3.4 Abstraction Layer Implementation . 25
5.4 ETSI-ISG-PDL Platform Services . 26
5.4.1 List of all Platform Services . 26
5.4.2 ETSI-ISG-PDL Atomic Platform Services . 28
5.4.2.1 Introduction to Atomic Platform Services . 28
5.4.2.2 ETSI-ISG-PDL Namespace Platform Service. 29
5.4.2.3 ETSI-ISG-PDL Identity Platform Service . 29
5.4.2.4 ETSI-ISG-PDL Location Platform Service . 30
5.4.2.5 ETSI-ISG-PDL Registration Platform Service . 30
5.4.2.6 ETSI-ISG-PDL Discovery Platform Service . 30
ETSI
4 ETSI GS PDL 012 V1.1.1 (2022-05)
5.4.3 ETSI-ISG-PDL Composite Services . 31
5.4.3.1 List of all Composite platform Services . 31
5.4.3.2 ETSI-ISG-PDL Messaging Service . 32
5.4.3.3 ETSI-ISG-PDL Policy Service. 33
5.4.3.4 ETSI-ISG-PDL Security Platform Services . 33
5.4.3.4.1 Introduction to Security Platform Services . 33
5.4.3.4.2 ETSI-ISG-PDL Authentication Platform Service . 34
5.4.3.4.3 ETSI-ISG-PDL Authorization Platform Service . 34
5.4.3.4.4 ETSI-ISG-PDL Cryptography Platform Service . 34
5.4.3.4.5 ETSI-ISG-PDL Encryption Platform Service. 34
5.4.3.4.6 ETSI-ISG-PDL Identity Management Platform Service . 35
5.4.3.4.7 ETSI-ISG-PDL Key Management Platform Service . 35
5.4.3.5 ETSI-ISG-PDL Logging Platform Service . 35
5.4.3.6 ETSI-ISG-PDL Governance Platform Services . 35
5.4.3.6.1 Introduction to Governance Platform Services . 35
5.4.3.6.2 ETSI-ISG-PDL Implementation Agreements . 36
5.4.3.6.3 ETSI-ISG-PDL Governing Entity . 37
5.4.3.6.4 Creating, Changing and Enforcing Governance IAs and rules . 37
5.4.3.7 ETSI-ISG-PDL Composition Platform Service . 38
5.4.3.8 ETSI-ISG-PDL Access Control Platform Service . 38
5.4.3.9 ETSI-ISG-PDL Fault Tolerance Platform Service . 38
5.4.3.10 ETSI-ISG-PDL Distribution Transparency Platform Service . 39
5.4.3.11 ETSI-ISG-PDL Publish and Subscribe Platform Service. 39
5.4.3.12 ETSI-ISG-PDL Concurrency Platform Service . 39
5.4.3.13 ETSI-ISG-PDL Storage related services . 39
5.4.3.13.1 Types of Storage Platform Services . 39
5.4.3.13.2 ETSI-ISG-PDL In Memory Storage Platform Service . 39
5.4.3.13.3 ETSI-ISG-PDL File System Storage Platform Service . 40
5.4.3.13.4 ETSI-ISG-PDL On-Chain Storage Platform Service . 40
5.4.3.13.5 ETSI-ISG-PDL Off-Chain Storage Service . 40
5.4.3.13.6 ETSI-ISG-PDL Distributed Blockchain Storage Platform Service . 41
5.4.3.14 ETSI-ISG-PDL Modelling Related Platform Services . 41
5.4.3.14.1 Introduction to Modelling . 41
5.4.3.14.2 ETSI-ISG-PDL Information Model . 42
5.4.3.14.3 ETSI-ISG-PDL Data Model . 42
5.4.3.14.4 ETSI-ISG-PDL Model Search . 43
5.4.3.14.5 ETSI-ISG-PDL Model Stitching . 43
5.4.3.15 ETSI-ISG-PDL Topology Platform Service . 44
5.4.3.16 ETSI-ISG-PDL Event Processing Platform Service . 44
5.4.3.17 ETSI-ISG-PDL Distributed Data Collection Platform Service . 45
5.4.3.18 ETSI-ISG-PDL Distributed Secret Sharing Platform Service . 45
5.4.3.19 Resource Management Platform Services . 45
5.4.3.19.1 Introduction to Resource Management . 45
5.4.3.19.2 Resource Discovery . 45
5.4.3.19.3 Resource Virtualization . 46
5.4.3.19.4 Resource Inventory Management . 46
5.4.3.19.5 Resource Administration and Management . 46
5.4.3.19.6 Resource FCAPS . 47
5.4.3.19.7 Resource Composition . 47
5.4.3.20 ETSI-ISG-PDL Platform Service Management Platform Services . 47
5.4.3.20.1 Introduction to Platform Service Management . 47
5.4.3.20.2 Platform Service Discovery Platform Service . 47
5.4.3.20.3 Platform Service Virtualization . 47
5.4.3.20.4 Platform Service Inventory Management . 48
5.4.3.20.5 Platform Service Administration and Management . 48
5.4.3.20.6 Platform Service FCAPS . 48
5.4.3.20.7 Platform Service Composition . 48
5.4.3.21 ETSI-ISG-PDL Application Management Services . 48
5.4.3.21.1 Introduction to Application Management . 48
5.4.3.21.2 Application Composition . 49
5.4.3.21.3 Application and Platform Service Orchestration . 49
5.4.3.21.4 Orchestration Platform Service . 49
ETSI
5 ETSI GS PDL 012 V1.1.1 (2022-05)
5.4.3.21.5 Platform exploration . 49
5.4.3.21.6 Application Registration . 49
5.4.3.22 ETSI-ISG-PDL Transaction Management Service . 49
5.4.3.23 ETSI-ISG-PDL Data Model Gateway/Broker . 50
5.4.3.23.1 Introduction to presentation services . 50
5.4.3.23.2 ETSI-ISG-PDL API Presentation Platform Service . 51
5.4.3.24 ETSI-ISG-PDL Application Specific Services . 51
5.5 ETSI-ISG-PDL Application Clients . 52
5.5.1 Introduction to Application Clients . 52
5.5.2 ETSI-ISG-PDL Computer Applications . 52
5.5.3 ETSI-ISG-PDL Mobile Device Application . 52
5.5.4 ETSI-ISG-PDL Cloud Applications . 52
5.6 Summary . 53
Annex A (informative): Change History . 54
History . 55

ETSI
6 ETSI GS PDL 012 V1.1.1 (2022-05)
List of figures
Figure 1: Main Components of the ETSI-ISG-PDL Reference Architecture .18
Figure 2: A Category "Alpha" platform .21
Figure 3: Category "Bravo" platform .22
Figure 4: Category "Charlie" platform .23
Figure 5: Category "Delta" platform .24
Figure 6: Abstraction Layer Implementation .25
Figure 7: ETSI-ISG-PDL Atomic Platform Services .29
Figure 8: ETSI-ISG-PDL Composite Platform Services .32
Figure 9: Security Platform Services .34
Figure 10: Governance Platform Services .35

ETSI
7 ETSI GS PDL 012 V1.1.1 (2022-05)
List of tables
Table 1: Service types .19
Table 2: ETSI-ISG-PDL Platform Services .26

ETSI
8 ETSI GS PDL 012 V1.1.1 (2022-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 Web server (https://ipr.etsi.org/).
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™ and LTE™ 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 defines a high level and abstract Reference Architecture (RA) for a Permissioned Distributed
Ledger platform. The present document also describes the characteristics and behaviour of this platform, along with the
services that it provides.
The following areas are discussed in detail:
1) PDL Platform Services.
2) PDL Abstraction Layers.
3) PDL Interfaces and Interface Reference Points.
ETSI
9 ETSI GS PDL 012 V1.1.1 (2022-05)
The objectives of the present document are to:
• Maximize the choice of technology solutions available to entities using ETSI-ISG-PDL endorsed PDL
platforms.
• Maximize ETSI-ISG-PDL endorsed PDL platforms' scalability in terms of the applications supported and the
number of entities able to use them.
The ETSI-ISG-PDL RA is described in terms of abstract foundational (required minimum) and functional components
that support specific sets of functionalities and reference points that describe the standardized interactions between
different parts of the platform and with the external entities or platform. This enables technology vendors and
developers to focus on their respective areas of expertise and platform users to choose a best-of-breed team of
vendors/developers for their specific requirements.
Preface
The present document defines a RA for a Permissioned Distributed Ledger platform. The present document also
describes the characteristics and behaviour of this platform, along with the services that it provides and exemplary
solutions that can be built using it.
A RA is a template for defining a solution to a particular problem domain (in this case, a PDL platform). It provides a
set of common definitions of concepts, terminology, and common characteristics and behaviour of the system, including
a set of external Reference Points that standardize communication. The present document uses a Functional Block
architecture to define three key aspects of a PDL Platform:
• Platform Services, which are services and functionality provided by the PDL platform.
• Abstraction layers, which are Data Model Brokers allowing different and diverse applications on one
side and different DLT chain types on the other side to interface with the PDL platform.
• Modularity, which allows evolution and adaptation of PDL platforms to changing requirements.
The objectives of using the RA are to:
• Maximize the choice of technology solutions available to entities using ETSI-ISG-PDL-endorsed technologies,
Common Services, and applications.
• Maximize ETSI-ISG-PDL endorsed PDL platforms' scalability in terms of the applications supported and the
number of entities able to use them.
The ETSI-ISG-PDL RA also provides standardized terminology to simplify the interaction between PDL Platforms
Services and applications developed by technology vendors/developers.

ETSI
10 ETSI GS PDL 012 V1.1.1 (2022-05)
1 Scope
The present document defines a RA for a Permissioned Distributed Ledger platform [i.1]. The present document also
describes the characteristics and behaviour of this platform, along with the services that it provides and exemplary
solutions that can be built using it.
The objectives of the present document are to:
• Maximize the choice of technology solutions available to entities using ETSI endorsed PDL platforms.
• Maximize ETSI endorsed PDL platforms' scalability in terms of the applications supported and the number of
entities able to use them.
In scope:
• Definition of Functionalities, Interfaces, Reference points (e.g. Identity Services: PDL identity, Node identity,
User identity).
Out of scope:
• Specific implementation details (e.g. Implementation of identity using a specific method). Such
implementation details may be added at a later phase as separate documents or as corollaries/annexes to future
releases of the present document.
The approach taken in the present document is to focus on defining what needs to happen, not how it is implemented.
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 at
https://docbox.etsi.org/Reference/.
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.
ETSI
11 ETSI GS PDL 012 V1.1.1 (2022-05)
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 are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] Framework for Permissioned Public Blockchain Networks, Inter American Development Bank
(2021): "LACChain Framework for Permissioned Public Blockchain Networks".
NOTE: Available at https://publications.iadb.org/publications/english/document/LACChain-Framework-for-
Permissioned-Public-Blockchain-Networks-From-Blockchain-Technology-to-Blockchain-Networks.pdf.
[i.2] MEF Sonata IRP MEF 55 Lifecycle Service Orchestration, 55.0.1 October 2017: "MEF 55 - LSO
Reference Architecture".
NOTE: Available at https://www.mef.net/resources/mef-55-1.
[i.3] NIST Special Publication 800-162 (January 2014): "Guide to Attribute Based Access Control
(ABAC) Definition and Considerations".
NOTE: Available at https://doi.org/10.6028/NIST.SP.800-162.
[i.4] Gamma, E., Helm, R. Johnson, R., Vlissides, J.: "Design Patterns:-Elements of Reusable Object-
Oriented Software", Addison-Wesley, Nov, 1994.-ISBN 978-0201633610.
[i.5] Riehle, D.: "Composite Design Patterns", Proceedings of the 1997 Conference on Object-Oriented
Programming Systems, Languages and Applications (OOPSLA '97), ACM Press, 1997,
Page 218-228.
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the following terms apply:
Abstraction Layer: functionality that serves as an intermediator between subsystems that may be using different
protocols, vocabulary, and methods that serves their respective purposes
Access Control Policy: privileges and permissions of a subject entity to perform operations on a set of target entities
addressable atorage: content/data that can be accessed through a web link (URL)
API Broker: software that mediates between two systems with different Data Models implemented as APIs
NOTE: Also referred to as API Gateway.
API Gateway: See API Broker.
application (software): program or group of programs designed to perform specific tasks for end users
application abstraction layer: APIs and interfaces, including API Brokers, enabling Applications to communicate
with an ETSI-ISG-PDL Platform
Application Programming Interface (API): system of tools and resources in an operating system, enabling developers
to create software applications
asynchronized data: data that does not require synchronization with other data
ETSI
12 ETSI GS PDL 012 V1.1.1 (2022-05)
Attribute Based Access Control (ABAC): access control method where the subject requests for performing an
operation on objects are granted/denied based on:
• Assigned attributes of the subject.
• Assigned attribute of the object.
• Environmental conditions.
• Set of policies.
NOTE: As defined by NIST [i.3].
blockchain: censorship and tamper-proof growing list of records, called blocks, that are linked using cryptography
NOTE: Each block contains a cryptographic hash of the previous block, a timestamp, and transaction data.
business service: service that is delivered to business customers by business units
category alpha application: application that is developed and delivered to all users of said application by a single
vendor/developer using a Category Alpha Platform developed by that same vendor/developer
NOTE Can only use a single DLT type prescribed by the developer.
category alpha platform: PDL platform that is designed, developed, delivered, and integrated to all users of said
platform by a single vendor using a single DLT technology
NOTE: Broken down to sub-categories "Alpha-1" and "Alpha-2".
category bravo application: application that is developed and delivered to all users of said application by a single
vendor/developer using a Category Bravo Platform developed by that same vendor/developer
NOTE: Can only use DLT types prescribed by the developer.
category bravo platform: PDL platform that is designed, developed, delivered, and integrated to all users of said
platform by a single vendor, but can operate using two or more underlying DLT technologies
NOTE: Broken down to sub-categories "Bravo-1" and "Bravo-2".
category charlie application: application that is developed towards a specification of an Application so that any user
of an application supporting such specifications can fully interoperate with other users of other applications built
towards the same Application specifications
category charlie platform: PDL platform that can operate using two or more underlying DLT technologies and is
designed and developed towards a specification of an application abstraction layer so that any Application that supports
such an abstraction layer can interface with said platform
NOTE: Broken down to sub-categories "Charlie-1", "Charlie-2", "Charlie-3" and "Charlie-4".
category delta platform: Category Charlie platform that only supports a single DLT type
NOTE: Broken down to sub-categories "Delta-1", "Delta-2", "Delta-3" and "Delta-4".
Certificate Authority (CA): entity that issues digital certificates. A digital certificate certifies the ownership of a
public key by the named subject of the certificate
composite application: applications using the PDL platform that are made up of other applications that use the PDL
platform
composition: act of creating a new object or a new functionality through combination of two or more existing objects
or functionalities
concurrency: occurrence of and/or execution at the same time of different programmatic units
consumer: PDL Platform entity that consumes data produced by another entity
ETSI
13 ETSI GS PDL 012 V1.1.1 (2022-05)
data model: concepts of interest to an environment in a form that is dependent on data repository, data definition
language, query language, implementation language, and/or protocol
NOTE: Data Models are derived from the Information Model.
data model broker: software that mediates between two systems with different data models
NOTE: Also referred to as Data Model Gateway.
data model gateway: Same as Data Model Broker.
directly connected storage: storage that is local to the node and is either physically connected to the node or is external
storage connected using a shared communication channel that is managed by the owner of that node
NOTE: Examples of physically connected storage: internal drive, external thunderbolt drive. Examples of
external storage: NAS, Cloud.
Discretionary Access Control (DAC): access control policy where the owner of a resource/object defines the access
control policy for the users
distributed addressable storage: addressable Storage that is distributed across multiple storage devices
Distributed Ledger Ttechnology (DLT): technology implementing a distributed ledger which is a consensus of
replicated, shared, and synchronized digital data geographically spread across multiple sites, countries, or institutions
NOTE: Unlike with a distributed database, there is no central administrator.
Domain Name System (DNS): hierarchical and decentralized naming system for computers, services, or other
resources connected to the Internet or a private network
NOTE: It associates various information with domain names assigned to each of the participating entities.
external data: data obtained from resources or systems external to the PDL platform
external IRP: IRP between a PDL platform and external entities
Functional Block: abstraction that defines the external structural representation of the capabilities and functionality of
a component or module, and its relationships with other Functional Blocks
NOTE: Functionalities such as capabilities, behaviour, and relationships, as well as their inputs, outputs, and
optionally, transfer functions. The internal structure of a Functional Block is not revealed.
functional capability: capabilities that a system has to manage resource in each functional area of operations
Governance: collection of rules and tools that control the behaviour and function of a PDL platform
implementation agreement: rules and agreements that describe how a Platform Service is implemented
information model: representation of concepts of interest to an environment in a form that is independent of data
repository, data definition language, query language, implementation language, and protocol
insignificant event: event that does not affect any node other than the node where it occurred and does not affect the
chain or consensus mechanism
Interface Reference Point: communication channels through which Functional Blocks communicate with each other
NOTE: IRPs are given names for reference purposes (e.g. "Debka").
Internal Data: data that is generated by a node either through computation or through a directly connected sensor that
feeds data to that node
Internal IRP: IRP between Functional Blocks internal to a PDL platform
Internet Corporation for Assigned Names and Numbers (ICANN): American multi-stakeholder group and non-
profit organization responsible for coordinating the maintenance and procedures of several databases related to the
namespaces and numerical spaces of the Internet, ensuring the network's stable and secure operation
ETSI
14 ETSI GS PDL 012 V1.1.1 (2022-05)
Internet Engineering Task Force (IETF): open standards organization, which develops and promotes voluntary
Internet standards, in particular the standards that comprise the Internet protocol suite
InterPlanetary File System (IPFS): protocol and peer-to-peer network for storing and sharing data in a distributed file
system that uses content-addressing to uniquely identify each file in a global namespace connecting all computing
devices
NOTE: A global namespace connecting all computing devices such as the public internet.
Loosely Coupled: functionality that has little or no dependency on other functionalities
Mandatory Access Control (MAC): access control policy defined by system administrators
Minimum Viable Product (MVP): version of a product with just enough features to satisfy early customers and
provide feedback for future product development
Non-Addressable Storage: content/data that cannot be addressed and accessed by any other entity except for the entity
that directly manages this data
orchestration: automated (and/or manual) configuration and management of systems and their Functional Blocks
NOTE: Orchestrated objects may be Resources, Platform Services, Applications. Orchestration emphasizes
coordinated actions; one form of this coordination is service function chaining.
PDL Abstraction Layer: APIs and interfaces, including API Brokers, enabling Platform services to communicate with
ETSI-ISG-PDL endorsed PDL types
PDL Hardware Interface: point across which electrical, mechanical, and/or optical signals are conveyed from a sender
to one or more receivers using one or more protocols
PDL Data Model Broker/Gateway: translates between data models allowing entities using different data models to
communicate each using its own data model
NOTE: Details are for further study.
PDL Platform Atomic Service: PDL Platform Service that does not use any other PDL Platform Service to perform its
functionality
NOTE: May use external applications or functions.
PDL Platform Composite Service: PDL Platform Service that uses one or more other PDL Platform Services to
perform its functionality
PDL Platform Mandatory Service: PDL Platform Service that is m
...