A1256655844VnkwR

1
RTM in SPACE4U Design and Implementation

Hailiang Mei H.Mei_at_tue.nl
2
Outline

• Design of RTM Framework
• Implementation
• Conclusion and Future Work
• Related Works (Possible RTM Approaches)

3
Relation with SIM
get/exec
add/replace delete/exec
4
RTM Framework inside Device
5
Access Management for RTM

• Each node (object) is identified by an URI
• Each node has a set of properties
• This tree can be extended by add message or a
  new installations on the device
• Leaf node can be either a value or a pointer to
  an executable command

6
Secure Communication

• Authentication
• Decryption and encryption
• Maintain log file
• Can keep user update with latest operations
  (Transparent control)

7
RTM Initialization Sub-process (1)
get/exec
add/replace delete/exec
8
RTM Initialization Sub-process (2)

• Consider three roles
• Initiator, doctor(TM) and patient (Terminal)
• Initiator
• Decide the patient and doctor
• Patient
• Send help message to doctor (if known)
• Or broadcast help message
• Doctor
• Check the received help message
• Can request RTM connection with patient

9
Outline

• Design of RTM Framework
• Implementation
• Conclusion and Future Work
• Related Works (Possible RTM Approaches)

10
Comply with ROBOCOP Framework
OS/drivers

• RCDP component is available
• Scommunication can be implemented based on
  open-SSL and SyncML protocol stack
• Access Manager is open

11
RTM Component
12
RTM SIM Integration
13
Implementation plan
14
Conclusion

• Secured RTM (RTM.01, mandatory)
• Management client oriented
• Healthy terminal oriented
• Component downloading due to context changing
  (CAC.0102)
• (Legal) Component sharing (RTM.02, optional)
• Service discovery (RTM.03, optional)
• Non-healthy terminal oriented
• Remote diagnosis (RTM.04, similar to HM.03,
  Mandatory )
• Remote repair (RTM.05, similar to HM.04,
  Mandatory )
• Management server oriented
• User service data survey (RTM.06, optional)
• User transparent control (RTM.07, Mandatory)

15
Conclusion

• Secured RTM (RTM.01, mandatory) ?
• Management client oriented
• Healthy terminal oriented
• Component downloading due to context changing
  (CAC.0102)
• (Legal) Component sharing (RTM.02, optional) ?
• Service discovery (RTM.03, optional) ?
• Non-healthy terminal oriented
• Remote diagnosis (RTM.04, similar to HM.03,
  Mandatory) ?
• Remote repair (RTM.05, similar to HM.04,
  Mandatory ) ?
• Management server oriented
• User service data survey (RTM.06, optional) ?
• User transparent control (RTM.07, Mandatory) ?

16
Future Work

• Formulate access control mechanism
• Some ideas borrowed from SNMP and SyncML
• Limiting the root node access rights properties
• Certain access management might be done by
  interacting with users
• Define communication protocol and message format
• Largely based on SyncML
• Implementing

17
Questions?
18
Outline

• Design of RTM Framework
• Implementation
• Conclusion and Future Work
• Related Works (Possible RTM Approaches)

19
Possible RTM approaches

• Telnet/SSH
• Virtual Network Computing (VNC)
• Web server
• UPnP
• SNMP
• SyncML (Open Mobile Alliance)

20
Virtual Network Computing
21
Virtual Network Computing
22
Web Server

• The device runs a small web server application
• A service runs on the device to generate run-time
  HTML file
• The remote terminal manager access the device via
  the web browser and execute scripts on the device

23
Web Server (example)
24
UPnP
Overall stack
Control stack
25
SNMP
26
SNMP (example)
27
SyncML DM (OMA)
OMA DM
Over the air
28
SyncML DM (OMA)
OMA DM

• Server
• ltGetgt
• ltCmdIDgt4lt/CmdIDgt
• ltItemgt
• ltTargetgt
• ltLocURIgtVendor/Ring_signals/Default_ringlt/LocUR
  Igt
• lt/Targetgt
• lt/Itemgt
• lt/Getgt
• Client
• ltResultsgt
• ltCmdRefgt4lt/CmdRefgt
• ltCmdIDgt7lt/CmdIDgt
• ltItemgt
• ltDatagtMyOwnRinglt/Datagt
• lt/Itemgt
• lt/Resultsgt

29
SyncML DM (OMA)
OMA DM
30
Review of approaches

• Virtual Network Computing (VNC, open source)
  (Dropped due to obvious security problems)
• Web server (Dropped due to less flexibility and
  limited functionalities)
• UPnP based (Dropped due to less competitive with
  SyncML DM)
• SNMP based (Continuing as the complementary)
• SyncML DM (Continuing as the main reference)