Project

General

Profile

Actions

Feature #5475

closed

Support configuring counter Ny1

Added by pespin about 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
arehbein
Category:
-
Target version:
-
Start date:
03/02/2022
Due date:
% Done:

100%

Spec Reference:
Tags:

Description

src/osmo-bsc/bts_ipaccess_nanobts_omlattr.c nanobts_attr_bts_get():

    /* 10 milliseconds */
    msgb_tv_put(msgb, NM_ATT_BTS_AIR_TIMER, osmo_tdef_get(bts->network->T_defs, 3105, OSMO_TDEF_MS, -1)/10);

    /* 10 retransmissions of physical config */
    msgb_tv_put(msgb, NM_ATT_NY1, 10);             //<---- THIS IS RIGHT NOW HARDCODED

Right now, we allow configuring "T3105", but "Ny1" counter is hardcoded to 10. This is bad, because Ny1 needs to be adapted also based on T3105.
T3105 sets how often we reschedule a "Physical Information" message, eg sent BTS->MS during an incoming handover access.
Ny1 sets how many "Physicial information" messages are sent, aka how many times T3105 is rearmed before stopping.
If T3105 is set to low values (meaning it will retransmit quite quickly), the Ny maybe adapter to higher values to keep retrying for the same amount of time.

See some further explanations here: https://pcstelconext.wordpress.com/2011/05/02/2g-timer-explanations/ , grep for "T3105" and "Ny1" (4.10.3 IV. Precautions)

See also 3GPP TS 04.08 section 11.1.2 "Timers on the network side". Specially important when looking for a good T3105 default value candiate:

NOTE 3: This timer may be set to such a low value that the message is in fact continuously transmitted.


Files

run run 234 Bytes arehbein, 12/17/2022 01:31 PM
expout expout 1.07 KB arehbein, 12/17/2022 01:31 PM
testsuite.log testsuite.log 4.38 KB arehbein, 12/17/2022 01:31 PM
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)