Project

General

Profile

Actions

Bug #1833

closed

UPLINK MCS gets reduced from MCS9->MCS6 when good radio condition exists

Added by arvind.sirsikar over 7 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
High
Target version:
-
Start date:
10/25/2016
Due date:
% Done:

0%

Spec Reference:

Description

During EGPRS UL testing with osmo-trx setup, it is seen that MCS gets reduced very fast even when radio condition is good. Same issue is present for GPRS testing as well.

This condition exists only with osmo-trx setup.


Related issues

Related to OsmoPCU - Bug #3395: Uplink CS/MCS control is broken osmo-pcu is used with osmo-bts-trx/osmo-trxResolvedpespin07/14/2018

Actions
Related to OsmoTRX - Bug #4373: OsmoTRX calculates relatively lower C/I values for EDGE/8-PSK bursts (compared to GMSK)Resolvedfixeria01/22/2020

Actions
Actions #1

Updated by arvind.sirsikar over 7 years ago

We have modified osmo-pcu.cfg as below

cs link-quality-ranges cs1 6 cs2 5 8 cs3 7 13 cs4 12

TO

cs link-quality-ranges cs1 0 cs2 0 8 cs3 0 13 cs4 0

and validated in integration setup. further investigation needs to be done on how measurement parameter is conveyed between TRX and PCU apart from the usual DATA-IND message

Actions #2

Updated by arvind.sirsikar over 7 years ago

  • Status changed from New to Stalled
Actions #3

Updated by laforge over 6 years ago

Actions #4

Updated by laforge over 6 years ago

  • Status changed from Stalled to New
  • Assignee set to 4368
Actions #5

Updated by laforge over 5 years ago

Actions #6

Updated by laforge over 5 years ago

  • Assignee changed from 4368 to msuraev
Actions #7

Updated by laforge almost 5 years ago

  • Assignee changed from msuraev to lynxis
Actions #8

Updated by pespin over 4 years ago

IIUC this issue was expected until recently when we started providing and fixing (osmo-pcu.git e13cdc503e2faf06699aedd4e84c69ad42916755) measurement values from osmo-trx through osmo-bts-trx into osmo-pcu. fixeria what do you think?

Actions #9

Updated by fixeria over 4 years ago

  • Status changed from New to Feedback

IIUC this issue was expected until recently when we started providing and fixing
measurement values from osmo-trx through osmo-bts-trx into osmo-pcu.
fixeria what do you think?

ACK. This should not happen anymore, but we need a TTCN-3 test case to be sure.
arvind.sirsikar, could you please test with the current master and update the issue? Thanks!

Actions #10

Updated by fixeria over 4 years ago

  • Related to Bug #3395: Uplink CS/MCS control is broken osmo-pcu is used with osmo-bts-trx/osmo-trx added
Actions #11

Updated by fixeria over 4 years ago

BTW, Fairwaves noticed that OsmoTRX computes significantly lower C/I values for EDGE bursts (e.g. 1 dB for 8-PSK vs 8 dB for GMSK). There was a patch somewhere, I'll send it to Gerrit as soon as I find it.

Actions #12

Updated by laforge about 4 years ago

  • Assignee deleted (lynxis)
Actions #13

Updated by pespin about 4 years ago

  • Related to Bug #4373: OsmoTRX calculates relatively lower C/I values for EDGE/8-PSK bursts (compared to GMSK) added
Actions #14

Updated by pespin about 4 years ago

  • Assignee set to arvind.sirsikar

We have some TTCN3 tests passing already for that, as explained in #3395.
Improvements regarding C/I in osmo-trx are still WIP in #4373.

arvind.sirsikar please can you test again with current master osmo-trx + osmo-bts-trx + osmo-pcu and see if you still see any issues?

Actions #15

Updated by fixeria almost 2 years ago

  • Status changed from Feedback to Resolved

All related tickets are closed, the problem of low C/I for 8-PSK bursts has been fixed.
No feedback during the past 2 years, marking as resolved.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)