Cellular Network Infrastructure » Radio Access Network » OsmoBSC

We now have these dynamic pchan types:

• TCH/F_PDCH (PDCH ACT style)
• TCH/F_TCH/H_PDCH (CHAN ACT style)

TCH/F_PDCH uses different RSL messaging than TCH/F_TCH/H_PDCH, but
it would be trivial to have a TCH/F_PDCH dynamic TS using the
CHAN ACT way.

I am recording this issue merely for completeness sake, because I
expect us to reject this anyway, because:

• no-one will really want to use TCH/F besides on hardware that is
  only capable of dynamic TCH/F_PDCH (e.g. specific ip.access boxes
  that require PDCH ACT style anyway).
• with osmo-bts, there is no disadvantage in the PDCH ACT style.
  The only way to actually notice the difference would be to look
  at Abis traces and log output.
• there would be a naming clash: TCH/F_PDCH is already assigned to
  PDCH ACT style TCH/F_PDCH, we would need another name for CHAN
  ACT style TCH/F_PDCH.

These factors combined make it rather unattractive to implement
a CHAN ACT style TCH/F_PDCH.