9YZ056140014PGZZA - V1 - Alcatel-Lucent Small Cell Feature Activation Procedures

Use pursuant to applicable agreements
Title page
Alcatel-Lucent
Small Cell | BCR4.3
Feature Activation Procedures
9YZ-05614-0014-PGZZA
Issue 5 | April 2014
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 2014 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.
Trademark
Sun, Sun Microsystems, the Sun Logo, Solaris, and JRE are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other
countries.
Xypoint Assistance Data Server (ADS) is the trademark of TeleCommunication Systems, Inc. (TCS).
Alcatel-Lucent Proprietary
Contents
About this document

Purpose ........................................................................................................................................................................................... xix
xix
Reason for reissue ...................................................................................................................................................................... xxi

xxi
New in this release ..................................................................................................................................................................... xxi

xxi
Other changes ............................................................................................................................................................................. xxii

xxii
Intended audience ..................................................................................................................................................................... xxii

xxii
Supported systems .................................................................................................................................................................... xxii

xxii
How to use this document ..................................................................................................................................................... xxii

xxii
Conventions used .................................................................................................................................................................... xxiii

xxiii
Related information ................................................................................................................................................................ xxiii

xxiii
Document support ................................................................................................................................................................... xxiv

xxiv
Technical support ...................................................................................................................................................................... xxv

xxv
How to order ............................................................................................................................................................................... xxv

xxv
How to comment ....................................................................................................................................................................... xxv

xxv
1 IuFlex features
Overview ...................................................................................................................................................................................... 1-1

1-1
75397 - IuFlex for IuCS and IuPS ...................................................................................................................................... 1-2

1-2
107284 - IuFlex over ATM .................................................................................................................................................... 1-7

1-7
Creating IPC objects with WPS Small Cells ................................................................................................................ 1-48

1-48
IPCCLI batch file processing with WPS Small Cells ............................................................................................... 1-50
1-50
2 Security features
Overview ...................................................................................................................................................................................... 2-1

2-1
78243 - Security hardening of the BSG ............................................................................................................................ 2-2

2-2
....................................................................................................................................................................................................................................
Alcatel-Lucent SC Alcatel-Lucent Proprietary iii
9YZ-05614-0014-PGZZA BCR4.3 Use pursuant to applicable agreements
Issue 5 April 2014
Contents
....................................................................................................................................................................................................................................
114366 - SCMS security enhancements ........................................................................................................................... 2-5
2-5
121317 - Tamper Alarm ....................................................................................................................................................... 2-10

2-10
83086 - Certificate-based authentication and security for V2 HW ...................................................................... 2-14

2-14
155820 - Security enhancements via radius support on the BSR Gateway ...................................................... 2-17
2-17
3 Transport features
Overview ...................................................................................................................................................................................... 3-1

3-1
78241 - Direct tunnel ............................................................................................................................................................... 3-2

3-2
104503 - Dual stack (ANSI/ETSI) on ATM/IP .............................................................................................................. 3-5

3-5
77713 - PDP shutdown of data session .......................................................................................................................... 3-66

3-66
84791 - Real-time monitoring of backhaul bandwidth ............................................................................................. 3-70

3-70
131828 - 2 ms TTI on E-DCH ........................................................................................................................................... 3-73

3-73
122468 - Satellite backhaul ................................................................................................................................................ 3-78

3-78
4 Small Cell specific features
Overview ...................................................................................................................................................................................... 4-1

4-1
75545 - GPS localization ....................................................................................................................................................... 4-3

4-3
104564 - SCMS support of GPS localization locking ................................................................................................. 4-6

4-6
113610 - Support for assisted GPS .................................................................................................................................. 4-14

4-14
109515 - Internet breakout at CPE ................................................................................................................................... 4-17

4-17
83062 - Fault Management support of NTP server .................................................................................................... 4-22

4-22
83241 - Fault Management support of AAA ................................................................................................................ 4-28

4-28
83249 - Launch point to AAA and NTP server ........................................................................................................... 4-36

4-36
114578 - SCMS 2.4 support of SAM 7.0 ...................................................................................................................... 4-38

4-38
84181 - All-in-one BSR Gateway .................................................................................................................................... 4-41

4-41
83087 - Distributed SS7 ..................................................................................................................................................... 4-47

4-47
84990 - SCMS support of BSR Gateway ...................................................................................................................... 4-55

4-55
96373 - FM support for DNS/ToD functions ............................................................................................................... 4-59

4-59
....................................................................................................................................................................................................................................
iv Alcatel-Lucent Proprietary Alcatel-Lucent SC
Use pursuant to applicable agreements 9YZ-05614-0014-PGZZA BCR4.3
Issue 5 April 2014
Contents
....................................................................................................................................................................................................................................
120359 - HDM alarm management in WMS Small Cells for Small Cell ........................................................ 4-62
4-62
119109 - Meinberg NTP integration ................................................................................................................................ 4-65

4-65
117813 - Small Cell Access Point capacity licensing ............................................................................................... 4-68

4-68
114014 - Active-Warm standby BSR Gateway redundancy ................................................................................... 4-72

4-72
120353 - RTCP for IuCSoIP ............................................................................................................................................... 4-79

4-79
78594 - Small Cells network support for End-to-End call subscriber trace ..................................................... 4-82
4-82
119110 - Static IP address ................................................................................................................................................... 4-90

4-90
157214 - PPPoE configuration .......................................................................................................................................... 4-94

4-94
119911 - Assisted GPS using proprietary TCS solution ........................................................................................... 4-98

4-98
123830 - UE-based Assisted GPS .................................................................................................................................. 4-105

4-105
125544 - AMR frame concatenation with preemption ........................................................................................... 4-110

4-110
158467 - 32 PS user capacity for V2 Enterprise and Metro AP ......................................................................... 4-121

4-121
76986 - Cell broadcast services in support of CMAS ............................................................................................ 4-124

4-124
124168 - DPDK support on BSR Gateway ................................................................................................................ 4-130

4-130
117826 - Multiple Operator Core Network ................................................................................................................ 4-133

4-133
5 Services features
Overview ...................................................................................................................................................................................... 5-1

5-1
83021 - Presence API .............................................................................................................................................................. 5-2

5-2
75399 - Home network local routing .............................................................................................................................. 5-11

5-11
76974 - Enhanced PM processing for BSG counters ................................................................................................ 5-16

5-16
114380 - DHCP options (60, 125, 43) ............................................................................................................................ 5-21

5-21
89552 - Network overload avoidance ............................................................................................................................. 5-25

5-25
6 Metro Small Cells features
Overview ...................................................................................................................................................................................... 6-1

6-1
101681 - PM enhancements for Metro Small Cells ..................................................................................................... 6-2

6-2
101373 - FM enhancements for Metro Small Cells ..................................................................................................... 6-6

6-6
....................................................................................................................................................................................................................................
Alcatel-Lucent SC Alcatel-Lucent Proprietary v
Issue 5 April 2014
Contents
....................................................................................................................................................................................................................................
100854 - Optimized paging for large Metro cells deployments ............................................................................ 6-12
6-12
92068 - ACL extension for large Small Cell Groups ................................................................................................ 6-18
6-18
111039 - Extended range cell ............................................................................................................................................. 6-25

6-25
7 Radio resource management features
Overview ...................................................................................................................................................................................... 7-1

7-1
78229 - Location lock on 2G RF fingerprint .................................................................................................................. 7-2

7-2
114997 - 2G MCC-based NLL on V1 boards (HiLo) .................................................................................................. 7-6

7-6
119860 - 3G sniffing capability in 2100/850 MHz .................................................................................................... 7-13

7-13
76985 - Automatic carrier selection ................................................................................................................................. 7-16

7-16
116495 - UL interferences management based on Tx power update ................................................................... 7-23

7-23
116496 - 64QAM for HSDPA ........................................................................................................................................... 7-28

7-28
108877 - Coverage self-optimization based on admission ...................................................................................... 7-32

7-32
114174 - UMTS Small Cell to LTE cell reselection .................................................................................................. 7-38

7-38
116498 - Multi-objectives joint coverage optimization ........................................................................................... 7-44

7-44
170891 - Neighbor list optimization based on UE measurements ....................................................................... 7-48

7-48
170695 - Change of Service Area Location Reporting ............................................................................................. 7-52

7-52
171355 - Coordinated self optimization in groups ..................................................................................................... 7-57

7-57
8 Mobility features
Overview ...................................................................................................................................................................................... 8-1

8-1
100856 - Intra-frequency Small Cell to 3G Macro MAHO for CS calls ............................................................. 8-2
8-2
100857 - Intra-frequency Small Cell to 3G Macro MAHO for PS and CS+PS calls ...................................... 8-6
8-6
75387 - UE assisted Small Cell to Macro handover .................................................................................................. 8-10

8-10
75386 - Cell change order ................................................................................................................................................... 8-15

8-15
100888 - Inter-frequency Small Cell to 3G Macro handover for PS and CS+PS calls ................................ 8-19
8-19
101684 - 3G Macro to Small Cell handover for PS and CS+PS calls ................................................................ 8-24
8-24
172248 - Release PS during SIM bearer (CS+PS) handover ................................................................................. 8-31

8-31
....................................................................................................................................................................................................................................
vi Alcatel-Lucent Proprietary Alcatel-Lucent SC
Issue 5 April 2014
Contents
....................................................................................................................................................................................................................................
9 Common Configuration Procedures
Overview ...................................................................................................................................................................................... 9-1

9-1
IPC configuration with WPS Small Cells ........................................................................................................................ 9-2

9-2
BSG configuration with WPS Small Cells ...................................................................................................................... 9-6

9-6
Small Cell attributes configuration with WPS Small Cells ....................................................................................... 9-8
9-8
Glossary
Index
....................................................................................................................................................................................................................................
Alcatel-Lucent SC Alcatel-Lucent Proprietary vii
Issue 5 April 2014
Contents
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
viii Alcatel-Lucent Proprietary Alcatel-Lucent SC
Issue 5 April 2014
List of tables
1-1 FGW<DN;> ................................................................................................................................................................. 1-4

1-4
1-2 BSG:1 ............................................................................................................................................................................. 1-4

1-4
1-3 FGWConfig ................................................................................................................................................................. 1-5

1-5
1-4 FGW <DN;> ............................................................................................................................................................. 1-10

1-10
1-5 BSG:1 .......................................................................................................................................................................... 1-10

1-10
1-6 LIPC ............................................................................................................................................................................. 1-11

1-11
1-7 LIPC::SS7Stack::SS7LinkSet ............................................................................................................................. 1-11
1-8 LIPC::SS7Stack::PeerIPSP .................................................................................................................................. 1-12
1-9 LIPC::IuCSIP ........................................................................................................................................................... 1-13

1-13
1-10 LIPC::IuPSIP ............................................................................................................................................................ 1-13

1-13
1-11 BSRCluster Profile ................................................................................................................................................. 1-14

1-14
1-12 FGWConfig ............................................................................................................................................................... 1-14

1-14
1-13 LIPC=1 ........................................................................................................................................................................ 1-14

1-14
1-14 FGW<DN;> .............................................................................................................................................................. 1-14

1-14
1-15 BSG:1 .......................................................................................................................................................................... 1-15

1-15
1-16 LIPC=1 ........................................................................................................................................................................ 1-15

1-15
1-17 FGWConfig ............................................................................................................................................................... 1-16

1-16
1-18 LIPC=1 ........................................................................................................................................................................ 1-16

1-16
2-1 SupportedAlarmsInrealTime ............................................................................................................................... 2-11
2-2 BSR .............................................................................................................................................................................. 2-11

2-11
2-3 BSR .............................................................................................................................................................................. 2-12

2-12
2-4 BSR .............................................................................................................................................................................. 2-16

2-16
2-5 /FGW:<DN>/AAA:1 ............................................................................................................................................. 2-21

2-21
....................................................................................................................................................................................................................................
Alcatel-Lucent SC Alcatel-Lucent Proprietary ix
Issue 5 April 2014
List of tables
....................................................................................................................................................................................................................................
2-6 /FGW:<DN>/AAA:1/AAAremoteAAAServer <instance> ..................................................................... 2-21
2-7 /FGW:<DN>/AAA:1/AAAsecurityGateway <instance> ......................................................................... 2-22
2-8 BSR .............................................................................................................................................................................. 2-23

2-23
2-9 /FGW:<DN>/AAA:1 ............................................................................................................................................. 2-23

2-23
3-1 IuCS: .............................................................................................................................................................................. 3-8

3-8
3-2 IuPS: ............................................................................................................................................................................... 3-8

3-8
3-3 LIPC::SS7Stack::SS7LinkSet ............................................................................................................................... 3-9
3-4 LIPC::SS7Stack::PeerIPSP .................................................................................................................................. 3-10
3-5 LIPC::IuCSIP ............................................................................................................................................................ 3-11

3-11
3-6 LIPC::IuPSIP ............................................................................................................................................................ 3-11

3-11
3-7 BSR .............................................................................................................................................................................. 3-67

3-67
3-8 BSR .............................................................................................................................................................................. 3-68

3-68
3-9 BSG .............................................................................................................................................................................. 3-70

3-70
3-10 BSR .............................................................................................................................................................................. 3-71

3-71
3-11 BSG .............................................................................................................................................................................. 3-71

3-71
3-12 BSR .............................................................................................................................................................................. 3-71

3-71
3-13 BSR .............................................................................................................................................................................. 3-74

3-74
3-14 EDCH .......................................................................................................................................................................... 3-75

3-75
3-15 BSR .............................................................................................................................................................................. 3-76

3-76
3-16 Feature acceptance criteria .................................................................................................................................. 3-78

3-78
3-17 BSR .............................................................................................................................................................................. 3-81

3-81
3-18 BSR .............................................................................................................................................................................. 3-82

3-82
4-1 GPS ................................................................................................................................................................................. 4-4

4-4
4-2 GPS ................................................................................................................................................................................. 4-4

4-4
4-3 /FemtoCluster:<DN>/Femto<instance>: .......................................................................................................... 4-7
4-4 /Profile:<DN>/BSRProfile:<DN>/GPS<instance>: ..................................................................................... 4-8
4-5 Profile:<DN>/BSRProfile:<DN>/GPS<instance>: .................................................................................... 4-12
....................................................................................................................................................................................................................................
x Alcatel-Lucent Proprietary Alcatel-Lucent SC
Issue 5 April 2014
List of tables
....................................................................................................................................................................................................................................
4-6 /FemtoCluster:<DN>/BSRClusterProfile:<DN>/AGPS<instance> .................................................... 4-15
4-7 enableAGPS .............................................................................................................................................................. 4-15

4-15
4-8 BSR .............................................................................................................................................................................. 4-18

4-18
4-9 BSR: localRoutingAPN ........................................................................................................................................ 4-19

4-19
4-10 BSR: localRoutingPassNetworkList ................................................................................................................ 4-20
4-11 BSR .............................................................................................................................................................................. 4-20

4-20
4-12 <FGW<DN;BVG:1>> .......................................................................................................................................... 4-44

4-44
4-13 <FGW<DN;BPG:1>> ........................................................................................................................................... 4-44

4-44
4-14 <BSRCluster Profile> ............................................................................................................................................ 4-45

4-45
4-15 <FGW<DN;BVG:1>> .......................................................................................................................................... 4-45

4-45
4-16 <FGW<DN;BPG:1>> ........................................................................................................................................... 4-45

4-45
4-17 <LIPC::SS7Stack> ................................................................................................................................................. 4-52

4-52
4-18 <LIPC::SS7Stack> ................................................................................................................................................. 4-52

4-52
4-19 <LIPC::SS7Stack> ................................................................................................................................................. 4-53

4-53
4-20 <LIPC::SS7Stack> ................................................................................................................................................. 4-53

4-53
4-21 ........................................................................................................................................................................................ 4-69

4-69
4-22 ........................................................................................................................................................................................ 4-70

4-70
4-23 ........................................................................................................................................................................................ 4-74

4-74
4-24 ........................................................................................................................................................................................ 4-76

4-76
4-25 BSR .............................................................................................................................................................................. 4-77

4-77
4-26 BSR::IuCSUplane::enableRtcp ......................................................................................................................... 4-80
4-27 BSR::IuCSUplane::enableRtcp ......................................................................................................................... 4-80
4-28 </FGW:<DN>/ItfFgw:1/SubscriberTraceConfig:1> ................................................................................ 4-84
4-29 </FGW:<DN>/ItfFgw:1/SubscriberTraceConfig:1 / SubscriberTrace:1> ........................................ 4-84
4-30 <IPC/1 : LIPC/1 : SubscriberTraceConfig:1 > ............................................................................................ 4-85
4-32 <Femto <dn> : BSRProfile : SubscriberTraceConfig/1 > ...................................................................... 4-87
....................................................................................................................................................................................................................................
Alcatel-Lucent SC Alcatel-Lucent Proprietary xi
Issue 5 April 2014
List of tables
....................................................................................................................................................................................................................................
4-33 </FGW:<DN>/ItfFgw:1/SubscriberTraceConfig:1> ................................................................................ 4-88
4-35 <Femto <dn> : BSRProfile : SubscriberTraceConfig/1> ........................................................................ 4-88
4-36 AGPSProxy ............................................................................................................................................................. 4-101

4-101
4-37 AGPS ........................................................................................................................................................................ 4-102

4-102
4-38 GPS ............................................................................................................................................................................ 4-103

4-103
4-39 BSR ............................................................................................................................................................................ 4-107

4-107
4-40 AGPS ........................................................................................................................................................................ 4-108

4-108
4-41 BSR ............................................................................................................................................................................ 4-108

4-108
4-42 BSR ............................................................................................................................................................................ 4-117

4-117
4-43 FGW .......................................................................................................................................................................... 4-117

4-117
4-44 FGW .......................................................................................................................................................................... 4-118

4-118
4-45 BSR ............................................................................................................................................................................ 4-119

4-119
4-46 LCell .......................................................................................................................................................................... 4-122

4-122
4-47 LCell .......................................................................................................................................................................... 4-122

4-122
4-48 BSG ........................................................................................................................................................................... 4-127

4-127
4-49 BSR ............................................................................................................................................................................ 4-127

4-127
4-50 BSRProfile .............................................................................................................................................................. 4-127

4-127
4-51 BSRProfile::sparePara1 ...................................................................................................................................... 4-131

4-131
4-52 BSRProfile::sparePara1 ...................................................................................................................................... 4-132

4-132
4-53 BSR ............................................................................................................................................................................ 4-137

4-137
4-54 BSR ............................................................................................................................................................................ 4-143

4-143
4-55 BSR ............................................................................................................................................................................ 4-143

4-143
5-1 FGW:<DN>/BSG:<instance>/Presence:<instance 1 to 10> ...................................................................... 5-3
5-2 /FGW:<DN>/BSG<instance>/Presence:<instance>/PresenceeventMapping:<instance 1 to 13>

................................................................................................................................................................................. 5-45-4
5-4
5-3 FGW:<DN> ................................................................................................................................................................. 5-5

5-5
....................................................................................................................................................................................................................................
xii Alcatel-Lucent Proprietary Alcatel-Lucent SC
Issue 5 April 2014
List of tables
....................................................................................................................................................................................................................................
5-4 /FGW:<DN>/BSG:<instance> ............................................................................................................................. 5-5
5-5 PresenceNetwork/FemtoCluster:<cluster id>/Femto:<id>/Presence ...................................................... 5-6
5-6 Network/FemtoCluster:<cluster
id>/Femto:<id>/PresenceHighAccuracyMonitoredDetectionProfile .................................................. 5-7
5-7 Network/FemtoCluster:<cluster id>/Femto:<id> .......................................................................................... 5-7
5-8 Network/Profile:<profile name>/BSRProfile:<id> ....................................................................................... 5-8
5-9 /FGW:<DN> ................................................................................................................................................................ 5-8

5-8
5-10 Network/FemtoCluster:<cluster id>/Femto:<id> .......................................................................................... 5-9
5-11 BSR .............................................................................................................................................................................. 5-11

5-11
5-12 BSR:passHomeNetworkLocalRoutingNetworkList .................................................................................. 5-13
5-13 BSR .............................................................................................................................................................................. 5-14

5-14
5-14 BSR .............................................................................................................................................................................. 5-23

5-23
5-15 BSR .............................................................................................................................................................................. 5-23

5-23
5-16 BSG: ............................................................................................................................................................................. 5-27

5-27
5-17 BSG: ............................................................................................................................................................................. 5-27

5-27
6-1 <BSR:PM> ................................................................................................................................................................... 6-3

6-3
6-2 <BSR:PM> ................................................................................................................................................................... 6-4

6-4
6-3 <BSR> ........................................................................................................................................................................... 6-8

6-8
6-4 <FGW:BSG> ............................................................................................................................................................... 6-9

6-9
6-5 <BSR> ......................................................................................................................................................................... 6-10

6-10
6-6 <FGW:BSG> ............................................................................................................................................................ 6-10

6-10
6-7 <BSR> ......................................................................................................................................................................... 6-10

6-10
6-8 BSR .............................................................................................................................................................................. 6-13

6-13
6-9 BSR .............................................................................................................................................................................. 6-15

6-15
6-10 BSR .............................................................................................................................................................................. 6-21

6-21
6-11 FGW ............................................................................................................................................................................. 6-21

6-21
6-12 FGW ............................................................................................................................................................................. 6-22

6-22
....................................................................................................................................................................................................................................
Alcatel-Lucent SC Alcatel-Lucent Proprietary xiii
Issue 5 April 2014
List of tables
....................................................................................................................................................................................................................................
6-13 BSR .............................................................................................................................................................................. 6-23
6-23
6-14 LCell ............................................................................................................................................................................ 6-26

6-26
6-15 BSR .............................................................................................................................................................................. 6-26

6-26
6-16 BSR::AutoConfigPW ............................................................................................................................................ 6-26

6-26
6-17 BSR .............................................................................................................................................................................. 6-27

6-27
7-1 LCELL ........................................................................................................................................................................... 7-4

7-4
7-2 BSR ................................................................................................................................................................................. 7-4

7-4
7-3 BSR ................................................................................................................................................................................. 7-8

7-8
7-4 LCELL ........................................................................................................................................................................... 7-9

7-9
7-5 LCell: ........................................................................................................................................................................... 7-14

7-14
7-6 LCell: ........................................................................................................................................................................... 7-14

7-14
7-7 LCell ............................................................................................................................................................................ 7-17

7-17
7-8 LCell ............................................................................................................................................................................ 7-21

7-21
7-9 BSRProfile ................................................................................................................................................................. 7-24

7-24
7-10 BSRProfile ................................................................................................................................................................. 7-26

7-26
7-11 HSDPA ........................................................................................................................................................................ 7-29

7-29
7-12 LCell ............................................................................................................................................................................ 7-29

7-29
7-13 HSDPA ........................................................................................................................................................................ 7-30

7-30
7-14 BSR .............................................................................................................................................................................. 7-34

7-34
7-15 AutoConfigPW ....................................................................................................................................................... 7-34

7-34
7-16 AutoConfigPW ....................................................................................................................................................... 7-35

7-35
7-17 BSRProfile:LCell .................................................................................................................................................... 7-39

7-39
7-18 BSRProfile:LCell .................................................................................................................................................... 7-42

7-42
7-19 BSR .............................................................................................................................................................................. 7-45

7-45
7-20 BSR .............................................................................................................................................................................. 7-46

7-46
7-21 sparepara35 ................................................................................................................................................................ 7-49

7-49
7-22 RFTrace ...................................................................................................................................................................... 7-50

7-50
....................................................................................................................................................................................................................................
xiv Alcatel-Lucent Proprietary Alcatel-Lucent SC
Issue 5 April 2014
List of tables
....................................................................................................................................................................................................................................
7-23 BSR .............................................................................................................................................................................. 7-53
7-53
7-24 BSRProfile::sparePara4 ........................................................................................................................................ 7-54

7-54
7-25 BSR .............................................................................................................................................................................. 7-55

7-55
7-26 BSR::sparePara3 ...................................................................................................................................................... 7-59

7-59
7-27 BSR::sparePara3 ...................................................................................................................................................... 7-60

7-60
8-1 BSRProfile ................................................................................................................................................................... 8-3

8-3
8-2 LCell (BSRProfile-LCell/1) ................................................................................................................................... 8-3

8-3
8-3 BSRProfile ................................................................................................................................................................... 8-3

8-3
8-4 BSRProfile ................................................................................................................................................................... 8-4

8-4

8-4
8-6 BSRProfile ................................................................................................................................................................... 8-6

8-6

8-7
8-8 BSRProfile ................................................................................................................................................................... 8-7

8-7
8-9 BSRProfile ................................................................................................................................................................... 8-8

8-8
8-10 BSRProfile ................................................................................................................................................................... 8-8

8-8

8-8
8-12 BSRProfile ................................................................................................................................................................. 8-11

8-11
8-13 BSRProfile ................................................................................................................................................................. 8-13

8-13
8-14 BSRProfile ................................................................................................................................................................. 8-16

8-16
8-15 BSRProfile ................................................................................................................................................................. 8-17

8-17
8-16 LCell(BSRProfile-LCell/1) ................................................................................................................................. 8-20

8-20
8-17 HO(BSRProfile-HO/1) .......................................................................................................................................... 8-21
8-18 LCell(BSRProfile-LCell/1) ................................................................................................................................. 8-22

8-22
8-19 BSR::sparepara31 ................................................................................................................................................... 8-32

8-32
8-20 BSR::sparepara 31 .................................................................................................................................................. 8-33

8-33
....................................................................................................................................................................................................................................
Alcatel-Lucent SC Alcatel-Lucent Proprietary xv
Issue 5 April 2014
List of tables
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
xvi Alcatel-Lucent Proprietary Alcatel-Lucent SC
Issue 5 April 2014
List of figures
1-1 To connect ATM interfaces on 4 MSCs and 3 SGSNs to one BSG ........................................................ 1-7
7-1 Cell reselection ......................................................................................................................................................... 7-38

7-38
....................................................................................................................................................................................................................................
Alcatel-Lucent SC Alcatel-Lucent Proprietary xvii
Issue 5 April 2014
List of figures
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
xviii Alcatel-Lucent Proprietary Alcatel-Lucent SC
Issue 5 April 2014
About this document
About this document
Purpose
The purpose of this information product is to provide activation/deactivation procedures,
corresponding impact on the network elements, and related information for the following:
BCR 4 features:
UE for Assisted GPS (123830)
Multi objectives joint coverage optimization (116498)
UMTS Small Cell to LTE cell reselection (114174)
Cell Broadcast Services in support of CMAS (76986)
Neighbour list optimization based on UE measurements (170891)
Release PS during SIM bearer (CS+PS) handover (172248)
DPDK support on BSR Gateway (124168)
Change of SAI reporting (170695)
Coordinated self optimization in groups (171355)
Multiple Operator Core Network (117826)
3.0 features:
Cell change order (75386)
UE assisted Small Cell to Macro handover (75387)
Automatic carrier selection (76985)
Small Cells network support for end-to-end call subscriber trace (78594)
Certificate-based authentication and security for V2 HW (83086)
All-in-one BSR Gateway (84181)
ACL extension for large Small Cell Groups (92068)
Optimized paging for large Metro cells deployments (100854)
Intra-frequency Small Cell to 3G Macro MAHO for CS calls (100856)
Intra-frequency Small Cell to 3G Macro MAHO for PS and CS+PS calls (100857)
Inter-frequency Small Cell to 3G Macro handover for PS and CS+PS calls
(100888)
...................................................................................................................................................................................................................................
Alcatel-Lucent SC Alcatel-Lucent Proprietary xix
Issue 5 April 2014
About this document
....................................................................................................................................................................................................................................
Extended cell range (111039)
Active-Warm standby BSR Gateway redundancy (114014)
UL interferences management based on Tx power update (116495)
64QAM for HSDPA (116496)
Small Cell Access Point Capacity Licensing (117813)
Meinberg NTP integration (119109)
3G sniffing capability in 2100/850 MHz (119860)
RTCP for IuCSoIP (120353)
HDM alarm management for WMS Small Cells (120359)
Tamper alarm (121317)
Static IP address (119110)
PPPoE configuration (157214)
Assisted GPS using proprietary TCS solution (119911)
Coverage self-optimization based on admission (108877)
3G Macro to Small Cell handover for PS and CS+PS calls (101684)
AMR frame concatenation with preemption (125544)
2 ms TTI on E-DCH (131828)
32 PS user capacity for V2 Enterprise and Metro AP (158467)
Security enhancements via radius support on the BSR Gateway (155820)
Satellite backhaul (122468)
2.4 features:
IuFlex for IuCS and IuPS (75397)
Home network local routing (75399)
GPS localization (75545)
Enhanced PM processing for BSG counters (76974)
PDP shutdown of data session (77713)
Location lock on 2G RF fingerprint (78229)
Direct tunnel (78241)
Security hardening of the BSG (78243)
Presence API (83021)
FM support of NTP server (83062)
Distributed SS7 (83087)
FM support of AAA (83241)
Launch point to AAA and NTP server (83249)
Real-time monitoring of backhaul bandwidth (84791)
....................................................................................................................................................................................................................................
xx Alcatel-Lucent Proprietary Alcatel-Lucent SC
Issue 5 April 2014
About this document
....................................................................................................................................................................................................................................
SCMS support of BSR Gateway (84990)
Network overload avoidance (89552)
FM support for DNS/ToD functions (96373)
CM enhancements for operator managed Small Cells (100902)
FM enhancements for Metro Small Cells (101373)
PM enhancements for Metro Small Cells (101681)
Dual Stack (ANSI/ETSI) on ATM/IP (104503)
SCMS support of GPS Localization Locking (104564)
IuFlex over ATM (107284)
Internet breakout at CPE (109515)
Support for assisted GPS (113610)
SCMS security enhancements (114366)
DHCP options (60,125,43) (114380)
SCMS 2.4 support of SAM 7.0 (114578)
2G MCC-based NLL on V1 boards (HiLo) (114997)
Reason for reissue

The reissue reasons are:
Issue number Issue date Reason for reissue

5 April 2014 Standard
4 February 2014 Standard
3 November 2013 Standard
2 September 2013 Standard
1 September 2013 Standard
New in this release

Features
The feature activation procedures for the following features have been added:
Multiple Operator Core Network (117826), see 117826 - Multiple Operator Core
Network (p. 4-133)
UE for Assisted GPS (123830), see 123830 - UE-based Assisted GPS (p. 4-105).
Multi objectives joint coverage optimization (116498), see 116498 - Multi-objectives
joint coverage optimization (p. 7-44).
....................................................................................................................................................................................................................................
Alcatel-Lucent SC Alcatel-Lucent Proprietary xxi
Issue 5 April 2014
About this document
....................................................................................................................................................................................................................................
UMTS Small Cell to LTE cell reselection (114174), see 114174 - UMTS Small Cell
to LTE cell reselection (p. 7-38).
Cell Broadcast Services in support of CMAS (76986), see 76986 - Cell broadcast
services in support of CMAS (p. 4-124).
Neighbour list optimization based on UE measurements (170891), see 170891 -
Neighbor list optimization based on UE measurements (p. 7-48).
Release PS during SIM bearer (CS+PS) handover (172248), see 172248 - Release PS
during SIM bearer (CS+PS) handover (p. 8-31).
DPDK support on BSR Gateway (124168), see 124168 - DPDK support on BSR
Gateway (p. 4-130).
Change of SAI reporting (170695), see 170695 - Change of Service Area Location
Reporting (p. 7-52).
Coordinated self optimization in groups (171355), see 171355 - Coordinated self
optimization in groups (p. 7-57).
Other changes
The following features are modified in Issue 5:
Added the procedure to add PPID in IPSec router GUI in the feature: Cell Broadcast
Services in support of CMAS (76986), see 76986 - Cell broadcast services in
support of CMAS (p. 4-124).
Modified the feature activation procedure in the feature: Multiple Operator Core
Network (117826), see 117826 - Multiple Operator Core Network (p. 4-133).
Added the parameter: disableAutoConfLCellUnlock in the feature: Coordinated
self optimization in groups (171355), see 171355 - Coordinated self optimization in
groups (p. 7-57).
Modified the following attributes in 122468 - Satellite backhaul (p. 3-78):
Default value of attribute maximumAllowedNtpJitter as 40000
Maximum jitter value 40 ms
And a note stating that the frequency accuracy will be +/- 250 ppb.
Intended audience
The document is intended for configuration management personnel.
Supported systems
This document applies to Alcatel-Lucent Small Cell system release BCR4.3.
How to use this document

No specific recommendation applies regarding the way readers must read this document.
....................................................................................................................................................................................................................................
xxii Alcatel-Lucent Proprietary Alcatel-Lucent SC
Issue 5 April 2014
About this document
....................................................................................................................................................................................................................................
Conventions used
Vocabulary conventions
In this document, BSR Gateway may be referred to as BSG or FGW. All these terms refer
to Alcatel-Lucent 9365 BSR Gateway.
Typographical conventions
The following conventions are used in this document:
Graphical representation Description

Emphasis Emphasizes a specific word or phrase.
Command-syntax Indicates the exact command format that must
be entered at the command-line interface.
Output Indicates output that appears on the screen.
GUI Indicates the following for a graphical user
interface:
The name of a window.
The actions that must be taken on a
pull-down menu.
Path Indicates a directory path or a file name.
Attribute Indicates that this word is a GUI or CLI
attribute (parameter).
<> Indicates that the text between the < > signs
must be determined and filled in by the user.
Related information
For information on subjects related to the content of this document, refer to the
documents listed in the following table:
Refer to this document At this location For more information on

Alcatel-Lucent 9365 BSR http://support.alcatel- BSR Signaling Gateway
Gateway - Operations, lucent.com (BSG) configuration
Administration, Maintenance
and Provisioning,
9YZ-05614-0401-REZZA
....................................................................................................................................................................................................................................
Alcatel-Lucent SC Alcatel-Lucent Proprietary xxiii
Issue 5 April 2014
About this document
....................................................................................................................................................................................................................................
Refer to this document At this location For more information on

Alcatel-Lucent Iu Protocol http://support.alcatel- Alcatel-Lucent Iu Protocol
Converter - Operations, lucent.com Converter (IPC)
Administration and configuration
Maintenance,
9YZ-05614-0500-REZZA
Alcatel-Lucent Small Cell - http://support.alcatel- Small Cell IuFlex features
IuFlex and Customized IuFlex lucent.com
System Definition
Specification,
9YZ-05614-0015-DSZZA
Alcatel-Lucent Small Cell - http://support.alcatel- Small Cell security features
Security System Definition lucent.com
Specification,
9YZ-05614-0007-DSZZA
Alcatel-Lucent Small Cell - http://support.alcatel- Small Cell transport features
Transport System Definition lucent.com
Specification,
9YZ-05614-0006-DSZZA
Alcatel-Lucent Small Cell - http://support.alcatel- Small Cell specific features
Specific Features System lucent.com
Definition Specification,
9YZ-05614-0005-DSZZA
Alcatel-Lucent Small Cell - http://support.alcatel- Small Cell, services features
Services System Definition lucent.com
Specification,
9YZ-05614-0001-DSZZA
Document support
For support in using this or any other Alcatel-Lucent document, contact Alcatel-Lucent at
the following telephone numbers.
From United States
If you are using a landline, a cellular phone or VOIP, dial this number:
1-888-582-3688
From other countries
If you are using a cellular phone or VOIP, dial this number: +1-630-224-2485
If you are using a landline (phone without a plus [+] character), replace the plus sign
with your country's exit code. Dial this number: Exit code for the country of origin
-1-630-224-2485. See the country-specific exit codes listed here.
....................................................................................................................................................................................................................................
xxiv Alcatel-Lucent Proprietary Alcatel-Lucent SC
Issue 5 April 2014
About this document
....................................................................................................................................................................................................................................
These numbers apply for document support only. Please see the section Technical
support for details about product hardware, software, and technical support.
Technical support
For technical support, contact your local Alcatel-Lucent customer support team. See the
Alcatel-Lucent Support web site (http://www.alcatel-lucent.com/support/) for contact
information.
How to order
To order Alcatel-Lucent documents, contact your local sales representative or use Online
Customer Support (OLCS) (http://support.alcatel-lucent.com).
How to comment
To comment on this document, go to the Online Comment Form (http://infodoc.alcatel-
lucent.com/comments/) or e-mail your comments to the Comments Hotline
(comments@alcatel-lucent.com).
....................................................................................................................................................................................................................................
Alcatel-Lucent SC Alcatel-Lucent Proprietary xxv
Issue 5 April 2014
About this document
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
xxvi Alcatel-Lucent Proprietary Alcatel-Lucent SC
Issue 5 April 2014
1 IuFlex features
1
Overview
Purpose
This chapter describes the activation/deactivation procedure for the Small Cell IuFlex
features.
Contents
75397 - IuFlex for IuCS and IuPS 1-2

107284 - IuFlex over ATM 1-7
Creating IPC objects with WPS Small Cells 1-48
IPCCLI batch file processing with WPS Small Cells 1-50
...................................................................................................................................................................................................................................
Alcatel-Lucent SC Alcatel-Lucent Proprietary 1-1
Issue 5 April 2014
IuFlex features 75397 - IuFlex for IuCS and IuPS
....................................................................................................................................................................................................................................
75397 - IuFlex for IuCS and IuPS

Overview
The IuFlex feature allows the Small Cell Cluster to connect to multiple core network
nodes. This feature enables a Small Cell Cluster overcome strict conventional network
hierarchy, where it was allowed to be connected to only one CN node. The IuFlex feature
provides more flexibility to the network and increases its performance, capacity, and
scalability.
The IuFlex feature can be configured with BSG, in the following two variations:
Standardized (NRI-based) IuFlex which requires support from CN.
Customized (LAI/RAI based) IuFlex which does not require any support from CN.
IPC does not support the standard IuFlex feature. It remains transparent to BSG and
Mobile Switching Center (MSC).
Small Cells are connected to the BSG through Iu interfaces carrying IuCS and IuPS
RANAP signaling messages. On establishing an Iu connection, the BSG selects the Iu
interface to the core network node through the IPC, based on routing information
provided by the Small Cells.
The core network node selection is done in the BSG with the help of a Network Node
Selection Function (NNSF) algorithm.
The IuFlex feature introduces the concept of pool-areas. Each pool-area comprises of all
Location Areas (LAs)/ Routing Areas (RAs) of one or more RNCs that are served by a
certain group of CN nodes in parallel.
One Small Cell Cluster can support multiple sets of LAs and RAs, each of which has
associated groups of CN nodes. Each of these sets of LAs and RAs is named a region.
Each region provides services for a set of Location Areas, or Routing Areas in the PS
Domain. Each region has an associated set of Iu interfaces to MSCs or Serving GPRS
Support Nodes (SGSNs). An Iu interface can be associated with multiple regions.
Purpose
This topic describes the activation and deactivation procedures for IuFlex for IuCS and
IuPS (75397) feature.
Related information
Note: The same procedures must be used for activating and deactivating the
Customised IuFlex (77712) feature.
....................................................................................................................................................................................................................................
1-2 Alcatel-Lucent Proprietary Alcatel-Lucent SC
Issue 5 April 2014
....................................................................................................................................................................................................................................
Before you begin
Before configuring, ensure that:
The communication between the SCMS and the BSG is operational.
The SSH key is exchanged to enable a password-less sftp communication between the
SCMS and the BSG. The communication is to download the Small Cell related
information files to the BSG.
The Small Cell has the correct setting in the ClusterProfile, else BulkCM download is
required.
Feature activation procedure

To configure the IuFlex feature with WPS Small Cells
Perform the following steps to configure the IuFlex for IPC feature with WPS Small
Cells:
...................................................................................................................................................................................................
1 Execute the steps in Creating IPC objects with WPS Small Cells (p. 1-48)
...................................................................................................................................................................................................
2 Navigate to LIPC MO in WPS Small Cells. Set attribute enableIuFlex as True

...................................................................................................................................................................................................
3 Execute the steps in IPCCLI batch file processing with WPS Small Cells (p. 1-50).
E...................................................................................................................................................................................................
N D O F S T E P S
Feature Deactivation Procedure

To disable the IuFlex feature with WPS Small Cells
Perform the following steps to configure the IuFlex for IPC feature with WPS Small
Cells:
...................................................................................................................................................................................................
1 Execute the steps in Creating IPC objects with WPS Small Cells (p. 1-48).
...................................................................................................................................................................................................
2 Navigate to LIPC MO in WPS Small Cells. Set attribute enableIuFlex as False.

...................................................................................................................................................................................................
3 Execute the steps inIPCCLI batch file processing with WPS Small Cells (p. 1-50).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Managed objects involved in feature deactivation
The following objects are involved for deactivation of IuFlex in BSG:
Table 1-1 FGW<DN;>
Parameter name Description Value Command Additional comment
activateIuFlexCS This attribute is used True set { Constraint validation

to enable and disable activateIuFlexCS fails if multiple IuCS
the IuFlex support =True}; instances are added
for IuCS interface. get {
without enabling this
activateIuFlexCS};
attribute.
to get the value of the
attribute.
activateIuFlexPS This attribute is used True set { Constraint validation
to enable and disable activateIuFlexPS fails if multiple IuCS
the IuFlex support =True}; instances are added
for IuPS interface. get {
activateIuFlexPS}
attribute.
to verify the attribute
value.
Table 1-2 BSG:1
Parameter name Description Value Command Additional

comment
defaultCsRegionRef This parameter must FGW=530601, set { The configuration of

refer to a default BSG=1,CsRegion=1 defaultCsRegion the default region
CsRegion. If there is Ref="FGW=530601, reference is
failure in routing a BSG=1,CsRegion= dynamic.
call to any of the 1}; Depending upon the
configured deployment
CsRegions, then this scenario a default
reference is used as region is selected.
default region to
route the calls.
defaultPsRegionRef This parameter must FGW=530601, set The configuration of
refer to a default BSG=1,PsRegion=1 {defaultPsRegion the default region
PsRegion. If there is Ref="FGW=530601, reference is
failure in routing a BSG=1,PsRegion= dynamic.
call to any of the 1"}; Depending upon the
configured deployment
PsRegions, then this scenario a default
reference is used as region is selected.
default region to
route the calls.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
The following objects are involved in the deactivation of IuFlex in WMS Small Cells:
Table 1-3 FGWConfig
activateIuFlexCS This attribute is set True Through WPS Small None

to configure IuFlex Cells, under
for CS domain. FGWConfig the
value must be set to
False
activateIuFlexPS This attribute is set True Through WPS Small None

for PS domain. FGWConfig the
value must be set to
False
Impacted services
There is no impact on any service on activation/deactivation of this feature. Also there is
no downtime on activation. The configuration is dynamic.
Impacted network elements
Network Element Impact Comment
WPS Small Cells No

Wireless Management System Small No
Cells (WMS Small Cells)
Home Device Manager (HDM) No

HDM adaptation layer No
Small Cell Yes
Iu Protocol Converter (IPC) No
IPsec Router No
BSR Packet Gateway (BPG) No
BSR Voice Gateway (BVG) No

BSG No
Authentication, Authorization and No

Accounting (AAA)
Small Cell Management System No
(SCMS)
Restrictions and limitations

None
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Duration for activation and deactivation
The activation/deactivation of IuFlex for IuCS and IuPS is done in a fraction of a second
without interrupting any other services.
Downtime
If the Small Cell does not have the correct setting in the ClusterProfile, BulkCM
download is required. This results in a downtime of approximately 15 minutes.
....................................................................................................................................................................................................................................
Issue 5 April 2014
IuFlex features 107284 - IuFlex over ATM
....................................................................................................................................................................................................................................
107284 - IuFlex over ATM

Overview
The IuFlex over ATM feature enables multiple IuFlex Iu interfaces, to connect from BSG
to MSC or SGSN through the IPC.
A BSG that supports the IuFlex features, can support up to 12-IuCS interfaces and
12-IuPS interfaces. Some (or all) of the Iu interfaces are connected to core network nodes
through ATM interfaces. These interfaces use an IPC that supports the IuFlex over ATM
feature, as shown in the following figure:
Figure 1-1 To connect ATM interfaces on 4 MSCs and 3 SGSNs to one BSG
The IuFlex over ATM feature is required on the IPC, such that the signaling configuration
illustrated can be supported a common pair of SCTP associations carrying traffic for
multiple Iu interfaces. The feature also increases the number of Iu interfaces from IPC to
core network nodes, to match the number possible from the BSG.
The IPC has up to 12 IuCS and 12 IuPS interfaces to core network nodes, and connects to
up to 8 BSGs.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
The following example configurations are possible:
A BSG can connect to up to 12 MSCs and 12 SGSNs, and 1 to 7 BSGs can also
connect to this same set of 12 MSCs and 12 SGSNs.
A BSG can connect to 6 MSCs and 6 SGSNs, and a second BSG can connect to a
different set of 6 MSCs and 6 SGSNs.
Other configurations that are within the constraints of 12 MSCs, 12 SGSNs and 8 BSGs
are possible. Deployment of any specific configuration must consider the total traffic
capacity of the IPC.
Purpose
This topic describes the activation and deactivation procedures for IuFlex over
Asynchronous Transfer Mode (ATM) (107284) feature using the BSG and IPC.
Before you begin

To configure with IPC
Ensure that:
IPCCLI is accessible in fms01 or fms02, wherever, the OAMLMTGwServer is
running. Use rnccheckservers command to determine the FMS (Flexent Mobility
Server), which has the LmtGwServer is running.
During creation of LIPC::SS7Stack::SS7LinkSet, the attribute
LIPC::SS7Stack::SS7LinkSet::linkType is set as iTU96. Also
LIPC::SS7Stack::SS7LinkSet::slsRange is set as sLS16.
During creation of PeerIPSP for CS and PS cluster, the attribute PeerIPSP::
m3uaDefaultNwkId is set as m3UANWKAPPITU and attribute
PeerIPSP::m3uaNwkAppIncl is set asfalse.
During creation of LIPC:IuCSIP and LIPC:IuPSIP MO, the attributes
LIPC::IuCSIP:: rANAPDestinationPointCodeBSG and LIPC::IuPSIP::
rANAPDestinationPointCodeBSG are configured as Originating PointCode
(OPC) of the BSG. Also LIPC::IuCSIP:: aNSIslsRange and LIPC::IuPSIP::
aNSIslsRange are set with the default value as aNSISLS32.
Note: The activation and deactivation at IPC is executed through IPCCLI. After
IuFlex activation, multiple instances of IuCS and IuPS can be added to the IPC,
through the IPCCLI.

To configure the IuFlex over ATM feature with IPCCLI
Perform the following steps:
...................................................................................................................................................................................................
1 Log in to the IPC using the Internet Protocol (IP) address.

....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Enter the following command to determine the FMS in which the LmtGwServer is
operational.
[IPC2425:fms01]-> rnccheckservers
Result: AVAIL OAMLMTGwServer.1 OAMLMTGwCapsule fms02 ACT
...................................................................................................................................................................................................
3 Execute the following command from the LmtGwServer:

[IPC2425:fms02]-> IPCCLI
Result: IPC Software (current) IPC-02.04.01.04
IPCCLI? Menu
...................................................................................................................................................................................................
4 Once the IPCCLI main menu is displayed, select option 4.

...................................................................................................................................................................................................
5 The Object Management Options is displayed. Select the appropriate option.

E...................................................................................................................................................................................................
N D O F S T E P S
To configure the IuFlex feature with WPS Small Cells

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Select LIPC MO in WPS Small Cells.

...................................................................................................................................................................................................
3 All the attributes that belong to LIPC MO are displayed on the right side. Select
enableIuFlex and set the value as True.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Managed objects involved in feature activation
Managed objects in BSG
Table 1-4 FGW <DN;>
Parameter name Description Default value Command Additional comment
activateIuFlexCS This attribute is used False set { Constraint

to enable the IuFlex activateIuFlex validation fails if
support for IuCS CS=True} multiple IuCS
interface instances are added
without enabling
this attribute.
activateIuFlexPS This attribute is used False set { Constraint

to enable the IuFlex activateIuFlex validation fails if
support for IuPS PS=True} multiple IuCS
interface instances are added
without enabling
this attribute.
Table 1-5 BSG:1
defaultCsRegionRef This parameter must FGW=530601,BSG=1, set { The default region

refer to a default CsRegion=1 defaultCsRegion reference is
CsRegion. If there is Ref="FGW=530601, dynamically
failure in routing a BSG=1,CsRegion= configured.
configured deployment scenario
CsRegions, then this a default region is
reference is used as selected.
default region to
route the calls.
defaultPsRegionRef This parameter must FGW=530601,BSG=1, set The default region
refer to a default PsRegion=1 {defaultPsRegion reference is
PsRegion. If there is Ref="FGW=530601, dynamically
a failure in routing a BSG=1,PsRegion= configured.
PsRegions, then this a default region is
a default region to
route the calls
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Managed objects in IPC
Table 1-6 LIPC
enableIuFlex A flag to enable False Use IPCCLI Constraint

IuFlex support. command, refer validation fails if
IuFlex is supported IPCCLI multiple IuCS
if the flag is set as commands instances are added
True. (p. 1-16) without enabling
this attribute.
Table 1-7 LIPC::SS7Stack::SS7LinkSet
linkType Specifies the iTU96 Use IPCCLI During creation of

protocol variant to command, refer SS7LinkSet, MO
be used in the IPCCLI needs to set the
interface. Where, 92 commands attribute value as per
and 96 determines (p. 1-16) the requirement.
the version of SCCP
to be used.
ITU96 means
that the IPC
uses ITU
protocol for
MTP3/SCCP
layers, and the
peer node
conforms to
SCCP ITU
1996 standards.
ANSI_96
means that the
IPC uses ANSI
protocol and
the peer node
conforms to
ANSI 1996
standards.
Note: For
Japan/TTC
Networks (that is,
where the
SS7Stack::isITU16
is set as TRUE),
select ITU96.
slsRange The number of Default = sLS16 Use IPCCLI During creation of

Signaling Link command, refer SS7LinkSet, MO
Selection (SLS) IPCCLI needs to set the
values for this Link commands attribute value as per
Set. (p. 1-16) the requirement.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 1-8 LIPC::SS7Stack::PeerIPSP
m3uaDefaultNwkId This attribute m3UANWKAPPITU Use IPCCLI During creation of

indicates the default command, refer PeerIPSP, MO needs
network Id, which is IPCCLI to set the attribute
used to decode the commands value as per the
incoming M3UA (p. 1-16) requirement.
messages in the
absence of M3UA
Network
Appearance
parameter. Enum 0
is for ITU, variant1
is for ANSI variant
with 5-bit SLS. And
2 is for ANSI variant
with 8-bit SLS.
m3uaNwkAppIncl This attribute False Use IPCCLI During creation of

indicates the command, refer PeerIPSP, MO needs
inclusion of M3UA IPCCLI to set the attribute
Network commands value as per the
Appearance in the (p. 1-16) requirement.
M3UA messages. If
IPC is working in
the IuFlex
configuration with
ANSI and ITU
messages exchanged
over a single
association, then this
flag must be enabled
to differentiate the
traffic.
When this flag is
enabled, the BSG
must send
appropriate Network
Appearance value in
M3UA messages.
The Network
Appearance can be
any one of the
following based on
the variant type.
SS7Stack::m3uaNwk
AppITUSS7Stack::
m3uaNwkAppANSI
5BitSS7Stack::m3ua
NwkAppANSI8Bit.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 1-9 LIPC::IuCSIP
rANAPDestination- ITU RANAP use BSG ITU IuCS Use IPCCLI During creation of
PointCodeBSG Destination Point pointcode. command, refer IuCSIP, MO needs
Code of the BSG. IPCCLI to set the attribute
The value of this commands value as per the
parameter has to be (p. 1-16) requirement.
coordinated with the
own point code
value set at the BSG.
This point code
(WHEN
NON-ZERO) is
used as OPC in
messages towards all
the ITU core
networks
aNSIslsRange The number of Default value = Use IPCCLI During creation of

Signaling Link aNSISLS32 command, refer IuCSIP, MO needs
Selection (SLS) IPCCLI to set the attribute
values for the linkset commands value as per the
(p. 1-16) requirement.
Table 1-10 LIPC::IuPSIP
rANAPDestination- ITU RANAP use BSG ITU IuPS Use IPCCLI During creation of
PointCodeBSG Destination Point pointcode command, refer IuPSIP, MO needs
Code of the BSG. IPCCLI to set the attribute
The value has to be commands value as per the
coordinated with the (p. 1-16) requirement.
own point code
value set at the BSG.
This point code
(WHEN
NON-ZERO) is
used as OPC in
messages towards all
the ITU core
networks
aNSIslsRange The number of Default Value = Use IPCCLI During creation of

Signaling Link aNSISLS32 command, refer IuPSIP, MO needs
Selection (SLS) IPCCLI to set the attribute
values for the linkset commands value as per the
(p. 1-16) requirement.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Managed objects in WMS Small Cells
Table 1-11 BSRCluster Profile
iuflexLaiRaiSelect This attribute is set Femto Through WPS Small None

based on whether Cells under
the LAI/RAI is sent BSRCluster Profile,
for IuFlex by Small the value femto
Cell or macro cell. must be selected.
Table 1-12 FGWConfig
activateIuFlexCS This attribute is set False Through WPS Small None

for CS domain. FGWConfig the
value must be set as
True
activateIuFlexPS This attribute is set False Through WPS Small None
for PS domain. FGWConfig the
True
Table 1-13 LIPC=1
enableIuFlex This attribute is set False Through WIPs under None

to enable the IuFlex LIPC the values
feature. need to select as
True
Managed objects in feature deactivation

Table 1-14 FGW<DN;>
activateIuFlexCS This attribute is used Working set { Constraint validation

to enable and disable configuration activateIuFlexCS fails if multiple IuCS
the IuFlex support value: True =True} instances are added
for IuCS interface get {
activateIuFlexCS}
attribute.
value.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 1-14 FGW<DN;> (continued)
activateIuFlexPS This attribute is used Working set { Constraint validation

to enable and disable configuration activateIuFlexPS fails if multiple IuCS
the IuFlex support value: True =True} instances are added
for IuPS interface get {
activateIuFlexPS}
attribute.
value.
Table 1-15 BSG:1
defaultCsRegionRef This parameter must FGW=530601,BSG=1, set { The default region

refer to a default CsRegion=1 defaultCsRegion reference is
CsRegion. If there is Ref="FGW=530601, dynamically
failure in routing a BSG=1,CsRegion= configured.
CsRegions, then this a default region is
default region to
route the calls.
defaultPsRegionRef This parameter must FGW=530601,BSG=1, set The default region
refer to a default PsRegion=1 {defaultPsRegion reference is
PsRegion. . If there Ref="FGW=530601, dynamically
is failure in routing a BSG=1,PsRegion= configured.
PsRegions, then this a default region is
default region to
route the calls

The following objects are involved for deactivation of IuFlex in IPC:
Note: Before deactivation of IuFlex feature, ensure that IuCSIP and IuPSIP MO
contain only one IuCSInstance and IuPSInstance. Otherwise, IPCCLI command fails
during deactivation.
Table 1-16 LIPC=1
enableIuFlex This attribute is used Working This attribute is used Constraint

to enable the IuFlex configuration value: to enable the IuFlex validation fails if
support in IPC. True support in IPC. multiple IuCS
instances are added
without enabling
this attribute.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 1-17 FGWConfig
activateIuFlexCS This attribute is set Working Through WPS Small None

to configure IuFlex configuration value: Cells, under
for CS domain. True FGWConfig the
False
activateIuFlexPS This attribute is set Working Through WPS Small None
to configure IuFlex configuration value: Cells, under
for PS domain. True FGWConfig the
False
Table 1-18 LIPC=1
enableIuFlex This attribute is used Working Through WPS Small None

to enable the IuFlex Configuration value Cells, under LIPC,
support in IPC. = True the value must be
false
IPCCLI commands
Configuration Manager active on fms01
STATE SERVER CAPSULE NODE TYPE

================================================================
AVAIL LogMgrInstance.1 OAMLogMgrCapsule fms01 ACT
AVAIL OAMAlarmMgr.1 OAMAlarmMgrCapsule fms01 ACT
AVAIL OAMBUMgr.1 OAMBUMgrCapsule fms01 ACT
AVAIL OAMDataAuditServer.1 OAMDataAuditServerCapsule fms02 ACT
AVAIL OAMEATranslator.1 OAMEATranslatorCapsule fms02 ACT
AVAIL OAMFMSTranslator.1 OAMFMSTranslatorCapsule fms02 ACT
AVAIL OAMInterfaceRAgent.1 OAMInterfaceRCapsule fms01 ACT
AVAIL OAMLMTGwServer.1 OAMLMTGwCapsule fms01 ACT ----> its
running in fms01
AVAIL OAMMEOServer.1 OAMMEOServerCapsule fms02 ACT
AVAIL OAMOAMSchedulerServer.1 OAMOAMSchedulerServerCapsule fms02
ACT
AVAIL OAMOFManager.1 OAMOFManagerCapsule fms02 ACT
AVAIL OAMPMServer.1 OAMPerfMgrCapsule fms01 ACT
AVAIL OAMShelfTranslator.1 OAMShelfTranslatorCapsule fms01 ACT
AVAIL OAMSignalTranslator.1 OAMSignalTranslatorCapsule fms01 ACT
AVAIL OAMSIHBServer.1 OAMAlarmMgrCapsule fms01 ACT
AVAIL OAMSUMgr.1 OAMSUMgrCapsule fms01 ACT
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
AVAIL OAMSysCoordServer.1 OAMSysCoordServerCapsule fms01 ACT
AVAILABLE: 17 UNAVAILABLE: 0 INITIALIZED: 0 RECOVERING: 0

OFFLINE: 0
WAITFORPROMOTE : 0 INVALID : 0
AMW domain is completely up; all servers are AVAILABLE!

[IPC2425:fms01]->
IPC Software (current) IPC-02.04.01.04
IPCCLI? menu
----------( IPC CLI Main Menu )----------
1. Batch Job Scheduling

2. Fault Management
3. Log and File Management
4. Object Management
5. IPC Audits
6. Software Upgrade
7. System Management
Select from menu or (E)xit (H)elp (F)ile? 4
---------------------( Object Management )---------------------
1. Audit 5. Lock 9. Cancel Test 13. PowerOn

2. Get Attributes 6. Unlock 10. Create 14. PowerOff
3. Set Attributes 7. Shutdown 11. Delete
4. List 8. Test 12. Reset
Select from menu or (B)ack (M)ain (E)xit (H)elp (F)ile?
+++++++Activation of IuFlex feature++++
---------------------( Object Management )----------------------

Select from menu or (B)ack (M)ain (E)xit (H)elp (F)ile? 3
----------( Object Selection )----------
SET:name=""
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
1. LIPC
Select from menu or (Q)uit (H)elp (F)ile? 1
Enter instance number (integer): 1
----------------------( Object Selection )----------------------

SET:name="LIPC=1"
1. ALL 9. GICCVirtualRouter 17. IuPSIP

2. ATMQOS 10. IPQOS 18. PG
3. AuditEntity 11. IPQoSFlow 19. RoutingTableEntry
4. BearerQOS 12. ItfIPC 20. SNMP
5. CFLBuffer 13. IuCS 21. SS7Stack
6. Cabinet 14. IuCSIP 22. SuMgr
7. ExtAlmBox 15. IuCSMGW
8. GICCIPInterface 16. IuPS
Select from menu or (B)ack (C)omplete (Q)uit (H)elp (F)ile? c

-----( Attribute Selection - 0 of 56 Items )-----
SET:name="LIPC=1"
1. aLCAPalcMultiplier
2. aLCAPalcoffset
3. aLCAPfPaTMcacFactor
4. administrativeState
5. applMonPollingInterval
6. applMonThresholdValue
7. cPUOverloadBeginLevel2Timer
9. cPUOverloadBeginThreshold
10. cPUOverloadEndLevel1Timer
12. cPUOverloadEndThreshold
13. cPUOverloadThreshold
14. cSDataSupport
15. cabinetGrowthDegrowth
16. clockSource
17. configIniIntervalTimer
18. enableIuFlex
Select from menu or (D)isplay (S)ubmit (Q)uit (H)elp (F)ile (N)ext?

18
-----( Parameter Value Selection - enableIuFlex )-----
1. false
2. true
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Select from menu or (B)ack (Q)uit (H)elp (F)ile? 2

SET:name="LIPC=1"
2. aLCAPalcoffset
14. cSDataSupport
16. clockSource
18. enableIuFlex
Select from menu or (D)isplay (S)ubmit (Q)uit (H)elp (F)ile (N)ext

(R)emove? s
SET :name="LIPC=1",enableIuFlex=true [ Wed Jul 21 12:13:01 UTC 2010:
STARTED ]
SET :name="LIPC=1",enableIuFlex=true [ Wed Jul 21 12:13:02 UTC 2010:

COMPLETED (OK) ]
================================================================
+++++De-activation of IuFlex Feature++++
Before deactivating IuFlex feature, make sure that IuCSIP / IuPSIP
have only one IuCSInstance / IuPSInstance
----------------------( Object Management )--------------------- 1.

Audit 5. Lock 9. Cancel Test 13. PowerOn
SET:name=""
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
1. LIPC
----------------------( Object Selection )----------------------

SET:name="LIPC=1"


SET:name="LIPC=1"
2. aLCAPalcoffset
14. cSDataSupport
16. clockSource
18. enableIuFlex
Select from menu or (D)isplay (S)ubmit (Q)uit (H)elp (F)ile (N)ext?

18
-----( Parameter Value Selection - enableIuFlex )-----
1. false
2. true
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

SET:name="LIPC=1"
2. aLCAPalcoffset
14. cSDataSupport
16. clockSource
18. enableIuFlex
Select from menu or (D)isplay (S)ubmit (Q)uit (H)elp (F)ile (N)ext

(R)emove? s
SET :name="LIPC=1",enableIuFlex=false [ Wed Jul 21 12:13:01 UTC
2010: STARTED ]
SET :name="LIPC=1",enableIuFlex=false [ Wed Jul 21 12:13:02 UTC

2010: COMPLETED (OK) ]
================================================================
++++++ creation of SS7Linkset for IuCS cluster +++++

CREATE:name=""
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
1. LIPC
-----------------------( Object Selection )---------------------
CREATE:name="LIPC=1"

Select from menu or (B)ack (C)omplete (Q)uit (H)elp (F)ile? 21

CREATE:name="LIPC=1,SS7Stack=1"
1. PeerIPSP
2. RANAPStackGroup
3. SIGTRANStackGroup
4. SS7LinkSet
5. SS7StackGroup

-------------( Object Selection )-------------
CREATE:name="LIPC=1,SS7Stack=1,SS7LinkSet=100"
1. SS7Link
------------( Attribute Selection - 0 of 10 Items )-------------

1. *adjacentPointCode 5. *tst 9. sparesString

2. *interfaceType 6. sparesBool 10. userLabel
3. *linkType 7. sparesInt
4. *slsRange 8. sparesReal
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Select from menu or (D)isplay (S)ubmit (Q)uit (H)elp (F)ile? 1

*adjacentPointCode Int Min: 1 Max: 16711679
Value ? 1025
-------------- Attribute Selection - 1 of 10 Items )------------

Select from menu or (D)isplay (S)ubmit (Q)uit (H)elp (F)ile

(R)emove? 2
-----( Parameter Value Selection - *interfaceType )-----
1. iUCS
2. iUPS
-------------( Attribute Selection - 2 of 10 Items )------------


(R)emove? 3
-----( Parameter Value Selection - *linkType )-----
1. aNSI96
2. iTU96
------------( Attribute Selection - 3 of 10 Items )--------------


....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
(R)emove? 4
-----( Parameter Value Selection - *slsRange )-----
1. sLS16
2. sLS256
3. sLS32


(R)emove? 5
*tst String MaxLength: 15
Enter String value
Value ? "MSC"


(R)emove? s
CREATE :name="LIPC=1,SS7Stack=1,SS7LinkSet=100",adjacentPointCode=
1025,interfaceType=iUCS,linkType=iTU96,slsRange=sLS16,tst="MSC" [
Wed Sep 8 10:27:03 UTC 2010: STARTED ]
1025,interfaceType=iUCS,linkType=iTU96,slsRange=sLS16,tst="MSC" [
Wed Sep 8 10:27:05 UTC 2010: COMPLETED (OK) ]
================================================================
++++++ creation of SS7Linkset for IuPS cluster +++++
----------------------( Object Management )---------------------

....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
CREATE:name=""
1. LIPC


1. PeerIPSP
2. RANAPStackGroup
4. SS7LinkSet
5. SS7StackGroup

....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
1. SS7Link


Value ? 2025


(R)emove? 2
1. iUCS
2. iUPS



(R)emove? 3
1. aNSI96
2. iTU96
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................


(R)emove? 4
1. sLS16
2. sLS256
3. sLS32


(R)emove? 5
Enter String value
Value ? "SGSN"


(R)emove? s
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
2025,interfaceType=iUPS,linkType=iTU96,slsRange=sLS16,tst="SGSN" [
2025,interfaceType=iUPS,linkType=iTU96,slsRange=sLS16,tst="SGSN" [
================================================================
++++++ creation PeerIPSP for IuCS cluster +++++

CREATE:name=""
1. LIPC


....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
1. PeerIPSP
2. RANAPStackGroup
4. SS7LinkSet
5. SS7StackGroup

-------------( Attribute Selection - 0 of 14 Items )-------------
CREATE:name="LIPC=1,SS7Stack=1,PeerIPSP=1"
1. *iPSPMode 8. *refGICCVirtualRouter
2. *m3uaClient 9. *requestedOutStrms
3. *m3uaDefaultNwkId 10. sparesBool
4. *m3uaNwkAppIncl 11. sparesInt
5. *peerPort 12. sparesReal
6. *pspIntfType 13. sparesString
7. *refBSGAddrList 14. userLabel
-----( Parameter Value Selection - *iPSPMode )-----
1. dOUBLE
2. sINGLE


(R)emove? 2
-----( Parameter Value Selection - *m3uaClient )-----
1. sERVER
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 3
-----( Parameter Value Selection - *m3uaDefaultNwkId )-----
1. m3UANWKAPPANSI5BIT
3. m3UANWKAPPITU

(R)emove? 4
-----( Parameter Value Selection - *m3uaNwkAppIncl )-----
1. false
2. true
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 5
*peerPort Int Min: 1 Max: 65535
Value ? 2905

(R)emove? 6
-----( Parameter Value Selection - *pspIntfType )-----
1. iUCS
2. iUPS

(R)emove? 7
*refBSGAddrList Sequence Min: 1 Max: 2 String MaxLength: 400
DnString
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Enter simple Sequence value as: {x, y, z}
Value ? "LIPC=1,RoutingTableEntry=1"

(R)emove? 8
*refGICCVirtualRouter String MaxLength: 400 DnString
Enter String value
Value ? "LIPC=1,GICCVirtualRouter=1"

(R)emove? 9
*requestedOutStrms Int Min: 2 Max: 17
Value ? 17
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? s
CREATE :name="LIPC=1,SS7Stack=1,PeerIPSP=1",iPSPMode=dOUBLE,
m3uaClient=sERVER,m3uaDefaultNwkId=m3UANWKAPPITU,m3uaNwkAppIncl=
false,peerPort=2905,pspIntfType=iUCS,refBSGAddrList="LIPC=1,
RoutingTableEntry=1",refGICCVirtualRouter="LIPC=1,
GICCVirtualRouter=1",requestedOutStrms=17 [ Wed Sep 8 10:37:42
UTC 2010: STARTED ]
false,peerPort=2905,pspIntfType=iUCS,refBSGAddrList="LIPC=1,
UTC 2010: COMPLETED (OK) ]
================================================================
++++++ creation PeerIPSP for IuPS cluster +++++
-----------------------( Object Management )-------------------

CREATE:name=""
1. LIPC

....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

1. PeerIPSP
2. RANAPStackGroup
4. SS7LinkSet
5. SS7StackGroup

1. dOUBLE
2. sINGLE

....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 2
1. sERVER

(R)emove? 3
3. m3UANWKAPPITU

(R)emove? 4
1. false
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
2. true

(R)emove? 5
Value ? 2917

(R)emove? 6
1. iUCS
2. iUPS
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 7
DnString

(R)emove? 8
Enter String value

(R)emove? 9
Value ? 17
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? s
false,peerPort=2917,pspIntfType=iUPS,refBSGAddrList="LIPC=1,
UTC 2010: STARTED ]
false,peerPort=2917,pspIntfType=iUPS,refBSGAddrList="LIPC=1,
================================================================
+++++ creation of IuCSIP +++++
-----------------------( Object Management )--------------------

CREATE:name=""
1. LIPC

....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

CREATE:name="LIPC=1,IuCSIP=1"
1. IuCSInstance
-------------( Attribute Selection - 0 of 14 Items )-----------
1. *aESANetworkAddress 8. administrativeState
2. *aNSIslsRange 9. rANAPDestinationPointCodeBSG
3. *peerIPSPList 10. sparesBool
4. *psMode 11. sparesInt
5. *refBVGAddrList 12. sparesReal
6. *refGICCVirtualRouter 13. sparesString
7. aNSIRANAPDestinationPointCodeBSG 14.userLabel

*aESANetworkAddress String RequiredLength: 59 NsapAddress
Enter String value
Value ?
"45.49.89.91.42.43.20.00.0f.00.00.00.00.00.00.00.00.00.00.00"
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 2
-----( Parameter Value Selection - *aNSIslsRange )-----
1. aNSISLS256
2. aNSISLS32
--------------( Attribute Selection - 2 of 14 Items )------------

(R)emove? 3
*peerIPSPList Sequence Min: 1 Max: 2 String MaxLength: 400 DnString
Value ? {"LIPC=1,SS7Stack=1,PeerIPSP=1"}
--------------( Attribute Selection - 3 of 14 Items )------------

(R)emove? 4
-----( Parameter Value Selection - *psMode )-----
1. aCTIVESTANDBY
2. lOADSHARED
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 5
*refBVGAddrList Sequence Min: 1 Max: 10 String MaxLength: 400
DnString
Value ? {"LIPC=1,RoutingTableEntry=2"}

(R)emove? 6
Enter String value
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
(R)emove? 9
rANAPDestinationPointCodeBSG Int Min: 0 Max: 65535
Value ? 602

(R)emove? 8
-----( Parameter Value Selection - administrativeState )-----
1. locked
2. shuttingDown
3. unlocked

(R)emove? s
CREATE :name="LIPC=1,IuCSIP=1",aESANetworkAddress=
"45.49.89.91.42.43.20.00.0f.00.00.00.00.00.00.00.00.00.00.00",
aNSIslsRange=aNSISLS32,peerIPSPList={"LIPC=1,SS7Stack=1,PeerIPSP=
1"},psMode=lOADSHARED,refBVGAddrList={"LIPC=1,RoutingTableEntry=
2"},refGICCVirtualRouter="LIPC=1,GICCVirtualRouter=2",
administrativeState=unlocked,rANAPDestinationPointCodeBSG=602 [
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
"45.49.89.91.42.43.20.00.0f.00.00.00.00.00.00.00.00.00.00.00",
================================================================
++++++ Creation of IuPSIP MO ++++++++

CREATE:name=""
1. LIPC


CREATE:name="LIPC=1,IuPSIP=1"
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
1. IuPSInstance
---------( Attribute Selection - 0 of 11 Items )---------
1. *aNSIslsRange 7. sparesBool
2. *peerIPSPList 8. sparesInt
3. *psMode 9. sparesReal
4. aNSIRANAPDestinationPointCodeBSG 10. sparesString
5. administrativeState 11. userLabel
6. rANAPDestinationPointCodeBSG

1. aNSISLS256
2. aNSISLS32

(R)emove? 2
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 3
1. aCTIVESTANDBY
2. lOADSHARED

(R)emove? 5
1. locked
2. shuttingDown
3. unlocked

(R)emove? 6
rANAPDestinationPointCodeBSG Int Min: 0 Max: 65535
Value ? 601
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? s
CREATE :name="LIPC=1,IuPSIP=1",aNSIslsRange=aNSISLS32,peerIPSPList=
{"LIPC=1,SS7Stack=1,PeerIPSP=2"},psMode=lOADSHARED,
================================================================
Impacted services
no downtime on activation. The configuration is dynamic.
WPS Small Cells No

WMS Small Cells No
HDM No

Small Cell No
IPC No
IPsec Router No
BPG Yes During creation of Iu interfaces,
family type must be set accordingly.
BVG No
BSG No
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
AAA No
Security Gateway Management No

System
Small Cell Cluster Yes Small Cell Cluster attribute values

must be configured.

In SEP mode, IuFlex is not supported in IPC.
Duration and for activation and deactivation

The activation/deactivation of IuFlex over ATM is done in a fraction of a second without
interrupting any other services.
Downtime
None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
IuFlex features Creating IPC objects with WPS Small Cells
....................................................................................................................................................................................................................................
Creating IPC objects with WPS Small Cells

Purpose
This topic describes the procedure to export IPC configuration and create IPC objects
with WPS Small Cells.
Export IPC configuration

The following steps must be performed to export IPC configuration:
...................................................................................................................................................................................................
1 Log in to IPC with FMS01/02 IP address. Execute the following command to find an
active FMS:
[IPC2425:fms01]-> RCCcstat
Result: RCC Cluster [FLXcluster] Status
fms01 2 A - ACTIVE
fms02 3 L - LEAD
[IPC2425:fms01]->
...................................................................................................................................................................................................
2 Execute the following command in the IPC of the active FMS:

./flx/RNCinitdb/current/bin/datablitz_meosDump.ksh
...................................................................................................................................................................................................
3 The db_walk.dump file is created in the IPC (/flx/RNCinitdb/current/bin), which has data
from the first day.
...................................................................................................................................................................................................
4 Perform the following steps to copy the db_walk.dump file to your desktop.
1. Open the windows command prompt.
2. Navigate to the directory, where you want to save the db_walk.dump file.
3. Execute the command, ftp 135.254.212.98 ( use the IPC IP address ).
4. Use the IPC credentials to log in.
5. Execute the command, bi to set the binary transfer mode.
6. Execute cd /flx/RNCinitdb/current/bin command, to navigate to the
destination folder.
7. Execute mget db_walk.dump to transfer the file.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
IuFlex features Creating IPC objects with WPS Small Cells
....................................................................................................................................................................................................................................
Importing IPC db_walk.dump file
Perform the following steps to import the IPC db_walk.dump file to WPS Small Cells:
...................................................................................................................................................................................................
1 Open the latest version of WPS Small Cells software.

...................................................................................................................................................................................................
2 Perform the following steps to create an IPC object using the WPS Small Cells:
1. Initially WPS Small Cells contains only the Network object.
2. To create, Object Creation: create , select IPC[OAMOAM] from the drop-down.
3. Enter a value for userLabel.
4. Create, to create the IPC object.
...................................................................................................................................................................................................
3 Perform the following steps to a LIPC MO, under IPC object (create only one LIPC MO)
:
1. Select an IPC object.
2. In the Object Creation: create drop-down list, select LIPC[04_00_00IPC].
3. Enter a value for id and Create.
4. A LIPC MO is created in IPC/1/LIPC/1/SS7Stack/1 path.
...................................................................................................................................................................................................
4 Select the LIPC MO and Overview on the right side. Now load IPC snapshot file link to
load the db_walk.dump to WPS Small Cells.
...................................................................................................................................................................................................
5 A new popup window opens, browse to select db_walk.dump file and OK.
...................................................................................................................................................................................................
6 WPS Small Cells loads the mediated data, and replaces the initial snapshot under LIPC
MO.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
IuFlex features IPCCLI batch file processing with WPS Small Cells
....................................................................................................................................................................................................................................
IPCCLI batch file processing with WPS Small Cells

Purpose
This topic describes the procedure to generate IPCCLI batch and update IPC database
with WPS Small Cells.
Generating IPCCLI batch files

The following steps must be performed to generate IPCCLI batch files:
...................................................................................................................................................................................................
1 Select LIPC MO, then Overview on the right pane.

...................................................................................................................................................................................................
2 Execute the following command in the IPC of the active FMS:

./flx/RNCinitdb/current/bin/datablitz_meosDump.ksh
...................................................................................................................................................................................................
3 Give a name to the output CLI file. For example, Lipc1.cli, and OK.
...................................................................................................................................................................................................
4 The following three files are generated:

LIPC1Summary.html
LIPC1.cli has the following content:
create (LIPC=1,SS7Stack=1,SS7LinkSet=1)\
adjacentPointCode="1025"\
interfaceType="IUCS"\
linkType="ITU96"\
slsRange="SLS16"\
tst="MSC"\
userLabel=""
set (LIPC=1)\
enableIuFlex="true"
LIPC1Reversed.cli has the following content:
delete (LIPC=1,SS7Stack=1,SS7LinkSet=1)
set (LIPC=1)\
enableIuFlex="false"
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Importing IPC CLI batch file to IPC
Perform the following steps to import the IPC CLI batch file to IPC:
...................................................................................................................................................................................................
1 Log in to the command prompt. Navigate to the directory that has the Lipc1.cli file.
...................................................................................................................................................................................................
2 Execute the command ftp ip-address, where ip-address is the IP of the IPC.
...................................................................................................................................................................................................
3 Enter the IPC credentials to log in. Execute the command bi to set binary transfer mode.
...................................................................................................................................................................................................
4 Execute the command cd /flx/RNCinitdb/current/bin, to navigate to the

destination folder.
...................................................................................................................................................................................................
5 Execute the command mput Lipc1.cli, to transfer the file.

E...................................................................................................................................................................................................
N D O F S T E P S
Updating IPC database from WPS Small Cells generated IPC CLI batch file
Perform the following steps to update the IPC database from the WPS Small Cells
generated IPC CLI batch file:
...................................................................................................................................................................................................
1 Log in to the command prompt.

...................................................................................................................................................................................................
2 Navigate to the folder containing the Lipc1.cli file.

...................................................................................................................................................................................................
3 Execute the command telnet <ip-address>, where ip-address is the IP of the IPC.
...................................................................................................................................................................................................
4 Enter the IPC credentials to log in.

...................................................................................................................................................................................................
5 Execute the command [IPC2425:fms01]-> cd /flx/RNCinitdb/current/bin, to

navigate to the folder where the Lipc1.cli file is present.
...................................................................................................................................................................................................
6 Execute the following commands:
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
[IPC2425:fms01]-> ./meosCli s Lipc1.cli
...................................................................................................................................................................................................
7 Execute the following command in the IPC FMS prompt, to check if all the 17 servers are
functioning:
Result:

=================================================================
AVAIL LogMgrInstance.1 OAMLogMgrCapsule
fms02 ACT
AVAIL OAMAlarmMgr.1 OAMAlarmMgrCapsule
fms02 ACT
AVAIL OAMBUMgr.1 OAMBUMgrCapsule
fms02 ACT
AVAIL OAMDataAuditServer.2 OAMDataAuditServerCapsule
fms01 ACT
AVAIL OAMEATranslator.2 OAMEATranslatorCapsule
fms01 ACT
AVAIL OAMFMSTranslator.2 OAMFMSTranslatorCapsule
fms01 ACT
AVAIL OAMInterfaceRAgent.1 OAMInterfaceRCapsule
fms02 ACT
AVAIL OAMLMTGwServer.1 OAMLMTGwCapsule
fms02 ACT
AVAIL OAMMEOServer.2 OAMMEOServerCapsule
fms01 ACT
AVAIL OAMOAMSchedulerServer.2 OAMOAMSchedulerServerCapsule
fms01 ACT
AVAIL OAMOFManager.2 OAMOFManagerCapsule
fms01 ACT
AVAIL OAMPMServer.1 OAMPerfMgrCapsule
fms02 ACT
AVAIL OAMShelfTranslator.1 OAMShelfTranslatorCapsule
fms02 ACT
AVAIL OAMSignalTranslator.2 OAMSignalTranslatorCapsule
fms02 ACT
AVAIL OAMSIHBServer.1 OAMAlarmMgrCapsule
fms02 ACT
AVAIL OAMSUMgr.1 OAMSUMgrCapsule
fms02 ACT
AVAIL OAMSysCoordServer.1 OAMSysCoordServerCapsule
fms02 ACT

OFFLINE: 0
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
[IPC2425:fms01]->
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
2 Security features
2
Overview
Purpose
This chapter describes the activation/deactivation procedure for the Small Cell security
features.
Contents
78243 - Security hardening of the BSG 2-2

114366 - SCMS security enhancements 2-5
121317 - Tamper Alarm 2-10
83086 - Certificate-based authentication and security for V2 HW 2-14
155820 - Security enhancements via radius support on the BSR Gateway 2-17
...................................................................................................................................................................................................................................
Issue 5 April 2014
Security features 78243 - Security hardening of the BSG
....................................................................................................................................................................................................................................
78243 - Security hardening of the BSG

Overview
This feature introduces the following security improvements to the BSG to reduce the risk
of misuse of the Small Cell:
A second level of Access Control List (ACL) enforcement for closed access Small
Cells.
Validation of Small Cell registrations.
Blocking of uplink connection-less RANAP messages sent by Small Cells towards the
core network.
This feature has three security goals:
The Small Cell registration with the BSG must be secured.
If a user is not listed in the ACL stored in the BSG, the user must not gain access to
the Small Cell network through a compromised closed access Small Cell.
A Small Cell must not be able to impact the calls of another Small Cell.
This feature is active by default. However, two security functions of the feature can be
disabled independently. They are:
The ACL check of closed access Small Cells can be disabled in the BSG. If this check
is disabled, the BSG omits the detection of the RANAP Common Id message and thus
also omits the second-level ACL check.
Validation of the Small Cell Registration message can be disabled in the BSG. If this
validation is disabled, the BSG omits the check of the Small Cell registration
parameters against the Small Cell configuration data sent from the SCMS.
All other security functions of this feature are always available and cannot be disabled.
Purpose
This topic describes the activation and deactivation procedures for Security hardening of
the BSG (78243) feature.
Related information
From the Small Cell, the activation and deactivation of the feature is through the WPS
Small Cells.
Before you begin

Ensure that the SSH key, between the BSG and SCMS, is authenticated for automatically
transferring the BSR Data XML file from SCMS to BSG, through the SFTP server.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
The following procedure must be followed:
1. Log in as the root user.
2. Execute the command ssh-keygen -t rsa to create an SSH key.
3. Press Enter twice when prompted for Pass Phrase.
4. An Id_rsa.pub file is created in the /root/.ssh/ folder.
5. To ensure that the SSH key exchange is successful, execute the following command:
# sftp fgwuser@ <SCMS IP address>
For example, # sftp fgwuser@172.61.111.5
Connecting to 172.61.111.5...
This system is a restricted access system. All activity on
this system is subject to monitoring. If information
collected reveals possible criminal activity or activity
that exceeds privileges, evidence of such activity may be
provided to the relevant authorities for further action. By
continuing past this point, you expressly consent to this
monitoring.
6. Log in to the SCMS as a root user.
7. Execute the following commands:
chown R fgwuser:<group of fgwuser> /home/fgwuser/.ssh;
chmod 700 /home/fgwuser/.ssh;
chmod 600 /home/fgwuser/.ssh/authorized_keys
8. Copy the content of Id_rsa.pub to the /home/fgwuser/.ssh/authorized_keys file.
The /opt/log/FMG/Log_Secutity.log is used to log security-related transitions.
Feature activation and deactivation procedures

...................................................................................................................................................................................................
1 The security hardening feature is enabled by default and it is highly recommended not
to disable. Also there is no provision for configuration with WPS Small Cells.
E...................................................................................................................................................................................................
N D O F S T E P S
Impacted services
None
WPS Small Cells No
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
WMS Small Cells No
HDM No
Small Cell No
IPC No
IPsec Router No
BPG No
BVG No
BSG Yes The security hardening feature is
enabled by default and hence it is
inherent to load test, and hence
potential performance & capacity
impact is not considered here.
AAA No
System

None

NA
Downtime
NA
....................................................................................................................................................................................................................................
Issue 5 April 2014
Security features 114366 - SCMS security enhancements
....................................................................................................................................................................................................................................
114366 - SCMS security enhancements

Overview
The SCMS security enhancements feature incorporates the following security measures:
Uses the SUN Basic Security Model (BSM) on the file server for operating system /
file system activity auditing. This enables utilization of security logs for activities
related to the operating system / file system configuration.
Uses only SSH version 2 on the file server.
SCP is disabled for ftpuser. Only sftp from Small Cell to file server is permitted.
Optimized approach to restrict sftp commands for ftpuser.
A dedicated directory per Small Cell for file upload. In order, to restrict a hacked
Small Cell from having read/write access to PM and other files, of other Small Cells.
Purpose
This topic describes the activation and deactivation procedures for the SCMS security
enhancements (114366) feature.
Feature activation and deactivation procedure

This feature cannot be activated or deactivated.
To verify the functionality of this feature, perform the following steps (The following
output is just an illustration, the operator must modify the parameter values
appropriately)
...................................................................................................................................................................................................
1 To verify, that the SCP is disabled for ftpuser, login to the Small Cell as admin user and
perform the following steps illustrated:
scp gpsFile ftpuser@172.61.111.3:/var/tmp/.
Result: ftpuser@172.61.111.3's password:
Enter the user Id and password, in this example 172.61.111.3 is file server IP.
This service allows sftp connections only.
root@femto-2119688856:/var/tmp#
Normally sftp is used by Small Cell for getting a software image or Bulkcm.xml file
from the sftp server. It is not triggered manually by the user, but is automatically
triggered.
...................................................................................................................................................................................................
2 Log in to the file server machine as a root user.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Consider the following steps illustrated, to verify the packages installed:
1. bash-3.00# pkginfo -l NNaudtrl
PKGINST: NNaudtrl
NAME: Alcatel-Lucent Audit Trail Application
CATEGORY: application
ARCH: sparc
VERSION: V02_04.E01-20102801
BASEDIR: /opt/nortel
VENDOR: Alcatel-Lucent
DESC: This package installs the Audit Trail application
PSTAMP: zsups28220100716101329
INSTDATE: Dec 30 2010 16:08
STATUS: completely installed
FILES: 28 installed pathnames
6 directories
11 executables
276 blocks used (approx)
2. bash-3.00# pkginfo -l SMCosh541
PKGINST: SMCosh541
NAME: openssh
ARCH: sparc
VERSION: 5.4p1
BASEDIR: /usr/local
VENDOR: The OpenSSH Group
PSTAMP: Steve Christensen
EMAIL: steve@smc.vnet.net
4 shared pathnames
19 directories
21 executables
3. bash-3.00# pkginfo -l SMCossl
PKGINST: SMCossl
NAME: openssl
ARCH: sparc
VERSION: 1.0.0
BASEDIR: /usr/local
VENDOR: The OpenSSL Group
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
1 shared pathnames
43 directories
32 executables
4. bash-3.00# pkginfo -l SMCzlib
PKGINST: SMCzlib
NAME: zlib
ARCH: sparc
VERSION: 1.2.4
BASEDIR: /usr/local
VENDOR: Greg Roelofs and Jean-loup Gaillt
4 shared pathnames
11 directories
3 executables
5. bash-3.00# pkginfo -l SUNWjass
PKGINST: SUNWjass
NAME: Solaris Security Toolkit 4.2.1 with File Server
Extensions
ARCH: Solaris
VERSION: 4.2.1
BASEDIR: /opt VENDOR: Sun Microsystems, Inc. & Alcatel-
Lucent DESC: The Solaris Security Toolkit is
collection of tools and scripts used to automate the security
hardening and verification of a system running the Solaris
OE. File Server Extension made by Alcatel-Lucent
PSTAMP: on10-dhpg20050725154502
HOTLINE: Please contact Alcatel-Lucent HNMS project group.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
50 directories
410 executables
bash-3.00#
...................................................................................................................................................................................................
3 Execute the following command as a root user, to ensure an entry for ATCron in file
server root crontab:
bash-3.00# crontab -l
Result: #ident "@(#)root 1.21 04/03/23 SMI"
#
# The root crontab should be used to perform accounting data
collection.
#
#
10 3 * * * /usr/sbin/logadm
15 3 * * 0 /usr/lib/fs/nfs/nfsfind
30 3 * * * [ -x /usr/lib/gss/gsscred_clean ] && /usr/lib/gss/
gsscred_clean
0 4 * * * /fsconf/purge/delMIB.sh
10 4 * * * /fsconf/purge/db.sh
20 1 * * * /fsconf/purge/delObservation.sh
10 1 * * * /fsconf/purge/deltrace.sh
0 1 * * * /fsconf/purge/deldiagnostic.sh
0,5,10,15,20,25,30,35,40,45,50,55 * * * * /opt/nortel/shell/
AuditTrail/ATCron -standalone >> /opt/nortel/logs/AuditTrail/
.ATCronMessageLog 2>&1 (Ensure that this entry is present)
bash-3.00#
E...................................................................................................................................................................................................
N D O F S T E P S
Impacted services
None
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
WPS Small Cells No
WMS Small Cells No

HDM No

Small Cell No
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No
System

None.

NA
Downtime
None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Security features 121317 - Tamper Alarm
....................................................................................................................................................................................................................................
121317 - Tamper Alarm

Overview
In the event that the Small Cell Access Point, detects that it has been tampered with, it
raises an alarm to the SCMS.
Tampering is detected by a switch on the device, and the device is not destroyed by this
action.
SCMS forwards the alarm to the Northbound Interface (NBI). The SCMS may shut down
the Access Point, if instructed to do so, by the IT system of the operator.
Purpose
This topic describes the activation and deactivation procedures for Tamper alarm
(121317) feature.

To configure through WPS Small Cells
...................................................................................................................................................................................................
1 Load the exported snapshot from WMS Small Cells into the WPS Small Cells. Import the
snapshot into WPS Small Cells.
...................................................................................................................................................................................................
2 Set the attributes, faultId as tamperDetected and reportingMecanism as

expediated, available under SupportedAlarmsInrealTime.
...................................................................................................................................................................................................
3 Set faultNotificationEnabled as True in BSRProfile.

...................................................................................................................................................................................................
4 Click Run checks... on the FemtoCluster.

...................................................................................................................................................................................................
5 Create a WorkOrder and copy it into WMS Small Cells.

...................................................................................................................................................................................................
6 Navigate to Configuration > Sessions Manager > Create new Session, to launch the
WorkOrder in WMS Small Cells.
...................................................................................................................................................................................................
7 The attribute is automatically updated in the Small Cell.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
8 Once the CM download is successful in HDM, verify the attribute values by uploading
the database file from Small Cell.
E...................................................................................................................................................................................................
N D O F S T E P S

Managed objects in the WMS Small Cells
Table 2-1 SupportedAlarmsInrealTime
Parameter name Description Value Comments
faultId:: Detects tamper.

tamperDetected
reportingechanism::ex- Report alarm to SCMS By setting it
pediated as logged, the
alarm is not
sent to SCMS
but is present
in the logs.
Table 2-2 BSR
Parameter Description Default Value Value Syntax Permitted

name values
BSR:: The parameter is False Set as True boolean { True, False }

faultNotifica- to switch on/off
tionEnabled the real-time
fault
notification.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 2-3 BSR
Parameter Description Default Value Value Syntax Additional

name comment
BSR:: This parameter False If set as True boolean Tamper Alarm

EnclosureTam- indicates device fault can be
peringDetected whether physical tampering is cleared by
tampering of the detected. If set manually setting
device enclosure as False no this parameter
occurred, such sign of device as False.
as illegal tampering is
opening of the detected.
box. Note:
Tampering state
must be
persisted across
reboots but not
factory reset.
BSR:: The parameter is False False boolean { True, False}

faultNotifica- to switch on/off
tionEnabled the real-time
fault
notification.
Impacted services
If it is a consumer board and has been tampered, the board becomes permanently
non-functional.
If it is an enterprise board and has been tampered, the board can be recovered by setting
the EnclosureTamperingDetected parameter as False.
Impacted Network Elements
WPS Small Cells No
WMS Small Cells No
HDM No
Small Cell Yes See Impacted services (p. 2-12)
IPC No
IPsec Router No
BPG No
BVG No
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
BSG No
AAA No
System

None.
Duration
NA
Downtime
None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Security features 83086 - Certificate-based authentication and security for V2
HW
....................................................................................................................................................................................................................................
83086 - Certificate-based authentication and security for V2

HW
Overview
The feature aims at providing the Small Cell with an authentication capability, based on a
certificate, with information safely stored in the Small Cell.
Also, the Small Cell uses a secure boot.
Alcatel-Lucent provides a mechanism, for controlling and restricting the number of Small
Cells produced by a factory (manufacturers).
It is also enables the network / service providers, to restrict the use of Small Cells to
specific network providers.
This feature introduces the following two security improvements to the Small Cell:
Certificate-based authentication
Secure boot
Certificate-based authentication
For certificate-based authentication, the Small Cell is securely programmed with a private
key. The Small Cell is also provided with a signed certificate, which binds the
corresponding public key to the Small Cell unique identity. This certificate is used to
authenticate the Small Cell to the SeGW, and the SeGW is in turn authenticated to the
Small Cell by means of a certificate. Once both entities have been authenticated, an IPsec
tunnel is established which permits the Small Cell connect to the rest of the Small Cell
network, and normal proceed with the normal processing.
Secure boot
The performance of the Small Cell is enhanced by using a newer device from PicoChip
(PC302). The PC302 uses TrustZone, which is used to secure information and boot files
for the Small Cell. The secure boot enables secure insertion of information to the Small
Cell.
Purpose
This topic describes the activation and deactivation procedures for Certificate-based
authentication and security for V2 HW (83086) feature.
....................................................................................................................................................................................................................................
Issue 5 April 2014
HW
....................................................................................................................................................................................................................................
Before you begin
Ensure that:
The Security Gateway is operational.
The Security Gateway is configured with the Chain of Certificates, and Security
Gateway Tunnel End Point (TEP) is configured to use the certificate-based
authentication.
Note: A separate TEP is required for certificate-based authentication, apart from the
Extensible Authentication Protocol (EAP) TEP.
TrustZone with secure boot enabled Small Cell is used.
The private key for the Small Cell is configured in Small Cell.
The CA certificates and Small Cell certificate are configured in Small Cell.

Note: This feature cannot be activated or deactivated. The unique identity of the
Small Cell is set using the WPS Small Cells.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Set the attribute, hnbUniqueIdentity with an appropriate value.

...................................................................................................................................................................................................
3 Click Run checks... on the Small Cell.

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
HW
....................................................................................................................................................................................................................................
Managed objects
Table 2-4 BSR
Parameter name Description Syntax Permitted

values
hnbUniqueIdentity This attribute reports the unique identity of the string length=16
Small Cell. This is an EUI-64 number as specified
in 3GPP TS23.003.
Impacted services
None
WPS Small Cells No

WMS Small Cells No
HDM No
Small Cell Yes
IPC No
IPsec Router No
BPG No
BVG No
BSG Yes
AAA Yes
Security Gateway Management Yes
System
SCMS Yes

None.
Duration
NA
Downtime
None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Security features 155820 - Security enhancements via radius support on the
BSR Gateway
....................................................................................................................................................................................................................................
155820 - Security enhancements via radius support on the BSR

Gateway
Overview
This feature deals with the implementation of radius interface between the Security
Gateway (SeGW) and the BSR Gateway to enhance the security features of the Small
Cell Solution.
Purpose
This topic describes the activation and deactivation procedures for Security enhancements
by means of radius support on the BSR Gateway (155820) feature.
Note: This feature is the same as 77716.
Before you begin

1. Ensure that the Security Gateway is physically connected to the All-in-one-Small Cell
Gateway (AIOG).
2. Ensure that the remote AAA is physically connected to AIOG.
a. AIOG is operational. The communication link between the SCMS and BSG is
operational.
b. The SSH key is exchanged, for a password-less sftp communication between
SCMS and BSG. This enables SCMS to download the Small Cell related
information file to BSG.
AAA configuration
The SERVER_SECRET parameter must be set, as in the Security Gateway or other
instances created with in AAA:1
The AAA_config.ini file present in /opt/conf provides configuration information for AAA.
...................................................................................................................................................................................................
1 This file has the configurations for AAA Proxy Server communication with OAM and
BSG.
...................................................................................................................................................................................................
2 It defines the port which has the AAA server running. It must be set as 1812.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
BSR Gateway
....................................................................................................................................................................................................................................
Activating the AAA executable
...................................................................................................................................................................................................
1 AAA executable starts up only if at least one instance of AAAsecurityGateway class is

present.
E...................................................................................................................................................................................................
N D O F S T E P S
Modifying AAAsecurityGateway and AAAremoteAAAServer attributes using WMS Small Cells

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to Network, select a BSR Gateway instance. Select Import bulkcm file on the
right side and import the OAM_PreConfig.xml file.
...................................................................................................................................................................................................
3 Navigate to Network > FGW > AAA:1 and create object AAAsecurityGateway:1.
Set the following attributes:
securityGatewayCalledStationId as 192.168.17.1/32
securityGatewayDefaultSeGW as False
securityGatewayFemtoVPNSubnets as 10.63.0.0/24
securityGatewayId as 1
securityGatewayNasIdentifier as " "
securityGatewayNasIpAddress as 172.63.112.7
securityGatewayNasPorts as " "
securityGatewayReservedAddressSubnets as 10.10.16.12/30
securityGatewaySharedSecret as secret.
...................................................................................................................................................................................................
4 Navigate to Network > FGW > AAA:1 and create object AAAremoteAAAServer:1.
Set the following attributes:
remoteAAAServerId as 1
remoteAAAServerIpAddress as 172.63.112.7
remoteAAAServerRealm as eapds2460.iprc.nlt.in
remoteAAAServerSharedSecret as secret.
....................................................................................................................................................................................................................................
Issue 5 April 2014
BSR Gateway
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
5 On the main window, navigate to Checks and click Run checks....

...................................................................................................................................................................................................
6 Create a WorkOrder and export it into WMS Small Cells.

...................................................................................................................................................................................................
7 Log in to the WMS Small Cells as administrator.

...................................................................................................................................................................................................
8 Navigate to Configuration > Sessions Manager > Create a new session and locate the
work order file.
...................................................................................................................................................................................................
9 Click Add to list and select Launch.

...................................................................................................................................................................................................
10 Once the work order is successfully launched, select Activate.

E...................................................................................................................................................................................................
N D O F S T E P S
Configuring AAA* to support multi-homed SeGW

In case of a SeGW that has more than one NAS-IP-address (multi-homed), bound with a
static IP address, the AAA* attribute SecurityGatewayNasIdentifier must be
configured.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Navigate to Network > FGW > AAA:1 > AAAsecurityGateway:1 and set attribute
securityGatewayNasIdentifier as ALSMS: <IP address of active SeGW>.
For example: ALSMS:172.71.113.7,172.71.113.8
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
BSR Gateway
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
work order file.
...................................................................................................................................................................................................

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
To configure using WPS Small Cells

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Set the attribute hnbUniqueIdentity to EUI-64 value of the Small Cell.

...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
5 Launch the WorkOrder in WMS Small Cells using Configuration > Sessions Manager >
Create new Session.
...................................................................................................................................................................................................
6 The attribute is automatically updated in Femto.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
BSR Gateway
....................................................................................................................................................................................................................................
Managed objects involved in activation from BSG
Managed Object Class Name: AAA
Table 2-5 /FGW:<DN>/AAA:1
Parameter name Description Syntax
AAAremoteAAAServer:<id> This attribute contains information for the sequence [0..10]

pool of remote AAA servers which can be
accessed by the BSG.
securityGateway:<id> This attribute contains information for the sequence [0..20]

Security Gateways which can be accessed by
the BSG.
clusterPrimaryDNS This attribute provides the IP address for the ipAddress

Primary DNS server for the cluster.
clusterSecondaryDNS This attribute provides the IP address for the ipAddress

Secondary DNS.
accReqRetryTimer This attribute sets the time after which the [500..5000], unit=ms
BSG AAA server retransmits access request
messages to the external AAA server.
accReqRetryMax This attribute provides the maximum [0..5] integer
retransmit count after which the BSG AAA
server contacts the secondary external AAA
server
acctReqRexmitTimer This attribute sets the retry timer for [500..5000], unit = minutes
accounting termination request from the
BSG AAA server to the Security Gateway.
maxAcctReqXmts This attribute provides the maximum retries [0..10] integer

allowed for accounting termination request.
pendingAllocTimer This attribute starts the timer on receiving [1..120], unit = seconds
VPN IP until Accounting Start is received.
On time-out, the VPN IP is moved to
Available state.
Table 2-6 /FGW:<DN>/AAA:1/AAAremoteAAAServer <instance>
remoteAAAServerId Instance number of integer

remoteAAAServer.
remoteAAAServerIpAddress This parameter provides either the IP ipAddress

address or FQDN for the remote Example: 172.63.112.7 or
AAA server. remoteAAA1.iprc.nlt.in
remoteAAAServerRealm This parameter provides the realm string, length = 50
associated with the Remote AAA
server
remoteAAAServerSharedSecret This parameter provides the shared string, length = 228

secret used between the Small Cell
Gateway and the remote AAA server
....................................................................................................................................................................................................................................
Issue 5 April 2014
BSR Gateway
....................................................................................................................................................................................................................................
Table 2-7 /FGW:<DN>/AAA:1/AAAsecurityGateway <instance>
Parameter name Description Syntax Default
securityGatewayAddress- This parameter provides [1..4294967295], unit = 600000

LeaseTime the address lease time in seconds
seconds for the Security
Gateway.
securityGatewayCalled- This parameter provides aaa.bbb.ccc.ddd/ee

StationId the Called Station Id Example:192.168.17.1/32
subnet value for the
Security Gateway.
securityGatewayDefault- This parameter controls Boolean False
SeGW whether the Security
Gateway performs
authorization of the Small
Cell, when connected
using the default Security
Gateway. When set as
False, the Small Cell
Gateway does not carry
out the authorization. And
when set as True, the
Small Cell Gateway
completes the
authorization.
securityGatewayFem- This parameter provides string, length = 100
toVPNSubnets the subnet range from Example: 10.63.0.0/24
which the Small Cell
Gateway allocates the
Small Cell VPN IP
address.
securityGatewayId Instance number of integer
Security Gateway.
securityGatewayNasIden- This parameter provides string, length = 50
tifier the NAS identifier for the
Security Gateway.
securityGatewayNasIpAd- This parameter provides ipAddress
dress the NAS IP address for the
Security Gateway.
securityGatewayNasPorts This parameter provides string, length = 100
the NAS ports available to
the Security Gateway. The
ports are defined in a
comma-separated list.
securityGatewayRe- This parameter provides string, length = 100

servedAddressSubnets the subnet range which the
Small Cell Gateway may
use for other (non-Small
Cell VPN) IP addresses.
....................................................................................................................................................................................................................................
Issue 5 April 2014
BSR Gateway
....................................................................................................................................................................................................................................
Table 2-7 /FGW:<DN>/AAA:1/AAAsecurityGateway <instance> (continued)
Parameter name Description Syntax Default
securityGatewaySharedSe- This parameter provides string, length = 228

cret the shared secret used
between the Small Cell
Gateway and the Security
Gateway.
Table 2-8 BSR
Parameter name Description Syntax Permitted values
hnbUniqueIdentity This attribute reports the string [1..128] units=PDU

unique identity of the
Small Cell. This is an
EUI-64 number as
specified in 3GPP
TS23.003.

Managed objects involved in deactivation from BSG
Table 2-9 /FGW:<DN>/AAA:1
Parameter name Description Command
administrativeState This attribute enables/disables AAA set{

administrativeState=
locked};
Impacted Services
Feature activation/deactivation requires restarting the Small Cell, which interrupts
services.
WPS Small Cells No

WMS Small Cells No
HDM No

Small Cell Yes Feature activation/deactivation
requires restarting the Small Cell.
IPC No
....................................................................................................................................................................................................................................
Issue 5 April 2014
BSR Gateway
....................................................................................................................................................................................................................................
IPsec Router Yes Third party Security Gateway must

support RADIUS, digital certificates
and allocate VPN IP from pool as
required.
BSR Gateway Yes

AAA Yes Remote AAA for DS2460 Small
Cells and allocate VPN IP from pool
as required.
System
Restrictions and Limitations

NA
Duration
NA
Downtime
Feature activation/deactivation requires restarting the Small Cell, which causes temporary
downtime.
....................................................................................................................................................................................................................................
Issue 5 April 2014
3 Transport features
3
Overview
Purpose
This chapter describes the activation/deactivation procedure for the Small Cell transport
features.
Contents
78241 - Direct tunnel 3-2

104503 - Dual stack (ANSI/ETSI) on ATM/IP 3-5
77713 - PDP shutdown of data session 3-66
84791 - Real-time monitoring of backhaul bandwidth 3-70
131828 - 2 ms TTI on E-DCH 3-73
122468 - Satellite backhaul 3-78
...................................................................................................................................................................................................................................
Issue 5 April 2014
Transport features 78241 - Direct tunnel
....................................................................................................................................................................................................................................
78241 - Direct tunnel

Overview
The direct tunnel feature allows the SGSN to establish a direct user plane tunnel between
the RAN and the GGSN within the PS domain.
The SGSN in the core network handles the control plane signaling, and determines when
to establish a direct user plane tunnel between the Small Cell and GGSN within the PS
domain of the core network.
In the Small Cell IuPS architecture, the Small Cell SGSN interface uses two tunnels for
user data. One tunnel is between the Small Cell and the SGSN, and one tunnel is between
the SGSN and the GGSN. With the direct tunnel option, the SGSN can set up and use a
single tunnel between the RAN and the GGSN.
The direct tunnel concept as applied to the Small Cell, is shown in the following figure:
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Purpose
This topic describes the activation and deactivation procedures for Direct tunnel (78241)
feature.
Before you begin

Ensure that:
The Small Cell version is Direct tunnel feature complaint.
The direct tunnel functionality is supported by both, the SGSN and the GGSN in the
core network.

...................................................................................................................................................................................................
1 There is no provision to activate or deactivate the direct tunnel feature.

E...................................................................................................................................................................................................
N D O F S T E P S
Impacted services
None.
WPS Small Cells No

WMS Small Cells No
HDM No
Small Cell Yes With the support of the direct tunnel

functionality in the Small Cell
Solution, the network can experience
looping PDP contexts or inconsistent
PDP context data in some rare error
cases, for example, at node failures
or restarts. Hence the Small Cell
must be compliant to the error
handling requirements as per the
3GPP standards. These error
handling requirements are defined in
3GPP TR 23.919 (Direct Tunnel
Deployment Guideline), Section 5.4
and 3GPP TS 23.060 Section 13.8.3.
IPC No
IPsec Router No
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
BPG Yes With the support of the direct tunnel

functionality in the Small Cell
Solution, the network can experience
looping PDP contexts or inconsistent
PDP context data in some rare error
cases, for example, at node failures
or restarts. Hence the BPG must be
compliant to the error handling
requirements as per the 3GPP
standards. These error handling
requirements are defined in 3GPP
TR 23.919 (Direct Tunnel
Deployment Guideline), Section 5.4
and 3GPP TS 23.060 Section 13.8.3.
BVG No
BSG No
AAA No
System
Serving General Packet Radio Yes The direct tunnel functionality is

Service Node (SGSN) / Gateway supported by both the SGSN and the
GPRS Support Node (GGSN) GGSN in the core network.

None

NA
Downtime
NA
....................................................................................................................................................................................................................................
Issue 5 April 2014
Transport features 104503 - Dual stack (ANSI/ETSI) on ATM/IP
....................................................................................................................................................................................................................................
104503 - Dual stack (ANSI/ETSI) on ATM/IP

Overview
This feature enables connection of a Small Cells Cluster to MSC(s) and SGSN(s) that use
the SS7 signaling standard ANSI and ITU. It enables configuration of the SS7 signaling
type, ITU or ANSI, per Iu interface type, and thus a one Small Cells Cluster supports both
standards simultaneous.
The BSG supports both the standards simultaneously, but with the following limitations:
All IuCS interfaces on one cluster can be configured, en bloc or independently, to be
either ANSI or ITU.
All IuPS interfaces on one cluster can be configured, en bloc, to be either ANSI or
ITU.
Coexistence of different standard on IuCS of one cluster, or coexistence of different
standard on IuPS of one cluster is not supported. The configuration with this limitation is
called as Simplified Dual Stack support.
With the introduction of Dual Stack (ITU/ANSI) feature, IPC supports configuration of
each Iu link from the BSG as either ITU or ANSI. This configuration is feasible, as the
variant type of each BSG-CN pair is determined based on the CNs variant configuration.
Purpose
This topic describes the activation and deactivation procedures for Dual stack
(ANSI/ETSI) on ATM/IP (104503) feature using the BSG, IPC, and WPS Small Cells.
Before you begin

Ensure that:
IPCCLI is accessible in fms01 or fms02, wherever, the OAMLMTGwServer is active.
Use rnccheckservers command to determine the FMS, which has the
activeLmtGwServer.
During creation of LIPC::SS7Stack::SS7LinkSet, the attribute
LIPC::SS7Stack::SS7LinkSet::linkType is set to aNSI96. Also
LIPC::SS7Stack::SS7LinkSet::slsRange is set to sLS256.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
During creation of PeerIPSP for CS and PS cluster, the attribute PeerIPSP::
m3uaDefaultNwkId is set to m3UANWKAPPANSI5BIT or m3UANWKAPPANSI8BIT as
required. And attribute PeerIPS::m3uaNwkAppIncl is set tofalse.
During creation of LIPC:IuCSIP and LIPC:IuPSIP MOs, the attributes
LIPC::IuCSIP:: rANAPDestinationPointCodeBSGand LIPC::IuPSIP::
rANAPDestinationPointCodeBSG are configured as BSGs originating pointcode
(OPC). Also LIPC::IuCSIP:: aNSIslsRange and LIPC::IuPSIP::
aNSIslsRange are set with the default value as aNSISLS32 for ANSI 5 bit
configuration, else aNSISLS256 is set for ANSI 8 bit configuration.

Note: There is no provision to enable or disable the dual stack feature. The attribute in
IuCS / IuPS MO class only provides an option to define the family of the Iu instance.
It must be either ITU or ANSI as per the Simplified Dual Stack configuration.
To configure using WPS Small Cells:
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Navigate to Network > FGW and create objects IuCS and IuPS. Select <family type> as
iTU or ANSI as appropriate.
...................................................................................................................................................................................................
4 Set the following attributes:

administrativeState as unlocked.
ranapRemoteSSN as 142
sccpReference as FGW=530601,BSG=1,SCCP=1
dpc as 1041
routingContext as 1
localPointCode as 602
deloading as False
globalCnIdPlmnIdentityMcc as 262
globalCnIdPlmnIdentityMnc as 95
globalCnIdCnid as 2
ranapTimerInConnGuard as 2000
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
work order file.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
To configure the dual stack feature with IPC

Note: There is no individual attribute to activate the ANSI feature. The whole IuCS
and IuPS cluster must be created. And while creation of the cluster, MO attributes
must be considered.
Perform the following steps to create the required managed objects (MOs) with IPCCLI:
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Log in to IPC using IP address.

...................................................................................................................................................................................................
4 Enter the following rnccheckservers command to determine FMS which has an active
LmtGwServer.
...................................................................................................................................................................................................
5 From that LmtGwServer enter the following IPCCLI command:

....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
IPCCLI? Menu
...................................................................................................................................................................................................

...................................................................................................................................................................................................
7 Then the Object Management Options is displayed. Select the appropriate option.
E...................................................................................................................................................................................................
N D O F S T E P S

Table 3-1 IuCS:
Family This attribute used This attribute is set This attribute is set The family must be
to define the at the time of on creation. as per Simplified
standard that is creating to either Dual Stack
supported by the Iu. aNSI or iTU limitation.
Table 3-2 IuPS:
Family This attribute used This attribute is set This attribute is set The family must be
to define the at the time of on creation. as per Simplified
standard that is creating to either Dual Stack
supported by the Iu. aNSI or iTU limitation.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 3-3 LIPC::SS7Stack::SS7LinkSet
linkType Specifies the aNSI96 Use IPCCLI During creation of

protocol variant to command (refer SS7LinkSet, MO
be used in the IPCCLI commands needs to set the
interface. Where, 92 for ANSI 5 bit - attribute value as per
and 96 determines IPCCLI the requirement.
the version of SCCP commands for 5 bit
to be used..- ITU96 ANSI
means that the IPC configuration
uses ITU protocol (p. 3-12)or IPCCLI
for MTP3/SCCP commands for
layers, and the peer ANSI 8 bit -
node conforms to IPCCLI
SCCP ITU 1996 commands for 8 bit
standards.- ANSI
ANSI_96 means that configuration
the IPC uses ANSI (p. 3-38)as
protocol, and the appropriate. )
peer node conforms
to ANSI 1996
standards.Note: For
Japan/TTC
Networks (i.e.
Where the
SS7Stack::isITU16
is set to TRUE),
select ITU96
slsRange The number of Set as sLS32 for Use IPCCLI During creation of
Signaling Link ANSI 5 bit command (refer SS7LinkSet, MO
Selection (SLS) configuration or IPCCLI commands needs to set the
values for this Link sLS256 for ANSI 8 for ANSI 5 bit - attribute value as per
Set bit configuration IPCCLI the requirement.
commands for 5 bit
ANSI
configuration
(p. 3-12)or IPCCLI
commands for
ANSI 8 bit -
IPCCLI
commands for 8 bit
ANSI
configuration
(p. 3-38)as
appropriate. )
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 3-4 LIPC::SS7Stack::PeerIPSP
m3uaDefaultNwkId This attribute Set as Use IPCCLI During creation of

indicates the default m3UANWKAPPANSI command (refer PeerIPSP, MO needs
network Id, which is 5BIT for ANSI 5 bit IPCCLI commands to set the attribute
used to decode the configuration or for ANSI 5 bit - value as per the
incoming M3UA m3UANWKAPPANSI IPCCLI commands requirement.
messages in the 8BIT for ANSI 8 bit for 5 bit ANSI
absence of M3UA configuration configuration
Network (p. 3-12)or IPCCLI
Appearance commands for ANSI
parameter. As per 8 bit - IPCCLI
the Enum .0 is for commands for 8 bit
ITU variant1 is for ANSI configuration
ANSI variant with 5 (p. 3-38)as
bit SLS and 2 is for appropriate. )
ANSI variant with 8
bit SLS.
m3uaNwkAppIncl This attribute False Use IPCCLI During creation of

indicates the command (refer PeerIPSP, MO needs
inclusion of M3UA IPCCLI commands to set the attribute
Network for ANSI 5 bit - value as per the
Appearance in the IPCCLI commands requirement.
M3UA messages. for 5 bit ANSI
When the IPC is configuration
working in Iuflex (p. 3-12)or IPCCLI
configuration with commands for ANSI
ANSI and ITU 8 bit - IPCCLI
messages exchanged commands for 8 bit
over a single ANSI configuration
association, this flag (p. 3-38)as
must be enabled to appropriate. )
differentiate the
traffic.
When this flag is
enabled, the BSG
must send
appropriate Network
Appearance value in
M3UA messages.
The Network
Appearance can be
any one of the
following based on
the variant type.
SS7Stack::m3uaNwk
AppITUSS7Stack::
m3uaNwkAppANS
I5BitSS7Stack::m3
uaNwkAppANSI8Bit.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 3-5 LIPC::IuCSIP
rANAPDestination- ITU RANAP use BSG ANSI IuCS Use IPCCLI During creation of
PointCodeBSG Destination Point pointcode. command (refer IuCSIP, MO needs
Code of the BSG. IPCCLI commands to set the attribute
The value of this has for ANSI 5 bit - value as per the
to be coordinated IPCCLI commands requirement.
with the own point for 5 bit ANSI
code value set at the configuration
BSG.This point code (p. 3-12)or IPCCLI
(WHEN commands for ANSI
NON-ZERO) is 8 bit - IPCCLI
used as OPC in commands for 8 bit
messages towards all ANSI configuration
the ITU core (p. 3-38)as
networks appropriate. )
aNSIslsRange The number of Set as aNSISLS32 Use IPCCLI During creation of
Signaling Link for ANSI 5 bit command (refer IuCSIP, MO needs
Selection (SLS) configuration or IPCCLI commands to set the attribute
values for the linkset aNSISLS256 for for ANSI 5 bit - value as per the
ANSI 8 bit IPCCLI commands requirement.
configuration for 5 bit ANSI
configuration
(p. 3-12)or IPCCLI
commands for ANSI
8 bit - IPCCLI
commands for 8 bit
ANSI configuration
(p. 3-38)as
appropriate. )
Table 3-6 LIPC::IuPSIP
aNSIRANAPDesti- ANSI RANAP use BSG IuPS Use IPCCLI During creation of
nationPoint- Destination Point pointcode command (refer IuPSIP, MO needs
CodeBSG Code of the BSG. IPCCLI commands to set the attribute
The value of this has for ANSI 5 bit - value as per the
to be coordinated IPCCLI commands requirement.
with the own point for 5 bit ANSI
code value set at the configuration
BSG. This point (p. 3-12)orIPCCLI
code (WHEN commands for ANSI
NON-ZERO) is 8 bit - IPCCLI
used as OPC in commands for 8 bit
messages towards all ANSI configuration
the ANSI core (p. 3-38)as
networks. appropriate. )
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 3-6 LIPC::IuPSIP (continued)
aNSIslsRange The number of Set as aNSISLS32 Use IPCCLI During creation of

Signaling Link for ANSI 5 bit command (refer IuPSIP, MO needs
Selection (SLS) configuration or IPCCLI commands to set the attribute
values for the linkset aNSISLS256 for for ANSI 5 bit - value as per the
ANSI 8 bit IPCCLI commands requirement.
configuration for 5 bit ANSI
configuration
(p. 3-12)or IPCCLI
commands for ANSI
8 bit - IPCCLI
commands for 8 bit
ANSI configuration
(p. 3-38)as
appropriate. )

There is no individual attribute to deactivate the ANSI feature. The whole IuCS and IuPS
cluster must be cleared, so that IPC does not contain any ANSI related MOs.
IPCCLI commands for 5 bit ANSI configuration


================================================================
AVAIL OAMLMTGwServer.1 OAMLMTGwCapsule fms01 ACT----> its
running in fms01
AVAIL OAMOAMSchedulerServer.1 OAMOAMSchedulerServerCapsule fms02 ACT

OFFLINE: 0
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

[IPC2425:fms01]->
IPCCLI? menu
----------( IPC CLI Main Menu )----------

2. Fault Management
5. IPC Audits
6. Software Upgrade
----------------------( Object Management )-------------------

++++++ creation of SS7Linkset for IuCS cluster (ANSI 5 bit

configuration )+++++
-------------------------( Object Management )----------------

CREATE:name=""
1. LIPC
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
--------------------------( Object Selection )-----------------



1. PeerIPSP
2. RANAPStackGroup
4. SS7LinkSet
5. SS7StackGroup

1. SS7Link


Value ? 1111025
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................


(R)emove? 2
1. iUCS
2. iUPS


(R)emove? 3
1. aNSI96
2. iTU96


(R)emove? 4
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
1. sLS16
2. sLS256
3. sLS32


(R)emove? 5
Enter String value
Value ? "MSC"
--------------( Attribute Selection - 5 of 10 Items )--------------


(R)emove? s
1025,interfaceType=iUCS,linkType=aNSI96,slsRange=sLS32,tst="MSC" [
1025,interfaceType=iUCS,linkType=aNSI96,slsRange=sLS32,tst="MSC" [
================================================================
-------------------------( Object Management )-----------------

....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
CREATE:name=""
1. LIPC


1. PeerIPSP
2. RANAPStackGroup
4. SS7LinkSet
5. SS7StackGroup

1. SS7Link
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................


Value ? 1112025


(R)emove? 2
1. iUCS
2. iUPS


(R)emove? 3
1. aNSI96
2. iTU96
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................


(R)emove? 4
1. sLS16
2. sLS256
3. sLS32


(R)emove? 5
Enter String value
Value ? "SGSN"


(R)emove? s
2025,interfaceType=iUPS,linkType=aNSI96,slsRange=sLS32,tst="SGSN"
[ Wed Sep 8 10:27:03 UTC 2010: STARTED ]
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
[ Wed Sep 8 10:27:05 UTC 2010: COMPLETED (OK) ]
================================================================
++++++ creation PeerIPS for IuCS cluster +++++

CREATE:name=""
1. LIPC


1. PeerIPSP
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
2. RANAPStackGroup
4. SS7LinkSet
5. SS7StackGroup

3. *m3uaDefaultNwkId 10.sparesBool
1. dOUBLE
2. sINGLE


(R)emove? 2
1. sERVER
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 3
3. m3UANWKAPPITU

(R)emove? 4
1. false
2. true
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 5
Value ? 2905

(R)emove? 6
1. iUCS
2. iUPS

(R)emove? 7
DnString
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 8
Enter String value

(R)emove? 9
Value ? 17
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? s
m3uaClient=sERVER,m3uaDefaultNwkId=m3UANWKAPPANSI5BIT,
m3uaNwkAppIncl=false,peerPort=2905,pspIntfType=iUCS,refBSGAddrList=
"LIPC=1,RoutingTableEntry=1",refGICCVirtualRouter="LIPC=1,
UTC 2010: STARTED ]
================================================================
++++++ creation PeerIPS for IuPS cluster +++++
----------------------( Object Management )--------------------

CREATE:name=""
1. LIPC
------------------------( Object Selection )--------------------

....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

1. PeerIPSP
2. RANAPStackGroup
4. SS7LinkSet
5. SS7StackGroup
1. dOUBLE
2. sINGLE

....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 2
1. sERVER

(R)emove? 3
3. m3UANWKAPPITU

(R)emove? 4
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
1. false
2. true

(R)emove? 5
Value ? 2917

(R)emove? 6
1. iUCS
2. iUPS
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 7
DnString

(R)emove? 8
Enter String value

(R)emove? 9
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Value ? 17

(R)emove? s
m3uaNwkAppIncl=false,peerPort=2917,pspIntfType=iUPS,refBSGAddrList=
UTC 2010: STARTED ]
================================================================
-------------------------( Object Management )------------------

CREATE:name=""
1. LIPC
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................



1. IuCSInstance
--------------( Attribute Selection - 0 of 14 Items )-----------
7. aNSIRANAPDestinationPointCodeBSG 14. userLabel

Enter String value
Value ?
"45.49.89.91.42.43.20.00.0f.00.00.00.00.00.00.00.00.00.00.00"
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 2
1. aNSISLS256
2. aNSISLS32

(R)emove? 3

(R)emove? 4
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
1. aCTIVESTANDBY
2. lOADSHARED

(R)emove? 5
DnString

(R)emove? 6
Enter String value
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 7
aNSIRANAPDestinationPointCodeBSG Int Min: 0 Max: 65535
Value ? 111602

(R)emove? 8
1. locked
2. shuttingDown
3. unlocked

(R)emove? s
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
"45.49.89.91.42.43.20.00.0f.00.00.00.00.00.00.00.00.00.00.00",
administrativeState=unlocked,aNSIRANAPDestinationPointCodeBSG=
111602 [ Wed Sep 8 10:47:14 UTC 2010: STARTED ]
"45.49.89.91.42.43.20.00.0f.00.00.00.00.00.00.00.00.00.00.00",
111602 [ Wed Sep 8 10:47:14 UTC 2010: COMPLETED (OK) ]
================================================================

CREATE:name=""
1. LIPC
----------------------( Object Selection )--------------------

....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
1. IuPSInstance

1. aNSISLS256
2. aNSISLS32

(R)emove? 2
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
(R)emove? 3
1. aCTIVESTANDBY
2. lOADSHARED

(R)emove? 5
1. locked
2. shuttingDown
3. unlocked
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
(R)emove? 4
Value ? 111601

(R)emove? s
================================================================
IPCCLI commands for 8 bit ANSI configuration


================================================================
AVAIL OAMLMTGwServer.1 OAMLMTGwCapsule fms01 ACT ----> its
running in fms01
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
AVAIL OAMOAMSchedulerServer.1 OAMOAMSchedulerServerCapsule fms02
ACT

OFFLINE: 0

[IPC2425:fms01]->
IPCCLI? menu
----------( IPC CLI Main Menu )----------

2. Fault Management
5. IPC Audits
6. Software Upgrade
-----------------------( Object Management )--------------------

++++++ creation of SS7Linkset for IuCS cluster (ANSI 8 bit

configuration )+++++
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
CREATE:name=""
1. LIPC


1. PeerIPSP
2. RANAPStackGroup
4. SS7LinkSet
5. SS7StackGroup

....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
1. SS7Link
--------------( Attribute Selection - 0 of 10 Items )--------------


Value ? 1111025

(R)emove? 2
1. iUCS
2. iUPS

(R)emove? 3
1. aNSI96
2. iTU96
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 4
1. sLS16
2. sLS256
3. sLS32
------------( Attribute Selection - 4 of 10 Items )------------

elect from menu or (D)isplay (S)ubmit (Q)uit (H)elp (F)ile (R)emove?
5
Enter String value
Value ? "MSC"


(R)emove? s
1025,interfaceType=iUCS,linkType=aNSI96,slsRange=sLS256,tst="MSC"
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
1025,interfaceType=iUCS,linkType=aNSI96,slsRange=sLS256,tst="MSC"
================================================================

CREATE:name=""
1. LIPC
-----------------------( Object Selection )--------------------


1. PeerIPSP
2. RANAPStackGroup
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
4. SS7LinkSet
5. SS7StackGroup

1. SS7Link


Value ? 1112025


(R)emove? 2
1. iUCS
2. iUPS
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................


(R)emove? 3
1. aNSI96
2. iTU96


(R)emove? 4
1. sLS16
2. sLS256
3. sLS32

(R)emove? 5
Enter String value
Value ? "SGSN"
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................


(R)emove? s
================================================================
++++++ creation PeerIPS for IuCS cluster +++++

CREATE:name=""
1. LIPC
-----------------------( Object Selection )-------------------

....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

1. PeerIPSP
2. RANAPStackGroup
4. SS7LinkSet
5. SS7StackGroup

1. dOUBLE
2. sINGLE

....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 2
1. sERVER

(R)emove? 3
3. m3UANWKAPPITU

(R)emove? 4
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
1. false
2. true

(R)emove? 5
Value ? 2905

(R)emove? 6
1. iUCS
2. iUPS
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 7
DnString

(R)emove? 8
Enter String value

(R)emove? 9
Value ? 17

....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? s
UTC 2010: STARTED ]
================================================================
++++++ creation PeerIPS for IuPS cluster +++++
----------------------( Object Management )-------------------

CREATE:name=""
1. LIPC

....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................


1. PeerIPSP
2. RANAPStackGroup
4. SS7LinkSet
5. SS7StackGroup

1. dOUBLE
2. sINGLE

....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 2
1. sERVER

(R)emove? 3
3. m3UANWKAPPITU
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 4
1. false
2. true

(R)emove? 5
Value ? 2917

(R)emove? 6
1. iUCS
2. iUPS
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 7
DnString

(R)emove? 8
Enter String value
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 9
Value ? 17

(R)emove? s
UTC 2010: STARTED ]
================================================================
----------------------( Object Management )--------------------

CREATE:name=""
1. LIPC
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................



1. IuCSInstance

Enter String value
Value ?
"45.49.89.91.42.43.20.00.0f.00.00.00.00.00.00.00.00.00.00.00"
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 2
1. aNSISLS256
2. aNSISLS32
-----------------( Attribute Selection - 2 of 14 Items

)-----------------

(R)emove? 3
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
(R)emove? 4
1. aCTIVESTANDBY
2. lOADSHARED

(R)emove? 5
DnString

(R)emove? 6
Enter String value
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 7
Value ? 111602

(R)emove? 8
1. locked
2. shuttingDown
3. unlocked
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
(R)emove? s
"45.49.89.91.42.43.20.00.0f.00.00.00.00.00.00.00.00.00.00.00",
"45.49.89.91.42.43.20.00.0f.00.00.00.00.00.00.00.00.00.00.00",
aNSIslsRange=aNSISL256,peerIPSPList={"LIPC=1,SS7Stack=1,PeerIPSP=
================================================================
---------------------( Object Management )----------------------

CREATE:name=""
1. LIPC
---------------------( Object Selection )----------------------

....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

1. IuPSInstance

1. aNSISLS256
2. aNSISLS32

(R)emove? 2
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 3
1. aCTIVESTANDBY
2. lOADSHARED

(R)emove? 5
1. locked
2. shuttingDown
3. unlocked
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

(R)emove? 4
Value ? 111601

(R)emove? s
================================================================
Impacted services
no downtime on this activation. It is a dynamic configuration.
WPS Small Cells No
WMS Small Cells No

HDM No
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Small Cell No
IPC No
IPsec Router No
BPG No
BVG No
BSG Yes During creation of Iu interfaces,
family type must be set accordingly.
AAA No
System
Small Cells Cluster Yes Small Cells Cluster attribute values
must be configured.

None

NA
Downtime
None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Transport features 77713 - PDP shutdown of data session
....................................................................................................................................................................................................................................
77713 - PDP shutdown of data session

Overview
The PDP shutdown of data session (77713) feature, provides the ability to deactivate a
PDP context when a UE reselects from the macro to the Small Cell, or from the Small
Cell to the macro independently. Some operators may just want incoming deactivation, to
ensure that the billing is updated when a UE enters a Small Cell. Other operators may
want both incoming and outgoing deactivation.
Incoming deactivation
In case of incoming deactivation, the Small Cell corrupts the Routing Area Update (RAU)
request towards the SGSN. Each Small Cell provisions a different LA and RA to its
neighbors. As a result, the UE performs a RAU when it enters the Small Cell coverage.
For incoming mobility with a RAU, the Small Cell modifies the PDP context status in the
NAS message, if the IE shows a non-zero status, by resetting the IE to all zeroes
indicating no PDP context present. If the IE is not present, then the Small Cell inserts an
all-zero IE in the RAU NAS message. This result in a mismatch in the SGSN, which then
releases the PDP context. The SGSN responds with a RAU Accept NAS message,
containing an IE with an all-zero PDP context status. This NAS message causes a
mismatch in the UE, which releases the PDP context. If the SGSN does not provide an IE,
then the Small Cell inserts an all-zero IE in the RAU Accept NAS message.
Outgoing deactivation
The outgoing deactivation requires the Small Cell to manipulate a number of
NAS/RANAP scenarios between the UE and SGSN. During an outgoing cell reselection,
the Small Cell remaps the NSAPI Ids between the UE and SGSN. That is, when a UE
requests activation of NSAPI x, the Small Cell translates the request such that the SGSN
assumes the UE is requesting the activation of NSAPI y. While the UE remains within the
Small Cell controlled area, the Small Cell translates between NSAPI x & y, such that both
the UE and SGSN are happy. Once the UE moves to the macro controlled area, since
NSAPI Ids between the UE and SGSN are different and the UTRAN no longer remaps
these IDs, both UE and SGSN locally deactivate the PDP context. Thereby, forcing the
end user, or more likely the UE, to activate a new PDP context. In case of only outgoing
shutdown, the Small Cell detects the active NSAPI detected on an incoming RAU
request, and preserves these contexts and NSAPI mappings. In case, the UE attempts to
activate a PDP context on an NSAPI already used for translation, the Small Cell detects
the clash, shuts down the PDP context which has clashed and allows re-establishment.
Dependencies
As a part of the operators strategy, Internet Breakout at CPE (109515) feature utilizes the
PDP shutdown feature, but is not dependent upon it.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
The solution for Internet Breakout at the CPE, relies upon the translation of the IP address
in the PDP context activation to the local IP address. This feature ensures that the PDP
context is reactivated in the Small Cell before any data is transferred on the local IP
address through the breakout feature. The operator is assured, that the data traffic passes
outside the CN and the lower billing tariff is justified. As the UE reselects from the Small
Cell to the macro network, the Internet breakout translation no longer works and it is
advantageous to deactivate the PDP context.
Purpose
This topic describes the activation and deactivation procedures for the PDP shutdown
(77713) feature.
Before you begin

Ensure that:
1. The Small Cell is active and running and is able to make CS/PS calls.
2. The user is able to make the BulkCM configuration changes using the WMS.

...................................................................................................................................................................................................
1 This feature can be activated/deactivated through the Small Cell using the WPS Small
Cells. Refer, Small Cell attributes configuration with WPS Small Cells (p. 9-8)
E...................................................................................................................................................................................................
N D O F S T E P S

The following Small Cell objects are involved in the activation of the feature:
Table 3-7 BSR
Parameter Name Parameter Value Comment

Description
enableIncoming- Parameter enables the True Default value is
DataShutdown shutdown of an False.
incoming PDP
context.
enableOutgoing- Parameter enables the True Default value is
outgoing PDP
context.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 3-7 BSR (continued)

Description
maxNumberOfUEDi- The maximum 256 When the
rectoryEntries number of UE BSR::enableIncom-
directory entries that ingDataShutdown is
can be stored in the set to TRUE,
Small Cell. BSR::maxNumberO-
fUEDirectoryEntries
(default 0) must be
set to a value, which
is suitable for the
number of UEs likely
to be accessed by the
Small Cell. That is,
the typical ACL size
of the Small Cell. A
value of 30 is
considered to be
suitable

The following Small Cell objects are involved in the deactivation of the feature:
Table 3-8 BSR

Description
enableIncoming- Parameter enables the False Default value is
incoming PDP
context.
enableOutgoing- Parameter enables the False Default value is
outgoing PDP
context.
Impacted services
None
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
WPS Small Cells No
WMS Small Cells No

HDM No

Small Cell No
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No
System

If an NSAPI translation is performed for outgoing PS shutdown, the PS session is
preserved when the UE reselects another Small Cell (Example, when moving within a
Small Cell Group).
The UE behavior during PDP context deactivation is not standardized. It is
manufacturer specific whether the UE reactivates the PDP context automatically and
in a seamless manner.
It is also GGSN-specific, whether the PDP reactivation results in the same IP address
being used on reactivation.
PS shutdown does not function if the RAC used is the same as macro (example, in
some Small Cells deployments), due to the lack of RAU when the UE reselects from
the macro to the Small Cell, which is required for the incoming shutdown.
Note: In case of the Internet breakout (109515) feature being activated, the IP address
allocated to the UE is different.

NA
Downtime
NA
....................................................................................................................................................................................................................................
Issue 5 April 2014
Transport features 84791 - Real-time monitoring of backhaul bandwidth
....................................................................................................................................................................................................................................
84791 - Real-time monitoring of backhaul bandwidth

Overview
The feature 84791 Real-time monitoring, introduces a new measurement method for the
available backhaul bandwidth. These new monitoring functions cope with changing
traffic parameters on the Small Cell backhaul. And also for Call Admissions Control
(CAC) and Resource Management (RRM), in the absence of a service level agreement
between the internet service provider and the mobility provider. The existing
measurement methods, introduced and improved in former releases, which are useful to
detect the maximum backhaul bandwidth are still required.
Purpose
This topic describes the activation and deactivation procedures for Real-time monitoring
of backhaul bandwidth (84791) feature.

...................................................................................................................................................................................................
1 The managed objects must be modified to activate/deactivate the feature.

E...................................................................................................................................................................................................
N D O F S T E P S

The following MOs are modified from the BSG, refer Chapter 9, Common
Configuration Procedures:
Table 3-9 BSG
Parameter Name Parameter Description Command

FGW::enableRTMonitoring This attribute controls the Set
enabling or disabling of the {enableRTMonitoring=
Real Time Monitoring feature True};
on the BSG.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
The following MOs are modified from WMS Small Cells, refer Chapter 9, Common
Table 3-10 BSR
Parameter Name Parameter Description Value

BSR::enableTransportCAC This is a configurable true
attribute to enable transport
Call Admission Control.
BSR::enableAbwMeasure- true
ments

The following MOs are modified from the BSG, refer Chapter 9, Common
Table 3-11 BSG
Parameter Name Parameter Description Command

FGW::enableRTMonitoring This attribute controls the Set
enabling or disabling of the {enableRTMonitoring=
Real Time Monitoring feature False};
on the BSG.

The following MOs are modified from WMS Small Cells, refer Chapter 9, Common
Table 3-12 BSR

BSR::enableTransportCAC This is a configurable false
attribute to enable transport
Call Admission Control.
BSR::enableAbwMeasure- false
ments
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Impacted services
None
WPS Small Cells No
WMS Small Cells No

HDM No

Small Cell No
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No
System

None

NA
Downtime
NA
....................................................................................................................................................................................................................................
Issue 5 April 2014
Transport features 131828 - 2 ms TTI on E-DCH
....................................................................................................................................................................................................................................
131828 - 2 ms TTI on E-DCH

Overview
Feature 131828 introduces the capability to support 2 ms TTI and 2xSF2 + 2xSF4, with a
maximum potential physical layer rate of 5.7 Mbps. In order to support 2xSF2 + 2xSF4,
the Signaling Radio Bearer (SRB) must be mapped onto E-DCH.
Feature 131828 introduces the ability to support higher UL data rates on E-DCH.
The support of the higher E-DCH rates requires the following:
Small Cell hardware platform support
UE category support
High bandwidth backhaul support
Appropriate RF conditions
Optimized TCP/IP, RoT, and OLPC settings
Small Cell Solution supports all the six E-DCH categories from 3GPP TS25.306 Rel-6.
The following image describes the E-DCH capabilities of the different terminal types:
* In category 2, 2 ms TTI suboption is not supported, primarily due

to its limited benefit (throughput is reduced).
Note: The highlighted rows in the table describe the additional higher E-DCH rate UE
options that the feature facilitates.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Purpose
This topic describes the activation and deactivation procedures for 2 ms TTI on E-DCH
(131828) feature.

...................................................................................................................................................................................................
1 In the WPS Small Cells, locate the snapshot exported from WMS Small Cells. Import the
...................................................................................................................................................................................................
2 Navigate to the Femto > EDCH, set attribute eDCH2msActivation as True,

eDCHmaxCatPerf as 6 and maxEdchCellRate as 5740.
...................................................................................................................................................................................................
3 Navigate to BSR, set activateEDCH as True.

...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S

Managed objects in Small Cell
Table 3-13 BSR
Parameter name Description Syntax Value Default Permitted values

value
activateEDCH Flag to activate/deactivate boolean True True {True, False}

feature. If set as True,
E-DCH is activated in the
cell.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

value
eDCH2msActivation This parameter is used to boolean True False {True, False}

indicate whether 2 ms TTI in
E-DCH is activated. It
applies to Small Cells
supporting CAT 4 or 6 UEs.
Table 3-14 EDCH
Parameter name Description Syntax Value Default value Permitted

values
eDCHmaxCatPerf Determines the maximum uint16 6 3 [1..6]

E-DCH UE category
performance which may be
supported, capped to the
maximum capability of the
Small Cell platform.
maxEdchCellRate Maximum UL cell integer 5740 5740 [0..6000]
throughput for E-DCH, units=kbps
capped by the platform
capability.
Feature deactivation procedure

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to the Femto > EDCH, set attribute eDCH2msActivation as False.

...................................................................................................................................................................................................
3 Navigate to BSR, set activateEDCH as False.

...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S

Table 3-15 BSR
Parameter name Description Syntax Value Default Permitted

value values
activateEDCH Flag to activate/deactivate boolean False True {True, False}

feature. If set as False,
E-DCH is deactivated in the
cell.
eDCH2msActivation This parameter determines boolean False False {True, False}
whether 2ms TTI is
supported on the Small Cell
platform.
Impacted services
During activation there is disruption in connection with the BSR Gateway, hence calls are
dropped.
WPS Small Cells No

WMS Small Cells No
HDM No

Small Cell Yes Calls are dropped during activation
as the connection with BSR
Gateway is disrupted.
IPC No
IPsec Router No
BPG No
BVG No
BSG No
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
AAA No

System

Small Cell hardware version V1 does not support 2 ms TTI.
High rate E-DCH is supported only in an isolated cell configuration.
The peak E-DCH user data rate is reduced when combined with a simultaneous CS
voice call.
116495 - UL interferences management based on Tx power update, feature must be
enabled to support mesh scenarios.
Duration
NA
Downtime
None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Transport features 122468 - Satellite backhaul
....................................................................................................................................................................................................................................
122468 - Satellite backhaul

Overview
This feature enables using a satellite link for the backhaul system instead of using a DSL
line.
Note:
The deployment configuration for this feature is not plug and play.
122468 - Satellite backhaul is an optional feature.
Purpose
This topic describes the activation and deactivation procedures for Satellite backhaul
(122468) feature.
Before you begin

The operator must provide the following information to Alcatel-Lucent to analyze the
feasibility of the feature:
Table 3-16 Feature acceptance criteria
Sl Information required Mandatory

No. (M) or
Optional (O)
General information
1 Who are your satellite operator partners? M
2 Describe the footprint you provide around the world? M
3 Describe your HUBs architecture (star or mesh)? M
4 Describe your satellite equipment manufacturers (For example, M
manufacturers of the satellite modem equipment)?
Key technical information
1 Maximum throughput (DL and UL) parameters M
2 Minimum uplink bandwidth supported (A minimum of 120 kbps is M
required for one CS voice call. However, certain features can
optimize the uplink bandwidth in the satellite modem)
3 Maximum RTT value in good and poor weather conditions ( 700 M
ms)
4 Maximum jitter value in good and poor weather conditions ( 40 M
ms)
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 3-16 Feature acceptance criteria (continued)
Sl Information required Mandatory

No. (M) or
Optional (O)
5 Maximum packet loss value in good and poor weather conditions ( M
0.5 %)
6 Maximum MTU size (A minimum of 1500 bytes is required) M
7 Support of expedited data delivery for voice call M
8 Provide real-time bandwidth measurement M
9 Support of IPSec tunnel (critical) M
Performance information
1 Type of satellites supported (For example, bent-pipe, multiple spot, O
and shaped beams)
2 Frequency used by the satellites (Ka band preferred) O
3 EIRP MAP of your footprint areas O
4 Type of transmission to terminal (For example, HUB to satellite O
station, satellite station to HUB and whether the type of transmission
is MF-TDMA or SCPC at the Tx side)
5 Type of MODCOD used by the satellites (For example, QPSK or M
8-PSK)
6 Time to recover satellite link lost connection M
7 Minimum EIRP value for which MOS score for CS voice call is M
acceptable
QoS of the satellite modem
1 Number of priority service levels to classify SmallCell traffic (Five M
levels preferred)
2 Type of queuing management M
3 Number of and type of IP optimization options supported M
Additionally, the operator must also meet the following satellite backhaul requirements.
The following measurements must be obtained when the NTP is converging:
Maximum RTT (Femto-NTP server): 700 ms
Maximum RTT (Femto-GW): 700 ms
Maximum RTT (Femto-FMS): 700 ms
Maximum packet loss: 0.5 %
Maximum jitter: 40 ms
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Minimum guaranteed bandwidth (Femto-Gateway): 70 kbps per simultaneous call +
50 kbps for signaling
An MTU size of 1500 bytes.
Note:
With the specified values, the frequency accuracy will be +/- 250 ppb.
The Alcatel-Lucent service organization verifies the conformance of the
pre-requisites before the deployment of the feature.
The following configurations are required to ensure that the solution deployed has an
adequate voice quality:
General backhaul network configuration to ensure that all necessary ports are
available.
Satellite equipment configuration to ensure adequate QoS for voice calls, and to
ensure that any signaling and management traffic is sent in a timely fashion.
Small Cell equipment configuration to ensure operation over a satellite network (a
satellite network may be characterized as having higher latency, jitter, and packet loss
than a typical backhaul network, although any of these values could be high in other
types of backhaul network as well).
The following features must be disabled:
National location lock
All backhaul measurements features (disabled by setting BSR:enableULBWMea-
surements to FALSE)
Small Cell to Small Cell handover (as multiple Small Cells are not supported over
a single link)
See Managed objects involved in feature activation (p. 3-81) for information related
to attributes.
Hardware
The Small Cell CPE hardware version must be V2.x or higher.

There is no specific feature activation parameter for this feature. To start up the Small
Cell using a satellite backhaul, connect the Ethernet cable from the Small Cell to the
satellite modem. Use the appropriate software load for the Small Cell and download the
configuration file from the SCMS. The Small Cell then performs an NTP convergence so
that the oscillator can be disciplined over a high latency, high jitter connection. Some
attributes must be modified to ensure that the feature functions appropriately.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to Network > profile > BSRProfile . Set attribute maximumAllowedNtpJit-

ter as 1000000 and enableOutgoingFemtoHandover as FALSE.
...................................................................................................................................................................................................
3 Navigate to Network > FemtoCluster > Femto. Set attributes nationalLocation-

LockEnabled and enableULBWMeasurements as FALSE.
...................................................................................................................................................................................................
4 Click Run checks... on the Femto.

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S

Table 3-17 BSR
Parameter Description Syntax Default value Permitted Values

name values
maximu- The oscillator integer 40000 [40000..1000000]

1000000
mAl- disciplining algorithms
lowedNt- uses windows of packets.
pJitter If the jitter exceeds this
value, the window will
not be used for oscillator
disciplining.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

name values
enableOut- Activates / deactivates boolean False {True, False

goingFem- Small Cell to Small Cell False}
toHan- handover.
dover
national- Enables/Disables the boolean False {True, False

Location- National location lock False}
LockEn- (78230) feature.
abled
enableUL- Activates / deactivates boolean False {True, False
BWMea- backhaul measurements False}
surements

Table 3-18 BSR

name values
maximu- The oscillator integer 40000 [40000..1000000]

1000000
mAl- disciplining algorithms
lowedNt- uses windows of packets.
pJitter If the jitter exceeds this
value, the window will
not be used for oscillator
disciplining.
enable- Activates / deactivates boolean False {True, True

Outgoing- Small Cell to Small Cell False}
Femto- handover.
Handover
national- Enables/Disables the boolean False {True, True

Location- National location lock False}
LockEn- (78230) feature.
abled
enableUL- Activates / deactivates boolean False {True, True
BWMea- backhaul measurements False}
surements
Impacted services
None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
WPS Small Cells No
WMS Small Cells Yes

HDM No

Small Cell Yes
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No
System

The satellite backhaul feature has the following limitations:
The satellite backhaul feature does not support the following features:
National location lock
Backhaul measurement
Small Cell to Small Cell handover
This feature is supported only on the V2 version of the Small Cell hardware.
Duration
Approximately 90 minutes.
Downtime
Upgrading the Small Cell software version to 3.031 or higher and NTP convergence may
result in a downtime of approximately 90 minutes.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
4 S4mall Cell specific
features
Overview
Purpose
This chapter describes the activation/deactivation procedure for the Small Cell specific
features.
Contents
75545 - GPS localization 4-3

104564 - SCMS support of GPS localization locking 4-6
113610 - Support for assisted GPS 4-14
109515 - Internet breakout at CPE 4-17
83062 - Fault Management support of NTP server 4-22
83241 - Fault Management support of AAA 4-28
83249 - Launch point to AAA and NTP server 4-36
114578 - SCMS 2.4 support of SAM 7.0 4-38
84181 - All-in-one BSR Gateway 4-41
83087 - Distributed SS7 4-47
84990 - SCMS support of BSR Gateway 4-55
96373 - FM support for DNS/ToD functions 4-59
120359 - HDM alarm management in WMS Small Cells for Small Cell 4-62
119109 - Meinberg NTP integration 4-65
117813 - Small Cell Access Point capacity licensing 4-68
114014 - Active-Warm standby BSR Gateway redundancy 4-72
120353 - RTCP for IuCSoIP 4-79
78594 - Small Cells network support for End-to-End call subscriber trace 4-82
...................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features Overview
....................................................................................................................................................................................................................................
119110 - Static IP address 4-90

157214 - PPPoE configuration 4-94
119911 - Assisted GPS using proprietary TCS solution 4-98
123830 - UE-based Assisted GPS 4-105
125544 - AMR frame concatenation with preemption 4-110
158467 - 32 PS user capacity for V2 Enterprise and Metro AP 4-121
76986 - Cell broadcast services in support of CMAS 4-124
124168 - DPDK support on BSR Gateway 4-130
117826 - Multiple Operator Core Network 4-133
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 75545 - GPS localization
....................................................................................................................................................................................................................................
75545 - GPS localization

Overview
GPS localization introduces the capability of the Small Cell to localize itself using simple
GPS method.
Purpose
This topic describes the activation and deactivation procedures for GPS localization
(75545) feature for the Small Cell.

To configure the GPS localization feature through WPS Small Cells
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Set the attributes, gpsScanOnBoot and geographicalLocationConfigured,

available under pre-provision data of Small Cell, as TRUE.
...................................................................................................................................................................................................
3 Perform Run checks... on the FemtoCluster.

...................................................................................................................................................................................................

...................................................................................................................................................................................................
Create new Session.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
The following objects are involved in the activation of GPS localization at the WMS
Small Cells:
Table 4-1 GPS

comment
GPS:: ScanOnBoot Enables or disables GPS scans True

during the Small Cell startup.

The following objects are involved in the deactivation of GPS localization at the WMS
Small Cells:
Table 4-2 GPS

comment
GPS:: ScanOnBoot Enables or disables GPS scans False

during the Small Cell startup.
WPS Small Cells No

WMS Small Cells No
HDM No
Small Cell Yes Once enabled, the Small Cell must

be rebooted so the location is
identified based on the GPS
functionality.
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No

System
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
None.
Duration for Activation and Deactivation

The activation/deactivation of GPS localization can be done in a fraction of a second
without interrupting any other services.
Impacted services
Activating/deactivating this feature has no impact on any service. The configuration is
dynamic.
Downtime
Once the feature is enabled, the Small Cell is rebooted, so the location is identified.
Hence, there is a downtime, of less than 5 minutes during reboot.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 104564 - SCMS support of GPS localization locking
....................................................................................................................................................................................................................................
104564 - SCMS support of GPS localization locking

Overview
The GPS localization feature (75545) introduces the capability for the Small Cell to
localize itself using simple GPS method. This SCMS feature supports location locking
described in the feature 75545.
The Small Cell is provisioned as done in the actual release. For location-based
auto-configuration, the coordinates provided by the operator are used as a reference.
GPS is only used for location checking and emergency calls by the Small Cell.
The SCMS is synchronized by the Small Cell inform message or on demand, with the
geographical coordinates obtained by the GPS and sent by the Small Cell. These GPS
geographical coordinates are not part of the input to the auto-configuration algorithm.
Purpose
This topic describes the activation and deactivation procedures for the SCMS support of
GPS localization locking (104564) feature through WPS Small Cells.
Before you begin

Before you log in to WPS Small Cells, perform the following checks:
Navigate to Network > profile > BSRProfile > GPS, ensure that the attribute
enableGPSLocationCheck is set as TRUE.
Navigate to Network > FemtoCluster > Femto > Edition, ensure that the attributes
gpsScanOnBoot and geographicalLocationConfigured are set as TRUE.

To configure the GPS feature through the WPS Small Cells
Perform the following steps, to configure the GPS feature:
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Modify the attribute enableGPSLocationCheck available in the GPS attribute under

BSRProfile.
...................................................................................................................................................................................................
3 Perform Run checks... on the network.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
4 Create a work order and copy it to the WMS Small Cells.

...................................................................................................................................................................................................
5 In the WMS Small Cells, navigate to Configuration > Sessions Manager > Create New
Session to launch the work order.
...................................................................................................................................................................................................
6 Restart the Small Cell to verify the registration request from the Small Cell to the HDM,
which is then forwarded to WMS Small Cells.
...................................................................................................................................................................................................
7 Check if the Small Cell is active in HDM. And also, if it has the corresponding
BulkCM.xml file from the fileserver.
...................................................................................................................................................................................................
8 In the WMS Small Cells, navigate to Configuration > Object Editor modify any of the
GPS parameter values for this corresponding Small Cell and Apply All Changes.
...................................................................................................................................................................................................
9 Execute the Bulk Set online command, to trigger the CM download and update the
corresponding changes to this Small Cell.
...................................................................................................................................................................................................
10 To verify these changes in the HDM, navigate to Device Information > Queued
Functions > Queue Function and select Get Parameter Values from the Function
drop-down list.
E...................................................................................................................................................................................................
N D O F S T E P S

The following objects are involved in the activation of the Small Cell:
Table 4-3 /FemtoCluster:<DN>/Femto<instance>:
latitude Defines the

latitudinal position
of the network
element.
longitude Defines the
longitudinal position
of the network
element.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 4-3 /FemtoCluster:<DN>/Femto<instance>: (continued)
uncertaintyRadius Indicates the [0..50000]

uncertainty radius of unit=meters
the Area Identity
supported. This
parameter is
required if RANAP
LOCATION
REPORTING
CONTROL includes
Accuracy Code IE.
areaIdentityGA If the Geographical

Area is requested for
Reporting Area in
the RANAP
LOCATION
REPORTING
CONTROL, this
parameter indicates
the Area Identity
used. Area Identity
supported is Point,
Point with
uncertainty and
Polygon3pt
locationReportGA This provides the
geographical
coordinates required
if Geographical Area
with Polygon3pt is
requested.
Table 4-4 /Profile:<DN>/BSRProfile:<DN>/GPS<instance>:

comment
ScanOnBoot Enables or disables

GPS scans during the
Small Cell start up.
enableProvisioned- Enables Small Cell to False

LocationReport report provisioned
location rather than
GPS location.
enableAllowedGP- Enables the Small True

SAfterTimerEx- Cell GPS function,
pired even if the GPS
receiver fails to fix
the timer, within the
time specified.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 4-4 /Profile:<DN>/BSRProfile:<DN>/GPS<instance>: (continued)

comment
enableGPSLoca- Enables use of GPS True

tionCheck Location check
otherwise fall back to
non-GPS location and
movement checks.
enableNonGPSLo- Enables use of True
cationCheckFor- non-GPS location
FailGPSInitialStar- check if GPS receiver
tup fails to return a
geographical location
at initial startup.
enableNonGPSLo- Enables use of True
cationCheckFor- non-GPS movement
FailGPSSubse- check if GPS receiver
quentStartup fails to return a
geographical location
at subsequent startup.
LastSuccess- Specifies the date and
fulScanTime time, when the GPS
scan last-completed
successfully. This
value is retained
during resets. The
values for
LockedLatitude,
LockedLongitute and
NumberOfSattelites
correspond to this
time. If a scan has
never succeeded
before, the value is
the Unknown Time
value, as defined in
TR-106a2 [4] Section
3.2.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

comment
LockedLatitude This parameter -11241629

specifies the actual [-90000000 ..
location of the FAP, 90000000 ]
returned by the GPS
Diagnostics Test. This
parameter specifies
the latitude position of
the device 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)+
((19.43*1,000,000)/
60). Latitude of
500.00 S would be
represented as value
-50,000,000. This
value is retained
during resets and is
only reset after
another scan
completes
successfully. If a scan
has never succeeded
before, the value 0 is
reported.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

comment
LockedLongitude This parameter -35885969

specifies the actual [-180000000..180000000]
location of the FAP,
returned by the GPS
Diagnostics Test. This
parameter specifies
the longitude position
of the device, 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
during resets and is
only reset after
another scan
completes
successfully. If a scan
has never succeeded
before, the value 0 is
reported.
lockedHorizonta- The location accuracy 4

lAccuracy provided by the GPS
receiver.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

comment
horizontalPosition- The distance between 12141381

Difference the GPS detected
location (defined by
GPS::lockedLatitude
and
GPS::lockedLongi-
tude) and the
Authorised Small Cell
Location (defined by
BSR::latitude and
BSR::longitude)
authorisedLoca- Maximum radius of 65 [1..100]
tionRadius the provisioned Small
Cell location allowed.
scannedLocation- Minimum accuracy 15 [1100]
Accuracy required by GPS
receiver when it
scanned it location.
scanTimeoutInital- Maximum time 1200 [1..65000]
Startup allowed for the GPS
to provide location to
requested accuracy at
initial startup.
scanTimeoutSubse- Maximum time 120 [1..65000]

quentStartup allowed for the GPS
to provide location to
requested accuracy at
subsequent startup.

To deactivate SCMS synchronization with the geographical coordinates obtained by the
GPS sent by the Small Cell, firstly the related attribute must be disabled. To disable, set
the enableGPSLocationCheck value as FALSE.
The objects involved in the deactivation of the Small Cell are:
Table 4-5 Profile:<DN>/BSRProfile:<DN>/GPS<instance>:
enableGPSLoca- Enables use of GPS False

tionCheck Location check
otherwise fall back to
non-GPS location
and movement
checks.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Impacted services
None
WPS Small Cells No
WMS Small Cells Yes

HDM Yes GPS Location parameters change
according to Small Cell values.
HDM adaptation layer Yes There is a GPS reporting
mechanism.
Small Cell Yes GPS Location parameters change

according to GPS values.
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No
System

None.
Downtime
Changing profiles requires a new Bulk CM creation and this results in downtime.
Note: Changing a profile impacts all other Small Cells using the same profile.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 113610 - Support for assisted GPS
....................................................................................................................................................................................................................................
113610 - Support for assisted GPS

Overview
This feature introduces the capability of the Small Cell to support assisted GPS.
Purpose
This topic describes the activation and de-activation procedures, objects involved for the
feature, Support for assisted GPS (113610).
Related information
From the Small Cell, the activation and deactivation of the feature is through the WPS
Small Cells.
Before you begin

Ensure that the GPS localization (75545) feature is enabled.

To configure the support for assisted GPS feature through the WPS Small Cells
Perform the following steps to configure the support for assisted GPS feature through the
WPS Small Cells.
...................................................................................................................................................................................................
snapshot into the WPS Small Cells.
...................................................................................................................................................................................................
2 Modify the attribute enableAGPS available under the BSRClusterProfile data of

FemtoCluster.
...................................................................................................................................................................................................
3 Perform Run checks on the FemtoCluster.

...................................................................................................................................................................................................
4 Create a WorkOrder and copy into the WMS Small Cells.

...................................................................................................................................................................................................
Create new Session.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
Managed objects in feature activation

Table 4-6 /FemtoCluster:<DN>/BSRClusterProfile:<DN>/AGPS<instance>
Parameter name Description Syntax Value Additional comment
enableAGPS Enables support for Assisted enum suplServer or Attribute modified

GPS and specifies AGPS AgpsServer- proprietarySer- from
server type. Type ver (depending BSRClusterProfile>AGPS
on commercial MO of FemtoCluster
Assisted GPS or
u-blox for trial)
serverAddress Contains the IP Address as a string length=128

dotted decimal value or
FQDN of the assisted GPS
server
serverAddressSec- Contains the IP Address as a string length=128
ondary dotted decimal value or
FQDN of a secondary assisted
GPS server
serverCertificate Contains the Certificate used bin.hex length=4096,

by the AGPS Client to min=0
Authenticate the AGPS Server
serverPort Specifies the TCP port used integer [0..65535]

for the assistance protocol

Table 4-7 enableAGPS
Parameter name Description Syntax Value Additional comment
enableAGPS Enables support for Assisted enum disabled Attribute modified from
GPS and specifies AGPS AgpsServer- BSRCluster
server type. Type Profile>AGPS MO of
FemtoCluster
Impacted Services
There is no impact on any service on activation/deactivation of this feature. It is a
dynamic configuration.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
WPS Small Cells No
WMS Small Cells No

HDM No

Small Cell Yes Once enabled, Small Cell must be
rebooted, so the location is identified
based on the assisted GPS
functionality.
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No
System

None.
Duration
The activation/deactivation of support for assisted GPS can be done in a fraction of a
second without interrupting any other services.
Downtime
Whenever BSRClusterProfile attributes are modified, Small Cell must be rebooted, to
verify the functionality of the feature. Hence there is a downtime of less than 5 minutes
during reboot.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 109515 - Internet breakout at CPE
....................................................................................................................................................................................................................................
109515 - Internet breakout at CPE

Overview
The feature internet breakout at CPE (109515) is an extension of the home network local
routing (75399) feature, which provides the packet forwarding ability of the Small Cell to
include datagrams addressed to non-local IP addresses.
Feature 75399 provides a home network local routing solution for the Small Cell network.
It provides sufficient local IP network connectivity to support commonly used network
discovery and transport protocols.
With feature 75399, Small Cell provides the UE with an interface to the local network.
This interface comprises a Layer 2 Ethernet interface and Layer 3 IP address. The Small
Cell manages these interfaces on behalf of the UE, and bridges the user IP traffic between
a particular PS bearer in the radio interface of the UE and the Layer2 Ethernet interface.
The UE PS radio bearer is identified by detecting the use of a particular APN during
activation of the associated PDP Context.
The Small Cell provides the packet forwarding intelligence to route uplink user datagrams
to hosts in the local network or to the local router for forwarding through the ISP network
to host in the wider internet.
Purpose
This topic describes the activation and deactivation procedures for Internet breakout at
CPE (109515) feature through the Small Cell and IPC.
Before you begin

From the Small Cell, the activation and deactivation of the feature is through WPS Small
Cells.
Before you begin, ensure that:
The Small Cell is up and running and is able to make CS/PS calls.
The WMS Small Cells is available to make the BulkCM changes.

...................................................................................................................................................................................................
1 Refer Chapter 9, Common Configuration Procedures

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Managed objects in the Small Cell
Table 4-8 BSR
Parameter Description Default Syntax Value Permit-

name value ted
values
enableLocal- The flag to enable/disable the Local Network False bool- True
Routing Routing feature. ean
maxNum- The maximum number of UE Directory entries 0 integer 256
berOfUEDi- that are stored in the Small Cell.
rectoryEn-
tries
LocalRoutin- The APN which the Small Cell. substitutes for string ti-hnlr length=
gReplace- the localRoutingAPN in an Activate PDP 100The
mentAPN Context Request message received from a UE Local-
.If this attribute is not empty, and the APN Routin-
present in the Activate PDP Context Request gRe-
message, matches one of those in the place-
localRoutingAPN array, the APN in the men-
Activate PDP Context Request message is tAPN is
replaced with the localRoutingReplace- config-
mentAPN. If this item is not present the APN in ured at
the Activate PDP Context Request is not the CN
altered. for
Inter-
net
break-
out.
LocalRout- When set as True, the uplink frames bearing IP True bool- True { True,
ingPassLo- traffic with a destination address in the local ean False }
calTraffic network is passed to the local network.
Downlink frames bearing IP traffic with a
source address in the local network is passed to
the UE. When set as False, this local traffic is
discarded by the Small Cell.
localRouting- This parameter specifies the IP address as ipAd-

GTPUmain- dotted decimal value of the network local dress
tenaceIC- routing ICMP Echo server. If it is set as zero
MPEcho- (or not present) the DNS server supplied by the
Server GGSN is used instead.
localRout- Used to send ICMP echo by means of GTP-U 0
ingTPU- regularly, to maintain Local Routing PDP
Maintenance- Context with the core network. If the value is 0
Timer ICMP Echo is not used to maintain GTP-U.
localRouting- The three most significant octets of the MAC FE0000 bin.hex FE0000 [3..]
MACad- address, assigned to UEs receiving Local length=3
dressOctects Routing service.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Parameter Description Default Syntax Value Permit-

name value ted
values
enableLocal- When set as True, the Small Cell pages a False bool- False { True,
RoutingFor- PMM Idle mode UE to change to PMM ean False }
wardMulti- Connected mode and deliver multicast, or
castInIdle broadcast frames from the local network.
Otherwise, the UE is changed to PMM
Connected when a directly addressed frame is
received for the UE. The local network can
have significant volumes of multicast/broadcast
traffic, enabling this parameter can adversely
affect battery life of the UE.
enableLocal- Set as True to permit only users with IMSIs in True bool- True { True,
RoutingPri- the Small Cell Access Control List to activate a ean False }
oritizedAc- Home Network Local Routing Context. Set as
cess False to permit all users to activate a Local
Routing Context.
localRouting- Defines the amount of time in seconds the 20 integer 20 [5..3600]

PagingRe- Small Cell waits for a paging response when it units=
sponseWait- has paged a UE for Local Routing. secs
Time
localRouting- Defines the number of repeat attempts for 3 integer 3 [0..10]
PagingRe- paging that a Small Cell performs for UE Local
peatAttempts Routing.
Table 4-9 BSR: localRoutingAPN
LocalRoutingAPN The APN for which any string. Example: This APN is not
the Small Cell iprc-hnlr known to the CN
provides the Local but configured at the
Routing service. UE.
List of APNs for which the Small Cell provides the Local Routing service, depending on
the sense of the localRoutingOnAPNmatch flag. The UE includes the desired APN in
the Activate PDP Context Request message at PS bearer start. A wildcard APN string
ALL_APN can be used. If an ALL_APN is present in any of localRoutingAPN array
elements, then a bearer activated on any APN is considered to match the APN list. A
special APN string APN_NOT_PRESENT can be used to match a bearer activated without
an APN.
Note: Small Cell supports up to 5 APNs. Based on the requirement, the user can
create up to 5 localRoutingAPN MOs under BSR and provide APN Strings.
At least one APN must be set to make this feature functional.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Managed objects in the IPC
Table 4-10 BSR: localRoutingPassNetworkList
networkIpAddress The IP address part 0.0.0.0

of a network address
netMask The net mask length 0
List of up to 20 network addresses and netmasks that the Small Cell passes. All other
traffic is dropped. Examples: 0.0.0.0/0 specifies the entire internet. 1.2.3.4/32 specifies an
individual IP address. If the list is empty all traffic is dropped. The localRouting-
PassLocalTraffic is independent of thelocalRoutingPassNetworkList.
Note: If an operator wants to have different network address and netmask, the
required number of localRoutingPassNetworkList MOs must be created for
each of them under BSR.

Table 4-11 BSR
enableLocalRouting The flag to False

enable/disable the
Local Network
Routing feature.
Impacted services
There is no impact on any service on activation/deactivation of this feature. As the
attributes are not of type RW-RR.
WPS Small Cells No
WMS Small Cells No
HDM No
Small Cell No
IPC No
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
IPsec Router No
BPG No
BVG No
BSG No
AAA No

System

None.
Duration
The activation/deactivation of internet breakout at CPE can be done in a fraction of a
second without interrupting any other services.
Downtime
None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 83062 - Fault Management support of NTP server
....................................................................................................................................................................................................................................
83062 - Fault Management support of NTP server

Overview
WMS Small Cells provides integrated Fault Management support of the Network Time
Protocol (NTP) server. The following are the key benefits of this feature:
Device discovery
NSP layouts
First alert Fault Management (in both Resource Browser and Alarm Manager)
Support of northbound CORBA Fault and NE Discovery OSS Interfaces
Integrated online help:
in context of the adequate fault clearance procedure, upon request from the user
using the alarm browser
user guide accessible online from the NSP GUI
Alarms from the NTP server are managed by the existing WMS Small Cells toolset. And
it supports:
The 9-alarm rule-set (inhibit, send SMS, send E-mail, change severity, and so on).
The trouble ticketing interface.
The alarm browser.
The managed and unmanaged alarm stream.
The various resources browsers (topological, grid, and matrix).
The 3GPP R6 FM IRP is supported for the NTP server. And an integrated online alarm
help is provided.
The NTP servers are deployed in a DUAL configuration mode, with one server active and
the second as a standby. This configuration offers best resilience against failures.
Purpose
This topic describes the activation and deactivation procedures for the Fault Management
support of NTP server (83062) feature.

...................................................................................................................................................................................................
1 The feature is activated using WPS Small Cells (refer To configure through the WPS
Small Cells (p. 4-23)) and NTP server (refer To configure using NTP server (p. 4-25)).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
To configure through the WPS Small Cells
...................................................................................................................................................................................................
snapshot into WPS Small Cells
...................................................................................................................................................................................................
2 Create an NTP server network element object under the Small Cell cluster.
...................................................................................................................................................................................................
3 Provide the NTP Device IP address and SNMP Port number, used by the NTP server to
listen for the SNMP messages.
...................................................................................................................................................................................................
4 Log in to the WMS Small Cells terminal as the oamops user.

...................................................................................................................................................................................................
5 Navigate to /opt/nortel/shell/wicl/scripts/encrypt/ and execute the command:

./encrypt.tcl -entity SNMP -secret <password-string1>
Example:
bash-3.00# ./encrypt.tcl -entity SNMP -secret iprcnltntp801
968f8d9c91938b918b8fc7cfce (hexadecimal numbers)
...................................................................................................................................................................................................
6 Repeat step 5 to generate another password string.

...................................................................................................................................................................................................
7 In the WPS Small Cells, navigate to NTP/0 > SNMPParamv3/0 >

USMSecurityModelParam/0.
...................................................................................................................................................................................................
8 Set the attributes, authPassword and privPassword with the 2 generated encrypted
passwords.
...................................................................................................................................................................................................
9 Create a WorkOrder and copy to the WMS Small Cells, to create this NTP network
element.
Sample work order - NTP_example.xwo
<?xml version='1.0' encoding='UTF-8'?>
<workorders>
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
<workorder name="new workorder" creationDate="2011-02-07 04:
09:07.371 -0500" originator="" description="">
<Cluster id="UMAINSERV1" model="OAM" version="OAM" clusterId=
"UMAINSERV1" method="create"/>
<NTP id="0" model="OAM" version="OAM" clusterId=
"UMAINSERV1" method="create">
<attributes>
<clusterId>Cluster/UMAINSERV1</clusterId>
</attributes>
<SNMPParamv3 id="0" method="create">
<attributes>
<DeviceIpAddress>172.60.120.4</DeviceIpAddress>
<DeviceIpport>161</DeviceIpport>
</attributes>
<USMSecurityModelParam id="0" method="create">
<attributes>
<authPassword>968F8D9C91938B918B8FC7CFCE</
authPassword>
<privPassword>968F8D9C91938B918B8FC7CFCE</privPassword>
</attributes>
</USMSecurityModelParam>
</SNMPParamv3>
</NTP>
</workorder>
</workorders>
Sample reverse work order - NTP_example_reverse.xwo
<workorders>
<workorder name="new workorder_reverse" creationDate="2011-02-
07 04:09:07.371 -0500" originator="" description="">
"UMAINSERV1" method="delete"/>
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
<NTP id="0" model="OAM" version="OAM" clusterId="UMAINSERV1"
method="delete">
<SNMPParamv3 id="0" method="delete">
<USMSecurityModelParam id="0" method="delete"/>
</SNMPParamv3>
</NTP>
</workorder>
</workorders>
...................................................................................................................................................................................................
10 FTP the new workorder file into WMS Small Cells, under /opt/nortel/data/cmXML.
...................................................................................................................................................................................................
11 Launch the WorkOrder in WMS Small Cells, using Configuration > Sessions Manager >
Create new Session.
E...................................................................................................................................................................................................
N D O F S T E P S
To configure using NTP server

...................................................................................................................................................................................................
1 Log in to the NTP server GUI as an admin user.

...................................................................................................................................................................................................
2 In the Config tab, fill in the following the SNMP details of the WMS Small Cells server:
Under Trap > Destination, providing the IP address of the WMS Small Cells server
and select the version as v3.
Enter the following information for the v3User tab:
UserName : FMS
AuthPhrase :
< value provided for authPassword while configuring NE in
FMS >
AuthCrypt : MD5
Priv Phrase :
< value provided for privPassword while configuring NE in
SCMS >
PrivCrypt : AES
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Min Priv : select < Auth and Privacy to ensure the user applies
the authentication phrase and the private phrase to login >.
Save the configuration.
E...................................................................................................................................................................................................
N D O F S T E P S
Additional Information
By default the alarm profile for NTP server, has the null trap notification
disabled. So the alarm profile must be configured, to enable the NTP server forward the
traps to the configured trap destinations, that is the WMS Small Cells server.
Perform the following steps to configure the Alarm profile:
1. In the Alarm profile table, select send Trap for all the traps. This ensures transfer of
all the traps to the WMS Small Cells server.
Note: A new FMS user must be created at the NTP server whenever the NTP server is
restarted, to manage the communication between the NTP server and WMS Small
Cells.
Deactivation procedure
This feature cannot be deactivated.
Impacted services
None
NTP server Yes

WPS Small Cells Yes
WMS Small Cells Yes
HDM No

Small Cell No
IPC No
IPsec Router No
BPG No
BVG No
BSG No
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
AAA No

System

NA

NA
Downtime
NA
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 83241 - Fault Management support of AAA
....................................................................................................................................................................................................................................
83241 - Fault Management support of AAA

Overview
WMS Small Cells provides integrated Fault Management support of the AAA. The
following are the key benefits of this feature:
Device discovery
NSP layouts
First alert Fault Management (in both Resource Browser and Alarm Manager)
Integrated online help:
in context of the adequate fault clearance procedure, upon request from the user
using the alarm browser
user guide accessible online from the NSP GUI
Alarms from the external AAA are handled and managed by the existing WMS Small
Cells toolset. And therefore, supports:
The 9 alarm rule-set (inhibit, send SMS, send E-mail, change severity, and so on).
The trouble ticketing interface.
The alarm browser.
The managed and unmanaged alarm stream.
The various resources browsers (topological, grid and matrix).
The 3GPP R6 FM IRP is supported for AAA. And an integrated online alarm help is
provided.
The AAA servers are deployed in a dual load balancing configuration, and the link
between AAA and WMS Small Cells is monitored to give the operator a view of the
availability of the AAA.
The access point to the AAA is contextual, meaning that the CLI or the LMT of the
selected device opens (as opposed to open a CLI or LMT interface and then to connect to
the network element).
This access point capability is applicable to AAA devices.
Automatic credential (login, password) request is not done.
Purpose
This topic describes the activation and deactivation procedures for the Fault Management
support of Alcatel-Lucent 8950 AAA (AAA) (83241) feature.
Related information
The feature is included in the WMS Small Cells release by default.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1 This feature is activated using both, the AAA (refer To configure using AAA (p. 4-31))
and WMS Small Cells (refer To configure using WMS Small Cells (p. 4-29)).
E...................................................................................................................................................................................................
N D O F S T E P S
To configure using WMS Small Cells

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Create a AAA network element object under the Small Cell Cluster.
...................................................................................................................................................................................................
3 Provide the AAA Device IP address and SNMP port number, used by the AAA to listen
for the SNMP messages.
...................................................................................................................................................................................................
4 Log in to the WMS Small Cells terminal as an oamops user.

...................................................................................................................................................................................................
5 Navigate to /opt/nortel/shell/wicl/scripts/encrypt/ and execute the command:

./encrypt.tcl -entity SNMP -secret <password-string1>
Result: Example:
bash-3.00# ./encrypt.tcl -entity SNMP -secret iprcnltaaa801
968f8d9c91938b9e9e9ec7cfce (hexadecimal numbers)
...................................................................................................................................................................................................
6 Repeat Step 5 to generate another password string.

...................................................................................................................................................................................................
7 In the WPS Small Cells, navigate to AAA/0 > SNMPParamv3/0 >

USMSecurityModelParam/0.
...................................................................................................................................................................................................
8 Set the attributes, authPassword and privPassword with the 2 generated encrypted
passwords.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
9 Create a WorkOrder and copy it to the WMS Small Cells, to create this AAA network
element.
Sample work order - AAA_example.xwo
<workorders>
<workorder name="new workorder" creationDate="2011-02-07 04:46:
43.535 -0500" originator="" description="">
<AAA id="0" model="OAM" version="OAM" clusterId="UMAINSERV1"
method="create">
<attributes>
<clusterId>Cluster/UMAINSERV1</clusterId>
</attributes>
<SNMPParamv3 id="0" method="create">
<attributes>
<DeviceIpAddress>172.62.112.9</DeviceIpAddress>
<DeviceIpport>161</DeviceIpport>
</attributes>
<USMSecurityModelParam id="0" method="create">
<attributes>
<authPassword>968F8D9C91938B9E9E9EC7CFCE</authPassword>
<privPassword>968F8D9C91938B918B8FC7CFCE</privPassword>
</attributes>
</USMSecurityModelParam>
</SNMPParamv3>
</AAA>
"UMAINSERV1" method="create"/>
</workorder>
</workorders>
Sample reverse work order - AAA_example_reverse.xwo
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
<workorders>
<workorder name="new workorder_reverse" creationDate="2011-02-
07 04:46:43.535 -0500" originator="" description="">
<AAA id="0" model="OAM" version="OAM" clusterId="UMAINSERV1"
method="delete">
<SNMPParamv3 id="0" method="delete">
<USMSecurityModelParam id="0" method="delete"/>
</SNMPParamv3>
</AAA>
</workorder>
</workorders>
...................................................................................................................................................................................................
10 FTP the new workorder file into WMS Small Cells, under /opt/nortel/data/cmXML.
...................................................................................................................................................................................................
11 Launch the WorkOrder in WMS Small Cells, using Configuration > Sessions Manager >
Create new Session.
E...................................................................................................................................................................................................
N D O F S T E P S
To configure using AAA

...................................................................................................................................................................................................
1 Log in to the AAA Service Management Tool GUI as an admin user.

...................................................................................................................................................................................................
2 Navigate to Configuration Tools > Server Properties > Policy Server > SNMP. Enter the
following the SNMP details of the AAA server:
For SNMP Address provide the SNMP IP address and the SNMP port number (used by
AAA to listen to SNMP messages), separated by :.
Save the configuration.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Navigate to Configuration Tools > 8950 AAA Operators > SNMP V3 Users and enter the
following values:
User Name : FMS
Security Transforms, select AuthMD5PrivAes.
Authentication Pass Phrase : Use the authPassword value used previously.
Privacy Pass Phrase : Use the privPassword value used previously.
Minimum Security for Local : authPriv
Local MIB Access : select Read Only.
...................................................................................................................................................................................................
3 Navigate to Logging Tools > Log Channels, edit the existing log channel. Set the
Destination as <WMS Small Cells IP address:SNMP port>
...................................................................................................................................................................................................
4 Navigate to Logging Tools > Log Channels > ALU_Femto_Alerts, enter the following
value:
Oid : 1.3.6.1.4.1.831.1.1.1
Version : SnmpV3
Operation : Trap
SnmpV3 User name : FMS
SnmpV3 Security Use : authPriv
SnmpV3 Security Methods : AuthMD5PrivAes
SnmpV3 Auth Password : password-string1 used in Step 5
SnmpV3 Priv Password : password-string2 used in Step 5
Server Address : Provide the WMS IP address and SNMP port no separated by : (
example, 172.210.221.111).
Format Timestamp : Yes
Format Thread : Auto
...................................................................................................................................................................................................
5 Navigate to Logging Tools > Log Rules > Active Log Rules and create a new rule. Enter
the following values:
Log Area : alarm
Channels : ALU_Femto_Alerts
Select Make Rule Active.
...................................................................................................................................................................................................
6 Navigate to the Policy Server tab and Restart.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
To configure alerts
...................................................................................................................................................................................................
1 Navigate to Configuration Tools > Alerts.

...................................................................................................................................................................................................
2 Select the Low Disc Space alert. Edit the Description field, add a preceding :
followed by a , example : Low Disc Space.
Result: Example of Low Disk Space Alert Message:
2010/02/18 15:29:16.571 (Warning) Alert on for Disk Space -
<GLOBAL> > - Usable Space, 26.42 billions of bytes is below
26.84 billions of bytes: Low Disk Space.
...................................................................................................................................................................................................
3 Select the Queue Depth Warning alert. Edit the Description field, add a preceding :
followed by a , example : Queue Depth Warning.
Result: Example of Queue Depth Warning Alert Message:
2010/02/21 14:41:00.600 (Warning) Alert on for Queue
Statistics - Work-Normal - Queue Depth Count, 748.22 elements/
second is above 100 elements/second: Queue Depth Warning
...................................................................................................................................................................................................
4 Select the Database Response Latency alert. Edit the Description field, add a
preceding : followed by a , example : Database Response Latency.
Result: Example of Database Response Latency Alert Message:
2010/02/21 14:49:49.699 (Warning) Alert on for Method
Statistics - read-database.getUser:: TOTAL time / TOTAL
count, 745.63 thousandths of milliseconds per call is below 1
milliseconds per call: Database Response Latency
...................................................................................................................................................................................................
5 Select the Database Read Error alert. Edit the Description field, add a preceding :
followed by a , example : Database Read Error.
Result: Example of Database Read Error Alert Message:
Statistics - read-database.getUser:: ERROR count / TOTAL
count, 1 calls per call is above 100 thousandths of calls per
call: Database Read Errors
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
6 Select the LDAP Response Latency alert. Edit the Description field, add a preceding
: followed by a , example : LDAP Response Latency .
Result: Example of LDAP Response Latency Alert Message:
Statistics - read-Ldap.getUser:: TOTAL time / TOTAL count,
745.63 thousandths of milliseconds per call is below 1
milliseconds per call: LDAP Response Latency
...................................................................................................................................................................................................
7 Select the LDAP Read Errors alert. Edit the Description field, add a preceding :
followed by a , example : LDAP Read Errors.
Result: Example of LDAP Read Errors Alert Message:
Statistics - read-ldap.getUser:: ERROR count / TOTAL count, 1
calls per call is above 100 thousandths of calls per call:
LDAP Read Errors
...................................................................................................................................................................................................
8 Select the MAP GW Response Latency alert. Edit the Description field, add a
preceding : followed by a , example : MAP GW Response Latency.
Result: Example of MAP GW Response Latency Alert Message:
Statistics - read-eapaka.readMapGateway: TOTAL time / TOTAL
count, 745.63 thousandths of milliseconds per call is below 1
milliseconds per call: MAP GW Response Latency
...................................................................................................................................................................................................
9 Select the MAP GW Read Errors alert. Edit the Description field, add a preceding :
followed by a AA, example : MAP GW Read Errors.
Result: Example of MAP GW Read Errors Alert Message:
Statistics - eapaka.readMapGateway: ERROR count / TOTAL
count, 1 calls per call is above 100 thousandths of calls per
call: MAP GW Read Errors
...................................................................................................................................................................................................
10 Navigate to the Policy Server tab and Restart.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Deactivation procedure
This feature cannot be deactivated.
Impacted services
None
WPS Small Cells No
WMS Small Cells Yes

HDM No
Small Cell No
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA Yes
System

NA

NA
Downtime
NA
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 83249 - Launch point to AAA and NTP server
....................................................................................................................................................................................................................................
83249 - Launch point to AAA and NTP server

Overview
SCMS provides a reach-through / launch point, to the devices or any associated CLI /
LMT from the icon representing the network element on the NSP desktop.
The reach-through / launch point is contextual, meaning that the CLI or the LMT of the
selected device opens (as opposed to open a CLI or LMT interface and then to connect to
the network element).
This reach-through / launch point capability is applicable to AAA and NTP devices.
Automatic credential (login, password) is not requested.
Purpose
This topic describes the activation and deactivation procedures for launch point to AAA
and NTP server (83249) feature.

This feature is active by default, if the Fault Management support of NTP server ( 83062)
is active. This feature cannot be activated or deactivated.
Perform the following steps to verify the functionality:
...................................................................................................................................................................................................
1 Log in to the Network Service Platform (NSP) GUI as an admin user.

...................................................................................................................................................................................................
2 Navigate to File > Select Network Layout > View > NTP. Here, NTP is an example
name given to the NTP network element. configured.
...................................................................................................................................................................................................
3 Right click on NTP > Configuration > Set NEs OAM Link Administrative State and
Unlock.
...................................................................................................................................................................................................
4 Right click on the NTP > Show Alarms, verify that Loss of supervision alarm is not
displayed.
...................................................................................................................................................................................................
5 In the NSP layout, right click the NTP GUI to Launch NTP GUI action. The NTP GUI
opens in a new window. This action ensures, that the NTP network element can be
successfully managed by the WMS Small Cells.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 83249 - Launch point to AAA and NTP server
....................................................................................................................................................................................................................................
Impacted Services
None
NTP server Yes
WPS Small Cells No

WMS Small Cells Yes
HDM No
Small Cell No
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA Yes

System

NA

NA
Downtime
NA
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 114578 - SCMS 2.4 support of SAM 7.0
....................................................................................................................................................................................................................................
114578 - SCMS 2.4 support of SAM 7.0

Overview
This feature enables SCMS 2.4 to integrate with SAM 7.0 and IP routers 7.0 version.
With this feature, the SCMS 2.4 can connect to either of the two versions of the supported
SAM servers, that is, 6.1 or 7.0 R6.
In SAM 7.0 R6, the alarm name is not unique. For example, there are three
InterfaceDown (id 36) alarms, but they are distinguished by their package names
(service.InterfaceDown, vpls.InterfaceDown, and vprn.InterfaceDown). The existing
SAM alarm dictionary uses alarm id as the alarmInfoKey. This approach is no longer
feasible, as the existing alarmInfoKey no longer identifies an alarm uniquely.
SCMS 2.4 is intended to support, either of the 2 releases of SAM, that is, 6.1 or 7.0 R6.
Hence the delivery must include both the samOss.jar files.
Purpose
This topic describes the activation and deactivation procedures for SCMS 2.4 support for
SAM 7.0 (114578) feature using the following network elements:
WMS Small Cells
Alcatel-Lucent 5620 Service Aware Manager (SAM)

...................................................................................................................................................................................................
1 The following SAM adapter parameters must be provisioned by the operator in the WMS
Small Cells installation GUI:
Parameter Value
SAM Deployment yes
haenabled yes/no
serverurl SAM server URL
serverport If haenabled is set to yes, port number is 1100,
else 1099
haserverurl If haenabled is set to yes, then provision
redundant SAM server URL
haserverport If haenabled is set to yes, then provision, port
number is 1100
httpserverport port number is 8080
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Parameter Value
user WMS server hostname
password Generic 5620 SAM Password
samversion 6.1.R2 / 7.0.R6
...................................................................................................................................................................................................
2 Then the ROC configuration file located at opt/nortel/config/iut_tools/roc/iut_rocconfig.

xml, can be verified.
E...................................................................................................................................................................................................
N D O F S T E P S
Feature Deactivation Procedures

For deactivating the feature, execute the following steps to provision the SAM adapter
parameters in the WMS Small Cells server:
...................................................................................................................................................................................................
1 Log in to the WMS Small Cells over SSH protocol, as the root user.
...................................................................................................................................................................................................
2 Navigate to location, /opt/nortel/shell/utran and execute the following script:

./updateRocConfig.sh
Result: Please enter deployment 1(for yes)/2(for no)
(current value is: yes). If no value is filled in, the
previous one will be kept.
[1] yes
[2] no
Set the SAM deployment parameter as no.
...................................................................................................................................................................................................
3 Now, log in as an oamops user and stop the utran group.

#stopgu
...................................................................................................................................................................................................
4 Restart utran group.

#startgu
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Impacted Services
Feature deactivation requires restarting the utran group, which causes a temporary outage.
WPS Small Cells No
WMS Small Cells Yes WMS Small Cells initializes SAM

7.0. The SAM adapter behavior
changes due to this feature.
HDM No
Small Cell No
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No
System

NA

NA
Downtime
Feature deactivation requires restarting the utran group, which causes a temporary outage.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 84181 - All-in-one BSR Gateway
....................................................................................................................................................................................................................................
84181 - All-in-one BSR Gateway

Overview
Previously the control and user plane functions of the Small Cell Solution were split
across two different platforms. The control plane was managed by the BSG and the user
plane was managed by the SeGW.
The logical functions of the Alcatel-Lucent VPN Firewall, IPSec Router, BVG and BPG
were all hosted on a single network element, the SeGW.
The signaling translation between the SS7 and Small Cell IP domains and the
concentration function for the control plane was hosted on a separate network element,
the BSG.
The purpose of this feature is to merge some of the preceding functions supported across
different network elements onto a single unit. And therefore, introduces the concept of the
All-In-One BSR Gateway (Small Cell Gateway). The Small Cell Gateway supports only
Small Cell specific functions:
This feature supports the following two variations of the All-In-One BSR Gateway (Small
Cell Gateway):
Small Cell Gateway hosts BSG + BVG/BPG + [Domain Name Server (DNS) / Time
of Day (ToD)]
External Security Gateway used for IPSec + Alcatel-Lucent VPN Firewall
Possibility to use standard SeGW (not Small Cell specific), providing IPSec +
Alcatel-Lucent VPN Firewall functionality or any other third party Security
Gateway (IPSec + Alcatel-Lucent VPN Firewall).
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Small Cell Gateway hosts BSG + [DNS/ToD]

This configuration allows the Security Gateway, to continue as an optional
external SeGW, providing the IPSec + Alcatel-Lucent VPN Firewall + BVG/BPG
function.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Coexistence of AIOG and Non-AIOG
It is possible to have both AIOG and Non-AIOG architecture in the same Small Cells
Cluster. Both BVG and BPG can exist in Small Cell Gateway and SeGW (legacy).
The user plane configuration at the Small Cell determines the path of user plane traffic.
Purpose
This topic describes the activation and deactivation procedures for All-in-one BSR
Gateway (84181) feature.
Before you begin

Ensure that:
BVG is configured and peer network element, Media Gateway (MGW) is accessible.
BPG is configured and peer network element, Serving GPRS Support Node (SGSN)
is accessible.
Feature activation procedure using WMS Small Cells

Execute the following commands:
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Create the BPG/BVG <child type> objects under the existing FGWConfig.
...................................................................................................................................................................................................
4 Set the attribute administrativeState as unlocked.

...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
work order file.
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
11 On successful activation, verify the CM sync status by executing the following command
in the WMS Small Cells WICL:
For example: FGW 301 FGWStatus 0 dis
Result: actionInfoLogInfoTime UNSET
cmSyncState cm_sync_complete
preprovisioned false
shutdownTimeoutAction locked
shutdownTimer 60
E...................................................................................................................................................................................................
N D O F S T E P S

Managed objects from BSG
Table 4-12 <FGW<DN;BVG:1>>
Parameter Description Syntax Default value Value Permitted

name values
administra- This attribute is enum locked unlocked {locked,

tiveState used to administra- unlocked}
enable/disable tiveState
BVG.
Table 4-13 <FGW<DN;BPG:1>>

name values
administra- This attribute enum locked unlocked {locked,

tiveState is used to administrativeState unlocked}
enable/
disable BPG.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Managed objects from WMS Small Cells
Table 4-14 <BSRCluster Profile>
itfBVGIPAddr IP Address of the BVG. It specifies <ipAddress>

the IP address either as dotted
decimal value or FQDN.
Note: This parameter is not used for activation/deactivation. It is used to configure the
Small Cell to communicate with the BVG/BPG.
Feature Deactivation Procedures

Managed objects involved in deactivation from BSG
Table 4-15 <FGW<DN;BVG:1>>

name values
administra- This attribute is enum locked locked {locked,

tiveState used to administra- unlocked}
enable/disable tiveState
BVG.
Table 4-16 <FGW<DN;BPG:1>>

name values
administra- This attribute enum locked locked {locked,

tiveState is used to administrativeState unlocked}
enable/
disable BPG.
Impacted Services
None
WPS Small Cells No
WMS Small Cells No

HDM No
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Small Cell Yes The user plane IP is configured as

BVG/BPG of AIOG.
IPC No
IPsec Router Yes IP routes are updated to access the

new BVG/BPG of AIOG
BPG Yes
BVG Yes
BSG Yes BVG and BPG instances are
created.
IP route tables are updated for
AIOG BVG and BPG.
New IP /Vlan supports Small
Cell Gateway for BVG/BPG
If both BVG/BPG are locked in
Small Cell Gateway, then the
CS and PS calls are blocked.
AAA Yes Remote AAA for DS2460 Small

Cells and allocate VPN IP from pool
as required.
Security Gateway Management Yes Rule sets and routes are added to
System reach AIOG BVG/BPG.

None

NA
Downtime
None. The configuration is dynamic.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 83087 - Distributed SS7
....................................................................................................................................................................................................................................
83087 - Distributed SS7

Overview
Distributed SS7 (DSS7) feature is an internal feature for the IPC, aimed at providing:
Increased capacity - The feature distributes the signaling stack over multiple
processors, which increases the IPC capacity and reduce the impact of processor
failure.
Improved availability - The feature distributes the signaling across multiple
processors, hence providing improved resilience to processor failures. Previously, all
IPC signaling and call processing was handled on a single processor.
Previously, the IPC implementation used an SS7 stack from Trillium. Trillium also
provides a DSS7 version, which is used for the implementation of the DSS7 feature.
Prior to this feature, the IPC signaling stack software executed on a pair of Signaling
Processors (SPs) configured in an active/standby mode. This architecture provided limited
performance and availability. The inability of the simplex configuration in meeting the
capacity requirements for the IPC and the non-reliablility of the Active copy leads to
100% loss of ongoing calls.
To meet the capacity targets, there is a need for distributed configuration of SS7,
SIGTRAN, and application stacks.
The DSS7 stack provides, a highly fault tolerant and scalable implementation of the SS7
protocol, enabling the IPC to meet a higher capacity and stringent reliability and
performance requirements demanded by the network operators.
Even after the introduction of D-SS7, the system can continue to support simplex
configuration. In a distributed configuration, there are multiple active SPs present where
each set of SP performs different functionality based on the stacks hosted on them.
Depending on the stacks running on the SPs, each SP is classified as SP-SS7, SP-IP, or
SP-C.
SP-SS7: The SP that operates the SS7 Transport stack (that is, MTP3/ Q.2140/ SSCOP) is
termed as SS7 Link Processor (SP-SS7). This processor terminates the MTP3 links
between the IPC and the peer network element(s) in the ATM network. The SPs 1-12-1
and 2-12-1 are SP-SS7 processors.
SP-IP: The SP that operates the SIGTRAN Transport stack (that is, M3UA/SCTP) is
termed as SIGTRAN Link Processor (SP-IP). This processor terminates the SCTP
associations between the IPC and BSGs in the IP network. The SPs 1-11-1 and 2-11-1 are
SP-IP processors.
SP-C: The SP that operates the RANAP and ALCAP stack (that is, RANAP/SCCP and
ALCAP/STC.1) is termed as Application or Control Processor (SP-C).
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Purpose
This topic describes the activation and deactivation procedures for Distributed SS7
(83087) feature.
Before you begin

Ensure that the IPCCLI is accessible in fms01 or fms02, wherever, the LMTGwServer is
running. Use rnccheckservers command to determine the SCMS, which has the
LmtGwServer is running.

To support DSS7 configuration in IPC, two DPCRoutes must be created for an Iu
interface, with two different ports ( for IuCS port: 2905, 2906 and IuPS ports: 2917,
2918) referencing different SCTP association with the same port (for IuCS 2905, and for
IuPS 2917) in BSG. When the IPC transfers the IuCS packets from port 2905 and 2906,
all the packets are received at port 2905 in BSG, to process the packets. When the IPC
transfers the IuPS packets from port 2917 and 2918, all the packets are received at port
2917 in BSG, to process the packets. The response from BSG reaches IPC using multiple
DPCRoutes.
...................................................................................................................................................................................................
1 Load the exported snapshot from WMS Small Cells into the WMS Small Cells.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Navigate to FGWConfig > BSG. Set attribute administrativeState as unlocked.

...................................................................................................................................................................................................
4 Create object M3UA: l under BSG and objects SCTPAssociation:2 and SCTPAssocia-
tion:21 under M3UA: l.
...................................................................................................................................................................................................
5 Navigate to FGWConfig > BSG > M3UA: l > SCTPAssociation:2

The operator must complete the IuCS cluster configuration by modifying the following
attributes as required:
localSockAddressIpaddress as 172.62.108.10
localSockAddressPort as 2905
interfaceReference as FGW=530601
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
ServerHardware as 1
Interface as 16.
...................................................................................................................................................................................................
6
Create object SCTPAssociationremoteSockAddress:1 under SCTPAssociation:2 and set
the following attributes as required:
remoteSockAddressIpaddress as 172.62.108.4
remoteSockAddressPort as 2905.
...................................................................................................................................................................................................
7 Navigate to FGWConfig > BSG > M3UA: l > SCTPAssociation:21

The operator must complete the IuCS cluster configuration by modifying the following
attributes as required:
localSockAddressIpaddress as 172.62.108.10
interfaceReference as FGW=530601
ServerHardware as 1
Interface as 16.
...................................................................................................................................................................................................
8
Create object SCTPAssociationremoteSockAddress:1 under SCTPAssociation:21 and set
the following attributes as required:
remoteSockAddressIpaddress as 172.62.108.4
...................................................................................................................................................................................................
9 Navigate to FGWConfig > BSG:1 and create object DPCRoute:2.

...................................................................................................................................................................................................
10 Navigate to FGWConfig > BSG:1 > DPCRoute:2 and create object DPCRouterefAssocia-
tions:1. Set the following attribute:
refAssociationsRefAssociations as FGW=530601,BSG=1,M3UA=1,
SCTPAssociation=2.
...................................................................................................................................................................................................
11 Navigate to FGWConfig > BSG:1 > DPCRoute:2 and create object DPCRouterefAssocia-
tions:2. Set the following attribute:
refAssociationsRefAssociations as FGW=530601,BSG=1,M3UA=1,
SCTPAssociation=21.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
12 Navigate to FGWConfig > BSG:1 > M3UA:1 and create object SCTPAssociation:221. Set
the following attributes:
localSockAddressIpaddress as 172.62.108.10.
interfaceReference as FGW=530601,ServerHardware=1,Interface=16.
...................................................................................................................................................................................................
13 Navigate to FGWConfig > BSG:1 > M3UA:1 and create object SCTPAssociation:222. Set
the following attributes:
localSockAddressIpaddress as 172.62.108.10.
interfaceReference as FGW=530601,ServerHardware=1,Interface=16.
...................................................................................................................................................................................................
14 Navigate to FGWConfig > BSG:1 > M3UA:1 > SCTPAssociation:221 and create object
SCTPAssociationremoteSockAddress:1 . Set the following attributes:
remoteSockAddressIpaddress as 172.62.108.4.
...................................................................................................................................................................................................
15 Navigate to FGWConfig > BSG:1 > M3UA:1 > SCTPAssociation:222 and create object
SCTPAssociationremoteSockAddress:1 . Set the following attributes:
remoteSockAddressIpaddress as 172.62.108.4.
...................................................................................................................................................................................................
16 Navigate to FGWConfig > BSG:1 and create object DPCRoute:221.

...................................................................................................................................................................................................
17 Navigate to FGWConfig > BSG:1 > DPCRoute:221 and create object DPCRouterefAsso-
ciations:1. Set attribute refAssociationsRefAssociations as FGW=530601,BSG=
1,M3UA=1,SCTPAssociation=221.
...................................................................................................................................................................................................
18 Navigate to FGWConfig > BSG:1 > DPCRoute:221 and create object DPCRouterefAsso-
ciations:2. Set attribute refAssociationsRefAssociations as FGW=530601,BSG=
1,M3UA=1,SCTPAssociation=222.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
20 Create a work order and export it into WMS Small Cells.

...................................................................................................................................................................................................

...................................................................................................................................................................................................
work order file.
...................................................................................................................................................................................................

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
Feature activation procedure - using IPC

The instances of IuCS and IuPS are added to the IPC using IPCCLI.
...................................................................................................................................................................................................
1 Log in to the IPCCLI as an admin user.

...................................................................................................................................................................................................
2 Execute the following command to determine the instance having the SCMS
LmtGwServer operational:
Example: [IPC2425:fms01]-> rnccheckservers
...................................................................................................................................................................................................
3 Execute the following command from the fms02 instance:

IPCCLI? Menu
...................................................................................................................................................................................................
4 Select option 4.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
5 The object management options are displayed. Select the appropriate option as required.
E...................................................................................................................................................................................................
N D O F S T E P S

Managed objects from IPC
Table 4-17 <LIPC::SS7Stack>
Parameter Description Value Command Comment

Name
enableDistribut- A flag to enable Default: false Use IPCCLI After enabling
edSPs Distributed command, refer the DSS7 flag,
stack. DSS7 is IPCCLI LIPC must be
activated if the commands reset to
flag is set as (p. 1-16). configure the
True. IPC stack into
distributed mode
(refer IPCCLI
commands
(p. 1-16)).
Managed objects from WMS Small Cells
Parameter Name Description Value

enableDistributedSPs A flag to enable Distributed Default: False
stack. DSS7 is activated if the
flag is set as True.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Managed objects involved in deactivation in IPC
Parameter Description Value Command Comment

Name
enableDistribut- A flag to enable Default: False Use IPCCLI After
edSPs Distributed command, refer deactivating
stack. DSS7 is IPCCLI DSS7 feature,
deactivated if the commands need to perform
flag is set as (p. 1-16). LIPC reset to
False. configure the
IPC stack into
SIMPLEX mode
(refer IPCCLI
commands
(p. 1-16)).
Managed objects involved in deactivation in WPS Small Cells
Parameter Name Description Value

enableDistributedSPs A flag to enable Distributed Default: False
stack. DSS7 is deactivated if
the flag is set as False.
Impacted Services
The BSR Gateway is not impacted. The IPC functioning is interrupted and there is a
downtime on activation/deactivation of this feature.
WPS Small Cells No
WMS Small Cells No
HDM No
Small Cell No
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
IPC Yes There is a downtime during

activation/deactivation of DSS7
feature.
IPsec Router No
BPG Yes
BVG No
BSR Gateway Yes Multiple DPC routes are referenced

in Iu interface during creation.
AAA No
System

None

There is downtime in the IPC for approximately 45 minutes.
Downtime
NA
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 84990 - SCMS support of BSR Gateway
....................................................................................................................................................................................................................................
84990 - SCMS support of BSR Gateway

Overview
Previously, Alcatel-Lucent Small Cell Solution was designed such that there would be
dedicated BSR Gateways for User Plane (SeGW) and Control Plane (BSG) functions. The
different gateways were each deployed on separate hardware units.
The BSR Gateway combines the control and user plane functions onto a single hardware
platform. The BSR Gateway is an evolution of the BSG to include the Security Gateway
functionality. The BSR Gateway has a single OAM interface.
The DNS/ToD functionality can be hosted on the BSR Gateway hardware.
Fault management
SCMS provides integrated Fault Management support for the BSR Gateway. The
following are the key benefits:
Device discovery
NSP layouts
First Alert Fault Management (in both Resource Browser and Alarm Manager)
Integrated on-line help
Alarms from the BSR Gateway are handled and managed by the SCMS toolset. The
SCMS therefore, supports the alarms rule-set (inhibit, send SMS, send email, change
severity, and so on), the trouble ticketing interface, the alarm browser, the managed and
unmanaged alarm stream, the various resources browsers (topological, grid).
On the NSP GUI, the user can see an icon representing the BSR Gateway.
The Fault Management supervision guideline covers the BSR Gateway.
The BSR Gateway is a redundant NE and SCMS supports this redundancy as supported
for the BSG previously.
PM Counter files collection
SCMS provides an automatic collection of the performance counters files by WMS Small
Cells. The BSR Gateway generates its counters in XML PM format. These files are
collected by the WMS Small Cells on the same granularity as generated in the gateway.
The collected files are stored in WMS Small Cells (or any location that the user has
provisioned). The storage duration is 3 days plus the current day, and the native purge
mechanism of WMS Small Cells purges the files after this period.
Launch point
WMS Small Cells supports Launch point/Reach through functionality for BSR Gateway
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Purpose
This topic describes the activation and deactivation procedures for SCMS support of
Alcatel-Lucent 9365 BSR Gateway (BSR Gateway) (84990) feature.
Before you begin

Ensure the Small Cell Solution is upgraded to Small Cell Solution 2.4.1.

The managed objects for BVG/BPG must be created using SCMS, with the same BSR
Gateway configuration used to enable the All-in-one BSR Gateway (84181) feature (refer
84181 - All-in-one BSR Gateway (p. 4-41) for more information)
Perform the following steps to complete the uploadDB operation:
...................................................................................................................................................................................................
1 Log in to BSR Gateway as an admin user.

...................................................................................................................................................................................................
2 Execute the following commands:

/opt/bin/BSGCLI.exe
CLI >> set {uploadDB=True};
Waiting for OAM response...
Set command response from OAM:
Action Initiated Check the appropriate attributes for SUCCESS or
FAILURE
...................................................................................................................................................................................................
3 Verify the completion of the uploadDB operation using the CLI. Ensure the dbStatus
parameter value is updated as uploadDBSuccessful.
...................................................................................................................................................................................................
4 FTP the latest upload file from BSR Gateway (example, /opt/upload/FGW-OAM-
Config:901:1017FM301H:201103031147.tar) to WMS Small Cells.
...................................................................................................................................................................................................
5 Copy the configuration file to the PC which has WPS Small Cells installed.
...................................................................................................................................................................................................
6 Untar the configuration file (example, FGW-OAM-

Config:901:1017FM301H:201103031147.tar)
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
7 Open the WPS Small Cells and import the existing network snapshot from WMS Small
Cells.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
9 Create the BPG/BVG MOs under the existing FGWConfig with the appropriate attribute
values.
...................................................................................................................................................................................................
10 In the Edition tab, select Generate CLI batch file to generate a new BSR Gateway CLI
file and save it locally.
...................................................................................................................................................................................................
11 In the BSR Gateway CLI navigate to /opt/conf, copy the saved BSR Gateway CLI file.
Execute the command loadbatchfile -v <batchfile_name> to process as a batch
file.
E...................................................................................................................................................................................................
N D O F S T E P S
To configure Launch point

In the WMS Small Cells NSP GUI, navigate to Network Layout >> FGW >>
Configuration >> Launch SSH (for both active/passive machines separately).
Software management
SCMS supports Software Management and Software Inventory Management. WMS
Small Cells supports software upgrades/updates through NSP GUI.

NA
Impacted services
None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
WPS Small Cells Yes
WMS Small Cells Yes

HDM No

Small Cell Yes
IPC Yes
IPsec Router No
BPG Yes
BVG Yes
BSG Yes
AAA No
System

None.

NA
Downtime
None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 96373 - FM support for DNS/ToD functions
....................................................................................................................................................................................................................................
96373 - FM support for DNS/ToD functions

Overview
Previously, the DNS/ToD functions were made part of the BSR Gateway hardware
platform (SUN x4250). However, there was no Fault Management (FM) solution for the
DNS/ToD functions.
The purpose of this feature is to introduce minimum FM capabilities for the DNS/ToD
functions when running on the BSG.
Without the DNS function, Small Cells will not be able to connect to the network. This
feature provides customers with an integrated solution to determine if the DNS/ToD
functions residing in the BSR Gateway are operational.
Purpose
This topic describes the activation and deactivation procedures for FM support for
DNS/ToD functions (96373) feature.
Before you begin

Ensure that the BSR Gateway is operational:
Log in to WMS Small Cells as an admin user.
Navigate to File > Network Layout, select the network element (example BSG) >
Configurations > WICL and execute the display command. Consider the following
example:
2# FGW 601 display
RESULT:
aliasName UNSET
clusterId Cluster/
UMAINSERV1
fgwClusterId 53
fgwId 601
mimVersion BCR-02-04-
FGW-XMIM-4.1
mode
nonRedundant
OAMlinkAdministrativeState unlocked
siteName UNSET
systemRelease UNSET
unknownStatus
unknownstatusfalse
userSpecificInfo UNSET
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Note: In the output ensure that the value for the unknownStatus field is
unknownstatusfalse.
Ensure that the DNS and ToD servers operational:
Log in to WMS Small Cells as an admin user.
Navigate to File > Network Layout select the network element (example DNS), right
click and select Show Alarms.
Verify that the dnsServerDown alarm is not present. The presence of an
dnsServerDown alarm indicates that the DNS server running on the BSR Gateway is
not functional.
Navigate to File > Network Layout select the network element (example ToD), right
click and select Show Alarms.
Verify that the sntpServerDown alarm is not present. The presence of an
sntpServerDown alarm indicates that the ToD server is not functional.

...................................................................................................................................................................................................
1 The FM support for DNS/ToD functions feature is active by default. The feature cannot
be activated or deactivated.
E...................................................................................................................................................................................................
N D O F S T E P S
Impacted Services
None
WPS Small Cells No
WMS Small Cells Yes
HDM No
Small Cell No
IPC No
IPsec Router No
BPG No
BVG No
BSG Yes
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
AAA No

System
DNS Yes
ToD Yes

NA

NA
Downtime
None. The configuration is dynamic.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 120359 - HDM alarm management in WMS Small Cells for
Small Cell
....................................................................................................................................................................................................................................
120359 - HDM alarm management in WMS Small Cells for Small

Cell
Overview
This feature integrates all the HDM alarms in WMS Small Cells using the interface
between the two systems. An icon represents HDM on the WMS Small Cells GUI.
HDM alarms are available on the WMS Small Cells 3GPP FM North Bound Interface
(NBI).
The alarm, indicating a link failure between WMS Small Cells and HDM, is available in
context of the HDM icon, and is available on the WMS Small Cells NBI as well.
The feature requires the SCMS to manage all the HDM alarms and the HDM.
Purpose
This topic describes the activation and deactivation procedures for the HDM alarm
management in WMS Small Cells for Small Cell (120359) feature.

To configure with WMS Small Cells
...................................................................................................................................................................................................
1 Export the latest snapshot from WMS Small Cells.

...................................................................................................................................................................................................
2 Load the exported snapshot from WMS Small Cells to WPS Small Cells, by importing the
snapshot to WPS Small Cells.
...................................................................................................................................................................................................
3 Create an instance for HDM. Set the cluster id for HDM

...................................................................................................................................................................................................
4 Perform Run Checks ... on the network.

...................................................................................................................................................................................................
5 Create a work order and copy to the WMS Small Cells.

...................................................................................................................................................................................................
6 In the WMS Small Cells, navigate to Configuration > Sessions Manager > Create new
Session, to launch the work order.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
7 Once the work order is successful, create a layout for HDM. Navigate to File > Select
Network Layout, select New, enter a Name.
...................................................................................................................................................................................................
8 To edit, right click the new instance, select Open Group, right click NE Store > Find >
Select > Move To.
...................................................................................................................................................................................................
9 Navigate to File > Save Network Layout.

...................................................................................................................................................................................................
10 Open the new layout, navigate to View, right click, and select RC Open Group, right click
the icon, select Configuration > Set NE's Administrative State. Ensure that
the administrative state is unlocked.
E...................................................................................................................................................................................................
N D O F S T E P S
Feature deactivation
...................................................................................................................................................................................................
1 To remove the HDM from SCMS. Open the newly created layout, navigate to View, right
click, and select RC Open Group, right click the icon, select Configuration > Set
NE's Administrative State. Select Lock.
...................................................................................................................................................................................................
2 In the WMS Small Cells, navigate to Configuration > Sessions Manager. Execute the
reverse work order.
E...................................................................................................................................................................................................
N D O F S T E P S
Impacted services
None
WPS Small Cells No
WMS Small Cells No
HDM No
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell
....................................................................................................................................................................................................................................
Small Cell No
IPC No
IPsec Router No
BPG No
BVG No
BSR Gateway No
AAA No
System

Only Application alarms related to the default counters, available in the dashboard
module of HDM, can be monitored.
If new counters are defined, a corresponding entry must be made in the Alarm
Dictionary, for displaying the alarm in SCMSs GUI.
Manual alarm synchronization is not supported.

NA
Downtime
NA
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 119109 - Meinberg NTP integration
....................................................................................................................................................................................................................................
119109 - Meinberg NTP integration

Purpose
This topic describes the procedure to activate the Meinberg NTP integration (119109)
feature.
Feature overview
This feature allows the Small Cell AP to derive its NTP timing from the Meimberg M600
NTP Server.
Prior to this feature, the Small Cell AP used two NTP Servers (primary and secondary).
With this feature, the Small Cell AP can use up to five NTP Servers. There is no defined
primary/secondary server, all the NTP Servers have equal priority.
Before you begin

Ensure that the Meinberg M600 NTP Server is operating in the stratum level 1 condition.

Perform the following steps to configure the feature through WPS Small Cells:
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to BSRClusterProfile MO, set attribute NTPAddressingScheme to operate in a

Primary-Secondary mode, or ServerPool mode as appropriate.
The NTP process starts automatically as per the parameters configured. In the ServerPool
mode, the server is selected randomly and evenly distributed over the available servers.
...................................................................................................................................................................................................
3 The ntpServerIPAddrList parameter is a child object of BSRClusterProfile MO and

maximum of ten instances can be created.
...................................................................................................................................................................................................
4 The ntpServerIPAddr attribute is present under every instance of ntpServerIPAddrList

attribute which holds the actual NTP server IP address value.
...................................................................................................................................................................................................
5 Perform Run Checks ... on the network
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................
8 Once the work order is successful, WMS Small Cells sets the parameter on all the Small
Cells in that cluster.
E...................................................................................................................................................................................................
N D O F S T E P S
Managed objects in feature activation

The following BSR objects are modified:
Parameter Description Syntax Permitted Value Default

Name
NTPAddressing- NTP addressing enum { primaryAndSecon
Scheme scheme that can dary=0,
be used.
serverPool=1 }
ntpServerIPAd- The NTP Server sequence [0..10]
drList address list for of struct
RF clock NTPServerI-
disciplining. PAddr
NTPServerI- id: <Instance struct { { [1..10], } { , 0.0.0.0 }
PAddr number of Integer32 id,
ntpServerIPAd- ipAddress
drList>. ntpServerI-
ntpServerI- PAddr }
PAddr: <The
NTP server IP
Address>.
Note:
If BSR::ntpAddressingScheme is set as serverPool, ensure that the
BSR::ntpServerIPAddrList is not empty
A maximum of five servers are supported in the server pool mode.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
WPS Small Cells No
WMS Small Cells No

HDM No

Small Cell Yes
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No
System
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 117813 - Small Cell Access Point capacity licensing
....................................................................................................................................................................................................................................
117813 - Small Cell Access Point capacity licensing

Overview
This feature enables operators change the number of concurrent users allowed to make
calls on a Small Cell. The number of users depends on the licenses purchased.
The first 16 users of a Small Cell are considered base, and no license is required.
Additional blocks of 8 users are licensed up to the maximum supported by the platform.
That is, licenses are required for 24 users or 32 users.
The Small Cell Access Point capacity licensing feature, currently supports a maximum of
32 users.
The licenses are entered into the SCMS for validation and provisioning to the Small Cell.
Customers with existing deployments must contact their account team for licenses, before
upgrading the Small Cell, to ensure that the service is not unexpectedly limited. Licenses
for existing Small Cells must be entered into the SCMS prior to the upgrade, to ensure
that they are provisioned correctly.
Purpose
This topic describes the activation and deactivation procedures for Small Cell Access
Point Capacity Licensing (117813) feature.
Related Information
This feature is the same as the OAM feature, Small Cell MS Small Cell capacity and
power licensing (121329).
Feature activation procedures

Note: A license file is obtained from the License Key Delivery Infrastructure (LKDI).
This license file is uploaded to the Wireless License Management (WLM) server.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to the BSRProfile selected for this feature. Set the parameter additionalFem-
toUserCapacityLicensing as 1 or 2, as appropriate.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
This parameter defines the number of user capacity tokens needed for a Small Cell. Each
token represents 8 users. A Small Cell with a token value of 0, supports up to 16 users.
The value of this attribute can be 0, 1 or 2. The maximum value of this attribute is 2. To
activate this feature in the Small Cell, the attribute must be set as 1 or 2.
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
Table 4-21
Parameter Description Default Value Syntax Value Permitted

name Values
additionalFem- This parameter 0 integer 1 or 2 {0, 1, 2}

toUserCapaci- defines the
tyLicensing number of user
capacity tokens
needed for a
Small Cell. Each
token represents
8 users. A Small
Cell with a
token value of 0,
supports up to
16 users.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 4-22

name Values
additionalFem- This parameter 0 integer 0 {0, 1, 2}

toUserCapaci- defines the
tyLicensing number of user
capacity tokens
needed for a
Small Cell. Each
token represents
8 users. A Small
Cell with a
token value of 0,
supports up to
16 users.
Note: With the parameter additionalFemtoUserCapacityLicensing set as 0,

the Small Cell supports up to 16 users (default number of users).
Impacted services
None
WPS Small Cells Yes additionalFemtoUserCapaci-

tyLicensing parameter is
modified.
WMS Small Cells Yes A new Wireless License
Management (WLM) server is
added.
HDM No

Small Cell Yes This feature is applicable only for
Small Cell which support 32 users.
That is, only Small Cell V2 with
PC323/333 pico chip. The feature is
not applicable for Small Cell V1.2 or
Small Cell V1.5.
IPC No
IPsec Router No
BPG No
BVG No
BSG No
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
AAA No
SCMS Yes The licenses are entered into the

SCMS for validation and
provisioning to the Small Cell.
System

None.
Duration
NA
Downtime
None
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 114014 - Active-Warm standby BSR Gateway redundancy
....................................................................................................................................................................................................................................
114014 - Active-Warm standby BSR Gateway redundancy

Overview
This feature improves the overall availability of the BSR Gateway. It reduces the Small
Cell downtime in case of a failure of an active BSR Gateway.
In normal mode of operation, each Small CellAP has 2 SCTP associations, with the active
BSR Gateway (A-BSR Gateway) and the standby BSR Gateway (S-BSR Gateway). All
traffic is supported by the A-BSR Gateway. Only the A-BSR Gateway has associations
with the CN.
When an A-BSR Gateway fails:
The S-BSR Gateway detects the failure, the IP address exposed to the CN floats on
the S-BSR Gateway, and the S-BSR Gateway resets the connection with the CN
(RANAP reset).
Small CellAP detects the A-BSR Gateway failure and drops ongoing calls.
New calls are supported using the other SCTP association (the S-BSR Gateway)
In case, a new call attempt fails (for example, because the CN connection is not still
setup), the Small CellAP either, stops to radiate or redirects the call to the macro
coverage, if available. This enables efficient management of emergency calls.
This feature enables the BSR Gateway to support the Small CellAP with a single SCTP
association. This is needed for:
Supporting a third-party Small CellAP in the scope of Iuh feature
Enable migration scenario (for example, when the BSR Gateway is upgraded to
higher version while Small CellAP is not.)
Purpose
This topic describes the activation and deactivation procedure for Active-Warm standby
BSR Gateway redundancy (114014) feature.
Before you begin

Ensure that the BSR Gateway is running in Active-Standby configuration.

Note: The core network is assumed to be operational in less than 30 seconds. If the
core network takes longer than 30 seconds, there is delay in connection establishment
between the BSR Gateway and the core network. This leads to an increase in the
number of handovers to the macro network.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to the BSRProfile selected for this feature, set enableWarmStandbyAssoc as

True.
...................................................................................................................................................................................................
3 Navigate to the FGW selected for this feature, set node1FemtoAddress as <ipAddress>
and node2FemtoAddress as <ipAddpress>.
Note:
The IP addresses, node1FemtoAddress and node2FemtoAddress as they are not
floated by the BSR Gateway between the A-BSR Gateway and S-BSR Gateway,
when the active BSR Gateway is changed, that is, these IP addresses are not
floated at BSR Gateway switchover.
However, it may be floated between bonding interfaces in the event of local link /
switch failure, that is, during intra-LAG switchover.
This IP address is on the same subnet and VLAN as the PhysicalInterfaceS MOI
that has interfaceType set as FemtoCP. Hence, it uses the same default BSR
Gateway.
The configurations must be done in, both, the A-BSR Gateway and the S-BSR
Gateway.
...................................................................................................................................................................................................
4 Navigate to the BSRClusterProfile selected for this feature, set attribute bsrGWNode1 as
the fixed IP address of A-BSR Gateway (Server Hardware=1).
Set bsrGWNode2 as the fixed IP address of S-BSR Gateway (Server Hardware=2).
...................................................................................................................................................................................................

...................................................................................................................................................................................................
6 Create a work order and export it to the WMS Small Cells.

...................................................................................................................................................................................................
work order file.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................
shutdownTimer 60
E...................................................................................................................................................................................................
N D O F S T E P S
Note: When the feature is enabled, BSR::bsrGWNode1 and BSR::bsrGWNode2 can

also be provisioned with the FQDN of the BSR Gateway nodes. In this case, the
Small Cell contacts the DNS server to resolve the FQDN of A-BSR Gateway and
S-BSR Gateway.

Managed objects of the BSR Gateway:
Table 4-23
Parameter name Description Default Syntax Value Permitted

Value Values
enableWarmStandbyAssoc This parameter is a feature flag. When set as False boolean True { True, False }
True, it enables use of the Active Warm If set as False,
standby feature, with the Small Cell BSR
connecting to both active, and standby Gatewayonly
gateways. binds to the
Also the Small Cell uses BSR::bsrGWN- floating IP
ode1 and BSR::bsrGWNode2 in preference address,
to BSR::bSRGatewayIpAddress for ipAddressFemtoCpLocal,
connecting to the gateway. for SCTP
associations to
the Small Cells.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 4-23 (continued)

Value Values
node1FemtoAddress This attribute represents the IP address for IP address

Node1 of the gateway.
This address may be used by the Small Cell
call processing to access the BSR Gateway
end of the SCTP associations on Node1 of
the gateway when FGW::
enableWarmStandbyAssoc is set as True.
This IP address is not floated by the BSR
Gateway application, between BSR
Gateway nodes, when the active node is
changed.
However, it may be floated between
physical interfaces or bonding interfaces in
the event of local link / switch failure.
This IP address is on the same subnet and
VLAN as the PhysicalInterfaceS/B MOI that
has interfaceType set as FemtoCP, and
hence uses the same defaultGateway.
node2FemtoAddress This attribute represents the IP address for IP address
Node2 of the gateway.
This address may be used by the Small Cell
call processing to access the BSR Gateway
end of the SCTP associations on Node2 of
the gateway when FGW::
enableWarmStandbyAssoc is set as True.
This IP address is not floated by the BSR
Gateway application, between BSR
Gateway nodes, when the active node is
changed.
However, it may be floated between
physical interfaces or bonding interfaces in
the event of local link / switch failure.
This IP address is on the same subnet and
VLAN as the PhysicalInterfaceS/B MOI that
has interfaceType set as FemtoCP, and
hence uses the same defaultGateway.
Managed objects of the Small Cell:
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 4-24
Parameter name Description Default Syntax Value Permitted Values

Value
enableWarm- This parameter is a feature flag. False boolean True { True, False }
StandbyAssoc When set as True, it enables use of When this is If set as False, BSR
the Active Warm standby feature, set as True, Gatewayonly binds to the
with the Small Cell connecting to parametersb- floating IP address,
both active, and standby gateways. srGWNode1 ipAddressFemtoCpLocal,
Also the Small Cell uses and for SCTP associations to
BSR::bsrGWNode1 and bsrGWNode2 the Small Cells.
BSR::bsrGWNode2 in preference must be
to BSR::bSRGatewayIpAddress populated.
for connecting to the gateway.
bsrGWNode1 The address of gateway node 1. It IP address length=128

can be defined in either a DNS
name or an IP address in dot
decimal format.
Note: In 3.0 only IP address is
supported.
bsrGWNode2 The address of gateway node 2. It IP address length=128
can be defined in either a DNS
name or an IP address in dot
decimal format.
Note: In 3.0 only IP address is
supported.

Feature deactivation in Small Cell
...................................................................................................................................................................................................
1 In the BSRProfile, set enableWarmStandbyAssoc as False.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 4-25 BSR

Value
enableWarmStandbyAssoc This parameter is a feature flag. When False boolean False { True, False }
set as True, it enables use of the If set as False,
Active Warm standby feature, with the BSR
Small Cell connecting to both active, Gatewayonly
and standby gateways. binds to the
Also the Small Cell uses floating IP
BSR::bsrGWNode1 and address,
BSR::bsrGWNode2 in preference to ipAddressFemtoCpLocal,
BSR::bSRGatewayIpAddress for for SCTP
connecting to the gateway. associations to
the Small Cells.
Impacted services
None
WPS Small Cells No

WMS Small Cells No
HDM No
Small Cell Yes

IPC No
IPsec Router No
BPG No
BVG No
BSG Yes
AAA No
SCMS Yes
System

None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Duration
Approximately 15-20 minutes.
Downtime
The BSR Gateway downtime during the activation of the feature is approximately 7
minutes.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 120353 - RTCP for IuCSoIP
....................................................................................................................................................................................................................................
120353 - RTCP for IuCSoIP

Overview
This feature deals with the support of Real Time Transport Control Protocol (RTCP)
protocol on IuCSoIP interface. Support of RTCP on IPCSoIP is optional as per 3GPP
standard. This protocol enables monitoring the quality of the Real-time Transport
Protocol (RTP) links between the Radio Network Controller (RNC) and MSC functions.
In the Small Cells Cluster, RTP connections are set between the SCAP (Small Cell Access
Point) and the MSC, using the BVG function. This feature supports one RTCP connection
for each RTP connection, so that the quality of the latter can be monitored end to end by
the former. The RTCP connections are set in the same way as the RTP connections,
between the SCAP and the MSC, using the BVG function.
Purpose
This topic describes the activation and deactivation procedure for RTCP for IuCSoIP
(120353) feature.
Before you begin

Ensure that:
RTCP feature is activated in MSC
BVG is equipped with the software that performs transport address / User Datagram
Protocol (UDP) port translation for RTCP, similar to RTP in both uplink and
downlink, in response to the existing DPAT signaling for RTP.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to the BSRProfile selected for this feature, set enableRtcp as True.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Cells in that cluster using SetParameterValues.
E...................................................................................................................................................................................................
N D O F S T E P S
Table 4-26 BSR::IuCSUplane::enableRtcp
Parameter Description Default Syntax Value Permitted

name Value Values
enableRtcp When set as True, the feature is False boolean True { True, False }
enabled. This supports the
RTCP protocol monitoring the
RTP streams on the IuCS
interface.
Table 4-27 BSR::IuCSUplane::enableRtcp

name Value Values
enableRtcp When set as False, the feature False boolean False { True, False }
is disabled.
Impacted services
None
WPS Small Cells No

WMS Small Cells No
HDM No
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Small Cell Yes
IPC No
IPsec Router No
BPG No
BVG Yes
BSG No
AAA No
SCMS No
System

None.
Duration
The activation/deactivation of the feature in Small Cell is done in a negligible amount of
time, without interrupting any other services.
Downtime
None
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 78594 - Small Cells network support for End-to-End call
subscriber trace
....................................................................................................................................................................................................................................
78594 - Small Cells network support for End-to-End call

subscriber trace
Overview
This feature enables the network operator trace a specific subscriber within his network
on the basis of the IMSI.
The subscriber trace feature, facilitates the operator to acquire:
Protocol level details of an ongoing call
Important information to trouble shoot issues in the Small Cell network proactively
The subscriber trace feature, supports maintenance of the Small Cells network quality at a
high level. It also supports testing new features in the network.
The capability to log data on any interface, at the call level for a specific user, enables the
operator get information, which cannot be derived from Performance Measurements.
Examples of such applications are, perception of end-user QoS during a call, correlation
between protocol messages and RF measurements.
Finally, the feature enables the operator test the capabilities of handsets from various
vendors in the Small Cell environment. Since 3G has many features that are very much
handset dependant, the impact of these features on the network performance can be very
efficiently tested.
The subscriber tracing functionality needs co-ordination between the SCMS and all the
NEs (that is, BSR Gateway, IPC, Small Cell). The SCMS provides the capability to
activate/deactivate the tracing of a specific call/subscriber. Based on the signaling
information the NEs track the traced subscriber and record messages as needed. The trace
follows the subscriber as long as the call is within the span of control of the Small Cell
network. On the completion of the subscriber trace, the trace records are collected by the
SCMS from all the NEs, which can then be provided at the northbound interface for
retrieval.
Purpose
This topic describes the activation and deactivation procedure for Small Cells network
support for End-to-End call subscriber trace (78594) feature.
Before you begin

Ensure that:
Small Cell is operational and accessible by WPS Small Cells.
IPC is operational and IPCCLI is accessible.
....................................................................................................................................................................................................................................
Issue 5 April 2014
subscriber trace
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to the Network > FGW and set subscriberTraceEnable as True. And set
sftpServer with the IP address of the WMS Small Cells.
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
To configure using IPCCLI

...................................................................................................................................................................................................
1 Log in to the IPC using the IP address.

...................................................................................................................................................................................................
2 Enter the following command to determine the FMS, in which the LmtGwServer is
running:
...................................................................................................................................................................................................
3 Execute the following command from the LmtGwServer:

....................................................................................................................................................................................................................................
Issue 5 April 2014
subscriber trace
....................................................................................................................................................................................................................................
Result: IPC Software (current) IPC-02.04.01.04 IPCCLI? Menu
...................................................................................................................................................................................................

...................................................................................................................................................................................................
5 The Object Management Options is displayed. Select the appropriate option.

E...................................................................................................................................................................................................
N D O F S T E P S

Managed objects in the BSR Gateway
Table 4-28 </FGW:<DN>/ItfFgw:1/SubscriberTraceConfig:1>
Parameter name Description Default Syntax Value Permit-

Value ted
Values
sftpServer This attribute defines the sftp PM string IP address of the length=
file server where PM OBS daily WMS Small Cells, 256
files are pushed by Small Cell. It example:
is either of the format of FQDN 172.60.111.5.
or IP address, for example, Using the WPS Small
135.168.0.1 or xxx.yyy.com,. Cells navigate to
FGWConfig > ItfFgw >
SubscriberTraceCon-
fig and set the value.
subscriberTra- This is the feature flag for False boolean True { True,
ceEnable subscriber trace. Using the WPS Small False }
Cells navigate to
FGWConfig > ItfFgw >
SubscriberTraceCon-
fig and set the value.
Note: A child object SubscriberTrace MO must be created under SubscriberTrace-

Config, to define the IMSI to obtain subscriber trace.
Table 4-29 </FGW:<DN>/ItfFgw:1/SubscriberTraceConfig:1 / SubscriberTrace:1>

Value ted
Values
IMSI This is an input parameter to string Any IMSI configured length=16

invoke RF Trace on a particular in HNLR, example:
UE 262900000003131.
....................................................................................................................................................................................................................................
Issue 5 April 2014
subscriber trace
....................................................................................................................................................................................................................................
Table 4-29 </FGW:<DN>/ItfFgw:1/SubscriberTraceConfig:1 /
SubscriberTrace:1> (continued)

Value ted
Values
traceId A trace identifier assigned to the string Example: 003 length-3

subscriber trace. It must be
unique within the list of traces
being configured.
traceDuration Defines the time duration of the 120 integer Values must be 15..240]
trace. multiples of 15. That step=15
is, 15 or 30 or 45 or units=
60 upto 120 mins
traceReporting- This parameter defines the time t800 Using the WPS Small The value
Period interval with in which, the trace Cells navigate to can either
file must be reported to the file FGWConfig > ItfFgw > be, t60 or
server. SubscriberTraceCon- t900 or
fig > SubscriberTrace t1800 or
and set the value. t3600
administra- Defines the administrative state locked enum unlocked

tiveState of the managed object. The Admin- Using the WPS Small
administrative state can be istra- Cells navigate to
changed by a set ACTION. tiveState FGWConfig > ItfFgw >
SubscriberTraceCon-
fig > SubscriberTrace
and set the value.
Table 4-30 <IPC/1 : LIPC/1 : SubscriberTraceConfig:1 >

Value Values
sftpServer This attribute defines the sftp PM string IP address of the length=256
file server where PM OBS daily WMS Small Cells,
files are pushed by Small Cell. It example:
is either of the format of FQDN 172.60.111.5.
or IP address, for example, The value can also
135.168.0.1 or xxx.yyy.com,. be set using WPS
Small Cells.
Navigate to IPC >
LIPC >
SubscriberTrace-
Config , and set
the value.
subscriberTra- This is the feature flag for False boolean True { True, False }
ceEnable subscriber trace.
rootDirectory This attribute defines the root /opt/ string length=100
directory for Subscriber Trace nortel/
files to be pushed to on the FMS dat
File Server. a/utran/
trace
....................................................................................................................................................................................................................................
Issue 5 April 2014
subscriber trace
....................................................................................................................................................................................................................................
Table 4-30 <IPC/1 : LIPC/1 : SubscriberTraceConfig:1 > (continued)

Value Values
userName To be used by the IPC to string Example: fgwuser Give a user

authenticate with the file server name which is
defined in
WMS Small
Cells server or
any other
server.
password Password to be used by the IPC Provide a

to authenticate with the file password for
server. This string is set to an which defined
empty string if no authentication the username.
is required.
isSshKeyAu- Indicates if key is authenticated boolean True If key is

thenticationDone between the IPC and FMS. authenticated
between IPC
and FMS, set
the attribute
value as True.
sftp is
performed
with out the
password, else
attribute set as
False and
sftp is
performed
with password
defined.
Note: A child object SubscriberTrace MO must be created under SubscriberTrace-

Config, to define the IMSI to obtain subscriber trace.
Parameter name Description Default Syn- Value Permitted Values

Value tax
IMSI This is an input parameter to string Any IMSI length=16

invoke RF Trace on a particular configured in
UE HNLR,
example:
262900000003131.
traceId A trace identifier assigned to the string Example: 003 length-3

subscriber trace. It must be unique
within the list of traces being
configured.
traceDuration Defines the time duration of the 120 inte- Values must be 15..240] step=15
trace. ger multiples of 15. units=mins
That is, 15 or 30
or 45 or 60
upto 120
....................................................................................................................................................................................................................................
Issue 5 April 2014
subscriber trace
....................................................................................................................................................................................................................................
Table 4-31 <IPC/1 : LIPC/1 : SubscriberTraceConfig:1 > (continued)
Parameter name Description Default Syn- Value Permitted Values

Value tax
traceReporting- This parameter defines the time t800 The value can
Period interval with in which, the trace either be, t60 or
file should be reported to the file t900 or t1800 or
server. t3600
administra- Defines the administrative state of locked enum unlocked
tiveState the managed object. The AdministrativeState
The value can
administrative state can be also be set using
changed by a set ACTION. WPS Small
Cells. Navigate
to FGWConfig >
ItfFgw >
Subscriber-
TraceConfig >
SubscriberTrace
, and set the
value.
Table 4-32 <Femto <dn> : BSRProfile : SubscriberTraceConfig/1 >
Parameter name Description De- Syntax Value Permitted

fault Values
Value
sftpServer This attribute defines the sftp PM string IP address of the length=256
file server where PM OBS daily WMS Small
files is pushed by Small Cell. It is Cells, example:
in either of the format of FQDN 172.60.111.5.
or IP address, for example,
135.168.0.1 or xxx.yyy.com,.
subscriberTra- This is the feature flag for False boolean True { True, False }
ceEnable subscriber trace. In the WPS
Small Cells
under
Femto<dn>/
BSRProfile /
SubscriberTraceConfig,
set the value.
....................................................................................................................................................................................................................................
Issue 5 April 2014
subscriber trace
....................................................................................................................................................................................................................................
Table 4-33 </FGW:<DN>/ItfFgw:1/SubscriberTraceConfig:1>

Value Values
subscriberTra- This is the feature flag for False boolean False { True, False
ceEnable subscriber trace. Using the WPS }
Small Cells
navigate to
FGWConfig >
ItfFgw >
Subscriber-
TraceConfig and
set the value.

Value Values
subscriberTra- This is the feature flag for False bool- False { True, False }
ceEnable subscriber trace. ean In the WPS
Small Cells
under IPC /
LIPC /
set the value.
Table 4-35 <Femto <dn> : BSRProfile : SubscriberTraceConfig/1>

Value Values
subscriberTra- This is the feature flag for False boolean False { True, False }
ceEnable subscriber trace. In the WPS
Small Cells
naviagte to
Femto <dn> >
BSRProfile >
set the value.
Impacted services
None
....................................................................................................................................................................................................................................
Issue 5 April 2014
subscriber trace
....................................................................................................................................................................................................................................
WPS Small Cells No
WMS Small Cells No

HDM No

Small Cell Yes
IPC Yes
IPsec Router No
BPG No
BVG No
BSG Yes
AAA No
SCMS No
Security Gateway Management System No

None.
Duration
N/A
Downtime
None
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 119110 - Static IP address
....................................................................................................................................................................................................................................
119110 - Static IP address

Overview
This feature enables the Small Cell access point obtain a static IP using a temporary
DHCP server.
The Small Cell access point retrieves IP configuration data from a temporary DHCP
server, and stores it in the Small Cell NOR flash memory. The temporary DHCP server
can be disconnected after the IP configuration has been saved. Once the static IP has been
configured, on subsequent restart, the Small Cell access point uses the saved IP
configuration for IP transport setup.
Note: First start up after a factory reset requires access to a temporary DHCP server,
as the Small Cell does not retain the static IP configuration after a factory reset.
Purpose
This topic describes the activation and deactivation procedures for static IP address
(119110) feature.

Perform the following steps to configure the temporary DHCP server:
...................................................................................................................................................................................................
1 In the temporary DHCP server edit the /etc/dhcpd.conf file. Add the following sample
entry:
option vivso 00:00:02:7D:03:01:01:01;
#####Static IP set to true ###########
:02:08:30:31:30:32:30:33:30:34;
#:03:06:31:32:33:34:35:36;
Sample dhcpd.conf with Small Cell details:
option vivso 00:00:02:7D:03:01:01:01;
#####Static IP set to true ###########
:02:08:30:31:30:32:30:33:30:34;
#:03:06:31:32:33:34:35:36;
option dhcp-parameter-request-list 1, 28, 3, 6, 125;
default-lease-time 2;
max-lease-time 4;
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
max-lease-time 3600;
interface eth0;
#platform3
host femto-4011070052 {
hardware ethernet 50:67:f0:52:8a:27;
fixed-address 172.65.102.119;
option subnet-mask 255.255.255.128;
option routers 172.65.102.1;
option domain-name-servers 172.65.126.10;
option domain-name "iprc.nlt.in";
}
...................................................................................................................................................................................................
2 Restart the temporary DHCP server.

Note: Whenever the dhcpd.conf is modified, the temporary DHCP server must be
restarted.
...................................................................................................................................................................................................
3 Restart the Small Cell.

Result: Lights on the Small Cell device flash for 10 seconds and the Small Cell starts
up.
Note: On subsequent Small Cell restart, the Small Cell uses the saved IP.
...................................................................................................................................................................................................
4 Ensure that in the file /var/opt/alu/fbsr/bcManager/mode_selected, the value of

mode_selected is 2.
The parameter mode_selected can have the following values:
Permitted values for mode_selected Meaning

1 updated PPPoE
2 static IP
3 inventory PPPoE
4 DHCP
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
5 Once the Small Cell is operational, in the HDM navigate to a registered Small Cell,
navigate to Devices > Manage Devices > Queue Function > Parameter Value > Get
Parameter Values. A new Get Parameter Values window opens, navigate to Services >
BSR > 1. Ensure that the attribute ipTransportAccesscontrolMode has the value
none.
E...................................................................................................................................................................................................
N D O F S T E P S

Perform a Small Cell factory reset to deactivate the feature.
Impacted services
None.
WPS Small Cells No

WMS Small Cells No
HDM No
Small Cell Yes Small Cell must be restarted to
activate/deactivate the feature.
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No
SCMS No

System
DHCP server Yes

The Small Cell does not retain the static IP configuration after a factory reset.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Duration
NA
Downtime
Approximately 10 minutes for restarting the Small Cell.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 157214 - PPPoE configuration
....................................................................................................................................................................................................................................
157214 - PPPoE configuration

Overview
This feature enables installation of a Small Cell access point using a temporary DHCP
server.
The Small Cell access point retrieves Point-to-Point Protocol over Ethernet (PPPoE)
configuration data from a DHCP server, and stores it in the Small Cell NOR flash
memory. The temporary DHCP server can be disconnected after the IP configuration has
been saved. Once the PPPoE configuration has been configured, on subsequent restart,
the Small Cell access point uses the saved PPPoE configuration for IP transport setup.
Challenge Handshake Authentication Protocol (CHAP) and Password Authentication
Protocol (PAP) are supported for authentication using DHCP configured username and
password.
Note: First start up after a factory reset requires access to a DHCP server, as the Small
Cell does not retain the PPPoE configuration after a factory reset.
Purpose
This topic describes the activation and deactivation procedures for PPPoE configuration
(157214) feature.

Perform the following steps to configure the DHCP server:
...................................................................................................................................................................................................
1 In the DHCP server edit the /etc/dhcpd.conf file. Add the following sample entry:
To enable CHAP
# CHAP is enabled and PAP is disabled
option vivso 00:00:02:7D:17:01:01:01:02:07:73:6f:76:61:72:61:
6a:03:06:6e:65:77:73:79:73:04:01:01;
To enable both CHAP and PAP
# CHAP and PAP is enabled
option vivso 00:00:02:7D:17:01:01:01:02:07:73:6f:76:61:72:61:
6a:03:06:6e:65:77:73:79:73:04:01:00;
To enable PAP
# PAP is enabled
option vivso 00:00:02:7D:14:01:01:01:02:07:73:6f:76:61:72:61:
6a:03:06:6e:65:77:73:79:73;
Sample dhcpd.conf with Small Cell details:
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
max-lease-time 4;
max-lease-time 3600;
interface eth0;
#platform3
host femto-4011070052 {
hardware ethernet 50:67:f0:52:8a:27;
option subnet-mask 255.255.255.128;
option routers 172.65.102.1;
option domain-name-servers 172.65.126.10;
option domain-name "iprc.nlt.in";
option vivso 00:00:02:7D:14:01:01:01:02:07:73:6f:76:61:72:61:6a:
03:06:6e:65:77:73:79:73; ### Static IP Enable, PPPoe User
(testuser) Password (testpassword)
option vivso 00:00:02:7D:17:01:01:01:02:07:73:6f:76:61:72:61:
6a:03:06:6e:65:77:73:79:73:04:01:01;
# CHAP is enabled and PAP is disabled
# option vivso 00:00:02:7D:17:01:01:01:02:07:73:6f:76:61:72:
61:6a:03:06:6e:65:77:73:79:73:04:01:00;
# CHAP and PAP is enabled
option dhcp-parameter-request-list 1, 28, 3, 6, 125;
}
...................................................................................................................................................................................................
2 Restart the DHCP server.

Note: Whenever the dhcpd.conf is modified, the DHCP server must be restarted.
...................................................................................................................................................................................................
3 Restart the Small Cell.

Result: Lights on the Small Cell device flash for 10 seconds and the Small Cell starts
up.
Note: On subsequent Small Cell restart, the Small Cell uses the saved IP.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
4 Ensure that in the file /var/opt/alu/fbsr/bcManager/mode_selected, the value of

mode_selected is 1.
The parameter mode_selected can have the following values:
Permitted values for mode_selected Meaning

1 updated PPPoE
2 static IP
3 inventory PPPoE
4 DHCP
...................................................................................................................................................................................................
5 Once the Small Cell is operational, in the HDM navigate to a registered Small Cell,
navigate to Devices > Manage Devices > Queue Function > Parameter Value > Get
Parameter Values. A new Get Parameter Values window opens, navigate to Services >
BSR > 1. Ensure that the attribute ipTransportAccesscontrolMode has the value
pppoe.
E...................................................................................................................................................................................................
N D O F S T E P S

To deactivate the feature the Small Cell device requires a factory reset operation.
Impacted services
None.
WPS Small Cells No

WMS Small Cells No
HDM No
Small Cell Yes Small Cell must be restarted to

activate/deactivate the feature.
IPC No
IPsec Router No
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
BPG No
BVG No
BSG No
AAA No
SCMS No
DHCP server Yes

System

The Small Cell does not retain the PPPoE configuration after a factory reset.
Duration
NA
Downtime
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 119911 - Assisted GPS using proprietary TCS solution
....................................................................................................................................................................................................................................
119911 - Assisted GPS using proprietary TCS solution

Overview
This feature enables the use of an assisted GPS, using TeleCommunication Systems
(TCS) proprietary interface, to be used for GPS localization and location lock.
The GPS localization (75545) feature, uses an 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. This mechanism can take a long time
to determine the location, and results in a long startup time when location verification is
required before the Small Cell starts transmitting.
An assisted GPS, where GPS assistance data is provided through the network to the GPS
receiver, provides better performance of GPS location detection, providing better
sensitivity, higher accuracy, and faster time to first fix (TTFF).
This feature provides a solution to implement the assisted GPS on the Small Cell, to
improve its capability to perform GPS location detection and therefore reduce startup
time when geographic location verification is required before the Small Cell starts
transmitting.
The GPS assistance data is provided by TCS, using a proprietary interface to their
Assistance Data Server (ADS).
Note: The Assisted GPS clients (Small Cells) and Assisted GPS Caching Proxy are
Alcatel-Lucent network elements, and the TCS ADS is a customer provided network
element.
Purpose
This topic describes the activation and deactivation procedures for Assisted GPS using
proprietary TCS solution (119911) feature.

Configuring using WMS Small Cells:
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Create a AGPSProxy object under the existing FGWConfig.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

proxyType as cachingProxyTCSADS
addressServer as <value>
portServer as <value>
authorisationIdentity as <value>
ipAddressClientProxyLocal as <value>
ipAddressServerLocal as <value>
portClientProxyLocal as <value>
portProxyServer as <value>
timerConnectionReestablishmentDelay as 60
timerPeriodicRefresh as 1800
For more information regarding the <value> for attributes of AGPSProxy MO, see
Managed objects involved in activation (p. 4-101).
...................................................................................................................................................................................................
4 Navigate to Network > FemtoCluster > BSRClusterProfile > AGPS and set the following
values:
assistancePort - Port number that the Small Cell uses to send AGPS request to
BSR Gateway. Set assistancePort with value, same as the portClientProxy-
Local value of the AGPSProxy MO.
proxyAddress - Contains FQDN or IP address of the BSR Gateway. Set
proxyAddress with value, same as the ipAddressClientProxyLocal value of
the AGPSProxy MO.
...................................................................................................................................................................................................
5 Navigate to Network > FemtoCluster > Femto and set the following values:
Parameter name Definition Default value Permitted values
aGPSclientType Defines the types of AGPS assistanceDataServ- { assistanceDataServerTCS=

client. erTCS 0,agpsServerTypeSpare1=1,
agpsServerTypeSpare2=2,
agpsServerTypeSpare5=5 }
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Parameter name Definition Default value Permitted values
aGPSLocationSource Defines the source of the expected { expected=0,

estimated location that is referenceAndLastKnown=9,
used by AGPS. spare1=1, spare2=2,
When set as expected, it is spare3=3, spare4=4,
the provisioned expected spare5=5 }
location of the device.
When set as
referenceAndLastKnown, it
is the coarse AGPS
reference location when
there has been no previous
location detected or
movement has been
detected and the last
known location if
movement of the device
has not been detected.
aGPStimerConnectionDe- Defines the initial time that 20 [6..3600] units=secs
layInitial the AGPS client waits
between attempts to
re-establish
communication with a
server/proxy following
failure. This is the initial
value for a timer, that
doubles on each failure,
until the maximum is
reached. On reaching the
maximum value the AGPS
client continues to use that
value as the wait time.
aGPStimerConnectionDe- Defines the maximum time 320 [6..14400] units=secs
layMax that the AGPS client waits
between attempts to
re-establish a
communication link with a
server/proxy following
failure.
aGPStimerPeriodicRefresh Defines the interval 1800 6..6900] units=secs
between periodic refreshes
of GPS assistance data.
...................................................................................................................................................................................................
6
latitude as the latitude of Small Cell.
longitude as the longitude of Small Cell.
geographicalLocationConfigured as True.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
Managed objects involved in activation

Managed object in the BSR Gateway:
Table 4-36 AGPSProxy
Parameter Description Syntax Permitted values Default value

name
proxyType Specifies the type of enum { cachingProxyTCSADS= cachingProxyTC-

AGPSproxy. AgpsProxy- 0,agpsServerTypeSpare1= SADS
Type 1,
agpsServerTypeSpare2=
2,
3,
4,
agpsServerTypeSpare5=5
}
addressServer This attribute provides string length=50
the IP address or FQDN
of the AGPS Server.
ipAddressServ- This is the IP address ipAddress
erLocal that is used by the Proxy
Server for the Proxy.
This IP address is on the
same subnet and VLan as
the PhysicalInterfaceS/B
MOI that has
interfaceType set as
FemtoOamProxy and
hence uses the same
defaultGateway.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 4-36 AGPSProxy (continued)

name
portProxyServer This is the source integer 8895 [1024..65535]

portnumber used by the
AGPSProxy for
connections towards the
AGPS Server.
portServer This attribute provides integer 8895 [0..65535]
the destination port
number used for
connections to the AGPS
Server.
authorisation- Contains the identity string length=128

Identity used by the AGPS Server
to authorize the source of
the request.
ipAddressCli- Provides the IP address ipAddress
entProxyLocal of the AGPS Proxy (the
destination address) used
by AGPS clients.
portClient- Port that the AGPS integer [1024..65535] 8895

ProxyLocal Proxy listens to for
connection requests from
AGPS clients.
timerConnec- Defines the time that the unit 16 10..3600] units=secs 60
tionReestablish- AGPS Proxy waits to
mentDelay establish a
communication link with
the AGPS Server,
following failure.
timerPeriodicre- Defines the interval unit 16 [6..6900] units=secs 1800
fresh between periodic
refreshes of GPS
Assistance Data from the
AGPS Server.
Managed object in the Small Cell:
Table 4-37 AGPS
Parameter name Description Syntax Permitted values Default value
proxyAddress Contains the FQDN or IP ipAddress length = 128

Address of the assisted
GPS proxy.
assistancePort Specifies the transport layer integer [0..65535] 8895

port used for the assistance
protocol.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 4-38 GPS
aGPSLocation- Defines the source of the enum { expected=0, expected

Source estimated location used by referenceAndLastKnown=9,
AGPS. spare1=1, spare2=2,
spare3=3, spare4=4,
spare5=5 }
expected - expected
location of the device
is provisioned.
referenceAndLast-
Known - coarse
AGPS reference
location when there
has been no previous
location detected or
movement has been
detected and the last
known location if
movement of the
device has not been
detected.
aGPSclientType Defines the types of AGPS enum { assistanceDataServerTCS=0, assistanceDataServ-
client. agpsServerTypeSpare1=1, erTCS
agpsServerTypeSpare5=5 }

The feature gets deactivated once the GPS fix is obtained.
Deactivate using WPS Small Cells
To disable the feature on subsequent Small Cell startup, using the WPS Small Cells, set
the parameter aGPSclientType as agpsServerTypeSpare1.
Impacted Services
None
WPS Small Cells Yes
WMS Small Cells Yes
HDM Yes
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Small Cell Yes AGPS client

IPC No
IPsec Router No
BSR Gateway Yes
AAA No
System

NA

NA
Downtime
NA
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 123830 - UE-based Assisted GPS
....................................................................................................................................................................................................................................
123830 - UE-based Assisted GPS

Overview
niIt may be required to locate precisely a UE inside the wireless network, for emergency
calls as well as commercial value added services. Currently, as the coverage of a Small
Cell is less, the location of the access point is sufficient to approximate the location of a
mobile user within the Small Cell. However, with the introduction of Metro Cells the cell
radius can be larger than 100 m, and the location method may not be sufficient, especially
to comply with E911 Phase II regulations in the US.
UEs equipped with a GPS receiver can provide an accurate position, however, when the
GPS signal is weak (for example, indoors far from the window), an autonomous GPS
receiver may fail to get a location fix within an acceptable time. The GPS receiver has to
be equipped with a GPS Assistance data (for example, Ephemeris and Almanac data) to
improve the performance of the GPS receiver..
The GPS assistance data is provided by TeleCommunication Systems (TCS), using a
proprietary interface to their Assistance Data Server (ADS). The ADS receives GPS
assistance data from a global reference network (Xypoint Reference Network, or XRN)
and then parses and stores the applicable reference data.
On request from a Location Server (LS), the ADS assembles requested assistance data
and sends it to the LS in HTTP response. When a Small Cell access point has to provide
GPS assistance data to a UE, it requests the GPS assistance data from the TCS ADS
server.
In order to avoid swamping the TCS ADS server, direct queries from the Small Cell
access point to the TCS ADS are avoided. Instead, a caching proxy function inside the
Small Cell network periodically collects the GPS assistance data from the ADS and
provides this data to a Small Cell access point on request.
Note: The proxy/cache function has already been introduced as part of feature
119911- Assisted GPS using proprietary TCS solution. See 119911 - Assisted GPS
using proprietary TCS solution (p. 4-98).
Purpose
This topic describes the activation and deactivation procedure for the UE-based Assisted
GPS (123830) feature.
Before you begin

Ensure that:
Feature 119911- Assisted GPS using proprietary TCS solution is configured. See
119911 - Assisted GPS using proprietary TCS solution (p. 4-98).
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
To configure using WMS Small Cells
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
3 The AGPSProxy MO defines the following interfaces:

BSR Gateway and the TCS ADS
BSR Gateway and the Small Cells
Create a AGPSProxy object under the existing FGWConfig.
...................................................................................................................................................................................................

proxyType as cachingProxyTCSADS
addressServer as <value>
portServer as <value>
authorisationIdentity as <value>
ipAddressClientProxyLocal as <value>
ipAddressServerLocal as <value>
portClientProxyLocal as <value>
portProxyServer as <value>
timerConnectionReestablishmentDelay as 60
timerPeriodicRefresh as 1800
For more information regarding the <value> for attributes of AGPSProxy MO, see
Managed objects involved in activation (p. 4-101).
...................................................................................................................................................................................................
5 Navigate to Network > FemtoCluster > BSRClusterProfile > AGPS and set attribute
ueBasedAGPSEnabled as True. See Managed objects in the BSR Gateway
(p. 4-107).
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
6 Navigate to Network > FemtoCluster > Femto and set the AGPS attributes, see
(p. 4-108).
...................................................................................................................................................................................................
7
latitude as the latitude of Small Cell.
longitude as the longitude of Small Cell.
geographicalLocationConfigured as True.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
9 Create a WorkOrder and export it to the WMS Small Cells.

...................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S

Table 4-39 BSR
Parameter name Description Value Default Syntax Permitted

Value Values
ueBasedAGPSEn- Feature flag for UE-Based True False boolean { True,

abled Assisted GPS. False }
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 4-40 AGPS
Parameter name Definition Syntax Default value Permitted values
clientProfile Configuration of sequence [0..10]

each type of profiles, of struct A
e.g. Emergency or GPSProfile
Value Added
Services, and so on.
referenceTimeAl- Allowed Reference boolean True { True, False }
lowed Time assist data to
be sent to UE.
almanacSatellite- Allowed Almanac boolean True { True, False }
HealthAllowe d and Satellite Health
assist data to be sent
to UE.
utcModelAllowed Allowed UTC boolean True { True, False }

Model assist data to
be sent to UE.
ionosphericModelA- Allowed Ionospheric boolean True { True, False }
llowed Model assist data to
be sent to UE.
realTimeIntegrityAl- Allowed Real Time boolean True { True, False }

lowed Integrity assist data
to be sent to UE.
navigationModelAl- Allowed navigation boolean True { True, False }

lowed model assist data to
be sent to UE.

The feature gets deactivated once the GPS fix is obtained.
Deactivate using WPS Small Cells
Navigate to Network > FemtoCluster > BSRClusterProfile > AGPS and set attribute
ueBasedAGPSEnabled as False. See Managed objects in the BSR Gateway
(p. 4-108).

Table 4-41 BSR
Parameter name Description Value Default Syntax Permitted

Value Values
ueBasedAGPSEn- Feature flag for UE-Based Assisted False False boolean { True,
abled GPS. False }
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Impacted services
None
WPS Small Cells Yes
WMS Small Cells Yes

HDM Yes

Small Cell Yes
IPC No
IPsec Router No
BSR Gateway Yes
AAA No
SCMS No

None.
Duration
N/A
Downtime
None
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 125544 - AMR frame concatenation with preemption
....................................................................................................................................................................................................................................
125544 - AMR frame concatenation with preemption

Overview
Feature 125544 enables the support of emergency voice calls, with good voice quality, in
case the backhaul is shaped to 64 kbps. If the Small Cell is to serve as an alternative to the
fixed line, then the Small Cell must support a minimum number of simultaneous
emergency calls. For example, with a 64 kbps backhaul, using the proposed concatenation
format and a rtpMuxperiod equaling 40 ms, a minimum of two emergency calls can be
simultaneously handled.
The AMR frame concatenation reduces the bandwidth required for an emergency call, by
multiplexing two voice frames from the same voice call into a single RTP PDU. This
would reduce the bit rate (at IP layer) required to support the voice call from 57.6 kbps to
35.2 kbps.
As part of the preemption mechanism, concurrent Small Cell traffic (such as normal
CS/PS call or NTP or FMS) must be terminated/suspended, or a CS call must be
redirected to Macro (if available and if CS preemption is enabled), in order to free up the
resources for the emergency calls. The proposed design corresponds to the split BVG
architecture.
Purpose
This topic describes the activation and deactivation procedures for AMR frame
concatenation with preemption (125544) feature.
Before you begin

An additional BVG instance must be configured in the BSR Gateway, that is, another
IP address, to serve the user-plane emergency traffic. The Small Cell must coordinate
with the following two IP addresses:
IP address of the BVG residing on the SeGW, which facilitates the normal CS user
plane non-emergency traffic.
IP address of the BVG instance on the BSR Gateway which facilitates the
emergency traffic when the feature is enabled.
To enable the end-to-end functionality of the feature, the Downlink (D/L) AMR Frame
Concatenation Port Number and Uplink (U/L) AMR Frame Concatenation Port
Number must be exchanged using the appropriate BSGAP signaling.

....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to Network > FGWConfig, set attributes amrDlConcatPort as 4000 and

amrFrameConcatMode as EmergencyCSV.
...................................................................................................................................................................................................
3 Navigate to Network > BSRProfile, locate attribute sparePara27 set values for
afcbvgipaddr and afcbvgportno, with the IP address and port number of the BVG.
...................................................................................................................................................................................................
4 Set the following attribute values:
Parameter name Value Permitted values
afcMode 1 {0,1}
afcPENECS 1 {0,1,2}
afcPENEPS 1 {0,1}
afcPENTP 1 {0,1}
afcTimer 40 {40, 50, 60}
afcnemmax 12 {1...12}
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
To configure a Small Cells Cluster with IPC
Note: In case of a Small Cells Cluster with IPC the following network elements must
be configured, in addition to the WPS Small Cells configuration
IPC
Alcatel-Lucent 7750 Service Router (7750 SR)
SeGW
Note: The parameter values used in the following procedure must be changed as
applicable to the customer's network design. Configure the values as per the operating
network. Following parameter values are examples:
BVG IP address = 172.24.26.7
Port numbers = 2/1/3 vlan 417
RoutingTableEntry = 5
GICCVirtualRouter = 2
IPC configuration
Perform the following steps to configure the IPC to accommodate the additional BVG
residing in the BSG:
...................................................................................................................................................................................................
1 Create a new file addRoutingTable.cli, with the following content:

create (LIPC=1,RoutingTableEntry=5)\
administrativeState=UNLOCKED\
rtDestIPAddr=" <IP-address> "\
rtDestIPMask=" <IP-address> "\
rtNextHop=" <IP-address> "\
refGICCVirtualRouter="(LIPC=1,GICCVirtualRouter=2)"
...................................................................................................................................................................................................
2 Execute the following command:

execute /flx/RNCinitdb/current/bin/meosCli s addRoutingTable.cli
...................................................................................................................................................................................................

/flx/RNCinitdb/current/bin/meosCli
Set (LIPC=1,GICCVirtualRouter=2) refListRoutingTableEntry=
["Integer.LIPC.1.Integer.RoutingTableEntry.4.",
"Integer.LIPC.1.Integer.RoutingTableEntry.2.",
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
"Integer.LIPC.1.Integer.RoutingTableEntry.5."]
E...................................................................................................................................................................................................
N D O F S T E P S
7750 SR configuration
The Virtual Private LAN Service (VPLS) must be configured to facilitate traffic between
the 7750 SR and the additional BVG. Perform the following steps:
...................................................................................................................................................................................................
1 Execute the following commands to create VPLS 417 (VPLS used for the second BVG).
A:SR-401A>config>service> vpls# info
----------------------------------------------
description "to FGW-401-A eth2-CSUP"
stp
shutdown
exit
sap 2/1/3:417 create
exit
sap ccag-1.b:417 create
exit
spoke-sdp 100:417 create
exit
no shutdown
----------------------------------------------
...................................................................................................................................................................................................
2 Execute the following command to add the routing information in VPRN 2, to facilitate
the cnCSUP traffic to IPC:
static-route 172.24.26.0/28 next-hop 172.24.17.4
...................................................................................................................................................................................................

/flx/RNCinitdb/current/bin/meosCli Set (LIPC=1,GICCVirtualRouter=
2) refListRoutingTableEntry=
["Integer.LIPC.1.Integer.RoutingTableEntry.4.",
"Integer.LIPC.1.Integer.RoutingTableEntry.2.",
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
"Integer.LIPC.1.Integer.RoutingTableEntry.5."]
E...................................................................................................................................................................................................
N D O F S T E P S
SeGW configuration
In the SeGW, UDP port 4000 is used for communication between the UE group and the
BSG. Perform the following steps to configure the SeGW:
...................................................................................................................................................................................................
1 Log in to the SeGW GUI. Navigate to the Host Group Editor and configure all the UE
groups as shown in the following image:
...................................................................................................................................................................................................
2 Add the IP address of the BVG to the host BSG.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Navigate to the Service Group Editor and add UDP port 4000 for IuCS.
...................................................................................................................................................................................................
4 Navigate to the Brick Zone Ruleset Editor, and enable UDP port 4000 to facilitate the
flow of traffic between the UE groups and BSG in the Front End Zone.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
5 Enable UDP port 4000 to facilitate the flow of traffic between the UE groups and BSG in
the BSG Zone.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 4-42 BSR
Parameter Description Syntax Value Comments

name
sparePara27 Spare parameter 27. string afcbvgipaddr=<IP address>

length=50 afcbvgportno=<port no>
sparePara37 Spare parameter 37. Used string afcMode=1 afcPENECS

to enable the feature. length=50 afcPENECS=1 can be set
between 0
afcPENEPS=1 and 2.
afcPENTP=1 afcPENEPS
afcTimer=40 can be set
as 0 or 1.
afcnemmax=12
Managed objects in BSR Gateway
Table 4-43 FGW
Parameter Description Syntax Value Default value Permitted

name values
amrDlConcat- This attribute integer 4000 4000 [0..65535]

Port provides the port
number used for
the AMR
downlink
concatenation
port.
amrFrameCon- This attribute enum AfcMode EmergencyCSV Disabled {Disabled=0,
catMode specifies the EmergencyCSV=1}
classes of traffic
which apply
AMR frame
concatenation.

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to BSRProfile, locate attribute sparePara37 and set the following values:
Parameter name Value
afcMode 0
afcPENECS 1
afcPENEPS 1
afcPENTP 1
afcTimer 40
afcnemmax 12
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S

Managed objects in BSR Gateway
Table 4-44 FGW

name values
amrDlConcat- This attribute integer 4000 4000 [0..65535]

Port provides the port
number used for
the AMR
downlink
concatenation
port.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 4-44 FGW (continued)

name values
amrFrameCon- This attribute enum AfcMode Disabled Disabled {Disabled=0,

catMode specifies the EmergencyCSV=1}
classes of traffic
which apply
AMR frame
concatenation.
Table 4-45 BSR
Parameter name Description Syntax Value
sparePara37 Spare parameter 37. Used to string afcMode=0

enable the feature. length=50 afcPENECS=1
afcPENEPS=1
afcPENTP=1
afcTimer=40
afcnemmax=12
Impacted services
There is a downtime of approximately 5-10 minutes when the BSR Gateway is restarted.
WPS Small Cells No

WMS Small Cells No
HDM No

Small Cell Yes Enabling the feature routes the
emergency traffic to the BSG
instance of the BVG , instead of the
SeGW instance of the BVG.
IPC No
IPsec Router No
BPG No
BVG Yes An additional BSG instance of the
BVG is created.
BSG Yes BSG requires to be restarted.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
AAA No

System

The features has the following limitations:
This feature is supported only on a Sun Netra based BSR Gateway.
This feature is not supported in an AIOG architecture.
Duration
Approximately 10-15 minutes.
Downtime
There is a downtime of approximately 5-10 minutes when the BSR Gateway is restarted.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 158467 - 32 PS user capacity for V2 Enterprise and Metro AP
....................................................................................................................................................................................................................................
158467 - 32 PS user capacity for V2 Enterprise and Metro AP

Overview
Feature 158467 enables the support of up to 32 Packet Switched (PS) users on a single V2
Enterprise/Metro Small Cell access point, based on PC333 Picochip baseband solution.
The number of supported active users depends on the RAB combination supported per
user.
The following PS combinations are supported:
Call type Maximum no of calls supported
R99 32
HS 32
E-DCH 16
15 DCH+ 9 E-DCH+ 24 CS 24 CS + PS
Purpose
This topic describes the activation and deactivation procedures for 32 PS user capacity for
V2 Enterprise and Metro AP (158467) feature.

...................................................................................................................................................................................................
1 In the WPS Small Cells, locate snapshot exported from WMS Small Cells. Import the
...................................................................................................................................................................................................
2 Navigate to the BSRProfile selected for this feature. Set the parameters
additionalFemtoUserCapacityLicensing as 2, numCellDCHUE as 32 and
hardwareProfile as 250mW-32users.
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S

Table 4-46 LCell
Parameter Description Syntax Value Default Permitted values

name value
additional- This parameter defines the integer 2 0 {0, 1, 2}

FemtoUser- number of user capacity tokens
CapacityLi- needed for a Small Cell. Each
censing token represents 8 users. A
Small Cell with a token value
of 0, supports up to 16 users.
numCellD- Indicates the maximum integer 32 16 [1..64]
CHUE number of UEs the Small Cell
can admit (capped to the
maximum number supported
by the platform).
hardwarePro- This attribute is for the 250mW- 250mW- 250mW-16users,

file hardware template/profile that 32users 16users 250mW-24users,
the SCMS applies for the 250mW-32users
configuration data. If it is
empty, then the default profile
for the hardware type is used
when creating the bulkcm file
by the SCMS.

Table 4-47 LCell
Parameter Description Syntax Value Default Permitted values

name value
additional- This parameter defines the integer 0 0 {0, 1, 2}

FemtoUser- number of user capacity tokens
CapacityLi- needed for a Small Cell. Each
censing token represents 8 users. A
Small Cell with a token value
of 0, supports up to 16 users.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Impacted services
Feature activation requires the Small Cell to be restarted. Hence there is a downtime of
approximately 10 minutes, during which services are disrupted.
WPS Small Cells No
WMS Small Cells No

HDM No

Small Cell Yes The configuration file is downloaded
in the Small Cell, which must be
restarted for feature activation.
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No
System

None.
Duration
NA
Downtime
Approximately 10 minutes to restart the Small Cell.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 76986 - Cell broadcast services in support of CMAS
....................................................................................................................................................................................................................................
76986 - Cell broadcast services in support of CMAS

Overview
This feature provides support of the Commercial Mobile Alert System (CMAS) service
within the Small Cell network
The CMAS service is specific to the US market and is established by the Federal
Communications Commission (FCC). 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 send 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 onto the
correct Small Cells that have been addressed by the CBC.
Purpose
This topic describes the activation and deactivation procedures for Cell broadcast services
in support of CMAS (76986) feature.

To modify attribute cellBroadcastService using WPS Small Cells
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Navigate to Network > FWConfig and set attribute cellBroadcastService as True.

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
work order file.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
9 Once the work order is successfully launched, and select Activate.

...................................................................................................................................................................................................
10 Repeat Step 1 and Step 2.

...................................................................................................................................................................................................
11 Navigate to Network > ItfFGW and create object IuBC.

Set the following parameters:
administrativeState as locked
cellBroadcastFailureWaitTimer as 120
cellBroadcastRestartWaitTimer as 120
ipAddressCellBroadcastLocal as IPAddress
ipAddressCellBroadcastPrimary as IPAddress
ipAddressCellBroadcastSecondary as IPAddress
keepAliveIntvl as 4
keepAliveProbes as 3
keepAliveTCP as True
keepAliveTime as 10
maximumTransientProcedureThreshold as 200000
overloadCauseValue as 6
retryTimer as 5
spareParameter1 as " "
timerFailover as 120
userLabel as " ".
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
12 Navigate to Network > ItfFGW > IuBC and set attribute administrativeState as
unlocked.
...................................................................................................................................................................................................
13 Navigate to Network > FemtoCluster > BSRProfile and set the following values:
cbsEnable as True
lacCBS between [1..65535], exclude 65534
sacCBS between [0..65535].
...................................................................................................................................................................................................
14 Repeat Step 4 through Step 9.

E...................................................................................................................................................................................................
N D O F S T E P S
Procedure to add PPID 31 using IPSec router GUI

...................................................................................................................................................................................................
1 login to the IPSec router GUI as admin user.

...................................................................................................................................................................................................
2 In the left side pane, navigate to system>Policies>Brick Zone Rulesets and double click
on the relevant folder for SCTP association between Femto and BSG.
...................................................................................................................................................................................................
3 Click on the Frontendzone and navigate to the rule that caters to the Femto BSG SCTP
association.
...................................................................................................................................................................................................
4 If the option Enable SCTP is checked, manually enter the value 31 in the Add New PPID
attribute and press Enter.
...................................................................................................................................................................................................
5 Navigate back to Frontendzone box, click on File and select save and apply option to
save the new PPID.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Managed objects in the BSG:
Table 4-48 BSG

name
cellBroadcast- This attribute controls boolean { True, False } False

Service the enabling or disabling
of CBS on the BSR
Gateway. When set as
True the service is
enabled.
Managed objects in Small Cell:
Table 4-49 BSR
lacCBS LAC for the broadcast integer [1..65535]

domain Note: 65534 is not a valid
entry.
sacCBS SAC for the broadcast integer [0..65535] 0
domain.
Table 4-50 BSRProfile
cbsEnable Feature flag for CBS. boolean {True, False} False

...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Navigate to Network > ItfFGW > IuBC and set attribute administrativeState as
locked.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
4 Navigate to Network > FWConfig and set attribute cellBroadcastService as False.

...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
work order file.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
10 Once the work order is successfully launched, and select Activate.

E...................................................................................................................................................................................................
N D O F S T E P S
Impacted services
Services are interrupted when the BSR Gateway state changes between locked and
unlocked state. And Small Cell requires a restart during activation/deactivation.
WPS Small Cells Yes

WMS Small Cells No
HDM No

Small Cell Yes BulkCM download and reboot is
required during activation and
deactivation of the feature.
IPC No
IPsec Router Yes The rule governing SCTP layer

between BSR and FGW is impacted.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
BSR Gateway Yes The NE must be Locked/Unlocked

during activation and deactivation of
the feature.
AAA No
System

The feature supports only IP transport, ATM transport is not supported.

NA
Downtime
There is an outage during activation and deactivation, as the Small Cell requires a restart.
And BSR Gateway state changes between locked and unlocked state, which interrupts
operation.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 124168 - DPDK support on BSR Gateway
....................................................................................................................................................................................................................................
124168 - DPDK support on BSR Gateway

Overview
This feature deals with improving the number of bearer plane packets per second treated
on the BSR Gateway Application (BGA) boards.
The usage of Intel Data Plane Development Kit (DPDK) enables drastic improvement of
the number of packets treated per second by the BONO card, from 406 000 over six cores
to more than one million packets per core.
This feature facilitates tackling the capacity degradation brought by the AIOG
architecture compared to the classical architecture. Furthermore, the usage of the Intel
DPDK is a mandatory enabler for the integrated IPC feature.
Purpose
This topic describes the activation and deactivation procedures for DPDK support on
BSR Gateway (124168) feature.
Related information
The DPDK feature:
is supported only for BSR Gateway on the ATCA platform.
is supported only on RHEL version 6.2 or higher.
must be disabled before downgrading to Small Cell versions lesser than release
BCR4.3
The BONO card must be manually rebooted to disable the DPDK feature.

To configure through WMS Small Cells
...................................................................................................................................................................................................

...................................................................................................................................................................................................
2 Navigate to Configuration > Object Editor.

...................................................................................................................................................................................................
3 Locate the appropriate FGW cluster from the drop-down menu.

...................................................................................................................................................................................................
4 Select FGW<DN>/FGWConfig/1. Set attribute sparePara1 as enableDPDK=True.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
5 Click Apply all changes.

E...................................................................................................................................................................................................
N D O F S T E P S

Table 4-51 BSRProfile::sparePara1

name values
enableD- Parameter to enable the boolean False {True, True

PDK feature False}

...................................................................................................................................................................................................

...................................................................................................................................................................................................
2 Navigate to Configuration > Object Editor.

...................................................................................................................................................................................................
3 Locate the appropriate FGW cluster from the drop-down menu.

...................................................................................................................................................................................................
4 Select FGW<DN>/FGWConfig/1. Set attribute sparePara1 as " ".

...................................................................................................................................................................................................
5 Click Apply all changes.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

name values
enableD- Parameter to enable the boolean False {True, False

PDK feature False}
Impacted services
The BSR Gateway requires to be restarted, hence there is an outage during that period.
WPS Small Cells Yes

WMS Small Cells Yes
HDM Yes
Small Cell No
IPC No
IPsec Router No
BSR Gateway Yes The BSR Gateway requires to be
restarted
AAA No
System
Duration
NA
Downtime
TheBSR Gateway requires to be restarted, hence there is an outage during that period.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Small Cell specific features 117826 - Multiple Operator Core Network
....................................................................................................................................................................................................................................
117826 - Multiple Operator Core Network

Overview
The Multiple Operator Core Network (MOCN) is a solution where two or more operators
share common RAN in certain areas or even in the whole network but do not share their
core networks. Small Cell cluster was capable of supporting connection to only one
operator core network nodes based on the one operator, one radio access network
principle. The implementation of MOCN feature allows multiple core network operators
to share Small Cell cluster and its network elements (Small Cell, SeGW,SCMS) in a
shared area based on UTRAN network sharing principles. One specific CN operator can
also have several pooled MSCs/SGSNs connected to the Small Cell cluster and this
functionality will be supported in combination of Iu-flex feature (75387) function already
available in Small Cell network elements.
Purpose
This topic describes the activation and deactivation procedures for the Multiple Operator
Core Network (122611) feature.
Before you begin

Ensure that:
Small Cell Gateway is upgraded to BCR 4.3.2 release.
Activate IuFlex feature for CS and PS in SeGW as specified in 75397 - IuFlex for
IuCS and IuPS (p. 1-2).
Small Cell is upgraded to BCR 4.3.2 release.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Create MOCN objects as follows:

Navigate to Network > FWConfig and create MOCN/1.
Navigate to Network > FWConfig and create MOCN/2.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
4 Configure HPLMN in each MOCN operator as follows:

Navigate to Network > FWConfig > MOCN/1 and set
hPLMNPlmnIdentityMcc=OP1_mcc.
hPLMNPlmnIdentityMnc=OP1_mnc.
superLACActivation=SuperLACNotActive.
hPLMNPlmnIdentityMcc=OP2_mcc.
hPLMNPlmnIdentityMnc=OP2_mnc.
superLACActivation=SuperLACNotActive.
...................................................................................................................................................................................................
5 Create Iu links and IuFlex configurations as specified in 75397 - IuFlex for IuCS and
IuPS (p. 1-2).
...................................................................................................................................................................................................
6 Navigate to Checks and click Run checks.....

...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
9 Navigate to Configuration > Sessions Manager create a new session and locate the work
order file.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
11 Select Activate once the work order is successfully launched.

...................................................................................................................................................................................................
12 Repeat Step 1 and Step 2.

...................................................................................................................................................................................................
13 Navigate to Network > FWConfig and set mocnEnable as true.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................
16 Activate the MOCN feature in Small Cell as follows:

Navigate to Network > Profile > BSRProfile and set mocnEnable as true.
Navigate to Network > Profile > BSRProfile and set mocnRedirectionTimer between
Integer (10..20).
...................................................................................................................................................................................................
17 Create MOCN objects in BSR Profile as follows:

Navigate to Network > Profile > BSRProfile and create MOCN/1.
Navigate to Network > Profile > BSRProfile and create MOCN/2.
...................................................................................................................................................................................................
18 Configure Split NRI Table as follows:

Navigate to Network > Profile > BSRProfile and set nriMaskSize [1...10].
Navigate to Network > Profile > BSRProfile and set sparePara6 with nriPSMaskSize.
For example, nriPSMaskSize=10.
Navigate to Network >Profile > BSRProfile and create SplitNriTable. Upto 100 tables
can be created and set as provided in the following table.
Navigate to Network > Profile > BSRProfile > SplitNriTable and set nriEndValue.
Navigate to Network > Profile > BSRProfile > SplitNriTable and set
nriStartValue.
Navigate to Network > Profile > BSRProfile > SplitNriTable and set pLMN.
...................................................................................................................................................................................................
19 Configure IMSI range in sparePara38. For example, MOCN1_IMSIRange=788..789

MOCN2_IMSIRange=790..791.
...................................................................................................................................................................................................
20 Redirect network and default MOCN operator configuration in the LocationProfile.

Navigate to Network > LocationProfile> BSRLocationProfile and set
defaultMocnOperatorForRedirectionMcc.
defaultMocnOperatorForRedirectionMnc.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
mocnOperatorSelection to splitNRIs or defaultMocnOperator.
defaultMocnOperatorRef to MOCN/1 or MOCN/2.
...................................................................................................................................................................................................
21 Configure common PLMN as follows:

Navigate to Network > LocationProfile> BSRLocationProfile> LCell set
ownPLMNMCC.
Navigate to Network > LocationProfile> BSRLocationProfile> LCell set
ownPLMNMNC.
...................................................................................................................................................................................................
22 Create MOCN objects in LocationProfile as follows:

Navigate to Network > LocationProfile> BSRLocationProfile createMOCN/1.
Navigate to Network > LocationProfile> BSRLocationProfile createMOCN/2.
...................................................................................................................................................................................................
23 Configure HPLMN in each MOCN operator as follows:

Navigate to Network > LocationProfile> BSRLocationProfile > MOCN/1 set
hPLMNMCC=OP1_mcc.
hPLMNMNC=OP1_mnc.
hPLMNMCC=OP2_mcc.
hPLMNMNC=OP2_mnc.
...................................................................................................................................................................................................
24 Create MOCN objects in FemtoCluster.

Navigate to Network > FemtoCluster> Femto > create MOCN/1.
Navigate to Network > FemtoCluster> Femto > create MOCN/2.
...................................................................................................................................................................................................
25 Repeat Step 6 through Step 11 to complete the process.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 4-53 BSR
Parameter name Description Syntax Value Default value
The following are the new MIM attributes in BSR MO for the MOCN feature.
mocnEnable Feature flag for MOCN feature boolean True False

support.
mocnOperatorSelection Option for selecting MOCN operator enum {defaultMocnOperator,

splitNRIs
for non-supporting UE. MocnOp- detectedMacroPLMN,
eratorSe- splitNRIs}
lection
defaultMocnOperatorRef Reference to default MOCN operator dn class=

for non-supporting UE. An empty MOCN
value is allowed if the feature is
disabled.
defaultMocnOperator- PLMN Id of the MOCN operator struct
ForRedirection sharing the Small Cell to be used for PLMNID
redirecting emergency or
non-emergency call during RRC
connection rejection.
splitNriTable This attribute allows nonoverlapping sequence

NRI value allocations to different [0..100] of
MOCN operators. Unique NRI value struct
range per operator shall be used. SplitNri-
Table
nriMaskSize This attribute defines the size of NRI integer [1..10]
mask. This value is the number of
bits of the received NRI, from the
most significant downwards, that
shall be used for selecting MOCN
operator.
mocnRedirectionTimer Timer for controlling the redirection integer [10..20], 20
procedure for nonsupporting UE. unit=secs
Small Cell supports new MOCN MO in the BSR MIM. When MOCN feature is enabled, number of MOCN
instances are more than one
Class Description Derived Named by DN range

from
MOCN MO for Small Cell network sharing BSRTop BSR [1..9999999]

by Multi-Operator Core Network.
MOCN MO contains the following new attribute
Parameter Name Description Syntax Value
hPLMN PLMN Id of the MOCN operator struct

sharing the Small Cell. It is part of PLMNID
the Multiple PLMN List broadcast in
the Master Information Block.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Parameter name Description Syntax Value Default value
plmnMacroUMTSCellFre- Indicates the list of Macro cell sequence

quencyList UMTS neighbour cell frequencies of [0..10] of
the PLMN. struct
FDDFre-
quencyList
plmnGsmFrequencyList Indicates the GSM frequency list of sequence
the PLMN. [0..10] of
struct
GSMFre-
quencyList
Type name Field name Descrip- Syntax Permitted

tion value
SplitNriTable pLMN PLMN Id string length=10

in the
format of
<MCC>:<MNC>
SplitNriTable nriStartValue The start integer
value of
NRI
SplitNriTable nriEndValue The end integer
value of
NRI
PLMNID mcc The string length=3
Mobile
Country
code
PLMNID mnc The string length=3
Mobile
Network
code
The following existing MIM attributes get included in MOCN MO to configure per
operator specific values for various features
ePLMN support for camping and umtsMacroEPLMN

notification (b76976)
gsmMacroPLMN
enableOwnPLMNHighPriority
prioritizeOwnPLMNoverRAT
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Home tariff and visitor's differentiated fullnameofNetwork

support (b1718, b75544)
shortnameofNetwork
fullnameofNetwork2
shortnameofNetwork2
areaSelectNormalFlag
areaSelectEmergencyFlag
saSAC1
laLAC1
saSAC2
laLAC2
saSAC3
laLAC3
Prioritized Open Access (b77735) laLAC4
saSAC4
enableDynamicLACpublic
enableDynamicSACpublic
fullnameofNetwork3
shortnameofNetwork3
Super LAC feature (b79495) AIalignSAI
replaceLocationReportSAI
Dynamic LAC-SAC Allocation (b78695) dSAthresholdRSCP
dSAthresholdEcNo
dSAthresholdRXLEV2G
enableDynamicSACowner
enableDynamicSACguest
enableDynamicSACEC
enableDynamicSACfemto
enableDynamicLACowner
enableDynamicLACguest
enableDynamicLACEC
enableDynamicLACfemto
samePLMNDynamicLACSAC
areaSelectFemto
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
RTCP for IuCSoIP (b120353) enableRtcp

rtcpTxInterval
rtcpCSdataTxInterval
Macro to Femto HO (75389, 75390, 83083) maxUmtsCellsRegister
virtualCellIdUmts
maxGsmCellsRegister
virtualCellIdGsm
Self-Optimization (Macro cell list ratioGSMCellAboveThreshold
optimization)
Software support for 850/1900 dual band umtsPreferredBand
Femto (b78691)
gsmPreferredBand
Handover attributes targetHOCS
targetHOPS
targetHOCSPS
sBCsRabMappingTable
sBtargetHOFddFreqCS
sBtargetHOFddFreqCSPS
Managed objects in the Small Cell Gateway
Small Cell Gateway supports the following new MIM attributes in FGW MO for MOCN
feature.
Parameter Description Syntax Values Default
Name
mocnEnable This attribute boolean True False
defines
whether the
Multiple
Operator
Core
Network
feature is
activated or
not. When set
to True the
feature is
enabled.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Small Cell Gateway supports the new MOCN MO in FGW MIM.

Class name Description Derived Named by DN range Cardinality
from
MOCN This class UnForced- FGW [1..9999999] [0..4]
models the Manage-
small cell dResource
network
shared by
Multi-
Operator
Core
Network.
MOCN MO contains the following new attribute.
Parameter Description Syntax Values Default
name
hPLMN This attribute struct PLMN
represents the
PLMN Id of
the MOCN
operator
sharing the
Small Cell
network.
superLA- This enum SuperLAC-
CActivation parameter SuperLAC- NotActive
activates and Status
deactivates
the Super
LAC feature
for the
MOCN
operator
Type name Field name Description Syntax Permitted Default
values value
PLMN plmnIdenti- PLMN string length = 3
tyMcc Identity
value,
subfield
MCC
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
PLMN plmnIdenti- PLMN string length = 3

tyMnc Identity
value,
subfield
MNC

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to Network > BSRProfile, set parameter mocnEnable as False.

...................................................................................................................................................................................................
3 On the main window, navigate to Checks and click Run checks.....

...................................................................................................................................................................................................
4 Create a WorkOrder and export to WMS Small Cells.

...................................................................................................................................................................................................
5 Log in to WMS Small Cells as administrator.

...................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................
8 Once the work order is successful, select Activate.

...................................................................................................................................................................................................
snapshot intoWPS Small Cells.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
11 Navigate to Network > FWConfig and set attribute mocnEnable as False.

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S

Table 4-54 BSR
Parameter name Description Syntax Values Default value
mocnEnable Feature flag for MOCN feature boolean False False

support.
Managed objects in Small Cell Gateway
Table 4-55 BSR
Parameter name Description Syntax Values Default value
mocnEnable This attribute defines whether the boolean False False

Multiple Operator Core Network
feature is activated or not. When set
to True the feature is enabled.
Impacted services
The FGW::mocnEnable can be set to true through BSGCLI, but must not be disabled
through BSGCLI. The MOCN feature can be deactivated through bulkcm only.
Network Element Impact
WPS Small Cells No

WMS Small Cells Yes
HDM No

Small Cell Yes
IPC No
IPsec Router No
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Network Element Impact
BPG No
BVG No
Small Cell Gateway Yes
AAA No
Duration
NA
Downtime
For activating/deactivating the feature the Small Cell requires to be restarted, hence there
is a temporary downtime.
....................................................................................................................................................................................................................................
Issue 5 April 2014
5 Services features
5
Overview
Purpose
This chapter describes the activation/deactivation procedure for the Small Cell Services
Features.
Contents
83021 - Presence API 5-2

75399 - Home network local routing 5-11
76974 - Enhanced PM processing for BSG counters 5-16
114380 - DHCP options (60, 125, 43) 5-21
89552 - Network overload avoidance 5-25
...................................................................................................................................................................................................................................
Issue 5 April 2014
Services features 83021 - Presence API
....................................................................................................................................................................................................................................
83021 - Presence API

Overview
The Presence API feature creates an API to provide an External Application or Presence
Server (PS) with the ability to get presence information from the Small Cell System.
The PS has information regarding the UEs Present (either in idle or connected mode),
with in each Small Cell CPE. That is, the UEs under the coverage area of the Small Cell.
Presence status change (arrival/departure) is also provided by the Small Cell System.
Presence is a service that has wide and varied uses within communication networks. It
allows value added applications to be implemented based upon the presence state of UEs
within the Small Cell network. Presence state (known as a Presentity) conveys UE
location information in the network and information on the services they are currently
using, such as when busy with a CS call, to applications (known as Watchers). Watchers
can utilize the presence information as enablers for advanced services.
Purpose
This topic describes the activation and deactivation procedures for Presence API (83021)
feature through the BSG and WPS Small Cells.
Before you begin

Before configuring, ensure that:
Communication between the SCMS and the BSG is operational.
The SSH key is exchanged, to enable password-less sftp communication between the
SCMS and the BSG to download the Small Cell related information files to the BSG.

To configure the Presence API feature with WPS Small Cells
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 5-1 FGW:<DN>/BSG:<instance>/Presence:<instance 1 to 10>
presenceServer Represents the URI sip:172.60.121.2 or

for the Presence sip:presence.iprc.nl-
Server or Presence t.in
Application
uEType Represents the type authorisedAndUnau-
of UE report to be thorisedUEs or
sent to the Presence authorisedUEs
server.
psserverHeartbeat- This timer is used to 30 seconds
Time determine whether
the link to the
Presence Server is
still active. The
timer represents the
time to wait for a
response from the
Server for each
attempt to establish
contact. Setting the
counter to 0 disables
the check on the
link.
sipHeaderExpires- This timer represents 3600 seconds
Timer the lifetime of the
presence event. The
presence event is
either refreshed or
removed on the
expiration of this
timer.
operatorDomain This represents the 172.60.121.2 or
domain of the iprc.nlt.in
operator. When the
BSG publishes a
presence event, the
identity of the UE,
that the BSG is
publishing presence
on its behalf, is
IMSI@domain
sIPTimerT1 This timer represents rTT500 ms

the start time to be
used to wait for SIP
responses from the
network
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 5-1 FGW:<DN>/BSG:<instance>/Presence:<instance 1 to 10> (continued)
sIPTimerT2 This time represents limit4000 ms

the upper limit on
the round-trip time
to wait for SIP
responses from the
network. This time
must be set to a
value greater than
sIPTimerT1
sIPTimerT4 This time represents 5 seconds
the maximum
duration for an SIP
message to remain
in the network.
sipOptions This flag enables or True or False

disables the SIP
OPTIONS Method.
A setting of True
enables the Method.
Event Mapping 1 to13
Table
5-2 /FGW:<DN>/BSG<instance>/Presence:<instance>/PresenceeventMapping:<instance
1 to 13>
bsrEvent Represents the uEPresent or

Presence event incomingHandover-
received from the WithCSRAB or
Small Cell. cSRABSetup or
cSRABRelease or
outgoingHandover
or detach or uELost
or unAuthorisedUE
or transientUE or
expiry or refresh or
incomingHandover-
WithPSRAB or
incomingHandover-
WithCSRA-
BandPSRAB
standardEvent Represents the unknown or

Standard event that on_the_phone
the bsrEvent is
mapped to. A
Standard Event
contains one of the
following strings:
unknown or
on_the_phone.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 5-3 FGW:<DN>
activatePresenceAPI This attribute True

controls the enabling
or disabling of the
Presence API feature
on the BSG. If set to
True the feature is
enabled.
presenceFQDN This is the fully True

qualified domain
name that is used by
external Presence
servers and
applications to
contact the active
BSG node.
updateExpiryTimer This timer is used by 2160 mins
the BSG to remove
presence entries that
have not been
updated by the BSR
after the expiry of
the timer. A setting
of zero disables the
timer.
Table 5-4 /FGW:<DN>/BSG:<instance>
temporalUEPresen- This time interval 10 seconds

ceExpiryTime defines the wait time
for the BSG,
between publishing
and then removing
the presence events
published on the
Presence Server for
unauthorized and
transient UEs
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 5-4 /FGW:<DN>/BSG:<instance> (continued)
ueIdleTimer This attribute 364 minutes

indicates the time a
UE can remain in
idle state without
performing periodic
routing area update
procedure or
periodic location
area updating
procedure. The
value of this timer
must be set at least 4
minutes greater that
the higher of T3212
and T3312 in use in
the core network.
diffServCodePoin- This attribute dSCP0

tSIP defines the DiffServ
Code Point to be
used for the
Presence API
interface.
Table 5-5 PresenceNetwork/FemtoCluster:<cluster id>/Femto:<id>/Presence
monitoredDetection- Controls the low

Accuracy accuracy, to detect
whether a UE is still
present on the Small
Cell. At Low
Accuracy, the Small
Cell relies on
standard mobility
events. At High
Accuracy, the Small
Cell actively
determines if the UE
is still present based
upon the settings in
attribute
presenceHighAccu-
racyMonitoredDe-
tection.
monitoredDetection- Defines the number 3

MaxPagingRepeat- of repeated attempts
Attempts for paging, a Small
Cell performs, for
UE presence
detection.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 5-5 PresenceNetwork/FemtoCluster:<cluster id>/Femto:<id>/Presence
(continued)
monitoredDetec- Defines the amount 15 seconds

tionPagingRespon- of time in seconds,
seWaitTime the Small Cell waits
for a paging
response when it has
paged a UE for
presence detection.
reportUnauthorise- Controls whether True or False

dAccess presence is reported
for unauthorized UE
access to the Small
Cell.
Table 5-6 Network/FemtoCluster:<cluster

id>/Femto:<id>/PresenceHighAccuracyMonitoredDetectionProfile
detectionInterval Defines the interval 10 minutes

at which the Small
Cell checks for the
presence of the UE
periodically. The
value 0 means that
high accuracy
detection is disabled
for the period.
startTime Defines the time 00:00 hours
when the High
Accuracy Monitored
Detection starts. The
format is HH:MM.
endTime Defines the time 23:59 hours

when the High
Accuracy Monitored
Detection ends. The
format is HH:MM.
Table 5-7 Network/FemtoCluster:<cluster id>/Femto:<id>
presenceReportin- This is the flag to true

gActive determine whether
Presence Reporting
is Active on the
Small Cell.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 5-7 Network/FemtoCluster:<cluster id>/Femto:<id> (continued)
presenceReport- This parameter ALL

ingList specifies the list of
IMSIs for which UE
Presence reporting is
performed. The list
is defined as a
NULL terminated
string with
comma-separated
IMSI values. If the
string contains the
value ALL, it
indicates that all
IMSIs are included
for presence
reporting. If the list
is empty then UE
Presence is not
reported.
geographicalLoca- Flag to determine false
tionConfigured whether
geographical
location has been
configured.
Table 5-8 Network/Profile:<profile name>/BSRProfile:<id>
maxNumberOfU- The maximum 256

EDirectoryEntries number of UE
Directory entries
that are stored on the
Small Cell.

Table 5-9 /FGW:<DN>
activatePresenceAPI This attribute False

controls the enabling
or disabling of the
Presence API feature
on the BSG. If set to
True the feature is
enabled.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 5-10 Network/FemtoCluster:<cluster id>/Femto:<id>
presenceReportin- This is the flag to false

gActive determine whether
Presence Reporting
is Active on the
Small Cell.
Impacted services
None
WPS Small Cells No

WMS Small Cells No
HDM No
Small Cell Yes When this feature is activated, Small

Cell sends presence events to the
BSG for each and every UE activity.
IPC No
IPsec Router No
BSR Gateway Yes When this feature is activated, the

BSG processes presence events from
Small Cell and PUBLISH SIP
messages to Presence
Server/Application Server.
AAA No

System
Presence Server Yes Presence Server/Presence

Application Server integrated to
BSG.

None.

NA
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Downtime
None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Services features 75399 - Home network local routing
....................................................................................................................................................................................................................................
75399 - Home network local routing

Overview
The primary aim of the feature, home network local routing (75399), is to permit
applications in a UE, with in the coverage of a Small Cell, to use the services in the local
network. And the services are used with the same convenience, as experienced by users of
Wi-Fi connected devices. It provides sufficient local IP network connectivity, to support
commonly used network discovery and transport protocols. Home network local routing
provides convenient access, to the local network for the user. In addition, the operator
retains subscription-based control of the feature and visibility when the feature is in use.
It provides, local network access in a manner, compatible with existing data applications
at the UE.
Purpose
This topic describes the activation and deactivation procedures for the home network
local routing (75399) feature for Small Cell.
Before you begin

Before you begin, ensure that:
Small Cell is active and operational for CS/PS calls.
User is able to complete the blukcm config changes from WMS Small Cells.

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S

Table 5-11 BSR

comment
enableHomeNet- The flag enables/disables the True Default value is

workLocalRouting home network local routing False.
feature.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

comment
maxNumberOfU- The Maximum number of UE 256 Default value is 0

EDirectoryEntries Directory entries that is stored
on the Small Cell.
homeNetworkLo- The APN included by the UE iprc-hnlr This can be any

calRoutingAPN in an Activate PDP Context string value which
Request message, for which the is not known to the
Small Cell provides the home CN.
network local routing service.
validHomeNet- The APN which the Small Cell True any string which
workLocalRoutin- substitutes for the needs to be
gAPN homeNetworkLocalRoutin- configured at CN
gAPN when detected in an (APN terminating
Activate PDP Context Request. in CN itself)
If this item is not present the
APN in the Activate PDP
Context Request is not altered.
enablePrioritize- When set as True, permits only True Default value is
dAccessHNLR users with IMSIs in the Small True.
Cell Access Control List to
activate a home network local
routing context. When set as
False, permits all users to
activate a home network local
routing context.
gTPUMaintenance- Used to send ICMP echo 0 Default value is 0
TimerHNLR through GTP-U regularly, to
maintain HNLR PDP Context
with core network. If the value
is 0, ICMP Echo is not used to
maintain GTP-U.
hNLRPagingRe- Defines the amount of time in 20 Default Value is 20
sponseWaitTime seconds the Small Cell waits
for a paging response when it
has paged a UE for HNLR.
hNLRPagingRe- Defines the number of repeat 3 Default value is 3.

peatAttempts attempts for paging that a
Small Cell performs for UE
HNLR.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

comment
enableHNLRFor- When set as True the Small False Default value is

wardMulticastInIdle Cell pages a PMM Idle mode False.
UE to move it to PMM
Connected and deliver
multicast or broadcast frames
from the local network.
Otherwise the UE is moved to
PMM Connected when a
directly addressed frame is
received for the UE. The local
network can have significant
volumes of multicast/broadcast
traffic, enabling this attribute
can adversely affect battery life
of the UE.
passLocalHome- When set as True, the uplink True Default value
NetworkLocalRout- frames bearing IP traffic with a isTrue.
ingTraffic destination address in the local
network is passed to the local
network. Downlink frames
bearing IP traffic with a source
address in the local network is
passed to the UE. When set as
False, this local traffic is
discarded by the Small Cell.
homeNetworkLo- IP address of the home network

calRoutingIC- local routing ICMP Echo
MPEchoServer server. When set as 0 (or not
present) the DNS server
supplied by the GGSN is used
instead.
The Small Cell can pass, a list of up to 20 network addresses and netmasks. All other
traffic is dropped. Examples: 0.0.0.0/0 specifies the entire internet. 1.2.3.4/32 specifies an
individual IP address. If the list is empty, all traffic is dropped. The passLocalHome-
NetworkLocalRoutingTraffic is independent of the passHomeNetworkLocal-
RoutingNetworkList.
Table 5-12 BSR:passHomeNetworkLocalRoutingNetworkList
networkIpAddress The IP address part 0.0.0.0.0

of a network
address.
netMask The net mask length 0
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 5-13 BSR
enableHomeNet- The flag False Default value is

workLocalRouting enables/disables the false.
Home network local
routing feature.
Impacted Services
There is no impact on any service on activation/deactivation of this feature, as the
attributes are not of type RW-RR.
WPS Small Cells No

WMS Small Cells No
HDM No
Small Cell No
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No

System.

None.

The feature can be activated/deactivated in a fraction of a second without interrupting any
other services.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Downtime
None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Services features 76974 - Enhanced PM processing for BSG counters
....................................................................................................................................................................................................................................
76974 - Enhanced PM processing for BSG counters

Overview
This feature introduces an enhanced Performance Management collection mechanism for
BSG counters. This new mechanism enables managing the enhanced functionality of PM
counter treatment, such as temporal aggregation, alarm on performance threshold, alarm
on performance processing.
PM data collection device is introduced for BSG counters, in order to provide classical
management of the data and introduce a PM framework, that enhances PM capabilities.
The scope of this feature is on the SCMS system, and requires no change in the BSG
equipment.
Another important functionality of this feature, is temporal aggregation of PM files.
Hourly and daily aggregation of PM files.
In case of hourly aggregation, PM files are generated every hour at XX:23 Hrs.
Navigate to /opt/nortel/data/utran/observation/stats/<Date>/FGW-<FGW-User-Label>
directory, for example:
/opt/nortel/data/utran/observation/stats/20110211/FGW-FGW-901,
where Date = 20110211 and FGW-User-Label = FGW-901 and execute the command
ls-lrt:
-rw-rw-rw- 1 oamops oamgroup 1524 Feb 11 05:23
A20110211.0400+0530-0500+0530_FGW=FGW-901.xml.gz (Hourly aggregation
file for 0400-0500 Hrs)
In case of daily aggregation, PM files are generated every day at 01:23 Hrs. Daily
aggregation file of X day, is generated at X+1 day 01:23 hours (Once the 1st hourly
aggregation file of X+1 day is generated, then daily aggregation file of X is generated and
is available under X day directory).
Navigate to /opt/nortel/data/utran/observation/stats/<Date>/FGW-<FGW-User-Label>
directory, for example:
/opt/nortel/data/utran/observation/stats/20110211/FGW-FGW-901,
where Date = 20110211 and FGW-User-Label = FGW-901 and execute the command
ls-lrt:
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
A20110210.0000+0530-0000+0530_FGW=FGW-901.xml.gz
Purpose
This topic describes the activation and deactivation procedures for Enhanced PM
processing for BSG counters (76974) feature.

...................................................................................................................................................................................................
1 This feature cannot be activated or deactivated. The main functionality of this feature is to
raise Threshold and Synthetic Alarms based on the counters available in the BSG PM
files. These threshold values must be defined in the SCMS. The alarms are raised, only if
the threshold values are defined.
E...................................................................................................................................................................................................
N D O F S T E P S
Defining threshold alarms

Perform the following steps to define the threshold values to raise and clear the alarms:
...................................................................................................................................................................................................
1 Log in to the WMS Small Cells terminal as an oamops user.

...................................................................................................................................................................................................
2 Navigate to /opt/nortel/data/custom/utran/ directory.

...................................................................................................................................................................................................
3 Edit the CP_APM_FMS_FGWThresholdDef.xml file.

...................................................................................................................................................................................................
4 For example, consider the following entry:

<THD class="FGW/BVG" counter="VS.TotalULBVGPkts" severity=
"MAJOR" compOp="GREATER" startValue="50008" endValue="49000"
refPeriod="0"/>
This entry implies that, when the value of VS.TotalULBVGPkts is greater than 50008,
SCMS raises a MAJOR alarm, until the counter value becomes lesser than 49000.
...................................................................................................................................................................................................
5 On modifying the cfg file, the PM server must be restarted. Execute the following
commands:
To shut down:
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
/opt/nortel/shell/sysmgt/wam_stopgroup.sh utran_pm
To start:
/opt/nortel/shell/sysmgt/wam_startgroup.sh utran_pm
E...................................................................................................................................................................................................
N D O F S T E P S
Defining synthetic alarms

Perform the following steps to define the threshold values to raise and clear the alarms:
...................................................................................................................................................................................................
1 Log in to the WMS Small Cells terminal as oamops user.

...................................................................................................................................................................................................
2 Navigate to /opt/nortel/data/custom/utran/ directory.

...................................................................................................................................................................................................
3 Edit the CP_APM_FMS_FGWSynFormula_custom.cfg file, to define customer synthetic

counters.
...................................................................................................................................................................................................
4 For example, consider the following entry:

FGW/BSG/M3UA SHO.DATASUM = FGW/BSG/M3UA.VS.data + FGW/BSG/
M3UA.VS.duna;
This entry implies, that the synthetic counter SHO.DATASUM has to be defined under
FGW/BSG/M3UA. The value of SHO.DATASUM is the sum of VS.data and VS.duna
available under FGW/BSG/M3UA.
...................................................................................................................................................................................................
5 Edit the /opt/nortel/data/custom/utran/CP_APM_FMS_FGWThresholdDef.xml, and

define the corresponding threshold value, for example:
<THD class="FGW/BSG/M3UA" counter="SHO.DATASUM" severity="MAJOR"
compOp="GREATER" startValue="20" endValue="10" refPeriod="0"/>
...................................................................................................................................................................................................
6 When this value is greater that the threshold value, an alarm is raised.
...................................................................................................................................................................................................
7 On modifying the cfg file, the PM server must be restarted. Execute the following
commands:
To shut down:
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
/opt/nortel/shell/sysmgt/wam_stopgroup.sh utran_pm
To start:
/opt/nortel/shell/sysmgt/wam_startgroup.sh utran_pm
E...................................................................................................................................................................................................
N D O F S T E P S

This feature cannot be activated or deactivated.
Impacted Services
None
WPS Small Cells Yes

WMS Small Cells Yes
HDM No
Small Cell No
IPC No
IPsec Router No
BPG No
BVG No
BSG Yes
AAA No

System

NA

NA
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Downtime
NA
....................................................................................................................................................................................................................................
Issue 5 April 2014
Services features 114380 - DHCP options (60, 125, 43)
....................................................................................................................................................................................................................................
114380 - DHCP options (60, 125, 43)

Overview
This feature permits the local gateway identify the Small Cell through DHCP options, and
associate the Small Cell IP traffic with the provision of enhanced QoS over the backhaul.
The Small Cell includes DHCP options 60, 43 and 125, in the DHCP requests to the local
gateway. These options identify the manufacturer, device serial number, and product class
of the Small Cell to the local gateway.
The local gateway may include options 43 and 125 in DHCP responses, to the Small Cell.
The content of these options is logged by the Small Cell, but is otherwise ignored by the
Small Cell.
DHCP options (114380) feature allows the Small Cell present its manufacturer, model,
and serial number to the local gateway, with the DHCP options included in the DHCP
requests, sent to the DHCP server at the local gateway.
This is expected to be of use, in scenarios where the local gateway is able to selectively
provide enhanced quality of service to IP traffic. If the local gateway is able to identify its
Small Cell, then it can associate the Small Cell IP traffic with an enhanced QoS on the
backhaul.
For example, a residential gateway can maintain multiple PPP connections to the BRAS,
with differing QoS. Feature 114380, permits Small Cell IP traffic to be associated with a
PPP connection with appropriate QoS.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
The following image describes the DHCP exchange with the local gateway:
Purpose
This topic describes the activation and deactivation procedures for the Dynamic Host
Configuration Protocol (DHCP) options (60, 125, 43) (114380) feature.
Before you begin

Ensure that the 125 and 43 options are enabled in DHCP before it is enabled in the Small
Cell.

To configure with WPS Small Cells
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to Network, select the configured Small Cell profile. Set the enableDHCPop-
tions to true.
The DHCP exchange with the local gateway occurs early in the Small Cell
initialization, even before the MIM is available.
If the local exchange is not accomplished, before the MIM is available and the feature
is enabled, the Small Cell reboots to exchange the modified DHCP with the local
gateway.
E...................................................................................................................................................................................................
N D O F S T E P S
Table 5-14 BSR
Parameter name Description Value
BSR::enableDHCPoptions Enables or disables the feature. It is set as True

False by default.
Managed objects involved in deactivation
Table 5-15 BSR
BSR::enableDHCPoptions Enables or disables the feature. It is set as False

False by default.
Impacted services
None
WPS Small Cells No
WMS Small Cells No

HDM No
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Small Cell Yes If the local exchange is not

accomplished, before the MIM is
available and the feature is enabled,
the Small Cell reboots to exchange
the modified DHCP with the local
gateway.
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No
System

NA

NA
Downtime
NA
....................................................................................................................................................................................................................................
Issue 5 April 2014
Services features 89552 - Network overload avoidance
....................................................................................................................................................................................................................................
89552 - Network overload avoidance

Overview
The purpose of the Network Overload Avoidance feature is to protect the core network,
the BSG, and the IPC from getting overloaded and/or crashing, when there is an
unexpected increase in the number of registrations following a BSG failure.
The BSG is deployed in an active-standby configuration.
A redundant setup consists of two identical signaling gateways connected by an
(redundant) inter-BSG link. This inter-BSG link is used for BSG-internal state
synchronization. In case of failure of active node, the standby node takes over the
handling of the traffic in a seamless manner.
Only an active node can establish SCTP associations towards the core network and
receive calls from the CN. When there is a switchover from active to standby, the active
node establishes SCTP associations with the core network and the new standby node
terminates its existing associations.
The Network Overload Avoidance feature is designed to protect the CN, the BSG
(standby becoming active) and the IPC following a BSG (active) failure. When the
standby BSG becomes active, all the Small Cells register again and all UEs perform an
LA/RA update. Despite the existing 2 minutes spreading for a Small Cell registration, the
LA/RA update can create an overload in the BSG, IPC and CN.
This feature uses the standard Linux firewall functionality in the BSG to rate-limit the
incoming SCTP INIT messages, that is, slows down the rate at which the Small Cells
connect to the BSG.
Purpose
This topic describes the activation and deactivation procedures for Network Overload
Avoidance (89552) feature.
Before you begin

Ensure that the following entries are present in the /etc/sysconfig/iptables files at the
BSG:
-A RH-Firewall-1-INPUT -p sctp --chunk-types any INIT -m
limit --limit 100/sec --limit-burst 10 -j ACCEPT
-A RH-Firewall-1-INPUT -p sctp --chunk-types any INIT -j DROP
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Feature activation procedure using WMS Small Cells
Execute the following commands:
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Locate the appropriate FGW <DN> and set attributes sctpInitRateLimit as 200 and
sctpInitBurstSize as 20.
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
work order file.
...................................................................................................................................................................................................

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Managed objects in BSG:
Table 5-16 BSG:
Parameter name Description Command Default
sctpInitRateLimit This attribute defines the set Default: 1

maximum number of SCTP {sctpInitRateLimit=
If the sctpInitRateLimit is
INIT messages that the BSG 200};
set to a non zero value then
accepts per second. When this feature is enabled and
this rate exceeds the appropriate iptables rules are
messages are dropped. inserted.
sctpInitBurstSize This attribute defines the set
maximum burst size of {sctpInitBurstSize=
SCTP INIT messages that 20};
the BSG accepts. When this
limit is exceeded the
messages are dropped.

Managed objects in BSG:
Table 5-17 BSG:
Parameter name Description Command Value
sctpInitRateLimit This attribute defines the set Default: 1

maximum number of SCTP {sctpInitRateLimit=0};
If the sctpInitRateLimit is
INIT messages per second set as 0, the feature is
that the BSG accepts. When disabled and appropriate
this rate exceeds the iptables rules are cleared.
messages are dropped. Value
of 0, disables this feature.
Impacted Services
None
WPS Small Cells No
WMS Small Cells No

HDM No

Small Cell No
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
IPC No
IPsec Router No
BPG Yes In this feature, the BPG must be
restarted. Hence the traffic is
interrupted even though the BSG is
redundant.
BVG Yes As the BSG must be restarted after

enabling or disabling this feature,
even the BVG must be restarted.
Hence the traffic is interrupted even
though the BSG is redundant.
BSG Yes BSG must be restarted. Hence the
traffic is interrupted even though
BSG is redundant.
AAA No

System

NA

NA
Downtime
BSG must be restarted and hence there is downtime.
....................................................................................................................................................................................................................................
Issue 5 April 2014
6 Metro Small Cells features
6
Overview
Purpose
This chapter describes the activation/deactivation procedure for the Metro Small Cells
Features.
Contents
101681 - PM enhancements for Metro Small Cells 6-2

101373 - FM enhancements for Metro Small Cells 6-6
100854 - Optimized paging for large Metro cells deployments 6-12
92068 - ACL extension for large Small Cell Groups 6-18
111039 - Extended range cell 6-25
...................................................................................................................................................................................................................................
Issue 5 April 2014
Metro Small Cells features 101681 - PM enhancements for Metro Small Cells
....................................................................................................................................................................................................................................
101681 - PM enhancements for Metro Small Cells

Overview
This feature provides enhancements to Performance Management (PM) for
operator-managed Small Cells. It transfers the PM files, hourly, to the sftp server.
Purpose
This topic describes the activation and deactivation procedures for the PM enhancements
for Metro Small Cells (101681) feature, using the WPS Small Cells and HDM.
Before you begin

Ensure
The Small Cell is successfully activated in the HDM.
PM collection is activated in the Small Cell. And the sftpServer IP address and
transferTime are configured appropriately.

Note: To activate this feature, it is mandatory to configure both WPS Small Cells and
HDM.
To configure the feature through WPS Small Cells
Perform the following steps
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 In BSRProfile, set attribute transferFrequency as hour24 or hour1.

When set as hour24, the PM files are transferred from the Small Cell to the sftpserver,
once a day.
every hour.
...................................................................................................................................................................................................
3 Perform Run checks... on the BSRProfile.

...................................................................................................................................................................................................
4 Create a work order and copy it to WMS Small Cells.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
5 In the WMS, navigate to Configuration > Sessions Manager > Create New Session to
launch the work order.
...................................................................................................................................................................................................
6 The attribute is automatically updated in the Small Cell using the Set Parameter Value.
...................................................................................................................................................................................................
7 Once the Set Parameter Value operation is successful, verify the attribute using Get
Parameter Value from the HDM.
E...................................................................................................................................................................................................
N D O F S T E P S
To configure the feature through HDM

...................................................................................................................................................................................................
1 In the HDM, navigate to Manage Devices > Manage Femto > Queue Function and
perform the Set Parameter Values operation, on the Small Cell for the following
attributes:
transferFrequency= hour24 or hour1
once a day.
every hour.
...................................................................................................................................................................................................
2 Verify that the Set Parameter Value operation, is successful on the Small Cell.
E...................................................................................................................................................................................................
N D O F S T E P S

Table 6-1 <BSR:PM>
transferFrequency This is used to set hour1

the frequency of PM
uploading either in
one hour or one day.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Note: Once the transferFrequency is set as hour1, PM files are transferred to
sftpserver hourly, only after next daily PM file is transferred to sftpserver.

Table 6-2 <BSR:PM>
transferFrequency This is used to set hour24

the frequency of PM
uploading either in
one hour or one day.
Note: Once the transferFrequency is set as hour24, PM files are transferred to

sftpserver everyday, only after next hourly PM file is transferred to sftpserver.
Impacted services
None
WPS Small Cells Yes

WMS Small Cells Yes
HDM No
Small Cell Yes
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No
System

None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Downtime
None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Metro Small Cells features 101373 - FM enhancements for Metro Small Cells
....................................................................................................................................................................................................................................
101373 - FM enhancements for Metro Small Cells

Overview
Currently when a Small Cell is out of service, the operator is not informed. This is a
normal behavior, as the end user is in control of residential Small Cell operations.
However, when the Small Cells are deployed as public cells to complement the macro
network, there is a need for the operator to know in real time if those Small Cells are
active or out of service.
This feature provides the ability to keep the operator informed, of the operational state of
a limited number of Small Cells, in real time.
Purpose
This topic describes the activation and deactivation procedures for the FM enhancements
for Metro Small Cells (101373) feature.
It also describes the following 2-sub features, which are independent and can be activated
separately, based on user requirement:
Real-time monitoring of Small Cell status from the BSG.
Real-time state change notifications.
This feature consists of the following 2-sub features (both are independent and can be
individually activated as required) :
Real-time monitoring of Small Cell status from the BSG
Real-time state change notifications
Before you begin

Ensure that:
The Small Cell is successfully activated in the HDM.
The BSG-SCMS OAM link is functional.
Configuring real-time monitoring of Small Cell status from BSG

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to the BSRProfile selected for this feature. In the BSRPreprovision data, set the
attribute enableServiceMonitoring as True.
...................................................................................................................................................................................................
3 Set attributes bsrRegisterAfterFailureTimer as 600, bsrRegisterAfterInit-

Timer as 600 and maxNumBSRServiceAlarmsmust as 100.
...................................................................................................................................................................................................
4 Perform Run checks... on BSRPreprovision.

...................................................................................................................................................................................................
5 Create a work order and export it to WMS Small Cells.

...................................................................................................................................................................................................

...................................................................................................................................................................................................
work order file.
...................................................................................................................................................................................................

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
Configuring Real-time state change notifications

...................................................................................................................................................................................................
1 Export the snapshot from WMS Small Cells and import it to WPS Small Cells.
...................................................................................................................................................................................................
2 Navigate to the BSRProfile selected for this feature. Set attribute enableRealTimeSCN
as True..
...................................................................................................................................................................................................
3 Perform Run checks... on the BSRProfile.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
4 Create a work order and copy the work order to WMS Small Cells.
...................................................................................................................................................................................................
5 In the WMS Small Cells, navigate to Configuration > Sessions Manager > Create New
Session to launch the work order.
...................................................................................................................................................................................................
6 The attribute is automatically updated in the Small Cell using the Set Parameter Value
operation.
...................................................................................................................................................................................................
7 Once the Set Parameter Value is successful in the HDM, verify the attribute values by
uploading the database file from the Small Cell.
E...................................................................................................................................................................................................
N D O F S T E P S
To configure using HDM

...................................................................................................................................................................................................
1 In the HDM, navigate to Manage Devices > Manage Femto > Queue Function > Set
Parameter Values. Set attribute enableRealTimeSCN as true.
...................................................................................................................................................................................................
2 Verify that the Set Parameter Values operation is successful in the Small Cell.
E...................................................................................................................................................................................................
N D O F S T E P S
Managed objects involved in activation - Real-time monitoring of Small Cell status from BSG
activation
Table 6-3 <BSR>
enableServiceMonitoring This attribute controls the enabling True

or disabling of service monitoring
for the Small Cell. If set to true, the
generation of bsrOutOfService
alarms is enabled for the Small Cell.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 6-4 <FGW:BSG>
Parameter name Description Value Command
enableBSRServiceMoni- This attribute controls the True {enableBSRService

toring enabling or disabling of Monitoring=True};
service monitoring for the
Small Cell. If set as True,
the generation of
bsrOutOfService alarms is
enabled for the Small Cell.
bsrRegisterAfterFailure- This attribute represents 600 set
Timer the time, in seconds for the {bsrRegisterAfter
BSG to wait for a Small FailureTimer=600};
Cell to re-register before
sending the
bsrOutOfService alarm.
A timer is set in the Small
Cells for which SCTP
association failure is
detected. And it has the
BSR::enableService-
Monitoring attribute set
as True. If the timer
expires before the Small
Cell has re-registered the
bsrOutOfService alarm
is raised.
bsrRegisterAfterInitTimer This attribute represents 600 set
the time, in seconds for the {bsrRegisterAfter
BSG to wait for a Small InitTimer=600};
Cell to register before
sending the
bsrOutOfService alarm.
After the BSG
initialization, a timer is set
for Small Cells not
registered with the BSG
and have the BSR::
enableServiceMoni-
toring attribute set as
True. If the timer expires
before the Small Cell has
registered the
bsrOutOfService alarm is
raised.
maxNumBSRService- This attribute contains the 100 Set

Alarms threshold value for the {maxNumBSRService
number of pending Alarms=100};
bsrOutOfService alarms
reported to the SCMS.
Occurrences of the
bsrOutOfService alarm
beyond the threshold
value, are logged but not
reported to SCMS.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Managed objects involved in activation - Real-time state change notifications
The following WMS Small Cells objects must be modified:
Table 6-5 <BSR>
enableRealTimeSCN To enable/disable the real-time state True

change notification reporting to
SCMS.

Real-time monitoring of Small Cell status from the BSG
The following BSG object must be modified:
Table 6-6 <FGW:BSG>
enableBSRServiceMoni- This attribute controls the False {enableBSRService

toring enabling or disabling of Monitoring=false};
the Small Cell service
monitoring on the BSG. If
set as True, the generation
of Small Cell service
alarms is enabled at the
BSG.
Real-time state change notifications

The following WMS Small Cells managed object must be modified:
Table 6-7 <BSR>
enableRealTimeSCN To enable/disable the False

real-time state change
notification reporting to
SCMS.
Impacted services
None
WPS Small Cells Yes
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
WMS Small Cells Yes
HDM No
Small Cell Yes

IPC No
IPsec Router No
BSR Gateway Yes
AAA No
System

None.
Downtime
None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Metro Small Cells features 100854 - Optimized paging for large Metro cells
deployments
....................................................................................................................................................................................................................................
100854 - Optimized paging for large Metro cells deployments

Overview
The optimized paging for large Metro cells deployments feature, allows large
deployments of Metro cells, in public places, using the same Location Area / Routing
Area as the macro network.
Purpose
This topic describes the activation and deactivation procedures for Optimized paging for
large Metro cells deployments (100854) feature.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to the BSRProfile selected for this feature. Set the following parameters:
enableSameLaRaMacro as manual
accessMode as openAccess
...................................................................................................................................................................................................
3 In the BSRProfile, using the object creation operation, create the MacroLacRacList class.
...................................................................................................................................................................................................
4 Set LAC as 16000 and RAC as 160. Configure the same LAC/RAC values in the BSR
Gateway and Small Cell.
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
deployments
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
work order file.
...................................................................................................................................................................................................

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
Table 6-8 BSR
Parameter name Description Syntax Value Permitted Values
macroLacRacList List of macro sequence [0..100] of sequence [0..100] of sequence [0..100] of

LAC/RAC which struct MacroLacRac struct MacroLacRac struct MacroLacRac
may be configured
for same LA/RA as
Macro.
An array size of 0
indicates
notprovisioned.
LAC and RAC
values listed are to
be used by the Small
Cells, to be the same
as the Macro LAC
RAC.
....................................................................................................................................................................................................................................
Issue 5 April 2014
deployments
....................................................................................................................................................................................................................................
EnableSameLaRa- Used to enum manual { disable=0, gsm=1,

Macro enable/disable the fdd=2,
feature. gsmPreferred=3,
disable - disables fddPreferred=4,
feature manual=5 }
gsm - autoconfigure
from GSM
fdd - autoconfigure
from 3G
gsmPreferred -
autoconfigure from
GSM if available,
3G otherwise,
fddPreferred -
autoconfigure from
FDD if available,
GSM otherwise
manual - use the
manually configured
RAC/LAC as same
LA/RA as macro.

To deactivate through WPS Small Cells
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to the BSRProfile selected for this feature. Set parameter enableSameLaRa-
Macro as disable.
...................................................................................................................................................................................................
3 In the BSRProfile, delete the MacroLacRacList class.

...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Issue 5 April 2014
deployments
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
work order file.
...................................................................................................................................................................................................

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
Table 6-9 BSR
macroLacRacList List of macro sequence [0..100] of sequence [0..100] of sequence [0..100] of

LAC/RAC which struct MacroLacRac struct MacroLacRac struct MacroLacRac
may be configured
for same LA/RA as
Macro.
An array size of 0
indicates
notprovisioned.
LAC and RAC
values listed are to
be used by the Small
Cells, to be the same
as the Macro LAC
RAC.
....................................................................................................................................................................................................................................
Issue 5 April 2014
deployments
....................................................................................................................................................................................................................................
EnableSameLaRa- Used to enum disable { disable=0, gsm=1,

Macro enable/disable the fdd=2,
feature. gsmPreferred=3,
disable - disables fddPreferred=4,
feature manual=5 }
gsm - autoconfigure
from GSM
fdd - autoconfigure
from 3G
gsmPreferred -
autoconfigure from
GSM if available,
3G otherwise,
fddPreferred -
autoconfigure from
FDD if available,
GSM otherwise
manual - use the
manually configured
RAC/LAC as same
LA/RA as macro.
Impacted services
None
WPS Small Cells Yes

WMS Small Cells Yes
HDM No

Small Cell Yes Small Cell must be in the Open
Access mode.
IPC No
IPsec Router No
BSR Gateway Yes

AAA No
SCMS Yes
System
....................................................................................................................................................................................................................................
Issue 5 April 2014
deployments
....................................................................................................................................................................................................................................
None.
Duration
The feature is activated/deactivated in negligible time without interrupting any services.
Downtime
None
....................................................................................................................................................................................................................................
Issue 5 April 2014
Metro Small Cells features 92068 - ACL extension for large Small Cell Groups
....................................................................................................................................................................................................................................
92068 - ACL extension for large Small Cell Groups

Overview
This feature extends the ACL size of a Small Cell Group, to support large enterprise
deployments where thousands of employees are allowed to access a particular Small Cell
Group.
Purpose
This topic describes the activation and deactivation procedures for ACL extension for
large Small Cell Groups (92068) feature.
Related information
The same feature activation procedure is applicable for Small Cell support of extended
ACL size for large Small Cell Groups (121327) feature.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to the selected FemtoCluster. Create an object EnterpriseList, with Owner and
Guest ACL entries.
Enterprise<DN>
Owner<IMSI>
Guest<IMSI>
...................................................................................................................................................................................................
3 Set the attribute CSG Id.

Note: The attribute numberOfImsi is a Read-only attribute set by WMS Small Cells
automatically when generating the BSRINFO file.
...................................................................................................................................................................................................
4 Set attributes aclListRef as EnterpriseList and femtoACLlistIndicator as

fgwACL of the Small Cell Group.
...................................................................................................................................................................................................
5 Clear the values of FemtoACLlist and FemtoACLlistGuest attributes.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
8 Navigate to Configuration >> Sessions Manager >> Create new Session, to launch the
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
To configure Small Cell Gateway through WPS Small Cells

...................................................................................................................................................................................................
1 Launch WPS Small Cells.

...................................................................................................................................................................................................
2 Launch and log in to the WMS Small Cells as an admin user.

...................................................................................................................................................................................................
3 Navigate to Configuration > CM XML > Export Network to export the entire network
snapshot.
...................................................................................................................................................................................................
4 Import the new network snapshot into WPS Small Cells.

...................................................................................................................................................................................................
5 Navigate to FGW<DN>;FGWConfig/1;.
...................................................................................................................................................................................................
6 Set the parameters averageNumberOfImsi, mimimumIMSIList &

maximumIMSIList.
Note: Parameter totalNumberOfEnterpriseImsis is set automatically, once the
Small Cell Gateway analyzes the BSRINFO file from the WMS Small Cells.
...................................................................................................................................................................................................
7 Click Run checks on FGW<DN>.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................
10 Navigate to Summary & Action in Session Manager, to activate the session or to schedule
the session.
...................................................................................................................................................................................................
11 The changes are sent on SNMP to activate the changes.

E...................................................................................................................................................................................................
N D O F S T E P S
To configure Small Cell Gateway through WMS Small Cells

...................................................................................................................................................................................................
1 Launch and log in to the WMS Small Cells as an admin user.

...................................................................................................................................................................................................
2 Navigate to Configuration > ObjectEditor > Search > select FGW<DN>. Click Append
select FGWConfig/1.
...................................................................................................................................................................................................
3 Set parameters averageNumberOfImsi, mimimumIMSIList & maximumIMSIList.

Note: Parameter totalNumberOfEnterpriseImsis is set automatically, once the
Small Cell Gateway analyzes the BSRINFO file from the WMS Small Cells.
...................................................................................................................................................................................................
4 Select Mode > Online Commands.

...................................................................................................................................................................................................
5 Click Save and Apply all changes.

...................................................................................................................................................................................................
6 The changes are sent on SNMP to activate the changes.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Managed objects modified from WPS Small Cells
Table 6-10 BSR
Parameter name Description Default Value Syntax Permitted

values
femtoACLlist This specifies the list of users string length=4096

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.
femtoA- This is to indicate whether the Small string length=4096

CLlistGuest Cell uses its local ACL or the one on
the BSR Gateway.
femtoACLlistIndi- Represents the Closed Subscriber femtoACL enum {

cator Group Identity. ACLlistIndicator femtoACL=
0,
fgwACL=1
}
aclListRef This specifies the list of users
resources, as either Owner or as
Guest within closed access operation
mode.This parameter is not exposed
to the Small Cell. It is a Small Cell
Group level attribute.
Table 6-11 FGW
Parameter Description Value Syntax Permitted

name values
EnterpriseList This class models the data for defining

enterprise groups in the FGW. This class
is not visible on the itf-fgw or CLI
interface. An instance of this object is
created for each enterprise list.
aclList Represents the list of up to 10000 users Enter- sequence [1..10000]

permitted to use the Small Cell priseList of struct ACLEntry
resources, as part of an enterprise group,
within closed access operation mode.
csgId Represents the Closed Subscriber Group Unsigned32 [1..125000000]

Identity.
The 'EnterpriseList' class supports an
attribute with the name 'csgId' which
shall be of suitable type and format to
store a Closed Subscriber Group Identity
(CSG-ID) where an operator wishes to
use this mechanism to manage Extended
ACLs.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 6-11 FGW (continued)
Parameter Description Value Syntax Permitted

name values
numberOfImsi Represents the number of IMSIs held in Unsigned32

the list for this group
Table 6-12 FGW
Parameter name Description Syntax Default Permitted values

value
averageNumber- This attribute represents the average uint16 10 [10..256]

OfImsi number of IMSIs per Small Cell ACL
list. The value is used as a multiplier
to estimate the total number of IMSIs
contained in all the Small Cell ACL
lists stored on the BSR Gateway.
mimimumIMSIL- This attribute represents the minimum Unsigned32 11200000 [5000000..11200000]
ist threshold for the number of IMSIs
held in the ACL lists on the BSR
Gateway, before alarm FGW::
minimumImsiListThresholdExceeded
is sent.
maximumIMSIL- This attribute represents the Unsigned32 14200000 [11250000..16000000]
ist maximum threshold for the number
of IMSIs held in the ACL lists on the
BSR Gateway, before alarm FGW::
maximumImsiListThresholdExceeded
is sent.
totalNumberOfEn- This attribute represents the total This parameter set

terpriseImsis number of IMSIs held in the automatically, once the BSR
Enterprise Groups ACL lists that are Gateway parses the
controlled by the BSR Gateway. This BSRINFO file from the
attribute reflects the addition and WMS Small Cells
removal of IMSIs from the internal
lists.

...................................................................................................................................................................................................
1 In the WPS Small Cells, set attributes aclListRef as UNSET and femtoACLlistIn-
dicator as FemtoACL of the Small Cell Group.
...................................................................................................................................................................................................
2 Set FemtoACLlist and FemtoACLlistGuest with appropriate IMSI values.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Navigate to Configuration > Sessions Manager. Execute the reverse work order.
E...................................................................................................................................................................................................
N D O F S T E P S

Table 6-13 BSR
Parameter name Description Default Syntax Permitted values

Value
femtoACLlist This specifies the list of users string length=4096

resources as owner, within closed
access operation mode. The list is
defined as a NULL terminated
string with comma-separated IMSI
values.
femtoA- This is to indicate whether the string length=4096

CLlistGuest Small Cell uses its local ACL or the
one on the BSR Gateway.
femtoACLlistIndi- Represents the Closed Subscriber fem- enum { femtoACL=0,

cator Group Identity. toACL ACLlistIndi- fgwACL=1 }
cator
aclListRef This specifies the list of users

resources, as either Owner or as
Guest within closed access
operation mode.This parameter is
not exposed to the Small Cell. It is
a Small Cell Group level attribute.
Impacted services
None.
WPS Small Cells Yes
WMS Small Cells Yes
HDM No
Small Cell Yes
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
IPC No
IPsec Router No
BPG No
BVG No
BSG Yes
AAA No
System
SCMS Yes

None.
Duration
Downtime
NA.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Metro Small Cells features 111039 - Extended range cell
....................................................................................................................................................................................................................................
111039 - Extended range cell

Overview
Feature 111039 allows the operator, to configure the cell radius to up to 2 km on a V2
Metro/Enterprise, and provide UE speed up to 120 km/hr. It is mainly for outdoor rural
deployment.
Purpose
This topic describes the activation and deactivation procedures for Extended range cell
(111039) feature.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to the selected BSR profile. Set attributes extendedCellEnable and

DBC::extendedCell as True.
Note: Attribute DBC::extendedCell must be set only incase of PC323. In PC333,
the feature is enabled by default.
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 6-14 LCell
Parameter name Description Default Value Syntax Permitted

values
maxBSRPower- This parameter defines the maximum 13.0 real [-50.0..24.0]

LimitdBm allowed Small Cell transmission power in step=0.1
dBm. It is set by SCMS. It controls Small precision=1
Cell maximum coverage and interference units=dBm
to other cells.
Table 6-15 BSR
Parameter Description Value Default Syntax Permitted values

name Value
extendedCel- Enables cell radius of up to 2km True False bool- { True, False }
lEnable ean
DBC::extend- Indicates if the baseband device True False bool- { True, False }
edCell supports an extended cell range of up ean
to 2km
bsrPilotPower- BSR Pilot power adjust mode. mim- enum { mimBased=0,
AdjustMode Note: The change of the value doesn't Based BsrPi- rscpBased=1,
take effect until next time cell is setup. lot- ecIoBased=2 }
Power-
Adjust
Mode
ueBasedPilot- enum { disable=0,
PowerAdjust- targetEcIo=1,
Mode neighbourEcIo=2 }
Table 6-16 BSR::AutoConfigPW
Parameter Description Default Syntax Permitted values

name value
antennaGainIn- Antenna gain (cable and connector losses). 0.0 real [-25.0..25.0] step=0.1
cLoss Small Cell at 5 m height, then feeders up to precision=1 units=dBi
the antenna on 20 m pole (example, 8 dBi
antenna gain, 0.5 dB connector losses, 0.1
dB/m: 8 - 0.5 (0.1*15) = 6 dBi).
slopeFactor Slope correction factor for free space 1.0 real [-5.0..5.0] step=0.1
path-loss formula. precision=1
htCorrection- Free space path-loss formula correction 0.00 real [-50.00..50.00] step=0.01
Factor factor for antenna height and ground precision=2
affects.
targetPilotR- Used to optimise UE received pilot power -100.0 real [-120.0..-30.0] step=0.1
SCPdBm in auto configuration and self optimization. precision=1 units=dBm
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 6-16 BSR::AutoConfigPW (continued)
Parameter Description Default Syntax Permitted values

name value
targetPilotE- Used to optimize UE received pilot Ec/Io -10.0 real [-25.0..0.0] step=0.1
cIodB in auto configuration and self optimization. precision=1 units=dB
maxBSRPower- This is read only and gives the current real [-50.0..24.0] step=0.1
dBm maximum transmit power as determined by precision=1 units=dBm
the Small Cell coverage optimization
requirements.
maxPilotPower- Used by Small Cell server (SCMS) to 20.0 real [-50.0..24.0] step=0.1
dBm control maximum Small Cell pilot precision=1 units=dBm
coverage, in order to reduce theSmall Cell
interference to neighbor cells.
minBSRPower- Used by Small Cell server SCMS to 0.0 real [-50.0..24.0] step=0.1
dBm control minimum Small Cell coverage, in precision=1 units=dBm
order to maintain the Small Cell minimum
coverage. This value is used to set an
allowed maximum Small Cell transmission
power.
minPilotPower- Used by Small Cell serverSCMS to control -20.0 real [-50.0..24.0] step=0.1
dBm minimum Small Cell pilot coverage, in precision=1 units=dBm
order to maintain the Small Cell minimum
coverage.
indoorPenetra- Used by the Small Cell server SCMS to 30.0 real 0.0..100.0] step=0.1
tionLoss control minimum Small Cell pilot precision=1 units=dB
coverage, in order to maintain the Small
Cell minimum coverage.
maxCoverage- Used by the operator to adjust Small Cell 30.0 real [1.0..2000.0] step=0.1
Distancem coverage within the limit set by precision=1 units=meters
MaxPowerdBm.
Table 6-17 BSR

name Value
extendedCel- Enables cell radius of up to 2km False False boolean { True, False }
lEnable
Impacted services
None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
WPS Small Cells Yes
WMS Small Cells No

HDM No

Small Cell Yes
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No
System
SCMS Yes

None.
Duration
NA
Downtime
NA.
....................................................................................................................................................................................................................................
Issue 5 April 2014
7 7 adio resource
R
management features
Overview
Purpose
This chapter describes the activation/deactivation procedures for the Radio Resource
Management features.
Contents
78229 - Location lock on 2G RF fingerprint 7-2

114997 - 2G MCC-based NLL on V1 boards (HiLo) 7-6
119860 - 3G sniffing capability in 2100/850 MHz 7-13
76985 - Automatic carrier selection 7-16
116495 - UL interferences management based on Tx power update 7-23
116496 - 64QAM for HSDPA 7-28
108877 - Coverage self-optimization based on admission 7-32
114174 - UMTS Small Cell to LTE cell reselection 7-38
116498 - Multi-objectives joint coverage optimization 7-44
170891 - Neighbor list optimization based on UE measurements 7-48
170695 - Change of Service Area Location Reporting 7-52
171355 - Coordinated self optimization in groups 7-57
...................................................................................................................................................................................................................................
Issue 5 April 2014
Radio resource management features 78229 - Location lock on 2G RF fingerprint
....................................................................................................................................................................................................................................
78229 - Location lock on 2G RF fingerprint

Overview
This feature adds a 2G RF fingerprint test to the location and movement checks. Location
and movement checks, are performed by the Small Cell during auto-configuration,
following power on or reset. As the Small Cell is user installable, a single test cannot
accurately determine its position. As a result, a number of tests are run and the operator
can configure the interpretation of each test, and the final overall results is determined.
The 2G RF fingerprint test, is one of the tests run during auto-configuration to determine,
if the Small Cell is in the correct location or moved.
The following checks are available based on status of the Small Cell:
Location check
The location check determines the position of the Small Cell, when its position is
unknown. The location check is in case of first time power on or factory reset. The
results obtained from the tests are compared against the neighboring cell information,
provided by the operator.
Movement check
The movement check determines if the Small Cell has moved from its previous
location. The check is run at power on or reset. Here, the test compares the newly
detected cells with the union of the cells, provided by the operator and the cells found
during the previous location or movement check.
The 2G RF fingerprint test uses the 2G network listening functionality of the Small Cell,
to detect neighboring 2G macro cells visible to the Small Cell. It then compares this list
with a known list to determine a result. The test is configurable, as the threshold needed
for the test to pass is configurable, that is, the number of matched cells. The 2G algorithm
follows the same principles as the existing 3G RF fingerprint test.
The 2G fingerprint test result is then scored (a score of 0 means that the test is zero and
does not contribute to the overall score). The scores of all the tests are summed and
compared against, a configurable overall threshold for location, and a configurable
threshold for movement checking. The 2G fingerprint test, complies with the existing
configuration structures and mechanisms for determining the overall result. The
subsequent functionality, including alarms, resulting from a failure or success of the
location or movement checking does not change.
The feature works with the 2G network listening functionality, provided on v1 boards and
v1.2 boards onward. On v,1 boards the 2G network listening functionality is provided by
the HiLo module. And for v1.2 onwards, this is provided by PicoChips embedded
PC8211 or PC8211-302, 2G network listening functionality.
This feature provides a more reliable location/movement check, even in areas with a poor
3G coverage.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Note:
LCELL::LocationCheckPassFlag, must be used to determine, if it is the initial
check (location check) or a subsequent check (movement check).
The 2G LMC check is not performed during self-optimization period.
Purpose
This topic describes the activation and deactivation procedures for location lock on 2G
RF fingerprint (78229) feature.
Before you begin

Ensure that:
1. The Small Cell HW is in a proper working condition.
2. The Small Cell is active, with a load containing the feature
3. The 2G neighbor cell detection is configured appropriately.
4. If 2G location or movement check succeeds, the test score is marked as 1, and the
corresponding scores are accounted to determine the overall LMC.
5. If 2G NLA is disabled, or if the 2G LMC fails then the test score is marked as 0
(failed) and not considered in the overall LMC determination.

...................................................................................................................................................................................................
1 There is no separate flag for feature activation. The 2G RF fingerprint test is run during
auto-configuration. However, whether the result of the test contributes to the overall
location or movement check, can be configured by setting the appropriate score.
Compare Output Result

The number of detected Is greater than / equal to the Pass
macro cells matching the threshold
neighbor cell list
The number of detected Is lesser than the threshold Pass
macro cells matching the and no new cells found
neighbor cell list
The number of detected Is lesser than the threshold Fail
macro cells matching the and new cells are found
neighbor cell list
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
The following objects are involved in the activation of location lock on 2G RF
fingerprint:
Table 7-1 LCELL

LCELL::gsmLocationCheck- Threshold value successful [ 0..64 ] Default: 1
DetectedThreshold GSM RF fingerprint location
check, based on the number of
detected macro cells
LCELL::gsmMove- The threshold value for [ 0..64 ] Default: 2
mentCheckDetectedThreshold successful GSM RF
fingerprint movement check,
based on the number of
detected macro cells
Note: In case of an empty neighbor cell list, or a neighbor cell list containing non
permissible cells, the initial location check can be marked successful by setting the
threshold to 0.
Table 7-2 BSR
Parameter Name Parameter Description Additional Comment

BSR::lMCvisibleGs Location and movement The parameter contains the
mCellsTest check using visible 2G macro following LMC test:
cells test LocationWeight
MovementWeight
testScore
testComplete
Deactivation procedures
There is no separate flag for feature deactivation. The 2G RF fingerprint test is run during
auto-configuration. However, whether the result of the test contributes to the overall
location or movement check, can be configured by setting the appropriate score. When
the scores are set to 0, the 2G LMC result is not accounted for overall LMC
determination.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Impacted services
None
WPS Small Cells No
WMS Small Cells No

HDM No

Small Cell No
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No
System

None

NA
Downtime
NA
....................................................................................................................................................................................................................................
Issue 5 April 2014
Radio resource management features 114997 - 2G MCC-based NLL on V1 boards (HiLo)
....................................................................................................................................................................................................................................
114997 - 2G MCC-based NLL on V1 boards (HiLo)

Overview
The 2G Mobile Country Code (MCC) based National Location Lock (NLL) on V1 boards
(HiLo) feature, was applicable only to V1 HiLo boards. With the implementation of
feature 114997, 2G MCC check which is part of NLL, can be run on hardware prior V1.2
(that is, HiLo modules). Earlier due to the limitation of HiLo module, the 2G MCC check
was restricted. The 114997 feature changes the search algorithm used with the HiLo
module as the source for 2G network listening, but the calculation of the final result
remains the same as for all 2G & 3G MCC tests.
With this feature enabled the Small Cell can search for cells with any PLMN ID. The
Small Cell reads the MCC for the cells found and uses the result to determine the country
location of the Small Cell. As a result of 2G MCC check, the Small Cell populates the
LCELL::gsmNatCell parameter, which contains information of the nCC, bCC,
gsmFreqBand, bCCHArfcn, mCC, mNC, bCCHRSSI for each cell found. With this feature
the HiLo module in Small Cell returns 13 cells with the strongest signals.
The Small Cell determines the weighted sum of macro cells having an MCC
(LCELL::ownPLMNMCC) value equal to its MCC (National cells) value. The Small Cell
determines the weighted sum of all cells having an MCC (LCELL::ownPLMNMCC)
value equal to its MCC (Foreign cells) value. The following ranges are based on the
strength of the cell (similar to 3G MCC / previous 2G MCC calculation).
Range Cell strength Number of Number of Weight per

ranges in dBm national foreign cells range
where: cells per per range
T= range
BSR::gsmN-
LLThreshold
for 2G test
n=
NLLTest-
StrengthIn-
crement
(dBm)
(T is a
negative
strength
units dBm)
i=1 -T < Rangei < -T Ni Fi Wi = 1
+n
i=2 -T+n < Rangei < Ni Fi Wi = 2
-T + 2n
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Range Cell strength Number of Number of Weight per

ranges in dBm national foreign cells range
where: cells per per range
T= range
BSR::gsmN-
LLThreshold
for 2G test
n=
NLLTest-
StrengthIn-
crement
(dBm)
(T is a
negative
strength
units dBm)
i=3 -T+2n < Rangei Ni Fi Wi = 3
< -T + 3n
< -T + 4n
The Small Cell applies the following formulae to obtain a result:

If (Ni x Wi) > (Fi x Wi), then BSR:: gsmNLLMCCResult is set as Passed.
If (Ni x Wi) < (Fi x Wi), then BSR:: gsmNLLMCCResult is set as Failed.
If all ranges are empty, that is, no cells are found, then BSR:: gsmNLLMCCResult is
set as unknown.
Search time depends on the strength of cells in the neighborhood. The cell search is
bounded by a guard timer gsmModuleInitGuardTimer (default 90 seconds), if the
coverage is weak. The typical search time is in the order of 50 seconds.
The ability to execute 2G MCC check on V1 CPEs benefits the areas with weak or no 3G
coverage.
Note:
LCELL::LocationCheckPassFlag is used to determine if the check is the initial
check (location check) or a subsequent check (movement check).
The 2G MCC check is not implemented during self-optimization period.
Purpose
This topic describes the activation and deactivation procedures for 2G MCC-based NLL
on V1 boards (HiLo) (114997) feature.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Before you begin
Ensure that
The Small Cell V1 Hilo hardware is operational.
2G neighbor cell detection is configured.
Note: If gsmNatLocLockFrequency differs from the GSM band(s) configured in
LCELL::gsmFrequencyList, then HiLo module is reset for band reconfiguration.
gsmNatLocLockFrequency must be configured using WPS Small Cells. This structure
sequence is available under Femto Preprovision data. Four instances of this struct can
be created. The following mandatory attributes present in struct must be set:
bandIndicator
bCCHARFCNstart
bCCHARFCNsize
Use the WPS Small Cells to perform Run Checks ... on the network. Create a work
order and apply it in WMS Small Cells. Refer Small Cell attributes configuration
with WPS Small Cells (p. 9-8) for more information.

...................................................................................................................................................................................................
1 The NLL check must be enabled setting the parameter BSR::nationalLocationLockEn-

abled using the HDM or WMS Small Cells. The 2G Macro MCC check is allowed when
the BSR::nllgsmMacroMCCTest:locationWeight parameter is not equal to 0, and the HiLo
module is operational.
...................................................................................................................................................................................................
2 The BSR::nllgsmMacroMCCTest:locationWeight parameter must be set using the WMS

Small Cells.
E...................................................................................................................................................................................................
N D O F S T E P S

Managed objects involved from Small Cell
Table 7-3 BSR
Parameter name Description Value comment
BSR::nationalLoca- Enables/Disables the NLL Boolean

tionLockEnabled Feature 78230. Default: 0
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Parameter name Description Value comment
BSR:: NLL check using the 2G Macro The

nllGsmMacroMC- MCC test. nllGsmMacroMC-
CTest CTest parameter uses
the structure LMCtest
which contains the
following elements:
LocationWeight
Movement-
Weight
testScore
testComplete
BSR:: Result of NLL 2G MCC check. Passed /Failed/ Automatically updated
gsmNLLMCCResult notrun/unknown by Small Cell
Default: notrun If no cells are found,
then BSR::
gsmNLLMCCResult is
set as unknown.
Managed objects modified using the WMS Small Cells
Table 7-4 LCELL
Parameter Name Parameter Description Value Comment
LCELL:: gsmNatCell List of gsmUMTS sequence [0..16] of struct Contains information

neighbor cells with GsmNatCell about the nCC, bCC,
country code information gsmFreqBand,
for use with NLL. bCCHArfcn, mCC, mNC,
bCCHRSSI parameters for
each found cell.
LCELL:: Indicates the list of GSM sequence [0..4] of struct
gsmNatLocLockFre- neighbor cell frequencies GSMFrequencyList
quency and bands for searching
during NLL 2G MCC test.
Note:
If the GSM band(s) configured in LCELL::gsmNatLocLockFrequency differs from
the GSM band(s) configured in LCELL::gsmFrequencyList, then the Small Cell
configures the HiLo module with the GSM bands from LCELL::gsmNatLocLock-
Frequency. The command AT*PSRDBS HiLo AT with mode 0 is used (takes
effect after next power on). The HiLo module is reset to configure the band.
Finally the frequencies configured in gsmNatLocLockFrequency are ignored.
As a result of the preceding action, if the module fails to restart due to expiry of
the GSMListener::gsmModuleInitGuardTimer timer, or for other reasons, then
network listening is terminated. In this case the Small Cell sets parameter
BSR::gsmNLLMCCResult as notrun.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
If the LCELL::gsmNatLocLockFrequency list is empty, then the band need not be
configured. The Hilo Module uses the band(s) already configured from the
LCELL::gsmFrequencyList during neighbor cell detection.
To initiate cell search during the 2G MCC check, the Small Cell sends the
AT+KCOPS command with Public Land Mobile Network (PLMN) wild-card
parameter, to the HiLo module and starts the AT guard timer GSMLISTENER::gs-
mATCmdGuardTimer.
- Following receipt of a response OK for AT+KCOPS, the Small Cell stops the AT
guard timer GSMListener::gsmATCmdGuardTimer and starts the guard timer
GSMListener::gsm ModuleInitGuardTimer, to start a cell search across all PLMN
IDs.
- Failure to receive an OK in response to AT+KCOPS, or the expiry of
SMListener::gsm ATCmdGuardTimer results in a failure. This may result in the
2G NLL being terminated and in this case the Small Cell sets BSR::gsmNLLMC-
CResult as notrun. This case occurs when the HiLo module software has not been
updated.
Following +KCOPS response, the search for a cell starts. On completion the
response +KCELL is sent from the HiLo module. If the gsmModuleInitGuard-
Timer expires before the AT response, +KCELL is received from the module.
Then a AT+KCELL command is sent to the HiLo module to determine the state of
the search. This situation occurs when there are weak cells resulting in increased
time spent for completing the search. In such cases, the search is terminated when
the guard timer expires and the cells found to date read.

The overall NLL check can be disabled using the flag BSR::nationalLocationLockEn-
abled. Or if the parameter BSR::nllgsmMacroMCCTest:locationWeight is set as 0, then
2G Macro MCC test is invalid and must not be executed.
Impacted services
The 2G MCC checks by means of the network listening function could consume some
time to search for a result. The check could increase the time consumed for
auto-configuring a Location Check. The time consumed can be reduced by appropriately
tuning the search parameters. The typical search time is in the order of 50 seconds. If the
cells are weak or not present, then the cell search is bound by a guard timer
GSMLISTENER::gsmModuleInitGuardTimer (default 90 seconds).
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
The following table lists examples of the time consumed for a 2G MCC check over the
GSM180 and P-GSM900 bands based on V1 boards with HiLo module:
GSM1800 P- GSM900
Maximum Typical Maximum Typical
(seconds) (seconds) (seconds) (seconds)
(Medium (Medium
coverage) coverage)
Total Time 90 50 90 50
(based on HiLo
module 50
seconds typical
and 90 seconds
time-out)
WPS Small Cells No

WMS Small Cells Yes
HDM Yes
Small Cell Yes
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No

System

None

NA
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Downtime
None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Radio resource management features 119860 - 3G sniffing capability in 2100/850 MHz
....................................................................................................................................................................................................................................
119860 - 3G sniffing capability in 2100/850 MHz

Overview
This feature enables full support of the V2-EC-2S - 2100 MHz Home Cell. In particular,
it introduces the 3G network listening capabilities in 2100/850 MHz and 2G network
listening capabilities in 1900/850 MHz frequency bands.
Purpose
This topic describes the activation and deactivation procedure for the 3G sniffing
capability in 2100/850 MHz (119860) feature.

...................................................................................................................................................................................................
snapshot into WPS Small Cells
...................................................................................................................................................................................................
2 Dual band configuration must be enabled by configuring two frequency bands of

supported dual bands in the following MIM attributes:
macroUMTSCellFrequencyList
gsmFrequencyList
For the macroUMTSCellFrquencyList attribute, set the two frequency bands as
2100 MHz and 850 MHz.
For the gsmFrequencyList attribute, set the two frequency bands as 1900 MHz and
850 MHz.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
4 Create a WorkOrder and copy it to the WMS Small Cells.

...................................................................................................................................................................................................
5 Navigate to Configuration >> Sessions Manager >> Create new Session, to launch the
WorkOrder in WMS Small Cells
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S

Managed objects in WMS Small Cells:
Table 7-5 LCell:
LCELL:: macroUMTSCellFrequen- Indicates the list of Macro cell Set the value for the two frequency
cyList UMTS neighbor cell frequencies. bands, as 2100 MHz and 850 MHz.
LCELL:: gsmCellFrequencyList Indicates the GSM frequency list Set the value for the two frequency
bands, as 850 MHz and 1900 MHz.
LCELL:: gsmNatLocLockFrequency Indicates the list of GSM neighbor
cell frequencies and bands available
for search during National Location
Lock 2G MCC test.

Managed objects in WMS Small Cells:
Table 7-6 LCell:
LCELL:: macroUMTSCellFrequen- Indicates the list of Macro cell Clear the values of the two
cyList UMTS neighbor cell frequencies. frequency bands.
LCELL:: gsmCellFrequencyList Indicates the GSM frequency list Clear the values of the two
frequency bands.
LCELL:: gsmNatLocLockFrequency Indicates the list of GSM neighbor
cell frequencies and bands available
for search during National Location
Lock 2G MCC test.
Impacted services
There is no impact on any service on activation/deactivation of this feature.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
WPS Small Cells No
WMS Small Cells No

HDM No

Small Cell Yes Once the appropriate frequencies are
defined, restart the Small Cell so it
can find the cells with the
frequencies defined in the frequency
list.
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No
System

None

NA
Downtime
None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Radio resource management features 76985 - Automatic carrier selection
....................................................................................................................................................................................................................................
76985 - Automatic carrier selection

Overview
The Automatic carrier selection feature, enables automatic selection of the Small Cell
frequency. The less interfered carrier is selected, to optimize Small Cell performance and
to minimize impact on the macro layer when shared with the Small Cell. It is triggered at
the Small Cell set up, or during Small Cell operation on RF measurements. This feature is
for residential deployments or isolated cells deployments (this feature cannot be used for
group deployment, as a single frequency is used across the group).
This feature allows the Small Cell, to select and configure its own carrier (Band, DL/UL
Frequency and PSC) from a list of potential Small Cell carriers. The chosen carrier (from
the potential carriers list), is the one with the least interference (smallest measured RSCP)
from the neighboring Small Cells.
Purpose
This topic describes the activation and deactivation procedure for Automatic carrier
selection (76985) feature.

...................................................................................................................................................................................................
1 See Small Cell attributes configuration with WPS section, To configure a Small Cell
profile (bsrprofile) attribute (p. 9-9).
Note: Navigate to the specific Profile selected for this feature. Navigate to LCell and
modify the parameters to values as defined in the Managed Objects section, see
Managed objects involved in feature activation (p. 4-69).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 7-7 LCell
Parameter name Description Default Value Syntax Permitted Values
acsCarrierSelection- The automatic carrier selection acsOff enum { acsOff=0,

Mode mode. acsMacroStatic=1,
Can be set with the following acsMacroDynamic=2,
values: acsTrafficDynamic=3
}
acsOff - The feature is
disabled and the carrier is set
by the operator.
acsMacroStatic - The
carrier is selected as part of
Auto-configuration only, based
on information about the
Macro Network.
acsTrafficDynamic - The
carrier is selected as part of
Auto-configuration, based on
information about the Macro
Network. At Self-Optimisation,
the selection is re-assessed and
possibly changed.
acsAllowedFemto- Complete list of UMTS FDD sequence

Carriers carriers that may be selected for the [0..8] of
Small Cell. struct Ac
Note: entries not supported by the sAllowed-
Small Cellhardware is ignored. FemtoCar-
rier
acsPotentialMacro- List of UMTS FDD carriers that are sequence

Carriers checked for potential Macro cells. [0..8] of
In case, the list is empty, all carriers struct
in LCell::acsAllowedFemtoCarriers Frequency
are considered as selectable.
Note: Entries not supported by the
Small Cell hardware are ignored.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 7-7 LCell (continued)
acsMappingMode The mode of mapping table for bestMacro- enum { bestMacrocell=0,

automatic carrier selection. cell allDetected=1,
The parameter can be set with the allDetectedExclusive=2
following values: }
bestMacrocell, - The macro

carrier, on which the cell with
highest CPICH RSCP has been
detected is used to determine
the list of selectable Small Cell
carriers.
allDetected - For each macro
carrier with cells detected, the
corresponding set of allowed
Small Cell carriers is
considered. The list of
selectable Small Cell carriers is
the union of these sets.
allDetectedExclusive - For
each macro carrier with cells
detected, the corresponding set
of allowed Small Cell carriers
is considered. The list of
selectable Small Cell carriers is
the union of these sets, but
excluding all macro carriers
with cells detected.
acsMappingMacro- For each carrier with macro cells string length=32
CarrierToAllowed- detected, this parameter indicates
FemtoCarrier the allowed carriers for Small Cell.
The format is - entry number (ID
value) in <LCell::acsPotentialMacro
Carriers>: comma-separated entry
number (ID value) in
<LCell::acsAllowedFemtoCarri-
ers>. For example: 1:1,2,3,4,2:1,2,4.
acsMappingNoMac- For the case that no Macro cells are string length=32
roToAllow detected, this parameter indicates
edFemtoCarrier the allowed carriers for Small Cell.
The format is - 0:comma-separated
entry number (ID value) in
<LCell::acsAllowedFemtoCarri-
ers>. For example: 0:1,2,3,4.
acsFemtoCarrierCo Mode how to compare different femtoOnly enum { femtoOnly=0,
mparisonMode selectable Small Cell carriers: AcsFemto- macroDb=1,
Based on Small Cell Ncells only, CarrierCo macroSearch=2 }
macro Ncells as in data base, or new mparison-
search for macro NCells Mode
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
umtsOpenCarrier- If True, then an open search for False boolean { True, False }
MacroSearc macro cells outside the composed Note: This
hEnableFlag neighbor cell list and the externally parameter is treated
supplied list, is done for Automatic as False in 3.0.
Carrier Selection, during
Auto-configuration or
Self-optimization using network
listening function. If False, only the
already detected macro neighbor
cells are considered.
UARFCNDLInUse The DL UARFCN being used by integer [0..16383]

the Small Cell. Note: This
parameter is also
used in
LCell::acsCar-
rierSelectio
nMode, is set to
acsOff.
UARFCNULInUse The UL UARFCN being used by integer [0..16383]

the Small Cell. Note: This
parameter is also
used in
LCell::acsCar-
rierSelectio
nMode, is set to
acsOff.
fddFreqBandInUse The frequency band being used by enum { fdd2100=1,

the Small Cell. FDDRa- fdd1900=2,
dioFre- fdd1800=3,
quency bandIV=4,
Band bandV=5,
bandVI=6,
bandVII=7,
bandVIII=8,
bandIX=9,
bandX=10,
bandXI=11,
bandXII=12,
bandXIII=13,
bandXIV=14,
Note: This
parameter is also
used in case
LCell::acsCar-
rierSelectio
nMode is set as
acsOff.
lastCarrierChange Specifies the date and time, when 0001-01-01T dateTime

the carrier was last changed. This 00:00:00Z
value is retained across reboot. If a
selection has never succeeded
before, the value will be the
Unknown Time value.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
acsNumDetectedCar- Number of carriers with macro cells -1 integer

riers detected during each
Auto-configuration and/or
Self-optimization for Automatic
Carrier Selection.
A value of -1 indicates that no
macro carrier detection was done
for Automatic Carrier Selection.
Note: Depending on the setting of
LCell::umtsOpenCarrierSearchEnableFlag,
the number of detected carriers
might be lower than the actual
number of carriers with macro cells.
acsHystCPICHactiv Hysteresis threshold for comparing 10 integer units=dB
e interference level (CPICH RSCP) of
new carrier with interference level
(CPICH RSCP) of current carrier
during self-optimization.
Note: If acsPotentialMacroCarriers is populated, then acroUMTSCellFre-

quencyList must be populated with the same values.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 7-8 LCell
Parameter Description Default Value Syntax Value Permitted Values

name
acsCarrierSe- The automatic carrier acsOff enum acsOff { acsOff=0,

lectionMode selection mode. acsMacroStatic=1,
Can be set with the acsMacroDynamic=2,
following values: acsTrafficDynamic=3
}
acsOff - The
Note: In the 3.0
feature is disabled
release,
and the carrier is set acsTrafficDynamic
by the operator. value but if this is
acsMacroStatic - treated as
The carrier is acsMacroDynamic.
selected as part of
Auto-configuration
only, based on
information about
the Macro Network.
acsTrafficDy-
namic - The carrier
is selected as part of
Auto-configuration,
based on information
about the Macro
Network. At
Self-Optimisation,
the selection is
re-assessed and
possibly changed.
Impacted services
Feature activation requires the Small Cell to be restarted. The feature impacts the Small
Cell start up (duration to scan the macro carriers and Small Cell carriers by network
listening during Auto-configuration) and availability (duration to scan the macro carriers
and Small Cell carriers by network listening during Self-optimization). In case, multiple
selectable Small Cell carriers are available, all the carriers must be evaluated by network
listening. Hence, Small Cell services are impacted during the Small Cell restart operation.
WPS Small Cells No

WMS Small Cells No
HDM No
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Small Cell Yes

IPC No
IPsec Router No
BPG No
BVG No
BSR Gateway Yes
SCMS Yes
AAA No

System

None.
Duration
Time taken for the Small Cell to restart or self-optimize. This depends on the number of
entries in the acsAllowedFemtoCarriers and acsPotentialMacroCarriers lists.
Downtime
There is a downtime during the Small Cell restart or self-optimization. This time depends
on the number of entries in the acsAllowedFemtoCarriers and acsPotentialMac-
roCarriers lists.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Radio resource management features 116495 - UL interferences management based on Tx power
update
....................................................................................................................................................................................................................................
116495 - UL interferences management based on Tx power

update
Overview
The main purpose of the Uplink (UL) interferences management based on Tx power
update feature, is to control the UL interference a Small Cell UE creates, on the receiver
of the neighboring macro cells or neighboring Small Cells, on the same frequency as the
serving Small Cell.
This is achieved by using UE measurements to control the power transmitted by the UE.
Purpose
This topic describes the activation and deactivation procedure for UL interferences
management based on Tx power update (116495) feature.

...................................................................................................................................................................................................
Note: Navigate to the specific BSRProfile selected for this feature and modify the
parameters to values as defined in the Managed Objects section, see Managed
objects involved in feature activation (p. 4-69).
E...................................................................................................................................................................................................
N D O F S T E P S
Note: This feature has interactions with network listening (3G Macro, Small Cell and
Small Cell Group support), handovers, hand-ins, UL DBC, and CELL_FACH. The
operator must be aware of setup procedures, monitoring logs, operations, and
messaging for these interactions.
....................................................................................................................................................................................................................................
Issue 5 April 2014
update
....................................................................................................................................................................................................................................
Parameter Description Default Syntax Value Permitted Values

name Value
ulIntfCtrlFem- Flag to enable control the UL False boolean Set as { True, False }
toEnabled interference into neighboring True, if
Small Cells. Macro
Note: Only effective if the cells are
Small Cell is part of a Small deemed
Cell group and neighboring as
Small Cells are configured. inter-
fered
ulIntfCtrlMac- Flag to enable control the UL False boolean Set as { True, False }
roEnabled interference into neighboring True, if
macro cells. Small
Cells
(group
or
other-
wise) are
deemed
as
inter-
fered
ulIntfCtrl- Maximum Rx interference -100 integer [-120..-80] units=dBm
MaxFemtoInter- level caused by a Small Cell
ferenc eLevel UE with high speed UL data
connection in a Small Cell
neighbor cell when UL
interference is controlled.
ulIntfCtrlMax- Maximum Rx interference -106 integer [-120..-80] units=dBm

MacroInterfer- level caused by a Small Cell
enc eLevel UE with high speed data
connection in a macro
neighbor cell when UL
interference is controlled.
....................................................................................................................................................................................................................................
Issue 5 April 2014
update
....................................................................................................................................................................................................................................
Table 7-9 BSRProfile (continued)

name Value
ulIntfCtrlMeas- Reporting interval for report- enum { reportinginterval250=250,

Period intra-frequency measurement. inginter Report- reportinginterval500=500,
val1000 ing- reportinginterval1000=
Inter- 1000,
valIntr reportinginterval2000=
aFreq 2000,
reportinginterval3000=
3000,
4000,
6000,
8000,
12000,
16000,
20000,
24000,
28000,
32000,
64000 }
ulIntfCtrlMin- Minimum UL data rate to start 384 integer [0..16000] units=kbps
DataRate UL interference control for an
UE.
ulIntfCtrlMin- Minimum RTWP measured in -94 integer [-120..0] units=dBm
RTWP Small Cell before the UL
interference of an UE with
high speed UL data
connection gets controlled.
ulIntfCtrlMin- Hysteresis to RTWP measured 3 integer [0..30] units=dB

RTWPHyst in Small Cell before the UL
interference control of an UE
with high speed UL data
connection gets stopped.
ulIntfCtrlTxPw- Hysteresis to relax the power 3 integer [0..30] units=dB

rHyst restriction to an UE with high
speed UL data connection due
to UL interference control.
....................................................................................................................................................................................................................................
Issue 5 April 2014
update
....................................................................................................................................................................................................................................

Value
ulIntfCtrlFem- Flag to enable control the UL False boolean False { True, False }
toEnabled interference into neighboring
Small Cells.
Note: Only effective if the
Small Cell is part of a Small
Cell group and neighboring
Small Cells are configured.
ulIntfCtrlMac- Flag to enable control the UL False boolean False { True, False }
roEnabled interference into neighboring
macro cells.
Impacted services
None
WPS Small Cells No

WMS Small Cells No
HDM No
Small Cell Yes
IPC No
IPsec Router No
BPG No
BVG No
BSR Gateway No
SCMS No
AAA No

System

None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
update
....................................................................................................................................................................................................................................
Duration
NA
Downtime
None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Radio resource management features 116496 - 64QAM for HSDPA
....................................................................................................................................................................................................................................
116496 - 64QAM for HSDPA

Overview
Higher order modulation facilitates attaining higher throughput. In Rel-7, 3GPP has
standardized the usage of 64 Quadrature Amplitude Modulation (QAM) for High-Speed
Downlink Packet Access (HSDPA). 64QAM allows transmission of 1.5 times more bits
per symbol compared to 16QAM. The peak PHY rate is increased from 14 Mbps to 21
Mbps.
64QAM is more sensitive to noise and interferences, hence in order to decode the signal
successfully, the receiver requires higher Carrier to Interference-plus-Noise Ratio (CINR)
range. An enhanced UE receiver is required for 64QAM operation (but enhanced receiver
actually benefits beyond 64QAM coverage).
64QAM usage is expected to be more prevalent in the Small Cell environment than in the
Macro Cell environment.
Small Cells offer a good CINR distribution, as:
The area to be covered is small.
Possibly good isolation between Small Cells, or between Small Cells and Macro cells,
in case of indoor / dedicated carrier scenario.
This brings better UE throughput and cell capacity overall.
Purpose
This topic describes the activation and deactivation procedure for 64QAM for HSDPA
(116496) feature.
Related Information
In Rel-7 UMTS 3GPP, 64QAM and MAC-ehs are new features which facilitate attaining
higher peak throughputs for HSDPA. Achievable rates depend on the UE category and
radio conditions but can be up to 21.6 Mbps in Rel-7 or 42 Mbps with MIMO in Rel-8.
64QAM is a prerequisite for MAC-ehs.. Support for flexible RLC sizes is also a Rel-7
feature, and together with 64-QAM and MAC-ehs it is possible to achieve higher data
rates.
64QAM must be enabled to support MAC-ehs.
Note: Feature 64QAM for HSDPA (116496) must be enabled to support Flexible RLC
and MAC-ehs support (116497) feature.
Before you begin

Ensure that the Dynamic code allocation (132623) feature is enabled.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Note: Navigate to the specific Profile selected for this feature and modify the
parameters to values as defined in the Managed Objects section, see Managed
objects involved in feature activation (p. 4-69).
E...................................................................................................................................................................................................
N D O F S T E P S
Table 7-11 HSDPA

name Value Values
enable64QAMflag Feature enable flag - Allows False boolean True { True, False }
the use of 64QAM for release
7 UE cat 13 to 20 on HSDPA.
rLCLengthIndi- RLC frame length indicator bits15 enum bits15 { bits7=7,
catorSize size in bits. RLCLengthIndicator bits15=15 }
Size
maxHsdpaUser- Maximum DL user 14000 uint16 21 [0..42000]

Rate throughput for HSDPA, units=kbps
capped by the platform
capability
hsdpaMbrCap- Parameter enables capping of 100 uint16 100 [0..200]
ping HSDPA data rate to the units=percent
Maximum Bit rate signaled in
RANAP.
A value of 0 means that
capping is disabled.
Table 7-12 LCell

name Value Values
srnsRelocateO- Determines whether a call True boolean True { True, False }

nEarlierCon- requiring a particular release
tainer of container can be relocated
to an earlier release of RNC.
For example, a Rel-6 E-DCH
call can be relocated on Rel-5
container.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 7-13 HSDPA
Parameter Description Default Value Syntax Value Permitted Values

name
enable64QAMflag Feature enable flag - False boolean False { True, False }

Allows the use of
64QAM for release 7 UE
cat 13 to 20 on HSDPA.
Impacted services
None
WPS Small Cells Yes

WMS Small Cells No
HDM No
Small Cell Yes

IPC No
IPsec Router No
BPG No
BVG No
BSR Gateway No
SCMS No
AAA No
System

None.
Duration
NA
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Downtime
None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Radio resource management features 108877 - Coverage self-optimization based on admission
....................................................................................................................................................................................................................................
108877 - Coverage self-optimization based on admission

Overview
Feature 108877 enables the Small Cell to adapt its coverage so that public users are not
drawn in. The feature is applicable to deployments where the Small Cell has an access
control list (ACL). Public users are users not in the ACL.
If an excessive number of public users are drawn towards the Small Cell, it is an
indication that the Small Cell coverage (CPICH power level) is high and can be reduced.
Public users drawn in to the Small Cell are rejected by the Small Cell during the
attempted NAS mobility procedure.
Conventionally, a UE sends a location update when it enters the coverage range of the
Small Cell. The Small Cell determines the IMSI of the UE and performs a check against
the ACL. If the user is not in the ACL, then the Small Cell sends a LAU reject message,
which prevents the user from reaccessing the Small Cell for a period of 12-24 hours (or
power off).
The principle of this feature is that when many public users are detected by the Small
Cell, then the Small Cell is likely to be causing disruption to the macro network, if the
carrier is shared with the macro network.
If the Small Cell coverage is high, it generates both, increased signaling by capturing
unauthorized macro UEs and interferences (CPICH leakage). However, the Small Cell
pilot power cannot be reduced much, as this causes coverage gaps in the home/enterprise
area where the Small Cell Solution is originally introduced to enhance coverage.
Purpose
This topic describes the activation and deactivation procedures for Coverage
self-optimization based on admission (108877) feature.
Before you begin

In the WPS Small Cells, navigate to Femto, ensure that the attribute accessMode is set
as closedAccess.
This feature is only triggered by public UEs, that is, IMSIs not present in the ACL list.
Verify the ACL list by using the values in the attribute femtoACLlist.

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to BSR and set attribute, enableCoverageSelfOptimisa-

tionBasedOnAdmission as True.
...................................................................................................................................................................................................
3 Set the following parameters:

enableCoverageSelfOptimisationBasedOnMacroHO as True.
e6eTriggerEnabled as False.
bsrPilotPowerAdjustMode as mimBased.
ueBasedPilotPowerAdjusteMode as disable.
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S

In the WPS Small Cells, modify the following attributes:
...................................................................................................................................................................................................
1 Navigate to BSR and set attribute, enableCoverageSelfOptimisa-

tionBasedOnAdmission as False.
...................................................................................................................................................................................................
2 Set enableCoverageSelfOptimisationBasedOnMacroHO as False.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Managed objects
Managed objects in the Small Cell for coverage self-optimization based on
admission
Table 7-14 BSR
Parameter name Description Syntax Default value Permitted

values
enableCoverag- Parameter used to enable feature. If boolean False { True.

eSelfOptimisation- the events exceed threshold the False}
BasedOnMacroHO Small Cell pilot power is increased.
e6eTriggerEnabled When enabled the Small Cell sends boolean True { True.
UE a measurement control message False}
for UE to report event 6e.
bsrPilotPowerAd- The change of the value doesn't take enum mimBased {

justMode effect until next time cell is setup. BsrPilotPower- mimBased=
Adjust Mode 0,rscpBased=1,
ecIoBased=2}
ueBasedPilotPow- Dynamically adjust Small Cell Pilot enum disable { disable=0,
erAdjusteMode power based on UE's regular UeBasedPilot- targetEcIo=
measurement report of Pilot Ec/Io Power 1,
during DCH state. AdjustMode neighbourEcIo=2
}
Table 7-15 AutoConfigPW

values
admissionBasedPi- A structure which has attributes to struct

lotPowerControl control CPICH power level based AdmissionBased-
on idle mode mobility events Pilot Power
rejected by the Small Cell ACL,
(that is, by public UEs).
increaseMeasure- Period representing the maximum integer 60 1..1440]
mentPeriod period over which events are units=mins
counted for power increase.
increaseTestPeriod Period at which the events during integer 30 1..120]
the last increaseMeasurementPeriod units=mins
minutes are tested in order to
increase the pilot power .
increaseEvent- Number of attempted public UE integer 1 [1..100]

Threshold mobility events used to give the
threshold event rate over period
increasePeriodThreshold. If the
number of seen events exceed this
number the Small Cell increases its
pilot power.
increasePeri- Period over which the threshold integer 60 [1..120]

odThreshold event rate is calculated for Small units=mins
Cell pilot power increase.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 7-15 AutoConfigPW (continued)

values
increaseStepdB Power increment step when real 1.0 [0.0..10.0]

increasing the CPICH power. step=0.1
precision=1
units=dB
decreaseMeasure- Period representing the maximum integer 60 [1..1440]
mentPeriod period over which events are units=mins,
counted for power decrease.
decreaseTestPeriod Period representing the period at integer 10 [1..120]
which the events during the last. units=mins,
decreaseEvent- Number of attempted public UE integer 10 [1..100]

Threshold mobility events used to give the
threshold event rate over period
decreasePeriodThreshold. If the
rate of seen events is below this rate
the Small Cell decreases its pilot
power.
decreasePeri- Period over which the threshold integer 60 1..120]

odThreshold event rate is calculated for Small units=mins,
Cell pilot power increase.
decreaseEventMini- Minimum number of admission integer 5 [1..100]

mum events that must be seen before the
Small Cell pilot power can be
decreased due to admission events.
decreaseStepdB Power decrement step when real 1.0 [0.0..10.0]

decreasing the CPICH power. step=0.1
precision=1
units=dB
Managed objects in the Small Cell for coverage self-optimization based on Macro
handover
Table 7-16 AutoConfigPW

values
macroHOPilotPow- Attributes to control CPICH power struct

erControl level based on connected mode. MacroHOPilot-
handout events detected by the Power
Small Cell for private UEs (that is,
UEs in the Small Cell ACL).
testPeriod Period at which the macro HO integer 30 1..120]

events during the last units=mins
measurementPeriod minutes are
tested in order to increase the pilot
power .
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 7-16 AutoConfigPW (continued)

values
measurementPeriod Period representing the maximum integer 60 1..1440]

period over which events are units=mins
counted for power increase.
eventThreshold Number of attempted private UE integer 10 [1..100]

handover to macro events used to
give the threshold event rate over
period periodThreshold. If the rate
of seen events exceed this rate the
Small Cell increases its pilot power.
periodThreshold Period over which the threshold integer 60 [1..120]

event rate is calculated for Small units=mins
Cell pilot power increase due to
Macro HO.
adjustmentStep Power increment step when real 1.0 [0.0..10.0]

increasing the CPICH power step=0.1
precision=1
units=dB
Impacted services
None.
WPS Small Cells Yes

WMS Small Cells No
HDM No
Small Cell Yes

IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No

System
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
None.
Duration
NA
Downtime
None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Radio resource management features 114174 - UMTS Small Cell to LTE cell reselection
....................................................................................................................................................................................................................................
114174 - UMTS Small Cell to LTE cell reselection

Overview
Feature 114174 provides the first step of mobility between the UMTS and LTE through
cell reselection from the WCDMA Small Cell to LTE. Cell reselection between UTRAN
and E-UTRAN is supported.
Figure 7-1 Cell reselection
Legend:
Cell reselection in idle mode from UTRA to E-UTRA is highlighted in blue.
This feature allows an LTE enabled UE to move from the Small Cell network to the
desired LTE cell in idle mode. Small Cell transmits the LTE cell information in SIB19,
when enabled. A total of eight such LTE cells can be defined in single SIB19. But
normally only two to three LTE cells are defined. To define the LTE cells, LTE network
radio parameters information is required, for example, Down Link (DL) eARFCN,
blacklisted Cell.
Purpose
This topic describes the activation and deactivation procedures for UMTS Small Cell to
LTE cell reselection (114174) feature.
Assumptions
Feature 114174 does not facilitate UE mobility from Small Cell to LTE network, in
Cell-DCH, Cell-FACH or in Cell-PCH/URA-PCH modes.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Before you begin
Ensure that you are aware of the LTE DL frequency (eARFCN) of the target cell.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Set the attributes, see Managed objects involved in feature activation (p. 7-39) for
values.
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................
6 Once the work order is successful, navigate to HDM > Devices > Manage Femto > Queue
Action > Trigger > Trigger CM File Creation Action, to download a new BulkCM.xml file
from WMS Small Cells >Femto.
E...................................................................................................................................................................................................
N D O F S T E P S

Table 7-17 BSRProfile:LCell
Parameter name Description Syntax Default Permitted values Value

value
sIB19Enable Feature flag for SIB 19 support boolean False { True, False } True
utraServingCellPri- Priority parameters for serving struct

ority cell as broadcast in SIB 19. SIB19UTRASCellPri
orityParams
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 7-17 BSRProfile:LCell (continued)

value
lteCarrierPriority Priority parameters for LTE sequence [0..8] of

carriers as broadcast in SIB 19. struct SI
B19LTECarrierPriorityParams
SIB19UTRASCell priority: Defines the priority of struct { integer { , ,0, } { [0..7], [0..62]
PriorityParams the serving cell in SIB 19.0 is the priority, integer step=2 units=dB,
lowest priority and maxPrio-1 is utraSPrioritySearch1, [0..7], [0..62] step=2
the highest. integer units=dB }
Note: 7 = maxPrio - 1 utraSPrioritySearch2,
integer
utraSPrioritySearch1: Defines utraThreshSLow }
the Srxlev of the UTRA serving
cell used for neighboring
measurement triggering.
utraSPrioritySearch2: Defines
the Squal of the UTRA serving
cell used for neighboring
measurement triggering.
utraThreshSLow: Defines the
RSCP threshold Low of the
UTRA serving cell used by the
UE reselection process.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 7-17 BSRProfile:LCell (continued)

value
SIB19LTECarrier id: Instance number of struct { Integer32 id, {, { [1..8], [0..65535],

PriorityParams lteCarrierPriority. eARFCN: integer eARFCN, , {
Defines the EARFCN of the measBand-
downlink carrier frequency. enum width 6, , , , measBandwidth6=6,
MeasurementBand- True} measBandwidth15=15,
measurementBandwidth: widthmeas
Defines the Measurement urementBandwidth, measBandwidth25=25,
bandwidth information common
integer priority, measBandwidth50=50,
for all neighboring cells on the
carrier frequency. The values integer measBandwidth75=75,
indicate the number of resource qrxlevminEUTRA, measBand-
blocks over which the UE could width100=100 },
integer threshXHigh,
measure. [0..7],
integer threshXLow,
priority: Defines the priority of [-140..-44] step=2
the E-UTRA target frequency.0 is string units=dBm,
the lowest priority and maxPrio-1 blacklistedCells,
[0..62] step=2
is the highest.Note: 7 = maxPrio - boolean units=dB,
1 eutraDetection}
[0..62] step=2
qrxlevminEUTRA: Defines the
units=dB,
Qrxlevmin (RSRP) of the
E-UTRA cell used for S criteria of length=64,
the reselection process. { True, False }
threshXHigh: An Srxlev based }
threshold used by the UE for cell
reselection towards a higher
absolute priority layer when
absolute priorities are applied. A
threshold is defined for each
absolute priority layer.
threshXLow: An Srxlev based
threshold used by the UE for cell
reselection towards an equal or
lower absolute priority layer when
absolute priorities are applied. A
threshold is defined for each
absolute priority layer.
blacklistedCells: Defines the
blacklisted cells of this E-UTRA
carrier. It defines as a
comma-separated string of up to
16 integer values in the range of
[0..503].
Note: 16 =
maxEUTRACellPerFreq
eutraDetection: Defines the
'TRUE' means that the UE may
detect the presence of an E-UTRA
cell and report to NAS.
Note: If the value of E-UTRA
detection is not identical across
the frequency layers, UE behavior
....................................................................................................................................................................................................................................
is unspecified.
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 7-18 BSRProfile:LCell

Value
sIB19Enable Feature flag for SIB 19 support boolean False { True, False } False
Impacted services
As the new database will be downloaded from the SCMS to Small Cell, There is a an
outage (<5 mins) in each Small Cell.
WPS Small Cells No

WMS Small Cells No
HDM No
Small Cell Yes As the new database will be
downloaded from the SCMS to
Small Cell, There is a an outage (<5
mins) in each Small Cell.
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No
System

None.
Duration
NA
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Downtime
As the new database is downloaded from the SCMS to Small Cell, There is an outage (<5
mins) in each Small Cell.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Radio resource management features 116498 - Multi-objectives joint coverage optimization
....................................................................................................................................................................................................................................
116498 - Multi-objectives joint coverage optimization

Overview
Feature 116498 optimizes QoS by continuously updating the Small Cell coverage with
the multiple objectives: load, coverage and pilot power in an enterprise/metro
environment.
Previously, in an enterprise/metro environment, the pilot power was set to a constant
value, as the primary objective was to provide continuous coverage. The variation of the
cell load over the day was not considered. The number of UEs could suddenly increase
(for example, people gathering for a meeting).
When the coverage was constant, theSmall Cell continued to capture new UEs leading to
a degradation of the QoS of the already connected UEs.
The objective of this feature is to ensure that:
Load is balanced over the cells over time .
Overlap between Small Cells is sufficient to ensure continuous coverage.
Purpose
This topic describes the activation and deactivation procedures for Multi-objectives joint
coverage optimization (116498) feature.
Before you begin

Ensure that:
Standalone/Grouped Small Cells are operational and accessible by WPS Small Cells.
Macro neighbors must exist in case of a standalone Small Cell. Macro neighbors may
exist in case of grouped Small Cells also.
There is sufficient coverage overlap between the cells being enabled and their
neighbors (Small Cell and/or macro).

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to BSRProfile, set jCOEnabled as True.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................
6 Once the work order is successful, navigate to HDM > Devices > Manage Femto Queue a
Connection Request to this device > Queued Functions. Select Custom Download.
...................................................................................................................................................................................................
7 Navigate to WMS Small Cells >Femto to download a new BulkCM.xml file.

...................................................................................................................................................................................................
8 Once step 6, is successful, verify the attributes in HDM by executing the

GetParameterValues on that particular attribute.
E...................................................................................................................................................................................................
N D O F S T E P S

Table 7-19 BSR

value
jCOEnabled Flag to enable the feature boolean True False {True, False}

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to BSRProfile, set jCOEnabled as False.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................
Connection Request to this device > Queued Functions. Select Custom Download.
...................................................................................................................................................................................................
7 Navigate to WMS Small Cells >Femto to download a new BulkCM.xml file.

...................................................................................................................................................................................................
8 Once step 6, is successful, verify the attributes in HDM by executing the

E...................................................................................................................................................................................................
N D O F S T E P S

Table 7-20 BSR

value
jCOEnabled Flag to enable the feature boolean False False {True, False}
Impacted services
is a temporary outage.
WPS Small Cells Yes

WMS Small Cells No
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
HDM Yes

Small Cell Yes Small Cell requires to be restarted.
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No

System

The features Multi objectives joint coverage optimization (116498) and Coverage
self-optimization based on admission (108877) cannot be activated simultaneously,
that is, attributes jCOEnabled and enableCoverageSelfOptimisa-
tionBasedOnAdmission must not be set as True simultaneously. For more
information on feature 108877, see 108877 - Coverage self-optimization based on
admission (p. 7-32).
Note: If attribute ueBasedPilotPowerAdjustMode is set as True, the Coverage
self-optimization based on admission (116498) feature takes precedence over the
Coverage self-optimization based on admission (108877).
Duration
NA
Downtime
is a temporary downtime.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Radio resource management features 170891 - Neighbor list optimization based on UE
measurements
....................................................................................................................................................................................................................................
170891 - Neighbor list optimization based on UE

measurements
Overview
This feature enhances the detection, auto-configuration, and self-optimization of neighbor
cells.
This feature enhances the mechanism of discovering the neighbor cells as follows:
Enhanced neighbor cell discovery by means of UE measurements reports of detected
cells.
Optimization of the neighbor list.
The Small Cell maintains internally a list of neighbor cell candidates, and selects a subset
from this out of these which is signaled towards the UE, either in SIB11 for idle mode, or
in Measurement Control message in connected mode.
Purpose
This topic describes the activation and deactivation procedures for Neighbor list
optimization based on UE measurements (170891) feature.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Set the attribute, sparePara35 as

NLOptimisationParams=000000;NLmaxAge=ZZ;NLUlTime=HHMM;
The flags enableNLOptimisation, usePreviousNCellList, resetN-
CellList, enableNCellDetectionAlarms, neighbourInfoFileGen,
neighbourInfoFileUpload and maxNCellListAge are encoded in sparePara35
as NLOptimisationParams=000000;NLmaxAge=ZZ;NLUlTime=HHMM;.
Each boolean flag being defined as one digit in the value segment of the
NLOptimisationParams string, with value 0 or 1, and the parameter maxNCellListAge
as the terminating integer value, ZZ.
Note: If an incorrect number of flags are set, then all flags and parameters are set to
their default values. If any individual flag is set with an invalid value, then the default
value for that flag is considered.
....................................................................................................................................................................................................................................
Issue 5 April 2014
measurements
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S

Table 7-21 sparepara35
Parameter name Description Syntax Default Permitted values

value
enableNLOptimisa- Enables the feature when set as 1. boolean 0 {0, 1}

tion
usePreviousN- Used to define whether the cells boolean 0 {0, 1}
CellList sniffed during previous optimization
is to be considered while populating
the new neighbor list.
resetNCellList Clears the existing neighbor list boolean 0 {0, 1}

when set as 1.
neighbourInfoFile- Generate statistics files when set as boolean 0 {0, 1}

Gen 1.
neighbourInfo- Uploads statistics files in .tgz format boolean 0 {0, 1}

FileUpload when set as 1.
maxNCellListAge integer {1.. 31}
nlUploadTime Specifies the time of the day when 24 hour {00..23, 00..60}
the files will be uploaded format
NLmaxAge Defines the maximum time a stored integer 7 {1.. 32}

neighbor cell list is considered as (days)
valid
....................................................................................................................................................................................................................................
Issue 5 April 2014
measurements
....................................................................................................................................................................................................................................
Table 7-22 RFTrace
Parameter name Description Default Value Syntax Permitted values
sftpServer FTP server to upload 0.0.0.0 IP address

the statistics file.
rootDirectory Directory location string length=100
where the file should
be uploaded

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Set the attribute, sparePara35 as Unset.

...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
Impacted services
Small Cell requires a restart during activation/deactivation. Hence services are disrupted
during that period.
....................................................................................................................................................................................................................................
Issue 5 April 2014
measurements
....................................................................................................................................................................................................................................
WPS Small Cells Yes
WMS Small Cells Yes

HDM No

Small Cell Yes
IPC No
IPsec Router No
BSR Gateway No
AAA No

System

None.
Duration
NA
Downtime
There is an outage during activation and deactivation, as the Small Cell requires a restart.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Radio resource management features 170695 - Change of Service Area Location Reporting
....................................................................................................................................................................................................................................
170695 - Change of Service Area Location Reporting

Overview
Change of Service Area Location Reporting is used by the core networks to be informed,
in real time, of the current Service Area Identifier (SAI) of the cell a UE is located on -
for emergency calls or value added location-based services. The service area in which a
UE is located can change during the lifetime of a call, as a result of handover between
cells assigned with difference SAIs.
The core network can automatically track that mobility by requesting Change of Service
Area Location Reporting to the RAN. Once a Change of Service Area Location Reporting
has been requested, the RAN is required to report, after every handover, the SAI of the
new serving cell if the SAI is different from the service area previously reported for that
UE.
When the core network sends a RANAP LOCATION REPORTING CONTROL whose
request type is Change of SAI, then the Small Cell network issues a RANAP LOCATION
REPORT message with the current SAI whenever the information given in the previous
LOCATION REPORT message or INITIAL UE MESSAGE message is not valid anymore.
For the Small Cells Cluster, the SAI changes in the following situations:
After a Macro to Small Cell handover
After a Small Cell to Small Cell handover
Optionally the Small Cell sends the RANAP LOCATION REPORT after receiving the
RANAP LOCATION REPORTING CONTROL for change of service area even if the SAI
has not changed.
Purpose
This topic describes the activation and deactivation procedures for Change of Service
Area Location Reporting (170695) feature.
Related information
Support for all types of location reporting by the Small Cell depends on the call type, and
the status of operation of the location-based services are on the cell:
For emergency calls, location reporting is always enabled.
For a non-emergency call, location reporting is supported only when the
location-based services have been enabled on the Small Cell.

To support Change of SAI Location Reporting for non-emergency calls, the
location-based services must be enabled in the Small Cell configuration data.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to Network > profile > BSR . Set attribute activateLocationBasedSer-

vices as True.
...................................................................................................................................................................................................
3 Navigate to Network > profile > BSRProfile, locate attribute sparePara4 and set values
for attributes alwaysSendLR and positionDataforSA.
See Managed objects involved in feature activation for more information regarding
the attributes.
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S

Table 7-23 BSR

name values
activateLo- Feature activation control to boolean True {True, True

cationBased- enable/disable Location False}
Services Based Services functionality
availability on the Small Cell.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Notes:
1. The attribute activateLocationBasedServices is common for all types of Location Reporting and is
not specific to Change of Service Area Location Reporting.
The Location Report for event type Change of Service Area is managed by the following
attributes:
Parameter Description Syn- Default value Permitted values Values

name tax
alwaysSendLR Defines whether location string alwaysSendLR=False {alwaysSendLR=True, alwaysSendLR=True

report is sent. alwaysSendLR=False}
position- Defines the value inte- {1.. 255} positionDataforSA=<value>

DataforSA populated for position data ger
IE when Service Area is
reported.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to Network > profile > BSR . Set attribute activateLocationBasedSer-

vices as False.
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 7-25 BSR

name values
activateLo- Feature activation control to boolean True {True, False

cationBased- enable/disable Location False}
Services Based Services functionality
availability on the Small Cell.
Impacted services
None
WPS Small Cells Yes

WMS Small Cells Yes
HDM Yes
Small Cell Yes The Small Cell performance is impacted by one
additional RANAP Location Report message generated
by the Small Cell after every:
Handover from a Macro to Small Cell
Handover between Small Cells
IPC No
IPsec Router No
BSR Gateway Yes The BSR Gateway performance is impacted by one

additional RANAP Location Report message generated
by the Small Cell after every:
Handover from a Macro to Small Cell
Handover between Small Cells
AAA No

System
Duration
NA
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Downtime
NA
....................................................................................................................................................................................................................................
Issue 5 April 2014
Radio resource management features 171355 - Coordinated self optimization in groups
....................................................................................................................................................................................................................................
171355 - Coordinated self optimization in groups

Overview
Currently, periodic self optimization is triggered independently by each Small Cell during
a quiet time and this behavior is suitable for residential Small Cells.
However, this behavior is not suited to groups of Enterprise or Metro cells. One of the
limitations of independently triggered self-optimization is that, more than one Small Cell
in a group can initiate periodic sniffing at the same time, implying that these Small Cells
cannot detect each other. These Small Cells could be critical neighbors from a mobility
perspective, which can result in performance degradation.
This feature aims to improve coordination of periodic sniffing within a group of Small
Cells.
Another area of focus for this feature are the trigger conditions for execution of
sniffer-based algorithms as part of auto-configuration and self-optimization procedures.
Purpose
This topic describes the activation and deactivation procedures for Coordinated self
optimization in groups (171355) feature.
Related information
Feature 171355 interacts with feature 170891 - Neighbor list optimization based on UE
measurements and mobility reports. For more information, see 170891 - Neighbor list
optimization based on UE measurements (p. 7-48).

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to Network > profile > BSR .

Set attribute sparePara3 with values enableCoordinatedSelfOptGroups=True;
enablePeriodicSelfOpt=False;disableAutoConfLCellUnlock=True;
triggerSelfOpt=False.
The attribute sparePara3 cane also be set as CoordinatedSelfOptGroups=true,
false,true,false.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
To trigger the self-optimization using WMS Small Cells

The WMS Small Cells does not have a managed object, but can be triggered using the
Wireless Internet Command Language (WICL). Perform the following steps:
...................................................................................................................................................................................................
1 Navigate to /opt/Nortel/data/cmXML and create a file 3gsitefile with execute permission.

...................................................................................................................................................................................................
2 Edit 3gsitefile and update the Small Cell group name as appropriate.
...................................................................................................................................................................................................
3 Using the WICL GUI execute the following command:

act3gsniffer -file <path> - interval <duration in sec> verbose
For example: act3gsniffer -file /cmXML/3gsitefile - interval 5
verbose
For more information on the WICL GUI usage, see Alcatel-Lucent 9353 Wireless
Management System Small Cells - Commands Reference Guide (WICL),
9YZ-05614-0608-RKZZA.
...................................................................................................................................................................................................
4 Navigate to /opt/Nortel/data/cmXML and verify the log file with format

3gsitefile_YYYY_MM_DD_HOUR_MIN_SEC.log. The time stamp on the log file depends
on the interval duration defined in the command.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 7-26 BSR::sparePara3
Parameter name Description Syntax Default Permitted Values

value values
enableCoordinated- Parameter to enable the feature boolean False {True, True

SelfOptGroups False}
enablePeriodicSel- Enables the periodic boolean True {True, False
fOpt self-optimization function False}
during non-busy time
disableAutoConfL- Disables the boolean False {True, True

CellUnlock auto-configuration procedures False}
when receiving Unlock
command on LCell from
SCMS.
triggerSelfOpt Triggers the self-optimization boolean False {True, False
function in Small Cell False}

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to Network > profile > BSR .

Set attribute sparePara3 with values enableCoordinatedSelfOptGroups=False;
enablePeriodicSelfOpt=True;disableAutoConfLCellUnlock=False;
triggerSelfOpt=False.
The attribute sparePara3 can also be set as CoordinatedSelfOptGroups=true,
false,false,false.
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S

Table 7-27 BSR::sparePara3
Parameter name Description Syntax Default Permitted Values

value values
enableCoordinatedSel- Parameter to enable the boolean False {True, False

fOptGroups feature False}
enablePeriodicSelfOpt Enables the periodic boolean True {True, True
self-optimization False}
function during non-busy
time
disableAutoConfLCel- Disables the boolean False {True, False

lUnlock auto-configuration False}
procedures when
receiving Unlock
command on LCell from
SCMS.
triggerSelfOpt Triggers the boolean False {True, False

self-optimization False}
function in Small Cell
Impacted services
Any ongoing call (CS/PS) other than an emergency call is dropped during this procedure.
WPS Small Cells Yes

WMS Small Cells Yes
HDM Yes

Small Cell Yes TheSmall Cell performs the
self-optimization procedures during
its non-busy time. Any ongoing call
(CS/PS) other than an emergency
call is dropped during this
procedure.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
IPC No
IPsec Router No
BSR Gateway No
AAA No
System
Duration
NA
Downtime
None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
8 Mobility features
8
Overview
Purpose
This chapter describes the activation/deactivation procedure for the Small Cell Mobility
Features.
Contents
100856 - Intra-frequency Small Cell to 3G Macro MAHO for CS calls 8-2

100857 - Intra-frequency Small Cell to 3G Macro MAHO for PS and CS+PS 8-6
calls
75387 - UE assisted Small Cell to Macro handover 8-10
75386 - Cell change order 8-15
100888 - Inter-frequency Small Cell to 3G Macro handover for PS and CS+PS 8-19
calls
101684 - 3G Macro to Small Cell handover for PS and CS+PS calls 8-24
172248 - Release PS during SIM bearer (CS+PS) handover 8-31
...................................................................................................................................................................................................................................
Issue 5 April 2014
Mobility features 100856 - Intra-frequency Small Cell to 3G Macro MAHO for
CS calls
....................................................................................................................................................................................................................................
100856 - Intra-frequency Small Cell to 3G Macro MAHO for CS

calls
Overview
This feature allows a CS call to be handed over to the best 3G intra-frequency macro cell
as measured by the UE.
Prior to this feature, the Small Cell to 3G Macro CS calls were handed over to the best 3G
cell determined by the Small Cell Listening Function (or sniffer). The sniffer scans and
ranks the 3G (and 2G) neighboring cell during auto-configuration and self-optimization.
Whenever a Small Cell is deployed on the same frequency as the 3G macro cell, there
could be important interference between both cells, and in that case, in order to find the
most suitable 3G target cell, a mobile assisted handover is preferred.
With this feature, UE measurements are used to select the best 3G intra-frequency target
cell.
Note: In this case, Compressed Mode is not needed.
Purpose
This topic describes the activation and deactivation procedure for Intra-frequency Small
Cell to 3G Macro MAHO for CS calls (100856) feature.
Before you begin

Ensure that the Small Cell, WPS Small Cells, WMS Small Cells and HDM are
operational.

...................................................................................................................................................................................................
Note: Navigate to the specific BSRProfile and modify the parameters to values as
defined in the Managed Objects section, see Managed objects involved in feature
activation (p. 4-69).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
CS calls
....................................................................................................................................................................................................................................

name Values
mahoActiva- Flag to activate/deactivate True boolean True { True, False }

tionIntra the feature.
Table 8-2 LCell (BSRProfile-LCell/1)

name Value
targetHOCS Defines the allowed and fddPre- enum can be set as { disable=0,
preferred target system for ferred TargetHO fdd or gsm=1, fdd=2,
outgoing handover of UEs gsmPreferred gsmPreferred=3,
with CS calls. or fddPreferred=4 }
fddPreferred
to enable this
feature.
Note: In case, the Small Cell to Small Cell handover is enabled, the Small Cell can
prioritize handover to another Small Cell. One out of two different Cell Individual
Offsets (CIOs) is applied to the macro cell, depending on the scenario:
cioMacroMixed (if there are other Small Cells monitored concurrently), or,
cioMacroNormal

name Value
cioMacroMixed Cell individual offset for an 0.0 real [-10.0..10.0] [-10.0..10.0]

intra-frequency macro cell step 0.5 step=0.5
when there are other Small precision=1
Cells monitored
concurrently.
cioMacroNor- Cell individual offset for an 0.0 real [-10.0..10.0] [-10.0..10.0]
mal intra-frequency macro cell step 0.5 step=0.5
when there are not any precision=1
Small Cells monitored
concurrently.
intraMa- During intra-frequency 0 integer [-24..0] [-24..0] step=1

hoOwnEcNo MAHO, the own cell Ec/No step=1 units=dB
must be this level or worse units=dB
to trigger Small Cell to
Macro handover.
....................................................................................................................................................................................................................................
Issue 5 April 2014
CS calls
....................................................................................................................................................................................................................................
Note: In order to avoid unnecessary mobility procedures, while the serving Small Cell
EcNo is above intraMahoOwnEcNo, 1C measurements are ignored. Therefore an
intra-frequency handover cannot occur.

name Value Values
mahoActiva- Flag to activate/deactivate True boolean False { True, False }

tionIntra the feature.

name Value Values
targetHOCS Defines the allowed and fddPreferred enum disable/ gsm { disable=0,
preferred target system for TargetHO gsm=1, fdd=2,
outgoing handover of UEs gsmPreferred=3,
with CS calls. fddPreferred=4
}
Impacted services
Feature activation results in Small Cell soft reset. Hence, Small Cell services are impacted
during the Small Cell restart operation.
WPS Small Cells No
WMS Small Cells No

HDM No

Small Cell Yes Small Cell must be restarted.
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No
....................................................................................................................................................................................................................................
Issue 5 April 2014
CS calls
....................................................................................................................................................................................................................................

System

None.
Duration
The activation/deactivation of this feature is done in 10 minutes (approximately). And this
includes the time taken for Small Cell soft reset from OAM, for Import Bulk CM, and
Custom Download policy at the HDM.
Downtime
There is a downtime during the Small Cell reset operation.
....................................................................................................................................................................................................................................
Issue 5 April 2014
PS and CS+PS calls
....................................................................................................................................................................................................................................
100857 - Intra-frequency Small Cell to 3G Macro MAHO for PS

and CS+PS calls
Overview
The Intra-frequency Small Cell to 3G Macro MAHO for PS and CS+PS calls (100857)
feature, allows a PS call or a CS+PS call to be handed over the best 3G intra-frequency
macro cell, as measured by the UE.
Handover between the Small Cell and the macro network is performed using the RANAP
relocation procedure (also known as an SRNS relocation UE involved).
Purpose
This topic describes the activation and deactivation procedure for Intra-frequency Small
Cell to 3G Macro MAHO for PS and CS+PS calls (100857) feature.
Before you begin

operational.

...................................................................................................................................................................................................
Note: Navigate to the specific BSRProfile and modify the parameters to values as
defined in the Managed Objects section, seeManaged objects involved in feature
activation (p. 4-69).
E...................................................................................................................................................................................................
N D O F S T E P S

name Values
mahoActiva- Flag to True boolean True { True, False }

tionIntra activate/
deactivate the
feature.
....................................................................................................................................................................................................................................
Issue 5 April 2014
PS and CS+PS calls
....................................................................................................................................................................................................................................

name Values
targetHOPS Defines the fddPreferred enum TargetHO can be set as { disable=0,

allowed and fdd or gsm=1, fdd=2,
preferred target gsmPreferred gsmPreferred=3,
system for or fddPreferred=4
outgoing fddPreferred }
handover of UEs to enable this
with PS calls. feature.
targetHOCSPS Defines the fddPreferred enum TargetHO can be set as { disable=0,
allowed and fdd or gsm=1, fdd=2,
preferred target gsmPreferred gsmPreferred=3,
system for or fddPreferred=4
outgoing fddPreferred }
handover of UEs to enable this
with feature.
simultaneous CS
and PS calls.
Note: In case, the Small Cell to Small Cell handover is enabled, the Small Cell can
prioritize handover to another Small Cell. So one out of two different CIOs (Cell
Individual Offset) is applied to the macro cell, depending on the scenario:
cioMacroMixed (if there are other Small Cells monitored concurrently), or,
cioMacroNormal

name Values
cioMacroMixed Cell individual 0.0 real [-10.0..10.0] [-10.0..10.0]

offset for an step 0.5 step=0.5
intra-frequency precision=1
macro cell when
there are other
Small Cells
monitored
concurrently.
cioMacroNor- Cell individual 0.0 real [-10.0..10.0] [-10.0..10.0]
mal offset for an step 0.5 step=0.5
intra-frequency precision=1
macro cell when
there are not any
Small Cells
monitored
concurrently.
....................................................................................................................................................................................................................................
Issue 5 April 2014
PS and CS+PS calls
....................................................................................................................................................................................................................................
Note: In order to avoid unnecessary mobility procedures, while the serving Small Cell
EcNo is above intraMahoOwnEcNo, 1C measurements are ignored. Therefore an
intra-frequency handover cannot occur.

name Values
intraMa- During 0 integer [-24..0], [-24..0] step=1

hoOwnEcNo intra-frequency unit=dB, step=1 units=dB
MAHO, the own
cell Ec/No must
be this level or
worse to trigger
Small Cell to
Macro handover.

name Values
mahoActiva- Flag to True boolean False { True, False }

tionIntra activate/
deactivate the
feature.

name Values
targetHOPS Defines the fddPreferred enum TargetHO disable/ gsm { disable=0,

allowed and gsm=1, fdd=2,
preferred target gsmPreferred=3,
system for fddPreferred=4
outgoing }
handover of UEs
with PS calls.
targetHOCSPS Defines the fddPreferred enum TargetHO disable/ gsm { disable=0,
allowed and gsm=1, fdd=2,
preferred target gsmPreferred=3,
system for fddPreferred=4
outgoing }
handover of UEs
with
simultaneous CS
and PS calls.
....................................................................................................................................................................................................................................
Issue 5 April 2014
PS and CS+PS calls
....................................................................................................................................................................................................................................
Impacted services
Feature activation results in Small Cell soft reset. Hence, Small Cell services are impacted
during the Small Cell restart operation.
WPS Small Cells No
WMS Small Cells No

HDM No

Small Cell Yes Small Cell must be restarted.
IPC No
IPsec Router No
BPG No
BVG No
BSG Yes
AAA No
SCMS Yes

System

None.
Duration
The activation/deactivation of this feature is done in 10 minutes (approximately). And this
includes the time taken for Small Cell soft reset from OAM, for Import Bulk CM, and
Custom Download policy at the HDM.
Downtime
There is a downtime during the Small Cell reset operation.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Mobility features 75387 - UE assisted Small Cell to Macro handover
....................................................................................................................................................................................................................................
75387 - UE assisted Small Cell to Macro handover

Overview
Previously, handover from a Small Cell to a macro cell was triggered based on
measurements of the Small Cell only. The quality of the actual macro cells available at
the location of the Small Cell was measured during the auto-configuration/self-
optimization phase.
Feature 75387, makes it possible to determine the best target macro cell just before the
handover is triggered at the current UE location.
To determine the best target macro cell, this feature enables the UE to send
inter-frequency or inter-RAT measurements prior to the execution of a handover of a
voice call.
Purpose
This topic describes the activation and deactivation procedures for UE assisted Small Cell
to Macro handover (75387) feature.
Before you begin

Ensure the following:
BSR Gateway and Small Cell are operational.
3G/2G macro neighbor cells are configured.
WMS Small Cells is available to make the BulkCM changes.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to the specific BSRProfile in which the feature related changes are planned.
Set the attributes as described in Managed objects involved in feature activation section,
see Managed objects involved in feature activation (p. 4-69).
...................................................................................................................................................................................................

...................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Connection Request to this device > Queued Functions.. Select Custom Download.
...................................................................................................................................................................................................
7 Navigate to WMS Small Cells > Femto to download a new BulkCM.xml file.
...................................................................................................................................................................................................
8 Once step 6 is successful in HDM, verify the attributes in HDM by executing the
E...................................................................................................................................................................................................
N D O F S T E P S

Parameter name Description Value Syn- De- Permitted Values

tax fault
Value
mahoInterQuality- Determines whether In the WPS bool- False {True, False }

ConfigMahoInter- inter-frequency/RAT MAHO is Small ean
Candidate enabled for this scenario. Cells, set
BSRProfile
If set as False, the
inter-frequency/RAT is not > HO as
activated. True.
If set as True, the

inter-frequency RAT is a
candidate for MAHO.
mahoInterActiva- This parameter determines the In the WPS enum never { automatic=0,
tionCs activation of inter-frequency/ Small always=1, never=2,
RAT MAHO for CS+PS Cells, set numberOfTargets=3 }
services. BSRProfile
> LCell as
always - Enable MAHO
always.
never - Disable MAHO
automatic - Use measurement
statistics to automatically
determine
numberOfTargets - Enable
MAHO only when the number
of HO candidates exceed a
threshold.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

tax fault
Value
mahoInterLayers Determines which macro layers In the WPS enum fddgsm { fdd=0, gsm=1,
MAHO may be eligible. This Small MahoLayers fddgsm=2 }
applies to MAHO for Cells, set
inter-frequency 3G and BSRProfile
inter-RAT only. > LCell as
fddgsm.
mahoInter2d2fEcno- The threshold for sending a 2d In the WPS

Threshold2d measurement report. If the Small
measured EcNo value of the Cells, set
used frequency falls below the BSRProfile
value (threshold2d > HO
hysteresis2d/2) for the time value.
timeToTrigger2d then blind HO
is triggered.
At the threshold, the UE triggers
event 2d and compress mode is
activated. The UE begins to
perform inter-frequency/
inter-RAT measurements.
mahoInter2d2fEcno- The threshold for sending a 2f In the WPS

Threshold2f measurement report. If the Small
measured EcNo value of the Cells, set
used frequency rises above the BSRProfile
value (threshold2f + > HO
hysteresis2f/2) for the time value.
timeToTrigger2f , then HO due
to EcNo is not necessary.
mahoInter2d2fRscp- The threshold for sending a 2d In the WPS
Threshold2d measurement report. If the Small
measured RSCP value of the Cells, set
used frequency falls below the BSRProfile
value (threshold2d > HO
hysteresis2d/2) for the time value.
timeToTrigger2d, then blind HO
is triggered.
At the threshold, the UE triggers
event 2d and compress mode is
activated. The UE begins to
perform inter-frequency/
inter-RAT measurements.
mahoInter2d2fRscp- The threshold for sending a 2f In the WPS

Threshold2f measurement report. If the Small
measured RSCP value of the Cells, set
used frequency raises above the BSRProfile
value (threshold2f + > HO
hysteresis2f/2) for the time value.
timeToTrigger2f, then HO due to
EcNo is not necessary.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................

tax fault
Value
mahoInterQualityFdd- Defines the Ec/No threshold of In the WPS

OwnEcNo the cell, for which the MAHO Small
measurement report must be Cells, set
lesser than or equal to before an BSRProfile
inter-freq/RAT HO is triggered. > HO
A handover is triggered at the value.
set value.
mahoInterQualityFdd- Defines the RSCP threshold of In the WPS

OwnRscp the cell, for which the MAHO Small
measurement report must be Cells, set
lesser than or equal to before an BSRProfile
inter-freq/RAT HO is triggered. > HO
A handover is triggered at the value.
set value.

Parameter Description Value Syn- Default Permitted Values

name tax Value
mahoInterActi- This parameter determines the In the WPS enum never { automatic=0,
vationCs activation of inter-frequency/RAT Small always=1,
MAHO for CS+PS services. Cells, set never=2,
always - Enable MAHO BSRProfile numberOfTargets=3
> LCell as }
never - Disable MAHO never.
automatic - Use measurement statistics
to automatically determine
numberOfTargets - Enable MAHO
only when the number of HO
candidates exceed a threshold.
Impacted services
Feature activation requires the Small Cell to be restarted. All the services are impacted
during this period.
WPS Small Cells No
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
WMS Small Cells No
HDM No
Small Cell Yes CM download is triggered by means

of HDM and Small Cell requires to
be restarted.
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No
SCMS Yes
System

None.
Duration
The activation/deactivation of the feature takes approximately 20 minutes. 5 minutes for
creating a work order using WPS Small Cells, and 15 minutes approximately for
executing the work order using WMS Small Cells (including the time taken for custom
download from the HDM to the Small Cell).
Downtime
....................................................................................................................................................................................................................................
Issue 5 April 2014
Mobility features 75386 - Cell change order
....................................................................................................................................................................................................................................
75386 - Cell change order

Overview
This feature facilitates an outgoing handover from the Small Cell to a 2G Macro network
in the PS domain.
The handover between the Small Cell and the 2G Macro network is performed using a
Cell Change Order procedure.
Prior to feature 75386, the Small Cell supported handover of CS (and CS+PS calls) to the
2G Macro network, but PS only calls could not be handed over to 2G. The mechanism for
transferring a PS only call from 3G to 2G is called Cell Change Order. Essentially, this
commands the UE to perform cell reselection from the 3G cell to the 2G cell and
re-establish on the 2G cell.
Purpose
This topic describes the activation and deactivation procedures for Cell change order
(75386) feature.
Before you begin

Ensure the following:
BSR Gateway and Small Cell are operational.
2G macro neighbor cells are configured.
WMS Small Cells is available to make the BulkCM changes.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to the specific BSRProfile in which the feature related changes are planned.
Set the attributes as described in Managed objects involved in feature activation section,
see Managed objects involved in feature activation (p. 4-69).
...................................................................................................................................................................................................

...................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
from WMS Small Cells > Femto.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S

Parameter name Description Value Syntax Default Permissible

Value Values
targetHOPS Defines the allowed and In the WPS enum fddPre- { disable=0,
preferred target system for Small Cells, set Tar- ferred gsm=1, fdd=2,
outgoing handover of UEs BSRProfile > getHO gsmPreferred=3,
with PS calls. LCell as gsm or fddPreferred=4 }
gsmPreffered
.
mahoInterActiva- This parameter determines In the WPS enum never { automatic=0,
tionPs the activation of Small Cells, set Maho- always=1,
inter-frequency/RAT MAHO BSRProfile > Activa- never=2,
for PS services. LCell as never. tion numberOfTargets=3
always - Enable MAHO }
never - Disable MAHO
automatic - Use
measurement statistics to
automatically determine
numberOfTargets - Enable
MAHO only when the
number of HO candidates
exceed a threshold.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Parameter name Description Value Syntax Default Permissible

Value Values
blindHO2d2f The threshold for sending a In the WPS -15 In the range of
EcnoThreshold2d 2d measurement report. If Small Cells, set -24 to 0
the measured EcNo value of the BSRProfile >
the used frequency is lesser HO value.
than the (threshold2d
hysteresis2d/2) value for the
time timeToTrigger2d, then a
blind HO is triggered.
blindHO2d2f The threshold for sending a In the WPS -15 In the range of
EcnoThreshold2f 2f measurement report. If Small Cells, set -24 to 0
the measured EcNo value of BSRProfile > HO
the used frequency raises value.
above the threshold2f +
hysteresis2f/2 value for the
time timeToTrigger2f,
then HO due to EcNo is no
longer necessary
blindHO2d2f The threshold for sending a In the WPS In the range of

RscpThreshold2d 2d measurement report. If Small Cells, set -115 to -25
the measured RSCP value of BSRProfile > HO
the used frequency falls value.
below the threshold2d
hysteresis2d/2 value for the
time timeToTrigger2d
then blind HO is triggered.
blindHO2d2f The threshold for sending a In the WPS In the range of

RscpThreshold2f 2f measurement report. If Small Cells, set -115 to -25
the measured RSCP value of BSRProfile > HO
the used frequency rises value.
above the threshold2f +
hysteresis2f/2 value for the
time timeToTrigger2f,
then HO due to EcNo is no
longer necessary.

Parameter name Description Value Syntax Default Permitted

Value Values
targetHOPS Defines the allowed and preferred In the WPS enum fddPre- { disable=0,
target system for outgoing Small Cells, TargetHO ferred gsm=1,
handover of UEs with PS calls. set fdd=2,
BSRProfile gsmPreferred=3,
> LCell as fddPreferred=4
fdd or }
disable.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Impacted services
Feature activation requires the Small Cell to be restarted. Services are impacted during
this period.
WPS Small Cells No
WMS Small Cells No

HDM No

Small Cell Yes
IPC No
IPsec Router No
BPG No
BVG No
BSG Yes
AAA No
SCMS Yes

None.
Duration
The activation/deactivation of the feature takes approximately 20 minutes. 5 minutes for
creating a work order using WPS Small Cells, and 15 minutes approximately for
executing the work order using WMS Small Cells (including the time taken for custom
download from the HDM to the Small Cell).
Downtime
....................................................................................................................................................................................................................................
Issue 5 April 2014
Mobility features 100888 - Inter-frequency Small Cell to 3G Macro handover
for PS and CS+PS calls
....................................................................................................................................................................................................................................
100888 - Inter-frequency Small Cell to 3G Macro handover for

PS and CS+PS calls
Overview
This feature enables the support of outgoing handover from a Small Cell to a UMTS
Macro network in the PS domain.
Purpose
This topic describes the activation and deactivation procedures for Inter-frequency Small
Cell to 3G Macro handover for PS and CS+PS calls (100888) feature.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to the BSRprofile selected for this feature.

Set the attribute values as described in the Managed objects involved in feature activation
section, Managed objects involved in feature activation (p. 4-69).
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S

Managed objects in the BSR
Table 8-16 LCell(BSRProfile-LCell/1)
Parameter name Description Default Syntax Permitted values

value
targetHOPS Defines the allowed and preferred fddPre- enum TargetHO { disable=0, gsm=1,
target system for outgoing handover ferred fdd=2,
of UEs with PS calls. gsmPreferred=3,
fddPreferred=4 }
targetHOCSPS Defines the allowed and preferred fddPre- enum TargetHO { disable=0, gsm=1,
target system for outgoing handover ferred fdd=2,
of UEs with simultaneous CS and gsmPreferred=3,
PS calls. fddPreferred=4 }
mahoInterActiva- This parameter determines the never enum { automatic=0,

tionPs activation of inter-frequency/ MahoActivation always=1, never=2,
RATMAHO for PS services.always numberOfTargets
- Enable MAHOnever - Disable =3 }
MAHOautomatic - Use
measurement statistics to determine
the numberOfTargets automatically.
Enable MAHO only when the
number of HO candidates exceed a
threshold.
mahoInterActiva- This parameter determines the never enum { automatic=0,

tionCsPs activation of inter-frequency/RAT MahoActivation always=1, never=2,
MAHO for CS+PS services.always numberOfTargets
- Enable MAHOnever - Disable =3 }
MAHOautomatic - Use
measurement statistics to determine
the numberOfTargets automatically.
Enable MAHO only when the
number of HO candidates exceed a
threshold.
mahoInterLayers Determines which macro layers fddgsm enum { fdd=0, gsm=1,
MAHO may be eligible. This MahoLayers fddgsm=2 }
applies to MAHO for inter-freq 3G
and inter-RAT only.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 8-17 HO(BSRProfile-HO/1)
Parameter name Description Default Value Syn- Permitted

Value tax values
mahoInterQualityCon- Inter-freq/RAT MAHO configuration for Set as bool- { True,

figMahoInterCandidate quality-based MAHO. True ean False }
Determines whether inter-frequency/RAT
MAHO is enabled for this scenario
When set as False, it is not activated for
the scenario.
When set as True it becomes a candidate
for MAHO.
mahoInter2d2fEcno Defines 2d2f Ecno for -15 inte- [-24..0]

Threshold2d Inter-frequency/RAT MAHO trigger. ger step=1
It is also the threshold for sending a 2d units=dB
measurement report. If the measured
EcNo value of the used frequency falls
below the value (threshold2d
hysteresis2d/2) for the time
timeToTrigger2d then blind HO is
triggered.
mahoInter2d2fEcno Defines 2d2f Ecno for -15 inte- [-24..0]

Threshold2f Inter-frequency/RAT MAHO trigger. ger step=1
It is also the threshold for sending a 2f units=dB
EcNo value of the used frequency raises
above the value (threshold2f +
hysteresis2f/2) for the time
timeToTrigger2f then HO due to EcNo is
no longer necessary.
mahoInter2d2fRscp Defines 2d2f Rscp for Inter-freq/RAT -110 inte- [-115..-25]
Threshold2d MAHO trigger. ger step=1
The threshold for sending a 2d units=dBm
RSCP value of the used frequency falls
below the value (threshold2d
hysteresis2d/2) for the time
timeToTrigger2d then blind HO is
triggered.
mahoInter2d2fRscp Defines 2d2f Rscp for Inter-freq/RAT -110 inte- [-115..-25]
Threshold2f MAHO trigger. ger step=1
The threshold for sending a 2f units=dBm
RSCP value of the used frequency raises
above the value (threshold2f +
hysteresis2f/2) for the time
timeToTrigger2f then HO due to EcNo is
no longer necessary.
mahoInterQualityFdd- Defines the Ec/No threshold of own cell -16 inte- [-24..0]
OwnEcNo that the MAHO measurement report must ger step=1
be less or equal to before units=dB
inter-frequency/RAT HO is triggered.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Table 8-17 HO(BSRProfile-HO/1) (continued)
Parameter name Description Default Value Syn- Permitted

Value tax values
mahoInterQualityFd- Defines the RSCP threshold of own cell -111 inte- [-115..-25]
dOwnRscp that the MAHO measurement report must ger step=1
be less or equal to before units=dBm
inter-frequency/RAT HO is triggered.

Managed objects in the BSR
Table 8-18 LCell(BSRProfile-LCell/1)

name value
targetHOPS Defines the allowed and disable fddPre- enum { disable=0, gsm=1,
preferred target system for ferred TargetHO fdd=2, gsmPreferred=3,
outgoing handover of UEs with fddPreferred=4 }
PS calls.
targetHOC- Defines the allowed and disable fddPre- enum { disable=0, gsm=1,
SPS preferred target system for ferred TargetHO fdd=2, gsmPreferred=3,
outgoing handover of UEs with fddPreferred=4 }
simultaneous CS and PS calls.
Impacted services
Small Cell must be restarted for activating this feature. All the services are impacted
during this process.
WPS Small Cells No

WMS Small Cells No
HDM No

Small Cell Yes The configuration file is downloaded
to the Small Cell, once it is restarted.
IPC No
IPsec Router No
BPG No
BVG No
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
BSG No
AAA No
System
SCMS Yes

None.
Duration
Downtime
None.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Mobility features 101684 - 3G Macro to Small Cell handover for PS and CS+PS
calls
....................................................................................................................................................................................................................................
101684 - 3G Macro to Small Cell handover for PS and CS+PS

calls
Overview
This feature enables the handover of incoming calls, from a Macro 3G network to the
Small Cell network for the PS domain. It includes handover of UEs with PS only
connections, and handover of UEs with simultaneous CS and PS connections.
Small Cell supports hard handover from Macro 3G to Small Cell, for CS voice calls,
using features, 3G Macro to Small Cell CS handover (75389) and Incoming CS handover
in open access (83083). This feature extends the incoming HO support to the PS domain,
that is, for PS and CS+PS calls. The handover from the Macro 3G network to the Small
Cell is triggered in the macro network.
The handover procedure between the Macro network and the Small Cell network is 3GPP
compliant. The Small Cell target cell selection, uses the same algorithm that is used for
CS calls.
Purpose
This topic describes the activation and deactivation procedure for 3G Macro to Small Cell
handover for PS and CS+PS calls (101684) feature.
Before you begin

Ensure that:
BSR Gateway is operational and FGW class is configured in the WPS Small Cells.
IPC is operational and IPCCLI is accessible.
Log in to the IPC, with the IP address of fms01 or fms02. Execute the following
command to find an active FMS:
[IPC2425:fms01]-> RCCcstat
Result: RCC Cluster [FLXcluster] Status
fms01 2 A - ACTIVE
fms02 3 L - LEAD
[IPC2425:fms01]->
WMS Small Cells and HDM are operational.
Ensure that the SGSN, has SRNS Relocation (UE Involved) enabled.
Ensure that the 3G MSC has SRNS Relocation (UE Involved) enabled.
Ensure that the Macro RNC has SRNS Relocation (UE Involved) of PS and CS+PS
enabled.
....................................................................................................................................................................................................................................
Issue 5 April 2014
calls
....................................................................................................................................................................................................................................
Note: When the feature is enabled at the Small Cell Gateway and IPC, the feature is
activated at the cluster level.
When the feature is enabled in a specific Small Cell, the feature is activated at the
Small Cell level.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Navigate to FGWConfig >BSG set the following attributes:

For a closed access Small Cell - set hoFromUmtsMacroEnabledClosedAccess as
True
For an open access Small Cell - set hoFromUmtsMacroEnabledOpenAccess as
True
psHoFromUmtsMacroEnabled as True
...................................................................................................................................................................................................

...................................................................................................................................................................................................
5 Create a work order and export it to the WMS Small Cells.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
7 Locate the appropriate work order file. Click Add to list and select Launch.
...................................................................................................................................................................................................
8 Once the work order is successfully launched, navigate to and select Activate.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
calls
....................................................................................................................................................................................................................................
shutdownTimer 60
E...................................................................................................................................................................................................
N D O F S T E P S
To configure using IPCCLI

...................................................................................................................................................................................................
1 Log in to the IPC using the IP address.

...................................................................................................................................................................................................
2 Execute the following command from the active FMS:

Result: IPC Software (current) IPC-02.04.01.04 IPCCLI? Menu
----------( IPC CLI Main Menu )----------
2. Fault Management
5. IPC Audits
6. Software Upgrade
Select from menu or (E)xit (H)elp (F)ile?
...................................................................................................................................................................................................

Result: ----------( Object Management )-----------
1. Audit 5. Lock 9. Cancel Test 13.
PowerOn
2. Get Attributes 6. Unlock 10. Create 14.
PowerOff
....................................................................................................................................................................................................................................
Issue 5 April 2014
calls
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
4 Select option 2, for current parameters information. Select option 3, for setting new
values for the parameters.
Result: ----------( Object Selection )----------
SET:name=""
1. LIPC
Select from menu or (Q)uit (H)elp (F)ile?1
Enter instance number (integer):
...................................................................................................................................................................................................
5 Enter 1. Locate attributes macroFemtoHOSupported and macroFemtoPSHOSup-

ported, and set them as True.
E...................................................................................................................................................................................................
N D O F S T E P S


name Value
hoFromUmts- Enables/disables incoming False boolean True { True, False }

MacroEnabled- handover from a UMTS
ClosedAccess source cell to a closed access
Small Cell.
hoFromUmts- Enables/disables incoming False boolean True { True, False }
MacroEnable- handover from a UMTS
dOpenAccess source cell to an open access
Small Cell.
psHoFro- Enables/disables incoming False boolean True { True, False }

mUmtsMacroE- handover from a UMTS Note: This
nabled source cell for PS calls. parameter must
be set, only if,
hoFromUmts-
MacroEnabled-
ClosedAccess or
hoFromUmts-
MacroEnable-
dOpenAccess is
set as True.
....................................................................................................................................................................................................................................
Issue 5 April 2014
calls
....................................................................................................................................................................................................................................

name Value
macroFemto- This attribute controls the False bool- True { True, False }
HOSupported acceptance of SCCP ean
Connection Request, and
RANAP Relocation Request
messages from the MSC. If
this attribute is set as False,
the SCCP Connection
Request from the MSC is
rejected.
macroFemtoP- This attribute controls the False bool- True { True, False }
SHOSupported acceptance of SCCP ean Note: This
Connection Request from the parameter must
SGSN. If this attribute is set be set, only if,
as False, the SCCP macroFemto-
Connection Request from the HOSupported is
SGSN is rejected. set as True.

name Value
hoFromUmts- Enables/disables incoming False bool- True { True, False }

MacroEnabled handover from a UMTS ean
source cell.
psHoFro- Enables/disables incoming False bool- True { True, False }
mUmtsMacroE- handover from a UMTS ean Note: This
nabled source cell for PS calls. parameter must
be set, only if,
hoFromUmts-
MacroEnabled is
set as True.


name Value Values
psHoFro- Enables/disables incoming False boolean False { True, False }

mUmtsMacroE- handover from a UMTS source
nabled cell for PS calls.
....................................................................................................................................................................................................................................
Issue 5 April 2014
calls
....................................................................................................................................................................................................................................

name Value Values
macroFemtoP- This attribute controls the False boolean False { True, False }
SHOSupported acceptance of SCCP
Connection Request from the
SGSN. If this attribute is set as
False the SCCP Connection
Request from the SGSN shall be
rejected.

name Value
psHoFro- Enables/disables incoming False boolean False { True, False }

mUmtsMacroE- handover from a UMTS source
nabled cell for PS calls.
Impacted services
None
WPS Small Cells No

WMS Small Cells Yes
HDM No
Small Cell Yes
IPC Yes
IPsec Router No
BSR Gateway Yes
AAA No
SCMS No

The 3G Macro to Small Cell PS handover procedure relies on the SRNS Relocation of PS
Service supported by the macro core network and RNC.
....................................................................................................................................................................................................................................
Issue 5 April 2014
calls
....................................................................................................................................................................................................................................
SRNS Relocation Info RRC containers are supported up to Release 7.
Duration
N/A
Downtime
None
....................................................................................................................................................................................................................................
Issue 5 April 2014
Mobility features 172248 - Release PS during SIM bearer (CS+PS) handover
....................................................................................................................................................................................................................................
172248 - Release PS during SIM bearer (CS+PS) handover

Overview
This feature enables the release of the PS component during a CS+PS handover. Previous
to this feature, PS handover could be enabled or disabled. When PS handover was
enabled, it applied to both PS and simultaneous CS+PS (SIM-bearer) calls.
This feature facilitates separating out handling of PS from SIM-bearer calls so that one
can enable PS-only handover, but retain the ability to handover only the CS part of
SIM-bearer calls while releasing the PS part of the call.
This feature enables disabling SIM-bearer handover without disabling all PS handovers
The CS handover is not impacted by the PS component (for example, due to time-outs of
the relocation for the PS).
Purpose
This topic describes the activation and deactivation procedures for Release PS during
SIM Bearer (CS+PS) handover (172248) feature.
Before you begin

operational.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to Network > profile > BSRProfile . Set attribute sparePara31 as

SimIuHo=3gsc;PsHoBlkTm= <0..99>.
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S

Table 8-19 BSR::sparepara31
Parameter Description Syntax Default Permitted values Values

name value
SimIuHo When a UE has string all {3gsc, all} 3gsc

simultaneous Iu connections 3gsc - simultaneous Iu
established and outgoing handover is not supported to 3G
handover is to be performed, macro cells but is supported to
the attribute SimIuHo 3G Small Cells.
determines if the handover
is supported for both of the all - simultaneous Iu handover
established Iu connections, is supported to 3G macro cells
or whether one Iu and 3G Small Cells.
connection (and RABs if
applicable) is released prior
to performing the handover
of a single Iu connection.
PsHoBlkTm After successfully seconds {0..99}

completing an incoming
handover of a UE with only
a CS connection, a timer is
started for duration set in
PsHoBlkTm. The
establishment of a new
signaling connection
towards the PS core network
is prevented for that
duration.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Navigate to Network > profile > BSRProfile . Set attribute sparePara31 as

SimIuHo=all;PsHoBlkTm=0.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S

Table 8-20 BSR::sparepara 31
Parameter Description Syntax Default Permitted values Values

name value
SimIuHo When a UE has string all {3gsc, all} all

simultaneous Iu connections 3gsc - simultaneous Iu
established and outgoing handover is not supported to 3G
handover is to be performed, macro cells but is supported to
the attribute SimIuHo 3G Small Cells.
determines if the handover is
supported for both of the all - simultaneous Iu handover
established Iu connections, is supported to 3G macro cells
or whether one Iu and 3G Small Cells.
connection (and RABs if
applicable) is released prior
to performing the handover
of a single Iu connection.
PsHoBlkTm After successfully seconds {0..99} 0

completing an incoming
handover of a UE with only
a CS connection, a timer is
started for duration set in
PsHoBlkTm. The
establishment of a new
signaling connection
towards the PS core network
is prevented for that
duration.
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
Impacted services
The Small Cell requires to be restarted, hence there is an outage during that period.
WPS Small Cells Yes
WMS Small Cells Yes

HDM Yes

Small Cell Yes The Small Cell requires to be
restarted
IPC No
IPsec Router No
BPG No
BVG No
BSG No
AAA No

System

None
Duration
NA
Downtime
The Small Cell requires to be restarted, hence there is an outage during that period.
....................................................................................................................................................................................................................................
Issue 5 April 2014
9 9 ommon Configuration
C
Procedures
Overview
Purpose
This chapter describes the common configuration procedures used in feature
activation/deactivation.
Contents
IPC configuration with WPS Small Cells 9-2

BSG configuration with WPS Small Cells 9-6
Small Cell attributes configuration with WPS Small Cells 9-8
...................................................................................................................................................................................................................................
Issue 5 April 2014
Common Configuration Procedures IPC configuration with WPS Small Cells
....................................................................................................................................................................................................................................
IPC configuration with WPS Small Cells

Purpose
This topic describes the procedure to configure IPC with WPS Small Cells.
Database creation for IPC using WPS Small Cells for dayone-cli
...................................................................................................................................................................................................
1 Log in to the IPC FMS blade (FMS01 or FMS02) as a root user.

...................................................................................................................................................................................................
2 Change path to /flx/RNCinitdb/current/bin directory, and execute the following script in

the FMSblade.
./datablitz_meosDump.ksh
...................................................................................................................................................................................................
3 On successful execution of the script, a db_walk.dump file is created in the IPC

(/flx/RNCinitdb/current/bin).
...................................................................................................................................................................................................
4 Copy the db_walk.dump file to your desktop.

E...................................................................................................................................................................................................
N D O F S T E P S
Importing IPC db_walk.dump file to WPS Small Cells

...................................................................................................................................................................................................

...................................................................................................................................................................................................
2 Navigate to Object Creation: create, select IPC[OAMOAM]. Enter a value for userLabel.
...................................................................................................................................................................................................
3 Create the IPC object.

...................................................................................................................................................................................................
4 The IPC object created, is shown on the left pane. To edit the IPC object, select the Object
type and the instance and Create. Object created is the MIM version of the IPC
(eg-:[LIPC_04_00_00/IPC]).
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
5 Select the LIPC MO and Overview on the right side. Now Load IPC snapshot file to load
the db_walk.dump to WPS Small Cells.
...................................................................................................................................................................................................
6 A new pop-up window opens, Browse to locate the db_walk.dump file on your desktop.
...................................................................................................................................................................................................
7 A report of the Load IPC snapshot file operation is generated. The warnings and errors in
the report, are mismatches between the MIM loaded to WPS Small Cells and the current
IPC MIM.
...................................................................................................................................................................................................
8 Following examples can be referred for using the WPS Small Cells:
1. Updating iPCId attribute of LIPC MO
Select LIPC on the left pane, and Edition, select iPCId attribute and provide a value.
2. Creating GICCIpInterface MO
Select LIPC MO on the left pane, select Edition on the right side. For Object
creation, select GICCIPInterface in the drop-down list. Enter a value for idand
Create. A GICCIpInterface object is created and appears in the left side under LIPC
MO.
...................................................................................................................................................................................................
9 Right click MO on the left side and perform Run checks... to check for consistency in the
IPC configuration.
E...................................................................................................................................................................................................
N D O F S T E P S
Generating the IPC CLI file and reverse using current workorder
Once the WPS Small Cells checks are successful, perform the following steps:
...................................................................................................................................................................................................
1 Select Generate IPC CLI file and reverse using current workorder on the right pane.
Browse to select a location to save the cli file.
...................................................................................................................................................................................................
2 Now transfer the LIPC1.cli file to IPC and place it in the /flx/RNCinitdb/current/bin
directory.
...................................................................................................................................................................................................
3 In the command prompt navigate to /flx/RNCinitdb/current/bin directory and execute the

following script:
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
./meosCli s filename (where filename is LIPC1.cli).
...................................................................................................................................................................................................
4 Once the script is executed successfully, execute the following command, to verify if the
database was updated appropriately and all the 17 servers are functioning properly:
[IPC 24:fms01]-> rnccheckservers
Example:

=================================================================
AVAIL LogMgrInstance.1 OAMLogMgrCapsule
fms02 ACT
AVAIL OAMAlarmMgr.1 OAMAlarmMgrCapsule
fms02 ACT
AVAIL OAMBUMgr.1 OAMBUMgrCapsule
fms02 ACT
AVAIL OAMDataAuditServer.2 OAMDataAuditServerCapsule
fms01 ACT
AVAIL OAMEATranslator.2 OAMEATranslatorCapsule
fms01 ACT
AVAIL OAMFMSTranslator.2 OAMFMSTranslatorCapsule
fms01 ACT
AVAIL OAMInterfaceRAgent.1 OAMInterfaceRCapsule
fms02 ACT
AVAIL OAMLMTGwServer.1 OAMLMTGwCapsule
fms02 ACT
AVAIL OAMMEOServer.2 OAMMEOServerCapsule
fms01 ACT
AVAIL OAMOAMSchedulerServer.2 OAMOAMSchedulerServerCapsule
fms01 ACT
AVAIL OAMOFManager.2 OAMOFManagerCapsule
fms01 ACT
AVAIL OAMPMServer.1 OAMPerfMgrCapsule
fms02 ACT
AVAIL OAMShelfTranslator.1 OAMShelfTranslatorCapsule
fms02 ACT
AVAIL OAMSignalTranslator.2 OAMSignalTranslatorCapsule
fms02 ACT
AVAIL OAMSIHBServer.1 OAMAlarmMgrCapsule
fms02 ACT
AVAIL OAMSUMgr.1 OAMSUMgrCapsule
fms02 ACT
AVAIL OAMSysCoordServer.1 OAMSysCoordServerCapsule
fms02 ACT

OFFLINE: 0
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
[IPC 24:fms01]->
Note: The IPC must be reset, whenever a user updates any RW-RR attribute with WPS
Small Cells and the updated value is uploaded in the IPC.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
Common Configuration Procedures BSG configuration with WPS Small Cells
....................................................................................................................................................................................................................................
BSG configuration with WPS Small Cells

Purpose
This topic describes the procedure to configure BSG with WPS Small Cells.
Importing the BSG BulkCM.xml file to WPS Small Cells

...................................................................................................................................................................................................

...................................................................................................................................................................................................
2 Navigate to Network > FGW (OAM object) on the left pane. Now, Import bulkcm file in
the Edition > Operations section on the right pane, to import the OAM_PreConfig file.
...................................................................................................................................................................................................
3 In the Operations: Import bulkcm file window, select the OAM_Preconfig.xml file.
...................................................................................................................................................................................................
4 WPS Small Cells runs the mediation BulkCM2CMXM process. In Network, the initial
snapshot is replaced by the mediated data loaded by WPS Small Cells under FGW Config.
...................................................................................................................................................................................................
5 Now, the FGW Config can be modified in WPS Small Cells.

E...................................................................................................................................................................................................
N D O F S T E P S
Example to describe creation of one IuCS MO class in WPS Small Cells

The following steps are to be performed:
...................................................................................................................................................................................................
1 Select FGWConfig/56090 1 under FGW/911.

...................................................................................................................................................................................................
2 In the Object Creation: create drop-down menu, select IuCS. And provide a value for id
and Create.
...................................................................................................................................................................................................
3 IuCS MO is created under FGWConfig/560901.
....................................................................................................................................................................................................................................
Issue 5 April 2014
Common Configuration Procedures BSG configuration with WPS Small Cells
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
4 Set the desired values for attributes.

E...................................................................................................................................................................................................
N D O F S T E P S
Generating the BSG CLI batch file

Once the WPS Small Cells checks are successful, perform the following steps:
...................................................................................................................................................................................................
1 Generate CLI batch file from the Operations section on the right pane. Browse, to select
a destination to save the file and select Generate reversed CLI file.
...................................................................................................................................................................................................
2 WPS Small Cells executes the generation of CMXML to CLI command and its reverse
with current data.
...................................................................................................................................................................................................
3 The CLI file is generated at the previously mentioned destination folder. Transfer the
generated CLI batch file into /opt/conf directory of BSG.
E...................................................................................................................................................................................................
N D O F S T E P S
Manually creating FGWConfig in BSG with WPS Small Cells

...................................................................................................................................................................................................
1 Navigate to Network > FGW/911 and select FGWConfig in the Object Creation: create
drop-down list and Create.
...................................................................................................................................................................................................
2 Enter values for all the mandatory attributes. Navigate to Network > FGW/11 and select
Overview on the right pane.
...................................................................................................................................................................................................
3 Select Generate CLI batch file, to generate a batch file.

...................................................................................................................................................................................................
4 Import the batch file to BSG and execute.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
Common Configuration Procedures Small Cell attributes configuration with WPS Small Cells
....................................................................................................................................................................................................................................
Small Cell attributes configuration with WPS Small Cells

Purpose
This topic describes the procedure to configure the Small Cell attributes with WPS Small
Cells.
To configure a Small Cell Cluster profile (bsrclusterprofile) attribute

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Modify bsrclusterprofile to the desired value.

...................................................................................................................................................................................................
4 Perform Run Checks ... on the network.

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
To configure the Small Cell pre-provisioning (bsrpreprovision) attributes

...................................................................................................................................................................................................
1 Export the latest snapshot from WMS Small Cells
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Modify bsrpreprovision to the desired value.

...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
To configure a Small Cell profile (bsrprofile) attribute

...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Modify bsrprofile to the desired value.

...................................................................................................................................................................................................

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
7 Once the work order is successful, navigate to HNM > Devices > Manage Femto > Queue
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 5 April 2014
Glossary
...................................................................................................................................................................................................................................
Numerics
3GPP
Third Generation Partnership Project
...................................................................................................................................................................................................................................
A AMR
Adaptive Multi-Rate
...................................................................................................................................................................................................................................
B BCR
BSR Cluster Release
BSG
Base Station Gateway
BSR
Base Station Router
...................................................................................................................................................................................................................................
C CHAP
Challenge Handshake Authentication Protocol
CINR
Carrier to Interference-plus-Noise Ratio
CN
Core Network
CS
Circuit Switched
CSN
Chip Serial Number
...................................................................................................................................................................................................................................
D DHCP
Dynamic Host Configuration Protocol
....................................................................................................................................................................................................................................
Alcatel-Lucent SC Alcatel-Lucent Proprietary GL-1
Issue 5 April 2014
Glossary
....................................................................................................................................................................................................................................
DSL
Digital Subscriber Line
...................................................................................................................................................................................................................................
E E-DCH
Enhanced Dedicated Channel
...................................................................................................................................................................................................................................
F FSN
Femto Serial Number
...................................................................................................................................................................................................................................
H HLR
Home Location Register
HNLR
Home Network Local Routing
HSDPA
High-Speed Downlink Packet Access
...................................................................................................................................................................................................................................
I IDNNS
Intra Domain NAS Node Selector
IMEI
International Mobile Equipment Identifier
IMSI
International Mobile Subscriber Identity
IP
Internet Protocol
IuCS
Interface between the MSC and RNS
IuPS
Interface between SGSN and RNS
...................................................................................................................................................................................................................................
L LA
Location Area
LAC
Location Area Code
....................................................................................................................................................................................................................................
GL-2 Alcatel-Lucent Proprietary Alcatel-Lucent SC
Issue 5 April 2014
Glossary
....................................................................................................................................................................................................................................
LAI
Location Area Identity
...................................................................................................................................................................................................................................
M MSC
Mobile Switching Center
...................................................................................................................................................................................................................................
N NAS
Non-Access Stratum
NNSF
NAS Node Selection Function
NRI
Network Resource Identifier
...................................................................................................................................................................................................................................
P P-TMSI
Packet Temporary Mobile Subscriber Identity
PAP
Password Authentication Protocol
PLMN
Public Land Mobile Network
PPPoE
Point-to-Point Protocol over Ethernet
PS
Packet Switched
...................................................................................................................................................................................................................................
Q QAM
Quadrature Amplitude Modulation
QoS
Quality of service
...................................................................................................................................................................................................................................
R RA
Routing Area
RAC
Routing Area Code
....................................................................................................................................................................................................................................
Issue 5 April 2014
Glossary
....................................................................................................................................................................................................................................
RAI
Routing Area Identifier
RAN
Radio Access Network
RANAP
Radio Access Network Application Part
RNC
Radio Network Controller
RSCP
Received Signal Code Power
RTCP
Real-Time Transport Control Protocol
RTP
Real-time Transport Protocol
...................................................................................................................................................................................................................................
S SAC
Service Area Code
SCTP
Stream Control Transmission Protocol
SeGW
Security Gateway
SGMS
Security Gateway Management System
SGSN
Serving GPRS Support Node
SRB
Signaling Radio Bearer
...................................................................................................................................................................................................................................
T TEP
Tunnel End Point
TMSI
Temporary Mobile Station Identity
....................................................................................................................................................................................................................................
Issue 5 April 2014
Glossary
....................................................................................................................................................................................................................................
TS
Technical Specification
TTI
Transmission Time Interval
...................................................................................................................................................................................................................................
U UDP
User Datagram Protocol
UE
User Equipment
UL
Uplink
UMTS
Universal Mobile Telecommunication System
...................................................................................................................................................................................................................................
V VLR
Visitor Location Register
...................................................................................................................................................................................................................................
W W-CDMA
Wideband Code Division Multiple Access
....................................................................................................................................................................................................................................
Issue 5 April 2014
Glossary
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 5 April 2014
Index
Numerics Coordinated self optimization in groups, 7-57

2 ms TTI on E-DCH, 3-73 Coverage self-optimization based on admission, 7-32
2G, 7-2 ................................................................................................
32 PS user capacity for V2 Enterprise and Metro AP,
D DHCP, 5-21
4-121
Direct tunnel, 3-2
3G Macro to Small Cell handover for PS and CS+PS
calls, 8-24 DNS
3GPP, 3-2 Domain Name Server, 4-59
64QAM for HSDPA, 7-28 document support, xxiv
................................................................................................ DPDK support on BSR Gateway, 4-130
A AAA, 4-28 ................................................................................................
ACL extension for large Small Cell Groups, 6-18 E Extended range cell, 6-25
Active-Warm standby BSR Gateway redundancy, 4-72 ................................................................................................
AMR frame concatenation with preemption, 4-110 F Feature number

ANSI, 3-5 100854, 6-12
Assisted GPS using proprietary TCS solution, 4-98 100856, 8-2
ATM, 1-7, 3-5 100857, 8-6
Automatic carrier selection, 7-16 100888, 8-19
................................................................................................ 101373, 6-6
B BSG, 9-6 101681, 6-2
................................................................................................ 101684, 8-24
C Cell broadcast services in support of CMAS, 4-124 104503, 3-5
Cell change order, 8-15 104564, 4-6
Certificate-based authentication and security for V2 HW, 107284, 1-7

2-14 108877, 7-32
Change of Service Area Location Reporting, 7-52 109515, 4-17
....................................................................................................................................................................................................................................
Alcatel-Lucent SC Alcatel-Lucent Proprietary IN-1
Issue 5 April 2014
Index
....................................................................................................................................................................................................................................
111039, 6-25 75397, 1-2
113610, 4-14 75399, 5-11
114014, 4-72 75545, 4-3
114174, 7-38 76974, 5-16
114366, 2-5 76985, 7-16
114380, 5-21 76986, 4-124
114578, 4-38 77713, 3-66
114997, 7-6 78229, 7-2
116495, 7-23 78241, 3-2
116496, 7-28 78243, 2-2
116498, 7-44 78594, 4-82
117813, 4-68 83021, 5-2
117826, 4-133 83062, 4-22
119109, 4-65 83086, 2-14
119110, 4-90 83087, 4-47
119860, 7-13 83241, 4-28
119911, 4-98 83249, 4-36
120353, 4-79 84181, 4-41
120359, 4-62 84791, 3-70
121317, 2-10 84990, 4-55
122468, 3-78 89552, 5-25
123830, 4-105 92068, 6-18
124168, 4-130 96373, 4-59
125544, 4-110 FM, 4-22
131828, 3-73 ................................................................................................
155820, 2-17 H HDM alarm management in WMS Small Cells for Small
157214, 4-94 Cell, 4-62
158467, 4-121 ................................................................................................
170695, 7-52 I Inter-frequency Small Cell to 3G Macro handover for PS

and CS+PS calls, 8-19
170891, 7-48
internet breakout at CPE, 4-17
171355, 7-57
Intra-frequency Small Cell to 3G Macro MAHO for CS
172248, 8-31
calls, 8-2
75386, 8-15
Intra-frequency Small Cell to 3G Macro MAHO for PS
75387, 8-10 and CS+PS calls, 8-6
....................................................................................................................................................................................................................................
IN-2 Alcatel-Lucent Proprietary Alcatel-Lucent SC
Issue 5 April 2014
Index
....................................................................................................................................................................................................................................
IP RTCP, 4-79
Internet Protocol, 1-7 RTCP for IuCSoIP, 4-79
IPC, 1-48, 9-2 ................................................................................................
IPCCLi, 1-50 S SAM, 4-38

IuFlex, 1-7 Satellite backhaul, 3-78
IuCS and IuPS, 1-2 Feature acceptance criteria, 3-78
................................................................................................ SCMS support of GPS, 4-6
L LKDI Security, 2-2
License Key Delivery Infrastructure, 4-68 SGSN, 3-66, 4-41
................................................................................................ GGSN, 3-2
M MCC Small Cell, 9-8
Mobile Country Code, 7-6 Small Cell Access Point capacity licensing, 4-68
Meinberg NTP integration, 4-65 Small Cells network support for End-to-End call
subscriber trace, 4-82
MGW, 4-41
Static IP address, 4-90
Multi-objectives joint coverage optimization, 7-44
................................................................................................
Multiple Operator Core Network, 4-133
T Tamper Alarm, 2-10
................................................................................................
ToD
N Neighbor list optimization based on UE measurements
and mobility reports, 7-48 Time of Day, 4-59
NLL ................................................................................................
National Location Lock, 7-6 U UE assisted Small Cell to Macro handover, 8-10
NTP, 4-22 UE based AGPS, 4-105

................................................................................................ UL interferences management based on Tx power
update, 7-23
O Optimized paging for large Metro cells deployments,
6-12 UMTS Small Cell to LTE cell reselection, 7-38
................................................................................................ ................................................................................................
P PDP, 3-66 W WLM
phone numbers Wireless License Management, 4-68
for document support, xxiv WPS Small Cells, 1-48, 9-2, 9-6, 9-8
PPPoE configuration, 4-94

Presence API, 5-2
................................................................................................
R Release PS during Sim Bearer (CS+PS) handover, 8-31
....................................................................................................................................................................................................................................
Alcatel-Lucent SC Alcatel-Lucent Proprietary IN-3
Issue 5 April 2014
Index
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
IN-4 Alcatel-Lucent Proprietary Alcatel-Lucent SC
Issue 5 April 2014

9YZ056140014PGZZA - V1 - Alcatel-Lucent Small Cell Feature Activation Procedures

Enviado por

Dados do documento

Título original

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

9YZ056140014PGZZA - V1 - Alcatel-Lucent Small Cell Feature Activation Procedures

Enviado por

Direitos autorais:

Formatos disponíveis

Use pursuant to applicable agreements

About this document

Reason for reissue ...................................................................................................................................................................... xxi

New in this release ..................................................................................................................................................................... xxi

Other changes ............................................................................................................................................................................. xxii

Intended audience ..................................................................................................................................................................... xxii

Supported systems .................................................................................................................................................................... xxii

How to use this document ..................................................................................................................................................... xxii

Conventions used .................................................................................................................................................................... xxiii

Related information ................................................................................................................................................................ xxiii

Document support ................................................................................................................................................................... xxiv

Technical support ...................................................................................................................................................................... xxv

How to order ............................................................................................................................................................................... xxv

How to comment ....................................................................................................................................................................... xxv

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

75397 - IuFlex for IuCS and IuPS ...................................................................................................................................... 1-2

107284 - IuFlex over ATM .................................................................................................................................................... 1-7

Creating IPC objects with WPS Small Cells ................................................................................................................ 1-48

Overview ...................................................................................................................................................................................... 2-1

78243 - Security hardening of the BSG ............................................................................................................................ 2-2

121317 - Tamper Alarm ....................................................................................................................................................... 2-10

83086 - Certificate-based authentication and security for V2 HW ...................................................................... 2-14

Overview ...................................................................................................................................................................................... 3-1

78241 - Direct tunnel ............................................................................................................................................................... 3-2

104503 - Dual stack (ANSI/ETSI) on ATM/IP .............................................................................................................. 3-5

77713 - PDP shutdown of data session .......................................................................................................................... 3-66

84791 - Real-time monitoring of backhaul bandwidth ............................................................................................. 3-70

131828 - 2 ms TTI on E-DCH ........................................................................................................................................... 3-73

122468 - Satellite backhaul ................................................................................................................................................ 3-78

4 Small Cell specific features

Overview ...................................................................................................................................................................................... 4-1

75545 - GPS localization ....................................................................................................................................................... 4-3

104564 - SCMS support of GPS localization locking ................................................................................................. 4-6

113610 - Support for assisted GPS .................................................................................................................................. 4-14

109515 - Internet breakout at CPE ................................................................................................................................... 4-17

83062 - Fault Management support of NTP server .................................................................................................... 4-22

83241 - Fault Management support of AAA ................................................................................................................ 4-28

83249 - Launch point to AAA and NTP server ........................................................................................................... 4-36

114578 - SCMS 2.4 support of SAM 7.0 ...................................................................................................................... 4-38

84181 - All-in-one BSR Gateway .................................................................................................................................... 4-41

83087 - Distributed SS7 ..................................................................................................................................................... 4-47

84990 - SCMS support of BSR Gateway ...................................................................................................................... 4-55

96373 - FM support for DNS/ToD functions ............................................................................................................... 4-59

119109 - Meinberg NTP integration ................................................................................................................................ 4-65

117813 - Small Cell Access Point capacity licensing ............................................................................................... 4-68

114014 - Active-Warm standby BSR Gateway redundancy ................................................................................... 4-72

120353 - RTCP for IuCSoIP ............................................................................................................................................... 4-79

119110 - Static IP address ................................................................................................................................................... 4-90

157214 - PPPoE configuration .......................................................................................................................................... 4-94

119911 - Assisted GPS using proprietary TCS solution ........................................................................................... 4-98

123830 - UE-based Assisted GPS .................................................................................................................................. 4-105

125544 - AMR frame concatenation with preemption ........................................................................................... 4-110

158467 - 32 PS user capacity for V2 Enterprise and Metro AP ......................................................................... 4-121

76986 - Cell broadcast services in support of CMAS ............................................................................................ 4-124

124168 - DPDK support on BSR Gateway ................................................................................................................ 4-130

117826 - Multiple Operator Core Network ................................................................................................................ 4-133

Overview ...................................................................................................................................................................................... 5-1

83021 - Presence API .............................................................................................................................................................. 5-2

75399 - Home network local routing .............................................................................................................................. 5-11

76974 - Enhanced PM processing for BSG counters ................................................................................................ 5-16

114380 - DHCP options (60, 125, 43) ............................................................................................................................ 5-21

89552 - Network overload avoidance ............................................................................................................................. 5-25

6 Metro Small Cells features