Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
RELEASE Five
scf.io/
DOCUMENT
066.05.01
Enterprise SON use cases
November 2013
www.scf.io/
www.smallcellforum.org
Four
RELEASE Five
Small Cell Forum works to accelerate small cell adoption to change
the shape of mobile networks and maximize the potential of mobile
services.
We are not a standards organization but partner with organizations that inform
and determine standards development. We are a carrier-led organization. This
means our operator members establish requirements that drive the activities
and outputs of our technical groups.
Our track record speaks for itself: we have driven the standardization of key
elements of small cell technology including Iuh,FAPI/SCAPI, SON, the small cell
services API,TR069 evolution and the enhancement of the X2 interface.
At the time of writing, Small Cell Forum has more than 140 members, including
68 operators representing more than 3 billion mobile subscribers 46 per
cent of the global total as well as telecoms hardware and software vendors,
content providers and innovative start-ups.
This document forms part of Small Cell Forums Release Five: Rural &
Remote that considers the opportunities and perceived barriers associated
with the deployment of small cells in rural and remote scenarios, including
disaster recovery, military installations, as well as verticals such as oil and gas,
maritime, aviation and automotive.
The Small Cell Forum Release Program has now established business cases
and market drivers for all the main use cases, clarifying market needs and
addressing barriers to deployment for residential, enterprise and urban small
cells.
Small Cell Forum Release website can be found here: www.scf.io
All content in this document including links and references are for informational
purposes only and is provided as is with no warranties whatsoever including
any warranty of merchantability, fitness for any particular purpose, or any
warranty otherwise arising out of any proposal, specification, or sample.
No license, express or implied, to any intellectual property rights is granted or
intended hereby.
If you would like more information about Small Cell Forum or would
like to be included on our mailing list, please contact:
Email info@smallcellforum.org
Post Small Cell Forum, PO Box 23, GL11 5WA UK
Member Services memberservices@smallcellforum.org
Scope
The Enterprise self-organizing networks (SON) use cases document is an informative
document. Its scope is to capture the use cases that illustrate, in a comprehensive
manner and building upon the Enterprise femto deployment guidelines document [ 1],
how the self-organizing function helps in the configuration, optimization and
maintenance of enterprise small cell networks with very low or no manual
intervention.
Specifically, the informative use cases are targeted towards the two predominant radio
access technologies (RAT) UMTS terrestrial access network (UTRAN) and evolved
UTRAN (E-UTRAN). In context, the 3GPP specified functions such as self-configuration,
automatic neighbor relations (ANR), physical cell identity/primary scrambling code
assignments, resource management and load balancing, robust handoff and random
access channel (RACH) optimization are addressed.
The target audience is systems and network deployment engineers as well as
designers working on SON solution architectures and SON algorithms.
Executive summary
The context and the definitions of small cells and enterprise small cell networks are done well in
[1]. For convenience, the relevant text is repeated here.
Small cells are low-power cellular base stations typically deployed in residential, enterprise or
hotspot settings. Small cells provide excellent user experience through better coverage for voice
and very high data throughputs. Small cells can also offload traffic from macrocell network and
enable new applications such as location-based services.
Enterprise small cell deployments refer to commercial multi-cell deployments that cover a wide
range of settings such as enterprise buildings, small offices and shopping malls. Enterprise small
cell deployments differ from residential ones due to large number of users, RF interactions
between small cells, mobility and handover from one small cell to another, potentially large RF
variations inside the buildings and potentially large coverage area per small cell.
The background document [1] provides recommendations for deployment, configuration and
operation of enterprise small cells. This document covers specifically the SON function as it
pertains to the enterprise small cell networks. The document aims to highlight, to the
appropriate detail possible, without infringing or architecture or algorithm choices, use cases for
the SON function. The broad goal of SON is to enable the configuration, deployment,
optimization, operation and maintenance of dense networks across multiple scales with very low
or no manual input or feedback and this spirit is maintained in the document.
For a very small number of use cases in an enterprise context, there is scope for a limited
involvement or assistance of IT technicians. Hence, a separate section (Section 4) is added to
show these use cases. The intent is for the document to stand on its own and address the
predominant usage of SON through the use cases of Section 3 with Chapter 4 occupying a very
narrow slice of usage. Chapters 1, 2 and 3 have validity beyond the enterprise while Chapter 4
is also limited only to the enterprise context.
Specifically, the following topics are addressed:
1.
2.
3.
4.
Enterprise SON use cases addressing the two predominant radio access
technologies UTRAN and EUTRAN.
SON use cases addressing the full life cycle of the network from initial
deployment and configuration through self-optimization as well as
maintenance aspects.
SON functionality specifically addressing the 3GPP identified areas such as
self-configuration, neighbor discovery, parameters (PCI/PSC) optimization,
resource sharing (for interference management and capacity optimization as
final goals), load balancing, robust handoff and RACH parameter
optimization.
In addition some attempt is made to address maintenance aspects of SON.
The goal of this informative document is to be useful to system architects and algorithm
designers working on architectures and SON functions at the front-end of the design process as
well as network designers at the back-end. Naturally, the goal is to illustrate that if the frontend designers cover the use cases in the design stage, then in the back-end the network
engineer will benefit significantly.
The real benefit is, of course, to both the network operators and users in terms of reduced
capex and opex for the same or better level of service.
Contents
1.
Introduction .....................................................................1
2.
SON and SON function ......................................................3
2.1
SON function ...................................................................... 3
2.2
SON features ...................................................................... 3
2.3
SON management ............................................................... 5
3.
Enterprise SON use cases .................................................7
3.1
Glossary of terms ................................................................ 7
3.2
Configuration ...................................................................... 8
3.3
Planning, deployment and operation ...................................... 9
3.4
Optimization ..................................................................... 13
3.5
Maintenance ..................................................................... 18
4.
IT technician assisted SON .............................................19
4.1
General use cases ............................................................. 19
4.2
Specific examples .............................................................. 23
5.
Summary ........................................................................26
References ................................................................................27
Tables
Table 3-1
Table 3-2
Table 3-3
Table 3-4
Table 3-5
Table 3-6
Table 3-7
Table 3-8
Table 3-9
Table 3-10
Table 3-11
Table 3-12
Table 3-13
Table 3-14
Table 3-15
Table 3-16
Table 3-17
Table 3-18
Table 4-1
Table 4-2
Table 4-3
Table 4-4
Table 4-5
Figures
Figure 1-1
Figure 2-1
Figure 2-2
Figure 4-1
1. Introduction
The concepts of small cell network and enterprise small cell networks are covered in
[1].
The need for and the functionality of SON functions are extensively covered in
literature (see for example [ 2] and references therein). Specifically, SON function
scope and coverage within the 3GPP context are addressed in [ 3] (and references
therein).
The SON function is not a specific node or element in the network. Rather, as the
name implies, it is a collection of functional entities that address the specific needs
discussed in the references pointed to above. In an architecture and algorithm
instantiation sense the functions lend themselves to a large number of choices.
Further, because heterogeneous networks are a significant context of deployment, the
SON functions vary according to the scale in which they are deployed (macro versus
small cells, etc.) and multiple SON functions may co-exist in a given operators
network together fulfilling the overall business needs of the operator. As such these
SON functions need to behave co-operatively and in the interest of the overall cost
functions and policies.
Enterprise small cell networks are, as the name implies, networks of small cells
deployed to enhance the experience of the users inside the enterprise. The networks
could be for closed subscriber groups (CSG), prioritized for enterprise users or open.
Each might entail different optimization criteria and the SON function must operate
under the constraints.
Without intending in any way to be comprehensive (or even specific in all contexts)
the following figure shows how the various scales might be deployed and might
interact with each other.
Figure 1-1
It might also be noted that the SON functions can reside in the same plane where
control and user data flow (between macro/ small cells and gateway/EPC, for
example) or in the direction of the management plane (EMS/ACS, NMS/OSS) or both
depending on the specific function being accomplished.
In addition, since the networks can be multi-RAT, it is possible for a single SON
function to optimize across the two or more RAT or for each RAT to have its own SON
function working co-operatively with the SON functions of other RAT.
Certain aspects of SON functions might have seeming overlap with normal radio
resource manager (RRM) functions. However, as explained later, SON functionality
and RRM functionality each have their specific domain. This allows the RRM to perform
its normal functions (primarily radio bearer control, radio admission control,
connection mobility control [ 4]) while the SON function can optimize RRM
parameters/operation as part of multi-cell co-ordination. It is important to note this
distinction while understanding the scope of the SON function. Where necessary, this
distinction is again pointed out as appropriate.
The scope of this document is narrowly to focus upon the SON function addressing the
enterprise deployments and even more specifically illustrate the SON function through
properly designed use cases, whether they be single RAT (intra and inter-frequency)
or multi-RAT (3G and LTE).
2.1
SON function
This note describes use cases of activities involving SON features, and uses the term
SON function to describe the logical entity which provides the algorithms, data
storage and interactions with other nodes to perform the SON activities. This term is
deliberately non-specific about where this SON function is located, and as such
encompasses the options for this entity to be using any of the centralized SON model,
the distributed SON model, or the hybrid SON model, as described in [3]. In some of
the use cases, it is clear there must be some distributed element to the SON Function
(e.g. when SON-related information is to be exchanged over X2 with other small cells)
for the use case to be as described, and in other use cases it is clear that there must
be some centralised SON function (e.g. for holding centralized data and applying
central control of multiple small cells) is inferred.
The use of the term SON function is also not specific about how much influence the
small cell SON features may have on the operation of the macrocells. The macrocells
may be totally autonomous, taking no account of the small cell network in their
management of load and interference (maybe including separate autonomous
macrocell SON functions), or they may have SON features tightly integrated with the
SON function of the small cells, balancing the load and interference between all the
cells within the network. This level of interaction clearly affects the complexity and
capability of the SON function, but does not really affect the use cases described here,
as each small cell interacts with the SON function, and what that SON function does
(except in very broad terms) to arrive at the configuration or commands given to the
small cells is outside the scope of this document.
2.2
SON features
The overall SON feature may be considered as a set of smaller features, some selfcontained, others interacting with each other. This section describes some of those
constituent SON features.
Self-configuration is defined as the process where newly deployed nodes are
configured by automatic installation procedures to get the necessary basic
configuration for system operation.
This process works in pre-operational state. Pre-operational state is understood as the
state from when the small cell is powered up and has backbone connectivity until the
RF transmitter is switched on.
As described in Figure 1-1, functions handled in the pre-operational state like:
Optimization/adaptation
a- 1 :
configuration of IP address
and detection of OAM
a- 2 :
(A ) Basic Setup
Self- Configuration
(pre - operational state)
a- 4 :
(B ) Initial Radio
Configuration
b- 1 :
downloading of firmware
( and operational parameters )
Self- Optimisation
( operational state )
(C ) Optimization/
Adaptation
c- 1 :
c-3 :
Figure 2-1
2.3
self healing
SON management
deployment so that the operators have opportunity to manage, monitor and plan their
future network deployments. The SON management system should be able to react
and (re-)configure SON functions depending on the operator target application.
Figure 2-2
SON management
3.1
Glossary of terms
Since the document and specifically sections to follow are heavy on acronyms, the following
glossary is added for convenience to the reader.
Acronym
ACS
ANR
CN
DL
ECGI
eNB
EPC
IP
IT
LTE
MME
MSC
NB
NLM
NRT
PCI
PLMNID
PSC
S1
SC
SGSN
TNL
TX
UL
UMTS
X2
Term
Auto-configuration server
Automatic neighbor discovery
Core network
Downlink. From the base station to the user equipment
E-UTRAN cell global identifier
e Node B (popular name for LTE base stations)
Evolved packet core
Internet protocol
Information technology
Long term evolution
Mobility management entity
Mobile-network switching center
Node B (popular name for UMTS base station)
Network listen module (sometimes called a sniffer)
Neighbor relations table
Physical cell identifier (PCI in LTE)
Public land-mobile network identifier
Primary scrambling code (in UMTS)
An LTE standards-defined interface between eNB and EPC. Has two planes. A
user plane and an MME plane.
Small cell
Serving GPRS support node
Transport network layer
Transmit or transmitter
Uplink. From the user equipment to the base station
Universal mobile transmission system
An LTE standards defined interface between eNBs.
Table 3-1
Glossary of terms
3.2
Configuration
Overview
Actors
Applicability
Preconditions
Flow
Uses
Notes
(Optional)
Table 3-2
Overview
Actors
Applicability
Preconditions
Flow
Overview
Uses
Notes
(optional)
Table 3-3
3.3
Overview
Actors
Applicability
Preconditions
Flow
Uses
Notes
(optional)
Table 3-4
Overview
Actors
Applicability
Preconditions
Many new small cells are added to create a new enterprise network or
expand an existing one
New small cells, ACS, SON function, optional enterprise small cell gateway,
NLM, an IT or operator technician
LTE and UMTS
An enterprise with an existing enterprise small cell network having an ACS
server inside or outside its private network. Optionally, there is a gateway (that
could be the enterprise edge router, also) outside the private network
Overview
Flow
Many new small cells are added to create a new enterprise network or
expand an existing one
1. A technician determines the required number of small cells and their
locations within the enterprise.
2. This is done using general deployment guidelines and enterprise
building dimensions [1]
3. The small cells are provisioned with the ACS and optional stand alone
SON function details
4. Small cells connect to the ACS and optional stand alone SON
function(s), are authenticated, and obtain their configuration from the
ACS.
5. As part of configuration, the small cells are configured to belong to a
common enterprise cluster and initialized to be in a training mode 1.
6. Optionally, NLM is switched on and neighbor network parameters
(DL/UL frequencies, PCI (PSC) etc.) are discovered and NLM data sent
to SON Function(s).
7. SON function(s) can be reside in individual small cells, one small cell or
the ACS server.
8. SON function(s) assign temporary or permanent radio parameters
(e.g., PCI (PSC), with consideration also to any co-channel macro
(e)NodeBs that are visible to the small cell (taking into consideration
any policies provisioned into the SON function).
9. The small cell connects to the MME (MSC and SGSN) in the EPC (CN)
(through the enterprise gateway or directly)
10. Optionally, small cells perform TNL address resolution for NLMdiscovered and ACS-provisioned neighbors or are provided by their
SON functions with neighbor address information.
11. Optionally, small cells establish X2 (Iurh) links to any neighbors for
which TNL addresses are available (whether discovered or provisioned)
12. The small cell transmitters are turned on and small cells begin to
operate in training mode.
13. The technician walks around the enterprise with a UE in connected
mode with the enterprise small cell network or some other tool to
collect information about RF environment in the enterprise (e.g., signal
quality of the small cells, surrounding macros, etc.).
14. The collected information is either passed autonomously or with
technician assistance to the SON function(s).
15. At the end of the walk-around, SON function(s) is instructed to
determine transmit power for the small cells.
16. SON function determines transmit power using obtained RF information
considering any co-channel macros and UL interference issues to
provide good coverage and capacity in the enterprise network.
17. Small Cells start radiating with the updated TX power and begin normal
operation.
18. Optionally, technician performs additional walk-arounds to verify
coverage and mobility in the enterprise. Based on this second walkaround, SON function(s) may raise alarms, error codes suggesting
required changes in the deployment. In such a case, technician may redo the calibration after taking remedial measures
Uses
Notes
(optional)
Table 3-5
1
Training mode is defined as a state where a UE can camp and move to connected state and the small cell
is capable of receiving and processing Event and Measurement reports. Mobility functions etc. are not
necessarily enabled in this state
10
Overview
Actors
Applicability
Preconditions
Flow
Uses
Notes
(optional)
Table 3-6
Overview
Actors
Applicability
Preconditions
Flow
Uses
Notes
(optional)
Table 3-7
11
Overview
Actors
Applicability
Preconditions
Flow
Uses
Notes
(optional)
Table 3-8
Overview
Actors
Applicability
Preconditions
Flow
Uses
Notes
(optional)
Table 3-9
12
Overview
Actors
Applicability
Preconditions
Flow
Uses
Notes
(optional)
As a result of the NRT update, the small cell SIB messages may need to be
updated by RRM
Table 3-10
3.4
Optimization
Overview
Actors
Applicability
Preconditions
Flow
Uses
Notes
(optional)
Table 3-11
13
Overview
Actors
Applicability
Preconditions
Flow
Small cell and macro partition resources to help balance load and
manage interference
Small cell, macro, ACS, SON function
LTE
An enterprise with an existing enterprise small cell Network having an ACS
server inside or outside its private network. Optionally, there is a gateway (that
could be the enterprise edge router also) outside the private network.
Enterprise small cell(s) are deployed in the same frequency as macros. For
time domain partitioning, macros and small cells need to operate
synchronously
1. SON function determines small cell is co-channel with macro (e.g., via NLM
measurements, configuration parameters)
2. ACS or SON function determines resource partitioning pattern between
small cell and macro, and convey it to the macro and small cell. ACS or
SON function may also determine configuration and control parameters,
(for example, reporting periods, RSRP thresholds for eICIC/ICIC in macro
and small cell)
3. Alternatively (to step 2),
a. Small cell(s) establish X2 link to co-channel macro and exchange traffic
load information with macro or SON function.
b. Macro or SON function determines the appropriate resource partitioning
pattern and conveys to small cell or macro respectively.
4. Resource partitioning can be achieved by utilizing standard-defined
procedures in time domain (i.e., eICIC) and/or frequency domain (i.e.,
ICIC).
5. The determination of partitioning pattern can be based on expected traffic
load on macro and small cell, past traffic history, or some other
configuration policy.
6. Small cell follows the resource partitioning pattern for scheduling its users.
7. When multiple small cells are installed in an enterprise, small cells in the
enterprise perform inter-small cell resource coordination within the
resources available through resource coordination with macro.
8. An enterprise-SON function in the enterprise may act as X2 aggregator
and/or proxy for eICIC/ICIC message exchange between small cell and
macro
Uses
Notes
(optional)
Table 3-12
14
Overview
Actors
Applicability
Preconditions
Flow
Uses
Notes
(optional)
Table 3-13
15
Overview
Actors
Applicability
Preconditions
Flow
Uses
Notes
(optional)
Table 3-14
Overview
Actors
Applicability
Preconditions
Flow
Uses
Notes
(optional)
Table 3-15
RACH optimization
16
Overview
Actors
Applicability
Preconditions
Flow
Uses
Notes
(optional)
Table 3-16
Overview
Actors
Applicability
Preconditions
Flow
Uses
Notes
(optional)
Table 3-17
17
3.5
Maintenance
Overview
Actors
Applicability
Preconditions
Flow
Uses
Notes
(optional)
Table 3-18
18
4.1
Overview
Actors
Applicability
Preconditions
Flow
Uses
Notes
(optional)
Enterprise small cell (NB or eNB), ACS, SON function, IT technician interface,
IT technician
An enterprise with an existing enterprise small cell network having an
associated ACS and SON function(s). An IT technician interface with access to
the relevant sources of information for the enterprise and able to validate the
credentials of the IT technician
1. The IT technician interface is provisioned and all the needed connectivity is
enabled
2. The interface aggregates SON function metrics from all registered SON
functions
3. The IT technician logs in to the IT technician interface, using any necessary
credentials for that enterprise.
4. The IT technician interface gathers any necessary instructions/information
(or displays previously received instructions/information) from the SON
function and elsewhere as required.
5. The IT technician interface displays any necessary instructions/information
to the IT technician
The IT technician interface could be implemented in a variety of ways, using a
variety of technologies in a variety of places.
The actual user interface, as an example, might take the form of a dashboard
such as Figure 4-1
Example IT technician user interface with a list of
notifications/actions and the ability to perform a number of operations
Table 4-1
19
Figure 4-1
Overview
Actors
Applicability
Preconditions
Flow
Uses
Notes
(optional)
Notification
Move small cell S/N 132334561 and small
cell S/N 132334561 apart
Move small cell S/N 132334561 and small
cell S/N 132339023 apart
Small cell positions are optimized with help from an IT technician and
to meet some desired optimization goal
Enterprise small cell (NB or eNB), ACS, SON function, NLM, IT technician
interface, IT technician
LTE and UMTS
An enterprise with an existing enterprise small cell network having an
associated ACS and SON function. Enterprise small cell network is in the
operational state, recording data and providing it to the SON function
The SON function analyses data received from the small cells in the enterprise
network.
The SON function determines a physical movement or addition of a small cell is
desirable.
The SON function generates a physical change request notification to the IT
Technician.
The IT technician makes the physical change.
The SON function assesses the new arrangement of the enterprise network
IT technician accesses IT technician interface
The physical placement of small cells in an enterprise network can be optimized
with IT technician assistance. There are multiple potential criteria for
optimizing placement:
In the simple / initial case small cells should be evenly spread.
Small cells may need to be moved / added to provide additional capacity in
certain areas of an enterprise.
Small cells may need to be moved / added as a result of a downlink power
calibration walk test (e.g. because the small cell-UE path-loss is too great).
Small cells may need to be moved / added according to other criteria, as
determined by the SON function.
The use case illustrates a SON cycle where the small cells report information to
the SON function, which determines physical actions required and sends
requests to perform these actions to the IT technician.
The SON function is not aware of the physical building layout and construction,
nor the physical locations of small cells within the building; it therefore only
knows of the relationships between small cells and macro cells from an RF /
RAN point of view (inter-small cell path-loss determined by NLM, handover
statistics, established X2 links, etc.). Therefore corresponding IT Technician
instructions can also only be in relative terms such as: Move SCx & SCy closer
together. or Install an additional small cell near to SCz
Table 4-2
20
Overview
Actors
Enterprise small cell (NB or eNB), ACS, SON function, NLM, IT technician
interface, IT technician
LTE and UMTS
An enterprise with an existing enterprise small cell network having an
associated ACS and SON function
Applicability
Preconditions
Flow
Uses
1. The SON function requests that the IT technician performs a walk test via
the IT technician interface
2. The IT technician initiates the walk test process from the IT technician
interface
3. The IT technician interface collects sufficient information about the mobile
device to be used, so that it can be identified by the enterprise small cells(*)
4. The IT technician interface informs the SON function that a walk test is
about to start, and the identifying information about the mobile to be used
5. The SON function informs all small cells within the enterprise that a walk
test is started and provides identifying information on the mobile to be
used for the test
6. The SON function informs the IT technician interface that the enterprise
small cell network is ready
7. The IT technician interface informs the IT technician that the test can
begin, giving any necessary instructions
8. The IT technician initiates a call/starts a streaming session, then
systematically walks the whole area covered by the enterprise small cell
network
9. During the test the enterprise small cells request and receive measurement
reports from the IT technicians mobile, at sufficiently granular time
intervals during the test
10. Either during the test or at the end of the test, the enterprise small cells
deliver the information determined from the mobiles measurement reports
to the SON function
11. The IT technician completes his walk of the area and stops the downlink
power calibration process
12. The SON function analyses the data collected from each small cell in the
enterprise
13. The SON function generates requests/notifications to the IT technician if
required (e.g. to move / add small cells)
IT technician accesses IT technician interface
21
Notes
(optional)
The path-loss between small cell and mobile is important, because too
large a loss can cause uplink interference from the small cell-attached
mobile to surrounding macrocells
The information to identify the test mobile to the small cells could be directly
mobile-related, e.g., for 3G the mobile number or IMSI could be used, or it
could be session related, e.g., a test call number, streaming server
address/URL to be used or local APN services.
22
4.2
Specific examples
Overview
Actors
Applicability
Preconditions
Flow
Uses
Notes
(optional)
Table 4-4
23
Overview
Actors
Applicability
Preconditions
Flow
24
Overview
Uses
Notes
(optional)
The information to identify the test mobile to the small cells could be directly
mobile-related, e.g. the mobile number or IMSI, or it could be session related,
e.g., a test call number, streaming server address/URL or local APN to be used
25
5. Summary
Enterprise deployments will be a key part of small cell deployments and therefore a key part of
small cell adoption and their success. SON functions are key in making the planning,
deployment, optimization and management of these networks so that they function the best
they can. If solutions meet the use cases in this document, this goal can be met in the main.
26
References
1
2
3
4
27