5 Apr
2016
5 Apr
'16
3:06 p.m.
On Mon, Apr 04, 2016 at 10:16:00AM +0200, Neels Hofmeyr wrote:
On Sun, Apr 03, 2016 at 10:27:51PM +0200, Harald Welte
wrote:
However, in our asn.1 the Extended RNC-ID seems to be available only for
Enhanced Relocation Complete messages.
9.1.33 lists it as optional IE for an InitialUE message, but it seems I
can't parse it with anything except
ranap_decode_enhancedrelocationcompleterequesties(), which is not related
to InitialUE messages. It thus seems that extended RNC IDs aren't widely
used? I also found the words "Note: Application of the Extended RNC-ID IE
to very large networks is FFS." in 9.2.1.39a. FFS meaning... For Future
Something?
I'm not supporting extended RNC-Ids at this point.
~Neels
Hi Neels,
one more comment:
On Sun, Apr 03, 2016 at 10:05:07PM +0200, Harald Welte wrote:
Hold on, in the RANAP specs I see the Extended RNC-ID IE:
"The Extended RNC-ID IE shall be used if the RNC identity has a value
larger than 4095."
It extends the range to ..65535 (9.2.1.39a in 3GPP TS 25.413 version
12.4.0 Release 12). I therefore think the HNB-GW should try to look
only like a single RNC
to the MSC, and very clearly only a single RANAP Reset should be sent.
One further reason: The RNC-ID only has a range from 0..4095, i.e. if