Alcatel-Lucent BCR Release 4 Specific Features System Definition Specification

Use pursuant to applicable agreements
Title page
Alcatel-Lucent
Small Cell | Release BCR 4
Specific Features System Definition Specification
9YZ-04190-0005-DSZZA
Issue 1 | March 2013
Alcatel-Lucent Proprietary

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 2013 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
............................................................................................................................................................................................ xv
xv
Reason for reissue
...................................................................................................................................................................... xvi
xvi
New in this release ..................................................................................................................................................................... xvi

xvi
Intended audience
...................................................................................................................................................................... xvi
xvi
Supported systems
..................................................................................................................................................................... xvi
xvi
How to use this document
..................................................................................................................................................... xvii
xvii
Prerequisites ................................................................................................................................................................................ xvii

xvii
Vocabulary conventions .......................................................................................................................................................... xvii
xvii
Typographical conventions
Related information
.................................................................................................................................................. xvii
xvii
................................................................................................................................................................. xvii
xvii
Document support
................................................................................................................................................................... xvii
xvii
Technical support
..................................................................................................................................................................... xvii
xvii
How to order ............................................................................................................................................................................... xvii

xvii
How to comment ....................................................................................................................................................................... xvii
xvii
1
Small Cell access restriction

Overview ...................................................................................................................................................................................... 1-1
1-1
................................................................................................................................................ 1-2
1-2
Access restriction parameters ............................................................................................................................................... 1-8

1-8
2
Small Cell coverage indicator

Overview ...................................................................................................................................................................................... 2-1
2-1
.............................................................................................................................................. 2-2
2-2
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
iii
9YZ-04190-0005-DSZZA Release BCR 4
Issue 1 March 2013
Contents
....................................................................................................................................................................................................................................
Small Cell auto-configuration

Overview ...................................................................................................................................................................................... 3-1
3-1
Small Cell auto-configuration .............................................................................................................................................. 3-2
3-2
Initial installation steps ........................................................................................................................................................... 3-5
3-5
Data pre-provisioning .............................................................................................................................................................. 3-7
3-7
PSC selection and macro cell generation ......................................................................................................................... 3-9
3-9
RF auto-configuration ........................................................................................................................................................... 3-11
3-11
Auto-configuration parameters .......................................................................................................................................... 3-13
3-13
Small Cell self-optimisation

Overview ...................................................................................................................................................................................... 4-1
4-1
Small Cell self-optimization
................................................................................................................................................ 4-2
4-2
Periodic self-optimization ...................................................................................................................................................... 4-4

4-4
Self-optimization parameters ................................................................................................................................................ 4-5
4-5
5
3G network listening
Overview ...................................................................................................................................................................................... 5-1
5-1
.............................................................................................................................................................. 5-2
5-2
3G network listening functions ............................................................................................................................................ 5-3

5-3
Macro neighbor cell detection and PSC selection
Quiet period
........................................................................................................ 5-4
5-4
................................................................................................................................................................................ 5-5
5-5
Network listening parameters ............................................................................................................................................... 5-6

5-6
6
Overview ...................................................................................................................................................................................... 6-1
6-1
.............................................................................................................................................................. 6-2
6-2
2G network listening functions ............................................................................................................................................ 6-3

6-3
Network listening parameters ............................................................................................................................................... 6-6
6-6
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
iv
Issue 1 March 2013
Contents
....................................................................................................................................................................................................................................
Access control list administration

Overview ...................................................................................................................................................................................... 7-1
7-1
Access control list administration ....................................................................................................................................... 7-2
7-2
Updating the ACL ..................................................................................................................................................................... 7-4
7-4
ACL use case .............................................................................................................................................................................. 7-5
7-5
ACL parameters ......................................................................................................................................................................... 7-8
7-8
Automatic fallback to macro in case of failure in core

Overview ...................................................................................................................................................................................... 8-1
8-1
Automatic fallback to macro in case of failure in core ............................................................................................... 8-2
8-2
SCTP association
...................................................................................................................................................................... 8-4
8-4
Automatic fallback to macro network in case of failure parameters ...................................................................... 8-5

8-5
9
NAT traversal
Overview ...................................................................................................................................................................................... 9-1
9-1
NAT traversal
............................................................................................................................................................................ 9-2
9-2
NAT traversal on the Small Cell .......................................................................................................................................... 9-4

9-4
10
Tone generation during voice call set up

Overview
................................................................................................................................................................................... 10-1
10-1

Start, removal and download of tones
....................................................................................................................... 10-2
10-2
............................................................................................................................ 10-4
10-4
Tone generation during call set up parameters

11
Open access
Overview
................................................................................................................................................................................... 11-1
11-1
Open access
12
............................................................................................................ 10-6
10-6
............................................................................................................................................................................. 11-2
11-2
Open access enhancements

Overview
................................................................................................................................................................................... 12-1
12-1
................................................................................................................................................ 12-2
12-2
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
v
Issue 1 March 2013
Contents
....................................................................................................................................................................................................................................
Deployment scenarios ........................................................................................................................................................... 12-4

12-4
UE tracking ............................................................................................................................................................................... 12-6
12-6
RANAP paging
....................................................................................................................................................................... 12-8
12-8
Mobility management considerations ............................................................................................................................. 12-9

12-9
Open access enhancements parameters
13
....................................................................................................................... 12-10
12-10
Detection of Collapsing LAI

Overview
................................................................................................................................................................................... 13-1
13-1
Detection of Collapsing LAI for the Small Cell

Description of Detection of Collapsing LAI
......................................................................................................... 13-2
13-2
............................................................................................................... 13-4
13-4
Detection of Collapsing LAI - alarms ............................................................................................................................. 13-6

13-6
14
ePLMN support for camping and notification

Overview
................................................................................................................................................................................... 14-1
14-1
............................................................................................................ 14-2
14-2
ePLMN support for camping and notification parameters ...................................................................................... 14-4

14-4
15
Small Cell group support

Overview
................................................................................................................................................................................... 15-1
15-1
Small Cell group support ..................................................................................................................................................... 15-2

15-2
Small Cell group support parameters .............................................................................................................................. 15-6
15-6
16
Super LAC
Overview
................................................................................................................................................................................... 16-1
16-1
Super LAC overview
............................................................................................................................................................ 16-2
16-2
Super LAC functional definition

Super LAC dependencies
...................................................................................................................................... 16-4
16-4
................................................................................................................................................... 16-5
16-5
Super LAC Small Cell requirements ............................................................................................................................... 16-6

16-6
Super LAC BSG Requirements
........................................................................................................................................ 16-7
16-7
Super LAC restrictions ......................................................................................................................................................... 16-9

16-9
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
vi
Issue 1 March 2013
Contents
....................................................................................................................................................................................................................................
17
Dynamic LAC-SAC allocation

Overview
................................................................................................................................................................................... 17-1
17-1
Dynamic LAC-SAC allocation overview ...................................................................................................................... 17-2

17-2
Dynamic LAC-SAC allocation functional definition ................................................................................................ 17-3
17-3
Dynamic LAC-SAC allocation feature dependencies
Dynamic LAC-SAC allocation parameters
18
.............................................................................................. 17-4
17-4
.................................................................................................................. 17-6
17-6
Multiple PDP contexts

Overview
................................................................................................................................................................................... 18-1
18-1
Multiple PDP Contexts ......................................................................................................................................................... 18-2

18-2
19
Prioritized Open Access

Overview
................................................................................................................................................................................... 19-1
19-1
Prioritized open access
........................................................................................................................................................ 19-2
19-2
UE tracking ............................................................................................................................................................................... 19-4

19-4
Call admission control and DBC ...................................................................................................................................... 19-5
19-5
Billing ......................................................................................................................................................................................... 19-7
19-7
Prioritised open access parameters
20
.................................................................................................................................. 19-8
19-8
FM enhancements for Metro Cells

Overview
................................................................................................................................................................................... 20-1
20-1
................................................................................................................................. 20-2
20-2
Real-time monitoring of Small Cell status from the Small Cell Gateway
FM enhancements parameters
21
........................................................ 20-3
20-3
........................................................................................................................................... 20-7
20-7
GPS Localization
Overview
................................................................................................................................................................................... 21-1
21-1
GPS Localization .................................................................................................................................................................... 21-2

21-2
GPS Localization Concept .................................................................................................................................................. 21-4
21-4
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
vii
Issue 1 March 2013
Contents
....................................................................................................................................................................................................................................
22
PM enhancements for Metro Cells

Overview
................................................................................................................................................................................... 22-1
22-1
PM enhancements for Metro Cells ................................................................................................................................... 22-2

22-2
23
Multiple PDP Contexts (3PS + CS)

Overview
................................................................................................................................................................................... 23-1
23-1
Multiple PDP Contexts (3PS + CS) ................................................................................................................................. 23-2

23-2
Multiple PDP overview ........................................................................................................................................................ 23-3
23-3
Call Processing Procedures ................................................................................................................................................. 23-4
23-4
Multiple PDP Parameters
24
.................................................................................................................................................... 23-5
23-5
Extended ACL size for large femto groups

Overview
................................................................................................................................................................................... 24-1
24-1
Extended ACL size for large femto groups ................................................................................................................... 24-2

24-2
25
Small Cell network support for end-to-end call and subscriber trace
Overview
................................................................................................................................................................................... 25-1
25-1
Small Cell network support of end to end call and subscriber trace .................................................................... 25-2
25-2
Small Cell network support of end to end call and subscriber trace parameters ............................................. 25-4
25-4
26
Active-Warm Standby Gateway Redundancy

Overview
................................................................................................................................................................................... 26-1
26-1
Active-Warm Standby BSR Gateway Redundancy ................................................................................................... 26-2

26-2
Principles ................................................................................................................................................................................... 26-4
26-4
Active / warm standby Small Cell Gateway redundancy parameters ................................................................. 26-5
26-5
27
All-In-One Small Cell Gateway

Overview
................................................................................................................................................................................... 27-1
27-1
All-in-One Small Cell Gateway ........................................................................................................................................ 27-2

27-2
Principles ................................................................................................................................................................................... 27-4
27-4
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
viii
Issue 1 March 2013
Contents
....................................................................................................................................................................................................................................
28
Coverage self-optimization based on admission

Overview
................................................................................................................................................................................... 28-1
28-1
Continuous coverage self-optimization based on admission .................................................................................. 28-2

28-2
Principles ................................................................................................................................................................................... 28-4
28-4
Continuous coverage self-optimization based on admission parameters ........................................................ 28-12
28-12
29
Static IP address
Overview
................................................................................................................................................................................... 29-1
29-1
Static IP address ...................................................................................................................................................................... 29-2

29-2
30
PPPoE configuration
Overview
................................................................................................................................................................................... 30-1
30-1
PPPoE configuration ............................................................................................................................................................. 30-2

30-2
31
Assisted GPS using TCS server

Overview
................................................................................................................................................................................... 31-1
31-1
Assisted GPS using TCS server ........................................................................................................................................ 31-2

31-2
Feature overview
.................................................................................................................................................................... 31-4
31-4
Principles ................................................................................................................................................................................... 31-7

31-7
Assisted GPS using TCS server parameters ............................................................................................................... 31-10
31-10
32
Increased paging capacity for large Metro cells deployment (same LA)
Overview
................................................................................................................................................................................... 32-1
32-1
.......................................................... 32-2
32-2
Principles ................................................................................................................................................................................... 32-4

32-4
Increased paging capacity parameters .......................................................................................................................... 32-12
32-12
33
Cell broadcast services in support of CMAS

Overview
................................................................................................................................................................................... 33-1
33-1
............................................................................................................... 33-2
33-2
Principles ................................................................................................................................................................................... 33-4

33-4
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
ix
Issue 1 March 2013
Contents
....................................................................................................................................................................................................................................
CMAS Small Cell architecture .......................................................................................................................................... 33-7

33-7
Cell broadcast services in support of CMAS parameters ...................................................................................... 33-11
33-11
34
UE based assisted GPS

Overview
................................................................................................................................................................................... 34-1
34-1
UE based assisted GPS ......................................................................................................................................................... 34-2

34-2
Principles ................................................................................................................................................................................... 34-5
34-5
UE based assisted GPS parameters .................................................................................................................................. 34-6
34-6
35
Multi objectives joint coverage optimization

Overview
................................................................................................................................................................................... 35-1
35-1
Multi objectives joint coverage optimization ............................................................................................................... 35-2

35-2
Measurements and alarms ................................................................................................................................................... 35-5
35-5
Multi objectives joint coverage optimization parameters ........................................................................................ 35-7
35-7
Glossary
Index
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
x
Issue 1 March 2013
List of tables
21-1
Configuration Management ................................................................................................................................. 21-8
23-1
DCH/DCH+DCCH (+CS 12.2 Speech) .......................................................................................................... 23-3
23-2
DCH/HS+DCCH (+CS 12.2 Speech)
23-3
E-DCH/HS (+CS 12.2 Speech)+DCCH
.............................................................................................................. 23-3
......................................................................................................... 23-3
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
xi
Issue 1 March 2013
List of tables
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
xii
Issue 1 March 2013
List of figures
21-1
GPS Localization on Small Cell startup
......................................................................................................... 21-5
21-2
Small Cell GPS Location Detection ................................................................................................................. 21-7
27-1
Configuration 1: duplex, BSG only .................................................................................................................. 27-4
27-2
Configuration 2: duplex
28-1
Small Cell throughput with fixed power
28-2
Macro cell throughput with fixed power, white zone is less than 64 kbps
28-3
Small Cell throughput with self-optimization based on admission
28-4
Macro cell throughput i.c.o. Small Cell power adaptation
28-5
Coverage optimization CPICH decrease example
................................................................................ 28-10
28-6
Coverage optimization CPICH increase example
................................................................................. 28-11
31-1
Small Cell assisted GPS architecture using TCS assistance data server ............................................. 31-8
32-1
Scenarios when the Small Cell and underlying macro network use different LAC and RAC
32-2
DSCR case ................................................................................................................................................................. 32-7

32-7
32-3
Non-DSCR case and loss of data
32-4
Non-Iu Flex
........................................................................................................................................ 27-5
........................................................................................................ 28-5
........................................ 28-6
..................................................... 28-7
..................................................................... 28-8
... 32-5
...................................................................................................................... 32-7
............................................................................................................................................................... 32-9
32-9
32-5
..................................................................................................................................................................................... 32-10
32-10
33-1
Small Cell network for CMAS ........................................................................................................................... 33-5
33-2
Small Cell network architecture for CMAS support
34-1
.................................................................................. 33-7
......................................................................................................................................... 34-3
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
xiii
Issue 1 March 2013
List of figures
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
xiv
Issue 1 March 2013
About this document

About this document
Purpose
The purpose of this information product is to provide details of the following features:
Small Cell access restriction (34532)

Small Cell coverage indicator (34533)
Small Cell auto-configuration (34535)
Small Cell self-optimization (34536)
3G network listening (34537)

2G network listening (36255)
Access control list administration (34538)
Automatic fallback to macro in case of failure in core (34539)
NAT traversal (34587)

Tone generation during call setup (76980)
Open access (76631)
Open access enhancements (75405)

Detection of Collapsing LAI (76977)
ePLMN support for camping and notification (76976)
Small Cell group support (80569)
Super LAC (79495)
Dynamic LAC-SAC allocation (78695)

Multiple PDP contexts (79147)
Prioritized open access (77735)
FM enhancements for Metro Cells (101373)

GPS Localization (75545)
PM enhancements for operator managed Metro Cells (101681)

Multiple PDP Contexts 3PS + CS (76984)
Extended ACL size for large femto groups (92068)
Small Cells Network Support for End-to-End Call/Subscriber Trace (78594)
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
xv
Issue 1 March 2013
About this document

....................................................................................................................................................................................................................................
Active-Warm standby BSR Gateway Redundancy (114014)

All-In-One Femto Gateway (84141)
Coverage self-optimization based on admission (108877)
Static IP address (119110)

PPPoE configuration (157214)
Assisted GPS using TCS Server (119911)
Increased paging capacity for large Metro cells deployment (same LA) (100854)
Cell broadcast services in support of CMAS (76986)
UE-based assisted GPS (12380)
Multi objectives joint coverage optimization (116498)
Reason for reissue
The reissue reasons are:

Issue number
Issue date
Reason for reissue
March 2013
Standard
New in this release
This section details what is new in the Alcatel-Lucent Small Cell Solution Specific
Features System Definition Specification, 9YZ-04190-0005-DSZZA for Release BCR 4.
Features
Cell broadcast services in support of CMAS (76986), see Chapter 33, Cell broadcast
services in support of CMAS
UE-based assisted GPS (12380), see Chapter 34, UE based assisted GPS
Multi objectives joint coverage optimization (116498), see Chapter 35, Multi
objectives joint coverage optimization
Other changes
Editorial and formatting updates

Intended audience
The primary audience for this document is:
Alcatel-Lucent customers who want to know about the Small Cell specific features.
Supported systems
This document applies to the BCR 4 system release.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
xvi
Issue 1 March 2013
About this document

....................................................................................................................................................................................................................................
How to use this document
Refer to this document for information on the Small Cell specific features.
Prerequisites
None.
Vocabulary conventions
None.
Typographical conventions
In this document BSR Gateway may be referred as BSG. Both the terms refer to
Alcatel-Lucent 9365 BSR Gateway.
Related information
For further information about the Small Cells Cluster Release, refer to the following
documents:
Alcatel-Lucent 936x Small Cell Operation, Administration, Maintenance and

Provisioning, 9YZ-04190-0100-REZZA
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-630-224-2485 (for all other countries)
Technical support
For technical support on the product, 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/) or e-mail your comments to the Comments Hotline
(comments@alcatel-lucent.com).
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
xvii
Issue 1 March 2013
About this document

....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
xviii
Issue 1 March 2013
S1mall Cell access

restriction
Overview
Purpose
This chapter describes the Small Cell access restriction (34532) feature.
Contents
1-2
Access restriction parameters
1-8
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
1-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number
Feature number 34532.

Feature description
The Small Cell takes the appropriate action to restrict or authorize access, while avoiding
core network overload that can be caused by numerous attempts to camp on the Small
Cell.
In this release, the Small Cell operates in closed access control mode. In this mode, only
registered UEs are allowed to camp on the cell and establish a call in a Small Cell. The
authorized UEs are kept in the access control list (ACL) stored in the Small Cell. The
ACL can have up to 32 entries. The Small Cell owner or operator can update the ACL.
Access control is performed during the Location Area Update (LAU) procedure or the
Routing Area Update (RAU) procedure when attempting to move from the macro cell to
the Small Cell. The LAU is initiated because the Small Cells have a different LA from the
macro cells. The UE identification is made using the IMSI. If the IMSI is not available, it
is fetched by the Small Cell from the UE.
The LAU procedure initiated by a UE is intercepted by the Small Cell and is transmitted
to the 3G-MSC only if the UE is authorized, that is, part of the ACL, on this particular
Small Cell. If the UE is not part of the ACL, the Small Cell rejects the call. An equivalent
process occurs for the RAU.
Access control is also performed for the GPRS Attach procedure.
Use cases
The following use cases are possible when a user tries to camp on a Small Cell:
Private and invited users in the ACL are accepted.

A public user who is not in any ACL of the cluster is rejected and permanently barred
from the LAI.
A user who is not in the ACL of the current Small Cell, but is in the ACL of another
Small Cell in the same LA of the Small Cells Cluster, is not able to camp on the Small
Cell. However, the user is not permanently barred from the LAI, so can still attach to
their own Small Cell.
The BSG stores all the ACLs of the cluster.
An emergency call is authorized in any Small Cell.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
1-2
Issue 1 March 2013
....................................................................................................................................................................................................................................
Private and invited users
1. The UE establishes the RRC connection to the Small Cell, to update its location.
2. The UE sends a Location Area (LA) Update Request and/or a Routing Area Update
Request.
3. If an IMSI is not available, the Small Cell fetches the IMSI from the UE.
4. The Small Cell checks the UE Access Control List
5. If the UE is allowed to access this Small Cell, the LA update is forwarded to the MSC
for the allowed users.
The following diagram illustrates the call flow for a LAU:
User is stored in ACL
Public users
If the UE is not allowed access, then the Small Cell queries the BSG to determine
whether this UE belongs to any other Small Cell ACL associated with this LA.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
1-3
Issue 1 March 2013
....................................................................................................................................................................................................................................
User is stored in ACL? No
Public user in another Small Cell in the same cluster (USIM case)
1. If the UE is not allowed access, then the Small Cell queries the BSG to determine
whether this UE belongs to any other Small Cell ACL associated with this LA.
2. If the BSG returns a positive response, then:
a. The Small Cell uses an authentication request to cause an authentication failure
(The Small Cell authenticates the UE but does not include the AUTH IE into the
UE request)
b. The Small Cell repeats the authentication request 2 more times. After three
consecutive failed authentications, the UE enters IDLE mode and the Small Cell is
barred for 1280s.
c. The Small Cell releases the radio resources locally with a delay of 2 seconds after
transmission of the last authentication request.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
1-4
Issue 1 March 2013
....................................................................................................................................................................................................................................
Authentication Request
(Without AUTN IE)
Authentication Failure
Authentication Request
(Without AUTN IE)
Authentication Failure
Public user in another Small Cell in the same cluster (SIM case)
In the SIM case, the Small Cell rejects the Location Update Request by one of the
following methods:
If there is a surrounding macro cell, then the Small Cell can redirect the UE to the
macro layer on RRC Connection Release, or on subsequent RRC Connection, after
releasing the previous RRC connection.
If there is no surrounding macro cell, then the LAU can be rejected with cause
protocol error unspecified and then releasing the RRC connection. The UE camps in
limited service mode on the Small Cell.
The RRC connection may be repeated after 15 seconds and rejected until the UE
moves away from the Small Cell.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
1-5
Issue 1 March 2013
....................................................................................................................................................................................................................................
RRC Connection Reject
Feature benefits
This feature enables the Small Cell business model that the operator wants to apply.
It prevents signaling overload of the core network, since the procedure impacts the Small
Cells Cluster only.
Impacted systems
Small Cell, BSG

Dependencies
None
Restrictions and limitations
None
Engineering impacts
None
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
1-6
Issue 1 March 2013
....................................................................................................................................................................................................................................
Operational requirements
None
Feature type
Basic
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
1-7
Issue 1 March 2013
....................................................................................................................................................................................................................................

Attributes of class BSR: ACL
Refer to ACL parameters (p. 7-8) for information on the following parameters:
femtoACLlist
femtoACLenable
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
1-8
Issue 1 March 2013
S2mall Cell coverage

indicator
Overview
Purpose
This chapter describes the Small Cell coverage indicator (34533) feature.
Contents
2-2
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
2-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number

Feature description
The purpose of this feature is to provide the end user with the information that their
terminal is connected to the UMTS network through the Small Cell. This information is
provided in text in the man-machine interface of the terminal.
The Small Cell supports a notification solution based on a Mobility Management (MM)
or GPRS Mobility Management (GMM) information message. The solution relies on the
execution of a MM information procedure after a LAU procedure, and a GMM
information procedure after a RAU or GPRS attach procedure. LAU or RAU procedures
occur when entering or leaving the Small Cell coverage. In any case, the MM information
message sent by the MSC and the GMM information message sent by the SGSN contains
the name of the HPLMN. When entering the Small Cell coverage, LAU or RAU occurs,
followed by the MM and GMM information procedure. The Small Cell intercepts the
MM Information message and replaces the full/short network names with provisioned
network names (such as Home Network).
On moving out of Small Cell coverage, the SGSN and/or 3G-MSC needs to update the
UE to show macro layer coverage.
In the figure below, the MM procedure is shown as part of a successful location update
procedure:
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
2-2
Issue 1 March 2013
....................................................................................................................................................................................................................................
UE
Small Cell
3G-MSC
1. RRC connection establishment
2. NAS: Location update request
2. NAS: Location update request
3. NAS: MM information
3. NAS: MM information
(Network name)
(Modified network name)
5. NAS: Location update accept

5. NAS: Location update accept
6. NAS: Location update complete

6. NAS: Location update complete
7. RRC connection release
Feature benefits
This feature provides a visual indication to the user of whether the UE is on the Small
Cell or the macro network. This may be important for the end user if a specific billing
applies under the Small Cell coverage.
Impacted systems
Small Cell, Small Cell Management System (SCMS)

Dependencies
Interworking
MSC, SGSN
Devices
UE must support MM and GMM information

procedures
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
2-3
Issue 1 March 2013
....................................................................................................................................................................................................................................
None
Engineering impacts
None
None
Feature type
Basic
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
2-4
Issue 1 March 2013
S3mall Cell
auto-configuration
Overview
Purpose
This chapter describes the Small Cell auto-configuration (34535) feature.

Contents
3-2
Initial installation steps
3-5
Data pre-provisioning
3-7
PSC selection and macro cell generation
3-9
RF auto-configuration
3-11
Auto-configuration parameters
3-13
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
3-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number

Feature description
The Small Cell incorporates auto-configuration and self-optimization functions that do

not need intervention by the end user or operator.
At installation time the Small Cell automatically self-configures as follows:
1. Purchase and installation
The user buys a Small Cell, which includes a hard-coded Factory Serial Number
(FSN). The user installs the unit physically and connects main power and a
functioning DSL line. The user takes no further part in the configuration process.
2. Authentication
When the user has switched on the Small Cell and the DSL link is active,
authentication takes place as follows:
The AAA authenticates the Small Cell.
The Small Cell sets up an IPsec tunnel to the SCMS.
The Small Cell performs a software download
The Small Cell reboots and the AAA re-authenticates it.

The Small Cell transmits its FSN and TR-069 user name and password to the
SCMS.
The SCMS authenticates the Small Cell.
3. Pre-provisioning data
The following identifiers uniquely identify a Small Cell in the network:
FSN
The FSN is held in the serialNumber attribute of class BSR.
The FSN is set in the Small Cell at the factory and never changes. The FSN is
included on the WMS Small Cells as part of the pre-provisioning data and is
checked at Small Cell registration time.
Cluster ID and BSR ID
The Cluster ID and BSR ID are held in the clusterId and bSRId attributes of class
BSR.
These identifiers are used primarily at transport level. A clusterId must be
pre-provisioned for each Small Cell. The bSRId is assigned by WMS Small Cells
and written to the bulkCM file (bSRId is unique per cluster).
The Small Cell is assigned the bSRId and the clusterId as part of the registration
procedure through the bulkCM interface. The bSRId and clusterId may change if a
Small Cell is re-homed to a new cluster.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
3-2
Issue 1 March 2013
....................................................................................................................................................................................................................................
The WMS Small Cells must be pre-provisioned before it can process Small Cell
registration requests. Some of this data is input to the auto-configuration algorithms.
The following data must be pre-provisioned:
Location areas
3G and 2G macro cells band and frequency
Small Cell specific data
Profiles and cluster profiles
See Data pre-provisioning (p. 3-7) for more information on pre-provisioning data.
4. User registration
The operator can offer a secure website to the Small Cell owner, to register users that
are allowed to access the Small Cell. The SCMS provides an interface to the IT
system of the operator to support ACL updates.
5. Auto-configuration
The SCMS auto-configuration capabilities control the automatic calculation of part of
the Small Cell configuration. The scope of SCMS auto-configuration is limited to the
automatic computation of the following data:
bsrId, used for the Small Cell ID
area codes: LAC, SAC and RAC
initial macro cell list, including disallowed cells
Some of these attributes are calculated when the Small Cell is pre-provisioned, that is,
when the work order for creating that Small Cell is loaded to the WMS Small Cells.
Other attributes are calculated after the Small Cell has been registered.
3G network listening is used for 3G macro cell detection and PSC selection. See
Chapter 5, 3G network listening
2G network listening is used for detection of 2G neighbor cells. See Chapter 6, 2G
network listening for more information.
Missing geo-coordinate information is stored in the MIB Small Cell for
location-based services.
Feature benefits
This feature is key to the success of the Small Cell, due to the large number of units that
are deployed.
Impacted systems
SCMS, Small Cell.

Dependencies
Features
Network listening
OAM auto-configuration
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
3-3
Issue 1 March 2013
....................................................................................................................................................................................................................................
Interworking
IT system
None
Engineering impacts
Small Cell templates and engineering parameters must be defined using the SCMS.
None
Feature type
Basic
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
3-4
Issue 1 March 2013
....................................................................................................................................................................................................................................

Installation, authentication and registration
The Small Cell is connected, authenticated, and the user provides relevant information
during the registration process. The initial installation, authentication and registration of
the Small Cell by the end user is briefly described in Small Cell auto-configuration
(p. 3-2). When these steps are done, the SCMS has the address and location of the Small
Cell in its database.
This initial information is used for the configuration of various parameters.
Location check
The physical location of the Small Cell is checked to ensure that it has been deployed in
the correct location. If the Small Cell is deployed in the wrong location, it is not allowed
to function.
There are various reasons for implementing location check functionality. The following
are among the principal reasons for location checking:
To ensure that the Small Cell does not operate in an area where the deploying operator
does not have the appropriate spectrum licenses.
To make appropriate adjustments to the configuration of the Small Cell if it has been
moved to another location.
After moving the Small Cell, it must be re-provisioned for emergency calls to be
directed to the correct emergency centre. In some countries this is a legal requirement.
UE assisted location checking is not supported.
To limit the use of Small Cells to a fixed address, or to a certain broadband operator,
for example, for business model reasons.
The location check also applies after initial deployment to ensure that the user has not
moved the Small Cell to an inappropriate location.
There are two major mechanisms available for location checking: backhaul fingerprinting
and RF fingerprinting.
Backhaul fingerprinting
The backhaul fingerprint is a combination of checks made through the backhaul Ethernet
interface. The individual backhaul checks are as follows:
Default router MAC address check

Trace route check of first public IP address
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
3-5
Issue 1 March 2013
....................................................................................................................................................................................................................................
RF fingerprinting
The number of 3G detected macro cells is checked against the initial list provided by the
SCMS.
National location check
National location check is described under feature 78230. (National Location Lock) in the
Small Cell Security System Definition Specification document.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
3-6
Issue 1 March 2013
....................................................................................................................................................................................................................................
Location areas
Pre-provisioning of location areas data enables the auto-configuration of LAC, SAC, and
RAC. Pre-provisioned location area data consists of geographical rectangles with a set of
associated LAC codes. These rectangles can be further divided into sub-rectangles. Each
sub-rectangle is associated with a SAC code. The same applies for RAC codes.
Macro cells
Small Cell bulk CM files contain an optional initial list of candidate neighbor cells.
Pre-provisioning of macro cells in WMS Small Cells enables the automatic calculation of
the initial list. This calculation is based on the location of the Small Cell and the macro
cells, and is also used by the location check mechanism.
Small Cell specific data
Small Cell specific data consists of any data that is specific to a particular Small Cell
instance. The data includes the serial number, latitude, longitude, z-coordinate, clusterId,
profileId. The attributes calculated by the auto-configuration can optionally be manually
provisioned, thus skipping the automatic calculation. These attributes include: bsrId,
LAC, SAC, RAC and the initial cell list.
Profiles and cluster profiles
Profiles and cluster profiles include any other data other than location areas, macro cells
and Small Cell specific data. Most Small Cell configuration attributes are common to
many other Small Cells. A set of profiles can be created on WPS Small Cells. Each Small
Cell is associated with a profile.
Important! Profile and cluster profiles cannot be modified after they have been
created.
Create work order
The pre-provisioned data is loaded onto the WMS Small Cells through a create work
order. The format of all these files is CM XML.
The WPS Small Cells can be used to create the data. Any other tool can be used if it can
create the input file in the specified format.
Invalid or obsolete data can be removed from the WMS Small Cells by means of a delete
work order.
Some classes and attributes accept modify work orders.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
3-7
Issue 1 March 2013
....................................................................................................................................................................................................................................
Session and work order facilities
The WMS Small Cells supports session and work order facilities to import and store
Small Cell pre-provisioning data. The data is imported from a back office system or from
a WPS Small Cells.
Data minimally includes:
Small Cell serial number
Network-unique DN to be allocated to the Small Cell

Cluster identifier, which associates that Small Cell with a cluster profile
Profile identifier
Initial IMSI list (ACL)
Geo-coordinates: latitude, longitude, and relative altitude indicator (z-coordinate)

Security gateway address
Emergency-call related data (areaIdentity, areaUncertainty, areaPoints)
List of disallowed macro cells
The following data is optional and, if not provided, is automatically calculated as part of
the SCMS:
Area codes (LAC, SAC, RAC)

Initial macro cell list, including disallowed cells
bsrId
Updates to pre-provisioned data
Updates to pre-provisioned macro network and area-code data are not automatically
propagated to Small Cells. The changes can be propagated by enabling a policy or action.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
3-8
Issue 1 March 2013
....................................................................................................................................................................................................................................

Small Cell PSC selection
Small Cell PSC selection can be manual or automatic and is based on selecting the Small
Cell PSC with the lowest CPICH RSCP or Ec/No. The selection is from a list of Small
Cell PSCs provided by the SCMS.
Initial macro cell list generation
Initial macro 2G and 3G cell list generation is based on scanning the macro cell PSCs at
different macro-cell frequencies for the best macro cells. The best macro cells are defined
in terms of CPICH RSCP or Ec/No.
Parameters provided by Alcatel-Lucent Home Device Manager (HDM)
The Small Cell checks whether the following parameters for the auto-configuration
process are provided by the SCMS:
UL & DL UARFCN or DL UARFCN & frequency band of the Small Cell

Small Cell Primary Scrambling Code list (for selection of PSC)
Neighbor macro cell frequency list (UARFCN/Frequency band list)
Small Cell Cell Id, SAC, LAC and RAC used by Small Cell
Initial access control list and a flag to indicate whether an identity check during
auto-configuration is performed
If any of the parameters are missing or incomplete, the Small Cell raises an
auto-configuration failure. The Small Cell indicates to the user that auto-configuration has
failed by turning off the auto-configuration LED.
Parameters provided by configuration file
All other parameters required by the Small Cell for auto-configuration process are
available through the configuration file. If their values are different from the default, the
SCMS can provide the Small Cell with the following parameters:
Power settings for common and dedicated channels (Optional, use default)
Maximum DL TX power (Optional, use default)
Target Pilot RSCP and Maximum Path Loss (Optional, use default)
Cell selection/reselection parameters, for example, Qrxlevmin, Qqualmin, Sintra,

Sinter, to be populated in SIB 3 (Optional, use default)
Initial macro cell neighbor list containing PSC and frequency (Optional, assume not
available), including cells that are not allowed for use.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
3-9
Issue 1 March 2013
....................................................................................................................................................................................................................................
PSC selection and 3G macro cell generation
When all essential auto-configuration parameters are available, the Small Cell enters the
PSC selection and macro cell generation phase of the auto-configuration. The cell is only
allowed to enter operation after auto-configuration is complete.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
3-10
Issue 1 March 2013
....................................................................................................................................................................................................................................
RF auto-configuration process
RF auto-configuration is defined as the 2G and 3G network listening in order to

determine macro neighbors and select the PSC for the Small Cell.
Before RF auto-configuration is run, the underlying procedures to initialize the backhaul,
authenticate the Small Cell, download software updates and bulk configuration files must
have been successfully completed and communication with the SCMS has been
established.
During auto-configuration the network listening functionality performs the following
functions:
Generate the initial list of detected macro cells

The Small Cell uses 2G network listening and 3G network listening to search for 2G
and 3G macro cells above a certain strength threshold, and adds them to the list of
detected cells. This process may be aided by the SCMS, which may also provide the
Small Cell with an initial list of macro cells that are allowed or not allowed. This
procedure varies depending on whether it is the first time through auto-configuration,
when there are no detected cells, or whether it is on a subsequent auto-configuration,
when there is an existing list of detected cells.
Determine the PSC for the Small Cell
If manual provisioning of the PSC is not enabled, then the Small Cell determines its
own PSC. First by listening to the surrounding reserved Small Cells, and then
remaining Small Cells with its assigned PSC or selecting either an unused PSC or the
PSC which is at lowest strength.
Perform an RF fingerprint location check
This function uses the RF fingerprint to determine whether the Small Cell is in the
correct initial location or has been moved. If this is the first time the Small Cell has
been powered on, the list of detected macro cells is compared with the
pre-provisioned macro cell list. If this is not the first time the Small Cell has been
powered on, the list of detected macro cells is compared with the list of macro cells
detected last time the Small Cell was powered on.
The Small Cell can then determine the action to be taken.
Perform national location check
Set pilot power
Parameter BsrPilotPowerAdjustMode specifies the method used to set pilot power.
This parameter is configurable through OAM.
Possible methods are:
BsrPilotPowerAdjustMode: MIMBased
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
3-11
Issue 1 March 2013
....................................................................................................................................................................................................................................
The Small Cell uses pCPICHpower and MaxBSRPowerLimitdBm as the initial

pilot and maximum Small Cell power.
BsrPilotPowerAdjustMode: RscpBased
BsrPilotPowerAdjustMode: EcIoBased
Small Cell measurement based pilot power adjustment is used to adjust cell pilot
power according to Io (IodBm) measured by the Small Cell to achieve the
required TargetMinEcIodB.
The following figure shows a high level flow diagram of the RF auto-configuration
process:
Enter RF
auto-configuration
Path when
first
powered on
Is detected
cell list
available
?
Path when
subsequently
powered on
Yes
No
Location detection RF fingerprint
2G and 3G
Macro cell list
generation
Check detected
cell list
Location detection RF fingerprint
Femto PSC
selection
RF
auto-configuration
complete
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
3-12
Issue 1 March 2013
....................................................................................................................................................................................................................................
Attributes of class BSRl : Auto-configuration
Parameter
Description
Syntax
Values
autoConfigProcedureTimer
Defines the over-arching

timer for the
auto-configuration and is the
maximum duration for the
following:
integer
[0..65535],
unit=secs
integer
[0..65535],
unit=secs
1. Receiving the indication

from SCMS
2. Start of
auto-configuration
3. Successfully recreating
the Small Cell
autoConfigProcedureTimerSqInit
Defines the over-arching

timer for the
auto-configuration during
subsequent initialization and
is the maximum duration for
the following:
1. Small Cell ready to
perform
auto-configuration (that
is, all essential
auto-configuration
parameters are available)
2. Start of
auto-configuration
3. Small Cell Successfully
recreates the Small Cell.
If this attribute is set to 0, the
Small Cell skips
auto-configuration.
femtoPSCList
List of PSCs available for

network listening and PSC
allocation.
sequence [1..16] of struct

FemtoPSC
bSRId
Indicates the BSR-Id of the

Small Cell.
integer
(0.. 65535)
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
3-13
Issue 1 March 2013
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
clusterId
Indicates the Small Cells

Cluster Id to which the Small
Cell belongs to.
integer
(1..511)
identityCheckEnabledAutoConfig
Indicates whether to perform

identity check during
auto-configuration.
boolean
femtoACLlist
Specifies the list of users

permitted to use Small Cell
resources as owner, within
closed access operation mode.
The list is defined as a NULL
terminated string with
comma-separated IMSI
values.
string
length=4096
femtoACLlistGuest
Specifies the list of users

resources as guest, within
closed access operation mode.
The list is defined as a NULL
terminated string with
comma-separated IMSI
values.
string
length=4096
Attributes of class DeviceInfo: Auto-configuration

Parameter
Description
Syntax
Values
SerialNumber
Identifier of the particular

device that is unique for the
indicated class of product and
manufacture, for example:
AF123456789.
string
length=64
Values
Attributes of class LCell: Auto-configuration

Parameter
Description
Syntax
macroUMTSCellFrequencyList
Indicates the list of macro cell

UMTS neighbor cell
frequencies.
Sequence [1..10] of struct

Frequency
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
3-14
Issue 1 March 2013
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
macrocellListSIB11
Indicates the number of macro

UMTS cells in SIB 11.
integer
[1..32]
gsmFrequencyList
Indicates the GSM frequency

list.

GSMFrequencyList
gsmCellListSIB11

GSM cells in SIB 11.
integer
[1..32]
locationCheckDetectedThreshold
Provides the threshold for the

passing of UMTS RF
fingerprint location check
based on the number of
detected macro cells.
integer
[0..64]
movementCheckDetectedThreshold
Provides the threshold for the

passing of UMTS RF
fingerprint movement check
based on the number of
detected macro cells.
integer
[0..64]
locationCheckPassFlag
Indicates whether the Small

Cell has passed UMTS RF
fingerprint location check
before.
boolean
macroCellMeasurementQuantity
Define the measurement

quantity for macro cell
detection.
enum MeasurementQuality
laLAC
Specifies a Location Area

Code, which is used to identify
a location area.
integer
(1..65535)
raRAC
Specifies a Routing Area Code,

which is used to identify a
routing area within a location
area.
integer
(0..255)
uraURAC
Specifies a UTRAN
Registration Area Code, which
is used to identify a UTRAN
registration area.
integer
(1..65534)
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
3-15
Issue 1 March 2013
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
ownPLMNMNC
Specifies the Mobile Network

Code of the PLMN the Small
Cell belongs to.
string
length=3
string
length=3
The Mobile Network Code is

part of the PLMN identity
broadcast in the Master
Information Block.
ownPLMNMCC
Specifies the Mobile Country

Code of the PLMN the Small
Cell belongs to.
The Mobile Country Code is
part of the PLMN identity
broadcast in the Master
Information Block.
Attributes of class GsmExtCell: Auto-configuration
Attributes of GSMExtCell: RF Planning

Parameter
Description
Syntax
Values
ndpLabel
This label helps to easily map

objects between engineering
tools (such as the RF planning
tool) and data configured in the
field.
string
length=25
Attributes of GSMExtCell: (Initial 2G macro cell list)

Parameter
Description
Syntax
Values
bSICVeriRequired
Indicates whether the Base

transceiver Station Identity
Code needs to be verified.
boolean
nCC
Specifies the Network Colour

Code, which is part of the
BSIC.
integer
(0..7)
bCC
Specifies the Base Station

Colour Code, which is part of
the BSIC.
integer
(0..7)
bCCHArfcn
Specifies the BCCH Arfcn.
integer
(0..1023)
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
3-16
Issue 1 March 2013
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
cellIdentity
Identifies a cell unambiguously

within a location area.
integer
(0..65535)
gsmFrequBand
Indicates the operating

frequency band of the GSM
cell.
enum GSMFrequencyBand
rAC
Specifies the routing area code

of the neighbor cell.
integer
(0..255)
lAC
Specifies the location area

code of the neighbor cell.
integer
(1..65535)
mCC
Specifies the mobile country

code.
string
length=3
mNC
Specifies the mobile network

code.
string
length=3
notAllowedCell
Indicates that this cell is not

allowed for cell reselection and
handover.
boolean
Attributes of class FDDExtCell: Auto-configuration
Attributes of FDDExtCell: RF Planning

Parameter
Description
Syntax
Values
ndpLabel
This label helps to easily map

objects between engineering
tools (such as the RF planning
tool) and data configured in the
field.
string
length=25
Attributes of class FDDExtCell: (Initial 3G macro cell list)

Parameter
Description
Syntax
Values
primaryCPICHInfo
Specifies the primary

scrambling code for the
downlink radio link.
integer
(0..511)
primaryCPICHTxPower
Specifies the power in dBm.
real
(-10.0..50.0),
step=0.1,
precision=1,
unit=dBm
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
3-17
Issue 1 March 2013
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
uARFCNDownlink
Specifies the downlink

ARFCN of the cell.
integer
(0 .. 16383)
uARFCN
Specifies the Uplink ARFCN

of the cell.
integer
(0 .. 16383)
(UARFCNDownlink and
default duplex distance).
rAC

integer
(0..255)
lAC

integer
(1..65535)
mCC

code.
string
length=3
mNC

code.
string
length=3
rNCID
Identifies the RNC to which

this cell is connected
integer
(0..4095)
fddFreqBand
Specifies the frequency band

which is supported by the
external UTRAN cell.
enum FDDRadioFrequencyBand
cellIdentity

within a PLMN.
integer
notAllowedCell
Indicates that this cell is not

allowed for cell reselection and
handover.
boolean
hcsPrioN
Specifies the HCS priority

level for the provisioned
UMTS macro cells. HCS
priority level 0 = lowest
priority, HCS priority level 7 =
highest priority. hcsPrioN > 7
indicates that no HCS priority
is assigned to the neighbor cell.
integer
(0..65535)
(0..255)
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
3-18
Issue 1 March 2013
S4mall Cell
self-optimisation
Overview
Purpose
This chapter describes the Small Cell self-optimisation (34536) feature.

Contents
4-2
Periodic self-optimization
4-4
Self-optimization parameters
4-5
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
4-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number

Feature description
Following auto-configuration and once in operation the Small Cell continually adapts
itself to changes in the neighboring macro Small Cells through the self-optimization
feature.
Self-optimization does the following:
Checks if the chosen PSC for the Small Cell is optimum or conflicting with
neighboring Small Cells.
Detects changes in the 2G and 3G macro neighboring cells and updates the detected
3G and 2G macro neighbor cell list for broadcast in SIB11 and determines the best
target cell for handover.
Measures the strength of neighboring cells in order to control the coverage by
optimizing CPICH transmit power.
Self-optimization is run once a day in a quiet period. See the Quiet Period topic (Chapter
5) for more information on how quiet period is determined. Once in the quiet period,
normal operation is suspended and the Small Cell reverts to network listening mode and
measurements are obtained through 3G network listening (see Chapter 5) and 2G network
listening (see Chapter 6).
If 2G network listening (HiLo) is configured, then 2G measurements are made
periodically. The periods are determined by gsmListeningPeriodicTimer.
During operation, the Small Cell continues to instruct connected UEs to perform
measurements on the surrounding neighbor cells and uses this to optimize its CPICH
transmit power.
Feature benefits
The self-optimization procedure is a key feature that maintains the Small Cell at the
optimal working point, guaranteeing residential service coverage while minimizing
interference with macro cells and other Small Cells.
Impacted systems
Small Cell.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
4-2
Issue 1 March 2013
....................................................................................................................................................................................................................................
Dependencies
2G network listening.
3G network listening.
None
Engineering impacts
None
None
Feature type
Basic
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
4-3
Issue 1 March 2013
....................................................................................................................................................................................................................................
Small Cell primary scrambling code optimization
Self-optimization checks that the chosen PSC for the Small Cell is not in conflict with
any surrounding Small Cell, which may have been added since its last self-optimization.
3G network listening is used to search for and measure the PSCs reserved for the Small
Cell. Self-optimization changes the PSC if necessary. See Chapter 6 for details on PSC
selection.
Neighbor list optimization
A list of the detected 3G and 2G neighbor cells, umtsMacroNCell and gsmMacroNCell is

maintained in the Small Cell. During self-optimization these lists are checked and
updated by the 3G and 2G network listening functions (see Chapters 5 and 6). If changes
are found, then a new list of neighbor cells is broadcast in SIB11 and the target cell(s) for
hand-over are re-calculated.
Coverage control and optimization
The Small Cell performs the following self-optimization procedures:

1. There are two methods of detecting whether the CPICH TX power needs to increase
or decrease:
a. When there are UEs in Cell DCH with active calls established, coverage is
maintained based on the UE measurement of the serving Small Cell CPICH
Ec/No.
Increase the CPICH TX power if serving Small Cell CPICH Ec/No is less than the
predefined threshold or a neighbor cell CPICH Ec/No.
b. When there is no UE in cell DCH, coverage is optimized based on RSSI
measurement (the same method as for auto-configuration).
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
4-4
Issue 1 March 2013
....................................................................................................................................................................................................................................
For information on parameters, refer to:
Chapter 5 3G network listening
Chapter 6 2G network listening
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
4-5
Issue 1 March 2013
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
4-6
Issue 1 March 2013
5
Overview
Purpose
This chapter describes the 3G network listening (34537) feature.

Contents
5-2
3G network listening functions
5-3
5-4
Quiet period
5-5
Network listening parameters
5-6
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
5-1
Issue 1 March 2013
....................................................................................................................................................................................................................................
Feature number

Feature description
The 3G Network Listening feature allows the Small Cell to act as a UE and receive
transmission from neighboring base stations.
The feature also allows the Small Cell to automatically identify, measure and record its
neighbor UMTS cells without the need for operator provisioned neighbor cell lists. This
information is used by the Small Cell to automatically select its primary scrambling code
and power levels to transmit and to create and update a list of UMTS neighbor cells.
This neighbor cell list is used by the Small Cell, when in base station mode, for
identification of the target cell for UMTS handover and rebroadcast in the system
information messages, in support of reselection by the UE.
Feature benefits
Provides the Small Cell with a means to identify neighboring UMTS cells for use in the
auto-configuration and self-optimization processes. It guarantees efficient configuration
for an optimal level of performance.
Impacted systems
Small Cell, SCMS.

Restriction/Limitation
The 3G network listening is always enabled. The PSC for the Small Cell is selected from
a list. The PSC and default PSC is no longer supported.
Feature type
Basic.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
5-2
Issue 1 March 2013
....................................................................................................................................................................................................................................

Receive mode
3G network listening is the capability of the Small Cell to switch to a UE mode with
receive only capability. When in this mode the Small Cell no longer acts as a base station
and cannot transmit.
3G network listening is used by the Small Cell to automatically detect its neighboring
cells in the Small Cells Cluster and the macro network.
3G network listening runs at power on, reset, and then once a day during a quiet period
when there are no active calls. The Small Cell can be configured to allow 3G network
listening to be run during the quiet period when there is an active PS call if 3G network
listening has not run for a period, and in this case, 3G network listening preempts the PS
call.
Functions
When in network listening mode, the functions provided are:
Cell Search
The ability to search for a 3G cell either on the same frequency (intra) or different
frequency (inter).
BCH Decode
Once a cell is found, the ability to access the broadcast channel from a base station in
order to decode the System Information Messages (SIB) broadcast.
These functions are used to:
Create and update the W-CDMA detected cell lists

Determine the target cell for W-CDMA handover
Detect neighboring Small Cells and select its own PSC
Receive details of inter-RAT neighbors (2G) which can be rebroadcast to assist UE in
reselection
Determine a 3G RF fingerprint for use in the location detection procedure of the

Small Cell
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
5-3
Issue 1 March 2013
....................................................................................................................................................................................................................................

Macro neighbor cell detection
During each running of 3G network listening the Small Cell searches for, measures the
strength and decodes the broadcast channel of neighboring UMTS macro cells and stores
them in umtsMacroNCell. Cells can be from the Small Cells own frequency (Intra) or
from other frequency (Inter), as configured in macroUmtsCellFrequencyList.
The search starts from the cells already detected in umtsMacroNCell (if available) and
FDDExtCell (if provided by the operator). The search terminates when sufficient cells (a
percentage of cells, ratioMacroCellBelowThreshold, out of a number of cells
gsmCelllistSIB11) over the configured threshold (macroCellRSCPThreshold and
macroCellEcNoThreshold) have been found.
If sufficient cells are not found or FDDExtCell and umtsMacroNCell are empty, then if
enabled (umtsOpenSearchEnableFlag) an open search is run across all configured
frequencies. If cells are marked by the operator as disallowed, then they are not
considered in the search.
The list of detected cells is ranked in terms of strength to determine the target cells for
handover and is used by the location detection (34588) and National location lock
(78230) features.
PSC selection
strength and decodes the broadcast channel for neighboring Small Cells from the list of
reserved PSCs provided, femtoPSClist. Details of the neighboring Small Cells are stored
in umtsFemtoNCell.
If configured for manual selection of PSC, isAutoPscConfigEnabled, then the Small Cell's
PSC is chosen from manualPscForFemto otherwise automatic selection takes place and
the Small Cell either selects an unused PSC or continues to use its own PSC already
assigned.
If all reserved PSCs are in use by neighboring Small Cells, then the PSC with the lowest
strength is selected and in this case a minor fault is raised, allReservedFemtoCellsInUse.
The use of a default PSC is no longer required and use of a range of PSCs is discontinued.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
5-4
Issue 1 March 2013
Quiet period
....................................................................................................................................................................................................................................
Quiet period
Description
Following a power on or reset during which 3G and 2G network listening are run, 3G
network listening and 2G network listening if Mode 2 is enabled, are run again once a day
during a quiet period. In order to determine the quiet period, the Small Cell records the
number of active calls during each hour of the day in the parameter busyHourLogger.
This builds up, over time, a picture of usage and allows the Small Cell to select a
non-busy hour once a day for 2G and 3G network listening. This is defined in the
parameter quietPeriod.
During the non-busy hour, the Small Cell randomly selects a minute at which to start the
activation period, activationIinterval. At any time within that activation window, if there
are no active calls in progress, the Small Cell turns off transmission and enters network
listening mode. The minute chosen is randomized, to try to prevent an adjacent Small Cell
from entering network listening at the same time. There is also a configuration option
that, if after a configurable number of times, selfOptMissedCount, the period is still found
to be busy, then the Small Cell clears PS calls to enable network listening.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
5-5
Issue 1 March 2013
....................................................................................................................................................................................................................................

Attributes of class BSR: 3G network listening
Parameter
Description
Syntax
Values
Specifies the period within the

quiet period when
self-optimization can run.
uint16
[1..60], unit=mins
selfOptMissedCount 1
Specifies the number of

sequential times that
self-optimization can be
missed before PS calls can be
preempted at the end of the
activation period.
uint16
[0..100]
busyHourLogger 1
Read only parameter

specifying the contents of the
busy hour logger for each hour
of the day, in local time.

BusyHourLogger
quietPeriod 1
Read only parameter indicating

the quiet period specified in
local time.
uint16
[0..23]
umtsNtwkListenEnableFlag
Indicates whether network

listening is supported instead
of the UE measurement
approach.
boolean
Constrained:
TRUE only.
activationInterval
If set to true, then network

listening is supported instead
of the UE measurement
approach.
umtsOpenSearchEnableFlag
Indicates whether a search for

UMTS cells should be
performed.
boolean
If set to true, then a search for

UMTS cells outside the
externally supplied list is
undertaken during
auto-configuration or
self-optimization when
network listening is enabled.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
5-6
Issue 1 March 2013
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
femtoPSCListEnableFlag
Determines whether the Small

Cell uses a list or a range for
the reserved PSCs.
boolean
Constrained:
TRUE only.
boolean
Constrained:
TRUE only.
When set to true a list is used.

defaultPSCEnableFlag
Indicates whether a default

Small Cell PSC should be
reserved.
If set to true, a default Small
Cell PSC is reserved.
femtoPSCList
Provides a list of primary

scrambling codes reserved for
SSmall Cells, one of which is
indicated as the default PSC.

FemtoPSC
netkListGuardConfigTimer
Before 3G network listening

can run, the PicoChip baseband
processor must be
re-programed with the 3G
network listening software
changing its function from 3G
base station mode to 3G
terminal mode.
uint16
[0..60000],
unit=ms
This attribute guards the time it

takes the PicoChip array to
re-program itself and then
come up in 3G network
listening mode.
bCHDecodeGuardTimer
This attribute is a guard timer

which bounds the BCH decode
function on the PicoChip
network listening PC8210.
uint16
[2..20], unit=secs
cellSearchGuardTimer
This attribute is a guard timer

which bounds the cell search
function on the PicoChip
network listening PC8210.
uint16
[1..10], unit=mins
Notes:
1.
Attribute applicable to 2G and 3G network listening, and used in determining and running the quiet period
for self-optimization.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
5-7
Issue 1 March 2013
....................................................................................................................................................................................................................................
Attributes of class LCell: 3G network listening

Parameter
Description
Syntax
Values
macroCellRSCPThreshold
Specifies the CPICH RSCP

threshold below which macro
cell optimization must be
performed.
integer
[-116..-25],
unit=dBm
macroCellEcNoThreshold
Specifies the CPICH Ec/No

threshold below which macro
cell optimization must be
performed.
integer
[-25..0], unit=dB
isAutoPscConfigEnabled
Indicates how PSC is

determined.
boolean
If set to TRUE, the Small Cell

automatically determines its
PSC. If set to FALSE, the
Small Cell uses the PSC
applied by the operator in
parameter manualPscForFemto.
manualPscForFemto
Specifies the Primary

Scrambling Code/Primary
CPICH scrambling code,
which is configured by the
operator when
isAutoPscConfigEnabled is set
to FALSE.
integer
(0..511)
primaryScramblingCode
Specifies the Primary

Scrambling Code/Primary
CPICH scrambling code,
which the Small Cell has
applied.
integer
(0..511)
macroCellListSIB11
Specifies the number of macro

UMTS cells in SIB 11.
integer
[1..32]
ratioMacroCellBelowThreshold
Specifies the ratio of the

number of macro cells to the
number of macro cell detected
that are above the
Lcell:macroCellRSCPThreshold. Note: The name should be
above not below.
real
[0.0..1.0],
precision=1,
step=0.1
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
5-8
Issue 1 March 2013
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
macroUMTSCellFrequencyList
Specifies the list of macro cell

UMTS neighbor cell
frequencies.

Frequency
ownPLMNMNC

code of the PLMN the Small
Cell belongs to. It is part of the
PLMN identity broadcast in
the Master Information Block.
string
length=3
ownPLMNMCC

code of the PLMN the Small
Cell belongs to. It is part of the
PLMN identity broadcast in
the Master Information Block.
string
length=3
umtsMacroNCell
UMTS macro neighbor cell list

generated by the
auto-configuration/selfoptimization function of the
Small Cell.

UmtsMacroNCell
umtsFemtoNCell
Small Cell neighbor cell list

generated by the
auto-configuration/selfoptimization function of the
Small Cell.

UmtsFemtoNCell
Attributes of class FddExtCell: Auto-configuration (initial UMTS neighbor cell list)

Parameter
Description
Syntax
Values
primaryCPICHInfo

downlink radio link.
integer
(0..511)
primaryCPICHTxPower
Specifies the power in dBm.
real
(-10.0..50.0),
step=0.1,
precision=1,
unit=dBm
uARFCNDownlink
Specifies the downlink

ARFCN of the cell.
integer
(0 .. 16383)
uARFCN
Specifies the uplink ARFCN of

the cell (UARFCNDownlink +
integer
(0 .. 16383)
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
5-9
Issue 1 March 2013
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
rAC

integer
(0..255)
lAC

integer
(1..65535)
mCC

code.
string
length=3
mNC

code.
string
length=3
rNCID
Specifies the identity of the

RNC to which this cell is
connected.
integer
(0..4095)
fddFreqBand
Specifies the frequency band

which is supported by the
enum FDDRadioFrequencyBand
cellIdentity

within a PLMN.
integer
notAllowedCell
Specifies that this cell is not

eligible for cell reselection and
handover.
boolean
(0..65535)
Global definitions: UmtsMacroNCell

Type
Parameter
Description
Syntax
Values
UmtsMacroNCell
primaryCPICHInfo

downlink radio link. A
value of -1 to indicate
that the PSC is
unknown.
integer
(0..511)
UmtsMacroNCell
fddFreqBand
Specifies the frequency

band, which is
supported by the
enum
FDDRadioFrequencyBand
UmtsMacroNCell
uARFCNDownlink
Specifies the Downlink

ARFCN of the cell
integer
(0 .. 16383)
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
5-10
Issue 1 March 2013
....................................................................................................................................................................................................................................
Type
Parameter
Description
Syntax
Values
UmtsMacroNCell
uARFCNUplink
Specifies the Uplink

ARFCN of the cell.
integer
(0 .. 16383)
(UARFCNDownlink +
UmtsMacroNCell
rAC
Specifies the routing

area code of the
neighbor cell.
integer
(0..255)
UmtsMacroNCell
lAC
Specifies the location

area code of the
neighbor cell.
integer
(0..65534)
UmtsMacroNCell
mCC
Specifies the mobile

country code.
string
length=3
UmtsMacroNCell
mNC

network code.
string
length=3
UmtsMacroNCell
rNCID
Specifies the identity of

the RNC to which this
cell is connected.
integer
(0..4095)
UmtsMacroNCell
cellIdentity
Identifies a cell
unambiguously within a
PLMN.
integer
(0..65535)
UmtsMacroNCell
freqType
Defines whether the

neighbor cell is an
intra-frequency or
inter-frequency
neighbor cell.
enum
FrequencyType
UmtsMacroNCell
cPICHRSCP
Specifies the measured

CPICH RSCP of the
neighbor cell. Mapping
between the value and
the real RSCP value is
given in TS25.133
Section 9.1.1.3.
integer
(0..91)
UmtsMacroNCell
cPICHEcNo

CPICH Ec/No of the
neighbor cell. Mapping
between the value and
the real RSCP value is
given in TS25.133
Section 9.1.2.3.
integer
(0..49)
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
5-11
Issue 1 March 2013
....................................................................................................................................................................................................................................
Type
Parameter
Description
Syntax
UmtsMacroNCell
cellInfoComplete
There are different

options of how the
neighbor cells can be
determined, for
example, from OA&M
configuration,
auto-configuration,
self-optimization or
sniffer functions.
boolean
Values
Some of these functions

are not able to provide
all of the data that is
required for handover,
for example, parameters
such as rAC, lAC, mCC,
mNC, rNCID and
cellIdentity.
This parameter
identifies if all the data
is available or whether
some data is missing. A
neighbor cell set as
FALSE is not
considered for handover.
UmtsMacroNCell
hcsPrioN
Contains the HCS

priority level for the
detected or provisioned
UMTS macro cells.
integer
(0..255)
HCS priority level 0 =

lowest priority, HCS
priority level 7 = highest
priority. HCS priority >
7 indicates that no HCS
priority is assigned.
For definitions of type umtsFemtoNCell, see the Small Cell Group Support chapter in
Alcatel-Lucent 9365 Base Station Router Small Cell Specific Features System Definition
Specification, 9YZ-04190-0005-DSZZA.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
5-12
Issue 1 March 2013
6
Overview
Purpose
This chapter describes the following features:
2G network listening Hilo based (36255)

2G network listening embedded (75888)
Contents
6-2
6-3
6-6
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
6-1
Issue 1 March 2013
....................................................................................................................................................................................................................................
Feature number
Feature number 36255 and 75888.

Feature description
The Small Cell supports a GSM receiver chain and can therefore receive the signal
transmitted by the 2G Macro network. The Small Cell can search for and sync to a macro
base station, and then decode the BCCH channel. It can then retrieve the relevant
information to build and maintain 2G neighbor lists and target cells for IRAT handover
and later, when in base station mode, to broadcast to the UE for cell reselection.
Measurements and information are provided by the network listening feature to the
auto-configuration and self-optimization functions.
Feature benefits
This feature simplifies the procedure for building the GSM neighbor list and target cells
for handover. This data can be autonomously determined by the Small Cell without
relying on the exchanges between the SCMS, Small Cell and existing macro OAM
solution.
In addition, in the case of poor or no 3G coverage, the 2G network listening capability
performs the following functions:
guarantee of the proper configuration for 2G handover

efficient update in case of a new frequency planning of the macro layer.
Impacted systems
Small Cell, SCMS.

This feature is supported in the 900/1800MHz band only.

The 2G Network Listening Hilo based feature (36255) only runs on V1 Small Cell
hardware that is fitted with the Hilo module.
The 2G Network Listening embedded feature (75888) runs on post V1 Small Cell
hardware, that is, V1.2 Small Cell and future boards.
Feature type
Optional
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
6-2
Issue 1 March 2013
....................................................................................................................................................................................................................................

2G network listening provides the Small Cell with the ability to listen to neighboring
GSM cells in the same manner as a UE. 2G network listening allows the Small Cell to
search for, measure the strength of and decode the BCCH channel of neighboring 2G
cells.
2G network listening runs at power on and following a reset and either periodically (HiLo
based only) or together with 3G listening in a quiet period. The information gathered by
2G network listening is used by the auto-configuration (34535), self-optimization (34536)
and national location lock (78230) features.
Two forms of 2G network listening on the Small Cell are provided, depending on the
hardware base:
2G network listening Hilo based (36255)
2G network listening embedded (75888)
Both forms of 2G network listening have the same functionality but are driven from a
different set of parameters.
2G network listening Hilo based
2G network listening (Hilo based) is provided on V1 hardware, V1 Small Cell and is

delivered through an optional 2G receiver module. This is a self-contained GSM quad
band module, named HiLo, from Sagem Communications. This module is added to the
Small Cell board, as an optional, factory-fitted feature. If the module is not fitted, then 2G
network listening is not run.
gsmListeningMode controls the modes of operation of the HiLo based option.
Modes of operation
Mode
Description
2G listening is not enabled.
2G listening is run at power on and reset, and

then at regular intervals determined by the
timer gsmListeningPeriodicTimer. In this
mode 2G listening can run while normal 3G
operation is in progress.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
6-3
Issue 1 March 2013
....................................................................................................................................................................................................................................
Mode
Description
2G listening is run at power on and reset, and

once a day during the quiet period (described
in the 3G network listening section) alongside
3G network listening but not simultaneously.
In this mode 2G network listening does not
run while 3G operation or 3G network
listening is in progress.
2G network listening embedded
2G network listening (embedded) is provided on V1.2 and future hardware. In this form,
the 2G receive chain and 2G network listening is embedded on the board and in the
baseband component. No additional module is required.
2G network listening is enabled through parameter, gsmListenerPicoBasedEnabled. 2G
network listening embedded works in a similar way to 3G network listening and before
operable the baseband needs to be reprogrammed. netkListGuardConfigTimer (see 3G
network listening chapter) bounds this re-programming. When in this mode, 3G operation
or 3G network listening is not operational.
2G neighbor cell detection
strength and decodes the broadcast channel of neighboring 2G macro cells and stores
them in gsmMacroNCell. gsmFrequencyList determines which GSM bands and
frequencies are searched.
The search starts from the cells already detected in gsmMacroNCell (if available) and
gsmExtCell (if provided by the operator) and search terminates when sufficient cells (a
percentage of cells, ratioGSMCellAboveThreshold, out of a number of cells
gsmCelllistSIB11) over the configured threshold (gsmCellRSSIthreshold) have been
found.
If sufficient cells are not found or gsmExtCell and gsmMacroNCell are empty, then if
enabled (gsmOpenSearchEnableFlag) an open search is run across all configured
frequencies. If cells are marked by the operators as disallowed then are not considered in
the search.
The list of detected cells is ranked in terms of strength to determine the target cells for
handover and is used by auto-configuration (34535), self-optimzation (34536) and
national location lock (78230) features.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
6-4
Issue 1 March 2013
....................................................................................................................................................................................................................................
Quiet period
See Quiet period topic (Chapter 5) for more information.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
6-5
Issue 1 March 2013
....................................................................................................................................................................................................................................

Attributes of class BSR: 2G network listening
Parameter
Description
Syntax
Values
Specifies the period within the

quiet period when
self-optimization can run.
uint16
[1..60], unit=mins
selfOptMissedCount 1

sequential times that
self-optimization can be
missed before PS calls can be
preempted at the end of
activation period.
uint16
[0..100]
busyHourLogger 1
Specifies an array to record the

number of active calls per hour
in the day.

BusyHourLogger
activationInterval
Notes:
1.
Attribute also applicable to 3G network listening.
2.
For the quietPeriod parameter, see Network listening parameters (p. 5-6)
Common attributes
Attributes of class GSMListener:

Parameter
Description
Syntax
Values
gsmMacroPLMN
Mobile country code and

mobile network code of the
GSM macro PLMN.

GSMPLMN
Global definitions:
Type
Parameter
Description
Syntax
Values
gsmMacroNCell
nCC
Specifies the Network

Colour Code, part of the
Base Transceiver
Station Identity Code
(BSIC).
integer
(0..7)
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
6-6
Issue 1 March 2013
....................................................................................................................................................................................................................................
Type
Parameter
Description
Syntax
Values
gsmMacroNCell
bCC
Specifies the Base

Station Colour Code,
part of the Base
transceiver Station
Identity Code (BSIC).
integer
(0..7)
gsmMacroNCell
gsmFrequBand
Specifies the operating

frequency band of the
GSM cell.
Recommending values:
enum
GSMFrequencyBand
gSM1900 for GSM

ExtCells. Frequency
band is GSM1900.
gSM1800 for all other
frequency bands.
gsmMacroNCell
bCCHArfcn
BCCH Arfcn
integer
(0..1023)
gsmMacroNCell
rAC

area code of the
neighbor cell.
integer
(0..255)
gsmMacroNCell
lAC

area code of the
neighbor cell.
integer
(1..65535)
gsmMacroNCell
mCC

country code.
string
length=3
gsmMacroNCell
mNC

network code.
string
length=3
gsmMacroNCell
cellIdentity
Identifies a cell
unambiguously within
an LA.
integer
(0..65535)
gsmMacroNCell
bCCHRSSI
Specifies the
BCCH/GSM carrier
RSSI of the GSM cell.
integer
(0..63)
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
6-7
Issue 1 March 2013
....................................................................................................................................................................................................................................
Type
Parameter
Description
Syntax
gsmMacroNCell
cellInfoComplete
There are different

options to determine the
neighbor cells, for
example, from OA&M
configuration,
auto-configuration,
self-optimization or
sniffer function.
boolean
Values
Some of these functions

do not provide all the
data that is required for
handover, for example,
parameters such as lAC,
mCC, mNC and
cellIdentity.
This parameter
identifies, if all the data
is available or some data
is missing. A neighbor
that is set to FALSE is
not considered for
handover.
Attributes of class LCell:

Parameter
Description
Syntax
Values
gsmcellRSSIThreshold
Indicates the RSSI threshold

below which open scan needs
to be performed
integer
[1..32]
ratioGSMCell
AboveThreshold
Indicates the ratio of the

number of macro cells out of
the number of macro cell
detected that are above the
gsmcellRSSIThreshold.
real
[0.0..1.0],
precision=1,
step=0.1
gsmCellListSIB11

GSM cells in SIB 11.
integer
[1..32]
allowedGSMOpenSearch
Specifies whether to perform

GSM open search.
boolean
gsmFrequencyList
Specifies the GSM frequency

list.

GSMFrequencyList
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
6-8
Issue 1 March 2013
....................................................................................................................................................................................................................................
For initial 2G macro cell list attributes, refer to the Auto-configuration parameters section.
Hilo specific parameters
Attributes of class GSMListener:

Parameter
Description
Syntax
gsmListeningMode
Mode of operation for 2G

Listening:
enum GsmListeningMode
Mode0 = 2G listening not

enabled
Mode1 = simultaneous
2G/3G
Mode2 = singular no 3G
Values
gsmListeningPeriodicTimer
Specifies the time between

self-optimization runs for 2G
when mode 1 is selected.
integer
[0..10000],
unit=mins
gsmModuleInitGuardTimer
Specifies the 2G module

initialization guard timer for
the HiLo module.
integer
[0..500], unit=secs
gsmATCmdGuardTimer
Specifies the guard timer for

AT commands to HiLo
module.
integer
[0..10000],unit=ms
gsmModuleErrorRepeat
Specifies the number of times

the HiLo module repeats a
command or power cycle due
to a failure.
integer
[0..5]
powerOnStablisationTime
Specifies the time to stabilize

the power at the HiLo module
before POK_IN is asserted.
integer
[0..1000], unit=ms
Values
Embedded specific attributes
Attributes of class BSR:

Parameter
Description
Syntax
gsmListenerPicoBasedEnabled
Enables/Disables the 2G
network listening function
based on PicoChip 2G network
listening software (PC8211).
boolean
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
6-9
Issue 1 March 2013
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
gsmBCCHDecodeGuardTimer
Guard timer bounding the

BCCH decode function on the
PicoChip 2G network listening
PC8211.
uint16
[500..6000],
unit=ms
gsmCellSearchGuardTimer
Guard timer bounding the Cell

Search function on the
PicoChip 2G network listening
PC8211.
uint16
[60..1000],
unit=ms
gsmMeasurementPeriod
Specifies the GSM RSSI

measurement period.
uint16
[5..300], unit=ms
Attributes of class LCell:

Parameter
Description
Syntax
Values
minGSMDetectThreshold
Specifies the minimum RRSI

strength (dBm) for a GSM cell
to allow a cell search to take
place.
integer
[-110..-48],
unit=dBm
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
6-10
Issue 1 March 2013
7 ccess control list

A
administration
Overview
Purpose
This chapter describes the access control list administration (34538) feature.
Contents
7-2
Updating the ACL
7-4
ACL use case
7-5
ACL parameters
7-8
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
7-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number

Feature description
The SCMS supports a set of web-based APIs, to exchange provisioning data related to the
Small Cell-specific access control list (ACL).
APIs that are related to management of the ACL include:
Get the current ACL (provide latest Small Cell list)

Set the ACL (for a specific Small Cell)
The following diagram shows an example of an access control list administration task
add a new UE:
The ACL can have up to 32 entries.

Feature benefits
This feature enables full usage of the access restriction capability of the Small Cell
solution by providing end users with the ability to control the list of authorized users on
their own Small Cell.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
7-2
Issue 1 March 2013
....................................................................................................................................................................................................................................
Impacted systems
SCMS
Dependencies
IT system
None
Engineering impacts
None
None
Feature type
Basic
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
7-3
Issue 1 March 2013
Updating the ACL
....................................................................................................................................................................................................................................
Updating the ACL

Subscriber registration and access restriction
The home subscriber is limited in the number of UEs that may be registered as authorized
to use the home cell. The registered UEs are kept in an 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 operator.
Updating the ACL
The subscriber can update their ACL by accessing a customer system via a well known
URL, for example, https://www.customercenter.com.
Using web access to the customer system, the subscriber can modify the ACL for their
Small Cell, in order to allow different IMSIs access to this Small Cell.
The customer system has a profile for each subscriber with a predefined username and
password, which is needed for the login. Up to 32 IMSIs can be added to the ACL for a
Small Cell.
Customer system
The customer system updates the HDM through a web based API. The web based API,
which is part of the HDM, offers a well-known URL, including all needed parameters, to
be used by the external customer system.
IMSI list
The full IMSI list is sent to the Small Cell every time there is any sort of update. The
ACL of the subscriber is kept on the customer system.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
7-4
Issue 1 March 2013
ACL use case
....................................................................................................................................................................................................................................
ACL use case

Preconditions
The following preconditions apply to the successful update of an ACL:
Subscriber has access to a web based customer system.

The IMSI of the owner is stored at the first position of the ACL list, and the customer
system does not permit the subscriber to remove this first entry from the list.
The customer system validates that the ACL size does not exceed 32 IMSIs and all
IMSIs are 15 digits.
The customer system is responsible for implementing other policies such as, for
example, barring prepaid SIMs, or mobiles where no non-roaming agreement exists.
Successful end condition
The following items indicate that an ACL has been successfully updated:
Customer system, HDM, Small Cell and BSG are updated with new ACL.
IMSIs are added to, or removed from, the ACL of the customer system, HDM, Small
Cell and BSG.
Failure end condition
Customer system, HDM, Small Cell and BSG are not updated with the latest ACL.
Use case diagram
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
7-5
Issue 1 March 2013
ACL use case
....................................................................................................................................................................................................................................
Main success scenario
The following steps depict a successful update of an ACL:

1. The subscriber accesses the customer system with his username and password
2. The subscriber updates the ACL through a customer system, adding or removing
MSISDNs.
3. The customer system converts the MSISDNs into IMSIs and exports the updated list
to the web based API of the HDM. The URL to the HDM-API may be similar to:
http://<ip_machine>:8443/ACLOperations/addListToACL?femtoACLlist=<newIMSiList>&
fBSRSerialNumber=<femtoBSR_SerialNumber>
4. The HDM updates the userTag of the subscriber information. This allows the ACL to
persist if a factory reset of the Small Cell occurs.
5. The HDM updates the Small Cell with the latest modified ACL using the TR69 Set
Parameter Value command.
6. The Small Cell triggers an update of the ACL towards the BSG (may be done
asynchronously).
7. The ACL of the HDM, the Small Cell and the BSG are in sync.
8. The HDM sends a success message towards the customer system, that all NEs are in
sync.
Note: The customer system is the master. In case of any link interruptions towards the
HDM or Small Cell, the customer system periodically triggers an update of the ACL
towards the HDM, Small Cell, and BSG until all the NEs are in sync. The Small Cell
-BSG trigger may occur asynchronously.
Failure causes
Failure causes while retrieving all MSISDNS from the ACL:
Other exceptions generated by the application.
Failure causes while adding a new list of MSISDNs to the ACL:
The new IMSI List contains a value that exceeds 15 characters

The new Small Cell ACL list is empty
The modified Small Cell ACL list exceeds 32 MSISDNs
The userTag update fails

The Small Cell cannot connect to the BSG to propagate the ACL update
Other exceptions generated by the application
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
7-6
Issue 1 March 2013
ACL use case
....................................................................................................................................................................................................................................
Sequence diagram
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
7-7
Issue 1 March 2013
ACL parameters
....................................................................................................................................................................................................................................
ACL parameters
Attributes of class BSR: ACL
Parameter
Description
Syntax
Values
femtoACLlist
Specifies the list of IMSIs

resources, within closed access
operation mode. The ACL is
defined as a NULL terminated
string with comma-separated
IMSI values.
string
length=600
femtoACLenable
Indicates whether to enable or

disable the ACL, in order to
validate UEs that could use
Small Cell.
boolean
A Small Cells Cluster operates

in either closed or open access
mode.
If the Small Cells Cluster
operates in closed access
mode, this attribute has to be
set to true.
If the Small Cells Cluster
operates in open access mode,
this attribute has to be set to
false.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
7-8
Issue 1 March 2013
8 utomatic fallback to
A
macro in case of failure in
core
Overview
Purpose
This chapter describes the automatic fallback to macro in case of failure in core (34539)
feature.
Contents
8-2
SCTP association
8-4
Automatic fallback to macro network in case of failure parameters
8-5
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
8-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number

Feature description
This feature allows the Small Cell to automatically shutdown its power amplifier (PA) if
the DSL link fails.
Without this feature, a DSL link failure would cause the loss of all signaling and user
plane links and other logical links, resulting in the dropping of existing calls and
potentially the isolation of a UE that cannot be paged.
Implementation is based on the Stream Control Transmission Protocol (SCTP) association
with the BSG (or rather, the loss of connectivity to the BSG).
When the PA is off, any UE previously attached to the Small Cell reselects the macro
layer if visible.
Feature benefits
This feature ensures consistent service and minimizes loss of quality if a connectivity
failure occurs between the Small Cell and the Small Cell Gateways due to an unreliable
DSL line.
Impacted systems
Small Cell
Dependencies
IT system
None
Engineering impacts
Periodic planned DSL interruptions need to be considered in the configuration of

heartbeat timers and counters.
None
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
8-2
Issue 1 March 2013
....................................................................................................................................................................................................................................
Feature type
Basic
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
8-3
Issue 1 March 2013
SCTP association
....................................................................................................................................................................................................................................
SCTP association
SCTP associations
The Small Cell support the configuration of SCTP associations. This allows
inter-operation with the BSG.
The SCTP has a keep alive timer (hbTimeout x maxAttempts). When the keep alive timer
expires, the Admin State/Op State of the SCTPAssoc managed object makes the transition
from Unlock/Enabled to Unlock/Disabled, the Small Cell detects a failure of the link to
the BSG. The Small Cell then performs the following actions:
Perform Iu Release Request

Perform RRC Connection Release procedure
Release SCTP association with the BSG
Disable the cell

Switch off the PA
When the Admin State/Op State of the SCTPAssoc managed object makes the transition
from Unlock/Disabled to Unlock/Enabled, the Small Cell performs the following actions:
Perform BSG registration

Enable the cell
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
8-4
Issue 1 March 2013
Automatic fallback to macro network in case of failure

parameters
....................................................................................................................................................................................................................................

parameters
Attributes of class SCTPASSOC: Automatic fallback
Parameter
Description
Syntax
maxInstream
Specifies the maximum

number of incoming stream.
integer
numOutStreams

outgoing streams.
integer
maxAttempts

number of SCTP connection
attempts after the association
goes down.
uint16
cookieLife
Specifies the cookie life in

seconds.
integer
hbOn
Indicates the turn on the SCTP

heartbeat.
boolean
initTimeout
Specifies the SCTP Init

Timeout in milliseconds.
integer
hbTimeout
Specifies the SCTP Heartbeat

Timeout in milliseconds.
integer
qosMapping
Specifies the DSCP value for

IP transport for all signaling
streams contained in this
association. On aSmall Cell
these are the IuCSPrime
signaling, IuPSPrime signaling
and BSG application.
enum DSCPClass
Values
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
8-5
Issue 1 March 2013

parameters
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
8-6
Issue 1 March 2013
NAT traversal
9
Overview
Purpose
This chapter describes the NAT traversal (34587) feature.

Contents
NAT traversal
9-2
NAT traversal on the Small Cell
9-4
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
9-1
Issue 1 March 2013
NAT traversal
NAT traversal
....................................................................................................................................................................................................................................
NAT traversal
Feature number

Feature description
The Small Cell uses a Network Address Translation (NAT) device for reuse of IP
addresses. This device performs NAT between the private Small Cell address and the
public address of the NAT device. This translation allows private IP addresses of Small
Cells to be reused on other home locations.
The IPSec tunnel between the Small Cell and the IPSec router supports IPSec IKEv2
NAT traversal.
The Small Cell supports IPsec IKE v2. The IKE protocol is responsible for setting up the
IPsec tunnel, and IKE v2 is required to support NAT traversal.
For NAT traversal the IPSec packets are UDP encapsulated/decapsulated for proper
functioning, as per RFC 3948/RFC 4306. The IPSec router supports a configurable value
for the UDP port number used in the RFC 4306 procedures. The UDP port configuration
is done via the OAM interface. All Small Cell clients use the same configured port
number.
Feature benefits
NAT traversal provides a solution to the problems inherent in using IPSec with NAT.
Impacted systems
Small Cell, IPSec router

Dependencies
None
None
Engineering impacts
None
None
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
9-2
Issue 1 March 2013
NAT traversal
NAT traversal
....................................................................................................................................................................................................................................
Feature type
Basic
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
9-3
Issue 1 March 2013
NAT traversal
....................................................................................................................................................................................................................................

Overview
The term NAT refers to network address translation involving the mapping of port
numbers, that is, network address port translation or (NAPT). NAT is widely used in
commercial routers and helps to reuse private IP addresses, especially for the limited
address space of IPV4, and is specified in RFC3022.
NAT allows Small Cell and other home network hosts to share the same public IP address.
The local private address of any of the home network hosts is locally assigned by OA&M
or DHCP.
Several NAT functions may be available in the Small Cell backhaul:
A local DSL router device and/or
A NAT function inside the DSL domain
The following figure gives an overview of the NAT traversal path and address naming:
A NAT device can transparently and automatically modify the source address and port
number belonging to the Small Cell. Small Cell backhaul only uses source address and
source port translation. For example, a local home DSL router may recover during normal
operation of the Small Cell.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
9-4
Issue 1 March 2013
NAT traversal
....................................................................................................................................................................................................................................
In addition to standard NAT (RFC3022), the Small Cell network includes the following
Small Cell proprietary address translation functions:
BSR Voice Gateway (BVG)

BSR Packet Gateway (BPG)
Supported NAT types
The following NAT types supported on the Small Cell transport network:
Port restricted cone NAT

Symmetric NAT
Port restricted cone NAT
With port restricted cone NAT, all requests from the same Small Cell address and port are
mapped to a unique external source IP address and port. The mapping is independent of
the destination address and port. An external host can send a packet to a particular port on
the Small Cell, only if the Small Cell had previously sent a packet from that port to the
external host.
Symmetric NAT
With symmetric NAT, all requests from the same Small Cell address and port to a specific
destination IP address and port are mapped to a unique external source IP address and
port. If the same Small Cell address, sends a packet with the same source address and port
to a different destination, a different mapping is used. Only an external host that receives
a packet can send a UDP packet back to the Small Cell.
Small Cell logical links and NAT traversal
The Small Cell supports a large number of logical links for the user plane, control plane,
management plane and other transport services. All logical interfaces are carried in the
IPSec tunnel.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
9-5
Issue 1 March 2013
NAT traversal
....................................................................................................................................................................................................................................
NAT traversal for secure logical interfaces
The Small Cell supports IPSec on the following logical interfaces on Small Cell:
All these logical interfaces use a common IPSec stack. This is either IP/ESP/UDP/IP/ETH
or IP/ESP/IP/ETH, depending on whether or not NAT is detected.
Support for NAT traversal incurs additional overhead for SSH and SFTP. For security
reasons, this IPSec stack is not needed for SSH and SFTP.
The Small Cell supports NAT detection according RFC 3947 (Negotiation of NAT
traversal in the IKE) to optimize the stack and therefore bandwith usage for IPSec
transport. If there is no NAT traversal in the managed IP transport network, then the Small
Cell uses IPsec according RFC2401 without UDP encapsulation.
If support for NAT traversal is not required, then the Small Cell uses the following
transport stacks for all secure logical interfaces:
Application/IP/IPSec(ESP)/IP/ETH for any application and
IPSec(AH, IKE)/IP/ETH for IPSec control
If NAT traversal is required, then the Small Cell uses tunnel mode, because in transport
mode NAT is very complex and is not supported by commercial routers.
The base architecture for IPsec specified in RFC2401 needs to be enhanced for NAT
traversal, because the outer header in tunnel mode is an IP header only, which cannot be
NATed independently if port restricted cone NAT or symmetric NAT is used.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
9-6
Issue 1 March 2013
NAT traversal
....................................................................................................................................................................................................................................
The Small Cell supports UDP-encapsulated IPSec (tunnel mode) according RFC3948 by
supporting the following transport stack for all secure logical interfaces:
Application/IP/IPSec(ESP)/UDP/IP/ETH for any application and

IPSec(AH, IKE)/UDP/IP/ETH for IPSEC control.
The Small Cell supports one IPSec tunnel address to be used as the Small Cell end
address on the inner header of the clear text IP packet. The Small Cell supports one
local private IP address for transport all IPSec traffic. This address is assigned by DHCP
or by OA&M. This address is also used to transport any other traffic over the managed IP
transport network.
The Small Cell supports IKEv2 according RFC4306 (Internet Key Exchange Protocol) to
improve NAT traversal.
One important characteristic of NAT is the need for IKE packets to be accepted with any
port number. In addition, if the NAT router is restarted during the lifetime of an IKE
connection, the source addresses and port numbers on that IKE connection may change.
For this reason, IKEv2 can negotiate UDP encapsulation of IKE and ESP packets.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
9-7
Issue 1 March 2013
NAT traversal
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
9-8
Issue 1 March 2013
10
10 generation during
Tone
voice call set up
Overview
Purpose
This chapter describes the Tone generation during voice call set up (76980) feature.
Contents
10-2
10-4
10-6
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
10-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number

Feature description
When a user originates a CS voice call on the Small Cell a distinctive tone is provided,
during the call set up period, to provide audible notification to the user that the call is
being served by the Small Cell. The tone is generated by the Small Cell.
The tone is defined in a data file provided by the network operator. The file contains
AMR encoded packets. All characteristics of the tone perceived by the user is thus
determined by the process that the network operator uses to generate this file. The Small
Cell does not contain an AMR Codec.
The mode of playing the tone is configurable (N times, or continuous).
Feature principles
The Small Cell stores a file containing a series of packets containing an AMR encoded
tone. This file is provided by the network operator.
You can update this file to change the tone provided. The file contains the AMR encoded
tone, at 12.2kbit/s, with no Silence Descriptor (SID) frames. The Small Cell supports a
tone file containing up to 3 seconds of tone.
When a UE requests set up of a CS voice call, the Small Cell sends the contents of this
file to the UE; following set up of the Dedicated Channel. The termination of the tone is
dependent on subsequent events received, and a configuration option.
This feature is optional, activated/deactivated by a MIM attribute.
Feature benefits
The improved end-user perception of the service provided through the Small Cell may
increase usage.
The end-user is provided with an audible notification (distinctive tone) when originating a
voice call through the Small Cell. This provides, for example, confirmation of the specific
billing that the network operator may offer for calls using the Small Cell.
Impacted systems
Small Cell.
None
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
10-2
Issue 1 March 2013
....................................................................................................................................................................................................................................
Feature type
Optional.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
10-3
Issue 1 March 2013
....................................................................................................................................................................................................................................

Start of tone generation
For a mobile originated CS Voice call, after the Small Cell has received a RRC Radio
Bearer Setup Complete message, the Small Cell generates a NAS PROGRESS message
towards the UE.
This message includes a Progress Indicator, requesting the UE to connect to the user
plane, that is, disabling the local generating of ringing tone in the UE.
The Small Cell starts playing the tone, from the stored file, over the dedicated channel to
the UE. One packet is taken from the file every 20ms and handled as if received over the
IuCS interface.
The following options can be selected through a configurable parameter:
play the tone continuously, that is, play all packets from the file, repeatedly, until a
stop event happens, or,
play the tone a specific number of times.
Removal of tone
The Small Cell provides a configurable option to indicate whether a tone from the
network takes precedence over the tone provided from the Small Cell.
The Small Cell stops playing the tone, and connects the UE to the IuCS user plane, when
one of the following events occurs:
A NAS CONNECT message is received from the MSC.

The tone file has been played the configured number of times.
If the Small Cell is configured such that network tones have precedence and if a NAS
PROGRESS message is received indicating tone/announcement from the network.
RAB release is also handled normally, thus also stopping the tone generation.
Download and/or update of tone file
The Small Cell downloads a new version of the tone file in response to a TR-069
Download command.
Two read-only MIM attributes are provided to indicate:
Download status
Current tone file name
When the Small Cell has downloaded the file it checks the validity of the file format, that
is, it determines whether it is possible to extract a series of packets from the file. If this
check fails, a MIM attribute is set to indicate the error, and the Small Cell does not
attempt to apply this tone.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
10-4
Issue 1 March 2013
....................................................................................................................................................................................................................................
If the Small Cell already has a valid tone file, it continues to use this. If the Small Cell
does not have a previous valid file, it performs call handling as if this feature is not
activated.
If the file passes the validity check, the Small Cell:
Uses this file for the tone for subsequent calls. (Existing calls continue unchanged).
Sets the MIM attribute to indicate success.

Sets a MIM attribute indicating the current active file name.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
10-5
Issue 1 March 2013
....................................................................................................................................................................................................................................

Attributes of class BSR: Tone generation during call set up parameters
Parameter
Description
Syntax
activateUserTone
Activates tone generation

during voice call set up.
Boolean
userToneControl
Controls how the tone is

played to the UE that is
originating a CS Voice call.
0=continuous; >0= number of
times the tone file is played.
integer
(0..100)
userToneProgressIndicator
Defines the Progress Indicator

(24.008) value to be generated
by the Small Cell, when
playing a tone to the UE.
enum PIvalue
pi1=1
userTonePrecedance
Controls whether a tone from

the network should take
precedence over the locally
generated tone.
enum TonePrecedance
Contains the filename for the

tone which is currently active
on the Small Cell.
string
activeToneFilename
Values
pi8=8
femto=0
network=1
20
Attributes of class SDM: Tone generation during call set up parameters

Parameter
Description
Syntax
Values
toneFileUpdateStatus
Indicates the status of the tone

file on the Small Cell.
enum ToneFileStatus
noToneFile=0
downLoadInProgress=1
downLoadSuccess=2
downLoadFailed=3
invalidFileFormat=4
toneFileActive=5
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
10-6
Issue 1 March 2013
11
Open access
11
Overview
Purpose
This chapter describes the open access (76631) feature.

Contents
Open access
11-2
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
11-1
Issue 1 March 2013
Open access
Open access
....................................................................................................................................................................................................................................
Open access
Feature number

Feature description
This feature allows the Small Cell to provide access to any UE, in a similar way to the
macro network. The access control list is not used to restrict access to the Small Cell.
The Small Cells Cluster is configured to provide open or closed access, but not both
simultaneously. The Small Cells Cluster supports a number of location areas (LAs), with
a limited number of Small Cells per LA, to control the paging traffic load. The number of
LAs is not limited by this feature.
Feature benefits
Open access allows macro coverage (hot spots, coverage holes) to be extended, using
easily installed Small Cells.
Impacted systems
Small Cell, BSG, SCMS

Dependencies
None
This feature can only be implemented per cluster and for a whole cluster. Therefore, a
Small Cells Cluster will provide either open or closed access.
Engineering impacts
Support for the open access feature must be configured in the BSG and in the Small Cells.
None
Feature type
Basic
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
11-2
Issue 1 March 2013
12
12
Open
access
enhancements
Overview
Purpose
This chapter describes the open access (75405) feature.

Contents
12-2
Deployment scenarios
12-4
UE tracking
12-6
RANAP paging
12-8
Mobility management considerations
12-9
12-10
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
12-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number

Feature description
The feature is an extension of feature 76631 (Open access). This feature grants open
access at the Small Cell, rather than at the cluster level. 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.
Open access can be granted to a Small Cell to allow any UE to use the Small Cell. In a
cluster, some Small Cells can have open access, while others in the same cluster can have
closed access using the access control list (ACL).
This feature provides an efficient paging mechanism on the Iu' interface between the BSR
Signaling Gateway (BSG) and the Small Cells. In order to make paging independent of
the size of a location area, the UE is tracked in the BSG. This reduces the BSG load,
because the BSG must page fewer Small Cells also causing less signaling load on the
DSL line.
The access mode of the Small Cell is configurable through OAM. Both open and closed
access Small Cells can be simultaneously supported in the same Small Cells Cluster.
Open and closed access modes are mutually exclusive in the Small Cell. If a Small Cell
operates in open access mode, the ACL is ignored. If the operator wants the user of a
Small Cell to receive the same network indication from open access Small Cells as from
macro cells, then no network name should be provisioned in the full and short network
names of the Small Cell.
Feature benefits
This feature enables mobile network operators to deploy a single Small Cells Cluster for
both closed and open access Small Cells.
This feature provides mobile network operators with the means to use a Small Cell for hot
spot coverage and to offer public access similar to that of the macro network, without
having to grant access to all Small Cells in a cluster. This allows the operator to easily
extend the coverage of the macro network without the need to add new sites to the macro
network.
The end-user benefits from better network coverage and better service in areas where the
coverage is weak.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
12-2
Issue 1 March 2013
....................................................................................................................................................................................................................................
Impacted systems

Dependencies
None
The maximum number of Small Cells in a group that can operate in open access mode is
50.
Engineering impacts
None
None
Feature type
Basic
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
12-3
Issue 1 March 2013
....................................................................................................................................................................................................................................
Open access Small Cells can be deployed either standalone or as a group of Small Cells
providing contiguous coverage. All Small Cells belonging to the same Small Cell Group
have the same mobility LAC assigned.
Standalone deployment
Standalone deployment of a Small Cell has usually no overlapping coverage with other
open or closed access Small Cells. Such a Small Cell is not assigned to a Small Cell
Group. Typical deployment scenarios are indoor coverage enhancements and
improvements for coffee shops and small restaurants.
The Small Cell uses a different mobility LAC to that of the underlying macro cell. This
allows tracking of the UEs entering the open access Small Cell. The LAC assignment
strategy is the same as for closed access Small Cells.
Macro cell
Group deployment
The open access Small Cell providing contiguous coverage must be assigned to a Small
Cell Group. Typical deployment scenarios are indoor coverage enhancements and
improvements for large restaurants, enterprises buildings, and offices, which cannot be
covered by a single Small Cell. All Small Cells belonging to the same group use the same
mobility LAC. This avoids location area updates when users are moving within the
coverage area of the Small Cell Group, and ensures that the core network is not loaded
with a large number of location and routing area update procedures.
The Small Cell Group uses a different mobility LAC to that of the underlaying macro
cell. This allows tracking of the UEs entering the Small Cell Group.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
12-4
Issue 1 March 2013
....................................................................................................................................................................................................................................
Small Cell group 1
Macro cell
Small Cell group 2
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
12-5
Issue 1 March 2013
UE tracking
....................................................................................................................................................................................................................................
UE tracking
Description
Open and closed access Small Cells can operate in the same Small Cells Cluster. LAC
planning that is independent of the type of Small Cell eases and simplifies deployment of
the Small Cell network. For closed access Small Cells, the paging load does not depend
very much on the LAC planning, because the ACL is the main key for paging distribution
in the BSG.
For open access Small Cells, a similar approach is taken: The quasi-static ACL of closed
access Small Cells is emulated by a dynamic UE/IMSI database in the BSG called the
IMSI Directory. When the UE enters a standalone Small Cell or a Small Cell Group, the
open access Small Cells register in the IMSI directory. The Small Cell network cannot
detect when UEs are leaving its coverage area in IDLE mode. There is no communication
between the core network and the RAN to enable the removal of UEs from the IMSI
directory. Therefore, an expiration timer is associated with each entry in the IMSI
directory. On expiry of the timer, the BSG deletes the IMSI from the IMSI directory. The
timer value configured in the BSG must be aligned with the periodic location update
timer. The timer value should be slightly longer than the periodic LAU timer broadcast in
the open access Small Cells. The periodic LAU timer in the open access Small Cells can
be shorter than the timer in the CN, to limit the size of the IMSI directory in the BSG. The
time of the periodic LAU timer must be the same for all open access Small Cells in the
Small Cells Cluster.
Example
A UE moves in IDLE mode as shown in the following diagram:

Macro cell
LAC 1
Open access
6
Small Cell LAC 3
1
LAC 2
UE
2
LAC 2
4
LAC 2
7
LAC 2
Closed access
Small Cell
3
LAC 2
5
LAC 2
Open access
Small Cell group
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
12-6
Issue 1 March 2013
UE tracking
....................................................................................................................................................................................................................................
This example assumes that the same BSG serves all Small Cells covered by the macro
cell.
Process flow
...................................................................................................................................................................................................
The UE moves from macro to Small Cell 4:

An LA update is performed, Small Cell 4 registers the UE in the IMSI directory of the
BSG, UE is paged in Small Cells 1-5 and 7. The UE is paged in Small Cell 7 because the
UE is in the ACL of Small Cell 7 with same LAC as the Small Cell Group.
...................................................................................................................................................................................................
The UE moves from Small Cell 4 to Small Cell 3:

No LA update is performed, the UE remains registered with Small Cell 4 in the BSG. The
UE is paged as described in the preceding step.
...................................................................................................................................................................................................
The UE moves from Small Cell 3 to Small Cell 6:

An LA update performed, Small Cell 6 registers the UE in the IMSI directory of the BSG.
The BSG deletes the UE registration for Small Cell 4. The UE is paged in Small Cell 6.
...................................................................................................................................................................................................
The UE moves from Small Cell 6 to the macro cell:

An LA is update performed, the UE remains registered with Small Cell 6 in the BSG. The
UE is paged in LAC 1 (RNC).
...................................................................................................................................................................................................
The UE moves from the macro cell to Small Cell 7:

An LA update is performed. When the UE is paged in LAC 2, the BSG deletes the UE
from the IMSI directory, and the BSG pages the UE in Small Cell 7.
...................................................................................................................................................................................................
If the UE is not paged after camping on Small Cell 7, then the UE is de-registered with
Small Cell 6 when the timer expires.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
12-7
Issue 1 March 2013
RANAP paging
....................................................................................................................................................................................................................................
RANAP paging
RANAP paging mechanism
A UE can only be listed once in the IMSI Directory. The IMSI is always associated with
the Small Cell that last registered the UE. If a Small Cell is a member of a group, all
Small Cells of the group will be paged. Because of the use of common LACs for closed
and open access Small Cells, the BSG pages both closed and open access Small Cells.
Closed access Small Cells are only paged if the UE is included in their ACL. The
following diagram outlines the paging mechanism applied in the BSG:
If a UE is listed in the IMSI Directory and the area code of the Small Cell associated with
this IMSI does not match with the paged area code, then this is an invalid entry and the
BSG deletes the IMSI from the IMSI Directory.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
12-8
Issue 1 March 2013
....................................................................................................................................................................................................................................

Small Cell to Small Cell reselection
If open and closed access Small Cells have overlapping coverage, then the same
inter-Small Cell reselection strategy is applied between open access Small Cells and
between open and closed access Small Cells. This means that UEs camping on an open
access group are not forced to select a closed access Small Cell, if the cell reselection
strategy is configured for moving within the open access group. In this case, the closed
access Small Cell is only selected when the quality of the closed access Small Cell is
better than the quality of the open access Small Cell.
Macro to Small Cell reselection
Open and closed access Small Cells can use the same set of Primary Scrambling Codes
(PSCs). Hence, the macro network cannot apply different cell reselection strategies for
open and closed access Small Cells. The strategy for closed access Small Cells is that, the
UEs reselect the Small Cell as soon as the Small Cell is measured with a sufficient quality
level, even if the macro quality would be better at this time. The same strategy can be
applied for open access Small Cells, that is, all UEs in the coverage area of the open
access Small Cell will camp preferentially on the public Small Cell.
If the operator intends to apply different cell reselection strategies for open and closed
access Small Cells, then different sets of PSCs must be configured for open and closed
access Small Cells. This increases the required number of Small Cell neighbor cell entries
in the macro cells, which may not be available.
Femto to Macro handover
Handover from a Small Cell to a GSM or UMTS macro cell is available for open access
Small Cells.
Inter-Small Cell handover
Handover between open access Small Cells requires feature 75497 (Small Cell to Small
Cell handover).
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
12-9
Issue 1 March 2013
....................................................................................................................................................................................................................................

Small Cell access control
Parameter
Description
Syntax
Values
accessMode
Specifies whether a Small Cell

operates in closed access mode
or open access mode.
enum AccessMode
closedAccess
Specifies the minimum time

interval for generating UE
Registration messages towards
the BSG for a certain IMSI.
The UE registration guard time
is calculated as follows: UE
Registration guard time =
BSR::laT3212Timer ueRegistrationGuardTimeInterval
uint16
ueRegistrationGuardTimeInterval
openAccess
[1..1530],
unit=mins
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
12-10
Issue 1 March 2013
13
13
Detection
of Collapsing
LAI
Overview
Purpose
This chapter describes the Detection of Collapsing LAI (76977) feature.

Contents
13-2
13-4
Detection of Collapsing LAI - alarms
13-6
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
13-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number
Feature number 76977

Feature description
When a mobile network operator does not wish to use the geographical data to allocate a
LAI, the SCMS provisions the LAI value based on a pre-defined set of data. The term
collapsing indicates the exhaustion of this predefined list and subsequent raising of
alarms to alert the SCMS Operator to re-provision another LAI value that is
non-conflicting.
Note: Under normal circumstances the SCMS system is used to automatically assign
location, routing/service area codes for each Small Cell based on geographical
location information.
Feature overview
The following diagram provides the reference network architecture view.
Small Cell
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
13-2
Issue 1 March 2013
....................................................................................................................................................................................................................................
The following diagram provides a graphical overview of the feature.
Small Cell 1
Small Cell 2
When a new Small Cell (Small Cell 2 in this example) is added:
SCMS operator assigns a LAC value to Small Cell 2.
Small Cell 2 scans the RF environment.

Small Cell 2 generates an alarm if it detects a neighbor Small Cell having the same
LAI.
Feature benefits
The SCMS operator is sent an alarm to warn of collapsing LAI which would otherwise
lead to a missing call in case of high density Small Cell deployment.
Avoids poor quality end-user perception.
This feature enables an alternative means of assigning area codes, (for example; LAC,
LAI), where, depending on the mobile network operator, a prefixed scheme is used. The
data is provisioned through the SCMS to the Small Cell.
To avoid continuous network replanning, the mobile network operator must ensure that
area codes used are statistically random enough to prevent Detected Collapsing LAI
alarm conditions arising.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
13-3
Issue 1 March 2013
....................................................................................................................................................................................................................................

In the example shown in the following diagram, the mobile network operator has a
currently defined LAC range of 101-106 for the existing 6 Small Cells. A new cell is to be
introduced, Cell 7, with a LAC of 103.
Definitions:
LAI = (PLMN Id) + LAC
where PLMN Id = MCC + MNC
LAI Location Area Identity
PLMN Public Land Mobile Network
LAC Location Area Code
MCC Mobile Country Code
MNC Mobile Network Code
As the LAC value is within the range of 101-106 this conflicts with the existing
configuration and the cell being provisioned (in this case Cell 7) raises the alarm,
Detected Collapsing LAI.
The Small Cell being provisioned sends a real time alarm to the SCMS when a new Bulk
CM is downloaded and auto-configuration is executed. This prompts the SCMS operator
to choose a non-conflicting LAI. In the current case it is assumed that all existing cells
(1-6) are provisioned and in service.
The only option available is to increase the LAC range, for example to 101- 110. A
non-conflicting LAC value must now be provisioned for Cell 7, as result of which the
Detected Collapsing LAI alarms are then cleared (in the above example on Cell 3 and Cell
7).
If any of the existing Small Cells were out of service (switched off), then the existing
LAC range of 101- 106 would, temporarily, be adequate, allowing a value not in use to be
selected.
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.
Changing the area code on one Small Cell can create a ripple effect on the neighboring
Small Cells. The mobile network operator must ensure suitable LAC data ranges are
defined which will avoid a potential flood of Detected Collapsing LAI alarms and
continuous re-planning.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
13-4
Issue 1 March 2013
....................................................................................................................................................................................................................................
Different area codes for neighboring Small Cells
The mobile network 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 neighborhood. The
allocation of different LAIs in neighboring Small Cells is applicable for closed access (or
private access) and open access modes of operation. This ensures the UE performs a LA
update when it exits its home Small Cell.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
13-5
Issue 1 March 2013
....................................................................................................................................................................................................................................

Real time - Detected Collapsing LAI Alarm
The Small Cell will only raise the Real Time alarm of Detected Collapsing LAI after a
Bulk CM download has been completed and an auto-configuration has run.
Note: This can also be raised after a Factory Reset is performed, which results in a
new Bulk CM download and auto-configuration execution.
Non real time - Detected Collapsing LAI Alarm
When the Small Cell is subject to Power Cycle, Reboot or Reset conditions, and
subsequent auto-configuration and self optimization processes are executed, the
Collapsing LAI alarm is as per the default FM behavior.
Note:
1. The neighbor Small Cell will detect this alarm at the next auto-configuration/selfoptimization stage if a conflict in LAC data is detected, it is managed as per the
default FM behavior.
2. Reset types include Soft Reset (SW reset, push button on Small Cell) and Hard
Reset (Power On/Off).
Small Cell Operations with Raised Alarm
After raising the Detected Collapsing LAI alarm the Small Cell will continue normal
operations.
Behaviour under Small Cell Groups
If the Small Cell Group Id matches, between the source Small Cell and neighbor cell, the
Detected Collapsing LAI alarm will NOT be raised.
Note:
1. Small Cell Group Id is provisioned by SCMS.
2. Small Cell decodes the Cell Id from SIB3.
3. Small Cell neighbor cell data contains Small Cell Group Id.
4. If the Small Cell Group Id does not match then, by definition, these cells are not in
a group.
Alarm Clearance Procedure
In order to resolve the Detected Collapsing LAI alarm, the SCMS operator must replan
the LAC data to a value that is nonconflicting.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
13-6
Issue 1 March 2013
....................................................................................................................................................................................................................................
To aid this process, the list of LAC values of Small Cell neighbor cell(s) is sent in the
additional text field of the alarm to the SCMS. The area codes used must be statistically
random enough to prevent the Detected Collapsing LAI alarm conditions. The Small Cell
clears this alarm at auto-configuration or self optimization, when this conflict in LAC
data is no longer detected.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
13-7
Issue 1 March 2013
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
13-8
Issue 1 March 2013
14
14
ePLMN
support for
camping and notification
Overview
Purpose
This chapter describes the ePLMN support for camping and notification (76976) feature.
Contents
14-2
ePLMN support for camping and notification parameters
14-4
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
14-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number

Feature description
This feature adds an equivalent PLMN (ePLMN) list to the PLMN ID of a Small Cell. A
PLMN ID consists of a 3 digit Mobile Network Code (MNC) and a 3 digit Mobile
National Code (MCC). Each operator is allocated one or several PLMN IDs for each
country in which they operate. Small Cells are configured to be associated with one of the
PLMN IDs of the operator. During auto-configuration and self-optimization, 2G and 3G
neighbor cells that belong to a PLMN other than the PLMN of the Small Cell are
searched for, identified, added to the neighbor cells lists, made the target cell for handover
if appropriate, and broadcast in SIB11 as requested by the operator.
The Small Cell can be on the same PLMN as the macro network, or on a PLMN that is
only associated with the Small Cell network. The operator can either operate the Small
Cell network on a different PLMN from that of their macro network, or, they can install a
Small Cell in an area of the PLMN of another operator with whom they work in
partnership.
3G networks
For a 3G network, the operator can configure a list of frequencies. Because PLMN IDs
are allocated by frequency, the 3G network listening feature (34537) searches this list.
Any ePLMN cells found are stored in the detected cell list (LCELL::UmtsMacroNCell)
with their PLMN ID. If a UMTS macro cell is identified as a target cell for handover, then
Small Cell to UMTS macro cell handover occurs. ePLMN UMTS macro cells and UMTS
macro cells from the same PLMN as the Small Cell are broadcast in SIB11.
2G networks
The feature supports equivalent PLMNs on the GSM network.. The 2G network listening
feature (36255) only supports a single PLMN. This feature extends this to multiple
PLMNs on the GSM macro network as configured by the operator. All ePLMN cells
found on the GSM macro network are stored in the detected cell list (LCELL::gsmMacroNCell) with their PLMN ID. If a GSM macro cell is identified as a target cell for
handover, then Small Cell to GSM macro cell handover occurs. ePLMN GSM macro cells
and GSM macro cells from the same PLNM as the Small Cell are broadcast in SIB11.
Assumptions
This feature assumes the following:
More than one PLMN ID may exist per UMTS frequency.

Multiple PLMN IDs are supported across the band for GSM.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
14-2
Issue 1 March 2013
....................................................................................................................................................................................................................................
SIB18 will not be used to broadcast the ePLMN.

The UEs have been correctly configured with the ePLMN IDs supported by that
operator, from the core network, during a Routing Area or Location Area update.
Feature benefits
This feature allows the operator maximum flexibility when designing the Small Cell
network in association with their macro network, and enables the operator to work in
partnership with other operators.
Impacted systems
Small Cell
Dependencies
3G network listening (feature 34537)

2G network listening (feature 36255)
None
Engineering impacts
None
None
Feature type
Basic
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
14-3
Issue 1 March 2013
....................................................................................................................................................................................................................................

Attributes of class LCell
Parameter
Description
Syntax
umtsMacroEPLMN
The PLMN ID (MCC and

MNC) of equivalent PLMNs
on the UMTS macro network

PLMN
enableUMTSePLMN
This flag enables the ePLMN

feature to allow an ePLMN ID
cell to be stored and used.
boolean
Values
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
14-4
Issue 1 March 2013
15

15
Overview
Purpose
This chapter describes the Small Cell group support (80569) feature.
Contents
15-2
Small Cell group support parameters
15-6
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
15-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number

Feature description
Small Cell groups increase coverage when an individual Small Cell does not provide
sufficient coverage. They can be used in small or medium enterprises, or in public areas
such as airports.
A group of Small Cells located close together provide increased coverage. Small Cells
that are not located close together can also be part of a group, for example in an enterprise
with multiple premises on the same campus, where the same mobility LAC, RAC and
emergency call SACs can be assigned to a group of Small Cells.
A Small Cell group can include up to 50 Small Cells in open access mode, or 256 Small
Cells in closed access mode. A Small Cell can belong to only one Small Cell Group. All
Small Cells that belong to the same group must also belong to the same Small Cells
Cluster.
All Small Cells in a Small Cell Group must have the same values for the following
attributes:
Frequency used
Access control:
Open or closed access
Access control list for closed access
Billing definition:
If the home tariff feature is used, then the areaSelectNormalFlag must be common
to all Small Cells in the group. This is not true for areaSelectEmergencyFlag,
which is set individually as in the non-group case.
If dynamic SAC and LAC are used, then all Small Cells in the same group must
be configured in the same way.
Differentiated charging LACx and SACx.
Latitude
Longitude
Cluster identifier
Mobility LAC, RAC and SAC
Differentiated emergency call handling LAC3 and SAC3 values

Security gateway address
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
15-2
Issue 1 March 2013
....................................................................................................................................................................................................................................
Access control management
An authorized Small Cell user can update the ACL lists for the Small Cell group without
having to change the ACL lists individually for each Small Cell. Multiple authorized
users can change and update the ACL.
This common management of the access control lists is applicable for both owners and
guests.
Because the number of users (owners, employees, or guests) who can access the Small
Cell Group is higher than the number of users for a residential Small Cell, the ACL lists
support up to 256 IMSIs.
Billing
ASmall Cell can differentiate between categories of users (owner, visitor) using the
LAC1, LAC2, SAC1 and SAC2 parameters. These parameters can be either dynamically
read from the macro cell, or as defined.
All Small Cells belonging to the same Small Cell Group must share the same definition
for the LAC1, LAC2, SAC1 and SAC2 parameters. An SCMS user can update these
parameters for the Small Cell Group without having to change them individually for each
Small Cell.
Emergency calls
All Small Cells belonging of the same group must individually define the emergency call
parameters, SAC3 and LAC3. Allocation must be done in the same way as for a
standalone Small Cell.
Mobility management
The LAC and RAC parameters must have the same values for all Small Cells in the same
group. This avoids unnecessary location routing area updates when a UE moves inside the
group. The operator can either set these parameters manually or use the
auto-configuration functionality provided by SCMS (geographical location based
algorithm or random assignment).
For mobility purposes, and to detect collapsing LAIs, each Small Cell that belongs to a
group must know whether or not a sniffed Small Cell neighbor is part of the same group.
For cell reselection and handover within a group of Small Cells providing contiguous
coverage, no Primary Scrambling Code (PSC) should be reused. This means that all
neighbors of a Small Cell should have different PSCs, such that the PSC reported by the
UE in a measurement report can be uniquely assigned to a neighboring Small Cell.
PSCs can be manually provisioned for each Small Cell using the SCMS.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
15-3
Issue 1 March 2013
....................................................................................................................................................................................................................................
Inter-Small Cell SCTP establishment and maintenance
An SCTP connection between neighbor Small Cells is established to support inter-Small

Cell BSRAP signaling procedures. This connection is established between two Small
Cells, whenever a Small Cell determines that a handover relationship exists with a
neighbor Small Cell.
The SCTP connection between Small Cells performs heartbeating to ensure connectivity
between Small Cells is not lost. Failure of the SCTP connection heartbeat causes the
Small Cell to request the current IP address of the neighbor Small Cell from the BSG
before re-establishing the SCTP association. This ensures that the correct target Small
Cell is addressed if the IP address of the IPSec tunnel to one of the Small Cells changes.
PM files
To support aggregated PM analysis on a per-group basis, the ID of the group to which a

Small Cell belongs must be encoded into any generated PM result file when
measurements are taken.
Feature benefits
An operator can deploy multiple Small Cells to cover a larger area than an individual
Small Cell, while allowing simple configuration and management.
End users gain better coverage, and, depending on the commercial strategy of the
operator, a consistent reduced tariff, across all Small Cells in a group.
Impacted systems

Dependencies
Small Cell to Small Cell handover (feature 75494)

Management for a group of Small Cells (75497)
None
Engineering impacts
None
None
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
15-4
Issue 1 March 2013
....................................................................................................................................................................................................................................
Feature type
Basic
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
15-5
Issue 1 March 2013
....................................................................................................................................................................................................................................

Global definitions
Type
Parameter
Description
Syntax
Values
InterBSRInterface
informedFemtoNeighbourCellInfoTimeToLive
Specifies the length of

time informed neighbor
cell information is
retained, without being
refreshed, before it is
determined that it is no
longer valid.
integer
[0..125],
unit=hours
InterBSRInterface
detectedFemtoNeighbourCellInfoTimeToLive
Specifies the length of

time detected neighbor
cell information is
retained without being
refreshed before it is
determined that it is no
longer valid.
integer
[0..125],
unit=hours
InterBSRInterface
bSRAPEstablishmentMaxRetries
Defines a count of the

maximum number of
retries that a Small Cell
attempts to establish a
communication link
with another Small Cell.
integer
[0..10]
InterBSRInterface
bSRAPLinkEstDelayTimer
Defines the initial time

that a Small Cell waits
to establish a
communication link
with another Small Cell
following failure to
complete establishment
for bsRAPEstablishmentMaxRetries
attempts.
integer
[1..120],
unit=mins
The Small Cell uses this

as the start of an
exponentially increasing
timer that doubles on
each complete failure.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
15-6
Issue 1 March 2013
....................................................................................................................................................................................................................................
Type
Parameter
Description
Syntax
Values
InterBSRInterface
sctpMaxAttempts

of SCTP connection
attempt after the
association goes down.
integer
[0..10]
InterBSRInterface
sctpCookieLife
Specifies the cookie life

time in seconds.
integer
[1..60],
unit=secs
InterBSRInterface
sctpHbOn
Enables/disables the
SCTP heartbeating.
boolean
InterBSRInterface
sctpInitTimeout
Defines the SCTP Init

Timeout in
milliseconds.
integer
[1000..10000],
unit=ms
InterBSRInterface
sctpHbTimeout
Defines the SCTP

Heartbeat Timeout in
seconds.
integer
[1..3600],
unit=secs
umtsFemtoNCell
primaryCPICHInfo

downlink radio link. A
value of -1 to indicate
that the PSC is
unknown.
integer
(-1..511)
umtsFemtoNCell
rAC

area code of the
neighbor Small Cell
integer
(0..255)
umtsFemtoNCell
lAC

area code of the
neighbor Small Cell. A
value of 0 indicates that
the rAC, lAC cannot be
decoded.
integer
(0..65534)
umtsFemtoNCell
mCC

country code.
string
length=3
umtsFemtoNCell
mNC

network code.
string
length=3
umtsFemtoNCell
clusterId
Indicates the Small Cell

Cluster Id to which the
Small Cell belongs. A
value of 0 means that
the Cluster ID is not
known.
integer
(0..511)
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
15-7
Issue 1 March 2013
....................................................................................................................................................................................................................................
Type
Parameter
Description
Syntax
Values
umtsFemtoNCell
bsrId
Identifies a Small Cell

within a Small Cells
Cluster.
integer
(0..65535)
umtsFemtoNCell
cPICHRSCP

CPICH RSCP of the
neighbor Small Cell
mapping between the
value and the real RSCP
value is given in
TS25.133 Section
9.1.1.3.
integer
(0..91)
umtsFemtoNCell
cPICHEcNo

CPICH Ec/No of the
neighbor Small Cell.
Mapping between the
value and the real RSCP
value is given in
TS25.133 Section
9.1.2.3.
integer
(0..49)
umtsFemtoNCell
cellInfoComplete
Identifies whether all

this data is available or
some data is missing. It
should be set to true
only if all the data (such
as rAC, lAC, mCC,
mNC, rNCID,
cellIdentity ) is available
for the cell. This
parameter has no
bearing on Small Cell to
Small Cell handover.
boolean
umtsFemtoNCell
bsrGroupId
Specifies the group

assigned to the Small
Cell. If the Small Cell
does not belong to a
group, bsrGroupId has a
value of 0. If the Small
Cell Group is unknown,
bsrGroupId has a value
of 65535.
uint16
[0..65535]
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
15-8
Issue 1 March 2013
....................................................................................................................................................................................................................................
Type
Parameter
Description
Syntax
umtsFemtoNCell
measuredCPICHavailable
Indicates whether
cPICHRSCP and
cPICHEcNo are
measured for the cell.
boolean
umtsFemtoNCell
detectionStatus
Indicates how the

neighbor is added:
enum
DetectionStatus
umtsFemtoNCell
interBsrLinkStatus
Detected detected
by sniffer
Informed not
detected by Small
Cell, but detected by
a neighbor and
informed through
Small CellSmall
Cell communication
Configured
manually
configured and not
detected by sniffer
or informed by a
neighbor
Indicates the status of

the inter-Small Cell
SCTP connection. The
options are:
notRequired there
is no required
inter-Small Cell
communications
communicating
the link is up
notCommunicating
the link cannot be
established or the
SCTP heartbeat
monitor detects that
it out of service
Values
enum
InterBsrLinkStatus
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
15-9
Issue 1 March 2013
....................................................................................................................................................................................................................................
Type
Parameter
Description
Syntax
Values
umtsFemtoNCell
bsrCapabilitiesRegistered1
Defines the set of

capabilities for the
neighbor Small Cell that
have been registered by
that Small Cell to the
BSG. This attribute
defines a bitmap where
each bit represents a
different capability of
the neighbor Small Cell.
uint16
[0..255]
umtsFemtoNCell
bsrCapabilitiesInterBSR1
Defines the set of

capabilities for the
neighbor Small Cell that
are signaled directly
between Small Cells on
the interFemto interface
(if configured).
uint16
[0..255]
This attribute defines a

bitmap where each bit
represents a different
capability of the
neighbor Small Cell:
Bit 1 (LSB)
Defines whether the
Small Cell supports
incoming handover
capability
Bit 2 Spare
Bit 8 (MSB) Spare
umtsFemtoNCell
numberOfSuccessfulHos

successful Small Cell to
Small Cell HOs to this
neighbor
Counter32
umtsFemtoNCell
sfnOffset
Specifies the estimated

SFNSFN timing offset
to a neighbor cell. The
offset is a multiple of
chips. A value of -1
means that the
information is not
available.
integer
[-1..9830400]
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
15-10
Issue 1 March 2013
....................................................................................................................................................................................................................................
Type
Parameter
Description
Syntax
Values
umtsFemtoNCell
targetIPAddress
Specifies the virtual

HBSR host address of
the target Small Cell.
This address is an IPV4
address.
ipAddress
umtsFemtoNCell
interBsrInterfaceVersion
Specifies the inter-Small

Cell interface version. A
value of 0 means that no
interface capability
exists.
uint16
[0..255]
umtsFemtoNCell
sparePara
Spare parameter.
string
length=100
Small Cell group management

Parameter
Description
Syntax
activateFemtoToFemtoCommunications
Flag to determine whether a

Small Cell can communicate
with other Small Cells through
the Small CellSmall Cell
communications interface.
boolean
isAutoNeigbourCellDetectionEnabled
Determines if automatic
neighbor cell detection is
enabled.
boolean
rscpDeltaPscClashRealloc
CPICH RSCP of a detected

neighbor cell on the same PSC
to consider a PSC clash. This
triggers PSC re-allocation for a
group Small Cell supporting
Small CellSmall Cell
handover.
integer
pscAllocMinRscpNeigb
The minimum CPICH RSCP to

discard neighbor cell
measurements during PSC
allocation for Small
CellSmall Cell handover.
integer
The minimum CPICH RSCP to

discard neighbor cell
measurements for neighbor list
construction.
integer
neigbListMinRscp
Values
[-115..-25]
step=1, unit=dBm
[-115..-25]
step=1, unit=dBm
[-115..-25]
step=1, unit=dBm
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
15-11
Issue 1 March 2013
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
bsrGroupId
Specifies the group assigned to

the Small Cell. If the Small
Cell is not in a group, the value
of bsrGroupId is 0.
uint16
[0..65534]
Values
This parameter must be

configured if open access
groups are deployed.
Home tariff and visitor differentiated support

Parameter
Description
Syntax
areaSelectNormalFlag
Flag to determine whether

LAC or SAC within the SAI is
used to distinguish between
owner and guest users for
normal, non-emergency calls.
Setting it to off disables the
conditional setting of LAC or
SAC.
enum AreaSelect
areaSelectEmergencyFlag
Flag to determine which LAC

and/or SAC within the SAI is
used for an emergency call.
enum AreaSelect
Parameter
Description
Syntax
resetFemtoHOcounter
Triggers the Small Cell to reset

numberOfSuccessfulHos of all
the UmtsFemtoNCell
instances.
boolean
tBsrSetupAck
Defines the time a Small Cell

will wait for Small Cell setup
acknowledge from another
Small Cell.
integer
Attributes of BSR class

Values
[1..300], unit=secs
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
15-12
Issue 1 March 2013
16
Super LAC
16
Overview
Purpose
This chapter describes the Super LAC (79495) feature.

Contents
Super LAC overview
16-2
16-4
16-5
Super LAC Small Cell requirements
16-6
16-7
Super LAC restrictions
16-9
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
16-1
Issue 1 March 2013
Super LAC
Super LAC overview
....................................................................................................................................................................................................................................
Super LAC overview

Feature number

Feature overview
This feature reduces the number of LACs that needs to be seen in the CN per Small Cells
Cluster, but still allowing a larger number of LACs (or airLACs) over a Small Cells
Cluster for closed mode access. It is achieved by using the superLAC towards CN and
airLAC towards the UE as follow when the feature is activated.
The Small Cell will use the superLAC in the LAI IE in uplink RANAP messages (Initial
UE message and Direct Transfer messages towards CN and Relocation Required). If the
LAC in the LAI IE needs to be aligned to the SAI IE, the LAC in the LAI will be used for
the LAC in the SAI IE.
For the NAS messages, the Small Cell will first check whether the LAC in the LAI IE or
RAI IE is the airLAC in the same Small Cells Cluster. If it is, the Small Cell will replace
the airLAC in the LAI IE or RAI IE with the superLAC. If it is not, the Small Cell will
simply pass the NAS message up to the CN.
In the downlink, the Small Cell intercepts the NAS messages to replace the super LAC
with the air LAC.
Feature purpose
The main purpose of this feature is to minimize the provisioning effort on the SAI, RAI
and LAI in the CNs by reducing the number of LACs used by the Small Cells Cluster, in
the view of core network, to up to 3 per Iu or per pool of Iu when IuFlex is introduced.
Each LAC is called superLAC and is for any one of owner, guest or emergency call. This
is achieved by replacing the LAC in the RANAP messages and NAS messages to CN (in
the form of LAC in LAI and RAI IEs) with the superLACs provisioned by the OAM
system.
For NAS message to UE, the Small Cell will replace the LAC of the LAI and RAI IE in
the NAS messages back to the LAC seen by the UE in SIB 1. This LAC is often referred
to as the air LAC.
From the Home tariff and visitors access differentiated support (b1718) feature, 3 LACs
(or superLACs) have been defined for owner, guest and emergency calls by the SCMS in
the closed access mode. In the open access mode, another LAC value may be defined as a
superLAC and it is put in the LAC of the owner in b1718. These will be used in the
feature as the superLACs. If for some reasons the LAC in the LAI and SAI has to be the
same (for example; Nokia MSC), the dynamic LAC part of the Dynamic LAC-SAC
feature (b78695) must be turned off to ensure that the LAC in the SAI uses the same LAC
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
16-2
Issue 1 March 2013
Super LAC
Super LAC overview
....................................................................................................................................................................................................................................
in the LAI.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
16-3
Issue 1 March 2013
Super LAC
....................................................................................................................................................................................................................................

Functional definition
This feature uses the LAC1, LAC2 and LAC3 from the Home tariff and visitors access
differentiated support (b1718) feature as super LACs. Where LAC1 is for the owner,
LAC2 is for a guest and LAC3 is for emergency calls in a closed mode Small Cell and
only LAC1 in an open mode Small Cell.
In an IuFlex environment, the values of the LAC1, LAC2 and LAC3 will be associated
with a pool of IUs related to the Small Cell LAC.
In a non-IuFlex environment, the values of the LAC1, LAC2 and LAC3 will be based on
the IU which the BSG of all the Small Cells in a cluster is connected to.
The super LACs are known to the CN, whereas the air LAC is sent on SIB1 and is used
by the UE for mobility purposes.
In the direction towards the CN
For the RANAP messages to the CN, the Small Cell will always replace the LAC or the
LAC in the LAI IE with the super LAC. For the NAS messages to the CN, the Small Cell
will only replace the LAC in the LAI or/and RAI IEs with the superLAC if the LAC
(airLAC) in the NAS messages is in the same Small Cells Cluster as the Small Cell.
An air LAC is in the same Small Cells Cluster if the air LAC is detected in the Small Cell
neighbor cell list. As on the super LAC to be used, if the Home tariff and visitors access
differentiated support feature is activated, the superLAC will either be the owner
superLAC, guest superLAC or emergency call superLAC. If it is not activated or the
Small Cell is in open access mode, the superLAC will be the owner superLAC.
If the Dynamic LAC allocation feature is activated and the LAC in the LAI and SAI
towards the CN in the RANAP messages need to be aligned, the LAC in the SAI will use
the super LAC used in the LAI, if it is not already using the superLAC.
In the direction towards the UE
The Small Cell will always replace the LAC in the LAI or RAI IE of the NAS messages
with the air LAC if the feature is activated.
The air LAC in the UL NAS message is not replaced from different Small Cells Cluster or
Macro cell because the old LAC in the UL NAS message is needed by the CN to resolve
the old MSC or SGSN. This happens when the UE roams from a macro cell to the Small
Cell or from a Small Cell of another cluster to the Small Cell.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
16-4
Issue 1 March 2013
Super LAC
....................................................................................................................................................................................................................................

Feature dependencies
This feature is dependant on the following:
3G Network Listening' functionality

Home tariff and visitors' access differentiated support feature
Dynamic LAC-SAC Allocation feature
3G Network Listening' functionality
This must be operational in the Small Cell as well as Small Cell PSC detection introduced
by Collapsing of LAI feature (b76977), as this provides the detected neighboring Small
Cell list to determine whether an air LAC belongs to the same Small Cells Cluster as the
Small Cell.
Home tariff and visitors' access differentiated support feature
Determines which super LAC should be used.

Dynamic LAC-SAC Allocation feature
Determines whether to use the best macro cell LAC if the LAI LAC needs to be aligned
with SAI LAC. In this case, the Dynamic LAC has to be turned off when the superLAC
feature is activated. Dynamic SAC may still be activated even when Dynamic LAC is
de-activated as they are independently set.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
16-5
Issue 1 March 2013
Super LAC
....................................................................................................................................................................................................................................

Small Cell requirements
The Small Cell is able to activate and deactivate the feature via the OAM.
If the feature is activated, the Small Cell will intercept uplink NAS messages to replace
the air LAC in the RAI & LAI of the messages with the superLAC if the air LAC in the
NAS messages is in the same Small Cells Cluster as the Small Cell. Whether an air LAC
belongs to the Small Cells Cluster is determined from the Small Cell list detected.
For the RANAP messages towards the CN (that is, Initial UE message and Direct
Transfer RANAP messages, Relocation Required, Location Reporting), the Small Cell
always replaces the LAC in the LAI/SAI with the superLAC.
The super LAC to use depends on whether the Home tariff and visitors access
differentiated support (b1718) feature is activated. If it is activated, the super LAC to be
used will be the owner superLAC, guest superLAC or emergency call superLAC. If it is
not activated or the Small Cell is open access mode, the super LAC used will be the
owner superLAC.
If the Dynamic LAC-SAC allocation feature is activated and the LAC in the LAI and SAI
towards the CN in the RANAP messages need to be aligned, the LAC in the SAI will use
the super LAC used in the LAI if it is not already using the superLAC.
If the feature is activated, the Small Cell will intercept the downlink NAS messages to
replace the super LAC in the messages with the air LAC (the Small Cell LAC).
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
16-6
Issue 1 March 2013
Super LAC
....................................................................................................................................................................................................................................

BSG Requirements
The BSG is able to activate and deactivate the feature via the OAM.
During CN paging when this feature is activated, the BSG will not perform an area code
check when the area code is one of the superLACs as follows:
In closed mode paging: If LAC in Paging Area ID IE in RANAP Paging is one of the
superLACs, the BSG considers all Small Cells within the cluster as paging candidates.
In open mode paging: If LAC in Paging Area ID IE in RANAP Paging is one of the
superLACs, the BSG will skip the matching of the LAC with Small Cell and consider
all Small Cells registered with the IMSI in the IMSI directory in the Paging list.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
16-7
Issue 1 March 2013
Super LAC
....................................................................................................................................................................................................................................
This is shown in the following diagram:

Closed mode
paging
Paging from CN
For BCR2.1 Open Mode cluster

backward compatibility
Open Access
Cluster?
Yes
LAC in paging
area ID - one of
SuperLACs?
Add all BSRs matching

the paging area ID
in the paging list
Yes
No
No
Paging area
ID in CN
paging message?
Paging candidates:
BSRs matching the
paging area ID
No
Yes
UE in ACLs
and/or IMSI
directory?
Closed mode
paging
No
UE in ACLs of paging
candidates?
Yes
Any BSRs in
the paging list
in a Small Cell
group?
No
Yes
Add BSRs to
paging list
BCR2.2 open
mode paging
Paging candidates:
All BSRs
Add BSRs to
paging list
No
End
BCR2.2 open
mode paging
Yes
Add BSR groups
into paging list
No
UE in IMSI
directory?
Yes
Paging list
empty?
Yes
Yes
No
Page BSRs
in the
paging list
LAC in paging
area ID - one of
SuperLACs?
No
LAC/RAC
matches with
BSR?
No
Delete UE
from IMSI
directory
End
Yes
BSR in a
Small Cell group?
No
Yes
Add BSR
group into
paging list
Add BSRs
that match to
paging list
End
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
16-8
Issue 1 March 2013
Super LAC
....................................................................................................................................................................................................................................

Introduction
When the UE moves to the 2G/3G Macro network from the Small Cell, it sends the old
LAI or RAI (which is the air LAC of the Small Cell) in the NAS message (for example,
Location Update Request, Routing Area Update Request) to the MSC or SGSN. This
cannot be intercepted by the Small Cell and changed.
MSC case
In the MSC case, the MSC cannot locate the old VLR to process the location update
properly. The MSC can identify the UE with the TMSI only if it knows the old LAC.
Since the MSC cannot identify the UE, it always requests the IMSI from the UE
[TS29.002 Section 19.1.1.1] and then contacts the HLR to get authentication vectors and
subscriber data. The MSC then accepts the LAU, that is, the user is not impacted, but the
HLR load is increased.
SGSN case
In the SGSN case, the SGSN cannot locate the old SGSN and thus may reject the
Routing Area Update Request with cause = # 9 (MS identity cannot be derived by the
network).[TS24.008 Section 4.7.5.1.4]. Upon receiving the reject, the UE deletes any
P-TMSI, P-TMSI signature and any RAI and GPRS ciphering key sequence number, and
automatically initiates the GPRS attach procedure with the IMSI [TS24.008 Section
4.7.5.1.4]. In some cases, upon receiving a Routing Area Update Request or a GPRS
Attach Request, the SGSN may request the IMSI from the UE, if it cannot resolve the UE
identity and perform in the same manner as the MSC. Because the new SGSN does not
know the old SGSN, the new SGSN also deactivates the preserved PDP context in the
UE. This may impact end user experience because the UE must activate the PDP context
for the PS service again. This also happens in Small Cell to 2G/3G macro handover.
As Identity Request is unciphered every time cell reselection occurs from the Small Cell
to the macro network, it also goes against the recommendation of 3GPP that the sending
of unciphered IMSI over the air is minimized. When the UE moves to a Small Cell from a
neighboring Small Cell of another Small Cells Cluster, the Small Cell does not change the
old LAI or RAI in the NAS message (for example, Location Update Request, Routing
Area Update Request) to the 3G-MSC or 3GSGSN because it does not know the super
LAC of the neighboring Small Cells Cluster.
This will also lead to the 3G MSC not being able to locate the old VLR to process the
location update properly. The MSC can identify the UE with the TMSI only if it knows
the old LAC. Since the MSC cannot identify the UE, it always requests the IMSI from the
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
16-9
Issue 1 March 2013
Super LAC
....................................................................................................................................................................................................................................
UE [TS29.002 Section 19.1.1.1] and then contacts the HLR to get authentication vectors
and subscriber data. The MSC then accepts the LAU, that is, the user is not impacted, but
the HLR load is increased.
3G SGSN case
In the 3G SGSN case, the 3G-SGSN cannot locate the old SGSN and thus rejects the
Routing Area Update Request with cause = # 9 (MS identity cannot be derived by the
network).[TS24.008 Section 4.7.5.1.4]. On receiving the reject, the UE deletes any
P-TMSI, P-TMSI signature and RAI and GPRS ciphering key sequence number, and
automatically initiates the GPRS attach procedure with the IMSI [TS24.008 Section
4.7.5.1.4]. In some cases, on receiving a Routing Area Update Request or GPRS Attach
Request, the SGSN may request the IMSI from the UE when it cannot resolve the UE
identity and perform in the same manner as the MSC. As the new SGSN does not know
the old SGSN, the preserved PDP context is also deactivated. This may impact end user
experience as the UE must activate the PDP context for the PS service.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
16-10
Issue 1 March 2013
17
17
Dynamic
LAC-SAC
allocation
Overview
Purpose
This chapter describes the Dynamic LAC-SAC allocation (78695) feature.

Contents
Dynamic LAC-SAC allocation overview
17-2
Dynamic LAC-SAC allocation functional definition
17-3
17-4
17-6
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
17-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number

Feature overview
This feature is an extension to the Home tariff and visitors access differentiated support
feature. It configures SAI for Small Cell, owner, guests and emergency calls. This
configuration is based on system information broadcast (SIB 1 for LAC and SIB 3 for
Cell ID) by the best neighbour macro cell if available. The configured LAC and SAC
replace the fixed SAC and LAC values based on the Small Cell LAC and SAC and user
types (that is, owner, guest or emergency call) from the SCMS.
If the feature is deactivated, the SAC and LAC of the SAI will be the Small Cell LAC and
SAC provisioned, regardless of owner, guest or emergency call. Depending on MIM
settings, the SAI of the location-based services may use the Small Cell LAC and/or SAC,
or the macro LAC, and/or the macro cell ID for the SAI.
If there is no 3G neighbour macro cell coverage, or for any other reasons (for example,
LAC & Cell ID of the macro cell is not available), the SAI will be set as though the
feature is deactivated.
The network-wide reserved value for the owner is populated in the IN database to give
Small Cell Homezone billing. The macro value may be populated in the IN database and
by the best detected 3G macro cell (if this feature is activated) to give macro level billing.
For emergency calls
The LAC and SAC must have geographical significance, but the operator may choose to
use the macro level LAC/SAC to minimize the impact on core network routing tables.
This macro level LAC and SAC can be populated in the IN database and by the best
detected 3G macro cell if this feature is activated.
Feature benefits
This feature enables an alternative means of setting the SAI for the owner, guests and
emergency calls using the Macro cell's LAC and Cell Id through the Small Cell
Auto-Detection Mechanism (Network listening), instead of depending solely on the
mobile network operator's pre-provisioned scheme. However, the Small Cell will still
have to fall back to the pre-provisioned scheme if there is no relevant Macro coverage.
An example of the use of the feature is where the SAI-SAC is used for preferential billing
purposes for calls handled on the Small Cell. In the case of emergency calls the SAI-SAC
must be set to a geographically relevant value to ensure correct routing to the public
safety answer point. This geographical relevance may be encoded within the Cell ID of
the Macro network.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
17-2
Issue 1 March 2013
....................................................................................................................................................................................................................................

Functional definition
This feature provides the capability to dynamically set the LAC and SAC field of the SAI
IE based on the macro cell information (LAC & macro Cell ID) (for SAC mapping)
retrieved by 3G network listening. The Small Cell uses the LAC and Cell ID of the best
3G macro cell (in terms of CPICH RSCP).
Depending on the OAM settings, the Small Cell may set the:
LAC in the SAI IE of RANAP Location Report message to the fixed Small Cell LAC
provided in the bulkCM or dynamically to the macro cell LAC retrieved from the best
macro cell.
SAC in the SAI IE of RANAP Location Report message to the fixed Small Cell SAC
provided in the bulkCM or dynamically to the macro cell Cell Id retrieved from the
best macro cell.
LAC in the SAI IE of RANAP messages (Initial UE message, Direct Transfer) to the
fixed LAC for owner, visitor or emergency call provided in the bulkCM as per b1718
or to the macro cell LAC retrieved from the best macro cell.
SAC in the SAI IE of RANAP messages (Initial UE message, Direct Transfer) to the
fixed SAC for owner, visitor or emergency call provided in the bulkCM as per b1718
or to the macro cell Cell Id retrieved from the best macro cell.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
17-3
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature dependencies
This features relies upon 3G Network Listening functionality, being operational in the
Small Cell, as this provides the neighboring macro cell data (such as LAC and Cell ID).
This features is an extension of Home tariff and visitors' access differentiated support
(b1718) feature.
Requirements
The Small Cell will activate or deactivate the feature based on the MIM setting.
The choice of which macro network to select the information from is OAM selectable to
one of the following options:
use 2G only (taking the information from 2G if available with suitable quality)
use 3G only (taking the information from 3G if available with suitable quality)
2G preferred (taking the information from 2G if available with suitable quality,

otherwise taking the information from 3G if available with suitable quality)
3G Preferred (taking the information from 3G if available with suitable quality,
otherwise taking the information from 2G if available with suitable quality)
The feature impacts the SAI-LAC or SAC and provides the operator the ability to either
manually provision these or to take them from the underlying macro network.
The choices of configuration may be set independently for the following category of
users:
Owner
Guest
Emergency call
The usage of SAI-LAC or SAI-SAC may be configured with one of the following
options:
SAI-SAC set to Cell ID of Macro & SAI-LAC set to provisioned value
SAI-SAC set to provisioned value & SAI-LAC set to LAC of Macro

SAI-SAC set to Cell ID of Macro & SAI-LAC set to LAC of Macro
If this feature is activated, there is no suitable macrocell detected (for example, the Small
Cell cannot decode the SIBs of the macro network), the Small Cell will populate the SAI
IE (LAC, SAC) as if the feature is deactivated. Reverting to Home tariff and visitors'
access differentiated support feature (b1718 ) and an alarm is raised to notify the operator.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
17-4
Issue 1 March 2013
....................................................................................................................................................................................................................................
Feature Interworking
If this feature is deactivated, the Small Cell will perform the actions as specified for
Home tariff and visitors' access differentiated support feature (b1718).
The 3G network listening feature (b1586) will provide the LAC and Cell ID of the best
3G macro cell. If the 3G network listening feature is deactivated and the best 3G macro
cell is also in OAM provisioned 3G macro cell list (List of FDDExtCells), the Small Cell
is able to use the LAC and Cell ID provided in the provisioned list.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
17-5
Issue 1 March 2013
....................................................................................................................................................................................................................................

Attributes of class BSR: Dynamic LAC-SAC allocation parameters
Parameter
Description
Syntax
DynamicSACLACAllocationActivation
This parameter activates or

deactivates the Dynamic
SAC-LAC allocation feature.
boolean
DynamicSACLACmacroConfig
This parameter determines

which Macro network the
Small Cell is to perform
Dynamic SAC LAC allocation.
enum TargetHO
Values
Options: use 2G only (gsm)/

3G only (fdd) or 2G preferred
(gsmPreferred ) or 3G
Preferred (fddPreferred).
Attributes of class LCELL: Dynamic LAC-SAC allocation parameters

Parameter
Description
Syntax
Values
DSAthresholdRSCP
This parameter defines whether

the best 3G macro cell is
suitable in terms of CPICH
RSCP.
integer
[-115..-25],
unit=dBm
DSAthresholdEcNo

suitable in terms of CPICH
EcNo.
integer
[-24..0], unit=dB
DSAthresholdRXLEV2G

suitable in terms of RXLEV
(45.008 8.1.4 -110...-48dBm)
for Dynamic LAC-SAC
allocation.
integer
[-110..-48],
unit=dBm
enableDynamicSACowner

the SAC of owner must use the
Cell Id of the macro cell.
boolean
enableDynamicSACguest

the SAC of guest must use the
Cell Id of the macro cell.
boolean
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
17-6
Issue 1 March 2013
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
enableDynamicSACEC

the SAC of emergency call
must use the Cell Id of the
macro cell.
boolean
enableDynamicSACfemto

the SAC of Small Cell must
use the Cell Id of the macro
cell.
boolean
enableDynamicLACowner

the LAC of owner must use the
LAC of the macro cell.
boolean
enableDynamicLACguest

the LAC of guest must use the
LAC of the macro cell.
boolean
enableDynamicLACEC

the LAC of emergency call
must use the LAC of the macro
cell.
boolean
enableDynamic:LACfemto

the LAC of the Small Cell
must use the LAC of the macro
cell.
boolean
Values
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
17-7
Issue 1 March 2013
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
17-8
Issue 1 March 2013
18

18
Overview
Purpose
This chapter describes the Multiple PDP contexts (79147) feature.

Contents
Multiple PDP Contexts
18-2
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
18-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number

Feature description
`Multiple Packet Data Protocol (PDP) contexts are used in W-CDMA networks for one of
two reasons :
QoS differentiation (Secondary PDP context)

Access Point Name (APN) Differentiation of services (Multiple primary PDP
contexts). This is the main purpose of the feature.
Multiple PDP contexts are available for interactive and background classes, but not for
streaming.
All PS RAB combinations are supported.
For HSPA and ECDH, PDP each context is taken over a separate MAC-d flow. For DCH,
PDP contexts are MAC-d multiplexed.
Secondary PDP contexts
The UE may request QoS differentiation of services using a NAS secondary PDP context
activation procedure. In this procedure the UE defines a traffic flow template (TFT)
which determines an IP packet filter based on characteristics such as:
Source/Destination Address
Port Number/Range
Protocol type
The GGSN and UE then filter all packets corresponding to this filter down the defined
secondary PDP context and all of the rest of the packets are sent down the primary PDP
context.
Multiple Primary PDP contexts
The UE may request a second primary PDP context. This request will result in a new IP
address being created. This enables an operator to route certain services through a
separate APN at the GGSN. This APN may then go to a private data network.
Examples include:
One PDP context for general IP networking and one for customer VPN services
One PDP context for general IP networking and one for operator IMS
One PDP context for general IP networking and one for a special service provided by
the operator.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
18-2
Issue 1 March 2013
....................................................................................................................................................................................................................................
In this context, multiple PDP contexts are much more of a necessity for the operator, and
if the multiple PDP contexts are supported by the macro, then lack of support on the
Small Cell would probably block user services.
Feature benefits
This feature enables those services which require multiple PDP contexts.
Impacted systems
Small Cell, BSG, SCMS, Security Gateway.

Restrictions/Limitations
The following restrictions and limitations apply to this feature:
QoS differentiation between different PDP contexts is not always provided.

This feature is not applicable to V1.x based platforms.
Feature type
Basic.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
18-3
Issue 1 March 2013
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
18-4
Issue 1 March 2013
19

19
Overview
Purpose
This chapter describes the prioritized open access (77735) feature.

Contents
19-2
UE tracking
19-4
Call admission control and DBC
19-5
Billing
19-7
19-8
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
19-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number

Feature description
This features introduces a new type of Small Cell, the Prioritized Open Access Small
Cell. Although this Small Cell provides open access to all UEs, priority is given to certain
UEs over others. For example, a Small Cell owner will have a higher priority than a
public user. The priority of users is considered for call admission control and dynamic
bearer control.
This feature allows an open access Small Cell to give priority to owners or guests. Since
the Small Cell is hosted by the owner, who pays the electricity bill and possibly also
provides the internet connection, preferential access is given to the owner. An example
case for the deployment of a prioritized open access Small Cell is a shop, where public
users are allowed to use the Small Cell,, but the shop owner has priority of access over
public users.
The prioritized open access Small Cell does not perform access control. The Access
Control List (ACL) is only used to determine the priority of users. A user is prioritized if
the IMSI of the user is contained in the ACL of owners or of guests.
In order to give this priority to preferred users, the Small Cell may do one of the
following:
redirect existing calls to the macro cell using the Active Call Redirect (ACR) feature
preempt existing PS calls
perform DBC of existing PS calls
This is necessary because the Small Cell has a limited call capacity.
Preemption will not be applied to an emergency call, regardless of the type of the user,
private or public.
The term semi-open access is equivalent to prioritized open access. Non-prioritized
users are called public users in this document. Private users are those classified as
owners or guests. A Small Cell Group which supports prioritised open access is limited to
a maximum of fifty Small Cells. The feature can be activated on individual Small Cells
using the SCMS provisioning system.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
19-2
Issue 1 March 2013
....................................................................................................................................................................................................................................
Feature benefits
For operators, this feature widens the Small Cell market. It allows operators to extend or
improve the coverage of the macro network without having to, for example, add new sites
and deal with the associated planning permission and site acquisition issues. The feature
is mainly aimed at improving service in public places such as shops and enterprises.
With this feature, the Small Cell may service all users in the vicinity, while still
permitting a priority service to be provided to the Small Cell owner and guests. There is a
slight cost to this benefit: when compared with a closed-access Small Cell, the owner of
the system may see some increased call setup times, or reduced PS data rates.
Impacted systems
Small Cell, BSG, SCMS.

Dependencies
None
None
Engineering impacts
To support this feature, the Small Cell is impacted as follows:
Support of new configuration capabilities

Classification of users (public, owner, guest) and storage for the duration of the call
UE tracking modifications
Enhancements for call admission control and DBC
Support for home-zone and public billing in the same Small Cell
The SCMS must support the configuration of the new attributes introduced for prioritized
open access. The Interface between the IT system (back office system) of the operator and
the SCMS must support a new access mode value.
To use this feature, the Small Cells must be upgraded to the Small Cell Solution release
supporting prioritized open access. It is not necessary to upgrade all Small Cells in the
cluster, but only those which will use the feature. All Small Cells belonging to the same
group must be upgraded if prioritized open access is used in a Small Cell Group.
Feature type
Optional
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
19-3
Issue 1 March 2013
UE tracking
....................................................................................................................................................................................................................................
UE tracking
The prioritized open access Small Cell combines the tracking mechanisms of both
Openand Closed Small Cells. The BSG identifies Small Cells based on IMSI entries
in the ACLs and in the IMSI directory. If a user is contained in the ACL of a prioritized
open access Small Cell, (that is, a private user), the user is not registered in the IMSI
directory of the Small Cell. If the user is not in the ACL (that is, a public user), the
Small Cell sends a UE Registration message to the IMSI directory of the BSG and applies
the UE registration mechanisms as supported by open access Small Cells.
The BSG always checks both the ACL and the IMSI directory when a UE must be paged.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
19-4
Issue 1 March 2013
....................................................................................................................................................................................................................................

The existing call admission control algorithm is extended to include consideration of
types of user in the selection of a call to be handed over to a macro cell, preempted or
downgraded. This means that only one call admission control algorithm is still applicable
for all access modes.
User types
The user types are:
Public users, that is, users not listed in any ACL

Guests, that is, users listed in the guest ACL
Owners, that is, users listed in the owner ACL
The user type of existing calls is considered for both new incoming non-emergency and
emergency calls.
An open access Small Cell classifies all users as public users. A closed access Small Cell
can support only guests and owners, but no public users. A prioritized open access Small
Cell supports all three types of users.
Principles
The existing principles of call admission control and DBC are not changed, that is, the
logic to determine whether a call is redirected, preempted or downgraded. This means that
the enhanced call admission control capabilities introduced by this feature are applicable
for all Small Cells regardless of their access mode.
If call admission control has decided to perform Active Call Redirect (ACR), the Small
Cell will hand over a CS voice call in the following order:
1. CS call of a public user
2. CS call of a guest
3. CS call of an owner
The operator can configure whether ACR should be applied to the calls of any users, or
only to the calls of public users. This configuration option only applies for prioritized
open access Small Cells and non-emergency calls.
If the macro network does not support the Serving Radio Network Subsystem (SRNS)
Relocation procedure used for ACR, then ACR must be disabled and preemption or Radio
Access Bearer (RAB) downgrade must be applied according to the Call Admission
Control (CAC) rules.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
19-5
Issue 1 March 2013
....................................................................................................................................................................................................................................
Where call admission control has decided to perform preemption, or downgrade a PS

RAB, the Small Cell tries to preempt or downgrade a PS only call in the following order:
PS only call of a public user

PS only call of a guest
PS only call of an owner
For both preemption and downgrading, the operator can configure whether the calls of
any users or only those of public users can have the procedure applied to them. As before,
these configuration options only apply for prioritized open access Small Cells and
non-emergency calls.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
19-6
Issue 1 March 2013
Billing
....................................................................................................................................................................................................................................
Billing
The prioritized open access Small Cell supports differentiated billing for public users,
owners and guests. This requires new configuration options for the Service Area
Code/Location Area Code (SAC/LAC) values to be used in the Service Area Identifier
(SAI) for public users.
The Small Cell also supports different network names for public users, owners and
guests. This allows the system to indicate different billing rates for the different types of
users while they are camping on the same Small Cell.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
19-7
Issue 1 March 2013
....................................................................................................................................................................................................................................

Attributes of class BSR
Parameter
Description
Syntax
Values
accessMode
Defines whether a Small Cell

operates in closed access
mode, open access mode or
prioritized open access mode.
enum
closedAccess
activeCallRedirectEnable
Enables and disables the active

call redirection to macro
network feature.
boolean
activeCallRedirectAllUsers
Specifies whether all users or

only public users are selected
for active call redirection on
establishment of a new
non-emergency call.
boolean
enableNormalCallPreemption
Indicates whether to preempt a

PS call for CS call
establishment when CAC
failed for the RRC connection
of the CS call establishment.
boolean
enableNormalCallPreemptionAllUsers

for preemption on
non-emergency call.
boolean
enableRABDowngradeAllUsers

for RAB downgrade on
non-emergency call..
boolean
openAccess
semiOpenAccess
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
19-8
Issue 1 March 2013
20
20 enhancements for
FM
Metro Cells
Overview
Purpose
This chapter describes the FM enhancements for Metro Cells (101373) feature.
Contents
20-2
Real-time monitoring of Small Cell status from the Small Cell Gateway
20-3
20-7
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
20-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number

Feature description
This feature provides the ability to inform the operator of the operational state of a limited
number of Metro Cells in real time.
This feature provides enhancements to fault management for operator-managed Metro
Cells to support the real-time reporting and monitoring of the operational and service
status of the cells.
Real-time reporting of the operational and service status is not required for residential
Small Cells, because these Small Cells are under the control of the end-user, and can be
turned on and off at any time. This, together with the large number of residential Small
Cells, means that real-time information is not very useful to the operator. However, for
Metro Cells that are deployed as public cells to complement the macro network, the
operator must know in real-time whether those Metro Cells are up and running or out of
service.
Feature benefits
This feature enables better customer experiences for managing the Metro Cells, by
providing real-time operational status and service monitoring of operator-managed Metro
Cells.
Impacted systems
Small Cell, Small Cell Gateway, SCMS.

Dependencies
FRS-104306, CM/FM/PM enhancement for Small Cell at the SCMS.

None
Feature type
Basic
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
20-2
Issue 1 March 2013
Real-time monitoring of Small Cell status from the Small

Cell Gateway
....................................................................................................................................................................................................................................
Real-time monitoring of Small Cell status from the Small Cell

Gateway
Mechanism for detecting failures
The interface between the SCMS and Small Cell uses TR-069, so no heartbeat
mechanism exists to detect if a Small Cell goes out of service when it loses power or
communications with the operators network.
The link between the BSG part of the Small Cell Gateway and the Small Cell uses SCTP
([S.4]), which can detect connection failure by monitoring the number of retransmissions
and heartbeat idle connections. The Small Cell Gateway already uses this to detect failure
of the Small Cells. On detecting such SCTP association failures, the Small Cell Gateway
releases the dynamic resources associated with the Small Cell, including deletion of the
Small Cell from its registration table.
This feature enhances the Small Cell Gateway to raise an alarm to the SCMS when it
detects SCTP association failure with a Small Cell with real-time monitoring enabled.
Monitoring by the Small Cell Gateway can also detect further failure scenarios when a
Small Cell is not registered with it:
when the SCTP association is closed due to the Small Cell Gateway receiving a
shutdown request from the Small Cell
when a Small Cell fails to register within a configurable time period after BSG
initialization
The Small Cell normally sends a shutdown request during a graceful reset in other cases,
such as if its application process crashes. To avoid raising an alarm whenever a Small
Cell resets, the Small Cell Gateway can run an additional timer to allow the Small Cell
time to reconnect and reregister before raising an alarm.
Scenarios exist in which the Small Cell detects a fault and shuts down the SCTP
association as well as raising an alarm directly to the SCMS, so that the SCMS may
receive an alarm from both the Small Cell Gateway and the Small Cell.
Avoiding floods of alarms
There may be thousands of Small Cells for a Small Cell Gateway to monitor, so a
mechanism to avoid flooding the SCMS with alarms is required.
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 that contains the identity of the Small Cell.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
20-3
Issue 1 March 2013

Cell Gateway
....................................................................................................................................................................................................................................
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 bsrOutOfService alarm. Instead, when the threshold is crossed, the
BSR Gatewaycraises a massBsrOutOfService alarm to indicate a more widespread failure.
This contains no identification of the individual Small Cells.
Once the total number of failed Small Cells falls below the threshold, the Small Cell
Gateway can start raising the bsrOutOfService alarm again, including for any failed Small
Cells that the alarm was not raised for because at the time the threshold was passed.
Alarm clearance
The bsrOutOfService alarm would normally be cleared by the Small Cell Gateway when
the Small Cell reregisters with the Small Cell Gateway after reestablishing the
connection.
The alarm should also be cleared if the Small Cell is removed from the Small Cell
Gateways provisioning or if monitoring of the Small Cell is disabled.
The massBsrOutOfService alarm can be automatically cleared once the total number of
failed Small Cells falls below the threshold.
Real-time state change notifications
Many of the Managed Objects (MOs) of the Small Cell have operational state and
availability status parameters which reflect the status of the resources they model.
Changes in these parameters are already reported by the Small Cell to the SCMS, using
the TR-069 Inform method, but not in real-time as passive notification is used. This
feature allows the option for changes in these parameters to be reported in real-time using
TR-069 active notification.
Currently, the operational state of several MOs is required to deduce whether the Small
Cell is providing service. These include BSR, LCell, ItfBVG and ItfBPG. However
reporting the states changes of all these MOs in real time could lead to a lot of extra load
on the SCMS, especially as TR-069 requires a new connection to be setup for each new
Inform message. Scenarios exist in which, due to MO dependencies, a single fault causes
several, or even all, of these MOs to change state. Even if the Small Cell could ensure that
all state changes related to a single fault were sent in the same Inform, there are also cases
where different faults effecting different MOs are raised at slightly different times due to
the same underlying problem.
The Small Cell is a relatively simple network element, so the information sent in
real-time is restricted to the operational state and availability status of the top-level BSR
MO. This present a simpler picture to the operator, who can obtain the state of the other
MOs using GetParameterValues to diagnose the problem further.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
20-4
Issue 1 March 2013

Cell Gateway
....................................................................................................................................................................................................................................
It would be rather a large change to set the operationalState of the top level BSR MO to
disabled whenever the Small Cell does not provide service. For this feature, a simpler
alternative is taken where the availabilityStatus of the BSR MO is enhanced to indicates
degraded when the BSR MO is enabled but at least one of the LCell, ItfBVG or ItfBPG
MOs is disabled due to a fault.
The availabilityStatus parameter is a bit mask. The expected combinations are:
operationalStatus=enabled, availabilityStatus=000000000
operationalStatus=enabled, availabilityStatus=001000000 (degraded)
operationalStatus=disabled, availabilityStatus=000000010 (failed)
The SCMS presents these in a user-friendly way to the operator.

These parameters are made Forced Inform Parameters i.e. they are included in every
TR-069 Inform message, whether or not their values have changed (this follows TR-196
for its OpState parameter). Forced inclusion in the BOOT Inform is necessary to ensures
that the HDM is kept in sync after the Small Cell reboots.
Enhancements of existing Small Cell alarms direct to SCMS
Due to the expected large numbers of Small Cells, Small Cells do not report faults that are
likely to be widespread (for example, due to link outages or faults with other network
elements) as real-time alarms directly to the SCMS. This avoids flooding the SCMS with
alarms. Therefore only local faults that affect service are suitable for raising as real-time
alarms.
Reclassification of existing faults
The Small Cell sends alarms only for all faults with a severity of Critical in the
DATA-SRS (alarms are only sent when BSR::faultNotificationEnabled=true).
Examination of the severity of the faults currently reported by the Small Cell has
highlighted the following:
The fault txMalfunction, which indicates a hardware problem which can only be
solved by replacing the small cell, needed to be promoted from major to critical.
There are critical faults which may not be of interest in being reported in real-time to
an operator. For example, basebandReconfigfailed, layerOneResetFailure, where the
small cell immediately escalates to a reset; and securityViolation, about which the
operator cannot do much. Some operators might want to turn these alarms off.
Non-critical faults exist which some operators may want reported as real-time alarms.
For example, overTemperature and underTemperature, which are temporary and will
recover automatically when the temperature moves back in range. In the
home/business Small Cell, where the operator has no control over the environment of
the Small Cell, it is not useful to report this to the operator. However as these faults
are local and disable service, the small cell operator may require in them, so it would
be useful to be able to report these faults via a real-time alarm.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
20-5
Issue 1 March 2013

Cell Gateway
....................................................................................................................................................................................................................................
Therefore it is desirable to introduce flexibility as to which faults map to a real-time

alarm, rather than a fixed list based on critical severity. This was achieved by introducing
a new MIM parameter indicating the faults which map to real-time alarms.
The SCMS needs to know which alarms it has to support, so this list can currently only
contain faults from a fixed subset of the Small Cell faults, for example, the critical ones
plus a limited number of other faults such as the temperature faults. To minimize future
rework, the list should be a reduced version of the TR-196 SupportedAlarm parameter, for
example a sequence of
EventType (string indicating the fault id)

ReportingMechanism (enum of Expedited, Logged).
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
20-6
Issue 1 March 2013
....................................................................................................................................................................................................................................
Attributes of class BSR of Small Cell model
Parameter
Description
Syntax
enableRealTimeSCN
Controls the enabling or

disabling of the real-time state
change reporting of a particular
Small Cell.
boolean
supportedAlarmsInRealTime
Used to configure the list of

alarms to be reported in real
time. The maximum size of
this list is limited (for example
to 20).
sequence of EventType
(string indicating the fault
id), and
ReportingMechanism
(enum of Expedited,
Logged).
This parameter is a cut-down

version of the SupportedAlarm
parameter defined in TR-196.
Values
Attributes of class BSR of Gateway model

Parameter
Description
Syntax
enableServiceMonitoring

disabling of service monitoring
for the Small Cell. If set to
True, the generation of
bsrOutOfService alarms is
enabled for the Small Cell.
boolean
Values
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
20-7
Issue 1 March 2013
....................................................................................................................................................................................................................................
Attributes of class BSG of Gateway model

Parameter
Description
Syntax
Values
maxNumBSRServiceAlarms
Specifies the threshold for the

number of bsrOutOfService
alarms that have been reported
to SCMS but have not yet
cleared. Below this threshold,
occurrences of the
bsrOutOfService alarm are
reported to SCMS. When the
threshold is exceeded
occurrences of the
bsrOutOfService alarm are
logged but not reported to
SCMS.
integer
[1..10000]
enableBSRServiceMonitoring

disabling of Small Cell Service
Monitoring on the Small Cell
Gateway. If set to True, the
generation of Small Cell
service alarms is enabled at the
Small Cell Gateway
boolean
bsrRegisterAfterFailureTimer
Specifies the time in seconds

for the Small Cell Gateway to
wait for a Small Cell to
reregister before sending the
bsrOutOfService alarm. A
timer is run for Small Cells for
which SCTP association failure
has been detected and which
have the BSR::enableServiceMonitoring attribute set to
True. If the timer expires
before the Small Cell has
reregistered, then the
bsrOutOfService alarm is
raised.
integer
[1..65535],
unit=secs
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
20-8
Issue 1 March 2013
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
bsrRegisterAfterInitTimer

for the Small Cell Gateway to
wait for a Small Cell to register
before sending the
bsrOutOfService alarm. After
Small Cell Gateway
initialization, a timer is run for
Small Cells which have not
registered with the Small Cell
Gateway and have the BSR::
enableServiceMonitoring
attribute set to True. If the
timer expires before the Small
Cell has registered the
bsrOutOfService alarm is
raised.
integer
[1..65535],
unit=secs
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
20-9
Issue 1 March 2013
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
20-10
Issue 1 March 2013
21
GPS Localization
21
Overview
Purpose
This chapter describes the GPS localization (75545) feature.

Contents
GPS Localization
21-2
GPS Localization Concept
21-4
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
21-1
Issue 1 March 2013
GPS Localization
GPS Localization
....................................................................................................................................................................................................................................
GPS Localization
Feature number

Feature description
This feature introduces the capability for a Small Cell to localize itself using simple GPS
method. To achieve this, the Small Cell supports a GPS receiver including an integrated
GPS antenna system, and optionally an external GPS antenna.
GPS localization information will be used in the location check in Small Cell to ensure
that it is in the authorized area.
The provisioned geographical location (also called authorized location) is used by
auto-configuration function to allocate the Small Cell carrier frequency, area code
(LAC/RAC/SAC), neighboring cells and the gateway addresses. So, it is imperative to
check the location of the Small Cell is within the authorized area. Geographical
coordinates obtained through the GPS receiver may also be used for emergency call, and
location based services, as they could be more accurate than the provisioned authorized
location.
Feature benefits
This feature allows GPS location to be detected and localizes the Small Cell location. It
enables the service provider to determine if the Small Cell is located within the boundary
of the transmission coverage. And also the service provider can stop transmission on the
Small Cell if it is out of their transmission license.
The end user may not be directly impacted by this feature.
Impacted systems
Small Cell, SCMS

Dependencies
The GPS localization feature depends on the following features:
Feature 34588 - Detection of location changes

Feature 75886 - V2 Hardware Architecture (1900/850 HW Small Cell)
This feature would require V2 Small Cell hardware, ie GPS on board to work. Initial start
up would probably require Small Cell to be near to the window to receive a GPS signal.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
21-2
Issue 1 March 2013
GPS Localization
GPS Localization
....................................................................................................................................................................................................................................
Engineering impacts
Provisioning of Small Cell location, allow radius of transmission

The Small Cell will check against it provisional location before allow transmission.
Feature type
Optional
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
21-3
Issue 1 March 2013
GPS Localization
....................................................................................................................................................................................................................................

Definition
This GPS Localization feature detects the current geographical location of the Small Cell
using a GPS receiver in the Small Cell. The GPS receiver provides the geographical
location to the Small Cell which is then cross-checked against the Small Cell's
provisioned authorized location. If the GPS provided location is not within a specified
range of the Small Cell provisioned authorized location then the Small Cell is prevented
from transmitting.
The precise geographical location provided by the GPS receiver is stored in the Small
Cell and may be used in an emergency call, or location based services, and reporting the
geographical location of the cell for the Presence API.
Principle
During the offline auto-configuration phase, the authorized location is pre-configured for
each Small Cell based on the subscriber address provisioned through the IT system. The
authorized location may be described using Ellipsoid point with uncertainty circle (cf
3GPP 23.032). This information is a part of the bulk CM file of the Small Cell.
The geographical coordinates provided by the operator IT system are also used for the
location of emergency call, and location based services.
The GPS receiver enables the Small Cell to self-localize, at initial startup and successive
startups, before radiating any 3G TX signal. The Small Cell then checks that the GPS
geographical coordinates are within the limits of the authorized location provided by the
IT system.
If the check is passed, then the Small Cell is authorized to proceed with the
auto-configuration and ultimately to transmit 3G signal. If the check fails, then the Small
Cell auto-configuration is stopped and the user is invited to contact the customer service.
For the purpose of the detection of location change, the Small Cell localizes itself
periodically and at every power on and performs the location check as described above.
GPS Localization on Small Cell startup
The following figure shows the process sequence for GPS localization on Small Cell
startup:
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
21-4
Issue 1 March 2013
GPS Localization
....................................................................................................................................................................................................................................
Figure 21-1 GPS Localization on Small Cell startup
Initial Startup
The first time, the Small Cell starts up or after a factory reset, it always uses the GPS
receiver to detect its current geographical location. If the GPS receiver fails to return its
location within a configurable time and accuracy, then it is considered as failed.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
21-5
Issue 1 March 2013
GPS Localization
....................................................................................................................................................................................................................................
The Small Cell can get its geographical location from the GPS unit without a backhaul
connection.
If the GPS localization feature is disabled or GPS receiver is non-funcational, it uses
Feature 34588 - Detection of location changes, and Feature 78230 - National location
lock.
Subsequent Startups
For subsequent start ups, the GPS receiver uses the previously stored geographical
location to assist in detection of its current geographical location. If the GPS receiver
does not provide the geographical location within a configurable time and accuracy, then
it is considered as failed.
Note: When the Small Cell is starting up for the first time, it runs an auto configuration
with location check and movement check to gather information for subsequent checks.
If the GPS fails to provide a geographical location, the operator may enable the used
Feature 78230 - National location lock or wait for the GPS receiver to get a fix on the
location.
Alarms
A critical alarm and visual external indication are set if the GPS fails to provide a
geographical location within the specified time. If non-GPS checks are permitted on GPS
failure, and the non-GPS checks pass, then the alarm should not be raised.
The alarm is cleared only if, the GPS receiver fixes its location if it is allowed to
continue, or until location check is passed or operator overrides.
Optimization
If the GPS receiver fails to locate its geographical location within the time specified, the
GPS receiver continues detecting its location until it is successful. The critical alarm and
visual external indication are cleared after the GPS location gets a fix on its geographical
location.
If the location check fails, it is allowed to continue optimizing its location until the GPS
location check succeeds or legacy location/national location checks or movement checks
pass. GPS receiver provides a geographical location with a radius of uncertainty. If the
GPS location, including the uncertainty area, is within the Small Cell provisioned
geographically with a configurable area of authorized area, then the Small Cell is in the
correct location and is allowed transmission.
Small Cell GPS Location Detection
The following diagram describes the feasible radii for geographical location optimization:
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
21-6
Issue 1 March 2013
GPS Localization
....................................................................................................................................................................................................................................
Figure 21-2 Small Cell GPS Location Detection
The Small Cell does not start transmission if the geographical location, including the
uncertainty area, from the GPS receiver is not contained within the configurable radius of
the provisioned authorized location. The scanned location accuracy and radius margin of
error to the provisioned location are configurable through OAM.
The operator may override GPS location check failure through OAM. If the Small Cell
has failed the location check using GPS receiver, it raises an alarm. When GPS
localization later passes, or the operator allows override location check, the alarm is
cleared.
A visible external indication is given to the user that the GPS location check has failed. If
it is passed, or the operator overrides location check, then the external indication is
cleared. The Small Cell stores its geographical location from the GPS receiver, this
includes Ellipsoid point with scanned location accuracy in meters if the GPS receiver got
its location fixed.
If the Small Cell is not equipped with a GPS receiver it uses the Features 34588 Detection of location changes and Feature 78230 - National location lock. Small Cell
supports the Location Reporting Control procedure and report directly in request
type in Location Reporting Control message.
The Small Cell supports the population of the GPS location into the geographical location
used for the Presence API as a configurable option. Small Cell supports the LOCATION
REPORT message including the Service Area of the UE in the Area Identity IE sent to the
CN.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
21-7
Issue 1 March 2013
GPS Localization
....................................................................................................................................................................................................................................
If the Small Cell is configured to report geographical location using GPS location, the
location report contains:
the Geographical Area IE within the Area Identity IE containing either a point with
indicated uncertainty which fulfils the requested accuracy, and
the Accuracy Fulfilment Indicator IE with the value requested accuracy
fulfilled or requested accuracy not fulfilled.
If the Small Cell is configured to report provisional location, it uses the provisional
location provided by the operator.
If GPS location is not available, it uses the provisional location by the operator.
Note: See TS25413, section 8.19 Location Reporting Control.
Configuration Management
Table 21-1
Name
Description
Syntax
ScanOnBoot
Enables or disables
GPS scans during the
Small Cell start up.
boolean
authorisedLocationRadius
Maximum location
radius allowed for
provisioning a Small
Cell.
integer
enableGPSLocationCheck
Enable use of GPS

Location check
otherwise fall back to
non-GPS location and
movement checks.
boolean
enableNonGPSLocationCheckForFailGPSInitialStartup
Enable to use
non-GPS location
check if GPS receiver
fails to return a
geographical location
at initial startup.
boolean
enableNonGPSLocationCheckForFailGPSSubsequentStartup
Enables non-GPS
movement check if
GPS receiver fails to
return a geographical
location at subsequent
startup.
boolean
Values
[1..1000],
unit=meters
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
21-8
Issue 1 March 2013
GPS Localization
....................................................................................................................................................................................................................................
Table 21-1
(continued)
Name
Description
Syntax
LastSuccessfulScanTime
Specifies the date and

time, when the GPS
was scan last
completed
successfully. This
value is retained
across reboot. The
values for
LockedLatitude,
dateTime
Values
LockedLongitute
and
NumberOfSattelites correspond
to this time. If a scan

has never succeeded
before, the value will
be Unknown Time
value, as defined in
TR-106a2 [4] Section
3.2.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
21-9
Issue 1 March 2013
GPS Localization
....................................................................................................................................................................................................................................
Table 21-1
(continued)
Name
Description
Syntax
Values
LockedLatitude
This parameter
specifies the actual
location of the FAP,
returned by the GPS
Diagnostics Test. It
specifies the latitude
of the device's
position in degrees,
multiplied by 1
million. The positive
value signifies the
direction, north of the
equator. The negative
value signifies the
direction, south of the
equator. Range is
from: 9000.00
South (-90,000,000)
to 9000.00 North
(90,000,000).
Example: A latitude
of 1319.43 N would
be represented as
13,323,833, derived
as (13*1,000,000)+
integer
[-90000000..90000000]
((19.43*1,000,000)/
60). Latitude of
500.00 S would be
represented as value
-50,000,000. This
value is retained
across reboots and is
only reset after
another scan
completes
successfully. If a scan
has never succeeded
before, the value 0 is
reported.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
21-10
Issue 1 March 2013
GPS Localization
....................................................................................................................................................................................................................................
Table 21-1
(continued)
Name
Description
Syntax
LockedLongitude
integer
This parameter
specifies the actual
location of the FAP,
returned by the GPS
Diagnostics Test. This
parameter specifies
the longitude of the
device's position in
degrees, multiplied
by 1 million. The
positive value
signifies the
direction, east of the
prime meridian. The
negative value
signifies the
direction, west of the
prime meridian.
Range is from:
18000.00 West
(-180,000,000) to
18000.00 East
(180,000,000).
Example: A longitude
of 1319.43 E would
be represented as
13,323,833, derived
as (13*1,000,000)+((19.43*1,
000,000)/60). A
longitude of 5000
W would be
represented as value
-50,000,000. This
value is retained
across reboots and is
only reset after
another scan
completes
successfully. If a scan
has never succeeded
before, the value 0 is
reported.
Values
[-180000000..
180000000]
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
21-11
Issue 1 March 2013
GPS Localization
....................................................................................................................................................................................................................................
Table 21-1
(continued)
Name
Description
Syntax
Values
lockedHorizontalAccuracy
The location accuracy

provided by the GPS
receiver.
integer
unit=meters
scanTimeoutInitalStartup
Maximum time
allowed for GPS to
provide location to
requested accuracy at
initial startup.
integer
[1..65000], unit=secs
scanTimeoutSubsequentStartup
Maximum time
allowed for GPS to
provide location to
requested accuracy at
subsequent startup.
integer
[1..65000], unit=secs
scannedLocationAccuracy
Minimum accuracy
required by GPS
receiver when it
scanned it location.
integer
[1..100], unit=meters
enableProvisionedLocationReport
Enables Small Cell to

report provisioned
location rather than
GPS location.
boolean
enableAllowedGPSAfterTimerExpired
Enables Small Cell

GPS function even if
the GPS receiver fails
to fix within the time
specified.
boolean
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
21-12
Issue 1 March 2013
22
22 enhancements for
PM
Metro Cells
Overview
Purpose
This chapter describes the PM enhancements for Metro Cells (101681) feature.
Contents
22-2
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
22-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number

Feature description
In the Small Cell deployment, a set of Small Cells which need to be closely monitored by
the operator, can report each day a set of hourly values for Performance Management
(PM). The objective of this feature is to increase the periodicity of QoS information
reporting from 1 day to 1 hour without any other change. It allows the operator to have a
frequent, and therefore a better view of the performance of selected operator managed
Metro Cells.
The PM reporting time should be randomized to avoid overloading the SCMS, and the
files should be compressed.
The Small Cell supports a MIM parameter PM::transferFrequency, to configure the

transfer frequency of the PM files either in hourly or in daily reporting.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
22-2
Issue 1 March 2013
23
23
Multiple
PDP Contexts
(3PS + CS)
Overview
Purpose
This chapter describes the Multiple PDP Contexts (3PS + CS) (76984) feature.
Contents
23-2
Multiple PDP overview
23-3
Call Processing Procedures
23-4
23-5
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
23-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number

Feature description
Feature 76984 introduces the support of three, PS interactive or background QOS PDP,
contexts towards the UE/SGSN.
Feature benefits
If the UE supports three PDP contexts and the Small Cell does not, the service may be
blocked to the user.
Impacted systems
Small Cell, SCMS.

Dependencies
None
None
Engineering impacts
None
None
Feature type
Optional
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
23-2
Issue 1 March 2013
....................................................................................................................................................................................................................................

Introduction
Feature 76984 is an extension of the feature 79147 and introduces the following:
Support for 3, PS interactive or background, PDP contexts (both supported by feature

79147). As in feature 79147, common PS RAB combinations/rates are supported for
1,2,3 PDP contexts.
RLC re-distribution among the PDP contexts, following RAB establishment/release,
to optimize the UE RLC memory between the PDP contexts.
RAB Support
The following RAB combinations are supported in the 3 PDP context:

Table 23-1
DCH/DCH+DCCH (+CS 12.2 Speech)
UL
DL
PDPs
384
384
1,2,3
128
384
1,2,3
64
384
1,2,3
128
128
1,2,3
64
128
1,2,3
64
64
1,2,3
32
32
1,2,3
1,2,3
Table 23-2
DCH/HS+DCCH (+CS 12.2 Speech)
UL
DL
PDPs
384
HS
1,2,3
128
HS
1,2,3
64
HS
1,2,3
Table 23-3
E-DCH/HS (+CS 12.2 Speech)+DCCH
UL
DL
PDPs
E-DCH
HS
1,2,3
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
23-3
Issue 1 March 2013
....................................................................................................................................................................................................................................

The following call flows are added for feature 76984:
Usecase
Start
Action
End
UE in idle has three

PDP contexts
preserved and data is
present for one of
them.
DCCH
Add 3 I/B RABs
DCCH+3I/B
User activates two

PDP contexts whilst
one is active.*
DCCH+1I/B
Add 2 I/B RABs
DCCH+3I/B
User activates a third

PDP context whilst
two are active.
DCCH+2I/B
Add 1 I/B RABs
DCCH+3I/B
User deactivates one

PDP context.
DCCH+3I/B
Release 1 I/B RABs
DCCH+2I/B
User deactivates two

PDP contexts.*
DCCH+3I/B
Release 2 I/B RABs
DCCH+1I/B
User deactivates three

PDP contexts.*
Release due to
inactivity, and either
CS is up or SGSN
does not release Iu.
DCCH+3I/B
Release 3 I/B RABs
DCCH
Note: Usecases marked with * are unlikely scenarios.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
23-4
Issue 1 March 2013
....................................................................................................................................................................................................................................

Configurable parameters
Name
Description
Syntax
Values
maxNoOfMpdpSupported
Maximum number of
supported PS I/B
PDP contexts
integer
1...3
Note: isMpdpIBsupported must also be set to TRUE to activate the feature.

Performance Counters
Multiple PDP contexts feature supports the following performance counters:
RAB.AttEstabThirdPS.sum
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
23-5
Issue 1 March 2013
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
23-6
Issue 1 March 2013
24
24
Extended
ACL size for
large femto groups
Overview
Purpose
This chapter describes the Extended ACL size for large femto groups (92068) feature.
Contents
24-2
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
24-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number

Feature description
This feature extends the size of the ACL of a Small Cell group to support medium or large
Enterprise deployments, where thousands of employees may be allowed to access a
particular Small Cell group. Without this feature, the ACL used by a Small Cell or group
can contain up to 256 entries.
For medium to large enterprises with several hundreds or thousands of employees, this
limit is too restrictive. Even in a relatively small office, where the number of employees
present in the enterprise premises may be low at any given time, they may wish to grant
access to a much larger number, for example, to employees from other sites or remote
workers.
With this feature, a Small Cell group in closed or 'prioritized open access' mode can have
an ACL with up to 10 000 members.
However, that the total number of ACL entries in a Small Cell Gateway (including all
groups and non-groups) is limited. The total number of ACL entries that can be held on
the Small Cell Gateway is the same as applied without this feature, where each Small Cell
can have an ACL with up to 256 entries.
Feature benefits
Service provider benefits
Ability to support large enterprises where more than 256 employees must be allowed in a
Small Cell group
End user benefits
Service is available to all users at all sites of an enterprise.

Impacted systems
Small Cell
Small Cell Gateway (BSG, BPG, BVG)
SCMS
Dependencies
Provisioning is dependent on the SCMS being able to provision the HNB Identity in the
Small Cell configuration data transferred to the Small Cell Gateway.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
24-2
Issue 1 March 2013
....................................................................................................................................................................................................................................
Restrictions and system impacts

Macro to Small Cell handover
The selection of target Small Cells for incoming macro handovers depends primarily on
the PSC used by each Small Cell (in the case of closed access or prioritized open access
Small Cells). Typically, a small number (for example, 6) PSCs is reused across a whole
Small Cell group. A significant part of each Small Cell group may thus be selected as an
initial target list.
The Extended ACL feature makes this problem much more acute. For any one group, the
ACL size is extended to 10,000 IMSIs, greatly increasing the chances of any one IMSI
being in the list. However, the point of the feature is that the same ACL is used in
multiple locations for multiple Small Cell groups within an enterprise. Thus, unless a
filter based on location data is applied, a given relocation attempt may target up to a sixth
of all the Small Cells in the enterprise at all enterprise locations.
If the set of target Small Cells consistently exceeds the maximum number set by the
OAM parameters, then all handover attempts from the macro call may be adversely
affected.
Presence
If presence reporting is configured for more than 256 IMSIs on a Small Cell, then it is
configured for All IMSIs in the Extended ACL. If this occurs, the network is likely to
generate a large amount of presence information.
Feature type
Optional.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
24-3
Issue 1 March 2013
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
24-4
Issue 1 March 2013
25
25
Small
Cell network
support for end-to-end
call and subscriber trace
Overview
Purpose
This chapter describes the Small Cell network support for end-to-end call and subscriber
trace (78594) feature.
Contents
Small Cell network support of end to end call and subscriber trace
25-2
Small Cell network support of end to end call and subscriber trace parameters
25-4
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
25-1
Issue 1 March 2013
Small Cell network support for end-to-end call and

subscriber trace
Small Cell network support of end to end call and

subscriber trace
....................................................................................................................................................................................................................................
Small Cell network support of end to end call and subscriber

trace
Feature number

Feature description
This feature enables the network operator to trace a specific subscriber within the Small
Cell network on the basis of the IMSI of the subscriber.
Subscriber tracing provide protocol level details of an ongoing call and provides the
operator with information for troubleshooting issues in the Small Cell network and
resolving these issues proactively. It also supports the maintenance of the Small Cell
network quality at a high level and supports testing new features in the network. The
ability to log data on any interface at call level for a specific user enables the operator to
get information that cannot be derived from performance measurements. The feature
enables the operator to test the capabilities of handsets from various vendors in the Small
Cell environment. Since 3G has many features that are very handset dependent, the
impact of these features on the network performance can be very efficiently tested.
The subscriber tracing function is supported by the SCS Small Cell Gateway, IPC, and
Small Cell. The SCMS provides the capability to activate and deactivate the tracing of a
specific call and subscriber. Based on the signaling information, the NEs keep track of the
subscriber being traced and records messages when needed. The trace follows the
subscriber as long as the call is within the control of the Small Cell network. After
completion of the subscriber trace, the trace records are collected by the SCMS from all
NEs. The records can then be provided at the northbound interface for retrieval.
Feature benefits
The results of a subscriber trace provide the operator with important information for
troubleshooting issues in the Small Cell network and resolving these issues proactively. It
also supports the testing of new features and the testing of the capabilities of UEs.
End user benefits
None
Impacted systems
Small Cell
Small Cell Gateway
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
25-2
Issue 1 March 2013

subscriber trace

subscriber trace
....................................................................................................................................................................................................................................
SCMS
IPC
Dependencies
None
Software debug trace is not included in the subscriber trace.

The Iur and Iub traces as defined in 3GPP TS32.423 are not part of the subscriber
trace as these interfaces are not supported by Small Cell systems.
The Small Cell trace records are limited to ASN.1 messages only. This feature does
not provide decoded messages.
Feature type
Optional.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
25-3
Issue 1 March 2013

subscriber trace

subscriber trace parameters
....................................................................................................................................................................................................................................
Small Cell network support of end to end call and subscriber

trace parameters
Small Cell
Attributes of class SubscriberTraceConfig
Parameter
Description
Syntax
Values
subscriberTraceEnable
Enables and disables the

feature.
boolean
maxParallelSubscriberTraces

number of active parallel call
traces that can be supported on
the Small Cell.
uint16
[1..64]
sftpServer
Specifies the file server where

Subscriber Trace files will be
pushed by the Small Cell. It
will be in either of the formats
of FQDN or IP address, for
example, 135.168.0.1 or
xxx.yyy.com.
string
length=256
rootDirectory
This attribute defines the root

directory for Subscriber Trace
files to be pushed to on the
SCMS File Server.
string
length=100
Small Cell Gateway

Parameter
Description
Syntax
Activates the subscriber trace

feature on the Small Cell
Gateway. When set to True the
feature is enabled.
boolean
sftpServer

pushed by the Small Cell
Gateway. It will be in either of
the formats of FQDN or IP
address, for example,
135.168.0.1 or xxx.yyy.com.
string
Values
length=256
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
25-4
Issue 1 March 2013

subscriber trace

....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
rootDirectory
Specifies the root directory for

RF Trace files to be pushed to
on the SCMS File Server.
string
length=100

number of active parallel call
traces that can be supported on
the Small Cell Gateway.
uint16
[0..100]
Attributes of class SubscriberTrace

Parameter
Description
Syntax
Values
iMSI
Specifies the IMSI of the call

that is to be traced.
string
length=15
traceId
Specifies the trace identifier

assigned to the subscriber
trace. It is a decimal string with
a fixed length of 3, for
example, 001, 101. It must be
unique within the list of traces
being configured.
string
length=3
traceReportingPeriod
Specifies the time interval over

which the trace file is to be
reported to the file server.
enum TraceReportingPeriod
traceRecordingSessionRef
This parameter identifies a

trace recording session for a
subscriber trace.
uint16
traceDuration
Specifies the time duration of

the subscriber trace.
uint16
traceStatus
Provides the status of the

tracing activity.
enum TraceStatus
traceEnabledBSRs
Contains the list of the Small

Cells for which the subscriber
trace has been enabled for this
subscriber.

TraceEnabledBSRs
unit=mins
step=15
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
25-5
Issue 1 March 2013

subscriber trace

....................................................................................................................................................................................................................................
IPC
Parameter
Description
Syntax
Values
Enables and disables the

feature.
boolean
sftpServer

pushed by the IPC. It must be
in IP Address dot decimal
format, for example,
135.168.0.1.
ipAddress
rootDirectory
Specifies the root directory for

RF Trace files to be pushed to
on the Sftp server.
string
length=100
username
Specifies the username to be

used by the IPC to authenticate
with the file server.
string
length=256
password
Specifies the password to be

used by the IPC to authenticate
with the file server. This string
is set to an empty string if no
authentication is required.
string
length=256
isSshKeyAuthenticationDone
Specifies whether key

authentication is done between
the IPC and the SCMS.
boolean

number of SubscriberTrace
MO instances that can be
unlocked when tracing is
enabled. In a distributed SS7
configuration, this value
represents the maximum
number of parallel traces per
signaling processor that is
hosting a RANAP/ALCAP
stack instance.
uint16
[1..100]
retryFTPTimer

after which FTP will be retried
after a failure.
uint32
unit=secs
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
25-6
Issue 1 March 2013

subscriber trace

....................................................................................................................................................................................................................................
Attributes of class SubscriberTrace

Parameter
Description
Syntax
Values
iMSI
Specifies the IMSI of the UE

that is to be traced.
string
length=15
traceId
Specifies the trace identifier

assigned to the subscriber
trace. It is a decimal string with
a fixed length of 3, for
example, 001, 101. It must be
unique within the list of traces
being configured.
string
length=3
traceReportingPeriod
Specifies the time interval for

which the trace file is to be
reported to the file server.
enum TraceReportingPeriod
unit=secs
traceDuration
Specifies the time duration of

the subscriber trace.
uint16
unit=mins
traceRecordingSessionRef
This parameter identifies a

trace recording session for a
subscriber trace.
uint16
traceStatus
Provides the status of the

tracing activity.
enum TraceStatus
step=15
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
25-7
Issue 1 March 2013

subscriber trace

....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
25-8
Issue 1 March 2013
26
26
Active-Warm
Standby
Gateway Redundancy
Overview
Purpose
This chapter describes the Active-Warm Standby Gateway Redundancy (114014) feature.
Contents
Active-Warm Standby BSR Gateway Redundancy
26-2
Principles
26-4
Active / warm standby Small Cell Gateway redundancy parameters
26-5
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
26-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number

Feature description
This feature improves the availability of the Small Cell Gateway, and reduces Small Cell
downtime when a failover occurs between the active and standby nodes within the
gateway .
With the introduction of this feature, a Small Cell is provisioned with the IP addresses of
both active and standby nodes within the gateway, and maintains persistent associations
with both nodes. Therefore when a failover occurs, an R3.0 Small Cell can use the
established SCTP association with the former standby (now active) node, significantly
reducing failover time. Small Cells from previous releases continue to be provisioned
with an IP address that floats between the active and standby nodes on failover.
Only the active node within the gateway is associated with the core network. Therefore on
failover, the standby node must establish an association and connectivity with the core
network.
The nodes within the gateway handshake to establish which node will take the active and
standby roles and which fixed IP address each node should bind to. Since the standby
node does not have connectivity with the core network, this decision must be passed to
the Small Cell to indicate which gateway traffic should be routed to. The Small Cell never
makes decisions as to which gateway to use. If the Small Cell becomes confused it must
take action to determine which gateway is currently active.
Feature benefits
This feature reduces downtime in the event of failure of a node within the Small Cell
Gateway, helping the service provider to improve service availability.
End user benefits
Deployment of this feature improves subscriber service availability.

Impacted systems
Small Cell
Small Cell Gateway
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
26-2
Issue 1 March 2013
....................................................................................................................................................................................................................................
Dependencies
There are no specific dependencies between this feature and other features. However the
2 SCTP association behaviour is only supported with Release 3.0 Small Cells using the Iu'
interface.
This feature requires Small Cells to use the dual association capability on the gateway
with reduced downtime on gateway failover.
Feature type
Basic.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
26-3
Issue 1 March 2013
Principles
....................................................................................................................................................................................................................................
Principles
Overview
The Small Cell Gateway consists of two nodes. At any time, one node is active and the
other is standby, with only the active node connected to the core network. The nodes must
use handshaking to agree which is the master (active) node.
In the normal mode of operation, each Small Cell has two SCTP associations: one
towards the active node, and one towards the standby node. All traffic is supported by the
active node. Only the active node has associations with the core network.
When the active node fails:
The standby node detects the failure.

The IP address exposed to the CN floats onto the standby node.
The standby node resets the connection with the core network (RANAP reset).
The Small Cell detects the active node failure (via loss of the SCTP association) and
drops ongoing calls.
After the Small Cell has been informed that the previous standby node has become
active, new calls are supported using the other SCTP association (towards the standby
node).
Assumptions
It is assumed that the core network connection will become active in less than 30 seconds.
If the core network takes longer than 30 seconds to become active, increased handovers to
the macro network may occur.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
26-4
Issue 1 March 2013
Active / warm standby Small Cell Gateway redundancy

parameters
....................................................................................................................................................................................................................................

parameters
Small Cell
Parameter
Description
Syntax
bSRGatewayIpAddress
Specifies the floating IP address

configured for the BSR Signaling
Gateway.
ipAddress
Values
This parameter is used if

enableWarmStandbyAssoc is set to
False.
bsrGWNode1
Specifies the address of gateway

node 1. It can be defined in either a
DNS name or an IP address in dot
decimal format.
string
length=128
string
length=128
In Release 3.0, only IP address

format is supported.
bsrGWNode2
Specifies the address of gateway

node 2. It can be defined in either a
DNS name or an IP address in dot
decimal format.
In Release 3.0, only IP address
format is supported.
enableWarmStandbyAssoc
The feature flag. When set to True,

enables use of the Active-Warm
Standby feature with the Small Cell
connecting to both active and
standby gateways, using
BSR::bsrGWNode1 and
BSR::bsrGWNode2 in preference to
BSR::bSRGatewayIpAddress for
connecting to the gateway.
boolean
timerOnlyConnectedToStandby
Timer to try and resolve state if only

connected to a standby gateway
node.
integer
timerDoubleStandby
Timer to try and resolve state if not

connected to an active gateway node.
integer
[15..300]
unit=secs
[30..600]
unit=secs
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
26-5
Issue 1 March 2013

parameters
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
timerFailover
Timer to specify when to stop

radiating after Small Cell detects that
failover has started.
integer
[30..600]
standbyNodeConnectivityThreshold
Specifies the number of losses of

communication with the standby
node that will trigger an alarm.
integer
failoverStopRadioOnEmergencyCall
If the Active-Warm Standby feature

is enabled, indicates whether to
disable the Small Cell radio if an
emergency call is made during
gateway node failover.
boolean
unit=secs
[1..1000]
Small Cell Gateway

Attributes of class BSG
Parameter
Description
Syntax
ipAddressFemtoCpLocal
Specifies the IP address used by

Small Cells that have the
Active-Warm Standby feature
disabled. This is the address that
these Small Cells use for call
processing and is therefore the BSG
end of the SCTP associations for
these Small Cells. This IP address
can be floated between BSG nodes
when the active node is changed.
ipAddress
Values
This IP address is on the same subnet

and VLan as the
PhysicalInterfaceS/B MOI that has
interfaceType set to FemtoCP and
hence uses the same default
Gateway.
This IP address must only be used by
nodes that do not maintain active
associations with both active and
standby nodes within the gateway.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
26-6
Issue 1 March 2013

parameters
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
node1FemtoAddress
Specifies the IP address for Node 1

of the gateway. This address may be
used by Small Cell call processing to
access the BSG end of the SCTP
associations on Node 1 of the
gateway when FGW::
True. This IP address is not floated
between BSG nodes when the active
node is changed. However it may be
floated between physical interfaces
or bonding interfaces in the event of
local link or switch failure. This IP
address is on the same subnet and
VLan as the PhysicalInterfaceS/B
MOI that has interfaceType set to
FemtoCP and hence uses the same
default Gateway.
ipAddress
length=100
node2FemtoAddress
Specifies the IP address for Node 2

of the gateway. This address may be
used by Small Cell call processing to
access the BSG end of the SCTP
associations on Node 2 of the
gateway when FGW::
True. This IP address is not floated
between BSG nodes when the active
node is changed. However it may be
floated between physical interfaces
or bonding interfaces in the event of
local link or switch failure. This IP
address is on the same subnet and
VLan as the PhysicalInterfaceS/B
MOI that has interfaceType set to
FemtoCP and hence uses the same
default Gateway.
ipAddress
length=100
enableWarmStandby
Assoc
Enables the Active-Warm Standby

gateway feature. If this parameter is
set to False, the gateway will only
bind to the floating IP address,
ipAddressFemtoCpLocal, for SCTP
associations to the Small Cells.
Boolean
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
26-7
Issue 1 March 2013

parameters
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
26-8
Issue 1 March 2013
27
27
All-In-One
Small Cell
Gateway
Overview
Purpose
This chapter describes the All-In-One Small Cell Gateway (84181) feature.
Contents
All-in-One Small Cell Gateway
27-2
Principles
27-4
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
27-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number

Feature description
This feature combines several logical functions onto a single hardware platform, and
integrates the OAM of these functions so that the resulting Small Cell Gateway appears as
a single network element to the mobile network operator.
The implementation of a single gateway for a Small Cell cluster reduces the number of
physical network elements in a Small Cell network deployment. This aggregation of
several logical elements into a single Small Cell Gateway (FGW) is in line with the
standardization of the 3GPP Femtocell (Home Node B) architecture. When this network
element is fully standards-compliant, it will perform the role of the Home Node B
Gateway (HNB-GW).
The Small Cell architecture in previous releases uses three logical elements for the Small
Cell Gateway functionality, namely the BSR Signaling Gateway (BSG), the BSR Voice
Gateway (BVG) and the BSR Packet Gateway (BPG). The Security Gateway (SeGW)
functionality is logically separate from the Small Cell Gateway. The deployment in these
releases has the BSG on one hardware platform and the BVG and BPG on a separate
hardware platform (the Brick, co-resident with the SeGW). These separate hardware
platforms have different redundancy schemes and different management channels, which
result in significant complexity in both connectivity and management.
The purpose of this feature is to reduce operational complexity by co-locating the Small
Cell-specific functionality (BSG, BVG and BPG), and to increase flexibility by
supporting the use of a standard security gateway. The redundancy schemes are therefore
more uniform and the requirements placed on the network infrastructure are simplified.
Management of the system is also simplified and the diverse logical functions appear as a
single unit to the network management system. This brings the implementation in line
with the evolving 3GPP Home Node B standards.
Feature benefits
The Small Cell Gateway simplifies the physical and logical configuration of the Small
Cell cluster. As such, it reduces both the capital and operational expenses of the service
provider. Tighter integration of the logical network elements in the Small Cell Gateway
also improves the reliability of the gateway and simplify the software upgrade
procedures, as all logical elements are upgraded on the same upgrade cycle.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
27-2
Issue 1 March 2013
....................................................................................................................................................................................................................................
End user benefits
The Small Cell Gateway is functionality within the Small Cell core network. This feature
transparent to the end user.
Impacted systems
Small Cell
Small Cell Gateway
Dependencies
The Small Cell Gateway is dependent on feature 84990 (FMS Support of All-In-One
Femto Gateway). This feature provides the means to manage the Small Cell Gateway
from the central OAM system.
None
Feature type
Basic
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
27-3
Issue 1 March 2013
Principles
....................................................................................................................................................................................................................................
Principles
General
The functions that are required to support the Small Cell cluster (that is, the functionality
that acts as a virtual RNC to the core network) are integrated onto a single hardware
platform. The OAM is also integrated so that management is simplified.
The availability requirements of the Small Cell Gateway are met by implementing the
functionality on dual hardware nodes.
Multiple configurations are supported, and existing functionality (the Signaling Gateway)
interoperates with the existing implementation of the Traffic Gateways and Security
Gateway on the Brick. In addition, the Small Cell Gateway can interoperate with a
third-party Security Gateway.
The following configurations are supported:
Configurations supported
Figure 27-1 Configuration 1: duplex, BSG only
AAA
WMS
SGSN
MSC
IuPS-CP
IuPS-UP
Itf-FGW
IuCS-CP
Small
Cell
Node
FGW
Node
1 1
IuCS-UP
Small
Cell
Node
FGW
Node
22
a3
OAM-A
DNS
OAM-S
DNS
BSG-A
ToD
BSG-S
ToD
BVG
BPG
Iu-UP
Iu-CP
SeGW
SeGW
Iu-CP after failover
SeGW
The physical location of

BVG/BPG not relevant
(e.g. co-located with
SeGW on the Bricks)
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
27-4
Issue 1 March 2013
Principles
....................................................................................................................................................................................................................................
In this configuration, the Small Cell Gateway acts in legacy mode in a duplex network
architecture. It implements only the signaling gateway functionality and a few simple
services that are necessary for support of the IP infrastructure.
The BSG functionality and OAM functionality run in active-standby mode, and will fail
over together. The IP Services functionality (DNS and ToD) run in primary-secondary
load-sharing mode, with failover initiated by the client program (typically, the Small
Cell). This means that, as shown in the figure, Small Cell Gateway Node 2 is not fully in
standby mode as it has active DNS and ToD functions. In addition, the dashed lines from
the security gateways to Small Cell Gateway Node 2 are used for this low-volume IETF
Services traffic.
Figure 27-2 Configuration 2: duplex
AAA
WMS
SGSN
MSC
IuPS
Itf-FGW
IuCS
Small
Cell
Node
FGW
Node
1 1
Small
Cell
Node
FGW
Node
2 2
a3
OAM-A
DNS
BVG-A
OAM-S
DNS
BVG-S
BSG-A
ToD
BPG-A
BSG-S
ToD
BPG-S
Iu
Iu after failover
SeGW
SeGW
SeGW
In this configuration, the Small Cell Gateway has all the functions of configuration 1, and
also hosts the BVG and BPG logical functions. Since the Small Cell Gateway is now
hosting both control plane and user plane traffic, the core network interfaces are the full
IuCS and IuPS interfaces, running over IP. The a3 interface is still required.
The logical elements that are present in configuration 1 employ the same redundancy
mechanisms. The BVG and BPG functions run in active-standby mode, with the active
functions on the same node as the active BSG and OAM. All these functions will fail over
simultaneously if any single function needs to fail over.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
27-5
Issue 1 March 2013
Principles
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
27-6
Issue 1 March 2013
28
28
Coverage
self-optimization based on
admission
Overview
Purpose
This chapter describes the coverage self-optimization based on admission (108877)

feature.
Contents
Continuous coverage self-optimization based on admission
28-2
Principles
28-4
Continuous coverage self-optimization based on admission parameters
28-12
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
28-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number

Feature description
Feature 108877 allows the Small Cell to decrease its coverage so that public users are not
attracted to it. This feature tracks idle mode mobility events of public UEs attempting to
camp on the Small Cell. An excessive number of public users attracted towards the Small
Cell is used as an indication that the coverage (CPICH power level) of the Small Cell is
too great and may be reduced.
This feature is applicable to deployments where the Small Cell has an access control list
(ACL). Public users are those not in the ACL. Public users that are attracted to the Small
Cell are rejected by the Small Cell during the attempted NAS mobility procedure.
In dedicated carrier Small Cell deployments, if the Small Cell coverage is too great, it
may generate excessive core network signaling because public UEs attempt mobility
procedures toward the Small Cell.
In co-channel Small Cell deployments, there may also be CPICH leakage from the
intended Small Cell coverage area. Typically, the intended Small Cell coverage area is
within a building. This CPICH leakage may result in macro coverage holes.
The Small Cell pilot power cannot be reduced too much as this will cause coverage holes
in the home or enterprise area where the Small Cell is providing service.
Feature benefits
For co-channel deployments, the service provider benefits from reduced customer
dissatisfaction resulting from fewer macro network coverage holes. However Small Cell
users may be more dissatisfied if the coverage of their Small Cell no longer covers their
residence. The service provider also benefits from reduced signaling load because fewer
public UEs attempt connected mode mobility procedures with the Small Cell.
For separate channel deployments, the service provider benefits from reduced signaling
load because fewer public UEs attempt connected mode mobility procedures with Small
Cells.
End user benefits
For co-channel deployments, macro network user dissatisfaction will be reduced. Macro
user dissatisfaction may arise where macro supported calls are dropped because of macro
coverage holes created by poorly positioned Small Cell cells. This feature permits the
Small Cell to reduce its own coverage to reduce these macro coverage holes. However the
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
28-2
Issue 1 March 2013
....................................................................................................................................................................................................................................
Small Cell user may find the reduced coverage of the Small Cell does not adequately
cover the residence. The operator must anticipate the resulting dissatisfaction and offer
user support regarding the best positioning of the Small Cell within the residence.
For separate channel deployments, the feature does not significantly change the macro
user experience. Some modest saving in battery life may be attributed to the UE not being
attracted to the Small Cell. However the Small Cell user may find the reduced coverage
of the Small Cell does not adequately cover the residence. The operator must anticipate
the resulting dissatisfaction and offer user support regarding the best positioning of the
Small Cell within the residence.
Impacted systems
Small Cell CPE

Dependencies
Feature 108877 Coverage Optimization based on admission requires the existing

coverage auto configuration provided by feature 1485 . The configuration of the coverage
auto configuration dictates the minimum CPICH power that the Small Cell may use.
If enabled, the UE measurement based coverage optimization feature (1484) takes
precedence over this feature.
None
Feature type
Basic
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
28-3
Issue 1 March 2013
Principles
....................................................................................................................................................................................................................................
Principles
Overview
The Small Cell supports a number of self optimization functions to permit end users to
deploy residential Small Cells without network planning by the operator. This feature
provides additional controls to permit the tuning of Small Cell coverage to take account
of any local impact on the macro network.
Prior to this feature, Small Cell coverage (CPICH power level) is assigned based on the
MIM configuration or on the detected power level (RSSI) of the surrounding cells
(Feature 1485). This value is evaluated once every 24 hours during a non-busy hour. The
Small Cell coverage may then be increased from this minimum based on UE
measurements requested by the Small Cell to optimize coverage for the Small Cell private
users, that is, those users in the ACL.
In addition, Small Cell feature 1484 may temporarily adjust the coverage set by feature
1485 based on connected UE measurement reports, optimizing coverage for private UEs
in active calls.
However, where the Small Cell has been placed in a position that is not optimal, such as
near a window overlooking the street, the Small Cell coverage may extend into a public
area and public users may be attracted to the Small Cell. Public users are rejected because
they are not in the ACL.
This will have the following impacts:
If the Small Cell and macro networks share a carrier, then the Small Cell may
interfere with the macro coverage.
The signaling load on the core network may be increased. The magnitude of this
depends on behavior of the UE when it returns to the macro network after a Location
Area Update (LAU) or Routing Area Update (RAU) procedure with the Small Cell.
Feature 108877 introduces additional Small Cell coverage optimization that attempts to
limit these effects on the macro network by permitting the Small Cell to reduce its pilot
power below the existing auto-configured level.
In order to assess the impact of the Small Cell coverage on the macro network, the Small
Cell monitors the following statistics:
Rate of attempted LAU and RAU procedures started by UEs that are not in the macro
ACL. This indicates possible Small Cell interference in the macro network.
Rate of attempted outgoing handover attempts by connected mode UEs that are in the
ACL. This may indicate a hole in the Small Cell coverage.
The Small Cell uses these statistics as input to algorithms used to increase or decrease the
pilot power of the cell, adjusting the cells coverage to minimize the impact on macro
service.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
28-4
Issue 1 March 2013
Principles
....................................................................................................................................................................................................................................
Detailed description
Without this feature, the cell coverage wis typically updated automatically once every 24
hours, during non-busy hour, based on the detected RSSI level of the surrounding macro
or Small Cells. This provided minimum coverage. The CPICH power can then be
increased based on the UE measurements of Cell_DCH.
The principle of Small Cell coverage optimization without feature 108877 is to optimize
the coverage for the Small Cell private users (those in the ACL), but has no regard for the
coverage hole that this may create in the macro network. This may be acceptable on a
dedicated carrier or in a shared carrier where the Small Cell is deployed in an optimal RF
location (for example, the centre of the house). However there is no guarantee that the
users will deploy the Small Cell in an optimal location. For example, a Small Cell may be
deployed next to a window overlooking a street.
Feature 108877 permits Small Cell auto-configuration to take account of the case where
the Small Cell coverage is affecting users in the macro network.
The following diagrams illustrate the situation in a shared carrier environment where the
Small Cell is placed next to a window beside the street at one end of a long thin house
(typical UK terraced house).
Figure 28-1 Small Cell throughput with fixed power
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
28-5
Issue 1 March 2013
Principles
....................................................................................................................................................................................................................................
Figure 28-2 Macro cell throughput with fixed power, white zone is less than 64
kbps
In the preceding two figures, the Small Cell is placed close to the window. It can be seen
from the CINR throughput mapping that the coverage is optimal inside the house, but
due to bad isolation of the Small Cell signal the outdoor macro CINR is degraded, leading
to very low data throughput. The fact that the signal is leaking out of the house into a
public area can be detected by frequent LAU, RAU and HO procedures by public users,
that is, those not in the Small Cell ACL. The rate of these events is measured and
compared to a target threshold. If the rate of events is excessive, the CPICH pilot power
may be reduced. By doing so, Small Cell interference in the macro area is reduced, in
addition to reducing the signaling load toward the core network. If the number of events
is not excessive, the CPICH pilot power can be increased again, to maximize the Small
Cell coverage.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
28-6
Issue 1 March 2013
Principles
....................................................................................................................................................................................................................................
Figure 28-3 Small Cell throughput with self-optimization based on admission
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
28-7
Issue 1 March 2013
Principles
....................................................................................................................................................................................................................................
Figure 28-4 Macro cell throughput i.c.o. Small Cell power adaptation
In the two preceding figures, the Small Cell is still badly positioned, but feature 108877 is
now enabled. It can be seen that the macro CINR degradation is minimized. Meanwhile,
Small Cell coverage in the house is also greatly reduced, leading to reduced throughput
and even coverage holes. Tuning of feature 108877 is therefore critical to produce
desirable results.
Feature 108877 may increase and decrease the Small Cell pilot power according to the
rate of observed LAU and RAU procedures. The pilot power is bounded by a minimum
power level, to ensure minimal coverage, and a maximum power level, to keep the
interference to the macro network in reasonable proportion. In addition, the Small Cell
monitors the number of outgoing handover procedures by private UEs. A high handover
rate may imply coverage holes in the house and may be used as a trigger to increase the
Small Cell pilot power. This needs careful tuning, because outgoing handover may be due
to the user leaving the house or moving next to a window.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
28-8
Issue 1 March 2013
Principles
....................................................................................................................................................................................................................................
Interactions of this algorithm with existing self-optimization functionality:

1. The existing Small Cell auto-configuration and self-optimization determine the
minimum Small Cell pilot power, based on the surrounding RSSI level (at reboot and
then every 24 hours during non-busy hours).
2. Feature 108877 tunes the pilot power up or down, based on UE mobility events. It
may only vary the Small Cell pilot power between certain limits. The lower power
limit is the configured minimum power configured in BSR:autoConfigPW.minBSRPowerdBm. The high power limit is the lesser of the maximum CPICH power the
Small Cell can support (10 dB below maximum power) and a configured maximum
power BSR:autoConfigPW.maxBSRPowerdBm. This algorithm runs continuously in
the background. The CPICH power level arrived at by this feature is used in place of
the value from 1 unless a change in the surrounding RSSI is noticed during the
non-busy hour autoconfiguration.
3. When there is an active call, optional UE measurement based optimization may be
used to temporarily increase or decrease the Small Cell pilot power if needed. This
action takes precedence over any action resulting from interaction 2, especially if the
decision is to power down the Small Cell. This is to avoid degrading active Small Cell
calls. When the active call ends, the Small Cell power level recovers in steps toward
the power level set by interaction 2.
Small Cell MIM parameters permit tuning of this feature.
Where the Small Cell network uses a dedicated carrier, the Small Cell reselection
parameters are tuned in such a way that the UE is always attracted to reselect to the Small
Cell cell. Thus a high number of LAU or RAU does not necessarily indicate CPICH
leakage. In the dedicated carrier scenario, the main requirement is to reduce signaling in
the core network. If a significant increase of the CN signaling load occurs as a result of a
major rollout of Small Cell equipment, this feature may be activated to help to reduce the
signaling load.
Principles
A Small Cell in closed mode may monitor the number of idle mode procedures of public
UEs and connected mode mobility procedures of Private UEs, and from this deduce the
degree of macro interference it is causing. The Small Cell can then control its pilot power
to limit that interference.
The feature is disabled for Small Cells operating in open mode.
The feature is disabled if the Small Cell is operating as an isolated cell, that is, if no
neighbor Small Cell or macro 2G or 3G cells have been detected during
auto-configuration.
Public UEs are those that do not appear in the Small Cell Access Control List. Private
UEs are those that do appear in the Small Cell Access Control List.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
28-9
Issue 1 March 2013
Principles
....................................................................................................................................................................................................................................
If the rate of public UEs attempting mobility procedures through the Small Cell exceeds a
threshold rate, the Small Cell may reduce its coverage, that is, its pilot power. Conversely,
if the rate of these events is below a threshold, the Small Cell may increase its pilot power
back towards its maximum in order to increase coverage for private users. The Small Cell
may additionally monitor private UE handover events to the macro network. Frequent
occurrence of these events may be used as an indication that Small Cell coverage is
insufficient to cover the Small Cell location and a pilot power increase may be
appropriate.
The Small Cell supports separate configurable thresholds for triggering pilot power
increases and decreases on public UE mobility events. Each threshold is described as n
events in period t.
The Small Cell supports separate configuration of the pilot power increment due to
private UE connected mode mobility events.
The following diagrams illustrates the use of event rate measurements and event rate
thresholds:
Figure 28-5 Coverage optimization CPICH decrease example
Coverage Optimization CPICH Decrease Example

Event Measurement Period e.g. last 60 minutes
MIM BSR::admissionBasedPilotPower.DecreaseMeasurementPeriod

MIM BSR::admissionBasedPilotPower.DecreasetMeasurementPeriod
Public UE Reject event

Variable: numUeRejectEventCount
Based on Imsi reject at
Location Area Update
Routing Area Update
Event Measurement Period is the MIN(the time from Femto start to now ,
MIM BSR::admissionBasedPilotPower.DecreasetMeasurementPeriod
)
Femto start point
10
20
30
40
Test Period
e.g. Every 10 minutes.
MIM BSR::admissionBasedPilotPower.DecreaseTestPeriod
If number of events during measurement period exceeds
BSR::admissionBasedPilotPower.DecreaseEventMinimum
then check event rate to decrease Femto CPICH power.
50
60
70
80
90
100
Test period = decision point to increase CPICH power

1.
Calculate event rate for last event measurement period
2.
Calculate set event rate based on MIM parameters
3.
If event rate of last measurement period is less
than set event rate decrease the CPICH power specified
by
BSR::autoConfigPW:pAdjustmentStepdB
4.
Set event rate is calculated using
BSR::admissionBasedPilotPower.DecreaseEventThreshold
BSR::admissionBasedPilotPower.DecreaseperiodThreshold
5.
Measured event rate is calculated based on
Variable::numUeRejectEventCount
BSR::admissionBasedPilotPower.DecreaseMeasurementPeriod
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
28-10
Issue 1 March 2013
Principles
....................................................................................................................................................................................................................................
Figure 28-6 Coverage optimization CPICH increase example
Coverage Optimization CPICH Increase Example

MIM BSR::admissionBasedPilotPower.IncreaseMeasurementPeriod

Public UE Reject event

Variable: numUeRejectEventCount
Based on Imsi reject at
Routing Area Update

Femto start point
10
20
30
40
Test Period
e.g. Every 10 minutes.
MIM BSR::admissionBasedPilotPower.IncreaseTestPeriod
Check if eventMeasurementPeriod has reached
If yes check if decision can be made to increase CPICH power
50
60
70
80
90
100
decision point to increase CPICH power

1.
Calculate event rate for last event measurement period
2.
Calculate set event rate based on MIM parameters
3.
If event rate of last measurement period is greater
than set event rate increase the CPICH power specified
by
BSR::autoConfigPW:pAdjustmentStepdB
4.
Set event rate is calculated using
BSR::admissionBasedPilotPower.IncreaseEventThreshold
BSR::admissionBasedPilotPowerIncreaseperiodThreshold
5.
Measured event rate is calculated based on
Variable::numUeRejectEventCount
BSR::admissionBasedPilotPower.IncreaseMeasurementPeriod
The feature may be enabled for Small Cells operating in group mode if the group is
configured in closed mode. All the Small Cells in a group have the same LA and RA, so
idle mode UEs will not perform RA and LA Update as the UE moves through the group.
Handover of active calls between Small Cells may occur. However, Small Cell to Small
Cell handovers are not included as triggers in this feature. Consequently feature 108877
may be enabled in group mode, since only Small Cells in the group experiencing idle
mobility events from outside the group receive trigger events for this feature.
Small Cell groups that are not operating in closed mode are outside the scope of this
feature.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
28-11
Issue 1 March 2013

parameters
....................................................................................................................................................................................................................................

parameters
Small Cell
Attributes of class AdmissionBasedPilotPower
Parameter
Description
Syntax
Values
increaseMeasurementPeriod
Specifies the maximum period over

which events are counted for power
increase.
integer
[1..1440]
increaseTestPeriod
Specifies the period for which the

events during the last
admissionBasedPilotPower.increaseMeasurementPeriod minutes
are tested in order to increase the
pilot power.
integer
Specifies the number of attempted

public UE mobility events used to
give the threshold event rate over
period admissionBasedPilotPower.increasePeriodThreshold. If the rate
of events exceeds this threshold, the
Small Cell increases its pilot power.
integer
Specifies the period over which the

threshold event rate is calculated for
Small Cell pilot power increase.
integer
Specifies the power increment step

when increasing the CPICH power.
real
increaseEventThreshold
increasePeriodThreshold
increaseStepdB
minutes
[1..120]
minutes
[1..100]
events
[1..120]
minutes
[0.0..10.0]
step=0.1
precision=1
unit=dB
decreaseMeasurementPeriod

decrease.
integer
decreaseTestPeriod

events during the last
admissionBasedPilotPower.decreaseMeasurementPeriod minutes
are tested in order to decrease the
pilot power.
integer
[1..1440]
minutes
[1..120]
minutes
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
28-12
Issue 1 March 2013

parameters
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
decreaseEventThreshold

public UE mobility events used to
give the threshold event rate over
period admissionBasedPilotPower.decreasePeriodThreshold. If the rate
of events is below this rate the Small
Cell decreases its pilot power.
integer
[1..100]
decreasePeriodThreshold

Small Cell pilot power decrease.
integer
decreaseEventMinimum
Specifies the minimum number of

admission events that must be seen
before the Small Cell pilot power can
be decreased due to admission
events.
integer
Small Cell power decrement step

when decreasing the CPICH power.
real
decreaseStepdB
events
[1..120]
minutes
[1..100]
events
[0.0..10.0]
step=0.1
precision=1
unit=dB
Attributes of class MacroHOPilotPower

Parameter
Description
Syntax
Values
testPeriod

macro handover events during the
last macroHOPilotPower.measurementPeriod minutes are tested to
increase the pilot power.
integer
[1..120

increase.
integer

private UE handover to macro events
used to give the threshold event rate
over period macroHOPilotPower.periodThreshold. If the rate of events
exceeds this threshold, the Small
Cell increases its pilot power.
integer
measurementPeriod
eventThreshold
minutes
[1..1440]
minutes
[1..100]
events
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
28-13
Issue 1 March 2013

parameters
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
periodThreshold
Specifies the period over which the

Small Cell pilot power increase due
to macro handover.
integer
[1..120]
Specifies the power increment step

when increasing the CPICH power.
real
adjustmentStep
minutes
[0.0..10.0]
step=0.1
precision=1
unit=dB

Parameter
Description
Syntax
enableCoverageSelfOptimisationBasedOnAdmission
Enables feature 108877.
Boolean
enableCoverageSelfOptimsationBasedOnMacroHO
Enables feature 108877 additional

measurement of handovers to the
macro network by private UEs. If
these events exceed the threshold,
the Small Cell pilot power is
increased.
Boolean
Values
Attributes of class AutoConfigPW

Parameter
Description
Syntax
admissionBasedPilotPowerControl
Controls CPICH power level based

on idle mode mobility events
rejected by the Small Cell ACL (that
is, public UEs).
struct
AdmissionBasedPilotPower
macroHOPilotPowerControl
Controls CPICH power level based

on connected mode handover events
detected by the Small Cell for private
UEs (that is, those in the Small Cell
ACL).
struct
MacroHOPilotPower
numberACLrejections
Specifies the number of ACL

procedures rejected by the Small Cell
over the previous 24 hour period to
12 oclock midnight.
Integer
Values
[0..65535]
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
28-14
Issue 1 March 2013

parameters
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
pilotPowerReducedDueToAdmissionControl
Indicates that the Small Cell has

reduced its CPICH power to limit
interference in the macro network.
Small Cell users may experience
reduced coverage.
Boolean
Values
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
28-15
Issue 1 March 2013

parameters
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
28-16
Issue 1 March 2013
29
Static IP address
29
Overview
Purpose
This chapter describes the static IP address (119110) feature.

Contents
Static IP address
29-2
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
29-1
Issue 1 March 2013
Static IP address
Static IP address
....................................................................................................................................................................................................................................
Static IP address
Feature number

Feature description
This feature allows the Small Cell to store its IP configuration across reboots.
This feature allows the Small Cell to retrieve critical IP configuration data from a DHCP
server and to store it for future use. Once the static IP has been configured, the Small Cell
does not attempt DHCP again in normal operations except after a factory reset. The Small
Cell uses saved IP configurations for IP transport connections.
Principles
This feature is only used when a permanent DHCP server is not available. This feature
allows installation of the Small Cell using a temporary DHCP server. The Small Cell
receives the IP configuration from the DHCP server and stores it in memory. The
temporary DHCP server can be disconnected after the IP configuration has been saved.
On subsequent reboot, the Small Cell uses the saved IP configuration for the setup of IP
transport.
The Small Cell removes the saved configuration after a factory reset, so for the first boot
after a factory reset, access to a DHCP sever is required to set up IP transport.
Static IP address configurations in the DHCP server
To enable the Static IP Address feature, the following standard DHCP options must be
configured:
DHCP Option
Name/Description
Subnet Mask (negative IP address format, that is, 255.255.x.y)
Router IP Address (next hop - also called default gateway)
IP Address of DNS sServer(s)
51
IP Address Lease Time (0xFFFFFFFF)
54
Server Identifier (DHCP server IP Address)
In addition to the standard DHCP options, the Vendor Specific Options of DHCP Option
125 must be configured with the following values:
enterprise-number = 637
Vendor Specific Option 1 = true (that is, the Static IP Address feature is enabled.)
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
29-2
Issue 1 March 2013
Static IP address
Static IP address
....................................................................................................................................................................................................................................
The DHCP server sends option 125 (RFC3925) with sub-option 1 only, that is, option 125
contains the value 7D:03:00:00:02:7D:01:01:01.
The components of this value are as follows:
0000007D option number 125

03 length
0000027D enterprise number 637

01 sub option code 1
01 sub-option length 1
01 true
Feature benefits
This feature enables a service provider to configure the IP address of a Small Cell from an
installation tool.
End user benefits
This feature does not impact end users.

Impacted systems
Small Cell CPE

Dependencies
This feature is dependent on the following features:
157214 PPPoE configuration

126765 Static IP using Motive activation CD
If the Static IP address feature is enabled, the Home Network Local Routing (HNLR)
feature is not supported.
Feature type
Basic
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
29-3
Issue 1 March 2013
Static IP address
Static IP address
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
29-4
Issue 1 March 2013
30
PPPoE configuration
30
Overview
Purpose
This chapter describes the PPPoE configuration (157214) feature.

Contents
PPPoE configuration
30-2
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
30-1
Issue 1 March 2013
PPPoE configuration
PPPoE configuration
....................................................................................................................................................................................................................................
PPPoE configuration
Feature number

Feature description
This feature enables configuration of PPPoE credentials. It also enables the Small Cell to
store these parameters across reboots.
This feature allows the Small Cell to retrieve configured PPPoE configuration data from a
DHCP server and use this configuration to set up an IP transport connection. It also
allows the Small Cell to store this configuration for future use, that is, after the Small Cell
reboots, the Small Cell will attempt to use the saved PPPoE configuration to set up IP
transport.
Principles
This feature allows installation of the Small Cell using a temporary DHCP server. The
Small Cell receives PPPoE credentials from the DHCP server and stores them in memory.
The temporary DHCP server can be disconnected after the PPPoE credentials have been
saved. On subsequent reboots, the Small Cell uses the saved PPPoE configuration for IP
transport setup.
The Small Cell removes the saved configuration after a factory reset. Therefore for the
first boot after a factory reset, access to a DHCP server is required to set up IP transport.
PPPoE configurations in the DHCP server
To enable this feature, Vendor Specific Option 125 of DHCP must be configured with the
following values:
enterprise-number = 637
Vendor Specific Option 2 = <username> (up to 128 octets)
Vendor Specific Option 3 = <password> (up to 128 octets)

Vendor Specific Option 4 = <authentication method>
(true = CHAP only or
false PAP/CHAP)
The DHCP server sends option 125 with sub-options 2, 3 and 4.

In the following example, option 125 contains the value
00:00:02:7D:15:02:07:70:70:70:75:73:65:72:03:07:70:70:70:75:73:65:72:04:01:01.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
30-2
Issue 1 March 2013
PPPoE configuration
PPPoE configuration
....................................................................................................................................................................................................................................
The components of this value are as follows:
00:00:02:7D enterprise number
15 the length of the remainder of the set of values in option 125 (15 hex is 21 octets)
02 sub-option code (number 2 for PPP username)
07 length of sub-option 2
70:70:70:75:73:65:72 value of sub-option 2 (pppuser)

Note that this is an example username only.
03 sub-option code (number 3 for PPP password)
70:70:70:70:61:73:73 value of sub-option 3 (ppppass)
Note that this is an example password only.
04 sub-option code (number 4 for disable PAP)
01 value of sub-option 4 (true)
Feature benefits
This feature enables the service provider to configure PPPoE credentials from an
installation tool.
End user benefits
This feature does not impact end users.

Impacted systems
Small Cell CPE

Dependencies
This feature is dependent on the following features:
119110 Static IP address
126765 Static IP using Motive activation CD
None
Feature type
Optional
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
30-3
Issue 1 March 2013
PPPoE configuration
PPPoE configuration
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
30-4
Issue 1 March 2013
31
31
Assisted
GPS using TCS
server
Overview
Purpose
This chapter describes the Assisted GPS using TCS server (119911) feature.
Contents
31-2
Feature overview
31-4
Principles
31-7
Assisted GPS using TCS server parameters
31-10
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
31-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number

Feature description
GPS location detection is used by the Small Cell to determine and verify its geographic
location.
Autonomous GPS, where a GPS receiver is not provided with any assistance data and
relies completely on the information decoded from the signals transmitted by the GPS
satellites, can take a long time to determine the location, which results in long startup
time when location verification is required before the Small Cell can transmit.
Assisted GPS (AGPS), where GPS assistance data is provided through the network to the
GPS receiver, provides better performance of GPS location detection, providing better
sensitivity and faster time to first fix (TTFF).
This feature provides a solution for implementing AGPS on the Small Cell to improve its
capability to perform GPS location detection, reducing startup time when geographic
location verification is required before the Small Cell can transmit.
Feature benefits
The service provider can place more reliance on GPS location lock functionality, since
with AGPS a greater number of Small Cells can determine their geographical location
using GPS, even when located in a less than ideal position to acquire GPS signals.
Providing a caching proxy for assistance data within the Small Cell network avoids the
additional load impact that would occur if the TCS ADS was required to provide
assistance data to each Small Cell individually.
End user benefits
Assisted GPS provides the following benefits to the Small Cell end user:
Reduced startup time for those Small Cells equipped with a GPS receiver
Less restriction on the position of the Small Cell for it to acquire strong GPS signals
Impacted systems
Small Cell CPE

Small Cell Gateway
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
31-2
Issue 1 March 2013
....................................................................................................................................................................................................................................
Dependencies
This feature is dependent on the following feature:
75545 GPS-based Location Lock

The activation of AGPS functionality is only triggered when the Small Cell performs
a GPS-based location lock.
The TCS Assistance Data Server must be engineered to handle the periodic refresh of
assistance data requested by the AGPS caching proxy.
The operator must provision, as a minimum, a coarse estimate of the expected
location of the Small Cell.
Feature type
Basic
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
31-3
Issue 1 March 2013
Feature overview
....................................................................................................................................................................................................................................
Feature overview
Overview
Certain hardware versions of the Small Cell are equipped with a GPS receiver module to
enable them to use GPS to determine their geographical location. This GPS-determined
geographical location can then be used for location checking, to confirm that the Small
Cell is positioned in the authorized location before it is activated and used for location
reporting to location-based services.
To determine GPS location, the GPS receiver in the Small Cell must be positioned where
it can decode the signal from at least three GPS satellites for a 2D location fix, or four
GPS satellites for a 3D location fix. To further improve the accuracy of the GPS location
fix, five or six GPS satellites are preferred. In a fully open air environment, with a clear
view of the sky in all directions. This does not usually present a problem, as typically
twelve satellites are be in view at any location on the Earth. However, when the Small
Cell is not positioned in such an ideal location, for example indoors, or between
buildings, GPS location detection presents a challenge due to the reduction in signal
quality received from the GPS satellites.
If it is not possible to deploy the Small Cell where it has an adequate view of the sky, one
solution is to use an external GPS antenna connected to the Small Cell, which can be
placed in a more suitable position for GPS signal reception when the Small Cell itself
cannot be moved. However, the use of an external antenna is not suitable for all Small
Cell deployments.
Another solution to the problem is to use assisted GPS (AGPS). The GPS receiver is
provided with information to help it to determine its location.
By providing the GPS receiver module with information on its approximate geographic
location, the GPS receiver can use a more refined search algorithm by restricting the
search space (frequency, time) to the satellites that it is most likely to detect, instead of
performing a completely open search for all satellites without any knowledge of whether
it is possible to detect those satellites. This information contains the position of the GPS
satellites (ephemeris, almanac), and accurate time information. This effectively improves
the receiver sensitivity, and improves the ability of the Small Cell to determine its GPS
location when located in a poor position for GPS signal reception.
With AGPS, the information that the GPS receiver needs to successfully decode directly
from the messages transmitted by the GPS satellite signals before it can determine a GPS
location fix is also reduced, as much of the information is already provided within the
assistance data. This reduces the time to first fix, even when a Small Cell is located in an
ideal position for GPS signal reception.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
31-4
Issue 1 March 2013
Feature overview
....................................................................................................................................................................................................................................
This feature enables the Small Cell to obtain GPS assistance data from a
TeleCommunication Systems TCS Assistance Data Server (TCS ADS) which, when
combined with network timing information, is used for the following improvements in
determination of its geographic location:
The Small Cell can acquire GPS signals in challenging indoor environments and
urban canyons due to the increased sensitivity of the receiver by using refined search
algorithms.
The Small Cell can determine its geographic location faster, since information on the
GPS satellites downloaded from the TCS ADS reduces the amount of information that
needs to be decoded from the messages sent by the GPS satellites themselves.
Information for a single GPS satellite requires successful decoding of the message
frame from that satellite, which is transmitted over 30 seconds (1500 bits at 50 bits
per second). The complete set of almanac data for all satellites is transmitted by each
satellite over 25 frames (12.5 minutes). The time taken to receive this information is
much reduced when the information is provided by the TCS ADS instead of having to
decode the information from the signals received from the GPS satellites.
The Small Cell can provide a more accurate GPS fix faster due to the correction of
errors caused by the ionosphere.
GPS assistance data falls into a number of broad categories which are described in the
following table:
Data category
Data description
Data provided by
Almanac and satellite health
Almanac parameters
specify the coarse,
long-term model of the
satellite positions and
clocks.
TCS ADS
Allows calculation of
coarse positions of the
satellites. Useful for GPS
receiver tasks that require
coarse accuracy, such as
determining satellite
visibility.
Ephemeris data provides a

very accurate
representation of the orbit
of the satellite.
Allows calculation of
precise positions of the
satellites.
Navigation model
TCS ADS
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
31-5
Issue 1 March 2013
Feature overview
....................................................................................................................................................................................................................................
Data category
Data description
Data provided by
Real time integrity
Describes the real-time status

of the GPS constellation.
TCS ADS
Reference time
GPS Time Of Week

(TOW)
For coarse time

assistance, 2 second
accuracy is required.
NTP server (conversion from

UTC to GPS TOW using
UTC Model)
GPS Time Of Week Assist
Used for modulation data

wipe-off, to improve
signal acquisition.
TCS ADS
Acquisition assistance
Enables fast acquisition of

GPS signals.
UTC model
Relates GPS time to Universal

Time Coordinated (UTC).
TCS ADS
Ionospheric model
Models propagation
delays of the GPS signals
through the ionosphere.
TCS ADS
Allows removal of ~50%

of the ionospheric delay
from the range
measurements.
DGPS corrections
Helps to improve location

accuracy.
Reference position
Approximate position of
the device.
Helps UE GPS receiver to

reduce acquisition time by
reducing search space.
Provisioned information
(SCMS) or previous location
fixes
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
31-6
Issue 1 March 2013
Principles
....................................................................................................................................................................................................................................
Principles
Principles
The Small Cell uses assisted GPS (AGPS) to improve the performance of GPS-based
location lock functionality used by the Small Cell to determine its own geographical
location.
AGPS improves GPS sensitivity and time to first fix using the following information:
Information on the approximate geographical location of the Small Cell (reference

location).
The SCMS provides this information to the Small Cell either using the provisioned
expected geographical location of the Small Cell or using information from a previous
GPS location fix.
Information on the GPS satellites constellation (ephemeris, almanac, integrity, and
ionospheric model).
This information is provided to the Small Cell from an AGPS server.
GPS timing information (reference time).
This information is provided to the Small Cell using GPS-UTC timing conversion
information from the AGPS server and using reference time information provided by
an NTP server.
For this feature, the AGPS server is the TCS Assistance Data Server (ADS).
Assistance data from the TCS ADS is cached locally using an AGPS caching proxy on the
Small Cell Gateway. This cached data is downloaded to individual Small Cells whenever
they perform GPS location detection. The AGPS caching proxy is used to avoid a
substantial increase in the loading of the TCS ADS that would occur if it had to serve
every Small Cell individually.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
31-7
Issue 1 March 2013
Principles
....................................................................................................................................................................................................................................
Architecture description
Figure 31-1 Small Cell assisted GPS architecture using TCS assistance data server
TCS XRN
Xypoint Reference
Network
RINEX 2.10 extended/FTP

TCS ADS
SCMS
Assistance Data Server
Expected Small Cell Position

(Lat/long)
TCS Proprietary
AGPS
Client
GPS Assistance Information

GPS
Receiver
SeGW
ALU Proprietary
AGPS
Caching
Proxy
Small Cell
Timing Information
(NTP)
NTP
Small Cell Gateway
NEs provided by ALU

NEs customer is expected to provide
AGPS Caching Proxy

- Signaling concentrator between Small Cell and TCS ADS
- Cache reduces load on TCS ADS due to Small Cell multiplicity
NEs provided by ALU for Network Level

Software provided by ALU
In the AGPS architecture using TCS ADS, the Xypoint Reference Network (XRN)
collects satellite information from a set of global reference stations and is the source of
information collected from the GPS satellites. The TCS ADS receives and stores the
satellite information from the XRN though an FTP file transfer of extended RINEX 2.10
data.
The AGPS caching proxy in the Small Cell Gateway manages a local store of GPS
assistance data, which it periodically downloads from the TCS ADS. The interface
between the AGPS caching proxy and the TCS ADS uses a proprietary protocol. The
assistance data passed over this interface is the complete set of data for all GPS satellites
and is not location specific.
Whenever the Small Cell requires GPS location detection, the AGPS client in the Small
Cell requests a complete set of assistance data for all GPS satellites from the AGPS
caching proxy in the Small Cell Gateway.
The AGPS caching proxy responds to the request from the AGPS client by sending the
assistance data in its local store. This assistance data is then used by the AGPS client to
assist the GPS receiver in the Small Cell to perform GPS location detection.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
31-8
Issue 1 March 2013
Principles
....................................................................................................................................................................................................................................
The interface between the AGPS client and AGPS caching proxy is established through
the IPsec tunnel to maintain the auto-configuration capability of the Small Cell. If instead
a direct connection was supported between the client and proxy outside the IPsec tunnel,
additional firewall configuration for the end user in the end user network this could be
required. The extra configuration of firewall rules in the end user network to open up
ports for the interface between the AGPS client and the AGPS caching proxy is avoided
by establishing the interface through the IPsec tunnel. Enterprise networks, in particular,
have stringent firewall rules defined and prefer to minimize the number of ports opened.
The IPsec tunnel also provides security for the interface between the AGPS client and
AGPS caching proxy. This ensures integrity of the assistance data. While currently no
information sent over the interface requires privacy, if the interface is extended in the
future to include such information, IPSec also provides confidentiality of that private
information. The assistance data is encapsulated in XML between the AGPS client and
AGPS caching proxy to provide an extensible interface on which additional information
can be transferred in the future.
For redundancy, it will be possible to provision the AGPS caching proxy with a primary
and secondary TCS ADS. If the proxy fails to download information from the primary
server it switches to the secondary server.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
31-9
Issue 1 March 2013
....................................................................................................................................................................................................................................

Small Cell
Attributes of class GPS
The following attributes are readable and are reused when the last GPS detected location
is used for the AGPS reference location:
Parameter
Description
Syntax
Values
lockedLatitude
Specifies the latitude of the device in

degrees, multiplied by 1 million. A
positive value signifies north of the
equator. A negative value signifies
south of the equator.
integer
[-90000000
..90000000]
Range is from: 90 00.00' South

(-90,000,000) to 90 00.00' North
(90,000,000).
Example: A latitude of 13 19.43' N
would be represented as 13,323,833,
derived as (13*1,000,000)+((19.43*1,
000,000)/60). A latitude of 50 0.00' S
is represented as -50,000,000.
This value is retained across reboots
and is only reset after another scan
completes successfully. If no scans
have yet succeeded, a value of 0 is
reported.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
31-10
Issue 1 March 2013
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
lockedLongitude
Specifies the longitude of the device

in degrees, multiplied by 1 million. A
positive value signifies east of the
prime meridian. A negative value
signifies west of the prime meridian.
integer
[-180000000
..180000000]
integer
[-9999..9999]
Range is from: 180 00.00' West

(-180,000,000) to 180 00.00' East
(180,000,000).
Example: A longitude of 13 19.43' E
would be represented as 13,323,833,
derived as (13*1,000,000)+((19.43*1,
000,000)/60). A longitude of 50 0'0''
W is represented as -50,000,000.
completes successfully. If no scans
have yet succeeded, a value of 0 is
reported.
lockedAltitude
Defines the altitude position of the

network element relative to the
WGS84 reference ellipsoid surface.
completes successfully. If a scan has
never succeeded before, the value 0
is reported.
unit=meters
The following attributes of class GPS are configurable and are used when the expected
location is used for the AGPS reference location:
Parameter
Description
Syntax
Values
aGPSreferenceAltitude
Defines the reference location of the

device with coarse accuracy for use
by AGPS. This parameter specifies
the altitude relative to the WGS84
reference ellipsoid surface.
integer
[-9999..9999]
Specifies the maximum radius of the

provisioned Small Cell location
allowed.
integer
authorisedLocationRadius
unit=meters
[11..5000]
unit=meters
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
31-11
Issue 1 March 2013
....................................................................................................................................................................................................................................
The following attributes are configurable for defining the AGPS reference position:
Parameter
Description
Syntax
Values
aGPSreferenceAltitude
Defines a reference location for the

the altitude relative to the WGS84
reference ellipsoid surface.
integer
[-9999 .. 9999],
unit=meters
aGPSreferenceLongitude
Defines a reference location for the

the longitude in degrees (including
fractional part), multiplied by 1
million. A positive value signifies
east of the prime meridian. A
negative value signifies west of the
prime meridian.
integer
[-180000000 ..
180000000]
aGPSreferenceLatitude
Defines a reference location of the

the latitude in degrees (including
fractional part), multiplied by 1
million. A positive value signifies
north of the equator. A negative
value signifies south of the equator.
Range is from: 90 00.00' South
(-90,000,000) to 90 00.00' North
(90,000,000).
integer
[-90000000 ..
90000000]
Defines a reference location of the

the horizontal accuracy.
integer
aGPSreferenceHorizontalAccuracy
default=0
[1..20000]
units=kilometers
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
31-12
Issue 1 March 2013
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
aGPSLocationSource
Defines the source of the estimated

location that will be used by AGPS.
Enum:
expected is the provisioned

expected location of the device.
referenceAndLastKnown
referenceAndLastKnown is the
coarse AGPS reference location
when either no previous location has
been detected, or movement has
been detected and the last known
location if movement of the device
has not been detected.
spare1
Values
expected
spare2
spare3
spare4
spare5
The following attributes are configurable for defining the AGPS client parameters:
Parameter
Description
Syntax
aGPSclientType
Specifies the type of AGPS client.
enum AgpsClientType
aGPStimerConnectionDelayInitial
Defines the initial time that the

AGPS client will wait between
attempts to re-establish
communication with a server or
proxy following failure. This will be
an initial value for a timer that
doubles on each failure until the
maximum is reached, at which time
it will continue at the maximum
value.
uint16
aGPStimerConnectionDelayMax
Defines the maximum time that the

AGPS client will wait between
attempts to re-establish a
communication link with a server or
proxy following failure.
uint16
aGPStimerPeriodicRefresh
Defines the interval between

periodic refreshes of GPS assistance
data.
uint16
Values
[6..3600]
unit=secs
[6..14400]
unit=secs
[6..6900],
unit=secs
Attributes of class AGPS
The following attributes are configurable to define the AGPS proxy:
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
31-13
Issue 1 March 2013
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
proxyAddress
Contains the FQDN or IP address as

a dotted decimal value of the assisted
GPS proxy.
String length=128
assistancePort
Specifies the transport layer port

used for the assistance protocol.
integer
Values
[0..65535]
The following attributes are configurable and will be used when the expected location is
used for the AGPS reference location:
Parameter
Description
Syntax
latitude
Defines the latitude of the network

element.
struct Latitude
longitude
Defines the longitude of the network

element.
struct Longitude
Values
Small Cell Gateway

Attributes of class AGPSProxy
The following attributes are configurable for the AGPS proxy function:
Parameter
Description
Syntax
proxyType
Specifies the type of AGPS proxy.
enum AgpsProxyType
addressServer
Provides either the IP address or

FQDN of the AGPS server.
string
portServer
Provides the destination port number

used for connections to the AGPS
server.
integer
ipAddressServerLocal
Provides the IP address of the AGPS

Proxy used by the AGPS server.
ipaddress
portProxyServer
Specifies the source port number

used by the AGPS proxy for
connections towards the AGPS
server.
integer
authorisationIdentity
Contains an identity that will be used

by the AGPS server to authorize the
source of the request.
String length=128
Values
length=50
[0..65535]
[1024..65535]
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
31-14
Issue 1 March 2013
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
ipAddressClientProxyLocal
Provides the IP address of the AGPS

Proxy that is the destination address
used by AGPS clients.
ipAddress
portClientProxyLocal
Specifies the port the AGPS proxy

will listen to for connection requests
from AGPS clients
integer
[1024..65535]
timerConnectionReestablishmentDelay
Defines the time that the AGPS

proxy waits to establish a
communication link with the AGPS
server following a failure.
uint16
[10..3600]
timerPeriodicRefresh
Defines the interval between periodic

refreshes of GPS assistance data
from the AGPS server.
uint16
unit=secs
[6..6900],
unit=secs
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
31-15
Issue 1 March 2013
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
31-16
Issue 1 March 2013
32
32
Increased
paging capacity
for large Metro cells
deployment (same LA)
Overview
Purpose
This chapter describes the Increased paging capacity for large Metro cells deployment
(same LA) (100854) feature.
Contents
32-2
Principles
32-4
Increased paging capacity parameters
32-12
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
32-1
Issue 1 March 2013
Increased paging capacity for large Metro cells deployment

(same LA)

(same LA)
....................................................................................................................................................................................................................................

(same LA)
Feature number

Feature description
This feature allows large deployments of Metro Cells in public places to use the same
Location Area (LA) as the macro network. This feature avoids loading the CN and macro
network capacity when UEs move past Metro Cells in a busy public environment.
In order to support paging for a complete macro LA, a Small Cell cluster must connect to
every CN node in the Iu-Flex pool.
Because the BSG and Small Cell must manage a full RNC LA of paging, a new paging
interface and internal performance optimizations on both the BSG and Small Cell help to
reduce the loading due to extra paging.
Feature benefits
This feature provides the following benefits to the service provider:
Reduced macro RNC load LAU and RAU

Reduced CN load for SGSN and MSC when there are many LAU and RAU
Reduced resource consumption in the Small Cell during reselection from macro to
Small Cell
End user benefits
This feature provides the following benefits to end users:
Reduced delays for the user when redirected from a Small Cell to macro cell
Reduced battery impact due to LAU (especially for phones with low PS activity)
Impacted systems
Small Cell CPE

Small Cell Gateway
BSG
SCMS
IPC
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
32-2
Issue 1 March 2013

(same LA)

(same LA)
....................................................................................................................................................................................................................................
Dependencies
When a BSG is required to cover the same LA and RA as the macro cell for an LAC on a
different MSC/SGSN, this feature is dependent on the Standard Iu Flex (75397) and
Customized Iu Flex (77712) features.
Several Small Cells must be deployed in a network to support the paging load. The
Small Cell need to serve a certain number of distinct geographical regions based on
capacity planning.
Each BSG supports fewer Small Cells when dealing with the increased paging load.
If Standard or Customized IuFlex IuFlex is supported, the BSG restricts its Iu
interfaces to MSCs and SGSNs and not through an IPC, for this feature.
Currently, the IPC cannot support the increase in Iu interfaces, hence the Paging
message rates required for this feature with the maximum number of Iu interfaces
provided via IuFlex for this feature. However, this is an IPC restriction on the BSG,
and the BSG does not prevent such a configuration.
If IuFlex is deployed on the macro cell, then standard IuFlex must be deployed on the
BSG.
In this case it is not possible to have a mixture of Iu Flex on the macro cell and a
single Iu on the BSG with same LA and RA as the macro cell, otherwise the paging
will not be successful.
If Iu Flex is not deployed on the macro cell, then custom Iu Flex must be deployed on
the BSG.
Presence functionality is limited when the same LA and RA as the macro cell is
deployed. This is because there is no LAU or RAU, and the presence functionality
only detects presence when the UE moves into connected mode.
The Small Cells must not use the same LA and RA as the macro cell when in closed
access mode, due to the lack of access control.
A different network name using MM/GMM information cannot be used when the
same area code as the macro cell is used.
PS data shutdown may not be applied when using same LA and RA as the macro cell.
The SuperLAC feature must not be used with this feature.

The BSG can only host up to 32 Ius and requires multiple BSGs when this limit is
exceeded.
Feature type
Optional
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
32-3
Issue 1 March 2013

(same LA)
Principles
....................................................................................................................................................................................................................................
Principles
Problem statement
Metro Cells may be deployed to provide additional coverage or capacity to the macro
network. Those Metro Cells may be deployed indoors or outdoors, and any user is
allowed to camp on to it. In order to avoid swamping the core network, macro RNC and
Metro Cell with Location/Routing Updates, the public Metro Cells must be able to use the
same Location Area Code (LAC) and Routing Area Code (RAC) as the overlapping
macro cell.
When a different LAC and RAC is used to those of the underlying macro network, the
following scenarios are typical:
A user enters the coverage area of the Metro Cell from idle:
The RAU/LAU trigger results in resources being allocated for the procedure
(approximately 4 seconds of DCCH on the Small Cell). This will use up one user
of the Metro Cell user capacity for the available duration, although feature 104376
(DCCH in Cell_FACH) can mitigate for this prior to the introduction of feature
100854.
The RAU/LAU results in a signaling connection creation to the MSC and SGSN,
as well as security procedures, which loads the MSC and SGSN.
The MSC performs signaling to the HLR to update the subscriber location (If on a
different MSC/SGSN to the macro cell), which will load the HLR.
A user leaves the coverage area of the Metro Cell:

The RAU/LAU trigger results in resources being allocated on the macro cell,
using macro processor and physical layer resources.
The RAU/LAU results in the creation of a signaling connection to the MSC and
SGSN, as well as security procedures, which loads the MSC and SGSN.
If the MSC that is connected to the Small Cell cluster differs from the macro
MSC, the MSC performs signaling to the HLR to update the subscriber location,
which will load the HLR.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
32-4
Issue 1 March 2013

(same LA)
Principles
....................................................................................................................................................................................................................................
Figure 32-1 Scenarios when the Small Cell and underlying macro network use
different LAC and RAC
Macro Cell - LAC1

BSR Coverage - LAC2
Attached UE moving
LAU/RAU
LAU/RAU
Solution description
If the Small Cell uses the same LA and RA as the macro cell, then the BSG and Small
Cell must manage a full RNC LA of paging. This will be a much higher volume than
previously required. This raises the need to perform paging optimization, since when a
UE is paged, the paging message is sent to all Small Cells in that LAC, as well as to
macro cells. Processing all of the paging messages from the macro cell can overload the
Small Cell.
Generally, Small Cell CPU usage is dominated by the number of packet exchanges.
Therefore, one major optimization that can be made in the Small Cell is for the BSG to
batch paging messages from the CN.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
32-5
Issue 1 March 2013

(same LA)
Principles
....................................................................................................................................................................................................................................
Optimizations necessary to help reduce the loading due to extra paging:
Have the gateway perform preprocessing of the ASN.1 paging records and provide a
separate SCTP application context for a paging stream that combines both the PS and
CS paging records into a TLV format.
Internal improvements in efficiency. In addition, optimize the control plane handling
of paging messages within the Small Cell and BSG.
The BSG aggregates RANAP paging messages over an OAM configurable time
(batching delay), for example, 100-200 ms. The BSG then transfers and processes the
aggregated requests as a single entity until they are scheduled for transmission over
the air. The BSG can selectively perform this on Small Cells that are configured with
the same LAC as the macro. In all other cases the existing paging mechanisms should
be used.
This in turn creates a new proprietary protocol called BSG Paging Protocol (BSGPP)
The impacts of the optimizations are:
Paging delay will be increased by the delay due to batching.

A proprietary message stream is used for paging.
Due to restrictions on the performance with the volume of messages, the IPC is a
performance bottleneck for this feature. The feature works much better when the Iu
interfaces are IP.
Some operators may have for example, the SGSN on IP Iu and MSC on ATM Iu, so the
paging load on the IPC may be lower than that presented to the BSG.
Cell_FACH and Cell_PCH UEs on macro reselecting to a Small Cell on the same LA and RA as the
macro cell
Being on the same LA and RA as the macro cell does not prevent all signaling impacts
due to mobility in connected mode Cell_FACH or Cell_PCH or URA_PCH state on the
macro and reselecting to the Small Cell.
The Small Cell would normally release the RRC connection with release cause Directed
Signaling Connection Re-establishment (DSCR). This results in the UE performing an
RAU procedure with the SGSN, and the SGSN then releasing the Iu from the RNC,
which means that the UE, RNC and SGSN are in synch. However, this still results in
SGSN signaling due to the RAU procedure.
Some operators exclude from their KPIs drops due to call drops in PCH state. However,
the operator should still consider whether to send release cause DSCR or release cause
Normal release. This is controlled by a MIM parameter that is provisionable through
OAM.
This case is shown in the following figure:
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
32-6
Issue 1 March 2013

(same LA)
Principles
....................................................................................................................................................................................................................................
Figure 32-2 DSCR case

UE
RNC
BSR
SGSN
MSC
UE in PCH/FACH state with connection to RNC/SGSN

Cell Update triggers BSR
to release UE with cause
DSCR
Cell/URA Update(reselection, U-RNTI)
DSCR triggers UE to
perform RAU to inform
SGSN that UE is on a new
Iu
RRC Connection Request
Iu exists from
SGSN to RNC
RRC Connection Release (DSCR)
RAU procedure triggered by DSCR

Iu Release Command
Iu Release Complete
Iu Release Command
UE resources and Iu
released on RNC
Following RAU,
UE is likely to be
put into idle
Iu Release Complete
Another approach is to release the UE with a normal cause value and not trigger the RAU
procedure. However, with this approach DL data may be lost towards the UE and the
macro KPIs may look poor due to the loss of the UE (drop) when the response to the
UTRAN paging procedure fails to be received (PCH), or RLC disrupts (Cell_FACH).
This case is shown in the following figure:
Figure 32-3 Non-DSCR case and loss of data
UE
RNC
BSR
SGSN
UE in PCH/FACH state with connection to RNC/SGSN

Cell Update triggers BSR
to release UE withnormal
cause
MSC
Iu exists from
SGSN to RNC
Cell/URA Update(reselection, U-RNTI)

RRC Connection Release (Normal release)
DL data
Iu Release Request
Iu Release Command
Iu Release Complete
RANAP Page
RANAP Page
Idle Mode Page
RLC disruption in
FACH or paging
timeout in PCH
state
New DL data
results in UE
being paged
RRC Connection Request
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
32-7
Issue 1 March 2013

(same LA)
Principles
....................................................................................................................................................................................................................................
RRC redirection
When the same LA and RA as the macro cell is used, RRC redirection can still be
performed without a LAU or RAU. This is especially advantageous when service-based
redirection is used, for example, if the Small Cell when a Metro Cell attempts to perform
PS offload from the macro cell.
All UEs in the coverage area of the Metro Cell reselect towards to the Metro Cell, and
any RRC Establishment causes for conversational QOS (MO) are redirected to the macro
cell.
When a different LA to macro is used, call setup is delayed because the UE must perform
a LAU prior to voice establishment. Also in this case Mobile Terminated voice calls often
cannot be redirected because the paging association is lost.
When the same LA and RA as the macro cell is used, then both MO and MT calls can be
redirected without a LAU or RAU.
Solution architecture
Number of Iu Links
The number of Iu links supported on the BSG is increased as a part of feature 100854
from 12 Iu-CS and 12 Iu-PS to 32 Iu-CS and 32 Iu-PS interfaces.
This support is useful for Small Cell deployment using the same LA and RA as the macro
cell as described below, as well as for normal IuFlex scenarios.
For configurations in which IuFlex is not supported, the operator must support a
Custom IuFlex implementation in which the routing of the initial UE message is
performed based on the Small Cell and macro LAC.
When a new macro LAC or RAC is added for a Small Cell with the same LA and RA as
the macro cell, the appropriate MSC and SGSN Iu link must be re-provisioned to add the
LAC or RAC.
The following diagram shows the configuration of the MSCs and SGSNs and their
associated LAs and RAs for a non-IuFlex configuration. All the Small Cells on an LA
require Iu links to the SGSN and MSC. The LACs must be provisioned on this link in
order to send paging messages to the UEs on the Small Cell.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
32-8
Issue 1 March 2013

(same LA)
Principles
....................................................................................................................................................................................................................................
Figure 32-4 Non-Iu Flex

LA 1,4,8,9,13,17
MSC1
LA 21,24,28,29,33,37
MSC5
FGW1
FGW2
MSC2 LA 2,5,10,14
MSC6 LA 22,25,30,34
LA 6,11,15,18
MSC3
MSC4
LA2
LA1
LA4
LA8
LA9
LA13
MSC8
LA14
LA15
LA18
LA22
LA21
LA7
LA11
LA10
LA17
LA 3, 7,
12,16,19
LA3
LA6
LA5
LA12
BSRs Geographically
connected to FGW
LA16
LA24
LA28
LA29
LA37
LA35
LA38
LA/RA 3,7,12,16,19
SGSN1
BSRs Geographically
connected to FGW
LA39
LA/RA 23,27,
32,36,39
SGSN7 LA/RA 26,31,35,38
LA/RA 2,5,10,14
LA/RA 1,4,8,9,13,17
LA32
LA36
SGSN8
SGSN3 LA/RA 6,11,15,18

SGSN2
LA27
LA31
LA30
LA34
LA 23,27,
32,36,39
LA23
LA26
LA25
LA33
LA19
SGSN4
LA 26,31,35,38
MSC7
SGSN6
SGSN5
LA/RA 22,25,30,34
LA/RA 21,24,28,29,33,37
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
32-9
Issue 1 March 2013

(same LA)
Principles
....................................................................................................................................................................................................................................
Iu Flex
Figure 32-5
LA 1-19
LA 21-39
MSC1
LA 1-19
FGW1
FGW2
LA 21-39
MSC2
LA 1-19
LA 21-39
MSC3
LA 1-19
LA2
LA1
BSRs Geographically
connected to FGW
LA4
LA8
MSC4
LA5
LA9
LA13
LA14
LA15
LA12
LA16
LA19
LA/RA 1-19
LA/RA 1-19
LA24
LA7
LA11
LA18
LA22
LA21
LA3
LA6
LA10
LA17
LA 21-39
LA28
LA29
LA33
LA23
LA26
LA25
LA34
LA37
LA27
LA31
LA30
LA35
LA38
LA36
LA39
LA/RA 21-39
SGSN4
SGSN Pool
LA/RA 1-19
LA/RA 1-19
LA/RA 21-39
SGSN3
LA/RA 21-39
SGSN2
SGSN1
BSRs Geographically
connected to FGW
LA32
LA/RA 21-39
If IuFlex is supported, the operator must provision the whole Iu pool in the SGSN and
MSC for the Iu link to the BSG with the appropriate LAC and RAC used for Small Cells
with the same LA and RA as the macro cell.
MSC and SGSN dependencies
When a BSG is deployed to handle a number of macro location areas, the Iu in the MSC
and SGSN connected to the BSG must be provisioned so that it reflects all of the LA and
RA that the BSG handles.
SAI provisioning
The SAI is PLMN-Id || LAC || SAC.

The SAC is a 2 byte number and is not explicitly broadcast from the macro network.
Many operators equate the macro cell SAC to the broadcast Cell ID.
Different operators may have different requirements for this.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
32-10
Issue 1 March 2013

(same LA)
Principles
....................................................................................................................................................................................................................................
Two scenarios exist for provisioning the SAI of the Metro Cell:
It can be provisioned manually
It can be auto-configured to be the same as that of the macro cell
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
32-11
Issue 1 March 2013

(same LA)
....................................................................................................................................................................................................................................

Small Cell
Attributes of class BSR for feature control
Parameter
Description
Syntax
Values
enableSameLaRaMacro
Controls feature activation for Same

LA/RA as macro.
Enum
EnableSameLaRaMacro
disable=0
macroLacRacConfig
disable disables feature
gsm autoconfigure from GSM
fdd autoconfigure from 3G

gsmPreferred - autoconfigure
from GSM if available, 3G
otherwise.
fddPreferred autoconfigure
from GSM if available, 3G
otherwise.
manual use the maually

configured RAC/LAC as same
LA/RA as macro.
Controls autoconfiguration:
macroLacRacList
sameSaiMacro
autoConfigFallBack if auto
configuration is not possible,
fallback to manually configured
LAC/RAC.
gsm=1
fdd=2
gsmPreferred=3
fddPreferred=4
manual=5
Enum
MacroLacRacConfig
autoConfigFallBack
autoConfigOnly
autoConfigOnly if auto
configuration is not possible, do
not go into service.
Provides a list of macro LAC/RAC

which may be configured for Same
LA/RA as Macro
[0...100] struct
MacroLacRac
rac 0....255
Used when same LA/RA as macro is

enabled.
Enum
EnableSameSaiMacro
none
If set to none, the SAI LAC/SAC are

both taken from the BSR MIM.
lac 0...65534
lac
lacSac
If set to lac, the SAI SAC is taken

from the BSR MIM, and SAI-LAC is
the same as the macro. If set to
lacSac, the SAI SAC is taken from
the Cell ID of the macro cell and the
SAI-LAC is the same as the macro.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
32-12
Issue 1 March 2013

(same LA)
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
roamerReleaseCause
Specifies the RRC release cause to

be used when a UE sends a
Cell/URA Update from a
neighboring RNC.
Enum ReleaseCause
dscr
normal
Attributes of class BSR for reporting

Parameter
Description
Syntax
Values
broadcastLac
Contains the LAC broadcast by the

Small Cell. Read only.
integer
0...65534
broadcastRac
Contains the RAC broadcast by the

Small Cell. Read only.
integer
0....255
measureLAU
Controls activation of measurements

of the old LAI in LAU procedures.
Populated in lauStats.
Boolean
lauStats
Specifies the structure of statistics

identifying the frequency of old LAI
in a LAU procedure. Read only.
[0..10] struct LAUstats
resetSameLaRaCounter
Triggers the Small Cell to reset all

entries of BSR::lauStats.
boolean
Attributes of class LAUstats

Parameter
Description
Syntax
Values
lac
Specifies the LAC determined in

LAU.
integer
0...65534
lacStatsDay
Specifies the number of LAU for the

LAC for the current day.
integer
[0...65535]
lacStatsLastDay

LAC within the previous day (that is,
from midnight to midnight).
integer
[0...65535]
lacStatsLastWeek

LAC within the previous week (that
is, last week Monday 00:00 to
Sunday 24:00).
integer
[0...65535]
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
32-13
Issue 1 March 2013

(same LA)
....................................................................................................................................................................................................................................
Small Cell Gateway

Parameter
Description
Syntax
Values
macroLacRacList
Provides a list of LAC/RAC that are

configured for same LA/RA as
Macro.
sequence [0...100]
struct MacroLacRac
rac 0....255
Specifies the batching interval for

paging messages when Same LA/RA
as Macro is applied.
integer
[100...1000]
Defines the maximum Batch Rate

Interval allowed. This should be
determined by the network provider
provisioning a maximum Batch Rate
interval to be less than the Small Cell
DRX cycles.
integer
batchPagingOverloadLow
Specifies the number of BSGPP

Batch Paging messages per second
supported by the BSG before a
warning is raised.
Integer
[1000..100000]
batchPagingOverloadHigh
Specifies the number of BSGPP

Batch Paging messages per second
supported by the BSG before Batch
Paging messages are dropped.
Integer
[1000..100000]
minBatchPagingCPUUtilization
Specifies the minimum CPU

utilization for batch paging.
Integer
[50..90]
bsgppBatchInt
bsgppMaxBatchInt
lac 0...65534
unit=ms
[100...1000]
unit=ms
step=5
unit=%
maxBatchPagingCPUUtilization
Specifies the maximum CPU

utilization for batch paging.
Integer
[50..90]
step=5
unit=%
pagingOverloadLow
pagingOverloadHigh
Specifies the number of RANAP

pages per second supported by the
BSG before a warning is raised.
Integer
Specifies the number of RANAP

pages per second supported by the
BSG before paging messages are
dropped.
Integer
[1000...100000]
unit=RANAP
paging
messages/sec
[1000...100000]
unit=RANAP
paging
messages/sec
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
32-14
Issue 1 March 2013
33
33 broadcast services in
Cell
support of CMAS
Overview
Purpose
This chapter describes the Cell broadcast services in support of CMAS (76986) feature.
Contents
33-2
Principles
33-4
CMAS Small Cell architecture
33-7
Cell broadcast services in support of CMAS parameters
33-11
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
33-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number

Feature description
This feature enables operators to broadcast Commercial Mobile Alert System (CMAS)
messages to all UEs in any cell or cells within the Small Cell network. CMAS messages
are used to transmit emergency warnings in the US.
The CMAS (Commercial Mobile Alert System) service is specific to the US and is
established by the Federal Communications Commission (FCC). CMAS messages
originate from Federal Agencies. The CMAS network allows the Federal Emergency
Management Agency (FEMA) to aggregate alerts from the President of the United States,
the National Weather Service (NWS) and state and local emergency operations centers.
The alerts are then sent over a secure interface to participating wireless providers who in
turn sends those emergency alerts as cell broadcast messages to their subscribers.
For this feature, the Small Cell network provides connectivity to a Cell Broadcast Center
(CBC) which, on receiving requests from the operations centers, is responsible for the
generation of the broadcast messages into the wireless network. Once broadcast messages
have been received from the CBC, the Small Cell network is responsible for managing,
routing and transmitting the broadcast messages to the correct Small Cells that have been
addressed by the CBC.
Feature benefits
This feature enables the mobile operator to support a seamless Commercial Mobile Alert
System (CMAS) service in the US across the macro and Small Cell networks.
End user benefits
This feature enables end users to receive emergency warning messages across the whole
wireless network.
Impacted systems
Small Cell CPE
Small Cell Gateway

SCMS
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
33-2
Issue 1 March 2013
....................................................................................................................................................................................................................................
Dependencies
This feature is dependent on the following:
UEs with the CMAS application

Cell Broadcast Center
Only Active-Standby redundancy of the CBC is supported. Active-Active redundancy

is not supported.
When this feature is enabled on the Small Cell Gateway, the Small Cell Gateway must
be provisioned with the IP addresses of the primary and secondary Cell Broadcast
Center nodes.
If used in a network where the same LA is used for Small Cells and the macro
network, the capacity of the cell broadcast channel must be balanced with the capacity
requirements of the other channels.
Because of the impact on performance and capacity, this feature is only supported on
the ATCA platform for the Small Cell Gateway.
This feature will impact the UE battery life due to the additional broadcast messages
that must be detected and read. This is mitigated by using Level 1 DRX and by
deactivating the CTCH completely during periods of inactivity for cell broadcast.
When cell broadcast messages target a long list of service areas, the performance of
theSmall Cell Gateway is impacted due to the distribution and concentration of
sending such messages to, and collecting responses from, a large number of cells.
However, for CMAS, the frequency of cell broadcasts that target a large geographical
area is expected to be low.
Feature type
Optional
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
33-3
Issue 1 March 2013
Principles
....................................................................................................................................................................................................................................
Principles
Overview
CMAS alerts are sent to a Cell Broadcast Centre (CBC) over a secure interface using
proprietary dialog messages.
Three classes of warning notifications are supported:
Presidential
Imminent threat
Child abduction emergency (for example, AMBER)
CMAS uses the infrastructure of the Cell Broadcast Service (CBS) to broadcast CMAS
messages to WCDMA UEs. CMAS uses broadcast messages of up to 90 characters of
English text supported by GSM 7-bit encoding. These messages fit within 1 page of the
15 pages permitted by the Cell Broadcast Service. CMAS introduced new message
identifiers to the Cell Broadcast Service in the 3GPP R9 specification. However, these
identifiers are only significant between the CBC and the UE at the application layer.
Therefore for the UTRAN, CMAS is fully supported without modifications to the
standard Cell Broadcast Service (available since the 3GPP R99 specification).
CMAS requires a specialized CMAS application on the UE that supports the requirements
for the display and alerting of CMAS messages to the end user. This application is an
extension to the normal Cell Broadcast functionality on UEs, so only CMAS capable UEs
can support the service. This UE capability is transparent to the UTRAN. CMAS
messages are broadcast by the UTRAN independently of whether any CMAS capable
devices are within range to use them.
The Small Cell network for CMAS is depicted in the following figure:
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
33-4
Issue 1 March 2013
Principles
....................................................................................................................................................................................................................................
Figure 33-1 Small Cell network for CMAS

Feature Scope
Macro RNC
Federal Alert Gateways
Small Cells
Uu
Security
Gateway
IuBC
SABP/SCTP/IPSEC
Small Cell
Gateway
IuBC
SABP/TCP Cell
Broadcast
Centre
CMSP
Gateway
Hurricane Warning
The Federal Alert Gateway is responsible for aggregating requests from Federal Agencies
and Emergency Operations Centers and sending them to the CMSP Gateway.
The CMSP Gateway functions as a CBE in the cell broadcast architecture, submitting cell
broadcast messages to the CBC.
The CBC packages the CMAS messages into a 3GPP standard format of CBS broadcast
message data that is used to transfer the alerts between the CBC and the Small Cell
network. The CBC sends these broadcast messages to one or more target Small Cell
Clusters. Each message is individually addressed to one or multiple cells within the
cluster. The target clusters are determined on the CBC by a mapping of the geographic
target location of the CMAS message to the geographic coverage area of the cells covered
by each Small Cell Cluster. The CBC can also send broadcast messages to RNCs and
BSCs in the macro network.
Within the Small Cell network, the Small Cell Gateway performs signaling concentration
between the multiple Small Cells and the single CBC.
The Small Cell Cluster is responsible for periodically broadcasting the CMAS message
on one or more Small Cell (as addressed by the CBC) that can be read by all the mobile
devices that the Small Cells serve. The Small Cell is responsible for broadcasting the
messages over the air interface to be accessed by UEs.
Other procedures are supported between the Small Cell network and the CBC that allow
for management of the cell broadcast service, such as the ability to terminate message
broadcasts, check the broadcast load on cells, check the status of message broadcasts and
indicate failure and restart of the broadcast service.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
33-5
Issue 1 March 2013
Principles
....................................................................................................................................................................................................................................
Interfaces
The service provider uses the Iu-BC interface to manage Cell Broadcast Services between
the Cell Broadcast Centre (CBC) and the Small Cells. the Iu-BC interface belongs to the
core network of the operator. A CBC can serve multiple Small Cell Clusters, but each
Small Cell Cluster can only be served by a single CBC.
This feature only provides the functionality in the Small Cell network to support the Cell
Broadcast Service for CMAS using the Iu-BC interface to a CBC. The functionality of the
CBC, CMSP Gateway and Federal Alert Gateway is outside the scope of this feature.
These network elements are in the core network of the operator but are external to the
Small Cell network.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
33-6
Issue 1 March 2013
....................................................................................................................................................................................................................................

Architecture
For the Cell Broadcast Service, the management of procedures between the CBC and
Small Cells is controlled over the IuBC interface using the Service Access Broadcast
Protocol (SABP) [3GPP TS 25.419]. The SABP procedures are used to manage the
broadcast of messages on each Small Cell.
In the Small Cell CBS architecture, the CBC submits SABP messages addressed to one or
more cells (known as Broadcast Service Areas) over the IuBC interface to the Small Cell
Gateway. The Small Cell Gateway then identifies and routes these messages to each of
the addressed Small Cells within the Small Cell Cluster.
The Small Cells are the end point where the SABP procedures are terminated and perform
the broadcast of messages over the air interface. The messages are then available to be
read by any UEs that are camped on the cell.
The following diagram shows the Small Cell network architecture that supports CMAS:
Figure 33-2 Small Cell network architecture for CMAS support
U
E
Federal
Alert
Gateway
Uu
SC
C
U
E
Uu
Security GW
SC
Small Cell
Gateway
BSG
U
E
CBC
IP
Router
7750
SR
CMSP
Gateway
Uu
SC
U
E
IuBC
SABP/SCTP/IP
Iu-BC
SABP/TCP/IP/Ethernet
The Cell Broadcast Center accepts requests for Broadcast messages from the CMSP
Gateway and determines which target Small Cell Clusters the messages are be sent to.
The CBC sends a request to the Small Cell Gateway to broadcast a message when it needs
to be targeted to one or more cells within that Small Cell Cluster. For Cell Broadcast,
each cell is uniquely identified and addressed by a Broadcast Service Area. A single
message request can address one or multiple cells.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
33-7
Issue 1 March 2013
....................................................................................................................................................................................................................................
The CBC can support interfaces to multiple Small Cell Gateways and/or multiple RNCs
within the macro network.
The functionality of the CBC is outside the scope of this feature but is described here for
completeness of the network architecture.
Small Cell Gateway / BSR Signaling Gateway
The Small Cell Gateway (SCGW) performs a concentration function between the CBC
and the Small Cells within the cluster. The Small Cell Gateway does not execute the
elementary procedures of SABP, but acts as a router to transfer the SABP messages
between the CBC and Small Cells.
The Small Cell Gateway has the following responsibilities:
Acts as virtual RNC to the CBC.

Acts as a virtual CBC to the Small Cell
Requires connectivity to one CBC. Due to active/standby CBC redundancy, this CBC
can be two redundant network elements with separate IP addresses, but logically it is
considered as a single CBC.
Concentrates and coordinates between the CBC and Small Cells for transit of SABP
messages.
Filters and distributes SABP class 1 messages from the CBC to one or multiple target
Small Cells based on the service areas list received in the request.
Collects SABP messages from one or multiple Small Cells and generates a combined
message for multiple service areas back to the CBC.
Generates Failure information for unsuccessful responses to Class 1 procedures when
Service Areas addressed by the CBC are not registered in the Small Cell Gateway.
Monitors Small Cell link availability. When the connection to a Small Cell is lost,
informs the CBC by initiating the SABP Failure Indication procedure for the Service
Area of the Small Cell.
Ensures that the state of Cell Broadcasts is kept synchronized between the Small Cells
and the CBC.
Small Cell
The Small Cell acts as a virtual RNC to the Small Cell Gateway and is responsible for
managing the broadcast of any cell broadcast messages that are sent to it.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
33-8
Issue 1 March 2013
....................................................................................................................................................................................................................................
The Small Cell has the following responsibilities:
Registration of broadcast SAI (BC-SAI) of the Small Cell to the BSR Signaling
Gateway (BSG) (in WCDMA, the broadcast SAI is used to address individual cells).
Terminates the SABP protocol, provides BM-IWF interworking (simplified as there is
only one cell to manage) and BMC function for broadcast of Cell Broadcast messages
to the UE:
Interpretation of commands from CBC via SABP

Storage of CBS messages
Return to the CBC acknowledgement of successful or failed execution of SABP
procedures
Scheduling of BMC messages containing CBS data and related radio resources
After scheduling has been achieved, sending of CBS data via the
Broadcast/Multicast Control (BMC) protocol over the Uu air interface. The data is
then available to be read by all UEs that are camped on the cell.
Initiates SABP Restart procedure on startup, restart, or link recovery, to inform the
CBC of lost cell broadcast message information.
Small Cell Management System
The Small Cell Management system is responsible for the provisioning of the Broadcast
Service Area Identifier (BC-SAI) on Small Cells. The Broadcast Service Area uniquely
identifies an individual cell in the Small Cell architecture for the purpose of the cell
broadcast service, and is used to address target cells for SABP messages.
The SCMS can also be a source of data that maps the Broadcast Service Area to a
geographic location and cell radius which can be made available to the IT system of the
operator, to allow configuration of the mappings on the CBC. This is for the case when
the Small Cell cluster provides that information, for example when the GPS geo-location
of cells is used. Alternatively, the geographic location may be passed from the IT system
to the SCMS. The architecture and procedures for synchronization of the Broadcast
Service Area and geographic locations between the SCMS and the CBS is not within the
scope of this feature.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
33-9
Issue 1 March 2013
....................................................................................................................................................................................................................................
Assumptions
1. CMAS is a low frequency, best effort service.

There is no priority for the CBC Service
CMAS messages may not be broadcast in certain scenarios, such as overload,

failover, or transport failures.
2. CMAS messages are not configured for continuous lifetime. Instead, they have a
limited lifetime to prevent continuous broadcast of messages during network failures
that lead to loss of messages between the CBC and the Small Cell.
The CBC only configures CMAS messages with a maximum lifetime, not with an
unlimited lifetime.
The Small Cell also allows a maximum lifetime to be configured for messages, for
interoperability with CBCs that configure messages with an unlimited lifetime.
3. Robust error handling for message loss is provided by the CBC.
As the CBC is responsible for management of the cell broadcast service, and
initiates requests and requires responses to be returned for all SABP Class 1
procedures, it is expected to provide the full end-to-end error handling for such
procedures such as monitoring for procedure timeout and for implementing retry
policies in the event of message loss for a procedure.
The CBC is robust against message loss for SABP Class 2 procedures (which do
not have a success or failure response message). For example, the CBC should not
require reception of a SABP Restart Indication to consider a broadcast service
area operational, and should not require reception of a SABP Failure Indication to
determine when a broadcast service area has failed. Instead, the CBC should use
SABP Class 1 procedures (which have a success or failure response message) to
determine when broadcast service areas have failed, and a back-off and periodic
retry mechanism to determine when broadcast services areas become operational.
The Small Cell supports SABP Class 2 Restart and Failure procedures. However,
since these messages are not acknowledged, the Small Cell does not detect the
loss of these messages.
The SABP Error Indication message can only be sent by the Small Cell Gateway.
Concentration of SABP Error Indication messages from multiple Small Cells to a
single response to the CBC is not possible because the Small Cells may not report
all errors, or may report different errors, or may include different types of optional
information in the message. When possible, the Message Identifier IE and Serial
Number IE is included in the SABP Error Indication message to allow the CBC to
identify the procedure that has failed. However, this may not be possible in all
cases, for example, if those fields cannot be decoded from the initiating message.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
33-10
Issue 1 March 2013
....................................................................................................................................................................................................................................

Small Cell
Parameter
Description
Syntax
cbsEnable
Enables and disables the Cell

Broadcast Support feature.
Boolean
cTCHdeactInterval
Specifies the duration of Cell

Broadcast inactivity for the
deactivation of the CTCH. A setting
of 0 means that the CTCH is always
available while cell broadcast
messages are scheduled to be
broadcast.
integer
Specifies the maximum duration of a

cell broadcast message before the
BSR takes action to stop
transmission. A setting of 0 means no
preemptive action is taken.
integer
Specifies the guard time for SABP

restart procedures initiated by the
Small Cell. If failover of the Small
Cell Gateway is detected within this
time and the restart was not received
by the CBC, then messages are
re-sent. The value of this attribute
should account for any delays by the
Small Cell Gateway in sending the
message to the CBC .
uint16
Specifies the delay until CTCH is

deactivated after a kill of all
broadcast messages. This avoids
deactivating the CTCH while
broadcast messages are being resent
after a kill.
uint16
cbMessageKill
sABPrestartGuardTimer
cTCHdeactDelay
Values
0...2000
unit=seconds
0...30
unit=days
[0..1800]
unit=secs
[0..2000]
unit=secs
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
33-11
Issue 1 March 2013
....................................................................................................................................................................................................................................
Attributes of class LCELL

Parameter
Description
Syntax
Values
sacCbs
Specifies the SAC for the broadcast

domain.
integer
0...65535
lacCbs
Specifies the LAC for the broadcast

domain.
integer
1....65535
ctchN
Specifies the period for CTCH

allocation (N) broadcast in SIB5.
integer
1...256
unit=frames
The value of this parameter is

optimized for the scheduling of
BMC messages. Alcatel-Lucent
recommends that you do not change
the value of this parameter.
ctchK
Specifies the CBS frame offset (K)

broadcast in SIB5.
integer
0...255
unit=frames
The value of this parameter is

optimized for the scheduling of
BMC messages. Alcatel-Lucent
recommends that you do not change
the value of this parameter.
ctchBmcMaxLoad
tSib5Reading
Specifies the maximum CTCH load.

Used for BMC CAC to reject cell
broadcast messages if CTCH load is
exceeded.
uint16
Specifies the time until a UE has

read SIB5, that is, SIB5 repetition
period, plus duration of SIB5
broadcast.
uint16
10..90
unit=percent
02000
unit=ms
Small Cell Gateway

Parameter
Description
Syntax
Values
maxSABPmessageDistributionRateNormalLoad
Defines the maximum rate of egress

(in messages per second) that SABP
messages will be distributed to Small
Cells when the Small Cell Gateway
is not in overload.
integer
[1000..256000]
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
33-12
Issue 1 March 2013
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
maxSABPmessageDistributionRateOverload
Defines the maximum rate of egress

(in messages per second) that SABP
messages will be distributed to Small
Cells when the Small Cell Gateway
is in overload.
integer
[1000..256000]
maxSABPmessagesAllowedOnEgressQ
Defines the maximum number of

SABP messages that will be added to
the egress queue towards the Small
Cells in one sequence. This ensures
that when a SABP message is
distributed to a large number of
Small Cells, sending of non-SABP
messages to Small Cells will not be
delayed until one complete set of
SABP messages has been sent, but
will instead be interleaved between
several smaller blocks of SABP
messages.
integer
[1..10000]

Parameter
Description
Syntax
Values
lacCbs
Defines the LAC used for the

broadcast domain. If set to the value
-1, the LAC has not been configured
integer
[-1..65535]
sacCbs
Defines the SAC used for the

broadcast domain. If set to the value
-1, the SAC has not been configured
integer
[-1..65535]
Values
Attributes of class FGW

Parameter
Description
Syntax
cellBroadcastService
Controls the enabling or disabling of

Cell Broadcast Service on the Small
Cell Gateway. When set to True the
service is enabled.
Boolean
diffServCodePointCBC
Defines the DiffServ Code Point to

be used for all outgoing traffic on the
IuBC interface to the Cell Broadcast
Centre.
enum DSCPRange
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
33-13
Issue 1 March 2013
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
cellBroadcastResponseGuardTimer
Specifies the time to wait for Small

Cells to send their responses to a
Cell Broadcast procedure before a
combined response is sent to the Cell
Broadcast Centre. The timer is
started when a procedure is initiated
to Small Cells. The timer is stopped
when every Small Cell has sent a
response for the procedure and a
response has been sent to the CBC.
Upon expiry, a response is sent to the
CBC, and any Small Cells that have
not responded are considered to have
failed the procedure.
integer
[1..300]
unit=secs
Attributes of class IuBC

Parameter
Description
Syntax
ipAddressCellBroadcastPrimary
Defines the primary IP Address for

the Cell Broadcast Center.
ipAddress
ipAddressCellBroadcastSecondary
Defines the secondary IP Address for

the Cell Broadcast Center.
ipAddress
ipAddressCellBroadcastLocal
Defines the IP Address used by the

Cell Broadcast Center to reach the
CB services on the Small Cell
Gateway
ipAddress
retryTimer
Specifies the time to wait before

attempting to set up the TCP
connection to the Cell Broadcast
Center after setup of the connection
has failed. The timer is started when
an attempt to set up the TCP
connection to the CBC has failed.
The timer is stopped when a TCP
connection to the CBC is established.
Upon expiry, another setup of a TCP
connection to the CBC is attempted.
integer
Values
[1..30]
unit=secs
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
33-14
Issue 1 March 2013
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
cellBroadcastRestartWaitTimer
Specifies the period during which

restart indications from individual
SAIs will be combined into a single
restart indication sent to the Cell
started when a restart indication is
received and the timer is not already
running. Upon expiry, a combined
restart indication is sent to the CBC,
for all SAIs for which a restart was
received while the timer was
running. If the value is 0, restarts
will not be combined and separate
restarts will be sent to the CBC for
each SAI.
integer
[0..1800]
cellBroadcastFailureWaitTimer
Specifies the period during which

failure indications for individual
SAIs will be combined into a single
failure indication sent to the Cell
started when a failure event
associated with an SAI occurs and
the timer is not already running.
Upon expiry, a combined failure
indication is sent to the CBC, for all
SAIs for which a failure occurred
while the timer was running. If the
value is 0, failures will not be
combined and a separate failure will
be sent to the CBC for each SAI.
integer
keepAliveTCP
Indicates whether TCP keepalive is

supported on the TCP connection to
the CBC. When set to True, the TCP
keepalive is enabled.
boolean
keepAliveTime
Used for TCP keepalive. Specifies

the interval between the last data
packet sent and the first TCP
keepalive probe.
integer

the interval between subsequential
keepalive probes.
integer
keepAliveIntvl
unit=secs
[0..1800]
unit=secs
[1..7200]
unit=secs
[1..60]
unit=secs
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
33-15
Issue 1 March 2013
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
keepAliveProbes

the number of unacknowledged
probes to send before considering the
connection dead
integer
[1..10]
maximumTransientProcedureThreshold
Defines the upper threshold on the

number of SABP Class 1 procedures
that can be in progress at the same
time on the Small Cell Gateway
before new procedures are blocked.
This is counted based upon the
number of Service Areas included in
all the procedures.
integer
[1..5000000]
overloadCauseValue
Contains the SABP cause value to be

used when sending Error Indication
to the CBC for overload condition at
the Small Cell Gateway. A value of
-1 indicates that no error message
will be sent for overload.
integer
[-1..255]
timerFailover
This defines the maximum length of

time the IuBC will be blocked from
re-establishment following failover
of the Small Cell Gateway. This
prevents SABP procedures from
being performed while the Small
Cells are still reregistering with the
Small Cell Gateway.
integer
[30..600],
unit=secs
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
33-16
Issue 1 March 2013
34

34
Overview
Purpose
This chapter describes the UE based Assisted GPS (123830) feature.

Contents
34-2
Principles
34-5
UE based assisted GPS parameters
34-6
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
34-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number

Feature description
For emergency calls, it may be necessary to determine the exact location of a UE.
Currently, the coverage area of a Small Cell is 100 m or less, and the Small Cell is
sufficiently close to the UE on the Small Cell that the location of the Small Cell can be
reported, and comply with E911 Phase II regulation in the USA. However, the area of
coverage for a Metro Cell Outdoor is typically more than 100 m, so this approximation
for the location of a UE is not sufficient. Therefore a UE must report its location to the
Small Cell.
UEs that are equipped with a GPS receiver can provide an accurate position. However,
when the GPS signal is weak, a UE may fail to obtain a location fix within an acceptable
time, if at all. By providing the GPS receiver with information on its approximate
geographic location; information on the positions of the GPS satellites (ephemeris,
almanac), and accurate time information, the GPS receiver can use a more refined search
algorithm by reducing the search space size (frequency, time) for the satellites that it is
most likely to detect, instead of a performing a completely open search for all satellites.
This improves the sensitivity of the receiver, and improves the ability of the Small Cell to
determine its GPS location when the GPS signal is weak.
With AGPS, much of the information is provided within the assistance data. This reduces
the amount of information that the GPS receiver needs to successfully decode directly
from the messages from the GPS satellite signals before it can determine a GPS location
fix. This reduces the Time To First Fix even when a Small Cell is not located in an ideal
position for GPS signal reception.
The purpose of this feature is to provide GPS assistance data to UEs through open access
Small Cells. This data should be available from feature 119911 (Assisted GPS using
TCS server (p. 31-2)).
The following figure illustrates this feature:
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
34-2
Issue 1 March 2013
....................................................................................................................................................................................................................................
Figure 34-1 UE based assisted GPS

TCS
XRN
GPS
receiver
SeGW
AGPS
client
GPS
receiver
Uu
ll
f Sm a
it ion o
d pos git ude)
te
c
e
n
p
Ex
e/lo
atitud
C ell (l
n
rm atio
g Info
Tim in TP )
(N
Xypoint
Reference
Network
RINEX 2.10 extended/FTP
SCMS
TCS
ADS
NTP
Assistance
Data
Server
ALU proprietary:
E-RRLP/HTTP1.1/TCP/IP
GPS assistance
information
ALU proprietary:
E-RRLP/HTTP1.1/TCP/IP
MSC
AGPS
Caching
Proxy
GMLC
iSMLC
Small Cell
UE
RRLP/RLC/MAC/PHY
NEs provided by ALU
Small Cell
Gateway
SGSN
AGPS Caching Proxy

- Signaling concentrator between Small Cell and TCS ADS
- Cache reduces load on TCS ADS due to large number of Small Cells
NEs provided by customer

NEs provided by ALU for Network Level
Software provided by ALU
Feature benefits
This feature provides the following benefits to the Small Cell service provider:
Improvements in location-based services allow operators to offer additional

innovative services (value added services) and thus generate additional revenues.
Provides improved accuracy compared to Cell-Id based positioning.

Fulfills the US FCC E911 Phase 2 requirements for high accuracy location
determination.
End user benefits
This feature provides the following benefits to the Small Cell end user:
The location accuracy of an end-users/subscriber and thus allow the user to benefit
new services or enhancements of existing services.
Impacted systems
Small Cell CPE
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
34-3
Issue 1 March 2013
....................................................................................................................................................................................................................................
Dependencies
This feature is dependent on the following feature:
119911 Assisted GPS using TCS server (p. 31-2)
AGPS is supported when the target UE is in the Cell-DCH state, whether or not an RAB
is established. AGPS is not supported if the UE is in Cell-FACH.
Feature type
Basic
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
34-4
Issue 1 March 2013
Principles
....................................................................................................................................................................................................................................
Principles
Principles
Autonomous GPS is a UE positioning method based on conventional GPS technology.

The network does not provide any assistance data to the UE. Autonomous GPS may be
emulated by UE based AGPS, in which the network does not provide any assistance data.
Assisted GPS (AGPS), also known as network assisted GPS, allows the network to
deliver assistance data to the UE. The network retrieves this assistance data either from
the GPS signal sent by the GPS satellite constellation, or from the TCS Assistance Data
Server (TCS ADS). The UE performs the GPS measurements with the help of the
assistance data. In UE based AGPS, the UE also calculates the position of the UE.
The accuracy obtained depends mainly on the following:
The quality of the pseudo-range measurements

The accuracy of the clocks
The precision of the positions of the satellites

The relative positions between the different satellites and the receiver (geometry to
the satellites)
Additional ionospheric delay
Satellites are used as reference points. UE based AGPS requires UEs to be equipped with
a full GPS receiver function. Assisted GPS requires the wireless network infrastructure to
be equipped with a reference GPS receiver that can simultaneously see the same satellites
as the UE.
The benefits of using AGPS instead of autonomous GPS are as follows:
The search space size (frequency, time) for the UE is greatly reduced, therefore the
time to first fix (TTFF) is reduced from several minutes to several seconds.
The power consumption of the UE is reduced due to the rapid acquisition of signal
(the network can accurately predict the GPS signal that the target UE will receive and
convey that information to the UE).
The UE can detect and demodulate weaker signals.
Only point to point GPS assistance data delivery associated with a RANAP LRC is
supported in this release.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
34-5
Issue 1 March 2013
....................................................................................................................................................................................................................................

Small Cell
Parameter
Description
Syntax
ueBasedAGPSEnable
Enables and disables the UE based

assisted GPS feature.
Boolean
Values
Attributes of class AGPS

Parameter
Description
Syntax
clientProfile
Specifies the configuration of each

type of profile, that is, Emergency
Service or Commercial Service.
Sequence [0..10] of
AGPS_Profile
referenceTimeAllowed
Specifies whether Reference Time

assist data can be sent to the UE.
Boolean
almanacSatelliteHealthAllowed
Specifies whether Almanac and

Satellite Health assist data can be
sent to the UE.
Boolean
utcModelAllowed
Specifies whether UTC Model assist

data can be sent to the UE.
Boolean
ionosphericModelAllowed
Specifies whether Ionospheric Model

Boolean
realTimeIntegrityAllowed
Specifies whether Real Time

Integrity assist data can be sent to the
UE.
Boolean
navigationModelAllowed
Specifies whether Navigation Model

Boolean
maxUeBasedAGPSProcedureTime
Specifies the number of minutes

allowed for the UE based AGPS
procedure to complete. This is
necessary if delay tolerant in
response time is requested from the
core network.
Integer
ueBasedAGPSMeasCtrlTimeInterval
Specifies the interval in milliseconds

between multiple RRC measurement
control messages sent to the UE.
Integer
Values
[1..60]
unit=minutes
[200..2000]
unit=msecs
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
34-6
Issue 1 March 2013
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
positioningMethodCodeUEBasedAGPS
Specifies the code to use for

positioning method in the position
data IE within a RANAP location
report message if UE based AGPS
reporting is used.
uint16
[0..31]
Attributes of class AGPSProfile

Parameter
Description
Syntax
Values
profileName
Defines the name for an AGPS

profile. Case sensitive.
string
Emergency
Service
Commercial
Service
ueBasedAGPSAllowed
Indicates whether UE based AGPS is

allowed.
boolean
ueBasedAGPSLowDelayAllowed
Indicates whether UE based AGPS

with low delay is allowed.
boolean
ueBasedAGPSResponseTime
Defines the response time of UE

based AGPS.
integer
[6..64],
unit=secs
horizontalAccuracy
Defines the horizontal accuracy of

AGPS.
integer
unit=meters
responseTimeDelay
The delay type for AGPS response

time.
enum
AGPSResponseTimeDelay
maxNumGPSSatellites
The maximum number of GPS

satellites used in RRC measurement
control for this profile.
integer
enableFilterGPSAssistData
Indicates whether filtering of GPS

assist data is enabled.
boolean
allowedAudit
Indicates whether audit of GPS data

is allowed.
boolean
[4..16]
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
34-7
Issue 1 March 2013
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
34-8
Issue 1 March 2013
35
35 objectives joint
Multi
coverage optimization
Overview
Purpose
This chapter describes the multi objectives joint coverage optimization (116498) feature.
Contents
35-2
Measurements and alarms
35-5
Multi objectives joint coverage optimization parameters
35-7
...................................................................................................................................................................................................................................
Alcatel-Lucent SC
35-1
Issue 1 March 2013
....................................................................................................................................................................................................................................

Feature number

Feature description
Without this feature, the pilot power in an Enterprise or Metro environment is set to a
constant value to provide continuous coverage. Variation in the cell load over the day is
not taken into account. However, the number of UEs may suddenly increase, for example
when people gather for a meeting. If the same coverage is maintained, the Small Cell
continues to capture new UEs, leading to degradation of the QoS of the UEs that are
already connected.
The objectives of this feature are to ensure that:
The load is well balanced among the cells over time

The overlap between cells is sufficient to ensure continuous coverage
This feature requires some minimal manual RF planning before deployment. Such
minimal RF planning must ensure that the Small Cells provide the required coverage over
the area of interest (for example, coverage of a premium user in an office but, to limit
interference towards the macro network, no coverage outside the building). Thus the
power level of the Small Cell must not be below or above the configured thresholds.
To allow mobility between cells for continuous coverage, the overlap between cells must
be maintained. The overlap area must be small to minimize interference, but large enough
to allow handover.
The Small Cell must also provide a good user experience by delivering continuously good
QoS. If a Small Cell is loaded and continues to capture new users due to excessive
coverage, then users that are already connected to that Small Cell may be negatively
impacted. Rather than maintaining the same coverage, the Small Cell reduces its pilot
power and less loaded neighboring Small Cells increase their pilot power, thus reducing
the probability that a UE will camp on the loaded Small Cell.
These objectives may conflict. For example, if a Small Cell is fully loaded, that Small
Cell will reduce its area of coverage, which may result in coverage gaps.
Algorithm operation
When the feature is enabled, the algorithm waits for the load to increase to levels
requiring adjustment to the transmit power to balance the load. At lower loads,
measurement reports are activated with a periodicity set by parameter tJcoRscpMrPeriodLowLoad. As the load increases, the measurement frequency changes to a periodicity set
by parameter tJcoRscpMrPeriodHighLoad. When the load level, that is, the number of
active DCH calls, rises above a threshold determined by parameter jCOLoadTrigger, then
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
35-2
Issue 1 March 2013
....................................................................................................................................................................................................................................
the Small Cell uses the reports to derive a power change that will attempt to offload some
users to neighbor cells. If the power change is small (less than the value of parameter
thrJCOInform), then the power change may be implemented entirely by that Small Cell.
For larger power changes, the parameter jCOBalance apportions the change between the
loaded Small Cell and its neighbors, and this change is negotiated using signaling on the
BSRAP protocol. This procedure will be successful only if all neighbors agree to it.
A neighbor can reject the procedure for the following reasons:
Incompatible software
Requested power adjustment is out of bounds for recipient

Recipient is busy with another power adjustment procedure
Recipient is overloaded
No response
A power change is stepped in at a configurable rate. Once the power change has
completed, the algorithm sets a threshold that will trigger the Small Cell to revoke the
power change. When the load reduces to below that threshold, the same procedure is
activated to undo the power change.
If a loaded cell continues to operate at a level above the triggering threshold, the
algorithm can continue to reduce power at that cell.
The algorithm prevents other cells from within the neighbor list of a cell from attempting
to change their power while a power change operation is ongoing (plus a settling time).
Administratively locking a cell will prevent any of its neighbors from performing power
adjustments.
Feature benefits
This feature enhances the SON capabilities of Small Cells.

End user benefits
A network of Small Cells is less likely to overload to the point where new users are
unable to access the system due to capacity limits.
Impacted systems
Small Cell CPE

Dependencies
This feature cannot be enabled if feature 108877 (continuous coverage control based on
admission), is enabled. However, both features may be disabled.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
35-3
Issue 1 March 2013
....................................................................................................................................................................................................................................
The following restrictions and limitations apply:
This feature is intended to be used to be used in a coverage enhancement scenario

with intra-frequency handover only. Deploying into an inter-frequency environment
must be undertaken with careful planning of the radio environment to avoid call drops
of UEs in Compressed Mode that do not yet have sufficient coverage in an alternate
frequency to support a handover.
When configuring neighbor lists, only include Small Cells that are candidates for
handover in the neighbor lists. Do not add a full mesh.
Manually disabling neighbor relationships via parameter BSRneighbourcell::enableInstance does not automatically disable the relationship bidirectionally. This
parameter must be set to false at both ends of a neighbor relationship to disable the
relationship properly without causing adverse effects.
See the BSR Parameters Reference Guide for further information on this parameter.
The algorithm needs sufficient headroom either side of the provisioned transmit
power level to make at least one power level change. This must be accounted for in
network planning. The aim is not to plan for maximum coverage with a cell. The
allowance for headroom must be provisioned manually in the default transmit power
parameter.
If upgrading software on an existing group of Small Cells, all Small Cells must be
upgraded at the same time.
When configuring this feature, check the configuration of handover parameters such
as TimeToTrigger, to ensure the frequency of operation is not too close to handover
algorithm cycles. For example, ensure that the value of tJcoRetry is less than the value
of TimeToTrigger.
To avoid fluctuations in power that may cause interference to the macro layer, add
Small Cells with high levels of mobility to and from the macro layer (both idle mode
LAU and active mode handovers) to the jCOProhibit parameter of its neighbors. If
you expect the neighbor list to change periodically, add such Small Cells to the
jCOProhibit parameter of all Small Cells in the group. A typical installation location
for these mobility cells, or daylight cells, might be at the entrance to a hotel or
office block.
When planning the network, ensure that cells with higher volumes of traffic have
sufficient coverage overlap with neighbors, so that neighbor cells can take some of the
load during peak times when these cells may shrink. A typical installation location for
these social cells might be in a bar in a hotel, or in a canteen in an office block.
Feature type
Basic
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
35-4
Issue 1 March 2013
....................................................................................................................................................................................................................................

Overview
This topic describes the measurements and alarms for the multi objectives joint coverage
optimization feature (116498).
Measurements
The Small Cell maintains the following measurements:
The minimum, time averaged mean, and maximum CPICH Tx power during a
measurement period
The number of times the Small Cell has increased or decreased Tx power in response
to a BSR Power Adjustment Procedure
The number of times the BSR Power Adjustment Procedure is rejected, or fails, for
each cause value (Frozen, Busy, Overload, Out of Bounds Request, No Response,
Feature Disabled, Feature Not Present)
The mean number of UEs with at least one active call
Alarms
The Small Cell raises the following alarms:

Alarm
Severity
Description
Software
Compatibility
Error
Minor
The Small Cell receives a BSR Error Indication (Cause:

Message Type Not Defined) in response to a BSR Power
Adjustment Request.
This alarm indicates the transmitting Small Cell has not yet
been upgraded to support the feature. This alarm is cleared by
manually re-enabling the feature.
BSR Tx
Power
Configuration
Warning
Minor
The Small Cell spends greater than a configurable length of

time during a reporting period with a Tx power level different
to the configured Tx power level.
This alarm indicates that the load density at this Small Cell is
too large for its current Tx power level, so that it may be
advisable to either replan the local area Tx power levels or add
capacity. This alarm is cleared when a subsequent reporting
period does not spend greater than the configurable length of
time with a Tx power level different to the configured Tx
power level.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
35-5
Issue 1 March 2013
....................................................................................................................................................................................................................................
Alarm
Severity
Description
BSR Tx
Power Limit
Reached
Minor
The calculated power change would, when applied to current

Tx power levels, place the Tx power outside the configured
limits.
This alarm indicates that the operator should evaluate whether
to add capacity in the vicinity of this Small Cell. This alarm is
cleared on a subsequently accepted power adjustment.
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
35-6
Issue 1 March 2013
....................................................................................................................................................................................................................................

Small Cell
Parameter
Description
Syntax
jCOEnabled
Enables and disables this feature.
Boolean
Values
By default, the feature is disabled.

Do not enable the feature until the
neighbor list has stabilized. Only
enable it where it is needed (that is,
in load hotspots).
Alcatel-Lucent recommends that you
disable this feature if there are no
Small Cell or macro neighbors,
otherwise it may result in call drops.
jCOProhibit
Contains a list of Small Cell IDs to

be ignored by the multi objective
joint coverage optimization
algorithm. This list may contain IDs
that are not in the current neighbor
list because the Small Cell may be
moved.
sequence [0..64] of
struct BSRID
When adding cells ito this parameter,

the relationship created is not
automatically bi-directional, so care
must be taken to ensure that either
1-way or 2-way behavior is
configured appropriately.
jCOLoadTrigger
When the Small Cell load reaches

this value, the multi objective joint
coverage optimization algorithm is
triggered. Absolute load is
determined by number of DCH UEs.
integer
[1..100]
unit=percent
This value is a percentage of site

capacity.
tJCORetry
thrJCOPowerReset
Specifies the minimum time between

algorithm cycles.
integer
Determines the triggering of a

cancellation of an applied Tx power
reduction.
integer
[0..255]
unit=secs
[0..64]
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
35-7
Issue 1 March 2013
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
thrJCOInform
Sets a Tx Power change threshold

above which the Small Cells must
negotiate with neighbor Small Cells.
real
[0.0..6.0]
unit=dBm
step=0.1
precision=1
tJCOGuard
Specifies a guard timer for responses

to messages.
real
[0.01..2.55]
unit=secs
step=0.01
precision=2
maxJCORate
Specifies the maximum rate of

change of Tx Power for this Small
Cell. It is represented in dBm per
BSR::tJcoPowerStepTime seconds.
real
[0.2..4.0]
unit=dBm
step=0.1
precision=1
txPowerStepSize
Specifies the step size quantization to

use at this Small Cell. The allowed
values are 0.1, 0.5, 1.0 and 2.0.
real
[0.1..2.0]
unit=dBm
step=0.1
This parameter must have the same

value for all Small Cells within the
same group.
precision=1
This parameter relates to specific

hardware. If possible, set its value to
the largest value in a group of
devices, that is, if one Small Cell in a
group supports a 1.0 dB step size,
and the others support a 0.5 dB step
size, then use the value 1.0 dB
throughout the group).
txPowerMaxChange
Specifies the maximum allowable Tx

power change.
real
[0.1..10.0]
unit=dBm
step=0.1
precision=1
marginJCO
Specifies the margin used in

calculating the proposed power
change.
real
[0.0..5.0]
unit=dBm
step=0.1
precision=1
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
35-8
Issue 1 March 2013
....................................................................................................................................................................................................................................
Parameter
Description
Syntax
Values
tTimeToHO
Not used.
real
[0.00..2.55]
unit=secs
step=0.01
precision=2
thrJCOOverload
tJCOTrigger
jCOBalance
Specifies the threshold for raising an

alarm if the Small Cell is operating at
reduced power output for greater
than this percentage of a reporting
period.
integer
Specifies the Time-to-Trigger timer.

When a Small Cell reaches the
triggering load for the multi
objective joint coverage optimization
algorithm, the Small Cell must
maintain this load for at least this
length of time before attempting to
modify its transmit power.
real
When a Tx power change is

computed, this percentage is applied
as a power reduction at the loaded
cell. The remainder is applied as a
power increase at all Small Cell
neighbors in the same group.
integer
[1..100]
unit=percent
[0.1..10.0]
unit=secs
step=0.1
precision=1
[0..100]
unit=percent
This parameter must have the same

value for all Small Cells within the
same group.
tJcoRscpMrPeriodLowLoad
Specifies the periodicity of RSCP

MRs at low load.
enum
ReportingInterval
tJcoRscpMrPeriodHighLoad
Specifies the periodicity of RSCP

MRs at high load.
enum
ReportingInterval
thrJcoRscpMrPeriodSx
Specifies the low/high load threshold

switch as a percentage of
jCOLoadTrigger, to determine RSCP
MR periodicity.
integer
Specifies the time between power

increments and decrements during
power changes.
real
tJcoPowerStepTime
[1..100]
unit=percent
[0.1..5.0]
unit=secs
step=0.1
precision=1
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
35-9
Issue 1 March 2013
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
35-10
Issue 1 March 2013
Glossary
...................................................................................................................................................................................................................................
Numerics
2G
Second-generation wireless
3G
Third-generation wireless
Used to describe technologies such as UMTS and CDMA-2000 that support both voice channels
and higher-capacity data channels.
Also used to describe products that support these technologies.
3G-MSC
Third Generation - Mobile Switching Center

3GPP
Third Generation Partnership Project

...................................................................................................................................................................................................................................
ACL
Access Control List

ADS
Assistance Data Server

ADSL
Asymmetric Digital Subscriber Line

AGPS
Assisted Global Positioning System

AH
Authentication Header
ALCAP
Access Link Control Application Protocol

API
Application Programming Interface
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
GL-1
Issue 1 March 2013
Glossary
....................................................................................................................................................................................................................................
ARFCN
Absolute Radio Frequency Channel Number

AT
AT commands used by GSM. Usually these represent instructions beginning with "AT".
ATCA
Advanced Telecommunications Computing Architecture

ATM
Asynchronous Transport Mode

...................................................................................................................................................................................................................................
BC-SAI
Broadcast Service Area Identifer

BCC
Base Station Colour Code

BCCH
Broadcast Control Channel

BCR
BSR Cluster Release

BER
Bit Error Rate

BMC
Broadcast/Multicast Control
BPG
BSR Packet Gateway

BSG
BSR Signaling Gateway

BSGPP
BSG Paging Protocol

BSIC
Base transceiver Station Identity Code

BVG
BSR Voice Gateway
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
GL-2
Issue 1 March 2013
Glossary
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................................................
CBC

CBS
Cell Broadcast Service

CGI
Cell Global Identification

CHAP
Challenge Handshake Authentication Protocol

CINR
Carrier To Interference plus Noise Ratio

CM
CMAS
Commercial Mobile Alert System

CMSP
Commercial Mobile Service Provider

CPE
Customer Premise Equipment

CPICH
Common Pilot Channel

CS
Circuit Switched
CTCH
Common Traffic CHannel

...................................................................................................................................................................................................................................
DBC
Dynamic Bearer Control

DCCH
Dedicated Control Channel

DHCP
Dynamic Host Configuration Protocol
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
GL-3
Issue 1 March 2013
Glossary
....................................................................................................................................................................................................................................
DL
Downlink
DNS
Domain Name Server

DPAT
Dynamic Port Address Translation

DRX
Discontinuous Reception
DSCP
Differentiated Services Code Point

DSCR
Directed Signaling Connection Re-establishment

DSL
Digital Subscriber Line

Technology for transporting high-speed data over copper-pair subscriber loops.
DSLAM
Digital Subscriber Line Access Multiplexer

...................................................................................................................................................................................................................................
Ec/No
The received energy per chip divided by the power density in the band.
ePLMN
Equivalent Public Land Mobile Network

ESP
Encapsulation Security Payload

ETH
Ethernet
...................................................................................................................................................................................................................................
FACH
Forward Access Channel

FCC
Federal Communications Commission

FDD
Frequency Division Duplex

....................................................................................................................................................................................................................................
Alcatel-Lucent SC
GL-4
Issue 1 March 2013
Glossary
....................................................................................................................................................................................................................................
FEMA
Federal Emergency Management Agency

FSN
Factory Serial Number

FTP
File Transfer Protocol

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

GMM
GPRS Mobility Management

GPRS
General Packet Radio Service

GPS
Global Positioning System

GSM
Global System for Mobile communications

...................................................................................................................................................................................................................................
HDM
Home Device Manager

HLR
Home Location Register

HNB
Home Node B
HNBAP
Home Node B Application Part

HNLR
Home Network Local Routing

HO
Handover
HPLMN
Home Public Land Mobile Network
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
GL-5
Issue 1 March 2013
Glossary
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................................................
ID
Identification
IETF
Internet Engineering Task Force

IKE
Internet Key Exchange

IKEv2
IKE version 2
IMSI
International Mobile Subscriber Identity

IP
Internet Protocol
IPC
Iu Protocol Converter
IPsec
IP Security
IPV4
Internet Protocol Version 4

IRAT
Inter Radio Access Technology

IT
Information Technology
Iu-BC, Iu-BC'
Interfaces between the Small Cell Cluster and the Cell Broadcast Center
IuCS
Interface between the MSC and RNS

IuCS-CP
IuCS-Control Plane
IuPS
Interface between SGSN and RNS

IuPS-UP
IuPS-User Plane
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
GL-6
Issue 1 March 2013
Glossary
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................................................
KPI
Key Performance Indicator

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

LAI
Location Area Identity

LAU

LED
Light Emitting Diode

LRC
Location Report Control

LVF
Lucent VPN Firewall

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

MHz
Mega Hertz (million hertz or cycles)

MIM
Management Information Model

MM
Mobility Management
MNC
Mobile Network Code

MNO
Mobile Network Operator

MO
Managed Object
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
GL-7
Issue 1 March 2013
Glossary
....................................................................................................................................................................................................................................
MOI
Managed Object Instance

MSC
Mobile Services Switching Center

MSISDN
Mobile Station Integrated Services Digital Network

...................................................................................................................................................................................................................................
NAPT
Network Address Port Translation

NAS
Non Access Stratum

NAT
Network Address Translation

NCC
Network Country Code

NTP
Network Time Protocol

NWS
National Weather Service

...................................................................................................................................................................................................................................
OA&M
Operation, Administration & Maintenance

OAM
Operation, Administration, and Maintenance

OSS
Operations Support System

...................................................................................................................................................................................................................................
PA
Power Amplifier
PAP
Password Authentication Protocol

PCH
Paging Channel
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
GL-8
Issue 1 March 2013
Glossary
....................................................................................................................................................................................................................................
PDP
Packet Data Protocol

PLMN
Public Land Mobile Network

POK
Power on OK
PPPoE
Point-to-Point Protocol over Ethernet

PRACH
Physical Random Access Channel

PS
Packet Switched
PSC
Primary Scrambling Code

...................................................................................................................................................................................................................................
QoS
Quality Of Service
...................................................................................................................................................................................................................................
RA
Routing Area
RAB
Radio Access Bearer

RAC
Routing Area Code

RAI
Routing Area Identifier

RANAP
Radio Access Network Application Part

RAU
Routing Area Update

RF
Radio Frequency
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
GL-9
Issue 1 March 2013
Glossary
....................................................................................................................................................................................................................................
RFC
Request For Comments

RLC
Radio Link Control

RNC
Radio Network Controller

RRC
Radio Resource Control

RSCP
Received Signal Code Power

RSSI
Received Signal Strength Indicator

RTCP
Real Time Transport Control Protocol

RUA
Remote User Agent

Rx lev
Receiver, Receive side level

...................................................................................................................................................................................................................................
SABP
Service Access Broadcast Protocol

SAC
Service Area Code

SCMS
Small Cell Management System

SCTP
Stream Control Transmission Protocol

SFTP
Secure File Transfer Protocol

SGSN
Serving GPRS Support Node

SIB
System Information Block

....................................................................................................................................................................................................................................
Alcatel-Lucent SC
GL-10
Issue 1 March 2013
Glossary
....................................................................................................................................................................................................................................
SIM
Subscriber Identity Module

SON
Self-Optimizing Network
SSH
Secure SHell protocol

STRMGR
Stream Manager
...................................................................................................................................................................................................................................
TCP
Transmission Control Protocol

TCS
TeleCommunication Systems
TLV
Type Length Value

TMSI
Temporary Mobile Station Identity

TR69
Technical Report 69
TTFF
Time To First Fix

TX
Transmitter, Transmit side

...................................................................................................................................................................................................................................
UARFCN
UTRA Absolute Radio Frequency Channel Number

UDP
User Datagram Protocol

UE
User Equipment
UL
Uplink
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
GL-11
Issue 1 March 2013
Glossary
....................................................................................................................................................................................................................................
UMTS
Universal Mobile Telecommunication System

URL
Uniform Resource Locator

USIM
Universal Subscriber Identity Module

UTC
Coordinated Universal Time

UTRA
UMTS Terrestrial Radio Access

UTRAN
UMTS Terrestrial Radio Access Network

...................................................................................................................................................................................................................................
VLR
Visitor Location Register

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

WMS
Wireless Management System

...................................................................................................................................................................................................................................
XRN
Xypoint Reference Network
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
GL-12
Issue 1 March 2013
Index
Numerics
2G network listening, 3-11, 6-2

modes of operation, 6-3
3G network listening, 3-11, 5-2
functions, 5-3
PSC selection, 5-4
quiet period, 5-5
................................................................................................
A Access control
ACL mechanism, 1-2, 7-2, 15-2

parameters, 26-5
Active-Warm Standby BSR Gateway Redundancy, 26-2
AGPS, 34-5
................................................................................................
C Call admission control, 19-5
Cell broadcast services in support of CMAS, 33-2

parameters, 33-11
Cell reselection
initial neighbor list configuration, 3-2
neighbor list update process, 4-2
Configuration
auto-configuration function, 3-2
self-optimization function, 4-2
Continuous coverage self-optimization based on
admission, 28-2
parameters, 28-12
CPICH power, 28-4, 31-7
All-in-One Gateway, 27-2
................................................................................................
architecture
D DBC, 19-5
CMAS, 33-7
Assisted GPS using TCS server, 31-2
parameters, 31-10
Authentication functions, 3-2
Auto-configuration procedures, 3-2
Automatic fallback to macro network, 8-2
Automatic power amplifier shutdown, 8-2
................................................................................................
Deployment scenarios, 12-4

DSL link failure fallback, 8-2
................................................................................................
E ePLMN support for camping and notification, 14-2
parameters, 14-4
Extended ACL size for large femto groups, 24-2
................................................................................................
F Fallback after DSL link failure, 8-2
B Billing, 19-7
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
IN-1
Issue 1 March 2013
Index
....................................................................................................................................................................................................................................
Feature number
Functions
100854, 32-2
3G network listening, 5-3
101373, 20-2
................................................................................................
101681, 22-2
G GPS, 21-2
108877, 28-2
................................................................................................
114014, 26-2
H How to
116498, 35-2
119110, 29-2
119911, 31-2
123830, 34-2
157214, 30-2
comment, xvii
................................................................................................
I
Increased paging capacity for large Metro cells

deployment (same LA), 32-2
parameters, 32-12
34532, 1-2
IP address, 26-4
34533, 2-2
IP address reuse, 9-2
34535, 3-2
IPSec
34536, 4-2
34537, 5-2, 6-2
34538, 7-2
34539, 8-2
34587, 9-2
75405, 12-2
75545, 21-2
76631, 11-2
76976, 14-2
76980, 10-2
76984, 23-2
76986, 33-2
77735, 19-2
NAT traversal support, 9-2, 9-4, 11-2

................................................................................................
L LAU, 28-4, 31-7, 32-4, 33-4
LAU procedure, 1-2

................................................................................................
M Mobility management considerations, 12-9
Multi objectives joint coverage optimization, 35-2

alarms, 35-5
measurements, 35-5
parameters, 35-7
Multiple PDP Contexts, 18-2
Multiple PDP Contexts feature, 18-2
................................................................................................
78594, 25-2
79147, 18-2
80569, 15-2
84181, 27-2
92068, 24-2
FM enhancements for Metro Cells, 20-2
N NAPT
See: Network address port translation

Neighbor cell selection, 4-2
initial neighbor list configuration, 3-2
neighbor list update process, 4-2
Network address port translation, 9-4
FM enhancements for Small Cells, 20-3

....................................................................................................................................................................................................................................
Alcatel-Lucent SC
IN-2
Issue 1 March 2013
Index
....................................................................................................................................................................................................................................
Network address translation, 9-2, 9-4, 11-2
................................................................................................
Network listening feature, 5-2, 6-2
S SCTP association, 26-4
................................................................................................
O Open access, 11-2
Open access enhancements, 12-2
Security
access control, 1-2, 7-2
Self-optimization, 4-4
Deployment scenarios, 12-4
Self-optimization procedures, 4-2
mobility management considerations, 12-9
Small Cell
parameters, 12-10
access control, 1-2
UE tracking, 12-6
auto-configuration, 3-2
................................................................................................
coverage indicator, 2-2
P PM enhancements for Metro Cells, 22-2
self-optimization, 4-2
Port restricted cone NAT, 9-4

Power amplifier auto-shutdown, 8-2
Power control, 4-2
PPPoE configuration, 30-2
Prioritized open access, 19-2
billing, 19-7
call admission control, 19-5
DBC, 19-5
UE tracking, 19-4
Provisioning
Small Cell group support, 15-2

parameters, 15-6
subscriber trace, 25-2
parameters, 25-4
Sniffer function for network listening, 5-2, 6-2
static IP address, 29-2
Super LAC
restrictions, 16-9
Symmetric NAT, 9-4
................................................................................................
auto-configuration at installation, 3-2

PSC selection
................................................................................................
Q Quiet period

................................................................................................
T Tone generation during voice call set up feature, 10-2

................................................................................................
U UE based assisted GPS, 34-2
parameters, 34-6
UE measurements, 3-11
UE tracking, 12-6, 19-4
R RANAP paging, 12-8
RAU, 28-4, 31-4, 31-7, 32-4, 33-4

RAU procedure, 1-2
RF auto-configuration, 3-11
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
IN-3
Issue 1 March 2013
Index
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Alcatel-Lucent SC
IN-4
Issue 1 March 2013

Alcatel-Lucent BCR Release 4 Specific Features System Definition Specification

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Alcatel-Lucent BCR Release 4 Specific Features System Definition Specification

Enviado por

Direitos autorais:

Formatos disponíveis

Use pursuant to applicable agreements

Use pursuant to applicable agreements

Reason for reissue

New in this release ..................................................................................................................................................................... xvi

How to use this document

Prerequisites ................................................................................................................................................................................ xvii

How to order ............................................................................................................................................................................... xvii

Small Cell access restriction

Access restriction parameters ............................................................................................................................................... 1-8

Small Cell coverage indicator

Small Cell auto-configuration

Small Cell self-optimisation

Periodic self-optimization ...................................................................................................................................................... 4-4

3G network listening functions ............................................................................................................................................ 5-3

Network listening parameters ............................................................................................................................................... 5-6

2G network listening functions ............................................................................................................................................ 6-3

Access control list administration

Automatic fallback to macro in case of failure in core

Automatic fallback to macro network in case of failure parameters ...................................................................... 8-5

NAT traversal on the Small Cell .......................................................................................................................................... 9-4

Tone generation during voice call set up

Tone generation during voice call set up

Tone generation during call set up parameters

Open access enhancements

Open access enhancements

Deployment scenarios ........................................................................................................................................................... 12-4

Mobility management considerations ............................................................................................................................. 12-9

Detection of Collapsing LAI

Detection of Collapsing LAI for the Small Cell

Detection of Collapsing LAI - alarms ............................................................................................................................. 13-6

ePLMN support for camping and notification

ePLMN support for camping and notification

ePLMN support for camping and notification parameters ...................................................................................... 14-4

Small Cell group support

Small Cell group support ..................................................................................................................................................... 15-2

Super LAC overview

Super LAC functional definition

Super LAC Small Cell requirements ............................................................................................................................... 16-6

Super LAC restrictions ......................................................................................................................................................... 16-9

Dynamic LAC-SAC allocation

Dynamic LAC-SAC allocation overview ...................................................................................................................... 17-2

Multiple PDP contexts

Multiple PDP Contexts ......................................................................................................................................................... 18-2

Prioritized Open Access

Prioritized open access

UE tracking ............................................................................................................................................................................... 19-4

FM enhancements for Metro Cells

FM enhancements for Metro Cells

GPS Localization .................................................................................................................................................................... 21-2

PM enhancements for Metro Cells

PM enhancements for Metro Cells ................................................................................................................................... 22-2

Multiple PDP Contexts (3PS + CS)

Multiple PDP Contexts (3PS + CS) ................................................................................................................................. 23-2

Extended ACL size for large femto groups

Extended ACL size for large femto groups ................................................................................................................... 24-2

Active-Warm Standby Gateway Redundancy

Active-Warm Standby BSR Gateway Redundancy ................................................................................................... 26-2

All-In-One Small Cell Gateway

All-in-One Small Cell Gateway ........................................................................................................................................ 27-2

Coverage self-optimization based on admission

Continuous coverage self-optimization based on admission .................................................................................. 28-2

Static IP address ...................................................................................................................................................................... 29-2

PPPoE configuration ............................................................................................................................................................. 30-2

Assisted GPS using TCS server