CN114079980A

CN114079980A - Switching method and HaloB equipment

Info

Publication number: CN114079980A
Application number: CN202010783274.8A
Authority: CN
Inventors: 孙立新; 李娜; 孙玉飞
Original assignee: Baicells Technologies Co Ltd
Current assignee: Baicells Technologies Co Ltd
Priority date: 2020-08-06
Filing date: 2020-08-06
Publication date: 2022-02-22
Anticipated expiration: 2040-08-06
Also published as: CN114079980B

Abstract

The invention provides a switching method and a HaloB device, which solve the problem of service interruption during switching between the HaloB devices. The method of the invention comprises the following steps: a destination gateway of a destination HaloB acquires a session anchor point switching request message for a terminal; acquiring a first NAT mapping relation between a public network IP address of the terminal and a first private network IP address of the terminal on a source gateway side according to the session anchor point switching request message; and sending an Address Resolution Protocol (ARP) update request message to the upper-level switching equipment of the target gateway, wherein the ARP update request message carries a target Media Access Control (MAC) address corresponding to the public network IP address, and the target MAC address is the MAC address of the target gateway. When the switching occurs between the HaloB devices, the invention can realize uninterrupted service and ensure the normal transmission of the service.

Description

Switching method and HaloB equipment

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a handover method and a HaloB device.

Background

As shown in fig. 1, a HaloB device is a base station that aggregates lightweight core network capabilities, i.e., both the core network capabilities and the base station capabilities are localized, and besides providing the capabilities of the base station, the HaloB device also provides necessary core network capabilities, such as user equipment attachment, signaling transmission, control, and the like.

Since the base stations and the core network are both deployed on the same device, it is default that the base station on each device interacts with a Mobility Management Entity (MME) on the device, establishes a bearer with a gateway of the device, and provides a connection service for the terminal. When a terminal moves from one HaloB device to another, a session anchor point is switched, that is, the current service is interrupted, and reattachment connection is performed.

Disclosure of Invention

The invention aims to provide a switching method and a HaloB device, which are used for solving the problem of service interruption during switching between the HaloB devices.

In a first aspect, the present invention provides a handover method, applied to a destination HaloB, including:

a destination gateway of a destination HaloB acquires a session anchor point switching request message for a terminal;

the destination gateway of the destination HaloB acquires a first NAT mapping relation between the public network IP address of the terminal and a first private network IP address of the terminal on the source gateway side according to the session anchor point switching request message;

and the destination gateway of the destination HaloB sends an ARP (Address resolution protocol) updating request message to the upper-stage switching equipment of the destination gateway, wherein the ARP updating request message carries a destination Media Access Control (MAC) address corresponding to the IP address of the public network, and the destination MAC address is the MAC address of the destination gateway.

In a second aspect, the present invention further provides a handover method, applied to a source HaloB, including:

a source gateway of a source HaloB acquires a session anchor point switching request message aiming at a terminal;

and the source gateway of the source HaloB sends a first NAT mapping relation between the public network IP address of the terminal and a first private network IP address of the terminal on the source gateway side to the destination gateway of the destination HaloB according to the session anchor point switching request message.

In a third aspect, an embodiment of the present invention further provides a HaloB device, where the HaloB device is a target HaloB device, and the method includes:

a destination gateway, the destination gateway comprising:

the first acquisition module is used for acquiring a session anchor point switching request message for a terminal;

a second obtaining module, configured to obtain, according to the session anchor point handover request message, a first NAT mapping relationship between a public network IP address of the terminal and a first private network IP address of the terminal on a source gateway side;

the first sending module is configured to send an ARP update request message to a higher-level switching device of the destination gateway, where the ARP update request message carries a destination MAC address corresponding to the public network IP address, and the destination MAC address is the MAC address of the destination gateway.

In a fourth aspect, an embodiment of the present invention further provides a HaloB device, where the HaloB device is a source HaloB, and the method includes:

a source gateway, the source gateway comprising:

a third obtaining module, configured to obtain a session anchor point handover request message for a terminal;

and the eighth sending module is used for sending the first NAT mapping relation between the public network IP address of the terminal and the first private network IP address of the terminal on the source gateway side to the destination gateway of the destination HaloB according to the session anchor point switching request message.

In a fifth aspect, an embodiment of the present invention further provides a HaloB device, including a memory, a processor, and a computer program stored in the memory and executable on the processor; the processor, when executing the program, implements the steps of the handover method according to the first aspect described above, or implements the steps of the handover method according to the second aspect described above.

In a sixth aspect, the present invention further provides a computer-readable storage medium, on which a computer program is stored, which when executed by a processor implements the steps of the handover method according to the first aspect, or implements the steps of the handover method according to the second aspect.

The embodiment of the invention has the following beneficial effects:

according to the technical scheme of the embodiment of the invention, the session anchor point switching request message aiming at the terminal is obtained through the target gateway of the target HaloB; acquiring a first NAT mapping relation between a public network IP address of a terminal and a first private network IP address of the terminal on a source gateway side according to the session anchor point switching request message; and sending an ARP (address resolution protocol) update request message to the upper-level switching equipment of the destination gateway, wherein the ARP update request message carries a destination Media Access Control (MAC) address corresponding to the IP address of the public network, and the destination MAC address is the MAC address of the destination gateway.

Drawings

FIG. 1 is a schematic structural diagram of a conventional HaloB device;

FIG. 2 is a flowchart illustrating a handover method according to an embodiment of the present invention;

FIG. 3 is a second flowchart illustrating a handover method according to an embodiment of the present invention;

FIG. 4 is a third flowchart illustrating a handover method according to a third embodiment of the present invention;

FIG. 5 is a fourth flowchart illustrating a handover method according to an embodiment of the present invention;

FIG. 6 is a fifth flowchart illustrating a handover method according to an embodiment of the present invention;

FIG. 7 is a sixth flowchart illustrating a handover method according to an embodiment of the present invention;

figure 8 is one of the block schematic diagrams of a HaloB device of an embodiment of the present invention;

fig. 9 is one of schematic implementation structural diagrams of a HaloB device according to an embodiment of the present invention;

figure 10 is a second block schematic diagram of a HaloB device according to an embodiment of the present invention;

fig. 11 is a second schematic structural diagram of a HaloB device according to an embodiment of the present invention.

Detailed Description

In order to make the technical problems, technical solutions and advantages of the present invention more apparent, the following detailed description is given with reference to the accompanying drawings and specific embodiments. In the following description, specific details such as specific configurations and components are provided only to help the full understanding of the embodiments of the present invention. Thus, it will be apparent to those skilled in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the invention. In addition, descriptions of well-known functions and constructions are omitted for clarity and conciseness.

It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

In various embodiments of the present invention, it should be understood that the sequence numbers of the following processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.

In addition, the terms "system" and "network" are often used interchangeably herein.

In the embodiments provided herein, it should be understood that "B corresponding to a" means that B is associated with a from which B can be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may be determined from a and/or other information.

