SMALL CELL FORUM

RELEASE Four

scf.io/

DOCUMENT

069.04.01
Enterprises and multi-operator
small cells
Delivering venue centric small cell capabilities
December 2013

www.scf.io/

www.smallcellforum.org

SMALL CELL FORUM

RELEASE Four
Small Cell Forum supports the wide-scale deployment of small cells. Its mission
is to accelerate small cell adoption to change the shape of mobile networks and
maximise the potential of mobile services.
Small cells is an umbrella term for operator-controlled, low-powered radio access nodes,
including those that operate in licensed spectrum and unlicensed carrier-grade Wi-Fi. Small
cells typically have a range from 10 metres to several hundred metres. These contrast with
a typical mobile macrocell that might have a range of up to several tens of kilometres. The
term small cells covers residential femtocells, picocells, microcells and metrocells.
Small Cell Forum is a not-for-prot, international organisation. Its membership is open
to any legally established corporation, individual rm, partnership, academic institution,
governmental body or international organisation supporting the promotion and worldwide
deployment of small cell technologies. At the time of writing, Small Cell Forum has around
150 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.
Small Cell Forum is technology-agnostic and independent. It is not a standards-setting
body, but works with standards organisations and regulators worldwide to provide an
aggregated view of the small cell market.
This document forms part of Small Cell Forums Release Four: Urban. Urban small cells
are at an earlier stage in their commercial development than their more mature residential
and enterprise counterparts. As such, the present Release focuses on establishing the need,
evaluating the business case and identifying key barriers to commercial deployment. It
offers shared deployment learnings from leading operators and vendors, further renement
of our technical works and reporting progress on our activities to strengthen the ecosystem
through improved multivendor interoperability.
Release Four also contains works clarifying market needs and addressing barriers to
deployment of residential, enterprise and rural small cells.
Small Cell Forum Release website can be found here: www.scf.io and an overview of all the
material in Release Four: Urban can be found here: www.scf.io/doc/104
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, tness
for any particular purpose, or any warranty otherwise arising out of any proposal, specication, or
sample.
No license, express or implied, to any intellectual property rights is granted or intended hereby.
2007-2014 All rights reserved in respect of articles, drawings, photographs etc published in
hardcopy form or made available in electronic form by Small Cell Forum Ltd anywhere in the world.

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
As small cell deployments cover larger and larger private and semi-private spaces, the
desire to offer multi-operator coverage and service becomes stronger and stronger.
Small enterprises can tolerate single-operator deployments and may even use them as
a competitive lever to get the best subscription deal. Larger enterprises, though,
cannot bind themselves to one operator to the exclusion of others and must seek
multi-operator solutions in order to serve their diverse customer base well.
This paper examines the challenges and options for supporting multiple operators
within enterprise small cell deployments. It includes both protocol options with classic
Iu-h small cell architectures (such as MOCN) as well as alternative solutions such as
distributed antenna (DAS). Not least, it identifies the challenges of management of
the enterprise solution when split across the operators sharing the access network.

Report title: Enterprises and multi-operator small cells

Issue date: 03 December 2013
Version: 069.04.01

Executive summary
As small cell solutions move out of the residence and small business arenas and into
the enterprise, there will be an increasing need for the alternative solutions to be
shared between a number of individual operators.
This document describes alternative approaches to delivering shared infrastructure
within an enterprise small cell environment, including comparing small cell solutions
with classical distributed antenna solutions. Standardized 3GPP network sharing
capabilities are reviewed and the applicability of those techniques to small cell
deployments are analysed. It is demonstrated how current specifications are
incomplete in addressing the overall solution for deploying shared small cell systems,
including management systems supporting multi-operator deployments, and those
areas that may require vendor proprietary/pre-standard definitions are identified.

Report title: Enterprises and multi-operator small cells

Issue date: 03 December 2013
Version: 069.04.01

Contents
1.
1.1
1.2

Multi-operator scenarios ..................................................1

