для Cisco Cisco Packet Data Gateway (PDG)
HNB Gateway in Wireless Network
Features and Functionality - Base Software ▀
HNB-GW Administration Guide, StarOS Release 17 ▄
43
1. RMS provisions common PLMN - C as the PLMN of the HNB. It also provisions PLMN A and PLMN B in
HNB.
2. HNB sends Common PLMN in HNB Registration Request.
3. HNBGW sends Access Request towards AAA.
4. Optional Allowed PLMN List is sent in Access Accept. This is not implemented in 17.0.
5. HNBGW sends HNB Register Accept to HNB. HNB broadcasts Common PLMN and the PLMN list.
6. UE1 was registered in Macro RNC with PLMN X and LAC X. UE1 has moved to HNB coverage area. UE1
3. HNBGW sends Access Request towards AAA.
4. Optional Allowed PLMN List is sent in Access Accept. This is not implemented in 17.0.
5. HNBGW sends HNB Register Accept to HNB. HNB broadcasts Common PLMN and the PLMN list.
6. UE1 was registered in Macro RNC with PLMN X and LAC X. UE1 has moved to HNB coverage area. UE1
does Location Update Request with Old LAI as PLMN X + LAC X.
7. HNB to know the IMSI can send Identity request to UE1.
8. UE1 will respond with Identity Response.
9. HNB sends UE Registration request with UE Identity as IMSI to HNBGW. HNBGW is considering that it
8. UE1 will respond with Identity Response.
9. HNB sends UE Registration request with UE Identity as IMSI to HNBGW. HNBGW is considering that it
always receives UE Registration Request with IMSI. MOCN will work even if IMSI is not received; only that
re-routing load will increase.
re-routing load will increase.
10. HNBGW performs access control on the UE Registration request and sends UE Registration Accept if
successful.
11. HNB prepares Initial UE Message with LAI as Common PLMN C + CN LAC "Y". The message is forwarded to
HNBGW.
12. HNBGW applies selection algorithm for this Initial UE Message. As "Selected PLMN Identity" is not received
HNBGW considers UE1 as non-supported UE. Assuming no NRI is received; UE retrieves MCC, MNC from
the IMSI and selects the operator. HNBGW forwards the Location Update to the selected MSC. It sets the
redirect attempt flag.
the IMSI and selects the operator. HNBGW forwards the Location Update to the selected MSC. It sets the
redirect attempt flag.
13. MSC is not able to handle this UE rejects it with reroute command.
14. HNBGW now forwards this request to CN2 with redirect attempt flag enabled offcourse.
15. MSC forwards the reroute complete to HNBGW. As the UE is non-supporting it assigns Common PLMN + CN-
14. HNBGW now forwards this request to CN2 with redirect attempt flag enabled offcourse.
15. MSC forwards the reroute complete to HNBGW. As the UE is non-supporting it assigns Common PLMN + CN-
LAC i.e. PLMN C + LAC "Y".
16. HNBGW forwards the Location Update Accept to HNB.
17. If CN and OTA LAC are different HNB changes the LAC in Location Update Accept. i.e. PLMN C + LAC "Z".
17. If CN and OTA LAC are different HNB changes the LAC in Location Update Accept. i.e. PLMN C + LAC "Z".
System Management Features
This section describes following features:
Management System Overview
The system's management capabilities are designed around the Telecommunications Management Network (TMN)
model for management - focusing on providing superior quality network element (NE) and element management system
(Web Element Manager) functions. The system provides element management applications that can easily be integrated,
using standards-based protocols (CORBA and SNMPv1, v2), into higher-level management systems - giving wireless
operators the ability to integrate the system into their overall network, service, and business management systems. In
addition, all management is performed out-of-band for security and to maintain system performance.
model for management - focusing on providing superior quality network element (NE) and element management system
(Web Element Manager) functions. The system provides element management applications that can easily be integrated,
using standards-based protocols (CORBA and SNMPv1, v2), into higher-level management systems - giving wireless
operators the ability to integrate the system into their overall network, service, and business management systems. In
addition, all management is performed out-of-band for security and to maintain system performance.
Operation and Maintenance module of chassis offers comprehensive management capabilities to the operators and
enables them to operate the system more efficiently. There are multiple ways to manage the system either locally or
remotely using its out-of-band management interfaces. These include:
enables them to operate the system more efficiently. There are multiple ways to manage the system either locally or
remotely using its out-of-band management interfaces. These include:
Using the command line interface (CLI)