Role of scripting API & management interface

Transcription

1 Role of scripting & management interface May 18 th, 2017 Kazuaki Nimura Fujitsu Laboratories

2 Role of scripting & management interface Differences ing : Local execution of ing script. Remote execution of ing script. Interface: Remote execution of management command or script. Expose is limited to Local? Expose can be controlled remotely? Remotely exposes Consume d (1) ing(local) (2) ing(remote) 1 (3) interface

3 Role of scripting & management interface Interface: Can setup runtime by downloading a script and executed the script included scripting e.g. AddProperty. (2) and (4) provides almost same outcome. What is our target at all? Consume d (4) interface (script download and execute) 2

4 interface WoT / WoT Servient interface is underlying technology of Runtime. and Managed exists in a runtime (WoT or WoT Servient) and deals provisioning of runtime. Managed works based on management commands. Managed co-work with ing. of Managed provides information about what kind of management capabilities are available in the runtime. Managed deals system call. lication commands interface Managed System Note: script,, Interface, Managed, and Manager Description are tentative names. 3

5 Interface WoT WoT / WoT Servient Managed executes the management commands from Manager interface in. Repository lication lication Interface Managed Manager Description Repository 4

6 Interface WoT Servient WoT Servient Managed can communicates between WoT Servients. lication Interface Managed Manager Managed Interface 5

7 WoT WoT / WoT Servient Behavior of management Interface 1. Manager registers ManagerDesctiption describing the supported management interface. 2. Interface in downloads the ManagerDesctiption and prepares the interface. lication Interface Managed Manager Description Repository 6

8 WoT WoT / WoT Servient Behavior of management Interface 3. Interface interprets management script. Interface sends management command to -> Managed. 3. lication Interface 1. Managed 2. Manager Description Repository 7

9 Behavior of management Interface WoT WoT / WoT Servient 5. Manager execute the management commands. Repository lication lication Interface Managed 2. Manager Description Repository 8

10 Behavior of management Interface WoT WoT / WoT Servient 5. Manager execute the management commands. Repository lication lication (a) of lifecycle (b) of ing Managed (c) of security: permission (d) of security: method and setting Special Manager Description Repository 9

11 (a) of lifecycle Register a script remotely. A script is registered and interpreted, then exposes WoT and registers. Register another script remotely. Another script is added/injected to the executing script, then another WoT is exposed and is updated. Unregister a script / all scripts remotely. A script / all scripts are unregistered, then closes the WoT s and unregisters the s. Start/Stop scripts (Re)boot scripts with sequences WoT Servient Note: It deals handers as well.. 10 WoT Repo.

12 (b) of ing Open/close WoT remotely without script execution on WoT Servient. WoT that a script exposed via can be closed/opened remotely. Register/unregister remotely without script execution on WoT Servient. that a script registered via can be registered/unregistered remotely. WoT Servient WoT Repo. 11

13 (c) of security: permission Permission can be set through management interface. Confirm right to use management interface and give the permission Runtime level: When a script is registered, confirm whether the runtime is allowed to use the interface. level: When a script is registered, a manifest is checked whether the script can be executed on the Servient. Prevent unauthorized access by restricting s that scripts can use level: The script can call s only when those are permitted i.e. specified in Manifest. Manifest WoT Repo. WoT Servient 12

14 (d) of security: method and setting Choose methods of security remotely. Security method used by WoT Servient can be changed. After choosing a method, manages the security setting remotely. E.g. Control permission Authorize clients to access devices ( > Device) Cancel authorization for clients Change key for access WoT Servient Discovery method SSDP mdns Protocol http coap mqtt Security method Key Key ACE PKI * Also can choose discovery methods and protocols clientid0001 clientid0002 Access list deviceid0001 deviceid0002 deviceid0003 key key 13

15 How to achieve the Synchronization Synchronization can be realized as an application of ing. Not necessary to use management interface. Set Servient#1 to generate and Servient#2 to generate from. If changed, e.g. IP address change, it is reflected to the. Servient #2 is notified the change. If changed, e.g. adding a new capability like gradually turn off the Lamp, it is reflected to the. Servient #2 is notified the change and reflected to the exposure. Connect #2 and #1 in Servient #2. When WoT of Servient #2 is called, the callback function calls #1. Device shadow can have application script working between server call and client call in Servient #2. Device shadow Servient#1 Servient#2 14

16