Internet of Things Architecture

Subsequently, the IoT Service Resolution will call the notifyServiceResolution
operation of the IoT Service client, providing the service URL and the
subscription ID as parameters.

When the IoT Service Client is no longer interested in receiving notifications
pertaining to the subscription, it will call the unsubscribeServiceResolution
operation of the IoT Service Resolution using the subscription identifier as
parameter. As a result, the IoT Service Resolution will stop sending notifications
pertaining to the identified subscription.

IoT-Service

Client

(from WP4

Interactions)

IoT Service

Resolution

(from WP4

Interactions)

subscribeServiceResolution(ServiceID,

notificationCallback) :SubscriptionID

notifyServiceResolution(SubscriptionID, ServiceURL)

notifyServiceResolution(SubscriptionID, ServiceURL)

unsubscribeServiceResolution(SubscriptionID)

Figure 123 : Subscribe Resolution of Service Identifier to URL

Interaction Diagram: Look-up

For the look-up of a Service Description based on a Service Identifier, an IoT
Service Client synchronously calls the IoT Service Resolution component, using
the look-upService operation with the ServiceID of the service as parameter.
The IoT Service Resolution looks up the Service Description based on the
ServiceID and provides it as the return value.

The content, structure and representation of the Service Description are design
decisions, which are on purpose not taken at the Reference Architecture level.
An example for a Service Model (content & structure) can be found in [De
2012].