RRM.

2544 TEST CASE DESCRIPTION

All rights reserved

LTE 4: MOCN, LTE-RAN sharing, Lab

Purpose: The purpose of this case is to verify multiple operator core network
activation when eNB is connected to more than one MME with different
PLMN

Abstract: LTE4 is introduced in RL25 to enable MOCN. In this scenario, one

eNB is equipped with 3 sectors (sector 1, 2, 3) and can be
connected to 2 MMEs at the same time. MME1’s PLMN is 262xx
and MME2’s PLMN is 262yy. Ue1 is connected to sector 1 and
attach to MME1, meanwhile UE2 is connected to sector 1 (the same
sector as UE1) but attached to MME2. With this scenario, two
different network operators owning their own MME can share the
usage of one eNB (shared RAN) but still using their own MME.

Related LTE 4:MOCN

Features: LTE2: S1 Flexi

Related 3GPP TS 36.101 - User Equipment (UE) radio transmission and

specifications: reception
3GPP TS 36.104 - Base Station (BS) radio transmission and
reception
3GPP TS 36.211 - Physical channels and modulation
3GPP TS 36.213 - Physical layer procedures
3GPP TS 36.321 - Medium Access Control (MAC) protocol
specification
3GPP TS 36.322 - Radio Link Control (RLC) protocol specification
3GPP TS 36.300 - Overall description; Stage 2
3GPP TS 36.401 - Architecture description

Related Nokia Siemens Networks LTE Radio Access, Rel. RL25, Operating
documents: Documentation ,feature LTE4

Prerequisites: Required Network Elements / Amount

Equipment
eNB 1
MME 2
SAE-GW 2
UE (for data transfer) 2
Application PC (UE side) with all 2
automatic updates (Windows patches,
virus scanner updates etc.) switched
off. Installed applications:
• Iperf
Application PC (Core side) with all 2

RRM.2544 LTE 4: MOCN, LTE-RAN sharing, Lab.doc Page 1 of 11

 RRM.2544 TEST CASE DESCRIPTION
All rights reserved

automatic updates (Windows patches,

virus scanner updates etc.) switched
off. Installed applications:
• Iperf

RRH –FZHA 3

Additional
information:

RRM.2544 LTE 4: MOCN, LTE-RAN sharing, Lab.doc Page 2 of 11

 RRM.2544 TEST CASE DESCRIPTION
All rights reserved

1. Test Configuration

Network elements, instrumentation and terminals configuration

Figure A: LTE/SAE network overview and interfaces

Evolved UTRAN (E-UTRAN) Evolved Packet Core (EPC) S7

Rx
PCR
F
+
HSS
S5/S8
SG PDN
MM i
E
S-GW SAE PDN
HSS
Application
S6a server
S10 S7
MM
Evolved E Rx+
Node B S1-MME PCRF
LTE-UEs
(eNB)
UE 1 S11
S1-U S5/S8 SGi
Cell 1 PDN

LTE-Uu SAE PDN

S-GW Application
server

RRM.2544 LTE 4: MOCN, LTE-RAN sharing, Lab.doc Page 3 of 11

 RRM.2544 TEST CASE DESCRIPTION
All rights reserved

2. Setup / Test Preparation & Background Information

2.1 Background Information

MOCN - S1 setup
• MME send S1-setup message should include below infomation(P2.1.1):
• PLMN ID
• MME group ID
• MME code
• MME relative capacity
Detail information as below:
ASN1START

RRCConnectionRequest ::= SEQUENCE {

criticalExtensions CHOICE {
rrcConnectionRequest-r9 RRCConnectionRequest-r9-IEs,
criticalExtensionsFuture SEQUENCE {}
}
}

RRCConnectionRequest-r9-IEs ::= SEQUENCE {

ue-Identity InitialUE-Identity,
establishmentCause EstablishmentCause,
spare BIT STRING (SIZE (1))
}

InitialUE-Identity ::= CHOICE {

s-TMSI S-TMSI,
randomValue BIT STRING (SIZE (40))
}

EstablishmentCause ::= ENUMERATED {

emergency, highPriorityAccess, mt-Access, mo-
Signalling,
mo-Data, spare3, spare2, spare1}

-- ASN1STOP

RRCConnectionRequest field descriptions

ue-Identity
UE identity included to facilitate contention resolution by lower layers.
establishmentCause
Provides the establishment cause for the RRC connection request as provided by the upper layers. W.r.t. the cause
value names: highPriorityAccess concerns AC11..AC15, ‘mt’ stands for ‘Mobile Terminating’ and ‘mo’ for ‘Mobile
Originating.
randomValue
Integer value in the range 0 to 240 − 1.

MOCN - RRC connection message

RRC connection request and RRC connection setup complete messages should
include below information(P2.1.2):
RRC connection request message
• S-TMSI
• MME code

