Nokia Lte Mocn

LTE MOCN
Nokia NPO
1 © 2018 Nokia LTE MOCN

AGENDA
▪ Network Architecture
▪ RAN Sharing Configuration Example
▪ LTE MOCN Features
1. LTE4 – Multi Operator Core Network
2. LTE2 – S1 Flex
3. LTE1382 – Cell Resource Groups
▪ Parameter Configuration
2 © 2018 Nokia
AGENDA
2. LTE2 – S1 Flex
3 © 2018 Nokia
Network Architecture
4 © 2018 Nokia
Network Architecture
HSS
NT-HLR CS Domain/
PSTN
S6a
NB RNC
Iu-PS MGCF
UE
3G Domain SGSN
SGs
Rx
Gn Mw Mw
PCRF
Gn Gx
S1-mme
S11
4G Domain MME Gm IMS
Gm/s1-u
eNB SAE-GW IM-MGW

UE
RAN Sharing – Radio and IP Configuration Example
OSS/NetAct ToP EPC
Cloud Load Sharing
Mode
MME-A
PLMN 01
PLMN 07
eNB Radio and Routing MME-B

LNCEL PLMN 01
VLAN3 PLMN 07
MCC
LNCEL VLAN4
MNC01 M S MME-C
MCC EPC
UE Further C PLMN 01
GW
PLMN
MNC07 VLAN1 PLMN 07
MNC01
U S-GW1
LNMME VLAN2
10.X.X.X
MME1 PLMN 01 GW
VLAN A/B 10.10.X.X
PLMN 07 DST DST IP Range Sub GW S-GW2 1
eNB IP Routing
C:10.10.10.1 10.10.X.X
Configuration
10.X.X.X VLAN1 MME-A 10.X.X.X 24

MME-B 2
10.X.X.X 24
eNB IP
MME2 PLMN 01 U:10.10.10.2 10.10.X.X
Table
VLAN2 MME-C
PLMN 07 S-GW- 10.10.X.X 24 S-GWx 3
M:10.10.10.3 VLAN3 A A/B 10.10.X.X
10.X.X.X S-GW-n 10.10.X.X 24 n
UE MME3 PLMN 01 S:10.10.10.4 VLAN4
MGM &
0.0.0.0 0
MNC07 PLMN 07 S

AGENDA
2. LTE2 – S1 Flex
▪ PM Counters for MOCN
7 © 2018 Nokia
LTE MOCN Feature
8 © 2018 Nokia
LTE4 – Multi Operator Core Network
It’s a 3GPP standard for LTE network sharing by operators
▪ Feature LTE4 - Multi-Operator Core Network enables Sharing the
radio network up to 2 operators
▪ eNB radio frequency resources - spectrum

▪ Flexi multi-radio BTS equipment
▪ Transport network
▪ Feature introduce furtherPlmnIdL:
▪ New Object for the second Operator
furtherPlmnIdL (LNCEL)
Mobile country code “MCC”
Mobile network code “MNC”
Mobile network code length
9 © 2018 Nokia
With the feature LTE4 Multi-Operator Core Network
(MOCN)
▪ 2 Core Network can be connected to eNB
▪ Content of SIB1 does not only depend on database configuration but

