1. RoA and SoA Integration for Message Brokers Group Name: WG2-ARC Source: ALU Meeting Date: 2013-10-21 Agenda Item:

2. © 2013 oneM2M Partners oneM2M-ARC-2013-xxxx-xxxx 2 Outline Specifying Services in oneM2M Integration scenarios of message brokers (e.g. MQTT) Management considerations

3. Specifying Services in oneM2M

4. © 2013 oneM2M Partners oneM2M-ARC-2013-xxxx-xxxx 4 Outline Specifying Services in oneM2M Integration scenarios of message brokers (e.g. MQTT) Management considerations

5. © 2013 oneM2M Partners oneM2M-ARC-2013-xxxx-xxxx 5 What does SoA do for Us? SoA allows for modular software component design – Allows possible pluggable components to existing M2M systems (MQTT, XMPP solutions) – Allows for rapid extensions of additional features (easy add-ons) – Allows for deployed software components to be rapidly enhanced – Allows for easy penetration into existing Enterprise systems (e.g., ERP, CRM)

6. © 2013 oneM2M Partners oneM2M-ARC-2013-xxxx-xxxx 6 What do we have to specify for SoA Services – These are the set of messages that comprise the inter-component and external interfaces) Components for the services – these are those deployable pluggable implementations of the service Unified interfaces that permit communication between Components by simply specifying the message without the need for a specific protocol. – Unified in the sense that we do not have to specify messages for point to point flows between components and worry about their representations in a protocol because most implementations will use an Enterprise Service Bus and the ESB mediates the protocol.

7. © 2013 oneM2M Partners oneM2M-ARC-2013-xxxx-xxxx 7 Integrating RoA and SoA From a specification viewpoint integrating RoA and SoA would require: Resources operations and associated procedures to be defined such that they can be encapsulated as a Service to be used as a service building block and placed in a Service component. Define and document specific Services within the CSFs to be used as a service building block and placed in a Service component Note: These 2 principles would say that a Resource is owned by a CSF by the fact that the Resource is encapsulated by Service and the Services are documented within the CSFs.

8. © 2013 oneM2M Partners oneM2M-ARC-2013-xxxx-xxxx 8 Services – The Minimium Define the subset of services necessary to get the device communicating with applications this would be at a minimum: – M2M Business service subscription – Device/Application Provisioning and Registration with onboarding – Device/Application (CSE) to Server (CSE) protocol negotiation (XMPP, MQTT) – Network service exposure for triggering, M2M Business service subscription – Data Exchange for oversight and monitoring of the M2M traffic between endpoints – Device Management – Security Other services Data Repository, Policy Management would be commodity services that a SP could just buy off-the-shelf and plug into the ESB. Note that Device and Application registration would most likely require a minimalist protocol (possibly IP/UDP based) so that correct Service plugins can be used (open up the transport protocols)

9. Integration of Message Brokers Group Name: WG2-ARC Source: ALU Meeting Date: 2013-10-21 Agenda Item:

10. RoA Integration

11. Device AE AEs CSE Mcc Mca network Mcn MQTT protocol as oneM2M binding Mcc implements MQTT binding Data storage in CSE Full CSE functionality in the Device Mcc with MQTT binding Message protocol Message Broker

12. Device Application (incl. Message Client) Message Broker Applications CSE Int-1 Int-2 Mca Int-3 network Mcn Vanilla Message Client Vanilla Message Client in the device (no CSE) Int-3: CSE provides Message client for Pub/Sub functionality to perform: Optional data storage in the CSE Management Security, etc. no CSE in the device no Mcc

13. Device Application (incl.Message Client) Message Broker Applications CSE Int-1 Int-2 Mcc Mca Int-3 network Mcn Vanilla Message Client and limited CSE functionality in the device Vanilla Message Client in the device Int-3: CSE provides Message Client for pub/sub to perform optional data storage in the CSE Device provides limited CSE functionality to support DM, security, location, etc. CSE needs to understand and negotiate the appropriate Application Protocol on Mcc

14. SoA Integration

15. Device AE AEs CSE Mcc Mca network Mcn MQTT protocol as oneM2M binding MQTT Message Broker simply becomes a plugin to the SoA environment Mcc with MQTT binding Message protocol SubscriptionRegistration Protocol Negotiation Network Service Exposure MQTT Message Broker Data Exchange Device Management Security

16. Management considerations

17. Device Application (incl. Message client) Message Broker Applications CSE Mca M2M Service Administration (subscription, role, etc) network Mcn 1 2 Need to handle M2M subscription management, role management, etc. Question: do we use existing Mca for this, or create new M2M Service administration interfaces (2) Is there a need for 2 (to network) e.g. activate network subscriptions Is there a need for 3: management of Message broker (topics, etc.) 3