In the embodiment of the present invention, the access network may be an access network including a Macro Base Station (Macro Base Station), a micro Base Station (Pico Base Station), a Node B (3G mobile Station), an enhanced Base Station (eNB), a Home enhanced Base Station (Femto eNB or Home eNode B or Home eNB or HeNB), a relay Station, an access point, an RRU (Remote Radio Unit), an RRH (Remote Radio Head), and the like. The user terminal may be a mobile phone (or handset), or other device capable of sending or receiving wireless signals, including user Equipment, a Personal Digital Assistant (PDA), a wireless modem, a wireless communicator, a handheld device, a laptop computer, a cordless phone, a Wireless Local Loop (WLL) station, a CPE (Customer Premise Equipment) or a mobile smart hotspot capable of converting mobile signals into WiFi signals, a smart appliance, or other devices capable of autonomously communicating with a mobile communication network without human operation, and so on.

In making the description of the embodiments of the present invention, some concepts used in the following description will first be explained.

When initial user equipment is attached to the HaloB, the HaloB interacts with a remote management center, acquires subscription information of the equipment and stores the subscription information in the local, so that verification, authorization and the like of local subscription data are realized when the equipment is attached again. Meanwhile, when the far-end core network fails, the user with the local subscription information stored can be ensured not to be influenced by the far-end core network, and can be normally attached to the network for communication and the like.

UE (User Equipment) moves in different sectors of the same base station (eNB) (intra-cell handover), but the accessed eNB is unchanged (at least the eNB with the same ID), and the eNB is called a mobility anchor point in this scenario.

The UE is handed over between different enbs (inter-cell handover) under the same MME jurisdiction, then the accessed eNB changes, but the MME accessing the service does not change, so in this scenario, the MME is the mobility anchor.

The PGW (PND gateway) is a functional entity that allocates an IP address to the UE and is also a session anchor point during the UE online. When the UE is switched between different eNBs and MME, the session anchor point is kept unchanged, otherwise, the service is interrupted. The SGW (Serving Gateway) and the PGW may be set as one entity. In a halo b application scenario, the SGW and the PGW are collectively referred to as an SGW, and there is one SGW in each halo b to provide a session anchor point for the UE under the halo b.

The following briefly introduces a handoff

The switching includes switching based on X2 and switching based on S1.

The X2 handover refers to the existence of a direct X2 interface between two enbs, and data during handover can be forwarded to each other through an X2 interface, and the two enbs are required to belong to the same MME, that is, the two enbs are connected to the same MME.

The S1 handover refers to that the UE has no direct connection of the X2 interface between two enbs that are handed over, and the MME needs to forward the control signaling through the S1 interface between the enbs and the MME, and at the same time, an indirect handover forwarding tunnel is established, and handover data is forwarded to the target eNB.

Regarding tunnel establishment, an EPS (Evolved Packet System) Bearer in mobile communication includes a Data Radio Bearer (DRB) Bearer on a Radio side, an S1 Bearer between an eNB and an SGW, and an S5/S8 Bearer between the SGW and a PGW. The Radio side Bearer and the S1 Bearer are collectively called E-RAB (evolved Radio Access Bearer) Bearer. The bearers in the EPS bearer are in a one-to-one correspondence relationship.

When the S1 bearer and the S5/S8 bearer are established, a tunneling protocol based on GTP-U (GPRS tunneling protocol user plane) includes creating endpoint numbers at both ends of the bearer, and sending the endpoint numbers to the opposite end in conjunction with the IP address of the endpoint, as an addressing mechanism of the tunnel. Therefore, the tunnel establishment base, i.e. the tunnel end points, knows the TEID (tunnel endpoint Identifier) and IP address of the end point. The following scheme refers to TEID, but includes IP address information by default.

As shown in fig. 2, a schematic flow diagram of a handover method provided in an embodiment of the present invention is applied to a destination HaloB, and the method includes:

step 201, a destination gateway of a destination halo b acquires a session anchor point switching request message for a terminal;

here, the gateway in the halo b is a gateway device having a service gateway function and a NAT (Network Address Translation) function.

Step 202, the destination gateway of the destination HaloB acquires a first NAT mapping relation between the public network IP address of the terminal and a first private network IP address of the terminal at the source gateway side according to the session anchor point switching request message;

it should be noted that, because the destination gateway has the NAT function, the destination gateway can convert the internal private network IP address into the public network IP address, so as to solve the problem of IP address limitation.

Step 203, the destination gateway of the destination HaloB sends an ARP update request message to the upper-level switching device of the destination gateway, where the ARP update request message carries a destination MAC address corresponding to the public network IP address, and the destination MAC address is the MAC address of the destination gateway.

It should be noted that ARP (Address Resolution Protocol) is a TCP/IP Protocol that acquires a physical Address according to an IP Address.

When the host sends information, the ARP request containing the target IP address is broadcasted to all the hosts on the local area network, and the return message is received, so that the physical address of the target is determined; after receiving the return message, the IP address and the physical address are stored in the local ARP cache and are kept for a certain time, and the ARP cache is directly inquired when the next request is made so as to save resources.

The switch device judges the device corresponding to the MAC address of the next hop according to the IP and MAC mapping table and the IP address of the received data packet, and forwards the packet to the device.

When the terminal moves from the source HaloB to the destination HaloB, the MAC address corresponding to the public network IP address of the terminal is updated to the MAC address of the destination gateway because the serving gateway is switched to the destination gateway. Therefore, the upper-level switching equipment of the destination gateway updates the stored IP and MAC mapping table, judges the equipment corresponding to the MAC address of the next hop, namely the destination gateway, according to the IP address of the received data packet, such as the public network IP address of the terminal, and forwards the data packet to the destination gateway, and then the destination gateway can forward the data packet to the terminal.

According to the switching method, a session anchor point switching request message for a terminal is acquired through a target gateway of a target HaloB; acquiring a first NAT mapping relation between a public network IP address of a terminal and a first private network IP address of the terminal on a source gateway side according to the session anchor point switching request message; and sending an ARP (address resolution protocol) update request message to the upper-level switching equipment of the destination gateway, wherein the ARP update request message carries a destination Media Access Control (MAC) address corresponding to the IP address of the public network, and the destination MAC address is the MAC address of the destination gateway.

As an optional implementation manner, the method according to the embodiment of the present invention may further include:

and the destination gateway of the destination HaloB determines a second NAT mapping relation between the public network IP address of the terminal and the private network IP address of the terminal on the destination gateway side.

Here, the step may specifically include:

under the condition that a destination gateway of a destination HaloB allocates a second private network IP address for the terminal, replacing the private network IP address of the terminal in the first NAT mapping relation with the second private network IP address to obtain a second NAT mapping relation;

and under the condition that the destination gateway of the destination HaloB does not allocate the private network IP address to the terminal, the private network IP address of the terminal in the second NAT mapping relation is the first private network IP address.

If the current first private network IP address of the terminal is not used on the destination gateway side, the destination gateway may not assign a new IP address to the terminal.

Based on the embodiment shown in fig. 1, as an optional implementation manner, step 202 of the embodiment of the present invention may include:

the destination gateway of the destination HaloB sends a mapping relation acquisition request message to the source gateway of the source HaloB, wherein the mapping relation acquisition request message comprises the session anchor point switching request message and the information of the terminal;

