Shared LTE RAN

USER DESCRIPTION

93/1553-HSC 105 50/1-V1 Uen F

Copyright

© Ericsson AB 2011-2013. All rights reserved. No part of this document may be

reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use
of this document.

Trademark List

All trademarks mentioned herein are the property of their respective owners.
These are shown in the document Trademark Information.

93/1553-HSC 105 50/1-V1 Uen F | 2013-08-26

 Contents

Contents

1 Introduction 1
1.1 Basic Characteristics 2
1.2 Benefits 2
1.3 Additional Information 2

2 Feature Operation 3
2.1 Network Requirements 3
2.2 PLMN Concept and Identity Relations 3
2.3 S1/X2 Connection Handling to Support Shared LTE RAN 5
2.4 SIB1 to Support Shared LTE RAN 5
2.5 Mobility to Support Shared LTE RAN 6

3 Parameters 11
3.1 Introduced Parameters 11
3.2 Affected Parameters 12

4 Network Impact 13
4.1 Mobility 13

5 Associated Features and Affected Functions 15

5.1 Prerequisite Features 15
5.2 Affected Features 15
5.3 Related Features 15
5.4 Affected System Functions 15

6 Performance 17
6.1 KPIs 17
6.2 Counters 17
6.3 Events 18

7 O&M Information 19

93/1553-HSC 105 50/1-V1 Uen F | 2013-08-26

Shared LTE RAN

93/1553-HSC 105 50/1-V1 Uen F | 2013-08-26

 Introduction

1 Introduction

This document describes the Shared LTE RAN feature and its main benefits
and impacts in the LTE RAN.

A core network operator provides its mobile phone services through a Public
Land Mobile Network (PLMN). Conventionally, a PLMN consists of a RAN
and a core network, through which only one operator provides services to its
subscribers. Subscribers of other operators may receive services as national or
international roamers.

With the Shared LTE RAN feature, up to six operators (that is, with up to six
PLMNs) can share an LTE RAN.

Among all possible shared network configurations, the Shared LTE RAN feature
will support the following configurations:

• Gateway Core Network (GWCN): Both eNodeB and Mobility Management

Entity (MME) are shared by two or more operators.

• Multi Operator Core Network (MOCN): Two or more operators share an

eNodeB.

These configurations are standardized scenarios for network sharing as in

3GPP TS23.251. They are also shown in Figure 1.

GWCN MOCN
PDN-GW
and other core network nodes

SGW

MME

eNodeB

Cell

Operator A’s nodes or resources

Operator B’s nodes or resources
Shared nodes and resources
L0000505A

Figure 1 Shared LTE RAN Configurations

93/1553-HSC 105 50/1-V1 Uen F | 2013-08-26 1

 Shared LTE RAN

1.1 Basic Characteristics

This section describes the basic characteristics of the feature.

Feature name: Shared LTE RAN

Product identity:
See Feature Overview

Replaces: N/A

Dependencies

This feature has no prerequisite features.

This feature affects no other features.

1.2 Benefits
This section describes the benefits of this feature.

The Shared LTE RAN feature allows the operators to share a common
RAN. This provides operators with substantial cost reductions and a reduced
environmental footprint.

1.3 Additional Information

More information about this feature and related topics can be found in the
following documentation:

• 3GPP TS 36.413, S1 Application Protocol (S1AP)

• 3GPP TS 36.423, X2 Application Protocol (X2AP)

• 3GPP TS 36.331, Radio Resource Control (RRC); Protocol Specification

• 3GPP TS 23.251, Network Sharing; Architecture and Functional Description

• 3GPP TS 36.300, Evolved Universal Terrestrial Radio Access (E-UTRA)

and Evolved Universal Terrestrial Radio Access Network (E-UTRAN);
Overall description; Stage 2

• 3GPP TS 23.122, Non-Access-Stratum (NAS) functions related to Mobile

Station (MS) in idle mode

2 93/1553-HSC 105 50/1-V1 Uen F | 2013-08-26

 Feature Operation

2 Feature Operation

This section describes the Shared LTE RAN feature in more detail, including
network configuration requirements and operation flows.

The following areas are changed to support shared LTE RAN:

• S1/X2 Connection Handling

• System Information Broadcast

• Mobility

2.1 Network Requirements

The following must be fulfilled at feature activation:

• The license for the Shared LTE RAN feature must be activated.

• MME must support MOCN and GWCN configurations.

More details on the process required to load and activate the license are
provided in License Management.

2.2 PLMN Concept and Identity Relations

The following PLMNs are used in this document.

• Configured PLMNs: Configured PLMNs are all PLMNs that an eNodeB

can use and they are configured by operator using the Managed Object
Model (MOM). Configured PLMNs consist of a Primary PLMN and a list
of Additional PLMNs.

0 Primary PLMN is the PLMN configured on the eNodeB level, that is,
the same for all the cells in the eNodeB.

0 Additional PLMNs are an additional list of PLMNs that the operators

can configure, for each cell.

• Served PLMNs: Served PLMNs are the PLMNs that are served by the
MME.

• Active PLMNs: Active PLMNs in a cell are all configured PLMNs in the cell,
which are served by at least one MME.

• Serving PLMN: Serving PLMN is the PLMN that the MME has selected to
serve the User Equipment (UE). Normally it is the same PLMN that the UE

93/1553-HSC 105 50/1-V1 Uen F | 2013-08-26 3

 Shared LTE RAN

selected when it connected to the network, that is, selected PLMN, unless
the Non-Access Stratum (NAS) layers have moved the UE to another
PLMN.

• Equivalent PLMNs: Equivalent PLMNs are a list of PLMNs stored in the UE

that are considered as equivalent as the Serving PLMN for PLMN selection
and cell selection/re-selection of the UE.

• Selected PLMN: Selected PLMN is the PLMN that has been selected
by the UE in accordance with 3GPP TS 23.122, either manually or
automatically. The selected PLMN is selected from the PLMNs included in
the PLMN-IdentityList in System Information Block Type 1 (SIB1).

• Registered PLMN: Registered PLMN is the PLMN on which the UE has

successfully completed location registration (see Table 1 in 3GPP TS
23.122). In a shared network, the registered PLMN is the PLMN defined
by the PLMN identity of the CN operator that has accepted the location
registration.

Example 1 shows the PLMN Related Identity Relation.

|----|----|-----|----|--------|
MCC MNC MMEGI MMEC M-TMSI
|---------------|-------------|
GUGI S-TMSI
|----------|
MMEI
|---------|
PLMN-ID
|--------------------|
GUMMEI
|-----------------------------|
GUTI

|----|----|----|
MCC MNC TAC
|--------------|
TAI

Example 1 PLMN Related Identity Relation

The following identities are relevant to PLMN and are used in Example 1:

GUGI Globally Unique Group Identity

GUMMEI Globally Unique MME Identifier

GUTI Globally Unique Temporary Identifier

MCC Mobile Country Code

MMEC MME Code

4 93/1553-HSC 105 50/1-V1 Uen F | 2013-08-26

 Feature Operation

MMEGI MME Group Identity

MMEI MME Identifier

MNC Mobile Network Code

M-TMSI Mobile-Temporary Mobile Station Identifier

PLMN-ID Public Land Mobile Network Identity

S-TMSI SAE-Temporary Mobile Station Identifier

TAC Tracking Area Code

TAI Tracking Area Identity

2.3 S1/X2 Connection Handling to Support Shared LTE

RAN
Since up to six operators (that is, up to six PLMNs) can share an LTE RAN,
PLMN handling is important to provide correct PLMN information in the
following scenarios:

• Besides the primary PLMN, an additional PLMN list can be configured for
each cell. The additional PLMN list must be the same for all cells in an
eNodeB. The primary PLMN and the additional PLMN list will be sent to
MME in the S1AP S1 SETUP REQUEST. If the shared network support
service state is inoperable, only the primary PLMN is valid and should
be used.

• The eNodeB supports multiple served PLMNs, served MME GroupIDs,

and served MMECs for both LTE and other Radio Access Technologys
(RATs), if received in the S1AP S1 SETUP RESPONSE and S1 MME
CONFIGURATION UPDATE message.

Note: The non-LTE MME GroupID is ignored.

