Project

General

Profile

Actions

Bug #1883

closed

RACH load computation is wrong

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

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
12/19/2016
Due date:
% Done:

100%

Spec Reference:

Description

l1sap_info_time_ind() is suposed to be called [at least] once every TDMA frame.

To be sure, we count the number of frames expired based on info_time_ind->fn - btsb->gsm_time.fn

[btw: there could/should be an assert or a big fat LOGL_ERROR message if we ever have more than one FN difference]

We then take the number of RACH slots per multiframe (27 or 51, depending on combined/non-combined CCCH) and multiply that with frames_expired. This is clearly wrong.

We should instead check if the currently processed/expired frame number was a rach slot (e.g. by some array index), and if yes increment btsb->load.rach.total by one.


Related issues

Related to OsmoBTS - Feature #1884: distribute measurement processing accross timeslotsCloseddexter12/19/2016

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)