it should be noted that this step may be performed after the session between the destination MME and the destination gateway is established.

Here, the information of the terminal includes, but is not limited to: an IMSI (International Mobile Subscriber identity) of the terminal, a private network IP address of the terminal, and the like.

And the destination gateway of the destination HaloB receives the first NAT mapping relation sent by the source gateway of the source HaloB based on the mapping relation acquisition request message.

As an optional implementation manner, the method step 201 of the embodiment of the present invention may specifically include:

the destination gateway of the destination HaloB receives a session creation request message which is initiated by a destination mobility management entity MME of the destination HaloB and carries a session anchor point handover request message for the terminal, where the session creation request message further includes a context message of the terminal, bearer information corresponding to the terminal after handover, and a downlink endpoint number of an S1 tunnel used for handover.

Here, the session anchor point handover request message for the terminal may be represented by a preset handover indication.

Before the step is executed, the method may specifically include:

receiving, by a destination HaloB, a target handover request message sent by a source HaloB, where the target handover request message includes: original transmission path information of the terminal;

it should be noted that the original transmission path information of the terminal may include: bearer information of the UE (first bearer information in the embodiment of the present Application), address information of the source MME, identification information or domain name information of the source MME, ID information of S1AP (S1 Application Protocol ) of the source MME and the UE, an address of the uplink source gateway, and the like.

And generating updated path information for switching according to the target switching request message.

Based on the X2 handover, as an optional implementation manner, the receiving, by the destination HaloB, the target handover request message sent by the source HaloB may include:

a destination base station of a destination HaloB, receiving a first handover request message sent by a source base station of a source HaloB, wherein the first handover request message comprises: address information of a source MME of a source HaloB and first bearer information of the terminal;

in this step, the first Handover Request message may be a Handover Request message. It should be noted that, the first handover request message may further include: security information, context information of the terminal, and GUMMEI (Globally Unique MME Identity).

Correspondingly, the generating updated path information for handover according to the handover request message includes:

the destination base station of the destination HaloB allocates second bearing information to the terminal according to the first switching request message, wherein the second bearing information is corresponding bearing information after the terminal is switched;

the destination base station of the destination HaloB generates a downlink endpoint number of the S1 tunnel and a downlink endpoint number of the X2 tunnel for handover.

The downlink endpoint number of the S1 tunnel, namely S1-TEID; the downstream endpoint number of the X2 tunnel, namely X2-TEID. Wherein, the number of the tunnel end points of X2 and S1 is the same as the number of bearers.

Here, after the destination base station receives the first handover request message from the source base station, a response needs to be sent, and as an optional implementation manner, the method of the embodiment of the present invention further includes:

a destination base station of a destination HaloB, which sends a first reply message to a source base station of a source HaloB, wherein the first reply message comprises: a downlink endpoint number of the X2 tunnel and the second bearer information.

As an alternative implementation, the method of the embodiment of the present invention further includes:

the target MME of the target HaloB sends a context acquisition request message of the terminal to the source MME of the source HaloB;

the target MME of the target HaloB receives a context message of the terminal sent by the source MME of the source HaloB, wherein the context message comprises: the international mobile subscriber identity IMSI of the terminal and the first private network IP address.

It should be noted that the context message may also carry information of a context message that uniquely identifies the terminal, such as S1AP of the source MME and the UE.

Optionally, the context acquiring request message carries an indication of acquiring information of a source gateway of the source HaloB; the context message also includes information of the source gateway.

As an optional implementation manner, after step 201 of the method of the embodiment of the present invention, the method of the embodiment of the present invention further includes:

the destination gateway of the destination HaloB generates an uplink endpoint number of the S1 tunnel and bearing information of S1;

and the destination gateway of the destination HaloB sends the uplink endpoint number of the S1 tunnel to the destination MME of the destination HaloB, and the destination MME establishes the mapping relation between the second bearer information and the S1 bearer information according to the context message and the uplink endpoint number of the S1 tunnel.

The implementation mode corresponds to the situation that the destination gateway does not configure a new private network IP address for the terminal.

As another optional implementation manner, after the method step 201 of the embodiment of the present invention, the method of the embodiment of the present invention further includes:

a destination gateway of the destination HaloB, which configures a second private network IP address for the terminal;

and the destination gateway of the destination HaloB sends the uplink endpoint number of the S1 tunnel to the destination MME of the destination HaloB, and the destination MME of the destination HaloB establishes the mapping relation between the second bearer information and the S1 bearer information according to the context message, the uplink endpoint number of the S1 tunnel and the second private network IP address.

The realization mode corresponds to the situation that the destination gateway configures a new private network IP address for the terminal.

Based on this, the method of the embodiment of the present invention may further include:

and the destination MME of the destination HaloB sends an IP address updating instruction to the terminal, wherein the IP address updating instruction comprises the second private network IP address.

Based on the S1 handover, as another optional implementation manner, the receiving, by the destination HaloB, the target handover request message sent by the source HaloB may include:

the destination MME of the destination HaloB receives a second handover request message sent by the source MME of the source HaloB, where the second handover request message includes: a context message of a terminal, the context message comprising: the first bearing information of the terminal, the IMSI of the terminal and the first private network IP address;

in this step, the second handover Request message may be a Forward Relocation Request message.

It should be noted that, in the execution of this step, the source MME of the source HaloB receives a Handover request message sent by the source base station of the source HaloB. This message is used for the handover preparation phase.

Here, the second handover request message may further include: security information, information of the source gateway, etc.

the destination gateway of the destination HaloB generates an uplink endpoint number of the S1 tunnel according to the second switching request message;

the destination base station of the destination HaloB allocates second bearing information to the terminal, wherein the second bearing information is corresponding bearing information after the terminal is switched;

Here, after the destination MME receives the second handover request message sent by the source MME of the source HaloB, a response needs to be sent, and as an optional implementation manner, the method of the embodiment of the present invention further includes:

the destination MME of the destination HaloB sends a second response message to the source MME of the source HaloB, wherein the second response message comprises: the second bearer information, a downlink endpoint number of the X2 tunnel and a first indication message;

the first indication message is used for indicating that: the source base station of the source HaloB establishes an X2 tunnel with the destination base station of the destination HaloB and instructs the source base station to perform an X2 tunnel handover.

It should be noted that, in this embodiment, based on the message flow of S1 handover, an X2 handover tunnel is established, which can reduce the need to process a handover list during handover of a base station X2 and reduce MME messages carried during handover; reducing latency in creation and forwarding of a non-direct tunnel redundant transmission path within a source HaloB at S1-based handover of the source HaloB.

Optionally, the first bearer information includes:

the terminal is currently carrying the bearing information of the service; alternatively, the first and second electrodes may be,

the terminal carries the bearing information of the service currently and target bearing information, and the target bearing information comprises at least one of other bearing information except the bearing information of the service currently carried by the terminal in all the bearing information currently of the terminal.

