WO2016101586A1

WO2016101586A1 - Base station switching method and system, related device, and storage medium

Info

Publication number: WO2016101586A1
Application number: PCT/CN2015/083259
Authority: WO
Inventors: 高音; 和峰
Original assignee: 中兴通讯股份有限公司
Priority date: 2014-12-26
Filing date: 2015-07-03
Publication date: 2016-06-30
Also published as: CN105792292B; CN105792292A

Abstract

Disclosed are a base station switching method and system, a related device, and a storage medium. The method comprises: receiving a path switching request message; and when it is determined, according to the path switching request message, that the switching is switching in a same access gateway, performing local processing; or when it is determined that the switching is not switching in a same access gateway, sending the path switching request message to a core network.

Description

Base station switching method, system and related device, storage medium

Technical field

The present invention relates to a mobile access network technology, and in particular, to a base station handover method, system, related device, and storage medium.

Background technique

With the continuous evolution of wireless communication technologies and standards, mobile packet services have been greatly developed, and the data throughput capability of single terminals is constantly improving. Taking the Long Term Evolution (LTE) system as an example, the downlink maximum rate of 100 Mbps data transmission can be supported in the 20 M bandwidth. In the subsequent enhanced LTE (LTE Advanced) network, the data transmission rate will be further improved, and even Up to 1Gbps.

Based on the existing user plane data protocol stack of LTE, the downlink data received by the evolved base station (Evolved Node B, eNB) from the core network via the User Channel GPRS Tunneling Protocol (GTP-U, GPRS Tunneling Protocol for the User Plane) is solved. After the packet, the Packet Data Convergence Protocol (PDCP) sublayer, the Radio Link Control (RLC) protocol sublayer, the Medium Access Control (MAC) sublayer, and the physical layer are used. The (PHY) process is sent to the user equipment (UE, User Equipment); the processing of the uplink data is the same as the downlink data processing, except that the transmission direction is reversed.

In order to meet the growing demand for data traffic and the geographically uneven nature of services, operators are also adding low-power nodes (LPN, Low Power Node) or small in the process of deploying next-generation communication networks, such as LTE. A cell (Small Cell) or a micro base station (Pico eNB) is used for hotspot enhancement. As the number of LPN cells increases, the network deployment environment becomes more complex and brings some problems:

First, because the number of LPN cells is relatively large, user equipment (UE, User Equipment) When the terminal moves within the network, frequent inter-cell handover (Handover) may occur, which may easily cause problems such as dropped calls of the data service terminal, which may also result in a decrease in user data throughput and user experience. At the same time, such frequent handovers may also cause the terminal and the network, especially the core network, to receive a large amount of signaling impact, which may cause system resources to be congested or even paralyzed;

In addition, the LPN base stations are all connected to the core network (ie, the S1 interface), and the number of interfaces that the core network needs to process is increasing. In some scenarios, such as paging (Paging) or other broadcast services, the core network needs to send data on all relevant interfaces, which also poses great challenges to the processing power of the core network.

Summary of the invention

In view of the above, in order to solve the existing technical problems, the embodiments of the present invention provide a base station handover method, a system, a related device, and a storage medium, which can avoid the impact of frequent switching of the user equipment between the cells on the core network, and reduce the core. The number of interfaces on the network reduces the processing load on the core network.

The technical solution of the embodiment of the present invention is as follows:

The first aspect of the present invention provides a base station handover method, which is applied to an access gateway, and includes:

Receiving a path switch request message;

Performing local processing when determining that the handover is a handover under the same access gateway according to the path switch request message; and determining that the handover is not a handover under the same access gateway, sending the path switch request message to the core network.

In a specific embodiment, the method further includes:

The access gateway sends the service bearer information corresponding to the serving gateway S-GW and/or the service bearer information corresponding to the access gateway to the accessing base station by using the S1 interface message, where the service bearer information includes the bearer UL address and GTP TEID information.

In a specific embodiment, the S1 interface message is any one of the following: initial context establishment, please Request, radio access bearer setup request, radio access bearer modification request, S1 handover request.

In a specific embodiment, before the receiving the path switching request message, the method further includes:

The target base station receives an X2 handover request message from the source base station, where the X2 handover request message carries service bearer information to be established at the target base station, where the service bearer information is service bearer information and/or corresponding to the serving gateway S-GW. Service bearer information of the access gateway;

The target base station interacts with the source base station to implement data forwarding from the source base station to the target base station;

The target base station sends a path switch request message to the access gateway.

In an embodiment, the X2 handover request message further carries: S1 interface connection flag information allocated by the MME to the UE, and/or S1 interface connection flag information allocated by the access gateway to the UE.

