0% found this document useful (0 votes)
343 views44 pages

N26 Interworking Config Steps Ver 1.0

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
343 views44 pages

N26 Interworking Config Steps Ver 1.0

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 44

Modular Private Wireless

Release: MPW23-UR1

Feature configuration manual:


N26-Interworking (Data Only)

Author Vineet Awasthy, Janos Szamoskozi


Approver
Status: Initial Version
Document location
Organization CNS_ECE Sol MPS
Document ID
Document Type Nokia Internal Use
Version 1.0
1

1. Table of Content

Contents
1. Table of Content ..................................................................................................................... 1
2. Feature overview ................................................................................................................... 3
3. UE Capability .......................................................................................................................... 5
4. Feature Activation on eNB ..................................................................................................... 7
4.1. LTE to NR (5G-SA) interRAT HO 4G configuration............................................................ 7
4.1.1. LTE BTS level NR cell adjacency (LNADJN/LNADJNL) ..................................................... 7
4.1.2. LTE Cell level NR cell adjacency (LNRELN) ........................................................................ 9
4.1.3 A2, A1 events and timer related parameters (LNCELL) ................................................. 10
4.1.4 NR target cell parameters including B2 event (LNHON) ................................................ 11
4.1.5 NR measurement Default Profile configuration (NRMEASDPR) ................................... 13
4.1.6 Mobility Default Profile configuration (MODPR) ............................................................. 13
4.1.7 Feature activation on 4G side and eNB timer parameters (LNBTS) ............................. 14
4.2 NR (5G-SA) to 4G interRAT HO 4G configuration (LNBTS) ................................................ 15
4.3 Found SRAN SW bug on 4G side during the IRAT HO implementation ............................. 16
5 Feature activation on gNB ..................................................................................................... 17

5.1 NR (5G-SA) to LTE interRAT HO 5G configuration............................................................ 17


5.1.1 Feature activation on 5G side and gNB timer parameters (NRBTS) ............................ 17
5.1.2 A2 and A1 events and timer related parameters (NRCELL)........................................... 18
5.1.3 LTE target cell parameters including B2 event (NRHOIR).............................................. 21
5.1.4 NRBTS level LTE cell adjacency (NRADJECELL)................................................................ 23
5.1.5 NR cell level LTE cell adjacency (NRRELE) ......................................................................... 24
5.1.6 New Radio Performance Management (NRPMRNL) ........................................................ 24
6 CMU (5G) ................................................................................................................................ 25
6.1 AMF.............................................................................................................................. 25
6.2 SMF .............................................................................................................................. 28
6.3 UPF ............................................................................................................................... 30
6.4 5G APC: UDM/UDR ....................................................................................................... 31
7 CMU-(4G) ................................................................................................................................ 34
7.1 MME ............................................................................................................................ 34

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
2

7.2 SGW ............................................................................................................................. 36


7.2.1 Create loopback interface for S5, S5-U and S11 under signaling vprn ...................... 36
7.2.2 Create S5, S5-U and Sx-N4 under PDN as below............................................................ 36
7.3 4G APC: HSS/SPR........................................................................................................... 37
8 DNS ......................................................................................................................................... 38
8.1 MME AMF selection ...................................................................................................... 38
8.2 MME AMF selection ...................................................................................................... 38
8.3 AMF MME selection ...................................................................................................... 38
8.4 AMF MME selection ...................................................................................................... 38
8.5 Sample DNS configuration ............................................................................................. 39
9 Precheck ................................................................................................................................. 40
9.1 4G attach ...................................................................................................................... 40
9.2 5G PDU session establishment....................................................................................... 42
10 Troubleshooting ..................................................................................................................... 43

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
3

2. Feature overview
N26 interface is an inter-CN (Core Network) interface between the MME and 5GS AMF in order to
enable interworking between EPC and the NG core.

 The N26 interface is an inter-Core Network interface between the 4G LTE's MME and the 5G
core's 5GS AMF.
 It facilitates interworking between 4G's EPC and 5G's NG core, for mobility between LTE-EPC
and 5G-NR-5GC.
 The interface ensures seamless data continuity during inter-RAT handovers between LTE and
5G.

The feature supports N26-based interworking procedures to enable mobility between EPS and 5GS
with IP address preservation for single registration mode UEs.

PGW-C + SMF and UPF + PGW-U are dedicated for interworking between 5GS and EPC, which are
optional and are based on UE MM core network capability, UE subscription and AMF support of the
N26 interface.

Fig-1: N26 Interworking: High level Architecture

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
4

Network Elements Releases


N26 interworking feature is tested in MPW lab in MPW23_UR1 having below mentioned NE Sw release

Network Element Release


CMU 23.10.R1
CMM- MME CMM23.8.0.2
CMM- AMF CMM23.8.0.2
SMF/UPF/SGW 23.8.R2
DNS BIND9
APC-4G (HSS/PCRF) 22-9-pp4
APC-4G (UDM/AUSF) 22-9-pp4
eNB 23.R3
gNB 23.R3

