LTE439 SGW Relocation With X2 Connection
LTE439 SGW Relocation With X2 Connection
DN251653134
Issue 01
This document includes Nokia proprietary and condential information, which may not be
distributed or disclosed to any third parties without the prior written consent of Nokia. This
document is intended for use by Nokia’s customers (“You”/”Your”) in connection with a
product purchased or licensed from any company within Nokia Group of Companies. Use this
document as agreed. You agree to notify Nokia of any errors you may nd in this document;
however, should you elect to use this document for any purpose(s) for which it is not
intended, You understand and warrant that any determinations You may make or actions
You may take will be based upon Your independent judgment and analysis of the content of
this document.
Nokia reserves the right to make changes to this document without notice. At all times, the
controlling version is the one available on Nokia’s site.
NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES,
INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR
CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT,
REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE
FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF
ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.
© 2022 Nokia.
The LTE439: SGW Relocation with X2 Connection feature extends the functionality of the X2
handover (HO). A serving gateway (S-GW) can be changed during the HO's completion phase
without changing the mobility management entity (MME). In addition, the eNB supports the
release of a list of radio access bearers (E-RABs) indicated by the MME.
The LTE439: SGW Relocation with X2 Connection feature is an enhancement of the LTE53:
Intra and Inter eNB Handover with X2 feature. The novelty introduced with the LTE439: SGW
Relocation with X2 Connection feature is based on two functionalities that are independent
of each other. They can be, however, triggered by one common S1AP: PATH SWITCH
REQUEST ACKNOWLEDGE message. The new concepts are:
1. UL path switch
If the MME advises switching the UL path by providing new pairs of UL transport
addresses and a tunnel endpoint identifier (TEID) for all or some of the UE's E-RABs, then
the eNB reconfigures the transport layer to use the new addresses instead. According to
3GPP, all E-RABs of one UE must be served by one common S-GW. The procedure for that
is as follows:
target eNB sends the S1AP: PATH SWITCH REQUEST message to the MME with a new
TEID for downlink (DL) data
MME reconfigures transport paths in the evolved packet core (EPC)
new target S-GW sends DL data to the target eNB using IP addresses and DL TEIDs
provided in the S1AP: PATH SWITCH REQUEST message
MME responds with the S1AP: PATH SWITCH REQUEST ACKNOWLEDGE message
containing new pairs of IP addresses and TEIDs for UL data (located in the target S-
GW)
eNB switches a path for UL data to be sent to the target S-GW
The MME can provide pairs of UL IP address and TEID only for some of the E-RABs. If the
MME provides IP addresses with a different IP version from the one previously used, the
eNB reacts as in the case of a path-switch failure (for a detailed path-switch view, see
Path switch). That is why, both UL and DL must use the same IP version, for example, IPv4
or IPv6.
2. E-RAB release
According to 3GPP, the purpose of the E-RAB release procedure is to enable the release
of already established E-RABs for a given UE. The procedure uses UE-associated
signalling.
If the MME advises releasing a subset of E-RABs allocated during the HO preparation,
then the eNB starts the radio resource control (RRC) connection reconfiguration
procedure to release the respective data radio bearer (DRB) towards the UE. In contrast
to a regular E-RAB release procedure, no non-access stratum protocol data unit (NAS
PDU) is transferred to the UE. The procedure for that is the following:
target eNB sends the S1AP: PATH SWITCH REQUEST message to the MME to inform
about new IP addresses and DL TEIDs (for E-RAB to be switched in DL)
MME responds with the S1AP: PATH SWITCH REQUEST ACKNOWLEDGE message,
containing the E-RAB To Be Released List information element (IE), to indicate that
MME/S-GW released some of the bearers
eNB starts an RRC connection release procedure to release respective E-RABs towards
the UE and to modify configuration for the remaining E-RAB (if needed)
As a result, the UE is connected to the target cell with a reduced number of E-RABs.
The HO described in the LTE439: SGW Relocation with X2 Connection feature has the same
preparation stage as the one already known via the X2 interface. The only difference takes
place during the HO completion phase, in which the S-GW change is done (it is not changed
The eNB supports the following HO scenarios via the X2 interface in combination with the S-
GW relocation:
inter-eNB, intra-frequency
inter-eNB, inter-frequency band (if enabled)
inter-eNB, intra-frequency band with different center frequency (if enabled)
With the LTE439: SGW Relocation with X2 Connection feature, it rarely happens that the last
QCI1 is released (and it is the MME which decides which E-RAB should be released). This
impacts the features whose configuration depends on the presence of QCI1. The interaction
concerns the following features:
LTE42: DRX in RRC Connected Mode
LTE64: Service-based Handover Thresholds
LTE473: Extended DRX Settings
LTE585: Smart DRX
LTE872: SRVCC to WCDMA
LTE873: SRVCC to GSM
LTE907: TTI Bundling
LTE1140: Intra-frequency Load Balancing
LTE1406: Extended VoLTE Talk Time
LTE1469: Dynamic UE Measurement Configuration
LTE1929: UL Semi-persistant Scheduling
LTE2112: Dedicated Mobility Thresholds for SRVCC
LTE2430: QCI Establishment Triggered Protection Timer
For reference data descriptions, see Single RAN System/SRAN Reference Data
Requirements
For supported hardware and software, see Single RAN Features/List of Features and
Documents/List of Features Supported in Single RAN.
Alarms
There are no alarms related to the LTE439: SGW Relocation with X2 Connection feature.
Commands
There are no commands related to the LTE439: SGW Relocation with X2 Connection feature.
Parameters
There are no parameters related to the LTE439: SGW Relocation with X2 Connection
feature.