In a specific embodiment, the path switch request message carries at least one of the following: an S1 interface connection flag information allocated by the MME to the UE, an S1 interface connection flag information allocated by the access gateway to the UE, and a service gateway S corresponding to the handover required. - Service bearer information of the GW, and service bearer information corresponding to the access gateway that needs to be handed over.

In a specific embodiment, determining whether the handover is a handover under the same access gateway according to the path switch request message includes:

Matching at least one content carried in the path switching request message with the locally saved information, if the matching is successful, determining that the handover is a handover under the same access gateway; otherwise, determining that the handover is not under the same access gateway Switching.

In a specific embodiment, after the performing the local processing, the method further includes:

If the local processing is successful, the path request acknowledgement message is sent; if the local processing fails, the path request failure message is sent, where the path request acknowledgement message carries at least one of the following: the S1 interface connection flag information allocated by the MME to the UE, The S1 interface connection flag information allocated by the access gateway to the UE, the service bearer information corresponding to the serving gateway S-GW to be switched, and the service bearer information corresponding to the access gateway to be switched; the path request failure message Contains failure The reason is the S1 interface connection flag information allocated by the MME to the UE, and/or the S1 interface connection flag information allocated by the access gateway to the UE.

In a second aspect, the embodiment of the present invention further provides an access gateway, including: a first receiving module, a determining module, a local processing module, and a first sending module;

The first receiving module is configured to receive a path switch request message;

The determining module is configured to determine, according to the path switching request message, whether the handover is a handover under the same access gateway;

The local processing module is configured to perform local processing when the determining module determines that the handover is a handover under the same access gateway;

The first sending module is configured to send the path switching request message to the core network when the determining module determines that the switching is not a handover under the same access gateway.

In a specific embodiment, the access gateway further includes a second sending module,

The second sending module is configured to send, by using the S1 interface message, the service bearer information corresponding to the serving gateway S-GW and/or the service bearer information corresponding to the access gateway to the accessed base station, where the service bearer The information includes the bearer UL address and GTP TEID information.

In a specific embodiment, the second sending module is configured to send any one of the following S1 interface messages: an initial context setup request, a radio access bearer setup request, a radio access bearer modification request, and an S1 handover request.

In a specific embodiment, the path switch request message received by the first receiving module carries at least one of the following: an S1 interface connection flag information allocated by the MME to the UE, and an S1 interface connection flag information allocated by the access gateway to the UE, and needs to be switched. Corresponding to the service bearer information of the serving gateway S-GW, and the service bearer information corresponding to the access gateway that needs to be switched.

In a specific embodiment, the determining module is configured to match at least one content carried in the path switching request message with locally saved information, and if the matching is successful, determine that the switching is a handover under the same access gateway; Otherwise, it is determined that the handover is not under the same access gateway. Switch.

In a specific embodiment, the access gateway further includes a third sending module,

The third sending module is configured to: when the local processing is successful, the path request acknowledgement message is sent; when the local processing fails, the path request failure message is sent, where the path request acknowledgement message carries at least one of the following: MME The S1 interface connection flag information allocated to the UE, the S1 interface connection flag information allocated by the access gateway to the UE, the service bearer information corresponding to the serving gateway S-GW to be switched, and the service corresponding to the access gateway that needs to be switched And the path request failure message includes the reason for the failure, and the S1 interface connection flag information allocated by the MME to the UE, and/or the S1 interface connection flag information allocated by the access gateway to the UE.

In a third aspect, the embodiment of the present invention further provides a base station handover system, including an access gateway and a core network device, where

The access gateway is the access gateway described above.

In a specific embodiment, the system further includes a source base station and a target base station, where

The source base station is configured to send an X2 handover request message to the target base station when the handover condition is met, where the X2 handover request message carries service bearer information to be established at the target base station, where the service bearer information corresponds to the service gateway S. - service bearer information of the GW and/or service bearer information corresponding to the access gateway;

The target base station is configured to: after receiving the X2 handover request message from the source base station, interact with the source base station to implement data forwarding from the source base station to the target base station, and then send a path switch request message to the access gateway.

In an embodiment, the X2 handover request message sent by the source base station further carries: S1 interface connection flag information allocated by the MME to the UE, and/or S1 interface connection flag information allocated by the access gateway to the UE.

In a fourth aspect, an embodiment of the present invention provides a computer storage medium, where the computer storage medium stores computer executable instructions, where the computer executable instructions are used to execute the present invention. A base station handover method provided by an embodiment.

