<p>daniel has uploaded this change for <strong>review</strong>.</p><p><a href="https://gerrit.osmocom.org/11639">View Change</a></p><pre style="font-family: monospace,monospace; white-space: pre-wrap;">common/chapters/bts: Remove duplicate spaces in text<br><br>Change-Id: I38f3e94342461f494ef547bcdccd2594c30e679d<br>---<br>M common/chapters/bts.adoc<br>1 file changed, 21 insertions(+), 21 deletions(-)<br><br></pre><pre style="font-family: monospace,monospace; white-space: pre-wrap;">git pull ssh://gerrit.osmocom.org:29418/osmo-gsm-manuals refs/changes/39/11639/1</pre><pre style="font-family: monospace,monospace; white-space: pre-wrap;"><span>diff --git a/common/chapters/bts.adoc b/common/chapters/bts.adoc</span><br><span>index eb28497..30a33cc 100644</span><br><span>--- a/common/chapters/bts.adoc</span><br><span>+++ b/common/chapters/bts.adoc</span><br><span>@@ -1,20 +1,20 @@</span><br><span> [[bts]]</span><br><span> == Reviewing and Provisioning BTS configuration</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-The main functionality of the BSC component is to manage BTSs. As such,</span><br><span style="color: hsl(120, 100%, 40%);">+The main functionality of the BSC component is to manage BTSs. As such,</span><br><span> provisioning BTSs within the BSC is one of the most common tasks during</span><br><span style="color: hsl(0, 100%, 40%);">-BSC operation. Just like about anything else in OsmoBSC, they are</span><br><span style="color: hsl(120, 100%, 40%);">+BSC operation. Just like about anything else in OsmoBSC, they are</span><br><span> configured using the VTY.</span><br><span> </span><br><span> BTSs are internally numbered with integer numbers starting from "0" for</span><br><span style="color: hsl(0, 100%, 40%);">-the first BTS. BTS numbers have to be contiguous, so you cannot</span><br><span style="color: hsl(120, 100%, 40%);">+the first BTS. BTS numbers have to be contiguous, so you cannot</span><br><span> configure 0,1,2 and then 5.</span><br><span> </span><br><span> </span><br><span> === Reviewing current BTS status and configuration</span><br><span> </span><br><span> In order to view the status and properties of a BTS, you can issue the</span><br><span style="color: hsl(0, 100%, 40%);">-`show bts` command. If used without any BTS number, it will display</span><br><span style="color: hsl(120, 100%, 40%);">+`show bts` command. If used without any BTS number, it will display</span><br><span> information about all provisioned BTS numbers.</span><br><span> </span><br><span> ----</span><br><span>@@ -55,9 +55,9 @@</span><br><span> specified BTS (`show trx 0 0`).</span><br><span> </span><br><span> Furthermore, information on the individual timeslots can be shown by</span><br><span style="color: hsl(0, 100%, 40%);">-means of `show timeslot`. The output can be restricted to the</span><br><span style="color: hsl(120, 100%, 40%);">+means of `show timeslot`. The output can be restricted to the</span><br><span> timeslots of a single BTS (`show timeslot 0`) or that of a single</span><br><span style="color: hsl(0, 100%, 40%);">-TRX (`show timeslot 0 0`). Finally, you can restrict the output to</span><br><span style="color: hsl(120, 100%, 40%);">+TRX (`show timeslot 0 0`). Finally, you can restrict the output to</span><br><span> a single timeslot by specifying the BTS, TRX and TS numbers (`show</span><br><span> timeslot 0 0 4`).</span><br><span> </span><br><span>@@ -74,7 +74,7 @@</span><br><span> === Provisioning a new BTS</span><br><span> </span><br><span> In order to provision BTSs, you have to enter the BTS config node of the</span><br><span style="color: hsl(0, 100%, 40%);">-VTY. In order to configure BTS 0, you can issue the following sequence</span><br><span style="color: hsl(120, 100%, 40%);">+VTY. In order to configure BTS 0, you can issue the following sequence</span><br><span> of commands:</span><br><span> </span><br><span> ----</span><br><span>@@ -87,12 +87,12 @@</span><br><span> </span><br><span> At this point, you have a plethora of commands, in fact an entire</span><br><span> hierarchy of commands to configure all aspects of the BTS, as well as</span><br><span style="color: hsl(0, 100%, 40%);">-each of its TRX and each timeslot within each TRX. For a full</span><br><span style="color: hsl(120, 100%, 40%);">+each of its TRX and each timeslot within each TRX. For a full</span><br><span> reference, please consult the telnet VTY integrated help or the respective</span><br><span> chapter in the VTY reference.</span><br><span> </span><br><span> BTS configuration depends quite a bit on the specific BTS vendor and</span><br><span style="color: hsl(0, 100%, 40%);">-model. The section below provides just one possible example for the</span><br><span style="color: hsl(120, 100%, 40%);">+model. The section below provides just one possible example for the</span><br><span> case of a sysmoBTS.</span><br><span> </span><br><span> Note that from the `configure terminal` command onwards, the telnet VTY</span><br><span>@@ -140,7 +140,7 @@</span><br><span> </span><br><span> A GSM BTS periodically transmits a series of 'SYSTEM INFORMATION'</span><br><span> messages to mobile stations, both via the BCCH in idle mode, was well as</span><br><span style="color: hsl(0, 100%, 40%);">-via the SACCH in dedicated mode. There are many different types of such</span><br><span style="color: hsl(120, 100%, 40%);">+via the SACCH in dedicated mode. There are many different types of such</span><br><span> messages. For their detailed contents and encoding, please see _3GPP TS</span><br><span> 24.008_ <<3gpp-ts-24-008>>.</span><br><span> </span><br><span>@@ -161,7 +161,7 @@</span><br><span> === Neighbor List configuration</span><br><span> </span><br><span> Every BTS sends a list of ARFCNs of neighbor cells</span><br><span style="color: hsl(0, 100%, 40%);">-. within its 'SYSTEM INFORMATION 2' (and 2bis/2ter) messages on the BCCH</span><br><span style="color: hsl(120, 100%, 40%);">+. within its 'SYSTEM INFORMATION 2' (and 2bis/2ter) messages on the BCCH</span><br><span> . within its 'SYSTEM INFORMATION 5' messages on SACCH in dedicated mode</span><br><span> </span><br><span> For every BTS config node in the VTY, you can specify the behavior of</span><br><span>@@ -184,17 +184,17 @@</span><br><span> === Configuring GPRS PCU parameters of a BTS</span><br><span> </span><br><span> In the case of BTS models using Abis/IP (IPA), the GPRS PCU is located</span><br><span style="color: hsl(0, 100%, 40%);">-inside the BTS. The BTS then establishes a Gb connection to the SGSN.</span><br><span style="color: hsl(120, 100%, 40%);">+inside the BTS. The BTS then establishes a Gb connection to the SGSN.</span><br><span> </span><br><span> All the BTS-internal PCU configuration is performed via A-bis OML by</span><br><span> means of configuring the 'CELL', 'NSVC' (NS Virtual Connection and 'NSE'</span><br><span> (NS Entity).</span><br><span> </span><br><span> There is one 'CELL' node and one 'NSE' node, but there are two 'NSVC'</span><br><span style="color: hsl(0, 100%, 40%);">-nodes. At the time of this writing, only the NSVC 0 is supported by</span><br><span style="color: hsl(120, 100%, 40%);">+nodes. At the time of this writing, only the NSVC 0 is supported by</span><br><span> OsmoBTS, while both NSVC are supported by the ip.access nanoBTS.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-The respective VTY configuration parameters are described below. They</span><br><span style="color: hsl(120, 100%, 40%);">+The respective VTY configuration parameters are described below. They</span><br><span> all exist beneath each BTS VTY config node.</span><br><span> </span><br><span> But let's first start with a small example</span><br><span>@@ -224,29 +224,29 @@</span><br><span> </span><br><span> ==== `gprs cell bvci <2-65535>`</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-Configures the 'BSSGP Virtual Circuit Identifier'. It must be unique</span><br><span style="color: hsl(120, 100%, 40%);">+Configures the 'BSSGP Virtual Circuit Identifier'. It must be unique</span><br><span> between all BGSGP connections to one SGSN.</span><br><span> </span><br><span> NOTE: It is up to the system administrator to ensure all PCUs are</span><br><span style="color: hsl(0, 100%, 40%);">-allocated an unique bvci. OsmoBSC will not ensure this policy.</span><br><span style="color: hsl(120, 100%, 40%);">+allocated an unique bvci. OsmoBSC will not ensure this policy.</span><br><span> </span><br><span> </span><br><span> ==== `gprs nsei <0-65535>`</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-Configures the 'NS Entity Identifier'. It must be unique between all NS</span><br><span style="color: hsl(120, 100%, 40%);">+Configures the 'NS Entity Identifier'. It must be unique between all NS</span><br><span> connections to one SGSN.</span><br><span> </span><br><span> NOTE: It is up to the system administrator to ensure all PCUs are</span><br><span style="color: hsl(0, 100%, 40%);">-allocated an unique bvci. OsmoBSC will not ensure this policy.</span><br><span style="color: hsl(120, 100%, 40%);">+allocated an unique bvci. OsmoBSC will not ensure this policy.</span><br><span> </span><br><span> </span><br><span> ==== `gprs nsvc <0-1> nsvci <0-65535>`</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-Configures the 'NS Virtual Connection Identifier'. It must be unique</span><br><span style="color: hsl(120, 100%, 40%);">+Configures the 'NS Virtual Connection Identifier'. It must be unique</span><br><span> between all NS virtual connections to one SGSN.</span><br><span> </span><br><span> NOTE: It is up to the system administrator to ensure all PCUs are</span><br><span style="color: hsl(0, 100%, 40%);">-allocated an unique nsvci. OsmoBSC will not ensure this policy.</span><br><span style="color: hsl(120, 100%, 40%);">+allocated an unique nsvci. OsmoBSC will not ensure this policy.</span><br><span> </span><br><span> </span><br><span> ==== `gprs nsvc <0-1> local udp port <0-65535>`</span><br><span>@@ -266,7 +266,7 @@</span><br><span> </span><br><span> ==== `gprs ns timer (tns-block|tns-block-retries|tns-reset|tns-reset-retries|tns-test|tns-alive|tns-alive-retries)` <0-255></span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-Configures the various GPRS NS related timers. Please check the GPRS NS</span><br><span style="color: hsl(120, 100%, 40%);">+Configures the various GPRS NS related timers. Please check the GPRS NS</span><br><span> specification for the detailed meaning of those timers.</span><br><span> </span><br><span> </span><br><span></span><br></pre><p>To view, visit <a href="https://gerrit.osmocom.org/11639">change 11639</a>. To unsubscribe, or for help writing mail filters, visit <a href="https://gerrit.osmocom.org/settings">settings</a>.</p><div itemscope itemtype="http://schema.org/EmailMessage"><div itemscope itemprop="action" itemtype="http://schema.org/ViewAction"><link itemprop="url" href="https://gerrit.osmocom.org/11639"/><meta itemprop="name" content="View Change"/></div></div>
<div style="display:none"> Gerrit-Project: osmo-gsm-manuals </div>
<div style="display:none"> Gerrit-Branch: master </div>
<div style="display:none"> Gerrit-MessageType: newchange </div>
<div style="display:none"> Gerrit-Change-Id: I38f3e94342461f494ef547bcdccd2594c30e679d </div>
<div style="display:none"> Gerrit-Change-Number: 11639 </div>
<div style="display:none"> Gerrit-PatchSet: 1 </div>
<div style="display:none"> Gerrit-Owner: daniel <dwillmann@sysmocom.de> </div>