RRM.2544 LTE 4: MOCN, LTE-RAN sharing, Lab.doc Page 4 of 11

 RRM.2544 TEST CASE DESCRIPTION
All rights reserved

RRC connection setupcomplete message

• Selected PLMN identity
• Registered MME
• PLMN
• MME group ID
• MME code
-- ASN1START

RRCConnectionSetupComplete ::= SEQUENCE {

rrc-TransactionIdentifier RRC-TransactionIdentifier,
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionSetupComplete-r9 RRCConnectionSetupComplete-r9-IEs,
spare3 NULL, spare2 NULL, spare1 NULL
},
criticalExtensionsFuture SEQUENCE {}
}
}

RRCConnectionSetupComplete-r9-IEs ::= SEQUENCE {

selectedPLMN-Identity INTEGER (1..6),
registeredMME RegisteredMME OPTIONAL,
dedicatedInfoNAS DedicatedInfoNAS,
nonCriticalExtension SEQUENCE {} OPTIONAL
}

RegisteredMME ::= SEQUENCE {

plmn-Identity PLMN-Identity OPTIONAL,
mmegi BIT STRING (SIZE (16)),
mmec MMEC
}

-- ASN1STOP

RRCConnectionSetupComplete field descriptions

selectedPLMN-Identity
Index of the PLMN selected by the UE from the plmn-IdentityList included in SIB1. 1 if the 1st PLMN is selected from
the plmn-IdentityList included in SIB1, 2 if the 2nd PLMN is selected from the plmn-IdentityList included in SIB1 and so
on.
registeredMME
This field is used to transfer the GUMMEI of the MME where the UE is registered, as provided by upper layers.
mmegi
Provides the Group Identity of the registered MME within the PLMN, as provided by upper layers, see TS 23.003 [27].

MOCN - MME Selection Scenarios

RRM.2544 LTE 4: MOCN, LTE-RAN sharing, Lab.doc Page 5 of 11

 RRM.2544 TEST CASE DESCRIPTION
All rights reserved

Use Cases Parameters by UE MME Selection (without error cases)

Attach selectedPLMN-Identity Select one of the MMEs that contain selectedPLMN-

Identity in the first list of Served PLMN Ids via load
balancing.
Service selectedPLMN-Identity & Select MME that contains mmec of S-TMSI in set of
Request S-TMSI Served GUMMEIs.
Detach Note: service request always without TAU

Tracking Area Update (TAU)

TAU – selectedPLMN-Identity & Select MME that contains mmec of S-TMSI in set of
periodical (no S-TMSI Served GUMMEIs.
TA change)
TAU – new selectedPLMN-Identity & Select MME that contains GUMMEI (=registeredMME)
TA & old registeredMME (w/o in list of Served GUMMEIs
PLMN plmn-Identity)
If no such MME can be found, select one of the MMEs
that contain selectedPLMN-Identity in first list of Served
PLMN Ids via load balancing
TAU – new selectedPLMN-Identity & Select MME that contains registeredMME with old
TA & new registeredMME (with plmn-Identity) in set of Served GUMMEIs.
PLMN plmn-identity)
If no such MME can be found, select one of the MMEs
that contain selectedPLMN-Identity in first list of Served
PLMN Ids via load balancing.
TAU – for selectedPLMN-Identity Select one of the MMEs that contain selectedPLMN-
MME load Identity in the first list of Served PLMN Ids via load
balancing balancing.
Note: The eNB shall support the MME Selection for up to 16 MMEs.

2.2 Setting O&M Parameters

RRM.2544 LTE 4: MOCN, LTE-RAN sharing, Lab.doc Page 6 of 11

 RRM.2544 TEST CASE DESCRIPTION
All rights reserved

This
parameter
holds the
transport
network IP
address of
the Mobility
Management
Entity (MME)
Primary IP address of main primary 7...15
MME mainMmeIpAddrPrim interface characters -
This
parameter
holds the
transport
network IP
address of
the Mobility
Management
Entity (MME)
Secondary IP address of main secondary 7...15
MME mainMmeIpAddrSec interface characters -
MME Code
contained in
main
GUMMEI of
the Main 0...255, step
Main code of main MME mainMmeMainCode MME 1 -
Group Id
contained in
main
GUMMEI of
the Main 0...65535,
Main group id of main MME mainMmeMainGroupId MME step 1 -
Mobile
Country
Code
contained in
main
GUMMEI of
the Main 0...999, step
Main MCC of main MME mainMmeMainMcc MME 1 -
Mobile
Network
Code
contained in
main
GUMMEI of
the Main 0...999, step
Main MNC of main MME mainMmeMainMnc MME 1 -
Length of
Main Mobile
Network
Length of main MNC of main Code of the
MME mainMmeMainMncLength Main MME 2...3, step 1 -