The base station switching method, system, related device, and storage medium provided by the embodiment of the present invention receive a path switching request message; and when the switching is determined to be a handover under the same access gateway according to the path switching request message, local processing is performed. And determining, when the handover is not a handover under the same access gateway, sending the path switch request message to the core network. In the embodiment of the present invention, the access gateway is introduced between the base station and the core network, and the access gateway processes the handover between the base stations within the control range of the access gateway, so that the user equipment can frequently avoid switching to the core between the cells. The impact of the network reduces the number of interfaces on the core network and reduces the processing load on the core network.

DRAWINGS

FIG. 1 is a schematic flowchart of a method for handover of a base station according to an embodiment of the present invention;

2 is a schematic structural diagram of an access gateway according to an embodiment of the present invention;

3 is a schematic structural diagram of another access gateway according to an embodiment of the present invention;

4 is a schematic structural diagram of another access gateway according to an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of a system for setting an access gateway according to an embodiment of the present invention; FIG.

6 is a schematic diagram of an interface protocol stack between an access gateway and a base station according to an embodiment of the present invention;

FIG. 7 is a schematic flowchart of X2 handover under the same access gateway according to Embodiment 1 of the present invention;

8 is a schematic flowchart of X2 handover under the same access gateway according to Embodiment 2 of the present invention;

9 is a schematic flowchart of X2 handover under different access gateways according to Embodiment 3 of the present invention;

FIG. 10 is a schematic flowchart of X2 handover under different access gateways according to Embodiment 4 of the present invention.

detailed description

With the increase of the number of LPN cells deployed by operators and individuals in the future, the problem of the increase of the load on the core network is becoming more and more serious. In order to alleviate the load on the core network, the access gateway is used as an interface proxy between the base station and the core network. , respectively connecting the base station and the core network, shielding the access network pair The impact of the core network, specifically, the embodiment of the present invention provides a base station handover method, which is applied to an access gateway (also referred to as a Mobility Anchor (MA)), as shown in FIG. include:

Step 101: Receive a path switch request message.

In a specific embodiment, the path switch request message carries at least one of the following: an S1 interface connection identifier information (Source MME UE S1AP ID) allocated by the MME to the UE, and an S1 interface connection identifier information allocated by the access gateway to the UE (Source) The MA UE S1AP ID), the service bearer information corresponding to the serving gateway S-GW that needs to be switched, and the service bearer information corresponding to the access gateway that needs to be switched,

In the embodiment of the present invention, the target base station receives an X2 handover request message from the source base station, where the X2 handover request message carries service bearer information to be established at the target base station, where the service bearer information is a service corresponding to the serving gateway S-GW. The bearer information and/or the service bearer information corresponding to the access gateway; the target base station interacts with the source base station to implement data forwarding from the source base station to the target base station, and specifically, the target base station completes the handover preparation, and if successful, the feedback switchover The completion message is prepared. If the message fails, the handover preparation failure message is fed back, and the source base station completes the RRC reconfiguration process between the UE and the UE through the air interface. The ground side implements data forwarding from the source base station to the target base station, that is, the source base station switches to the target base station; after that, the target base station sends a path switch request message to the access gateway.

It should be noted that the X2 handover request message may further include: S1 interface connection identifier information allocated by the MME to the UE, and/or S1 interface connection identifier information allocated by the access gateway to the UE.

It should be noted that the X2 handover related message may be implemented by modifying an existing message, or by adding a separate message.

Step 102: Determine, according to the path switch request message, whether the handover is a handover under the same access gateway, and determine that the handover is a handover under the same access gateway, go to step 103; and determine that the handover is not the same When switching under the access gateway, go to step 104.

In a specific embodiment, determining whether the handover is a handover under the same access gateway according to the path switch request message includes: matching at least one content carried in the path switch request message with locally saved information, if matching If successful, it is determined that the handover is a handover under the same access gateway; otherwise, it is determined that the handover is not a handover under the same access gateway.

Step 103: Perform local processing.

In a specific embodiment, if the local processing is successful, the path request acknowledgement message is sent; if the local processing fails, the path request failure message is sent, where the path request acknowledgement message carries at least one of the following: the MME allocates to the UE. The S1 interface connection flag information, the S1 interface connection flag information allocated by the access gateway to the UE, the service bearer information corresponding to the serving gateway S-GW that needs to be switched, and the service bearer information corresponding to the access gateway that needs to be switched; The path request failure message includes the reason for the failure, and the S1 interface connection flag information allocated by the MME to the UE, and/or the S1 interface connection flag information allocated by the access gateway to the UE.