Enterprise and bring your own device .................................... 1
Nationwide enterprise operating in countries with regional
frequency allocations ........................................................... 1
1.3
Enterprise support for temporary employees and guest
contractors ......................................................................... 1
1.4
Enterprise support for access from the general public .............. 1
2.
3GPP network sharing capabilities ...................................2
2.1
Multi-operator core network architecture ................................ 2
2.2
Multi-operator gateway core node based sharing architecture ... 3
2.3
Multi-operator based 3G small cell architecture ....................... 4
2.4
Multi-operator based HeNB architecture ................................. 5
2.5
Converged multi-operator based approaches .......................... 6
3.
DAS network sharing capabilities .....................................7
4.
Management of multi-operator small cells .......................9
4.1
Multiple PLMN-ID based shared small cells .............................. 9
4.2
Common PLMN-ID based shared small cells ............................ 9
4.3
Qualification of network listen derived neighbour cell ............... 9
4.4
Identifying neighbour cells in shared networks ...................... 10
4.5
Small cell management system based configuration of
neighbour cells in shared networks ...................................... 10
5.
Example of TR-196v2/ePLMN based UMTS multioperator sharing .............................................................11
6.
Gaps and recommendations for future work...................13
6.1
Multiple PLMN Lists and MOCN based shared HNB .................. 13
6.2
Resource partitioning between shared networks .................... 13
6.3
Handover target identification for pre-R6 UEs........................ 13
7.
Summary ........................................................................14
References ................................................................................15

Report title: Enterprises and multi-operator small cells

Issue date: 03 December 2013
Version: 069.04.01

Figures
Figure 2-1

3GPP multi-operator core network (MOCN) architecture for 3G ............. 2

Figure 2-2

Gateway core node (GWCN) based network sharing ............................ 4

Figure 2-3

MOCN based shared 3G small cell network ......................................... 5

Figure 2-4

GWCN based shared small cell network ............................................. 5

Figure 2-5

LTE small cell sharing options ........................................................... 6

Figure 3-1

3G multi-operator DAS .................................................................... 7

Figure 3-2

Small cells used to drive a multi-operator DAS ................................... 8

Figure 5-1

3G small cell sharing based on TR-196v2/equivalent PLMNS ...............12

Report title: Enterprises and multi-operator small cells

Issue date: 03 December 2013
Version: 069.04.01

1. Multi-operator scenarios
1.1

Enterprise and bring your own device

Whereas previously many enterprises have been successful in being prescriptive in

terms of which mobile devices are supported within their environment, todays
workforce employees can carry several mobile devices, such as a smartphone, tablet,
and a laptop. Supporting these devices is an emerging key challenge for IT
departments. The proliferation of these consumer devices often called the bring
your own device (BYOD) trend that enterprise IT departments need to support, is
placing multi-device handling policies at the forefront of modern IT strategies.
In BYOD environments, the opportunity for an in-building enterprise solution to offer
coverage and capacity from a plurality of network operators can be seen as beneficial
as it is able to support the widest range of devices and associated subscriptions.

1.2

Nationwide enterprise operating in countries with regional

frequency allocations

Compared with countries with nationwide spectrum allocations, some countries

operate market based spectral allocations, for example USA. In such scenarios, an
enterprise that operates nationwide may find themselves operating in markets that
are preferentially covered by one particular operator and in other markets where the
spectrum allocations favour another operator. In such environments, the enterprise
may offer their workforce employees the choice of different service provider in order
to benefit from the locally significant superior service. Consequently, even when an
enterprise does not operate a BYOD policy, there may be requirements to support a
plurality of network operators.

1.3

Enterprise support for temporary employees and guest

contractors

Some enterprises make widespread use of temporary employees and/or guest

contractors that operate out of a standardized enterprise workspace. In such
situations, the mandating by the enterprise of the use of a particular mobile network
operator by its temporary employees and contractors is not a viable option.

1.4

Enterprise support for access from the general public

Certain enterprise locations may be required to support access from the general
public. For example, an enterprise that includes a retail branch network may be
interested in improving the coverage and capacity offered to the general public that is
visiting the branch.
More generically, an enterprise may operate in a venue that is designed to
accommodate the general public. Examples include shopping malls, concert venues,
transport hubs, etc. In such environments, the enterprise may require service be
made available for a plurality of network operators.

Report title: Enterprises and multi-operator small cells

Issue date: 03 December 2013
Version: 069.04.01

2.

3GPP network sharing capabilities

3GPP has integrated shared network capabilities into its architecture. From Release 6
(2006), 3GPP has enhanced its UMTS system definition to support network sharing
[1], enabling different core network operators to connect to a shared radio access
network.

2.1

Multi-operator core network architecture

3GPP has defined a multi-operator core network (MOCN) feature that enables the
radio access network to be shared, as shown in the Figure 2-1 below [1]. The shared
radio access network operator is labelled as X and the core network operators as A,
B and C. Typically, one of the core network operators will also be the radio access
network operator, although to generalise the approach, the following figures do not
mandate such, and then could allow for an independent entity to operate the shared
RAN network.