It should be noted that, in the above description of the limitation on the first bearer information, that is, the bearer information that the UE needs to switch, the first bearer information may not be all the bearer information of the current UE, and only the bearer information of the current bearer service may be sent. For example, currently, the UE has bearer 1, bearer 2, and bearer 3, where bearer 1 is a default bearer, and bearers 2 and 3 are dedicated bearers. At this time, there is a service ongoing on bearer 2, the source eNB sending the Handover Request may only include information of bearer 2 to be switched, and the others may not be carried; the information of bearer 2 and default bearer 1 may also be included for handover, or 3 bearers may all carry the information for handover.

It should be noted that the source eNB needs to have the capability of distinguishing different bearers.

As shown in fig. 3, a schematic flow diagram of a handover method provided in an embodiment of the present invention is a method for an opposite end corresponding to the method for a destination HaloB side, where the method is applied to a source HaloB, and includes:

step 301, a source gateway of a source HaloB acquires a session anchor point switching request message for a terminal;

here, likewise, the source gateway of the source HaloB is also a gateway device having a service gateway function and a NAT function.

And step 302, the source gateway of the source HaloB sends a first NAT mapping relation between the public network IP address of the terminal and the first private network IP address of the terminal on the source gateway side to the destination gateway of the destination HaloB according to the session anchor point switching request message.

In the switching method of the embodiment of the invention, a session anchor point switching request message for a terminal is acquired through a source gateway of a source HaloB; and sending a first NAT mapping relation between the public network IP address of the terminal and the first private network IP address of the terminal on the source gateway side to a target gateway of the target HaloB according to the session anchor point switching request message, so that the target gateway of the target HaloB can send an ARP update request message to the upper-level switching equipment of the target gateway, wherein the ARP update request message carries a target Media Access Control (MAC) address corresponding to the public network IP address, and the target MAC address is the MAC address of the target gateway.

As an optional implementation manner, step 302 of the method according to the embodiment of the present invention may specifically include:

the source gateway of the source HaloB receives a mapping relation acquisition request message sent by a destination gateway of the destination HaloB, wherein the mapping relation acquisition request message comprises the session anchor point standby switching request message and the information of a terminal;

it should be noted that this step may be performed after the destination gateway of the destination HaloB establishes the session between the destination MME and the destination gateway.

Here, the session anchor device handover request message may be represented by a preset handover indication, that is, the preset handover indication is carried in the mapping relationship acquisition request message.

The source gateway of the source HaloB searches a first NAT mapping relation between the public network IP address of the terminal and a first private network IP address of the terminal on the source gateway side according to the information of the terminal;

and the source gateway of the source HaloB sends the first NAT mapping relation to the destination gateway of the destination HaloB.

As an optional implementation manner, before step 301 of the method according to the embodiment of the present invention, the method according to the embodiment of the present invention may further include:

a source HaloB sends a target switching request message to a target HaloB, wherein the target switching request message comprises: and original transmission path information of the terminal.

Here, the target handover request message carries the original transmission path information of the terminal, and the purpose of the target handover request message is to generate updated path information for handover based on the original transmission path information of the terminal.

Based on the X2 handover, as an optional implementation manner, the sending, by the source HaloB, a target handover request message to the destination HaloB includes:

a source base station of a source HaloB sends a first switching request message to a destination base station of the destination HaloB, wherein the first switching request message comprises: address information of a source MME of the source HaloB, and first bearer information of the terminal.

Based on this, the method of the embodiment of the present invention further includes:

a source base station of a source HaloB, receiving a first reply message sent by a target base station of a target HaloB, wherein the first reply message comprises: a downlink endpoint number of the X2 tunnel and second bearer information, where the second bearer information is corresponding bearer information after the terminal is switched.

As an optional implementation manner, the embodiment of the present invention may further include:

the source MME of the source HaloB receives a context acquisition request message of the terminal sent by the target MME of the target HaloB;

a source MME of the source HaloB, sending a context message of the terminal to a target MME of the target HaloB, wherein the context message comprises: the international mobile subscriber identity IMSI of the terminal and the first private network IP address.

Here, optionally, the context acquiring request message carries an indication of acquiring information of a source gateway of the source HaloB; the context message also includes information of the source gateway.

Based on the S1 handover, as an optional implementation manner, the sending, by the source HaloB, the target handover request message to the destination HaloB includes:

the source base station of the source HaloB sends a third switching request message to the source MME of the source HaloB;

in this step, the third Handover request message is a Handover Required message. This message is used for the handover preparation phase.

A source MME of a source HaloB sending a second handover request message to a destination MME of a destination HaloB, the second handover request message comprising: a context message of a terminal, the context message comprising: the first bearing information of the terminal, the IMSI of the terminal and the first private network IP address.

the source MME of the source HaloB receives a second response message sent by the destination MME of the destination HaloB, where the second response message includes: a downlink endpoint number of an X2 tunnel, a first indication message and second bearing information, wherein the second bearing information is corresponding bearing information after the terminal is switched;

the source MME of the source HaloB sends the first indication message to a source base station of the source HaloB;

the first indication message is used for indicating that: and establishing an X2 tunnel between the source base station of the source HaloB and the target base station of the target HaloB, and indicating the source base station to switch the X2 tunnel.

Optionally, the first bearer information includes:

and after the source MME of the source HaloB and the source gateway of the source HaloB delete the session with the terminal, the source gateway of the source HaloB reserves and does not distribute the first private network IP address based on preset reservation duration.

It should be noted that the source gateway of the source HaloB reserves the first private network IP address of the terminal for a period of time, including the address mapped to the public network, and no longer allocates, which can avoid the collision with the terminal caused by reallocation.

Here, the preset retention time period is preset or indicated by the target network.

The following specifically describes the implementation process of the handover method of the present invention with respect to the interaction between four example slave devices.

Example one is based on the X2 interface handover without changing the IP address of the UE, as shown in fig. 4:

1) OMC is a unified management system, and configures a neighbor cell HaloB device list capable of being switched for all the HaloB devices;

2) when the UE is switched, the source eNB selects the eNB of the destination HaloB2, namely the target eNB, to perform X2 switching according to the switchable HaloB equipment list configured by the OMC.

Specifically, the source eNB sends a Handover Request message to the target eNB and carries information of the source MME at the same time; the information of the source MME may be address information of the MME, ID information of the MME, domain name information, or the like.

Optionally, the bearer information that needs to be switched is carried in the Handover Request.

Here, the bearer information that needs to be switched may not be all bearer information of the current UE, and only the bearer information of the current bearer service may be sent, for example, there are 3 bearers, bearer 1, bearer 2, and bearer 3, for the current UE. The bearer 1 is a default bearer, the bearers 2 and 3 are dedicated bearers, at this time, a service is in progress on the bearer 2, the source eNB sends the Handover Request, and may only include information of the bearer 2 to perform Handover, and the rest may not be carried; the information of bearer 2 and default bearer 1 may also be included for handover, or 3 bearers may all carry the information for handover. While the source eNB needs to have the capability to distinguish between different bearers.

3) After receiving the Handover Request, the target eNB generates new safety information according to the safety information carried in the message; according to the received bearing information, the address of the uplink path source SGW is known, and a new wireless bearing ID or a plurality of IDs are distributed at the same time; the endpoint numbers of the X2 and S1 tunnels, namely X2-TEID and S1-TEID, are generated simultaneously.

