Project

General

Profile

Actions

Feature #4794

closed

Downlink Repeated SACCH support

Added by laforge over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
-
Target version:
-
Start date:
10/09/2020
Due date:
% Done:

100%

Spec Reference:
3GPP TS 44.006 Section 11.2

Description

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.


Related issues

Related to OsmoBTS - Feature #4795: Uplink Repeated SACCH SupportResolveddexter10/09/2020

Actions
Related to OsmoBTS - Feature #4796: Downlink Repeated FACCH SupportResolveddexter10/09/2020

Actions
Related to OsmoBTS - Bug #3056: OsmoBTS doesn't implement SACCH Repetition Order (SRO)Rejected03/11/2018

Actions
Actions #1

Updated by laforge over 3 years ago

Actions #2

Updated by laforge over 3 years ago

  • Related to Feature #4796: Downlink Repeated FACCH Support added
Actions #3

Updated by laforge over 3 years ago

Actions #4

Updated by laforge over 3 years ago

See also: Chapter 7.2 of "GSM/EDGE Evolution and Performance".

Actions #5

Updated by dexter over 3 years ago

  • 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).

Actions #6

Updated by dexter over 3 years ago

  • 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

Actions #7

Updated by dexter over 3 years ago

  • % Done changed from 60 to 70

See also:
https://gerrit.osmocom.org/c/osmo-bts/+/21105 l1sap: add repeated downlink SACCH

Actions #8

Updated by dexter over 3 years ago

  • % Done changed from 70 to 80

The patch is still in review. I think we have most problems addressed now. See also: https://gerrit.osmocom.org/c/osmo-bts/+/21105

Actions #9

Updated by dexter over 3 years ago

  • % Done changed from 80 to 90

The patches are up for review, no open review issues at the moment.

Actions #10

Updated by dexter over 3 years ago

I have fixed the currently pending review issues, so no open review issues at the moment.

Actions #11

Updated by dexter over 3 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100

All related patches are merged, so we can resolve this now.

Actions #12

Updated by fixeria 4 months ago

  • Related to Bug #3056: OsmoBTS doesn't implement SACCH Repetition Order (SRO) added
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)