1. FIWARE: IoT – Release 4.3 - Sprint 4.3.2 review
Carlos Ralli . Telefonica I+D
IoT Chapter Architect, FIWARE

2. Latest Overall updates
Overall IoT Architecture significantly updated in the Wiki WIKI
Differentiation between (southbound) NGSI native and others
IoT Edge: management & monitoring of networks, gateways, devices.
Plan to develop SDKs for selected HW platforms
Guide developers with typical use-case scenarios
Changes still to be provided (we have a chapter F2F meeting in July):
Replace “Protocol Adaptor” GE by “IOT Agents (IDAS)” for gateways.
Consider a lightweight ContextBroker for GW2GW comms.
Increase our software for GWs (via OpenCall. TBC)
Backlog/JIRA status improved
All Ges should have improved their karma significantly. However, a small delay in one single task may ruin the whole Karma. Its calculation must be reviewed to reflect the reality (average) versus continuous improvement.
Coordination still to improve (a solution from Orange is on the way)
Catalogue IoT GEis have been updated
Architecture deliverable. To be delivered to Miguel tomorrow EoB.
Per-Gei development activities (see next slides)

3. Backend Device Management (IDAS) updates (TID)
Development
UL2.0 IoT Agent commands triggered by ContextBroker updates.
MQTT commands bug
Update of FIGWAY (client SDK) for the new UL2.0 IoT Agent.
Specification
IoT Manager initial specification.
Installation
New UL2.0 IoT Agent in FIWARE-Lab for the Vienna Dev Week.
New LWM2M IoT Agent in the FIWARE Lab.
Documentation
How-tos for the LWM2M/CoAP IoT Agent
How-tos for the skeleton of IoT Agent (node.js library)
Catalogue & Wiki updated.
New slides and exercises for Vienna Dev Week.

4. IoT Broker updates (NEC)
Development
IoT Broker / Confman Integration
Specification
IoT Broker / Confman modularization requirements
Installation / Release
Source code release
Binaries release
Documentation
Confman documentation
Catalogue & Wiki updated
F2F meeting preparation/organization (NEC is the host)

5. IoT Discovery updates (U.Surrey)
Development
Lite Info Model (Develop a lighter ontology for IoT entities than the one provided by IoT-A, which is more in-line with FIWARE IoT entities)
Update Handler (handle updates to the semantic model when its corresponding NGSI-9 description is updated.)
Specification
No tasks
Installation / Release
Documentation
Course preparation
Catalogue & Wiki updated
F2F meeting preparation/organization (NEC is the host)

6. EspR4FastData (Orange)
Development
Implementation of the new architecture featuring a NGSI Context Manager at the gateway level and a separate CEP that is compliant with the NGSI standard.
Specification
Specify a small-footprint NGSI Context Manager, with other gateway GEs (typically protocol adapters) using it as a common mean of communication between them, and also to the outside world.
Installation / Release
No tasks
Documentation
Catalogue & Wiki updated.

7. GEs in dormant state Protocol adaptor(s) – EPCGE & ZPA.
They will be replaced by lightweight IoT Agents.

8. Architecture.

9. Architecture. Typical use-case Scenarios (I)
Simplest scenario.
Extensively tested with developers. Most Feedback Implemented.
New features are required (Edge management, more Agents)

10. Architecture. Typical use-case Scenarios (II)
Added-value scenario.
Working. Still to be introduced in Hackathons (exercises, challenges, etc.)
Main work: developers to assess benefits and provide feedback.

11. Architecture. Typical use-case Scenarios (III)
FI-CORE target scenario.
Needs integration with new gateway solutions & improve added-value for the whole set.