OsmoPCU » History » Version 22
neels, 11/30/2016 04:14 PM
| 1 | 1 | laforge | h1. osmo-pcu |
|---|---|---|---|
| 2 | 16 | laforge | |
| 3 | 17 | laforge | {{>toc}} |
| 4 | 16 | laforge | |
| 5 | 3 | laforge | A PCU (Packet Control Unit) is one of the two GPRS elements in the BSS. It implements the RLC and MAC layers of the GPRS |
| 6 | 1 | laforge | Um (radio) interface on the MS-facing side, as well as the Gb Interface (NS,BSSGP) on the SGSN-facing side. |
| 7 | |||
| 8 | 3 | laforge | osmo-pcu is the Osmocom implementation of this PCU functionality. |
| 9 | 1 | laforge | |
| 10 | 18 | laforge | It implements a custom L1 interface that can be used with [[OsmoBTS:]] (specifically its |
| 11 | 16 | laforge | "sysmoBTS":http://www.sysmocom.de/products/sysmobts back-end), and also with |
| 12 | 18 | laforge | [[OsmoTRX:]]. |
| 13 | 3 | laforge | |
| 14 | 1 | laforge | Towards the SGSN, the BSSGP and NS protocols are implemented over UDP/IP, sometimes called "NS over IP". |
| 15 | 19 | laforge | It has been tested with [[OsmoSGSN:]] as well as an Ericsson SGSN so far. |
| 16 | 1 | laforge | |
| 17 | 13 | laforge | osmo-pcu is now considered stable and already performing useful service for a number of users, but as one |
| 18 | 1 | laforge | of the more recent additions to the Osmocom family, there still is plenty of area for improvement. |
| 19 | 14 | jerlbeck | |
| 20 | 17 | laforge | h2. Manuals |
| 21 | 11 | laforge | |
| 22 | 17 | laforge | * User Manual: http://ftp.osmocom.org/docs/latest/osmopcu-usermanual.pdf |
| 23 | * VTY Reference: http://ftp.osmocom.org/docs/latest/osmopcu-vty-reference.pdf |
||
| 24 | 20 | laforge | * Gb/IP Manual: http://ftp.osmocom.org/docs/latest/osmopcu-gb.pdf |
| 25 | 16 | laforge | |
| 26 | 17 | laforge | h2. Source Code |
| 27 | |||
| 28 | 1 | laforge | The source code is available from git://git.osmocom.org/osmo-pcu.git |
| 29 | |||
| 30 | You can browse it online via http://cgit.osmocom.org/cgit/osmo-pcu/ |
||
| 31 | |||
| 32 | 16 | laforge | h2. Mailing List |
| 33 | |||
| 34 | There is a mailing list for (development) discussion regarding the PCU: osmocom-net-gprs@lists.osmocom.org |
||
| 35 | You can subscribe to it (or manage your subscription) at http://lists.osmocom.org/cgi-bin/mailman/listinfo/osmocom-net-gprs |
||
| 36 | 1 | laforge | |
| 37 | 21 | laforge | Please make sure to read our [[cellular-infrastructure:MailingListRules]] before posting. |
| 38 | 16 | laforge | |
| 39 | h3. Supported |
||
| 40 | |||
| 41 | * GPRS CS1 to CS4 with dynamic link/rate adaption |
||
| 42 | 1 | laforge | * EDGE MCS1-MCS9 with dynamic link/rate adaption |
| 43 | 16 | laforge | * Single-slot and multi-slot operation on downlink |
| 44 | * Single-slot operation on uplink |
||
| 45 | * Independent TFI/USF per PDCH in single-slot allocation mode |
||
| 46 | * Automatic or fixed PDCH allocation algorithm selection |
||
| 47 | * Delayed release of downlink TBF |
||
| 48 | * Active queue management for downlink TBF (!CoDel) |
||
| 49 | * Initial setting of timing advance based on RACH |
||
| 50 | * BSSGP BVC flow control support |
||
| 51 | 22 | neels | * Using pchan types of @TCH/F_TCH/H_PDCH@ or @TCH/F_PDCH@, OsmoBTS supports |
| 52 | dynamic PDCH/TCH switching (implemented entirely in osmo-bts) |
||
| 53 | 1 | laforge | |
| 54 | |||
| 55 | 16 | laforge | h3. Shortcomings / Limitations / Restrictions |
| 56 | 14 | jerlbeck | |
| 57 | 22 | neels | _Note: this list may be outdated_ |
| 58 | 16 | laforge | |
| 59 | * No GPRS/EGPRS mixed mode (yet) |
||
| 60 | * No support for hand-over of any sort yet |
||
| 61 | * No support of processing measurement reports |
||
| 62 | * No timing advance loop, i.e. radial movement is limited |
||
| 63 | * No support for power control |
||
| 64 | * No Packet Access Reject message on congestion, access is just ignored |
||
| 65 | * No PCCCH support |
||
| 66 | * Only "Dynamic allocation RLC data block transfer" is supported |
||
| 67 | * No network controlled measurement/cell reselection order supported |
||
| 68 | * No PTCCH support |
||
| 69 | * No support for Packet Flow Contexts (PFC) |
||
| 70 | * No support for MS or PFC flow control |
||
| 71 | * No support for RLC unacknowledged mode operation |
||
| 72 | * No support for MBMS |
||
| 73 | |||
| 74 | h2. Authors / Credits |
||
| 75 | |||
| 76 | 1 | laforge | |
| 77 | osmo-pcu was originally developed by Ivan Kluchnikov and Andreas Everberg. |
||
| 78 | |||
| 79 | Today it is maintaned by Jacob Erlbeck at sysmocom. |
