User's Manual

nanoLTE AP Pre-Provisioning and Configuration Capturing Network Policies and AP Modes
NANO_INST_43370 v101_0.4 for N4G_1.1 © ip.access Limited 2016 Page 20
3.7 "Per AP" Parameters
All these parameters should be considered on a per AP basis. After analysis, some
parameters might be applicable to AP use cases, in which case include them in appropriate
use case Group Templates.
Parameter Description Comment
Device.Services.FAPService.{i}.
AccessMgmt.LTE.HNBName
eNodeB Name; as displayed by
UEs camped on the cell or when
performing a manual search for
cells on a UE. The default is
"ip.access".
It is recommended to ensure
this is set, typically on a per AP
basis. However, this depends on
network policy. For example,
there may be a policy where
APs with the same use case
should have the same
HNBName.
Device.Services.FAPService.{i}.
CellConfig.LTE.RAN.RF.PhyCel
lID
Physical Cell ID. This must not clash with
neighbouring LTE cells.
Device.Services.FAPService.{i}.
CellConfig.LTE.EPC.EAID
Emergency area ID. Tells the
AP which emergency area it
belongs to for PWS messages.
Depends on geographical
location (refer to the nanoLTE
AP Release Note to see if this is
supported in N4G_1.1).
Device.FAP.GPS.X_000295_LC
SLatitude,
Device.FAP.GPS.X_000295_LC
SLongitude
AP Location - GPS coordinates. Unique per AP. This must be
configured for enterprise APs to
ensure the Neighbour Cell
Wizard can identify appropriate
neighbour cell candidates by
location.
Device.Services.FAPService.{i}.
CellConfig.LTE.RAN.RF.Refere
nceSignalPower
The downlink Reference Signal
Power in dBm; defaults to -18.
The range is -60 to 50. The
linear average (in W) of all
resource elements that carry
cell-specific reference signals
within the operating bandwidth.
Only change this if the default
value is not correct for the AP’s
deployment scenario.
It may be desirable to have
some options for different
planned use-cases.
Device.Services.FAPService.{i}.
CellConfig.LTE.RAN.RF.X_000
295_ExternalPAGain
External PA Gain. Required for
the LRE feature only. The AP
must be connected to an
external PA to boosts its Tx
power for extended cell radius.
Do not change this if an AP will
not use LRE. If the same LRE
configuration is used by multiple
APs, consider a separate LRE
use case template.
Device.Services.FAPService.{i}.
CellConfig.LTE.RAN.PHY.PRA
CH.RootSequenceIndex
The root Sequence Index that
derives the 64 preamble
sequences to be used for
RACH.
Should be different from
neighbour cells to prevent
RACH collisions.
Device.Services.FAPService.{i}.
CellConfig.LTE.RAN.RF.EARF
CNUL
Uplink EARFCN.
This can be a comma separated
list of candidate UL frequencies.
However, as the nanoLTE AP
does not yet support self
configuration, only the first entry
will be used.
Typically selected per AP, from
a pool set aside for small cell
usage.