Step 104: Send the path switch request message to the core network.

In order to implement the embodiment of the present invention, after the base station accesses the access gateway, the access gateway may need to send the service bearer information corresponding to the serving gateway S-GW to the accessed base station through the S1 interface message and/or corresponding to the connection. The service bearer information of the gateway, where the service bearer information includes a bearer UL address and GTP TEID information. Here, the S1 interface message may be, but is not limited to, any one of the following: an initial context establishment request (INITIAL CONTEXT SETUP REQUEST), a radio access bearer setup request (E-RAB SETUP REQUEST), and a radio access bearer modification request (E) -RAB MODIFY REQUEST), S1 handover request (S1HANDOVER REQUEST).

On the control plane, the access gateway acts as an interface proxy between the base station and the core network, and shields the core network from the existence of the base station. That is, from the perspective of the base station, the access gateway is equivalent to the mobility management entity (MME); from the perspective of the MME, The access gateway is equivalent to a normal base station. On the user side, the access gateway carries the data transmission between the serving gateway (S-GW) and the base station. From the perspective of the base station, the MA is equivalent to the S-GW; from the perspective of the S-GW, the MA is equivalent to the ordinary base station.

An embodiment of the present invention further provides an access gateway. As shown in FIG. 2, the access gateway includes: a first receiving module 201, a determining module 202, a local processing module 203, and a first sending module 204.

The first receiving module 201 is configured to receive a path switching request message;

The determining module 202 is configured to determine, according to the path switching request message, whether the handover is a handover under the same access gateway;

The local processing module 203 is configured to perform local processing when the determining module 202 determines that the handover is a handover under the same access gateway;

The first sending module 204 is configured to send the path switch request message to the core network when the determining module 202 determines that the handover is not a handover under the same access gateway.

In a specific embodiment, as shown in FIG. 3, the access gateway further includes a second sending module 301.

The second sending module 301 is configured to send, by using an S1 interface message, service bearer information corresponding to the serving gateway S-GW and/or service bearer information corresponding to the access gateway to the accessed base station, where the service The bearer information includes a bearer UL address and GTP TEID information.

In a specific embodiment, the second sending module 301 is configured to send any one of the following S1 interface messages: an initial context setup request, a radio access bearer setup request, a radio access bearer modification request, and an S1 handover request.

In a specific embodiment, the first receiving module 201 is configured to receive the path switching request message carrying at least one of the following: an S1 interface connection flag information allocated by the MME to the UE, and an S1 interface connection flag allocated by the access gateway to the UE. The information, the service bearer information corresponding to the serving gateway S-GW, and the service bearer information corresponding to the access gateway that needs to be switched.

In a specific embodiment, the determining module 202 is configured to match at least one content carried in the path switching request message with locally saved information, and if the matching is successful, determine that the switching is performed under the same access gateway. Switching; otherwise, it is determined that the handover is not a handover under the same access gateway.

In a specific embodiment, as shown in FIG. 4, the access gateway further includes a third sending module 401.

The local processing module 203 is specifically configured to perform local processing according to the path switching request message and a preset control policy;

The third sending module 401 is configured to: when the local processing succeeds, the path request acknowledgement message is sent; when the local processing fails, the path request failure message is sent, where the path request acknowledgement message carries at least one of the following: The S1 interface connection flag information allocated by the MME to the UE, the S1 interface connection flag information allocated by the access gateway to the UE, the service bearer information corresponding to the serving gateway S-GW that needs to be switched, and the corresponding handover gateway corresponding to the access gateway The service bearer information includes the reason for the failure, the S1 interface connection flag information allocated by the MME to the UE, and/or the S1 interface connection flag information allocated by the access gateway to the UE.

The embodiment of the present invention further provides a base station handover system, where the system includes an access gateway and a core network device; wherein the access gateway is the access gateway shown in any of the foregoing FIG. 2 to FIG. .

The access gateway architecture provided by the present invention can avoid the frequency difference between user equipments and cells. The impact of switching on the core network. Reduce the number of interfaces with the core network and reduce the processing load of the core network. Enables efficient management of a large number of low power nodes. At the same time, the architecture modification involved in the present invention is transparent to the user equipment, and the influence on the terminal is avoided. At the same time, the modification of the access network is also reduced, thereby improving network compatibility.

The technical solution of the present invention is further described in detail in the following specific embodiments. In the following specific embodiments, the access gateway serves as an interface proxy between the base station and the core network, and respectively connects the base station and the core network, and shields the access network from the core network. The impact of the control plane interface signaling to ensure that the UE is the access gateway of the access network as the user equipment in the access gateway, wherein the access gateway acts as the access gateway of the user equipment in the access network, When the user equipment moves between cells served by the access gateway, the access gateway remains unchanged.

