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 12
Identities in PM File Headers
While the filename can be configured to provide a unique name related to the AP, the PM
File header also includes identity information:
• DN Prefix – user-configurable text. By appropriate configuration this can be
combined with the Local DN to generate a full DN
• Local DN - this attribute is set based on the class type and the object instance ID of
the AP object. This is typically “AP#0”.
• User label – set to the AP’s Object Name (the same parameter used for unique-id
in the filename)
• Job ID – the same parameter as the Job ID in the file name, subject to the same
NOS policy parameters.
Example PM File header:
<?xml version="1.0" encoding="UTF-8"?>
<mc:measCollecFile
xmlns:mc="http://www.3gpp.org/ftp/specs/archive/32_series/32.435#me
asCollec" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.3gpp.org/ftp/specs/archive/32_series
/32.435#measCollec pm_report.xsd">
<mc:fileHeader fileFormatVersion="32.435 V7.0"
vendorName="ip.access"
dnPrefix="ROOT#1;APS#0;LTE_APs#6;LTE_AP_INFO#793">
<mc:fileSender localDn="LTE_AP_#0" elementType="LTE AP"/>
<mc:measCollec beginTime="2000-03-01T14:00:00+02:00"/>
</mc:fileHeader>
<mc:measData>
Example Policies for PM Related Identities
Policies depend how the receiving PM system wishes to identify the AP. For example:
• the filename may suffice and there are no specific requirements for the header
• the Job ID in the filename and header (including equipment ID) uniquely identifies
the AP
• the operator has a rigorous policy for Object name that can be used by the PM
system
• The DN Prefix is configured so that when concatenated with the Local DN, it
produces the full DN (Distinguished Name) of the AP object as used in the NOS
(see example in PM Header above).