also on the status of S1-MME links associated with Primary and Further
PLMN IDs
▪ cellReservedForOperatorUse = [notReserved/reserved]
▪ cellBarred = [notBarred/barred]
▪ plmn-IdentityList = [Primary PLMN ID, Further PLMN IDs]
▪ All enabled BTS features are available for each operator
▪ SIB1 message carries PLMN IDs of both Operators. The amount of PLMN
IDs of each Operator can be different (1 for Op.A and 5 for Op.B or 2 for
Op.A and 3 for Op.B or any other case) however in total up to 6 PLMN
IDs can be defined per cell
10 © 2018 Nokia
PLMN Selection in MOCN
▪ Each core network operator is identified by a unique PLMN ID
which consists of mobile country code (MCC) and mobile network
code (MNC).
▪ The radio network broadcasts the PLMN IDs of the available core
network operators in system information.
▪ The UE decodes the system information received from the shared
radio network and takes the PLMN IDs into account in network and
cell selection.
▪ The UE selects the PLMN ID and creates the RRC connection with
the eNB.
▪ The Attach Request message is sent to the chosen network
operator.
▪ The MME verifies that the UE is allowed to attach to the network
and according to the result, either accepts or rejects the attach
11 © 2018 Nokia
LTE2 – S1 Flex
LTE2 – S1 Flex
▪ S1-Flex feature used together with the MOCN allows to connect
one eNB to several MMEs which belongs to different Core Network
operators
▪ originally in S1-Flex feature all MMEs must belong to one operator
only
▪ in maximum configuration 16 MMEs can be connected to single eNB
▪ If more than one MME is configured per CN operator, load
balancing functionality is applied between all MMEs of this
operator
12 © 2018 Nokia
LTE1382 – Cell Resource Groups
LTE1382 – Cell Resource Group
▪ Provides PDSCH, PUSCH resources reservation at cell level, among up
to 4 Cell Resource
Groups (CRG) → each CRG represents one or more PLMN Ids
▪ reservation is realized by assigning a complete TTI to one of the Cell Resource
Groups
▪ selection of a CRG for scheduling in a TTI is done by Weighted Round Robin algorithm
according to a configured share
▪ split of resources is configurable by plmnGroupShare parameter
▪ Introduces also reservation of Admission Control resources:
▪ Admission Control resources in the cell are distributed between the Operators
according to configurable share (also plmnGroupShare is used)
For example with 50/50 split:

• each Operator has assured AC
capacity in terms of number of
Active UEs, DRBs, QCI1 users
• each Operator can use all PRBs
in every second TTI
13 © 2018 Nokia
▪ Upon introduction of Cell Resource Groups feature
Admission Control thresholds are divided between CRGs
according to plmnGroupShare value
▪ configuration of Admission Control is still based on the existing
LNCEL
parameters (e.g. maxNumActUe, maxNumActDrb,
maxGbrTrafficLimit)
with no dedicated parameters per Operator
Default values of AC: Resource split:
▪ note that maxNumRrc is not subject to split according to CRG maxNumRrc = 300 plmnGroupShare1 = 40%
feature maxNumActUe = 300 plmnGroupShare2 = 60%
as UE PLMN Id is not known at this stage maxNumActDrb = 600
maxGbrTrafficLimit = 75
▪ allocation of AC capacity for particular Operator is done
Common for both CRGs maxNumRrc = 300
based on the
share defined by plmnGroupShare parameter Operator 1 (CRG1) Operator 2 (CRG2)
▪ e.g. number of Active UEs reserved for CRG1 is calculated as: maxNumActUe = 120 maxNumActUe = 180
maxNumActDrb = 240 maxNumActDrb = 360
LNCEL:maxNumActUe × plmnGroupShareCRG1 maxGbrTrafficLimit = 30 maxGbrTrafficLimit = 45
▪ note that maximum number of Emergency Sessions is also
subject to
the resource split (addEmergencySessions ×
plmnGroupShareCRG1)
14 © 2018 Nokia
▪ Reservation can be for PDSCH and PUSCH resources for the Operators
▪ LNCEL parameter cellResourceSharingMode defines whether resource reservation applies to both PDSCH and PUSCH
(cellResourceSharingMode = DLandUL) or only to PDSCH (cellResourceSharingMode = DLonly)
▪ Resource reservation is realized by assigning a complete subframe to one of the CRGs having data to
transmit according to a WRR algorithm
▪ if a CRG has been selected for scheduling but it has no data for transmission, it is skipped → in such case other CRG
(with data) is selected for transmission in this TTI
▪ note that in a single TTI, only one CRG can be scheduled i.e. even if CRG selected for scheduling cannot use all PRBs,
those remains unused
▪ the only exceptions to that rule are done for Random Access procedure and for UL retransmission i.e. UEs are scheduled
as without the feature, then remaining resources are assigned according to the feature
The diagram shows the behavior of the feature under

