Conditions when device operation is prohibited: Difference between revisions

From Teltonika Telematics Wiki
No edit summary
No edit summary
Line 1: Line 1:
==Introduction==
==Introduction==


In 03.27.16.Rev.00 new feature has been implemented to disable device from operating when it is being used in restricted countries.<br/>
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/>
In figure 1 block diagram of new logic is presented and it is presented below.
In figure 1 block diagram of new logic is presented and it is presented below.


Line 7: Line 7:
==Functionality description==
==Functionality description==


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


===Device Blocking===
===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 block itself 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:<br>
1. Device starts using restricted Mobile Country Code (MCC). Not-Allowed operator list contains MCCs:
<br>250   Russian Federation
  250 - Russian Federation
<br>257   Belarus
  257 - Belarus
<br>432   Iran
  432 - Iran
<br>368   Cuba
  368 - Cuba
<br>467   North Korea
  467 - North Korea
#Use of banned MCC for full 28 days.<br>
2. Restricted MCC is used for full 28 days. <br>
<br>
<br>
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.<br>
Device saves timestamp when device should be blocked (current timestamp + 28 days).<br>
<br>
<br>
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.'''
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.'''
<br/>
<br/>
This 7 days “counter” works in same way, it is not counting days it saves timestamp when block timestamp should be reset.<br>
This 7 days “counter” works in same way, it is not counting days it saves timestamp when block timestamp should be reset.<br>
Line 88: Line 88:


===FW upgrade downgrade rules===
===FW upgrade downgrade rules===
Device updated to this version will automatically have flag set to not allow device downgrade below 03.27.'''16'''.Rev.00 and upgrade to newer than 03.27.'''16'''.Rev.xx branch firmware version.
1. When device is updated to 03.27.'''16'''Rev.00 or newer revision it will have flag set automatically, which will prevent device from being allowed to downgrade below 03.27.'''16'''.Rev.00 and upgrade to newer othen than 03.27.'''16'''.Rev.XX branch firmware versions.<br>
2. When device is updated to '''04.00.00'''.Rev.00 it will have flag set automatically, which will prevent device from being allowed to downgrade below ''04.00.00''' versions, but it is possible to update to any newer version than ''04.00.00'''.<br>
3. It is possible to upgrade device from 03.27.'''16'''.Rev.00 branch version to base firmware version '''04.00.00'''.Rev.00 only using
intermediate version 03.27.'''16.Rev.02'''<br>


===Pass through command===
===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.
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>
<br>

Revision as of 08:52, 17 December 2024

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.

Figure 1 Block diagram of Countryblocking functionality

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:
  • 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


FW upgrade downgrade rules

1. When device is updated to 03.27.16Rev.00 or newer revision it will have flag set automatically, which will prevent device from being allowed to downgrade below 03.27.16.Rev.00 and upgrade to newer othen than 03.27.16.Rev.XX branch firmware versions.
2. When device is updated to 04.00.00.Rev.00 it will have flag set automatically, which will prevent device from being allowed to downgrade below 04.00.00 versions, but it is possible to update to any newer version than 04.00.00.
3. It is possible to upgrade device from 03.27.16.Rev.00 branch version to base firmware version 04.00.00.Rev.00 only using intermediate version 03.27.16.Rev.02

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.