Downlink Repeated SACCH support
In 3GPP Rel-7 (?) of GERAN, the concept of "repeated SACCH" was introduced.
The rationale for SACCH improvement can be found in 3GPP TDoc GP-042668 Section 1/2 (even though if later sections have not been implemented as suggested there): Particularly with AMR as a voice codec, the voice quality performance is better than that of control channels (and estimated 5dB).
So in the end, even though the voice channel would still be acceptable, calls fail due to signaling failure, both on SACCH and FACCH.
Repeated SACCH support basically replaces downlink System Information on SACCH (or even pending SAPI3 frames) with re-transmissions of SAPI0 frames. Due to some related logic (and sigaling in the TS 44.004 header), the MS can then even combine the bursts from multiple transmissiosn to decode the SACCH block.
- Assignee set to dexter
3GPP TS 44.004 specifies an SRR bit in the SACCH uplink block format. This bit is used to request a repeated SACCH downlink SACCH from the BTS. When the MS is unable to decode the downlink SACCH blocks from the BTS, it should set the SRR bit. My idea for a first experiment was to trigger this by sending malformed SACCH blocks to the MS, so far this did not work, even though the MS has the Repeated ACCH Capability bit in CM3 set.
Note: Some of the work here overlaps with repeated FACCH support (Repeated ACCH Capability bit / signalling).
- Status changed from New to In Progress
- % Done changed from 0 to 60
The SACCH repetition can now be requested from the MS. When I understand the spec correctly then only SAPI0 frames may be repeated, all others are not repeated.
See also: https://gerrit.osmocom.org/c/osmo-bts/+/21105 l1sap: add repeated downlink SACCH