2.4 SIB1 to Support Shared LTE RAN

With the introduction of multiple PLMNs, the SIB1 building is changed as
described in this section.

The SIB1 contains information relevant when evaluating whether a UE is

allowed to access a cell and defines the scheduling of other system information.

For each own cell, the SIB1 may include more than one PLMN and it must
include all Active PLMNs. The Primary PLMN must always be broadcasted in
the SIB1, because it is used to construct the Cell Global Identity (CGI) used by
the UE to identify the cell. If the Primary PLMN is excluded as the Active PLMN,
the Primary PLMN will be marked as ‘‘Reserved for operator use’’ in the SIB1.

93/1553-HSC 105 50/1-V1 Uen F | 2013-08-26 5

 Shared LTE RAN

2.4.1 SIB1
Table 1 Parameter Settings in SIB1
3GPP Parameter Name Parameter Settings Comments
(first) PLMN-Identity ENodeBFunction.eNodeBPlmnI Primary
d PLMN
(first) cellReservedF Set to "reserved", if ENodeBF
orOperatorUse unction.ENodeBPlmnId is
NOT included in the EUtra
nCellFDD.activePlmnList.
Otherwise, set to EUtranCellFDD.
primaryPlmnReserved.
(other) PLMN-Identit Set according to EUtranCellFD Additional
y D.activePlmnList (exclusive PLMNs
Primary PLMN).
(other) cellReserved Set according to corresponding
ForOperatorUse EUtranCellFDD.additionalPl
mnReservedList

2.5 Mobility to Support Shared LTE RAN

2.5.1 HRL Concept

The Handover Restriction List (HRL) is an Information Element (IE) in various

S1AP and X2AP messages.

The HRL consists of the following information:

• Serving PLMN

• Equivalent PLMNs

• Forbidden Tracking Areas (TAs): Forbidden TAs is a list of TAIs in the

E-UTRAN that are forbidden for the UE, that is, the UE is not allowed to
connect to a cell with that TAI.

• Forbidden Location Areas (LAs): Forbidden LAs is a list of Location Areas

Identifiers (LAIs) in any other RAT that are forbidden for the UE, that is, the
UE is not allowed to connect to a cell with that LAI.

• Forbidden Inter-RATs (IRATs): Forbidden IRATs indicates if one or several

RATs are forbidden for the UE, that is, the UE is not allowed to connect
to a cell of that RAT.

The HRL IE exists in the following S1AP and X2AP messages.

• S1AP: INITIAL CONTEXT SETUP REQUEST

6 93/1553-HSC 105 50/1-V1 Uen F | 2013-08-26

 Feature Operation

• S1AP: DOWNLINK NAS TRANSPORT

• S1AP: HANDOVER REQUEST

• X2AP: HANDOVER REQUEST

The purpose of HRL is to let eNodeB appropriately select target cells for future
handovers, for example to avoid the situation where UE connected to a PLMN
(belonging to one operator) is handed over to a cell that is connected to neither
that PLMN nor any associated equivalent PLMN (other irrelevant operator).

The HRL is stored in the UE context and used for both measurement selection
and handover evaluation.

In accordance with standards, if the HRL is not contained in the message above,
the target eNodeB shall consider that no access restriction applies to the UE.

2.5.2 Admission Control for Handover

In the Shared LTE RAN feature, admission control is performed based on
served PLMN in the HRL. This is done in the target cell for S1 handover, X2
handover. and intra-eNodeB handover.

The admission control algorithm is shown in Figure 2.

Handover request

Privileged access Non-privileged access

Admitted HRL received HRL not received

Serving Plmn in Serving Plmn in MOCN with one PLMN MOCN with more
HRL found in HRL not found in per operator or no than one PLMN per
activePlmnList activePlmnList shared network operator or GWCN

Admitted Rejected Admitted Rejected

L0000526A

Figure 2 Admission Control for Handover in Shared LTE RAN

93/1553-HSC 105 50/1-V1 Uen F | 2013-08-26 7

 Shared LTE RAN

2.5.3 Mobility Candidate Selection

Mobility candidate selection determines a set of frequencies in LTE or other

RAT, to which the connected UE can be transferred when it encounters poor
coverage in the current cell. This mechanism is provided by the following
features:

