aboutsummaryrefslogtreecommitdiffstats
path: root/doc/manuals/chapters
AgeCommit message (Collapse)AuthorFilesLines
2023-03-03VTY,CTRL: add pchan dynamic/{osmocom,ipaccess}Neels Hofmeyr2-20/+24
We already use "OSMO_DYN" as C name for "fully dynamic" timeslot config, when working with osmo-bsc.cfg I dearly miss this short name, it is a pain / has become ridiculous to write 'tch/f_tch/h_sdcch8_pdch'. Introduce 'dynamic/osmocom' and 'dynamic/ipaccess' as default names for our dynamic timeslots on VTY and CTRL. The old 'tch/f_tch/h_sdcch8_pdch' and 'tch/f_pdch' are still supported. Change-Id: I37719edd867c777d1ce944b8e2f1efffac38f00e
2022-10-20doc: running.adoc: Fix typo in MGW pinning sectionPau Espin Pedrol1-1/+1
Change-Id: If6651bea097790bbf4b536e762ce55ed3dcc9d75
2022-10-20doc: Use mgwpool.adoc from osmo-gsm-manuals.gitPau Espin Pedrol1-239/+0
The adoc file has been moved to osmo-gsm-manuals.git so that it can be included by other apps supporting MGW pooling from libosmo-mgcp-client, such as osmo-msc and osmo-hnbgw. Related: SYS#5987 Depends: osmo-gsm-manuals.git Change-Id Ieda0d4bfe6fc90da6e19c791d8ec2da89427ba3b Change-Id: Icaee61905fbefe4632b562603fce393b70a114b1
2022-10-20doc: Generalize mgwpool.adoc and move BSC-specific sections to runnning.adocPau Espin Pedrol2-82/+79
This is a preparation commit before moving mgwpool.adoc to a share place (osmo-gsm-manuals.adoc) so that other apps like osmo-msc and osmo-hnbgw can also include this section. Related: SYS#5987 Change-Id: Id0d292506e8b2a888c8d7a682a38db80e9d0933a
2022-10-19Use new mgcp-client VTY commands under mgw nodePau Espin Pedrol2-13/+13
New VTY commands have been added recently to the "mgw" node which drop the redundant "mgw" prefix on each fo them. Depends: osmo-mgw.git Change-Id: Id55af13d2ecde49d968b9dca6a2f8108a17ec484 Related: SYS#5987 Change-Id: I71e49cb4d6c2fe54a895aab0b0ba5acc4e57c253
2022-10-19Update examples to use mgw pooling VTY commandsPau Espin Pedrol1-4/+5
Let's avoid guiding users towards the old deprecated VTY interface. Line "mgw endpoint-range" is removed since it's nowadays deprected and implemented as a NOOP. Related: SYS#5987 Change-Id: Iff74a9efca2a0a2c38d5ac39df704b2b211fd906
2022-10-16Introduce support for MGW-pinning per BTSPau Espin Pedrol1-0/+49
This feature allows pinning each BTS to a specific MGW from the configured pool. The pinning can be soft or hard (strict). If strict pinning is not set, the configured MGW is selected with priority, but other MGWs can still be selected during each call setup if the preferred MGW is found not available at that time, hence avoiding denial of service for the entire BTS if that MGW goes down. If strict mode is selected, the call will be refused if the configured preferred MGW is not available at the time the call is set up. It is useful to use this feature when Osmux is configured between the BTS and the BSC and an MGW pool is in use. This way the BSC is capable of grouping all the calls of a BTS towards one MGW, hence taking advantage of the Osmux trunking optimizations to reduce link data usage (AMR payload of several concurrent calls ending up sharing the same underlaying UPD packet). Furthermore, this allows the operator to intelligently spread load over the MGW pool in order to avoid ending up with more than 256 concurrent Osmux circuits on any of the co-located MGWs in the pool (maximum supported at the moment). Related: SYS#5987 Depends: osmo-mgw.git 5d8b5b093595e1203e288c3175c163c0994b1102 Change-Id: I9a7a5af72795faed0d12d9d73b59951b6a0e9c7d
2022-09-30power_control: add CTRL command for sending default paramsVadim Yanitskiy2-2/+14
There exists a VTY command for sending default power control params, but so far there was no CTRL counterpart for it. This patch adds a SET command 'send-power-control-defaults': $ osmo_ctrl.py \ --host 127.0.0.1 -p 4249 \ --set "bts.0.send-power-control-defaults" 1 Similar to 'send-new-system-informations', this command takes an arbitrary dummy value (required for SET), which is simply ignored. Change-Id: Ib370bd97ee2d9f72f8bec553550b1792d1345387 Related: SYS#6138
2022-09-19doc: Document use of Osmux in IPA Abis against OsmoBTSPau Espin Pedrol1-8/+47
Related: SYS#5987 Change-Id: I41788f8d3bc29735cc30516f429311b73ba71910
2022-09-19vty: Allow setting LAC as hexadecimal valuePau Espin Pedrol3-16/+16
The LAC value currently configured is now printed as hexadecimal value too. It can still be entered as a decimal value in order to keep backward compatibility, though the hexadecimal one is now preferred. Related: OS#5631 Depends: libosmocore.git Ia2b7fbbf5502c28374c21dbff548232680da27d4 Change-Id: I9090d73ae9d39244b79b9dbafa1b164faebabc52
2022-06-30lchan_select: implement dynamic selection mode for assignmentVadim Yanitskiy1-2/+65
This change implements an additional channel allocation mode, which can be employed during a TCH channel allocation for assignment. Selection between ascending and descending order is performed depending on pre-configured parameters: * Uplink RxLev threshold and number of samples for averaging, * C0 (BCCH carrier) channel load threshold. This is useful in setups where Tx power of the RF carriers cannot be adjusted +dynamically at run-time and thus BS Power Control cannot be performed. In such setups the BCCH carrier is transmitting at relatively higher power than the other RF carriers. The key idea is to allocate channels in a smarter way, so that UEs with poor signal would get channels on carriers with high Tx power, while UEs with good signal could use carriers with lower Tx power. Change-Id: I1b7a0d706976b73cc5c30a8714b830811addfe8d Related: osmo-ttcn3-hacks.git Ia522f37c1c001b3a36f5145b8875fbb88311c2e5 Related: SYS#5460
2022-06-30lchan_select: allow different alloc order for assignment and handoverVadim Yanitskiy2-7/+20
A follow-up patch implements a special channel allocation mode, which is only working for assignment (basically TCH selection for a voice call). This mode cannot be employed for initial CHANNEL REQUEST or handover due to the absence of an already established lchan. Adding this mode to the existing VTY command syntax would be confusing: channel allocator (ascending|desscending|dynamic) ^^^^^^^ so this patch extends the VTY syntax in a way that it becomes possible to configure different channel allocator modes for different cases: OsmoBSC(config-net-bts)# channel allocator mode ? set-all Set a single mode for all variants chan-req Channel allocation for CHANNEL REQUEST (RACH) assignment Channel allocation for assignment handover Channel allocation for handover The old command syntax, which is basically 'set-all', is kept for backwards compatibility, but marked as deprecated. Change-Id: I3ae73b36ee9433cc768376b56f0765e5f416162f Related: SYS#5460
2022-06-30lchan_select: prepare a list of timeslots once, iterate over itVadim Yanitskiy1-4/+5
The lchan_avail_by_type() attempts to find an unused lchan for the given GSM_LCHAN_* value: TCH/F, TCH/H, or SDCCH. This is achieved by looking up timeslots with compatible GSM_PCHAN_* values. For instance, finding an unused SDCCH lchan may involve: * attempt to find a timeslot with pchan=GSM_PCHAN_CCCH_SDCCH4, * attempt to find a timeslot with pchan=GSM_PCHAN_CCCH_SDCCH4_CBCH, * attempt to find a timeslot with pchan=GSM_PCHAN_SDCCH8_SACCH8C, * attempt to find a timeslot with pchan=GSM_PCHAN_SDCCH8_SACCH8C_CBCH, * attempt to find a timeslot with pchan=GSM_PCHAN_OSMO_DYN (switched), * attempt to find a timeslot with pchan=GSM_PCHAN_OSMO_DYN (not switched). Each attempt involves iterating over all timeslots of each TRX, either in ascending or in descending order (see _lc_dyn_find_bts() and _lc_find_trx()). This patch simplifies the lookup logic by preparing a monolithic array of timeslot pointers once, and then using that array for each GSM_PCHAN_* lookup attempt. This change is required for the upcoming dynamic channel allocation mode, which is fa more complex than the existing ascending/descending ones. A side effect of this change is that the interference aware mode of allocation is not limited by the scope of a single TRX anymore. Interference levels are now compared within the scope of the whole BTS, so that lchans on the other TRXes may be picked if they are better according to the interference reports from the BTS. Change-Id: I7ccc56856bfd40fd7c63b7437736de60c2b516ff Related: SYS#5460
2022-06-23doc/manuals: document channel allocation parametersVadim Yanitskiy2-0/+80
Change-Id: Ib77eb3d4ad896f1e37b52e549ca3c24f4980240b Related: SYS#5460
2022-03-02doc: bsc.adoc: Update timer info from code (gsm_network_T_defs)Pau Espin Pedrol1-11/+11
Change-Id: I1652e6d53f568f606b692b16d4198d5209df2d9c
2021-12-06bts-examples: add example for E1 connected BTSPhilipp Maier1-0/+117
The manual lacks an example on how to set up an E1 connected BTS. Especially the relation between trunk number and E1 line number is not obvious. Change-Id: I02f5d4fe059e5cc9c3ffc2e3636d812532c09239 Related: OS#5308
2021-11-15[overpower] By default, permit only for speech channels using AMRVadim Yanitskiy1-4/+11
Change-Id: I087025f9db59348f2f70d4a291f8d887644d6b17 Related: SYS#5319
2021-11-15[overpower] Allow configuring specific channel mode(s)Vadim Yanitskiy1-0/+2
Change-Id: I34d29d7d0f66c629367f3d6e8a660e199ecbe080 Related: SYS#5319
2021-11-14doc/manuals: fix wrong CI in the inter-BSC handover diagramVadim Yanitskiy1-1/+1
The 'bts0' in BSS 'Beta' has LAC=42/CI=3. There is no LAC=42/CI=6. Change-Id: I0f2e351e802311d4601579c2e755ca13a9056348
2021-11-12doc/manuals: add documentation for Temporary ACCH OverpowerVadim Yanitskiy1-0/+58
Change-Id: Ie995dac6c7083a2b0b4d582f71f55b3736381edb Related: SYS#5319
2021-11-10gsm_data: use ascending order for interference boundariesVadim Yanitskiy1-7/+7
It's more logical to have the boundaries sorted in ascending order: * band 1 represents lowest interference levels, * band 5 represents highest interference levels. Change-Id: Ie9bf4bf0c89418685b8ea5096332d22cfba7c521 Related: SYS#5313
2021-11-10doc/manuals: add documentation for interference reportingVadim Yanitskiy1-0/+72
Change-Id: I3c15b11bbcba0811e3a15fe64365067bf8ad0dae Related: SYS#5313
2021-11-03control.adoc: comment out fixme notePhilipp Maier1-1/+1
The fixme note: "FIXME: add variables defined in src/ctrl/control_if.c?" is not directed at the reader of the manual. It should stay in the source, but it should not be visible in the pdf. Lets comment it out. Change-Id: Id68f53d18f0873af3c07a0ae52cd12bc94bc0b96
2021-11-03bsc_ctrl_commands: change neighbor-list mode/arfcn via control interfacePhilipp Maier1-0/+3
It is possible to change the neighbor-list mode via the VTY from automatic mode to manual neighbor-list configuration. In the manual mode, the user can add ARFCN values manually. This command can be found under the bts node. Lets add pendant of this command on the control interface as well. Change-Id: Id97bc0d31a358db6221c385761773fb48670c921 Related: SYS#5641
2021-11-03heighbor_ident: add/del neighbor cells via ctrl interfacePhilipp Maier1-0/+25
The VTY allows flexible control over the neighbor cell information via the neighbor command, which can be found in the configure terminal under the bts node. Lets add pendant of this command on the control interface as well. Change-Id: I343a40e18fa9b91e6c381912c0426a002841e079 Related: SYS#5641
2021-11-02control.adoc: improve description of command bts.N.send-new-system-informationsPhilipp Maier1-1/+1
Change-Id: I48bdb7fd991dac2d5112440c879d0ded5b726715 Related: SYS#5641
2021-10-07MS Power Control Loop: Use P_CON_INTERVAL=2 by defaultPau Espin Pedrol1-22/+50
Increase the reaction time at the expense of more stable loop with less temporary oscillations. See updated user manual documentation in this commit for a larger description. Related: SYS#5371 Change-Id: I46be244a5e01a74086e3a977ec3ea139742a0074
2021-09-29MS Power Control Loop: Allow Turn off/on C/I independent from value settingPau Espin Pedrol1-7/+11
Improve the current VTY support to allow enabling/disabling C/I logic independent from value setting. This way C/I support can be quickly disabled & enabled. Reminder: changing power parameters still require VTY Command "bts NR resend-power-control-defaults" to be excuted prior to new parameters being applied on the BTS. Related: SYS#4917 Change-Id: Id1224c2d9a52db2ed805c49e048d3086ed0167f5
2021-09-21MS Power Control Loop: Support turn off C/I based logicPau Espin Pedrol1-0/+8
Setting LOWER_CMP_N and UPPER_CMP_N for all channel types can be quite cumbersome and end up in lengthy config files. Let's instead add a placeholder command to apply it to all channel types of a BTS at once. This is useful specially since a user disabling C/I capabilities probably does so because it may require a fair amount of fine-tuning parameters to have it working perfectly. Hence, a user not willing to spend time configuring those parameters correctly (and for which default ones doesn't work properly) will require quick way to get rid of C/I based MS Power Control Loop. By disabling C/I comparison, osmo-bts will rely on RxLev only when applying the MS Power Control Loop, which is fine for non noisy environments. Related: SYS#4917 Change-Id: I0e1a1a9228a15e9ec9c41b7952b03e1d25309706
2021-09-15doc/mgwpool: update documentationPhilipp Maier1-14/+23
The mgw-pool now allows to set a decription for each MGW /MGCP client instance. Update the documentation so that it reflects the current state. Change-Id: I3026e027bba1a9a12ceca64e96df993b5957cb1d Related: SYS#5091
2021-09-13Power Control Loop: Set P_CON_INTERVAL to 1 by defaultPau Espin Pedrol1-9/+35
TS 45.008 section 4.7.1: """ Upon receipt of a command from an SACCH to change its power level on the corresponding uplink channel, the MS shall change to the new level at a rate of one nominal 2 dB power control step every 60 ms (13 TDMA frames), i.e. a range change of 15 steps should take about 900 ms. The change shall commence at the first TDMA frame belonging to the next reporting period (as specified in subclause 8.4). The MS shall change the power one nominal 2 dB step at a time, at a rate of one step every 60 ms following the initial change, irrespective of whether actual transmission takes place or not. """ Since the reported MS_PWR in L1 SACCH Header is, according to specs, the one used for the last block of the previous SACCH period, it becomes clear the first SACCH block after a requested MS Power Level change by the network may contain mismatches between the announced MS_PWR by the MS and the measured Rxlev/RxQual. Hence, let's better use a P_CON_INTERVAL of 1 which retriggers the MS Power Control Loop every second SACCH block. Related: SYS#5371 Change-Id: Iade5b597e0e56b07c6d78995fcec7c641e4e643f
2021-09-13Support Neighbor Address Resolution over PCUIF IPA multiplexPau Espin Pedrol1-6/+28
While NACC was initially developed, it became clear there was need for a way to interact PCU<->BSC in order resolve ARFCN+BSIC into CGI-PS for later RIM usage. Hence, this resolution was first (until today) implemented using an out of bands RPC system using the CTRL interface, which required specific config to be written and matches in osmo-pcu and osmo-bsc VTY (ip+port of the CTRL interface to use). However, this has several shortcomings: * As explained above, specific configuration is required * Since recently, we do support BSC redundancy in osmo-bts. Hence the BTS may switch to a BSC other than first one. If that happened, that'd mean the CTRL interface would still point to the initially configured one, which may not be the same currently serving the PCU. During recent development of ANR related features, a similar need for PCU<->BSC was required, but this time it was decided to extend the IPA multiplex of the Abis OML connection to pass PCUIF messages, transparently forwarded to each side by the BTS. This has the advantage that connection PCU<->BTS is handled by BTS and both sides send messages transparently. Let's switch by default to using this new interface, while still maintaing the old way for a while (announcing them as deprecated) to avoid breaking existing deployments until they are upgraded to new versions of osmo-pcu and osmo-bsc. Change-Id: I9073a121564503f483c84263ac72476041e47c03 Related: SYS#4971
2021-09-06doc: power_control.adoc: Add small time graph showcasing P_CON_INTERVALPau Espin Pedrol1-1/+16
Original graph made by Vadim Yanitskiy. Change-Id: I9b76088b2d46973b477deb555214d64fcc746754 Related: SYS#5371
2021-09-06MS Power Control Loop: Support set up of C/I parameters for osmo-btsPau Espin Pedrol1-4/+54
This commit extends existing VTY and RSL infrastructure to configure and manage MS Power Parameters used in MS Power Control loop, by adding support to set up Carrier-to-Interference (CI) parameters. Using C/I instead of existing RxQual is preferred due to extended granularity of C/I (bigger range than RxQual's 0-7). Furthermore, existing literature (such as "GSM/EDGE: Evolution and Performance" Table 10.3) provides detailed information about expected target values, even different values for different channel types. Hence, it was decided to support setting different MS Power Parameters for different channel types. These MS Power Parameters are Osmocom specific, ie. supported only by newish versions of osmo-bts. Older versions of osmo-bts should ignore the new IEs added just fine. The new IEs containing the MS POwer Parameters are not send for non osmo-bts BTSs, hence this commit is secure with regards to running osmo-bsc against an ip.access BTS such as nanoBTS. Related: SYS#4917 Depends: libosmocore.git Change-Id Iffef0611430ad6c90606149c398d80158633bbca Change-Id: I7e76ec47b323d469f777624b74b08752d1f5584f
2021-09-06doc: power_control.adoc: Improve VTY snippet foot notesPau Espin Pedrol1-8/+10
Change-Id: Ie5f129c418c187d4f331d6e92884f4f507fb018f
2021-09-03osmo_bsc_main: integrate MGW pooling into osmo-bscPhilipp Maier2-0/+246
Since the libosmo-mgcp-client now supports MGW pooling, lets use this feature in osmo-bsc. Large RAN installations may benefit from distributing the RTP voice stream load on multiple media gateways. Depends: osmo-mgw Icaaba0e470e916eefddfee750b83f5f65291a6b0 Change-Id: I8f33ab2cea04b545c403a6fe479aa963a0fc0d0d Related: SYS#5091
2021-08-26doc: manual: Fix typo in textPau Espin Pedrol1-1/+1
Change-Id: I1dfe298ad9a416ea15976527463a55873db56f22
2021-08-19doc: Improve ACC ramp documentationPau Espin Pedrol1-10/+24
Commit below added support for ACC ramping based on channel load, but documentation was not updated with it. Fixes: 1e5e7004dc7987b23f5791366efdf374675e346b Change-Id: I8701386b35ccdebfc843fd00535091648e52f739
2021-08-03osmo_bsc_main: remove unused commandline option -lPhilipp Maier1-2/+0
The option -l ("The local address of the MGCP") is still present in the commandline help and the manual, but it is used nowhere and osmo-bsc exists when it is used. Lets remove it. Change-Id: Ia295f4414e0d6e78b388c0c72f1a5b8df8bc3d7e
2021-08-03running.adoc: explain mgw reset-endpoint VTY settingPhilipp Maier1-0/+5
When OsmoBSC is restarted, it does not automatically clear the calls on the MGW. However, this is an important part of the configuration to avoid trouble with resource leakage on the MGW, so lets make (especially novice) users aware of that option. Change-Id: I19c499c6ac83d7f9437b18b372977f6f2d518adf Depends: osmo-mgw I47e7ff858d5067b46d52329be5f362ff61c0dff8 Related: SYS#5535
2021-07-19handover_ctrl: add control interface for handover settingsPhilipp Maier1-0/+28
The VTY handover_vtc.c offers a large number of handover specific settings. Those settings are (with one exception) auto generated using macros. Lets add an equivalent for the control interface that uses the same auto generation mechanisms. Change-Id: I12f143906818fd6b16e8783157cbb1eb51e49ffc Depends: libosmocore I53fc207677f52b1dc748b01d58424839cdba807c Related: SYS#5369
2021-07-09doc: bts.adoc: Update dyn ts section to include SDCCH8 supportPau Espin Pedrol1-5/+6
Related: SYS#5309 Change-Id: I40f4b19e7df83351c9c9e65d71880ac6aaa4ee88
2021-07-06Rename osmo dyn ts enums to contain SDCCH8Pau Espin Pedrol1-9/+9
They will gain support to be activated as SDCCH/8 soon too. Related: OS#5309 Depends: libosmocore.git I56dcfe4d17899630b17f80145c3ced72f1e91e68 Change-Id: Id5b89fe589a52ff88486435ac43809edb4b80f98
2021-07-05power_control: constrain BS power reduction on BCCH carrierVadim Yanitskiy1-0/+24
BS Power Control is not allowed on the BCCH/CCCH carrier, unless the BTS is operating in the BCCH carrier power reduction mode. Allow constrained BS power reduction (up to 6 dB) on active logical channels iff BCCH carrier power reduction mode is enabled. Take into account that the maximum power difference between a timeslot used for BCCH/CCCH and the timeslot preceding it shall not exceed 3 dB. Change-Id: I2cc6a86731984f586ef35b43a8d3de631f7d8a2f Related: SYS#4919, SYS#4918
2021-07-05power_control: implement BCCH carrier power reduction operationVadim Yanitskiy1-0/+81
The BCCH carrier (sometimes called C0) of a BTS shall maintain discontinuous Downlink transmission at full power in order to stay 'visible' to the mobile stations. Because of that, early versions of 3GPP TS 45.008 prohibited BS power reduction on C0. However, starting from version 13.0.0 (2015-11) there is a feature called 'BCCH carrier power reduction operation'. This is a special mode of operation, where the variation of RF level for some timeslots is relaxed for the purpose of energy saving. In BCCH carrier power reduction operation, for timeslots on the C0 carrier, except timeslots carrying BCCH/CCCH, the output power may be lower than the output power used for timeslots carrying BCCH/CCCH. In this case the maximum allowed difference in output power actually transmitted by the BTS is 6 dB. Introduce a VTY command to turn on and off the BCCH carrier power reduction operation. Also introduce a CTRL command. On the A-bis/RSL, abuse the BS POWER CONTROL message by setting the Channel Number IE to 0x80 (RSL_CHAN_BCCH). Currently, only osmo-bts-trx is supported. A value greater than zero makes it reduce the power on *inactive* timeslots of the BCCH carrier. Sending zero disables the BCCH power reduction mode completely. For more details, see 3GPP TS 45.008, section 7.1, and 3GPP TR 45.926. Change-Id: I047fce33d4d3e4c569dd006ba17858467a2f4783 Related: SYS#4919
2021-06-24control.adoc: add doc for apply-config-filePhilipp Maier1-0/+1
apply-config-file is not documented in the manual. Change-Id: I469e3925c1079e45eea246e599bcd50ba3fc9dd3 Related: SYS#5369
2021-06-24bsc_ctrl_commands: add command to write vty configPhilipp Maier1-0/+1
we recently added control commands to apply vty config files during runtime using the control interface. However, there is no command that allows us to store the config file modifications. Change-Id: If17095bb86f82dd8feb86eb72c4133ea3aa1c3b3 Related: SYS#5369
2021-05-21bts.adoc: fix typo BGSGP -> BSSGPPhilipp Maier1-1/+1
Change-Id: I4387b516c5c116cd7179611dc34a90b0a744cb6c
2021-05-01manual: Include QoS chapter and add osmo-bsc specific exampleHarald Welte1-0/+46
Change-Id: I3b1d44fc545725172142b903190a3ff5094805dd Requires: osmo-gsm-manuals.git Id344c29eda2a9b3e36376302b425e9db1f6c0f28 Requires: libosmo-abis.git I8991dd6eb406a5b9a70498974fc1ad339452f871
2021-04-27manual: Location Services: clarify BSC side addressNeels Hofmeyr1-2/+19
A clarification that I promised a while back but forgot to submit. Related: SYS#4876 Change-Id: I9b06ac7a2f2cb34cabfcec10af761322b8e962fb
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-23 23:26:29 +0000