Edutalk architecture

IoTtalk also provides an advanced feature called AutoGen, which can automatically generate the devices and the projects (services). An example is EduTalk.

We use AutoGen to automatically create an IoTtalk project for an EduTalk course lecture to perform physics experiments through interaction with a Smartphone. This novel approach for integrating IoT with EduTalk is provided by the AutoGen Subsystem (Fig. 2 (i)) that is considered as a platform to create the “EduTalk”

Subsystem (Fig. 2 (j)). The EduTalk subsystem is associated with a web-based GUI (Fig. 2 (k)) that allows the teachers/students to develop the lectures. After the IoT devices of the lecture are set up, the AutoGen Subsystem creates the device (Fig. 2 (a)-(b)). In Fig. 2, HTTPS is used for (e)-(i) and (j)-(k). The arrow link (g)->(k) represents page jumps from the IoTtalk GUI to the EduTalk GUI.

Fig. 3 illustrates an EduTalk service where the user uses the MorSensor (Fig. 3 (a)) and the Smartphone (Fig. 3 (b)) to control the Cyber device (Fig. 3 (c)) and to store data samples to Logger device (Fig. 3 (d)).

Fig. 3. A simplified EduTalk service.

Fig. 4 shows how EduTalk service is created by the AutoGen (Fig. 2(i)).It will automatically generate one input device model: the lectureRC model (Fig. 4 (b)) implements the DA/SA for the remote control device. Similarly, it will automatically initiate two output device models: the lectureCyber model (Fig. 4 (c)) that implements the DA/SA for the Cyber device and the FileLogger model (Fig. 4 (d)) that implements the DA/SA for the Logger device. The lecturerRC model includes Acceleration-I, Orientation-I, Gyroscope-I, Magnetometer-I (the IDFs for the Smartphone sensor) and the Humidity-I, Alcohol-I, UV-I (the IDFs for the MorSensor sensor). The lectureCyber model has Acceleration-O, Orientation-O, Gyroscope-O, Magnetometer-O (the Magnetometer-ODFs for the Smartphone sensor) and the Humidity-Magnetometer-O, Alcohol-Magnetometer-O, UV-Magnetometer-O (the ODFs for the MorSensor sensor). The FileLogger model has sAcceleration-O, sOrientation-O, sGyroscope-O, sMagnetometer-O (the ODFs to collect data from the Smartphone sensor) and the sHumidity-O, sAlcohol-O, sUV-O (the ODFs to collect data from the MorSensor sensor). To control the Cyber device and to save the data to the Logger device, the AutoGen subsystem will connect Acceleration-I with Acceleration-O and sAcceleration-O. In the IoTtalk project of the simplified EduTalk service, the remote control device sends both data to the Cyber device and the Logger device through the same joins.

The AutoGen Subsystem binds the SA/DA of the lectureRC model to the real

device, i.e., the MorSensor in Fig. 3 (a), and the Smartphone in Fig. 3 (b).

SA/DA service is activated

Fig. 4.

The detailed functional block diagram of the EduTalk and the AutoGen Subsystems in Fig. 2 are illustrated in Fig.

