TC65 JAVA User's Guide
Strictly confidential / Released
s
When an SM with keyword START:install is received and there is a valid parameter set for the operation, the module always reboots either when the operation completed, an error occurred or the safety timer expired. If there is any error during an update operation the old application is kept untouched, with one exception. If there is not enough space in the file system to keep the old and the new application at the same time, the old application is deleted before the download of the new one, therefore it is lost when an error occurs.
If install/update was successful, autostart is set to the new application.
8.6.2Delete
OTAP | Java Application | TC65 | |||||||
Controller | Server | ||||||||
|
|
|
| ||||||
|
|
|
| Parameter SMS |
|
| |||
|
|
| ... |
|
| ||||
|
|
|
|
| |||||
|
|
|
| Parameter SMS with "START:delete" |
|
| - Combination of SMS parameter | ||
|
|
|
|
|
|
| |||
|
|
|
|
|
|
| set and AT parameter set | ||
|
|
|
|
|
|
| - If parameter set complete: | ||
|
|
|
|
|
|
| Close running Java application | ||
|
|
|
|
|
|
| Timeout | Closedown | |
|
|
|
|
|
|
| Start delete procedure | ||
|
|
|
|
|
|
| Delete application dir | ||
|
|
|
| (HTTP Post Result) |
|
|
|
| |
|
|
|
|
|
|
| reboot | ||
|
|
|
|
|
|
|
|
| |
Safety Timeout
Reboot
Figure 19: OTAP: Delete Information Flow (The messages in brackets are optional)
When an SM with keyword START:delete is received and there is a valid parameter set for this operation, the module reboots either when the operation completed, an error occurred or the safety timer expired. If there is any error the application is kept untouched. Autostart is not changed.
TC65 JAVA User's Guide_V05 | Page 44 of 90 | 26.09.2005 |
