Conditions when device operation is prohibited
Introduction
From evaluation firmware version 03.27.16.Rev.XX and also from 04.00.00.Rev.XX base firmware version conditions are enabled to prevent device from operating when it is being used in restricted countries. Block diagram of the logic is presented in figure 1:
Description
Device Blocking
Device will automatically stop operating when conditions will be met. Conditions are hardcoded and cannot be changed:
1. Device connects to operator with restricted Mobile Country Code (MCC) and blocking timestamp is reached.
2. Restricted operator list contains MCCs:
250 - Russian Federation 257 - Belarus 432 - Iran 368 - Cuba 467 - North Korea
28-Day Blocking Counter:
- When a device connects to a operator with restricted MCC (Mobile Country Code) it saves blocking timestamp (current timestamp + 28 days) and starts counter as depicted in figure 1 flowchart. The counter tracks the cumulative number of days the device spends connected to an operator with restricted MCC
- If the device reaches 28 cumulative days of connection to to an operator with restricted MCC, it will be automatically blocked.
Resetting the Counter:
- To reset the counter and timestamp, the device must connect to a non-restricted MCC continuously for 7 uninterrupted days.
- If the device disconnects from operator with a non-restricted MCC or connects to operator with a restricted MCC during this 7-day reset period, the reset process fails, and the 28-day counter continues accumulating.
Example 1:
- The device spends 10 days connected to a operator with restricted MCC.
- It then disconnects for 5 days to to any operator with non-restricted MCC.
- Upon reconnecting to operator with the restricted MCC, the blocking counter resumes from 15 days (as the 7-day reset period was not met).
- If the device remains connected to operator with restricted MCC for an additional 13 days, the counter reaches 28 days, and the device will be blocked.
Example 2:
- The device spends 15 days connected to an operator with restricted MCC.
- It then connects to any operator with an operator with non-restricted MCC continuously for 7 uninterrupted days.
- In this case, the counter is fully reset to 0 days, and after device reconnects to an operator with restricted MCC counter will starts from day 0.
Device Unblocking
To unblock the device, as depicted in figure 1 flowchart, the device must maintain a continuous connection to operators with non-restricted MCCs for a full 7 days. Additionally, the device must have an active time synchronization and an inserted SIM card. If the device connects to a restricted operator MCC during this period, the unblocking counter resets.
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/Downgrade Rules
Firmwares have specific restrictions:
- Firmware release 03.27.16
- When a device is updated to 03.27.16.Rev.00 or a newer revision:
1. Downgrade to a version below 03.27.16.Rev.00 is not allowed
2. Upgrades to newer revisions of 03.27.16 is allowed
3. Upgrades to other firmware other than 03.27.16.Rev.XX and 04.00.00.Rev.XX is not allowed
Note:
- Upgrading from 03.27.16 to 04.00.00 can only be done using the specific intermediate version: 03.27.16.Rev.02
- Firmware release 04.00.00
- When a device is updated to 04.00.00.Rev.00 or a newer revision:
1. Downgrade to a version below 04.00.00.Rev.00 is not allowed
2. Upgrades to newer versions than 04.00.00.Rev.00 is allowed
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.