Jump to content
  • EN

Conditions when device operation is prohibited: Difference between revisions

← Older edit
VisualWikitext
No edit summary
No edit summary
 
(16 intermediate revisions by the same user not shown)
Line 1: Line 1:
==Introduction==
==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.<br/>
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''':
In figure 1 block diagram of logic is presented below:


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


===Device Blocking===
===Device Blocking===
Device will automatically stop operating 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. Conditions are hardcoded and cannot be changed:<br>


1. Device starts connect to operator with restricted Mobile Country Code (MCC). Not-Allowed operator list contains MCCs:
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
   250 - Russian Federation
   257 - Belarus
   257 - Belarus
Line 16: Line 16:
   368 - Cuba
   368 - Cuba
   467 - North Korea
   467 - North Korea
2. Device is connected to operator with restricted MCC for full 28 days. <br>
 
<br>
<br>
Device saves a timestamp when it should stop operating (Current timestamp + 28 days).<br>
28-Day Blocking Counter:
<br>
* 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
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.'''
* 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/>
<br/>


===Device Unblocking===
===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. <br>
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/>
<br/>
===Operating Device in Blocked State===
===Operating Device in Blocked State===
<table class="nd-othertables" style="width: 100%;">
<table class="nd-othertables" style="width: 100%;">
Line 85: Line 101:
=== Firmware Upgrade/Downgrade Rules ===
=== Firmware Upgrade/Downgrade Rules ===


Firmware branches have specific restrictions:
Firmwares have specific restrictions:


; Firmware Branch 03.27.16
; Firmware release 03.27.16
* When a device is updated to '''03.27.16.Rev.00''' or a newer revision of this branch:
* 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>
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>
2. Upgrades to newer revisions of '''03.27.16''' is allowed<br>
3. Upgrades to other firmware branches other than '''03.27.16'''.Rev.XX and '''04.00.00.'''Rev.XX is not 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 Branch 04.00.00
; Firmware release 04.00.00
* When a device is updated to '''04.00.00.Rev.00''' or a newer revision of this branch:
* 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>
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>
2. Upgrades to newer versions than '''04.00.00.Rev.00''' is allowed<br>


; 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===
===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>
Retrieved from "https://wiki.teltonika-gps.com/view/Conditions_when_device_operation_is_prohibited"