• Coverage-Triggered Inter-Frequency Session Continuity

• Coverage-Triggered CDMA-eHRPD Session Continuity

• Coverage-Triggered WCDMA Session Continuity

• Coverage-Triggered GERAN Session Continuity

In the Shared LTE RAN feature (supporting multiple PLMNs), different UE are
connected to networks belonging to different operators. To avoid UE belonging
to one operator being redirected or handed over to another operator's network,
an Allowed PLMN list is added to each frequency relation Managed Object
(MO) for all RATs. The Allowed PLMN list consists of 0 up to 15 PLMNs. If the
list is empty, the frequency relation is allowed for UE belonging to any PLMN. If
the list contains at least one PLMN, the frequency relation is only allowed for
UE that have at least one of the listed PLMN as serving PLMN or equivalent
PLMN in the HRL. The PLMN that can be included in the allowedPlmnList
should be possible to find on cells on that frequency. Forbidden IRAT IE in the
HRL is also checked to remove the indicated RATs.

This is also valid for blind release with direct and blind handover.

2.5.4 Handover Evaluation

When the UE reports that it has found a set of suitable cells based on LTE or
IRAT measurements, a handover evaluation is executed.

Handover evaluation decides whether a reported cell is suitable for the UE. The
target cells TAI is compared with the Forbidden TAIs in HRL. If all reported cells
are forbidden for the UE, the report is discarded. If it is still valid, the target cell
PLMN or PLMN list is compared with the UE serving PLMN and Equivalent
PLMNs. If there is a match between them, the best cell is selected as target cell.

Note: The paragraph above is not applicable for IRAT handover.

In the Shared LTE RAN feature, since X2 handover signaling is only allowed if
the eNodeBs are connected to the same MME pool, the target eNodeB MME
pools must be compared with the UE serving MME before X2 handover is
selected instead of S1 handover. If the target eNodeB is not connected to the
MME pool to which the UE serving MME belongs, X2 handover is not allowed.

8 93/1553-HSC 105 50/1-V1 Uen F | 2013-08-26

 Feature Operation

2.5.5 IdleModeMobilityControlInfo Handling

An IdleModeMobilityControlInfo parameter IE can be included in the
RRC CONNECTION RELEASE message. It consists of a list of frequencies
for different RATs. Each frequency has a priority that is used by the UE to
select on which frequencies and in which order it searches for new cells on
which to camp.

Without this feature, the IdleModeMobilityControlInfo parameter is

identical for all UE.

In the Shared LTE RAN feature, the IdleModeMobilityControlinfo

parameter is based on the allowed PLMN List. Firstly, decide which
frequency relations are allowed for a certain RAT, based on the criteria stated
for measurement selection above. Secondly, for the allowed frequency
relations, find the corresponding cell reselection priority based on the
cellReselectionPriority parameter in the MOM. If the maximum number
of frequencies in accordance with 3GPP is exceeded, the lists will be truncated.

93/1553-HSC 105 50/1-V1 Uen F | 2013-08-26 9

 Shared LTE RAN

10 93/1553-HSC 105 50/1-V1 Uen F | 2013-08-26

 Parameters

3 Parameters

This section describes parameters introduced by the Shared LTE RAN feature
and parameters affected by activating the feature.

More details regarding to these parameters can be found in Managed Object

Model RBS.

3.1 Introduced Parameters

Table 2 describes the parameters introduced by the feature.

Table 2 Introduced Parameters

Parameter Description
(1)
SharedNetworkSupportId Value component of the RDN
featureStateSharedNetworkS Activates or deactivates the Shared Network Support licensed
upport feature
The value is irrelevant when a valid license key is not installed
for the feature.
keyIdSharedNetworkSupport Product ID of the key for the Shared Network Support license
(NETSH)
licenseStateSharedNetworkS Indicates if the licensed state is ENABLED or DISABLED for the
upport Shared Network Support feature, and if a valid license key is
installed for the feature
serviceStateSharedNetworkS Indicates if the Shared Network Support feature is operable or
upport inoperable
allowedPlmnList Lists all PLMN IDs allowed for this frequency relation
This parameter exists in the following MOs:

• EUtranFreqRelation
• UtranFreqRelation
• GeranFreqGroupRelation
servedPlmnListLTERelated Lists the PLMN IDs served by the MME
servedPlmnListOtherRATs Lists PLMN IDs served by the MME for radio technologies other
than LTE
mmeGIListLTERelated MME group ID for LTE
mmeCodeListLTERelated MME code for LTE
mmeCodeListOtherRATs MME code for radio technologies other than LTE
nnsfMode Mode used by the RBS for the non-access stratum node selection
additionalPlmnReservedList Indicates if the list of PLMN IDs in the cellt are reserved for
operator use
additionalPlmnList Lists additional PLMN IDs supported in the cell

93/1553-HSC 105 50/1-V1 Uen F | 2013-08-26 11

 Shared LTE RAN

Parameter Description
activePlmnList Lists the PLMN IDs served by at least one MME
activePlmnList Lists the PLMN IDs of the external E-UTRAN cell

(1) Relative Distinguished Name

3.2 Affected Parameters

Table 3 describes the parameters affected by the feature.

Table 3 Affected Parameters

Parameter Description
includeInSystemInformation States whether the referred cell is included in system information
This parameter exists in the following MOs:

• EUtranCellRelation
• CDMA2000CellRelation

12 93/1553-HSC 105 50/1-V1 Uen F | 2013-08-26

 Network Impact

4 Network Impact

This section describes how the Shared LTE RAN feature impacts the network
functions and capabilities.

4.1 Mobility
This section provides information on the impact of the feature on mobility.

In the Shared LTE RAN feature, UE mobility can be extended with appropriate
configuration by the operator, for example the UE can be handed over from
network belonging to one operator to that belonging to another operator.

93/1553-HSC 105 50/1-V1 Uen F | 2013-08-26 13

 Shared LTE RAN

14 93/1553-HSC 105 50/1-V1 Uen F | 2013-08-26

 Associated Features and Affected Functions

5 Associated Features and Affected

Functions

This section describes how the Shared LTE RAN feature affects other features
and functions.

5.1 Prerequisite Features

This feature has no prerequisite features.

5.2 Affected Features

This feature affects no other feature.

5.3 Related Features

Table 4 lists features that are related to the Shared LTE RAN feature.

Table 4 Related Features

Feature Description
Idle Mode Support The Idle Mode Support feature enables the UE in idle mode to access the
network and be reached from the network within acceptable delay.
Coverage-Triggered The Coverage-Triggered Inter-Frequency Session Continuity feature manages
Inter-Frequency Session the redirection of UE in RRC_CONNECTED mode towards a different LTE
Continuity frequency when the UE measures poor coverage in the current LTE frequency.
Coverage-Triggered The Coverage-Triggered CDMA-eHRPD Session Continuity feature manages
CDMA-eHRPD Session the redirection of UE in RRC_CONNECTED mode towards a CDMA-eHRPD
Continuity network when the UE measures poor coverage in the current LTE frequency.
Coverage-Triggered The Coverage-Triggered WCDMA Session Continuity feature manages the
WCDMA Session redirection of UE in RRC_CONNECTED mode towards a WCDMA network
Continuity when the UE measures poor coverage in the current LTE frequency.
Coverage-Triggered The Coverage-Triggered GERAN Session Continuity feature manages the
GERAN Session redirection of UE in RRC_CONNECTED mode towards a GERAN network
Continuity when the UE measures poor coverage in the current LTE frequency.

5.4 Affected System Functions

This feature affects no system functions.

93/1553-HSC 105 50/1-V1 Uen F | 2013-08-26 15

 Shared LTE RAN

16 93/1553-HSC 105 50/1-V1 Uen F | 2013-08-26

 Performance

6 Performance

This section describes performance indicators, counters, and events associated

with the Shared LTE RAN feature.

6.1 KPIs
This feature has no associated Key Performance Indicators (KPIs).

6.2 Counters
Table 5 lists the important counters associated with the Shared LTE RAN
feature.