Figure 2-1

3GPP multi-operator core network (MOCN) architecture for 3G

Each cell in the shared radio access network broadcasts system information including
information about the available core network operators. Suitably enhanced UEs (i.e.,
Release 6 capable UEs) can decode this information and use such in network and cell
selection and re-selection procedures.
An individual CN is selected and assigned for a particular UE. Suitably enhanced UEs
can inform the radio access network of the selected CN operator. For UMTS, this NAS
node selection function (NNSF) is located in the RNC.
Note: NAS node means core network node. Its called a NAS node in this
context to differentiate it from the AS node thats doing the selecting. AS
means access stratum, synonymous with the radio access network in this
context. NAS means non-access stratum i.e., everything else.

Report title: Enterprises and multi-operator small cells

Issue date: 03 December 2013
Version: 069.04.01

3G UEs that have not been suitably enhanced with the ability to decode the enhanced
broadcast information are termed non-supporting UEs. Such UEs make use of a
common PLMN-ID that has been defined for conventional (non-shared) deployments.
Note: Public land mobile network identities (PLMN-IDs) are used by access
networks to broadcast the identity of the network and comprise a mobile country
code (MCC) and a mobile network code (MNC). The PLMN-ID is additionally used
as the leading digits in a mobile subscribers international mobile subscriber
identity (IMSI), which is stored in the UEs SIM card. A mobile device can
therefore compare the PLMN-ID recovered from the IMSI stored on its SIM card
with the PLMN-ID received from that broadcast from a mobile network to
determine if the network selected is a home network (HPLMN) or a foreign
network.
In Figure 2-1 above, the shared RAN operator X will be responsible for broadcasting
this common PLMN-ID which will be distinct from the PLMN-IDs of CN operators A, B
and C. In order to enable reselection of the shared operator X network by nonsupporting UEs of the different core networks, these core networks will typically be
enhanced with equivalent PLMN functionality, such that core networks A, B and C all
indicate that the common PLMN-ID used by RAN operator X is equivalent to their
respective HPLMNs.
Note, the scaling capabilities of the 3GPP MOCN-based sharing approach and
equivalent PLMN-based sharing are different:

2.2

For MOCN operation, UMTS and LTE have been specified to enable a
maximum of 6 operators (PLMN-IDs) to be broadcast [2] [3]
Non-access stratum (NAS) messaging has been specified to enable the
signalling of up to 15 equivalent PLMN identities [4] [5] to a particular UE.

Multi-operator gateway core node based sharing architecture

In addition to the MOCN configuration where only RAN elements are shared, 3GPP has
additionally defined an alternative approach to shared networks whereby both RAN
and MSCs and SGSNs are shared [1]. This configuration is referred to as gateway core
network (GWCN) and is shown in Figure 2-2.

Report title: Enterprises and multi-operator small cells

Issue date: 03 December 2013
Version: 069.04.01

Figure 2-2

2.3

Gateway core node (GWCN) based network sharing

Multi-operator based 3G small cell architecture

From a standardization perspective, the MOCN approach can be re-applied to the 3G

small cell architecture by augmenting the 3G small cells with the capability to
broadcast the enhanced system information. Because the small cell gateway is
signalled a UEs IMSI in the HNBAP UE-REGISTER-REQUEST message, it is able to use
the PLMN-ID recovered from the IMSI to select the appropriate core network, e.g., for
non-supporting UEs. Figure 2-3 shows how the MOCN concepts can be re-applied to
the 3G small cell network. Here, the small cell gateway is enhanced with NAS node
selection function [6].

Report title: Enterprises and multi-operator small cells

Issue date: 03 December 2013
Version: 069.04.01

Figure 2-3

MOCN based shared 3G small cell network

GWCN approaches can also be directly re-used to provide a shared network as shown
in Figure 2-4.

Figure 2-4

2.4

GWCN based shared small cell network

Multi-operator based HeNB architecture

Compared to the 3G approach, where the NNSF can only exist in the small cell
gateway, the shared LTE small cell architecture allows for the NNSF to be located
either at the LTE small cell or in the LTE small cell gateway [6]. The NNSF located in
Report title: Enterprises and multi-operator small cells
Issue date: 03 December 2013
Version: 069.04.01

