User's Manual

nano3G AP Installation Manual Installation Overview and Requirements
N3G_INST_300 v292_1.0 for N3G_2.92 © ip.access Limited 2012 Page 10
2.2.5 Parameters for Residential Deployments
Minimum Configuration - Residential Deployments
The minimum set of configuration data for the AP is:
Oscillator Synchronisation
Timeout
(oscillatorSynchronisationTime
out)
The number of days an AP can go without resynchronisation
before it raises the relevant alarm.
Closed Access vs Open
Access
See section 2.2.6.
IuUP Initialisation
(iuUpInitNoDataSupported)
If this attribute is set to TRUE (default value), the AP includes
NO_DATA RFCs as appropriate in IuUP Initialisation frames.If this
attribute is set to FALSE, the HNB omits any NO_DATA RFCs that
would otherwise have been included.
Network Listen Scan Interval
(applyFrequencyCorrection)
Set the interval for frequency corrections.
Default is 28 days.
For enterprise deployments use the OCXO option, this can be
increased to any value.
Realm Id (realmId) Allows a nano3G AP to include a configurable realm in the HNBAP
Register Request message. This is only used by Iuh APs.
Parameter Notes
Parameter Notes
HNB C-Id (hnbCId) This is the unique ID of this AP on the serving nano3G AC. The
term HNB is used in 3GPP in reference to small cells. The HNB
C-Id is used in the Register Request message to uniquely identify
the AP within the AC. The value is also combined with the RNC-ID
to give the 28 bit UC-Id (also known as TR-196 CellID) that is used
on-air in SIB3.
Use the same value in the dummy cell.
RNC ID (mcIdentity) RNC ID of the AC - this is selected by choosing the BSMIS object
for the AP’s site.
AC address (acAddressinUse) IP Address or FQDN of the serving AC.
MCC (mcc) Mobile Country Code.
MNC (mnc) Mobile Network Code.