Cisco Cisco Packet Data Gateway (PDG)
resulting integer value. These 20 bits carry a value which is unique for each aggregator. This combined with
the remaining 8 bits gives a unique value for each individual HNB behind the aggregator.
the remaining 8 bits gives a unique value for each individual HNB behind the aggregator.
On receiving a Relocation Request message, HNBGW will first do a lookup using the entire 28 bit Cell ID
(if there are normal HNBs too in addition to the aggregator HNBs). If this lookup fails and if the Cell ID has
the 16th bit set to 1, then HNBGW will lookup using the first 20 bits in the Cell ID to find the target HNB
aggregator. If this lookup is successful, it gives the HNB aggregator to which the relocation request will be
forwarded. This is then further forwarded to the individual HNB by the aggregator using the remaining 8 bits.
(if there are normal HNBs too in addition to the aggregator HNBs). If this lookup fails and if the Cell ID has
the 16th bit set to 1, then HNBGW will lookup using the first 20 bits in the Cell ID to find the target HNB
aggregator. If this lookup is successful, it gives the HNB aggregator to which the relocation request will be
forwarded. This is then further forwarded to the individual HNB by the aggregator using the remaining 8 bits.
By default, this feature is disabled. Any change in the status of this feature while calls are already up will lead
to the SCTP connections of all the HNBs in the HNBGW service to get torn down.
to the SCTP connections of all the HNBs in the HNBGW service to get torn down.
How It Works
Architecture
This section describes SRNS Relocation handin procedure in detail.
HNB-GW Administration Guide, StarOS Release 19
118
Handin with FAP Aggregator
How It Works