Gitiles
Code Review Sign In
gerrit.osmocom.org / osmo-bsc / 2eda570b750b5bfda858d5f73d619d5989a26d65 / . / doc / manuals / chapters / bts-examples.adoc
blob: 58cb3ab175e8c9f06fa9d16d27fe0a6bf521b124 [file] [log] [blame]
Oliver Smith27683cb2018-11-15 11:24:47 +0100[diff] [blame]1[[bts-examples]]
Harald Weltebec10b02019-02-04 23:04:58 +0100[diff] [blame]2== OsmoBSC example configuration files
Oliver Smith27683cb2018-11-15 11:24:47 +0100[diff] [blame]3
Harald Weltebec10b02019-02-04 23:04:58 +0100[diff] [blame]4The `osmo-bsc/doc/examples/osmo-bsc` directory in the OpenBSC source
Oliver Smith27683cb2018-11-15 11:24:47 +0100[diff] [blame]5tree contains a collection of example configuration files, sorted by BTS
6type.
7
8This chapter is illustrating some excerpts from those examples
9
Oliver Smith27683cb2018-11-15 11:24:47 +0100[diff] [blame]10[[bts_example_nbts]]
Harald Weltebec10b02019-02-04 23:04:58 +0100[diff] [blame]11=== Example configuration for OsmoBSC with one single-TRX nanoBTS
Oliver Smith27683cb2018-11-15 11:24:47 +0100[diff] [blame]12
Harald Weltebec10b02019-02-04 23:04:58 +0100[diff] [blame]13.OsmoBSC with one single-TRX nanoBTS
Oliver Smith27683cb2018-11-15 11:24:47 +0100[diff] [blame]14====
15
16----
17e1_input
18 e1_line 0 driver ipa <1>
19network
20 network country code 1
21 mobile network code 1
Oliver Smith27683cb2018-11-15 11:24:47 +0100[diff] [blame]22 encryption a5 0
23 neci 1
Oliver Smith27683cb2018-11-15 11:24:47 +0100[diff] [blame]24 handover 0
25 bts 0
26 type nanobts <2>
27 band DCS1800 <3>
28 cell_identity 0
29 location_area_code 1
30 training_sequence_code 7
31 base_station_id_code 63
32 ms max power 15
33 cell reselection hysteresis 4
34 rxlev access min 0
35 channel allocator ascending
36 rach tx integer 9
37 rach max transmission 7
Eric Wild10def2c2019-06-04 13:38:28 +0200[diff] [blame]38 ipa unit-id 1801 0 <4>
39 oml ipa stream-id 255 line 0
Oliver Smith27683cb2018-11-15 11:24:47 +0100[diff] [blame]40 gprs mode none
41 trx 0
42 rf_locked 0
43 arfcn 871 <5>
44 nominal power 23
45 max_power_red 20 <6>
46 rsl e1 tei 0
47 timeslot 0
48 phys_chan_config CCCH+SDCCH4
49 timeslot 1
50 phys_chan_config SDCCH8
51 timeslot 2
52 phys_chan_config TCH/F
53 timeslot 3
54 phys_chan_config TCH/F
55 timeslot 4
56 phys_chan_config TCH/F
57 timeslot 5
58 phys_chan_config TCH/F
59 timeslot 6
60 phys_chan_config TCH/F
61 timeslot 7
62 phys_chan_config TCH/F
63----
64====
65
66<1> You have to configure one virtual E1 line with the
67 IPA driver in order to use Abis/IP. One e1_line is
68 sufficient for any number of A-bis/IP BTSs, there is no
69 limit like in physical E1 lines.
70<2> The BTS type must be set using `type nanobts`
71<3> The GSM band must be set according to the BTS hardware.
72<4> The IPA Unit ID parameter must be set to what has been configured on
73 the BTS side using the __BTS Manager__ or `ipaccess-config`.
74<5> The ARFCN of the BTS.
75<6> All known nanoBTS units have a nominal transmit power of 23 dBm. If
76 a `max_power_red` of 20 (dB) is configured, the resulting output
77 power at the BTS Tx port is 23 - 20 = 3 dBm.
78
79[NOTE]
80====
81The `nominal_power` setting does __not__ influence the transmitted power
82to the BTS! It is a setting by which the system administrator tells the
83BSC about the nominal output power of the BTS. The BSC uses this as
84basis for calculations.
85====
86
87
88[[bts_example_nbts_multi]]
Harald Weltebec10b02019-02-04 23:04:58 +0100[diff] [blame]89=== Example configuration for OsmoBSC with multi-TRX nanoBTS
Oliver Smith27683cb2018-11-15 11:24:47 +0100[diff] [blame]90
Harald Weltebec10b02019-02-04 23:04:58 +0100[diff] [blame]91.OsmoBSC configured for dual-TRX (stacked) nanoBTS
Oliver Smith27683cb2018-11-15 11:24:47 +0100[diff] [blame]92====
93
94----
95e1_input
96 e1_line 0 driver ipa
97network
98 network country code 1
99 mobile network code 1
Oliver Smith27683cb2018-11-15 11:24:47 +0100[diff] [blame]100 encryption a5 0
101 neci 1
Oliver Smith27683cb2018-11-15 11:24:47 +0100[diff] [blame]102 handover 0
103 bts 0
104 type nanobts
105 band DCS1800
106 cell_identity 0
107 location_area_code 1
108 training_sequence_code 7
109 base_station_id_code 63
110 ms max power 15
111 cell reselection hysteresis 4
112 rxlev access min 0
113 channel allocator ascending
114 rach tx integer 9
115 rach max transmission 7
Eric Wild10def2c2019-06-04 13:38:28 +0200[diff] [blame]116 ipa unit-id 1800 0 <1>
117 oml ipa stream-id 255 line 0
Oliver Smith27683cb2018-11-15 11:24:47 +0100[diff] [blame]118 gprs mode none
119 trx 0
120 rf_locked 0
121 arfcn 871
122 nominal power 23
123 max_power_red 0
124 rsl e1 tei 0
125 timeslot 0
126 phys_chan_config CCCH+SDCCH4
127 timeslot 1
128 phys_chan_config SDCCH8
129 timeslot 2
130 phys_chan_config TCH/F
131 timeslot 3
132 phys_chan_config TCH/F
133 timeslot 4
134 phys_chan_config TCH/F
135 timeslot 5
136 phys_chan_config TCH/F
137 timeslot 6
138 phys_chan_config TCH/F
139 timeslot 7
140 phys_chan_config TCH/F
141 trx 1
142 rf_locked 0
143 arfcn 873
144 nominal power 23
145 max_power_red 0
146 rsl e1 tei 0
147 timeslot 0
148 phys_chan_config SDCCH8
149 timeslot 1
150 phys_chan_config TCH/F
151 timeslot 2
152 phys_chan_config TCH/F
153 timeslot 3
154 phys_chan_config TCH/F
155 timeslot 4
156 phys_chan_config TCH/F
157 timeslot 5
158 phys_chan_config TCH/F
159 timeslot 6
160 phys_chan_config TCH/F
161 timeslot 7
162 phys_chan_config TCH/F
163----
164====
165
166<1> In this example, the IPA Unit ID is specified as `1800 0`. Thus, the
167 first nanoBTS unit (`trx 0`) needs to be configured to 1800/0/0 and
168 the second nanoBTS unit (`trx 1`) needs to be configured to 1800/0/1.
169 You can configure the BTS unit IDs using the `ipaccess-config`
Daniel Willmann803a4dc2019-04-15 16:49:37 +0200[diff] [blame]170 utility included in OsmoBSC.
Oliver Smith27683cb2018-11-15 11:24:47 +0100[diff] [blame]171
172[NOTE]
173====
174For building a multi-TRX setup, you also need to connect the TIB cables
175between the two nanoBTS units, as well as the coaxial/RF AUX cabling.
176====