Here, the number of the tunnel end points of X2 and S1 is the same as the number of bearers.

4) The target eNB sends a response to the source eNB, and simultaneously carries the relevant information of the corresponding bearer and the endpoint number of the X2 tunnel.

5) The destination eNB sends a path switching request to a local MME (destination MME), and simultaneously carries information of a bearer to be switched, including an end point number of the S1 downlink tunnel, and also includes an S1AP ID that can uniquely identify the UE in the source MME, such as the source MME and the UE, and information of the source MME.

6) The local MME finds a source MME according to the source MME information and sends UE Context acquisition information to the source MME;

the UE Context acquisition message carries information which can uniquely identify the UE Context; such as S1AP ID of the source MME and the UE, together with an indication to acquire the source SGW + NAT (i.e., source gateway) message. And the source MME sends the context of the UE to the target MME and simultaneously carries the information of the source SGW + NAT.

7) After obtaining the UE Context, the destination MME initiates a request for creating a session to a destination gateway (destination SGW + NAT), that is, the destination gateway, and simultaneously carries the IMSI of the UE, the IP address of the UE, the tunnel endpoint number S1 allocated by the destination eNB, bearer information, source SGW + NAT information, a handover instruction, and the like.

8) And the destination SGW + NAT receives the switching indication in the message, does not allocate an IP address for the UE any more, continues to use the IP address in the message, creates S1 uplink tunnel endpoint numbers with the same number as the bearing number, and sends the tunnel endpoint numbers to the destination MME.

9) The target SGW + NAT acquires the NAT mapping relation of the UE from the source SGW + NAT, and carries UE information and switching indication; after receiving the switching instruction, the source SGW + NAT finds a corresponding mapping relation according to the UE information (ID or IP address), wherein the mapping relation comprises the mapping relation between the UE private IP address and the address of the common IP, and responds to the target SGW + NAT.

And then, the target SGW + NAT stores the mapping relation and sends an IP and MAC mapping relation updating request to the upper-level switch, namely, the MAC address of the mapped source SGW is updated to the MAC of the target SGW.

10) And the target MME sends bearer modification information to the target eNB to inform the target eNB of the tunnel endpoint identifier of the uplink tunnel and the like.

11) After the handover is completed, the target eNB instructs the source eNB to release the relevant information of the UE. And simultaneously, the source eNB sends a release message to the source MME, and the source MME and the source SGW + NAT delete the session of the local UE.

12) The source SGW + NAT reserves the IP address of the UE for a period of time, including addresses mapped to the public network that are no longer reassigned.

Here, the reserved time period may be preset in advance or indicated by the target network.

Example two changes the IP address of the UE based on the X2 interface handover, as shown in fig. 5:

steps a to g of the second example are the same as or similar to steps 1 to 7 of the first example, and are not repeated herein.

h) And the destination SGW receives the switching indication in the message, reserves the source IP address of the UE, reallocates a new IP address for the UE, creates an S1 uplink tunnel endpoint number with the same number as the bearer number, sends the tunnel endpoint number to the destination eNB by virtue of the destination MME, and simultaneously comprises the IMSI of the UE, so that the destination eNB maps the bearer with the UE one by one. The target eNB sends a message for updating the IP address to the UE, carries the new IP address of the UE, optionally carries the old IP address, and/or an address replacement indication.

i) The target SGW + NAT acquires the NAT mapping relation of the UE from the source SGW + NAT, and carries UE information and switching indication; after receiving the switching instruction, the source SGW + NAT finds a corresponding mapping relation according to the UE information (ID or IP address), wherein the mapping relation comprises the mapping relation between the UE private IP address and the address of the common IP, and responds to the target SGW + NAT.

And the target SGW + NAT changes the mapping relation, namely, the IP address 1 is replaced by the newly allocated IP address 2 of the UE, and an updating request of the mapping relation between the IP and the MAC is sent to the upper-level switch, namely, the MAC address of the mapped source SGW is updated to the MAC address of the target SGW.

j) After the handover is completed, the target eNB instructs the source eNB to release the relevant information of the UE. And simultaneously, the source eNB sends a release message to the local MME, and the local MME and the SGW delete the session of the local UE.

k) The source SGW + NAT reserves the IP address assigned to this UE for a period of time, including addresses mapped to the public network that are no longer reassigned.

Example three handover based on X2 and S1 interfaces without changing the IP address of the UE, as shown in fig. 6:

one) OMC is a unified management system, and a neighbor cell HaloB equipment list capable of being switched is configured for all the HaloB equipment;

and secondly) when the UE is switched, the source eNB sends a Handover Required message to the source MME, and the source MME selects a target HaloB, namely the target MME, to switch according to a switchable HaloB equipment list configured by the OMC.

Then, the source MME sends a Forward Relocation Request (Forward Relocation Request) to the destination MME, where the context of the UE is carried, and may specifically include security information and bearer information of the UE, and may also carry information of the source SGW + NAT, and the like.

Third), after obtaining the UE Context, the destination MME initiates a request for creating a session to the destination SGW + NAT (i.e., the destination gateway), and simultaneously carries the IMSI of the UE, the IP address of the UE, the bearer information, and the handover indication, and may also include the source SGW + NAT information, which may also be configured in advance, and the like.

And fourthly) the destination SGW + NAT receives the switching indication in the message, does not allocate an IP address for the UE any more, continues to use the IP address in the message, and simultaneously creates S1 uplink tunnel endpoint numbers with the same number as the bearing number, and sends the tunnel endpoint numbers to the destination MME.

And simultaneously, the target SGW + NAT acquires the NAT mapping relation of the UE from the source SGW + NAT gateway, carries UE information and switching instructions, finds the corresponding mapping relation according to the UE information (ID or IP address) after the source SGW + NAT receives the switching instructions, and responds to the target SGW + NAT, wherein the mapping relation comprises the mapping relation between the private IP address of the UE and the address of the common IP.

The destination SGW + NAT then stores this mapping.

And fifthly), the target MME sends a Handover Request message to the target eNB and simultaneously carries the context of the UE and the endpoint identification of the uplink S1 tunnel distributed by the target SGW + NAT.

Sixth), after receiving the Handover Request, the destination eNB generates new security information according to the security information carried in the message, learns the address of the uplink path source SGW according to the received bearer information, and allocates a new radio bearer ID or multiple IDs. The endpoint numbers of the X2 and S1 tunnels, namely X2-TEID and S1-TEID, are generated simultaneously.

And seventhly) the target eNB sends a response to the target MME, and simultaneously carries the relevant information of the corresponding bearer and the endpoint number of the tunnel.

Eighthly), the destination MME sends a forwarding reallocation response to the source MME, carries information for establishing an X2 tunnel and an instruction for establishing an X2 tunnel, instructs the source eNB and the destination eNB to establish an X2 tunnel and forwards switching data.

Nine) the source MME sends a command to the source eNB to instruct the source eNB to carry out X2 handover, and the tunnel endpoint identifier of the X2 is carried.

