Browse Prior Art Database

SYSTEM AND METHOD FOR SUPPORTING X2 HANDOVER IN HENBGW WITH MULTIPLE MME

IP.com Disclosure Number: IPCOM000245691D
Publication Date: 2016-Mar-30
Document File: 3 page(s) / 110K

Publishing Venue

The IP.com Prior Art Database

Related People

Sangram Kishore L: AUTHOR [+4]

Abstract

The Source Mobility Management Entity User Equipment S1 Application Protocol identifier ("Source MME UE S1 AP ID") and the "Local MME UE S1 AP ID" is included in the "Path Switch Request". This helps X2 handover to succeed with overlapping "MME UE S1AP IDs" across MMEs and optimizes the X2 handover procedure in the Home ENodeB (HeNB) Gateway.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 01 of 3

SYSTEM AND METHOD FOR SUPPORTING X2 HANDOVER IN HENBGW WITH MULTIPLE MME

    AUTHORS: Sangram Kishore L Prashanth Narayana Venkateswara Rao Soma

Indermeet Gandhi

CISCO SYSTEMS, INC.

ABSTRACT

    The Source Mobility Management Entity User Equipment S1 Application Protocol identifier ("Source MME UE S1 AP ID") and the "Local MME UE S1 AP ID" is included in the "Path Switch Request". This helps X2 handover to succeed with overlapping "MME UE S1AP IDs" across MMEs and optimizes the X2 handover procedure in the Home ENodeB (HeNB) Gateway.

DETAILED DESCRIPTION

     The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE)mobile communicationspecification specifies different types of handovers for user equipment (UE) devices. The two general types of handovers are X2-based and S1-based. The X2 Application Protocol (X2AP) is used to handle UE mobility within the Evolved f Evolved (UMTS) Terrestrial Radio Access Network (E-UTRAN). The S1-AP (S1 Application Protocol) protocol is used on the control plane between the eNodeB (eNB) and the core network, the Mobility Management Entity (MME). It is used for signaling about the S1 bearer set-up and paging initiation.

    A path switch request during X2-based handover contains only the "Source MME UE S1AP identifier (ID)". It does not contain the other "MME UE S1AP ID" which is generated locally by HeNB Gateway (HeNBGW).

    The HeNBGW is unable to uniquely identify the UE with the "Source MME UE S1AP ID" as this ID is shared across MMEs. As a result, the X2 handover will fail when the HeNBGW connects to more than one MME and these MMEs use overlapping "MME UE S1AP IDs". This is shown in Figures 1 and 2 below.

Copyright 2016 Cisco Systems, Inc.
1


Pa...