Conditions when device operation is prohibited
Introduction
From evaluation branch 03.27.16.Rev.00 and also from 04.00.00.Rev.00 base firmware new feature has been implemented to prevent device from operating when it is being used in restricted countries.
In figure 1 block diagram of new logic is presented and it is presented below.
Functionality description
Device checks conditions to block or unblock device each 10 minutes starting from device initialization.
Device Blocking
Device will automatically block itself when conditions will be met. All of the parameters are hardcoded and cannot be changed.
1. Device starts using restricted Mobile Country Code (MCC). Not-Allowed operator list contains MCCs:
250 - Russian Federation 257 - Belarus 432 - Iran 368 - Cuba 467 - North Korea
2. Restricted MCC is used for full 28 days.
Device saves timestamp when device should be blocked (current timestamp + 28 days).
There is possibility to reset this timestamp, to do so, device should stop detecting restricted MCC and spend full 7 days without connecting to it. If device have counted 10 days with banned MCC and stopped detecting it and to reset that time it has not been detecting banned MCC for 5 days and then again detected banned MCC, device will continue counting time before device block from 10 days as it is shown in figure 1.
This 7 days “counter” works in same way, it is not counting days it saves timestamp when block timestamp should be reset.
Device Unblocking
In order to unblock device, as it is shown in block diagram, device have to detect only allowed MCCs for full 7 days, have timesync and have SIM inserted. If this counter will be interrupted by founded banned MCC it will be reset.
This 7 days “counter” use same variable as 7days counter in device block part and it saves timestamp when device can be unblocked. In case if during this 7 days period conditions will be lost timestamp to unblock will be reset and user will have to fulfill conditions for full 7 days again.
Operating Device in Blocked State
| Blocked Features | Description |
|---|---|
| Record saving | Device will stop saving periodic and eventual records. Prior to device blocking saved records will not be lost. |
| Record sending | Device will not send any records to server. Prior saved records will be stored and sent once device is unblocked. |
| Periodic scenario update | Various features will be stopped:
|
| Sleep (Power Update) | Sleep feature will be disabled as well as Charger update, OBD plug out notify and OBD unlocker. Since these tasks runs under Power Update task which is responsible for sleep. |
| Accelerometer | Accelerometer reading will be stopped and accelerometer should not be initialized |
| IO element updating | IO element values will not be updated |
| Accelerometer related scenarios | Movement detection, crash detection etc. |
| BLE Sensors updating | Updating of BLE sensors will be stopped |
Firmware Upgrade Rules
Firmware versions have specific restirctions
- Firmware Branch 03.27.16
- When a device is updated to 03.27.16.Rev.00 or a newer revision of this branch:
- Any downgrade to a version below 03.27.16.Rev.00
- Upgrades to other firmware branches other than 03.27.16.Rev.XX
- Firmware Branch 04.00.00
- When a device is updated to 04.00.00.Rev.00 or a newer revision of this branch:
- Any downgrade to versions below 04.00.00.Rev.00
- Uupgrades to versions newer than 04.00.00 are still permissible.
- Firmware Upgrading Between Branches
- Upgrading from branch 03.27.16 to branch 04.00.00 can only be done using the intermediate version:
- 03.27.16.Rev.02 to 04.00.00.Rev.00
Pass through command
In order to allow client to know the location of the vehicle in special cases, pass through for single command has been implemented. SMS/GPRS command “getgps” will be allowed to be sent every 10 minutes to get location of the device, when it is operating in Blocked state.