Project

General

Profile

Bug #1950

LC15: BTS does not send L2 fill frame

Added by mqng2 over 1 year ago. Updated 2 months ago.

Status:
In Progress
Priority:
High
Assignee:
Category:
osmo-bts-litecell15
Target version:
-
Start date:
02/13/2017
Due date:
% Done:

0%

Estimated time:
Spec Reference:

Description

We have noticed that the LC15 BTS does not send L2 fill frame in case there is nothing to transmit.
This leads to bad RXQUAL repored by MS during signaling in TCH channel. Please refer to GSM 05.08, section 8.3

"On any TCH this subset of TDMA frames is always used for transmission during DTX. For speech, when
no signalling or speech is to be transmitted these TDMA frames are occupied by the SID (Silence
Descriptor) speech frame, see TS GSM 06.12 and TSM GSM 06.31 for detailed specification of the SID
frame and its transmission requirements. In other cases when no information is required to be transmitted,
e.g. on data channels, the L2 fill frame (see GSM 04.06 section 5.4.2.3) shall be transmitted as a FACCH
in the TDMA frame subset always to be transmitted.

On the SDCCH and on the half rate speech traffic channel in signalling only mode DTX is not allowed. In
these cases and during signalling on the TCH when DTX is not used, the same L2 fill frame shall be
transmitted in case there is nothing else to transmit."

History

#1 Updated by laforge 7 months ago

Hi Minh, what is the status of this bug report from almost one year ago? Can you please update us? Thanks!

#2 Updated by mqng2 7 months ago

laforge wrote:

Hi Minh, what is the status of this bug report from almost one year ago? Can you please update us? Thanks!

Hi Harald,

This bug was fixed in our public repository in the following commit

https://gitlab.com/nrw_noa/osmo-bts/commit/b32834b0e89ee987ff00e38041bd5683eea3cefd

I forgot to submit it to gerrit at that time. Do you want to submit it to gerrit?

#3 Updated by laforge 6 months ago

Hi Minh,

On Mon, Jan 08, 2018 at 02:38:21PM +0000, mqng2 [REDMINE] wrote:

This bug was fixed in our public repository in the following commit

https://gitlab.com/nrw_noa/osmo-bts/commit/b32834b0e89ee987ff00e38041bd5683eea3cefd

I forgot to submit it to gerrit at that time. Do you want to submit it to gerrit?

It would be great if we could all work together, including Nutaq / Nuran making sure
that bug fixes are submitted to upstream osmocom. It is a collaborative software
development project, which only works if people actually collaborate :)

Thanks a lot, it is appreciated.

#4 Updated by mqng2 6 months ago

Hi Harald,

The patch has been submitted to gerrit https://gerrit.osmocom.org/#/c/5753

#5 Updated by laforge 6 months ago

On Thu, Jan 11, 2018 at 02:51:44PM +0000, mqng2 [REDMINE] wrote:

The patch has been submitted to gerrit https://gerrit.osmocom.org/#/c/5753

Thanks!

#6 Updated by laforge 6 months ago

  • Assignee set to stsp

#7 Updated by stsp 5 months ago

  • Status changed from New to In Progress

Setting status to in-progress since this is being worked on.

It looks like this issue is currently waiting for an updated patch from Minh-Quang Nguyen at https://gerrit.osmocom.org/#/c/5753

#8 Updated by stsp 4 months ago

Vadim Yanitskiy has updated Minh-Quang Nguyen's patch. The patch is now waiting for another round of review and testing.

#9 Updated by fixeria 4 months ago

Vadim Yanitskiy has updated Minh-Quang Nguyen's patch.

Just had some spare time, and decided to move this work forward.
I am not familiar with this part of specifications, so only
cosmetic / code style changes were made.

#10 Updated by laforge 2 months ago

stsp wrote:

It looks like this issue is currently waiting for an updated patch from Minh-Quang Nguyen at https://gerrit.osmocom.org/#/c/5753

the point of assigning the ticket to you was that no such update appears to be coming, and that you should take things into your hands, sorry for not being explicit about it.

Also, it feels wrong that this is done in the bts-model specific part. The knowledge whether or not any real information or a L2 fill frame is to be sent in a given timeslot/frame number is something that's the same for all BTSs.

It's probably best to first establish some kind of decision tree (on paper, ...) looking at all the different cases and how we should behave in those cases, followed by some tests using the trxcon-fake_trx-osmo-bts-trx chain.

#11 Updated by stsp 2 months ago

In that case it's probably best if we sit down together and discuss this face to face.
I need to properly understand the goals you have in mind, and I need to learn which parts of the spec to study and learn whatever else I need to know to start working on this in earnest.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)