Osmocom's Base Station Controller for 2G mobile networks https://osmocom.org/projects/osmobsc
Go to file
Pau Espin 9f7611a32f Fix Lb/A SCCP conn lookup after recent regression in optimization patch
In osmo-bsc, there's currently 0..1 Lb links and 0..N A links, where N
is the number of MSC, but links can be shared in the underlaying stack
(struct osmo_sccp_instance), hence range 0..N of different
osmo_sccp_instance (identified by PC).
Even more, the Lb and A link can share the same underlaying stack, so
osmo-bsc can end up with only 1 struct osmo_sccp_instance shared by all
the above mentioned links in case all are configured under the same PC.
Total range A+Lb is 0..(1+N).

A struct gsm_subscriber_conn stores 2 struct sccp_instance*, one for
Lb (conn->lcs.lb.*)and one for A (conn->sccp.*).
They can actually point to the same sccp_instance or to different ones,
as explained above, depending on the configured setup. In any case, a
gsm_subscriber_conn needs 2 rb_nodes since it can hold
any of the 2 conn_ids independently (A or Lb).

The previous patch forgot to add that 2nd rb_node as well as some
initialization and release code for the Lb conn. This patch addresses
that.

When the 2nd rb_node, a problem when iterating the rbtree appears: how to
find out the "conn" pointer from the rb_node pointer, since the rb_node pointer
can be any of the 2 rb_nodes inside the struct at a different offsets.

In order to solve that problem, a new struct bscp_sccp_conn_node is
added, which holds all the relevant information used by the rbtree lookup code
in a generic way (rb_node and conn_id), plus a backpointer to the struct
bsc_gsm_subcriber it relates too.

Fixes: 85062ccad3
Change-Id: If42d93adee71d646766929a09bc01ae92b734ef3
2023-03-17 18:08:26 +00:00
contrib Bump version: 1.9.0.150-64930-dirty → 1.10.0 2023-02-07 17:21:11 +01:00
debian Bump version: 1.9.0.150-64930-dirty → 1.10.0 2023-02-07 17:21:11 +01:00
doc pcu_sock: activate/deactivate PDCH on pcu reconnect 2023-03-07 12:54:58 +00:00
include Fix Lb/A SCCP conn lookup after recent regression in optimization patch 2023-03-17 18:08:26 +00:00
m4 Drop unneeded ax_check_compile_flag.m4 2022-01-11 18:15:20 +01:00
src Fix Lb/A SCCP conn lookup after recent regression in optimization patch 2023-03-17 18:08:26 +00:00
tests Fix Lb/A SCCP conn lookup after recent regression in optimization patch 2023-03-17 18:08:26 +00:00
.gitignore .gitignore: remove non-existing files 2022-07-22 03:35:22 +07:00
.gitreview .gitreview: update repo url to new location 2017-08-08 17:24:04 +02:00
.mailmap add .mailmap file for mapping git author name/mail in shortlog 2016-08-08 17:40:28 +00:00
AUTHORS move openbsc/* to repos root 2017-08-27 03:52:43 +02:00
COPYING move openbsc/* to repos root 2017-08-27 03:52:43 +02:00
Makefile.am manuals: generate vty reference xml at build time 2020-06-16 10:16:30 +00:00
README.md convert README to README.md; expand on all fronts 2022-06-18 13:34:46 +02:00
README.vty-tests update git URLs (git -> https; gitea) 2022-06-18 14:04:11 +02:00
TODO-RELEASE Optimize subscr_conns lookup 2023-03-15 09:44:22 +00:00
configure.ac Bump version: 1.9.0.150-64930-dirty → 1.10.0 2023-02-07 17:21:11 +01:00
git-version-gen git-version-gen: Don't check for .git directory 2018-07-24 18:04:51 +02:00
osmoappdesc.py debian, osmoappdesc.py, tests: switch to python 3 2019-12-11 09:31:40 +01:00

README.md

osmo-bsc - Osmocom BSC Implementation

This repository contains a C-language implementation of a GSM Base Station Controller (BSC). IT is part of the Osmocom Open Source Mobile Communications project.

OsmoBSC exposes

  • A over IP towards an MSC (e.g. OsmoMSC): 3GPP AoIP or SCCPlite
  • Abis interfaces towards various kinds of BTS (osmo-bts, sysmobts, nanoBTS, Siemens, Nokia, Ericsson)
  • The Osmocom typical telnet VTY and CTRL interfaces.
  • The Osmocom typical statsd exporter.
  • Cell Broadcast Service Protocol (CBSP) towards a CBC (Cell Broadcast Centre, such as osmo-cbc).
  • Lb interface towards a SMLC (Serving Mobile Location Centre, such as osmo-smlc).

Homepage

You can find the OsmoBSC issue tracker and wiki online at https://osmocom.org/projects/osmobsc and https://osmocom.org/projects/osmobsc/wiki.

GIT Repository

You can clone from the official osmo-bsc.git repository using

    git clone https://gitea.osmocom.org/cellular-infrastructure/osmo-bsc

There is a web interface at https://gitea.osmocom.org/cellular-infrastructure/osmo-bsc

Documentation

User Manuals and VTY reference manuals are [optionally] built in PDF form as part of the build process.

Pre-rendered PDF version of the current "master" can be found at User Manual as well as the VTY Reference Manual

There also is an Abis reference Manual describing the OsmoBTS specific A-bis dialect, as well as a CBSP Reference Maunal describing the level of CBSP conformance.

Mailing List

Discussions related to osmo-bsc are happening on the openbsc@lists.osmocom.org mailing list, please see https://lists.osmocom.org/mailman/listinfo/openbsc for subscription options and the list archive.

Please observe the Osmocom Mailing List Rules when posting.

Contributing

Our coding standards are described at https://osmocom.org/projects/cellular-infrastructure/wiki/Coding_standards

We us a gerrit based patch submission/review process for managing contributions. Please see https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit for more details

The current patch queue for osmo-bsc can be seen at https://gerrit.osmocom.org/#/q/project:osmo-bsc+status:open

History

OsmoBSC originated from the OpenBSC project, which started as a minimalistic all-in-one implementation of the GSM Network. In 2017, OpenBSC had reached maturity and diversity (including M3UA SIGTRAN and 3G support in the form of IuCS and IuPS interfaces) that naturally lead to a separation of the all-in-one approach to fully independent separate programs as in typical GSM networks.

OsmoBSC was one of the parts split off from the old openbsc.git. Before, it worked as a standalone osmo-bsc binary as well as a combination of libbsc and libmsc, i.e. the old OsmoNITB. Since the standalone OsmoMSC with a true A interface (and IuCS for 3G support) is available, OsmoBSC exists only as a separate standalone entity.

OsmoBSC-NAT is a specialized solution to navigating RTP streams through a NAT. (Todo: describe in more detail)