Trust and Reputation Architecture (TRA)
Description (^) The Trust and Reputation Architecture component collects
user reputation scores and calculates service trust levels.
Additional
description
The component is described in detail in deliverable D4.2
Pertaining
requirements
UNI.610, UNI.613, UNI.617, UNI.619, UNI.622, UNI.719
Default function set
Function
name
Function description
Request
Reputation
Information
This function is invocated at a given remote entity to request
reputation information about another entity. As input
parameters, a unique identifier for the remote entity (subject),
as well as the concrete context (what kind of service) is given.
As a result a reputation bundle is provided.
Provide
Reputation
Information
This function is invocated at a given remote entity to provide
reputation information (recommendations or feedback) about
another entity. As input parameters, a unique identifier for the
entity to be assessed (subject), as well as the concrete context,
the given score and a timestamp are given. As a result, the
corresponding reputation element is provided.
C.6.2 IoT Service Resolution functional component
C.6.2.1 Use Cases
In this section we present two use cases that illustrate the utilisation of security-
related functional components.
Both use cases extend the ―Discovery of an IoT-Service based on Service
Specification‖ by adding additional steps before and after ensuring security and
privacy related aspects. It has to be emphasised that this use case ―discovery
of an IoT service based on service specification‖ is just a placeholder for any of
those use cases identified in the previous Appendix (C.2, C.3).
Use Case 1: Secure Discovery of an IoT Service
This use case illustrates how the discovery of services has to be restricted to
those users or applications that are authorised to know about it, including the
creation of a new pseudonym (to ensure the privacy of a user). In this use case,
it is assumed that the communication between functional components is not
limited.