o If the subscription is successful, the user will always be informed
about changes in the service descriptions fitting the provided service
specification. Unsubscribe to discovery of Service Descriptions
o The use case is initiated by a user of the system. The user has
previously subscribed to receive notifications about all the service
descriptions fitting a given service specification.o The assumption is that the user knows the subscription identifier of
the subscription assigned by the IoT Service Resolution.o In this use case, the subscription to the IoT Service Resolution
identified by the subscription identifier is cancelled.o If the unsubscription is successful, the user will no longer receive
notifications concerning service descriptions fitting the given service
specification. Manage service resolution and service descriptions (insert, update,
delete)
o This use case is initiated by a service (or an entity managing a
service).o The assumption is that a service description needs to be inserted,
updated or deleted due to a new service becoming available, an
aspect of a service changing (e.g. due to mobility), or a service no
longer being available. This use case is about the management of service descriptions in
the IoT-service resolution, and the association of service
identifiers to URLs / addresses. The service (or an entity-managing a service) inserts a new
service description, so that it can be looked up and discovered
and so that the service identifier can be resolved as a
URL/address. The service (or an entity managing a service) updates an existing
service description, which may include the update of the mapping
of a service identifier to a URL/address. The service (or an entity managing a service) deletes an existing
service description, so that a service is no longer available. If the management of a service description is successful, the
service descriptions can be looked up or discovered, and/or reflect
the status as reported by the services.