►
Description
A presentation hosted by the Hyperledger Telecom Special Interest Group on February 9, 2023 featuring Dr. Alexandros Psychas, Technical Coordination at Pledger and Nikolaos Kapsoulis, Blockchain Governance at Pledger. They are presenting the Telecom SIG White Paper Self-Assessing Service Level Agreements (SLAs) with Hyperledger Fabric. That can be found at:
https://www.hyperledger.org/wp-content/uploads/2023/01/HL_SolutionsBrief_SLAs_120922.pdf
The white paper describes a prototype approach for the self-assessment of SLAs on a Telecom industry perspective. Standard SLA assessment grants the control of SLA guarantees monitoring and computation over to the providers of the service. The business intelligence of the proposed solution aims in creating a fairer way of assessing SLAs in the broader Web3.0 Ecosystem by making use of the Hyperledger Fabric distributed ledger software hosting Trusted Execution Environments (TEEs).
If you're interested in how blockchain is being used in telecom, feel free to join Hyperledger's Telecom Special Interest Group. More is at: https://wiki.hyperledger.org/display/TCSIG/
Subscribe to the group's mailing list to take part in discussions and get notifications of meetings. Feel free to introduce yourself when you sign up. You can subscribe at: https://lists.hyperledger.org/g/telecom-sig
----
Hyperledger – Open Source Blockchain Technologies
Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use
Discord: https://discord.gg/rVCn4j7UFd
Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory
Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter
Follow-us on Twitter @Hyperledger
Learn about Hyperledger Membership: https://www.hyperledger.org/about/join
#Hyperledger #Blockchain
License
Creative Commons Attribution license (reuse allowed)
A
Okay,
hello
and
welcome
ahead
to
this
presentation
of
the
solution.
Brief
white
paper
that
we
have
documented
in
the
Telecom,
especially
if
there
is
interest
group
in
happy
relative
I-
want
to
start
with
the
way
the
what
paper
per
se
and
see
just
the
at
the
beginning
and
and
I
will
jump
into
the
slides
in
order
to
explain
what
we
are,
how
we
are
actually
doing,
what
we're
doing
and
what
we
are
doing
in
this
solution.
A
Brief
is
actually
a
novel
myth,
we're
presenting
you
know,
and
we
designed
and
presenting
a
novel
method
of
assessing
slas
agreements
and
how
we
do
this,
with
the
high
blood
fabric,
of
course,
and
a
dedicated
trusted
execution
environment
that
run
on
the
chain.
Briefly,
just
the
table
of
contents
of
the
solution.
A
Brief
we
approached
in
the
beginning,
and
we
see
like
the
conventional
there's,
a
late
standard,
SLA
assessment
and
and
how
it
is,
how
it
is
done
now
from
a
telecom
perspective,
the
slas
and
how
they
are
deployed
for
different
vendors
and
services
on
the
ecosystem
and
later
he
said
the
white
paper.
We
see
the
architecture
that
we
propose
and
therefore
unfolding
of
the
operations.
So
let
me
jump
to
the
slides,
I
believe
I'm.
Okay,
now
you
can
see
so.
A
To
note,
we
have
a
collaboration
with
the
elephant
working
on
this
white
paper,
as
we
will
close
here.
So
let
me
start
from
introducing
what
is
the
problem?
Actually,
what
are
the
uses
of
the
conversion
levels,
at
least,
and
how
we
wanted
to
approach
this
and
come
up
with
the
solution?
First
of
all,
this,
this
approach,
of
course,
is
very,
is
relevant
to
the
telephone
industry.
A
It
can
be
applied
to
other
it's
supposed
to
be
applied
to
other
kinds
of
several
level
agreements,
and
standardization
could
bring
this
to
other
Industries,
though
through
corresponding
work
on
it.
So
about
the
the
motivation
behind
it.
The
thing
is
that,
with
a
with
state-of-the-art
slas,
how
they
are
used,
how
they
were
born
and
they
are
used
in
the
industry.
Actually
there
are.
There
is
a
lot
of
power.
Of
course,
there
is
Monopoly
on
the
provider
side.
There
is
not
a
lot
of
transparency
between
the
agreement.
This
is
not.
A
A
So
the
solution
brief
is
about
is
about
a
setup
ecosystem
setup
on
top
of
hybrid
the
fabric
that
utilizes
a
trust
execution
environments
to
bring
privacy
and
transparency
which
actually,
in
the
world
of
people
saying
they
have
a
trade
though.
So
what
this
means
is
that
more
transparency
is
less
privacy
and
less
privacy.
It's
more
transparency,
and
this
kind
of
way
we
handle
here
in
the
in
the
presentation
of
this
a
solution.
Please,
to
note
that
we
have
started
this.
A
So
let's
go
a
bit
more
for
the
SLE
World,
actually,
okay,
what
we
are,
what
we're
having
easily
monitoring
is
private
and
public
Cloud
cases,
a
few
providers
that
have
the
Monopoly
like
Google,
Amazon
Microsoft.
Of
course
it's
the
big
corporations,
and
this
is
how
it
works
actually
and
but
also
there
exists,
but
not
so
famous
providers
more
like
smes
in
this
kind
of
smaller
businesses,
each
of
this
kind
of
providers.
A
A
Coming
up
with
with
an
SLA
violation
in
with
the
breach
of
an
agreement
through
and
the
definition
of
this
metrics,
actually,
the
definition
of
this
Matrix
brings
the
slas
to
be
as
much
as
understandable
between
the
evolved
parties.
However,
the
thing
is
that,
in
order
there
is
a
there
is
difference
with
Mo,
with
monitoring
the
SLA
and
defining
defining
a
metric,
but.
A
Obviously,
we
have,
for
example,
here
an
izone,
a
natural
standardization
document
which
defines
the
ways
that
these
Agreements
are
handled
between
the
provider
and
client,
the
infrastructure
provided
and
the
adopter
and
we're
talking,
of
course,
about
about
specific
kinds
of
descriptions
a
so
in
order
to
in
order
to
Define
aslay,
which
is
a
which
is
I,
mean
in
the
context
of
this
presentation.
It's
for
us
to
understand,
okay,
what
what
is
it?
If
we
have
no
idea
about
this?
A
It's
the
measurements
that
we
they
want,
that
the
provider
offers
to
us
as
they
promised
in
order
to
in
order
to
come.
You
know
to
construct
these
metrics
parameters
are
used
in
order
that
actually
Define
a
metric,
and
they
also
provide
how
it
should
be.
It
should
be
computed,
so
all
this
until
now,
and
the
rules
that
I'm
going
to
say
in
a
minute
in
a
minute
all
this
is
the
agreement,
so
is
the
contract
between
the
provider
and
the
doctor,
and
coming
to
the
role
is
very
quick.
A
A
The
thing
is
that
we
have,
of
course,
the
corresponding
the
corresponding
deployment
of
the
dedicated
software
of
the
providers.
A
this
kind
of
software
is
called
the
algorithmic
drivers
that
actually
have
a
layer
configuration
as
we're
going
to
explain
a
bit
and
the
the
layer
configuration
is
the
the
individual
parts
that.
A
This,
as
we
will
see
in
the
next
explanations,
are
actually
how
we
want
the
chain
code
to
execute
inside
the
fabric
Network
as
we're
going
to
see
on
the
blockchain.
So
this
is
the
intelligence.
If
you
want
there's
a
intelligence
that
should
happen
in
an
agreement.
This
is
how
it
happens
in
the
standard
conventional
if
you
will
slas
so
a
the
three.
The
three
layers
are:
the
sampling,
the
interval
layer,
develop
computation
and
the
calculation.
A
A
Collecting
it
actually
in
order
to
process
it.
The
interval,
as
the
word
says,
it's
about
the.
How
often
we
do
this
process
actually
and
there
is
different
kinds
as
the
building
Circle
there
is
the
basically
evaluation
cycle
and,
of
course,
lastly,
the
calculation.
The
metrical
regulation
is
about
the
actual
computation.
A
So
we
have
collected
the
data,
we
did
it
with
it
specific
frequency,
and
now
we
we
do
the
computation
and
we
have
the
SLA,
and
here
we
have
the
parametric
SLA,
which
is
part
of
our
design,
and
before
going
into
that
the
whole
process,
it's
actually
how
we
have
from
one
point,
the
real
data
and,
from
the
other
point,
the
contract
data,
and
if
we
come
up
with
evaluation
or
not.
So
this
is
the
logic
here
and
last
matters
list.
A
As
I
said,
the
parametric
SLA
is
the
concept
that
we
have
defined
in
our
architecture,
as
we
see
in
the
next
slide
of
an
SLA
that
exists
as
a
template,
if
you
will
on
the
Chain.
So
in
its
agreement
we
use
this
mathematics
SLA
the
parameters
are
filled.
Of
course
the
standard
is
standardized
in
the
sense
that
it
follows.
A
For
example,
we
have
the
availability
in
terms
of
accessibility.
This
kind
of
this
description
of
metric
is
not
only.
That
is
not
only
that
the
provider
that
the
client
actually
can
access
their
service
or
their
protection,
but
it's
actually
it's
not
only
available,
but
it
can
access.
This
is
accessibility
and
the
difference,
for
example,
from
availability
functionalities,
actually
that,
okay,
maybe
there
is
access,
but
maybe
it's
not
functional,
so
it
doesn't,
it
doesn't
work.
D
A
From
the
provider
and
the
client
page,
of
course,
the
providers
through
the
agreement
payment
and
they
signed
the
contract,
the
parametric
SLA,
which
is
a
new
SLA
field
and
signed
by
both
of
them
and
submits
on
The
Ledger
The
Enclave
operations
in
the
the
trust
execution
environment
actually
is
a
the
deployed
and
Hardware
exhalated
no
environment
that
exists
the
system
actually
that
exist
on
the
chain
and
its
contributation.
It's
when
we
say
hardware
and
isolated.
A
It
means
that
the
that
actually
from
a
different
kinds
of
processors,
it's
not
possible
to
entered
the
kind
of
computation
that
happens
through
a
certain
period
in
one
specific
processor.
So
the
hardware
isolation
brings
computational
privacy
to
the
hardware
level,
as
the
word
says,
and
it
protects
from
is
dropping
literally
every
every
kind
of.
A
Transparency
that
could
bring
data
to
to
leak
outside
of
where
we
want
to
have
it.
And,
of
course,
we
have
dedicated
chain
codes
inside
the
trust,
execution
environment.
As
we
will
see,
the
tunnel
link
same
it's
a
connector,
actually
that
we
are
passing
through
the
computed
slas,
the
Computing
measurements
of
the
nest
of
an
SLA
from
outside
the
world
inside
the
blockchain
and
the
T.
A
Precisely
in
terms
of
comparing
to
a
contemporary
methods,
so
again
a
bit
about
the
science
paramedic
SLA,
as
we
said,
the
customer
purchasing
the
product,
this
Imports,
of
course,
the
Bluetooth
transaction
that
happens
between
the
import
parties.
The
agreement,
which
is
the
scientist
La
exists
on
the
same
as
as
a
proof
of
the
contract
between
the
parties
and,
of
course
it
contains.
The
all.
A
A
So
the
hybridizer
fabric,
we
have
the
fabric
private
jingle,
which
is
actually
a
specific,
a
specific
deployment
of
trust,
execution
environment
on
fabric
Network
and
to
where
we
have
a
Enclave
chain
codes
that
execute
it
was
a
hardware
isolation
and
are
guaranteed
that
their
privacy
is
even
a
their
private
data,
is
even
private,
I
would
say
from
the
peers
that
run
it.
So
this
is
this
is
the
logic
of
the
FPC.
A
Will
rephrase
this
that
the
chain
codes
that
run
inside
the
FPC,
which
is
a
deployment
of
trust,
execution
environment
on
the
hybridled
fabric,
the
isolate
data
from
the
peers
that
even
contained
it?
So
we
have
a
total
privacy
of
data
collection,
which
is
the
monitoring
actually
and
executioner.
We
will
see
in
the
include
comparison,
the
next
and
to
enter
the
clean
monitoring.
A
Of
course,
the
from
one
point
we
have,
we
have
the
data
from
the
SLA
contract,
which
is
what
they
have.
The
two
parties
have
signed
and
agreed,
which
is
again
as
we
described
the
metrics
the
how
the
metrics
are
computed,
which
are
the
function
to
compute
the
metrics.
What
are
the
parameters
of
the
metrics,
etc,
etc
and
from
the
other
side?
But
we
see
also
the
ffs
deployment
we
use
ipfs
to
store
the
logs
of
the
machines,
for
example,
and
data
doesn't
need
to
be
on
the
Chain
anyway.
A
Are
actually
the
actual
data
and
the
real
metrics,
the
real
measurements
of
The
Matrix
from
the
service
or
infrastructure,
or
you
name
it
that
the
provider
has
a
offered
to
the
client
and
client
has
purchased
it.
So
this
Loop
inside
the
monitoring
newly
signed
slas
are
Monitor
and
their
post
actually
to
The
Enclave
comparison
for
detection
violations,
foreign.
A
Of
studying
a
set
of
the
art
attacks
on
this,
but
it
is
out
of
the
concept
out
of
this
this
presentations,
but
this
is
the
how
we
try
to
extend
this
white
paper
here.
So
I
was
saying
about
The
Enclave,
computation
inside
the
trust,
execution,
environment
and,
of
course,
the
computation
results
are
unbiased
in
the
sense
that
nobody
can
change
what
the
result
would
be.
So
we
have
a.
A
A
So,
at
the
end
of
the
logic,
the
conversation
comes
and
what
this
means
is
that
a
at
this
point
in
the
state
of
the
art,
there's
no
such
thing
as
automatic
conversation
providers
use
credits
that
are
added
to
the
client.
There
are
different
rules,
for
example.
If,
if
a
credit
level
goes
up
to
a
point,
then
it
makes
sense
to
refund
or
not
this
kind
of
things.
But
here
and
since
we're
talking
about
tokens
that
can
be
totally.
A
Minted
in
a
certain
ecosystem,
the
refunding
can
happen
at
the
point.
It
should
happen
in
the
sense
that
when
there
is
a
violation,
we
have
the
schema
that
we
reward
the
client
for
the
violation,
in
the
sense
that
okay,
they
didn't
receive
the
service
promise
that
they
have,
that
they
are
paying
for
actually
and
the
of
course,
in
order
to
keep
the
economic
model
valid,
the
the
provider
starts
in
this
on
the
same
on
the
same
amount.
So
this
is
the
the
Stations
of
the
compensation.
A
A
A
D
So
this
was
at
the
SLA
was
really
on
top
of
our
agenda
as
Telecom
sick
as
one
of
the
main
use
cases
since
the
beginning
really
and
then
Nicos
came
in
and
and
they've
done,
they
had
done
some
work
on
SLA
and
they've,
just
they.
They
just
completed
this
work
with
us
in
Telecom
6,
so
thanks
Nicholas
for
bringing
in
your
use
case.
D
B
C
A
Until
so
far,
we
have
a
hybridled
lab
that
is,
it's
built
towards
a
kind
of
I,
don't
wallet,
and
we
now
we're
focusing
a
bit
to
to
to
try
to
have
a
new
one,
a
new
proposal
that
combines
all
the
all
the
logic
that
we
have
described
and
the
interface
for
the
user
and
provider
as
well.
That
you
are
mentioning.
C
A
C
C
A
Okay,
and
from
for
from
the
perspective
confidential,
Computing
I
mean
it.
Could
the
trust
execution
environment
could
be
described,
as
is,
if
you
don't
mean
something
else
that
I'm
not
aware
of
so
definitely
it
can
be
it
can.
It
has
a
layer
of
confidentiality
in
the
sense
of
privacy
that
it
brings
to
the
table.
C
It's
sort
of
slightly
differentiation
between
te
and
confidential
Computing,
where
geez
just
validated
trusted
hardware
and
firmware
environment
for
your
workloads,
whereas
confidential
Computing
allows
you
to
have
encrypted
data
encrypted
data
transfer
within
the
computer
system
and
encrypted
data
execution
within
the
CPU,
which
is
different.
That.
C
A
No
I
mean
encryption
is
used
so
in
this
sense
that
okay,
maybe
it
is,
if
I'm,
not
mistaken,
for
compensation
Computing,
because
encryption
is
used
in
this
kind
of
operations
that
we
are
using
in
the
trash
distribution
environment.
So
there
is
a
there
is
encrypted
data
between,
for
example,
The
Enclave
chain
code
and
that
transfers
data
to
the
registry
of
the
enclave
and
the
validation
component.
So
the
communication
between
them
is
encrypted
in
this
sense,
so.
D
Yeah
I
mean
obviously
that
could
there
could
be
always
more
layers
of
kind
of
security
and
encryption
added
through
Hardware
encryption
and
so
on,
but
yeah
again,
so
you
have
to
also
kind
of
trade
off
as
a
the
application,
with
the
level
of
really
cost
and
so
on.
Each
one
of
these
additional
layers
of
security,
middle
care
and
I
assume
here
you
were
Nicholas
targeting
around
a
thousands
of
transactions
per
second
right,
so
adding
more
layers
of
Security
will
probably
have
a
significant
impact
on
that
as
well.
C
D
D
Yeah
I
mean
again,
so
we
could
probably,
if
you're
interested
we
could
probably
as
an
extension
of
this
world.
We
could
distort
a
new
solution
brief,
just
specifically
working
on
that,
which
is
quite
interesting
as
well
to
see
what
can
be
done
in
terms
of
Hardware,
but
making
sure
that
that
is
not
impacting
too
much
the
the
other
metrics
that
we
have
other
kpis
that
we
have
to
meet
when
we
are
talking
about
Telecom
right,
so
yeah.
D
A
But
for
the
deployment
yes,
I
would
say
that
there's
texture
is
actually
about
the
ecosystem,
so
it
it
is
not
a
network
of
happy
little
fabric
and
the
users,
the
involved
users,
that
is,
the
provider
the
adopted
and
so
on.
They
they
log
in
into
the
network
and
they
use
this
kind
of
functionality.
So
the
thing
is
that
we're
proposing
from
an
ecosystem
perspective
of
web3
we
will
and
how
this
would
have
all
the
providers
a
participate
and
the
corresponding
clientele.
D
A
D
The
end
of
just
add
to
that
at
the
end
of
the
day,
this
is
an
effort
to
automate
things
right
and
and
automation
kind
of
shows
this
value
at
scale
right,
so
obviously,
the
more
number
of
operators
and
the
more
number
of
kind
of
parties
that
are
involved
in
this.
Whatever
agreement
that
we
are
applying
here,
the
value
of
this
automation
is
going
to
be
higher
right,
so
yeah
I
mean
and
and
and
the
way
the
Telecom
kind
of
ecosystem
is
moving.
D
D
So
the
agreements
that
I
think
we're
going
to
have
in
a
couple
of
years
are
not
going
to
just
be
like
five
nine
availability
kind
of
agreements,
they're
going
to
be
way
more
complex
than
than
that
and
they're
going
to
be
more
difficult
to
be
done
manually.
So
these
kind
of
automated
and
distributed
a
smart
contract
based
slas
are
going
to
be
more
and
more
important.
C
Thank
you,
I
I
think
that's
something
needs
to
be
considered
whether
or
not
an
mnl
can
implement
the
chain
for
itself
and
its
customer.
All
the
chain
has
to
be
open
to
all
and
my
knows
to
join
and
use
because
that,
so
far,
my
experience
with
the
service
supporter
has
been
they
like
to
control
their
responsibility
and
liability
domain.
That
means
they're,
o
m
and
other
applications
manage
all
the
resources
that
they
own
are
responsible
for
other
than
the
DNS
being
one
shared
service.
D
Yeah
I
mean
the
implementation
of
it.
I
I
can
see
how
how
it
could
be
difficult
to
convince
different
MMOs
to
kind
of
share
their
their
usage,
information
and
performance
information
and
so
on
with
other
mnos
right,
but
at
the
end
of
the
day
there
are
there
are
lots
of
Technologies
now
kind
of
being
overlooked
within
hyperledger
and
other
other
areas
for
cross-chain
interaction
without
having
to
reveal
all
the
information.
So
so
these
are.
These
are
hopeful
kind
of
initiatives
that
hopefully
are
going
to
improve
the
improve
the
situation.
D
D
B
And-
and
we
generally
call
this
as
a
private
permission
chain,
so
so,
of
course,
this
whole
network
is
private
and
we
are
also.
We
are
also
adding
permissions
like
separate,
separate
contracts
for
for,
like
zero
knowledge,
kind
of
things
or
or
one
more
answer
like,
for
example,
if
you
have
a
different.
B
D
Yeah,
so
the
the
zero
knowledge
proof
is
is,
is
it
could
be,
could
be
one
of
the
one
of
the
solutions
but
yeah
yeah
that
that's
that's
a
design
thing
really.
So
this
is
something
that
the
operators
should
should
really
answer
and
then
and
see
how
what
level
of
privacy
they
need
when
it
comes
to
slas.
D
Okay,
so
I
have
shared
the
two
papers
that
were
mentioned
here
so
I've
shared
the
solution.
Brief
I've
shared
a
link
there,
so
obviously
it's
open
access
and
also
the
mdpi
paper
from
Nicos
that
was
mentioned
in
his
talk.
So
that's
also
Open
Access,
so
you
can
just
download
and
and
use
so
yeah
thanks,
everyone
for
joining,
and
thanks
Nicholas
for
bringing
your
use
case
to
us
and
also
kind
of
giving
these
couple
of
talks
about
the
work
which
is
going
to
be
I,
hope
very
interesting
for
people
again.
D
So
our
group
is
open
to
new
ideas
open
to
new
applications
of
hyperledger.
So
even
if
you
have
a
working
kind
of
idea
or
a
basic
idea
that
you've
worked
a
little
bit
in
your
own
institution,
you
can
bring
it
in
and
we
have
experts
from
from
different
areas,
mainly
RP
Ledger,
and
we
can
work
it
together
and
and
kind
of
produce
kind
of
collaborative
works,
such
as
the
the
solution.