FIG. 5 is a schematic structural diagram of a system for setting an access gateway according to an embodiment of the present invention. Referring to FIG. 5, a possible handover scenario of a UE in an access gateway scenario includes:

Scenario 1: SeNB1--->SeNB 2 (intra-MA), that is, X2 handover occurs in UE1 under the same access gateway;

Here, the SeNB refers to a small base station (Small eNB).

Scenario 2: SeNB 3<--->MA 2 (intra-MA), that is, UE1 or UE2 switches from the base station to the access gateway under the same access gateway;

Scenario 3: SeNB 2--->SeNB 3 (inter-MA), that is, X2 handover occurs between UE3 or UE4 under the access gateway;

Scenario 4: SeNB 3<--->Macro eNB (inter MA), UE4 switches from the base station under the access gateway to the macro base station.

FIG. 6 is a schematic diagram of an interface protocol stack between an access gateway and a base station in the following specific embodiments.

Example 1

This embodiment describes a scenario in which an X2 handover occurs in a UE under the same access gateway.

The base station acquires related information about the service bearer established by the UE, and obtains the following information:

After the UE accesses the base station under the access gateway, the access gateway sends the service bearer information to the base station through the S1 interface, including the UL address of the service bearer and the GTP TEID information, including the S-GW (bearing UL address and TEID). 1), and corresponds to the access gateway (bearing UL address and TEID 2).

The S1 interface message may be any one of the following: INITIAL CONTEXT SETUP REQUEST, E-RAB SETUP REQUEST, E-RAB MODIFY REQUEST, S1HANDOVER REQUEST message.

FIG. 7 is a schematic flowchart of X2 handover under the same access gateway according to Embodiment 1 of the present invention. As shown in FIG. 7, the process includes:

Step 701: The UE generates an X2 handover between the base stations under the access gateway, and the source base station initiates an X2 handover request to the target base station.

The X2 interface message includes the service bearer information that is required to be established at the target base station, and includes the UL address of the service bearer and the GTP TEID information, including the S-GW corresponding to the S-GW (bearing the UL address and the TEID 1), and corresponding to the access gateway. (bearing UL address and TEID 2). The message may also include the S1 interface connection flag information, the Source MME UE S1AP ID, and/or the S1 interface connection flag information allocated by the access gateway to the UE, and the source MA UE S1AP ID.

Step 702: The target base station completes the handover preparation, and if successful, feeds back the handover preparation completion message, and if it fails, feeds back the handover preparation failure message. The source base station completes the RRC reconfiguration procedure between the UE and the UE through the air interface. The ground side implements data forwarding from the source base station to the target base station.

Step 703: The target base station initiates a path switch request message to the access gateway through the S1 interface.

Here, the handover request message includes the S1 interface connection flag information, the Source MME UE S1AP ID, and/or the S1 interface connection flag information allocated by the access gateway to the UE, and the source MA UE S1AP ID. And the service bearer information that needs to be switched, including the bearer DL address, and TEID1 and/or TEID2.

Step 704: The local processing of the MA includes: after receiving the path switching request message, the access gateway determines, by using the local information, that the handover under the same access gateway occurs;

Here, for example, the S1 interface connection flag information, the Source MME UE S1AP ID, and/or the S1 interface connection flag information allocated by the access gateway to the UE, and the source MA UE S1AP ID, are determined by the carried MME to determine whether the UE has occurred. If the information stored in the same access gateway matches the above information, it is determined that the handover under the same access gateway has occurred, and the termination path switch request message is not forwarded to the MME and is locally processed. Then, the path request confirmation message is sent (step 705). If it fails, a path request failure message is delivered (step 706).

Step 705: The MA sends a path request acknowledgement message to the target base station.

Here, the path request acknowledgement message includes the service bearer information of the path switch success, including the UL address of the service bearer and the GTP TEID information, including the S-GW (bearing UL address and TEID 1), and/or corresponding to the access Gateway (bearing UL address and TEID 2). And the S1 interface connection flag information that is allocated by the MME to the UE, and/or the S1 interface connection flag information that the access gateway allocates to the UE.

Step 706: The MA sends a path request failure message to the target base station.

Here, the path request failure message includes the reason for the failure, and includes the S1 interface connection flag information allocated by the MME to the UE, and/or the S1 interface connection flag information allocated by the access gateway to the UE.

The foregoing switching related message may be implemented by modifying an existing message, or by adding a separate message to implement the foregoing function.

