handover decision: if a new call causes congestion that would trigger immedate re-assignment, assigning the other TCH kind from the start
For example, a call gets established and gets assigned a TCH/F, which would then reduce the amount of free tch-f lchans below the min-free-tch-f setting.
If the cell config is such that the next congestion check would immediately re-assign the lchan to TCH/H within the same cell, then rather assign a TCH/H in the first place.
Same goes for the reverse TCH kinds: avoid assigning TCH/H that would move to TCH/F upon first congestion check.
This requires a new code path into handover decision during handling of BSSMAP Assignment Request.
- is the new lchan causing congestion? (check min-free-tch-X)
- if it would cause congestion and another tch kind would not, suggest a different lchan.
- if this lchan's codec is allowed by the MSC, BSC and MS, use that right from the start.
Maybe this can be abstracted as a handover decision API, where any handover decision implementation can suggest more optimal lchan choices for first assignment.