Project

General

Profile

OsmoPCU » History » Version 17

laforge, 03/06/2016 05:22 AM
link manuals

1 1 laforge
h1. osmo-pcu
2 16 zecke2
3 17 laforge
{{>toc}}
4 16 zecke2
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 16 zecke2
It implements a custom L1 interface that can be used with [[OsmoBTS]] (specifically its
11
"sysmoBTS":http://www.sysmocom.de/products/sysmobts back-end), and also with
12
[[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 16 zecke2
It has been tested with [[osmo-sgsn]] 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 1 laforge
25 16 zecke2
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 zecke2
33
h2. Mailing List
34
35 1 laforge
There is a mailing list for (development) discussion regarding the PCU: osmocom-net-gprs@lists.osmocom.org
36
You can subscribe to it (or manage your subscription) at http://lists.osmocom.org/cgi-bin/mailman/listinfo/osmocom-net-gprs
37
38
39 16 zecke2
h2. Status
40
41
Information about testing is available here: [[GPRS-testing]]
42
43
44
h3. Supported
45
46
* GPRS CS1 to CS4 with dynamic link/rate adaption
47 1 laforge
* EDGE MCS1-MCS9 with dynamic link/rate adaption
48 16 zecke2
* Single-slot and multi-slot operation on downlink
49
* Single-slot operation on uplink
50
* Independent TFI/USF per PDCH in single-slot allocation mode
51
* Automatic or fixed PDCH allocation algorithm selection
52
* Delayed release of downlink TBF
53
* Active queue management for downlink TBF (!CoDel)
54
* Initial setting of timing advance based on RACH
55
* BSSGP BVC flow control support
56 1 laforge
57
58 16 zecke2
h3. Shortcomings / Limitations / Restrictions
59 14 jerlbeck
60 16 zecke2
61
* No GPRS/EGPRS mixed mode (yet)
62
* Timeslots have to be assigned dedicated as a PDCH, no dynamic PDCH/TCH switching
63
* No support for hand-over of any sort yet
64
* No support of processing measurement reports
65
* No timing advance loop, i.e. radial movement is limited
66
* No support for power control
67
* No Packet Access Reject message on congestion, access is just ignored
68
* No PCCCH support
69
* Only "Dynamic allocation RLC data block transfer" is supported
70
* No network controlled measurement/cell reselection order supported
71
* No PTCCH support
72
* No support for Packet Flow Contexts (PFC)
73
* No support for MS or PFC flow control
74
* No support for RLC unacknowledged mode operation
75
* No support for MBMS
76
77
78
h2. Authors / Credits
79
80 1 laforge
81
osmo-pcu was originally developed by Ivan Kluchnikov and Andreas Everberg.
82
83
Today it is maintaned by Jacob Erlbeck at sysmocom.
Add picture from clipboard (Maximum size: 48.8 MB)