Table-1: Network Element Release

Below mentioned procedures (including Mobility) were verified in MPW23_UR1 for data only.

 LTE attach using ‘Combo-SMF+PGW’ (UE capability 4G only)


 5G registration using ‘Combo-SMF+PGW’ (UE capability 5G only)
 EPS to 5GS idle mode mobility procedure using ‘Combo-SMF+PGW’ (UE capability 4G+5G)
 5GS to EPS idle mode mobility procedure using ‘Combo-SMF+PGW’ (UE capability 4G+5G)
 LTE attach and EPS to 5GS handover procedure using ‘Combo-SMF+PGW’ (UE capability
4G+5G)
 5G Registration and 5GS to EPS handover procedure using ‘Combo-SMF+PGW’ (UE capability
4G+5G)

Note:
 It is assumed 4G CMU and 5G CMU is configured with basic configuration to have a successful
4G attach and 5G PDU session establishment. Configuration related to Mobility is covered in
this document.
 External DNS is used for name resolution.

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
5

3. UE Capability
For Feature verification in MPW lab, we used Nokia-XR-20 with Android 12

Make sure:

 5G SA is enabled on UE.
 Select “preferred network type” as “NR/LTE” under test menu (*#*#4636#*#*)

 Select “SA” or “SA+NSA” as “preferred 5G NR mode” under developer settings.

or

 For 4G to 5G-SA IRAT HO the UE needs to have explicitly


capable for (TS 36.331):

When CB007742 feature is activated and configured in the

eNB (and in the source LTE Cell, meaning inter-RAT HO


fromLTE to 5G SA can be triggered from dedicated LTE Cell

perspective), eNB requires to have NR container of UE


RadioCapabilities.

Therefore, if the UE enters LTE Cell wherefrom inter-RAT


HOfrom LTE to 5G SA is possible to be triggered (meaning

CB007742 is activated and configured), eNB will request


theUE to provide NR container of UE Radio Capabilities via

RRC:UeCapabilityEnquiry

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
6

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
7

4. Feature Activation on eNB


4.1. LTE to NR (5G-SA) interRAT HO 4G configuration

4.1.1. LTE BTS level NR cell adjacency (LNADJN/LNADJNL)

arfcnValueNR practically the related 5G-SA cell’s arfcnSsbPbch value.

multiFrequencyBandList all the potential target NR bands need to be listed here. In the gNB
side the freqBandIndicatorNR parameter declares the NR band in use
on NRCELL level.

physCellIdNr practically the related 5G-SA cell’s physCellId value (PCI).

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
8

cellIdentity practically the related 5G-SA cell’s nrCellIdentity value.

Note: nrCellIdentity value is a cumulated one, if NRBTS ID is being changed, then this value
will be changed as well, moreover it may result this value to be changed by some other 5G
parameter(s) change either.

gnbIdLength practically the related gNB’s gNbIdLength value.

mcc, mnc, mncLength and trackingAreaCodeNR have to be given in-line with the settings of the
target 5G-SA cell.

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
9

4.1.2. LTE Cell level NR cell adjacency (LNRELN)

cellIdentity must be in-line with the related 5G-SA cell’s nrCellIdentity value.

Note: nrCellIdentity value is a cumulated one, if NRBTS ID is being changed, then this value
will be changed as well, moreover it may result this value to be changed by some other 5G
parameter(s) change either.

mcc, mnc and mncLength have to be given in-line with the settings of the target 5G-SA cell.

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
10

4.1.3 A2, A1 events and timer related parameters (LNCELL)

measQuantityNr: RSRP Defines which measurement quantity (RSRP or RSRQ)


of the 5G SA neighbor cell the UE has to use for
triggering B2-NR measurement reporting.

threshold2NR: -100dBm* Threshold for RSRP of serving cell for start of


coverage-based HO NR Measurements If the value is
equal to or below threshold2NR (event A2), coverage-
based HO NR measurements are started.

hysThreshold2NR: 0dB Related Hysteresis of Threshold for RSRP of serving


cell for start of coverage-based 5G SA HO
measurements
Parameter is used within the entry and leave condition
of the A2 triggered reporting condition.

a2TimeToTriggerActNRMeas: 320ms Time-to-trigger for event A2

threshold2a: -96dBm* Threshold for RSRP of serving cell for stopping of


Inter-RAT (InterFreq) Measurements
Threshold for RSRP of serving cell. If Inter-RAT
(InterFreq) measurements are active and value
exceeds Th2a (event A1) then Inter-RAT
measurements are stopped.

hysThreshold2a: 2dB Related Hysteresis of Threshold for RSRP of serving


cell for stopping of Inter-RAT (InterFreq)
Measurements.

a1TimeToTriggerDeactInterMeas: 480ms Time to trigger deactivating all measurements.


Duration for which the event A1 must be valid, that
results Inter-Frequency/Inter-RAT measurements are
being deactivated.

t304InterRATN: 500ms This timer value is used by eNodeB internally to


estimate the time the UE may spend accessing to
target NR system after receiving RRC:MOBILITY FROM
EUTRAN COMMAND before starting RRC Re-
Establishment.

Very important to set actAutoPucchAlloc=true in LNCEL_TDD or LNCEL_FDD object moreover


APUCCH_TDD or APUCCH_FDD MOs must be created accordingly on the 4G target cell side! This is
related to the found bug described in 4.3.

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
11

4.1.4 NR target cell parameters including B2 event (LNHON)

The below example is related to RSRP only triggering:

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
12

b2NrBeamReportQuantity, b2NrBeamThreshRsrp, b2NrMaxNumBeamsReport

Contention Free Random Access towards 5G neighbor cell is not yet available (at least not in 23R3)
therefore these related parameters no need to be configured.

b2NrCellReportQuantity Defines which measurement quantities (RSRP/RSRQ)


of NR neighbor cell reported in an event B2-NR measurement
report by UE.

b2NrReportIntervalRsrp The RSRP based B2-NR event triggers the UE to


perform periodical reporting with the indicated interval.

b2NrTimeToTriggerRsrpMeas Time for which the specific criteria for the RSRP based
B2-NR measurement must be met in order to trigger a
measurement report.

b2Threshold1RsrpNr Threshold1 for RSRP of serving cell. If RSRP (own cell)


based B2-NR measurement is activated, when RSRP of serving
cell < b2Threshold1RsrpNr and RSRP/RSRQ of NR neighbor
cell > b2Threshold2<RSRP, RSRQ>Nr (depending on
b2NrMeasQuantity), RSRP based B2-NR event report is
triggered and handover to NR may be triggered.

b2Threshold2RsrpNr NR RSRP threshold for neighbor cell on NR frequency,


such that it is considered to be good and reported in the
measurement result of B2-NR event.

hysB2NrThresholdRsrp Hysteresis for RSRP(Own cell) based B2-NR event for


NR measurement.

carrierFreqNr Identifies the SSB frequency of NR carrier to be


measured, practically the related 5G-SA cell’s arfcnSsbPbch
value.

freqBandIndicatorListNr Target NR band need to be listed. In the gNB side


freqBandIndicatorNR parameter declares the NR band in use
on NRCELL level.

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
13

4.1.5 NR measurement Default Profile configuration (NRMEASDPR)

These are above the default settings which works, however the measGapEnabledNRMeas
could be ‘FR1Only’ because yet (23R3) the feature does not support IRAT HO to FR2 cell.

4.1.6 Mobility Default Profile configuration (MODPR)

freqLayListPsHoNR List of NR target frequencies for handover to NR-SA for UE without


VoLTE bearer. It is practically the related 5G-SA cell’s arfcnSsbPbch
value.

freqLayListPsHoNRVoLte List of NR target frequencies for handover to NR-SA for UE with VoLTE
bearer. It is practically the related 5G-SA cell’s arfcnSsbPbch value.

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
14

4.1.7 Feature activation on 4G side and eNB timer parameters (LNBTS)

actHOtoNR: True By this parameter the feature CB007742 'Handover from LTE to 5G
Option 2' can be activated and deactivated.

tS1RelOvDeltN: 1000ms Delta for Supervision Timer For The Execution Phase Of An S1
Handover to NR TS1RELOCoverallDelta_NR is used to calculate the
duration of the timer TS1RELOCoverall which is used to guard against
failure of the MME to inform the source eNB of the outcome of the
UEs attempt to connect to the target during S1 handover to another
3GPP RAT. TS1RELOCoverall is started in the source eNB when the
RRC: MOBILITY FROM EUTRA COMMAND message is sent to the UE
and is stopped when S1AP: UE CONTEXT RELEASE COMMAND is
received from the MME to confirm the outcome. If the timer expires
the handover is aborted and the UE context is released.

tS1RelPrepN: 2000ms Guard against failure of the MME to respond in preparation phase of
S1 handover to another 3GPP RAT Timer tS1relprepN is used to guard
against failure of the MME to respond preparation phase of S1
handover to another 3GPP RAT. It is started in the source eNB when
the S1AP: HANDOVER REQUIRED message is sent to the MME and is
stopped when the S1AP: HANDOVER COMMAND or S1AP:
PREPARATION FAILURE message is received in response. If the timer
expires the handover is aborted or cancelled.

Moreover, there is another important but hidden timer that stands for
supervising the S1 handover cancellation related to IRAT HO to NR.
This can only be retrieved only from the system unit’s Linux
filesystem:

Location: /ffs/fs1/swpool/OAM/vendor_816519C8.xml
tS1RelCanN <p name="tS1RelCanN">2000</p>

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
15

4.2 NR (5G-SA) to 4G interRAT HO 4G configuration (LNBTS)

actHoFromNr This parameter enables the handover feature from NR SA (5GS to EPS
handover).

actHoFromNrDlDataForward This parameter activates the feature 'Data forwarding during HO from
5G SA to LTE' (DL user data forwarding during handover from 5GS to
EPS).

