Interaction Diagram: Subscribe Associations Look-up
For subscribing to asynchronously receive notifications about Associations
between a Virtual Entity and services fitting the given VE Service Specification,
an IoT Service Client synchronously calls the VE Resolution, using the
subscribeAssociationsLookup operation with the Virtual Entity ID, the VE
Service Specification and the notification callback, to which notifications are to
be sent, as parameters. The notification callback identifies the endpoint on the
IoT Service Client side that implements the notifyAssociationLookup operation.
The IoT Service Resolution returns the subscription identifier that can be used
to map an incoming notification to the subscription it belongs to.
Subsequently, the VE Resolution will call the notifyAssociationLookup operation
of the IoT Service client, providing the Associations 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 unsubscribeAssociationLookup
operation of the VE Resolution using the subscription identifier as parameter.
As a result, the VE Resolution will stop sending notifications pertaining to the
identified subscription.
IoT-Service
Client(from WP4
Interactions)Virtual Entity
Resolution(from WP4
Interactions)subscribeAssocationsLookup(VE-ID, VEServiceSpecification,
notificationCallback) :SubscriptionIDnotifyAssociationLookup(SubscriptionID, Association[ ])notifyAssociationLookup(SubscriptionID, Association[ ])unsubscribeAssociationLookup(SubscriptionID)Figure 133 : Subscribe Look-up of Associations for VE Identifier and VE Service
Specification