Introduction
In 03.27.16.Rev.00 new feature has been implemented to disable device from operating when it is being used in banned 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 startup.
Device Blocking
Device will automatically block itself when conditions will be met. All of the parameters are hardcoded and cannot be changed.
- Device starts using banned Mobile Country Code (MCC). Allowed MCC list is made using Auto_APN.csv file. MCC removed from that list: 250 and 257.
- Use of banned MCC for full 28 days.
Device is not counting days until ban, device saves timestamp when device should be blocked (current timestamp + 28 days). That was done to protect device from unnecessary NVRAM read/write operations.
There is possibility to reset this timestamp, to do so, device should stop detecting banned MCC and spend full 7 days without seeing it. In case, for example, 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 |
FW upgrade downgrade rules
Once device will be flagged as Blocked, even in unblocked state it will not be able to downgrade firmware version below 03.27.16 or upgrade to newer than 03.27.16 branch firmware version.
Additionally, new manufactured devices with firmware which does support Device Blocking feature, will automatically have flag set to not allow device downgrade below 03.27.16 and upgrade to newer than 03.27.16 branch firmware version.
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.