Table 5 Counters
Counter Description
pmPdcpVolDlDrbTransPlmn0 Total volume (PDCP SDU) on data radio bearers (1)that has been
transmitted in the downlink direction in the PDCP layer for
PLMN0
PLMN0 refers to the PLMN configured in the ENodeBFuncti
on.eNodeBPlmnId attribute.
pmPdcpVolDlDrbTransPlmn1 Total volume (PDCP SDU) on data radio bearers that has been
transmitted in the downlink direction in the PDCP layer for PLMN1
PLMN1 refers to the PLMN configured in the attribute
additionalPlmnList[0] located on the EUtranCellFDD MO.
pmPdcpVolDlDrbTransPlmn2 Total volume (PDCP SDU) on data radio bearers that has been
transmitted in the downlink direction in the PDCP layer for PLMN2
PLMN2 refers to the PLMN configured in the attribute
additionalPlmnList[1] located on the EUtranCellFDD MO.
pmPdcpVolDlDrbTransPlmn3 Total volume (PDCP SDU) on data radio bearers that has been
transmitted in the downlink direction in the PDCP layer for PLMN3
PLMN3 refers to the first PLMN configured in the attribute
additionalPlmnList[2] located on the EUtranCellFDD MO.
pmPdcpVolDlDrbTransPlmn4 Total volume (PDCP SDU) on data radio bearers that has been
transmitted in the downlink direction in the PDCP layer for PLMN4
PLMN4 refers to the first PLMN configured in the attribute
additionalPlmnList[3] located on the EUtranCellFDD MO.

93/1553-HSC 105 50/1-V1 Uen F | 2013-08-26 17

 Shared LTE RAN

Counter
pmPdcpVolDlDrbTransPlmn5
pmPdcpVolDlDrbTransPlmn6
Description
Total volume (PDCP SDU) on data radio bearers that has been
transmitted in the downlink direction in the PDCP layer for PLMN5
PLMN5 refers to the first PLMN configured in the attribute
additionalPlmnList[4] located on the EUtranCellFDD MO.
Total volume (PDCP SDU) on data radio bearers that has been
transmitted in the downlink direction in the PDCP layer for PLMN6
PLMN6 refers to an unexpected PLMN, that is, a PLMN
that cannot be associated with any PLMN configured in the
ENodeBFunction or cell.

(1) Packet Data Convergence Protocol

6.3 Events
Table 6 lists the important events associated with the Shared LTE RAN feature.

Table 6 Events
Event Event Parameter Description
INTERNAL_PROC_INITIA EVENT_PARAM_SERVINGPLMNID Serving PLMN of the UE based
L_CTXT_SETUP on the S1AP INITIAL CONTEXT
SETUP REQUEST message
INTERNAL_PROC_HO_PRE EVENT_PARAM_SERVINGPLMNID Serving PLMN of the UE based on
P_S1_IN the S1AP HANDOVER REQUEST
message
INTERNAL_PROC_HO_PRE EVENT_PARAM_SERVINGPLMNID Serving PLMN of the UE based on
P_X2_IN the X2AP HANDOVER REQUEST
message
INTERNAL_PROC_S1_SET EVENT_PARAM_MMENAME Serving PLMN of the UE based on
UP the X2AP HANDOVER REQUEST
message
INTERNAL_PROC_S1_SET EVENT_PARAM_S1_SETUP_RESU Remove the following cause values:
UP LT
EVENT_VALUE_GUGI_MISMATC
H_PROTOCOL_ERROR
EVENT_VALUE_PLMN_MISMATC
H_PROTOCOL_ERROR
Add the following cause value:
EVENT_VALUE_MAX_GUGI_EXC
EEDED
INTERNAL_PROC_X2_SET EVENT_PARAM_X2_SETUP_RESU Remove the following cause value:
UP LT
EVENT_VALUE_GUGI_MISMATC
H

18 93/1553-HSC 105 50/1-V1 Uen F | 2013-08-26

 O&M Information

7 O&M Information

This section provides Operation and Maintenance (O&M) information for the
Shared LTE RAN feature.

A license and parameter settings activate the Shared LTE RAN feature. Details
of the license activation process can be found in License Management

General information about configuration activities can be found in Radio

Network.

93/1553-HSC 105 50/1-V1 Uen F | 2013-08-26 19