Project

General

Profile

Actions

OsmoHNBGW

We have implemented 3GPP Iuh support in the Osmocom stack, mostly carried out by employees of sysmocom GmbH1, with highly appreciated (yet undisclosed) external backing.

Iu support in Osmocom allows using a femto-cell aka hNodeB as 3G base transceiver station, thus enabling UMTS voice (IuCS) and data (IuPS) connectivity using FOSS software from the core network right up to the femto-cell's ethernet jack.

Here is an overview of HNBGW operation:

                      Iuh                         IuCS/IuPS

NAS                   +----+----+                 +----+----+
Non-Access Stratum    | CC | MM |                 | CC | MM |
- - - - - - - - - - - +----+----+-------+         +----+----+
                      | RANAP   |       |    H    | RANAP   |
Access Stratum        +---------+ HNBAP |    N    +---------+ - - SCCP USER SAP
                      | RUA     |       |    B    | M3UA    |  \
                      +---------+-------+    -    +---------+  |
                      |        SCTP     |    G    | SCTP    |  } SIGTRAN
                      +-----------------+    W    +---------+  |
                      |        IP       |         | IP      |  /
                      +-----------------+         +---------+

Binary Packages

Osmocom provides binary packages for several flavors of Debian and Ubuntu GNU/Linux on a variety of architectures (i586, x86_64, armhf, armv7l). Unless you are a software developer interested in developing on Osmocom, it is recommended you use those packages instead of building from source.

For more details see Binary_Packages

HNB-GW

The HNB-GW, i.e. the HomeNodeB Gateway, negotiates HNBAP to register hNodeB connections, and then splits Iuh (RUA) to IuCS and IuPS (RANAP). IuCS/RANAP is delivered to the MSC, IuPS/RANAP to the SGSN.

The IuUP/RTP and GTP user plane data is optionally proxied via local MGW and UPF instances, or sent directly to the MSC's MGW and the GGSN. OsmoHNBGW controls its local MGW via the MGCP protocol, and the UPF via the PFCP protocol.

Manuals

Source code

The source code is available from gitea.osmocom.org (module osmo-hnbgw).

Public read-only access is available via

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

You can browse it via gitea: https://gitea.osmocom.org/cellular-infrastructure/osmo-hnbgw

Contributions are welcome via Gerrit.

Test Suite

Some context

See Harald's 3G talk at the 32c32

ASN1 support

RANAP, RUA and HNBAP, which make up the Iuh interface, are ASN1 encoded. Fair enough, but their ASN1 encoding uses APER, and heavily employs Information Object Classes (which basically means it wraps ASN1 encoded binary data in ASN1 IEs, with several levels of depth). In consequence, the libre asn1c compiler as-is unfortunately is not capable of generating de-/encoders for UMTS. The proprietary ffasn1c is capable of that, and we could publish the ffasn1c generated code without licensing problems, but we'd highly prefer to empower the FOSS community with the ability to modify and fix the ASN1 de-/encoders independently of proprietary software.

The great news is that Eurecom4 has worked on supporting both APER and the nested ASN1 structures ("Information Object Classes") in asn1c, and we are able to use their solutions in a FOSS way. With some fixes added, we have both their APER support and their pythonic solution for nested ASN1 available in Osmocom's libasn1c and asn1c git repositories (5).

Another problem with the Iuh ASN1 is that various type names are identical across RANAP, RUA and HNBAP, while their encodings differ. This causes type name collisions in the code generated by asn1c, hence we have added prefixing support to our version of asn1c. This simply means that each RANAP-related type name or function begins with "ranap_", and RUA names begin with "rua_", thus avoiding any and all name collisions between those protocols. See osmo-iuh/include/osmocom/ranap/ and ../rua/.

It could be more beautiful, but the bottom line is that we now have fully free/libre support for Iuh ASN1 encodings. Cheers

See also: generate sources from ASN1 files

External References

1 ​http://sysmocom.de

2 ​https://media.ccc.de/v/32c3-7412-running_your_own_3g_3_5g_network

3 ​http://git.osmocom.org/erlang/osmo_ss7

4 ​http://www.eurecom.fr

5 See ​http://git.osmocom.org/libasn1c/ and ​https://gitea.osmocom.org/osmocom/asn1c, osmo-iuh/master branch

Supported femtocells

In theory, any femtocell supporting a 3GPP Iuh interface should be supported, as long as you have control over it, i.e. can provision it to connect to your osmo-hnbgw installation. We have successfully operated osmo-hnbgw with the following devices:
  • ip.access nano3G-S8
  • ip.access nano3G-S16
  • ip.access nano3G-E16
  • custom hardware using osmo-hnodeb as the hNodeB-side Iuh protocol stack

Commercial Support

Commercial support as well as development, system integration and training services for this project are available from sysmocom

Files (0)

Updated by laforge 10 days ago · 20 revisions

Add picture from clipboard (Maximum size: 48.8 MB)