SureSignal 2.2 OAM

Use pursuant to applicable agreements
Title page
Alcatel-Lucent 936x
Small Cell | BCR 2.2
Operation, Administration, Maintenance and Provisioning
Alcatel-Lucent Proprietary
401-387-065
ISSUE 4
JULY 2010

Legal notice
Legal notice
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective
owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright 2010 Alcatel-Lucent. All rights reserved.
Contains proprietary/trade secret information which is the property of Alcatel-Lucent and must not be made available to, or copied or used by anyone outside
Alcatel-Lucent without its written authorization.
Not to be used or disclosed except in accordance with applicable agreements.
Contents
About this document

Purpose
......................................................................................................................................................................................... xvii
xvii
Reason for revision
.................................................................................................................................................................. xvii
xvii
New in this release
................................................................................................................................................................... xvii
xvii
xviii
Intended audience .................................................................................................................................................................... xviii
xviii
Supported systems ................................................................................................................................................................... xviii
How to use this document
Prerequisites
.................................................................................................................................................... xviii
xviii
.............................................................................................................................................................................. xviii
xviii
Conventions used
.................................................................................................................................................................... xviii
xviii
xix
Related information ................................................................................................................................................................... xix
xix
Document support ...................................................................................................................................................................... xix
xx
Technical support ......................................................................................................................................................................... xx
xx
How to order .................................................................................................................................................................................. xx
xx
How to comment .......................................................................................................................................................................... xx
Part I: Hazard statements

1
Safety statements
Safety statements description
............................................................................................................................................... 1-1
1-1
Part II: System description

2
Small Cell solution

2-1
Overview ...................................................................................................................................................................................... 2-1
2-2
Small Cell application and architecture ............................................................................................................................ 2-2
....................................................................................................................................................................................................................................
BCR 2.2
iii
401-387-065 Issue 4
July 2010
Contents
....................................................................................................................................................................................................................................
Small Cell description

3-1
Overview ...................................................................................................................................................................................... 3-1
Small Cell features
................................................................................................................................................................... 3-2
3-2
Home cell access point
........................................................................................................................................................... 3-6
3-6
Enterprise cell access point

4
................................................................................................................................................... 3-8
3-8
Small Cell cluster network elements

Overview ...................................................................................................................................................................................... 4-1
4-1
4-2
BSR Signaling Gateway ......................................................................................................................................................... 4-2
Brick
.............................................................................................................................................................................................. 4-3
4-3
4-5
NTP server ................................................................................................................................................................................... 4-5
5
Small Cell core network elements

Overview ...................................................................................................................................................................................... 5-1
5-1
AAA server
................................................................................................................................................................................. 5-2
5-2
5-3
DNS/DHCP server .................................................................................................................................................................... 5-3
5-4
IPC .................................................................................................................................................................................................. 5-4
5-5
Service Router ............................................................................................................................................................................ 5-5
6
Small Cell Management Solution

Overview ...................................................................................................................................................................................... 6-1
6-1
6-2
Architecture of the WMS for Small Cell .......................................................................................................................... 6-2
Components of the WMS for Small Cell
Interfaces of the WMS for Small Cell
......................................................................................................................... 6-4
6-4
............................................................................................................................ 6-11
6-11
Part III: Performing OAM&P on the Small Cells

7
Provisioning
7-1
Overview ...................................................................................................................................................................................... 7-1
WMS pre-provisioning
........................................................................................................................................................... 7-2
7-2
7-15
Small Cell auto-configuration ............................................................................................................................................ 7-15
7-18
HDM pre-provisioning ......................................................................................................................................................... 7-18
7-22
HDM-WMS synchronization ............................................................................................................................................. 7-22
....................................................................................................................................................................................................................................
BCR 2.2
iv
401-387-065 Issue 4
July 2010
Contents
....................................................................................................................................................................................................................................
Operation
8-1
Overview ...................................................................................................................................................................................... 8-1
Small Cell selection
................................................................................................................................................................. 8-2
8-2
8-4
Small Cell addition ................................................................................................................................................................... 8-4
8-7
Small Cell parameters check out ......................................................................................................................................... 8-7
8-10
Small Cell parameters modification ................................................................................................................................ 8-10
8-12
Small Cell profile modification ......................................................................................................................................... 8-12
8-14
Legal requisition activation/deactivation ....................................................................................................................... 8-14
8-15
Display and update the Access Control List ................................................................................................................. 8-15
Disabling and Enabling a Small Cell
.............................................................................................................................. 8-19
8-19
8-21
Small Cell deletion ................................................................................................................................................................. 8-21
8-23
Small Cell activation ............................................................................................................................................................. 8-23
8-24
Change of the Small Cell postal address ........................................................................................................................ 8-24
Management of Small Cell group
.................................................................................................................................... 8-25
8-25
Operational states synchronization
................................................................................................................................. 8-33
8-33
8-34
Small Cell specific parameters .......................................................................................................................................... 8-34
Small Cell software upgrade
.............................................................................................................................................. 8-35
8-35
8-36
Enhanced transport CAC activation ................................................................................................................................ 8-36
Small Cell access
................................................................................................................................................................... 8-37
8-37
Part IV: Fault management

9
Principles of alarm management

9-1
Overview ...................................................................................................................................................................................... 9-1
9-2
Fault Management .................................................................................................................................................................... 9-2
9-5
Small Cells real time management ..................................................................................................................................... 9-5
9-6
Alarm display ............................................................................................................................................................................. 9-6
Description of the Small Cell alarm sheet
10
....................................................................................................................... 9-7
9-7
Small Cell alarms

Overview
................................................................................................................................................................................... 10-1
10-1
....................................................................................................................................................................................................................................
BCR 2.2
v
401-387-065 Issue 4
July 2010
Contents
....................................................................................................................................................................................................................................
Class BSR Alarms

Overview
................................................................................................................................................................................... 10-5
10-5
securityViolation alarm
resetFailed alarm
....................................................................................................................................................... 10-6
10-6
................................................................................................................................................................... 10-7
10-7
resetInitiated alarm
............................................................................................................................................................... 10-8
10-8
.......................................................................................................................................................... 10-9
10-9
resetCompleted alarm
applicationInsane alarm
.................................................................................................................................................... 10-10
10-10
autoconfigfailure alarm
..................................................................................................................................................... 10-11
10-11
lmcFailure alarm
................................................................................................................................................................. 10-12
10-12
ipsecConfigurationAlarm alarm
.................................................................................................................................... 10-13
10-13
creationOfSecondSAFailed alarm
ipsecTunnelAlarm alarm
................................................................................................................................ 10-14
10-14
.................................................................................................................................................. 10-15
10-15
invalidDatabaseDetected alarm
..................................................................................................................................... 10-16
10-16
basebandReconfigfailed alarm
....................................................................................................................................... 10-17
10-17
allReservedFemtoCellsInUse alarm
selfoptNotRun alarm
............................................................................................................................ 10-18
10-18
......................................................................................................................................................... 10-19
10-19
bCHGuardTimeExpired alarm
....................................................................................................................................... 10-20
10-20
cellSearchGuardTimeExpired alarm
thresholdCriteriaNotMet alarm
............................................................................................................................ 10-21
10-21
...................................................................................................................................... 10-22
10-22
detectedCollapsingLAI alarm
........................................................................................................................................ 10-23
10-23
gsmBandNotSupported alarm
........................................................................................................................................ 10-24
10-24
gsmBCCHDecodeGuardTimerExpired alarm
gsmCellSearchGuardTimerExpired alarm
gsmThresholdCriteriaNotMet alarm
noMacroCellFound alarm
.......................................................................................................... 10-25
10-25
................................................................................................................. 10-26
10-26
............................................................................................................................ 10-27
10-27
................................................................................................................................................ 10-28
10-28
queueOverload alarm
........................................................................................................................................................ 10-29
10-29
systemOverload alarm
...................................................................................................................................................... 10-30
10-30
Class LCell Alarms

10-31
Overview ................................................................................................................................................................................. 10-31
....................................................................................................................................................................................................................................
BCR 2.2
vi
401-387-065 Issue 4
July 2010
Contents
....................................................................................................................................................................................................................................
codeAllocationFailure alarm
.......................................................................................................................................... 10-32
10-32
uLCongestion alarm
.......................................................................................................................................................... 10-33
10-33
dLCongestion alarm
.......................................................................................................................................................... 10-34
10-34
rSSImeasInitFail alarm
..................................................................................................................................................... 10-35
10-35
tSSImeasInitFail alarm
..................................................................................................................................................... 10-36
10-36
rACHmeasInitFail alarm
.................................................................................................................................................. 10-37
10-37
............................................................................................................................................. 10-38
10-38
hsbitratemeasInitFail alarm
rSSImeasStop alarm
.......................................................................................................................................................... 10-39
10-39
tSSImeasStop alarm
........................................................................................................................................................... 10-40
10-40
rACHmeasStop alarm
....................................................................................................................................................... 10-41
10-41
hsbitratemeasStop alarm
.................................................................................................................................................. 10-42
10-42
commonMeasInitTimeout alarm
................................................................................................................................... 10-43
10-43
invalidSIBSchedule alarm
............................................................................................................................................... 10-44
10-44
sIBUpdateCCCError alarm
............................................................................................................................................. 10-45
10-45
invalidSIBParameter alarm
............................................................................................................................................. 10-46
10-46
channelConfigBCHFailed alarm
................................................................................................................................... 10-47
10-47
channelConfigPCHFailed alarm
................................................................................................................................... 10-48
10-48
channelConfigFACHFailed alarm
................................................................................................................................ 10-49
10-49
channelConfigPRACHFailed alarm
............................................................................................................................ 10-50
10-50
sharedChannelConfigHSPAFailed alarm
rbSevereFailure alarm
................................................................................................................... 10-51
10-51
....................................................................................................................................................... 10-52
10-52
rbNonSevereFailure alarm
.............................................................................................................................................. 10-53
10-53
cpBlockRequestTimeout alarm
tpapReleaseIndPCH alarm
..................................................................................................................................... 10-54
10-54
.............................................................................................................................................. 10-55
10-55
tpapReleaseIndFACH alarm
........................................................................................................................................... 10-56
10-56
tpapReleaseIndRACH alarm
.......................................................................................................................................... 10-57
10-57
Class SDM Alarms

10-58
Overview ................................................................................................................................................................................. 10-58
suDownloadFailure alarm
............................................................................................................................................... 10-59
10-59
....................................................................................................................................................................................................................................
BCR 2.2
vii
401-387-065 Issue 4
July 2010
Contents
....................................................................................................................................................................................................................................
suActivationFailure alarm
............................................................................................................................................... 10-60
10-60
dbDownloadFailure alarm
............................................................................................................................................... 10-61
10-61
toneFileDownloadFailure alarm
toneFileCorrupt alarm
.................................................................................................................................... 10-62
10-62
....................................................................................................................................................... 10-63
10-63
Class RFTrace Alarms

10-64
Overview ................................................................................................................................................................................. 10-64
...................................................................................................................................... 10-65
10-65
rfTraceDedicatedFailure alarm
rfTraceHsdpaFailure alarm
............................................................................................................................................. 10-66
10-66
Class PM Alarms
10-67
Overview ................................................................................................................................................................................. 10-67
pmAuthenticationError alarm
........................................................................................................................................ 10-68
10-68
pmCommunicationError alarm
...................................................................................................................................... 10-69
10-69
Class ItfBGWY Alarms

10-70
Overview ................................................................................................................................................................................. 10-70
noResponseFromBGWY alarm
..................................................................................................................................... 10-71
10-71
Class ItfBVG Alarms

10-72
Overview ................................................................................................................................................................................. 10-72
itfBVGLinkFailure alarm
................................................................................................................................................ 10-73
10-73
Class IuPSPrime Alarms

10-74
Overview ................................................................................................................................................................................. 10-74
gTPEchoFailure alarm
...................................................................................................................................................... 10-75
10-75
Class ItfBPG Alarms

10-76
Overview ................................................................................................................................................................................. 10-76
itfBPGLinkFailure alarm
................................................................................................................................................. 10-77
10-77
Class SCTPASSOC Alarms

10-78
Overview ................................................................................................................................................................................. 10-78
sctpAssocAssociationDownAlarm alarm
.................................................................................................................. 10-79
10-79
....................................................................................................................................................................................................................................
BCR 2.2
viii
401-387-065 Issue 4
July 2010
Contents
....................................................................................................................................................................................................................................
Class Radio Alarms

10-80
Overview ................................................................................................................................................................................. 10-80
overTemperature alarm
..................................................................................................................................................... 10-81
10-81
txMalfunction alarm
.......................................................................................................................................................... 10-82
10-82
rxMalfunction alarm
.......................................................................................................................................................... 10-83
10-83
underTemperature alarm
.................................................................................................................................................. 10-84
10-84
clockSynchronisationFailure alarm
ntpServiceUnavailable alarm
.............................................................................................................................. 10-85
10-85
......................................................................................................................................... 10-86
10-86
Class CECTL Alarms

10-87
Overview ................................................................................................................................................................................. 10-87
picoArrayCommunicationFailure alarm
.................................................................................................................... 10-88
10-88
........................................................................................................................................... 10-89
10-89
layerOneResetFailure alarm
Class GSMListener Alarms
10-90
Overview ................................................................................................................................................................................. 10-90
gsmModuleFailtoInit alarm
............................................................................................................................................ 10-91
10-91
gsmModuleATCmdTimeoutError alarm
gsmNoCellsFound alarm
gsmATCmdFail alarm
.................................................................................................................... 10-92
10-92
................................................................................................................................................. 10-93
10-93
....................................................................................................................................................... 10-94
10-94
Part V: Configuration management

11
Configuration management
Overview
................................................................................................................................................................................... 11-1
11-1
11-2
Power control ........................................................................................................................................................................... 11-2
11-6
Radio resource management ............................................................................................................................................... 11-6
11-7
Mobility management ........................................................................................................................................................... 11-7
11-8
Operator managed Small Cells .......................................................................................................................................... 11-8
Part VI: Accounting management

12
Accounting management
12-1
Accounting management ..................................................................................................................................................... 12-1
....................................................................................................................................................................................................................................
BCR 2.2
ix
401-387-065 Issue 4
July 2010
Contents
....................................................................................................................................................................................................................................
Part VII: Performance management

13
Performance Measurement management

Overview
................................................................................................................................................................................... 13-1
13-1
13-2
Small Cell Performance Measurement principles ...................................................................................................... 13-2
13-5
PM enable action .................................................................................................................................................................... 13-5
13-6
PM disable action ................................................................................................................................................................... 13-6
13-7
PM and file upload procedures .......................................................................................................................................... 13-7
13-10
Display PM measurements ............................................................................................................................................... 13-10
14
Radio Frequency trace concepts

Overview
................................................................................................................................................................................... 14-1
14-1
14-2
Radio frequency trace tool .................................................................................................................................................. 14-2
Radio measurements
15
............................................................................................................................................................. 14-3
14-3
Radio Frequency trace components

Overview
................................................................................................................................................................................... 15-1
15-1
RF data files
............................................................................................................................................................................. 15-2
15-2
RF trace software components

RF trace interface
16
.......................................................................................................................................... 15-3
15-3
................................................................................................................................................................... 15-5
15-5
Radio Frequency trace operations

Overview
................................................................................................................................................................................... 16-1
16-1
RF trace setup
.......................................................................................................................................................................... 16-2
16-2
16-3
RF parameters .......................................................................................................................................................................... 16-3
16-4
Collection of RF data ............................................................................................................................................................ 16-4
RF trace alarms
....................................................................................................................................................................... 16-5
16-5
Part VIII: Security management

17
Principles of security
Overview
................................................................................................................................................................................... 17-1
17-1
17-2
Security principles .................................................................................................................................................................. 17-2
17-4
Security architecture framework ....................................................................................................................................... 17-4
....................................................................................................................................................................................................................................
BCR 2.2
x
401-387-065 Issue 4
July 2010
Contents
....................................................................................................................................................................................................................................
Security threats ........................................................................................................................................................................ 17-5

17-5
Security layers
......................................................................................................................................................................... 17-7
17-7
Security planes
........................................................................................................................................................................ 17-9
17-9
Security dimensions
............................................................................................................................................................ 17-11
17-11
17-13
Security mapping threats and dimensions ................................................................................................................... 17-13
18
Security architecture of the Small Cell solution

Overview
................................................................................................................................................................................... 18-1
18-1
18-2
Small Cell solution security architecture ....................................................................................................................... 18-2
18-4
Small Cell solution security overview ............................................................................................................................ 18-4
19
Small Cell Security

Overview
................................................................................................................................................................................... 19-1
19-1
19-2
Security on the Alcatel-Lucent Small Cell .................................................................................................................... 19-2
Hardware security
Trusted Boot
.................................................................................................................................................................. 19-4
19-4
............................................................................................................................................................................ 19-5
19-5
19-6
Managed accounts .................................................................................................................................................................. 19-6
19-7
Air interface security ............................................................................................................................................................. 19-7
19-9
Two IPSec tunnels .................................................................................................................................................................. 19-9
20
Secure protocols
Overview
................................................................................................................................................................................... 20-1
20-1
20-2
Secure Shell .............................................................................................................................................................................. 20-2
20-4
Secure FTP ................................................................................................................................................................................ 20-4
20-5
IP security .................................................................................................................................................................................. 20-5
Glossary
Index
....................................................................................................................................................................................................................................
BCR 2.2
xi
401-387-065 Issue 4
July 2010
Contents
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
xii
401-387-065 Issue 4
July 2010
List of tables
7-1
Mandatory parameters table
................................................................................................................................ 7-10
7-2
7-11
Optional parameters table ..................................................................................................................................... 7-11
....................................................................................................................................................................................................................................
BCR 2.2
xiii
401-387-065 Issue 4
July 2010
List of tables
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
xiv
401-387-065 Issue 4
July 2010
List of figures
2-1
Overall system view
................................................................................................................................................. 2-3
2-3
3-1
V1.5 home cell
3-2
V1.5 enterprise cell
6-1
WMS for Small Cell architecture diagram ....................................................................................................... 6-3
6-2
WMS data storage
7-1
WMS for Small Cell datasets and Bulk CM file generation ...................................................................... 7-3
7-2
Neighboring synchronization
7-3
Macro cells neighbor determination
7-4
7-7
LAC assignment ......................................................................................................................................................... 7-7
7-5
Auto-configuration process
7-6
7-17
Small Cell configuration ....................................................................................................................................... 7-17
7-7
Small Cell data model distribution
8-1
Small Cell group creation using WIPS
8-2
Latitude and longitude provisioning
8-3
Workorder to create a Small Cell group
8-4
Small Cell group modification workorder
8-5
Small Cell group update
8-6
Modification of the ACLList of a Small Cell group using HDM .......................................................... 8-30
15-1
Structure of the RF trace tool
.......................................................................................................................................................... 3-7
3-7
................................................................................................................................................... 3-9
3-9
..................................................................................................................................................... 6-5
6-5
............................................................................................................................... 7-4
.................................................................................................................. 7-5
................................................................................................................................. 7-16
................................................................................................................... 7-22
........................................................................................................... 8-26
................................................................................................................ 8-27
......................................................................................................... 8-27
..................................................................................................... 8-28
....................................................................................................................................... 8-29
............................................................................................................................ 15-4
....................................................................................................................................................................................................................................
BCR 2.2
xv
401-387-065 Issue 4
July 2010
List of figures
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
xvi
401-387-065 Issue 4
July 2010
About this document

About this document
Purpose
The purpose of this document is to provide the Operation, Administration, Maintenance

and Provisioning procedures that an operator is able to perform on the Small Cell using
the Wireless Management System for Small Cell (WMS).
Reason for revision
The reissue reasons are:

Issue
Issue date
Reason for reissue
July 2010
Final issue
June 2010
Final issue
March 2010
Final issue
September 2009
Final issue
0.2
June 2009
Preliminary issue
0.1
January 2009
Draft issue
New in this release
New features:
104812, 8 voice call capacity
Operator managed Small Cell
Other changes:
BSR Femto renamed in Small Cell.
New information blocks added or information blocks modified following the

introduction of the Small Cell devices in the Alcatel-Lucent portfolio.
Additional technical information: Small Cell LEDs definition
Updated procedures
Reformat to comply with current documentation standards.
...................................................................................................................................................................................................................................
BCR 2.2
xvii
401-387-065 Issue 4
July 2010
About this document

....................................................................................................................................................................................................................................
Intended audience
The audience for this document is:
Operations and maintenance personnel

Network administration personnel
Configuration management personnel
Supported systems
This document applies to Alcatel-Lucent 936x Small Cell BCR2.2 system release.
How to use this document
No specific recommendation applies regarding the way readers should read this
document.
Prerequisites
It is recommended that readers become familiar with the 3rd Generation Partnership
Project (3GPP) Technical Specification release 99 (R99) and the UMTS specification.
Access to the On-Line Customer Support (OLCS) interface is required. This is the web
portal to access all Alcatel-Lucent customer information.
Conventions used
Vocabulary conventions
None
Typographical conventions
The following typographical conventions are used in this document:
Graphical representation
Description
italicized text
File and directory names

Emphasized information
graphical user interface text
Text that is displayed in a graphical user

interface or in a hardware label
variable
A value that the user supplies.
Command-syntax
Command names that the user types
input text
Text that the user types or selects as input to a

system
output text
Text that a system displays or prints
Key-capture
Indicates a key combination on the keyboard.
Path
Indicates a directory path or a file name.
Attribute
Indicates that this word is a GUI or CLI

attribute (parameter).
....................................................................................................................................................................................................................................
BCR 2.2
xviii
401-387-065 Issue 4
July 2010
About this document

....................................................................................................................................................................................................................................
Graphical representation
Description
IP reference, reference number
Related document that is referenced in the

document
<>
Indicates that the text between the < > signs

should be determined and filled in by the user.
=>
Indicates that a sequence of pull-down menus

should be opened.
Indicates the parent-child relation between two

objects.
Related information
For information on subjects related to the content of this document, refer to the
documents listed in the following table:
Refer to this document
At this location
For more information on
HDM Configuration
Procedure User Guide Phase
5, NN-20500-168
http://support.alcatellucent.com
The way to configure the

HDM in order to manage the
Small Cells
W-CDMA Small Cell Solution

Performance Measurements
Definitions Manual | BCR 2.2
Performance Measurements,
401-387-055
On performance monitoring
measurements
W-CDMA Alcatel-Lucent
Small Cell | BCR 2.2 Specific
Features System Definition
Specification, 401-387-048
Details on specific features of

the Small Cell solution
Small Cell Security System

Definition Specification,
401-387-050
Security in the Small Cell

solution
Small Cell Feature Planning

Guide for the release,
UMT/SYS/INF/025597
The features delivered in this

release
Document support
For support in using this or any other Alcatel-Lucent document, contact Alcatel-Lucent at
one of the following telephone numbers:
1-888-582-3688 (for the United States)

1-317-377-8618 (for all other countries)
....................................................................................................................................................................................................................................
BCR 2.2
xix
401-387-065 Issue 4
July 2010
About this document

