diff options
| author | Neels Hofmeyr <neels@hofmeyr.de> | 2019-06-24 13:43:06 +0200 |
|---|---|---|
| committer | neels <nhofmeyr@sysmocom.de> | 2019-07-09 15:42:38 +0000 |
| commit | 08371ecc01a996f552ecfd4be9b3b738a9809e05 (patch) | |
| tree | 618aeb2345448d2c165d50cdb0e8fb7401583f85 /doc | |
| parent | 0fb9206c6a4032233a505267cc67d0e4f915a584 (diff) | |
doc/manuals, vty doc: more handover doc clarifications
Related: OS#3487
Change-Id: I1639efb2dbcca4f0e9c33a74f3067606ce5f4209
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/manuals/chapters/handover.adoc | 10 |
1 files changed, 6 insertions, 4 deletions
diff --git a/doc/manuals/chapters/handover.adoc b/doc/manuals/chapters/handover.adoc index 2f9d598c6..bb99751d3 100644 --- a/doc/manuals/chapters/handover.adoc +++ b/doc/manuals/chapters/handover.adoc @@ -434,7 +434,8 @@ with the next Measurement Report received. Configuration settings relevant for algorithm 1 start with `handover1`. For further details, please refer to the OsmoBSC VTY Reference -(<<vty-ref-osmobsc>>) or the telnet VTY online documentation. +(<<vty-ref-osmobsc>>) or the telnet VTY online documentation. See the +`handover1` settings on the `config-net` and `config-net-bts` nodes. ==== Handover Algorithm 2 @@ -451,7 +452,8 @@ configurable (see `handover2 penalty-time` configuration items). Configuration settings relevant for algorithm 2 start with `handover2`. For further details, please refer to the OsmoBSC VTY Reference -<<vty-ref-osmobsc>> or the telnet VTY online documentation. +<<vty-ref-osmobsc>> or the telnet VTY online documentation. See the `handover2` +settings on the `config-net` and `config-net-bts` nodes. ===== Load Distribution @@ -472,8 +474,8 @@ In either case, load distribution will only occur towards neighbor cells that adhere to minimum reception levels and distance, see `min rxlev` and `max distance`. -Load distribution will take effect only for already established voice channels. -An MS will always first establish a voice call with its current cell choice; in +Load distribution will take effect only for already established channels. +For example, an MS will always first establish a voice call with its current cell choice; in load situations, it might be moved to another cell shortly after that. Considering the best neighbor _before_ starting a new voice call might be desirable, but is currently not implemented. Consider that RXLEV/RXQUAL ratings |