ideal conditions i.e. each CRG has data to transmit in
each TTI selected for this CRG.
Following share is configured: CRG1=50%, CRG2=30%,
CRG3=20%
15 © 2018 Nokia
AGENDA
2. LTE2 – S1 Flex
16 © 2018 Nokia
Parameter Configuration
17 © 2018 Nokia
Intra frequency cell reselection, Triggering Measurements
Range and step
Abbreviated name Full name Description (In bold are current Default
field settings)
Decimal
mcc MCC in PLMN Primary Mobile Country Code of eNB
value 0..310..999
Decimal
mnc MNC in PLMN Mobile Network Code of eNB
value 0..410..999
Decimal 2..3
mncLength MNC Length in PLMN Length of MNC of eNB in digits
These are further PLMN IDs of the cell. The parameter

indicates which operators' (PLMNID) networks are
Further PLMN identity
furtherPlmnIdL available from the cell. These PLMN identities have a
list
cell scope. The primary PLMN ID has to be provided
separately for the eNB.
This parameter specifies whether the further PLMN is

furtherPlmnIdL Autonomous PLMN allowed to be autonomously removed from SIB1 in
Boolean false
> autoRemovalAllowed removal allowed case of the PLMN not supported by eNB cell
temporarily
Indicates if the cell/PLMN combination is reserved for

furtherPlmnIdL Cell reserved for operator use. Cells reserved for operator use are Not
Not Reserved/Reserved
> cellReserve operator use treated as barred by 'normal' UEs without a USIM with Reserved
AC 11 or 15 inserted.
18 © 2018 Nokia
Intra frequency cell reselection, Triggering Measurements
Range and step
Abbreviated
Full name Description (In bold are current field Default
name
settings)
furtherPlmnIdL Decimal
MCC in PLMN Primary Mobile Country Code of eNB
> mcc value 0..310..999
furtherPlmnIdL Decimal
MNC in PLMN Mobile Network Code of eNB
> mnc value 0..100..999
furtherPlmnIdL Decimal 2..3

MNC Length in PLMN Length of MNC of eNB in digits
> mncLength
Activation status of S1 This parameter indicates whether S1 Flex feature is

actS1Flex enabled/disabled enabled
flex feature enabled or disabled.
19 © 2018 Nokia
AGENDA
2. LTE2 – S1 Flex
20 © 2018 Nokia
PM Counters for MOCN
21 © 2018 Nokia
LTE1982 Additional PM-counters for MOCN-network
Counter name Description

SUM_RRC_CONN_UE_PLMN For each PLMN, to which a UE can be connected, a PLMN-specific counter (PLMN-ID)
(M8038C0) provides the sum of sampled values for measuring the number of simultaneously RRC-
Connected UEs, which are connected to this PLMN.
#LTE RAN Sharing The counter DENOM_RRC_CONN_UE_PLMN can be used by NetAct as a denominator to
calculate the average number of RRC-connected UEs per PLMN via
SUM_RRC_CONN_UE_PLMN/DENOM_RRC_CONN_UE_PLMN.
Notes: The UE informs the eNB during RRC connection establishment to which PLMN the
UE is connected. The PLMN may be changed during handover.
Trigger event: This counter is updated after each sampling interval (1 sec) with the
sample taken from the number of UEs in RRC_CONNECTED state, which is connected to a
specific PLMN (PLMN-ID).
Granularity: 1 sec
KPI: LTE_5842a
22 06/07/2020 © Nokia 2015 - MBB Customer Support Big Data & Network Engineering / Wojciech Wascinski
For internal use

