OsmoPCU » History » Revision 23

Revision 22 (neels, 11/30/2016 04:14 PM) → Revision 23/32 (laforge, 10/21/2017 06:40 PM)

h1. osmo-pcu 


 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 
 Um (radio) interface on the MS-facing side, as well as the Gb Interface (NS,BSSGP) on the SGSN-facing side. 

 osmo-pcu is the Osmocom implementation of this PCU functionality. 

 It implements a custom L1 interface that can be used with [[OsmoBTS:]] (specifically its 
 "sysmoBTS": back-end), and also with 

 Towards the SGSN, the BSSGP and NS protocols are implemented over UDP/IP, sometimes called "NS over IP".  
 It has been tested with [[OsmoSGSN:]] as well as an Ericsson SGSN so far. 

 osmo-pcu is now considered stable and already performing useful service for a number of users, but as one 
 of the more recent additions to the Osmocom family, there still is plenty of area for improvement. 

 h2. Position in a typical Osmocom network 

 digraph G { 
     rankdir = LR; 
     OsmoBTS -> OsmoBSC [label="Abis/IP"]; 
     OsmoBSC -> OsmoMSC [label="3GPP AoIP"]; 
     OsmoBTS -> OsmoPCU [label="pcu_sock"]; 
     OsmoPCU -> OsmoSGSN [label="Gb/IP"]; 
     OsmoMSC -> OsmoHLR [label="GSUP"]; 
     OsmoSGSN -> OsmoHLR [label="GSUP"]; 
     OsmoSGSN -> OsmoGGSN [label="Gp"]; 
     OsmoGGSN -> Internet [label="Gi"]; 
     OsmoPCU [color=red]; 

 h2. Manuals 

 * User Manual: 
 * VTY Reference: 
 * Gb/IP Manual: 

 h2. Source Code 

 The source code is available from git:// 

 You can browse it online via 

 h2. Mailing List 

 There is a mailing list for (development) discussion regarding the PCU: 
 You can subscribe to it (or manage your subscription) at 

 Please make sure to read our [[cellular-infrastructure:MailingListRules]] before posting. 

 h3. Supported 

 * GPRS CS1 to CS4 with dynamic link/rate adaption 
 * EDGE MCS1-MCS9 with dynamic link/rate adaption 
 * Single-slot and multi-slot operation on downlink 
 * Single-slot operation on uplink 
 * Independent TFI/USF per PDCH in single-slot allocation mode 
 * Automatic or fixed PDCH allocation algorithm selection 
 * Delayed release of downlink TBF 
 * Active queue management for downlink TBF (!CoDel) 
 * Initial setting of timing advance based on RACH 
 * BSSGP BVC flow control support 
 * Using pchan types of @TCH/F_TCH/H_PDCH@ or @TCH/F_PDCH@, OsmoBTS supports 
   dynamic PDCH/TCH switching (implemented entirely in osmo-bts) 

 h3. Shortcomings / Limitations / Restrictions 

 _Note: this list may be outdated_ 

 * No GPRS/EGPRS mixed mode (yet) 
 * No support for hand-over of any sort yet 
 * No support of processing measurement reports 
 * No timing advance loop, i.e. radial movement is limited 
 * No support for power control 
 * No Packet Access Reject message on congestion, access is just ignored 
 * No PCCCH support 
 * Only "Dynamic allocation RLC data block transfer" is supported 
 * No network controlled measurement/cell reselection order supported 
 * No PTCCH support 
 * No support for Packet Flow Contexts (PFC) 
 * No support for MS or PFC flow control 
 * No support for RLC unacknowledged mode operation 
 * No support for MBMS 

 h2. Authors / Credits 

 osmo-pcu was originally developed by Ivan Kluchnikov and Andreas Everberg. 

 Today it is maintaned by Jacob Erlbeck at sysmocom.
Add picture from clipboard (Maximum size: 48.8 MB)