Gitiles
Code Review Sign In
gerrit.osmocom.org / osmo-bsc / 27683cbe1305c1c2e4c49a1a9333167aa6e30c3c / . / doc / manuals / chapters / bts-examples.adoc
blob: b15fb9921f9bee3bfbb87ff1588d0903a7c6787c [file] [log] [blame]
Oliver Smith27683cb2018-11-15 11:24:47 +0100[diff] [blame^]1[[bts-examples]]
2== OsmoNITB example configuration files
3
4The `openbsc/doc/examples/osmo-nitb` directory in the OpenBSC source
5tree contains a collection of example configuration files, sorted by BTS
6type.
7
8This chapter is illustrating some excerpts from those examples
9
10[[bts_example_bs11]]
11=== Example configuration for OsmoNITB with one dual-TRX BS-11
12
13.OsmoNITB with BS11, 2 TRX, no frequency hopping
14====
15
16----
17e1_input
18 e1_line 0 driver misdn
19network
20 network country code 1
21 mobile network code 1
22 short name OpenBSC
23 long name OpenBSC
24 timer t3101 10
25 timer t3113 60
26 bts 0
27 type bs11 <1>
28 band GSM900
29 cell_identity 1
30 location_area_code 1
31 training_sequence_code 7
32 base_station_id_code 63
33 oml e1 line 0 timeslot 1 sub-slot full <2>
34 oml e1 tei 25 <3>
35 trx 0
36 arfcn 121
37 max_power_red 0
38 rsl e1 line 0 timeslot 1 sub-slot full <4>
39 rsl e1 tei 1 <5>
40 timeslot 0
41 phys_chan_config CCCH+SDCCH4
42 e1 line 0 timeslot 1 sub-slot full
43 timeslot 1
44 phys_chan_config TCH/F
45 e1 line 0 timeslot 2 sub-slot 1 <6>
46 timeslot 2
47 phys_chan_config TCH/F
48 e1 line 0 timeslot 2 sub-slot 2
49 timeslot 3
50 phys_chan_config TCH/F
51 e1 line 0 timeslot 2 sub-slot 3
52 timeslot 4
53 phys_chan_config TCH/F
54 e1 line 0 timeslot 3 sub-slot 0
55 timeslot 5
56 phys_chan_config TCH/F
57 e1 line 0 timeslot 3 sub-slot 1
58 timeslot 6
59 phys_chan_config TCH/F
60 e1 line 0 timeslot 3 sub-slot 2
61 timeslot 7
62 phys_chan_config TCH/F
63 e1 line 0 timeslot 3 sub-slot 3
64 trx 1
65 arfcn 123
66 max_power_red 0
67 rsl e1 line 0 timeslot 1 sub-slot full <4>
68 rsl e1 tei 2 <5>
69 timeslot 0
70 phys_chan_config TCH/F
71 e1 line 0 timeslot 4 sub-slot 0 <6>
72 timeslot 1
73 phys_chan_config TCH/F
74 e1 line 0 timeslot 4 sub-slot 1
75 timeslot 2
76 phys_chan_config TCH/F
77 e1 line 0 timeslot 4 sub-slot 2
78 timeslot 3
79 phys_chan_config TCH/F
80 e1 line 0 timeslot 4 sub-slot 3
81 timeslot 4
82 phys_chan_config TCH/F
83 e1 line 0 timeslot 5 sub-slot 0
84 timeslot 5
85 phys_chan_config TCH/F
86 e1 line 0 timeslot 5 sub-slot 1
87 timeslot 6
88 phys_chan_config TCH/F
89 e1 line 0 timeslot 5 sub-slot 2
90 timeslot 7
91 phys_chan_config TCH/F
92 e1 line 0 timeslot 5 sub-slot 3
93----
94====
95
96<1> The BTS type must be set to __bs11__
97<2> The OML E1 timeslot needs to be identical with what was on the BTS side using LMT.
98<3> The OML TEI value needs to be identical with what was configured on the BTS side using LMT.
99<4> The RSL E1 timeslot can be identical for all TRX.
100<5> The RSL TEI values __must__ be different if multiple TRX share one E1 signalling timeslot.
101<6> The TCH all need to be allocated one 16k sub-slot on the E1
102
103[[bts_example_nbts]]
104=== Example configuration for OsmoNITB with one single-TRX nanoBTS
105
106.OsmoNITB with one single-TRX nanoBTS
107====
108
109----
110e1_input
111 e1_line 0 driver ipa <1>
112network
113 network country code 1
114 mobile network code 1
115 short name OpenBSC
116 long name OpenBSC
117 auth policy closed
118 location updating reject cause 13
119 encryption a5 0
120 neci 1
121 rrlp mode none
122 mm info 1
123 handover 0
124 bts 0
125 type nanobts <2>
126 band DCS1800 <3>
127 cell_identity 0
128 location_area_code 1
129 training_sequence_code 7
130 base_station_id_code 63
131 ms max power 15
132 cell reselection hysteresis 4
133 rxlev access min 0
134 channel allocator ascending
135 rach tx integer 9
136 rach max transmission 7
137 ip.access unit_id 1801 0 <4>
138 oml ip.access stream_id 255 line 0
139 gprs mode none
140 trx 0
141 rf_locked 0
142 arfcn 871 <5>
143 nominal power 23
144 max_power_red 20 <6>
145 rsl e1 tei 0
146 timeslot 0
147 phys_chan_config CCCH+SDCCH4
148 timeslot 1
149 phys_chan_config SDCCH8
150 timeslot 2
151 phys_chan_config TCH/F
152 timeslot 3
153 phys_chan_config TCH/F
154 timeslot 4
155 phys_chan_config TCH/F
156 timeslot 5
157 phys_chan_config TCH/F
158 timeslot 6
159 phys_chan_config TCH/F
160 timeslot 7
161 phys_chan_config TCH/F
162----
163====
164
165<1> You have to configure one virtual E1 line with the
166 IPA driver in order to use Abis/IP. One e1_line is
167 sufficient for any number of A-bis/IP BTSs, there is no
168 limit like in physical E1 lines.
169<2> The BTS type must be set using `type nanobts`
170<3> The GSM band must be set according to the BTS hardware.
171<4> The IPA Unit ID parameter must be set to what has been configured on
172 the BTS side using the __BTS Manager__ or `ipaccess-config`.
173<5> The ARFCN of the BTS.
174<6> All known nanoBTS units have a nominal transmit power of 23 dBm. If
175 a `max_power_red` of 20 (dB) is configured, the resulting output
176 power at the BTS Tx port is 23 - 20 = 3 dBm.
177
178[NOTE]
179====
180The `nominal_power` setting does __not__ influence the transmitted power
181to the BTS! It is a setting by which the system administrator tells the
182BSC about the nominal output power of the BTS. The BSC uses this as
183basis for calculations.
184====
185
186
187[[bts_example_nbts_multi]]
188=== Example configuration for OsmoNITB with multi-TRX nanoBTS
189
190.OsmoNITB configured for dual-TRX (stacked) nanoBTS
191====
192
193----
194e1_input
195 e1_line 0 driver ipa
196network
197 network country code 1
198 mobile network code 1
199 short name OpenBSC
200 long name OpenBSC
201 auth policy closed
202 location updating reject cause 13
203 encryption a5 0
204 neci 1
205 rrlp mode none
206 mm info 0
207 handover 0
208 bts 0
209 type nanobts
210 band DCS1800
211 cell_identity 0
212 location_area_code 1
213 training_sequence_code 7
214 base_station_id_code 63
215 ms max power 15
216 cell reselection hysteresis 4
217 rxlev access min 0
218 channel allocator ascending
219 rach tx integer 9
220 rach max transmission 7
221 ip.access unit_id 1800 0 <1>
222 oml ip.access stream_id 255 line 0
223 gprs mode none
224 trx 0
225 rf_locked 0
226 arfcn 871
227 nominal power 23
228 max_power_red 0
229 rsl e1 tei 0
230 timeslot 0
231 phys_chan_config CCCH+SDCCH4
232 timeslot 1
233 phys_chan_config SDCCH8
234 timeslot 2
235 phys_chan_config TCH/F
236 timeslot 3
237 phys_chan_config TCH/F
238 timeslot 4
239 phys_chan_config TCH/F
240 timeslot 5
241 phys_chan_config TCH/F
242 timeslot 6
243 phys_chan_config TCH/F
244 timeslot 7
245 phys_chan_config TCH/F
246 trx 1
247 rf_locked 0
248 arfcn 873
249 nominal power 23
250 max_power_red 0
251 rsl e1 tei 0
252 timeslot 0
253 phys_chan_config SDCCH8
254 timeslot 1
255 phys_chan_config TCH/F
256 timeslot 2
257 phys_chan_config TCH/F
258 timeslot 3
259 phys_chan_config TCH/F
260 timeslot 4
261 phys_chan_config TCH/F
262 timeslot 5
263 phys_chan_config TCH/F
264 timeslot 6
265 phys_chan_config TCH/F
266 timeslot 7
267 phys_chan_config TCH/F
268----
269====
270
271<1> In this example, the IPA Unit ID is specified as `1800 0`. Thus, the
272 first nanoBTS unit (`trx 0`) needs to be configured to 1800/0/0 and
273 the second nanoBTS unit (`trx 1`) needs to be configured to 1800/0/1.
274 You can configure the BTS unit IDs using the `ipaccess-config`
275 utility included in OpenBSC.
276
277[NOTE]
278====
279For building a multi-TRX setup, you also need to connect the TIB cables
280between the two nanoBTS units, as well as the coaxial/RF AUX cabling.
281====