PDCP_SDU_UDATA_VOL_DL_PLMN For each PLMN, to which a UE can be connected (3GPP TS 23.251 Network Sharing), a
(M8038C2) PLMN-specific counter (PLMN-ID) provides the PDCP SDU user data volume on the eUu
interface in downlink for UEs, which are connected to this PLMN.
#LTE RAN Sharing Notes: Only PDCP SDUs for user data are taken into account; PDCP SDUs for signaling
data are not taken into account. The UE informs the eNB during RRC connection
establishment to which PLMN the UE is connected. The PLMN may be changed during
handover.
Trigger event: This counter is updated upon the transmission of a PDCP SDU on the eUu
interface in downlink (eNB -> UE) for UEs, which are connected to a specific PLMN (PLMN-
ID).
KPI: LTE_5844a
For internal use

PDCP_SDU_SDATA_VOL_DL_PLMN For each PLMN, to which a UE can be connected (3GPP TS 23.251 Network Sharing), a
(M8038C3) PLMN-specific counter (PLMN-ID) provides the PDCP SDU signaling data volume on the
eUu interface in downlink for UEs, which are connected to this PLMN.
#LTE RAN Sharing Notes: Only PDCP SDUs for signaling data are taken into account; PDCP SDUs for user
data are not taken into account. The PDCP SDU signaling data volume of the signaling
messages "RRC Connection Request" (UE -> eNB), "RRC Connection Setup" (eNB -> UE),
and "RRC Connection Setup Complete" (UE -> eNB) is not taken into account because
the selected core network PLMN-ID is not known early enough to the eNB in the early
phase of RRC connection establishment signaling.
The UE informs the eNB during RRC connection establishment to which PLMN the UE is
connected. The PLMN may be changed during handover.
Trigger event: This counter is updated upon the transmission of a PDCP SDU on the eUu
interface in downlink (eNB -> UE) for UEs, which are connected to a specific PLMN (PLMN-
ID).
KPI: LTE_5843a
For internal use

PDCP_SDU_UDATA_VOL_UL_PLMN For each PLMN, to which a UE can be connected (3GPP TS 23.251 Network Sharing), a
(M8038C4) PLMN-specific counter (PLMN-ID) provides the PDCP SDU user data volume on the eUu
interface in uplink for UEs, which are connected to this PLMN.
#LTE RAN Sharing Notes: Only PDCP SDUs for user data are taken into account; PDCP SDUs for signaling
data are not taken into account. The UE informs the eNB during RRC connection
establishment to which PLMN the UE is connected. The PLMN may be changed during
handover.
Trigger event: This counter is updated upon the reception of a PDCP SDU on the eUu
interface in uplink (UE -> eNB) for UEs, which are connected to a specific PLMN (PLMN-
ID).
KPI: LTE_5846a
For internal use

PDCP_SDU_SDATA_VOL_UL_PLMN For each PLMN, to which a UE can be connected (3GPP TS 23.251 Network Sharing), a
(M8038C5) PLMN-specific counter (PLMN-ID) provides the PDCP SDU signaling data volume on the
eUu interface in uplink for UEs, which are connected to this PLMN.
#LTE RAN Sharing Notes: Only PDCP SDUs for signaling data are taken into account; PDCP SDUs for user
data are not taken into account. The PDCP SDU signaling data volume of the signaling
messages "RRC Connection Request" (UE -> eNB), "RRC Connection Setup" (eNB -> UE),
and "RRC Connection Setup Complete" (UE -> eNB) is not taken into account because
the selected core network PLMN-ID is not known early enough to the eNB in the early
phase of RRC connection establishment signaling.
The UE informs the eNB during RRC connection establishment to which PLMN the UE is
connected. The PLMN may be changed during handover.
Trigger event: This counter is updated upon the reception of a PDCP SDU on the eUu
interface in uplink (UE -> eNB) for UEs, which are connected to a specific PLMN (PLMN-
ID).
KPI: LTE_5845a
For internal use

