forked from cellular-infrastructure/osmo-pcu
f1a7b8fc66
Currently the state on the TBF is set to ASSIGN when it is created and in general changed to FLOW when it is acknowledged by the MS. The moment when the assignment is really transmitted to the MS (which can take some time) is not reflected by the state. A TBF can considered to be valid, when the assignment is received by the MS. Add the state WAIT_ASSIGN that is entered when the assigment has been send to the MS (more precisely: when the corresponding RTS has been processed or the message has been sent to the BTS). The TBF, its PDCH(s), and its TFI can be assumed to be valid, when the TBF has a state of WAIT_ASSIGN or higher (assuming that the TBF starting time has not been set, which is currently only done for SBA, which are not associated with a TBF). Note that due to queuing in the BTS there can still be a invalid time period for immediate assignments, when the request is lingering in the AGCH or PCH queues. Sponsored-by: On-Waves ehf |
||
|---|---|---|
| contrib | ||
| examples | ||
| src | ||
| tests | ||
| .gitignore | ||
| COPYING | ||
| Makefile.am | ||
| README | ||
| TODO | ||
| configure.ac | ||
| git-version-gen | ||
| osmoappdesc.py | ||
README
This is an implementation of Packet Control Unit (PCU) according to TS 04.60 The PCU is part of BSS, so it connects directly to SGSN. == Current limitations == * No PFC support * No fixed allocation support * No extended dynamic allocation support * No unacknowledged mode operation * No PCCCH/PBCCH support * Only single slot assignment on uplink direction * No half-duplex class support (only semi-duplex) * No handover support * No measurement support * No TA loop * No power loop * No CS loop * No EGPRS