The documentation and any software described herein and/or provided to you in conjunction with this
documentation contain proprietary and confidential information of ip.access and may only be used
subject to a license agreement containing restrictions on use and disclosure. They are also protected
by copyright, patent rights and other intellectual and industrial property laws. The information
contained in this document and any software described herein is subject to change without notice. If
you find any problems in the documentation and/or the software please report them to us in writing.
The document and/or the software are not warranted to be error-free. No right, title, license or interest
in any physically or electronically distributed materials is transferred to you by such distribution. No
part of this document and/or the software may be reproduced, displayed, copied, translated, adapted,
downloaded, electronically transmitted, used or reproduced in any form including (without limitation)
distribution or storage in a system for retrieval without our express written permission (which may be
subject to conditions).
The documentation and/or software may provide links to Web sites and access to content, products,
and services from third parties. ip.access is not responsible for the availability of, or any content
provided on, third-party Web sites. You bear all risks associated with the use of such content. If you
choose to purchase any products or services from a third party, the relationship is directly between
you and the third party. ip.access is not responsible for: (a) the quality of third-party products or
services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of
products or services and warranty obligations related to purchased products or services. ip.access is
not responsible for any loss or damage of any sort that you may incur from dealing with any third
party.
ip.access is the owner of the "ip.access" trademark and all associated trade names, logos and
devices unless indicated to the contrary. Any other trademarks, logos and names appearing on in this
document may be the property of their respective owners.
ip.access Limited is a Private Limited Company Registered in England and Wales
Company No. 03400157
Registered Office:
Building 2020
Cambourne Business Park
Cambourne
CB23 6DW
UK
Tel: +44 (0) 1954 713 700
Fax: +44 (0) 1954 713 799
Further company information may be found at www.ipaccess.com.
Revision History
Version Change SummaryDateAuthor
292_0.1 Draft for N3G_2.92 and S16 information22 Aug 2012CFB
292_0.2 Updated with S16 information14 Sep 2012CFB
The ip.access nano3G AP is an indoor Access Point for enterprise applications.
This manual provides all the necessary information required to install an ip.access nano3G
AP. The manual provides step-by-step instructions for hardware installation and
configuration steps required to bring a nano3G AP into service.
The AP can be configured with a static IP address or it can obtain an IP address
dynamically via DHCP. The AP-NOS Server and AP-AC connections can be configured to
be secure (via IPSec and a security gateway) or unsecured.
1.1Overview
This manual is organised as follows:
•This introduction
•An overview of AP installation, including installation requirements for all AP
variants and specific requirements for each AP model
•AP pre-provisioning in the NOS Server using the NOS Client
•AP configuration file preparation - this is supplementary information for
pre-provisioning
•Commissioning an AP for connection to its serving NOS Server
•AP hardware installation
•Optional activities to finalize installation
•Installation troubleshooting
•Regulatory warnings and safety information
1.2User Requirements
It is assumed that any readers that will use the NOS Client already know how to:
•Start the NOS Client
•Navigate the Explorer Pane to find an AP object
It is also assumed that the any readers that will use the NOS Client will have suitable user
privileges for the NOS Client.
Refer to [OPM_415] for information on using the NOS Client.
[OPM_440]NOS Server Operations Manual (N3G_OPM_440)
[REF_105]nano3G System Glossary (N3G_REF_105)
[REF_110]nano3G System Configuration Management (CM) MIB Reference Manual
(N3G_REF_110)
[REF_300]nano3G AP License and Copyright Reference (N3G_REF_300)
[TRB_300]nano3G AP Troubleshooting Manual (N3G_TRB_300)
[21.905]Vocabulary for 3GPP Specifications (3GPP 3G TR 21.905)
1.4Licenses and Copyright Notices
Portions of the AP are constructed from third-party software and open source code and
ip.access ltd gratefully acknowledges the contributions that these libraries, technologies
and components have made to the product. Each of these is supplied under the terms of a
license agreement and these are either reproduced or referenced in [REF_300], in line with
the stipulations of their authors.
1.5Terminology
Common nano3G System terminology is defined in [REF_105].
There are three tasks that must be completed to install a nano3G AP and make it ready to
provide service:
•Pre-Provisioning
•Commissioning
•Site installation
These tasks can be completed in any order. In most cases, however, the most practical
approach is to provision and commission an AP before final site installation.
2.1.1Pre-Provisioning
Pre-provisioning means to provide configuration details for a nano3G AP prior to site
installation. As an AP’s configuration is stored on its serving NOS Server, an AP can be
pre-provisioned at any time. This offers maximum flexibility for pre-provisioning an AP as far
or as little ahead of site installation as is needed. Pre-provision a nano3G AP with the
information it needs to allow it to provide service, such as a serving AC address, neighbour
lists, operating frequency and network identity details.
It is recommended to perform at least some pre-provisioning for an AP before on site
installation. As a minimum, use the Create Site Wizard in the NOS Client to create a site
and AP object on the serving NOS Server that will contain the AP’s configuration. If an AP
attempts to connect to its serving NOS Server, but the NOS Server has not yet been
provisioned with site details for the AP, the NOS Server will raise alarms about attempts to
connect by an unknown AP.
For more information about AP pre-provisioning, see 3 Pre-Provisioning a nano3G AP.
2.1.2Commissioning
Use the nano3G AP’s built-in configuration web page to configure the AP with the settings it
needs to establish a connection with its serving NOS Server.
This is done using a commissioning terminal, either before sending the AP out for
installation or on site using a suitably prepared laptop.
Pre-Commissioning
This is recommended for residential deployment. The benefits of commissioning an AP
before on site installation are:
•The site installation engineer does not need a commissioning laptop.
•This also means that the site installation engineer does not need to know the user
name and password for the AP commissioning web page.
•If the AP has been properly pre-provisioned, the AP is effectively plug-and-play.
•This also means that a nano3G S8 AP or nano3G S16 AP could be installed by an
end customer, without help from a site installation engineer. The customer simply
needs to provide suitable network and power connections.
Note:For residential deployments, commissioning should have already been done at the factory
or by the supplier. If in doubt, contact the supplier for confirmation.
On-Site Commissioning
The benefits of using a laptop for commissioning an AP on site are:
•If there is a commissioning error, this can be corrected immediately without
needing to return the AP
•If an AP has been in storage for some time, the required software build and/or
ATAS package can be installed on the AP on site, without needing to return the AP
to base
2.1.3On Site Installation
Physical installation of a nano3G AP at its operating site, including providing the AP with
power and a suitable network connection that provides a backhaul path to the NOS Server
and AC.
If a nano3G AP has been enabled for service prior to the site visit, the installation engineer
can make test calls immediately.
Note:For some deployment scenarios, APs may be setup by end users. Generally, this may be
the case for plug and play residential deployments, where the end user has some easy to
follow setup instructions.
Note:Due to the physical installation requirements of a nano3G E8 AP or E16 AP, which must be
securely wall mounted in a location with adequate ventilation, it is recommended that an E8
AP or E16 AP is installed by a suitably qualified site installation engineer.
•A commissioning terminal, which can be either a desktop computer or a laptop,
with:
•OS: Windows XP or later
•Web browser: Microsoft Internet Explorer 7 or later
•JavaScript enabled in the web browser
•A short Ethernet cable for connecting the commissioning terminal to the AP
•A temporary means to provide power to the AP while it is connected to the
commissioning terminal
Site Installation Requirements
All nano3G AP models have the following general requirements for installation:
•A permanent means to provide power to the AP once it is connected to the
backhaul
•An Ethernet connection to the backhaul via CAT5 Ethernet cabling
•Access to a DNS service on the backhaul to resolve symbolic addresses
•Access to NTP services on the backhaul to set the correct time and date each time
the AP starts up
•Access to a DHCP service on the backhaul to allow dynamic IP address
configuration
•If IPsec will be used to secure the interface across the backhaul, access to the
relevant Security Gateway that terminates the IPsec tunnel
•If a firewall is in place on the network an AP will use for backhaul, this must be
configured to allow traffic to and from the AP - see the port usage section below
Special attention must be given to ensure a nano3G AP will meet its air cooling
requirements in its installed location.
Take the following points into consideration for the physical location of an AP:
•All AP models must be installed so that they are upright, to ensure proper air will
flow through the body of the AP to provide cooling.
•All AP models must not be installed in enclosed spaces where air flow is
restricted. This includes, but is not necessarily limited to:
•Roof or ceiling spaces
•Small cabinets
•Tightly enclosed shelf spaces
•When free-standing the nano3G S8 AP, the stand supplied for this purpose must
be used, and the AP must be upright, as noted above.
2.2.3Information Required for Pre-Provisioning
This information will be used to configure an AP from the NOS Client. The parameters
depend on the deployment scenarios:
•Parameters for Enterprise Deployments
•Parameters for Residential Deployments
Note:It is recommended to pre-provision an AP before taking it on site, so that the AP can
download its configuration when it starts up on site.
OMC-R Client Login Details
User name and password for the NOS Client. To be able to configure an AP from the NOS
Client, the user name must have Full Access to the NOS Server serving the AP and Full
Access granted to its APs. See [OPM_415] for full details about user permissions.
The minimum set of configuration data for the AP is:
ParameterNotes
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.
LAC (lac)Location Area Code.
RAC (lac)Routing Area Code.
SAI SAC (sac)This is the SAI SAC (Service Access Code) which can be used by
the billing system. If this is not used by the billing system, it is
recommended to set this to 1.
SAI LAC (saiLac)SAI Location Area Code which can be used by the billing system.
This is a different value than the LAC set in the
lacRacCandidateList for an individual AP. If this is not used by the
billing system, it is recommended to set this to 1.
UARFCN within
(rfParamsCandidateList)
Scrambling code
within (rfParamsCandidateList)
RSSI scan bands
(rssiScanBands_002)
Lat, Long and LCS uncertainty
(lcsLatitude), (lcsLongitude),
(lcsUncertainty)
The frequency on which the AP will operate. This should be
determined by network planning.
The scrambling code assigned to the AP. This should be
determined by network planning.
Specify which bands to scan with Network Listen, when
performing RSSI detect and BCCH decode tests. Leave this empty
to scan all bands supported by the AP hardware.
Latitude and longitude of the APs installation site, for RANAP
location reporting
The following table shows some other attributes to consider for initial AP configuration.
Apart from the static neighbour lists, which are usually configured individually, any of these
can be in a general template for all APs or can be set individually.
Neighbour List Population
(neighbourListPopulation)
Static neighbour lists, GSM and
UMTS
(staticGsmNeighbourList),
(staticUMTSNeighbourList_001
)
Determines whether values for cell parameters such as UARFCN,
LAC, RAC, and CPICH TX Power are selected by Network Listen
(NWL) or are configured via the management system.
The default is configuration by the management system. In this
case, cell parameters should be determined through planning,
preferably informed by on site measurements. This is particularly
appropriate for the enterprise APs, nano3G E8 APs and nano3G
E16 APs and for nano3G S8 APs used in enterprise or SOHO
environments.
This determines how the live neighbour list is populated. For
enterprise and SOHO deployments, the recommended setting is
STATIC_ONLY, which only uses neighbours entered in the static
neighbour lists, as determined by network planning.
These are complex attribute that specify GSM (2G) and UMTS
(3G) neighbour candidates. It is recommended to enter these
directly in the NOS Client. However, if a similar list has already
been configured for a nearby AP, it may be advantageous to copy
this attribute from a configuration file saved from the nearby AP,
load this into the target AP and then make suitable adjustments
from the NOS Client.
See [OPM_300] for static neighbour list configuration
Note: In the static neighbour list, the list must be ordered by best
first to ensure optimal reselection and handover.
Neighbour PLMNs
(neighbourPlmns)
PLMNs To Sync With
(plmnsToSyncWith)
PM Reporting URL
(reportingUrl)
Diagnostic Reporting URL
(diagnosticReportingUrl)
reportingUrl (reportingUrl)Set the URL of the NOS Server measurement reporting service.
localTimeZone
(localTimeZone)
psHandoverEnabled
(psHandoverEnabled)
If specified, this restricts the networks that neighbouring cells can
belong to for populating the neighbour lists by specifying the
MCC/MNC values.
If specified, this restricts the networks that nearby cells can belong
to for frequency synchronisation by specifying the MCC/MNC
values.
For reporting performance measurements to the PMS on the NOS.
Set the URL of the NOS Server diagnostics service. Replace
oam.server with the IP address or FQDN of the server.
Replace oam.server with the IP address or FQDN of the server.
Set the timezone, in POSIX format, where the APs are located.
This assumes that all APs on the same AC are in the same
timezone, which is the most probable scenario. If APs are spread
across several timezones, this can be an AP-specific setting.
Whether or not PS RABs will handover between an AP and the
macro network. This is disabled (false) by default.
Realm Id (realmId)Allows a nano3G AP to include a configurable realm in the HNBAP
The number of days an AP can go without resynchronisation
before it raises the relevant alarm.
See section 2.2.6.
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.
Set the interval for frequency corrections.
Default is 28 days.
For enterprise deployments use the OCXO option, this can be
increased to any value.
Register Request message. This is only used by Iuh APs.
2.2.5Parameters for Residential Deployments
Minimum Configuration - Residential Deployments
The minimum set of configuration data for the AP is:
ParameterNotes
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.
Determines whether values for cell parameters such as UARFCN,
LAC, RAC, and CPICH TX Power are selected by Network Listen
(NWL) or are configured via the management system.
The default is configuration by the management system. In this
case, cell parameters should be determined through planning,
preferably informed by on site measurements. This is particularly
appropriate for the enterprise APs, nano3G E8 APs and nano3G
E16 APs and for nano3G S8 APs used in enterprise environments.
Configuration by NWL can be selected for APs that are deployed
for plug-and-play installation by end users - typically only nano3G
S8 APs. In this case, the AP configuration must include extended
LAC/RAC and RF Parameter Candidate Lists. This is so that the
AP can choose the best settings from the candidate lists according
to its RF environment.
LAC (lac)Location Area Code. For configuration by Network Listen (NWL),
an AP needs a list of candidate LACs that can be chosen NWL.
NWL will look for the least conflicting option.
RAC (rac)Routing Area Code. For configuration by Network Listen (NWL),
an AP needs a list of candidate RACs that can be chosen by NWL.
NWL will look for the least conflicting option.
SAI SAC (sac)This is the SAI SAC (Service Access Code) which can be used by
the billing system. If this is not used by the billing system, it is
recommended to set this to 1.
SAI LAC (saiLac)SAI Location Area Code which can be used by the billing system.
This is a different value than the LAC set in the
lacRacCandidateList for an individual AP. If this is not used by the
billing system, it is recommended to set this to 1.
UARFCN within
(rfParamsCandidateList)
The frequency on which the AP will operate. For configuration by
Network Listen (NWL), an AP needs a list of candidate UARFCNs
that can be chosen by NWL.NWL will look for the least conflicting
option.
Scrambling code
within (rfParamsCandidateList)
The scrambling code assigned to the AP. For configuration by
Network Listen (NWL), an AP needs a list of candidate Scrambling
Codes that can be chosen by NWL.NWL will look for the least
conflicting option.
RSSI scan bands
(rssiScanBands_002)
Specify which bands to scan with Network Listen, when
performing RSSI detect and BCCH decode tests. Leave this empty
to scan all bands supported by the AP hardware.
Lat, Long and LCS uncertainty
(lcsLatitude), (lcsLongitude),
Latitude and longitude of the APs installation site, for RANAP
location reporting
The following table shows some other attributes to consider for initial AP configuration.
Apart from the static neighbour lists, which are usually configured individually, any of these
can be in a general template for all APs or can be set individually.
ParameterNotes
Neighbour List Population
(neighbourListPopulation)
Static neighbour lists, GSM and
UMTS
(staticGsmNeighbourList),
(staticUMTSNeighbourList_001
)
Neighbour PLMNs
(neighbourPlmns)
PLMNs To Sync With
(plmnsToSyncWith)
PM Reporting URL
(reportingUrl)
Diagnostic Reporting URL
(diagnosticReportingUrl)
This determines how the live neighbour list is populated. For
residential deployments, the recommended setting is
MERGE_STSTIC_AND_DETECTED, so that neighbours can be
determined by Network Listen as well as network planning.
This is generally not needed for residential deployments. Where
APs use Network Listen (NWL) to detect neighbours. However
there may be some cases where it is necessary to configure some
static neighbours.
See [OPM_300] for static neighbour list configuration
Note: In the static neighbour list, the list must be ordered by "best
first" to ensure optimal reselection and handover.
If specified, this restricts the networks that neighbouring cells can
belong to for populating the neighbour lists by specifying the
MCC/MNC values.
If specified, this restricts the networks that nearby cells can belong
to for frequency synchronisation by specifying the MCC/MNC
values.
For reporting performance measurements to the PMS on the NOS.
Set the URL of the NOS Server diagnostics service. Replace
oam.server with the IP address or FQDN of the server.
reportingUrl (reportingUrl)Set the URL of the NOS Server measurement reporting service.
Replace oam.server with the IP address or FQDN of the server.
Set the timezone, in POSIX format, where the APs are located.
This assumes that all APs on the same AC are in the same
timezone, which is the most probable scenario. If APs are spread
across several timezones, this can be an AP-specific setting.
This is disabled (false) by default. This is the normal setting for
residential deployments.
The number of days an AP can go without resynchronisation
before it raises the relevant alarm.
See section 2.2.6.
Entries in the Access Control List are only needed if an AP is
configured for Closed Access. The Access Control List is a white
list of IMSIs that are allowed to use the AP.
Each entry in the Access Control List also has an option to allow
hand-in from the macro network. A UE that is on the white list for
multiple APs can only be Allowed to do this on one AP.
Realm Id (realmId)Allows a nano3G AP to include a configurable realm in the HNBAP
2.2.6Access Control
The configurations for four common scenarios are described here:
•Full open access (Enterprise or Residential)
•Open access for Zonal AP (Enterprise only)
•Closed access with CSG parameter broadcast and Access Control via the AC,
which uses the AAA service (Enterprise or Residential)
•Closed access using Legacy Mode, with Access Control via the AC, which uses
the AAA service (Enterprise or Residential)
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.
Set the interval for frequency corrections.
Default is 28 days.
1 day for VCTCXO. This is used for most residential deployments.
Any time for OCXO.
Register Request message. This is only used by Iuh APs.
Note:In all cases, a UE that needs to make an emergency call can access an AP for that
purpose.
Full Open Access
In this scenario, any UE on the operator's network can use the AP.
In this scenario, any UE on the operator's network can use the AP. However, the AP will
notify the AC when UEs camp onto the AP, so that UEs registered for location services can
be identified and, if appropriate, trigger some action.
Zonal functionality requires the following attribute settings:
AttributeSettingNotes
Zonal AP
(reservedBoolean2)
CSG Access Mode
(csgAccessMode)
Non CSG UE Access Decision
(nonCsgUeAccessDecision)
Access Decision Mode
(accessDecisionMode)
TrueWhen set to True, this attribute causes the
Iuh 3GAP to request the IMSI from the UEs
when operating in Open Access Mode. This
IMSI is then included in the HNBAP UE
Registration and De-Registration Messages
between the AP and AC.
HybridMust be set to Hybrid as part of the
mechanism that ensures the IMSI check
takes place with the AC.
QueryCauses the AP to perform an IMSI challenge
to provide the AC with the IMSI.
The AC checks the IMSI with the AAA service
in the NOS, which always succeeds for
access. The AAA service uses this
information to inform any registered Zonal
presence application.
CSG LiteThe AP transmits the CSGIndicator, CSGID,
and HNBIdentifier (when available). This
prevents foreign CSG-capable UEs from
attempting to access the HNB.
This setting does not invoke CSG based
access control.
Closed Subscriber Group
Identifier
(csgId)
HNB Name
(hnbName)
0 to 134217727This is the Closed Subscriber Group Identity.
This is broadcast in SIB3 when Access
Decision Mode is set to CSG Lite. The UE
may have a whitelist of CSGIDs, and may
also permit manual selection of CSGIDs via
the corresponding HNB Names.
TextThis is an optional name of up to 48
characters.
It is only broadcast (in SIB20) if it has a value
and when Access Decision Mode is set to
CSG Lite.
Together with the CSG ID, this can be used
to identify a CSG cell to a UE user.
Information about zone configuration and implementation and setting up subscribed
services for GSMA OneAPI is outside the scope of this manual. Refer to manuals covering
the nano3G System NOS for further information.
This is the recommended approach for Closed Access.
A Closed Subscriber Group (CSG) identifies a cell to a UE in order for the UE to determine
whether or not it should attempt to use that cell according to a whitelist of CSG identifiers
stored by the UE. This is a 3GPP Release 9 capability, and may or may not be used by Rel
9 UEs.
In this scenario, the AP transmits CSG information and as a result, CSG-aware Release 9
UEs that do not have the AP in their CSG whitelists will ignore the AP. However, this is not
a full implementation of CSG-based access control.
Note:This assumes that the operator has mechanisms in place to update CSG-aware UEs that
need to use the APs.
All other UEs will attempt to access the AP, but only UEs that are in the whitelist will be
allowed access to the AP.
Use the following attribute settings:
AttributeSettingNotes
CSG Access Mode
(csgAccessMode)
Access Decision Mode
(accessDecisionMode)
Non CSG UE Access Decision
(nonCsgUeAccessDecision)
Closed Subscriber Group
Identifier
(csgId)
HNB Name
(hnbName)
HybridThe AP also accepts UEs that do not
implement CSG.
CSG LiteThe AP transmits the CSGIndicator, CSGID,
and HNBIdentifier (when available). This
prevents foreign CSG-capable UEs from
attempting to access the HNB.
This setting does not invoke CSG based
access control.
QueryCauses the AP to perform an IMSI challenge
to provide the AC with the IMSI (or IMEI for
emergency calls).
The AC checks the IMSI with the AAA service
in the NOS, which checks the IMSI whitelist
configured for the AP to determine whether or
not the AP is granted access.
0 to 134217727This is the Closed Subscriber Group Identity.
This is broadcast in SIB3 when Access
Decision Mode is set to CSG Lite. The UE
may have a whitelist of CSGIDs, and may
also permit manual selection of CSGIDs via
the corresponding HNB Names.
TextThis is an optional name of up to 48
characters.
It is only broadcast (in SIB20) if it has a value
and when Access Decision Mode is set to
CSG Lite.
Together with the CSG ID, this can be used
to identify a CSG cell to a UE user.
This is provisioned against an AP but used by
the AAA service in the NOS.
2.2.8Closed Access in Legacy Mode
In this scenario, the AP does not transmit any CSG parameters. Access control is
performed for all UEs.
Use the following attribute settings:
AttributeSettingNotes
Access Decision Mode
(accessDecisionMode)
Non CSG UE Access Decision
(nonCsgUeAccessDecision)
Access Control List
(accessControlList)
Legacy ModeInstructs the AP to function in a mode that
does not transmit any CSG parameters.
QueryCauses the AP to perform an IMSI challenge
to provide the AC with the IMSI (or IMEI for
emergency calls).
The AC checks the IMSI with the AAA service
in the NOS, which checks the IMSI whitelist
configured for the AP to determine whether or
not the AP is granted access.
List of IMSIs and
corresponding
phone numbers
This is provisioned against an AP but used by
the AAA service in the NOS.
The options described here can be used independently or in any combination.
Use an Existing AP
The Create Site Wizard, which is used for the initial pre-provisioning of an AP, allows
selection of an existing AP as the basis for configuring the new AP. This is a one-time
option that is only available in the Create Site Wizard.
Configuration Files
An initial configuration file can be used to rapidly configure the AP via the NOS Create Site
Wizard. This is can be an alternative or in addition to using settings from an existing AP or
using a template. Additional configuration files can be loaded against the AP object after it
has been created by the Create Site Wizard. If they will be used, the location of any
configuration files must be known.
Configuration files are described in section 4.
AP Templates
As with configuration files, an initial AP template can be used to rapidly configure the AP via
the NOS Create Site Wizard. This can be an alternative to or in addition to using settings
from an existing AP or using a configuration file. Additional templates can be applied
against the AP object after it has been created by the Create Site Wizard.
For information on working with templates, see [OPM_415].
All nano3G AP models require the configuration details listed in this section. Use this
information to commission an AP from the commissioning terminal, so that the AP can
subsequently connect to its serving NOS Server.
It is possible to commission an AP before taking it on site.
Note:For residential deployments, commissioning should have already been done at the factory
or by the supplier. If in doubt, contact the supplier for confirmation.
For connecting to the AP from the commissioning terminal:
•User name and password for the AP web server - if necessary, contact customer
support at ip.access for the current user name and password
For commissioning the AP:
•IP Address or FQDN of the serving NOS Server
•IP Address or FQDN of an NTP server
•DHCP or static IP
•If static IP is required:
•IP address for the AP
•Netmask
•IP Address or FQDN of the default gateway
•IP Address or FQDN of the Primary DNS
•IPSec is optional, but if IPSec is required:
•IP Address or FQDN of the IPsec Security Gateway
•IP Address or FQDN of a CRL server
•Optionally, Traffic Selector information (IP address and subnet mask)
A traffic selector defines a range of IP addresses that are sent through the
IPSec tunnel. This allows an extra degree of control over the traffic that is
passed down the IPSec tunnel. Normally, the security gateway controls this
range and no other configuration is needed.
The items in this section can only be used if the commissioning terminal is running a web
server that provides a path to any ip.access AP software download packages. That is, the
required .sdp files must be present on the commissioning terminal.
Setting up a web server for this purpose on the commissioning terminal is outside the scope
of this manual.
Software Image
If there is a requirement to update the AP’s software during commissioning, the relevant
.sdp file must be present on the commissioning terminal.
ATAS File
If there is a requirement to update the trust anchors in the AP during commissioning, the
relevant .sdp file containing the ATAS package must be present on the commissioning
terminal, ready to be downloaded to the AP. The ATAS package contains augmenting trust
anchors which allow an AP to trust specific security gateways.
This will be necessary where the security gateway certificates are not supplied by ip.access
Limited, to ensure the ATAS package is correct for the security gateway terminating IPsec.
The .sdp file containing the ATAS package must be created for the specific security
gateways used in each implementation of the nano3G System. This must be done in
consultancy with ip.access Limited prior to system deployment.
A suitable mains power supply point into which the power adapter for the AP can be
plugged.
Only use the power adapter available from ip.access to power the AP:
ip.access part numberPSA15R-090PV-R
Input100-240V ~ 50/60Hz 0.5A
Output+9VDC 1.67A
Power over Ethernet
POE requires the use of a power inserter and a splitter. The power inserter is positioned
close to the backhaul network connection and mains supply, while the splitter is positioned
close to the AP.
Only use the POE splitter available from ip.access:
ip.access part number222A
Input48VDC 0.35A
Output9VDC 1.33A
2.3.2nano3G S8 AP Physical Requirements
A nano3G S8 AP may be installed in one of the following ways (see section 6.2.4):
•Free-standing on a flat stable surface.
•Attached to a wall or partition using two screws that engage in keyhole slots in the
rear surface of the AP.
•Attached to a POE splitter using the two screws that engage in keyhole slots in the
rear surface of the AP. The POE splitter in turn attaches to a wall or partition using
two screws.
The unit must be vertical to ensure that air can circulate freely around it.
It is recommended to install the AP with its front surface facing the area requiring cellular
coverage, unobstructed by walls or partitions that may cause significant RF attenuation.
Dimensions and
weight
EnvironmentalCoolingVents on the back at top and bottom