SUM_ACTIVE_UE_DATA_DL_PLMN For each PLMN, to which a UE can be connected (3GPP TS 23.251 Network Sharing), a
(M8038C6) PLMN-specific counter (PLMN-ID) provides the sum of sampled values for measuring the
number of simultaneously Active UEs (with buffered user plane data in downlink) which
#LTE RAN Sharing are connected to this PLMN. The counter DENOM_ACTIVE_UE_DATA_DL_PLMN can be
used by NetAct as a denominator in order to calculate the average number of Active UEs
(with buffered user plane data in downlink) per PLMN via
SUM_ACTIVE_UE_DATA_DL_PLMN / DENOM_ACTIVE_UE_DATA_DL_PLMN.
Trigger event: This counter is updated after each sampling interval (1 millisecond) with
the sample taken from the number of Active UEs (with buffered user plane data in the
downlink), which are connected to a specific PLMN (PLMN-ID).
Granularity: 1 ms
KPI: LTE_5840a
For internal use

SUM_ACTIVE_UE_DATA_UL_PLMN For each PLMN, to which a UE can be connected (3GPP TS 23.251 Network Sharing), a
(M8038C8) PLMN-specific counter (PLMN-ID) provides the sum of sampled values for measuring the
number of simultaneously Active UEs (with buffered user plane data in uplink) which are
#LTE RAN Sharing connected to this PLMN. The counter DENOM_ACTIVE_UE_DATA_UL_PLMN can be used
by NetAct as a denominator in order to calculate the average number of Active UEs (with
buffered user plane data in uplink) per PLMN via SUM_ACTIVE_UE_DATA_UL_PLMN /
DENOM_ACTIVE_UE_DATA_UL_PLMN.
Trigger event: This counter is updated after each sampling interval (1 millisecond) with
the sample taken from the number of Active UEs (with buffered user plane data in the
uplink), which are connected to a specific PLMN (PLMN-ID).
Granularity: 1 ms
KPI: LTE_5841a
For internal use

IP_TPUT_VOL_UL_QCI{1-9}_PLMN For each PLMN, to which a UE can be connected (3GPP TS 23.251 Network Sharing), a
(M8038C10, M8038C12, M8038C14, PLMN-specific counter (PLMN-ID) provides the aggregated IP throughput volume on
M8038C16, M8038C18, M8038C20, QCI1 bearers in uplink as experienced by UEs which are connected to this PLMN.
M8038C22, M8038C24, M8038C26) The counter IP_TPUT_TIME_UL_QCI{1-9}_PLMN can be used by NetAct as a denominator
in order to calculate the average IP throughput on QCI{1-9} bearers in uplink per PLMN
#LTE RAN Sharing via IP_TPUT_VOL_UL_QCI{1-9}_PLMN / IP_TPUT_TIME_UL_QCI{1-9}_PLMN.
Trigger event: The volume of a data burst, excluding the data transmitted in the TTI,
when the buffer is emptied. A sample for ThpVolUl (Throughput Volume Uplink) is the
data volume counted on PDCP SDU level, in bits, and received in the UL for one E-RAB
during a sample of ThpTimeUl (Throughput Time Uplink).
KPI: LTE_5856a – LTE_5864
For internal use

IP_TPUT_TIME_UL_QCI{1-9}_PLMN For each PLMN, to which a UE can be connected (3GPP TS 23.251 Network Sharing), a
(M8038C11, M8038C13, M8038C15, PLMN-specific counter (PLMN-ID) provides the aggregated IP throughput time for QCI1
M8038C17, M8038C19, M8038C21, bearers in uplink for UEs which are connected to this PLMN.
M8038C23, M8038C25, M8038C27) The counter IP_TPUT_TIME_UL_QCI{1-9}_PLMN can be used by NetAct as a denominator
in order to calculate the average IP throughput on QCI{1-9} bearers in uplink per PLMN
#LTE RAN Sharing via IP_TPUT_VOL_UL_QCI{1-9}_PLMN / IP_TPUT_TIME_UL_QCI{1-9}_PLMN.
Trigger event: The time to transmit a data burst, excluding the last piece of data
transmitted in the TTI, when the buffer for a QCI{1-9} E-RAB is emptied.
KPI: LTE_5856a – LTE_5864a
For internal use

