Data Spaces SymposiumMarketplaces in Data Spaces

Francisco de laVega
CTO - FICODESDome ArchitectureOverview

Overview DOME will take the form of a federated
marketplace of curated cloud and edge
services made available through: the global DOME portal; and federated marketplaces

 A federated marketplace can be: Independent Marketplace, which comprises
a catalogue of cloud and edge data/app
services not tied to an IaaS or Platform provider
 Marketplace connected to an IaaS
provider, which comprises a catalogue of cloudand edge data/app services which customers
can pick and then easily deploy on top of theprovided infrastructure Marketplace connected to a Platform
provider which comprises a catalogue of cloudand edge data/app services which customers
can pick, easily activate and run integrated withthe rest of data/app services already running,integrated with the provided Platform.

Marketplaces federation + Shared
Catalogue

 The DOME Distributed Persistent Layer
manages storage of, and access to,
information associated with: the Shared Catalogue of Product Specifications(including the specifications of associatedservices and supporting resources) andProduct Offerings defined by service providers
 Product Orders and Product (instances ofProduct Specifications) along their lifecycle, as
well as information about actual Usage ofProducts

 The DOME Distributed Persistent Layer will
be implemented on top of a number ofinterconnected national blockchains(starting with Alastria and HashNet)
compatible with the European Blockchain
Service Infrastructure (EBSI) when notdirectly EBSIDOME architecture
Advisors
EuropeanCommission
EU member states
policy makers…
Gaia-X
Trust Framework

The Customer Journey

Product offering discovery

 customers can discover product offerings through afederated marketplaces or the DOME portal
 in some cases, despite discovery can take placethrough the DOME portal, the data/app service
provider may establish that procurement has to be
performed through marketplaces of its choice - inthat case, DOME will facilitate navigation of thecustomer to the corresponding portal

Product acquisition (through federated marketplace) acquisition of products can be performed
through the DOME portal or the portal ofsome of the federated marketplaces
 in both cases, creation of a product order
entity is issued into the DPL layer using
TMForum APIs

Product activation (product becomes available for use)

 procurement can be a relative complex process,overall if it requires activation of resources (e.g.,deployment of IoT devices) - a workflow will be
typically implemented
 once the procurement order is successfully completed
a product (instance of the product specification for thedemanding customer) is created and this is notified to
the generating marketplace (federated or DOME)

Product usage

 once everything is ready, client applications of
the customer can start using the service
 from time to time, the data/app service
provider generate usage logs (another entity inDOME information model) using TMForum APIs billing may be generated relying on DOMEThe Provider JourneyRegistration of product specification

 registration of product specifications translates intocreation of product specifications entities according
to the DOME information model (TM Forumcompliant) operations can be performed through APIs exported
by DPL access nodes or the DOME portal (which inturn rely on its corresponding DPL access node)

Registration of product specification

 VPs linked to product specification descriptions
following Gaia-X specifications are also generated
and stored on the blockchain
 Some VCs in the VP linked to product specification
descriptions should be issued by trusted issuers thatDOME has listed. Registration of a productspecification may be rejected if a certain VC is notpresent or cannot be verified

Creation of Product Offering registration of product offerings translates into creation ofproduct specifications entities according to the DOME
information model (TM Forum compliant) operations can be performed through APIs exported by DPL
access nodes or the DOME portal (which in turn rely on its
corresponding DPL access node) VPs linked to product specification descriptions following
Gaia-X specifications are also generated and stored on theblockchain

Creation of Product Offering the service provider establishes as part of a given
product offering description conditions linked tovisibility through federated marketplaces its up to a marketplace provider to decide whether toincorporate a given product offering: they may also
require verification of certain VCs (e.g., compliancewith concrete standards required by platformprovider) beyond those that are mandatory for DOME

Data Spaces SymposiumMarketplaces in Data Spaces

Francisco de laVega
CTO - FICODES