RRM.2544 LTE 4: MOCN, LTE-RAN sharing, Lab.doc Page 7 of 11

 RRM.2544 TEST CASE DESCRIPTION
All rights reserved

List of
transport
network Ip
Addresses
(IPv4) of up
to 15 further
MMEs in
addition to
the Main
MME IP address list mmeIpAddressList MME

This
parameter
holds the
transport
network IP
address of
the Mobility
Management
Entity (MME)
primary 7...15
Primary MME IP address mmeIpAddrPrim interface characters -

Support
Activation status of S1 flex status of S1 disabled (0),
feature actS1Flex Flex feature. enabled (1) enabled (1)

For a complete list of configurable parameters, see the PDDB.

Link as below: (NSN only)
http://pddb.inside.nokiasiemensnetworks.com/pddb/login.do

eNode B configuration

TxDiv can be enabled in a cell by setting the following O&M parameter:

 TxDiv (2), to be configured with BTS Site Manager

RRM.2544 LTE 4: MOCN, LTE-RAN sharing, Lab.doc Page 8 of 11

 RRM.2544 TEST CASE DESCRIPTION
All rights reserved

In this testcase the bandwith is set to 20 Mhz.

TDD frame config 1 SFF 7
MME 1 PLMN =262xx
MME 2 PLMN =262yy
MME 1 is primary MME
MME 2 is secondary MME

3. Test Execution / Implementation

Preconditions:

• All NEs of the LTE/SAE system (eNBs, MME, SAE-GW) are running.
• Tracing S1 log with WireShark
• eNB connect with two MME and S1-setup message complete
• Cell Onair and SIB1 messages include MME1 and MME2 information

Radio Aspects

During the test the UE is placed in a location with good SINR value. The table here
gives an overview about the classifications of SINR.

Signal Conditions SINR (dB) RSRP (dBm)

Very Good > 30 -70
Good 20 .. 25 - 80
Average 10 .. 15 - 90
Poor 0 .. 5 - 100

Table: SINR ranges and conditions.

In the following sequence the use of iperf is described for generating the data traffic.
Nevertheless, this is only meant as an example. The use of any other tool (Filezilla,
DOS FTP etc.) is acceptable as well.

RRM.2544 LTE 4: MOCN, LTE-RAN sharing, Lab.doc Page 9 of 11

 RRM.2544 TEST CASE DESCRIPTION
All rights reserved

Step 1:

Attach UE1 to the network

UE1 is attached in the Cell center with the PLMN 262xx and performs the DL
UDP throughput

Expected Result / Output

The UE1 is attached successfully and DL data transfer can reach 40Mbps

Check blow information from S1 log:

eNB sent UE1 attach request message to MME1
Attach process is complete.

Step 2:

UE2 attach

UE2 is attached in the Cell center with the PLMN 262yy(same RSRP and
SINR with UE1)and performs the DL UDP throughput

Expected Result / Output

The UE2 is attached successfully, UE1 and UE2 share 100PRBs resource.
UE1=20Mbps UE2=20Mbps

Check blow information from S1 log:

eNB sent UE2 attach request message to MME2
Attach process is complete.

Step 3:

Detach both UEs

After UE2 performs DL data traffic for 5 minutes, detach UE1 and UE2.

Expected Result / Output

UE can be detached successfully

4. Related Message Flow

n.a.

5. Epilogue

RRM.2544 LTE 4: MOCN, LTE-RAN sharing, Lab.doc Page 10 of 11

 RRM.2544 TEST CASE DESCRIPTION
All rights reserved

After finishing the test case please place back all changes done at databases in the
network-entities to the initial or default values.

The information in this document is subject to change without notice and describes only the product
defined in the introduction of this documentation. This document is intended for the use of Nokia
Siemens Networks customers only for the purposes of the agreement under which the document is
submitted, and no part of it may be reproduced or transmitted in any form or means without the prior
written permission of Nokia Siemens Networks. The document has been prepared to be used by
professional and properly trained personnel, and the customer assumes full responsibility when using
it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous
development and improvement of the documentation.

Nokia Siemens Networks liability for any errors in the document is limited to the documentary
correction of errors. NOKIA SIEMENS NETWORKS WILL NOT BE RESPONSIBLE IN ANY EVENT
FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR
CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this
document or the information in it.
This document and the product it describes are considered protected by copyright according to the
applicable laws.
Technical specifications, performance values and features are binding only insofar as they are
specifically and expressly agreed upon in a written contract.

NOKIA Siemens Networks logo is a registered trademark of Nokia Siemens Networks GmbH & Co
KG.
Other product names mentioned in this document may be trademarks of their respective companies,
and they are mentioned for identification purposes only.

RRM.2544 LTE 4: MOCN, LTE-RAN sharing, Lab.doc Page 11 of 11