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