aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPau Espin Pedrol <pespin@sysmocom.de>2020-07-20 13:11:04 +0200
committerPau Espin Pedrol <pespin@sysmocom.de>2020-07-20 14:05:01 +0200
commit54873873452989daca5185ad22f788c6bfe64fa2 (patch)
tree63e78232e3365dea98aff32ab4a607ecdefe5d1a
parent1db53c868a7e722834bbbcc637609565df53a5de (diff)
{bts,bsc}.adoc: Drop deprecated OsmoNITB references
dyn_ts_allow_tch_f is also deprecated and should not be used, so drop that too. Change-Id: Icc91dd41a237531cb512fa36d8b18d4d8d5ca8ed
-rw-r--r--doc/manuals/chapters/bsc.adoc11
-rw-r--r--doc/manuals/chapters/bts.adoc11
2 files changed, 8 insertions, 14 deletions
diff --git a/doc/manuals/chapters/bsc.adoc b/doc/manuals/chapters/bsc.adoc
index 49d25e5a9..0d3ded5c4 100644
--- a/doc/manuals/chapters/bsc.adoc
+++ b/doc/manuals/chapters/bsc.adoc
@@ -1,9 +1,5 @@
== BSC level configuration
-The BSC component is shared between OsmoBSC and OsmoNITB. This chapter
-describes some of the configuration options related to this shared BSC
-component.
-
=== Hand-over
==== Hand-over in GSM
@@ -25,11 +21,10 @@ communicates those by means of RSL to the BSC.
The hand-over decision is made by an algorithm that processes those
measurement results and determines when to perform the hand-over.
-==== Configuration of hand-over in OsmoBSC/OsmoNITB
+==== Configuration of hand-over in OsmoBSC
-OsmoBSC (like the internal BSC component of OsmoNITB) only support
-so-called intra-BSC hand-over, where the hand-over is performed between
-two BTSs within the same BSC.
+OsmoBSC only support so-called intra-BSC hand-over, where the hand-over is
+performed between two BTSs within the same BSC.
Hand-over is enabled and configured by the use of a set of `handover`
commands. Using those, you can tune the key parameters of the hand-over
diff --git a/doc/manuals/chapters/bts.adoc b/doc/manuals/chapters/bts.adoc
index 223cec169..94e89a41c 100644
--- a/doc/manuals/chapters/bts.adoc
+++ b/doc/manuals/chapters/bts.adoc
@@ -287,9 +287,9 @@ and then assign a logical TCH channel on it. Hence, though compatibility with
the BTS needs to be ensured, any MSC is compatible with dynamic timeslots by
definition.
-OsmoBSC and OsmoNITB support two kinds of dynamic timeslot handling, configured
-via the `network` / `bts` / `trx` / `timeslot` / `phys_chan_config`
-configuration. Not all BTS models support dynamic channels.
+OsmoBSC supports two kinds of dynamic timeslot handling, configured via the
+`network` / `bts` / `trx` / `timeslot` / `phys_chan_config` configuration. Not
+all BTS models support dynamic channels.
[[dyn_ts_compat]]
.Dynamic timeslot support by various BTS models
@@ -349,9 +349,8 @@ timeslots to TCH, and no PDCH timeslots would be left for GPRS service.
==== Dynamic Timeslot Configuration Examples
-This is an extract of an `osmo-bsc` or `osmo-nitb` config file. A timeslot
-configuration with five Osmocom style dynamic timeslots and one dedicated PDCH
-may look like this:
+This is an extract of an `osmo-bsc`` config file. A timeslot configuration with
+five Osmocom style dynamic timeslots and one dedicated PDCH may look like this:
----
network