C.3.2 IoT Service Resolution functional component
C.3.2.1 Use Cases
The use cases of this section cover the IoT Service Resolution functional
component as identified in the functional view (see 4.2.2.5). They provide a
service/resource abstraction level, i.e., service descriptions can be discovered
and looked up, but there is no relation to Virtual Entities (and thus Physical
Entities) being modelled. Associations between Virtual Entities and services are
handled by the Resolution of Virtual Entities component (see Section 4.2.2.3).
The following use cases are depicted in Figure 121.
Resolve Service Identifier to URL/Addresso The use case is initiated by a user of the system, i.e., a Human User
or an Digital Artefact. The user wants to have the URL or address of a
service for interacting with the service.o The assumption is that the user already knows a unique identifier of
the service.o In this use case, the IoT Service Resolution resolves the service
identifier to a URL or address.o If the resolution step is successful, the user can contact the service. Subscribe to resolution of Service Description based on Service Identifiero The use case is initiated by a user of the system, i.e., a Human User
or an Active Digital Artefact. The user wants to be asynchronously
notified about the URL or address of a service for interacting with the
service. A new notification will be sent whenever the URL of the
service changes.o The assumption is that the user already knows a unique identifier of
the service.o In this use case, the IoT Service Resolution asynchronously notifies
the subscribing user about the URL and sends a new notification
whenever the URL changes.o If the subscription is successful, the user will always receive the
current URL for contacting the service. Unsubscribe to resolution of Service Descriptiono The use case is initiated by a user of the system. The user has
previously subscribed to receive notifications about the current URL
of a service identified by a service identifier.