the LTE small cell is broadly aligned with the macro eNB capability that then allows
any eNB to be interconnected to multiple MME/S-GWs [7]. The NNSF located in the
LTE small cell is only applicable in those architectures that do not include an LTE small
cell gateway [8]. The Figure 2-5 below illustrates the two different options for
realizing shared LTE small cell.

Figure 2-5

LTE small cell sharing options

Note: Unlike in the 3G small cell scenario where the 3G small cell gateway has
visibility of the users IMSI via the HNBAP based UE registration procedure, the LTE
small cell gateway will not typically have visibility of UE IMSIs. Since non-supporting
UEs are not applicable in an LTE small cell deployment, this means that the LTE small
cell gateway (or the shared LTE small cell) should always use the selected PLMN as
indicated by the PLMN identity IE within the tracking area indicator IE included in the
S1AP initial UE message.
Whereas the above approaches with the NNSF in the access domain can be thought of
as broadly similar to the MOCN approach defined for 3G, the GWCN based approach is
also equally applicable to LTE, in which case the SGW and MME are shared, with the
latter being responsible for providing the equivalent PLMN list the UE.

2.5

Converged multi-operator based approaches

Those operators that intend to deploy multi-operator based co-located 3G small cell
and LTE small cell capability in a converged access point will typically be motivated to
align on an architecture where the NNSF is in the gateway component and a common
security gateway is shared between the different operators and between 3G small cell
and LTE small cell based access points.
Conversely, those operators that are purely focused on LTE and have pre-existing
MOCN arrangement for their macro networks, will typically be motivated to converge
on an architecture without LTE small cell gateway where the NNSF is in the LTE small
cell and a common approach aligned with their macro sharing strategy is applied to
the case of LTE small cell deployment.

Report title: Enterprises and multi-operator small cells

Issue date: 03 December 2013
Version: 069.04.01

3. DAS network sharing capabilities

Until recently, operators typically deployed their own systems for single operator DAS.
Unfortunately, this has resulted in multiple DAS systems installed in the same building
with consequential issues around the use of multiple cable runs, multiple antennas and
multiple maintenance contracts.
Today, regulatory authorities, building developers, building owners and landlords are
attracted to the benefits of shared multi-operator DAS systems. The support of multioperators in a DAS environment does place additional requirements on the system and
may therefore cause issues if legacy single operator systems are upgraded to multioperator support. In particular, new requirements will likely to be placed on:

Tx/Rx isolation between operators, ensuring that the transmission from one
operator does not lead to the desensitization of the base station of a second
operator.
Passive intermodulation, is generated due to non-linearities in the DAS
system and can cause significant issues in higher power multi-operator
deployments.

This has led to the creation of neutral hosting DAS providers that in some cases are
responsible for the design, construction, installation and operation of the complete
DAS system. Figure 3-1 shows an example of three operators sharing a DAS system.

Figure 3-1

3G multi-operator DAS

It is evident that the same techniques for distributing the antennas can be used with
shared small cell realizations, for example re-using the RF Combiner to support a
shared realization of small cells that are then used to drive the DAS system. Figure 32 illustrates how the separate operate RNC/NodeBs are replaced with small cells to
drive the shared DAS installation.

Report title: Enterprises and multi-operator small cells

Issue date: 03 December 2013
Version: 069.04.01

Figure 3-2

Small cells used to drive a multi-operator DAS

Report title: Enterprises and multi-operator small cells

Issue date: 03 December 2013
Version: 069.04.01

4. Management of multi-operator small cells

4.1

Multiple PLMN-ID based shared small cells

For full MOCN enabled cells, each small cell is required to broadcast system
information describing the available core networks. In particular, in UMTS the master
information block (MIB) includes the information element termed multiple PLMN list
[2] and in E-UTRA, the SystemInformationBlock1 includes the information element
termed PLMN-IdentityList [3]. These information elements identify up to 5 (UMTS) or
6 (E-UTRA) multiple public land mobile networks of a cell in a shared network.
Importantly, the current 3G small cell management system definition in TR 196v2 [2]
does not currently support the definition of such management information elements
for 3G small cells. Contrast this with LTE where for E-UTRA, TR-196v2 defines the
FAPService.{i}.CellConfig.LTE.EPC.PLMNList.{i} object that includes the list of PLMNIdentities broadcast in System Information Block1. No equivalent object is defined for
UMTS to enable the multiple PLMN list to be configured by the 3G small cell
management system.

4.2

Common PLMN-ID based shared small cells