rachAccessForHoFromNr This parameter selects whether target eNodeB shall provide and
reserve a dedicated RACH preamble for HO from NR SA. In case no
dedicated RACH preamble is provided UE will perform contention
based RACH access.

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
16

4.3 Found SRAN SW bug on 4G side during the IRAT HO


implementation

Please note that during the implementation MPW-S have recognized a missing PDL rule in 23R3 in 4G
BTS side that may cause improper handover function. The PDL rule is confirmed to be fixed from 24R2.

PR752098: CB007742 (actHOtoNR) related missing PDL rules in 4G BTS side

Description:

MPW team has recognized after 4G to 5G-SA inter-RAT Handover activation (CB007742 with
CB008731) the previously implemented and well-functioning 5G-SA to 4G inter-RAT Handover
(5GC00707, LTE4595) stops working with symptoms below:

Missing PDL rules to be created:

If actAutoPucchAlloc is set to 'false' in at least one LNCEL instance then actHOtoNR must be set to
'false'.

If actHOtoNR is set to 'true', then actAutoPucchAlloc must be set to 'true' in all LNCEL instances.

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
17

5 Feature activation on gNB


5.1 NR (5G-SA) to LTE interRAT HO 5G configuration

5.1.1 Feature activation on 5G side and gNB timer parameters (NRBTS)