Example 2

FIG. 8 is a schematic flowchart of X2 handover under the same access gateway according to Embodiment 2 of the present invention. As shown in FIG. 8, the process includes:

Step 801: The UE generates an X2 handover between the base stations under the access gateway, and the source base station initiates an X2 handover request to the target base station.

Here, the X2 interface message includes the service bearer information that is required to be established at the target base station, and includes the UL address of the service bearer and the GTP TEID information, including the bearer UL address and the TEID 1 corresponding to the S-GW. The message may also include the S1 interface connection flag information, the Source MME UE S1AP ID, and/or the S1 interface connection flag information allocated by the access gateway to the UE, and the source MA UE S1AP ID.

Step 802: The target base station completes the handover preparation, and if successful, feeds back the handover preparation completion message, and if it fails, feeds back the handover preparation failure message. The source base station completes the RRC reconfiguration procedure between the UE and the UE through the air interface. The ground side implements data forwarding from the source base station to the target base station.

Step 803: The target base station initiates a path switch request message to the access gateway through the S1 interface.

Here, the path switch request message includes the S1 interface connection flag information, the Source MME UE S1AP ID, and/or the S1 interface connection flag information allocated by the access gateway to the UE, and the source MA UE S1AP ID. And the service bearer information that needs to be switched, including the bearer DL address and TEID1.

Step 804: The local processing of the MA includes: after receiving the path switching request message, the access gateway determines, by using the local information, that the handover under the same access gateway occurs;

Here, for example, the source MME UE S1AP ID is used to determine whether the UE has switched under the same access gateway by using the S1 interface connection flag information allocated to the UE by the carried MME. If the locally saved information can match the above information, it is determined to occur. Switching under the same access gateway, then The terminating path switch request message is no longer forwarded to the MME and is locally processed. If successful, the path request acknowledgement message is sent (step 805). If it fails, a path request failure message is sent (step 806).

Step 805: The MA sends a path request acknowledgement message to the target base station.

Step 806: The MA sends a path request failure message to the target base station.

Example 3

This embodiment describes a scenario in which an X2 handover occurs in a UE under different access gateways.

FIG. 9 is a schematic flowchart of X2 handover under different access gateways according to Embodiment 3 of the present invention; Figure, as shown in Figure 9, the process includes:

Step 901: The UE generates an X2 handover between the base stations under different access gateways, and the source base station initiates an X2 handover request to the target base station.

Here, the X2 interface message includes the service bearer information that is required to be established at the target base station, and includes the UL address of the service bearer and the GTP TEID information, including the S-GW corresponding to the S-GW (bearing the UL address and the TEID 1), and corresponding to the connection Into the gateway (bearing UL address and TEID 2). The message may also include the S1 interface connection flag information, the Source MME UE S1AP ID, and/or the S1 interface connection flag information allocated by the access gateway to the UE, and the source MA UE S1AP ID.

Step 902: The target base station completes the handover preparation, and if successful, feeds back the handover preparation completion message, and if it fails, feeds back the handover preparation failure message. The source base station completes the RRC reconfiguration procedure between the UE and the UE through the air interface. The ground side implements data forwarding from the source base station to the target base station.

Step 903: The target base station initiates a path switch request message to the access gateway through the S1 interface.

Here, the path switch request message includes the S1 interface connection flag information, the Source MME UE S1AP ID, and/or the S1 interface connection flag information allocated by the access gateway to the UE, and the source MA UE S1AP ID. And the service bearer information that needs to be switched, including the bearer DL address, and TEID1 and/or TEID2.

Step 904: The local processing of the MA includes: after receiving the path switching request message, the access gateway determines, by using the local information, that the handover under the same access gateway occurs;

Here, for example, the S1 interface connection flag information, the Source MME UE S1AP ID, and/or the S1 interface connection flag information allocated by the access gateway to the UE, and the source MA UE S1AP ID, are determined by the carried MME to determine whether the UE has occurred. If the information stored in the same access gateway fails to match the information, it is determined that a handover under different access gateways is generated, and the path request message is sent to the MME.

Step 905: The MA sends a path request message to the MME.

Step 906: MME local processing, including: MME processing path request message, if successful, sending a path request confirmation message to the access gateway (step 907); otherwise, sending a path request failure message to the access gateway (step 908);

Step 907: The access gateway sends a path request acknowledgement message to the base station.