Ten) the destination MME sends a bearer modification message to the destination SGW + NAT, and carries the downlink endpoint tunnel identifier of the UE.

Eleven) the target SGW + NAT sends an IP and MAC mapping relation updating request to the upper-level switch gateway, namely, the MAC address of the source SGW + NAT is updated to the MAC address of the target SGW + NAT.

Twelve) upon completion of the handover, the destination HaloB2 instructs the source HaloB1 to release the relevant information for this UE. And simultaneously, the source eNB sends a release message to the source MME, and the source MME and the source SGW + NAT delete the session of the local UE.

Thirteen) the source SGW + NAT reserves the IP address of this UE for a period of time, including addresses mapped to the public network that are no longer reassigned.

Here, the reserved time period may be preset in advance or indicated by the target network. In order to avoid collision of the reallocation with this UE.

Example four changing the IP address of the UE based on the switching of the X2 and S1 interfaces, as shown in fig. 7:

wherein, steps a to C are the same as steps one to three in the above example 3, and are not described herein again;

D) the target SGW + NAT receives the switching indication in the message, reserves the source IP address of the UE, reallocates a new IP address for the UE, creates the number of the tunnel end points of the S1 uplink, the number of the tunnel end points is the same as the bearing number, and sends the tunnel end points to the target MME;

steps E to I are the same as steps five to nine of example 3 described above, and are not described herein again;

J) and the target MME sends a bearer modification message to the target SGW + NAT, and carries the downlink endpoint tunnel identifier of the UE. And meanwhile, the destination MME sends a message for updating the IP address to the UE, carries the new IP address of the UE, optionally carries the old IP address and/or an address replacement instruction.

K) The target SGW + NAT acquires the NAT mapping relation of the UE from the source SGW + NAT gateway, and carries UE information and switching indication; after receiving the switching instruction, the source SGW + NAT finds a corresponding mapping relation according to the UE information (ID or IP address), wherein the mapping relation comprises the mapping relation between the UE private IP address and the address of the common IP, and responds to the target SGW + NAT.

And then, the target SGW + NAT changes the mapping relation, namely, the IP address 1 is replaced by the newly allocated IP address 2 of the UE, and an updating request of the mapping relation between the IP and the MAC is sent to the upper-level switch, namely, the MAC address of the mapped source SGW + NAT is updated to the MAC address of the target SGW + NAT.

L) the handover is completed, the destination HaloB2 instructs the source HaloB1 to release the relevant information for this UE. And simultaneously, the source eNB sends a release message to the source MME, and the source MME and the source SGW + NAT delete the session of the local UE.

M) the source SGW + NAT reserves the IP address assigned to this UE for a period of time, including addresses mapped to the public network no longer being reassigned.

Here, the retention period may be preset in advance or indicated by the target network.

As shown in fig. 8, an embodiment of the present invention further provides a HaloB device, where the HaloB device is a destination HaloB device, and the device includes:

a destination gateway, the destination gateway comprising:

a first obtaining module 801, configured to obtain a session anchor point handover request message for a terminal;

a second obtaining module 802, configured to obtain, according to the session anchor switching request message, a first NAT mapping relationship between a public network IP address of the terminal and a first private network IP address of the terminal on a source gateway side;

a first sending module 803, configured to send an ARP update request message to a higher-level switching device of the destination gateway, where the ARP update request message carries a destination MAC address corresponding to the public network IP address, and the destination MAC address is the MAC address of the destination gateway.

Optionally, the destination gateway includes:

and the mapping relation determining module is used for determining a second NAT mapping relation between the public network IP address of the terminal and the private network IP address of the terminal at the destination gateway side.

Optionally, the mapping relationship determining module includes:

the first processing unit is used for replacing the private network IP address of the terminal in the first NAT mapping relation with a second private network IP address to obtain a second NAT mapping relation under the condition that a destination gateway of a destination HaloB allocates the second private network IP address to the terminal;

and the second processing unit is used for setting the private network IP address of the terminal in the second NAT mapping relation as the first private network IP address under the condition that the destination gateway of the destination HaloB does not allocate the private network IP address to the terminal.

Optionally, the second obtaining module 802 includes:

a first sending unit, configured to send a mapping relationship obtaining request message to a source gateway of a source HaloB, where the mapping relationship obtaining request message includes the session anchor point handover request message and information of a terminal;

and the first receiving unit is used for receiving the first NAT mapping relation sent by the source gateway of the source HaloB based on the mapping relation acquisition request message.

Optionally, the first obtaining module 801 includes:

a second receiving unit, configured to receive a session creation request message that is initiated by a destination mobility management entity MME of a destination HaloB and carries a session anchor point handover request message for a terminal, where the session creation request message further includes a context message of the terminal, bearer information corresponding to the terminal after handover, and a downlink endpoint number of an S1 tunnel used for handover.

Optionally, the HaloB device further comprises: a destination base station of a destination HaloB and a destination MME of the destination HaloB; wherein the destination base station or the destination MME comprises:

a first receiving module, configured to receive a target handover request message sent by a source HaloB, where the target handover request message includes: original transmission path information of the terminal;

and the first processing module is used for generating updated path information for switching according to the target switching request message.

Optionally, in a case that the destination base station includes the first receiving module and the first processing module, the first receiving module includes:

a third receiving unit, configured to receive a first handover request message sent by a source base station of a source HaloB, where the first handover request message includes: address information of a source MME of a source HaloB and first bearer information of the terminal;

the first processing module comprises:

a third processing unit, configured to allocate second bearer information to the terminal according to the first handover request message, where the second bearer information is corresponding bearer information after the terminal is handed over; a downstream endpoint number of the S1 tunnel and a downstream endpoint number of the X2 tunnel are generated for the handover.

Optionally, the destination base station includes:

a second sending module, configured to send a first reply message to a source base station of a source HaloB, where the first reply message includes: a downlink endpoint number of the X2 tunnel and the second bearer information.

Optionally, the destination MME includes:

a third sending module, configured to send a context acquisition request message of the terminal to a source MME of the source HaloB;

a second receiving module, configured to receive a context message of the terminal sent by a source MME of a source HaloB, where the context message includes: the international mobile subscriber identity IMSI of the terminal and the first private network IP address.

Optionally, the destination gateway further includes:

the second processing module is used for generating an uplink endpoint number of the S1 tunnel and bearing information of the S1 tunnel;

a fourth sending module, configured to send the uplink endpoint number of the S1 tunnel to a destination MME of a destination HaloB, where the destination MME establishes a mapping relationship between the second bearer information and the S1 bearer information according to the context message and the uplink endpoint number of the S1 tunnel.

Optionally, the destination gateway further includes:

the first configuration module is used for configuring a second private network IP address for the terminal;

the third processing module is used for generating an uplink endpoint number of the S1 tunnel and bearing information of the S1 tunnel;

a fifth sending module, configured to send the uplink endpoint number of the S1 tunnel to the destination MME of the destination HaloB, where the destination MME of the destination HaloB establishes a mapping relationship between the second bearer information and the S1 bearer information according to the context message, the uplink endpoint number of the S1 tunnel, and the second private network IP address.

