- User is prohibited to set an action of "no mitigation" or "data throttling"
or "tx backoff" to "extreme up zone".
- User is prohibited to set "normal zone" above 97deg.
- If the module enters into a state of "emergency only" calls, registration
again to a regular call, happens just when the module returns to "no
mitigation" state only.
- A "+CME ERROR: operation not supported" error will be received as a
response.
When temperature exceeds the current state threshold, the thermal
mitigation algorithm searches the next state when this temperature is lower
than threshold. After it finds it, the current state is updated to that state and
then it checks whether action is mitigate. If yes, then it activates the
mitigation according to the action_in of the current state.
When temperature decreases below threshold_clr then it does the same
algorithm as above, but in the opposite direction. It searches the next state
when this temperature is greater than threshold_clr, updates the current
state to that state, and activates mitigation as described above.
In the state definitions there are the following two rules:
- rule 1: overlap between 2 adjacent states of at least 2 deg (Celsius), i.e.:
thr of state(x) - thr_clr of state(x+1) greater or equal than 2
- rule 2: every state shall have free temperature range which has no part
in any overlap range.
This range should be at least 2 deg (Celsius), i.e.:
thre_clr state(x+2) - thre state(x) greater or equal than 2
Rule 1 comes to ensure hysteresis in the transition between two states.
Rule 2 comes to ensure a minimum range for a stable state.
To Next Page
Loading...
Need help?
General