Here, the path request acknowledgement message includes the service bearer information of the path switch success, including the UL address of the service bearer and the GTP TEID information, including the S-GW (bearing UL address and TEID 1) delivered by the MME, and/or Corresponds to the access gateway (bearing UL address and TEID 2). And the S1 interface connection flag information that is allocated by the MME to the UE, and/or the S1 interface connection flag information that the access gateway allocates to the UE.

Step 908: A path request failure message sent by the access gateway to the base station;

Example 4

FIG. 10 is a schematic flowchart of X2 handover under different access gateways according to Embodiment 4 of the present invention; Figure, as shown in Figure 10, the process includes:

Step 1001: The UE generates an X2 handover between the base stations under the access gateway, and the source base station initiates an X2 handover request to the target base station.

Step 1002: The target base station completes the handover preparation, and if successful, feeds back the handover preparation completion message, and if it fails, feeds back the handover preparation failure message. The source base station completes the RRC reconfiguration procedure between the UE and the UE through the air interface. The ground side implements data forwarding from the source base station to the target base station.

Step 1003: The target base station initiates a path switch request message to the access gateway through the S1 interface.

Step 1004: The local processing of the MA includes: after receiving the path switching request message, the access gateway determines, by using the local information, that the handover under the same access gateway occurs;

Step 1005: The MA sends a path request message to the MME.

Step 1006: The MME performs local processing, including: the MME processes the path request message, and if successful, Sending a path request acknowledgement message to the access gateway (step 1007); otherwise, sending a path request failure message to the access gateway (step 1008);

Step 1007: The access gateway sends a path request acknowledgement message to the base station.

Step 1008: A path request failure message sent by the access gateway to the base station;

The first receiving module, the determining module, the local processing module, the first sending module, the second sending module, and the third sending module in the access gateway provided by the embodiment of the present invention may all be implemented by using a processor in the access gateway. Of course, the functions performed by the above processor can also be implemented by specific logic circuits; in the process of the specific embodiment, the processor can be a central processing unit (CPU), a microprocessor (MPU), a digital signal processor (DSP). Or field programmable gate array (FPGA), etc.

It should be noted that, in the embodiment of the present invention, if the foregoing base station switching method is implemented in the form of a software function module and sold or used as a standalone product, it may also be stored in a computer readable storage medium. Based on such understanding, the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium, including a plurality of instructions. Make a meter The computer device (which may be a personal computer, server, or network device, etc.) performs all or part of the methods described in various embodiments of the present invention. The foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read only memory (ROM), a magnetic disk, or an optical disk. Thus, embodiments of the invention are not limited to any specific combination of hardware and software.

Correspondingly, the embodiment of the present invention further provides a computer storage medium, where the computer storage medium stores computer executable instructions, and the computer executable instructions are used to perform the base station switching method in the embodiment of the present invention.

Those skilled in the art will appreciate that embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention can take the form of a hardware embodiment, a software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.

The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Industrial applicability

In the embodiment of the present invention, the path switch request message is received; when the switch is determined to be the switch under the same access gateway according to the path switch request message, local processing is performed; and the switch is determined not to be the switch under the same access gateway. When the path switching request message is sent to the core network, the embodiment of the present invention controls the switching between the base stations within the control range of the access gateway by introducing the access gateway between the base station and the core network. The processing is performed, so that the impact of frequent switching of the user equipment between the cells on the core network can be avoided, the number of interfaces of the core network is reduced, and the processing load of the core network is reduced.

Claims

A base station handover method is applied to an access gateway, and the method includes:

Receiving a path switch request message;

Performing local processing when determining that the handover is a handover under the same access gateway according to the path switch request message; and determining that the handover is not a handover under the same access gateway, sending the path switch request message to the core network.
The method of claim 1 wherein the method further comprises:

The access gateway sends the service bearer information corresponding to the serving gateway S-GW and/or the service bearer information corresponding to the access gateway to the accessing base station by using the S1 interface message, where the service bearer information includes the bearer UL address and GTP TEID information.
The method according to claim 2, wherein the S1 interface message is any one of the following: an initial context setup request, a radio access bearer setup request, a radio access bearer modification request, and an S1 handover request.
The method of claim 1, wherein before the receiving the path switch request message, the method further comprises:

The target base station receives an X2 handover request message from the source base station, where the X2 handover request message carries service bearer information to be established at the target base station, where the service bearer information is service bearer information and/or corresponding to the serving gateway S-GW. Service bearer information of the access gateway;

The target base station interacts with the source base station to implement data forwarding from the source base station to the target base station;

