1. Possible options of using DDS in oneM2M Group Name: ARC Source: KETI, Huawei, Hitachi, China Unicom Meeting Date: 2016-05-15 Agenda Item: DDS binding

2. DDS is not a new topic in oneM2M The use of DDS in oneM2M has been studied and discussed several times – In TR-0009 Protocol Analysis, and advantage and the intended use of DDS has been studied. One of the main conclusion is that: The typical type of application using DDS today is one where low latency, highly deterministic communications is desired between devices. – DDS was discussed in the Industrial Domain Enablement work item, because the wide use of DDS protocol in industry domain. – In TP #22 meeting, DDS binding work item was proposed by KETI, considering the increasing use of DDS in various industries, especially in the scenarios where Real-Time and High-Performance is required.

3. Why DDS is needed in oneM2M (1) From the high level point of view, the intended areas of DDS matches the target market of oneM2M: The Purpose of oneM2M is to specify and promote an M2M Common Service Layer. At the same time, DDS has been widely applied to various industries. ETSI M2M Workshop, Sophia‐Antipolis, Dec. 2015, Nicolas Damour: Standardized Service Layering for IoT in oneM2M oneM2M target markets Areas where DDS is widely used

4. From the technical point of view, DDS can meet some requirements (not limited to as shown below): The oneM2M System shall support the ability for single or multiple M2M Applications to interact with a single or multiple M2M Devices/Gateways (application in the device/gateway) (OSR-009). (the many to many communication of DDS) In automated production with utilization of information and communication technology, behaviours of devices are controlled according to sensor values. In order to achieve adequate control, real-time Ethernet, with which sensors and devices are connected through controllers, are required to provide real-time transmission and a high-level of reliability. (DDS can provide real-time communication) The gateway shall be able to collect data from the field area network (e.g. industrial bus systems) according to the data collection policy stored in the gateway. (DDS has MultiTopic and ContentFilteredTopic which allow for content-based subscriptions ) The data collection policy shall be manageable (configured, updated, deleted..) by M2M Applications on the M2M service platform. (DDS has large number of configuration parameters and QoS policies) The oneM2M system shall be able to transmit data according to priority (CRPR-003). (DDS has the transport priority policy) Why DDS is needed in oneM2M (2)

5. Comparison of message protocols http://portals.omg.org/dds/features-benefits/ TCP/IP

6. Potential use of DDS in oneM2M 1.DDS protocol binding a)Simple binding (like MQTT binding) b)Content awareness binding: enable the oneM2M platform to control and manage all the publish/subscribe relations of the whole system, and meanwhile the data is transported peer to peer. 2.DDS real time subsystem integrated into oneM2M system, and oneM2M AE or IN-CSE can access interested data generated by DDS subsystem or further regulate the QoS policies of the DDS subsystem.

7. 1.a simple binding How the DDS protocol can be used to transport the oneM2M message? All the nodes need to support DDS basic protocol, i.e. DCPS and RTPS Mca or Mcc request and response messages are transported across the DDS protocol DDS Topic name may be defined as: – /oneM2M/req/ / – /oneM2M/resp/ /

8. 1.b content awareness binding DDS is a data centric and peer to peer data transport protocol, how to develop the advantage of the DDS in oneM2M system? How to enable the IoT platform have a overall knowledge of the whole system? For one certain node, what kind of data can it publish, and what kind of data is it interested in? DDS information repository may be implemented within the oneM2M platform: Manage the publish/subscribe relations: when a client requests a subscription for a topic, the DDS Information Repository locates the topic and notifies any existing publishers of the location of the new subscriber. After the publish/subscribe relation is established, the data is transmitted peer to peer, e.g. ASN to MN and ASN to IN DDS Topic name may need to be resource content related

9. 2. Integrate DDS subsystem As the oneM2M platform can be considered as a horizontal platform integrating the subsystems of different verticals, and meanwhile there are already many DDS based industry systems, it is necessary to study further how the existing DDS real time subsystem can be integrated to the oneM2M system. oneM2M platform Smart home devices and subsystem Smart Home application Connected Car application Industry application Connected cars subsystem DDS real time subsystme AE IN-CSE DDS device DDS enabled MN DDS device … DDS data bus oneM2M restful based interface

10. Comparisons of the potential solutions (1) solutionsThe work load/difficulty for standardizationThe work load/difficulty for deployment or the time to market 1a. Simple bindingThe solution is similar to MQTT binding, and only stage 3 PRO WG is impacted. The nodes in the oneM2M system need to be enhanced to support DDS protocol binding. 1b. Content awareness binding The solution is based on solution 1a. Because this aim of solution is P2P data transport, besides PRO WG, stage 2 ARC may be impacted. The oneM2M platform needs to be enhanced to support the repository function, and the nodes in the oneM2M system need to be enhanced to support DDS content awareness binding. 2. Integrating DDS system to oneM2M The scenario is clear and necessary, but at the first stage, a TR is needed to study the possible solution, e.g. QoS mapping, message mapping. Without any changes or enhancements, the DDS subsystem can be integrated to the oneM2M system. Only a interworking gateway is needed to bridge the DDS subsystem and the oneM2M system. Complexity increasing

11. Comparisons of the potential solutions (2) solutionsProsCons 1a. Simple binding1. Standardization work is clear and simple. 1.The nodes in the oneM2M system need to be enhanced to support DDS protocol binding. 2.The real time attribute of the DDS protocol is not kept. 1b. Content awareness binding 1. The nodes in the oneM2M system can transport data peer to peer, and the P2P transport is under the supervisory control of the oneM2M platform. 1. The nodes and the oneM2M platform need to be enhanced. 2. Integrating DDS system to oneM2M 1. Without any changes or enhancements, any existing DDS subsystem can be integrated to the oneM2M system. Only a interworking gateway is needed to bridge the DDS subsystem and the oneM2M system. 1. A TR may be needed to study the possible solutions.

12. DDS work item scope proposal Document title TSDDS protocol binding(1a) CRsCRs to TS-0001 related to DDS protocol binding TRContent awareness binding and Integrating DDS subsystem into the oneM2M system(1b+ 2)

13. Thanks for your listening! Q & A