main parts: the EduTalk GUI (Fig. 5 (a)), the EduTalk Event Handler (Fig. 5 (b)), the EduTalk Management Procedures (Fig.

AutoGen Subsystem contains three main parts: the the AutoGen Management Procedures

file (Fig. 5 (j)).

In the EduTalk Subsystem, t

settings on lectures, users and databank, such as create, update, retrieve, d lectures and users, and update and retrieve databank

add certain sensors while creating lectures.

handles the events receive

(c)). The EduTalk Event Handler EduTalk Management Procedures (Fig.

EduTalk DB (Fig. 5 (e)).

Subsystem is triggered by the AutoGen Subsystem, and it also sets up the EduTalk GUI (Fig. 5 (a)).

In the AutoGen Subsystem, the AutoGen Event Handler (Fig.

the MorSensor in Fig. 3 (a), and the Smartphone in Fig. 3 (b).

SA/DA service is activated for execution by the AutoGen Subsystem.

. IoTtalk configuration for the EduTalk service.

The detailed functional block diagram of the EduTalk and the AutoGen are illustrated in Fig. 5. The EduTalk Subsystem

: the EduTalk GUI (Fig. 5 (a)), the EduTalk Event Handler (Fig. 5 (b)), the EduTalk Management Procedures (Fig. 5 (d)), and the EduTalk DB (Fig.

AutoGen Subsystem contains three main parts: the AutoGen Event Handler (Fig.

the AutoGen Management Procedures (Fig. 5 (h)), and the EduTalk URL configuration

In the EduTalk Subsystem, the EduTalk GUI (Fig. 5 (a)) allows settings on lectures, users and databank, such as create, update, retrieve, d

lectures and users, and update and retrieve databank. It also allows users to choose to add certain sensors while creating lectures. The EduTalk Event Handler (Fig.

received from the EduTalk GUI and the AutoGen

The EduTalk Event Handler follows their instructions to execute the relevant EduTalk Management Procedures (Fig. 5 (d)), and store the execution results in the

(e)). The initialization program (Fig. 5 (k)) of the EduTalk Subsystem is triggered by the AutoGen Subsystem, and it also sets up the EduTalk

In the AutoGen Subsystem, the AutoGen Event Handler (Fig.

the MorSensor in Fig. 3 (a), and the Smartphone in Fig. 3 (b). Then, the for execution by the AutoGen Subsystem.

IoTtalk configuration for the EduTalk service.

The detailed functional block diagram of the EduTalk and the AutoGen he EduTalk Subsystem consists of four : the EduTalk GUI (Fig. 5 (a)), the EduTalk Event Handler (Fig. 5 (b)), the EduTalk DB (Fig. 5 (e)).The AutoGen Event Handler (Fig. 5 (f)), , and the EduTalk URL configuration

(a)) allows users to make settings on lectures, users and databank, such as create, update, retrieve, delete (CURD)

t also allows users to choose to The EduTalk Event Handler (Fig. 5 (b)) the EduTalk GUI and the AutoGen Subsystem (Fig. 5 execute the relevant execution results in the The initialization program (Fig. 5 (k)) of the EduTalk Subsystem is triggered by the AutoGen Subsystem, and it also sets up the EduTalk In the AutoGen Subsystem, the AutoGen Event Handler (Fig. 5 (f)) handles the

events from the EduTalk Subsystem and the CCM (Fig. 5 (g)).The AutoGen Event Handler parses the event and executes the relevant AutoGen Management Procedures (Fig. 5 (h)), such as create device (Fig. 5 (q)), delete device, and the EduTalk HTTP service (Fig. 5 (n)), which stores all the requests sent from EduTalk to IotTalk. The initialization program (Fig. 5 (i)) of the AutoGen Subsystem is triggered by the installation script of the whole IoTtalk system. After the AutoGen Subsystem is initialized, it activates the initialization program (Fig. 5 (k)) of the EduTalk Subsystem.

Fig. 5. The EduTalk Subsystem and the AutoGen Subsystem.

The Management procedures (Fig. 5 (d)) of EduTalk Subsystem contain three parts: Lecture management (Fig. 5 (m)), User management (Fig. 5 (o)), and DataBank management (Fig. 5 (p)).Fig. 6 shows the lecture management procedures. Teachers can perform operations on lectures, such as create new lectures, query particular lectures, update lecture content URLs, update default program codes, rename lectures, and delete lectures.

Fig.

Fig. 7 shows the user management procedures. The administrator can access and modify users’ information via the user management procedures.

create a new user, query a user’

user’s group from student to teacher versa.

Fig.

Fig. 8 shows the databank management procedures. With procedures, users can maintain their historical data from sensor

inserting data sources, querying data sources, and exporting them to Excel file for subsequent processing.

Fig.

We will focus on the

thesis, if you need more information about management, please refer to “EduTalk: A 3D Platform with IoT” [5].