....................................................................................................................................................................................................................................
Technical support
For technical support, contact your local Alcatel-Lucent customer support team. See the
Alcatel-Lucent Support web site (http://www.alcatel-lucent.com/support/) for contact
information.
How to order
To order Alcatel-Lucent documents, contact your local sales representative or use Online
Customer Support (OLCS) (http://support.alcatel-lucent.com)
How to comment
To comment on this document, go to the Online Comment Form (http://infodoc.alcatellucent.com/comments/enus/) or e-mail your comments to the Comments Hotline
(comments@alcatel-lucent.com).
....................................................................................................................................................................................................................................
BCR 2.2
xx
401-387-065 Issue 4
July 2010
Part I: Hazard statements
Overview
Purpose
This part provides hazard statements related to the Small Cell.

Contents
Chapter 1, Safety statements
1-1
...................................................................................................................................................................................................................................
BCR 2.2
I-1
401-387-065 Issue 4
July 2010
Hazard statements
Overview
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
I-2
401-387-065 Issue 4
July 2010
Safety statements
1

No safety statement
There are no physical safety statements that are related to the tasks described in this
document.
...................................................................................................................................................................................................................................
BCR 2.2
1-1
401-387-065 Issue 4
July 2010
Safety statements
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
1-2
401-387-065 Issue 4
July 2010
Part II: System description
Overview
Purpose
This part includes descriptive information about the Small Cell solution elements and the
Small Cell Management System.
Contents
Chapter 2, Small Cell solution
2-1
Chapter 3, Small Cell description
3-1
Chapter 4, Small Cell cluster network elements
4-1
Chapter 5, Small Cell core network elements
5-1
Chapter 6, Small Cell Management Solution
6-1
...................................................................................................................................................................................................................................
BCR 2.2
II-1
401-387-065 Issue 4
July 2010
System description
Overview
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
II-2
401-387-065 Issue 4
July 2010
Small Cell solution

2
Overview
Purpose
This chapter describes the principles and the architecture of the Small Cell solution.
Contents
Small Cell application and architecture
2-2
...................................................................................................................................................................................................................................
BCR 2.2
2-1
401-387-065 Issue 4
July 2010
Small Cell solution
....................................................................................................................................................................................................................................

Application
The aim of the Alcatel-Lucent 936x Small Cell solution is to offer an improved coverage
and a dedicated capacity. It allows to better address the enterprises and/or macro coverage
extension use.
This includes:
The open access model

The management of Small Cell groups.
8 voice call capacity
Small Cell to Small Cell mobility
From the end-user perspective connecting to the Small Cell or the Macro 3G network is
transparent and can be done with any legacy handset.
The solution has been designed for four categories of application:
Home
Enterprise
Public indoor also called solution for Metro Indoor
Public outdoor also called solution for Metro Outdoor
The public indoor and outdoor applications will be implemented in future release.
The solution is based on a flat IP architecture that collapses many functions of the
traditional UMTS network into a device.
Elements are provided in the solution to allow a scalable interconnection to the legacy
UMTS network over the existing standardized 3GPP interfaces.
The solution provides support for circuit switched voice as well as UMTS packet data and
High Speed Downlink Packet Access (HSDPA).
The solution benefits are:
Improvement of coverage and capacity at lower CAPEX/OPEX

Low latency
Easy evolution to mobile IP, IMS, LTE

Easy implementation
Improvement of coverage and quality for voice and high speed data on 3G handset
Cheaper communications, specific home tariff for all communications established at

home or in the office
Simplification and convenience (single bill, single handset, multiple lines, content
sharing)
....................................................................................................................................................................................................................................
BCR 2.2
2-2
401-387-065 Issue 4
July 2010
Small Cell solution
....................................................................................................................................................................................................................................
Architecture
The Alcatel-Lucent 936x solution is built around the following elements:
A large number of 3G access points (home, office, public area)

A set of cluster network elements to supply gateways functionality and time server
facilities
A set of core network elements for connection to a standard 3G Core Network through
the Iu-CS / Iu-PS interfaces
A management system which consists of:
Motive Home Device Manager (HDM)
Wireless Management System for Small Cells called WMS for Small Cells
Optionally the Wireless Provisioning System for Small Cells or WPS for Small
Cells
Figure 2-1 Overall system view
....................................................................................................................................................................................................................................
BCR 2.2
2-3
401-387-065 Issue 4
July 2010
Small Cell solution
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
2-4
401-387-065 Issue 4
July 2010

3
Overview
Purpose
First this chapter provides a functional overview, lists the features and describes the
interfaces of the Small Cells.
Secondly it details the characteristics of the Small Cell designed for the home and
enterprise applications, called:
Home Cell
Enterprise Cell
Contents
Small Cell features
3-2
3-6
3-8
...................................................................................................................................................................................................................................
BCR 2.2
3-1
401-387-065 Issue 4
July 2010
Small Cell features
....................................................................................................................................................................................................................................
Small Cell features

Small Cell functional overview
The Small Cell combines the traditional 3G Node B and RNC functions as represented in
the following figure.
IuCS
PSTN
PSTN
RNC
MSC
ATM/IP
ATM/IP
IuPS
Gn
Node B
UE
SGSN
Gi
GGSN
Internet
Internet
Small cell device integrates all this into a single unit

The Small Cell is designed to support up to 8 active subscribers with 3GPP compliant
release 99 DCH (packet and circuit switched services) with 3GPP release 4 HSDPA data
services in the UMTS 2100 MHz band.
The home subscriber is limited in the number of UEs that may be registered as authorized
to use the home cell. These are kept in an Access Control List (ACL) within the Small
Cell and used to allow only authorized UEs to camp on the cell and establish a call. The
ACL can be updated by the Small Cell owner or the operator. It may be disabled by the
operator to allow public access.
As a standard, and for home application, up to 20mW of transmit power is available,
sufficient to allow in-building coverage within the home environment. The approximate
cell radius is 30 meters, although this depends on the construction of the building in
which the Small Cell device is located as well as the prevailing RF conditions.
For enterprise cell device, the operator can increase the level of the RF transmit power up
to 100mW using the FMS. This is set as part of provisioning data.
Small Cell features
The Small Cell provides specific facilities and consists of some characteristics:
Easy to install
The Small Cell device is a small, lightweight, self-contained cell unit and easy to
install. It ensures zero-touch configuration. The end-user is only required to plug-in
the unit and to connect it to a functioning DSL. All other aspects of configuration, IP
connection or getting initial parameters for example, are automatic.
UMTS-compliant User Equipment
....................................................................................................................................................................................................................................
BCR 2.2
3-2
401-387-065 Issue 4
July 2010
Small Cell features
....................................................................................................................................................................................................................................
It allows the end-user to use UMTS-compliant User Equipment (UE) in the home or
in the office, and the network operator to provide a seamless service from macro to
the Small Cell network.
Ethernet interface
The Small Cell provides a 10/100BASE-T Ethernet interface to an IP Transport
Network via an external DSL router.
Tone generation
The Small Cell device generates a special tone during voice call set up, to alert the
end-user that the call is being handled by the Small Cells. This means the end-user is
made aware that the call is charged at the Small Cells network rate.
Emergency call support
An emergency call is given priority over other services. Small Cell allows public
access for emergency call establishment. It means the access control list is ignored
and that an emergency call pre-empts an existing non-emergency call. If the Macro
cell is available, then the UE obtains service from the Macro cell. If no coverage is
available, then the UE goes into Emergency Calls only mode and searches for any
suitable cell to camp on, including the Small Cells.
Security
Air interface security, UE identity checking, authentication, key agreement
procedures, integrity protection, encryption are compliant with the 3GPP standards. A
firewall is provided within the Small Cell unit to protect against malicious attacks.
Secure Shell (SSH) and SFTP are provided for secure management communication
with the FMS.
Self optimization
The Small Cell unit monitors the surrounding network. It changes its Primary
Scrambling Code (up to 16 codes are provided at initial configuration) and adjust
transmit power to avoid interference. Power levels are periodically monitored and
optimized for maximum coverage and capacity without interfering with the
surrounding Small Cells and the macro network.
Information message
The Small Cell network name is displayed on the users terminal.
Operational effectiveness
The Small Cell device supports two performance monitoring (PM) lists and real time
alarm which enhances the operational aspect of the Small Cells network.
National Location Lock
Operator controls over the use of the Small Cell device in unauthorized countries.
Specific features for enterprise or public applications
Four features characterizes the enterprise or public Small Cell device:
Small Cell group

Small Cell group is used in small or medium enterprises, or in public areas where an
Small Cell device is not sufficient to cover the target area. The coverage is provided
by a group of Small Cells. All the Small Cells belonging to the same group have a
common extended Access Control list if any and the same billing definition
(LACx/SACx attributes).
Small Cell to Small Cell CS handover
....................................................................................................................................................................................................................................
BCR 2.2
3-3
401-387-065 Issue 4
July 2010
Small Cell features
....................................................................................................................................................................................................................................
Handover CS voice calls is possible between neighbouring Small Cells within a Small
Cells group.
Open access list
Operator can make use of Small Cells for hot spot coverage and offer access similar to
that of the macro network, without having to grant access to all the Small Cell.
Eight voice call capacity
The call capacity is either:
Eight simultaneous CS calls
Four simultaneous PS calls
Up to four simultaneous PS +CS calls and additional simultaneous CS calls to a

maximum of eight users
Small Cell interfaces
The Small Cell supports logical interfaces and a single physical interface through which it
connects to an IP Transport network via a backhaul interface.
Supported interfaces
Interface description
Interface type
Air Interface (Uu)
Standard UMTS Interface
Logical
Comments
3GPP standards compliant for

local Area Base Stations
TS25.104
Small Cell Backhaul
Interface (Interface to
DSL Router)
Standard 10/100BaseT
Ethernet
Physical
Small Cell - BSG
Proprietary Interface Gateway Maintenance

Interface
Logical
Interface from the Small Cell

to the BSR Signaling Gateway
(BSG)
The BSG includes the

functions of HLR directory,
UE registration, UE
localization & Small Cell
registration.
This interface carries all
messages needed to be
exchanged b/w the Small
Cell & the BSG for such
functions.
All Small Cell -BSG
signaling traffic is IPSec
encrypted.
IuCS'
Proprietary Interface
This interface is proprietary
between the Small Cell and
BSG/BVG.
Logical
IuCS' interface is IP based &

the messages on this
interface are IPSec
encrypted.
....................................................................................................................................................................................................................................
BCR 2.2
3-4
401-387-065 Issue 4
July 2010
Small Cell features
....................................................................................................................................................................................................................................
Supported interfaces
Interface description
Interface type
Comments
IuPS'
The Small Cell cluster

supports an IuPS interface.
Logical
IuPS' interface is IP based &

the messages on this
interface are IPSec
encrypted.
This is the interface between

the Small Cell, BSG & BPG
See Figure 2-1, Overall system view (p. 2-3) to locate the interfaces in the overall
system view.
LED indicators
On the front side there are LEDs that provide information to the end user concerning the
status of the system. For LED details relating to the type of the Small Cell, refer to the
Small Cell notice. The following table provides generic information concerning the LED
end-user interface.
System status
LED definition
Power
System
Phone/Device
Power Off
OFF
OFF
OFF
Power ON
ON
ANY
ANY
Small Cell available

for service
ON
ON
ANY
Small Cell initialising
ON
FLASHING
OFF
Small Cell in
auto-configuration or
in self-optimisation
ON
FLASHING
OFF
Small Cell is not in

service and needs
operator intervention.
ON
OFF
OFF
Phone/Device has
active user(s).
ON
ON
ON
Phone has no active

users
ON
ON
OFF
Phone has maximum

number of users
active
ON
ON
FLASHING
Small Cell serious

hardware failure
(return to supplier)
FLASHING
OFF
OFF
....................................................................................................................................................................................................................................
BCR 2.2
3-5
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................

Home cell device
Three types of home cell access point are available:
Standalone V1.2 home cell device

Standalone V1.5 home cell device
Integrated home cell device
This table lists their characteristics.

Home cell
device
Standalone V1.2
home cell device
Features
Frequency
Mhz
2100
Output power
mW
20
User
capability
4
Characteristic
Lighter in
weight than the
first version and
energy efficient
Integrated
2G/3G sniffer
function
Standalone V1.5
home cell device
2100
20
Integrated
2G/3G sniffer
function
Same software
features as the
V1.2 standalone
home cell V1.2
device
New casing and
customization
possibilities
Two Ethernet
ports
Supports 7.2
Mbps L1
HSDPA bearer
and 1.4 Mbps L1
HSUPA bearer
....................................................................................................................................................................................................................................
BCR 2.2
3-6
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
Home cell
device
Integrated home
cell device
Features
Frequency
Mhz
2100
Output power
mW
20
User
capability
4
Characteristic
Integrated 2G
sniffer function
Integrated WiFi,
ADSL/ADSL2+
modem, IP
router funtion
Office and
public
conceivable
application
This is a view of the V1.5 home cell device.

Figure 3-1 V1.5 home cell
....................................................................................................................................................................................................................................
BCR 2.2
3-7
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................

Enterprise cell device
Two types of enterprise cell access point are available:
V1.2 enterprise cell device

V1.5 enterprise cell device
This table lists their characteristics.

Enterprise cell
device
V1.2 Enterprise
cell device
Features
Frequency
Mhz
2100
Output power
mW
100
User
capability
8
Characteristics
Integrated 2G
/3G sniffer
function
One Ethernet
port
V1.5 Enterprise
cell device
2100
100
New casing
Second ethernet
port
External power
adaptor or PoE+
(Power over
Ethernet
standard) for
supplying power
to the unit via an
ethernet cable
This is a view of the V1.5 enterprise cell device.
....................................................................................................................................................................................................................................
BCR 2.2
3-8
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
Figure 3-2 V1.5 enterprise cell
....................................................................................................................................................................................................................................
BCR 2.2
3-9
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
3-10
401-387-065 Issue 4
July 2010
S4mall Cell cluster network

elements
Overview
Purpose
This chapter describes the functions of the Small Cell cluster network elements.
Contents
BSR Signaling Gateway
4-2
Brick
4-3
NTP server
4-5
...................................................................................................................................................................................................................................
BCR 2.2
4-1
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................

BSG functional overview
The Base station router Signaling Gateway (BSG) terminates the signaling interfaces
going to the traditional core network elements. Thereby it creates the notion of a single
and virtual RNC.
This virtual RNC represents the Small Cell cluster as a whole. The BSG is the integration
point between the Small Cell cluster, and the core network which includes the 3G-MSC
for IuCS control plane purposes and the SGSN for IuPS control plane purposes.
The BSG acts as a:
Signaling Converter, to perform the signaling translation between the SS7 and the
Small Cell IP domains.
Signaling Concentrator, so that a batch of Small Cell appears as a single RNC in the
operator's network.
Mobility Gateway, to track the position of the UE in the Small Cell domain.
The BSG is also used to registered legal requisition information to meet some regulatory
requirements. The allowed legal authorities access to the following data through a web
server:
The Small Cell Internet Public IP address
The Small Cell Factory Serial Number

The port number of the DSL router the Small Cell connects to within the home
network
IMSI of the UE
Date, time and type of the event (SMS or call event)
....................................................................................................................................................................................................................................
BCR 2.2
4-2
401-387-065 Issue 4
July 2010
Brick
....................................................................................................................................................................................................................................
Brick
Brick functional overview
The brick is a single network element that implements the following logical
functionalities:
Base station router Voice Gateway (BVG)
Base station router Packet Gateway (BPG)

Firewall(s)
IPSec router(s)
Small Cell Voice Gateway
The BVG acts as the virtual MSC router for the Small Cell cluster. It acts as the
virtual RNC router for the MSC. All user plane traffic passes through to the MSC
directly from the BVG, while signaling is handled by the BSG.
The BVG enables the separation of the user plane from the control plane for the circuit
switched (CS) services. Iu-CS signaling traffic passes through the BSG.
Small Cell Packet Gateway
The BPG acts as a concentrator for the IuPS interface for a Small Cell cluster, presenting
a single IP address towards the SGSN from the virtual RNC represented by the BSG
and BPG. It performs port and address translation to enable routing to/from the many
Small Cells.
Depending on the number of Small Cells in the cluster, several BPGs may be deployed
per Small Cell cluster.
Firewall and IPSec router
The firewall function provides a Security Gateway/Firewall between the Small Cells and
the operators network, isolating the operators network from potentially harmful traffic.
The IPSec router provides secure IPSec tunnel endpoints to all Small Cells in the cluster.
The mapping is one or two IPSec tunnels for each Small Cell.
The following traffic passes through this tunnel:
All signaling traffic to/from the operator's network elements

All user plane packets
Signalling traffic for the BSG, BVG and BPG functions

All OAM traffic to manage the Small Cells
Having this centralized IPSec router avoids the need to implement IPSec on all the
network elements.
Both traffic inside and outside the IPsec tunnel(s) are subject to firewall checks.
....................................................................................................................................................................................................................................
BCR 2.2
4-3
401-387-065 Issue 4
July 2010
Brick
....................................................................................................................................................................................................................................
Brick management
The Alcatel-Lucent 5620 Security Management System (ALSMS) provides OAM

functions for the Brick.
....................................................................................................................................................................................................................................
BCR 2.2
4-4
401-387-065 Issue 4
July 2010
NTP server
....................................................................................................................................................................................................................................
NTP server
NTP server
The Network Timing Protocol (NTP) server provides the timing solution for the Small
Cell to keep the internal oscillator trained to the correct accuracy.
All Small Cells in the network derive their synchronization from the NTP server. The
server transmits NTP packets to keep the Small Cell synchronized with the network time.
This server guarantees a clock source stable in better than +/- 100 ppb.
The NTP solution is provided by Brilliant Telecommunications and is specific to the
timing solution provided in the Small Cell.
....................................................................................................................................................................................................................................
BCR 2.2
4-5
401-387-065 Issue 4
July 2010
NTP server
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
4-6
401-387-065 Issue 4
July 2010
S5mall Cell core network

elements
Overview
Purpose
This chapter describes the functions of the Small Cell core network elements.
Contents
AAA server
5-2
DNS/DHCP server
5-3
IPC
5-4
Service Router
5-5
...................................................................................................................................................................................................................................
BCR 2.2
5-1
401-387-065 Issue 4
July 2010
AAA server
....................................................................................................................................................................................................................................
AAA server
AAA server
The Alcatel-Lucent 8950 Authentication, Accounting and Authorisation (AAA) is a server

which provides the Small Cell authentication function for the Small Cell cluster.
When the Small Cell requests access to the network:
First it creates an IPsec tunnel to the IPsec router.

Then it requests the AAA to authenticate the request using a RADIUS interface to the
AAA.
The AAA:
Controls the challenge-response protocol between itself and the secure authentication
chip in the Small Cell when the EAP-DS2460 authentication protocol is used.
Interacts with the network to identify the Small Cell Factory Serial Number.
The AAA must be provisioned with the right information to authenticate the Small Cell,
the Serial Number and Pre-shared Key among others.
The AAA is provided with the adapted EAP plugin, to authenticate the Small Cell.
....................................................................................................................................................................................................................................
BCR 2.2
5-2
401-387-065 Issue 4
July 2010
DNS/DHCP server
....................................................................................................................................................................................................................................
DNS/DHCP server
Domain Name Server
There is a fixed mapping between a Small Cell and its IP address. Depending on operator
requirements this can be populated within the Domain Name server (DNS) to allow other
network elements to query the Small Cell address.
NEs use the DNS server to locate the IP address of other NEs within the network.
Dynamic Host Configuration Protocol
The DHCP automates the assignment of IP addresses, subnet masks, and other IP
parameters.
When a Small Cell unit connects to the Small Cell cluster, the Small Cell sends a
broadcast query requesting necessary information from the DHCP server.
The DHCP server manages a pool of IP addresses and information about client
configuration parameters such as the default gateway, the domain name, the DNS servers.
Upon receipt of a valid request the server will assign the Small Cell an IP address, and
configuration parameters such as subnet mask and default gateway.
....................................................................................................................................................................................................................................
BCR 2.2
5-3
401-387-065 Issue 4
July 2010
IPC
....................................................................................................................................................................................................................................
IPC
IuCS Protocol Converter
The IuCS Protocol Converter (IPC) is a functional element in the Small Cell network
solution for support of circuit switched voice and data over ATM transport.
The IPC connects a Small Cell cluster to a 3G-MSC using the Iu-CS over ATM interface.
One IPC can support up to eight Small Cell clusters, depending on throughput
requirements.
The IPC performs:
The IP to ATM conversion and vice versa for the IuCS and IuPS
For IuCS, both signaling and bearer conversion

For IuPS, signaling conversion
For multiple media gateway feature IPC needs to support two media gateways per MSC.
The IPC is required only if an ATM-based IuCS interface is required to the core network.
It is not required for an IP-based IuCS interface.
....................................................................................................................................................................................................................................
BCR 2.2
5-4
401-387-065 Issue 4
July 2010
Service Router
....................................................................................................................................................................................................................................
Service Router
Service Router function
The 7750 Service Router enables layer 2 and layer 3 services on a single platform with
the flexibility of any service over any port using a wide range of interfaces:
DS3/E3, Ethernet
SONET/SDH PoS
Frame relay
ATM
Additional interface options include:
OC-3/STM-1 support on the Any Service Any Port (ASAP) interface card
A combination interface card supporting Gigabit and 10 Gigabit ports
Service Router management
The 5620 Service Aware Manager (SAM) provides OAM functions for the 7750 SR.
....................................................................................................................................................................................................................................
BCR 2.2
5-5
401-387-065 Issue 4
July 2010
Service Router
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
5-6
401-387-065 Issue 4
July 2010
S6mall Cell Management

Solution
Overview
Purpose
This chapter describes the architecture and the elements of the Small Cell Management
Solution. It also covers the management system interfaces.
Contents
Architecture of the WMS for Small Cell
6-2
6-4
6-11
...................................................................................................................................................................................................................................
BCR 2.2
6-1
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................

WMS for Small Cell solution
The architecture of the WMS for Small Cell solution consists of the following products:
The 5580 Home Device Manager (Motive HDM). It is a product for the management
of TR-069 based Customer Premises Equipments (CPE).
The HDM main features are:
Suitable for customer care centers
Zero-touch provisioning
Interfacing with Small Cell

Configuration updates in conjunction with WMS for Small Cell
Software upgrades
Problem diagnosis and troubleshooting
Event Management of the Small Cell devices

Reporting facilities
The 9353 Wireless Management System (WMS) for Small Cell
The WMS is used for:
Small Cell OAM Auto-configuration
Synchronization with Macro Layer Radio configuration using the East-West

interface
Fault Management of the Gateways: BSG, IPC and 7750 SR IP router

3GPP R6 FM North bound interfaces
Performance management: Small Cell Counters storage, BSG and IPC Collection
and storage
The 9352 Wireless Provisioning System (WPS) for Small Cell
The WPS is used for:
Profile and Location management of Small Cell
Configuration management of BSG and IPC with checks
The following figure shows the relations between the different components of the WMS
for Small Cell.
....................................................................................................................................................................................................................................
BCR 2.2
6-2
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
Figure 6-1 WMS for Small Cell architecture diagram
WPS for Small Cell

CM Profiles
Locations
3GPP PM
3GPP FM
WMS for Small Cell
E-W itf
CM XML
Macro cell
config
3GPP PM
Storage
Auto - Config
CM Bulk files
JMS SOAP
HTTP
PM files
PM files
HDM
Inventory
Informs
On-line
Interface
Files
Other CPE
Small Cell CPE
....................................................................................................................................................................................................................................
BCR 2.2
6-3
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................

Overview
The management of the Small Cell devices is performed using the WMS for Small Cell.
The architecture combines the three components:
WMS
WPS
HDM
9353 Wireless Management System for Small Cell
This topic describes the WMS activities and the WMS data storage.
The WMS performs the following tasks:
Generation of the Bulk CM file:

The Femto Adaptation Layer (FAL) of the WMS generates the Bulk CM file, which
represents the initial model information base of the Small Cell. The file is kept
available one day after being collected by the Small Cell via Secured FTP.
Support of Small Cell software:
Small Cell software is downloaded from the WMS to the Small Cell when necessary
(configuration phase or software upgrade). The Small Cell software is stored on the
WMS. The software is collected by the Small Cell via SFTP.
Small Cell Performances Management files:
Small Cell PM files are stored on the WMS. Those counters are pushed through sFTP
every 24 Hours by the Small Cell . By default, the PM is not activated on the Small
Cell .
Small Cell RF Trace files:
Small Cell records RF Trace measurements on demand of the HNM. The RF Trace
files can be collected manually by user through SFTP.
Small Cell faults files:
Small Cell records Small Cell faults in a log file. The log file can be collected
manually by user through SFTP.
WMS data storage
The following diagram displays the data stored in the WMS.
....................................................................................................................................................................................................................................
BCR 2.2
6-4
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
Figure 6-2 WMS data storage
FM OSS PM OSS
PM OSS
FM OSS PM OSS
WMS for Small Cell
Small Cell
CM Bulk files
* *
Small Cell Small Cell Small Cell
IPC
IPC
IPC
IPC
BSG
BSG
BSG
BSG
RF Traces
SW
Backups
Alarms
PM files
SW
Backups
Alarms
PM files
SW
PM files
OSS : Operating System Software

FM : Faults Management
PM : Performances Management
RF : Radio-Frequencies
CM : Configuration Management
SW : SoftWare
....................................................................................................................................................................................................................................
BCR 2.2
6-5
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
9352 Wireless Provisioning System for Small Cell
This topic provides a description of the WPS objectives, main functionalities and
technical implementation.
WPS objectives
WPS tool suite provides the users with tools to generate XML work-orders to be activated
on the live network in order to implement a target configuration.
In the Small Cell network context, WPS for Small Cell is used to create Small Cell
profiles, create the Small Cell clusters, create the locations and to complete the Small Cell
configuration tasks including mechanism to import/export the configuration between
WPS for Small Cell and the WMS for Small Cell server.
For Small Cell profile, the WPS for Small Cell user creates a library of profiles that list
the majority of the parameters required for the configuration of the Small Cell. With WPS
toolset, this library is easily manageable.
For each Small Cell deployed in the network, the operator associates a given Small Cell
profile to specific Small Cell information such as:
The IMSI
The IP address on the VPN (to be used inside the IPSec tunnel).
The cluster the Small Cell must be associated with.

The security Gateway to be used.
The WPS is mainly used for:
Configuration management, offering tabular editor, CM XML import/export,

work-order synchronization, configuration audit, copy/paste, template management,
model check
Small Cell profile management
Cluster management
Location management
WPS main functionalities
The functionalities of the WPS are as follows:
Back office periodically generates a backup of the configuration with all Small Cell .
It contains the data managed at a back office level (such as the geographical location
information in latitude/longitude/z-coordinate format, Small Cell seria).
The WMS for Small Cell generates also periodically a network copy with all Small
Cell currently registered.
Both configurations are merged in the WPS for Small Cell .
Using the comparison capability of the WPS, the operator retrieves the Small Cells
which configuration is not complete (for example: cluster, security gateway or profile
is missing). He can therefore update the uncompleted configuration using bulk update
mechanisms.
A workorder in CM XML format is generated by the WPS. It is possible to import it
in the WMS for Small Cell to see all the Small Cell creations and updates.
....................................................................................................................................................................................................................................
BCR 2.2
6-6
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
In addition, the WPS checks:
The internal configuration of the Small Cell

The Small Cell configuration within a cluster and the BSG
Technical implementation
WPS for Small Cell is running on a dedicated Windows based PC.

The WPS platform is a Java application. It is a generic engine providing a wide range of
configuration management and reporting capabilities.
....................................................................................................................................................................................................................................
BCR 2.2
6-7
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
Motive Home Device Manager
This topic describes:
The management of the inventory

The management of the firmware image
The HDM policies

The individual configuration of the Small Cell
Inventory management
All Small Cells managed by the HDM are identified by means of their TR-069 device ID.
This identifier consists of the manufacturer name, the manufacturer OUI, the Product
Class and the device Serial Number.
The HDM stores all TR-069 object model data passed in the TR-069 Inform message.
This includes device information (vendor name, OUI, product class, serial sumber), the
WAN IP address, the URL of the connection request and connection request
username/password.
The HDM can be configured to store any selection of supported (standard or vendor
specific) TR-069 parameters in its cached data records. They contain cached values of the
last known configuration of CPE.
In addition to the TR-069 object model data, the HDM provides storage for non-TR-069
metadata for the device. This metadata informs about the state of the device (for
example Activated/Non-activated, Enabled/Disabled, Last Contact Time) and about
provisioning set as the cellid.
It also contains subscriber-related information (user-defined User Tags) and
service-related information (user-defined Service Tags and Dynamic Variables).
Firmware image management
The Motive HDM supports Small Cell firmware and software image management using
the standard TR- 069 two-stage approach. First, the device is configured to download the
image file from the FS/WMS using SFTP. Secondly, the CPE installs the software,
reboots and informs the Motive HDM that the new version is installed.
The HDM provides a specific User Interface (UI) screen for firmware image
management. The UI allows specification of firmware images with all the required
parameters. They can also be named and consequently be referred to by name, for
example when they are used as an argument in device operations.
Operators can use the UI to:
Check whether a firmware version has already been defined in the system.
Check whether any configured policies use the firmware before deleting this firmware
version.
Configure a list of prerequisite versions for the firmware update. An upgrade is

possible only if the current version is in the prerequisite list.
....................................................................................................................................................................................................................................
BCR 2.2
6-8
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
Policies
The HDM provides some facilities to configure and manage the device by means of
policies. A policy is a rule inside HDM. It is composed of a policy trigger and a policy
action that contains a set of device selection criteria.
When the policy trigger is received from a device that matches the device selection
criteria, the HDM automatically schedules a device operation based on the specified
selection. A policy continues to run against targeted devices unless it expires or reaches a
failure threshold or retry count configured in the policy. Policies run only on devices that
are currently enabled and not locked by an operator for manual operation. The HDM
offers multiple ways to enable or disable the created policies (immediately, at a specified
date and time, for a define duration repeated daily, weekly, or monthly, etc). In addition,
the policies can be imported or exported in XML format (an use case would be to get
policies from production environment without introducing user errors).
The results of the execution consists of a list of policy outcomes (whether each policy in
the list has been run, and if so, how many times it has run successfully or failed). The list
also provides details on the policy failure threshold (the number of devices on which it
had to fail before the policy was disabled), and whether that threshold was reached.
The HDM supports two types of policy triggers: instant triggers and event triggers.
Instant triggers are used to evaluate the list of targeted devices immediately. Event
triggers occur when an external event, such as a TR-069 Inform message, is received
from the device. A policy contains particular exit criteria which provides specific actions
to be performed after successful policy completion.
The actions may include:
Changing the value of one or more user or service tags. This allows to encode a
statemachine for service activation, for example, by changing the value of the VoIP
service tag from disable to enable after successful service activation policy
execution.
Sending a connection request to the device. This allows chaining policies together.
In combination with the user or service tag value change, it allows conditional
execution of multiple policies.
An example of a policy can be:
Change parameter x from value 2 to value 3 for a list of 1000 selected CPE based on
criteria ABC (for example within a cluster) when the event Periodic Inform has
been received.
Perform this task on a period of 2 days.

Retry maximum 3 times per CPE.
Stop the policy if 100 failures are reached.
Define the policy priority as maximal.
....................................................................................................................................................................................................................................
BCR 2.2
6-9
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
Individual configuration
As explained in the introduction section of this topic, HDM models the Small Cell and a
subset of its management model. HDM has extensive capabilities to identify groups of
Small Cell matching a given criteria (including an individual Small Cell ), and further to
apply specific policies and actions to that filtered set.
HDM supports making configuration changes and invoking actions to Small Cell through
the TR-069 interface for a small subset of the Small Cell MIB. The typical example is the
update of the ACL . The dynamic nature of ACL updates is automatically controlled,
without manual intervention by the HDM operator. When subscriber updates are received
from the Customer System through the HDM API, the HDM transmits updates to the
Small Cell using the TR-69 Set Parameter Values command.
....................................................................................................................................................................................................................................
BCR 2.2
6-10
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................

Overview
The WMS for Small Cell offers 3GPP OAM standards compliant interfaces that allow
network operators to manage Alcatel-Lucent Small Cell networks. The 3GPP compliant
North InTerFace (ITF-N) interfaces are based on the 3GPP standards, and the solutions
offered include support for the Alarm IRP as well as support of XML transfer of
performance counters files. In addition to standard 3GPP interface compliancy, the WMS
for Small Cell provides other interfaces for integration into a centralized Backup and
Restore solution, to a Health monitoring system, to an Inventory solution and so on. The
WMS for Small Cell also interfaces to customer care systems through Web services API
and notifications.
Interface descriptions
WMS for Small Cell provides:
Support for the Small Cell gateway alarms (BSG, IPC).
Interfaces for integration into the network operator IT environment such as:
Centralized backup
Restore solution (Symantec Netbackup)
Health monitoring system (TEC Tivoli)
External RADIUS interface for authentication to external RADIUS server

External LDAP interface for delegation of user identity management to external
LDAP system, supplied by Engineering Services
The Femto Adaptation Layer (FAL) in WMS for Small Cell
The FAL implements the functionality required to interact with the North Bound
Interface (NBI) of the HDM such as:
Notification processing
Bulk CM file creation
HDM support during device registration and auto-configuration.

East-West interface to ensure neighboring synchronization, for the initial start-up of
the Small Cell, between W-CDMA managing solution (WMS) and WMS for Small
Cell
The FS for the XML conversion of performance counters files in 3GPP R5 XML
format.
Work order management. The work orders are CM format XML files used to send
provisioning data from the WPS or from the operators IT system to the WMS for
Small Cell.
The HDM consists of several interfaces which functions are:
To acquire the Access Control List (ACL) information from the Small Cell after
device registration and auto configuration steps
To provide web service APIs through the Northbound Interface (NBI).
....................................................................................................................................................................................................................................
BCR 2.2
6-11
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
It covers
Device inventory functionality
Device registration
Metadata configuration
Device management using pre/custom defined TR-069 functions, actions and
policies
All software APIs required to interact with HDM NBI are provided by HDM
distribution:
The NBI provides web service APIs . It covers assurance-related functionality (a
set of web service methods that can be invoked from the OSS on HDM) to act on
devices from OSS through HDM.
The web services interface is implemented with web services technology that
follows the WS-Basic Profile 1.0 standard that BEA WebLogic 8.1 uses. The web
services interface is provided in the form of a WSDL file (Web Services
Description Language).
The HDM sends notifications (asynchronous events that are sent from HDM to
the OSS) on its NBI. These notifications can be interpreted as alarms and
converted to the appropriate format.
Notifications are implemented according to the JMS (J2EE) standard.
....................................................................................................................................................................................................................................
BCR 2.2
6-12
401-387-065 Issue 4
July 2010
Part III: Performing OAM&P on

the Small Cells
Overview
Purpose
This part details the provisioning principles and tasks, as well as operating procedures.
Contents
Chapter 7, Provisioning
7-1
Chapter 8, Operation
8-1
...................................................................................................................................................................................................................................
BCR 2.2
III-1
401-387-065 Issue 4
July 2010
Performing OAM&P on the Small Cells
Overview
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
III-2
401-387-065 Issue 4
July 2010
Provisioning
7
Overview
Purpose
This chapter describes the provisioning data set, in the WMS and in the HDM, which is
necessary to support Small Cell automatic configuration.
It is informative. It does not contain provisioning procedures.
It also describes the auto-configuration process launched when the end user plugs in the
Small Cell at home, and what happens during the first registration of a Small Cell.
Contents
7-2
Small Cell auto-configuration
7-15
HDM pre-provisioning
7-18
HDM-WMS synchronization
7-22
...................................................................................................................................................................................................................................
BCR 2.2
7-1
401-387-065 Issue 4
July 2010
Provisioning
....................................................................................................................................................................................................................................
Overview
The Small Cell has capabilities for automatic configuration based on the following
datasets:
Macro network dataset
Profiles dataset
Locations dataset
Small Cell specific dataset
These four datasets need to be pre-provisioned in the WMS for Small Cell.
Once the Small Cell is plugged-in, it initiates the registration process.
The auto-configuration process in the WMS generates a final configuration file, the bulk
CM file, resulting from the 4 datasets.
A CM bulk file is dedicated to a given Small Cell which uses the file to start-up and
configure itself.
....................................................................................................................................................................................................................................
BCR 2.2
7-2
401-387-065 Issue 4
July 2010
Provisioning
....................................................................................................................................................................................................................................
Figure 7-1 WMS for Small Cell datasets and Bulk CM file generation
Small Cell
Small Cell
Dataset
Dataset
PROFILES
PROFILES
Dataset
Dataset
MACRO
MACRO
Dataset
Dataset
CM XML
WO
CM XML
WO
LOCATIONS
LOCATIONS
Dataset
Dataset
CM XML
WO
Auto
Configuration
CM XML
WO
WMS for Small Cell
File
Server
HDM
Bulk
Bulk
CM
CM
file
file
TR69
DSLAM
CPE1
Small Cell
Gateways
SFTP
CPE_n
....................................................................................................................................................................................................................................
BCR 2.2
7-3
401-387-065 Issue 4
July 2010
Provisioning
....................................................................................................................................................................................................................................
Macro network data set
The macro network dataset is the list of macro cells used to automatically compute a
search priority list of neighbor macro cells for each Small Cell. The list includes both 3G
and 2G macro cells. Each macro cell definition includes its geographical coordinates.
The macro network dataset contains Macro Network 3G and 2G information, provided
either by East- West interface as an option for 3G, or by CM XML inputs using network
listening capability.
The Small Cell can autonomously build and maintain neighboring lists and target cells for
handover, but to speed-up Small Cell start-up, an initial list of cells can be provisioned for
each Small Cell.
Operating mode:
Manually, including specific external cells applicable for a Small Cell in each Small
Cell work-order
Automatically, pre-provisioning this Macro network dataset in the WMS.
With these information the auto-configuration process hosted in WMS for Small Cell
generates a configuration file dedicated to a given Small Cell. The device needs it to
start-up and be configured. The initial list of macro cells must be available when Macro
Cell auto-calculation algorithm is invoked for a Small Cell.
WMS East-West interface description
The WMS for Small Cell supports optionally a unique East-West interface. This interface
ensures neighboring synchronization for the initial start-up of the Small Cell between the
WMS for W-CDMA solution and the WMS for Small Cell. The handover is consequently
improved. See the following diagram:
Figure 7-2 Neighboring synchronization
2G OMC - R
Updated/deleted
2G cell
3G/2G
E/W interface
3G WMS
3G/3G
E/W interface
Update/delete
2G or 3G
neighboring cell
GSM Access
3G WMS
3G/Small Cell
E/W interface
Updated/deleted
3G cell
UMTS Access
WMS for Small Cell
Small Cell
neighboring cell
for initial
configuration
Small Cell
....................................................................................................................................................................................................................................
BCR 2.2
7-4
401-387-065 Issue 4
July 2010
Provisioning
....................................................................................................................................................................................................................................
This feature is applicable in the case of Alcatel-Lucent W-CDMA solution. For other
solution it is possible to use the standard CM XML interface to import or export the
macro cell data.
The RF coverage of the Small Cell and of the Macro will overlap. Despite the probability
being low, unwilling hand-over (and cell reselection) from Small Cell to Macro layer (2G
or 3G) may happen.
To avoid such situation, the operator has the possibility from the WMS to disallow some
2G and/or 3G Macro cells. For a given Small Cell, this operation prevents potential
handover (and cell reselection) to macro layer.
The list of non-authorized 2G/3G macro cells, can be provisioned using the WPS for
Small Cell or can be loaded in the WMS for Small Cell through the CM XML interface. It
contains a maximum of five 3G macro cells and five 2G macro cells.
Thus, the Small Cell can either listen or not any disallowed 2G/3G macro cells. It can also
discard or not select a disallowed 2G/3G macro..
Macro cells neighbor determination
With the macro 2G and 3G information (geographical coordinates, etc), a defined radius
is applied around the position of the new Small Cell to deploy. All the macro 2G and 3G
cells within the circle belong to the 2G Macro list and 3G Macro list.
Figure 7-3 Macro cells neighbor determination
With these information the auto-configuration process hosted in the WMS for Small Cell
generates a configuration file dedicated to a given Small Cell which will be used by the
device to start-up and be configured.
....................................................................................................................................................................................................................................
BCR 2.2
7-5
401-387-065 Issue 4
July 2010
Provisioning
....................................................................................................................................................................................................................................
Small Cell and Cluster profiles set
The Small Cell profiles are defined with generic configuration parameters applicable to a
set of Small Cells. The parameters include both common cluster data and common Small
Cell profile data.
To simplify configuration required for Small Cell deployment, a library of profiles is
pre-provisioned in WMS for Small Cell. Therefore, to get the majority of parameters
concerning a specific Small Cell group, it would only be required to point to one of the
Small Cell profiles and to a cluster profile. A CM XML work-order containing all
mandatory parameters for each profile defined, needs to be imported into the WMS for
Small Cell, before any Small Cell makes a reference to the profile.
A CM XML work-order containing at least all mandatory parameters for each Small Cell
needs to be imported into the WMS for Small Cell. This CM XML work-order can be
generated using tabular capabilities of WPS.
As the time interval between the purchase of a Small Cell and its network connection can
be short, it would be interesting to implement fully automated processes to provision this
data set into the WMS for Small Cell. This means to automate the translation of MSISDN
to IMSI and the postal address to the coordinates latitude-longitude-zCoordinate. It means
also to select the appropriate profile for the Small Cell and for the Small Cell cluster.
....................................................................................................................................................................................................................................
BCR 2.2
7-6
401-387-065 Issue 4
July 2010
Provisioning
....................................................................................................................................................................................................................................
Location data of the Small Cell
The Small Cell deployment area is divided into geographical locations, given their
top-left and bottom-right latitude and longitude (non-overlapping). Each of these location
areas gets a set of Location Area Codes (LACs) that can be allocated to the Small Cells
deployed. The set of LACs must not be used by the macro network.
In addition, each location is divided in sub-locations. Each of those is defined as well by
top-left and bottom-right latitude and longitude. A unique Routing Area Code (RAC)
value is assigned. A similar approach is handled for Service Area Code (SAC)
assignment.
The location datasets are lists of geographical rectangles (given by their top-left and
bottom-right latitude and longitude) and area codes (LAC/RAC/SAC) to be allocated to
the Small Cell laying in those geographical locations.
A XML workorder specifying the coordinates of each location and ranges of LACs,
RACs and SACs is required to be pre-provisioned in WMS for auto-configuration of
locations for the Small Cells.
When automatic mode is triggered, (by unset the LAC/RAC/SAC value in the Small Cell
work-order), the location to which the Small Cell belongs can be retrieved from this list.
The following diagram gives an example of a Small Cell LAC assignment in a LAC
range.
Figure 7-4 LAC assignment
Lac range = 1-5

Lac
Lac
Lac
Lac
Lac
Lac
range range range range range range
Lac
Lac
Lac
Lac
Lac
Lac
Lac=4
Lac=2
Lac=1
Lac=?
Lac
Lac
Lac
Lac
Lac
Lac
Lac
Lac
Lac
Lac
Lac
Lac
Lac=3
Lac
Lac
Lac
Lac
Lac
Lac
Lac
Lac
Lac
Lac
Lac
Lac
Lac=1
Lac=5
LAC zones are defined by Top-Left and Bottom-Right coordinates
Random LAC assignation
As an alternative to geographical criteria, Small Cell operators may assign randomly the
LAC for the Small Cells. The FAL is able to assign randomly these parameters using a
range or a list of possible values.
....................................................................................................................................................................................................................................
BCR 2.2
7-7
401-387-065 Issue 4
July 2010
Provisioning
....................................................................................................................................................................................................................................
Three LAC algorithms co-exist in the same WMS for Small Cell installation. The
procedure in that case is as follows:
If the Small Cell creation/modification workorder includes a manual LAC value, that
value shall prevail, any other computation is skipped.
If there is no value in Small Cell creation, or it is unset in Small Cell modification:
If geographical coordinates are available for that Small Cell, the

geographical-based algorithm is executed, modified to take into account the valid
set of LACs per cluster.
If geographical coordinates are not available, a LAC value from the allowed set in
the Small Cell cluster is used. The algorithm ensures that all allowed LAC codes
are used, so it first picks any unused LAC. If all LAC values in the allowed set are
already in use, it pseudo-randomly takes any value from the set.
Small Cells without coordinates are not considered by the geographical-based
algorithm: they are not present in the geographical grid service (FAL cache),
hence not retrieved in the find nearby Small Cells procedure. For the other way
around, Small Cells with geographical coordinates do not interfere the random
algorithm.
Detection of collapsing LAI
Detection of Collapsing LAI is an exceptional case, since normally the WMS for Small
Cell system is used to automatically assign location, routing/service area codes for each
Small Cell based on geographical location information.
The mobile operator must ensure that the LAI data chosen for a particular Small Cell has
a value which is not the same as another Small Cell within its neighbourhood. The
allocation of different LAIs in neighbouring Small Cells is applicable for closed access
(or private access) and open access modes of operation.
The Small Cell raises the 'Real Time' alarm of 'Detected Collapsing LAI' when the Bulk
CM download has been completed and after auto-configuration is run. In case of Small
Cell Power Cycle, Reboots or Resets, the non real time collapsing LAI alarm is raised.
In order to resolve the 'Detected Collapsing LAI' alarm, the WMS for Small Cell Operator
must re-plan the LAC data, to value that is nonconflicting. To aid this process, the list of
LAC values of Small Cell neighbour cell(s) is sent in the 'additional text' field of the
alarm to the WMS for Small Cell.
As a consequence of Small Cells being in service/out of service, LAC values could
'appear' and 'disappear'. This could trigger a flood of 'Detected Collapsing LAI' alarms.
Further changing the area code on one Small Cell can create a ripple effect on the
neighbouring Small Cells.
For the case where Small Cells are set up in a Group configuration, it would be more
effective to change the LAI data on the non-group Small Cell when the 'Collapsing LAI
Detected' alarms are raised.
....................................................................................................................................................................................................................................
BCR 2.2
7-8
401-387-065 Issue 4
July 2010
Provisioning
....................................................................................................................................................................................................................................
Dynamic LAC and SAC allocation
During the auto-configuration process the Small Cell listens to the 3G macro layer and
sets dynamically the LAC and SAC values with the incoming macro information.
It is an alternative to fix the LAC and SAC values from the WMS for Small Cell. The
Small Cell itself allocates the LAC and SAC.
Super LAC management
The Super LAC facility minimizes the provisioning effort in the CNs (Core Network) by
reducing the number of LACs used by the Small Cell cluster in the view of the CN.
Description:
LAC broadcast by the Small Cell cell (air LAC) is different from the LAC used
through Iu interface (super LAC)
As a result one LAC (super LAC) is required per Iu, or 3 if home tariff is used for the
owner, the guest, and emergency calls.
The UE sees multiple LACs which allows neighbor Small Cells to be configured
using different LACs (air LACs) , while the CN sees only one LAC (Super LAC) per
Small Cell cluster.
It is achieved using:
Super LAC value towards the CN

Air LACs value toward the UE
....................................................................................................................................................................................................................................
BCR 2.2
7-9
401-387-065 Issue 4
July 2010
Provisioning
....................................................................................................................................................................................................................................
Small Cell specific dataset
The Small Cell specific datasets contain parameters specific for each Small Cell. These
datasets are pre-provisioned in WMS for Small Cell prior to the Small Cell registration.
The Small Cell registration takes place before the Small Cell is plugged-in into the
network, but after Small Cell purchase. Some of the data contained in this dataset are
provided by the end-user.
The Small Cell specific datasets are provisioned with a cluster profile reference and a
Small Cell profile reference. Those profiles must be defined first. Otherwise there are
missing references.
Input data is based on:
Network design, it can be for example the IP address of the BVG and BPG, or the
value of the frequency bands.
Tests results or engineering recommendations, as for example threshold values, power
settings.
Operator policies used for example to get the value of parameters such as the access
list capabilities and the ciphering.
Type of Small Cell, as example parameter to specify hardware variant.
The following tables display the mandatory and the optional parameters.
Table 7-1
PARAMETER
DESCRIPTION
NORMALLY PROVIDED BY
FemtoId
ID of Small Cell. This ID is

unique in the network
Operator, based on operator

policies
clusterId
reference to OAM cluster
Operator, based on network

design
femtoClusterId
reference to Small Cell cluster

design
ipsecRouterIPAddr
transport address of IPSec

router

design
Latitude
location on Earth based on

north or south of the equator
Operator back-office, based on

location/postal address. It must
be within rectangles defined in
the Locations dataset
Longitude
east-west geographic
coordinate

location/postal address. It must
be within rectangles defined in
the Locations dataset
Profile
reference to Small Cell profile

policies/network design
serialNumber
S/N of Small Cell box

input provided by factory for
each Small Cell
....................................................................................................................................................................................................................................
BCR 2.2
7-10
401-387-065 Issue 4
July 2010
Provisioning
....................................................................................................................................................................................................................................
Table 7-1
(continued)
PARAMETER
DESCRIPTION
gsmListenerPicoBasedEnabled
Enables/Disables the 2G
network listening function
based on an integrated 2G
Network Listening software
(instead of using a separate
module)

input provided by factory for
each Small Cell
Table 7-2
Optional parameters table
PARAMETER
DESCRIPTION
areaIdentityGA
Area Identity used if

Geographical Area is
requested for Reporting Area
in the RANAP LOCATION
REPORTING CONTROL
Operator based on network

design
bsrId
ID for radio interface. It must

be unique per cluster

design. If unset, it is
automatically filled by WMS
for Small Cell
fddCellIdList
List of references to FDD

Neighbouring Cells
If unset, list of references is

auto-generated by WMS for
Small Cell, based on
pre-provisioned Macro info.
It can also be filled by
operator based on previous
calculations. Note that an
empty list of references will
mean that WMS for Small
Cell wont send any 3G
neighbor list in the CM Bulk
file. Additionally Small Cell
sniffs for available FDD
Cells
femtoACLlist
List of IMSIs permitted to

use H-BSR resources.
Operator back-office, based

on list provided by final user
at purchase. It can directly be
modified by final user after
registration
femtoACLlistGuest
List of IMSIs permitted to

use H-BSR resources as
guest.

on list provided by final user
at purchase. It can directly be
modified by final user after
registration
....................................................................................................................................................................................................................................
BCR 2.2
7-11
401-387-065 Issue 4
July 2010
Provisioning
....................................................................................................................................................................................................................................
Table 7-2
(continued)
PARAMETER
DESCRIPTION
gsmCellIdList
List of references to GSM

Neighbouring Cells
If unset, list of references is

auto-generated by WMS for
Small Cell, based on
pre-provisioned Macro info.
It can also be filled by
calculations. Note that an
empty list of references will
mean that WMS for Small
Cell wont send any 2G
neighbor list in the CM Bulk
file.
locationAreaCode
Fixed length code (2 octets)

identifying a location area
within a PLMN
If unset, auto-generated by
WMS for Small Cell based
on pre-provisioned Locations
when generating CM bulk
file. Or it can be filled by
calculations.
locationAreaCode1
Alternate LAC value, that

can be used for owner calls
Operator based on operator

policies. Optional alternate
LAC not used for mobility
procedures within the Small
Cell network.
locationAreaCode2

can be used for guest calls

LAC not used for mobility
Cell network.
locationAreaCode3

can be used for emergency
calls

SAC not used for mobility
Cell network.
notAllowedFddCellIdList
List of references to not

allowed FDD Neighbouring
Cell

design/policies.
notAllowedGsmCellIdList
List of references to not

allowed GSM Neighbouring
Cell

design/policies.
....................................................................................................................................................................................................................................
BCR 2.2
7-12
401-387-065 Issue 4
July 2010
Provisioning
....................................................................................................................................................................................................................................
Table 7-2
(continued)
PARAMETER
DESCRIPTION
routingAreaCode
Fixed length code (1 octet)

identifying a routing area
within a location area
calculations.
serviceAreaCode
Area code for service in the

range of [0..65535]
calculations.
serviceAreaCode1
Alternate SAC value, that

can be used for owner calls

Cell network.
serviceAreaCode2

can be used for guest calls

Cell network.
serviceAreaCode3

can be used for emergency
calls

Cell network.
uncertaintyRadius
Uncertainty radius of the

Area Identity supported. This
is required if RANAP
LOCATION REPORTING
CONTROL includes
Accuracy Code IE.

design. If using WiPS a
default value is provided.
userSpecificInfo
Information field reserved to

the user.

policies. Empty or any
string. No specific treatment
on this field is performed by
the system.
....................................................................................................................................................................................................................................
BCR 2.2
7-13
401-387-065 Issue 4
July 2010
Provisioning
....................................................................................................................................................................................................................................
Table 7-2
(continued)
PARAMETER
DESCRIPTION
zCoordinate
Coordinate Z of the position.

on consumer information. In
dense urban areas, it should
not be considered as an
optional parameter.
Consistent approximate
value should be provisioned
for coordinate Z.
....................................................................................................................................................................................................................................
BCR 2.2
7-14
401-387-065 Issue 4
July 2010
Provisioning
....................................................................................................................................................................................................................................

Data flows and system interactions
The following diagram gives a synthetic view of the data flows and system interactions
during the Small Cell auto-registration process.
Auto-registration process
1. At the factory, the Small Cell is manufactured with
An identifier
The address of the Small Cell signaling gateway
The WMS for Small Cell address
2. When the Small Cell is assigned to an end user, the customer back-office registers the
end user's characteristics.
It means
3.
4.
5.
6.
7.
Name
Telephone number
Postal address
The postal address is translated into latitude, longitude and z coordinates.
The Small Cell is created in the WPS according to the end user data. The creation can
be done from another Small Cell using the copy and paste facilities. According to the
geographical values and the operator engineering rules, the cluster identifier, the
profile, the IPsec address are defined. The work-order creation for the Small Cell is
generated according to the selected cluster and profile.
The work-order is then loaded in the WMS. The Small Cell is consequently registered
in the WMS database. When requested, the auto-configuration process generates the
Bulk CM File dedicated to the Small Cell. The WMS for Small Cell is responsible for
running the cell-planning algorithms. This process extracts the correct parameters for
the Small Cell. The parameters are sent through the CM Bulk File to the Small Cell
which configures itself accordingly. Among the parameters are the LAC/RAC/SAC,
the range of primary scrambling code, Cell-ID, most probable 3G and 2G neighbor
list and the transitory cell scrambling code.
The Bulk CM file is generated for the registration of the new Small Cell once it is
plugged into the network.
The HDM registers the Small Cell when it gets the data from the FAL, and generates
an activation event that triggers the pre-defined Small Cell device activation policy.
This policy includes a file download and causes the Small Cell to download the
configuration file from the WMS server.
During the auto-configuration process the Small Cell checks the MCC and the IP
address whether to start transmission or to turn off and inform the operator. This is
called the national location lock procedure. It provides the operator with the means to
prevent transmission when the Small Cell is installed in or moved to a country in
which the operator is not authorized to transmit.
....................................................................................................................................................................................................................................
BCR 2.2
7-15
401-387-065 Issue 4
July 2010
Provisioning
....................................................................................................................................................................................................................................
Figure 7-5 Auto-configuration process
Step 6
Small
CellCell
ID ID
Small
Step 1
SGW @
FMS @
Factory
FMS
Customer
Care
Step 6
New
Small Cell
E-W itf
HDM
HNM
Small
Small
Cell Cell
ID ID
W-CDMA
Small
Small
Cell
Cell
ID ID
Subscriber @
MSISDN
Postal @
Shop
WMS
Step 2
Billing
System
3G macro list
2G macro list
WMS
forforSmall
WMS
SmallCell
Cell
Configuration
snapshot
CM XML
New
subscriber
LAC, RAC, SAC
Auto
Configuration
Step 5
Configuration workorder
Small Cello Creation/Update
CM XML Step 4
Subscriber @
IMSI
Latitude
Longitude
Consumer profiles
RF and transport inputs
Small
Small
CellCell
ID ID
Clusterid
Profile
Z- coordinate
IPsec @
Operator Back-office
WPS for Small Cell
Step 3
Other data flows
The operator periodically generates a backup copy of all Small Cell network. It contains
all the data managed at the back office level (such as the latitude, longitude and the z
coordinates, the Small Cell serial number, the end users personal data).
The four steps of the data flow process are:
1. WMS for Small Cell periodically generates a second copy of all the Small Cell
currently registered.
2. Both copies are merged in the WPS for Small Cell .
3. Using the WPS capabilities, the operator can extract Small Cell with incomplete
configuration, and using bulk update mechanisms complete the configuration.
4. A work-order in CM XML format is generated by the WPS, compared to the WMS
for Small Cell initial backup and then imported in the WMS for Small Cell. The
operator uses the WPS-WMS CM XML interface to reflect all Small Cell creations
and updates.
....................................................................................................................................................................................................................................
BCR 2.2
7-16
401-387-065 Issue 4
July 2010
Provisioning
....................................................................................................................................................................................................................................
Detailed datasets
A bulk CM file is generated:
When the Small Cell registers for the first time.

When operator triggers a bulk CM rebuild procedure in case of macro network
modifications or software upgrades.
The following diagram displays in a more detailed way the content of the four data sets.
Figure 7-6 Small Cell configuration
3G & 2G Macro NW Data
Generic to all Small Cells
Generated by East-West i/f (for 3G)
CM XML format
Macrocell PSC, Frequency Band, DL
UARFCN, UL UARFCN, Longitude and
Latitude of the Base Station, Cell ID
of Macro Cell
3G Macro networks, on a per cell
basis:
PLMNId
LAC/RAC
CellId (incl. RNCId)
ARFCN UL & DL
PSC
Geographical coordinates
2G Macro networks, on a per cell
basis:
PLMNId
LAC/Ci
Frequency band
ARFCN
BSIC
Geographical coordinates
Small Cell and Cluster Profiles

Generic for all Small Cells
Generated by Back-Office
and / or WPS
CM XML format
Cell ID range
Frequency band
DL/UL UARFCN
PSC range
Min/max pilot and data
power settings
PLMN-ID
BSG IP@
Location Data for Small Cell

layer
Generic to all Small Cells
Generated by Back-Office
and / or WPS
CM XML format
Geographical area design
LAC/RAC/SAC ranges
Small Cell Specific data

Specific for each Small Cell
Generated by Back-Office and WPS
CM XML format
Small Cell Small Cell ID
Profile ID
Cluster ID
Initial ACL
Latitude / Longitude / z-cor
Authentication data (Digital Certificates)
Small Cell Serial Number
Small Cell Auto - configuration (Bulk CM file)

Based on geographical coordinates:
Initial 3G neighboring cells
Initial 2G neighboring cells
LAC/RAC/SAC
Based on operator policy:
UL/DL Frequency
Small Cellid
Dedicated PSC range
Configure RF parameters (CRP, HO, pilot,
path loss model, ) based on Small Cell
template Id
WMS
Auto-Config
HDM
CM Bulk files
Bulk
CM file
The MIB of a Small Cell

represents around
400 parameters
The figure displays the key informations computed by the auto-configuration process.
The Small Cell bulk CM file is collected by the Small Cell using secured FTP. The file is
kept one day on the WMS file server after being collected.
....................................................................................................................................................................................................................................
BCR 2.2
7-17
401-387-065 Issue 4
July 2010
Provisioning
....................................................................................................................................................................................................................................
Overview
The present topic describes the features and data required by the HDM to enable the
Small Cell management.
The configuration process of the HDM for Small Cell is described in the document HDM
Configuration Procedure User Guide Phase 5, NN-150-168.
Adapting HDM to Small Cell
To be able to manage the Small Cell, the HDM must be provisioned with the Small Cell
device type.
The Small Cell device type consists of the following data:
Name
Description
Activation data settings
HTTP default password

Access Control Server (ACS) URL
Provisioning mode
Connection Request Method
Connection Request Available option
Device type attributes

Baseline data
Subset of attributes of the Small Cell data model
Criteria templates
Five custom criteria templates are installed by the HDM adaptation kit.
Two of them are used to select the devices from their Cluster ID and Geographical
Location respectively:
Find devices by Cluster Id
Find devices by Location
Two other ones are used for Fault Management and Performance Management purposes:
Find devices by Alarms Management
Find devices by Performance Attributes
The last one is used for finding devices by their Service Tag:
Find devices by Service Tag
Those criteria templates are selected as search profiles in policies.
....................................................................................................................................................................................................................................
BCR 2.2
7-18
401-387-065 Issue 4
July 2010
Provisioning
....................................................................................................................................................................................................................................
Note: A policy is a rule that defines a set of conditions, or selection criteria, and
associated actions. If a device meets these conditions, the specified actions for that
rule are run.
Actions
The following actions are available:
PM Enable sets the variable Device.Services.BSR.1.PM.1.perfMeasEnabled of the

target Small Cell to TRUE. It is used by the Activate PM File Upload policy.
PM Disable sets the variable Device.Services.BSR.1.PM.1.perfMeasEnabled of the
target Small Cell to FALSE.
It is used by the Deactivate PM File Upload policy.
RFTrace Enable sets the variable
Device.Services.BSR.1.RFTrace.1.administrativeState of the target Small Cell to
unlocked.
It is used by the Activate RFTrace File Upload policy.
RFTrace Disable sets the variable
Device.Services.BSR.1.RFTrace.1.administrativeState of the target Small Cell to
locked.
It is used by the Deactivate RFTrace File Upload policy.
CM Download is used to download the initial configuration file from File Server.
It contains the file download parameters (name and location).
A get parameter value action is executed to synchronize the HDM database with
Small Cell data model, after the download. It is used by the CM Download policy.
SDF Download is used to download the firmware upgrade image file from File
Server.
It contains the file download parameters.
A get parameter value action is also executed to synchronize the HDM database with
the Small Cell data model.
This action is used by the SDF Download policy.
Trigger SDF File sets the Device.Services.BSR.1.SDM.1.sdmActionName parameter
to Rebuild.
Trigger CM File sets the Device.Services.BSR.1.SDM.1.sdmActionName parameter
to Rebuild.
If the action is performed, the Small Cell device sends a bootstrap event to the
server and the activation scenario restarts.
This action is used by the Automatic Femto re-sync with HDM policy.
....................................................................................................................................................................................................................................
BCR 2.2
7-19
401-387-065 Issue 4
July 2010
Provisioning
....................................................................................................................................................................................................................................
Small Cell Activation consists of three steps:

Custom function takes the periodic inform interval (s) as an input value, and sets
the corresponding parameter using the action Set Parameter Values. The default
value is 43200 seconds (12 hours).
The configuration file is downloaded.

Using the Femto Activation policy, the Small Cell database is synchronized with
the Small Cell data model.
Sync Operational States defines the set of Small Cell parameters, which needs to be
updated in the HDM database.
It is based on the Get Parameter Values function.
It is run from the Sync Operational States policy.
Policies
The following policies are defined:
Activate PM File Upload

It activates the transfer of the performance management files from the Small Cell to
the file server.
The selected Small Cells are identified by a search profile Find devices by Service
Tag.
Candidate devices have the service tag PMStatus value equal to disabled.
This policy is launched manually by the operator.
Deactivate PM File Upload. It deactivates the transfer of the performances
management file from the Small Cell to the file server.
It is run manually by the operator.
The selected Small Cells are identified by a search profile Find devices by
Performance Attribute.
Activate RFTrace File Upload. It activates the transfer of the radio frequencies trace
file from the target Small Cell to the file server.
The selected Small Cells are identified by a search profile Find devices by Service
Tag.
Candidate devices have the service tag RFTraceStatus value equal to disabled.
Deactivate RFTrace File Upload. It deactivates the transfer of the performances
management file from the Small Cell to the file server.
The target Small Cells are identified by a search profile Find devices by RFTrace
Attribute.
CM Download Policy. It is automatically launched following some events.
It activates the CM Download action for the Small Cell that raised the event.
It is activated only if the service tag operation of the Small Cell value is set to the
cmDownload value.
The possible events which launch the policy are:
Reboot of the Small Cell
Value change
....................................................................................................................................................................................................................................
BCR 2.2
7-20
401-387-065 Issue 4
July 2010
Provisioning
....................................................................................................................................................................................................................................
SDF Download. It is an event-based policy.

It activates the SDF Download action for the Small Cell that raised the event.
This policy is activated only if the service tag operation of the Small Cell value is set
to the sdfDownload value.
The possible events are:
Connection request
Periodic time
Reboot of the Small Cell

Value change
Connection request
Periodic time
Sync Operational States. It activates the Sync Operational States action to update a
set of parameters of the Small Cell state in the HDM.
It is executed always when the device sends aBoot Inform Femto Activation.
Automatic Femto re-sync with HDM. It triggers the CM File Creation action on the
target Small Cell.
The activation scenario is then run for the Small Cell.
The target Small Cells are filtered by a service tag criteria value cmDownloadRequest for the operation service tag.
This policy is run manually the operator.
Small Cell Activation Policy. It is an event-based policy.
It activates the Femto Activation action for the Small Cell that raised the event
Activation.
There is no search profile or filter mechanism on the Femto Activation policy.
....................................................................................................................................................................................................................................
BCR 2.2
7-21
401-387-065 Issue 4
July 2010
Provisioning
....................................................................................................................................................................................................................................
Overview
Small Cell configuration data being available both on HDM and WMS, there is a need for
data consistency. Data synchronization mechanism is supported between WMS and HDM
in order to solve irrelevant values.
The Small Cell data model organization and distribution is displayed in the following
diagram:
Figure 7-7 Small Cell data model distribution
BSR
HDM
Upsync
Non provisionable data

visible on TR-069
HDM data
(e.g. device GUID)
TR-069 data
only visible from HDM
(ie not in RAN model)
Persistent TR-069 data

only visible
from HDM
Provisioning data
(Bulk file)
WMS specific data

(e.g. Small Cell Network)
HDM data subset

(e.g. DeviceGUID)
Persistent
non provisionable
TR-069 data
TR-069 data
visible from
HDM and WMS
Non TR-069 data

(from WMS)
WMS
Upsync
and
DownSync
Per Small Cell

TR-069 data
Per Profile
TR-069 data
Persistent TR-069 data
visible from
HDM and WMS
DownSync
Non TR-069 data
Private data
Synchronization and Small Cell data model
The Small Cell model data is classified into different categories:
bsrProfile: shared radio parameters provisioned by WMS

Resynchronization from WMS to HDM only
femtoClusterProfile: shared cluster parameters provisioned by WMS
Resynchronization from WMS to HDM only
BSRAuto: specific parameters computed by Small Cell
Self optimization parameters (not modifiable): out of resynchronization scope
WMS for BSRAuto: specific parameters computed by FAL
....................................................................................................................................................................................................................................
BCR 2.2
7-22
401-387-065 Issue 4
July 2010
Provisioning
....................................................................................................................................................................................................................................
Resynchronization scope
femtoPreprovision: specific parameters modifiable by HDM and WMS
Resynchronization scope
To avoid inconsistency between the two databases, it is recommended to:
Modify the Small Cell profile attributes from the HDM

Modify the Small Cell profile attributes from the WMS
WMS update
On each modification on WMS:
For downSync data:

WMS calls a function on HDM to update the modification on HDM.
For upSync_downSync data:
WMS calls a function on HDM to update the modification on HDM.
For upSync data:
WMS just updates the database, no calls to HDM.
HDM update
On each modification on HDM:
For downSync data:

HDM doesnt send any notification to WMS.
For upSync_downSync data:
HDM sends a notification to WMS after Small Cell s response.
For upSync data:
HDM sends a notification to WMS after Small Cell s response.
Decision table
According the type of data, the WMS for Small Cell applies a generic decision table
identifying the data to be synchronized.
The columns headers are:
Computed by FAL are the attributes that are automatically calculated by FAL.
WMS Prov are attributes that can be modified by Operator by any means: Wips,
Activation Manager, Object Editor.
HDM Persisting are attributes that are visible (mostly accessible by TR 69, but not
only), modifiable and persistent in HDM (ex: dynamic get are not included).
The table results are:
DownSync is the synchronization from WMS to HDM.

UpSync is the synchronization from HDM to WMS.
....................................................................................................................................................................................................................................
BCR 2.2
7-23
401-387-065 Issue 4
July 2010
Provisioning
....................................................................................................................................................................................................................................
The following table describes the synchronization rules for Small Cell specific
parameters:
Computed by
FAL (fmsAuto)
WMS Prov
(bulkCM)
HDM Persisting
(itf-bsr)
Result
DownSync
Result UpSync
True (fmsAuto)
True (RW)
True (RW)
False (RO)
True (RW)
False (RO)
True (RW)
False (RO)
True (RW)
False (RO)
False (RO)
False
(femtoPreprov)
True (RW)
False (RO)
The following table describes the synchronization rules for Small Cell profile parameters:
Computed by
FAL (fmsAuto)
WMS Prov
(bulkCM)
True
Not applicable
False
(bsrProfile,
bsrClusterProfile)
True (RW)
False (RO)
HDM Persisting
(itf-bsr)
Result
DownSync
Result UpSync
True
False
Y (cause
bulkCM file)
True
False
Resynchronization property
A new attribute property should be added in the RAN model to indicate the
synchronization direction.
Name: resynchroDirection
Possible values are: upSync, downSync, upSync_downSync, none.
Limitations
The synchronization process is applicable only on parameters that are visible on WMS
and HDM.
As the HDM to Small Cell interface is not a full time connection mode, the Small Cell
can be turned on/off. It means any modifications on WMS or HDM may not directly sent
to the Small Cell if it is not connected, the data will be sent at next reconnection.
The synchronization feature insures data synchronization between WMS-HDM but not
data synchronization between HDM and Small Cells or WMS and Small Cell.
....................................................................................................................................................................................................................................
BCR 2.2
7-24
401-387-065 Issue 4
July 2010
Operation
8
Overview
Purpose
This chapter describes how to perform the main operating tasks on the Small Cell.
Contents
8-2
Small Cell addition
8-4
Small Cell parameters check out
8-7
Small Cell parameters modification
8-10
Small Cell profile modification
8-12
Legal requisition activation/deactivation
8-14
Display and update the Access Control List
8-15
8-19
Small Cell deletion
8-21
Small Cell activation
8-23
Change of the Small Cell postal address
8-24
8-25
8-33
Small Cell specific parameters
8-34
8-35
Enhanced transport CAC activation
8-36
Small Cell access
8-37
...................................................................................................................................................................................................................................
BCR 2.2
8-1
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................

Purpose
This topic describes how to display a target device in the Devices tab of the HDM.
Prerequisites
The HDM application displays the Welcometab.
Procedure
...................................................................................................................................................................................................
Click on the Manage Devices icon or click on the Devices tab.

...................................................................................................................................................................................................
Select the adapted Search Profile .

...................................................................................................................................................................................................
Fill the search criteria corresponding to the search profile.

...................................................................................................................................................................................................
Click on the Find devices button to display thes devices list.
....................................................................................................................................................................................................................................
BCR 2.2
8-2
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................
Results
The list of Small Cells corresponding to the Search Profile criteria are displayed in the
Devices tab. Each device is accessible via its Manage button and its Small Cell serial
number.
....................................................................................................................................................................................................................................
BCR 2.2
8-3
401-387-065 Issue 4
July 2010
Operation
Small Cell addition
....................................................................................................................................................................................................................................
Small Cell addition

Overview
This topic describes how to add a new Small Cell in the network.
Prerequisites
Small Cell profiles are already provisioned.

The following Small Cell provisioning data are available:
Device Type
Serial Number
Manufacturer
Product Class
Protocol
Subscriber Ref ID
IP Address
AAA is already provisioned with the serial number of the Small Cell to be added.
Network definition is completed with Small Cell profiles, macro data for 3G and 2G,
and with locations.
Procedure
Steps to add a new Small Cell to the network are as follows:

...................................................................................................................................................................................................
Using a text file editor, create a work order file with content similar to the following
example:
<?xml version='1.0' encoding='UTF-8'?>
<workorders>
<workorder name="new workorder (5)" creationDate="2008-09-04 17:
09:40.443 +0300" originator="" description="">
<FemtoNetwork id="1" model="OAM" version="OAM" clusterId=
"UMAINSERV1">
<Femto id="12345" method="create">
<attributes>
<clusterId>Cluster/UMAINSERV1</clusterId>
<femtoClusterId>Small Cell Cluster/1</femtoClusterId>
<ipsecRouterIPAddr>1.2.3.4</ipsecRouterIPAddr>
<latitude>48.7352</latitude>
<longitude>2.1055</longitude>
....................................................................................................................................................................................................................................
BCR 2.2
8-4
401-387-065 Issue 4
July 2010
Operation
Small Cell addition
....................................................................................................................................................................................................................................
<profile>Profile/0</profile>
<serialNumber>femto1435</serialNumber>
</attributes>
</Femto >
</FemtoNetwork>
</workorder>
</workorders>
...................................................................................................................................................................................................
Create a WICL script by typing the following WICL commands into a file:
CM createSession <Create_new_Femto> -file <prueba_vdf.xwo>
CM terminateSession <Create_new_Femto>
...................................................................................................................................................................................................
Download the script file as well as the workorders to the directory /opt/nortel/data/
cmXML on WMS for Small Cell using FTP and specifying the appropriate user name and
password.
...................................................................................................................................................................................................
Schedule a job in the crontab or jobscheduler to run the script.
Registration step
Configuration data for the new Small Cell are now available on WMS, so that the final
bulk CM file to be downloaded to the new Small Cell when it connects to the network, is
available.
This process of CM downloading is initiated when the Small Cell is plugged into the
network into the network at consumer's residence.
The Small Cell is shipped with generic factory default software and some initial data, that
allows Small Cell to connect to a known URL and download the accurate software when
it first connects to the network. Once software has been automatically upgraded to the
latest release, HDM indicates to the WMS that a new Small Cell is registering and that its
associated bulk CM file must be downloaded to this Small Cell.
When this process finishes, the new Small Cell will be fully configured and ready for
service, but as the HDM is not aware of the content of this initial configuration file. Then,
HDM database must be synchronized with initial Small Cell configuration with a Get
Parameter Values action (Sync Operational States Action) from the HDM application
interface.
....................................................................................................................................................................................................................................
BCR 2.2
8-5
401-387-065 Issue 4
July 2010
Operation
Small Cell addition
....................................................................................................................................................................................................................................
Procedure to synchronize the HDM database
The Small Cell automatically reaches HDM when it is powered on and downloads the
configuration file. It gets activated on the HDM. The following procedure describes how
to perform the Get Parameter Values action from the HDM.
...................................................................................................................................................................................................
After registration of the Small Cell, select the Small Cell from the HDM window, click on
the managebutton.
...................................................................................................................................................................................................
Synchronize the HDM database with the Small Cell configuration with a Get Parameter
Values action (Sync Operational States Action) from the HDM application interface.
....................................................................................................................................................................................................................................
BCR 2.2
8-6
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................

Purpose
This topic provides the use case to check the Small Cell parameter values.
Small Cell parameters
The following Small Cell parameters are checked:
BSR.ACL
BSR.ACLguest
BSR.bsrProfileID
BSR.latitude
BSR.longitude
DeviceInfo.(ManufacturerOUI/ProductClass/ModelName/SerialNumber)
Lcell.laLAC
Lcell.saSAC
Latitude and longitude are defined by the following components:
.degrees
.minutes
.seconds
.hemisphere
Procedure from HDM and WMS
Steps to check the Small Cell parameter values from the HDM are as follows:
...................................................................................................................................................................................................
From the main window select the Small Cell, click on the manage button.
...................................................................................................................................................................................................
In the Queued functions area select the function Get Parameter Values, Queue it
and specify the parameter you want to display.
...................................................................................................................................................................................................
Get all the Small Cell parameters from the HDM.

...................................................................................................................................................................................................
Another way to get the Lcell.saSAC parameter is to use a WICL script from the WMS.
FemtoNetwork <id> Femto <id> get serviceAreaCode
Where FemtoNetwork <id> and Femto <id> are the identifiers of the Small Cell
network and the Small Cell on WMS. These identifiers are determined when the Small
Cell network and the Small Cell are created by the workorder.
....................................................................................................................................................................................................................................
BCR 2.2
8-7
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................
For example, you can create a script file called script_file containing the following
command:
FemtoNetwork 1 Femto 7 get serviceAreaCode.
...................................................................................................................................................................................................
Download the script file to directory /opt/nortel/data/cmXML on WMS for Small Cell
using FTP and specifying the appropriate user name and password.
...................................................................................................................................................................................................
Run the following command on the WMS server:

/opt/nortel/shell/wicl/wiclsh -u administrator -p adminpass -f /
opt/nortel/data/cmXML/<fileName>
Where fileName is the name of the script file.

Example:
/opt/nortel/shell/wicl/wiclsh -u administrator -p adminpass -f /
opt/nortel/data/cmXML/script_file
Result:The value of the parameter is returned. It is of the following format:
--------------------------------------------------------Starting
Wireless Internet
Command
Language
--------------------------------------------------------Script mode launched

Wireless Internet Command Language (WICL)
3
The value 3 shown in the output is the value of the Lcell.saSAC parameter for Small Cell
7 in Small Cell network 1.
Procedure from WMS only
The parameter values can all be seen in WMS with :

>> /opt/nortel/shell/wicl/wiclsh -u administrator -p adminpass -c "Small Cell Network 1
Small Cell 101014 dis"
The results for the specified Small Cell are:
Starting Wireless Internet Command Language
Non interactive command mode launched
Wireless Internet Command Language (WICL)
....................................................................................................................................................................................................................................
BCR 2.2
8-8
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................
areaIdentityGA
point
bsrId
310
clusterId
Cluster/UMAINSERV1
fddCellIdList
UNSET
femtoACLlist
femtoACLlistGuest
262060000000419,262060000000420,
262060000000626,262060000000621
femtoClusterId
UNSET
gsmCellIdList
Small Cell Cluster/54
hnmDeviceGUID
UNSET
ipsecRouterIPAddr
11
latitude
initial-ipsecrouter.test.alcatel-lucent.com
locationAreaCode
51.5658
locationAreaCode1
432
locationAreaCode2
UNSET
serviceAreaCode3
UNSET
uncertaintyRadius
UNSET
userSpecificInfo
200
zCoordinate
UNSET
0
....................................................................................................................................................................................................................................
BCR 2.2
8-9
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................

Purpose
This topic describes how to modify the Small Cell parameters values.
Small Cell parameters
The following Small Cell parameters can be modified:
BSR.ACL
BSR.ACLguest
BSR.latitude
BSR.longitude
Lcell.laLAC
Lcell.saSAC
Latitude and longitude are structures having the following components:
Degrees
Minutes
Seconds
Hemisphere
Procedure to modify the Small Cell parameters
Prerequisites:
The WMS for Small Cell is pre-provisioned with applicable bsrProfiles, macro data
for 3G and 2G and locations.
New values are available.
Procedure to modify the Small Cell parameters from the IT operator system
...................................................................................................................................................................................................
Generate XML work order with the new value for a Small Cell parameters. If the value
needs to be auto-calculated by WMS for Small Cell, it must be set to unset in the work
order to be imported in the WMS for Small Cell.
...................................................................................................................................................................................................
Check the consistency of the work orders using WPS

...................................................................................................................................................................................................
With previous steps, WMS for Small Cell is updated with new values, but impacted Small
Cell needs to be re-configured with new configuration by re-building a new Bulk CM file
and imported it into affected Small Cell. Define the policy in HDM to launch rebuildCM
action on impacted Small Cells. This policy will trigger download of bulk CM file.
....................................................................................................................................................................................................................................
BCR 2.2
8-10
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................
Procedure to modify the Small Cell parameters from the HDM

...................................................................................................................................................................................................
Select the Small Cell from the main window.

...................................................................................................................................................................................................
Click on the manage button, and lock the device.

...................................................................................................................................................................................................
In the Queued Functions areas, use the function set parameter and specify the
parameter and its new value.
...................................................................................................................................................................................................
Click on the manage button, and unlock the device.

...................................................................................................................................................................................................
End of steps.
....................................................................................................................................................................................................................................
BCR 2.2
8-11
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................

Purpose
This topic describes how to modify the Small Cell profile parameter values.
Small Cell profile parameter modification
Prerequisites:
The WMS for Small Cell is pre-provisioned with applicable Small Cell profiles, with
macro data for 3G and 2G and locations.
The profiles are updated with new profile data or templates for new profile are
available in the WMS for Small Cell.
bsrProfileID is populated for each profile and each Small Cell data set, and its value is
unique per Profile.
Procedure to modify the Small Cell profile parameter
The steps of the procedure are as follows:

...................................................................................................................................................................................................
Generate
CM XML work order containing the new bsrProfile
CM XML work order with the assignation of the new profile to the Small Cell
...................................................................................................................................................................................................
Check consistency of the work order using WPS.

...................................................................................................................................................................................................
Import CM XML work order for new profile in the WMS for Small Cell.
...................................................................................................................................................................................................
Finally, import Small Cell specific CM XML work order, with the assignation of new
profile.
...................................................................................................................................................................................................
With previous steps, WMS for Small Cell data base is updated with new values, but the
impacted Small Cell needs to be re-configured with new configuration by re-building a
new CM file and importing it into affected Small Cells.
...................................................................................................................................................................................................
From the HDM, launch using the button enable or schedule the policy rebuildCM to
trigger a CM file creation action and download it on impacted Small Cell.
....................................................................................................................................................................................................................................
BCR 2.2
8-12
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................
The policy ensuring that a new CM file is built for each Small Cell is defined as follows:
Enable device filtering using filter Find device by bsrProfileId, that is the filter for
Small Cells running on previous bsrProfile version.
Select the action: Trigger CM File Creation Action, and then Create the policy using
the relevant button.
....................................................................................................................................................................................................................................
BCR 2.2
8-13
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................

Prerequisite
Legal requisition provides the facility to record and store information on the location of
the UE within the Small Cell network.
To activate the legal requisition function
Set the parameter activateLegalRequisition to:
callBased, for reporting the call events

sMSBased, for reporting the SMS events
callAndSmsBased, for reporting SMS and call events
To deactivate the legal requisition function
To deactivate the function, set the parameter activateLegalRequisition to off.

Being a parameter of the CM bulkfile, use the WMS to set the parameter
activateLegalRequisition accordingly.
....................................................................................................................................................................................................................................
BCR 2.2
8-14
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................

Purpose
This topic provides the way to view and update the Access Control List (ACL).
Customer system
The end-user views and updates the ACL of their Small Cell by accessing a customer
system through a well known URL, such as https://www.customercenter.com. Using this
web access to the customer system, the end-user can modify the ACL for his Small Cell
and allow different IMSIs access to their Small Cell.
Types of ACL
For charging purposes, there are two categories of end-users:
The end-user who owns the Small Cell and their family members.
All other users, that is, visitors or guests.
The ACL list consists of two separate lists:
ACL applies to the user category, charged at the Small Cell zone rate.
ACLguest applies to all other users, charged at the regular network tariff.
Important! These lists can support up to 32 entries. However the total number of
entries in both lists cannot be greater than 32. Therefore the network operator must
not provision more that 32 entries in total.
Profile
The network operator system has a profile for each subscriber with a predefined user
name and password used for the login. The user name and password ensure that the
corresponding Small Cell is updated. Up to 32 IMSIs can be added to the ACL of a Small
Cell. The customer system updates the HDM via a web-based Application Programming
Interface (API). This web-API, which is a part of the HDM, provides a well-known URL.
It includes all required parameters which are used by the external customer system. The
full list of the IMSIs is sent to the Small Cell each time an update is performed. The ACL
is stored in the customer system database.
Scope
Small Cell network level.

Procedure to display the ACL list
This procedure describes how to display the content of the ACL list from the HDM.
...................................................................................................................................................................................................
From the window displaying the managed Small Cell devices, select the Small Cell you
want the ACL list to be displayed.
....................................................................................................................................................................................................................................
BCR 2.2
8-15
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Select the Get Parameter Value command from this window.

...................................................................................................................................................................................................
Select the parameter femtoACLlist or femtoACLlistGuest according to the list to be

displayed.
...................................................................................................................................................................................................
Queue the command and launch it.

...................................................................................................................................................................................................
End of steps.
Modification of the ACL list from the IT customer center
This first procedure allows to modify the ACL list keeping the synchronization with the
customer system.
Prerequisites
The following are required:
The end-user must have access to a web based customer system.

The ACL list consists of two components, the ACL for the owner, and the ACLguest
for guests.
The IMSI of the owner is stored at the first location in the ACL (owner) list. The
end-user cannot remove this first entry from the list. The parameter femtoACLenable
must be set to true.
The size of both combined ACL lists does not exceed 32 IMSIs. The IMSI number is
composed of 12-15 digits, and is extracted from the MSISDN supplied by the
end-user.
The customer system implements other policies, such as barring pre-paid SIMs, or
barring mobiles if these ones have not roaming agreement..
The customer system ensures that each ACL is formatted correctly.
Actors
Role
Actor
Access to actor
Primary actor
End-user/customer
Application Programming
Interface (API) via https
Secondary actor
None
N/A
....................................................................................................................................................................................................................................
BCR 2.2
8-16
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................
Procedure
The steps of the main procedure are as follows:

...................................................................................................................................................................................................
The end-user accesses the customer system, specifying a user name and password.
...................................................................................................................................................................................................
The end-user updates the ACL, by adding or removing MSISDNs, using the customer
system.
...................................................................................................................................................................................................
The customer system converts the MSISDNs into IMSIs and exports the updated lists
using a web service call on the HDM URL.
...................................................................................................................................................................................................
The HDM updates the userTag information of the subscriber. This allows the ACLs to
persist after a factory reset of the Small Cell.
...................................................................................................................................................................................................
The HDM updates the Small Cell with the latest modified ACLs using the TR-069 Set
Parameter Value command.
...................................................................................................................................................................................................
The Small Cell triggers an update of the ACLs towards the BSG. The Small Cell discards
any IMSIs in excess of the 32 IMSI limit.
...................................................................................................................................................................................................
The ACLs of the HDM, the Small Cell and the BSG are synchronized.
...................................................................................................................................................................................................
The customer system is the master. In case of any link interruptions towards the HDM or
the Small Cell, or if an outage of these NEs occurs (for example, powering off of the
Small Cell), the customer system periodically triggers an update of the ACLs towards the
HDM, Small Cell, and BSG until all NEs are in sync. The Small Cell-BSG trigger may
occur asynchronously.
The customer system is responsible for polling the HDM for operation status.
Procedure results
Possible results of the procedure:

End condition
Description
Success
Customer system, HDM, Small Cell and BSG are updated with
new ACLs. IMSIs are added to, or removed from, the ACLs of
the customer system, HDM, Small Cell and BSG.
Failure
Customer system, HDM, Small Cell and BSG are not updated
with the latest ACLs.
....................................................................................................................................................................................................................................
BCR 2.2
8-17
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................
Modification of the ACL list from the HDM GUI
The ACL list can be modified from the HDM GUI when the operator requests a refresh of
the existing ACL and no MSISDN changes are necessary. This may happen when the
subscriber friends phone cannot be connected to the Small Cell, or in the case of a
factory reset.
The procedure is the one which describes how to modify the parameters of a Small Cell,
since the related parameter is defined as RW on the Small Cell interface. The device must
be locked before the modification.
However, the modification of the ACL content, from the HDM is highly undesirable since
it would lead to loss of synchronization with the customer system.
Failure description
Failure
Description
Failure causes while retrieving all MSISDNs

from the ACLs
Other exceptions generated by the application
Failure causes while adding a new list of

MSISDNs to the ACLs
The new IMSI list contains a value that

exceeds 15 characters
The new Small Cell ACL list is empty
The modified Small Cell ACL lists exceed

32 MSISDNs (An alarm will be logged if
the Small Cell discards guests in excess of
32 IMSIs total in the combined ACL and
ACLguest lists)
Other exceptions generated by the

application
userTag update fails
The customer system must handle overall

synchronization of updates to the userTag and
cache data. For example, the customer system
could be designed to cease the overall
operation based on a failure of the userTag
update; this would involve not attempting to
lock the device to apply the set of parameter
values (to HDM and on towards the Small
Cell), and instead sending a failure message to
the end subscriber.
Small Cell cannot connect to BSG to

propagate ACL update
In this case, the Small Cell periodically retries

until BSG is successfully updated. It is
possible that the BSG may be out of
synchronization with other network elements.
No specific management information currently
correlates this status.
....................................................................................................................................................................................................................................
BCR 2.2
8-18
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................

Purpose
This topic describes how to disable (or enable) a Small Cell. It does not affect the IMSI of
the user's phone, so calls can still be made using the macro network.
Policies and actions
Disabling a Small Cell prevents the Small Cell from executing policies and actions, and
from radiating, but does not remove it from the network element databases. The
parameter BSR.administrativeState is used for that purpose.
The BSR.administrativeState attribute
The BSR.administrativeState attribute is preserved through a power cycle. If the HDM

device state for the Small Cell in question, is set to disabled, then no further policies or
actions are executed on the device. Thus, any policy or action from the WMS for Small
Cell to deliver a new bulk cm (that might set BSR.administrativeState to unlocked) is
ignored. If the end user invokes a factory reset, then any HDM database requests are also
ignored.
Prerequisites
The Small Cell to be enabled or disabled is displayed in the Devices tab of HDM.
Otherwise follow the Small Cell Selection procedure to display it : Small Cell selection
(p. 8-2)
Procedure
...................................................................................................................................................................................................
Using the HDM GUI, set the BSR.administrativeState attribute to Locked.

...................................................................................................................................................................................................
Select the check box corresponding to the target Small Cell.

...................................................................................................................................................................................................
Click on the Enable button to enable a disabled Small Cell.

Click on the Disable button to disable an enabled Small Cell.
The Small Cell status is displayed in the Enabled column.
On the diagram, the Small Cell 2 is selected and can be toggled from one status to the
other.
....................................................................................................................................................................................................................................
BCR 2.2
8-19
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Using the HDM GUI, set the BSR.administrativeState attribute to Unlocked.
....................................................................................................................................................................................................................................
BCR 2.2
8-20
401-387-065 Issue 4
July 2010
Operation
Small Cell deletion
....................................................................................................................................................................................................................................
Small Cell deletion

Purpose
This topic describes how to delete a Small Cell.

Small Cell cluster
The procedure describes how to remove a Small Cell from the Small Cell Cluster.
This includes deleting and removing information about the Small Cell in the AAA, the
HDM, and in the WMS for Small Cell .
Procedure

...................................................................................................................................................................................................
Disable the Small Cell.

...................................................................................................................................................................................................
2
If...
Then...
You wish to delete the

Small Cell permanently
Remove provisioning data for the Small Cell from the AAA server by
deleting the profile for the Small Cell. Small Cell profiles are stored
in the Femto.csv file, one line per Small Cell.
Delete the profile by editing the Femto.csv file and removing the line
for the Small Cell you wish to delete.
Important! If you delete a Small Cell from the AAA server, you will
not be able to restore it unless you have an up to date backup of the
AAA database. Ensure that you have an up to date backup of the
AAA database before deleting any Small Cells from the AAA server.
You wish to retain the

Small Cell in the AAA
server so that you can
recreate it
Skip this step.
...................................................................................................................................................................................................
Remove provisioning data for the Small Cell from WMS for Small Cell . Do this using a
work order.
The current structure of the cluster must be available either as a workspace or through a
snapshot taken from the WMS for Small Cell and imported to WIPS or the IT system of
the operator. Create a work order to delete the Small Cell in this structure.
...................................................................................................................................................................................................
CM createSession <Delete_VAP> -file <prueba_vdf.xwo>
....................................................................................................................................................................................................................................
BCR 2.2
8-21
401-387-065 Issue 4
July 2010
Operation
Small Cell deletion
....................................................................................................................................................................................................................................
CM terminateSession <Delete_VAP>
...................................................................................................................................................................................................
Download the script file to directory /opt/nortel/data/cmXML on WMS for Small Cell
using FTP and specifying the appropriate user name and password.
...................................................................................................................................................................................................
Schedule a job in the crontab or jobscheduler to run the script.

...................................................................................................................................................................................................
Remove the Small Cell from the HDM, by invoking the appropriate Web Service method
call on HDM.
...................................................................................................................................................................................................
End of steps.
....................................................................................................................................................................................................................................
BCR 2.2
8-22
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................

Overview
This topic describes the reboot action from the HDM.

Prerequisites
The Small Cell must be previously registered and managed by the HDM.
Procedure
...................................................................................................................................................................................................
From the HDM window select the Small Cell you want to activate.
...................................................................................................................................................................................................
Lock the device by clicking the lock this device button.

...................................................................................................................................................................................................
In the Queued Functions area, select the Queue Action button and queue the actionFemto
Activation Action .
...................................................................................................................................................................................................
Unlock the device by clicking the lock this device button.

...................................................................................................................................................................................................
End of steps.
....................................................................................................................................................................................................................................
BCR 2.2
8-23
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................

Overview
This topic gives the procedure to change the postal address of a Small Cell.
Introduction
When a end user changes his postal address, the Small Cell must be re-allocated.
The end user is supposed to move in a new geographical location within the operators
country network.
The operator must delete the Small Cell from the databases in the provisioning systems of
the network, and recreate it in the database with new location data.
Prerequisites
The following are required:
The Small Cell is already subscribed in the network.
The Small Cell is known to be functioning, fault free, at the current address of the end
user.
Procedure

1. After the end user powers down the Small Cell in agreement with the operators
customer care center, the Small Cell stops RF transmission at the current address.
2. The customer care centre disables the service for the current location. The operator
provisions the system with the new address location details and the planned restart
date.
3. The operator removes provisioning data for the Small Cell from the WMS for Small
Cell. This is done using a work order. The current structure of the cluster must be
available either as a work space or through a snapshot taken from the WMS for Small
Cell and imported to WPS or the IT network system of the operator. A work order is
created to delete the Small Cell.
4. The operator removes the Small Cell from the HDM.
5. The operator recreates the Small Cell with the new location data in the WMS for
Small Cell (WMS for Small Cell and HDM for Small Cell ).
6. The end user plugs in the Small Cell in the new location, and powers it on.
7. The Small Cell initializes.
8. The WMS for Small Cell receives a registration request from the Small Cell at the
new location.
9. The Small Cell registers and authenticates.
10. End of steps.
....................................................................................................................................................................................................................................
BCR 2.2
8-24
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................

Prerequisites
To simplify network operations, Small Cell units of a group are configured using a
common set of parameters.
Parameter
Function
Access Mode:
Defines whether the Small Cell operates in

open access mode or in closed access mode
accessMode
Location:
latitude
longitude
Latitude gives the location of a place on Earth

north or south of the equator. Positive value
means a north orientation. Negative value
means a south orientation.
Longitude is the east-west geographic
coordinate. Positive value means a east
orientation. Negative value means a west
orientation.
Access Control list:
femtoACLlist
femtoACLlistGuest
Small Cell Cluster Identifier:

femtoClusterId
Mobitity LAC,RAC, SAC:
serviceAreaCode1, locationAreaCode1,
serviceAreaCode2,locationAreaCode2
serviceAreaCode3, locationAreaCode3
This specifies the list of IMSIs allowed to use

the Small Cell resources, within closed access
operation mode. It defines as a string with
comma-separated IMSI values.
Reference to its corresponding Small Cell
Cluster (BSG)
Location Area Code, Routing Area code,
Service Area Code
Alternate LAC/SAC values for billing
Emergency-call handling LAC3/SAC3

values
Individual attributes: some parameters are still defined individually per Small Cell,
mainly the serial number.
Small Cell groups is created using the WIPS, or the WMS for Small Cell . To modify an
existing group, the operator can choose between the WIPS, the WMS for Small Cell and
the HDM.
Small Cell group management using the WIPS
Small Cell groups can be created using the standard dialogs of WIPS. The operator can
also assign a Small Cell to groups by setting the parameter: femtoGroupId.
The CM-XML workorders created using WIPS are imported into WMS for Small Cell to
declare the Small Cell groups or to declare new Small Cell in an existing group.
....................................................................................................................................................................................................................................
BCR 2.2
8-25
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................
Figure 8-1 Small Cell group creation using WIPS
Small Cell group creation
Small Cell group creation workorders contain at least the following mandatory attributes
ipsecRouterIPAddr
femtoClusterId
userLabel
All other attributes are optional.

All Small Cell created with a femtoGroupId set to Small Cell Group/X will take the
values defined in the group X.
When a Small Cell group in created, auto-configuration is launched as if the group was a
single Small Cell. The auto-configuration is based on the longitude and the latitude
defined in the group. All grouped Small Cells will shared the same locationAreaCode.
This does not depend on the allocation algorithm.
To use LAC auto-configuration the parameter locationAreaCode must be left unset, and
the latitude and the longitude must be provisioned to avoid LAC collisions.
....................................................................................................................................................................................................................................
BCR 2.2
8-26
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................
Figure 8-2 Latitude and longitude provisioning

<workorders>
<workorder name="create_femtogroup">
<FemtoNetwork id="1" model="OAM" version="OAM">
<FemtoGroup id="0" method="create">
<attributes>
<ipsecRouterIPAddr>23.43.55.3</ipsecRouterIPAddr>
<femtoClusterId> FemtoCluster/56</femtoClusterId>
<femtoACLlist>323232422674</femtoACLlist>
<femtoACLlistGuest>323232422674</femtoACLlistGuest>
<latitude>10.0000</latitude>
<locationAreaCode>2323</locationAreaCode>
<locationAreaCode1>23</locationAreaCode1>
<longitude>5.0000</longitude>
<routingAreaCode>21</routingAreaCode>
<serviceAreaCode>53</serviceAreaCode>
<serviceAreaCode1>533</serviceAreaCode1>
</attributes>
</FemtoGroup>
</FemtoNetwork>
</workorder>
</workorders>
The following workorder is used to create a Small Cell group.

Figure 8-3 Workorder to create a Small Cell group
<workorders>
<workorder name="create_groupedfemto">
<Femto id="0" method="create">
<femtoGroupId>FemtoGroup/0</femtoGroupId>
< serialNumber>352653665632</serialNumber>
</Femto>
</FemtoNetwork>
</workorder>
</workorders>
Small Cell group modification
To modify a group, use the command modify of WIPS, modify directly the workorder.
The changes are propagated to all Small Cell units in the Small Cell Small Cell group.
....................................................................................................................................................................................................................................
BCR 2.2
8-27
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................
Figure 8-4 Small Cell group modification workorder

<workorders>
<workorder name="modify_group">
<FemtoGroup id="0" method="modify">
<femtoACLlist>323232422674,334323428976, 444334478736</femtoACLlist>
</FemtoGroup>
</FemtoNetwork>
</workorder>
</workorders>
<workorders>
<workorder name="ungroup_femto">
<Femto id="1" model="OAM" version="OAM">
<Femto id="0" method="modify">
<femtoGroupId>
</unset>
</femtoGroupId>
</Femto>
</FemtoNetwork>
</workorder>
</workorders>
Small Cell group management using the WMS for Small Cell
In WMS, the user can perform the same operations like above (i.e. ungroup Small Cell,
group modification, grouped Small Cell creation, Small Cell group creation) by using
WICL or Session Manager. This could be achieved by importing WO to the system.
The user can also update Small Cell /Small Cell Group parameters using the ObjectEditor
GUI.
....................................................................................................................................................................................................................................
BCR 2.2
8-28
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................
Figure 8-5 Small Cell group update
Small Cell group management using the HDM
Neither Small Cell nor Small Cell groups can be created using the HDM, but existing
Small Cell units and Small Cell groups can be modified using the HDM GUI, or the
HDM North Bound Interface procedure to create a Small Cell group. As an example, the
ACLList for all Small Cells in a group can be modified by creating a simple policy that
applies the action Set ACL to the criteria template Find Small Cells by Small Cell
Group Id.
....................................................................................................................................................................................................................................
BCR 2.2
8-29
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................
Figure 8-6 Modification of the ACLList of a Small Cell group using HDM
Procedure to create a Small Cell group
This is the procedure to create a Small Cell group. The operator generates the XML
workorder either using WIPS or using a custom CM-XML workorder creation tool that
complies with the CM-XML specifications. The operator imports the created workorder
in the WMS.
...................................................................................................................................................................................................
A new Small Cell group is ordered.
....................................................................................................................................................................................................................................
BCR 2.2
8-30
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
The back-office gathers and transmits to the network provisioning team the following
information:
Geographical coordinates of the Small Cell group
The initial IMSI ACL list

The serial numbers of the Small Cell units
...................................................................................................................................................................................................
The network provisioning team creates:
A new Small Cell group

Fills in the ACL list attributes.
Creates all Small Cell units.

Sets the parameters: femtoGroupId, serial number, and individual attributes.
...................................................................................................................................................................................................
The operator loads the workorder in the WMS for Small Cell and configures the network.
...................................................................................................................................................................................................
The Small Cell units connect and register to the HDM/WMS to retrieve their provisioning
data.
...................................................................................................................................................................................................
The Small Cell units informed the HDM about their provisioning update. The operator
can modify their configuration if necessary.
Procedure to add a Small Cell in a group
This is the procedure to add a Small Cell to a Small Cell group.

...................................................................................................................................................................................................
A new Small Cell is ordered in an existing group.

...................................................................................................................................................................................................
The network provisioning team:
Creates the new Small Cell.

Sets the femtoGroupId.
Sets the serial number

Sets other individual attributes according to the network configuration.
...................................................................................................................................................................................................
The operator loads the workorder in the WMS for Small Cell and configures the network.
...................................................................................................................................................................................................
The new Small Cell connects and registers to the HDM/WMS to retrieve its provisioning
data.
....................................................................................................................................................................................................................................
BCR 2.2
8-31
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
The Small Cell informed the HDM about its provisioning update. The operator can
modify the configuration if necessary.
Procedure to modify Small Cell group attribute
This is the procedure to modify the Small Cell group attribute in case of network
modification.
...................................................................................................................................................................................................
The Small Cell group owner needs to modify an attribute at group level, for example the
ACLList.
...................................................................................................................................................................................................
The operator connects to the HDM, creates a policy to activate the criteria template
findFemtosByGroupId and applies action set ACL value using the new ACL value.
...................................................................................................................................................................................................
The Small Cells connect to HDM one after another and take into account the new value.
....................................................................................................................................................................................................................................
BCR 2.2
8-32
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................

Overview
This topic describes how to synchronize the operational states of the Small Cell in the
HDM database.
The operational parameters are listed below:
Bsr.OpState
ItfBGWY.OpState
ItfBPG.OpState
ItfBVG.OpState
IuCSPrime.OpState
ItfGrPrime.OpState
Lcell.opState
Radio.OpState
SCTPAssoc.OpState
Procedure
The synchronization is performed using the HDM GUI.

...................................................................................................................................................................................................
Select the Small Cell and click on the managebutton.

...................................................................................................................................................................................................
In the Queued Functions area select Queue Action and select the action Sync
Operational States.
...................................................................................................................................................................................................
Launch the action.

...................................................................................................................................................................................................
End of steps.
....................................................................................................................................................................................................................................
BCR 2.2
8-33
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................

Small Cell parameters:
areaIdentityGA
bsrId
clusterId
fddCellIdList
femtoACLlist
femtoACLlistGuest
femtoClusterId
gsmCellIdList
hnmDeviceGUID
ipsecRouterIPAddr
latitude
locationAreaCode
locationAreaCode1
locationAreaCode2
locationAreaCode3
longitude
notAllowedFddCellIdList
notAllowedGsmCellIdList
profile
routingAreaCode
serialNumber
serviceAreaCode
serviceAreaCode1
serviceAreaCode2
serviceAreaCode3
uncertaintyRadius
userSpecificInfo
zCoordinate
....................................................................................................................................................................................................................................
BCR 2.2
8-34
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................

Overview
This topic describes how to upgrade the Small Cell software.

Prerequisities
Software upgrade is done through a Software Description File (SDF). This file is created
by the WMS.
The software load is first downloaded to the directory:
/opt/nortel/data/utran/software/femto/ALU. The target release then must be changed in the
SDF Download action with the new load name.
The HDM must be pre-configured with a SDF Download action.
HDM must also be pre-configured with a SDF download policy. The service tag value
must be sdfDownload and failure exit tag must be sdfDownloadFailed. When the
WMS for Small Cell sets the service tag and launches a Change Report (CR), the
download of the SDF starts automatically for the device.
Procedure
...................................................................................................................................................................................................
Select the Small Cell to upgrade.

...................................................................................................................................................................................................
Lock the Small Cell.

...................................................................................................................................................................................................
Trigger SDF File Creation action.

...................................................................................................................................................................................................
Unlock the Small Cell.

...................................................................................................................................................................................................
End of steps.
....................................................................................................................................................................................................................................
BCR 2.2
8-35
401-387-065 Issue 4
July 2010
Operation
....................................................................................................................................................................................................................................

Prerequisite
Some Mobile Operators have no strict SLAs with ISPs or DSL operators. This means that
Small Cell has no bandwidth guarantee and QoS for backhaul is not under control of the
Mobile provider. The Enhanced Transport CAC function shall verify if enough bandwidth
resources are available for a new incoming call. Within this option, the Transport CAC
will trigger an active call redirection instead of rejection.
The Transport CAC is controlled by the MIM attribute BSR: enableTransportCAC.
The Active Call Re-direction function due to Enhanced Transport CAC is manageable
with the MIM attribute BSR: aCRtransportCACEnable.
Active call re-direction due to lack of backhaul resources is invoked if BSR:
enableTransportCAC is set to true and if BSR: aCRtransportCACEnable is set to true.
Procedure
To set the Small Cell CAC activation parameter

Set the parameter aCRtransportCACEnable to:
true, to support the Enhanced Transport CAC function
false otherwise
Being a parameter of the CM bulk file, use the WMS to set the parameter
aCRtransportCACEnable accordingly.
....................................................................................................................................................................................................................................
BCR 2.2
8-36
401-387-065 Issue 4
July 2010
Operation
Small Cell access
....................................................................................................................................................................................................................................
Small Cell access

Functional description
Open access Small Cells extend the public coverage of the UMTS macro network. The
ACL check is disabled in Small Cells operating in open access mode. Every user, who has
access to the PLMN, can also access open access Small Cells.
In a cluster, some Small Cells will have open access while others in the same cluster will
have closed access using the access control list (ACL). This feature provides the operators
the means to make use of a Small Cell cell for hot spot coverage and also for offering
public access similar to that of the macro network, without having to grant access to all
Small Cells.
An open access Small Cell
Does not perform access control
Registers UEs upon receipt of the IMSI from the Core Network
Procedure
To set the access mode parameter:

Set the parameter accessMode to:
closedAccess, to operate in closed access mode
fopenAccess, to operate in open access mode
Being a parameter of the CM bulk file, use the WMS to set the parameter accessMode
accordingly.
....................................................................................................................................................................................................................................
BCR 2.2
8-37
401-387-065 Issue 4
July 2010
Operation
Small Cell access
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
8-38
401-387-065 Issue 4
July 2010
Part IV: Fault management
Overview
Purpose
This part describes the fault management process.

Contents
Chapter 9, Principles of alarm management
Chapter 10, Small Cell alarms
9-1
10-1
...................................................................................................................................................................................................................................
BCR 2.2
IV-1
401-387-065 Issue 4
July 2010
Fault management
Overview
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
IV-2
401-387-065 Issue 4
July 2010
9rinciples of alarm
P
management
Overview
Purpose
This chapter provides general information about the management of the faults and the
subsequent alarms generated by the Alcatel-Lucent Small Cell. The chapter also describes
the structure of the Small Cell alarm sheet.
Contents
Fault Management
9-2
Small Cells real time management
9-5
Alarm display
9-6
9-7
...................................................................................................................................................................................................................................
BCR 2.2
9-1
401-387-065 Issue 4
July 2010
Fault Management
....................................................................................................................................................................................................................................
Fault Management
Introduction
The Motive Home Device Manager (HDM), component of the Small Cell Management
System (WMS for Small Cell), is the centralized management system for the Small Cell.
The Small Cell supports the following functions:
Errors detection related to the Small Cell application software and/or hardware
Local recovery action for the detected fault within the Small Cell
Alarm clearance, after the fault has disappeared, according to the nature of the alarm
Faults reports to the HDM. As a standard,the Small Cell does not inform in real time
the Home Device Manager (HDM) but records the faults in a log file. The Small Cell
reports the count of alarms to the HDM on demand.
Real time monitoring for a limited number of flagged Small Cells, deployed for
example as public cells to complement the macro network.
Real time monitoring means that:
The Small Cell reports real time state changes.
The operator knows if a Small Cell is up and running or out of service.
Alarm clearance, after the fault has disappeared, according to the nature of the alarm.
Content of the historical log file
All the faults occurring in the Small Cell are recorded in an historical log file. A fault is
generated following one or more errors.
Faults are classified in two categories:
Hardware faults
Software faults
The Small Cell manages the errors and determines whether the error is a fault and records
the alarm.
For a non real time managed Small Cell , only the number of critical alarms currently
active in the Small Cell, and the number of critical alarms that have been raised since the
last information message, are sent to the HDM upon request.
Alarm severity
Alarms can have the following degree of severity:

Severity
Description
Critical
A service-affecting condition has occurred and

requires an immediate corrective action.
This degree of severity is reported when a
fault has affected the service delivered to the
user.
....................................................................................................................................................................................................................................
BCR 2.2
9-2
401-387-065 Issue 4
July 2010
Fault Management
....................................................................................................................................................................................................................................
Severity
Description
Major
A service-affecting condition has occurred and

requires an urgent corrective action.
This degree of severity is reported, when a
fault has reduced rather than removed the
capability of the managed object.
Minor
A non-service-affecting fault has occurred and

a corrective action should be taken to prevent
more serious faults.
This degree of severity is reported, when the
fault is not currently degrading the capacity of
the managed object. Minor faults do not
degrade the capacity of the managed object,
either because redundant capacity is available
or the fault does not affect user services.
Warning
A potential or impending service-affecting

fault has been detected, before any significant
effects.
The problem should be corrected to prevent it
becoming service-affecting.
Cleared
The fault has disappeared.

Such degree of severity is valid for faults
which are automatically cleared when the fault
condition does not exist anymore.
Nature of the alarm
The nature of the alarm can be as follows:

Nature
Description
ADAC
Alarms of this type are Automatically

Detected and Automatically Cleared (ADAC).
Alarms that belong to this category will
automatically be removed from the active list
when the fault is corrected.
Example:
The alarm is automatically cleared when the
software process has successfully restarted.
....................................................................................................................................................................................................................................
BCR 2.2
9-3
401-387-065 Issue 4
July 2010
Fault Management
....................................................................................................................................................................................................................................
Nature
Description
ADMC
Alarms of this type are Automatically

Detected but must be Manually Cleared
(ADMC).
Alarms that belong to this category must be
removed manually from the active list when
the fault is corrected.
Example:
After the software process has successfully
restarted the alarm must be manually reset.
The Small Cell only manages alarms of nature: ADAC.
....................................................................................................................................................................................................................................
BCR 2.2
9-4
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................

Real time alarm capability
For capacity reason, not more than 1% of Small Cells should be configured to report
alarms in real time at the same time. From a latency point of view, 5 minutes between
Small Cell alarm generation and alarm display on WMS for Small Cell is acceptable.
The operator activates the alarm flow from the HDM GUI, for a specific Small Cell or a
subset of Small Cells. The configured Small Cell can therefore send the alarm
information to the existing WMS for analysis by a Small Cell toolset.
The fault management parameters are:
faultNotificationEnabled to switch on the real time alarm notification when set to true.
faultResyncRequired. If set to true this parameter triggers the resynchronisation of the
activeFaultList between Small Cell and HDM.
activeFaultList used to buffer the active critical faults. The real time alarm is sent via
attribute value change notification of the activeFaultList , which includes a sequence
of active critical alarms.
Only alarms with severity value criticalraised or cleared by the Small Cell are sent to
HDM in real time if real time alarm reporting is enabled on that Small Cell. Those alarms
are added into the active fault list first before reporting to the HDM.
Real time Small Cell status
To know Small Cell real time status, it is proposed that the Small Cell GateWay
heartbeats the Small Cell, and when the heartbeat fails the Small Cell GateWay raises a
critical alarm. When the heartbeat returns the alarm needs to be cleared.
When the failure of a monitored Small Cell is detected and the number of failed Small
Cells is less than or equal to a configurable threshold, the Small Cell GateWay raises a
separate instance of a bsrOutOfService alarm containing the Small Cell's identity.
When the failure of a monitored Small Cell is detected and the number of failed Small
Cells is greater than the threshold, the Small Cell GateWay marks the Small Cell as failed
but does not raise the bsrOutOfServicealarm. Instead when the threshold is crossed the
Small Cell GateWay raises a massBsrOutOfService alarm to indicate a more widespread
failure. This contains no identification of the individual Small Cells .
....................................................................................................................................................................................................................................
BCR 2.2
9-5
401-387-065 Issue 4
July 2010
Alarm display
....................................................................................................................................................................................................................................
Alarm display
HDM alarm display
The HDM has no specific feature to display the alarms of a Small Cell. Per default, to
optimize the communication between the HDM and the Small Cell, there is no real time
alarm reporting. The alarms are stored in a log file in the Small Cell.
The alarm information consists of:
The number of critical alarms currently active

The number of critical alarms that have been raised since the last information message
WMS alarm display
Alarms are reported on the Small Cell Cluster icon of the WMS application.
The WMS therefore supports:
The 9 alarm rule-set (such as inhibit, send SMS, send email, or change severity)
The trouble ticketing interface

The alarm browser
The managed and un-managed alarm stream
The various resources browsers (such as topological, grid and matrix)
The Historical Fault Browser
Optionally, the WMS for Small Cell provides a mechanism to automatically clear the
Small Cell, when the real time alarm flow has been switched off by the operator using the
HDM interface.
....................................................................................................................................................................................................................................
BCR 2.2
9-6
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................

Alarm details are displayed through the Alcatel-Lucent 9353 Small Cell Management
System (WMS for Small Cell). The WMS for Small Cell options are described in
Alcatel-Lucent 9353 Management System for Small Cell - User Guide (NN-20500-208).
The name of the alarm is displayed in the field of the WMS for Small Cell window.
An alarm sheet provides a short explanation of the alarm with the following information:
Purpose specifying the objective of the sheet
Description explaining the meaning of the alarm

Severity level indicating the urgency of the action (warning, minor, major or critical)
Classification of the problem indicating the alarm category in the Small Cell object
model
Probable cause specifying the reason of the alarm
Event type providing a technical classification
Kind of actions performed consequently to the fault (ADAC in the present case)
Fault Consequence describing the impacts on the Small Cell
Corrective procedure to list the actions to suppress the failure
....................................................................................................................................................................................................................................
BCR 2.2
9-7
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
9-8
401-387-065 Issue 4
July 2010
10
Small Cell alarms

10
Overview
Purpose
This chapter provides detailed information about the alarms. They are sorted into
categories or classes.
Contents
Class BSR Alarms
10-5
Overview
10-5
10-6
resetFailed alarm
10-7
10-8
10-9
10-10
10-11
lmcFailure alarm
10-12
10-13
10-14
10-15
10-16
10-17
10-18
selfoptNotRun alarm
10-19
10-20
10-21
10-22
10-23
10-24
...................................................................................................................................................................................................................................
BCR 2.2
10-1
401-387-065 Issue 4
July 2010
Small Cell alarms
Overview
....................................................................................................................................................................................................................................
10-25
10-26
10-27
10-28
queueOverload alarm
10-29
10-30
Class LCell Alarms
10-31
Overview
10-31
10-32
uLCongestion alarm
10-33
dLCongestion alarm
10-34
10-35
10-36
10-37
10-38
rSSImeasStop alarm
10-39
tSSImeasStop alarm
10-40
rACHmeasStop alarm
10-41
10-42
10-43
10-44
10-45
10-46
10-47
10-48
10-49
10-50
10-51
10-52
10-53
10-54
10-55
10-56
10-57
Class SDM Alarms
10-58
....................................................................................................................................................................................................................................
BCR 2.2
10-2
401-387-065 Issue 4
July 2010
Small Cell alarms
Overview
....................................................................................................................................................................................................................................
Overview
10-58
10-59
10-60
10-61
10-62
10-63
10-64
Overview
10-64
10-65
10-66
Class PM Alarms
10-67
Overview
10-67
10-68
10-69
10-70
Overview
10-70
10-71
Class ItfBVG Alarms
10-72
Overview
10-72
10-73
10-74
Overview
10-74
10-75
Class ItfBPG Alarms
10-76
Overview
10-76
10-77
10-78
Overview
10-78
10-79
Class Radio Alarms
10-80
Overview
10-80
10-81
txMalfunction alarm
10-82
rxMalfunction alarm
10-83
10-84
....................................................................................................................................................................................................................................
BCR 2.2
10-3
401-387-065 Issue 4
July 2010
Small Cell alarms
Overview
....................................................................................................................................................................................................................................
10-85
10-86
Class CECTL Alarms
10-87
Overview
10-87
10-88
10-89
10-90
Overview
10-90
10-91
10-92
10-93
gsmATCmdFail alarm
10-94
....................................................................................................................................................................................................................................
BCR 2.2
10-4
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
Overview
....................................................................................................................................................................................................................................
Class BSR Alarms

Overview
Purpose
This section provides information about the BSR alarms.
....................................................................................................................................................................................................................................
BCR 2.2
10-5
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "securityViolation" alarm.

Description
The Small Cell Operation, Administration and Maintenance (OAM) module detects an
un-authorised interface access of
The operator needs to investigate the security issue.
Severity
critical
Problem classification
BSR
Probable cause
unauthorizedAccessAttempt
Event type
securityServiceOrMechanismViolation
Nature
ADAC
Fault consequence on the Small Cell
The Small Cell records the fault in the log. The fault will be cleared on the next reset.
Corrective procedure
Perform the following steps to clear the alarm:

...................................................................................................................................................................................................
This alarm is an ADAC alarm. It does not require operator's manual intervention.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-6
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
resetFailed alarm
....................................................................................................................................................................................................................................
resetFailed alarm
Purpose
This topic provides all informations about the "resetFailed" alarm.

Description
The reset action by the Small Cell has failed.

Severity
minor
BSR
Probable cause
unspecifiedReason
Event type
processingErrorAlarm
Nature
ADAC
The Small Cell records the fault in the log.


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-7
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "resetInitiated" alarm.

Description
The alarm is generated just before the Small Cell resets (the reset is delayed for a few
seconds). It contains the reset cause "manually initiated" or "autonomously initiated".
Severity
warning
BSR
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-8
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "resetCompleted" alarm.

Description
The alarm is generated when a reset has been successfully performed and when the Small
Cell is "stable" for a certain time after the reset.
Severity
warning
BSR
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-9
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "applicationInsane" alarm.

Description
The application software is not functioning properly. The alarm is raised for persistent
audit failures.
The fault will be cleared when audit no longer detects a problem.
Severity
critical
BSR
Probable cause
softwareProgramError
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-10
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "autoconfigfailure" alarm.

Description
The Small Cell auto-configuration has failed.

Severity
major
BSR
Probable cause
applicationSubsystemFailure
Event type
operationalViolation
Nature
ADAC
The Small Cell resets only if the alarm is raised during network listening.

...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-11
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
lmcFailure alarm
....................................................................................................................................................................................................................................
lmcFailure alarm
Purpose
This topic provides all informations about the "lmcFailure" alarm.

Description
The check of the Small Cell location and/or movement has failed.
The operator needs to be sure that the Small Cell is in correct location before overriding
it. He can use MIM parameters to determine the failed tests and may want to change the
various parameters to relax the criteria or disable the test.
Severity
critical
BSR
Probable cause
equipmentMalfunction
Event type
equipmentAlarm
Nature
ADAC
The Small Cell is disabled.


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-12
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "ipsecConfigurationAlarm" alarm.

Description
The Small Cell detects a SW-incompatibility on IPsec Router for the requested IPsec
configuration.
The operator could update the Ipsec router to support the second SA feature or disable the
feature on Small Cell (enableTwoSA=false).
Severity
minor
BSR
Probable cause
configurationOrCustomizationError
Event type
Nature
ADAC
The Small Cell records the fault in the log. The Small Cell continues with degraded
performance with only one child SA.

...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-13
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "creationOfSecondSAFailed" alarm.

Description
The creation of the second Child SA on the first IPsec tunnel has failed or the second
IPsec tunnel went down.
Severity
minor
BSR
Probable cause
Event type
Nature
ADAC
The Small Cell records the fault in the log. The Small Cell continues with degraded
performance with only one child SA.

...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-14
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "ipsecTunnelAlarm" alarm.

Description
The establishment of the second IPSec tunnel has failed or the second IPsec tunnel went
down.
The operator should check configuration of the second (high priority) tunnel and the
network or disable the two Ipsec tunnels feature (enableTwoIpsecTunnels=false).
Severity
critical
BSR
Probable cause
Event type
Nature
ADAC
The Small Cell is disabled and doesn't give user service.


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-15
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "invalidDatabaseDetected" alarm.

Description
The Small Cell detects the database as invalid due to a consistency error.
Severity
major
BSR
Probable cause
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-16
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "basebandReconfigfailed" alarm.

Description
The reconfiguration procedure of the baseband array has failed.

Severity
critical
BSR
Probable cause
Event type
Nature
ADAC
The Small Cell resets.


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-17
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "allReservedFemtoCellsInUse" alarm.

Description
The network listening has discovered that all reserved scrambling codes in the
neighbourhood of the Small Cell are used. This is due to insufficient reserved Physical
signaling Channel (PSC) for the deployment scenario.
The operator could increase number of reserved Small Cell PSCs.
Severity
minor
BSR
Probable cause
underlyingResourceUnavailable
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-18
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
selfoptNotRun alarm
....................................................................................................................................................................................................................................
selfoptNotRun alarm
Purpose
This topic provides all informations about the "selfoptNotRun" alarm.

Description
The self optimization process has not been run during the quiet allocated period, as active
calls are present.
Severity
minor
BSR
Probable cause
underlyingResourceUnavailable
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-19
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "bCHGuardTimeExpired" alarm.

Description
The Broadcast CHannel (BCH) Decode guard timer has expired.

Severity
minor
BSR
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-20
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "cellSearchGuardTimeExpired" alarm.

Description
The guard timer of the cell search function has expired.

Severity
minor
BSR
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-21
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "thresholdCriteriaNotMet" alarm.

Description
The threshold criteria for detection of cells has not been met and this has resulted in an
open search for more cells.
The operator could reconfigure threshold criteria MIM Parameters (macroCellRSCPthreshold, macroCellEcNoThreshold, RatioMacroCellbelowThreshold).
Severity
minor
BSR
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-22
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "detectedCollapsingLAI" alarm.

Description
The LAI value conflicts with another value already in use.

The operator should reconfigure the LAC on one of the conflicting (as per
additionalText).
Severity
critical
BSR
Probable cause
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-23
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "gsmBandNotSupported" alarm.

Description
The Small Cell hardware is not compatible with the gsm band configured.
The operator should configure the supported bands or set
gsmListenerPicoBasedEnabled=false.
Severity
critical
BSR
Probable cause
Event type
equipmentAlarm
Nature
ADAC
The Small Cell rejects the configuration.


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-24
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "gsmBCCHDecodeGuardTimerExpired"

alarm.
Description
The BCCH Decode guard timer has expired for 2G Network Listening (PicoChip based)
cells.
Severity
minor
BSR
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-25
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "gsmCellSearchGuardTimerExpired"

alarm.
Description
The Cell Search function guard timer has expired for 2G Network Listening (PicoChip
based) cells.
Severity
minor
BSR
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-26
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "gsmThresholdCriteriaNotMet" alarm.

Description
The threshold criteria for detection of gsm cells has not been met and this has resulted in
an open search for more cells.
The operator could change threshold criteria MIM Parameters.
Severity
minor
BSR
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-27
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "noMacroCellFound" alarm.

Description
There was no macro cell found during 2G/3G network listening.

The operator may need manually provision the Macro cell infor into the
Severity
critical
BSR
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-28
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
queueOverload alarm
....................................................................................................................................................................................................................................
queueOverload alarm
Purpose
This topic provides all informations about the "queueOverload" alarm.

Description
There was no free paging occasion found to schedule a paging record.

Severity
major
BSR
Probable cause
resourceAtOrNearingCapacity
Event type
qualityofServiceAlarm
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-29
401-387-065 Issue 4
July 2010
Small Cell alarms

Class BSR Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "systemOverload" alarm.

Description
The CPU and the memory are overloaded.

Severity
major
BSR
Probable cause
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-30
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
Overview
....................................................................................................................................................................................................................................
Class LCell Alarms

Overview
Purpose
This section provides information about the alarms related to the Small Cell Logical Cell
(LCell).
....................................................................................................................................................................................................................................
BCR 2.2
10-31
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "codeAllocationFailure" alarm.

Description
The channelisation code allocation has failed.

Severity
major
LCell
Probable cause
Event type
Nature
ADAC
The Small Cell resets during add cell failure.


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-32
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
uLCongestion alarm
....................................................................................................................................................................................................................................
uLCongestion alarm
Purpose
This topic provides all informations about the "uLCongestion" alarm.

Description
The alarm is raised when the condition for UpLink (UL) congestion has been reached.
The Small Cell starts the UL congestion control algorithm to clear the congestion.
Severity
major
LCell
Probable cause
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-33
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
dLCongestion alarm
....................................................................................................................................................................................................................................
dLCongestion alarm
Purpose
This topic provides all informations about the "dLCongestion" alarm.

Description
The alarm is raised when the condition for DownLink (DL) congestion has been reached.
The Small Cell starts the DL congestion control algorithm to clear the congestion.
Severity
major
LCell
Probable cause
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-34
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "rSSImeasInitFail" alarm.

Description
The initiation of the Received Signal Strengh Indicator (RSSI) measurement has failed.
Severity
major
LCell
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-35
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "tSSImeasInitFail" alarm.

Description
The initiation of the Transmitted Signal Strengh Indicator (TSSI) measurement has failed.
Severity
major
LCell
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-36
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "rACHmeasInitFail" alarm.

Description
The initiation of the Random Access CHannel (RACH) measurement has failed.
Severity
major
LCell
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-37
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "hsbitratemeasInitFail" alarm.

Description
The initiation of the High Speed Downlink Shared CHannel (HS-DSCH) provided bit rate
measurement has failed.
Severity
warning
LCell
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-38
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
rSSImeasStop alarm
....................................................................................................................................................................................................................................
rSSImeasStop alarm
Purpose
This topic provides all informations about the "rSSImeasStop" alarm.

Description
The RSSI measurement is discontinued.

Severity
major
LCell
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-39
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
tSSImeasStop alarm
....................................................................................................................................................................................................................................
tSSImeasStop alarm
Purpose
This topic provides all informations about the "tSSImeasStop" alarm.

Description
The TSSI measurement is discontinued.

Severity
major
LCell
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-40
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
rACHmeasStop alarm
....................................................................................................................................................................................................................................
rACHmeasStop alarm
Purpose
This topic provides all informations about the "rACHmeasStop" alarm.

Description
The RACH measurement is discontinued.

Severity
major
LCell
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-41
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "hsbitratemeasStop" alarm.

Description
The HS-DSCH provided bit rate measurement is discontinued.

Severity
warning
LCell
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-42
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "commonMeasInitTimeout" alarm.

Description
The Block Resource Request Component (BRRC) does not respond when a common
measurement starts.
Severity
major
LCell
Probable cause
responseTimeExcessive
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-43
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "invalidSIBSchedule" alarm.

Description
The CSIB has detected an invalid Service Indicator Busy (SIB) schedule. No update of
SIBs is performed towards the Clear Channel Capability (CCC).
Severity
major
LCell
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-44
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "sIBUpdateCCCError" alarm.

Description
The SIB update was not performed within CCC. The CCC specific error cause is
returned.
Severity
major
LCell
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-45
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "invalidSIBParameter" alarm.

Description
The CSIB has detected an invalid SIB parameter. No update of SIBs is performed towards
CCC.
Severity
major
LCell
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-46
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "channelConfigBCHFailed" alarm.

Description
The configuration of the Common Channel BCH has failed.

Severity
major
LCell
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-47
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "channelConfigPCHFailed" alarm.

Description
The configuration of the Common Transport Channel for the paging has failed.
Severity
major
LCell
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-48
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "channelConfigFACHFailed" alarm.

Description
The configuration of the Common Transport Channel for FACH has failed.
Severity
major
LCell
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-49
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "channelConfigPRACHFailed" alarm.

Description
The configuration of the Common Transport Channel for the Physical Random Access
CHannel (PRACH) has failed.
Severity
major
LCell
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-50
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "sharedChannelConfigHSPAFailed" alarm.

Description
The initiation of the Shared Channel for HSDPA/HSUPA has failed.

Severity
major
LCell
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-51
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "rbSevereFailure" alarm.

Description
A severe failure is detected in Radio Bearer (RB) subsystem.

Severity
major
LCell
Probable cause
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-52
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "rbNonSevereFailure" alarm.

Description
A non severe failure is detected in Radio BearerRB subsystem.

Severity
warning
LCell
Probable cause
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-53
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "cpBlockRequestTimeout" alarm.

Description
The Block Resource Request Module (BRRM) does not respond to a Block Resource
Request received from BRRC.
Severity
major
LCell
Probable cause
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-54
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "tpapReleaseIndPCH" alarm.

Description
The Transaction Processing Applications Program (TPAP) release indication for Paging
CHannel (PCH) was received by BRRM.
Severity
major
LCell
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-55
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "tpapReleaseIndFACH" alarm.

Description
The Transaction Processing Applications Program (TPAP) release indication for the
FACH was received by the BRRM.
Severity
major
LCell
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-56
401-387-065 Issue 4
July 2010
Small Cell alarms

Class LCell Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "tpapReleaseIndRACH" alarm.

Description
The Transaction Processing Applications Program (TPAP) release indication for the
RACH was received by the BRRM.
Severity
major
LCell
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-57
401-387-065 Issue 4
July 2010
Small Cell alarms

Class SDM Alarms
Overview
....................................................................................................................................................................................................................................
Class SDM Alarms

Overview
Purpose
This section provides information about the alarms related to the Software and Database
Manager (SDM).
....................................................................................................................................................................................................................................
BCR 2.2
10-58
401-387-065 Issue 4
July 2010
Small Cell alarms

Class SDM Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "suDownloadFailure" alarm.

Description
The download of the database has failed.

Severity
major
SDM
Probable cause
softwareError
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-59
401-387-065 Issue 4
July 2010
Small Cell alarms

Class SDM Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "suActivationFailure" alarm.

Description
The activation of a software image has failed.

Severity
major
SDM
Probable cause
softwareError
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-60
401-387-065 Issue 4
July 2010
Small Cell alarms

Class SDM Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "dbDownloadFailure" alarm.

Description
The database download has failed.

Severity
major
SDM
Probable cause
softwareError
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-61
401-387-065 Issue 4
July 2010
Small Cell alarms

Class SDM Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "toneFileDownloadFailure" alarm.

Description
A tone file download has failed.

Severity
minor
SDM
Probable cause
softwareError
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-62
401-387-065 Issue 4
July 2010
Small Cell alarms

Class SDM Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "toneFileCorrupt" alarm.

Description
A downloaded tone file has an invalid format.

Severity
minor
SDM
Probable cause
unspecifiedReason
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-63
401-387-065 Issue 4
July 2010
Small Cell alarms

Overview
....................................................................................................................................................................................................................................

Overview
Purpose
This section provides information about the alarms concerning the Radio Frequency (RF)
trace.
....................................................................................................................................................................................................................................
BCR 2.2
10-64
401-387-065 Issue 4
July 2010
Small Cell alarms

....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "rfTraceDedicatedFailure" alarm.

Description
In the RF Trace operation, all dedicated measurement, excluding HSDPA and Enhanced
Dedicated CHannel (EDCH), configurations have failed.
Severity
minor
RFTrace
Probable cause
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-65
401-387-065 Issue 4
July 2010
Small Cell alarms

....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "rfTraceHsdpaFailure" alarm.

Description
During trace operation, all HSDPA measurement configurations have failed.

Severity
minor
RFTrace
Probable cause
Event type
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-66
401-387-065 Issue 4
July 2010
Small Cell alarms

Class PM Alarms
Overview
....................................................................................................................................................................................................................................
Class PM Alarms
Overview
Purpose
This section provides information about the Performances Management (PM) alarms.
....................................................................................................................................................................................................................................
BCR 2.2
10-67
401-387-065 Issue 4
July 2010
Small Cell alarms

Class PM Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "pmAuthenticationError" alarm.

Description
An authentication error has occurred while transferring the PM files.

The operator could check SFTP server and related configuration.
Severity
critical
PM
Probable cause
unauthorizedAccessAttempt
Event type
communicationsAlarm
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-68
401-387-065 Issue 4
July 2010
Small Cell alarms

Class PM Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "pmCommunicationError" alarm.

Description
A failure has occurred while transferring the PM files, after several attempts.
Severity
warning
PM
Probable cause
Event type
communicationsAlarm
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-69
401-387-065 Issue 4
July 2010
Small Cell alarms

Overview
....................................................................................................................................................................................................................................

Overview
Purpose
This section provides information about the alarms related to the BSR Gateway.
....................................................................................................................................................................................................................................
BCR 2.2
10-70
401-387-065 Issue 4
July 2010
Small Cell alarms

....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "noResponseFromBGWY" alarm.

Description
The communication on the interface to BSR Gateway is interrupted.

Severity
major
ItfBGWY
Probable cause
Event type
communicationsAlarm
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-71
401-387-065 Issue 4
July 2010
Small Cell alarms

Class ItfBVG Alarms
Overview
....................................................................................................................................................................................................................................
Class ItfBVG Alarms

Overview
Purpose
This section provides information about the alarms.related to the interface between the
Small Cell and the BSR Voice Gateway (BVG).
....................................................................................................................................................................................................................................
BCR 2.2
10-72
401-387-065 Issue 4
July 2010
Small Cell alarms

Class ItfBVG Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "itfBVGLinkFailure" alarm.

Description
This alarm is created when ItfBVG link is in failure. The fault is detected when the BVG
does not receive the identifier number (id) exchanged over the interface between the
Small Cell and the BVG. This alarm is also sent when the procedure executed for the
binding update of the BVG failed.
The operator could check configuration of BVG IP address.
Severity
major
ItfBVG
Probable cause
Event type
communicationsAlarm
Nature
ADAC
The Small Cell records the fault in the log. The Small Cell gives reduced service (no CS
RABs).

...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-73
401-387-065 Issue 4
July 2010
Small Cell alarms

Overview
....................................................................................................................................................................................................................................

Overview
Purpose
This section provides information about the alarms related to fault occuring over the
interface between the Small Cell and the Serving GPRS Support
....................................................................................................................................................................................................................................
BCR 2.2
10-74
401-387-065 Issue 4
July 2010
Small Cell alarms

....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "gTPEchoFailure" alarm.

Description
An echo failure on the IuPS interface has occurred.

Severity
major
IuPSPrime
Probable cause
Event type
communicationsAlarm
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-75
401-387-065 Issue 4
July 2010
Small Cell alarms

Class ItfBPG Alarms
Overview
....................................................................................................................................................................................................................................
Class ItfBPG Alarms

Overview
Purpose
This section provides information about alarms related to the interface between the Small
Cell and the BSR Packet Gateway (BPG).
....................................................................................................................................................................................................................................
BCR 2.2
10-76
401-387-065 Issue 4
July 2010
Small Cell alarms

Class ItfBPG Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "itfBPGLinkFailure" alarm.

Description
A fault over the BPG interface has been detected. It happens in case of initializing BPG
binding update failure or where there is no response to a normal DPAT procedure. This
link failure is declared when the DPAT bind request fails.
Severity
major
ItfBPG
Probable cause
Event type
communicationsAlarm
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-77
401-387-065 Issue 4
July 2010
Small Cell alarms

Overview
....................................................................................................................................................................................................................................

Overview
Purpose
This section provides information about the Stream Control Transmission Protocol
(SCTP) alarms.
....................................................................................................................................................................................................................................
BCR 2.2
10-78
401-387-065 Issue 4
July 2010
Small Cell alarms

....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "sctpAssocAssociationDownAlarm" alarm.

Description
Either the Small Cell was not able to establish an SCTP association or the SCTP heartbeat
of an established SCTP Association was not successful.
The operator could check configuration of BSG IP address and whether BSG is
operational.
Severity
major
SCTPASSOC
Probable cause
communicationsSubsystemFailure
Event type
communicationsAlarm
Nature
ADAC
The Small Cell records the fault in the log. The Small Cell disables the SCTPASSOC and
LCell MOs. The Small Cell doesn't give user service.

...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-79
401-387-065 Issue 4
July 2010
Small Cell alarms

Class Radio Alarms
Overview
....................................................................................................................................................................................................................................
Class Radio Alarms

Overview
Purpose
This section provides information about the hardware faults classified as radio alarms.
....................................................................................................................................................................................................................................
BCR 2.2
10-80
401-387-065 Issue 4
July 2010
Small Cell alarms

Class Radio Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "overTemperature" alarm.

Description
The temperature is over the specified limit.

Severity
major
Radio
Probable cause
temperatureUnacceptable
Event type
environmentalAlarm
Nature
ADAC
The Small Cell records the fault in the log. RF is stopped, no user service is given. Radio
and LCell model objects are disabled.

...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-81
401-387-065 Issue 4
July 2010
Small Cell alarms

Class Radio Alarms
txMalfunction alarm
....................................................................................................................................................................................................................................
txMalfunction alarm
Purpose
This topic provides all informations about the "txMalfunction" alarm.

Description
The radio interface is detected in failure while activating the transmitter, or in case of
malfunction conditions in the radio transmitter.
Severity
critical
Radio
Probable cause
Event type
equipmentAlarm
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-82
401-387-065 Issue 4
July 2010
Small Cell alarms

Class Radio Alarms
rxMalfunction alarm
....................................................................................................................................................................................................................................
rxMalfunction alarm
Purpose
This topic provides all informations about the "rxMalfunction" alarm.

Description
The radio receiver malfunctions.

Severity
major
Radio
Probable cause
Event type
equipmentAlarm
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-83
401-387-065 Issue 4
July 2010
Small Cell alarms

Class Radio Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "underTemperature" alarm.

Description
The temperature is below the specified limit.

Severity
major
Radio
Probable cause
temperatureUnacceptable
Event type
environmentalAlarm
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-84
401-387-065 Issue 4
July 2010
Small Cell alarms

Class Radio Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "clockSynchronisationFailure" alarm.

Description
A failure synchronization of the network elements occurs or the network time server is
unreachable at start-up.
The operator could check configuration and status of NTP server.
Severity
critical
Radio
Probable cause
timingProblem
Event type
equipmentAlarm
Nature
ADAC
The Small Cell records the fault in the log. The radio transmission is stopped.

...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-85
401-387-065 Issue 4
July 2010
Small Cell alarms

Class Radio Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "ntpServiceUnavailable" alarm.

Description
The fault is raised if the Network Time Protocol (NTP) service in the Managed Transport
Network (MTP) is not available.
Severity
major
Radio
Probable cause
timingProblem
Event type
equipmentAlarm
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-86
401-387-065 Issue 4
July 2010
Small Cell alarms

Class CECTL Alarms
Overview
....................................................................................................................................................................................................................................
Class CECTL Alarms

Overview
Purpose
This section provides information about hardware faults classified as Channel Element
Controller (CECTL) alarms.
....................................................................................................................................................................................................................................
BCR 2.2
10-87
401-387-065 Issue 4
July 2010
Small Cell alarms

Class CECTL Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "picoArrayCommunicationFailure" alarm.

Description
Picoarray has failed to respond.

Severity
major
CECTL
Probable cause
Event type
equipmentAlarm
Nature
ADAC
The Small Cell resets picoArray.


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-88
401-387-065 Issue 4
July 2010
Small Cell alarms

Class CECTL Alarms
....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "layerOneResetFailure" alarm.

Description
The reset of the layer one has failed.

Severity
critical
CECTL
Probable cause
unspecifiedReason
Event type
equipmentAlarm
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-89
401-387-065 Issue 4
July 2010
Small Cell alarms

Overview
....................................................................................................................................................................................................................................

Overview
Purpose
This section provides information about the alarms of the Global System for Mobile
communications (GSM) listening module.
....................................................................................................................................................................................................................................
BCR 2.2
10-90
401-387-065 Issue 4
July 2010
Small Cell alarms

....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "gsmModuleFailtoInit" alarm.

Description
The initialization of the GSM listening module has failed.

Severity
major
GSMListener
Probable cause
Event type
equipmentAlarm
Nature
ADAC
The Small Cell resets. The Small Cell disables HiLo GSM module until next reset. If the
fault persists, there may be an hardware problem.

...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-91
401-387-065 Issue 4
July 2010
Small Cell alarms

....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "gsmModuleATCmdTimeoutError" alarm.

Description
The GSM listening module did not response to an AT (ATtention) command.

Severity
major
GSMListener
Probable cause
Event type
equipmentAlarm
Nature
ADAC
The Small Cell resets. The Small Cell disables HiLo GSM module until next reset. If the
fault persists, there may be an hardware problem.

...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-92
401-387-065 Issue 4
July 2010
Small Cell alarms

....................................................................................................................................................................................................................................
Purpose
This topic provides all informations about the "gsmNoCellsFound" alarm.

Description
There is no GSM cell found during a search.

Severity
minor
GSMListener
Probable cause
unspecifiedReason
Event type
equipmentAlarm
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-93
401-387-065 Issue 4
July 2010
Small Cell alarms

gsmATCmdFail alarm
....................................................................................................................................................................................................................................
gsmATCmdFail alarm
Purpose
This topic provides all informations about the "gsmATCmdFail" alarm.

Description
The AT (ATtention) command has failed.

Severity
minor
GSMListener
Probable cause
Event type
equipmentAlarm
Nature
ADAC


...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
BCR 2.2
10-94
401-387-065 Issue 4
July 2010
Part V: Configuration
management
Overview
Purpose
This part provides information about specific configuration of the Small Cell.
Contents
Chapter 11, Configuration management
11-1
...................................................................................................................................................................................................................................
BCR 2.2
V-1
401-387-065 Issue 4
July 2010
Overview
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
V-2
401-387-065 Issue 4
July 2010
11
11
Configuration
management
Overview
Purpose
This chapter explains how the operator can modify the parameters for the power control,
the radio resource management and the mobility management. These parameters are
defined in the Small Cell Parameter User Guide.
For more details of configurable Small Cell specific features, refer to document:
W-CDMA Alcatel-Lucent Small Cell | BCR 2.1 Specific Features System Definition
Specification, 401-387-048
Small Cell Parameter User Guide BCR2.1., BCR/IRC/APP/026964
The Small Cell Parameter User Guide provides parameter setting recommendations.
This document gives the rationale of these settings, by describing Alcatel-Lucents
Small Cell algorithms and parameters from an engineering point of view. It also gives
some engineering rules related to parameter settings. The parameters described are
customer configuration parameters accessible using the WMS for Small Cell.
Contents
Power control
11-2
Radio resource management
11-6
Mobility management
11-7
Operator managed Small Cells
11-8
...................................................................................................................................................................................................................................
BCR 2.2
11-1
401-387-065 Issue 4
July 2010
Power control
....................................................................................................................................................................................................................................
Power control
Prerequisite
The power control application optimizes the utilization of power resources between the
HSDPA and R99 traffic.
Refer to the FPUG document to access information on the parameters relating to power
control.
To display and modify those parameters, use the following procedures.
Note: First look at the class of the parameter to modify, to know whether it is
necessary to lock or unlock the device before executing the procedure
Procedure
...................................................................................................................................................................................................
From the HDM main window, select the Small Cell.
....................................................................................................................................................................................................................................
BCR 2.2
11-2
401-387-065 Issue 4
July 2010
Power control
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Click on the manage button.

...................................................................................................................................................................................................
In the Queued Functions area use the Queue Function menu.

...................................................................................................................................................................................................
Select the function Get Parameter Values.
...................................................................................................................................................................................................
Select the parameters to be displayed using the Add button.
....................................................................................................................................................................................................................................
BCR 2.2
11-3
401-387-065 Issue 4
July 2010
Power control
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Execute by selecting the queue button.

...................................................................................................................................................................................................
Read the result.

...................................................................................................................................................................................................
End of steps.
Modify parameter values

...................................................................................................................................................................................................
From the HDM, select the Small Cell to be configured.

...................................................................................................................................................................................................
Click on the manage button.

...................................................................................................................................................................................................
In the Queued Functions area use the Queue Function menu.

...................................................................................................................................................................................................
Select the function Set Parameter Values .
....................................................................................................................................................................................................................................
BCR 2.2
11-4
401-387-065 Issue 4
July 2010
Power control
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Select the parameters to be modified using the Add button.

...................................................................................................................................................................................................
Write the New Parameter Value in the relevant field

...................................................................................................................................................................................................
Save.
...................................................................................................................................................................................................
Execute by selecting the queue button.

...................................................................................................................................................................................................
Read the result.

...................................................................................................................................................................................................
10
End of steps.
....................................................................................................................................................................................................................................
BCR 2.2
11-5
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................

Description
Radio resource control is used to accept or reject connection requests. A specific process
is performed for Emergency calls.
The list of parameters allowing the radio resource management is given in the Femto
Parameter User Guide.
The operator modifies the default value, using the Procedure to modify the Small Cell
parameters from the HDM (p. 8-11).
....................................................................................................................................................................................................................................
BCR 2.2
11-6
401-387-065 Issue 4
July 2010
Mobility management
....................................................................................................................................................................................................................................
Mobility management
Description
Parameters for the mobility management are used:
In idle mode, to hand over/from UMTS or GSM macro cells.

In connected mode, to perform a blind handover to UMTS or GSM macro cells.
For that purpose, the Small Cell defines and maintains a list of neighboring cells using
auto-configuration and procedures which require the relevant parameters defined in the
FPUG document. The operator modifies the default value according to his network needs,
using the Procedure to modify the Small Cell parameters from the HDM (p. 8-11)
Hierarchical Cell Structures
The Hierarchical Cell Structures (HCS) is a function of mobility management and is used
to :
Keep stationary UEs in the Small Cell cell
Keep UEs in a Small Cell cell, even if Small Cell cell quality diminishes temporarily
Minimize cell re-selection ping-pong between Small Cell and macro cells.
Minimize NAS procedures and therefore the signaling load.
Description of the function:
Prioritizes cell layers for mobiles in idle mode.

Controls the UE cell reselection from the Small Cell to the macro network in a
hierarchical cell structure.
Small Cell broadcasts HCS parameters.
UE re-selection algorithm takes into account HCS parameters and the UE mobility
state
Parameters set in the Small Cell profile:
enableHCS to enable or disable the use of hierarchical cell structure (HCS) for cell
re-selection
hcsPrioS to specify the HCS priority level (0-7) for the serving cell
qHCSs to specify the quality threshold levels for applying prioritized hierarchical cell
re-selection for the serving cell
....................................................................................................................................................................................................................................
BCR 2.2
11-7
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................

Operator managed access mode
The operator managed Small Cell provides an open access mode to the network.
When the Small Cell is in open access mode, it accepts access of all UEs and the Access
Control List (ACL) is not used to control the access of the UEs.
When the Small Cell is in closed access mode, the ACL list is used to control the UEs
access. The Small Cell only accepts access of these UEs listed in the ACL. Residential
Small Cells provide a closed access mode.
The Small Cell access control list stores a maximum of 256 IMSI values.
Operator managed Small Cells parameters
There is a need for operators to configure specific parameters when the Small Cell is an
operator managed Small Cell. Those parameters are settled via the bulkcm file by default
for standard cells.
HDM is enhanced on TR-069 protocol implementations on GetParameterValues() and
SetParameterValues() RPCs, in order to support configuration (read/write) of parameters
with complex type. Those parameters can be of "sequence", "struct" or "enum" types.
This allows to add or remove whole managed objects. It allows also to grow or shrink
sequences.
For operator managed Small Cells, the following parameters can be set via HDM :
Area codes:
Local, routing and service area codes
laLAC
The Location Area Code (LAC) is used to identify a location area.
raRAC
The Routing Area Code (RAC) is used to identify a routing area within
a location area.
saSAC
The Service Area of Cell (SAC) is identified along with LAC and
PLMN ID.
laLAC1 / laLAC2 / laLAC3 / laLAC4

The laLACn parameters are alternate values to laLAC for respectively for owner
calls(1), guest calls(2), for emergency calls(3), prioritized open access(4).
saSAC1 / saSAC2 / saSAC3 / saSAC4
The saSACn parameters are alternate values to saLAC for respectively for owner
calls(1), guest calls(2), for emergency calls(3), prioritized open access(4).
Location information
latitude
The latitude parameter defines the Small Cell geographical latitude location in
degrees, minutes and seconds. The hemisphere of the position is also defined.
longitude
....................................................................................................................................................................................................................................
BCR 2.2
11-8
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
The longitude parameter defines the Small Cell geographical longitude location in
degrees, minutes and seconds. The hemisphere of the position is also defined.
areaIdentityGA
The areaIdentityGA parameter indicates the Area Identity used if Geographical
Area is requested for Reporting Area in the RANAP location reporting control.
Area Identity supported is Point, Point with uncertainty and Polygon3pt.
uncertaintyRadius
The uncertaintyRadius parameter indicates the uncertainty radius of the Area
Identity supported. This is required if RANAP RANAP location reporting control
includes Accuracy Code IE.
Neighboring information
Neighbor cells parameters
Small Cell neighbourCell

The Small Cell neighbourCell parameter describes an adjacent cell relationship
that exists between two Small Cells.
FddExtCell
The FddExtCell parameter describes an adjacent cell relationship that exists
between a LCell (one Small Cell) and any other UTRAN Fdd neighbor cell.
GsmExtCell
The GsmExtCell parameter describes an adjacent cell relationship that exists
between a LCell (one Small Cell) and any other GSM neighbor cell.
PSC configuration
Primary Scrambling Code (PSC) parameters
isAutoPscConfigEnabled
The isAutoPscConfigEnabled parameter specifies how the Small Cell determine
its primary scrambling code. If true, the Small Cell automatically determines its
PSC, if set to false, the Small Cell shall use the PSC applied by the operator via
the parameter manualPscForFemto.
femtoPSCList
The femtoPSCList parameter is a list of PSC available for network listening and
PSC allocation.
manualPSCForFemto
The manualPSCForFemto parameter specifies the Primary Scrambling Code /
Primary CPICH scrambling code, which is configured by the operator when
isAutoPscConfigEnabled=FALSE.
The operator modifies the default value according to his network needs, using the
Procedure to modify the Small Cell parameters from the HDM (p. 8-11)
....................................................................................................................................................................................................................................
BCR 2.2
11-9
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
11-10
401-387-065 Issue 4
July 2010
Part VI: Accounting

management
Overview
Purpose
This part contains no task-related information, as there are no accounting tasks that an
operator can perform on the Small Cell.
Contents
Chapter 12, Accounting management
12-1
...................................................................................................................................................................................................................................
BCR 2.2
VI-1
401-387-065 Issue 4
July 2010
Overview
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
VI-2
401-387-065 Issue 4
July 2010
12
12
Accounting
Not applicable
...................................................................................................................................................................................................................................
BCR 2.2
12-1
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
12-2
401-387-065 Issue 4
July 2010
Part VII: Performance

management
Overview
Purpose
This part provides the information required to execute the performance monitoring tasks.
Contents
Chapter 13, Performance Measurement management
13-1
Chapter 14, Radio Frequency trace concepts
14-1
Chapter 15, Radio Frequency trace components
15-1
Chapter 16, Radio Frequency trace operations
16-1
...................................................................................................................................................................................................................................
BCR 2.2
VII-1
401-387-065 Issue 4
July 2010
Performance management
Overview
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
VII-2
401-387-065 Issue 4
July 2010
13
13
Performance
Measurement
management
Overview
Purpose
This chapter describes how to perform the Performance Measurement tasks using the
HDM.
For more information concerning the performance management principles, the PM
counter types and the list of performance measurements supported on the Small Cell,
refer to the following document:
W-CDMA Small Cell Solution Performance Measurements Definitions Manual,
401-387-055.
Contents
Small Cell Performance Measurement principles
13-2
PM enable action
13-5
PM disable action
13-6
PM and file upload procedures
13-7
Display PM measurements
13-10
...................................................................................................................................................................................................................................
BCR 2.2
13-1
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................

PM principles
The Small Cell provides a mean of measuring its own performance. The PM counters
provide the basis for the calculation of Key Performance Indicators (KPIs). The KPIs are
either a single Performance Measurement (PM) counter or formulas including several PM
counters such as dropping rates or accessibility rates.
The KPIs are important performance indicators that support operators in any of the
following areas:
Network planning
Network optimization
Network expansion
Troubleshooting
Network acceptance
The Small Cell manages the Performance Measurements of the following categories:
Paging
Radio Resource Management
Handover
System Load
Radio Link
Mobility Management
Security
Session Management
PM Files
The Small Cell stores all the performance counters in a local file. The Small Cell
compresses the counter file in a zip format.
After PM collection is stopped, the Small Cell uses the normal PM file transfer
mechanism to push the result files to WMS for Small Cell (i.e. using transferTime,
randomDelay, etc.). The PM files in Small Cell can then be removed after successful
transfer.
The operator can activate a short list with reduced number of PM counters to monitor
pre-defined KPIs. The report to the HDM is performed automatically for these counters,
while the report of the main counter list is performed on demand. By this means the
volume of PM data sent to the File Server (FS) is limited.
The user then has several possibilities to activate the collection of counters on the
network:
Bulk method: create a HDM policy applicable to the Small Cell s to be observed,
setting the desired value. This is recommended to set the short value.
Single method: direct command on the HDM.
....................................................................................................................................................................................................................................
BCR 2.2
13-2
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
PM Configuration
The HDM has the following parameters for the management of PM:
perfMeasEnabled
This attribute activates or deactivates PM collection and PM result storage.
sftpServer
This attribute defines the sftp PM file server where PM files are pushed by Small Cell.
rootDirectory
This attribute defines the location where PM files are pushed to by Small Cell onto
the PM File Server.
transferTime
This attribute defines the hour value at which the PM transfer mechanism starts. It is
between midgnight (0:00) and 23:00 the day after. Only complete hours are
authorized, for example 00:00, 01:00 or 23:00.
sftpRandomDelay
This attribute defines a random delay which must be completed by each Small Cell
before opening a SFTP connection. Each Small Cell waits for this random delay
before opening a SFTP session.
silentConnectionTimeout
This attribute defines the duration the Small Cell must wait before cancelling the
connection attempt if the server does not answer.
transferFrequency
This attribute defines the frequency of PM uploading either in one hour or one day.
Values of the parameter perfMeasEnabled:
The default value is no. PM measurement collection is deactivated. No PM file is

created.
Short: performance monitoring is activated using about 35 counters.
Full: performance monitoring is activated using about 138 counters
Values of the parameter sftpServer:
The value is defined by the operator.
Values of the parameter rootDirectory:

The default value is /opt/nortel/data/utran/observation/femto.
Values of the parameter transferTime:
The value is automatically determined by the Small Cell.
Values of the parameter sftpRandomDelay:
It defines a random delay which must be computed by each Small Cell before opening
a SFTP connection. Each Small Cell waits for this random delay before opening a
SFTP session.
Values of the parameter silentConnectionTimeout:

The default value is 540.
....................................................................................................................................................................................................................................
BCR 2.2
13-3
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
Values of the parameter transferFrequency:
Hour24: PM measurement collection is collected once a day. This is the default value.
Hour1: PM measurement collection is collected every hour.
This chapter provides procedures to enable and disable the collection of performance
measurements on a Small Cell.
In case of FS backup, the FS activity and the transfer of the PM files are stopped. Two
policies concerning PM management to be used in case of FS backup have been defined
and are described next.
....................................................................................................................................................................................................................................
BCR 2.2
13-4
401-387-065 Issue 4
July 2010
PM enable action
....................................................................................................................................................................................................................................
PM enable action
Purpose
The topic describes how to enable the collection of the PM counters.

Procedure
To enable the PM collection of a Small Cell, the operator must set the parameter
Device.Services.BSR.1.PM.1.perfMeasEnabled to the value short or full.
...................................................................................................................................................................................................
Select the Small Cell, click on the manage button.

...................................................................................................................................................................................................
Lock it.
...................................................................................................................................................................................................
In the Queued Functions area , select Queue Action.

...................................................................................................................................................................................................
Launch the action Set Parameter Value with the edited parameter perfMeasEnabledat
the value short or full.
...................................................................................................................................................................................................
Unlock the device.

...................................................................................................................................................................................................
End of steps.
....................................................................................................................................................................................................................................
BCR 2.2
13-5
401-387-065 Issue 4
July 2010
PM disable action
....................................................................................................................................................................................................................................
PM disable action
Purpose
This topic describes how to disable the collection of the PM counters.

Procedure
To disable the PM collection of a Small Cell, the operator must set the parameter
Device.Services.BSR.1.PM.1.perfMeasEnabled to the value no.
...................................................................................................................................................................................................
Select the Small Cell, click on the manage button.

...................................................................................................................................................................................................
Lock it.
...................................................................................................................................................................................................
In the Queued functions area , select Queue Action.

...................................................................................................................................................................................................
Launch the action Set Parameter Value with the edited parameter .perfMeasEnabled at
the value no.
...................................................................................................................................................................................................
Unlock the Small Cell.

...................................................................................................................................................................................................
End of steps.
....................................................................................................................................................................................................................................
BCR 2.2
13-6
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................

PM procedures in case of FS backup
In this specific case two policies can be used from the HDM to activate or deactivate the
PM Small Cell file:
activate PM File upload policy
deactivate PM File upload policy
In both policies the number of targeted Small Cell devices is defined in the Maximum
Device Per Policy Run field. The operator must also set the following variables:
Expiration Timeout
Execution Timeout
Activate PM file upload policy
To activate the PM file upload on each Small Cells when their PMStatus service tag is set
to disable, the specific policy is defined as follows:
Field
Description
Action
PM enable
Search profile
Find Devices by Service Tag
Service tag
PMStatus
Service tag
Disabled
Service tag name in exit option
PMStatus
Service tag value in exit option
Enabled
Policy
Instant-triggered
Priority
Low
Maximum Device Per Policy Run
20 000
Expiration Timeout
4 hours
Execution Timeout
30 minutes
Other parameters
Default values
This policy enables the PM file upload of Small Cell devices and should be scheduled by
the operator after an FS backup.
Procedure
Perform the following steps from the HDM:

...................................................................................................................................................................................................
Select the menu policies.
....................................................................................................................................................................................................................................
BCR 2.2
13-7
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Check if the policy Activate PM File Upload exists.

...................................................................................................................................................................................................
If the policy does not exist, create it using the button New and use the value of the
parameters defined in the table above.
...................................................................................................................................................................................................
To schedule the execution of the policy, select it and click on the schedule button.
...................................................................................................................................................................................................
Tick the function Enable policy at this future day and time, and specify the date and
the time to execute the policy according to the end of FS backup, using the calendar.
...................................................................................................................................................................................................
End of steps.
Deactivate PM file upload policy
To deactivate the PM file upload on each Small Cells, the policy must be defined as
follows:
Field
Description
Action
PM Disable
Search profile
Find Devices by Performance Attribute
Service tag
PMStatus
Service tag
Disabled
Service tag name in exit option
PMStatus
Service tag value in exit option
Disabled
Policy
Instant-triggered
Priority
Low
Maximum Device Per Policy Run
20 000
Expiration Timeout
4 hours
Execution Timeout
30 minutes
Other parameters
Default values
This policy disables the PM file upload of Small Cell devices and should be scheduled by
the operator before an FS backup.
Procedure
Perform the following steps from the HDM:
....................................................................................................................................................................................................................................
BCR 2.2
13-8
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Select the menu policies.

...................................................................................................................................................................................................
Check if the policy Deactivate PM File Upload exists.

...................................................................................................................................................................................................
If the policy does not exist, create it using the button New and use the value of the
parameters above.
...................................................................................................................................................................................................
To schedule execution of the policy, select it, click on the schedule button.
...................................................................................................................................................................................................
Select the function Enable policy at this future day and time, and specify the date and
time to execute the policy according to the beginning of FS backup, using the calendar.
...................................................................................................................................................................................................
End of steps.
....................................................................................................................................................................................................................................
BCR 2.2
13-9
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
PCT tool can be used to analyze and display the PM measurements.
....................................................................................................................................................................................................................................
BCR 2.2
13-10
401-387-065 Issue 4
July 2010
14
14
Radio
Frequency trace
concepts
Overview
Purpose
This chapter presents the Radio Frequency trace tool and describes the radio
measurements.
Contents
Radio frequency trace tool
14-2
Radio measurements
14-3
...................................................................................................................................................................................................................................
BCR 2.2
14-1
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................

Purpose
To collect radio measurements from the Small Cell, the operator uses the Radio
Frequency (RF) trace tool.
Objectives
Analysis of the RF trace data collected by the RF trace tool allows the network operator
to:
Commission and tune properly the Small Cell
Execute some performance analysis

Check network capacity
Set optimization parameters
Perform tests
Process
The RF trace tool collects data from the Small Cell cell and the User Equipment (UE).
The consolidated data, available in the Small Cell, provide radio measurement
information for post-analysis by the Motive Home Device Manager (HDM).
....................................................................................................................................................................................................................................
BCR 2.2
14-2
401-387-065 Issue 4
July 2010
Radio measurements
....................................................................................................................................................................................................................................
Radio measurements
Measurement types
Radio measurements are divided into three categories according to the following
measurement types:
UE measurements
Traffic processing measurements

Common and dedicated measurements
UE measurements
Block error rate over the Common Pilot Channel (CPICH)

Block error rate on any transport channel
UE transmitted power
UE received power
Traffic processing measurements
Uplink Signal-to-Interference Ratio (SIR) target

Number of radio bearers
Transport channel identifier

Quality estimation for each transport channel
Number of different block sizes used
Total number of received blocks
Total number of received blocks with errors

HSDPA measurements
Common and dedicated measurements
Small Cell identifier

Received power at the connector of the Small Cell antenna
Carrier transmitted power (Small Cell)
Pilot transmitted power (Small Cell)

SIR over the Dedicated Physical Control CHannel (DPCCH) in the Small Cell
Transmitted power (Small Cell)
Number of random access attempts
....................................................................................................................................................................................................................................
BCR 2.2
14-3
401-387-065 Issue 4
July 2010
Radio measurements
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
14-4
401-387-065 Issue 4
July 2010
15
15
Radio
Frequency trace
components
Overview
Purpose
This chapter describes RF trace data files, RF trace software components and RF trace
interface.
Contents
RF data files
15-2
15-3
RF trace interface
15-5
...................................................................................................................................................................................................................................
BCR 2.2
15-1
401-387-065 Issue 4
July 2010
RF data files
....................................................................................................................................................................................................................................
RF data files
Allocation
When the RF trace is activated, the Small Cell allocates memory resources for storage of
the RF trace records in its memory space.
File format
The RF trace tool stores the collected information in the Small Cell. The format used is a
binary compressed one.
The RF trace tool affixes a timestamp to the trace data. The Small Cell maintains only one
single trace file.
File transfer
The HDM only supervises the Small Cell which collects the trace and sends the trace
using sFTP to the FS/WMS. Once the RF trace file stored in the Small Cell has been
transferred to the FS/WMS, it is not deleted until the memory space is required for other
radio measurements.
File size
The size of the RF file is 0.5 MB.

File format translation
The HDM and the WMS never see the RF trace files, and therefore cannot modify them.
A specific RF trace tool that comes with the Small Cell software decode the RF trace files
in order to analyze the result.
....................................................................................................................................................................................................................................
BCR 2.2
15-2
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................

RF trace tool
The RF trace tool is part of the Small Cell Operation, Administration and Maintenance
(OAM) application.
It reads the configuration data for radio measurements from the Management Information
Base (MIB) table and forwards it to the BSR Call Processing (BSR CP) component.
RF trace tool architecture
The BSR-CP specifies the architecture of the Small Cell call processing software
components. For the collection of traces, the OAM application maintains two
measurement components:
CellMeas
UEMeas
The cell component in the Small Cell sends the measurements to theCellMeas component.
The User Equipement (UE) sends the RF measurements to the UEMeas component.
The trace data is then transferred to the RF trace agent.
The RF trace agent in the OAM application collects the RF trace data from the CellMeas
and UEMeas components and forwards them to the trace manager.
The following figure shows a structural diagram of the RF trace tool within the Small
Cell.
....................................................................................................................................................................................................................................
BCR 2.2
15-3
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
Figure 15-1 Structure of the RF trace tool

Transfer trace data
through SFTP
HNM
HDM
Configuration
parameters
TR-069
Start/Stop
(Lock/Unlock)
Trace
manager
Logs
MIB
RF trace agent
CellMeas
UEMeas
OAM
Send configuration
details
and trigger tracing
From Cell
From UE
BSR-CP
....................................................................................................................................................................................................................................
BCR 2.2
15-4
401-387-065 Issue 4
July 2010
RF trace interface
....................................................................................................................................................................................................................................
RF trace interface
Interface
The OAM component in Figure 15-1, Structure of the RF trace tool (p. 15-4). is the
interface in the Small Cell, which activates the RF trace measurements.
The interface informs the management object for RF trace about the two following states:
Administrative state:
Locked to start the RF tracing process
Unlocked to stop the RF tracing process
Operational state:
Enabled
Disabled
On creation, the RF trace object is in the locked and enabled states. Unlocking the object
shall activate the trace. The state of the object changes to disabled state when an
abnormal event occurs.
Trace status
The status of traces are defined in this table:

Scenario
Tracing State
Administrative State
Initialization (assuming the

administrative state is locked)
Idle
Locked
Set on administrative state

unlocked from HDM
Tracing
unlocked

locked from HDM
Idle
locked

unlockedfrom HDM
Tracing
unlocked
Trace duration complete
Completed
locked. An AVCN(*) is then
recorded.
(*) Attribute Value Change Notification (AVCN)

Transitions
When the RF trace administrative state and operational state change from unlocked /
enabled to unlocked / disabled or locked / enabled or locked / disabled, the Small Cell
stops RF trace activity.
When the RF trace administrative state /operational state change from unlock / disabled
or lock/enabled to lock/disabled to unlock/enabled, the Small Cell starts the RF trace
activitiy.
....................................................................................................................................................................................................................................
BCR 2.2
15-5
401-387-065 Issue 4
July 2010
RF trace interface
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
15-6
401-387-065 Issue 4
July 2010
16
16
Radio
Frequency trace
operations
Overview
Purpose
This chapter presents RF trace setup, RF trace parameters, RF trace data collection and
associated alarms.
Contents
RF trace setup
16-2
RF parameters
16-3
Collection of RF data
16-4
RF trace alarms
16-5
...................................................................................................................................................................................................................................
BCR 2.2
16-1
401-387-065 Issue 4
July 2010
RF trace setup
....................................................................................................................................................................................................................................
RF trace setup
Setup
The Small Cell trace is launched from the HDM.

The requirements to run the Small Cell RF traces properly are :
Trace capability supported in the Small Cell

Capability to collect the radio data measured by a specific UE and by the Small Cell
itself
Availability of the RF trace from the management interface
Knowledge of the International Mobile Subscriber Identity (IMSI) to be traced
Files transfer
The Small Cell informs the HDM when the radio measurements are completed.
The Small Cell sent the results to FS/WMS.
The HDM never sees the RF trace files. It only supervises the Small Cell to collect and to
sent the trace using a SFTP transfer to the FS/WMS. The WMS as the HDM cannot
modify the RF Trace file. It is possible to use an RF Trace tool that comes with the Small
Cell software to decode and analyze the radio measurements.
If the interface between the FS/WMS and the Small Cell is unavailable, the traced data
remain stored in the Small Cell When the interface between the FS/WMS and the Small
Cell becomes active again, the trace file is transferred to the FS/WMS always through an
SFTP session.
The Small Cell records a notification after the successful completion of the trace file
transfer. The Small Cell does not support real time notifications to the HDM. The Small
Cell only sends notifications to the HDM periodically, for example. once per day. The
period is a configurable parameter.
....................................................................................................................................................................................................................................
BCR 2.2
16-2
401-387-065 Issue 4
July 2010
RF parameters
....................................................................................................................................................................................................................................
RF parameters
Description
The tracing process requires the following parameters :
IMSI (mandatory)
Periodicity of measurements (default value is 2 min)
Measurement type (mandatory)

Trace duration (default values are : 120 min, minimum 15 min, maximum 240 min)
Trace file name
Trace end time
sftpServer
The sftpServer parameter contains the FS/WMS IP address.
....................................................................................................................................................................................................................................
BCR 2.2
16-3
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
Management from the HDM
The RF trace tool is configured from the HDM. The RF trace is turned on and off by
unlocking and locking the instances of the managed object RFTrace. The operator
sends a command from the HDM to the Small Cell to start the RF trace. The message sent
contains all the parameters needed to perform the radio measurements.
Upon trace activation, the RF trace agent reads the configuration data from the MIB table.
The configuration data are also provided to the BSR-CP, which can trigger the activation
of the tracing on the cell component of the Small Cell and the UE.
Upon the expiration of the trace duration or after the trace session is stopped from the
HDM, the RF trace agent shall update the traceEndTime parameter in the MO
RFTrace and an AVCN is recorded. The Small Cell closes the trace file after the expiry
of the requested trace duration.
If the Small Cell is overloaded, it stops the RF trace and informs the HDM. The RF trace
file is then deleted.
Radio Access Tracing
The RF trace tool collects the RF measurement data for the specific IMSI. The Small Cell
is able to monitor one UE at the same time. The Small Cell provides an interface for
starting and stopping the RF trace session for one UE at any time.
The RF trace stays in idle status when the UE is not available (in case of out of coverage,
lost of synchronization with the Small Cell for example). The call trace is suspended. The
measurements are not stored till the UE becomes available again. The tracing file contains
information concerning the event. The RF trace stops as soon as the trace measurement is
over or when the operator locks the RF trace object.
....................................................................................................................................................................................................................................
BCR 2.2
16-4
401-387-065 Issue 4
July 2010
RF trace alarms
....................................................................................................................................................................................................................................
RF trace alarms
Alarm concepts
The Small Cell reports alarms to the HDM. There are no real time notifications but
notifications are logged into a file. The file is forwarded to the HDM on request.
Please refer to: UMTS Alcatel-Lucent Small Cell Alarms Reference Guide, 401-387-054
Alarms list
This alarm is raised in the Small Cell during the RF trace operation if all dedicated
measurement configurations, excluding HSDPA, fail.
This alarm is raised in the Small Cell during RF trace operation if all HSDPA
measurement configurations fail.
....................................................................................................................................................................................................................................
BCR 2.2
16-5
401-387-065 Issue 4
July 2010
RF trace alarms
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
16-6
401-387-065 Issue 4
July 2010
Part VIII: Security management
Overview
Purpose
This part provides information about security management of the Small Cell.
Contents
Chapter 17, Principles of security
17-1
Chapter 18, Security architecture of the Small Cell solution
18-1
Chapter 19, Small Cell Security
19-1
Chapter 20, Secure protocols
20-1
...................................................................................................................................................................................................................................
BCR 2.2
VIII-1
401-387-065 Issue 4
July 2010
Security management
Overview
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
VIII-2
401-387-065 Issue 4
July 2010
17
17
Overview
Purpose
This chapter describes general principles of security for the Alcatel-Lucent 9360 Small
Cell Solution.
Contents
Security principles
17-2
Security architecture framework
17-4
Security threats
17-5
Security layers
17-7
Security planes
17-9
Security dimensions
17-11
Security mapping threats and dimensions
17-13
...................................................................................................................................................................................................................................
BCR 2.2
17-1
401-387-065 Issue 4
July 2010
Security principles
....................................................................................................................................................................................................................................
Security principles
Overview
The Small Cell solution is vulnerable to attacks and threats to the services that are
provided to users. The security principles are based on an architecture that ensures
protection against these attacks.
Origin of attack
Understanding the origin of an attack is crucial to understand how the system is protected.
The types of attacks are listed in terms of trusted relationship with the operator:
Insider
Special entity
Partner or enterprise
Access network
External
Insider
An insider attack is an attack from an operator employee or contractor, and is performed

from or through a system that is directly connected to the operator network. Insider
attacks also include attacks from a compromised operator system, for example viruses or
malware installed on a server.
Special entity
A special entity attack is an attack from within the network of a governmental agency or
specialized entity with connectivity to the operator in order to access information or
provide service as required by law (Wiretapping, Emergency call location, services to the
disabled). Others may in their turn have compromised these networks.
Partner or enterprise
A partner attack or enterprise attack is an attack from within an operator with which the
operator has commercial agreements (wireless, ISP or outsourced management, service,
or application hosting) or from inside an enterprise customers network.
Access network
An access network attack is an attack from the operators wireless or wireline access
network (for example UMTS or DSL) by subscribers or non-subscribers.
External
An external attack is an attack from outside the operator's networks. For example from
users or sites on the Internet. External attackers may breach the first line of defense
(compromise and remotely control an operator network element, propagate a virus or
force door locks to an equipment site) to continue the attack from a more trusted origin.
....................................................................................................................................................................................................................................
BCR 2.2
17-2
401-387-065 Issue 4
July 2010
Security principles
....................................................................................................................................................................................................................................
Minimize breaches
Follow these following guidelines to minimize security breaches:
Use security in depth.

Assume that no element is failure proof and that an element may have bugs, human
design or operational errors, that could be used by an attacker.
Place limited trust in subscribers, end terminals, and operational personnel.
Use least privilege access to elements and services.
Place limited trust in application security.
Use a relationship that requires the least trust. This may not always be possible, since
interfaces to applications often must be trusted.
Perform regular backups of all systems to enable re-installation if systems are
compromised.
Never send unencrypted security credentials between elements.
Limit the personnel that can perform security management tasks.
Preferably only security administrators are able to configure security settings on
network elements.
Activate logging services to keep track of activities and preserve the logs and traces.
The use of logging reduces the need of human supervision of each element.
Try to keep security designs simple.
Complex security design increases the risk of flaws in design or implementation.
....................................................................................................................................................................................................................................
BCR 2.2
17-3
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................

Overview
The security architecture framework describes a security structure for an end-to-end

network security solution and can be applied to network elements, services, and
applications. The security architecture is described fully in ITU-T X.805.
The framework also provides a comprehensive, top-down, end-to-end perspective to
detect, predict, and correct security vulnerabilities.
Framework areas
The following list describes the areas that build the security architecture framework:
Threats
Layers
Planes
Dimensions
These areas are explained in greater detail in the following topics.

Diagram
Threats
Security Layers
Corruption
Privacy
Availability
Destruction
Data integrity
Communication security
Data confidentiality
Infrastructure security
Non-repudation
Vulnerabilities
Access control
Services security
Authentication
Application security
Removal
Disclosure
Interruption
End-user plane
Attacks
Control plane
Management plane
Security dimensions
....................................................................................................................................................................................................................................
BCR 2.2
17-4
401-387-065 Issue 4
July 2010
Security threats
....................................................................................................................................................................................................................................
Security threats
Overview
The security architecture distinguishes the following threats. The threats are categorized
by ITU-T X.805:
Threat
Description
Destruction
The destruction of network resources or information.
Corruption
The change of messages or assets.
Theft, removal, or loss
The theft, removal or loss of information or resources.
Disclosure
The unauthorized access to information.
Interruption
The network elements or services becoming unavailable, unusable

or degraded.
Destruction
Destruction is an attack on availability.

Destruction examples:
Deleting users or content
Corruption
Corruption is an attack on integrity.

Corruption examples:
Changing billing
Changing content
Charging wrong service provider
Removal
Removal is an attack on availability.

Removal examples:
Making free calls
Disclosure
Disclosure is an attack on confidentiality.

Disclosure examples:
Accessing call data

Users viewing preferences
....................................................................................................................................................................................................................................
BCR 2.2
17-5
401-387-065 Issue 4
July 2010
Security threats
....................................................................................................................................................................................................................................
Interruption
Interruption is an attack on availability.

Interruption examples:
Denial of Services (DoS)

Abuse of QoS
....................................................................................................................................................................................................................................
BCR 2.2
17-6
401-387-065 Issue 4
July 2010
Security layers
....................................................................................................................................................................................................................................
Security layers
Definition
Security layers A security layer is a hierarchy of network equipment and facility

groupings.
Security dimensions are applied to the security layers.
Security layers
The security architecture distinguishes the following security layers:

Layer
Description
Consists of the network transmission facilities and the individual

network elements that are protected by the security dimensions. The
infrastructure layer represents the fundamental building blocks of
networks, their services, and applications.
Examples of components that belong to the infrastructure layer are
routers, switches, servers, and the communication links between them.
Services security
Provides security for services that service providers deliver to their

customers.
The following services are included:
Basic transport and connectivity
Service enablers needed to provide a service

For example Authentication, Authorization, and Accounting
(AAA), Domain Name Server (DNS), and Dynamic Host
Configuration Protocol (DHCP) services
Value-added services
For example freephone service, Quality of Service (QoS), Virtual
Private Network (VPN), location services, and instant messaging
The services security layer protects the service providers and their
customers, both of which are potential targets of security threats.
For example, the attackers may attempt to deny the service provider's
ability to offer the services, or they may attempt to disrupt service for
an individual customer of the service provider.
....................................................................................................................................................................................................................................
BCR 2.2
17-7
401-387-065 Issue 4
July 2010
Security layers
....................................................................................................................................................................................................................................
Layer
Description
Provides security for the network-based applications that are accessed

by the customers of service providers.
The following applications are enabled by network services:
Basic file transport
Web browsing applications
Fundamental applications, such as directory assistance,

network-based voice messaging, and e-mail
High-end applications
For example customer relationship management,
electronic/mobile-commerce, network-based training, or video
collaboration
Network-based applications may be provided by third-party

application service providers (ASPs), service providers acting also as
ASPs, or by enterprises hosting them in their own (or leased) data
centers.
At this layer there are four potential targets for security attacks: the
application user, the application provider, the middleware provided by
third-party integrators (for example web-hosting services), and the
service provider.
Diagram
Security Layers
Threats
Destruction
Corruption
Services security
Removal
Vulnerabilities
Disclosure
Interruption
Attacks
....................................................................................................................................................................................................................................
BCR 2.2
17-8
401-387-065 Issue 4
July 2010
Security planes
....................................................................................................................................................................................................................................
Security planes
Definition
Security plane A security plane is a type of network activity that is protected by security
dimensions.
A network must be designed in such a way that events in one security plane do not affect
another security plane.
For example, a flood of Domain Name Server (DNS) lookups on the end-user plane,
initiated by end-user requests, should not lock out the OAM&P interface in the
management plane that would allow an administrator to correct the problem.
Security planes
The architecture distinguishes the following security planes:

Security plane
Description
Management
Protects OAM&P functions of the network elements, transmission facilities,

back-office systems (operations support systems, business support systems,
customer care systems), and data centers.
The management plane supports the fault, configuration, administration,
provisioning, and security (FCAPS) functions. It should be noted that the
network carrying the traffic for these activities may be in-band or
out-of-band with respect to the service provider's user traffic.
Control
Protects activities that enable the efficient delivery of information, services,

and applications across the network. It typically involves machine-tomachine communications of information that allows the machines (switches
or routers) to determine how best to route or switch traffic across the
underlying transport network. This type of information is sometimes
referred to as control or signaling information. The network carrying these
types of messages may be in-band or out-of-band with respect to the service
provider's user traffic.
For example, IP networks carry their control information in-band, whereas
the PSTN carries its control information in a separate out-of-band signaling
network (the SS7 network).
Examples of traffic of this type include
End-user
routing protocols
DNS
SS7
Megaco/H.248
Addresses security of access and use of the service provider's network by

customers. This plane also represents actual end-user data flows. End users
may use a network that only provides connectivity, they may use it for
value-added services such as Virtual Private Network (VPN)s, or they may
use it to access network-based applications.
....................................................................................................................................................................................................................................
BCR 2.2
17-9
401-387-065 Issue 4
July 2010
Security planes
....................................................................................................................................................................................................................................
Diagram
Security Layers
Threats
Destruction
Services security
Corruption
Removal
Vulnerabilities
Disclosure
Interruption
End-user plane
Control plane
Attacks
Management plane
....................................................................................................................................................................................................................................
BCR 2.2
17-10
401-387-065 Issue 4
July 2010
Security dimensions
....................................................................................................................................................................................................................................
Security dimensions
Definition
Security dimension A security dimension is a set of security measures that addresses a

network security threat.
Security dimensions apply to the network, services and applications, and end users.
Security dimensions
The architecture distinguishes the following security dimensions:

Security
dimensions
Description
Authentication
Confirms the identity of a communicating entity (person, device, service

or application).
Authentication ensures the entity is not attempting a masquerade or
unauthorized replay of a previous communication.
Access control
Protects against unauthorized use of network resources.

Access control ensures that only authorized personnel or devices are
allowed access to the following:
Non-repudiation
network elements
stored information
information flows
services
applications
Prevents an individual or entity from denying having performed a

particular action.
Non-repudiation provides evidence that can be presented to a third party
and used to prove that some kind of event or action has taken place.
Data confidentiality
Protects data from unauthorized disclosure.

Data confidentiality ensures that the data content cannot be understood
by unauthorized entities. Encryption, access control lists, and file
permissions are methods often used to provide data confidentiality.
Communication
security
Ensures that information flows only between the authorized end points.
Data integrity
Ensures the correctness or accuracy of data.
The information is not diverted or intercepted as it flows between these

end points.
The data is protected against unauthorized modification, deletion,
creation, and replication, and provides an indication of these
unauthorized activities.
....................................................................................................................................................................................................................................
BCR 2.2
17-11
401-387-065 Issue 4
July 2010
Security dimensions
....................................................................................................................................................................................................................................
Security
dimensions
Description
Availability
Ensures that there is no denial of authorized access to network elements,

stored information, information flows, services, and applications due to
events impacting the network.
Disaster recovery solutions are included in this category.
Privacy
Protects information that might be derived from the observation of

network activities.
Examples of this information include web sites that a user has visited, a
user's geographic location, and the IP addresses and Domain Name
Server (DNS) names of devices in a service provider network.
....................................................................................................................................................................................................................................
BCR 2.2
17-12
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................

Overview
Security threats against a network must be counteracted. Each threat is opposed by a

security dimension.
Mapping
The following table is a mapping of security dimensions to security threats:

Security threat
Security
dimension
Destruction
Corruption
Theft,
removal, or
loss
Data
confidentiality
Access
control
Authentication
Nonrepudiation
Data integrity
Availability
Privacy
Disclosure
Interruption
Y
Y
Y
....................................................................................................................................................................................................................................
BCR 2.2
17-13
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
17-14
401-387-065 Issue 4
July 2010
18
18
Security
architecture of
the Small Cell solution
Overview
Purpose
This chapter describes the security architecture of the Alcatel-Lucent 9360 Small Cell
Solution.
Contents
Small Cell solution security architecture
18-2
Small Cell solution security overview
18-4
...................................................................................................................................................................................................................................
BCR 2.2
18-1
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................

Overview
The security architecture of the Small Cell network divides network elements (NEs) into
three categories:
Secure
These NEs contain privileged information which must not be compromised.
Trusted
These NEs are in controlled environments and can be trusted to operate correctly, but
they do not contain privileged information.
Insecure
These NEs are in uncontrolled environments and cannot be trusted at all.
The insecure NEs (the Small Cells) communicate with other NEs through an encrypted
tunnel, and they are authenticated at the time that the tunnel is set up. Subsequent
messages are therefore guaranteed to come from the authenticated Small Cell.
Secure
Trusted
Authenticated
Encrypted and
Authenticated
Insecure
(Small Cell)
Secure
This architecture is vulnerable to hacking of the Small Cell hardware and software
because no secure connection exists between the two secure areas.
Network elements
There are a number of network elements in the Small Cell network. To minimize the
impact of a hacked Small Cell, they are all aware of security concerns.
....................................................................................................................................................................................................................................
BCR 2.2
18-2
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................
The network elements involved in the authentication of the Small Cell are:
The Small Cell, based on the (insecure) Picochip and the secure authentication chip if
the EAP-DS2460 authentication protocol is used
The VPN Firewall Brick (trusted), which terminates the IPsec tunnel(s) from each
Small Cell
The ALSMS (trusted), which manages the VPN Firewall Bricks and controls the
authentication by offloading it to the 8950 AAA server
The 8950 AAA server (secure), which controls the challenge-response protocol
between itself and the secure authentication chip in the Small Cell if the EAP-DS2460
authentication protocol is used
The Small Cell authentication database (FemtoAuthDB, secure), a flat text file that
maintains a table consisting of the Small Cell serial numbers and their associated
shared secrets
The FemtoAuthDB Management System (secure), which populates and manages the
FemtoAuthDB
The EAP-DS2460 authentication mechanism
The algorithm which is used for authentication is determined entirely by the secure
authentication chip on the Small Cell. Because the entire algorithm must be run securely,
there is no means of altering it, except to use a different chip. The chip is selected for a
combination of low cost and security of algorithm. The algorithm is a proprietary
implementation which uses the SHA-1 engine for secure hashing. This means that its
security is the same as that of SHA-1.
Because the algorithm is proprietary, specific code is needed within the operators
network to authenticate the challenge response. The ALSMS only supports a small
number of authentication options. Other authentication options are handled by connecting
to an external AAA server. This AAA server must implement the specific algorithm
required.
The 8950 AAA server performs this authentication. This server requires a database or file
to hold the mappings between Small Cell Serial Number and Shared Secret. The
FemtoAuthDB is implemented as a file with one line per Small Cell containing the Serial
Number and Shared Secret. Batches of Small Cells are added to the file as the
authentication information is received from the factory. In addition, the 8950 AAA server
contains a blacklist of Serial Numbers which are not permitted to connect to the network;
this can be used to temporarily disable Small Cells at the operator's discretion."
The ALSMS
Although the ALSMS, 8950 AAA Server and FemtoAuthDB database are all described as
separate components, they may all reside on the same hardware. Alcatel-Lucent
recommends that the 8950 AAA and FemtoAuthDB database be on the same hardware,
with the database in a separate partition of the disk.
....................................................................................................................................................................................................................................
BCR 2.2
18-3
401-387-065 Issue 4
July 2010
....................................................................................................................................................................................................................................

Overview
The following diagram provides an overview of security for the Small Cell solution:
Network firewall
embedded in Small Cell
Network
firewall
Apps; Portals;
Internet
PSTN
Internet
3GPP Core Network

MSC
SECURE
DOMAIN
3GPP Interfaces
Small Cell
Gateways
and OAM
HLR
Iu-CS
AAA Server/
Auth database
Small Cell
authentication
WMS
HDM
BVG
SGSN
Iu-PS
BSG
One Physical Housing

One
Physical Element
Firewall/IPSec
Routing
IPSEC over xDSL
Small Cell
INSECURE
DOMAIN
Physical integrity
based on seqled,
tamper-evident unit
UTRAN
UTRAN (RNC+L1
(RNC+L1 radio)
radio)
Gi
BPG
Traffic Aggregation
Security
Signalling Translation
Network firewall
embedded in
Small Cell
Small Cell local security

Integrity of critical data
stored in Small Cell
Legacy 3GPP
R99 & HSPA terminal
3GPP ciphering for
security on air interface
....................................................................................................................................................................................................................................
BCR 2.2
18-4
401-387-065 Issue 4
July 2010
19
Small Cell Security

19
Overview
Purpose
This chapter describes the security mechanisms and interfaces implemented in the Small
Cell solution.
Contents
Security on the Alcatel-Lucent Small Cell
19-2
Hardware security
19-4
Trusted Boot
19-5
Managed accounts
19-6
Air interface security
19-7
Two IPSec tunnels
19-9
...................................................................................................................................................................................................................................
BCR 2.2
19-1
401-387-065 Issue 4
July 2010
Small Cell Security
....................................................................................................................................................................................................................................

Purpose
This topic provides an introduction to security management on the Small Cell CPE.
References are provided for more detailed information.
Security associations
A pair of tunnel mode security associations (SAs), one SA in each direction, exists
between each Small Cell and an IPsec gateway in the operator's central office. This SA
serves all Small Cell logical interfaces that terminate at network elements within the
central office.
Small Cell authentication with WMS for Small Cell
The Small Cell authenticates with the WMS for Small Cell (WMS for Small Cell). This is
performed after the successful execution of the hardware, software platforms and IPsec
configuration authentication processes.
Subscriber authentication
The Small Cell provides mechanisms for subscriber authentication. By default at least one
subscriber, the end user, must be defined and known to the network service provider. In
addition, further subscribers ('guests', 'visitors') can be defined to access the Small Cell.
Secure authentication chip
An SHA-1 coprocessor provides secure storage for the authentication keys for the Small
Cell. Authentication keys for the UE are created dynamically through communication
with the HLR and are deleted at the end of a call. This authentication is performed when
the EAP-DS2460 authentication mechanism is used.
Secure data
UE authentication vectors are stored encrypted in RAM. With hard or soft reset, the
values are deleted and the Small Cell must get them again from the VLR or HLR.
Certificates of one or more certificate authorities (CA) are stored in flash memory. These
are not stored securely.
Subscriber information
Subscriber information in the Small Cell has the following characteristics:

Characteristic
Description
Owner
Operator
Data type
Confidential
....................................................................................................................................................................................................................................
BCR 2.2
19-2
401-387-065 Issue 4
July 2010
Small Cell Security
....................................................................................................................................................................................................................................
Characteristic
Description
Flow
First flow: over the air first authentication signalling transaction with IMSI
is not secured. Thereafter it is ciphered and integrity protected.
Second flow: IMSIs for access control list (ACL). Operator secure area to
Small Cell gateway over secure network. From Small Cell gateway to
Small Cell over IPsec tunnel.
Secure communication channels
The Small Cell uses IPsec communication channels.

SFTP support
The Small Cell supports SFTP functionality for secure transfer of data and files from the
management system through the IPsec tunnel.
SSH support
The Small Cell supports secure cut-through from the management system by means of
SSH through the IPsec tunnel.
Ports
Unused ports are blocked. Operating system hardening ensures that insecure services such
as FTP and telnet are blocked.
....................................................................................................................................................................................................................................
BCR 2.2
19-3
401-387-065 Issue 4
July 2010
Small Cell Security
Hardware security
....................................................................................................................................................................................................................................
Hardware security
Security subsystem
The security subsystem of the Small Cell is shown in the following figure.
SIM
External
Connector
EEPROM
PC202
PC202
CPLD
GemCore
DS2460
A-Chip
Embedded
authentication
chip
This subsystem contributes to the Small Cell security autentication when the
EAP-DS2460 security mechanism is activated.
Embedded authentication chip
The embedded authentication chip provides 1 KBit of data storage for validation of the
Small Cell hardware to the network on power up of the Small Cell. The embedded
authentication chip interfaces to the PC202 baseband processor through the CPLD.
Data security
During operation of the Small Cell, all sensitive data are stored in readable form only in
volatile memory (that is, memory that does not survive power resets). The lifetime of
such readable data in memory is limited to their actual use time, that is, they are removed
from memory immediately after they have been used.
Hardware authentication
When the EAP-DS2460 security mechanism is selected, the Small Cell hardware
authenticates itself to the network. This is achieved by using information stored in the
embedded authentication chip. The hardware authentication procedure ensures that cloned
software and hardware will be unable to authenticate to the network, the secret keys
stored securely within the authentication chip would need to be discovered.
....................................................................................................................................................................................................................................
BCR 2.2
19-4
401-387-065 Issue 4
July 2010
Small Cell Security
Trusted Boot
....................................................................................................................................................................................................................................
Trusted Boot
Function overview
Any software download, configuration download or patch is validated by the software

prior to committing it.
The trusted boot feature requires that each unit of software or of configuration data must
be digitally signed.
The Public Keys of the boot process are available to the application to permit this
verification. If the download is not verified, a subsequent boot does not accept them and
the download is rejected.
Functional definition
Validation is performed by checking the software against a signed list of hash values. The
software is verified as generated by the ALU build process and unaltered subsequently. To
ensure correct operation of the system, configuration parameters are similarly verified,
and if they are subsequently modified by an authorized source (e.g. the WMS for Small
Cell), then the modifications need also to be signed.
The trust is based on two sources. One is a read-only portion of the Small Cell NOR
Flash, and the other is a Public-Private Key Pair which is securely maintained by
Alcatel-Lucent.
Functional distribution
The trusted boot functionality is implemented entirely within the Small Cell. However, its
working relies on a process within software generation to ensure that each version of
Small Cell software delivered to a network operator is appropriately signed.
....................................................................................................................................................................................................................................
BCR 2.2
19-5
401-387-065 Issue 4
July 2010
Small Cell Security
Managed accounts
....................................................................................................................................................................................................................................
Managed accounts
Username and password
Network operators who need to log in to a Small Cell have to supply a username and
password. The account management makes the administration of the username and
password easier by placing them on an external Authentication Server (AS). This means
that any change to user profiles and passwords applies immediately across all the Small
Cells in the network.
Account management
The operator account management requires either a separate account server or access to
the WMS for Small Cell account server, depending on the operator preference. The
account server has to be authenticated to the Small Cell, and this authentication also
require Public/Private Keys. The operator account management covers updates to the
Small Cell configuration and file stuctures and permissions. It also covers connectivity
between the Small Cell and the external network element which provides for account
authentication.
Authentication server
Each user login attempt to a Small Cell, except those to the locally-authenticated debug
login, is authenticated to the Authentication Server. If the server is not reachable, if the
server is not authenticated, or if the user authentication attempt fails, the user login
attempt fails. If the user authentication fails, this event is logged.
The Small Cell authenticates the Authentication Server prior to user login authentication,
using public key authentication. The Authentication Server is configurable with an
operator-defined policy regarding strength, duration and renewal rules for passwords. The
Small Cell maintains an inactivity timer for each login. If the timer expires, then the user
is automatically logged out.
The Small Cell limits the number of simultaneous logins to an operator-defined
maximum. The interface between the Small Cell and the Authentication Server uses the
IPsec tunnel.
Roles and responsabilities
The account management is based on the principle of roles and responsibilities. Each role
has different capabilities depending on what the role is responsible for. The software
ensures that a particular role is not able to perform actions which are outside the realm of
its responsibilities. A particular account has multiple roles, and the account management
allows them to perform operations for any of the roles that they fulfill.
In addition, the management of the different accounts allows the addition and deletion of
roles from a particular account. To improve the security of individual accounts, the
account management system support configurable password policies, such as password
strength and password duration.
....................................................................................................................................................................................................................................
BCR 2.2
19-6
401-387-065 Issue 4
July 2010
Small Cell Security
....................................................................................................................................................................................................................................

Overview
Attempted attacks on the Uu air interface are handled by the Small Cell in compliance
with the 3GPP standards. This provides integrity protection and encryption. The
behaviour of the Small Cell on this interface regarding the security procedures is identical
to that of a regular RNC in a traditional UMTS network.
The Small Cell supports the following for security on the air interface:
Ciphering of the control and user plane
Integrity protection on all RRC signalling channels

Authentication of attached UEs
Ciphering
The Small Cell supports ciphering for security on the air interface.
All UMTS air interface communications are ciphered, except for the following:
Connection establishment
System information broadcast
Ciphering keys
The Small Cell has two ciphering keys per active UE:
One for CS connections, established between the CS service domain and the UE
One for PS connections, established between the PS service domain and the UE
The keys exist only while one or more Uu connections exist. If no UE is active, the Small
Cell has no ciphering keys. If one UE is active, the Small Cell has one or two ciphering
keys. If four UEs are active, the Small Cell may have up to eight ciphering keys. During
reconfiguration of ciphering, both the old and the new keys are present.
Characteristic
Description
Owner
Operator
Data type
Confidential
Flow
Operator secure area to Small Cell Gateway over secure

network
From Small Cell Gateway to Small Cell over IPsec tunnel
Integrity protection
The Small Cell supports 3GPP standard integrity protection on all RRC signalling
channels over the air interface. The integrity protection functionality for control plane
traffic on the Uu interface is implemented in software on the Small Cell.
....................................................................................................................................................................................................................................
BCR 2.2
19-7
401-387-065 Issue 4
July 2010
Small Cell Security
....................................................................................................................................................................................................................................
Integrity keys
The Small Cell has one integrity key per active UE. The same integrity key is used for
both CS and PS domains. The keys exist only while one or more Uu connections exist. If
no UE is active, then the Small Cell has no integrity keys. If four UEs are active, then
four integrity keys are present. During reconfiguration of integrity protection, both the old
and the new keys are present.
....................................................................................................................................................................................................................................
BCR 2.2
19-8
401-387-065 Issue 4
July 2010
Small Cell Security
Two IPSec tunnels
....................................................................................................................................................................................................................................
Two IPSec tunnels

Function overview
The two IPSec tunnels facility implements a specific QoS approach over an ADSL or
FTTH backhaul solution. Small Cell is supporting a second tunnel splitting the Small Cell
traffic into two PVCs. One tunnel is used for high priority traffic, the other one is used for
best effort traffic.
The IPsec Router supports two public Tunnel End Point (TEP) addresses:
IP1: Public TEP Address of Brick for low priority IPsec tunnel
IP2: Public TEP Address of Brick for high priority IPsec tunnel
Functional definition
During startup the Small Cell establishes the first tunnel to the IPsec Router. For this
purpose it auto-configures it's private TEP address by DHCP. This address is used to
terminate both IPsec tunnels.
The Small Cell supports a MIM attribute Small Cell virtualHbsrHostAddress (read-only)
with the Virtual HSmall Cell Host address for the first IPsec tunnel received from the
IPsec Router during IPsec tunnel establishment. During this authentication phase the first
security association is configured to carry encrypted ESP payload.
The Small Cell verifies then two attributes:
'Two IPsec Tunnels' feature is enabled
'Two Security Association' is enabled
If the 'Two IPsec Tunnels' feature is enabled, the Small Cell establishes the second IPsec
tunnel to the IPsec Router. For this purpose it uses the second TEP Address of the IPsec
Router which is configured in the Bulk CM File and processes the standard IPsec tunnel
establishment procedure. On Small Cell the same TEP Address is used as for the first
IPsec tunnel.
If the 'Two Security Associations' feature is disabled then the Small Cell continues with a
single child security association on first IPsec tunnel. If 'Two Security Associations'
feature is enabled, the Small Cell establishes a second, non-encrypted child security
association transported over the low priority path.
....................................................................................................................................................................................................................................
BCR 2.2
19-9
401-387-065 Issue 4
July 2010
Small Cell Security
Two IPSec tunnels
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
19-10
401-387-065 Issue 4
July 2010
20
Secure protocols
20
Overview
Purpose
This chapter describes the secure protocols used in the Alcatel-Lucent 9360 Small Cell
Solution.
Contents
Secure Shell
20-2
Secure FTP
20-4
IP security
20-5
...................................................................................................................................................................................................................................
BCR 2.2
20-1
401-387-065 Issue 4
July 2010
Secure protocols
Secure Shell
....................................................................................................................................................................................................................................
Secure Shell
Overview
This topic describes Secure Shell (SSH) and its implementation in the Alcatel-Lucent
Small Cell Solution.
SSH is a protocol for creating a secure connection between two systems. In the SSH
protocol, the client machine initiates a connection with a server machine. The Small Cell
CPE functions as an SSH Server. Services such as telnet-like shell, SFTP can be run over
the secure connection and any standard client that supports SSH can be used to
communicate with the Small Cell.
SSH provides the following:
After an initial connection, the client verifies whether it is connecting to the same
server during subsequent sessions.
The client transmits its authentication information, such as a username and password,
in an encrypted format to the server.
All data sent and received during the connection is transferred using strong encryption
(normally 128 bit), making it extremely difficult for an attacker to decrypt and read.
SSH access to the Small Cell is only available through the IPsec tunnel from the operator
network. SSH is not available in the Small Cell local network or the ISP network. This
means that the major reason to use SSH is to protect traffic within the MNO domain.
SSH protocols
SSH consists of the following three protocols working together:
SSH Transport Layer protocol
SSH Authentication Protocol

SSH Connection Protocol
The protocol stack is as follows:
SSH services
SSH Authentication Protocol
SSH Connection Protocol
SSH Transport Layer Protocol
SSH data stream (TCP)
....................................................................................................................................................................................................................................
BCR 2.2
20-2
401-387-065 Issue 4
July 2010
Secure protocols
Secure Shell
....................................................................................................................................................................................................................................
The SSH Transport Layer Protocol provides server authentication, confidentiality, and
integrity. It may optionally also provide compression. The transport layer is typically run
over a TCP/IP connection, but may also be used over any other reliable data stream. The
client ensures that it is communicating to the valid intended server by validating the
server using host-key based authentication. To accomplish this, the client must know the
public key of the server.
The SSH User Authentication Protocol authenticates the client-side user to the server. It
runs over the transport layer protocol. Mechanisms or user authentication include
public-key based authentication, password-based authentication, host-key based
authentication mechanism, and keyboard-interactive authentication. The server sends the
list of authentication mechanisms a client can use to authenticate itself. The client can
select an authentication mechanism from this list, and authenticate itself using the
selected method.
The SSH Connection Protocol multiplexes the encrypted tunnel into several logical
channels so that they can all share the same transport and authentication layers. Each
channel is a separate application (or service). These services can include telnet-like shells
and SFTP. The channel parameters can also be negotiated.
SSH Server
SSH Server on the Small Cell listens on TCP port 22 within the IPsec tunnel. The Small
Cell supports SSH Server version 2.0.
Command interface
The Small Cell CPE supports interactive login sessions using the SSH Server. It uses a
telnet-like shell that provides a command line interface. Every command executed is
logged. The Small Cell allows up to 5 concurrent SSH sessions.
Host key
One host key is configured on each Small Cell. This is its public key. The client uses this
public key to verify the authenticity of the server. The client opening the SSH session
with the Small Cell maintains a local database that associates each Small Cell host name
with the corresponding host key (public key).
Encryption and authentication
The Small Cell supports the following mechanisms:

Function
Mechanism
SSH payload encryption algorithm
A lightweight encryption algorithm such as

RC4
Message authentication code algorithm
HMAC-SHA1
Session Id key exchange algorithm
Diffie-Hellman-group1
SSH client authentication
Password based
....................................................................................................................................................................................................................................
BCR 2.2
20-3
401-387-065 Issue 4
July 2010
Secure protocols
Secure FTP
....................................................................................................................................................................................................................................
Secure FTP
Overview
Secure File Transfer Protocol (SFTP) is a protocol for secure file system access, and thus
secure file transfer, over an insecure network. This protocol assumes that it is running
over a secure channel, such as SSH, and that the client is already authenticated. The Small
Cell has an SFTP server, which is used to transfer files over a secure SSH connection.
These files may include configuration files and logs. The Small Cell also contains an
SFTP client, which may be used to download software images from the SFTP server.
The SFTP client in the Small Cell authenticates itself to an SSH server using a public key
based authentication mechanism.
SFTP access to the Small Cell is only available through the IPsec tunnel from the operator
network. SFTP is not available in the Small Cell local network or the ISP network.
File operations supported
The Small Cell supports file related operations, such as uploading and downloading
configuration files, log messages, and listing directory contents., using the SFTP server.
The SFTP server interacts with the local file system on the Small Cell to provide such
services.
The Small Cell supports an SFTP client that logs onto a configured SFTP server to
download files.
The SFTP client provides an API to access the SFTP server. This API can be invoked
either from the command line interface of the SSH server or from the application. The
SFTP client can be invoked from the command line interface of the SSH server by
specifying the IP address and port number of the SFTP server.
The Small Cell supports the following file operations from an SFTP client:
Creation and deletion of files

Writing
Reading
Retrieval of file attributes
Creation and deletion of directories on the Small Cell from an external SFTP client
The SSH server supports the moving and renaming of files from an SFTP client.
....................................................................................................................................................................................................................................
BCR 2.2
20-4
401-387-065 Issue 4
July 2010
Secure protocols
IP security
....................................................................................................................................................................................................................................
IP security
Overview
This topic describes IPsec and its implementation on the Alcatel-Lucent Small Cell
Solution.
About IPsec
IP security (IPsec) provides authentication and encryption of IP packets between Small

Cells and network elements (NEs) in the central office network at the network layer. For
communication between the Small Cells and the network elements of the mobile network
operator, IP packets are encrypted only between the Small Cell and the security gateway.
The security gateway acts as a security gateway for the network elements of the mobile
network operator.
The Small Cells communicate with the other components in the Small Cell network
through the managed IP network, which is considered to be insecure. The managed IP
network is outside the control of the mobile network operator, so the security of control
data that is transmitted between these devices cannot be guaranteed. IPsec is therefore
used to encrypt data to and from these peers.
Security services provided
IPsec provides the following network security services:
Data Confidentiality protects data from unauthorized disclosure. Encryption is the

security mechanism used. IPsec uses ESP protocol (encryption of packets before
transmission across a network), which provides confidentiality to the traffic flow.
Data Integrity ensures that modifications to the original data are detectable at the
receiver end. Authentication is the security mechanism used. IPsec uses ESP protocol
(authentication of packets to ensure that the data has not been altered during
transmission), which provides integrity to the traffic flow.
Data Origin Authentication verifies the identity of the claimed source of data. This
service is dependent on the data integrity service. IPsec uses ESP protocol to provide
Data Origin Authentication.
Anti-Replay the detection and rejection of replayed packets. IPsec uses ESP protocol
to provide Data Anti-Replay protection.
NAT support IPsec uses UDP encapsulation because the IPsec tunnel path uses
network address translation (NAT).
Key management
The Small Cell supports an automated key management mechanism. The Small Cell uses
the Internet Key Exchange Version 2 (IKEv2) protocol to negotiate and obtain
authenticated keying material for the secure communication.
The Small Cell also uses IKEv2 to negotiate, establish, modify and delete security
associations (SA).
....................................................................................................................................................................................................................................
BCR 2.2
20-5
401-387-065 Issue 4
July 2010
Secure protocols
IP security
....................................................................................................................................................................................................................................
IPsec protocols
The Small Cell supports the IP encapsulating security payload (ESP) protocol for
providing confidentiality (encryption), connectionless integrity, data origin authentication,
and anti-replay service.
The authentication algorithm to be used in the Authentication Data field is configurable.
The Small Cell does not support the IP Authentication Header (AH) protocol. Since ESP
can also provide the functions of AH, this protocol is not needed.
The Small Cell uses IPsec in tunnel mode for communication with the network elements
of the mobile network operator: Tunnel mode communication with the network elements
is through the IPsec Gateway only.
Certificate authority
This is used to authenticate the IPsec Gateway for compliance with RFC 4306. The
operator may select any certificate authority, either private or public. The selected
certificate authority must support X.509 V3 extensions.
IKE v2
The Small Cell sends and receives IKE messages on a specific, configurable UDP port
number with a slightly different format, due to support for NAT traversal. Four octets of
zero are prepended to IKE messages before they are sent. These octets are not part of the
IKE message, and are not included in any of the length fields or checksums defined by
IKE. The port number may deviate from the standard port number of 4500 at the request
of the customer.
Cryptographic suites
For ESP:
Encryption algorithm: AES-128
Integrity algorithm: HMAC-SHA1-96 with key length = 160 bits
For IKEv2:
Encryption algorithm: AES-128

Pseudo-random function: HMAC SHA1
Integrity algorithm: HMAC-SHA1-96
Diffie-Hellman group: 1024-bit MODP
Security associations
IPsec provides network security services by establishing a security association (SA) from
the Small Cell to the IPsec Gateway. Security associations are negotiated between the
Small Cells and the security gateway using IKEv2. The SA defines the security protocols
and cryptographic algorithms used for secure communication between the Small Cell and
all the network elements of the mobile network operator.
....................................................................................................................................................................................................................................
BCR 2.2
20-6
401-387-065 Issue 4
July 2010
Secure protocols
IP security
....................................................................................................................................................................................................................................
Since IKEv2 is used, the SA may use multiple proposals containing security protocols and
algorithms while negotiating with the security gateway.
The SA determines which protocol and algorithm to apply to the traffic between the Small
Cell and the network elements of the mobile network operator, and the keys to use for the
data flow.
Security associations are unidirectional and are established per security protocol. All
security associations can use the same combination of protocols and algorithms.
The Small Cell is responsible for the initial setup of security associations.
The following parameters are used to create security associations:
Tunnel header IP source and destination address

Security Parameter Index (SPI)
Security protocol (IKE, ESP)

Authentication algorithm
Encryption algorithm
Integrity algorithm
Diffie-Hellmann algorithm
SA lifetime
There are two types of security association: tunnel mode and transport mode. The Small
Cell only supports tunnel mode.
The Small Cell supports automatic configuration of the security associations.
The user must provide the required values at the Small Cell and at the security gateway
for automatic negotiation of security associations and the establishment of the IPsec
security association (using IKEv2) for secure communication. If a security association is
not available, then outbound IPsec processing invokes IKE negotiation to establish
security associations.
Rekeying of security associations
Rekeying of a security association used for IKE is only possible by restarting a Small
Cell. The modification is therefore service impacting.
Security association lifetime
With IKEv2, the lifetime of a security association is configured on both peers, and is not
negotiated. Each peer uses its own lifetime policy. When the configured lifetime expires,
The Small Cell starts re-keying. The Small Cell selects a random start time for the
re-keying procedure, to avoid overload on the security gateway.
The Small Cell supports a fixed lifetime of 4 hours for ESP security associations. There is
no timeout for IKE security associations.
....................................................................................................................................................................................................................................
BCR 2.2
20-7
401-387-065 Issue 4
July 2010
Secure protocols
IP security
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
20-8
401-387-065 Issue 4
July 2010
Glossary
...................................................................................................................................................................................................................................
Numerics
3GPP
Third Generation Partnership Project

...................................................................................................................................................................................................................................
AAA
Authorisation, Authentication and Accouting

AC
Alternative Current
AC/DC
Alternative Current / Direct Current

ACL
Access Control List

ACS
Auto Configuration Server

ADAC
Automatically Detected Automatically Cleared

ADMC
Automatically Detected Manually Cleared

ADSL
Asymmetric Digital Subscriber Line

ADSL2+
Enhanced ADSL
AES
Advanced Encryption Standard

AH
Authentication Header
....................................................................................................................................................................................................................................
BCR 2.2
GL-1
401-387-065 Issue 4
July 2010
Glossary
....................................................................................................................................................................................................................................
AKA
Authentication and key agreement

ALSMS
Alcatel-Lucent Security Managment System

API
Application Programming Interface

ARPU
Average Revenue Per User

ASP
Application Service Provider

AV
Authentication Vector
AVCN
Attribute Value Change Notification

...................................................................................................................................................................................................................................
BCH
Broadcast CHannel
BCR
Bsr Cluster Release

BLER
Block error rate

BPG
BSR Packet Gateway

BRR
Block Resource Request

BRRC
Block Resource Request Component

BRRM
Block Resource Request Module

BSG
BSR Signalling Gateway

BSR
Base Station Router

BSR-CP
BSR - Call Processing

....................................................................................................................................................................................................................................
BCR 2.2
GL-2
401-387-065 Issue 4
July 2010
Glossary
....................................................................................................................................................................................................................................
BVG
BSR Voice Gateway

...................................................................................................................................................................................................................................
CA
Certificate Authorities
CAC
Call Admission Control

CAPEX
Capital Expanditure
CCC
Clear Channel Capability

CDR
Charging Data Record

CellMeas
Cell Measurement
CETL
Channel Element Controller

CGF
Charging Gateway Function

CID
Customer Information Development

CM
Configuration Management
CN
Core Network
COA
Care Of Adress
CPE
Customer Premises Equipment

CPICH
Common Pilot Channel

CPLD
Complex Programming Logic Device

CS
Circuit Switched
....................................................................................................................................................................................................................................
BCR 2.2
GL-3
401-387-065 Issue 4
July 2010
Glossary
....................................................................................................................................................................................................................................
CSM
Customer Support Manager

CSR
Customer Service Representative

...................................................................................................................................................................................................................................
DC
Direct Current
DCH
Dedicated Channel
DHCP
Dynamic Host Configuration Protocol

DL
Downlink
DNS
Domain Name Server

DoS
Denial of Services
DPCCH
Dedicated Physical Control CHannel

DSL
Digital Subscriber Line

...................................................................................................................................................................................................................................
EDCH
Enhanced Dedicated CHannel

ESP
Encapsulating Security Payload

...................................................................................................................................................................................................................................
FACH
Forward Access CHannel

FAL
Femto Adaptation Layer

fBSR
femto Base Station Router

FCAPS
Fault , Configuration, Accounting, Performance, Security

....................................................................................................................................................................................................................................
BCR 2.2
GL-4
401-387-065 Issue 4
July 2010
Glossary
....................................................................................................................................................................................................................................
FDD
Frequency Division Duplex

FM
Fault Managment
FOA
First Office Application

FS
File Server
FTP
File Transfer Protocol

FTTH
Fiber To The Home

FTTU
Fiber To The User

FXS
Foreign eXchange Subscriber

...................................................................................................................................................................................................................................
GGSN
Gateway GPRS Support Node

GPRS
General Packet Radio Service

GSM
Global System for Mobile communications

GUI
Graphical User Interface

...................................................................................................................................................................................................................................
H-BSR
Home- Base Station Router

HA
Home Agent
HA
High Availability
HDM
Home Device Manager

HDMS
Home Device Management System

....................................................................................................................................................................................................................................
BCR 2.2
GL-5
401-387-065 Issue 4
July 2010
Glossary
....................................................................................................................................................................................................................................
HFB
Historical Fault Browser

HGW
Home Gateway
HLR
Home Location Register

HMAC
Hash Message Authentication Code

HS-DSCH
High Speed Downlink Shared Channel

HSDPA
High Speed Downlink Packet Access

HSPA
High Speed Packet Access

HSUPA
High Speed Uplink Packet Access

HTTP
HyperText Transfer Protocol

HUS
Home Unit Server

...................................................................................................................................................................................................................................
IKE
Internet Key Exchange

IMS
IP Multimedia Subsystem
IMSI
International Mobile Subscriber Identity

IP
Information Product
IP
Internet Protocol
IPC
IP Protocol Converter
IPSec
IP Security
....................................................................................................................................................................................................................................
BCR 2.2
GL-6
401-387-065 Issue 4
July 2010
Glossary
....................................................................................................................................................................................................................................
IPTV
Internet Protocol Television

IRP
Information Routing Protocol

ISP
Internet service provider

IT
Information Technology
ITF-N
InTerFace-North
ITU
International Telecommunications Union

IUCC
USIM Integrated Circuit Card

...................................................................................................................................................................................................................................
J2EE
Java 2 (Platform) Enterprise Edition

JMS
Java Message Service

JMS
Java Message Service

...................................................................................................................................................................................................................................
LAC
Location Area Code

LAI
Location Area Identity

LAN
Local Area Netwok

LCell
Logical Cell
LDAP
Lightweight Directory Access Protocol

...................................................................................................................................................................................................................................
MCC
Mobile Country Code

....................................................................................................................................................................................................................................
BCR 2.2
GL-7
401-387-065 Issue 4
July 2010
Glossary
....................................................................................................................................................................................................................................
MIB
Model Information Base

MIM
Management Information Model

MIP
Mobile Internet Protocol

MMS
Multimedia Message Services

MNC
Mobile Network Code

MNO
Mobile Network Operator

MO
Managed Object
MO
Model Object
MODP
MODular exPonential
MSC
Mobile Switching Centre

MSIN
Mobile Subscriber Identification Number

MSISDN
Mobile Station ISDN Number

MTP
Managed Transport Network

...................................................................................................................................................................................................................................
NAT
Network Access Translation

NBI
NorthBound Interface
NBS
NorthBound System
NE
Network Element
....................................................................................................................................................................................................................................
BCR 2.2
GL-8
401-387-065 Issue 4
July 2010
Glossary
....................................................................................................................................................................................................................................
NOC
National Operations Centre

NSP
Network Service Platform

NTP
Network Time Protocol

NTPTS
NTP Timing Server

...................................................................................................................................................................................................................................
OAM
Operation, Administration and Maintenance

OLCS
OnLine Customer Support

OPEX
Operational Expanditure
OSS
Operating Support Systems

OUI
Organizationally Unique Identifier

...................................................................................................................................................................................................................................
PABX
Private Automatic Branch eXchange

PBX
Private Branch eXchange

PC
Personal Computer
PCH
Paging CHannel
PDP
Packet Data Protocol

PLMN
Public Land Mobile Network

PM
Performance Management
PPP
Point to Point Protocol

....................................................................................................................................................................................................................................
BCR 2.2
GL-9
401-387-065 Issue 4
July 2010
Glossary
....................................................................................................................................................................................................................................
PRACH
Physical Random Access CHannel

PS
Packet Switch
PSC
Primary Scrambling Code

PSC
Physical signaling Channel

PSTN
Public switched telephone network

PVC
Permanent Virtual Circuit

...................................................................................................................................................................................................................................
QOS
Quality of Service
...................................................................................................................................................................................................................................
RA
Routing Area
RAC
Routing Area Code

RACH
Random Access CHannel

RAM
Random-Access Memory
RANAP
Radio Access Network Application Part

RB
Radio Bearer
REALM
Requirements/Execution Availability Logistics Module

RF
Radio Frequency
RFC
Request For Comments

RNC
Radio Network Controller

....................................................................................................................................................................................................................................
BCR 2.2
GL-10
401-387-065 Issue 4
July 2010
Glossary
....................................................................................................................................................................................................................................
ROC
Regional Operations Centre

ROM
Read-Only Memory
RPC
Remote Protocol Call

RRC
Remote Reboot Controller

RRC
Resource Request Channel

RRC
Radio Resource Control

RSSI
Received Signal Strengh Indicator

RTP
Real-Time Transport Protocol

...................................................................................................................................................................................................................................
SA
Security Association
SAC
Service Area Code

SAI
Service Area Identity

SAM
Service Aware Manager

SAM
Service Activation Manager

SBI
SouthBound Interface
SCTP
Stream Control Transmission Protocol

SDF
Software Description File

SDM
Software and Database Manager

....................................................................................................................................................................................................................................
BCR 2.2
GL-11
401-387-065 Issue 4
July 2010
Glossary
....................................................................................................................................................................................................................................
SFTP
Secure File Transfer Protocol

SGSN
Serving GPRS Support Node

SGW
Signalling Gateway
SHA
Secure Hash Algorithm

SIB
Service Indicator Busy

SIR
Signal to Interference Radio

SLA
Service Level Agreement

SMC
Service Managment Client

SMG
System Managment Solutions

SMS
Short Message System

SMT
Server Management Tool

SNMP
Simple Network Managment Protocol

SPI
Security Parameter Index

SRD
System Requirements Documents

SS7
Signaling System Number 7

SSH
Secure Shell
SSM
Self-Service Manager
STB
Set-Top Box
....................................................................................................................................................................................................................................
BCR 2.2
GL-12
401-387-065 Issue 4
July 2010
Glossary
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................................................
TCP
Transmission Control Protocol

TEP
Tunnel End Point

TMS
Trouble Managment Software

TMSI
Temporary Mobile Subscriber Identity

TPAP
Transaction Processing Applications Program

TR-069
Technical Report Number 69 ( ASDL Wold )

TSSI
Transmitted Signal Strengh Indicator

TT
Trouble ticketing
...................................................................................................................................................................................................................................
UDP
User Datagram Protocol

UE
User Equipment ( Terminal )

UEMeas
User Equipment Measurement

UI
User Interface
UL
Uplink
UMTS
Universal Mobile Terrestrial System

URL
Uniform Resource Locator

USIM
Universal Subscriber Identity Module

UTRAN
Umts Terrestrial Radio Access Network

....................................................................................................................................................................................................................................
BCR 2.2
GL-13
401-387-065 Issue 4
July 2010
Glossary
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................................................
VAP
Vodaphone Access Point

VLR
Visitor Location Register

VoIP
Voice over IP
VPC
Virtual Private Channel

VPN
Virtual Private Network

...................................................................................................................................................................................................................................
W-CDMA
Wideband Code Division Multiple Access

WAN
Wide Area Network

WICL
Wireless Internet Command Language

WIPS
Wireless Provionning System

WLAN
Wide Local Area Network

WMS
W-CDMA Managment System

WMS for Small Cell
Wireless Management System for Small Cell

WNMS
W-CDMA Network Managment System

WPS
Wireless Provionning System

WS
Web Services
WSDL
Web Services Description Language
....................................................................................................................................................................................................................................
BCR 2.2
GL-14
401-387-065 Issue 4
July 2010
Glossary
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................................................
XML
eXtended Markup Language
....................................................................................................................................................................................................................................
BCR 2.2
GL-15
401-387-065 Issue 4
July 2010
Glossary
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
GL-16
401-387-065 Issue 4
July 2010
Index
Numerics
8950 AAA, 18-2

................................................................................................
A AAA, 5-2
Access control
Security dimension, 17-11
Access control list, 8-15
ACL, 6-11
See: access control list
Add a new Small Cell fom the IT
Authentication database, 18-2

Availability
................................................................................................
B brick
gateway, 4-3
BSG
gateway, 4-2
bulk file, 6-4, 6-11
................................................................................................
main success scenario, 8-4

Add a new Small Cell using the HDM, 8-6
Air interface, 19-7
ALSMS
See: Security Management Server
Application layer
Security architecture, 17-7
Attacks
access network, 17-2
C Check Small Cell parameter values, 8-7
main success procedure, 8-7

Ciphering, 19-7
Control plane, 17-9
Corruption
Security threats, 17-5
external, 17-2
................................................................................................
insider, 17-2
D Data confidentiality
origin, 17-2
partner or enterprise, 17-2
special entity, 17-2
Authentication
hardware, 19-4
Authentication and key agreement, 19-7

Data integrity
Data security, 19-4
Destruction
device, 3-6, 3-8
Authentication chip, 19-4

....................................................................................................................................................................................................................................
BCR 2.2
IN-1
401-387-065 Issue 4
July 2010
Index
....................................................................................................................................................................................................................................
DHCP
Interruption
protocol, 5-3
Dimension
access control, 17-11
authentication, 17-11
availability, 17-11
communication security, 17-11
data confidentiality, 17-11
data integrity, 17-11
non-repudiation, 17-11
inventory, 6-8
IP security
See: IPsec
IPsec, 20-5
IuCS, 5-4
IuPS, 5-4
................................................................................................
L LED
indicators, 3-2
privacy, 17-11
Disclosure
DNS
server, 5-3
................................................................................................
M Management plane, 17-9
Minimization of security breaches, 17-3

Modify Small Cell parameter values, 8-10, 8-12
................................................................................................
................................................................................................
E Embedded authentication chip, 19-4
N network timing protocol, 4-5
................................................................................................
Non-repudiation
F features, 3-2
FemtoAuthDB
See: Authentication database
NTP
See network timing protocol, 4-5
................................................................................................
................................................................................................
G gateway
P policies, 6-8
brick, 4-3
Privacy
BSG, 4-2
................................................................................................

protocol
H Hardware authentication, 19-4
HDM, 6-2, 6-4, 6-8

................................................................................................
I
indicators
LED, 3-2
Infrastructure layer
Integrity protection, 19-7
interfaces, 3-2, 6-11
DHCP, 5-3
................................................................................................
S SA
See: security association

Secure FTP, 20-4
Secure memory, 19-2
Secure Shell, 20-2
Security
hardware, 19-4
Network element level, 19-2
....................................................................................................................................................................................................................................
BCR 2.2
IN-2
401-387-065 Issue 4
July 2010
Index
....................................................................................................................................................................................................................................
overview, 18-4
................................................................................................
principles, 17-2
V VPN Firewall Brick, 18-2
threats, 17-5
................................................................................................
Security architecture
dimensions, 17-11
W WMS, 6-4
WPS, 6-2, 6-4, 6-6
framework, 17-4
layers, 17-7
mapping threats and dimensions, 17-13
planes, 17-9
Security association, 19-2, 20-5
Security Management Server, 18-2
Security subsystem, 19-4, 19-5, 19-9
server
DNS, 5-3
Services layer
SFTP
See: Secure FTP
SSH
See: Secure Shell
................................................................................................
T Theft, removal, or loss

Threat
corruption, 17-5
destruction, 17-5
disclosure, 17-5
interruption, 17-5
theft, removal, or loss, 17-5
................................................................................................
U Update access control list, 8-15
main success procedure, 8-17

Use case
check Small Cell parameter values, 8-7
Modify Small Cell parameter values, 8-10, 8-12
update access control list, 8-15
User plane, 17-9
....................................................................................................................................................................................................................................
BCR 2.2
IN-3
401-387-065 Issue 4
July 2010
Index
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
BCR 2.2
IN-4
401-387-065 Issue 4
July 2010

SureSignal 2.2 OAM

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

SureSignal 2.2 OAM

Загружено:

Авторское право:

Доступные форматы

Use pursuant to applicable agreements

Use pursuant to applicable agreements

About this document

Reason for revision

New in this release

Part I: Hazard statements

Part II: System description

Small Cell solution

Small Cell description

Home cell access point

Enterprise cell access point

Small Cell cluster network elements

Small Cell core network elements

Small Cell Management Solution

Part III: Performing OAM&P on the Small Cells

Operational states synchronization

Part IV: Fault management

Principles of alarm management

Small Cell alarms

Class BSR Alarms

Class LCell Alarms

Class SDM Alarms

Class RFTrace Alarms

Class ItfBGWY Alarms

Class ItfBVG Alarms

Class IuPSPrime Alarms

Class ItfBPG Alarms

Class SCTPASSOC Alarms

Class Radio Alarms

Class CECTL Alarms

Part V: Configuration management

Part VI: Accounting management

Part VII: Performance management

Performance Measurement management

Radio Frequency trace concepts

Radio Frequency trace components

RF trace software components

Radio Frequency trace operations

Part VIII: Security management

Security threats ........................................................................................................................................................................ 17-5

Security architecture of the Small Cell solution

Small Cell Security

Mandatory parameters table

Overall system view

V1.5 home cell

V1.5 enterprise cell

WMS for Small Cell architecture diagram ....................................................................................................... 6-3

WMS data storage

Macro cells neighbor determination

Small Cell data model distribution

Small Cell group creation using WIPS

Latitude and longitude provisioning

Workorder to create a Small Cell group

Small Cell group modification workorder

Small Cell group update

Structure of the RF trace tool

About this document

The purpose of this document is to provide the Operation, Administration, Maintenance

The reissue reasons are:

Reason for reissue

New in this release

104812, 8 voice call capacity

Operator managed Small Cell

BSR Femto renamed in Small Cell.