Dear
all
Regarding ARID (NetId in my
contribution), I have more important point than what we discussed in the last
telecon.
(What we discussed was one BS can
have more than one NetIDs (ARIDs))
I have suggested the mechanism
that the serving BS provides the NetID to the target BS and the target BS
makes a decision of necessity of IP re-establishment.
Therefore, we don’t need to
advertise the NetID (ARID) periodically with NBR-ADV for IP re-establishment
purpose.
I think that currently it is
enough to give one bit to MSS to notify the necessity of IP re-establishment
in 802.16e standard.
However if NetID(ARID) has to be
delivered to MSSs for future use (HO between different systems, e.g. 802.16
and 3GPP) then I have suggestion.
That is BS can tell the MSS only
when the NetID(ARID) is changed (When provided NetID (ARID) from the serving
BS is different from the NetID(ARID) in the target BS) in RNG-RSP or REG-RSP
where appropriate.
a.
When MSSs’ NetID(ARID) is changed, BS provides
specific NetID(ARID) # to MSS then MSS regards the existence of NetID as the
necessity of IP re-establishment. à IP re-establishment is
required
b.
When MSSs’ NetID(ARID) is same, BS either provides
NetID (ARID) 00000000 or does not provide NetID(ARID) value (TLV).
à IP re-establishment is not
required.
c.
When NetID (ARID) comparison is not possible, BS
set NetID (ARID) 11111111 à IP re-establishment is
required.
(This idea is not included in my
contribution.)
For little more information on
this please refer to IEEE C802.16e-04_90r2 Minimizing IP
Connectivity Establishment Procedure.pdf in
handoff directory of http://upload.wirelessman.org/
.
I would like to hear your
opinion.
Best
Regards,
Ronny (Yong-Ho)
Kim