Hi Max,
shall we generate SI2qter for a cell with no neighborcells at all? Where is the point in scheduling it?
holger
No, SI2qter is completely optional. The presence of it is indicated in SI3 - see commit f3f3505f493f63e9e79c72e407907783913b9c9c in openbsc. The scheduler is in src/common/sysinfo.c - see f3ee66207de2859cf4751b44241c0f84cf0999b4 in osmobts.
On 05/17/2016 09:06 PM, Holger Freyther wrote:
Hi Max,
shall we generate SI2qter for a cell with no neighborcells at all? Where is the point in scheduling it?
holger
On 18 May 2016, at 11:03, Max msuraev@sysmocom.de wrote:
No, SI2qter is completely optional. The presence of it is indicated in SI3 - see commit f3f3505f493f63e9e79c72e407907783913b9c9c in openbsc. The scheduler is in src/common/sysinfo.c - see f3ee66207de2859cf4751b44241c0f84cf0999b4 in osmobts.
yes, but why do we schedule SI2qter for a GSM1900 cell that has absolutely no neighbors?
Seems like a bug. Does it only happens for 1900?
On 05/18/2016 11:04 AM, Holger Freyther wrote:
On 18 May 2016, at 11:03, Max msuraev@sysmocom.de wrote:
No, SI2qter is completely optional. The presence of it is indicated in SI3 - see commit f3f3505f493f63e9e79c72e407907783913b9c9c in openbsc. The scheduler is in src/common/sysinfo.c - see f3ee66207de2859cf4751b44241c0f84cf0999b4 in osmobts.
yes, but why do we schedule SI2qter for a GSM1900 cell that has absolutely no neighbors?