Pre-Release 6 UEs may be supported in a shared network by using equivalent PLMN

or ePLMN capability. A list of ePLMNs can be sent to the UE by the core network at
each location and/or routing area update and indicates a list of PLMN identities that
the UE should treat as being equivalent to the registered PLMN.
In particular, consider the case of two core networks, MNC#1 and MNC#2 that agree
to share a network. In order to support pre-R6 UEs, these two core network operators
can define a new PLMN-ID, e.g., corresponding to MNC#3. Each of the core networks
will then signal that the PLMN-ID associated with MNC#3 as being equivalent to the
HPLMN.
The shared 3G small cell can then be configured to broadcast the PLMN-ID associated
with MNC#3 which will ensure that UEs from both MNC#1 and MNC#2 will consider
the shared 3G small cell as being equivalent to their home PLMN.
In contrast to MOCN, E-PLMN configuration for 3G is supported by TR-196v2 defining
the FAPService.{i}.CellConfig.UMTS.CN object that includes the EquivPLMNID list to
enable the 3G small cell management system to configure equivalent PLMN
functionality.

4.3

Qualification of network listen derived neighbour cell

In typical 3G/LTE small cell deployments, the neighbour cell list will be automatically
configured by using network listen capability in the small cell. The small cell will
typically be configured to only include neighbouring cells associated with its broadcast
PLMN-ID in its neighbour cell list. In both multiple PLMN-ID and common PLMN-ID
operation, the small cell needs to be signalled the PLMN identities of the core networks
sharing the small cell from the small cell management system. The small cell can then
ensure that neighbouring cells from overlapping macro networks belonging to both
core networks are included in the neighbour cell list.
For LTE based small cells, the TR-196v2 PLMN List object can be used by the small cell
to qualify network listen derived neighbour cell information [9]. For 3G based small

Report title: Enterprises and multi-operator small cells

Issue date: 03 December 2013
Version: 069.04.01

cells, the lack of PLMN List object means that the small cell should be configured to
use the equivalent PLMN list to qualify network listen derived neighbour cell
information.
The 3G/LTE small cell is able to report the PLMN-ID of its neighbouring cells using the
TR-196v2 management object to the small cell management system.

4.4

Identifying neighbour cells in shared networks

In UMTS, as well as of system information block (SIB) 11/11bis being used to signal
inter-frequency, intra-frequency and inter-RAT neighbouring cells, SIB Type 18 can
additionally provide the UE with knowledge of the PLMN identity of the neighbouring
cells to be considered for cell reselection. This then enables a shared 3G small cell to
be operated in an environment of two non-shared macro networks.
Note: Pre-Release 6 UEs will not have the capability to decode SIB type 18
information.
In E-UTRA, the measurement reports enable the UE to indicate to the shared small
cell, the decoded PLMN identity/ies associated with the neighbour cell measurement.

4.5

Small cell management system based configuration of

neighbour cells in shared networks

There may be instances where the small cell management system is used to manually
configure neighbouring cells. Consequently, the small cell management system may
be configured to provide the small cell a table of neighbouring cells, for example that
can be used to augment the list of neighbouring cells identified by network listen
procedures.
In such circumstances, the TR-196v2 management object allows the small cell
management system to identify the PLMN-ID associated with a GSM/UMTS/E-UTRA
neighbouring cell.

Report title: Enterprises and multi-operator small cells

Issue date: 03 December 2013
Version: 069.04.01

10

5. Example of TR-196v2/ePLMN based UMTS multi-operator

sharing
The previous section has highlighted the gaps in standardization for supporting full
MOCN capabilities within a 3G small cell deployment. This section provides an example
of how existing equivalent PLMN capabilities can be used to share small cell
infrastructure.
An example of the signalling exchanges for a 3G small cell shared using equivalent
PLMNs is shown in Figure 5-1, where a shared 3G small cell, with PLMN-ID#3 is
shared between two macro 3G networks with PLMN-IDs, PLMN-ID#1 and PLMN-ID#2.
As per normal equivalent PLMN approaches, the two independent core networks are
both configured to signal the PLMN-ID#3 as being equivalent.
In steps [1] through [4], the 3G small cell is configured using the standard TR-196v2
data model, with the PLMN-ID configured as being PLMN-ID#3, but also the
EquivPLMNID being a list comprising PLMN-ID#1 and PLMN-ID#2.
The figure shows signalling procedures for different UEs. In steps [5] through [14], a
UE of PLMN-ID#1 reselects the shared small cell and successfully registers on the core
network of PLMN-ID#1. In steps [15] through [24], a UE of PLMN-ID#2 reselects the
shared small cell and successfully registers on the core network of PLMN-ID#2.
Finally, steps [25] through [34] show the signalling of a UE from an unknown network
that is then load balanced between the two core networks to enable it to receive
service on the shared small cell access network.

