- Количество слайдов: 13
Possible options of using DDS in one. M 2 M Group Name: ARC Source: KETI, Huawei, Hitachi, China Unicom Meeting Date: 2016‐ 05‐ 15 Agenda Item: DDS binding
DDS is not a new topic in one. M 2 M • The use of DDS in one. M 2 M 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.
Why DDS is needed in one. M 2 M (1) From the high level point of view, the intended areas of DDS matches the target market of one. M 2 M: • • The Purpose of one. M 2 M is to specify and promote an M 2 M Common Service Layer. At the same time, DDS has been widely applied to various industries. one. M 2 M target markets ETSI M 2 M Workshop, Sophia‐Antipolis, Dec. 2015, Nicolas Damour: Standardized Service Layering for Io. T in one. M 2 M Areas where DDS is widely used
Why DDS is needed in one. M 2 M (2) From the technical point of view, DDS can meet some requirements (not limited to as shown below): • • • The one. M 2 M System shall support the ability for single or multiple M 2 M Applications to interact with a single or multiple M 2 M 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 Multi. Topic and Content. Filtered. Topic which allow for content‐based subscriptions ) The data collection policy shall be manageable (configured, updated, deleted. . ) by M 2 M Applications on the M 2 M service platform. (DDS has large number of configuration parameters and Qo. S policies) The one. M 2 M system shall be able to transmit data according to priority (CRPR‐ 003). (DDS has the transport priority policy)
Comparison of message protocols TCP/IP http: //portals. omg. org/dds/features‐benefits/
Potential use of DDS in one. M 2 M 1. DDS protocol binding a) b) Simple binding (like MQTT binding) Content awareness binding: enable the one. M 2 M 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 one. M 2 M system, and one. M 2 M AE or IN‐CSE can access interested data generated by DDS subsystem or further regulate the Qo. S policies of the DDS subsystem.
1. a simple binding How the DDS protocol can be used to transport the one. M 2 M 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: – /one. M 2 M/req/
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 one. M 2 M system? How to enable the Io. T 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 one. M 2 M 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
2. Integrate DDS subsystem • As the one. M 2 M platform can be considered as a horizontal platform integrating the subsystems of different verticals, and meanwhile there already many DDS based industry systems, it is necessary to study further how the existing DDS real time subsystem can be integrated to the one. M 2 M system. Smart Home application Connected Car application Industry application AE IN‐CSE one. M 2 M platform DDS device Connected cars subsystem Smart home devices and subsystem one. M 2 M restful based interface DDS real time subsystme DDS enabled MN DDS data bus … DDS device
Comparisons of the potential solutions (1) solutions The work load/difficulty for standardization The work load/difficulty for deployment or the time to market 1 a. Simple binding The solution is similar to MQTT binding, and only stage 3 PRO WG is impacted. The nodes in the one. M 2 M system need to be enhanced to support DDS protocol binding. 1 b. Content awareness binding The solution is based on solution 1 a. Because this aim of solution is P 2 P data transport, besides PRO WG, stage 2 ARC may be impacted. The one. M 2 M platform needs to be enhanced to support the repository function, and the nodes in the one. M 2 M system need to be enhanced to support DDS content awareness binding. 2. Integrating DDS system to one. M 2 M The scenario is clear and necessary, but at the first stage, a TR is needed to study the possible solution, e. g. Qo. S mapping, message mapping. Without any changes or enhancements, the DDS subsystem can be integrated to the one. M 2 M system. Only a interworking gateway is needed to bridge the DDS subsystem and the one. M 2 M system. Complexity increasing
Comparisons of the potential solutions (2) solutions Pros Cons 1 a. Simple binding 1. Standardization work is clear and simple. 1. The nodes in the one. M 2 M system need to be enhanced to support DDS protocol binding. 2. The real time attribute of the DDS protocol is not kept. 1 b. Content awareness binding 1. The nodes in the one. M 2 M system can transport data peer to peer, and the P 2 P transport is under the supervisory control of the one. M 2 M platform. 1. The nodes and the one. M 2 M platform need to be enhanced. 2. Integrating DDS system to one. M 2 M 1. Without any changes or enhancements, any existing DDS subsystem can be integrated to the one. M 2 M system. Only a interworking gateway is needed to bridge the DDS subsystem and the one. M 2 M system. 1. A TR may be needed to study the possible solutions.
DDS work item scope proposal Document title TS DDS protocol binding(1 a) CRs to TS‐ 0001 related to DDS protocol binding TR Content awareness binding and Integrating DDS subsystem into the one. M 2 M system(1 b+ 2)
Thanks for your listening! Q&A