# SpecTalk: Conforming IoT Implementations to Sensor Specifications
## 6 Conclusions  
This paper proposed SpecTalk, a platform that automatically generates the code to conform IoT applications to TAICS specifications. Specifically, SpecTalk generates a program to accommodate the API of the IoT DUTs. Then, the device can be tested by SpecTalk following the TAICS data formats. We described three types of tests: self-test, mutual-test, and visual test. A self-test involves the sensors and the actuators of the same DUT. A mutual-test involves the sensors and the actuators of different DUTs. A visual-test uses a monitoring camera to investigate the actuators of multiple DUTs. We conductedthese types of tests in the Hsinchu International AI Smart Park, and the greenhouse on Bao Mountain, Hsinchu. We also exercised acceptance tests of the smart buildings in the China Medical University in Shuinan Trade and Economic Park, and the fountain of the Ming Der High School, Taichung. Our experiments in the tests proved that SpecTalk is feasible and can effectively conform IoT application implementation to TACIS specifications. We also proposed a simple analytic model to select the frequency of control signals for the input patterns in a SpecTalk test. Our study indicates that it is appropriate to select the control signal frequency such that the inter-arrival time between two control signals is larger than 10 times the activation delay of the DUT. In this paper, we conducted a primary derivation of the probability aiming to produce a simple close form. Right now, we do not have enough practical examples to investigate a secondary detailed derivation (which may result in tedious non-close form equations). The secondary derivation will be considered in future work.  
Based on SpecTalk, we can interwork TACIS with all smart applications conforming to the specifications developed by TTC (Japan), TIA (USA), IEEE (USA), CCSA (China), ETSI (EU), ARIB (Japan), TSDSI (India), MTSFB (Malaysia), and TTA (Korea). For example, we can use the procedure in Figure 8 to connect all devices that conform to the ETSI TS 103 410-4 specification. Through this simple process, TACIS data formats can be transformed to the data formats specified by other standard organizations.  
Methodology and formal analysis, Y.-B.L.; conceptualization, S.-L.C. Both authors have read and agreed to the published version of the manuscript.  
This work was supported in part by the Center for Open Intelligent Connectivity from The Featured Areas Research Center Program within the framework of the Higher Education Sprout Project by the Ministry of Education in Taiwan; in part by the Ministry of Science and Technology under Grant 108-2221-E-009-047, Grant 107-2221-E-197-006-MY3, and Grant 108-2321-B-197-003; and in part by the Ministry of Economic Affairs under Grant 107-EC-17-A-02-S5-007. This work was also supported in part by the Artificial Intelligence to Precision Health: Integrating Dynamic Physiological Signals and EMR to build a Medical Digital Twins Platform sponsored by the Taiwan Ministry of Science and Technology under Grant Number: MOST 109-2321-B-009-007.  
The authors declare no conflict of interest.