View source for 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''':

[[File:Fmbdeviceblockingtree.png|thumb|center|<div style="text-align:center;">Block diagram of logic ('''figure 1''')</div>]]
== Description ==

===Device Blocking===
Device will automatically stop operating when conditions will be met. Conditions are hardcoded and cannot be changed:<br>

1. Device connects to operator with restricted Mobile Country Code (MCC) and blocking timestamp is reached.<br>
2. Restricted operator list contains MCCs:
   250 - Russian Federation
   257 - Belarus
   432 - Iran
   368 - Cuba
   467 - North Korea

<br>
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.
<br/>

===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. <br>

<br/>

===Operating Device in Blocked State===
<table class="nd-othertables" style="width: 100%;">
 <tr>
        <th style="width: 30%; text-align:center; border-bottom: 1px solid #4c8bba; vertical-align:middle; border-bottom: 1px solid #4c8bba;; background: #4c8bba; color: white">'''Blocked Features'''</th>
        <th style="width: 70%; text-align:center; border-bottom: 1px solid #4c8bba; vertical-align:middle; border-bottom: 1px solid #4c8bba;; background: #4c8bba; color: white">'''Description'''</th>
    </tr>
        <tr>
        <td style="vertical-align:middle; text-align:center; border-bottom: 1px solid #4c8bba; border-left: 1px solid #4c8bba;">Record saving</td>
        <td style="vertical-align:middle; border-bottom: 1px solid #4c8bba; border-right: 1px solid #4c8bba;">Device will stop saving periodic and eventual records. Prior to device blocking saved records will not be lost.</td>
    </tr>
        <tr>
        <td style="vertical-align:middle; text-align:center; border-bottom: 1px solid #4c8bba; border-left: 1px solid #4c8bba;">Record sending</td>
        <td style="vertical-align:middle; border-bottom: 1px solid #4c8bba; border-right: 1px solid #4c8bba;">Device will not send any records to server. Prior saved records will be stored and sent once device is unblocked.</td>
    </tr>
        <tr>
        <td style="vertical-align:middle; text-align:center; border-bottom: 1px solid #4c8bba; border-left: 1px solid #4c8bba;">Periodic scenario update</td>
        <td style="vertical-align:middle; border-bottom: 1px solid #4c8bba; border-right: 1px solid #4c8bba;">Various features will be stopped:
*	OBD/LVCAN 
*	Output/Input controlling/reading<br>
*	Geofencing<br>
*	Trip<br>
*	Ecodriving<br>
*	GSM Jamming<br>
*	GSM Jamming<br>
*	GNSS Jamming<br>
*	Fuel Consumption<br>
*	Immobilizer<br>
*	Overspeeding<br>
*	Private/Business<br>
*	Ignition update<br>
*	Sleep
</td>
    </tr>
        <tr>
        <td style="vertical-align:middle; text-align:center; border-bottom: 1px solid #4c8bba; border-left: 1px solid #4c8bba;">Sleep (Power Update)</td>
        <td style="vertical-align:middle; border-bottom: 1px solid #4c8bba; border-right: 1px solid #4c8bba;">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.</td>
    </tr>
        <tr>
        <td style="vertical-align:middle; text-align:center;border-bottom: 1px solid #4c8bba; border-left: 1px solid #4c8bba;">Accelerometer</td>
        <td style="vertical-align:middle; border-bottom: 1px solid #4c8bba; border-right: 1px solid #4c8bba;">Accelerometer reading will be stopped and accelerometer should not be initialized</td>
    </tr>
        <tr>
        <td style="vertical-align:middle; text-align:center; border-bottom: 1px solid #4c8bba; border-left: 1px solid #4c8bba;">IO element updating</td>
        <td style="vertical-align:middle; border-bottom: 1px solid #4c8bba; border-right: 1px solid #4c8bba;">IO element values will not be updated</td>
    </tr>
        <tr>
        <td style="vertical-align:middle; text-align:center; border-bottom: 1px solid #4c8bba; border-left: 1px solid #4c8bba;">Accelerometer related scenarios</td>
        <td style="vertical-align:middle; border-bottom: 1px solid #4c8bba; border-right: 1px solid #4c8bba;">Movement detection, crash detection etc.</td>
    </tr>
        <tr>
        <td style="vertical-align:middle; text-align:center; border-bottom: 1px solid #4c8bba; border-left: 1px solid #4c8bba;">BLE Sensors updating</td>
        <td style="vertical-align:middle; border-bottom: 1px solid #4c8bba; border-right: 1px solid #4c8bba;">Updating of BLE sensors will be stopped</td>
    </tr>
</table>


=== 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<br>
2. Upgrades to newer revisions of '''03.27.16''' is allowed<br>
3. Upgrades to other firmware other than '''03.27.16'''.Rev.XX and '''04.00.00.'''Rev.XX is not allowed<br>
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<br>
2. Upgrades to newer versions than '''04.00.00.Rev.00''' is allowed<br>


===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.
<br>