| Harald Welte | 4ff37fe | 2016-02-20 10:56:10 +0100 | [diff] [blame] | 1 | == Overview |
| 2 | |
| 3 | === About OsmoPCU |
| 4 | |
| 5 | OsmoPCU is the Osmocom implementation of the GPRS PCU (Packet Control |
| 6 | Unit) element inside the GPRS network. |
| 7 | |
| 8 | The OsmoPCU is co-located within the BTS and connects to OsmoBTS via its |
| Jonathan Brielmaier | 58721eb | 2016-05-25 15:01:11 +0200 | [diff] [blame] | 9 | PCU socket interface. |
| Harald Welte | 4ff37fe | 2016-02-20 10:56:10 +0100 | [diff] [blame] | 10 | |
| 11 | On the other side, OsmoPCU is connected via the Gb interface to the |
| 12 | SGSN. |
| 13 | |
| 14 | [[fig-gprs-pcubts]] |
| 15 | .GPRS network architecture with PCU in BTS |
| 16 | [graphviz] |
| 17 | ---- |
| 18 | digraph G { |
| 19 | rankdir=LR; |
| 20 | MS0 [label="MS"] |
| 21 | MS1 [label="MS"] |
| 22 | MS0->BTS [label="Um"] |
| 23 | MS1->BTS [label="Um"] |
| 24 | BTS->BSC [label="Abis"] |
| 25 | BSC->MSC [label="A"] |
| 26 | BTS->PCU [label="pcu_sock"] |
| 27 | PCU->SGSN [label="Gb"] |
| 28 | SGSN->GGSN [label="GTP"] |
| Pau Espin Pedrol | 7b7fb22 | 2021-01-29 13:04:36 +0100 | [diff] [blame] | 29 | PCU [color=red] |
| Harald Welte | 4ff37fe | 2016-02-20 10:56:10 +0100 | [diff] [blame] | 30 | } |
| 31 | ---- |
| 32 | |
| 33 | === Software Components |
| 34 | |
| 35 | OsmoPCU consists of a variety of components, including |
| 36 | |
| 37 | * Gb interface (NS/BSSGP protocol) |
| 38 | * `pcu_sock` interface towards OsmoBTS |
| 39 | * TBF management for uplink and downlink TBF |
| 40 | * RLC/MAC protocol implementation |
| 41 | * per-MS context for each MS currently served |
| 42 | * CSN.1 encoding/decoding routines |
| 43 | |
| 44 | ==== Gb Implementation |
| 45 | |
| 46 | OsmoPCU implements the ETSI/3GPP specified Gb interface, including TS |
| 47 | 08.16 (NS), TS 08.18 (BSSGP) protocols. As transport layer for NS, it |
| 48 | supports NS/IP (NS encapsulated in UDP/IP). |
| 49 | |
| 50 | The actual Gb Implementation is part of the libosmogb library, which is |
| 51 | in turn part of the libosmocore software package. This allows the same |
| 52 | Gb implementation to be used from OsmoPCU, OsmoGbProxy as well as |
| 53 | OsmoSGSN. |
| 54 | |
| 55 | ==== `pcu_sock` Interface to OsmoBTS |
| 56 | |
| 57 | The interface towards OsmoBTS is called 'pcu_sock' and implemented as a |
| 58 | set of non-standardized primitives over a unix domain socket. The |
| 59 | default file system path for this socket is `/tmp/pcu_bts`. |
| 60 | |
| Vadim Yanitskiy | 088dcbc | 2020-05-31 03:54:34 +0700 | [diff] [blame] | 61 | The PCU socket can be changed on both OsmoBTS and OsmoPCU to a different |
| Harald Welte | 4ff37fe | 2016-02-20 10:56:10 +0100 | [diff] [blame] | 62 | file/path name, primarily to permit running multiple independent BTS+PCU |
| 63 | pairs on a single Linux machine without having to use filesystem |
| 64 | namespaces or other complex configurations. |
| 65 | |
| 66 | NOTE: If you change the PCU socket path on OsmoBTS by means of the |
| 67 | `pcu-socket` VTY configuration command, you must ensure to make the |
| 68 | identical change on the OsmoPCU side. |