Conditions when device operation is prohibited: Difference between revisions

Revision as of 10:41, 17 December 2024

Introduction

From evaluation branch 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.
In figure 1 block diagram of logic is presented below:

Description

Device checks conditions to block or unblock device each 10 minutes starting from device initialization.

Device Blocking

Device will automatically stop operating when conditions will be met. All of the parameters are hardcoded and cannot be changed.

1. Device starts connect to operator with restricted Mobile Country Code (MCC). Not-Allowed operator list contains MCCs:

  250 - Russian Federation
  257 - Belarus
  432 - Iran
  368 - Cuba
  467 - North Korea

2. Device is connected to operator with restricted MCC for full 28 days.

Device saves a timestamp when it should stop operating (Current timestamp + 28 days).

The device tracks the duration of connection to operators with restricted MCCs for compliance purposes. If the device disconnects from a restricted operator, a 7-day non-connection period is required to reset this counter. For instance, if the device spends 10 days connected to a restricted operator, then disconnects, and reconnects after only 5 days, the 7-day reset period is not met. Consequently, the counter does not reset but continues from the 10-day mark. If the total connected time reaches a specific limit, such as 28 days, the device will automatically stop operating to enforce compliance as it is shown in figure 1.

Device Unblocking

To unblock the device, as depicted in the 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: OBD/LVCAN Output/Input controlling/reading Geofencing Trip Ecodriving GSM Jamming GSM Jamming GNSS Jamming Fuel Consumption Immobilizer Overspeeding Private/Business Ignition update Other SpecFW features Sleep
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

Firmware branches have specific restrictions:

Firmware Branch 03.27.16

When a device is updated to 03.27.16.Rev.00 or a newer revision of this branch:

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 branches other than 03.27.16.Rev.XX and 04.00.00.Rev.XX is not allowed

Firmware Branch 04.00.00

When a device is updated to 04.00.00.Rev.00 or a newer revision of this branch:

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

Firmware Upgrading Between Branches

Upgrading from branch 03.27.16 to branch 04.00.00 can only be done using the specific intermediate version:
- From 03.27.16.Rev.02 to 04.00.00.Rev.XX

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.

@@ Line 1: / Line 1: @@
 ==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.<br/>
+From evaluation branch '''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.<br/>
-In figure 1 block diagram of new logic is presented and it is presented below.
+In figure 1 block diagram of logic is presented below:
-[[File:Fmbdeviceblockingtree.png|Figure 1 Block diagram of Countryblocking functionality|thumb|center]]
+[[File:Fmbdeviceblockingtree.png|Figure 1 Block diagram of logic|thumb|center]]
-==Functionality description==
+== 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.<br>
+Device will automatically stop operating when conditions will be met. All of the parameters are hardcoded and cannot be changed.<br>
-. Device starts using restricted Mobile Country Code (MCC). Not-Allowed operator list contains MCCs:
+. Device starts connect to operator with restricted Mobile Country Code (MCC). Not-Allowed operator list contains MCCs:
 - Russian Federation
 - Belarus
@@ Line 18: / Line 18: @@
 - Cuba
 - North Korea
-. Restricted MCC is used for full 28 days. <br>
+. Device is connected to operator with restricted MCC for full 28 days. <br>
 <br>
-Device saves timestamp when device should be blocked (current timestamp + 28 days).<br>
+Device saves a timestamp when it should stop operating (Current timestamp + 28 days).<br>
 <br>
-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.'''
+The device tracks the duration of connection to operators with restricted MCCs for compliance purposes. If the device disconnects from a restricted operator, a 7-day non-connection period is required to reset this counter. For instance, if the device spends 10 days connected to a restricted operator, then disconnects, and reconnects after only 5 days, the 7-day reset period is not met. Consequently, the counter does not reset but continues from the 10-day mark. If the total connected time reaches a specific limit, such as 28 days, the device will automatically stop operating to enforce compliance as it is shown in '''figure 1.'''
 <br/>
-This 7 days “counter” works in same way, it is not counting days it saves timestamp when block timestamp should be reset.<br>
 ===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.<br>
+To unblock the device, as depicted in the 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>
-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.
 <br/>
 ===Operating Device in Blocked State===