The target base station sends a path switch request message to the access gateway.
The method according to claim 4, wherein the X2 handover request message further carries: S1 interface connection flag information allocated by the MME to the UE, and/or S1 interface connection flag information allocated by the access gateway to the UE.
The method of claim 1 wherein said path switch request message carries At least one of the following: the S1 interface connection flag information allocated by the MME to the UE, the S1 interface connection flag information allocated by the access gateway to the UE, the service bearer information corresponding to the serving gateway S-GW that needs to be switched, and the corresponding handover required The service bearer information of the access gateway.
The method of claim 6, wherein determining whether the handover is a handover under the same access gateway according to the path switch request message comprises:

Matching at least one content carried in the path switching request message with the locally saved information, if the matching is successful, determining that the handover is a handover under the same access gateway; otherwise, determining that the handover is not under the same access gateway Switching.
The method according to any one of claims 1 to 7, wherein after the performing the local processing, the method further comprises:

If the local processing is successful, the path request acknowledgement message is sent; if the local processing fails, the path request failure message is sent, where the path request acknowledgement message carries at least one of the following: the S1 interface connection flag information allocated by the MME to the UE, The S1 interface connection flag information allocated by the access gateway to the UE, the service bearer information corresponding to the serving gateway S-GW to be switched, and the service bearer information corresponding to the access gateway to be switched; the path request failure message The reason for the failure is included, and the S1 interface connection flag information allocated by the MME to the UE, and/or the S1 interface connection flag information allocated by the access gateway to the UE.
An access gateway, the access gateway includes: a first receiving module, a determining module, a local processing module, and a first sending module;

The first receiving module is configured to receive a path switch request message;

The determining module is configured to determine, according to the path switching request message, whether the handover is a handover under the same access gateway;

The local processing module is configured to perform local processing when the determining module determines that the handover is a handover under the same access gateway;

The first sending module is configured to determine, in the determining module, that the switching is not the same access When the handover is performed under the gateway, the path switch request message is sent to the core network.
The access gateway according to claim 9, wherein the access gateway further comprises a second sending module,

The second sending module is configured to send, by using the S1 interface message, the service bearer information corresponding to the serving gateway S-GW and/or the service bearer information corresponding to the access gateway to the accessed base station, where the service bearer The information includes the bearer UL address and GTP TEID information.
The access gateway according to claim 10, wherein the second sending module is configured to send any one of the following S1 interface messages: an initial context setup request, a radio access bearer setup request, a radio access bearer modification request, S1 switch request.
The access gateway according to claim 9, wherein

The first receiving module, configured to receive the path switching request message, carries at least one of the following: the S1 interface connection flag information allocated by the MME to the UE, the S1 interface connection flag information allocated by the access gateway to the UE, and the corresponding handover required The service bearer information of the serving gateway S-GW and the service bearer information corresponding to the access gateway that needs to be switched.
The access gateway of claim 12, wherein

The determining module is configured to match at least one content carried in the path switching request message with locally saved information, and if the matching is successful, determine that the switching is a handover under the same access gateway; otherwise, determine the switching Not for switching under the same access gateway.
The access gateway according to any one of claims 9 to 13, wherein the access gateway further comprises a third sending module,

The third sending module is configured to: when the local processing is successful, the path request acknowledgement message is sent; when the local processing fails, the path request failure message is sent, where the path request acknowledgement message carries at least one of the following: MME The S1 interface connection flag information allocated to the UE, the S1 interface connection flag information allocated by the access gateway to the UE, the service bearer information corresponding to the serving gateway S-GW to be switched, and the service corresponding to the access gateway that needs to be switched And the path request failure message includes the reason for the failure, and the S1 interface connection flag information allocated by the MME to the UE, and/or the S1 interface connection flag information allocated by the access gateway to the UE.
A base station switching system, the system comprising an access gateway and a core network device; wherein

The access gateway is the access gateway according to any one of claims 9 to 14.
The system of claim 15 wherein the system further comprises a source base station and a target base station, wherein

The source base station is configured to send an X2 handover request message to the target base station when the handover condition is met, where the X2 handover request message carries service bearer information to be established at the target base station, where the service bearer information corresponds to the service gateway S. - service bearer information of the GW and/or service bearer information corresponding to the access gateway;

The target base station is configured to: after receiving the X2 handover request message from the source base station, interact with the source base station to implement data forwarding from the source base station to the target base station, and then send a path switch request message to the access gateway.
The system according to claim 16, wherein the X2 handover request message sent by the source base station further carries: S1 interface connection flag information allocated by the MME to the UE, and/or an S1 interface connection flag allocated by the access gateway to the UE information.
A computer storage medium having stored therein computer executable instructions for performing the base station handover method of any one of claims 1 to 8.