BTS: accept also relative frame numbers with rach requst
The rach request contains a relative frame number (Fn % 42432),
while BTS::rcv_rach() accepts the full frame number only.
Since the BTS is always aware of the full frame number this is
not a problem. But for BSC co-located PCU schemes it is a problem
since the rach request only contains the relative frame number
as mentioned above.
The pcu continusly receives frame number updates with the GSM time
indication message. It is simple to re-calculate the full frame
number from that information.
This patch makes BTS::rcv_rach() compatible with relative frame
numbers, while not breaking the compatibility for full frame
numbers
Change-Id: Iaa182d8d29c6a0f5fa06064c2eb48b21b1ba2775
diff --git a/tests/tbf/TbfTest.cpp b/tests/tbf/TbfTest.cpp
index aec6ef8..e367ce6 100644
--- a/tests/tbf/TbfTest.cpp
+++ b/tests/tbf/TbfTest.cpp
@@ -42,6 +42,8 @@
#include <errno.h>
+#define DUMMY_FN 2654167
+
void *tall_pcu_ctx;
int16_t spoof_mnc = 0, spoof_mcc = 0;
@@ -166,6 +168,7 @@
trx = &bts->trx[0];
trx->pdch[ts_no].enable();
+ the_bts->set_current_frame_number(DUMMY_FN);
}
static gprs_rlcmac_dl_tbf *create_dl_tbf(BTS *the_bts, uint8_t ms_class,
@@ -1692,7 +1695,7 @@
{
BTS the_bts;
int ts_no = 7;
- uint32_t fn = 2654167; /* 17,25,9 */
+ uint32_t fn = DUMMY_FN; /* 17,25,9 */
uint32_t tlli = 0xf1223344;
const char *imsi = "0011223344";
uint16_t qta = 31;