Jupyter Notebook Videos & Presentations | Episode 7 Subscriptions and Notifications
Two service providers wishing to link their IoT systems can grant cross-communication permissions via Access Control policies. In effect, one system sends commands to the second. This assumes that they have not formalized cross-business operating procedures. If not, there is still a way for them to deploy cross-organizational applications using Notifications.
Take the case of two streetlight operators in adjoining districts. One operator might wish to synchronize its lighting plans with the other. This operator can ‘subscribe’ to be notified about events in the second operator’s system. It allows the first operator to react to a status change instead of relying on a direct instruction sent by the second operator. In addition to avoiding the need for continuous polling, an event-driven approach decouples communications to the application which results in a modular communications architecture. oneM2M standardizes this arrangement via the Subscription and Notification common service function (CSF).
The CSF is also useful where one operator uses a proprietary technology that does not lend itself to cross communication with other systems. Here, oneM2M provides a bridging role between service providers and their respective technologies.
In this short talk, Andreas and Ken discuss the Notifications function and how it operates in oneM2M.
Link to Jupyter Notebook series and explanations on oneM2M Wiki: https://wiki.onem2m.org/index.php?tit...
Presentation: https://wiki.onem2m.org/images/c/cd/O...
Jupyter Notebook for this episode (online): https://mybinder.org/v2/gh/oneM2M/one...
Join the discussions on GitHub: https://github.com/oneM2M/onem2m-jupy...
ACME oneM2M CSE: https://github.com/ankraft/ACME-oneM2...
oneM2M Homepage: https://onem2m.org