Академический Документы
Профессиональный Документы
Культура Документы
SAFETY WARNING
Alcatel-Lucent training materials can be for products or refer to products that have both lethal and dangerous voltages
present. Always observe all safety precautions and do not work on the equipment alone. The user is strongly advised not
to wear conductive jewelry while working on the products. Equipment referred to or used during this course may be
electrostatic sensitive. Please observe correct anti-static precautions.
DISCLAIMER
ALCATEL-LUCENT DISCLAIMS ALL WARRANTIES REGARDING THE TRAINING COURSES OR THE CONTENT, EXPRESS OR IMPLIED,
INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. THE ALCATEL-LUCENT WILL NOT BE RESPONSIBLE OR LIABLE FOR ANY INJURY, LOSS, CLAIM, DAMAGE, OR ANY
SPECIAL, EXEMPLARY, PUNITIVE, INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING WITHOUT
LIMITATION LOSS PROFITS OR LOSS SAVINGS), WHETHER BASED IN CONTRACT, TORT, STRICT LIABILITY OR OTHERWISE, THAT
ARISES OUT OF OR IS IN ANY WAY CONNECTED WITH (A) ANY USE OR MISUSE OF THE CONTENT OR THE TRAINING COURSES
BY YOU, OR (B) ANY FAILURE OR DELAY BY ALCATEL-LUCENT, ITS OFFICERS, DIRECTORS, AGENTS OR EMPLOYEES IN
CONNECTION WITH THE CONTENT OR THE TRAINING COURSES (INCLUDING, WITHOUT LIMITATION, THE USE OF OR INABILITY
TO USE ANY COMPONENT OF THE CONTENT OR TRAINING BY YOU). SOME JURISDICTIONS LIMIT OR PROHIBIT SUCH
EXCLUSION OF WARRANTIES OR LIMITATION OF LIABILITIES AND SO THE FOREGOING EXCLUSION OF WARRANTIES OR
LIMITATION OF LIABILITY MAY NOT APPLY TO YOU.
GOVERNING LAW
These Terms of Use and Legal Notice are governed by the laws of France. The operation and use of the training course is
governed by the laws of the country that governs your employment contract, if applicable. If any provision of these Terms
of Use and Legal Notice, or the application thereto to a person or circumstance, is held invalid or unenforceable by law,
statute or a court of competent jurisdiction, for any reason, then such provision shall be modified and/or superseded by a
provision that reflects the intent of the original provision as closely as possible. All other provisions of these Terms of Use
and Legal Notice shall remain in full force and effect. You may not assign these Terms of Use or any permission granted
hereunder without Alcatel-Lucents prior written consent. Nothing herein shall be deemed an employment agreement or
an offer of employment or an alteration in any way of a users terms of employment with or within Alcatel-Lucent.
Copyright 2013 Alcatel-Lucent. All Rights Reserved
training.feedback@alcatel-lucent.com
Thank you!
Document History
1 Course introduction 7
1.1 Small Cell Solution course curriculum 8
1.2 Before we start 10
1.3 How to use LiveMeeting 11
1.4 Our expectations 12
1.5 Who we are 13
1.6 Ice breaker 14
1.7 Objectives 16
2 Small Cell Management overview 17
2.1 The challenges 18
2.2 Network architecture 19
2.3 MOCN with shared spectrum 20
2.4 W-CDMA + Small Cell 21
2.5 Motive Home Device Manager 22
2.6 WPS Small Cells 23
2.7 WMS Small Cells 24
3 Small Cell Management functions, architecture and hardware 27
3.1 Small Cell Management System Upgrade to BCR4.3 28
3.2 Compatibility matrix 29
3.3 Small Cell Management architecture 31
3.4 Small Cell Management detailed architecture 32
3.5 Small Cell Management North Bound interfaces 33
3.6 Small Cell Management hardware 34
3.7 Small Cell Management - small server solution 35
3.8 Support of new HDM hardware 36
4 OAM in Small Cell Management 40
4.1 OAM support overview 41
4.2 Small Cell Management 42
4.3 Support of the BSR Gateway 43
4.3.1 WPS support of BSR Gateway 45
4.3.2 BSR GW software management and inventory 46
4.3.3 Fault management of BSR Gateway in WMS 47
4.4 WPS configuration management of IPC 49
4.5 Performance management 50
The number of managed devices is orders of magnitude larger which means that the frequency of interaction
between the device and the management server needs to go down. The frequency of interaction needs to
be controllable from the management application and the communication pattern needs to be robust
against communication failures.
Wireless base stations have large associated data models. The same level of detail for Small Cells cannot
be maintained because the increased number of devices. In addition, a large part of the configuration is
quasi-static. Small Cell devices work with a mixed TR-069 model that consists of
Parameters that are manageable automatically
Parameters that are grouped into profiles.
A Small Cell network is an UMTS network requiring constant tuning. The Small Cell must be as
autonomous as possible introduction of network listening and Self-Optimization.
Multiple core network operators can share SC access network based on the network sharing agreement
between them.
MOCN is a solution where two (or more) operators share some common RAN in certain areas or even in the
whole network but do not share their core networks. Until BCR 4.3, SC Solution was capable of supporting
connection to only one operator core network nodes based on one operator, one RAN principle.
The implementation of MOCN allows multiple core network operators to share SC Solution and its NEs (SC,
BSR GW, SCMS) in a shared area based on UTRAN network sharing principles. One specific CN operator
may also have several pooled MSCs/SGSNs connected to the SC Solution and this functionality will be
supported in combination of Iu-flex function already available in SC NEs.
For supporting UEs, SC/BSR GW routes to one CN based on UE selection, while for non-supporting UEs,
SC/BSRGW routes to one CN. If rejected by 1st CN, rerouting done on 2nd CN
There are many RAN sharing scenarios possible depending on MOCN operator strategies, rules &
legislation in different countries. Some of the examples are:
Operator without an UMTS license can share other operator RAN network and provide 3G services to
its customers
A geographically split network, where cooperating operators can cover different parts of a country
Infrastructure sharing, where same RAN can provide service to many operators, thus avoiding the
necessity of deploying RAN per operator.
Problem diagnosis and troubleshooting using policy-based automation of device management and
automated management or monitoring thru the use of Dynamic variables and Policy engine:
Event-triggered policy for TR-069 and system events
Instant-triggered policy
Support for organizational department through Operator roles and rights device and function dependent.
Taking into account the global picture, where there are ADSL, W-CDMA and Small Cell worlds, the Small Cell
Management takes the best assets from:
ADSL OAM solution (with HDM) and
W-CDMA solution (with WMS).
WPS for Small Cell Wireless Provisioning System
Planning of templates
Editing, auditing, checking
WMS for Small Cell - Wireless Management Solution
RF algorithm, synchronization with Macro layer
Auto-Config: Mediation HDM <-> WMS Small Cells and auto-configuration algorithm
Templates, software, temporary bulk CM
PM files storage
HDM Home Device Manager
Small Cell management: configuration, software, upgrade, status
The Operation and Maintenance (OAM) for the Small Cell Solution, is carried out by the Small Cell
Management that consists of three parts:
Motive Home Device Manager (HDM)
9353 Wireless Management System (WMS) Small Cells
optional 9952 Wireless Provisioning System (WPS).
The Motive HDM is a standard web application that uses the following servers in full configuration:
The Presentation and application tier are hosted by a Oracle Sparc T4-1.
The Database tier is hosted by a Oracle Enterprise M4000 with Sun StorageTek ST2540 disk array.
For the 9353 WMS Small Cells that is mainly a Java application an Oracle Netra T5440 is used!
For trials, test beds and small network deployment scenarios, the WMS for Small Cell is hosted on an
Oracle T5220.
The optional 9952 WPS Small Cells is a software that can be installed on any laptop or PC complying with
the minimum hardware requirements.
For a small server configuration the Oracle Sparc T4-1 is used for HDM and WMS each.
WPS Small Cells allows also to configure the BSR Gateway by using the large set of WPS basic
configuration capabilities. WPS provides conversion mechanism between WMS/WPS CM XML data model
format and CLI/BulkCM format supported by the BSR Gateway.
Performance Counter Collection compliant to 3GPP R6 Standard TS32.435 with 15-minute granularity.
In previous release WPS support of BSR GW is limited to CLI parameters. This new feature (83247)
provides full configuration support of BSR GW including CLI parameters and Bulk CM parameters.
To beneficiate from the WPS basic toolset for the BSR Gateway configuration (tabular editor, CM XML
import/export, workorder synchronization, configuration audit, copy/paste, template management, model
check), WPS supports the CM XML Model of the BSR GW.
In addition, to ensure the consistency of the BSR Gateway configuration, WPS implements a set of
enhanced checks related to the BSR GW and its interfaces.
WPS Small Cells allows also to configure the BSR Gateway by using the large set of WPS basic
configuration capabilities. WPS provides conversion mechanism between WMS/WPS CM XML data model
format and CLI/BulkCM format supported by the BSR Gateway.
In previous release WPS support of BSR GW is limited to CLI parameters. This new feature (83247)
provides full configuration support of BSR GW including CLI parameters and Bulk CM parameters.
WPS will support
Pre-provision BSR GW (i.e.) generate and deploy BSR GW initial configuration from a predefined WPS
template.
BulkCM attributes/objects configuration of a BSR GW using WPS
CLI attributes/objects configuration of a BSR GW using WPS.
Model Consistency Checks
WPS basic functionalities with respect to BSR GW (Copy, paste, templates, Clone Workorders, etc)
full support of the CM functions for BSR GW using SNMP.
Fault Management of the BSR Gateway including Small Cell Management toolset - Alarm Browser,
Resources Browsers, 9 alarm rule-set (inhibit, send SMS, send email, change severity, etc), Trouble
Ticketing, Managed/Un-managed alarm stream, HFB (Historical Fault Browser), Audible alarm, 3GPP R6
FM IRP (Integration Reference Point).
In addition to 3GPP R6 support, this new BCR4.0 feature brings in following enhancements with respect to
SmallCell Itf-NDN for alarms forwarded from Small Cell MS to OSS
Itf-NDN reflects the CM containment hierarchy unlike Small Cell MS3.0 where only the Cluster DN is
used.
Flexibility for operators to configure the Small Cell identifier used in Itf-NDN. Following SmallCell
identifiers are supported
femtoid (SmallCell identifier used in WMS)
OUI-FSN (SmallCell manufacturer OUI + serial number)
bsrName (value of bsrName attribute of the SmallCell)
bsrName + OUI-FSN
Sample DN:
Root=3G,SubNetwork=<roc>,SubNetwork=UTRAN,SubNetwork=FemtoCluster<femtoClusterID>,[SubNetw
ork=FemtoGroup<femtoGroupID>],ManagedElement=Femto<selected identifier>
PM allows you to collect, store and transfer PM data from the NEs. Small Cell Management retrieves the
data from the NE using SFTP. The performance data is then pulled from Small Cell Management by the PM
post-processing tool over FTP.
The PM function provides a remote retrieval system for PM data related to the normal operations of the BSR
Gateway. This data is collected and stored on the NE for a specified amount of time and retrieved at periodic
intervals by the Small Cell Management.
PM files are in 3GPP format. The Small Cell Management does not perform any action on the data collected.
It stores this data and makes it available to an upstream network analysis system for compilation with
performance data from other NEs.
The access network PM applications are in charge of the following actions:
uploading the raw data from the Network Elements
mediating the raw data collected into the XML format defined by the OAM
post-processing this translated data for viewing and creating tables, graph reports, Geographical
Information System views and call trace analysis.
Data collection and mediation are performed through WICL commands. The functional split between sub-
systems is as following:
NEs are in charge of recording data according to a pre-defined Granularity Period and a counter list.
One XDR file is generated at the end of every Granularity Period.
WMS is in charge of collecting data files from the NEs and exporting them in XML format. The WMS is
also responsible for network configuration export (CM.xml).
Manual post-processing. The data can be used for QoS data computation and network performance
monitoring.