Site Tools


IoTivity Notification Service

This page describes the detailed information for IoTivity Notification Service. Currently it is possible to observe the resources in IoTivity base framework to receive notifications when attribute values have changed. IoTivity Notification Service can utilize caching and monitoring features from IoTivity Resource. It can support having all necessary attributes to enable notification service so that devices vendors can use same to generate notifications and for smart devices to process and understand these notifications.


D2D Notification: Consumer finds the IoTivity notification resource and make the observation request for the notification resource in a network when the resource status changes, provider send notification to observers.

D2S Notification: When the consumers find the notification resource through IoTivity Cloud Interface, consumers could make the observe request to the notification provider via IoTivity cloud.


  • Uniform Standardized Notification information irrespective of platform
  • Platform independent (Attributes, description information, icon URL etc. are same)
  • Provides SDK and open APIs for developers to subscribe and receive the Notification Object
  • Priority Notification (information, notice, alert, event)
  • Notification Synchronization (Read / Deleted)
  • Notification via Cloud Server
  • Interest Notification


Sequence Diagrams

Start or Stop Notification service

IoTivity application starts / stops notification service to launch / terminate a provider or consumer.

Discovery of Notification Resource

Consumer finds IoTivity notification resource when a provider creates the resource. A notification consumer, OCF client, can discover available notification resources on the network using the regular IoTivity discovery process which works on specific resource type.

Subscription to Notification Resource

Either consumer or provider request subscription according to the result of subscription policy exchange. Once the notification resource is discovered, consumer can subscribe to notification message resource which is described in the notification resource, OCF resource server. The notification resource includes an subControllability flag that indicates if this subscription is controlled by the provider or if any consumer is free to subscribe.

Sending Notifications

After subscription to the notification message and synchronization resources, the consumer receives notifications from message resource. This can be alert, event, notice, warning or information notifications. The notification messages are delivered only to the subscription-allowed consumers according to the controllability.

Synchronization of Notification Message

The consumer can acknowledge the state of the notification message such as read or deleted state through updating notification sync resource. The message resource comes with a unique id for the notification that must be used by a client to acknowledge the notification.

Notification operation using cloud interface

For delivery of notifications accross closed-network boundaries, the cloud interface can be used as relay between a notification consumer and provider. The application using the cloud client has first to sign up & sing in to connect to the cloud as describe in IoTivity cloud. The flow for notification messages and the acknowledgement status is same with D2D service, after enabling D2S service.

Notification Filtering with Topic Resource

In convergence environment, showing notifications of which private device on public display device, e.g., kiosk, need to be restricted. The topic resource provides additional information for consumers to decide to pick interested notifications from interest-matched applications. An additional topic resource is defined with optional resource. The consumer could get the provider’s topic list receiving ‘GET’ response of the resource, and then request to subscribe to the interest topics sending the list of them with POST message.

Resource Model

The notification service is provided through a notification resource and related resources which are used to deliver the notification message and synchronize the acknowledgement status of the client. The device and/or application who want to deliver the notifications to other devices should create the notification resource. The figure below illustrates the generic structure of notification resources, their properties and relationship.

Notification Resource Properties

Notification Message Resource Properties

Notification Sync Resource Properties

Notification Topic Resource Properties

notification_service.txt · Last modified: 2017/07/24 07:32 by ch79.cho