Skip to content

M0.9 Refactoring

Jump to bottom Edit New page
Riccardo edited this page Jul 18, 2014 · 20 revisions

This page collects design/specification brainstorming notes to support the refactoring activities undergoing v0.9.

Next Meetings

- May 30 at 12:00 AM - Internal Meeting on Data Models
- June 3 at 12:00 AM - Internal Meeting on API Style
- June 3 at 14:30 AM - Internal Meeting on support for IP Devices (with CSP)
- June 6 at 12:00 AM - API and data-models Wrap-up

Meetings Notes (in Italian)

Refactoring goals

  • Centralization of API end-points across the whole JEMMA architecture
  • Harmonization of API style (choices of REST vs. RPC style vs. Event-Oriented depending on the need) and underlying technologies (e.g. Jersey, Jabsorb, etc.)
  • Provide the right SW infrastructure to support harmonized Data Models being agreed in Energy@home Std. WG - possibly keeping some flexibility to map/support 3rd-party data models
  • "hard" separation (inclusion only via external repository - NOT needing to joinly compile) of
    • APIs
    • GUIs
    • JavaGAL
    • "core"
  • Refactor the Reference design to support IP devices Adapters

Reference architecture

North-bound segment

TODO

inputs

  • Example from D. Pala (lettura_potenza_istantanea.pdf) - not public
  • Document B-3 (expected on Oct 2014) and B-5 (expected on Dec. 2014) from Std. WG

standards

  • oneM2M (it should inherit most of ETSI M2M work)
  • Any REST API ? (main isse: shall we find standard resource model in IP devices or we must expect a different adapter for each device ?)
  • XMPP (see IoT standards and [here]
  • MQTT

Core segment

TODO

South-bound segment

Generic wrappers/ Device Access Layer standards

TODO

ZigBee devices and similar

TODO

IP Devices

TODO Overall strategy:

  • Feed early inputs from Std WG (Final results expected in Sept./Nov.)
  • Suggest standards Std WG based on available FOSS tools/implementations available

Current std to be considered:

For Low-power IP devices

Note:Many of these standards are inter-linked with each other

*Notes: *

  • Some of the technologies above are used in commercial/pre-commercial eco-systems such as Thread

For "non-constrained" IP Devices

  • Any REST API ? (main isse: shall we find standard resource model in IP devices or we must expect a different adapter for each device ?)
  • XMPP-oriented devices (see IoT standards and here) - but it's probably more applicable to the north-bound part of the architecture (see here)

Other inputs

  • Document A-3 (expected on Jul 2014) and A-5 (expected on Oct. 2014) from Std. WG

JEMMA Data Models

TODO Overall strategy:

  • feed information about activity on Std WG DataModels
  • feed info on implementation details i.e. how to host, share and ensure alignment of Data Models/Ontology within the JEMMA CEMS and across the domain.

Inputs:

  • Energy@home extension proposal (not yet public - shared by E@h with Zigbee Alliance)

Relevant tools / to be considered for integration or inspiration

Migration strategy

TODO

  • Best ways to shift from v0.2 -> v0.9
Add a custom footer
Add a custom sidebar

Clone this wiki locally