Ci-dessous, les différences entre deux révisions de la page.
Les deux révisions précédentes Révision précédente Prochaine révision | Révision précédente | ||
cours:mit_2018_2019 [2019/01/29 12:33] tigli [Evaluation Rules :] |
cours:mit_2018_2019 [2019/02/05 16:36] (Version actuelle) tigli [Session 7 : Advanced MIT : SWoT (Semantic Web of Things), middleware and semantic composition] |
||
---|---|---|---|
Ligne 119: | Ligne 119: | ||
**Notice: It is mandatory to have Linux operating system.** | **Notice: It is mandatory to have Linux operating system.** | ||
- | ==== Lecture 5 : Service oriented Architecture and Middleware for IoT : Towards Web of Things (WoT) and Web Services for Devices (WSD) ==== | + | ==== Session 5 : Service oriented Architecture and Middleware for IoT : Towards Web of Things (WoT) and Web Services for Devices (WSD) ==== |
---- | ---- | ||
Ligne 156: | Ligne 156: | ||
- | ==== Session 6 : Web Service for Devices Discovery, Availability Management and Dynamic software composition ==== | + | ====== Synthesis ======= |
+ | |||
+ | Middleware for IoT are deployed on heterogeneous IoT Plateform to provide a more homogeneous way to develop some distributed software applications. Most of the time, we distinguish four levels : IoT Devices, Edge, Fog, and Cloud. | ||
+ | |||
+ | **Exercice :** Find in the technical and scientific litterature some definitions and recent surveys on these concepts for IoT. Write a paper (Max 2 pages long) on this 4-levels point of view of distributed system that can then emerged like CyberPhysical Systems. | ||
+ | For example you can argue : | ||
+ | * why differents patterns of communication are used in this 4-levels System, | ||
+ | * what are the famoust technologies for each levels | ||
+ | |||
+ | <note> | ||
+ | This paper will be sent **To tigli@unice.fr** with ** Subject : <Your Name> IoT Paper 2019 ** as to attached files : one .zip with sources (tex/docx) and one pdf, no later than 10th of February | ||
+ | </note> | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ==== Session 6 : Web Service for Devices : Discovery, Availability Management and Dynamic software composition ==== | ||
---- | ---- | ||
Ligne 163: | Ligne 179: | ||
== Material == | == Material == | ||
- | * {{:cours:2017-2018_lecture_6_wsd_composition.pdf|Slides of the Lecture on Web Service for Devices and Dynamic Composition}} | + | * {{:cours:2017-2018_upnp_dpws.pdf|Slides of the Lecture on Web Service for Devices standards}} |
+ | **Lab : UPnP Manipulations without programming ** | ||
- | == Ubiquaria tutorial == | + | * Install [[https://www.meshcommander.com/upnptools|Developper Tools for UPnP Technologies]] |
+ | * "Network Light" simulate an UPnP device. | ||
+ | * Device Spy Tool allow to interact with any UPnP device in your Local Network | ||
+ | * Device Sniffer allow to spy the UPnP protocols exchange | ||
+ | // Exercice : // | ||
+ | * Run a "Network Light" and interact with if thanks to the Device Spy Tool. How many services are available ?. What are both kinds of software communication patterns | ||
+ | * Find the description of the "Network Light" Device/Services. What is the format of this description ? Can you then imagine how the Device Spy create an interface for each discovered device on the fly ? | ||
+ | * Thanks to Device Sniffer, you can observe the different messages between Clients (UPnP control point) and Servers (UPnP Devices). What are the messages corresponding to SSDP ? What is the HTTP-like protocol that carry this kind of message? | ||
+ | |||
+ | **Lab UPnP with Node-RED** | ||
+ | * After creating you own UpnP device, try to use it with Node-RED. First, you need to install node-red-upnp-control-point and node-red-contrib-upnp. You can find them at the following address: http://trolen.polytech.unice.fr/cours/mit/ | ||
+ | * With the samples in node-red-contrib-upnp package, try to discover the UPnP device | ||
+ | * Then, try to interact with them, send an action to a UPnP device and subscribe to changes on the device. | ||
+ | |||
+ | **Lab : Create your own UPnP device (with some C# programming)** | ||
* {{:cours:2017-2018_tutorial_6_wsd_upnp.pdf|Tutorial on Web Services for Devices (UPnP)}} | * {{:cours:2017-2018_tutorial_6_wsd_upnp.pdf|Tutorial on Web Services for Devices (UPnP)}} | ||
* Tutorial Videos : [[https://www.youtube.com/watch?v=MnMaz5WYsb0|video1]] & [[https://www.youtube.com/watch?v=4UMJhMJMiUY|Video2]] | * Tutorial Videos : [[https://www.youtube.com/watch?v=MnMaz5WYsb0|video1]] & [[https://www.youtube.com/watch?v=4UMJhMJMiUY|Video2]] | ||
- | * {{:cours:2017-2018_tutorial_6_wsd_composition.pdf|Tutorial on WSD Dynamic Composition}} | + | |
==== Session 7 : Advanced MIT : SWoT (Semantic Web of Things), middleware and semantic composition ==== | ==== Session 7 : Advanced MIT : SWoT (Semantic Web of Things), middleware and semantic composition ==== | ||
Ligne 178: | Ligne 208: | ||
||| | ||| | ||
- | ** Lecturer : G. Rocher, GFI Informatique ** | + | Lecturers : G. Rocher, GFI Informatique - J.Y. Tigli |
* {{:cours:swot.pdf| Slides of the Lecture on Semantic Web of Things }} | * {{:cours:swot.pdf| Slides of the Lecture on Semantic Web of Things }} | ||
Ligne 193: | Ligne 223: | ||
The mission of SOFIA project is to create a semantic interoperability platform which enables and maintains cross-industry interoperability which is a platform for new services. Concurrently the solution will foster innovation while maintaining value of existing legacy multi-vendor interoperability platform. | The mission of SOFIA project is to create a semantic interoperability platform which enables and maintains cross-industry interoperability which is a platform for new services. Concurrently the solution will foster innovation while maintaining value of existing legacy multi-vendor interoperability platform. | ||
- | * Industrial products from SOFIA : ** SMALL at Tecnalia ** | + | * Industrial products from SOFIA : ** SMALL at Tecnalia ** |
- | * Industrial products from SOFIA : ** SOFIA 2 at Indra ** | + | * Industrial products from SOFIA : ** SOFIA 2 at Indra ** |
+ | |||
+ | * **[[https://fiware-orion.readthedocs.io/en/master/index.html|FiWare]]** | ||
+ | * **OneM2M, ETSI ** | ||
{{ :cours:etsi-onem2m.png?150|}} | {{ :cours:etsi-onem2m.png?150|}} | ||
Ligne 215: | Ligne 248: | ||
- Evaluation of a Practical Course : Evaluation from the Tutorial of the Modeled Complex Event Processes using Synchronous languages approaches and model checking [Deadline 02/20/19] | - Evaluation of a Practical Course : Evaluation from the Tutorial of the Modeled Complex Event Processes using Synchronous languages approaches and model checking [Deadline 02/20/19] | ||
- One or more MCQ during some sessions [02/05/19 and 02/12/19 or 02/19/19] | - One or more MCQ during some sessions [02/05/19 and 02/12/19 or 02/19/19] | ||
- | - Personnal Work : Writing of a short survey about a technological or research topic in the field of IoT (as an homework or during the 3 hours last exam, according to rthe availability of the students for homeworks)[Deadline 02/15/19] | + | - Personnal Work : Writing of a 2 pages long paper like explain at the end of the Session5 Lab [Deadline 02/15/19] |