Cisco Cisco Packet Data Interworking Function (PDIF)
HNB Gateway in Wireless Network
▀ How HNB-GW Works
▄ HNB-GW Administration Guide, StarOS Release 17
60
The HNB-GW is reloaded or service restarted and SCCP Subsystem Number (SSN) allowed from CN
(SGSN/MSC) node is received.
The received SSN Prohibited or Point-code Address Inaccessible indication comes for a CN node, HNB-GW
start a configurable timer.
If SSN allowed indication comes before timer expires, the timer is stopped.
On timer expiry HNB-GW deletes all SCCP connections towards the CN node.
If SSN Allowed indication comes after timer expiry, HNB-GW sends RANAP-RESET command
message to the CN node.
The RANAP-RESET from HNB-GW is sent only if HNB-GW-initiated RANAP-RESET is configured in HNB-GW
service.
service.
CBS Call Procedures
This section describes the HNB/HNB-GW requirements for Cell Broadcasting Service (CBS) in addition to the
network-initiated call procedures for CBS.
network-initiated call procedures for CBS.
HNB Requirements for CBS
Following are the requirements from HNB side for CBS to take place:
HNB includes “Service Area for Broadcast” information element (IE) in HNB REGISTRATION REQUEST
message.
“Service Area” in the SABP messages needs to be same as that of HNB Register request.
HNB Processes SABP messages received from HNB-GW and responds back with success/failure to HNB-GW.
HNB is responsible for storage and scheduling of CBS messages.
HNB is responsible for initiating PAGING towards UE when HNB receives WRITE-REPLACE message with
Paging-ETWS-Indicator.
HNB responds with ERROR Indication procedure if it receives SABP messages from HNB-GW which can not
be detected due to syntactic error. HNB also includes message identifier in the error indication messages for
which error has been detected.
which error has been detected.
After successful registration with HNB-GW, HNB is responsible for initiating RESTART procedure towards
HNB-GW. HNB is also responsible to send RESTART message to HNB-GW when broadcast related restart
situation occurs at HNB.
situation occurs at HNB.
Before initiating Deregistration request towards HNB-GW, HNB sends FAILURE indication towards HNB-GW
to indicate broadcast related unavailability in this service area. HNB is also responsible for sending FAILURE
towards HNB-GW when broadcast related failure is detected at HNB.
towards HNB-GW when broadcast related failure is detected at HNB.
HNB-GW requirement for CBS
Following are the requirements from HNB-GW side for CBS to take place:
HNB-GW supports one HNB per Broadcast Service Area.
TCP Handling
HNB-GW supports TCP connection towards one Cell Broadcasting Center (CBC).