IP_TPUT_VOL_DL_QCI{1-9}_PLMN For each PLMN, to which a UE can be connected (3GPP TS 23.251 Network Sharing), a
(M8038C28, M8038C30, M8038C32, PLMN-specific counter (PLMN-ID) provides the aggregated IP throughput volume on
M8038C34, M8038C36, M8038C38, QCI1 bearers in downlink as experienced by UEs which are connected to this PLMN.
M8038C40, M8038C42, M8038C44) The counter IP_TPUT_TIME_DL_QCI{1-9}_PLMN can be used by NetAct as a denominator
in order to calculate the average IP throughput on QCI{1-9} bearers in downlink per
#LTE RAN Sharing PLMN via IP_TPUT_VOL_DL_QCI{1-9}_PLMN / IP_TPUT_TIME_DL_QCI{1-9}_PLMN.
Trigger event: The volume of a data burst, excluding the data transmitted in the TTI,
when the buffer is emptied. A sample for ThpVolDl (Throughput Volume Downlink) is the
data volume counted on PDCP SDU level, in bits, and was successfully transmitted
(acknowledged by the UE) in the DL for one E-RAB during a sample of ThpTimeDl
(Throughput Time Downlink).
For internal use

IP_TPUT_TIME_DL_QCI{1-9}_PLMN For each PLMN, to which a UE can be connected (3GPP TS 23.251 Network Sharing), a
(M8038C29, M8038C31, M8038C33, PLMN-specific counter (PLMN-ID) provides the aggregated IP throughput time on QCI1
M8038C35, M8038C37, M8038C39, bearers in downlink as experienced by UEs which are connected to this PLMN.
M8038C41, M8038C43, M8038C45) The counter IP_TPUT_TIME_DL_QCI{1-9}_PLMN can be used by NetAct as a denominator
in order to calculate the average IP throughput on QCI{1-9} bearers in downlink per
#LTE RAN Sharing PLMN via IP_TPUT_VOL_DL_QCI{1-9}_PLMN / IP_TPUT_TIME_DL_QCI{1-9}_PLMN.
Trigger event: The time to transmit a data burst, excluding the last piece of data
transmitted in the TTI, when the buffer for a QCI{1-9} E-RAB is emptied.
For internal use

Nokia Lte Mocn

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Nokia Lte Mocn

Uploaded by

Copyright:

Available Formats

LTE MOCN

1 © 2018 Nokia LTE MOCN

eNB SAE-GW IM-MGW

eNB Radio and Routing MME-B

10.X.X.X VLAN1 MME-A 10.X.X.X 24

MME2 PLMN 01 U:10.10.10.2 10.10.X.X

6 © 2018 Nokia LTE MOCN

▪ eNB radio frequency resources - spectrum

▪ New Object for the second Operator

▪ Content of SIB1 does not only depend on database configuration but

For example with 50/50 split:

The diagram shows the behavior of the feature under

These are further PLMN IDs of the cell. The parameter

This parameter specifies whether the further PLMN is

Indicates if the cell/PLMN combination is reserved for

furtherPlmnIdL Decimal 2..3

Activation status of S1 This parameter indicates whether S1 Flex feature is

Counter name Description

Counter name Description

Counter name Description

Counter name Description

Counter name Description

Counter name Description

Counter name Description

Counter name Description

KPI: LTE_5856a – LTE_5864

Counter name Description

KPI: LTE_5856a – LTE_5864a

Counter name Description

KPI: LTE_5847a – LTE_5855a

Counter name Description

KPI: LTE_5847a – LTE_5855a

You might also like