actInterRatHoFromEutraToSA: True CB008731 feature activation flag. This


parameter activates/deactivates the inter-RAT
handover from LTE to 5G-SA from 5G (target)
point of view.

nonContentRachAcFullConfigHO: True By default, this parameter is set to ‘True’ but in


this scenario, Contention Free Random Access
will not be used during such HO (setting of this
parameter does not matter) as configuration of
the CB007742 (LTE side) will not allow to
configure the UE to provide beam level
measurements of NR target cells which are
required by the gNB to assign dedicated
preamble for Contention Free Random Access
Procedure.

T304: 2000ms This parameter defines the timer value to be


configured in the UE for successful completion
of random access on the corresponding SpCell or
primary cell.

tNgRelocExecDeltL: 5000ms This parameter indicates the delta for


supervision timer for the handover execution
phase of handover from E-UTRA to NR-SA at the
target gNB.
The supervision timer tNgRelocExec is the sum
of NRBTS.t304 and this parameter.

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
18

5.1.2 A2 and A1 events and timer related parameters (NRCELL)

nrhoirDNlist This parameter indicates the list of distinguished


name(s) of the NRHOIR (IRAT handover
parameters) associated with the NR Cell

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
19

A2 event thresholds

a2ThresholdhoSsbRsrpSA This parameter indicates the threshold value for RS


type SS/PBCH blocks and measurement quantities
RSRP to be used in NR measurement report triggering
condition on event A2 for handover in SA mode.

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
20

A1 event thresholds

a1ThresholdhoSsbRsrpSA This parameter indicates the threshold value for RS


type SS/PBCH blocks and measurement quantities
RSRP to be used in NR measurement report triggering
condition on event A1 for handover in SA mode.

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
21

5.1.3 LTE target cell parameters including B2 event (NRHOIR)

allowedMeasBandwidth This parameter indicates transmission bandwidth of


the adjacent LTE cell. This parameter must be in-line
with the adjacent TDD LTE cell’s chBw parameter or
FDD LTE cell’s dlChBw and ulChBw value.

b2MeashoEnabled This parameter indicates the measurement


configuration that is enabled on event B2 for
handover. This can be the RSRP measurement or the
RSRQ measurement or both or combined criteria.

earfcnValue This parameter indicates the carrier frequency used


by the adjacent LTE TDD cell (earfcn) or FDD cell in DL
direction (earfcnDL) value.

b2Threshold1hoRsrp This parameter indicates the threshold1 value for


measurement quantities of serving cell’s RSRP to be
used in NR measurement report triggering condition
on event B2 for handover.

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
22

b2Threshold2hoRsrp This parameter indicates the threshold2 value for


measurement quantities of the neighbor cell’s RSRP
to be used in NR measurement report triggering
condition on event B2 for handover.

The above mentioned RSRP thresholds (a2ThresholdhoSsbRsrpSA, a1ThresholdhoSsbRsrpSA,


b2Threshold1hoRsrp, b2Threshold2hoRsrp) are given in a relative way that can be translated to an
absolute RSRP value by adding them to -156dBm.

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
23

5.1.4 NRBTS level LTE cell adjacency (NRADJECELL)

earfcnValue This parameter indicates the carrier frequency used


by the adjacent LTE TDD cell (earfcn) or FDD cell in DL
direction (earfcnDL) value.

eNodeBId This parameter indicates the Macro eNB identifier


within the Global eNB Id of an adjacent eNB,
practically lnBtsId value in LTE BTS side.

ePSTrackingAreaCode This parameter indicates the EPS Tracking Area Code


of the adjacent LTE cell, practically tac value in LTE
cell side.

lcrId This parameter indicates the E-UTRAN local cell


