N26 Interworking Config Steps Ver 1.0
N26 Interworking Config Steps Ver 1.0
Release: MPW23-UR1
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
MPW23_UR1: N26-Interworking
2
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.
MPW23_UR1: N26-Interworking
4
Below mentioned procedures (including Mobility) were verified in MPW23_UR1 for data only.
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.
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#*#*)
or
RRC:UeCapabilityEnquiry
MPW23_UR1: N26-Interworking
6
MPW23_UR1: N26-Interworking
7
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.
MPW23_UR1: N26-Interworking
8
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, mncLength and trackingAreaCodeNR have to be given in-line with the settings of the
target 5G-SA cell.
MPW23_UR1: N26-Interworking
9
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.
MPW23_UR1: N26-Interworking
10
MPW23_UR1: N26-Interworking
11
MPW23_UR1: N26-Interworking
12
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.
b2NrTimeToTriggerRsrpMeas Time for which the specific criteria for the RSRP based
B2-NR measurement must be met in order to trigger a
measurement report.
MPW23_UR1: N26-Interworking
13
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.
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.
MPW23_UR1: N26-Interworking
14
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>
MPW23_UR1: N26-Interworking
15
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.
MPW23_UR1: N26-Interworking
16
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.
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:
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.
MPW23_UR1: N26-Interworking
17
MPW23_UR1: N26-Interworking
18
MPW23_UR1: N26-Interworking
19
A2 event thresholds
MPW23_UR1: N26-Interworking
20
A1 event thresholds
MPW23_UR1: N26-Interworking
21
MPW23_UR1: N26-Interworking
22
MPW23_UR1: N26-Interworking
23
mcc, mnc, mncLength and ePSTrackingAreaCode have to be given in-line with the settings of the
target LTE cell.
MPW23_UR1: N26-Interworking
24
mcc, mnc and mncLength have to be given in-line with the settings of the target LTE cell.
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
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
MPW23_UR1: N26-Interworking
26
Enable Full DNN support in AMF (Should not use Short DNN)
o cmm amfGParms modify --amfGparmName
alwaysSendDnnWithOperatorIdentifier --amfGparmValue true
Create new Slice (for 4G Subscriber) config to allow 4G Subscriber in 5G network using sst only (sd
should not be defined)
MPW23_UR1: N26-Interworking
27
Enable sending 'New Security Context Indicator' NSCI IE in Handover Request, as part of EPS
to 5GS handover
MPW23_UR1: N26-Interworking
28
6.2 SMF
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
MPW23_UR1: N26-Interworking
29
MPW23_UR1: N26-Interworking
30
6.3 UPF
s5 "default"
interface
gtp-u router "vprn1002" "Signaling-
Gateway" interface-realm "default"
MPW23_UR1: N26-Interworking
31
{"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,
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"
}
MPW23_UR1: N26-Interworking
33
}
],
"nss":{
"subscribedSnssaiInfos":{
"1-ABCDEF":{
"dnnInfos":[{
"dnn":"internet",
"iwkEpsInd": true
}]
}
}
}
}
]
}}
MPW23_UR1: N26-Interworking
34
7 CMU-(4G)
7.1 MME
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.
MPW23_UR1: N26-Interworking
35
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
MME-gParm-list.cfg
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
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
MPW23_UR1: N26-Interworking
37
- Enable parameter ‘Interworking between 5GS and EPS is allowed’, Under ‘configure’ ‘hss-1’
MPW23_UR1: N26-Interworking
38
8 DNS
DNS is needed to support 4GS-5GS Interworking.
"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
“tac-lb<TAC-lb>.tac-
hb<TAC-hb>.tac.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org”
“mmec<MMEC>.mmegi<MMEGI>.mme.epc.mnc<MNC>.mcc<MCC>.3gppnetwor
k.org”
MPW23_UR1: N26-Interworking
39
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.
MPW23_UR1: N26-Interworking
41
MPW23_UR1: N26-Interworking
42
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”
Enable below parameters under preferences -> Protocols -> ESP, enable below checkbox:
MPW23_UR1: N26-Interworking