Report title: Enterprises and multi-operator small cells

Issue date: 03 December 2013
Version: 069.04.01

11

Figure 5-1

3G small cell sharing based on TR-196v2/equivalent PLMNS

Report title: Enterprises and multi-operator small cells

Issue date: 03 December 2013
Version: 069.04.01

12

6. Gaps and recommendations for future work

6.1

Multiple PLMN Lists and MOCN based shared HNB

When analysing the LTE specific data model, the

FAPService.{i}.CellConfig.LTE.EPC.PLMNList.{i} object is defined that can be used to
configure the PLMN identity as well as five other PLMN identities to be broadcast in the
multiple PLMN list.
No equivalent object is defined for signalling the multiple PLMN list for UMTS. This
means that the only standard approach for shared 3G small cell is for operators to cooperatively define a new PLMN-ID for broadcast by the shared small cell network. Prior
to any update of the TR-196v2 data model to include the PLMNList in the UMTS cell
configuration object, operators and vendors will need to use vendor proprietary
solutions for signalling the PLMN list from the small cell management system to the 3G
small cell.

6.2

Resource partitioning between shared networks

The definition of a shared small cell raises the issue of how to partition the small cell
resources between the multiple core network operators and how such information gets
configured. The small cell could use the allocation of resources based on PLMN lists
within the current TR-196v2 data model. However, there may be cases where a single
core-network operator is identified by a plurality of PLMN identities in which case
multiple list entries are associated to the same core network. In such a case, any
resource partitioning based on listed identities may be inadequate.
Instead, where defined resource partitioning is required to be supported by the shared
small cell infrastructure, vendor proprietary extensions to the TR-196v2 data model
should be used to define how small cell resources should be partitioned between
different core network operators.

6.3

Handover target identification for pre-R6 UEs

R6 UEs when operating on a shared network are able to receive and decode SIB18
information that then enables the PLMN identity of neighbouring cells to be signalled
to the UE. The pre-R6 UE does not have the ability to decode such information and is
therefore not able to qualify its neighbour cell measurements.
The 3G small cell functionality for supporting shared operation should therefore be
enhanced with capability to recover the PLMN List from the NAS signalling. The
enhanced 3G small cell should then use this recovered information within its handover
logic for target cell identification, ensuring that there is a corresponding PLMN
equivalency for any identified handover target for any particular UE.

Report title: Enterprises and multi-operator small cells

Issue date: 03 December 2013
Version: 069.04.01

13

7. Summary
There are several drivers for enabling small cell equipment to be shared between a
number of individual operators. This document describes alternative approaches for
delivering shared infrastructure within an enterprise small cell environment.
Standardized 3GPP network sharing capabilities are reviewed and the applicability of
those techniques to small cell deployments are analysed. It is demonstrated how
current specifications are incomplete in addressing the overall requirements for
deploying shared small cell systems and those areas that may require vendor
proprietary/pre-standard definitions are identified.

Report title: Enterprises and multi-operator small cells

Issue date: 03 December 2013
Version: 069.04.01

14

References
1
2
3
4
5
6
7
8
9

3GPP Technical Specification 23.251 Network Sharing; Architecture and functional

description
3GPP Technical Specification 25.331 Radio Resource Control (RRC); Protocol
specification
3GPP TS 36.331, E-UTRA Protocol Specification: Radio Resource Control (RRC)
3GPP TS 24.008, Mobile radio interface Layer 3 specification; Core network
protocols; Stage 3
3GPP TS 24.301, Non-Access-Stratum (NAS) protocol for Evolved Packet System
(EPS); Stage 3
3GPP Technical Specification 23.830 Architecture aspects of Home NodeB and
Home eNodeB
3GPP Technical Specification 36.410 S1 general aspects and principles
3GPP Technical Report 37.803, Mobility enhancements for Home Node B (HNB)
and Home enhanced Node B (HeNB)
Broadband Forum FAP Service: 2.0: Femto Access Point Service Data Model

Report title: Enterprises and multi-operator small cells

Issue date: 03 December 2013
Version: 069.04.01

15