Optionally, the destination MME includes:

a sixth sending module, configured to send an IP address update instruction to the terminal, where the IP address update instruction includes the second private network IP address.

Optionally, in a case that the destination MME includes the first receiving module, the first receiving module includes:

a fourth receiving unit, configured to receive a second handover request message sent by a source MME of a source HaloB, where the second handover request message includes: a context message of a terminal, the context message comprising: the first bearing information of the terminal, the IMSI of the terminal and the first private network IP address;

when the destination gateway includes the first processing module, the first processing module includes:

a fourth processing unit, configured to generate an uplink endpoint number of the S1 tunnel according to the second handover request message;

when the destination base station includes the first processing module, the first processing module includes:

a fifth processing unit, configured to allocate second bearer information to the terminal, where the second bearer information is corresponding bearer information after the terminal is switched;

a sixth processing unit, configured to generate a downstream endpoint number of the S1 tunnel and a downstream endpoint number of the X2 tunnel for handover.

Optionally, the destination MME includes:

a seventh sending module, configured to send a second response message to the source MME of the source HaloB, where the second response message includes: the second bearer information, a downlink endpoint number of the X2 tunnel and a first indication message;

Optionally, the first bearer information includes:

In the HaloB device of the embodiment of the invention, a session anchor point switching request message for a terminal is acquired through a first acquisition module of a target gateway of a target HaloB; the second acquisition module acquires a first NAT mapping relation between a public network IP address of the terminal and a first private network IP address of the terminal on the source gateway side according to the session anchor point switching request message; the first sending module sends an ARP (address resolution protocol) updating request message to the upper-level switching equipment of the destination gateway, the ARP updating request message carries a destination Media Access Control (MAC) address corresponding to the public network IP address, and the destination MAC address is the MAC address of the destination gateway.

It should be noted that the HaloB device of the embodiment of the present invention can implement the above steps in the method embodiment applied to the objective HaloB, and can achieve the same technical effect.

In some embodiments of the present invention there is also provided a HaloB device comprising a memory, a processor and a computer program stored on the memory and executable on the processor; when the processor executes the program, the processes applied to the switching method embodiment as described above are implemented, and the same effect can be achieved, and for avoiding repetition, the details are not described here.

The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the computer program implements each process of the foregoing switching method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not described here again. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

Preferably, referring to fig. 9, an embodiment of the present invention further provides a HaloB device, including:

a processor 901, configured to acquire a session anchor point handover request message for a terminal; and acquiring a first NAT mapping relation between the public network IP address of the terminal and a first private network IP address of the terminal on the source gateway side according to the session anchor point switching request message.

The transceiver 902 is configured to send an ARP update request message to a higher-level switching device of the destination gateway, where the ARP update request message carries a destination MAC address corresponding to the public network IP address, and the destination MAC address is the MAC address of the destination gateway.

The processor 901 of the embodiment of the present invention may also be configured to implement the functions implemented by all the modules in the above-mentioned HaloB device embodiment, and may also achieve the same technical effects as those achieved by the above-mentioned HaloB device embodiment.

As shown in fig. 10, an embodiment of the present invention further provides a HaloB device, where the HaloB device is a source HaloB, and includes:

a source gateway, the source gateway comprising:

a third obtaining module 1001, configured to obtain a session anchor point handover request message for a terminal;

an eighth sending module 1002, configured to send, according to the session anchor point handover request message, a first NAT mapping relationship between the public network IP address of the terminal and the first private network IP address of the terminal on the source gateway side to the destination gateway of the destination HaloB.

Optionally, the eighth sending module 1002 includes:

a fifth receiving unit, configured to receive a mapping relationship obtaining request message sent by a destination gateway of a destination HaloB, where the mapping relationship obtaining request message includes the session anchor backup handover request message and information of a terminal;

the searching unit is used for searching a first NAT mapping relation between a public network IP address of the terminal and a first private network IP address of the terminal on a source gateway side according to the information of the terminal;

and the second sending unit is used for sending the first NAT mapping relation to a destination gateway of a destination HaloB.

Optionally, the source HaloB further comprises: a source base station and a source MME of a source HaloB; wherein the source base station or the source MME includes:

a ninth sending module, configured to send a target handover request message to a target HaloB, where the target handover request message includes: and original transmission path information of the terminal.

Optionally, in a case that the source base station includes the ninth sending module, the ninth sending module includes:

a third sending unit, configured to send a first handover request message to a destination base station of the destination HaloB, where the first handover request message includes: address information of a source MME of the source HaloB, and first bearer information of the terminal.

Optionally, the source base station includes:

a third receiving module, configured to receive a first reply message sent by a destination base station of a destination HaloB, where the first reply message includes: a downlink endpoint number of the X2 tunnel and second bearer information, where the second bearer information is corresponding bearer information after the terminal is switched.

Optionally, the source MME includes:

a fourth receiving module, configured to receive a context acquisition request message of the terminal sent by a destination MME of a destination HaloB;

a tenth sending module, configured to send a context message of the terminal to a destination MME of a destination HaloB, where the context message includes: the international mobile subscriber identity IMSI of the terminal and the first private network IP address.

a fourth sending unit, configured to send a second handover request message to a source MME of the source HaloB, where the source MME of the source HaloB sends the second handover request message to a destination MME of the destination HaloB, and the second handover request message includes: a context message of a terminal, the context message comprising: the first bearing information of the terminal, the IMSI of the terminal and the first private network IP address.

Optionally, the source MME includes:

a fifth receiving module, configured to receive a second response message sent by a destination MME of a destination HaloB, where the second response message includes: a downlink endpoint number of an X2 tunnel, a first indication message and second bearing information, wherein the second bearing information is corresponding bearing information after the terminal is switched;

an eleventh sending module, configured to send the first indication message to a source base station of a source HaloB;

Optionally, the first bearer information includes:

Optionally, the source gateway includes:

and the fourth processing module is configured to, after the source MME of the source HaloB and the source gateway of the source HaloB both delete sessions with the terminal, reserve and not allocate the first private network IP address based on a preset reservation duration.

In the halo B device of the embodiment of the invention, a session anchor point switching request message for a terminal is acquired through a third acquisition module of a source gateway of a source halo B; and the eighth sending module sends the first NAT mapping relation between the public network IP address of the terminal and the first private network IP address of the terminal on the source gateway side to the destination gateway of the destination HaloB according to the session anchor point switching request message, so that the destination gateway of the destination HaloB can send an ARP update request message to the upper-stage switching equipment of the destination gateway, the ARP update request message carries a destination Media Access Control (MAC) address corresponding to the public network IP address, and the destination MAC address is the MAC address of the destination gateway.

It should be noted that the HaloB device of the embodiment of the present invention can implement the steps in the above-mentioned method embodiment applied to the source HaloB, and can achieve the same technical effect.

Preferably, referring to fig. 11, an embodiment of the present invention further provides a HaloB device, including:

a processor 1101 configured to obtain a session anchor point handover request message for a terminal.