resource identifier. The lcrId is unique within an eNB,
practically lcrId value in LTE cell side.

physCellId This parameter indicates the physical cell ID of the


adjacent E-UTRAN cell, practically phyCellId value in
LTE cell side.

mcc, mnc, mncLength and ePSTrackingAreaCode have to be given in-line with the settings of the
target LTE cell.

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
24

5.1.5 NR cell level LTE cell adjacency (NRRELE)

eNodeBId This parameter indicates the Macro eNB identifier


within the Global eNB Id of an adjacent eNB,
practically lnBtsId value in LTE BTS side

lcrId This parameter indicates the E-UTRAN local cell


resource identifier. The lcrId is unique within an eNB,
practically lcrId value in LTE cell side.

mcc, mnc and mncLength have to be given in-line with the settings of the target LTE cell.

5.1.6 New Radio Performance Management (NRPMRNL)

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
25

6 CMU (5G)
6.1 AMF
N26 supports a subset of the functionalities (essential for interworking) that are supported over S10.

The AMF supports the subscribed UE usage type for selecting the target MME during the 5GS to EPS

handover procedure.

GTPv2-C is used over the N26 signaling interface between EPC and 5GC

Support of UE usage type for selecting target MME

The AMF receives the UE usage type either from the unified data management (UDM) during the access
and mobility (AM) registration update procedure or from a source MME during EPS to 5Gs mobility
procedure.

The subscription data from UDM always take precedence (if it is different from the UE usage type
received from the MME).

When the UE usage type is available in AMF, it is used as a service parameter (that is, x-3gpp-mme:xs10+
ue-<ue usage type> to select a target MME during the 5GS to EPS handover procedure in the DNS query
step). If there is no DNS record that matches the UE usage type, then a selection of another record is

performed based on the record priority/weight.

Below config steps are needed to enable N26-interworking on AMF:

 Configure DNS-IP END-POINT-config (if not configured)


o cmm serviceIp create --poolType "IPDS" --poolId 0 --
poolMemberId 0 --niType "DNS" --svcIp "10.82.134.71" --
subnetLoc "external" --assignmentType "fixed" --useFds false
o cmm serviceIp create --poolType "IPDS" --poolId 0 --
poolMemberId 1 --niType "DNS" --svcIp "10.82.134.72" --
subnetLoc "external" --assignmentType "fixed" --useFds false

 Configure external dns


o cmm dns modify --dnsConfigName "config" --priDnsIp
"<External DNS-IP>"
 Enable n26 interworking support in amfGParm list
o cmm amfGParms modify --amfGparmName n26iwkSuppt --
amfGparmValue ENABLE

 Create amfServiceIp for N26 interface


o cmm amfServiceIp create --name N26_name --svcIpV4
10.82.134.126 --poolType IPDS --poolMemberId 0 --
assignmentType floating

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
26

 Create GTP profile for N26


o cmm amfGtpProfile create --name N26_GtpProf_name --
sendEchoTimerT3 60000 --waitEchoTimerT3 6000 --echoRequests 9
--contextReqT3 3000 --n3ContextReq 3 --contextRspT3 3000 --
n3ContextRsp 3 --relocationCancelT3 3000 --n3RelocationCancel
3 --relocationCmplT3 3000 --n3RelocationCmpl 3 --
relocationReqT3 3000 --n3RelocationReq 3 --sendPeriodicEcho
true --sendEchoOnFailure true

 Create localEndPointConfig for N26


o cmm amfN26LocalEndPointConfig create --endPointName N26 --
amfServiceIpName N26_name --protocolProfileName
N26_GtpProf_name --enable true

 Enable n26 interworking on amfUePlmnService


o cmm amfUePlmnServices modify ETPLMN --n26Iwk true

 Enable Full DNN support in AMF (Should not use Short DNN)
o cmm amfGParms modify --amfGparmName
alwaysSendDnnWithOperatorIdentifier --amfGparmValue true

 Enable ‘5g4gRetPrefPlmn’ parameter in amfGparam list


o cmm amfGParms modify --amfGparmName 5g4gRetPrefPlmn --
amfGparmValue ENABLE

 Enable ‘use5gNasCount4Eps’ parameter in amfGparam list


o cmm amfGParms modify --amfGparmName use5gNasCount4Eps --
amfGparmValue true

Create new Slice (for 4G Subscriber) config to allow 4G Subscriber in 5G network using sst only (sd
should not be defined)

 Create Default Snssais


o cmm snssai create --name eMBB4G --sliceServiceType 1

o cmm snssai modify eMBB4G --supportedInAllTa true

o cmm snssaiListItem create --snssaiListName Snssai1 --


snssaiName eMBB4G

o cmm allowedSnssai create --name eMBB4G --sliceServiceType 1

o cmm snssaiToDnn create --snssaiToDnnListName DNN1 --


snssaiName eMBB4G --dataNetworkName internet

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
27

o cmm allowedSnssaiListItem create --allowedSnssaiListName


Snssai1 --allowedSnssaiName eMBB4G

 Enable sending 'New Security Context Indicator' NSCI IE in Handover Request, as part of EPS
to 5GS handover

o cmm amfGParms modify --amfGparmName sendNsci --amfGparmValue


true

 Create NF instance for apn/dnn send back by SMF i.e


“internet.mnc040.mcc999.3gppnetwork.org".

o cmm networkFunctionInstance create --instanceId "81838605-


8185-0d98-8786-878885800694" --nfType "SMF" --plmnName
"999_40" --fqdn "internet.mnc040.mcc999.3gppnetwork.org" --
nfServicesListName "smfServices" --supiRangeListName
"HomeSUPI" --defaultNetworkFunction "true" --enable "true" --
nfIpEndPointListName "Nsmf_Common_EpList" --pgwFqdn
"internet.mnc040.mcc999.3gppnetwork.org"

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
28

6.2 SMF

SMF from 5G CMU is configured as Combo-GW (SMF + PGW-C).

Configure full dnn (do not use short dnn)

 / configure mobile-gateway pdn 1 apn


"internet.mnc040.mcc999.gprs"
allow-emergency
pco-option
link-mtu 1456
dns-server-ipv4
primary 10.82.134.12
exit
exit
ip-alloc-method local-pool hss-static
ip-alloc-priority-order hss-static
pdn-type ipv4 ipv6 ipv4v6
selection-mode subscribed-apn ms-provided-apn
network-provided-apn
session-timeout 0
no shutdown

 /configure mobile-gateway pdn 1 signaling diameter mip6-agent-


info use-fqdn internet.mnc040.mcc999.3gppnetwork.org use-realm
mpw

we need to add s5-ref-point under sba-server-services, as this will be used during 5G to 4G HO


preparations

 /configure mobile-gateway pdn 1

sba-server-services
nsmf-pdusession "server-pdu"
n3-interface-realm "n3-default"
s5-ref-point "default"
 /configure mobile-gateway profile pfcp pfcp-association-peer-
list "pfcp-assoc-list" pfcp-peer 10.82.16.65 bfd-enable

 /configure mobile-gateway profile pfcp up-peer-list "upf-peer"


peer 10.82.16.65 network-realm "realm-for-interworking" ip-pool
internet ipv4-prefix 10.82.134.208/29

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
29

 /configure mobile-gateway profile pfcp up-peer-list "upf-peer"


peer 10.82.16.65 apn "internet.mnc040.mcc999.3gppnetwork.org"
network-realm "realm-for-interworking"

 configure mobile-gateway profile pfcp up-peer-list "upf-peer"


peer 10.82.16.65 apn "internet.mnc040.mcc999.3gppnetwork.org" no
block

 configure mobile-gateway profile pfcp up-peer-list "upf-peer"


peer 10.82.16.65 apn "internet.mnc040.mcc999.3gppnetwork.org"
ip-pool-list ip-pool internet

 configure mobile-gateway pdn 1 signaling diameter mip6-agent-


info use-fqdn "internet" use-realm "mpw"

 configure mobile-gateway pdn 1 home-plmn-list "homeplmn"

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
30

6.3 UPF

 Create loopback interface for S5-U under signaling vprn

o configure service vprn 1002


interface "S5-U" create
address 10.82.134.251/32
loopback

 Configure plmn list


o configure mobile-gateway profile list plmn "home"

 Configure plmn list under pdn


o configure mobile-gateway pdn 1 home-plmn-list “home”

 Configure S5 under pdn


o configure mobile-gateway pdn 1

s5 "default"
interface
gtp-u router "vprn1002" "Signaling-
Gateway" interface-realm "default"

 Configure sba-server service under pdn


o configure mobile-gateway pdn 1
sba-server-services
nsmf-pdusession "S5-U"
s5-ref-point "S5-U"
version 1 patch 2
exit

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
31

6.4 5G APC: UDM/UDR

 Configure UDR (UICC, NGC-Profile, Subscriber)


 Create UE profile having 2 nssai within ‘sm-data’ section:
o One with st only (no sd for 4G UEs)
o Second with st:ssd (for 5G UE)
 Enable "iwkEpsInd" under sm-data ("iwkEpsInd": true)
 Enable "iwkEpsInd" under nss for subscriber nssai ("iwkEpsInd": true)
 UE profile should contain full dnn in under smd-data while short dnn should be used under
am-data and smf-sel data section, example as below:
 Define apn/dnn in standard format having (mcc/mnc)

Below Profile can be used as a reference:

{"add": { "profiles" :
[
{
"name":"n26-profile",
"am": {
"gpsis": [
"msisdn-12345"
],
"subscribedUeAmbr": {
"uplink": "200 Mbps",
"downlink": "100 Mbps"
},
"nssai": {
"defaultSingleNssais": [
{
"sst": 1,
"sd": "ABCDEF"
}
]
},
"subscribedDnnList": [
"internet"
]
},
"sm":[
{
"dnnConfigurations": {
"internet.mnc040.mcc999.gprs": {
"3gppChargingCharacteristics": "123A",
"5gQosProfile": {
"5qi": 9,
"arp": {
"preemptCap": "MAY_PREEMPT",
"preemptVuln": "NOT_PREEMPTABLE",
"priorityLevel": 2
}
},
"iwkEpsInd": true,

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
32

"ladnIndicator": true,
"pduSessionTypes": {
"defaultSessionType": "IPV4"
},
"sessionAmbr": {
"downlink": "500 Mbps",
"uplink": "200 Mbps"
},
"sscModes": {
"allowedSscModes": [
"SSC_MODE_2",
"SSC_MODE_1"
],
"defaultSscMode": "SSC_MODE_3"
}
}
},
"singleNssai":
{
"sst": 1
}
},
{
"dnnConfigurations": {
"internet.mnc040.mcc999.gprs": {
"3gppChargingCharacteristics": "123A",
"5gQosProfile": {
"5qi": 9,
"arp": {
"preemptCap": "MAY_PREEMPT",
"preemptVuln": "NOT_PREEMPTABLE",
"priorityLevel": 2
}
},
"iwkEpsInd": true,
"ladnIndicator": true,
"pduSessionTypes": {
"defaultSessionType": "IPV4"
},
"sessionAmbr": {
"downlink": "500 Mbps",
"uplink": "200 Mbps"
},
"sscModes": {
"allowedSscModes": [
"SSC_MODE_2",
"SSC_MODE_1"
],
"defaultSscMode": "SSC_MODE_3"
}
}
},
"singleNssai":
{

"sst": 1,
"sd": "ABCDEF"
}

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
33

}
],
"nss":{
"subscribedSnssaiInfos":{
"1-ABCDEF":{
"dnnInfos":[{
"dnn":"internet",
"iwkEpsInd": true
}]
}
}
}
}
]
}}

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
34

7 CMU-(4G)
7.1 MME

 Create GTP profile for N26 and S10 interafce


o cmm gtpProfile create --name N26 --description N26 --
sendEchoTimerT3 60000
o cmm gtpProfile create --name S10 --description S10 --
sendEchoTimerT3 60000

 Configure external dns


o cmm dns modify --dnsConfigName "config" --priDnsIp
"<External DNS-IP>"

 Create localEndPointConfig for N26 and for S10 interafec


o cmm localEndPtCfg create --avRequested 0 --dscpCode AF11 --
interfaceName S10 --protocolProfileName S10 --shutdown false

o cmm localEndPtCfg create --avRequested 0 --dscpCode AF11 --


interfaceName N26 --protocolProfileName N26 --shutdown false

 Create ServiceIp for N26 interface


o cmm serviceIp create --poolType IPDS --poolId 0 --poolMemberId 0
--niType N26 --svcIp 10.82.16.72

 Enable ‘n26iwk’ parameter in gParam list


o cmm gParms modify --gParmName n26iwk --gParmValue ON

 Enable ‘discoverMme’ parameter in gParam list


o cmm gParms modify --gParmName discoverMme --gParmValue Yes

 Enable ‘pgwSelectionWithSnaptr’ parameter in gParam list


o cmm gParms modify --gParmName pgwSelectionWithSnaptr --
gParmValue Yes

 Enable ‘use5gNasCount4Eps’ parameter in gParam list

 cmm amfGParms modify --amfGparmName use5gNasCount4Eps --


amfGparmValue true

 Create ‘plmnSecurityProfile’

PlmnSecurity is being created whenever an MME PLMN is created. So it is tied to the PLMN. This profile
intents for a given range of IMSIs that can point to a different plmnSecurity. This new profile is used as
an override to plmnSecurity - if it is provisioned and linked.

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
35

o [cmm@cmm-1-necc0 ~]$ cmm plmnSecurityProfile create --name


interrat5gAuth
+-------------------------+----------------+
| Field | Value |
+-------------------------+----------------+
| plmnSecurityProfileList | interrat5gAuth |
| name* | interrat5gAuth |
+-------------------------+----------------+
[cmm@cmm-1-necc0 ~]$
o [cmm@cmm-1-necc0 ~]$ cmm plmnSecurityProfile modify --
plmnSecurityProfileListName interrat5gAuth --procedureName
TAUpdate --irat5gAuth true
+------------------------------+-------------------------+
| Field | Value |
+------------------------------+-------------------------+
| plmnSecurityProfile | interrat5gAuth~TAUpdate |
| plmnSecurityProfileListName* | interrat5gAuth |
| procedureName* | TAUpdate |
| authInteraction | 10 |
| gutiReallocation | 20 |
| irat5gAuth | true |
+------------------------------+-------------------------+

 Configure the map of a 5G security context to an EPS security context to comply with 3GPP
TS33.501
o cmm gParms modify --gParmName use5gNasCount4Eps –gParmValue Yes

 Varify gParm list with attached one

MME-gParm-list.cfg

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
36

7.2 SGW

7.2.1 Create loopback interface for S5, S5-U and S11 under signaling vprn
configure service vprn 1002
interface "S5" create
address 10.82.16.250/32
loopback
exit
interface "S5-U" create
address 10.82.16.251/32
loopback
exit
interface "S11" create
address 10.82.16.253/32
loopback

7.2.2 Create S5, S5-U and Sx-N4 under PDN as below


configure mobile-gateway pdn 1

s5 "default"
interface
gtp-c router "vprn1002" "Signaling-Gateway"
interface-realm "default"
gtp-u router "vprn1002" "Signaling-Gateway"
interface-realm "default"
exit
exit
s11 "default"
interface
gtp-c router "vprn1002" "Signaling-Gateway"
s1-u "default" interface-realm "default"
exit
exit
sx-n4 "default"
pfcp-association-list "pfcp-list"
interface
pfcp router "vprn1002" "Signaling-Gateway"
exit
signaling
pfcp
profile "pfcp1"
exit
exit
exit
n2 "default"
exit

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
37

7.3 4G APC: HSS/SPR

Login to APC GUI

- Enable parameter ‘Interworking between 5GS and EPS is allowed’, Under ‘configure’  ‘hss-1’

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
38

8 DNS
DNS is needed to support 4GS-5GS Interworking.

8.1 MME AMF selection

During 4G to 5G HO, will send NAPTR query with following format

"tac-lb<TAC-low-byte>.tac-mb<TAC-middle-byte>.tac-hb<TAC-
high-byte>.5gstac.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org“

Where TAC is tracking are identity of the target 5G cell as received in HO required
message

The MME selects AMF with "x-3gpp-amf:x-n26“ in response to enable


interworking

8.2 MME AMF selection


During 4G to 5G idle mobility, will send NAPTR query with following format

“pt<AMF Pointer>.set<AMF Set Id>.region<AMF Region


Id>.amfi.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org”

The MME selects AMF with "x-3gpp-amf:x-n26“ in response to enable


interworking

8.3 AMF MME selection


During 5G to 4G HO, will send NAPTR query with following format

“tac-lb<TAC-lb>.tac-
hb<TAC-hb>.tac.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org”

The AMF selects MME with "x-3gpp-mme:x-s10“ to enable interworking

8.4 AMF MME selection


During 5G to 4G idle mobility, will send NAPTR query with following format

“mmec<MMEC>.mmegi<MMEGI>.mme.epc.mnc<MNC>.mcc<MCC>.3gppnetwor
k.org”

The AMF selects MME with "x-3gpp-mme:x-s10“ to enable interworking

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
39

8.5 Sample DNS configuration

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
40

9 Precheck
9.1 4G attach
Before trying mobility cases, it is suggested to try 4G attach and verify that the UE
session is ready for 5G mobility, Check if Interworking is subscribed.

If Session is not Subscribed, the check :

 N26 is enabled in CMM


 Check iwk parameter in UDR under ‘SM-data’ and under ‘nss-data’ and in APN subscription
 PGW NAPTR response contains “x-3gpp-pgw:x-s5-gtp+nc-smf” in AMF.
 UE is capable for both 4G and 5G network

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
41

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
42

9.2 5G PDU session establishment


Before trying mobility cases, it is suggested to try 5G pdu session establishment and verify that the
UE session is ready for 4G mobility

If session is not-subscribed, then check that

 N26 is enabled in AMF


 UE is subscribed to iwkEPS in UDM
 SMF profile in NRF contains pgwFqdn data
 UE is capable for both 4G and 5G network

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking
43

10 Troubleshooting
For troubleshooting purpose NAS messages should be decoded on wireshark.

 In Wireshark go to preferences -> Protocols -> NAS-5GS -> check the box “Try to detect and
decode 5G-EA0 ciphered message”

In order to view ESP packets :

 Enable below parameters under preferences -> Protocols -> ESP, enable below checkbox:

Some common issues with their resolution are listed as below:

 AMF sending Mac-Failure during Authentication Procedure:


o Problem with AV, verify if SIM card and UDM contains same Ki, OP/oPC
 PDU session establishment Failure (Network Failure):

o check UPF selection config in SMF


o Check APN/DNN on UE is same as what is provisioned in UDR and in SMF/UPF

 PDU session establishment Failure (PDN-Type Not supported):

o Check If SMF/UPF and UDR is provisioned with same PDN-Type (Ipv4/IPv6/IPv4v6) as


configured on UE

 HandoverCancle with cause- radioNetwork: tS1relocprep-expiry (9)

o Check IP configuration of N26 interface on MME, AMF and in DNS


o Check ip reachablity of N26 interface from MME towards AMF
o Check gNB timer
 “tNgRelocPrep” – 2000 ms
o Check eNB timers:
 “tS1eRABModInd” – 2000 ms
 “tS1RelPrepTd” - 500 ms

 UE capability for N26 interworking is disabled in UE capability exchange request:

o Verify if “preferred network type” is “NR/LTE” under test menu (*#*#4636#*#*)


o Verify if 5G is enabled on device

Nokia-Internal © Nokia 2023

MPW23_UR1: N26-Interworking

You might also like