And the transceiver 1102 is configured to send, to the destination gateway of the destination HaloB, a first NAT mapping relationship between the public network IP address of the terminal and the first private network IP address of the terminal on the source gateway side according to the session anchor point handover request message.

The processor 1101 of the embodiment of the present invention may also be configured to implement the functions implemented by all the modules in the above-mentioned HaloB device embodiment, and may also achieve the same technical effects as those achieved by the above-mentioned HaloB device embodiment.

In various embodiments of the present invention, it should be understood that the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

While the foregoing is directed to the preferred embodiment of the present invention, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the appended claims.

A1. A switching method applied to a destination HaloB is characterized by comprising the following steps:

A2. The method of claim a1, wherein the method further comprises:

A3. The method of claim a2, wherein the determining the second NAT mapping between the terminal's public network IP address and the terminal's private network IP address on the destination gateway side comprises:

A4. The method of claim a1, wherein the obtaining the first NAT mapping relationship between the public network IP address of the terminal and the first private network IP address of the terminal on the source gateway side according to the session anchor point handover request message includes:

A5. The method of claim a1, wherein the obtaining the session anchor point handover request message for the terminal comprises:

A6. The method according to claim a5, wherein before the receiving the create session request message initiated by the destination mobility management entity MME of the destination HaloB and carrying the session anchor point handover request message for the terminal, the method further comprises:

A7. The method according to claim a6, wherein the receiving, by the destination HaloB, the target handover request message sent by the source HaloB comprises:

generating updated path information for handover according to the handover request message includes:

A8. The method of claim a7, wherein the method further comprises:

A9. The method of claim a7, wherein the method further comprises:

A10. The method according to claim a9, wherein the context fetch request message carries an indication to fetch information of the originating gateway of the originating HaloB; the context message also includes information of the source gateway.

A11. The method of claim a7, wherein after the obtaining the session anchor handover request message for the terminal, the method further comprises:

A12. The method of claim a7, wherein after the obtaining the session anchor handover request message for the terminal, the method further comprises:

A13. The method of claim a12, wherein the method further comprises:

A14. The method according to claim a6, wherein the receiving, by the destination HaloB, the target handover request message sent by the source HaloB comprises:

A15. The method of claim a14, wherein the method further comprises:

A16. The method of claim a7 or a14, wherein the first bearer information comprises:

B17. A handover method applied to a Source HaloB, comprising:

B18. The method of claim B17, wherein the sending, according to the session anchor point handover request message, the first NAT mapping relationship between the public network IP address of the terminal and the first private network IP address of the terminal on the source gateway side to the destination gateway of the destination HaloB includes:

B19. The method of claim B17, wherein before the obtaining the session anchor point handover request message for the terminal, the method comprises:

B20. The method of claim B19, wherein the source HaloB sending a target handover request message to a destination HaloB comprises:

B21. The method of claim B20, wherein the method further comprises:

B22. The method of claim B20, wherein the method further comprises:

B23. The method of claim B19, wherein the source HaloB sending a target handover request message to a destination HaloB comprises:

B24. The method of claim B22, wherein the method further comprises:

B25. The method of claim B20 or B23, wherein the first bearer information comprises:

B26. The method of claim B17, wherein the method further comprises:

C27. A HaloB device, said HaloB device being a destination HaloB, comprising: a destination gateway, the destination gateway comprising:

C28. The HaloB device of claim C27, wherein the destination gateway comprises:

C29. The HaloB device of claim C28, wherein the mapping determination module comprises:

C30. The HaloB device of claim C27, wherein the second acquisition module comprises:

C31. The HaloB device of claim C27, wherein the first acquisition module comprises:

C32. The HaloB device of claim C31, further comprising: a destination base station of a destination HaloB and a destination MME of the destination HaloB; wherein the destination base station or the destination MME comprises:

C33. The HaloB device of claim C32, wherein if the destination base station comprises the first receiving module and the first processing module, the first receiving module comprises:

the first processing module comprises:

C34. The HaloB device of claim C33, wherein the destination base station comprises:

C35. The HaloB device of claim C33, wherein the destination MME comprises:

C36. The HaloB device of claim C35, wherein the context retrieval request message carries an indication to retrieve information of a source gateway of the source HaloB; the context message also includes information of the source gateway.

C37. The HaloB device of claim C33, wherein the destination gateway further comprises:

C38. The HaloB device of claim C33, wherein the destination gateway further comprises:

C39. The HaloB device of claim C38, wherein the destination MME comprises:

C40. The HaloB device of claim C32, wherein if the destination MME comprises the first receiving module, the first receiving module comprises:

C41. The HaloB device of claim C40, wherein the destination MME comprises:

C42. The HaloB device of claim C33 or C40, wherein the first bearer information comprises:

D43. A HaloB device, the HaloB device being a source HaloB, comprising: a source gateway, the source gateway comprising:

D44. The HaloB device of claim D43, wherein the eighth sending module comprises:

D45. The HaloB device of claim D43, further comprising: a source base station and a source MME of a source HaloB; wherein the source base station or the source MME includes:

D46. The HaloB device of claim D45, wherein if the source base station comprises the ninth transmitting module, the ninth transmitting module comprises:

D47. The HaloB device of claim D46, wherein the source base station comprises:

D48. The HaloB device of claim D46, wherein the source MME comprises:

D49. The HaloB device of claim D45, wherein if the source base station comprises the ninth transmitting module, the ninth transmitting module comprises:

D50. The HaloB device of claim D48, wherein the source MME comprises:

D51. The HaloB device of claim D46 or D49, wherein the first bearer information comprises:

D52. The HaloB device of claim D43, wherein the source gateway comprises:

E53. A HaloB device comprising a memory, a processor and a computer program stored on the memory and executable on the processor; characterized in that the processor, when executing the program, carries out the steps of the handover method according to any one of claims a1 to a16, or carries out the steps of the handover method according to any one of claims B17 to B26.

F54. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the switching method according to any one of claims a1 to a16, or carries out the steps of the switching method according to any one of claims B17 to B26.

Claims

1. A switching method applied to a destination HaloB is characterized by comprising the following steps:

2. The method of claim 1, further comprising:

3. The method of claim 2, wherein the determining the second NAT mapping between the public network IP address of the terminal and the private network IP address of the terminal on the destination gateway side comprises:

4. The method according to claim 1, wherein the obtaining, according to the session anchor point handover request message, a first NAT mapping relationship between a public network IP address of the terminal and a first private network IP address of the terminal on a source gateway side includes:

5. A handover method applied to a Source HaloB, comprising:

6. The method according to claim 5, wherein the sending, according to the session anchor point handover request message, the first NAT mapping relationship between the public network IP address of the terminal and the first private network IP address of the terminal on the source gateway side to the destination gateway of the destination HaloB comprises:

7. The method of claim 5, wherein before the obtaining the session anchor point handover request message for the terminal, the method comprises:

8. The method of claim 7, wherein the source HaloB sends a target handover request message to a destination HaloB, comprising:

9. A HaloB device, said HaloB device being a destination HaloB, comprising: a destination gateway, the destination gateway comprising:

10. A HaloB device, the HaloB device being a source HaloB, comprising: a source gateway, the source gateway comprising: